TL;DR
SC-500 is the Cloud and AI Security Engineer Associate exam, generally available since July 2026 as the successor to the retired AZ-500. It runs 120 minutes with a 700 passing score and assesses four skill areas led by data and network security. Study the official study guide directly, since third-party coverage is still thin and some details remain unverified.
By SecLern Editorial. Published 2026-10-18. Exam facts checked 2026-10-17 against the Microsoft Learn certification page and the official SC-500 study guide. Anything Microsoft does not publish is marked unverified below, never stated as fact.
What SC-500 is, and where it sits
The official exam title is Exam SC-500: Implementing End-to-End Security Controls for Cloud and AI Workloads, and it anchors the Cloud and AI Security Engineer Associate certification. Think of it as the security-engineer seat for Azure-centered estates with AI workloads in scope: identity and governance, data and network protection, compute security, and posture management across the estate. It succeeds AZ-500, which retired 2026-08-31 with Pearson VUE pointing candidates at SC-500 as the related new exam. If your team still says AZ-500 out of habit, translate it: same career slot, new code, AI workloads now explicit. The beta ran May through July 2026 and the exam is generally available now, so plan on live-exam difficulty and live-exam retake policy, not beta terms. Start from the SC-500 study hub.
The four assessed areas
Microsoft publishes each area as a percentage range, not a fixed weight. Ranges are honest about form variation, so plan hours on midpoints and hold margin at the edges.
- Manage identity, access, and governance: 20 to 25%. Entra ID, conditional access, privileged identity management, role design, and governance controls. Identity decides breaches, so this area punches above its range in scenario count.
- Secure storage, databases, and networking: 25 to 30%. The heaviest area. Encryption at rest and in transit, key management, storage controls, database security, virtual networks, private endpoints, and network security groups. Expect the most configuration-judgment questions here.
- Secure compute: 20 to 25%. Virtual machines, containers, and AI workload compute: hardening, patching, endpoint protection, container controls, and securing the compute behind AI services.
- Manage and monitor security posture: 20 to 25%. Defender for Cloud, secure score, compliance tracking, logging and monitoring, incident visibility. The area that turns the other three into an operated system.
Midpoint planning gives roughly 22.5/27.5/22.5/22.5, which sums near 95 only because midpoints of ranges do that; normalize to 100 when you allocate hours (about 24/29/24/24). Those midpoints are our study arithmetic, not Microsoft figures. For method, the study plan habit of pairing each service with its failure mode ports well: learn every control with the attack it stops.
Format facts, and the gaps we refuse to fill
Verified on Microsoft Learn: 120 minutes duration and a 700 passing score. Microsoft does not publish a fixed question count on the certification page, so this post states no count; any fixed number you meet elsewhere is unofficial until Microsoft prints it. Same for the score scale, price, renewal terms, and practice assessment availability: unverified at our check, so check the Microsoft page on booking week rather than trusting a blog. The official study guide lists the measured skills per area and is the single best prep document precisely because third-party books are still catching up. Work it end to end: for each listed skill, build the control in a trial tenant or whiteboard the configuration from memory. SC-500 rewards people who have clicked the blade, not people who have read about the blade. Verify coverage with readiness once you have fresh scenario items.
How it differs from AZ-500 thinking
AZ-500 veterans carry over roughly three quarters of the substrate: identity, network controls, compute hardening, and monitoring fundamentals all persist. The delta is scope and emphasis. AI workloads join explicitly, which means data protection around model inputs and outputs, securing AI service endpoints, and governance over who can deploy what. Study-guide currency matters more than usual here: the guide carries a 2026 update stamp, and the exam tracks the guide, so a 2025-era AZ-500 book teaches the past. If you hold AZ-500, do not assume grandfathering covers the new ground; hiring managers will ask what you know about AI workload controls, and this exam is the answer. If you are choosing between the two codes, there is no choice left to make: AZ-500 retired, and new sittings are SC-500.
A prep plan for thin-coverage exams
New exams punish generic prep, so run a tight loop. Weeks 1 to 2: identity and governance, with conditional access policies and role design as daily lab work. Weeks 3 to 4: the heavy area, data and networking, one service control per day with its encryption and access story. Weeks 5 to 6: compute plus posture management, ending each week by explaining your tenant's secure score movement aloud. Throughout: one page of notes per skill in the official guide, phrased as configuration decisions, not definitions. Finish with full-length timed sittings and patch only the misses, per readiness explained. And keep a quarterly re-check habit: new exams move fastest in year one, and a stale fact about this exam costs more than a stale fact about a ten-year-old one. One more gap to respect: until Microsoft publishes firmer detail, treat every third-party SC-500 mock as uncalibrated. Such mocks give useful reps but unreliable score prediction. Judge readiness by lab fluency (can you configure each skill without the docs) rather than by any vendor percentage, and sit when the tenant work feels routine.
Building your practice tenant
SC-500 is a controls exam, so reading about controls without touching them leaves half the points unreachable. Set up a non-production tenant you control and work the study guide as a build list. For identity week: create test users and groups, write two conditional access policies (one blocking legacy auth, one requiring compliant devices for admins), assign a privileged role through just-in-time elevation, then try to break your own policies with the test accounts and read the sign-in logs. For data and networking week: deploy a storage account with private-endpoint-only access, rotate a key, enable infrastructure encryption where offered, and peer two virtual networks with the segmentation you would defend in an interview. For compute week: harden one virtual machine to your own baseline, enable update management, and onboard it to endpoint protection, recording each deviation you find. For posture week: open the secure score dashboard before and after each change so you learn which controls move the score and by how much. End every lab by deleting what you built or documenting why it stays; abandoned test resources become someone else's attack surface, and the exam's governance area would fail you for them. One built control beats ten read chapters, and your notes become configuration decisions instead of definitions.
Sources
- Microsoft Learn, Cloud and AI Security Engineer Associate (exam status, duration, areas)
- Microsoft Learn, SC-500 study guide (measured skills per area)
Read next
Compare roles with CISSP vs management thinking, borrow pacing from the Security+ study plan, and check the AZ-900 baseline if cloud fundamentals feel shaky. Labs live under study.