Microsoft Copilot for Security — Prompting Guide
# Microsoft Copilot for Security — Prompting Guide
> A practical guide to Microsoft Copilot for Security: how it works, how SCUs are consumed, and how to write prompts that give you better results without burning unnecessary compute.
---
## What Is Copilot for Security?
Microsoft Copilot for Security is a separate AI product from Microsoft 365 Copilot. It is a security-specific AI assistant that connects to your Microsoft security stack — Defender XDR, Sentinel, Intune, Purview, and Entra — and lets analysts investigate threats, triage incidents, and produce security reports using natural language.
It is **not** a feature of your M365 Copilot license. It runs on its own billing model and its own compute layer.
**Where it lives:**
- Standalone portal: [securitycopilot.microsoft.com](https://securitycopilot.microsoft.com)
- Embedded in Microsoft Defender XDR, Sentinel, Intune, Purview, and Entra (the embedded experience triggers the same SCU consumption)
**What it connects to (plugins/data sources):**
| Plugin | What Copilot can access |
|--------|------------------------|
| Microsoft Defender XDR | Incidents, alerts, devices, users, email threats |
| Microsoft Sentinel | Log data, incidents, watchlists, KQL workspace |
| Microsoft Intune | Device compliance, configuration, app inventory |
| Microsoft Purview | DLP alerts, compliance posture, audit logs |
| Microsoft Entra | Identities, sign-in risk, conditional access, privileged roles |
| Threat Intelligence (MDTI) | Threat actor profiles, CVE enrichment, IOC reputation |
| 3rd-party plugins | ServiceNow, Splunk, and others via the plugin marketplace |
---
## How SCUs Work — The Billing Mechanic
**SCU = Security Compute Unit.** Every interaction with Copilot for Security consumes SCUs. Understanding this mechanic is the most important thing you can do before deploying it at scale.
### SCU Capacity Models
| Model | Cost | How it works |
|-------|------|-------------|
| Provisioned | $4 USD/SCU/hour | Pre-allocated capacity. Billed per hour whether used or not. Stops working when exhausted — analysts see an error until the next hourly cycle. |
| Overage | $6 USD/SCU/hour | Kicks in when provisioned SCUs run out. Must be configured with a cap. |
| M365 E5 Inclusion | Included | 400 SCUs/month per 1,000 paid E5 licenses. Scales with license count. No overage billing — exhaustion = blocked analysts, not surprise charges. |
| M365 E7 | Included | Same inclusion model as E5. |
**Key rule:** Provisioned SCUs are billed per hour, not per minute. One SCU covers roughly one agent skill execution or one AI reasoning step. Complex, open-ended prompts chain multiple reasoning steps and consume multiple SCUs per interaction.
### What Triggers SCU Consumption
| Action | SCU cost |
|--------|---------|
| Simple, specific prompt with clear data source | Low (1–2 SCUs) |
| Open-ended exploratory prompt requiring multi-step reasoning | High (3–8+ SCUs) |
| Promptbook (pre-built workflow) | Medium but predictable |
| KQL skill execution (pre-built query) | Low (~1 SCU per execution) |
| Repeated follow-up prompts to clarify a vague initial prompt | Cumulative — each follow-up burns another SCU |
**The most expensive pattern:** Vague prompt → Copilot reasons broadly → you refine → Copilot reasons again → you refine again. Three prompts where one specific prompt would have done the job.
**The cheapest pattern:** Specific prompt with data source, timeframe, and output format specified → one interaction → done.
---
## The 4 Elements of an Effective Security Prompt
Every prompt to Copilot for Security should include:
| Element | What it does | Example |
|---------|-------------|---------|
| **Goal** | What you want | "Summarize the incident", "List affected devices", "Write an executive summary" |
| **Data source** | Where to look | "in Microsoft Defender XDR", "from Sentinel workspace [name]", "in Entra ID" |
| **Scope** | Timeframe or filter | "from the last 24 hours", "for incident ID 15134", "for user john.doe@company.com" |
| **Output format** | How to present it | "as a bulleted list", "in a paragraph suitable for a manager", "in a table with columns X, Y, Z" |
**Without these elements:** Copilot reasons broadly, uses more SCUs, and returns output you'll need to refine.
**With these elements:** Copilot executes efficiently and returns structured, usable output in one shot.
---
## Prompting Patterns: What Saves SCUs vs. What Burns Them
### ❌ High-cost patternswhen to use it
Community prompt sourced from the open-source GitHub repo kesslernity/awesome-microsoft-copilot-prompts (NOASSERTION). A "Microsoft Copilot for Security — Prompting Guide" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
productivitycommunitydeveloper
source
kesslernity/awesome-microsoft-copilot-prompts · NOASSERTION
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar