Plan an Azure Active Directory self-service password reset deployment
This deployment plan offers guidance and best practices for deploying Azure AD self-service password reset (SSPR).
If you're an end user and need to get back into your account, go to https://aka.ms/sspr.
Self-Service Password Reset (SSPR) is an Azure Active Directory (AD) feature that enables users to reset their passwords without contacting IT staff for help. The users can quickly unblock themselves and continue working no matter where they are or time of day. By allowing the employees to unblock themselves, your organization can reduce the non-productive time and high support costs for most common password-related issues.
SSPR has the following key capabilities:
- Self-service allows end users to reset their expired or non-expired passwords without contacting an administrator or helpdesk for support.
- Password Writeback allows management of on-premises passwords and resolution of account lockout though the cloud.
- Password management activity reports give administrators insight into password reset and registration activity occurring in their organization.
This deployment guide shows you how to plan and then test an SSPR roll-out.
To quickly see SSPR in action and then come back to understand additional deployment considerations:
Learn about SSPR
Learn more about SSPR. See How it works: Azure AD self-service password reset.
The key benefits of enabling SSPR are:
Manage cost. SSPR reduces IT support costs by enabling users to reset passwords on their own. It also reduces the cost of time lost due to lost passwords and lockouts.
Intuitive user experience. It provides an intuitive one-time user registration process that allows users to reset passwords and unblock accounts on-demand from any device or location. SSPR allows users to get back to work faster and be more productive.
Flexibility and security. SSPR enables enterprises to access the security and flexibility that a cloud platform provides. Administrators can change settings to accommodate new security requirements and roll these changes out to users without disrupting their sign-in.
Robust auditing and usage tracking. An organization can ensure that the business systems remain secure while its users reset their own passwords. Robust audit logs include information of each step of the password reset process. These logs are available from an API and enable the user to import the data into a Security Incident and Event Monitoring (SIEM) system of choice.
Azure Active Directory is licensed per-user meaning each user requires an appropriate license for the features they use. We recommend group-based licensing for SSPR.
To compare editions and features and enable group or user-based licensing, see Licensing requirements for Azure AD self-service password reset.
For more information about pricing, see Azure Active Directory pricing.
A working Azure AD tenant with at least a trial license enabled. If needed, create one for free.
An account with Global Administrator privileges.
The following example describes the password reset solution architecture for common hybrid environments.
Description of workflow
To reset the password, users go to the password reset portal. They must verify the previously registered authentication method or methods to prove their identity. If they successfully reset the password, they begin the reset process.
For cloud-only users, SSPR stores the new password in Azure AD.
For hybrid users, SSPR writes back the password to the on-prem Active Directory via the Azure AD Connect service.
Note: For users who have Password hash synchronization (PHS) disabled, SSPR stores the passwords in the on-prem Active Directory only.
You can help users register quickly by deploying SSPR alongside another popular application or service in the organization. This action will generate a large volume of sign-ins and will drive registration.
Before deploying SSPR, you may opt to determine the number and the average cost of each password reset call. You can use this data post deployment to show the value SSPR is bringing to the organization.
Enable combined registration for SSPR and MFA
Microsoft recommends that organizations enable the combined registration experience for SSPR and multi-factor authentication. When you enable this combined registration experience, users need only select their registration information once to enable both features.
The combined registration experience does not require organizations to enable both SSPR and Azure AD Multi-Factor Authentication. Combined registration provides organizations a better user experience. For more information, see Combined security information registration
Plan the deployment project
Consider your organizational needs while you determine the strategy for this deployment in your environment.
Engage the right stakeholders
When technology projects fail, they typically do so due to mismatched expectations on impact, outcomes, and responsibilities. To avoid these pitfalls, ensure that you are engaging the right stakeholders and that stakeholder roles in the project are well understood by documenting the stakeholders and their project input and accountabilities.
Required administrator roles
|Business Role/Persona||Azure AD Role (if necessary)|
|Level 1 helpdesk||Password administrator|
|Level 2 helpdesk||User administrator|
|SSPR administrator||Global administrator|
Communication is critical to the success of any new service. You should proactively communicate with your users how their experience will change, when it will change, and how to gain support if they experience issues. Review the Self-service password reset rollout materials on the Microsoft download center for ideas on how to plan your end-user communication strategy.
Plan a pilot
We recommend that the initial configuration of SSPR is in a test environment. Start with a pilot group by enabling SSPR for a subset of users in your organization. See Best practices for a pilot.
To create a group, see how to create a group and add members in Azure Active Directory.
The following settings are required to enable SSPR along with recommended values.
|SSPR Properties||Self-service password reset enabled||Selected group for pilot / All for production|
|Authentication methods||Authentication methods required to register||Always 1 more than required for reset|
|Authentication methods required to reset||One or two|
|Registration||Require users to register when signing in||Yes|
|Number of days before users are asked to reconfirm their authentication information||90 – 180 days|
|Notifications||Notify users on password resets||Yes|
|Notify all admins when other admins reset their password||Yes|
|Customization||Customize helpdesk link||Yes|
|Custom helpdesk email or URL||Support site or email address|
|On-premises integration||Write back passwords to on-premises AD||Yes|
|Allow users to unlock account without resetting password||Yes|
When enabling SSPR, choose an appropriate security group in the pilot environment.
- To enforce SSPR registration for everyone, we recommend using the All option.
- Otherwise, select the appropriate Azure AD or AD security group.
When SSPR is enabled, users can only reset their password if they have data present in the authentication methods that the administrator has enabled. Methods include phone, Authenticator app notification, security questions, etc. For more information, see What are authentication methods?.
We recommend the following authentication method settings:
Set the Authentication methods required to register to at least one more than the number required to reset. Allowing multiple authentications gives users flexibility when they need to reset.
Set Number of methods required to reset to a level appropriate to your organization. One requires the least friction, while two may increase your security posture.
Note: The user must have the authentication methods configured in the Password policies and restrictions in Azure Active Directory.
Set Require users to register when signing in to Yes. This setting requires users to register when signing in, ensuring that all users are protected.
Set Number of days before users is asked to reconfirm their authentication information to between 90 and 180 days, unless your organization has a business need for a shorter time frame.
Configure both the Notify users on password resets and the Notify all admins when other admins reset their password to Yes. Selecting Yes on both increases security by ensuring that users are aware when their password is reset. It also ensures that all admins are aware when an admin changes a password. If users or admins receive a notification and they haven't initiated the change, they can immediately report a potential security issue.
It's critical to customize the helpdesk email or URL to ensure users who experience problems can get help immediately. Set this option to a common helpdesk email address or web page that your users are familiar with.
For more information, see Customize the Azure AD functionality for self-service password reset.
Password Writeback is enabled with Azure AD Connect and writes password resets in the cloud back to an existing on-premises directory in real time. For more information, see What is Password Writeback?
We recommend the following settings:
- Ensure that Write back passwords to on-premises AD is set to Yes.
- Set the Allow users to unlock account without resetting password to Yes.
By default, Azure AD unlocks accounts when it performs a password reset.
Administrator password setting
Administrator accounts have elevated permissions. The on-premises enterprise or domain administrators can't reset their passwords through SSPR. On-premises admin accounts have the following restrictions:
- can only change their password in their on-prem environment.
- can never use the secret questions and answers as a method to reset their password.
We recommend that you don't sync your on-prem Active Directory admin accounts with Azure AD.
Environments with multiple identity management systems
Some environments have multiple identity management systems. On-premises identity managers like Oracle AM and SiteMinder, require synchronization with AD for passwords. You can do this using a tool like the Password Change Notification Service (PCNS) with Microsoft Identity Manager (MIM). To find information on this more complex scenario, see the article Deploy the MIM Password Change Notification Service on a domain controller.
Plan Testing and Support
At each stage of your deployment from initial pilot groups through organization-wide, ensure that results are as expected.
To ensure that your deployment works as expected, plan a set of test cases to validate the implementation. To assess the test cases, you need a non-administrator test user with a password. If you need to create a user, see Add new users to Azure Active Directory.
The following table includes useful test scenarios you can use to document your organizations expected results based on your policies.
|Business case||Expected results|
|SSPR portal is accessible from within the corporate network||Determined by your organization|
|SSPR portal is accessible from outside the corporate network||Determined by your organization|
|Reset user password from browser when user is not enabled for password reset||User is not able to access the password reset flow|
|Reset user password from browser when user has not registered for password reset||User is not able to access the password reset flow|
|User signs in when enforced to do password reset registration||Prompts the user to register security information|
|User signs in when password reset registration is complete||Prompts the user to register security information|
|SSPR portal is accessible when the user does not have a license||Is accessible|
|Reset user password from Windows 10 Azure AD joined or hybrid Azure AD joined device lock screen||User can reset password|
|SSPR registration and usage data are available to administrators in near real time||Is available via audit logs|
You can also refer to Complete out an Azure AD self-service password reset pilot roll. In this tutorial, you will enable a pilot roll out of SSPR in your organization and test using a non-administrator account.
While SSPR does not typically create user issues, it is important to prepare support staff to deal with issues that may arise. While an administrator can reset the password for end users through the Azure AD portal, it is better to help resolve the issue via a self-service support process.
To enable your support team's success, you can create a FAQ based on questions you receive from your users. Here are a few examples:
|User doesn't have any registered authentication methods available||A user is trying to reset their password but doesn't have any of the authentication methods that they registered available (Example: they left their cell phone at home and can't access email)|
|User isn't receiving a text or call on their office or cell phone||A user is trying to verify their identity via text or call but isn't receiving a text/call.|
|User can't access the password reset portal||A user wants to reset their password but isn't enabled for password reset and can't access the page to update passwords.|
|User can't set a new password||A user completes verification during the password reset flow but can't set a new password.|
|User doesn't see a Reset Password link on a Windows 10 device||A user is trying to reset password from the Windows 10 lock screen, but the device is either not joined to Azure AD, or the Intune device policy isn't enabled|
To roll back the deployment:
for a single user, remove the user from the security group
for a group, remove the group from SSPR configuration
For everyone, disable SSPR for the Azure AD tenant
Before deploying, ensure that you have done the following:
Created and begun executing your communication plan.
Determined the appropriate configuration settings.
Identified the users and groups for the pilot and production environments.
Determined configuration settings for registration and self-service.
Configured password writeback if you have a hybrid environment.
You're now ready to deploy SSPR!
See Enable self-service password reset for complete step-by-step directions on configuring the following areas.
Enable SSPR in Windows
For machines running Windows 7, 8, 8.1, and 10 you can enable users to reset their password at the Windows sign in screen
Azure AD can provide additional information on your SSPR performance through audits and reports.
Password management activity reports
You can use pre-built reports on Azure portal to measure the SSPR performance. If you're appropriately licensed, you can also create custom queries. For more information, see Reporting options for Azure AD password management
You must be a global administrator, and you must opt-in for this data to be gathered for your organization. To opt in, you must visit the Reporting tab or the audit logs on the Azure Portal at least once. Until then, the data doesn't collect for your organization.
Audit logs for registration and password reset are available for 30 days. If security auditing within your corporation requires longer retention, the logs need to be exported and consumed into a SIEM tool such as Azure Sentinel, Splunk, or ArcSight.
Authentication methods- Usage and Insights
Usage and insights enable you to understand how authentication methods for features like Azure AD MFA and SSPR are working in your organization. This reporting capability provides your organization with the means to understand what methods register and how to use them.
To get started deploying SSPR, see Enable Azure AD self-service password reset