Published Jul 23, 2026
Message Center
Updated October 7,9, 2026: We have updated the timeline and content. Thank you for your patience.
What and Why
We're introducing a new Microsoft Entra capability that allows authenticatedAllow password changeschange after secure sign-in directly from My Sign-Ins using an existing strong credential, such as a passkey, FIDO2 security key, or Windows Hello for Business. Users can complete this action even if they don't know their current password and without using self-service password reset (SSPR) or contacting the helpdesk.
Many organizations are adopting authenticatedallowed password changechanges after secure sign-ins but still maintain passwords for legacy applications and services. This update helps reduce password-related support requests and removes a common barrier to adoption. The feature is disabled by default and requires administrator enablement before users can access it.
Rollout Schedule
Impact on Your Organization
Who is affected
Platforms/Services
What will happen
Action Required/Recommendations
No action is required.
If your organization plans to support authenticatedallowed password change:changes after secure sign-in:
Learn more
Compliance Considerations
| Question | Answer |
| Does the change include an admin control? | Yes. The feature is disabled by default and requires explicit administrator enablement. |
| Does the change modify how users can access or correct their personal data? | Yes. Users gain a new self-service method to update their password using an existing |
Updated October 7, 2026: We have updated the timeline and content. Thank you for your patience.
What and Why
We're introducing a new Microsoft Entra capability that allows authenticated password changes directly from My Sign-Ins using an existing strong credential, such as a passkey, FIDO2 security key, or Windows Hello for Business. Users can complete this action even if they don't know their current password and without using self-service password reset (SSPR) or contacting the helpdesk.
Many organizations are adopting authenticated password change but still maintain passwords for legacy applications and services. This update helps reduce password-related support requests and removes a common barrier to adoption. The feature is disabled by default and requires administrator enablement before users can access it.
Rollout Schedule
Impact on Your Organization
Who is affected
Platforms/Services
What will happen
Action Required/Recommendations
No action is required.
If your organization plans to support authenticated password change:
Learn more
Compliance Considerations
| Question | Answer |
| Does the change include an admin control? | Yes. The feature is disabled by default and requires explicit administrator enablement. |
| Does the change modify how users can access or correct their personal data? | Yes. Users gain a new self-service method to update their password using an existing authenticated password change. |