One of the most common questions we hear from customers is: “How many SCUs do I need to get started with Security Copilot?” Given the dynamic nature of AI-powered security workflows, forecasting compute needs can be a challenge, especially for teams just starting their journey.
Based on my experience, it’s best to start with 3 SCUs and then increase incrementally if queries begin to fail or slow down. I usually find the sweet spot around 5–6 SCUs for medium environments and 6–10 for larger ones.
To make planning easier, Microsoft launch of the Security Copilot capacity calculator,
This tool offers a practical starting point to help estimate how many SCUs my client may require. With a few clicks, customers can get an idea of estimated SCU usage based on inputs like number of users in an embedded Security Copilot experience. While actual consumption may vary as it depends on real-time prompt activity, the calculator serves as a helpful guide for initial provisioning and budget planning.
Once you’ve estimated your baseline needs, you can get started in Security Copilot or in the Azure portal. Security Copilot offers two flexible models to support both predictable workloads and unplanned spikes in usage:
- Provisioned SCUs: Ideal for predictable, ongoing operations. A minimum of one provisioned SCU is required.
- Overage SCUs: Designed for variable demand. Overage SCUs allow usage to scale seamlessly, and customers only pay for what they use, up to their chosen optional overage limit.
With the capacity calculator, organizations can confidently begin their Security Copilot journey and better manage usage to align with their business needs. After getting started, teams can monitor consumption through the in-product usage dashboard and adjust capacity as demand fluctuates. Learn more about Security Copilot pricing here.
