How to Enable Self-Service Password Reset in Microsoft Entra ID

November 17, 2026

Microsoft Entra self-service password reset (SSPR) lets users verify their identity and reset a forgotten password without waiting for an administrator or help desk. A controlled rollout can reduce lockout-related downtime, but SSPR is not a single toggle: licensing, authentication methods, registration, hybrid identity, and recovery security all matter.

This guide follows Microsoft’s current documented workflow. Portal labels can differ slightly by tenant and migration state. The steps below were verified against Microsoft documentation but were not executed in a live tenant for this article.

Before you start

Prepare the following before changing the policy:

  • A pilot group. Start with IT staff or a small test group. Do not begin with every user.
  • A test user. Use a non-administrator account whose password you know. Do not use a privileged account for the first test.
  • Appropriate permissions. Microsoft’s current tutorial requires at least the Authentication Policy Administrator role for the documented setup.
  • Licensing. Cloud-only password reset is included with Microsoft Entra ID Free and Microsoft 365 Business Standard or higher, but every user who benefits from SSPR needs an appropriate license. On-premises password writeback requires Microsoft Entra ID P1 or P2, or Microsoft 365 Business Premium. Standalone Microsoft 365 Basic and Standard do not support on-premises writeback.

For a production rollout, also identify how users will register a second recovery method, how the help desk will verify users who cannot complete SSPR, and who will monitor password-reset notifications.

1. Create a pilot group

  1. Open the Microsoft Entra admin center.
  2. Go to Entra ID > Groups and create or select a security group for the pilot.
  3. Add a small number of test users. Include at least one ordinary user and, if your support process requires it, a separate administrator test account.

Use a dedicated group rather than targeting individual users. It makes the rollout easier to review, expand, and reverse.

2. Enable SSPR for the pilot

  1. In the Microsoft Entra admin center, go to Entra ID > Password reset > Properties.
  2. For Self service password reset enabled, select Selected.
  3. Select the group picker, choose the pilot group, and save the change.

The available scope is normally None, Selected, or All. Use Selected first. Microsoft’s documented portal workflow currently allows one group to be selected directly in this screen, while nested groups can be used as part of a broader deployment design.

3. Configure authentication methods

SSPR must verify enough independent evidence before it permits a password reset. The reset policy can require one or two methods. Requiring two methods is stronger, but users must register enough methods to satisfy that requirement.

Microsoft now recommends managing authentication methods through Entra ID > Authentication methods > Policies. The legacy MFA and SSPR policy controls for managing authentication methods were deprecated after September 30, 2025. Your tenant may still show legacy controls during migration, so check the policy migration state before changing settings in both places.

For the pilot:

  1. Open Entra ID > Authentication methods > Policies.
  2. Enable the methods your organization has approved and target them to the pilot group or the appropriate user scope.
  3. Return to Entra ID > Password reset > Authentication methods, if that page is available in your tenant, and set the number of methods required to reset to 2 for a stronger pilot policy.
  4. Save the changes.

Do not assume that two entries in the policy always equal two independent factors. For SSPR, Microsoft Authenticator, software OATH tokens, and hardware OATH tokens count as one authentication method. If your policy requires two methods, Authenticator alone is not sufficient. Microsoft recommends that users register two or more usable methods so a lost phone or unavailable channel does not create another help-desk incident.

SMS, voice calls, and personal email may be convenient recovery options, but they have different security risks. Use stronger methods where practical, document exceptions, and do not allow a recovery address or phone number that the organization cannot protect or verify.

4. Require users to register their recovery information

  1. Go to Entra ID > Password reset > Registration.
  2. Set Require users to register when signing in to Yes.
  3. Choose how often users must reconfirm their authentication information. Microsoft’s tutorial uses 180 days as an example; choose a value that matches your risk and support requirements.
  4. Save the settings.

Users can also register manually at aka.ms/ssprsetup. A registration prompt may interrupt a sign-in session once, but it does not terminate an already authenticated session. Keep the registration window short and communicate the change before expanding the pilot.

5. Configure notifications and the help-desk link

  1. Open Entra ID > Password reset > Notifications.
  2. Enable notifications when a user resets their password.
  3. Enable notifications to all administrators when another administrator resets a password.
  4. Open Customization and add a help-desk email address or support URL.
  5. Save the settings.

Password-reset notifications give users and administrators an opportunity to report an unexpected reset. They do not replace sign-in monitoring or incident-response procedures.

6. Test registration and a password reset

Test with a non-administrator pilot account in a private or incognito browser window so cached sessions do not hide configuration problems.

  1. Open a private browser window and visit aka.ms/ssprsetup.
  2. Sign in as the pilot user and register the required authentication methods.
  3. Open another private browser window and visit aka.ms/sspr.
  4. Enter the user’s account name and complete the CAPTCHA.
  5. Complete the required verification methods and set a new password.
  6. Sign in to a normal Microsoft 365 application with the new password.
  7. Confirm that the user received the password-reset notification.

Also test the failure paths: a user with only one registered method, an expired or inaccessible phone, an administrator account, and a user outside the pilot group. These tests confirm that the policy is scoped correctly instead of merely proving that one successful reset works.

Hybrid identity: password writeback is a separate deployment

Cloud-only SSPR changes the password in Microsoft Entra ID. If your users are synchronized from on-premises Active Directory Domain Services, the password must be written back to the on-premises directory for the change to work consistently.

Do not assume that enabling cloud SSPR enables writeback. Microsoft documents separate prerequisites, including an appropriate license, a supported Microsoft Entra Connect or Cloud Sync deployment, and the required administrative permissions. For Cloud Sync, Microsoft’s current tutorial requires the Microsoft Entra Connect cloud sync provisioning agent version 1.1.977.0 or later and a Hybrid Identity Administrator account.

After the synchronization service is configured, review Entra ID > Password reset > On-premises integration. Enable password writeback only after confirming that the synchronization agent, service-account permissions, password policies, and directory scope are ready. You can also enable account unlock without requiring a password reset, if that matches your operational policy.

On-premises password policy can still reject a reset. A successful cloud message is not proof that the new password has reached every domain controller. Validate the result against the on-premises directory and allow for synchronization and replication delays.

Security and operational checklist

  • Roll out to a pilot group before selecting all users.
  • Require two SSPR methods where the user population and recovery channels support it.
  • Prefer phishing-resistant or app-based methods for sign-in and recovery where available; treat SMS, voice, and personal email as risk-managed exceptions.
  • Keep administrator accounts under the stronger administrator reset policy and monitor administrator-reset notifications.
  • Make sure users have more than the minimum number of registered methods.
  • Define a help-desk identity-verification process for users who cannot complete SSPR. Do not bypass verification because a user is under time pressure.
  • Review the Authentication methods policy migration state. Avoid maintaining contradictory legacy and current policies.
  • For hybrid tenants, test password writeback and account unlock separately from cloud-only resets.

Common problems

The user is told to contact an administrator. Confirm that the user is in the SSPR scope, has a valid license, and has registered enough methods for the current policy.

The user registered Authenticator but still cannot satisfy a two-method reset. Authenticator counts as one SSPR method. Register and enable another approved method.

The reset succeeds in the cloud but the on-premises password does not work. Check that writeback is enabled, the user is in scope, the synchronization agent is healthy, and the on-premises account permissions and password policy allow the change.

Users see unexpected registration prompts. Review the selected SSPR group, the registration policy, group membership, and the Authentication methods policy. Test in a private browser window after allowing time for policy propagation.

References

Need help planning SSPR, Microsoft 365 identity, or hybrid password writeback? Contact Guava Systems for implementation assistance.

Topics:
Read next
November 21, 2026

How to Create and Configure a Shared Mailbox in Microsoft 365

Create a Microsoft 365 shared mailbox, grant the correct Full Access and Send As permissions, understand automapping and licensing, and verify that users can work from Outlook safely.
November 21, 2026

How to Require MFA for Administrator Roles with Microsoft Entra Conditional Access

Protect privileged Microsoft Entra accounts by creating a report-only Conditional Access policy that requires MFA for built-in administrator roles, then safely moving it to On.