Dev.to Security 🔐 Cybersecurity 👁 0 📖 8 min read

SC-500: The Exam That Replaced AZ-500 — Cloud Security, Now With AI Workloads on the Syllabus

SC-500: The Exam That Replaced AZ-500 — Cloud Security, Now With AI Workloads on the Syllabus AZ-500 retired on August 31, 2026. Its replacement is not a refresh with a new code: SC-500, Implementing End-to-End Securit

SC-500: The Exam That Replaced AZ-500 — Cloud Security, Now With AI Workloads on the Syllabus

AZ-500 retired on August 31, 2026. Its replacement is not a refresh with a new code: SC-500, Implementing End-to-End Security Controls for Cloud and AI Workloads, earns a differently named certification — Microsoft Certified: Cloud and AI Security Engineer Associate — and it tests a job that is visibly wider than the one AZ-500 tested. The old exam asked whether you could secure Azure. SC-500 asks whether you can secure Azure, the data and networks around it, and the AI workloads running on top of it.

That last clause is the whole story. Microsoft's study guide puts AI security in two places at once: securing AI solutions sits inside the compute domain, and securing AI workloads sits inside the posture domain. A candidate who studies SC-500 as "AZ-500 with a new name" will walk into questions about Copilot data exposure, AI gateways, and agent identities that no AZ-500 material ever covered.

What SC-500 actually is

SC-500 certifies a security engineer who protects organizational systems and data across cloud and hybrid environments — identity, network, application, data, and compute — and who also makes sure the platforms, data, identities, and infrastructure used by AI workloads are securely implemented and monitored. That is Microsoft's audience profile, and it is deliberately broad: the exam expects you to work across Entra ID, Azure networking, storage and databases, compute, Defender, Sentinel, and Purview, and to talk to the architects, administrators, and developers who own each piece.

The exam mechanics, from Microsoft's official study guide and exam page: 120 minutes, pass mark 700 on a 1,000-point scaled score, $165 in the United States with pricing set by country or region, booked and sat through Pearson VUE at a test center or online with OnVUE proctoring. Microsoft does not publish an exact question count — most of its role-based exams run 40 to 60 — and there are no formal prerequisites, though the exam plainly assumes hands-on Azure experience. The certification is valid for one year and renews free with an online assessment on Microsoft Learn. The beta opened in May 2026 and the exam went generally available in July 2026; AZ-500 and the Azure Security Engineer Associate certification retired August 31, 2026, with no conversion path — existing AZ-500 certifications stay Active until their one-year expiry, then become Historical.

The four domains, and why none of them can be skipped

Microsoft's study guide lists four domains with a strikingly flat spread:

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%

No domain falls below 20 percent and the largest tops out at 30. That flatness is the exam's defining structural fact: there is no light domain to skim and no single heavy domain to carry your score. Every domain is roughly a quarter of the exam, so a weak domain costs you roughly a quarter of the exam.

Domain 1: Manage identity, access, and governance (20–25%)

Identity is the control plane for everything else on this exam, and the domain tests it as an engineering discipline, not a vocabulary list. Entra ID work covers privileged identity management, conditional access, multifactor and passwordless authentication, app registrations and OAuth consent, and managed identities. Then Key Vault end to end — keys, secrets, and certificates, and the access policies that decide who can touch them. Then governance: Azure Policy, regulatory compliance in Defender for Cloud, resource locks, role-based access control including custom roles, and the unglamorous work of finding overprivileged access and removing it.

The exam's favorite trap in this domain is the difference between a control that exists and a control that is enforced. A conditional access policy in report-only mode, a PIM role that is eligible but never activated, a Key Vault access policy that grants more than the workload needs — SC-500 writes scenarios around controls that look right in the portal and fail in practice. Study the enforcement state, not the configuration screen.

A second trap is scope. Conditional access, access reviews, and entitlement management all fail the same way: applied to the wrong population. The scenario names a group of users, a set of apps, or a class of resources; the correct answer is the policy that covers exactly that scope, not the broader one that looks safer.

Domain 2: Secure storage, databases, and networking (25–30%)

The heaviest domain, and the most sprawling. Storage account security and firewall rules, Defender for Storage, Azure SQL platform security and auditing, Defender for Databases — then networking: network security groups and application security groups, Azure Virtual Network Manager, Virtual WAN, VPN, Entra Private Access, private endpoints and Private Link, Azure Firewall, and Network Watcher.

Two ideas organize the whole domain. The first is defense in depth across the data path: encryption at rest and in transit, access controls on the storage account, firewall rules that admit only the right networks, and private connectivity that keeps traffic off the public internet. The exam tests the layers together — a question that is really about which layer failed, with each wrong answer fixing a different, innocent layer.

The second is that networking questions on SC-500 are connectivity questions first and firewall questions second. A scenario about a hybrid workload that cannot reach a database, a private endpoint that resolves to the wrong address, a Virtual WAN hub that routes around the firewall — the answer is usually about how traffic flows, not about which rule to add. If your study has been entirely rule-based, spend time tracing packets through NSGs, route tables, Private Link, and Firewall before exam day.

Domain 3: Secure compute (20–25%) — this is where the AI lives

Compute covers serverless and platform services, managed identities and service principals, virtual machines and containers: hardening operating systems and workloads, securing container environments and orchestration, and managing updates and vulnerability remediation. That is the traditional half of the domain. The new half is security for AI, and it is where SC-500 most differs from AZ-500.

The AI content, per Microsoft's study guide and the exam's syllabus: data overexposure in SharePoint as it feeds Copilot, Copilot and AI app risk through Purview Data Security Posture Management, real-time protection for Copilot Studio agents, conditional access for Entra Agent ID, blast-radius analysis in Defender XDR, the AI Gateway in API Management for Microsoft Foundry, Defender for AI Service, and guardrails in Foundry. The exam treats AI workloads as ordinary workloads with extraordinary data access: an agent that can read SharePoint inherits SharePoint's exposure, and a model gateway that has no guardrails is a data path with no firewall.

The study implication is practical: if you have never opened Purview's DSPM for AI or configured an AI Gateway, do it in a trial tenant before the exam. The questions are written for people who have seen these blades, and the distractors are written for people who have only read the definitions.

Domain 4: Manage and monitor security posture (20–25%)

The operational domain, and the second home of the AI work. It covers securing AI workloads and solutions — enforcing responsible AI and data protection, monitoring and mitigating AI-specific risks, implementing security controls for generative AI and AI platforms — alongside the posture work: assessing compliance and security posture, using Defender and Sentinel for threat detection, and responding to and remediating security incidents.

This is the domain where the exam tests judgment under pressure. The scenario gives you an alert or a posture finding, and the question is what you do first: which signal confirms the scope, which Defender or Sentinel view answers the question, when a finding is a misconfiguration to remediate and when it is an incident to escalate. The wrong answers are always real actions in the wrong order. The only reliable defense is having done the workflow once in a trial tenant: trigger an alert, open it in Defender XDR, pivot to Sentinel, check the posture score, and close it out.

AZ-500 vs SC-500: what actually changed

The certification changed its name for a reason. AZ-500 certified an Azure Security Engineer; SC-500 certifies a Cloud and AI Security Engineer. The identity, storage, networking, and compute fundamentals carry over — Entra ID, Key Vault, NSGs, Azure Firewall, Defender for Cloud, and the rest are still the core of the job — but the exam adds AI workload security as a first-class topic in two domains, widens the networking scope toward hybrid and multi-cloud connectivity, and frames the whole job around end-to-end controls rather than Azure-only controls.

If you hold AZ-500-era study notes, audit them against the four SC-500 domains before you trust them. Anything about Entra ID, Key Vault, storage, networking, and compute fundamentals still applies. Anything that never mentions AI workloads, DSPM for AI, agent identities, or AI gateways is incomplete for this exam — and anything that describes AZ-500 as bookable is out of date. Book SC-500, not the retired exam.

How to study for four equal domains

Six to eight weeks suits most people who already administer Azure. The even weighting makes the plan simple: give each domain roughly equal time, and keep the last week for timed practice. A plan that front-loads identity and squeezes posture into the final days is planning to lose a quarter of the exam.

Weeks 1–2, identity and governance: PIM, conditional access, Key Vault, Azure Policy, access reviews. Build each control in a trial tenant and then try to break it — a policy in report-only mode, an overprivileged role, a vault with a loose access policy. Weeks 3–4, storage, databases, and networking: storage firewalls, SQL auditing, NSGs, Private Link, Azure Firewall, and one full connectivity trace from a hybrid workload to a database. Weeks 5–6, compute and AI: container hardening, managed identities, then the AI controls — DSPM for AI in Purview, an AI Gateway, an agent identity with conditional access. Weeks 7–8, timed runs: full 120-minute blocks under exam conditions, reading the explanation for every miss — not just the wrong answers, but the right ones you guessed.

Two habits separate passing candidates from failing ones on this exam. First, verify everything in the portals, not in a book: SC-500 tests the consoles as they are now, and the blades move. Second, practice the scenario format: read the question, name the domain, name the tool, and only then look at the options. The exam's distractors are built for candidates who match keywords to answers; the domain-first habit defeats them.

Bottom line

SC-500 is AZ-500's job grown wider: the same cloud security engineering, plus the AI workloads that now sit on top of it, tested across four domains that are each worth about a quarter of the exam. The flat weighting is the warning — there is nowhere to hide, and the AI content in the compute and posture domains is the part older material cannot teach you. Study the outline as it stands today, build the AI controls in a trial tenant, and practice the operational workflows as procedures, not definitions.

Start by finding out where you stand: the free SC-500 practice test at https://study4pass.com/study-material/microsoft/sc-500 runs real exam-style questions with full explanations and no signup, so you can measure each of the four domains before you commit your study weeks.

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.