Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

2.1.1.7. Configure Self-Service Password Reset (SSPR)

2.1.1.7. Configure Self-Service Password Reset (SSPR)

💡 First Principle: A forgotten password is an identity-proofing problem, not a helpdesk problem. If users prove who they are with methods they registered in advance, the system can safely reset the password itself, which removes the most common helpdesk ticket and the social-engineering risk of resetting passwords over the phone.

Scenario: Your helpdesk handles 400 password tickets a month. You want to pilot self-service reset with the Finance team, require two verification methods, and, because most users are synchronized from on-premises Active Directory, make sure a reset in the cloud also changes the password users type at their domain-joined PCs.

What It Is: Microsoft Entra self-service password reset lets users change or reset their password, or unlock their account, with no administrator involvement. Users start at aka.ms/sspr (or the Can't access your account link), pass a CAPTCHA, and verify with the methods they registered.

Licensing: Password change for cloud-only users (they know the current password) works on Microsoft Entra ID Free. Password reset for cloud-only users needs Microsoft 365 Business Standard or higher, or Microsoft Entra ID P1/P2. Reset or change with on-premises writeback needs Microsoft Entra ID P1/P2 or Microsoft 365 Business Premium; Business Basic and Standard don't include writeback (SSPR licensing).

Enabling SSPR (Entra ID > Password reset), at least Authentication Policy Administrator:
  • Properties: Self service password reset enabled = None, Selected or All. Selected targets one group in the admin center (nested groups are supported), which makes it the pilot option.
  • Authentication methods: Number of methods required to reset = 1 or 2. Which methods users may use is now governed by the tenant-wide Authentication methods policy: beginning September 30, 2025, methods can't be managed in the legacy MFA and SSPR policies, and security questions are the one method still managed in the legacy SSPR settings. Microsoft Authenticator and OATH tokens count as a single method, so they can't satisfy a two-method requirement together.
  • Registration: Require users to register when signing in (Yes/No) and Number of days before users are asked to reconfirm their authentication information (0 to 730; 0 means never). Users can also register at aka.ms/ssprsetup.
  • Notifications: Notify users on password resets emails the user; Notify all admins when other admins reset their password emails Global Administrators.
  • Customization: a custom helpdesk email or URL for the "Contact your administrator" link.

If a user registered fewer methods than the policy requires, SSPR shows an error and they must ask an administrator for a reset (how SSPR works).

Administrator Accounts Are Different: Accounts holding Microsoft Entra administrator roles (Global Administrator, User Administrator, Helpdesk Administrator, Password Administrator and many more) don't follow the policy you configure for users. When they reset through SSPR, a two-gate policy that you can't change applies: two pieces of authentication data, and security questions are prohibited (admin reset policy). The two-gate policy applies once a custom domain is configured, Microsoft Entra Connect is synchronizing, or a trial is past 30 days; before that a one-gate policy applies. Whether administrators may use SSPR at all is a separate switch: the AllowedToUseSspr property of the tenant authorization policy. Always test SSPR with a non-admin account.

Password Writeback (Hybrid): For users whose password is managed on-premises (password hash sync, pass-through authentication or federation), SSPR only works if password writeback is deployed. Writeback runs through Microsoft Entra Connect or Microsoft Entra Connect cloud sync, is synchronous (the user immediately learns if the password breaks on-premises policy), enforces AD DS history, complexity and age rules, and needs no inbound firewall rules because it relays over outbound 443. To enable it with Connect Sync (tutorial):

  1. Grant the Connect AD DS account Reset password, Change password, write on lockoutTime and pwdLastSet, and Unexpire Password.
  2. In the Connect wizard, Customize synchronization options > Optional features > Password writeback.
  3. In the admin center, as at least Hybrid Identity Administrator, Password reset > On-premises integration > Write back passwords to your on-premises directory (optionally Allow users to unlock accounts without resetting their password).
Practical Implementation: Disable SSPR for Administrator Accounts
# Turns off SSPR for administrator accounts tenant-wide (can take up to 60 minutes)
Connect-MgGraph -Scopes Policy.ReadWrite.Authorization
Update-MgPolicyAuthorizationPolicy -AllowedToUseSspr:$false
Visual: SSPR Decision Path

⚠️ Common Pitfall: Testing SSPR with your own admin account. Admins follow the fixed two-gate policy, so the test tells you nothing about what your users will experience.

⚠️ Exam Trap: "Synced users get contact your administrator when they try SSPR" points to missing password writeback, not a missing license or a Conditional Access block. And writeback requires P1/P2 or Business Premium, never Business Standard.

Key Trade-Offs:
  • One vs. Two Methods: One method is easier to register and use; two methods resist an attacker who controls a single phone number or mailbox.
  • Selected vs. All: A pilot group lets you fix registration problems before they reach everyone, but anyone outside the group still needs the helpdesk.

Reflection Question: Your policy requires two methods and allows only the Authenticator app and mobile phone. Which users will be unable to reset, and what would you change in the methods available to fix it?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•22 professional certifications earned