azureblog.co.uk
← SC-500 study plan
SC-500 · Manage and monitor security posture

Implement Microsoft Security Copilot

Workspaces and capacity, permissions and roles, plugins, and Microsoft and Security Store agents.

  • 14 min
  • 4 concepts
  • Try it yourself
  • 4-question check

Learn

Security Copilot is a generative AI assistant for security and IT teams, available as a standalone portal and embedded in Defender, Entra, Intune, Purview and other products. Setting it up means providing capacity, deciding who can use it, connecting data sources through plugins, and choosing which agents run.

  1. 1

    Configure workspaces for Security Copilot

    Security Copilot runs on Security Compute Units (SCUs): provision capacity (provisioned SCUs plus optional overage) in an Azure subscription, and link it to a workspace. Workspaces separate teams or regions with their own capacity, settings and data location. Configure data sharing options and where prompts are evaluated.

    Remember: No SCUs, no Copilot.

  2. 2

    Manage permissions and roles in Security Copilot

    Security Copilot roles: Copilot owner (manage settings, capacity, plugins for everyone) and Copilot contributor (use Copilot, create sessions). By default, Security Administrators and Global Administrators are owners. Access to data still depends on the user's own permissions in each product (Copilot acts with the user's identity).

    Remember: Copilot can't see more than the user can.

  3. 3

    Enable and configure plugins

    Plugins connect Copilot to data and actions: Microsoft plugins (Defender XDR, Sentinel, Entra, Intune, Purview, Defender EASM, Azure Firewall), non-Microsoft plugins (ServiceNow, Splunk, and others) and custom plugins (API, KQL or GPT-based). Owners control which plugins are available and whether contributors can add custom plugins.

    Remember: Owners decide who can add custom plugins.

  4. 4

    Enable and configure Microsoft agents and Security Store agents

    Agents run autonomously on tasks, for example the Phishing Triage Agent (Defender), Conditional Access Optimization Agent (Entra), Vulnerability Remediation Agent (Intune) and Data Loss Prevention / Alert Triage agents (Purview). The Microsoft Security Store offers partner agents. Set each agent's identity, permissions, triggers and scope, and review its decisions and feedback.

    Remember: Agents need an identity, permissions and human review.

How Security Copilot fits together

  1. ExperiencesStandalone portal and embedded in Defender, Entra, Intune, Purview
  2. AgentsMicrosoft and Security Store agents that run tasks
  3. PluginsMicrosoft, non-Microsoft and custom data sources
  4. CapacitySecurity Compute Units in workspaces

Try it

Which part of Security Copilot setup?

This interactive part needs JavaScript.

In the portal

  • Security Copilot capacityAzure portal: Security Copilot > Create capacity
  • Owner settingsMicrosoft Defender portal: securitycopilot.microsoft.com > Owner settings
  • AgentsMicrosoft Defender portal: securitycopilot.microsoft.com > Agents

Key terms

Click a card to see the definition.

Check your understanding

4 questions. Score 80% or more and these skills are marked as confident in your SC-500 study plan.

  1. What capacity unit does Security Copilot use?

  2. Can Copilot show a user data they can't otherwise access?

  3. Which role manages Security Copilot settings and plugins?

  4. Where can you get partner-built security agents?

Sources

Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.