Microsoft Entra IDHowto Sspr Authenticationdata
In brief
Some organizations prefer to bootstrap this process through synchronization of authentication data that already exists in Active Directory Domain Services. This synchronized data is made available to Microsoft Entra ID and SSPR without requiring user interact…
Documentation change
Some organizations prefer to bootstrap this process through synchronization of authentication data that already exists in Active Directory Domain Services. This synchronized data is made available to Microsoft Entra ID and SSPR without requiring user interaction. When users need to change or reset their password, they can do so even if they haven't previously registered their contact information.
You can prepopulate authentication contact information if you meet the following requirements:
diff --git a/docs/identity/authentication/howto-sspr-authenticationdata.md b/docs/identity/authentication/howto-sspr-authenticationdata.md index 14f0e4ed7d7..550ffbf207d 100644 --- a/docs/identity/authentication/howto-sspr-authenticationdata.md +++ b/docs/identity/authentication/howto-sspr-authenticationdata.md @@ -13,7 +13,8 @@ To use Microsoft Entra self-service password reset (SSPR), authentication inform Some organizations prefer to bootstrap this process through synchronization of authentication data that already exists in Active Directory Domain Services. This synchronized data is made available to Microsoft Entra ID and SSPR without requiring user interaction. When users need to change or reset their password, they can do so even if they haven't previously registered their contact information. > [!IMPORTANT] -> Starting **July 6, 2026**, a registration campaign will prompt affected users to register methods ahead of enforcement. Ensure users have registered at least one method that satisfies your SSPR policy. For more information, see [How to manage authentication methods](how-to-authentication-methods-manage.md). +> Starting **Aug 6, 2026**, If your SSPR settings require users to register during sign-in, and enabled users do not have enough methods to complete SSPR, a registration campaign will prompt affected users to register methods ahead of enforcement. Ensure users have registered at least one method that satisfies your SSPR policy. For more information, see [How to manage authentication methods](how-to-authentication-methods-manage.md). +> > Starting **September 7, 2026**, SSPR will only accept explicitly registered authentication methods. Directory-sourced properties — such as `mobilePhone`, `businessPhone`, and `otherMails` — that were never registered will no longer work for SSPR verification. You can prepopulate authentication contact information if you meet the following requirements: