EBS Analysis: Learn about Security Copilot for Microsoft 365 E5 and E7 customers

Security Copilot Arrives for Microsoft 365 E5 and E7: What Enterprise Security Teams Need to Know

The economics of enterprise security have shifted. For years, advanced AI-driven security operations required separate procurement, dedicated Azure infrastructure, and specialized capacity planning. Microsoft’s announcement at Ignite 2025 changes that calculus: Security Copilot—complete with embedded agents across Defender, Entra, Intune, and Purview—is now included for eligible Microsoft 365 E5 and E7 customers at no additional license cost.

This inclusion model represents more than a pricing adjustment. It signals a fundamental rearchitecture of how agentic AI integrates into daily security workflows. Organizations that have invested in E5 or E7 licensing now have immediate access to autonomous investigation, automated triage, and context-aware remediation guidance inside the consoles their teams already use. The rollout began November 18, 2025 for existing Security Copilot customers on E5, with phased expansion to all eligible tenants. For security leaders, the question is no longer whether to adopt generative AI for security operations—it is how to operationalize it effectively before the included capacity becomes a constraint.

Architecture and Capabilities: Agentic Defense Across the Security Fabric

Security Copilot’s inclusion in E5/E7 delivers what Microsoft terms “agentic defense”—autonomous, proactive agents embedded directly in product workflows rather than surfaced only through a standalone chat interface. At Ignite 2025, Microsoft introduced dozens of new agents spanning four pillars:

• Microsoft Defender: Security operations agents that classify alerts, summarize threats, and guide incident remediation—reducing mean-time-to-triage for phishing, endpoint detections, and cloud workload alerts.
• Microsoft Entra: Identity and access agents that optimize Conditional Access policies, automate access reviews, and surface risky sign-in patterns before they become incidents.
• Microsoft Purview: Data security agents that triage DLP and insider risk alerts, discover sensitive data across the estate, and accelerate compliance investigations.
• Microsoft Intune: Endpoint management agents that assess configuration changes for security and productivity impact before deployment, maintaining compliant device posture.

These agents operate in two modes: embedded within each product portal (security.microsoft.com, entra.microsoft.com, purview.microsoft.com, intune.microsoft.com) and through the standalone Security Copilot portal for cross-domain investigation. Critically, customers with Microsoft Sentinel can also apply their included SCU allocation to Security Copilot scenarios within Sentinel, extending agentic capabilities to SIEM and SOAR workflows.

Beyond pre-built agents, the platform exposes developer surfaces—Agent Builder, Model Context Protocol (MCP) integration, and Graph APIs—allowing organizations to codify proprietary runbooks as custom agents. Partner-built agents from the Security Store are also supported, with SCU consumption covered under the inclusion model until further notice.

How the Inclusion Model Works: Capacity, Compute Units, and Economics

The most consequential architectural shift is the move from provisioned hourly capacity to a monthly inclusion model based on Security Compute Units (SCUs). Under the prior pay-as-you-go model, customers provisioned SCUs per hour and were billed for the full provisioned amount regardless of actual consumption. The E5/E7 inclusion model eliminates that inefficiency.

Each eligible tenant receives 400 SCUs per month for every 1,000 paid user licenses, capped at 10,000 SCUs monthly. This scales linearly: a 400-user organization receives 160 SCUs/month; a 4,000-user organization receives 1,600 SCUs/month. SCUs represent the compute required to execute AI workloads—prompt processing, agent execution, incident summarization, and data retrieval across integrated services.

Key operational characteristics of the inclusion model:

• No hourly provisioning: SCUs are deducted from the monthly bucket only when work executes. A 40-second prompt consuming 3 SCUs and a 10-second incident summarization consuming 0.5 SCUs deduct 3.5 SCUs total—no idle-hour charges.
• Monthly reset, no rollover: Unused SCUs expire at month-end. Capacity planning must account for seasonal variation in alert volume, investigation peaks, and project-based workloads.
• Default Security Copilot Capacity: An automatically created, tenant-wide capacity object appears in the tenant upon enablement. It carries a default workspace, is shared across all users and experiences, and shows informational UI cost values that do not generate charges.
• Throttling and overage: Usage beyond the monthly allocation will be throttled at a future date. Microsoft has signaled a pay-as-you-go option at $6 per SCU with 30-day advance notice before enforcement.

This model favors bursty, investigation-driven workloads over continuous high-volume automation. Teams running persistent agent loops or high-frequency promptbooks should model their SCU burn rate carefully.

Implementation Considerations: Zero-Click Activation and Administrative Control

Security Copilot provisions automatically for eligible tenants—no Azure subscription linkage, no consent flows, no manual SCU provisioning. Eligible customers receive Microsoft 365 admin center notifications (targeted to Security Admins for Defender/Entra, Purview Compliance Admins for Purview) and see in-product banners across Defender, Purview, Entra, Intune, and the standalone portal.

Auto-provisioning configures several default settings that administrators should review immediately:

• Data geography: The region where customer prompts, responses, and processed data are stored.
• Customer Data sharing preferences: Disabled by default. When enabled, Microsoft may use de-identified data to improve models.
• Microsoft 365 service data access: Enabled by default. Security Copilot can query and process data from licensed M365 services (Defender, Entra, Purview, Intune) to generate responses. Disabling this breaks cross-product scenarios.
• Default role assignments: Security Admin, Global Security Administrator, and Purview Compliance Admin roles receive Security Copilot Owner and Contributor permissions automatically.

Administrators manage these settings in the Security Copilot Owner settings page. A critical nuance: if an organization opts out of M365 service data access, Security Copilot cannot function with Purview, Defender, Entra, or Intune data—effectively limiting it to general knowledge and manually provided context.

For existing Security Copilot customers who previously provisioned paid capacity: Microsoft recommends retaining that capacity rather than deleting it. The inclusion capacity and pre-existing provisioned capacity can coexist, providing a buffer during transition and ensuring continuity if inclusion SCUs are exhausted.

Security and Governance: Data Handling, Access Control, and Compliance

Security Copilot processes Customer Data—including prompts, responses, and data retrieved from integrated M365 services—to generate insights. Microsoft states this data is copied, processed, and stored only to deliver the service and in accordance with product terms and data protection commitments. Access is scoped to the products and permissions configured in the tenant.

Governance considerations for enterprise deployment:

• Role-based access: Default role assignments are broad. Organizations should audit Owner/Contributor assignments and align them with least-privilege principles, particularly in regulated environments where security analysts may not require full Purview or Entra data access.
• Data residency: Verify the auto-selected geography aligns with data sovereignty requirements. The geography determines where prompts and derived artifacts are stored.
• Audit and monitoring: The standalone Security Copilot portal includes an in-product usage dashboard tracking SCU consumption. Security teams should integrate this into existing FinOps and SecOps monitoring to detect anomalous usage patterns that could indicate misconfigured agents or unauthorized experimentation.
• Partner agent risk: Third-party agents from the Security Store consume included SCUs but may require separate partner licensing. Their data handling practices should be evaluated independently; SCU inclusion for partner agents may change in future rollout phases.

Organizations subject to strict regulatory frameworks (GDPR, HIPAA, FedRAMP) should validate that Security Copilot’s data processing architecture—particularly the copying and temporary storage of Customer Data for response generation—aligns with their control requirements. Microsoft’s product terms govern, but tenant-level configuration choices (data sharing off, geography selection) materially affect the compliance posture.

Operational Implications: Workforce Enablement and Capacity Management

The inclusion model removes procurement friction but introduces operational discipline requirements. Because SCUs are a shared, finite monthly resource, security leaders must treat them as a managed asset.

Workforce enablement: In-product recommendation cards suggest high-value use cases—phishing triage, alert summarization, access reviews, vulnerability remediation. However, agents do not auto-deploy. Each team (SOC, Identity, Data Security, IT Admin) must explicitly configure and enable agents in their respective portals. Guided onboarding assists, but organizational change management—training analysts to trust agent outputs, establishing escalation paths for agent errors, defining human-in-the-loop checkpoints—remains the customer’s responsibility.

Capacity governance: With 400 SCUs per 1,000 users monthly, a 5,000-employee organization has 2,000 SCUs to allocate across Defender, Entra, Purview, Intune, Sentinel, and custom agents. High-volume scenarios—continuous phishing triage across thousands of user-reported messages, daily access review automation for hundreds of applications, persistent sensitive data scanning—can consume allocation rapidly. Security operations managers should:

• Establish SCU budgets per team or workload.
• Monitor the usage dashboard weekly, not monthly.
• Prioritize agent deployment by ROI: phishing triage and alert summarization typically yield the highest analyst-time savings per SCU.
• Defer low-ROI custom agents until usage patterns stabilize.

MSP and multi-tenant considerations: Managed service providers deploying Security Copilot for eligible E5/E7 customers after November 18, 2025 will find those customers no longer billed separately. MSPs should update billing models and ensure their admin privileges respect the customer’s data sharing and geography preferences.

Common Pitfalls and Limitations

Several constraints deserve explicit attention during planning:

• Sentinel data lake costs excluded: While Security Copilot scenarios in Sentinel consume included SCUs, the underlying Log Analytics workspace ingestion, retention, and query compute costs remain separate Azure charges.
• Non-agentic Purview investigations excluded: The classic (non-agentic) Data Security Investigations experience in Purview is not covered by the inclusion model.
• Logic Apps integration costs: Automation workflows using Azure Logic Apps with Security Copilot connectors incur standard Logic Apps consumption charges.
• Partner agent licensing: SCU costs for third-party agents are included temporarily, but partner licensing fees (purchased via Security Store) are separate and may change.
• Prerequisite dependencies: Some agents require capabilities outside E5/E7 (e.g., specific Defender plans, Entra ID P2 features). Those prerequisites are not covered by the inclusion.
• No SCU carryover: Monthly reset without rollover means December’s unused capacity cannot offset January’s incident response surge. Plan for peaks.
• Data access toggle is binary: Disabling M365 service data access disables all cross-product Copilot functionality. There is no per-product granularity.

Why This Matters to Enterprise IT

The inclusion of Security Copilot in Microsoft 365 E5 and E7 represents a inflection point for enterprise security architecture. Three factors make this consequential:

1. Democratization of agentic security operations. Previously, organizations needed dedicated budget, Azure expertise, and capacity planning to experiment with generative AI for security. Now, every E5/E7 customer—regardless of size—has a production-grade allocation. Mid-market enterprises that could not justify a separate Security Copilot purchase gain immediate access to the same agentic capabilities as global enterprises.

2. Consolidation of the Microsoft security stack. Agents embedded across Defender, Entra, Purview, and Intune create a unified reasoning layer over previously siloed signal sources. An identity anomaly detected in Entra can trigger a Defender investigation, surface related Purview data exfiltration signals, and inform an Intune device compliance action—all orchestrated through natural language prompts or autonomous agent chains. This cross-domain correlation is the practical realization of the “unified security operations” vision Microsoft has articulated for years.

3. Shift from tool acquisition to capacity stewardship. The limiting factor is no longer license procurement but SCU allocation strategy. Security leaders must now operate like cloud FinOps practitioners: forecasting consumption, setting guardrails, and continuously optimizing agent portfolios. Organizations that treat included SCUs as unlimited will hit throttling; those that implement disciplined capacity governance will extend the inclusion value significantly.

EBS Consulting Perspective

From an enterprise consulting standpoint, this inclusion model accelerates three client conversations we are already having:

Security operations modernization. Clients with mature SOCs have been piloting Security Copilot in standalone mode. The inclusion model lets them shift from pilot to production without new budget cycles. Our guidance: start with the highest-volume, lowest-complexity use case—user-reported phishing triage in Defender. It delivers measurable MTTD/MTTR improvement, consumes predictable SCUs, and builds analyst trust in agent outputs. Expand to alert summarization and guided remediation once the workflow is proven.

Identity governance automation. Entra agents for access review automation and Conditional Access optimization address a perennial pain point: quarterly access review campaigns that consume weeks of identity team effort. The included SCUs make this viable at scale. We recommend clients map their access review catalog, identify high-risk applications, and configure agents for automated evidence gathering and recommendation generation—keeping human approval as the final gate.

Data security and compliance acceleration. Purview agents for DLP alert triage and sensitive data discovery directly reduce the manual investigation burden on privacy and compliance teams. However, clients must validate that auto-provisioned data geography settings satisfy regulatory requirements before enabling Purview data access. We have seen tenants where the default geography conflicted with data residency mandates—requiring a support ticket and re-provisioning delay.

Across all domains, the inclusion model changes the procurement conversation from “should we buy Security Copilot?” to “how do we govern the Security Copilot we already have?” That shift—from acquisition to stewardship—is where consulting value concentrates: capacity planning, role refinement, agent portfolio management, and integration with existing SecOps/ITSM tooling (ServiceNow, Jira, Splunk via Logic Apps or Graph API).

Practical Next Steps

1. Confirm eligibility and activation status. Check the Microsoft 365 admin center Message Center for notifications addressed to Security Admin and Purview Compliance Admin roles. Verify in-product banners in Defender, Entra, Purview, and Intune.
2. Review auto-provisioned defaults. In the Security Copilot Owner settings page, validate: data geography alignment with sovereignty requirements; Customer Data sharing preference (recommend leaving disabled); M365 service data access (enable for cross-product scenarios); role assignments for Owner/Contributor access.
3. Inventory current security workflows by SCU intensity. Map high-frequency tasks (phishing triage, alert enrichment, access reviews, DLP investigation, device compliance checks) and estimate SCU consumption per execution. Prioritize agent enablement by analyst-hours-saved per SCU.
4. Establish capacity governance. Create a monthly SCU budget allocation across teams. Configure the usage dashboard in the standalone Security Copilot portal as a monitored metric. Set alerts at 70% and 90% of monthly allocation.
5. Enable agents incrementally. Start with Defender phishing triage and Entra access review agents. Validate outputs against human analyst benchmarks for two weeks before expanding. Document false positive/negative rates to calibrate trust thresholds.
6. Plan for overage scenarios. Model the $6/SCU pay-as-you-go cost for peak months (incident response surges, audit periods). Determine whether to pre-approve overage or accept throttling as a circuit breaker.
7. Assess custom agent opportunities. Identify repetitive, well-documented runbooks (e.g., “investigate impossible travel alert,” “enrich vulnerability CVE with asset context”) as candidates for Agent Builder. Factor MCP and Graph API integration effort into sprint planning.
8. Engage MSP partners. If you operate through a managed service provider, confirm their billing model reflects the inclusion and that their admin practices respect your data governance choices.

Looking Ahead

The inclusion of Security Copilot in Microsoft 365 E5 and E7 is not a static endpoint—it is the baseline for an evolving agentic security platform. Microsoft’s roadmap signals continued agent proliferation, deeper cross-product reasoning, and expanding developer surfaces for custom automation. The inclusion capacity (400 SCUs per 1,000 users) will likely face pressure as agent capabilities grow and adoption widens.

For enterprise security leaders, the imperative is clear: operationalize the included capability now, build the governance muscle to manage SCUs as a strategic resource, and position the organization to absorb future agentic advances without procurement delays. The technology is provisioned; the competitive advantage belongs to teams that translate it into measurable risk reduction.

EBS Consulting helps security organizations design agent deployment roadmaps, implement SCU governance frameworks, and integrate Security Copilot outputs into existing SecOps and ITSM workflows. If your team is evaluating how to move from inclusion to impact, we should talk.

EBS Consulting Advice

If your organization is evaluating Learn about Security Copilot for Microsoft 365 E5 and E7 customers, do not treat the technology decision in isolation. Start with the business outcome, current architecture, security and identity controls, operational constraints, migration dependencies and governance requirements. A practical assessment should identify the current-state gaps, prioritize the risks and define an implementation roadmap with measurable outcomes.

EBS can help assess the environment, develop the architecture and modernization roadmap, and translate the technical options into an actionable business plan. Relevant EBS services: Microsoft Azure consulting Microsoft Solution Assessments Modern Workplace.

Have a technology challenge? Email info@escapebusinesssolutions.com to describe your situation. We welcome questions, consulting discussions and requests for a proposal.