Microsoft AZ-500 Retirement: What Changed and What to Study Now

Microsoft AZ-500 is now a retired exam. Microsoft retired Azure Security Technologies on August 31, 2026, so candidates should no longer treat an older AZ-500 outline as a current booking or certification plan. The useful question in late 2026 is what the old material still teaches, what changed in Microsoft’s security certification direction, and where a cloud-security learner should focus next.

The retired Microsoft AZ-500 exam covered identity and access, networking, compute and data protection, Microsoft Defender for Cloud, and security operations. Those skills remain valuable, but the current Microsoft path has moved toward the broader Microsoft SC-500 exam and the Microsoft Cloud and AI Security Engineer Associate certification.

That is not a simple code change. AZ-500 centered on securing Azure technologies. SC-500 keeps many cloud-security foundations while expanding the role across end-to-end cloud controls and explicit AI-workload and agent security. The best transition plan therefore preserves durable engineering skills while rebuilding study priorities around the current role.

AZ-500 is legacy context, not a current exam target

The first update is administrative and important: AZ-500 can no longer be scheduled. Any course or article that still describes it as an active Microsoft exam is outdated. Existing notes can still be useful, but they should be labeled as legacy material and mapped against the current path before more study time is invested.

Separate exam facts from skill value. The exam code and retired certification path are historical. Least privilege, network segmentation, Key Vault security, workload protection, data security, posture management, and monitoring are still current security-engineering concerns.

This prevents two opposite mistakes: throwing away good Azure security knowledge because the exam retired, or continuing to prepare against an obsolete objective list as though Microsoft’s role definition had not changed.

Identity and least privilege still transfer directly

Identity remains the control plane for much of cloud security. Microsoft Entra ID, role assignments, privileged access, Conditional Access, managed identities, service principals, and governance still matter when protecting modern Azure workloads.

The current Microsoft SC-500 Entra identity protections material extends familiar AZ-500 thinking into a broader environment. Human administrators are only part of the picture. Applications, automation, managed identities, and AI agents can all become security principals with permissions that need to be designed, reviewed, and monitored.

When you revisit an old identity lab, do not simply confirm that a role assignment works. Ask whether the principal needs the permission, whether the scope is narrower than the whole subscription, whether the access should be time-bound, and which evidence would reveal misuse.

Key Vault and secret-management skills remain current

AZ-500 candidates studied keys, secrets, certificates, encryption, and secure application access. Those skills continue to transfer because cloud applications and automation still need protected credentials and cryptographic material.

Microsoft SC-500 Key Vault security is a useful bridge from the retired exam to current practice. The modern question is broader than whether a secret can be stored safely. It includes which identity accesses it, how permission is scoped, whether private connectivity is required, how rotation works, and whether a stored secret can be eliminated entirely.

Update old labs by replacing long-lived credentials with managed identity or another appropriate short-lived mechanism where possible. That reflects a durable cloud-security principle: reduce standing secrets and reduce the blast radius of any credential that still exists.

Network security still matters as part of end-to-end architecture

Network security groups, Azure Firewall, private endpoints, application protection, secure hybrid connectivity, and segmentation remain highly relevant. What changes is the context in which they are applied.

Azure network security controls for Microsoft SC-500 should be studied as traffic-path decisions rather than isolated features. Identify the source, destination, allowed path, identity boundary, inspection point, and expected telemetry.

A private endpoint can reduce public exposure, but it does not replace authorization. A firewall can restrict network traffic, but it does not replace application permissions or data protection. Strong current preparation connects network controls to identity, workload configuration, encryption, and monitoring.

Data protection and database security remain durable skills

Storage accounts, databases, keys, encryption, private access, backups, logging, and authorization remain central to cloud-security engineering. Existing AZ-500 notes on these areas can often be retained after they are checked against current Azure behavior.

Reframe each service around a threat model. What data is sensitive? Which identity needs access? Which network path is allowed? Which key protects the data? How is recovery handled? Which telemetry would reveal suspicious access or policy drift?

This becomes more important as AI applications consume enterprise data. An organization can have strong storage encryption and still create risk if an AI agent or workload identity has unnecessarily broad permissions to the same data.

Defender for Cloud and posture management remain central

AZ-500 learners studied Microsoft Defender for Cloud, secure score, recommendations, workload protections, vulnerability findings, and security posture. That foundation remains useful because current cloud security is as much about preventing weak configurations as responding to active attacks.

Do not treat a recommendation as the end of the task. Ask what caused the finding, which resource or architecture choice created the exposure, what change fixes the root problem, and how you will verify the control without breaking the workload.

A useful lab deliberately introduces a safe weak configuration, observes the posture signal, remediates it, and then confirms that both the finding and the underlying exposure are gone. This creates operational understanding rather than dashboard familiarity.

AI workload and agent security are the clearest new study area

The most obvious expansion beyond the AZ-500 era is AI security. Current cloud and AI security engineers must think about model endpoints, AI services, enterprise data used by AI systems, agent identities, tool permissions, and monitoring of automated actions.

Microsoft SC-500 AI workload and agent security should be treated as genuinely new material rather than a renamed AZ-500 objective. An agent can read data, call tools, trigger workflows, and act through application identities, so least privilege and auditability become even more important.

The good news is that mature principles transfer: secure identity, narrow permissions, network segmentation, data governance, threat modeling, logging, and human oversight. The architecture is newer; the control objectives are familiar.

Build a transition matrix instead of restarting from zero

Create four categories for your old AZ-500 notes: transfers directly, needs an updated implementation, useful background only, and newly missing from the current role. Identity, network controls, Key Vault, data protection, posture management, and monitoring will populate the first two categories. AI workload and agent security will create some of the largest new gaps.

Then rebuild your learning sequence around current SC-500 responsibilities. A transition matrix prevents wasted time because it shows exactly which old labs can be reused and which areas require genuinely new study.

Every legacy topic should have a reason to remain. If you cannot map it to a current responsibility or explain its continuing architectural value, it should not consume the same study time as active SC-500 material.

Audit old AZ-500 resources before trusting them

Retirement creates a second problem beyond the exam code: old learning resources can mix durable security principles with product names, portal paths, or certification statements that are no longer current. Review every resource with that distinction in mind.

First, verify whether the material describes an active credential or simply teaches an Azure security concept. Remove any scheduling guidance, passing strategy, or certification-path claims that assume AZ-500 is still available. Second, check whether service names, identity patterns, and security products have changed. Third, compare the topic with current SC-500 responsibilities so that useful material is placed in the right modern context.

Do not discard a good network-segmentation or Key Vault lab merely because its title says AZ-500. Rewrite the learning objective around the current security problem. Conversely, do not preserve an outdated exam-domain percentage or “current exam” statement just because the technical lab remains valid.

This audit process turns an old course library into a current skill library. It also prevents a learner from spending valuable time mastering details that no longer support the active Microsoft security path.

Use one modern security lab to prove the transition

Take a small Azure workload and secure it end to end. Use a workload identity with least privilege, protect secrets or keys, restrict network paths, secure storage or a database, enable posture management, and collect the telemetry needed to validate the design.

Then add a small AI component or agent. Document which identity it uses, which data it can reach, which tools it can invoke, and which logs show its actions. Introduce one weak permission or exposed path and work through prevention, detection, and remediation.

Finally, repeat the design exercise without following the old AZ-500 checklist. Start with the threat model, then choose identity, network, data, secret, posture, and monitoring controls. If you can reconstruct a secure design from the risks, your knowledge has transferred beyond the retired exam.

Microsoft AZ-500 remains useful as a historical skill framework, but it should no longer drive a current exam plan. Keep the durable security-engineering foundations and point new preparation toward Microsoft SC-500 and the current Cloud and AI Security Engineer role.

  • img