Microsoft Azure Security Engineer AssociateStudy guide
The associate certification for implementing and operating Azure security (AZ-500).
About Microsoft Azure Security Engineer Associate (AZ-500)
Microsoft Azure Security Engineer Associate (AZ-500) is a Associate-level certification from Microsoft. This page organizes the exam scope into a 4-chapter, 12-section study guide and lets you check your understanding with exam-style practice questions. A good flow is to read the chapters below in order, then test yourself via "Practice questions."
Exam domains (approximate weighting)
- Manage identity and access~28%
- Secure networking~23%
- Secure compute, storage, and databases~22%
- Manage security operations~27%
Weights are approximate guidance for the live exam. Each domain is covered in detail in the chapters and sections below.
Note: This exam is scheduled to retire on 2026-08-31 (successor: SC-500).
Official exam information: https://learn.microsoft.com/en-us/credentials/certifications/resources/study-guides/az-500
1Manage Identity and Access
- 1.1Identity Management with Microsoft Entra ID
Understand Microsoft Entra ID (formerly Azure AD), the starting point of Azure security: tenants/users/groups, hybrid identity (sync), and external identities (B2B, plus Microsoft Entra External ID for customers; the older Azure AD B2C is closed to new tenants since May 2025). The basis of "Manage identity and access" in AZ-500.
- 1.2MFA and Conditional Access
Understand multi-factor authentication (MFA) beyond passwords alone, and Conditional Access that controls access based on sign-in context (user, location, device, risk)—the core of Zero Trust.
- 1.3RBAC and Privileged Identity Management (PIM)
Understand role-based access control (RBAC) that defines "who can do what," and Privileged Identity Management (PIM) that activates powerful roles only when needed—supporting least privilege.
2Secure Networking
- 2.1Traffic Control with NSGs and ASGs
Understand network security groups (NSGs) that allow/deny traffic at subnet/NIC level, and application security groups (ASGs) that group VMs by app role. The basis for minimizing traffic within a virtual network.
- 2.2Azure Firewall and Secure Management Access
Understand Azure Firewall for centralized VNet traffic control, Azure Bastion for secure VM access without public IPs, and NAT gateway to consolidate outbound to one IP—the basics of perimeter defense and secure operational access.
- 2.3Protecting Public Apps with WAF and DDoS
Understand Web Application Firewall (WAF) and DDoS Protection for public apps, plus private endpoints that keep service connectivity inside the VNet. These defend against L7 attacks and volumetric attacks.
3Secure Compute, Storage, and Databases
- 3.1Key Vault and Encryption
Understand Azure Key Vault for safely storing keys/secrets/certificates and the basics of encryption at rest. Combined with managed identity, keeping no credentials in code is core to AZ-500.
- 3.2Securing Storage and Databases
Understand storage account access control (SAS, disabling keys, Entra authorization) and network restrictions, plus Azure SQL authentication, firewall, Transparent Data Encryption (TDE), and Always Encrypted. Defend the data layer in depth.
- 3.3Securing Compute and Defender for Cloud
Understand secure VM operations (Just-In-Time VM access, disk encryption, update management) and Microsoft Defender for Cloud (secure score, workload protection) for visualizing and strengthening cloud-wide posture.
4Manage Security Operations
- 4.1Logging, Monitoring, and Security Alerts
Understand Azure Monitor, the Log Analytics workspace, and diagnostic settings as the foundation of security operations. Recording what happened and collecting/analyzing/retaining logs is the prerequisite for detection and investigation.
- 4.2Microsoft Sentinel (SIEM / SOAR)
Understand Microsoft Sentinel, a cloud-native SIEM (security information and event management) and SOAR (automated response). It ingests broadly via data connectors, detects threats with analytics rules, and responds automatically with playbooks.
- 4.3Governance and Compliance
Understand Azure Policy to technically enforce organizational rules, Azure Blueprints to apply bundled configuration templates (note: deprecated and slated for retirement in July 2026; the successor is Azure Deployment Stacks with Azure Policy), and Defender for Cloud’s regulatory compliance to visualize alignment with standards. Keep large environments consistently secure.

