Blog Post

Microsoft Entra Blog
5 MIN READ

Microsoft Entra ID security updates: What organizations need to do now

Swaroop Krishnamurthy's avatar
Jun 08, 2026

Prepare now for three Microsoft Entra ID changes affecting Custom controls, credential registration, and self-service password reset (SSPR) enforcement.

Microsoft Entra ID continues to strengthen identity security by modernizing how authentication and access policies are enforced. As part of this effort, Microsoft is retiring legacy capabilities and closing gaps that attackers could exploit. These updates focus on three key areas: replacing Custom controls with External MFA, enforcing Conditional Access consistently during credential registration, and requiring explicitly registered authentication methods for self-service password reset (SSPR). Together, these changes help ensure that your security policies are applied uniformly and backed by strong, user-verified signals.

Key points

  • Custom controls are being deprecated in favor of External MFA. Existing configurations keep working during the transition, but you should begin migration planning now. Custom controls retire September 30, 2026, and reach end of life in May 2027.
  • Conditional Access will be enforced consistently during credential registration. Starting July 13, 2026, policies targeting the Register security information action will also apply to Windows Hello for Business provisioning and macOS Platform Single Sign-on registration. Test policies in report-only mode before then.
  • SSPR will require explicitly registered authentication methods. A registration campaign begins Oct 65, 2026, and from Nov 9, 2026, SSPR will accept only registered methods — directory-sourced phone numbers and email addresses that were never formally registered will no longer be accepted.

Deprecation of Custom controls

What’s changing?

Microsoft Entra ID is deprecating Custom controls in favor of External MFA, a more integrated, standards-based capability for incorporating third-party MFA providers directly into Conditional Access. External MFA delivers deeper policy integration, a more seamless user experience, and greater flexibility than the legacy Custom controls model. While existing Custom controls configurations will continue to function during the transition period, organizations should begin planning their migration to External MFA.

When will you see this change?

Custom controls will be retired on September 30, 2026, and the service will reach end of life in May 2027.

Who will be affected by this change?

This update affects organizations currently using Custom controls to integrate third-party MFA providers with Conditional Access.

How will this affect your organization?

Organizations relying on Custom controls will need to transition to External MFA to maintain support and continue using third-party MFA solutions within Microsoft Entra ID. Moving to External MFA also enables more consistent Conditional Access enforcement and improved integration with Microsoft Entra security capabilities.

What do you need to do to prepare?

Organizations should: 

  • Review existing Custom controls integrations
  • Evaluate External MFA migration requirements
  • Test Conditional Access policies and user experiences before migration
  • Begin migration planning ahead of the retirement date
  • Read more in the External MFA General Availability announcement and migration guidance.

Consistent Conditional Access enforcement for credential registration

What’s changing?

Microsoft is strengthening Conditional Access enforcement during credential registration flows to close a long-standing enforcement gap.

Today, policies targeting the Register security information user action are enforced in My Security Info and Microsoft Authenticator, but not during Windows Hello for Business provisioning or macOS Platform Single Sign-on registration. Conditional Access policies will be enforced consistently across these registration experiences. If users do not meet policy requirements, they will be prompted to satisfy those requirements before completing registration. MFA will continue to be required by default for passwordless credential enrollment, with Conditional Access providing an additional layer of control.

When will you see this change?

This update will roll out during the week of July 13, 2026 to all tenants.

Who will be affected by this change?

This change affects organizations using:

  • Conditional Access policies scoped to registration flows
  • Windows Hello for Business
  • macOS Platform Single Sign-on
  • Passwordless credential enrollment scenarios

How will this affect your organization?

Organizations may see additional prompts or enforcement steps during device setup and credential registration if users do not meet Conditional Access requirements. This change ensures registration flows are governed by the same security controls already applied across other authentication experiences.

What do you need to do to prepare?

Organizations should review existing registration policies and validate that users can meet Conditional Access requirements during onboarding and device setup. Microsoft recommends testing policies in report-only mode before enforcement begins.

SSPR update: Registered authentication methods required

What’s changing?

Microsoft is updating Microsoft Entra self-service password reset (SSPR) so that only explicitly registered authentication methods can be used for verification. Directory-sourced phone numbers or email addresses stored only as user object properties—but never formally registered as authentication methods—will no longer be accepted. This change aligns SSPR with Entra ID’s broader authentication model by requiring verification methods tied to user intent and proof of possession.

When will you see this change?

Beginning Oct 5, 2026, Microsoft will deploy an SSPR registration campaign that prompts affected administrators and end users to register authentication methods ahead of enforcement. No administrator action is required to enable this campaign.

Starting Nov 9, 2026, SSPR will accept only authentication methods that users or administrators have explicitly registered.

Who will be affected by this change?

This update affects organizations and users that still rely on unregistered directory-based phone numbers or email addresses for password reset verification.

How will this affect your organization?

Users without registered authentication methods may experience interruptions during password reset or account recovery flows after enforcement begins. Organizations may also see an increase in registration prompts during the transition period.

What do you need to do to prepare?

Organizations should:

  • Review authentication method registration coverage
  • Identify users relying on unregistered directory values
  • Encourage users to register approved authentication methods
  • Communicate upcoming changes to users and help desk teams

Microsoft will prompt affected users and administrators during the transition period to help organizations prepare before enforcement begins.

Now is the time to review your current configurations, identify where these changes apply in your environment, and begin preparing your users and admins before enforcement milestones arrive. Start by assessing any Custom controls dependencies, validating registration-related Conditional Access policies, and confirming that authentication methods used for SSPR are explicitly registered.

- Swaroop Krishnamurthy, Principal Product Manager

 

Additional resources

Learn more about Microsoft Entra 

Prevent identity attacks, ensure least privilege access, unify access controls, and improve the experience for users with comprehensive identity and network access solutions across on-premises and clouds.

Updated Aug 04, 2026
Version 4.0

5 Comments

  • VinnieG's avatar
    VinnieG
    Copper Contributor

    With the introduction of External MFA we need two things please!

    1. Authentication Strength - Need to allow option for External MFA

    2. SSPR - This won't work with external MFA. This needs to be sorted!

  • David Wykes's avatar
    David Wykes
    Copper Contributor

    Hi,

    Theres still no information about authentication strengths beyond don’t use it as “External MFA isn't yet compatible with authentication strength policies.”

    Is this going to be  implemented in time for the Sep cutoff for creating new custom controls?

    It’s a pretty critical requirement for passing through security contexts to the external mfa system - Duo in my case.

  • Cyril_K's avatar
    Cyril_K
    Copper Contributor

    Hi,

    Regarding the SSPR change.

    I've already submitted a support request to get those answers but I've read opposite things here or posted on blogs by MVPs, or regarding the attributs during some tests...

    How to identity impacted users in the report ? Should we filter on isSsprEnabled=true and isSsprRegistered=false, which is what is advised on blogs ? Or isSsprCapable=true and methodsRegistered=None which is what I could notice with a test account and agreed by the support ? Or multiple filters ?

    Also, if we don't want the campaign to launch on July 6th, how can we prevent it ? 

    Thanks in advance

  • While seems a bit short on notice of the change I am happy to see these coming. 

     

    Question on "directory sourced phone numbers". Could you please clarify the definition. 

     

    Another question: Microsoft posted an initiative about phasing out phone numbers and SMS based codes in Entra, at least now in effect for home users. 

     

    Do I understand correctly business accounts are still going to be supporting phone numbers / SMS even though the reason for removal has been justified with security concerns that truthfully apply?

    • TimLarson's avatar
      TimLarson
      Icon for Microsoft rankMicrosoft

      Karl-WE​ 

      Following up on your question below ...

       

      Question on "directory sourced phone numbers". Could you please clarify the definition. 

       

      In context of the SSPR change - directory sourced phone numbers are the user-object properties - mobilePhone and businessPhones/officePhone set on

      the user account, not registered authentication methods.

       

      The SSPR change above does not impact any prior announcement regarding phasing out of SMS based MFA and authentication for Entra. All

      prior announcements regarding changes in SMS support in Entra still apply.