Design authentication and authorisation
Recommending authentication, identity management, authorisation to Azure and on-premises resources, and managing secrets, certificates and keys.
- 18 min
- 5 concepts
- Try it yourself
- 4-question check
Learn
Identity is the control plane of a cloud design. The architect's job is to pick the right identity type for each user and workload, enforce strong authentication, give least-privilege access, and keep secrets out of code.
- 1
Recommend an authentication solution
Use Microsoft Entra ID for workforce identity with Conditional Access and phishing-resistant MFA. For hybrid, recommend password hash sync (resilient, enables leaked credential detection). For customer-facing apps, recommend Microsoft Entra External ID (external tenant) for sign-up and sign-in with local or social accounts. For apps, use modern protocols: OpenID Connect and OAuth 2.0, or SAML for SaaS.
Remember: Customers: Entra External ID. Staff: Entra ID with CA.
- 2
Recommend an identity management solution
Automate the lifecycle: HR-driven provisioning (Workday or SuccessFactors to Entra ID or AD), SCIM provisioning to SaaS apps, entitlement management for access requests, access reviews for recertification, and lifecycle workflows for joiners and leavers. Use B2B collaboration for partners and cross-tenant sync for multi-tenant organisations.
Remember: HR is the source of truth for joiners and leavers.
- 3
Recommend a solution for authorizing access to Azure resources
Use Azure RBAC with built-in roles at the narrowest scope, assigned to groups. Use PIM for privileged roles. Use managed identities for workloads. Consider ABAC conditions (for example on storage blob tags) to reduce role assignments. Use Azure Policy for guardrails and deny assignments through deployment stacks or managed apps where needed.
Remember: Groups, narrowest scope, JIT for admins.
- 4
Recommend a solution for authorizing access to on-premises resources
Publish on-premises web apps with Microsoft Entra Application Proxy or Entra Private Access so users authenticate with Entra ID and Conditional Access, with Kerberos constrained delegation for Windows-integrated apps. Use Entra Domain Services for lift-and-shift apps needing LDAP or Kerberos in Azure, or extend AD with domain controllers in Azure.
Remember: Legacy web app remote access: Application Proxy.
- 5
Recommend a solution to manage secrets, certificates, and keys
Use Azure Key Vault with the RBAC permission model, soft delete and purge protection, private endpoints, and one vault per app per environment. Use Managed HSM for FIPS 140-3 Level 3 single-tenant keys. Rotate secrets and certificates automatically, and use managed identities to reach the vault. Customer-managed keys encrypt services like Storage and SQL with your own keys.
Remember: One vault per app per environment; purge protection on.
Who signs in, and with what
| Who | Recommend |
|---|---|
| Employees | Microsoft Entra ID with Conditional Access and phishing-resistant MFA |
| Partners | Entra B2B collaboration |
| Customers | Microsoft Entra External ID |
| Azure workloads | Managed identities |
| Workloads outside Azure | Service principal with workload identity federation |
Try it
Choose the identity design.
This interactive part needs JavaScript.
In the portal
- Key vaultsAzure portal: Key vaults > Create
- Application ProxyEntra admin center: Global Secure Access > Connect > Connectors
- External IDEntra admin center: Entra ID > External Identities > Overview
Key terms
Click a card to see the definition.
Check your understanding
4 questions. Score 80% or more and these skills are marked as confident in your AZ-305 study plan.
A public app needs sign-up with Google accounts. What do you recommend?
External ID handles customer identities.
Which Key Vault setting stops a deleted vault being permanently removed during retention?
Purge protection enforces the retention period.
Which gives single-tenant FIPS 140-3 Level 3 HSMs?
Managed HSM is dedicated.
A legacy on-premises app needs Kerberos and remote access with MFA. What do you recommend?
Users authenticate with Entra; KCD signs them in to the app.
Sources
- Microsoft Learn: Design authentication and authorization solutions
- Microsoft Learn: Microsoft Entra External ID overview
- Microsoft Learn: Azure Key Vault best practices
- Microsoft Learn: Azure ABAC
Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.