Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Some information in this article relates to a prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Before you start building security agents, it's important to understand the associated licensing and consumption costs. This article outlines the cost considerations for Microsoft Security Copilot.
Security compute units
Security compute units (SCUs) are the required units of resources that are needed for dependable and consistent performance of Microsoft Security Copilot.
The following are the minimum requirements to help you get started to create an agent:
Security Copilot access that includes needing SCUs. For more information, see Get started with Security Copilot.
Azure subscription to purchase security compute units.
Guidance on SCU consumption
This section outlines when SCUs are consumed based on how agents are created, tested, or published.
| Action | SCUs Consumed | Description |
|---|---|---|
| Creating an agent using natural language (NL2Agent) via Agent builder form | No | Does not spin SCUs |
| NL2Agent via MCP | No | Does not spin SCUs |
| Agent builder form | No | Does not spin SCUs |
| Agent created elsewhere without Security Copilot tools | No | External agent creation does not trigger SCU consumption |
| Test agents | Yes | Always spins SCUs |
| Publish agents | No | Does not spin SCUs |