examOS.
Exam CatalogueStudy PlansRoadmapsBlogs
Login

ExamOS

Credits PolicyReferral PolicyQuality StandardsPricingPrivacy PolicyTerms of UseContact UsReport a Bug

Follow us

Disclaimer: ExamOS is an independent platform, not affiliated with any certification provider, and does not use or distribute exam dumps.

Share your feedback

Checking sign-in status...

examOS.Study Plan
Disclaimer: ExamOS is an independent platform, not affiliated with any certification provider, and does not use or distribute exam dumps.
← Back to Exam Details
examOS.Study Plan · examos.io

Study Plan

Cloud and AI Security Engineer (SC-500) Study Plan for 2026

Study plan for SC-500 covering identity and governance, storage and networking, secure compute, AI security, and security posture management.

MicrosoftSC-500Passing score: 700 / 1000Security engineers with practical Azure and hybrid administration experience, strong familiarity with Microsoft Entra ID, and familiarity with Microsoft 365 administration14-Sep-202611 views
Start date: _______________Target exam date: _______________

Your personalized plan

A focused route built around your experience and daily study commitment.

Timeline

12 weeks

Personalized calendar

Daily commitment

1h

5 study & practice hrs/week

Progress

0/6

milestones completed

Saved on this device

Your week-by-week breakdown


Your week 1

Milestone 1: Identity, Access, and Governance (Domain 1)

This domain covers who can reach a resource and how you prove that access stays compliant over time. Expect scenarios about temporary elevation, app-to-app trust, and secrets that must never appear in plaintext. The correct answer minimizes standing privilege.

Topics

  • • Microsoft Entra ID: PIM, Conditional Access, MFA, passwordless
  • • Managed identities vs service principals
  • • Azure Key Vault: firewalls, access policies, RBAC, Defender for Key Vault
  • • Azure Policy: built-in and custom definitions
  • • Regulatory compliance in Defender for Cloud
  • • Resource locks and RBAC right-sizing

Activities

  • • Complete the Microsoft Learn modules on Implement and configure Privileged Identity Management (PIM) and Implement and configure authentication methods.
  • • Create a managed identity for an Azure resource. Grant it access to a Key Vault secret. Verify the resource can retrieve the secret without any credential in code.
  • • Configure a Conditional Access policy that requires MFA for a specific application. Test with a user account to confirm enforcement.
  • • Create a custom Azure Policy definition. Assign it at the resource group scope and verify compliance.
  • • Complete a Daily Sprint in Challenger mode on Domain 1. Repeat until you pass two consecutive sessions.

Your week 2

Milestone 2: Secure Storage, Databases, and Networking (Domain 2)

The heaviest domain. The recurring test is picking the right layer: does the scenario need a firewall rule, a private connection, or a detection plan? Prevention controls (storage firewall, NSG, private endpoint) are separate from detection controls (Defender for Storage, Defender for Databases). Know which is which.

Topics

  • • Storage security: firewalls, private endpoints, encryption, Defender for Storage
  • • Azure SQL security: platform-level security, auditing, Defender for Databases
  • • Network security: NSGs, Azure Firewall, WAF, DDoS Protection
  • • Private Link and Private Endpoint design
  • • Application Gateway and Front Door security
  • • Azure Backup security features

Activities

  • • Configure a storage account firewall to allow access only from a specific VNet. Verify access is blocked from outside the VNet.
  • • Create a private endpoint for an Azure SQL Database. Verify the database is no longer reachable from the public internet.
  • • Enable Defender for Storage on a storage account. Upload a test file with a known malware signature and verify the alert fires.
  • • Configure Azure SQL auditing to send logs to a Log Analytics workspace. Run a query and confirm the audit record appears.
  • • Deploy Azure Firewall in a hub VNet with a UDR routing spoke traffic through it. Verify traffic inspection is working.
  • • Complete a Daily Sprint in Challenger mode on Domain 2. Repeat until you pass two consecutive sessions.

Your week 3

Milestone 3: Secure Compute (Domain 3, Part 1)

This domain covers infrastructure-level defenses for VMs, containers, and hybrid servers. It also introduces the AI security content that is unique to SC-500. The AI security portion covers securing AI workloads, which is a meaningful shift from AZ-500.

Topics

  • • Disk encryption: Azure Disk Encryption vs SSE with PMK
  • • Azure Bastion for secure VM access
  • • Just-in-Time (JIT) VM access
  • • Azure Arc for hybrid and multicloud servers
  • • Defender for Servers
  • • Container security: AKS, ACR, image scanning

Activities

  • • Deploy an Azure Bastion host. Connect to a VM through Bastion using RDP. Verify the VM has no public IP.
  • • Configure JIT VM access with a time-bound policy. Test that a VM port is closed by default and only opens after an approved request.
  • • Enable Defender for Servers on a subscription. Review the recommendations and remediate one.
  • • Connect an on-premises server to Azure Arc. Verify it appears in Defender for Cloud.
  • • Complete a Daily Sprint in Challenger mode on Domain 3 (compute portion). Repeat until you pass two consecutive sessions.

Your week 4

Milestone 4: AI Security (Domain 3, Part 2)

This is the new content that makes SC-500 distinct from AZ-500. It covers securing AI workloads, agent identities, and the controls Microsoft provides for AI-specific threats. The exam tests whether you understand where AI security fits alongside traditional controls.

Topics

  • • Microsoft Entra Agent ID: identities for AI agents
  • • AI Gateway security in Microsoft Foundry
  • • Guardrails in Microsoft Foundry
  • • Defender for AI Services workload protection
  • • Microsoft Defender XDR for AI identity risks
  • • Microsoft Purview Data Security for AI data risks
  • • Securing Copilot Studio agents
  • • Microsoft Agent 365

Activities

  • • Complete the Microsoft Learn modules on Securing AI solutions and Microsoft Entra Agent Identity.
  • • Configure a guardrail in Microsoft Foundry that blocks a specific denied topic. Test with a prompt that should be blocked.
  • • Enable Defender for AI Services on an AI workload. Review the recommendations and alerts it generates.
  • • Create an Entra Agent ID for a test agent. Review its permissions and apply least-privilege scoping.
  • • Configure AI Gateway security in Foundry. Verify that API calls to the model are routed through the gateway.
  • • Complete a Daily Sprint in Challenger mode on AI security. Repeat until you pass two consecutive sessions.

Your week 5

Milestone 5: Manage and Monitor Security Posture (Domain 4)

This domain covers operational threat detection and response: Defender for Cloud, Microsoft Sentinel, and Security Copilot. It also includes data security posture management through Microsoft Purview. The exam tests whether you can design monitoring and response workflows, not just configure them.

Topics

  • • Microsoft Defender for Cloud: Secure Score, recommendations, regulatory compliance
  • • Microsoft Sentinel: data connectors, analytics rules, workbooks, SOAR playbooks
  • • Microsoft Security Copilot: permissions, agents, plugins
  • • Microsoft Purview Data Security Posture Management
  • • Incident response workflows with Defender XDR
  • • Regulatory compliance dashboards

Activities

  • • Review your Secure Score in Defender for Cloud. Identify the top 3 recommendations by impact. Remediate one and verify the score increases.
  • • Connect a data source to Microsoft Sentinel (e.g., Azure Activity Log). Write a simple analytics rule and verify it generates an incident.
  • • Create a SOAR playbook in Sentinel that automates a response to a specific alert. Test it with a sample incident.
  • • Configure a regulatory compliance assessment in Defender for Cloud for a standard (e.g., ISO 27001 or PCI-DSS). Review the findings.
  • • Complete a Daily Sprint in Challenger mode on Domain 4. Repeat until you pass two consecutive sessions.

Your week 6

Milestone 6: Exam Simulation and Booking

Your final push. Consolidate all four domains. The AI security content appears in Domain 3 and Domain 4, so review those together.

Topics

  • • Full syllabus review across all four domains
  • • Cross-domain scenarios: identity + storage + AI, compute + posture
  • • Time management (120 minutes for 40-60 questions)
  • • Case study technique: identify the binding constraint

Activities

  • • Take the free official practice assessment on Microsoft Learn. Compare your score to Week 1.
  • • Take at least 3 Mock Exams in Legend mode. For every missed question, write one sentence explaining the security principle behind the correct answer.
  • • Review the AI security content one final time: Entra Agent ID, AI Gateway, guardrails, Defender for AI Services. These are the highest-risk areas for candidates coming from AZ-500.
  • • Simulate real exam conditions once: no phone, no breaks, 120 minutes, same time of day as your scheduled exam.
  • • Book your exam when your readiness score is stable and above 80, with every domain covered.

Your weeks 7–12

Use this practice and review phase for mock exams, weak-topic revision, and reworking missed questions before exam day.

Stay consistent by setting a target date for this certification.

Set target

Week-by-Week Breakdown


W1

Week 1

Identity, Access, and Governance (Domain 1)

This domain covers who can reach a resource and how you prove that access stays compliant over time. Expect scenarios about temporary elevation, app-to-app trust, and secrets that must never appear in plaintext. The correct answer minimizes standing privilege.

Topics

  • Microsoft Entra ID: PIM, Conditional Access, MFA, passwordless
  • Managed identities vs service principals
  • Azure Key Vault: firewalls, access policies, RBAC, Defender for Key Vault
  • Azure Policy: built-in and custom definitions
  • Regulatory compliance in Defender for Cloud
  • Resource locks and RBAC right-sizing

Daily Study Routine

Suggested 2–3 Hour Day

TimeActivity
10 minReview yesterday's missed questions. Identify whether the miss was a control-type confusion (prevention vs detection) or a knowledge gap.
30 minWork through the Microsoft Learn module for this week's topic.
30 minHands-on lab in Azure portal, Defender portal, or Microsoft Foundry.
20 minComplete a Daily Sprint or Mock Exam.

Activities

  • Complete the Microsoft Learn modules on Implement and configure Privileged Identity Management (PIM) and Implement and configure authentication methods.
  • Create a managed identity for an Azure resource. Grant it access to a Key Vault secret. Verify the resource can retrieve the secret without any credential in code.
  • Configure a Conditional Access policy that requires MFA for a specific application. Test with a user account to confirm enforcement.
  • Create a custom Azure Policy definition. Assign it at the resource group scope and verify compliance.
  • Complete a Daily Sprint in Challenger mode on Domain 1. Repeat until you pass two consecutive sessions.
W2

Week 2

Secure Storage, Databases, and Networking (Domain 2)

The heaviest domain. The recurring test is picking the right layer: does the scenario need a firewall rule, a private connection, or a detection plan? Prevention controls (storage firewall, NSG, private endpoint) are separate from detection controls (Defender for Storage, Defender for Databases). Know which is which.

Topics

  • Storage security: firewalls, private endpoints, encryption, Defender for Storage
  • Azure SQL security: platform-level security, auditing, Defender for Databases
  • Network security: NSGs, Azure Firewall, WAF, DDoS Protection
  • Private Link and Private Endpoint design
  • Application Gateway and Front Door security
  • Azure Backup security features

Activities

  • Configure a storage account firewall to allow access only from a specific VNet. Verify access is blocked from outside the VNet.
  • Create a private endpoint for an Azure SQL Database. Verify the database is no longer reachable from the public internet.
  • Enable Defender for Storage on a storage account. Upload a test file with a known malware signature and verify the alert fires.
  • Configure Azure SQL auditing to send logs to a Log Analytics workspace. Run a query and confirm the audit record appears.
  • Deploy Azure Firewall in a hub VNet with a UDR routing spoke traffic through it. Verify traffic inspection is working.
  • Complete a Daily Sprint in Challenger mode on Domain 2. Repeat until you pass two consecutive sessions.
W3

Week 3

Secure Compute (Domain 3, Part 1)

This domain covers infrastructure-level defenses for VMs, containers, and hybrid servers. It also introduces the AI security content that is unique to SC-500. The AI security portion covers securing AI workloads, which is a meaningful shift from AZ-500.

Topics

  • Disk encryption: Azure Disk Encryption vs SSE with PMK
  • Azure Bastion for secure VM access
  • Just-in-Time (JIT) VM access
  • Azure Arc for hybrid and multicloud servers
  • Defender for Servers
  • Container security: AKS, ACR, image scanning

Activities

  • Deploy an Azure Bastion host. Connect to a VM through Bastion using RDP. Verify the VM has no public IP.
  • Configure JIT VM access with a time-bound policy. Test that a VM port is closed by default and only opens after an approved request.
  • Enable Defender for Servers on a subscription. Review the recommendations and remediate one.
  • Connect an on-premises server to Azure Arc. Verify it appears in Defender for Cloud.
  • Complete a Daily Sprint in Challenger mode on Domain 3 (compute portion). Repeat until you pass two consecutive sessions.
W4

Week 4

AI Security (Domain 3, Part 2)

This is the new content that makes SC-500 distinct from AZ-500. It covers securing AI workloads, agent identities, and the controls Microsoft provides for AI-specific threats. The exam tests whether you understand where AI security fits alongside traditional controls.

Topics

  • Microsoft Entra Agent ID: identities for AI agents
  • AI Gateway security in Microsoft Foundry
  • Guardrails in Microsoft Foundry
  • Defender for AI Services workload protection
  • Microsoft Defender XDR for AI identity risks
  • Microsoft Purview Data Security for AI data risks
  • Securing Copilot Studio agents
  • Microsoft Agent 365

Activities

  • Complete the Microsoft Learn modules on Securing AI solutions and Microsoft Entra Agent Identity.
  • Configure a guardrail in Microsoft Foundry that blocks a specific denied topic. Test with a prompt that should be blocked.
  • Enable Defender for AI Services on an AI workload. Review the recommendations and alerts it generates.
  • Create an Entra Agent ID for a test agent. Review its permissions and apply least-privilege scoping.
  • Configure AI Gateway security in Foundry. Verify that API calls to the model are routed through the gateway.
  • Complete a Daily Sprint in Challenger mode on AI security. Repeat until you pass two consecutive sessions.
W5

Week 5

Manage and Monitor Security Posture (Domain 4)

This domain covers operational threat detection and response: Defender for Cloud, Microsoft Sentinel, and Security Copilot. It also includes data security posture management through Microsoft Purview. The exam tests whether you can design monitoring and response workflows, not just configure them.

Topics

  • Microsoft Defender for Cloud: Secure Score, recommendations, regulatory compliance
  • Microsoft Sentinel: data connectors, analytics rules, workbooks, SOAR playbooks
  • Microsoft Security Copilot: permissions, agents, plugins
  • Microsoft Purview Data Security Posture Management
  • Incident response workflows with Defender XDR
  • Regulatory compliance dashboards

Activities

  • Review your Secure Score in Defender for Cloud. Identify the top 3 recommendations by impact. Remediate one and verify the score increases.
  • Connect a data source to Microsoft Sentinel (e.g., Azure Activity Log). Write a simple analytics rule and verify it generates an incident.
  • Create a SOAR playbook in Sentinel that automates a response to a specific alert. Test it with a sample incident.
  • Configure a regulatory compliance assessment in Defender for Cloud for a standard (e.g., ISO 27001 or PCI-DSS). Review the findings.
  • Complete a Daily Sprint in Challenger mode on Domain 4. Repeat until you pass two consecutive sessions.
W6

Week 6

Exam Simulation and Booking

Your final push. Consolidate all four domains. The AI security content appears in Domain 3 and Domain 4, so review those together.

Topics

  • Full syllabus review across all four domains
  • Cross-domain scenarios: identity + storage + AI, compute + posture
  • Time management (120 minutes for 40-60 questions)
  • Case study technique: identify the binding constraint

Activities

  • Take the free official practice assessment on Microsoft Learn. Compare your score to Week 1.
  • Take at least 3 Mock Exams in Legend mode. For every missed question, write one sentence explaining the security principle behind the correct answer.
  • Review the AI security content one final time: Entra Agent ID, AI Gateway, guardrails, Defender for AI Services. These are the highest-risk areas for candidates coming from AZ-500.
  • Simulate real exam conditions once: no phone, no breaks, 120 minutes, same time of day as your scheduled exam.
  • Book your exam when your readiness score is stable and above 80, with every domain covered.

Overview

SC-500 replaced AZ-500 on August 31, 2026. Roughly 80% of the content carries over from AZ-500: identity, networking, storage, databases, compute, Defender for Cloud, and Sentinel. The remaining 20% is new, covering AI workload security, Microsoft Entra Agent ID, Defender for AI, and Security Copilot.

This is not AZ-500 with an AI chapter bolted on. The AI security content is woven into the compute and posture domains, and it appears in scenario questions alongside traditional infrastructure topics. Candidates who skip the AI sections will lose marks across multiple domains, not just one.

Domain Weight
Manage identity, access, and governance 20-25%
Secure storage, databases, and networking 25-30%
Secure compute 20-25%
Manage and monitor security posture 20-25%

Domain 2 is the heaviest at 25-30%. It merges what AZ-500 tested across two separate domains (networking, and storage/databases) into one. The AI security content lives primarily inside Domain 3 (Secure compute), covering Foundry guardrails, AI Gateway, Entra Agent ID, and Defender for AI Services.

Recommended experience: Practical experience administering Azure and hybrid environments, including compute, network, and storage. Strong familiarity with Microsoft Entra ID. Familiarity with Microsoft 365 administration.

A note on AZ-500 migration: If you hold AZ-500 or were studying for it, your existing knowledge covers Domains 1, 2, and most of 3. Focus your new study time on the AI security content: Entra Agent ID, AI Gateway in Microsoft Foundry, guardrails, Defender for AI Services, and Security Copilot.

Frequently Asked Questions (FAQ)

Do I need AZ-500 before SC-500?

No. AZ-500 retired on August 31, 2026. SC-500 is the replacement. If you already passed AZ-500, your certification remains on your transcript but can no longer be renewed. SC-500 is the current credential for the Azure Security Engineer Associate role.

How long does it take to prepare for SC-500?

Six weeks for candidates with Azure administration experience. If you already hold AZ-500 or studied for it, you can prepare in four weeks by compressing the non-AI domains and focusing on AI security and posture management.

What is the difference between SC-500 and AZ-500?

AZ-500 tested identity, networking, compute/storage, and security operations. SC-500 restructures this into four domains and adds AI workload security. Key Vault moves from its own domain into identity. Networking merges with storage/databases. AI security content covers Entra Agent ID, AI Gateway, guardrails, Defender for AI Services, and Security Copilot. Roughly 80% of AZ-500 carries over.

What are the most important AI security topics?

Microsoft Entra Agent ID (identities for AI agents), AI Gateway in Microsoft Foundry (securing model API calls), guardrails in Foundry (content filtering and safety), and Defender for AI Services (threat detection for AI workloads). These appear in Domain 3 and Domain 4.

Do I need hands-on experience with Microsoft Foundry?

Yes, at a foundational level. The exam tests whether you can configure guardrails, enable Defender for AI Services, and understand how AI Gateway routes traffic. If you have not worked with Foundry, spend extra time in Weeks 4.

Can I use Microsoft Learn during the exam?

Yes. All role-based exams, including SC-500, give you access to Microsoft Learn during the exam. A "Learn" button opens Microsoft Learn in a split-screen view. You can only access Microsoft Learn. Use it to confirm specific details like service limits or feature availability. Candidates who know the material well use it to verify edge cases. Candidates who rely on it consistently run out of time.

What is the most important domain to study?

Secure storage, databases, and networking (25-30%) is the heaviest domain. Manage identity, access, and governance (20-25%) is the foundation for every other domain. Secure compute (20-25%) includes the AI security content, which is the biggest new area. Manage and monitor security posture (20-25%) covers Defender for Cloud, Sentinel, and Security Copilot.

What are the most common ways people fail?

  • Confusing prevention with detection. Storage firewall prevents access. Defender for Storage detects threats. NSG prevents traffic. Defender for Databases detects anomalies. The exam tests whether you know which is which.
  • Skipping AI security. Candidates coming from AZ-500 sometimes assume it is an optional add-on. It is not. It appears in Domain 3 and Domain 4.
  • Not understanding PIM vs Conditional Access. PIM reduces how long a role is usable. Conditional Access decides whether a sign-in is allowed. A scenario about reducing standing privilege is PIM.
  • Ignoring Key Vault firewalls. Key Vault has network-level controls independent of RBAC. A scenario about restricting vault access to specific VNets is a firewall question, not an RBAC question.
  • Underestimating Sentinel. Domain 4 covers Sentinel data connectors, analytics rules, and SOAR playbooks. Candidates who only know Defender for Cloud miss a significant portion.

What are the three biggest preparation mistakes?

  1. Treating SC-500 as AZ-500 with a new name. The domain structure changed. Key Vault moved. Networking merged with storage and databases. AI security is woven into compute and posture. Study the SC-500 study guide, not AZ-500 materials.
  2. Skipping the AI security labs. Reading about guardrails is not the same as configuring one. Reading about AI Gateway is not the same as routing traffic through it. The exam tests configuration judgment.
  3. Not practicing cross-domain scenarios. SC-500 questions frequently combine domains: an identity scenario that requires a Key Vault firewall, a compute scenario that requires an AI Gateway, a posture scenario that requires a Sentinel playbook. Practice connecting the domains.

Is there a renewal option?

Yes. SC-500 is valid for 1 year. You can renew it for free by passing an online assessment on Microsoft Learn. The renewal assessment is shorter and focuses on what has changed since you certified.