R-04 Entra & Security
Entra ID risk policies retired: the same name is not enough

On 1 October 2026, Microsoft retired the legacy risk policies in Entra ID Protection, meaning the user risk policy and the sign-in risk policy. Their successor is risk-based policies in Conditional Access. Many treated this as a box to tick: create a new policy, give it a similar name, done.
That is exactly the problem. A similar name is not the same protection. What matters is that the new policy hits the same users, the same resources and the same exclusions as the old one. Otherwise the most unpleasant thing in security happens: nothing. A compromised account signs in as usual, without a challenge and without a block, and nobody notices.
What changed
You configured the classic risk policies directly in ID Protection. Microsoft writes on Learn: “The legacy risk policies configured in Microsoft Entra ID Protection are retiring on October 1, 2026.” From now on, risk runs through Conditional Access, in the same rule set as everything else, with assignments, resources, controls and report-only mode.
That makes sense. But Microsoft does not make it easy for you:
- No automatic conversion. The migration consists of manual steps. If you need help, you can open a support request “Migrate legacy ID Protection policy”.
- No documented behavior after the deadline. Whether legacy policies still apply after 1 October, are frozen or removed is stated neither on Learn nor in any Message Center post I could find. In early November, the Learn pages still use the future tense.
For you this means: do not rely on the old policies. If you have no active Conditional Access policy with a risk condition, assume you have no risk protection.
Why “the same name” is not enough
A policy is called “Sign-in Risk High MFA”. Looks good. But:
- Who is assigned? All users, a group, guests?
- Which resources are in scope? Microsoft uses “All resources” in both of its guides.
- Which exclusions exist, and are they the same as before?
- Is the policy set to “On” or still to “Report-only”?
The Conditional Access overview shows two new risk policies, everything looks tidy. But the scope covers only 80 percent of users. The other 20 percent run without risk protection, and nothing about it looks like an error.
That is why: document the current state of the old policies, meaning users, exclusions, risk level and action. That is your baseline for comparison.
The right controls
| Policy | Condition | Control according to Microsoft |
|---|---|---|
| User risk | Risk level High | “Require risk remediation”. Entra automatically applies authentication strength and “Sign-in frequency: Every time”. |
| Sign-in risk | Risk level Medium and High | Require MFA, “Sign-in frequency: Every time” recommended |
“Require risk remediation” is the reason a second look pays off. Microsoft manages the right remediation flow for every authentication method, including passwordless users. The old “change your password” logic goes nowhere for users with passkeys. Two limitations: the control remediates only user risk, not sign-in risk, and it is not supported for guests and external users.
If you keep using “Require password change”: it only works if users have registered MFA. For hybrid users, password writeback must also be enabled.
⚠️ Attention
Microsoft states explicitly: “Don’t combine sign-in risk and user risk conditions in the same Conditional Access policy.” Two signals mean two policies. This is not a matter of style.
Step by step
- Document the current state: users, exclusions, risk levels and actions of the old policies.
- Create new policies in report-only mode: in the Entra Admin Center › Entra ID › Conditional Access › Policies, separately for user risk and sign-in risk, target resource “All resources”.
- Set exclusions: break glass accounts and service accounts such as the Entra Connect Sync account.
- Check MFA registration: a sign-in risk policy with MFA only helps if users have registered MFA.
- Evaluate report-only: in the sign-in logs you see which sign-ins the policy would have hit. Compare that with your list from step 1.
- Turn the policies on. Report-only is a test, not protection.
- Turn off the old policies: if they still show as active in your tenant, set “Enforce policy” to “Disabled” under ID Protection › Dashboard.
- Monitor: in the first weeks, look specifically at hits, blocks and helpdesk questions.
Licenses and workload identities
License: Risk-based policies require Microsoft Entra ID P2 or Entra Suite. Check whether the users in scope are actually licensed, not just whether P2 exists somewhere in the tenant. And important for mid-sized companies: Microsoft 365 Business Premium includes only Entra ID P1. That means no risk-based Conditional Access, neither old nor new.
Workload identities: The old risk policies only covered users, never service principals. The migration does not change that. User-scoped Conditional Access does not block service principals. If you want that, you need separate policies for workload identities, and for those a Workload Identities Premium license. They only apply to single-tenant service principals registered in your tenant. Managed identities and multitenant apps are not covered, and the only control is “Block”.
Compliance and marketing
- Fact: The legacy risk policies are retired, Conditional Access is the way forward.
- Marketing: “With Conditional Access you are compliant.” No. A technical control is not evidence for NIS2, DORA or ISO 27001.
- Assumption: That your new policies cover the old scope remains an assumption until the logs show it.
This is not legal advice. If audit or supervisory authorities are involved, talk to your compliance team.
What stays
Steering risk in Conditional Access is right. One rule set instead of two, more control, report-only for testing. But Microsoft retired a security feature without documenting what happens afterwards and without a migration tool. For a feature meant to stop compromised accounts, that is too little. All the more important that you do not just create, but measure.
☕ Espresso Moment: Same name, same effect? Only if you measured it.
Your takeaways
- The legacy risk policies in ID Protection have been retired since 1 October 2026. What happens to them afterwards, Microsoft does not document.
- Without an active Conditional Access policy with a risk condition, you have no reliable risk protection.
- The same name does not mean the same protection: compare users, resources and exclusions.
- Create user risk and sign-in risk in separate policies.
- Use “Require risk remediation” for user risk, also because of passwordless users.
- Test in report-only, then turn on.
- Check licenses: P2 or Entra Suite, Business Premium is not enough.
- Workload identities were never covered and need their own policies with their own license.
Sources: Microsoft Learn “Risk-based access policies”, “Configure and migrate risk policies” and “Conditional Access for workload identities”
Did you measure after the migration, or just tick the box? Tell me on LinkedIn.
