SSPR Not Working in Entra ID? The Proven SSPR_0014 Fix

By Ahmet Tolga KAYA 8 min read
SSPR Not Working in Entra ID? The Proven SSPR_0014 Fix

SSPR not working for users who could reset their password last month has one new cause that every Microsoft Entra ID admin should rule out first. Microsoft is changing what self-service password reset accepts: a phone number or alternate email that only sits in the directory will stop being enough, and the method has to be explicitly registered. This guide shows you how to read the error, find every affected account with PowerShell, register the right methods, and prove the fix worked.

Why SSPR Not Working Tickets May Be Appearing Now

Message center notice MC1325414 says only explicitly registered authentication methods will be accepted for SSPR verification. Directory attributes such as mobilePhone, businessPhone and otherMails stop being valid unless they were registered. Until now, an account prepopulated by Entra Connect or a script could pass verification even if the person had never visited the Security info page.

Microsoft says about 86% of SSPR verifications already use registered methods, so most users will notice nothing. The rest are the problem: people silently relying on directory data, who find SSPR not working at the moment they need it most. According to the notice, all users are in scope, including administrators, across the public cloud and US government clouds. Those without a registered method cannot complete a reset and are told to register or contact an administrator.

The SSPR November 2026 Dates Do Not Agree

Be careful with any single date you read, because Microsoft’s own sources conflict:

  • The MC1325414 summary says the requirement starts on November 9, 2026.
  • The rollout schedule in the same notice says enforcement begins on November 7, 2026, with general availability from early to mid-November.
  • The Microsoft Learn page on prepopulating contact data, updated November 5, 2026, says the change starts in February 2027.

I could not find a Microsoft statement that resolves this, so check the message center in your own tenant. The practical answer is the same either way: if your SSPR November 2026 readiness work is not finished, finish it now. Registering methods is safe under every one of those dates, and it keeps SSPR not working from turning into a helpdesk incident.

Read the Error First: SSPR_0014 and Its Lookalikes

Not every case of SSPR not working has the same cause, and the code tells you where to look. The closest match for missing data is SSPR_0014, whose technical text reads “Additional security info is needed to reset your password.” The SSPR troubleshooting article documents it as the state where necessary information is missing from the account.

SSPR not working illustration showing the SSPR_0014 additional security info error page

MC1325414 does not name a specific error code for the new behavior, so treat SSPR_0014 as the likely symptom rather than a confirmed one. These other documented codes point somewhere else entirely, and registering methods will not clear them:

  • SSPR_0013: the user is not a member of a group enabled for password reset.
  • SSPR_0012: the organization lacks the required licenses.
  • SSPR_0011: no password reset policy has been defined.
  • SSPR_0009: password reset has not been enabled by the administrator.

If you see one of these, SSPR not working has a policy or licensing cause, not a registration one. The same article also covers a policy mismatch: a user with one piece of contact data when the policy requires two verification methods.

Step 1: Find Every User With SSPR Not Working Risk

To see who could hit SSPR not working next, open the Microsoft Entra admin center, go to Authentication methods > User registration details, and filter SSPR Capable to Not Capable. For anything you want to export or repeat, use Get-MgReportAuthenticationMethodUserRegistrationDetail, which needs the AuditLog.Read.All permission and a role such as Reports Reader. If this is your first time with the module, start with our guide to installing the Microsoft Graph PowerShell module.

Connect-MgGraph -Scopes "AuditLog.Read.All"

$gap = Get-MgReportAuthenticationMethodUserRegistrationDetail -All `
    -Filter "isSsprEnabled eq true and isSsprRegistered eq false"

$gap | Select-Object UserPrincipalName, IsAdmin, UserType,
    @{n="Methods"; e={$_.MethodsRegistered -join ","}} |
    Export-Csv .\sspr-gap.csv -NoTypeInformation

$gap.CountCode language: PHP (php)

The filter is deliberate. isSsprEnabled means policy allows the user to reset, and isSsprRegistered means they have registered the required number of methods. Together they return exactly the people who are allowed to use SSPR but are not ready for it. Sort the CSV by IsAdmin and handle privileged accounts first.

Two limits apply: the report data can lag by up to 36 hours, and disabled or soft-deleted users do not appear. To see which directory values a person may have been relying on, read them directly:

Connect-MgGraph -Scopes "User.Read.All"

Get-MgUser -UserId alex@contoso.com -Property mobilePhone,businessPhones,otherMails |
    Select-Object MobilePhone, BusinessPhones, OtherMailsCode language: CSS (css)

Step 2: Make Users Register Before the Next Reset

The cheapest fix for SSPR not working is getting users to register while they can still sign in. In the admin center, go to Entra ID > Password reset > Registration and set Require users to register when signing in to Yes. Users can dismiss the prompt, but it returns at each sign-in until they finish. Keep the reconfirmation setting above zero, because a value of 0 means users are never asked to confirm their details; the allowed range is 0 to 730 days.

SSPR not working fix flowchart: read the error, find unregistered users, register methods, verify

Point people to https://aka.ms/ssprsetup. Also check Entra ID > Password reset > Authentication methods for the Number of methods required to reset, since users can only reset with a method the administrator has enabled. A separate feature, the authentication methods registration campaign, is not a substitute here: it targets only one method at a time, either Microsoft Authenticator or passkeys, and passkeys alone do not satisfy SSPR.

Step 3: Fix Users Who Are Already Locked Out

Someone with SSPR not working and no way in cannot register anything, so an admin has to step in. Reset the password from Entra ID > Users, then add a method: select the user, open Authentication methods, and choose Add authentication method. This requires at least the Authentication Administrator role; Microsoft names Privileged Authentication Administrator for setting contact details on any account.

For a verified list of users, the same thing works from PowerShell:

Connect-MgGraph -Scopes "UserAuthenticationMethod.ReadWrite.All"

New-MgUserAuthenticationPhoneMethod -UserId alex@contoso.com `
    -PhoneType "mobile" -PhoneNumber "+1 5555551234"

New-MgUserAuthenticationEmailMethod -UserId [email protected] `
    -EmailAddress "[email protected]"Code language: CSS (css)

The phone format matters: use a plus sign, the country code, a space, then the number. A user can hold only one phone of each type and only one email method. To work through many accounts, prepare a CSV yourself with UserPrincipalName and RecoveryEmail columns, then run it with -WhatIf before you commit:

Import-Csv .\sspr-verified.csv | ForEach-Object {
    New-MgUserAuthenticationEmailMethod -UserId $_.UserPrincipalName `
        -EmailAddress $_.RecoveryEmail -WhatIf
}Code language: PHP (php)

Do not blindly copy directory values into registered methods. A stale or wrong number becomes a working password reset path into that account, which is the weakness this change is meant to remove. Confirm each value with the person first. Connection problems? See how to connect Microsoft Graph with PowerShell.

Step 4: Verify the SSPR Not Working Fix

Do not close an SSPR not working ticket on a successful registration alone. Check the account state, then run a real reset:

$upn = "[email protected]"

Get-MgReportAuthenticationMethodUserRegistrationDetail `
    -Filter "userPrincipalName eq '$upn'" |
    Select-Object IsSsprEnabled, IsSsprRegistered, IsSsprCapable, MethodsRegistered

Get-MgUserAuthenticationPhoneMethod -UserId $upn | Select-Object PhoneType, PhoneNumber
Get-MgUserAuthenticationEmailMethod -UserId $upn | Select-Object EmailAddressCode language: PHP (php)
SSPR not working fixed: illustration of PowerShell output showing IsSsprCapable True with sample data

You want IsSsprCapable to show True, though the report can take up to 36 hours to catch up. The method cmdlets read the authentication methods on the account directly instead of the report, and the write scope above covers them. Finally, have the user complete a reset at https://aka.ms/sspr. Only that proves the whole path works.

Pick Methods That Survive the 2027 Retirement

Do not solve this with phone numbers alone. MC1536049 retires Microsoft-provided SMS and voice for SSPR starting in February 2027, with a 50-day transition for each user group. Global Administrators and external users follow a later rollout that begins July 1, 2027. If you register only phones today, you could face another round of SSPR not working tickets within months.

Keep these rules in mind when you choose:

  • Email OTP remains a valid SSPR method and is simple to prepopulate.
  • Microsoft Authenticator and OATH tokens together count as a single method, and Authenticator cannot be the only option when just one method is required.
  • Passkeys alone do not satisfy SSPR, so passkey-only users still need a qualifying method.

Passwordless users have one more option. Allow password change after secure sign-in, under Entra ID > Authentication methods > Policies > Password, lets them change a cloud password from Security info. It needs Entra ID P1 or P2, applies to the whole tenant, and is rolling out through the end of November 2026. It is separate from SSPR and does not help anyone who cannot sign in.

Read more: How to Fix Entra Connect Permission-Issue Export Errors

Read more: How to Connect Microsoft Graph with PowerShell

Why is SSPR not working for users who had a phone number in the directory?

Microsoft is moving SSPR to explicitly registered authentication methods. Directory attributes such as mobilePhone, businessPhone and otherMails stop being valid for verification unless the method was registered.

What does SSPR_0014 mean?

SSPR_0014 reads “Additional security info is needed to reset your password.” It means necessary information is missing from the account. An admin can reset the password and add a method, and the user can then register their own details.

When does the SSPR registered methods change take effect?

Sources conflict. MC1325414 gives November 7 and November 9, 2026, while a Microsoft Learn page updated on November 5, 2026 says February 2027. Check the message center in your tenant and register methods now either way.

How do I find users without registered SSPR methods?

Use the User registration details report in the Entra admin center, or run Get-MgReportAuthenticationMethodUserRegistrationDetail with the filter isSsprEnabled eq true and isSsprRegistered eq false. Report data can lag by up to 36 hours.

Do passkeys count as a method for SSPR?

No. Microsoft states that passkeys alone do not satisfy SSPR requirements. Users also need a qualifying method such as email OTP, or Microsoft Authenticator combined with another method where the policy requires it.

References

Microsoft message center (mirror): MC1325414: SSPR will require registered authentication methods

Microsoft message center (mirror): MC1536049: SMS and voice retirement for SSPR

Microsoft Learn: Prepopulate contact information for SSPR

Microsoft Learn: Troubleshoot self-service password reset

Microsoft Learn: How self-service password reset works

Microsoft Learn: Enable self-service password reset

Microsoft Learn: Authentication methods activity report

Microsoft Learn: userRegistrationDetails resource type

Microsoft Learn: Get-MgReportAuthenticationMethodUserRegistrationDetail

Ahmet Tolga KAYA

Systems Engineer and Technical Writer focused on Windows, Microsoft technologies, infrastructure, cybersecurity, automation, and platform reliability.