azureblog.co.uk
← SC-300 study plan
SC-300 · Implement authentication and access management

Manage risk with Microsoft Entra ID Protection

User risk and sign-in risk policies, MFA registration campaigns, investigating and remediating risky users and sign-ins, and risky workload identities.

  • 16 min
  • 5 concepts
  • Try it yourself
  • 4-question check

Learn

ID Protection uses Microsoft's signals to score how likely a sign-in or account is compromised, and lets Conditional Access respond automatically, so users can fix their own risk rather than waiting for the helpdesk.

  1. 1

    Implement and manage user risk by using Microsoft Entra ID Protection or Conditional Access policies

    User risk is the likelihood an account is compromised, from detections like leaked credentials or threat intelligence. Microsoft recommends a Conditional Access policy for high user risk that requires a secure password change (with MFA), or, for passwordless users, revoking sessions. Policies in ID Protection itself are legacy; build them in Conditional Access.

    Remember: High user risk → secure password change.

  2. 2

    Implement and manage sign-in risk by using Microsoft Entra ID Protection or Conditional Access policies

    Sign-in risk is the likelihood a particular sign-in isn't from the account owner: anonymous IP addresses, atypical travel, unfamiliar sign-in properties, malicious IPs, password spray. Recommended policy: require MFA for medium and high sign-in risk, with sign-in frequency set to every time. Successful MFA remediates the risk.

    Remember: Risky sign-in → MFA, every time.

  3. 3

    Implement and manage multifactor authentication registration by using authentication methods and registration campaigns

    Users can only self-remediate if they've registered MFA. Use Conditional Access on the Register security information user action to control where registration happens (for example trusted locations or with a TAP), and a registration campaign (nudge) to prompt users to set up Microsoft Authenticator at sign-in, with a snooze limit.

    Remember: No MFA registered, no self-remediation.

  4. 4

    Monitor, investigate and remediate risky users and risky sign-ins

    Reports: Risky users, Risky sign-ins and Risk detections. Admins can confirm compromised (sets risk to high and feeds machine learning), confirm safe, dismiss user risk, reset the password, or block the user. Export data to Log Analytics, Sentinel or Defender XDR for longer retention and correlation.

    Remember: Confirm compromised or safe to train the system.

  5. 5

    Monitor, investigate, and remediate risky workload identities

    ID Protection also detects risk for service principals, such as leaked credentials, suspicious sign-ins, unusual credential additions or admin consent to the app. Review the Risky workload identities report, and use Conditional Access for workload identities to block risky service principals. This needs Workload Identities Premium.

    Remember: Apps get risky too: Workload Identities Premium.

Sign-in risk or user risk?

Sign-in risk
  • Is this sign-in suspicious?
  • Anonymous IP, atypical travel, password spray
  • Remediate with MFA
User risk
  • Is this account compromised?
  • Leaked credentials, threat intelligence
  • Remediate with a secure password change

Try it

Your policies: medium or high sign-in risk requires MFA; high user risk requires a secure password change. Try a scenario.

This interactive part needs JavaScript.

In the portal

  • Risky usersEntra admin center: ID Protection > Risky users
  • Risky sign-insEntra admin center: ID Protection > Risky sign-ins
  • Registration campaignEntra admin center: Entra ID > Authentication methods > Registration campaign

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-300 study plan.

  1. What's the recommended control for high user risk?

  2. Which detection raises user risk rather than sign-in risk?

  3. Why push MFA registration campaigns?

  4. What licence covers risky workload identities?

Sources

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