azureblog.co.uk
← SC-500 study plan
SC-500 · Manage identity, access, and governance

Secure access to Azure resources with Microsoft Entra ID

PIM, Conditional Access, MFA and passwordless, application identities, OAuth consent, and managed identities, from a security engineer's view.

  • 20 min
  • 6 concepts
  • Try it yourself
  • 4-question check

Learn

For a cloud security engineer, identity controls are the first line of defence for Azure: who can sign in to the portal, who can hold Owner, which apps can call your APIs, and which workloads can reach secrets.

  1. 1

    Implement and configure Privileged Identity Management (PIM)

    Make Azure roles such as Owner, Contributor and User Access Administrator, and Entra roles such as Global Administrator, eligible in PIM with time-limited activation, MFA, justification and approval. Use PIM for Groups for bundles of access. Review PIM alerts for permanent privileged assignments and run access reviews of privileged roles.

    Remember: No standing Owner on subscriptions.

  2. 2

    Implement conditional access policies

    Protect Azure management with a policy targeting the Windows Azure Service Management API (portal, CLI, PowerShell, ARM) requiring phishing-resistant MFA and a compliant device for admins. Block legacy authentication, require MFA for all users, use risk-based policies, and protect sensitive actions with authentication context and protected actions.

    Remember: Protect ARM: target Windows Azure Service Management API.

  3. 3

    Implement and configure authentication methods, including multifactor authentication (MFA) and passwordless

    Enable phishing-resistant methods (passkeys/FIDO2, Windows Hello for Business, certificate-based authentication) in the authentication methods policy, and require them with authentication strengths. Note that Microsoft enforces MFA for Azure portal, CLI and PowerShell sign-ins (mandatory MFA for Azure).

    Remember: Azure management sign-ins now require MFA.

  4. 4

    Implement and configure identity for applications, including enterprise applications and app registrations

    Prefer certificates or federated credentials over secrets, set app instance property lock, restrict who can register apps, assign owners, require assignment for enterprise apps, and monitor credential expiry. Use app roles and least-privilege API permissions.

    Remember: Secrets in app registrations are a common attacker target.

  5. 5

    Manage OAuth permission grants and consent settings

    Restrict user consent to verified publishers and low-risk permissions or disable it; enable the admin consent workflow. Review existing grants (enterprise app Permissions, or with Graph PowerShell) and revoke risky ones such as broad Mail.Read or Files.Read.All. Defender for Cloud Apps OAuth app governance flags risky apps.

    Remember: Illicit consent grant attacks abuse permissive consent settings.

  6. 6

    Implement and configure managed identities for Azure resources

    Use system-assigned or user-assigned managed identities so workloads authenticate to Key Vault, Storage and SQL without secrets. Assign data-plane roles (for example Key Vault Secrets User, Storage Blob Data Reader) at the narrowest scope. Monitor managed identity sign-ins in Entra sign-in logs.

    Remember: Managed identity + data-plane role at narrow scope.

Layers protecting Azure management

  1. Strong sign-inPhishing-resistant MFA, authentication strength.
  2. Conditional AccessCompliant device, risk, location for Azure management.
  3. Just-in-time rolesPIM eligible assignments with approval.
  4. Least privilegeNarrow scopes, custom roles where needed.
  5. MonitorSign-in and audit logs, PIM alerts.

Try it

Practise building a Conditional Access policy and see who is affected.

This interactive part needs JavaScript.

In the portal

  • PIM for Azure resourcesEntra admin center: ID Governance > Privileged Identity Management > Azure resources
  • Consent settingsEntra admin center: Entra ID > Enterprise apps > Consent and permissions
  • Authentication strengthsEntra admin center: Entra ID > Authentication methods > Authentication strengths

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 SC-500 study plan.

  1. Which Conditional Access target protects the Azure portal and ARM?

  2. How do you stop users consenting to unverified apps?

  3. Which credential type is safest for an app registration?

  4. A workload needs to read blobs without secrets. What do you configure?

Sources

Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.