Identity, access, and security
Microsoft Entra ID, authentication, authorization, RBAC, and Zero Trust ideas for AZ-900.
Learning objectives
Work through each idea below. Use Listen to hear the explanation — pick a voice next to Listen anytime (Sophia is the default).
- Microsoft Entra ID
- Authentication vs authorization
- SSO, MFA, and passwordless (Hello / FIDO2 / Authenticator) strengthen sign-in.
- External identities
- Microsoft Entra Domain Services
- RBAC
- Conditional Access evaluates context and risk before granting access.
- Defense in depth
- Zero Trust
- Microsoft Defender for Cloud
Microsoft Entra ID
cloud identity directory for users, groups, and app registrations.
Authentication vs authorization
prove identity vs grant permissions.
SSO, MFA, and passwordless (Hello / FIDO2 / Authenticator) strengthen sign-in.
SSO, MFA, and passwordless (Hello / FIDO2 / Authenticator) strengthen sign-in.
External identities
B2B guests for partners; B2C for customer identities.
Microsoft Entra Domain Services
managed domain join / LDAP / Kerberos without your own DCs.
RBAC
assign roles at a scope to enforce least privilege on Azure resources.
Conditional Access evaluates context and risk before granting access.
Conditional Access evaluates context and risk before granting access.
Defense in depth
layered controls across identity, network, compute, and data.
Zero Trust
never trust by default; verify explicitly and assume breach.
Microsoft Defender for Cloud
security posture and threat protection recommendations.