What Is the SC-500 Exam?
SC-500 (Implementing End-to-End Security Controls for Cloud and AI Workloads) is Microsoft's Associate-level certification for the Cloud and AI Security Engineer Associaterole. Per Microsoft's official audience profile, you're a security engineer who protects organizational systems and data across cloud and hybrid environments by implementing controls that proactively prevent unauthorized access and mitigate risk — spanning identity, network, application, data, and compute, plus ensuring the platforms and infrastructure behind AI workloads are securely implemented and monitored.
SC-500 exists because AZ-500 (Microsoft Azure Security Technologies) is retiring on August 31, 2026. Rather than a cosmetic rename, Microsoft rebuilt the exam around a wider mandate: nearly all of AZ-500's identity, networking, storage/database, and Defender for Cloud/Sentinel content carries over, but Secure compute now includes an entire AI-security sub-domain that has no AZ-500 equivalent — Copilot, Microsoft Foundry agents, and Microsoft Entra Agent ID.
You should sit SC-500 if you have practical experience administering Azure and hybrid environments (compute, network, storage), strong familiarity with Microsoft Entra ID, and familiarity with Microsoft 365 administration — the same bar AZ-500 set, now extended to AI workload security.
Exam Snapshot
Exam code
SC-500
Level
Associate
Questions
~40–60
Duration
100 minutes
Passing score
700 / 1000
Cost
$165 USD
Domains
4
Renewal
Free annual online assessment
Domain Breakdown
Straight from Microsoft's official SC-500 skills-measured outline — every bullet below is a tested sub-skill, not a paraphrase.
Domain 1: Manage identity, access, and governance
20–25%Secure access to resources by using Microsoft Entra ID
- • Implement and configure Privileged Identity Management (PIM)
- • Implement conditional access policies
- • Implement and configure authentication methods, including MFA and passwordless
- • Implement and configure identity for applications, including enterprise applications and app registrations
- • Manage OAuth permission grants and consent settings
- • Implement and configure managed identities for Azure resources
Secure secrets and keys by using Azure Key Vault
- • Deploy Key Vault and configure Key Vault settings
- • Configure access to Key Vault and firewall settings on Key Vault
- • Manage keys, secrets, and certificates
- • Scan for secrets by using Defender Cloud Security Posture Management (Defender CSPM)
- • Implement Defender for Key Vault
Implement governance to enforce security and regulatory compliance
- • Implement security controls by using Azure Policy, including built-in and custom definitions
- • Evaluate regulatory compliance and implement security standards/recommendations in Defender for Cloud
- • Implement resource locks; manage built-in and custom role assignments (Azure roles and Entra roles)
- • Evaluate and remediate overprivileged access assignments by using RBAC
- • Configure security controls for backup protection using Azure Backup security features
- • Implement security controls by using infrastructure as code
Domain 2: Secure storage, databases, and networking
25–30% — largestImplement security for storage accounts
- • Configure security for storage accounts and Azure Storage firewall rules
- • Implement Defender for Storage threat protection configurations
- • Manage access to storage, including access policies
Implement security for databases
- • Implement platform-level security configurations in Azure SQL
- • Configure database auditing for Azure SQL Database and Azure SQL Managed Instance
- • Configure Defender for Databases protection across Azure database services
Implement security for Azure network services
- • Implement and manage network security groups (NSGs) and application security groups (ASGs)
- • Implement network access policies by using Azure Virtual Network Manager
- • Configure security for an Azure Virtual WAN and for VPN connections
- • Implement and configure Microsoft Entra Private Access
- • Configure Azure private endpoints (PaaS access) and Azure Private Link services (network resources)
- • Implement and configure Azure Firewall
- • Evaluate effective security rules by using Azure Network Watcher diagnostics
Domain 3: Secure compute
20–25%Implement security for AI — entirely new vs. AZ-500
- • Identify overexposure of data in SharePoint
- • Identify risks to Copilot/AI apps by using Microsoft Purview Data Security Posture Management (DSPM)
- • Enable real-time protection for Microsoft Copilot Studio agents
- • Implement conditional access for Microsoft Entra Agent ID; manage Entra Agent ID access
- • Analyze blast radius for Entra Agent ID risks by using Defender XDR
- • Configure and deploy AI Gateway in Azure API Management for Microsoft Foundry
- • Enable Defender for AI Service in Cloud Workload Protection; configure Foundry agent guardrails
- • Monitor AI security via the Data and AI security dashboard in Defender for Cloud
- • Manage agents in the Microsoft 365 admin center
Implement security for servers and virtual machines
- • Implement disk encryption; plan and implement Azure Bastion
- • Enable and enforce just-in-time (JIT) VM access
- • Extend security controls to hybrid/multicloud servers by using Azure Arc
- • Onboard servers to Defender for Servers; configure vulnerability scanning and EDR
- • Implement agentless scanning for VMs in Defender for Servers
- • Configure secure boot, vTPM, integrity monitoring, and security type on a VM
- • Enforce security configuration of Azure-managed servers via Azure Machine Configuration
Implement security for application platform services
- • Detect misconfigurations and runtime risks in containers via Defender for Containers
- • Configure security controls for AKS, Azure Container Registry, Container Instances, and Container Apps
- • Configure security controls for Azure Functions (auth + network access) and Logic Apps
- • Configure security controls for Azure App Service and Azure Web Application Firewall
- • Implement security policies for back-end API protection by using API Management
Domain 4: Manage and monitor security posture
20–25%Manage security posture by using Defender for Cloud
- • Identify security risks by using Defender CSPM; evaluate compliance against security frameworks
- • Enable and configure Defender for Cloud workload protection plans
- • Connect hybrid cloud and multicloud environments (AWS, GCP) to Defender for Cloud
- • Configure Microsoft Defender Vulnerability Management settings for Azure VMs
- • Discover unprotected assets via Microsoft Defender External Attack Surface Management (EASM)
Implement activity and event collection in Microsoft Sentinel
- • Create and connect workspaces; assign Sentinel roles; implement content hub solutions
- • Configure Microsoft data connectors; implement syslog and CEF event collection
- • Collect Windows Security events via data collection rules, including Windows Event Forwarding
- • Create custom log tables to store ingested data
- • Implement automation rules and playbooks; implement data retention in Sentinel data stores
- • Query Microsoft Purview Audit in Defender XDR
Implement Microsoft Security Copilot
- • Configure workspaces for Security Copilot
- • Manage permissions and roles in Security Copilot
- • Enable and configure plugins, Microsoft agents, and Security Store agents
Coming from AZ-500? Read our AZ-500 Cheat Sheetalongside this guide — nearly every non-AI concept there maps directly onto SC-500.
Five Decision Traps That Separate a Pass From a Fail
Gating an AI agent vs. governing its data vs. detecting misuse
A scenario restricting who can invoke a Microsoft Entra Agent ID-backed agent wants a conditional access policy scoped to the agent. A scenario about the agent overexposing sensitive data wants Microsoft Purview DSPM/DLP. A scenario about detecting an agent behaving maliciously after the fact wants Defender for AI Service or Defender XDR blast-radius analysis. All three sound like "AI security" — only one answers "who can use it."
Private endpoints vs. Private Link services vs. Entra Private Access
Azure private endpoints secure inbound access to a PaaS resource (e.g., a storage account or SQL server) from inside a virtual network. Azure Private Link services expose your own service privately to other virtual networks. Microsoft Entra Private Access secures user/hybrid access to private apps and resources — not PaaS-to-PaaS or service-exposure scenarios. The exam distinguishes them by asking "who or what is connecting to whom."
Azure Bastion vs. JIT VM access vs. NSGs
Bastion gives browser-based RDP/SSH to a VM without exposing a public IP. JIT VM access keeps management ports closed by default and opens them only for a time-boxed, approved window. NSGs are the general-purpose network segmentation layer underneath both. A scenario asking for "reduce the window an admin port is exposed" wants JIT, not just an NSG rule.
Sentinel automation rules vs. playbooks
An automation rule is the orchestration layer — it decides which incidents trigger action, in what order, and can tag/assign/close an incident directly. A playbook is the actual Logic App workflow an automation rule can invoke to take a concrete remediation action. A scenario asking for "run this Logic App automatically when a high-severity incident is created" needs both: the playbook to do the work, and an automation rule to trigger it.
Defender CSPM vs. Defender Vulnerability Management vs. Defender EASM
Defender CSPM evaluates configuration posture and compliance across resources you already know about. Defender Vulnerability Management specifically scans Azure VMs for software vulnerabilities. Defender EASM discovers assets you did not know you had — unmanaged, shadow-IT, or externally exposed resources outside your existing inventory. A scenario about "assets we don't know exist" is EASM, not CSPM.
4-Week SC-500 Study Plan
Weighted toward Week 2 because storage/database/networking alone is 25–30% of the exam, and Week 3 dedicates real time to the AI-security sub-domain that has no AZ-500 equivalent.
- • Configure PIM role activation, conditional access policies, and passwordless/MFA authentication methods end to end
- • Register an application, configure enterprise application permissions, and manage OAuth consent settings
- • Deploy Key Vault, configure access + firewall settings, and enable Defender for Key Vault
- • Assign built-in and custom RBAC roles, then practice identifying and remediating an overprivileged assignment
- • Write and assign an Azure Policy definition and confirm compliance evaluation surfaces it in Defender for Cloud
- • Configure storage account security, Storage firewall rules, and Defender for Storage threat protection
- • Enable Azure SQL platform-level security configurations, database auditing, and Defender for Databases
- • Build NSGs/ASGs, then compare them against a private endpoint, a Private Link service, and Entra Private Access on the same network diagram
- • Configure Azure Firewall and Virtual WAN security, then run Network Watcher effective security rules against your own NSG to see what actually applies
- • Study the AI-security sub-domain first and in isolation: Purview DSPM for Copilot risk, Copilot Studio real-time protection, Entra Agent ID conditional access + blast-radius analysis, Foundry AI Gateway in API Management, Foundry guardrails, and the Data and AI security dashboard
- • Configure JIT VM access and Azure Bastion, then onboard a VM to Defender for Servers and enable agentless scanning
- • Harden AKS, ACR, Container Apps, Functions, and App Service; deploy a Web Application Firewall and API Management back-end protection policy
- • Connect a workspace to Microsoft Sentinel, configure a data connector, and build one automation rule that invokes a playbook
- • Configure Defender CSPM, a workload protection plan, and connect a hybrid/multicloud (AWS or GCP) environment to Defender for Cloud
- • Set up a Security Copilot workspace, assign roles, and enable a plugin
- • Two full-length mock exams (100 minutes each); review every miss and re-test the weakest domain the next day — prioritize AI-security misses since that domain has no prior AZ-500 foundation to fall back on
Frequently Asked Questions
What is the SC-500 exam?+
SC-500 — officially Implementing End-to-End Security Controls for Cloud and AI Workloads — is Microsoft's Associate-level exam for the Cloud and AI Security Engineer Associate certification. Per Microsoft's official audience profile, it validates securing identity, network, application, data, and compute across cloud and hybrid environments, plus ensuring the platforms, data, identities, and infrastructure behind AI workloads are securely implemented and monitored.
Is SC-500 the replacement for AZ-500?+
Yes. Microsoft Certified: Azure Security Engineer Associate (AZ-500) retires August 31, 2026. SC-500 (Cloud and AI Security Engineer Associate) replaces it, carrying forward the identity, networking, storage/database, and Defender for Cloud/Sentinel scope almost unchanged, while adding a genuinely new domain: securing AI workloads (Copilot, Microsoft Foundry agents, Microsoft Entra Agent ID). Existing AZ-500 certifications remain valid until they individually expire — you do not need to retake anything unless your certification is expiring.
What is the single largest domain on SC-500?+
Secure storage, databases, and networking at 25–30% — the only domain above 25%. It covers storage account and Azure Storage firewall configuration, Defender for Storage, Azure SQL platform security and auditing, Defender for Databases, NSGs/ASGs, Virtual Network Manager, Virtual WAN and VPN security, Entra Private Access, private endpoints, Private Link, Azure Firewall, and Network Watcher effective security rules — the same breadth AZ-500 tested, carried over largely intact.
What is genuinely new on SC-500 that AZ-500 never tested?+
The entire "Implement security for AI" sub-domain inside Secure compute: identifying SharePoint data overexposure, Microsoft Purview DSPM for Copilot/AI app risk, real-time protection for Copilot Studio agents, conditional access and blast-radius analysis for Microsoft Entra Agent ID, AI Gateway in API Management for Microsoft Foundry, Defender for AI Service, Foundry agent guardrails, the Data and AI security dashboard, and agent management in the Microsoft 365 admin center. Even candidates who know AZ-500 cold need to study this sub-domain from scratch — none of it existed on the previous exam.
How many questions are on SC-500 and what is the passing score?+
SC-500 runs about 100 minutes with roughly 40–60 questions, scored on Microsoft's 0–1000 scale where 700 is a pass. As with most Microsoft role-based exams, the questions are scenario-based rather than pure recall — you're given a security requirement and asked to choose the correct control, not define a term.
Do I need AZ-500 before taking SC-500?+
No prerequisite is enforced at registration. Candidates without prior Azure security experience should expect a longer runway (8–12 weeks) since SC-500 assumes practical experience administering Azure and hybrid environments plus strong familiarity with Microsoft Entra ID. Candidates who already hold AZ-500 or have equivalent hands-on experience can move much faster — most of the exam maps directly onto what AZ-500 already tested.
How long should I study for SC-500?+
Candidates already comfortable with AZ-500-level material (identity, networking, Defender for Cloud, Sentinel) should plan 3–5 weeks, focused mostly on the new AI-security sub-domain. Candidates without that background should plan 8–12 weeks, starting with the official Microsoft Learn path before layering on scenario practice across all four domains.
Should I still take AZ-500 if it retires soon, or go straight to SC-500?+
If you're starting from zero now, go straight to SC-500 — AZ-500 stops being scheduleable as it approaches its August 31, 2026 retirement, and SC-500 covers the same core skills plus the AI-security domain employers are increasingly asking for. If you're already deep into AZ-500 prep and can sit the exam well before the retirement date, finishing AZ-500 and upgrading to SC-500 later is also reasonable — just don't start a fresh AZ-500 study plan this late in its lifecycle.
What are the prerequisites for SC-500?+
None are formally enforced, but Microsoft's official audience profile expects practical experience administering Azure and hybrid environments (compute, network, storage), strong familiarity with Microsoft Entra ID, and familiarity with Microsoft 365 administration. It is not an entry-level exam — Microsoft explicitly positions it at the same Associate security-engineer level as AZ-500.
How is MSCertQuiz different from other SC-500 practice material?+
SC-500 is a brand-new exam, so most "SC-500 practice questions" circulating right now are either recycled AZ-500 content with the exam code swapped, or generic Azure-security trivia that never mentions Entra Agent ID, Purview DSPM, Copilot Studio real-time protection, or Foundry AI Gateway by name. MSCertQuiz has 500 SC-500 questions built directly against all four official domains — including full coverage of the AI-security sub-domain — with reasoning-based explanations for every answer.
Ready to test this against real scenarios?
500 SC-500 practice questions across all four domains, including full AI-security coverage — 40 free, no card required.