Some of the identities in your company directory no longer belong to people. AI agents now sign in, hold permissions and touch sensitive data around the clock, and securing them has quietly become part of your job description.
Those agents never take a holiday and never log off. They read the same SharePoint libraries as your users, call the same APIs, and act at machine speed, which means a misconfigured or compromised agent can expose data faster than any phishing victim ever could. Meanwhile, most security certifications still describe a world where every credential had a human being attached to it, and every threat arrived through a person.
And someone has to answer for all of it. When the Copilot rollout needs a security sign-off, when an auditor asks which agent can reach which data, when the board wants to know whether any of this is safe, those questions land on the security engineer's desk. Being the person trusted with them has always rested partly on what's certified behind your name, and that just changed.
Microsoft's answer landed this year in two moves. It retired AZ-500, the Azure Security Engineer certification that defined this job for the past several years, and introduced SC-500, the Cloud and AI Security Engineer Associate, an exam that treats agents, Copilot and multicloud estates as ordinary parts of a security engineer's job rather than exotic extras.
That new name will follow you further than your CV. Security work is unusually credential-gated: client contracts, tenders and compliance frameworks often list the certifications a supplier's engineers must hold, and when Microsoft replaces the named credential, those lists follow it. Sooner or later the documents around your work will say SC-500 where they used to say AZ-500.
That makes this less a rebadge and more a redefinition of the role, wide enough that it deserves a proper look before you commit study time to it. If you hold AZ-500, or you were partway through planning for it, the first question is what its retirement actually means for you, and the honest answer starts with how abruptly the old certification ended.
Why AZ-500 had to go
Microsoft retired AZ-500 on 31 August 2026, and the small print matters more than usual. The notice covers the certification, the exam and the renewal assessments together, so nobody can earn it any more, and existing holders can't renew it either. The badge you have stays on your transcript, but when its expiry date arrives, it lapses for good. If Azure Security Engineer is on your CV, it's worth opening your Microsoft Learn profile today, checking that date, and planning SC-500 on the right side of it.
The reason for the hard stop is visible in your own calendar. The role stopped being an Azure-only job. Security engineers now inherit an AWS account from an acquisition, a Microsoft 365 tenant mid-Copilot-rollout, and a growing population of agents alongside the Azure environment they started with. An exam scoped to one cloud couldn't test the job any more, so Microsoft drew a bigger boundary and named the new certification after it.
What SC-500 expects of you
The Cloud and AI Security Engineer Associate certification is aimed at working security engineers, and Microsoft's assumed background is specific: hands-on Azure and hybrid administration across compute, network and storage, strong Microsoft Entra ID knowledge, and familiarity with Microsoft 365. The exam itself runs 120 minutes at Pearson VUE, in English, with 700 as the pass mark, and its study guide spreads the marks unusually evenly across four domains:
- Manage identity, access and governance, 20 to 25%. Privileged Identity Management, conditional access, managed identities, Key Vault, Azure Policy and custom roles.
- Secure storage, databases and networking, 25 to 30%. The largest slice: storage firewalls, SQL auditing, network security groups, private endpoints, Azure Firewall and VPN security.
- Secure compute, 20 to 25%. Virtual machines, containers, Kubernetes, app services, and the entire AI security block covered below.
- Manage and monitor security posture, 20 to 25%. Defender for Cloud, vulnerability management, external attack surface management, Microsoft Sentinel and Security Copilot.
Put those four side by side and what stands out is breadth. Posture management now includes connecting AWS and GCP into Defender for Cloud, Sentinel has moved from a specialist topic to core syllabus, and Security Copilot administration appears on a certification for the first time. AZ-500 veterans will recognise the skeleton, but the body around it has grown.
What securing AI means here, in practice
Nothing in Microsoft's older security exams prepared anyone for this section, and it's more concrete than the marketing phrase AI security suggests. The exam expects you to treat agents exactly the way the opening of this article described them: as identities. Each one gets a Microsoft Entra Agent ID, and you're tested on putting conditional access policies around those IDs, managing their access lifecycles, and running blast radius analysis in Defender XDR, which is the exercise of mapping how far an attacker could reach if one agent were compromised.
Around that core sit the supporting jobs. You'll need to find and fix data oversharing before Copilot goes live and amplifies it, using Purview's posture tools to spot SharePoint content that far too many people can read. You'll need real-time protection for agents built in Copilot Studio, guardrails for agents built in Foundry, and the AI Gateway in API Management standing between models and the systems that call them. None of it requires you to understand how a language model works inside. All of it requires the discipline you already apply to human identities, extended to software that acts on its own.
Getting ready for SC-500
Let the weightings set your study plan, because no domain dominates and a strong AZ-500 background covers roughly three quarters of the ground already: identity, networking, compute and governance are home territory, while the AI block, Sentinel depth and Security Copilot are where the genuinely new study time goes. There's no practice assessment yet, so create your own in a test tenant: connect a second cloud into Defender for Cloud, stand up a Sentinel workspace, and put a conditional access policy on an agent identity to see what the controls actually look like.
If you'd rather cover all four domains with an instructor and labs instead of assembling that yourself, the four-day Microsoft Cloud and AI Security Engineer (SC-500) Course was built for exactly this exam. Teams juggling this alongside other Microsoft exams this year can also lean on Unlimited Microsoft Training, one subscription that spans the instructor-led Microsoft courses we run. And if you're still deciding where SC-500 sits among Microsoft's security credentials, our guide to choosing between the Microsoft security certifications puts the whole family side by side.
Frequently asked questions
Is SC-500 harder than AZ-500 was?
It's wider rather than deeper. The level is the same, associate, but the four domains are weighted so evenly that there's no single strong area to lean on, and the exam adds ground AZ-500 never touched: Microsoft 365, Sentinel, Security Copilot and AI workloads. Engineers who've lived only in Azure infrastructure will feel the stretch more than the difficulty.
Is there a bridge exam or discount for AZ-500 holders?
No. Microsoft hasn't announced any transition offer, so SC-500 is a full exam at full price whatever you held before. Your Azure security experience is the bridge, since it covers most of the syllabus.
Does SC-500 cover clouds other than Azure?
Yes, within limits. The syllabus includes connecting AWS and Google Cloud environments into Defender for Cloud and managing their security posture from there. You're tested on securing a multicloud environment with Microsoft's tools, not on AWS or Google's own security services.
How long does the certification stay valid?
One year, like Microsoft's other associate certifications, renewed through a free online assessment you take from home before the expiry date. That ordinary renewal cycle is exactly what AZ-500 holders have now lost, which is why moving across matters.
SC-500 is Microsoft's way of asking whether you can keep all of them, human and otherwise, inside the lines, and right now it's the credential that says you can.
Closing lines
None of this needs to be a scramble. If you've been doing this work already, SC-500 mostly asks you to prove it, plus a newer slice you can learn in weeks rather than months. So the sensible move is simple: pick your exam date, put it ahead of your AZ-500 expiry if you have one, and spend the gap studying the difference between the engineer you are and the one the exam describes. The agents in your directory will keep multiplying either way. The question organisations are starting to ask is who's certified to keep them safe, and there's no reason the answer shouldn't be you.
