Reset User MFA Factors
Reset a user's multi-factor authentication methods in Microsoft Entra ID
Resets a user's multi-factor authentication (MFA) methods in Microsoft Entra ID by removing all of their registered authentication methods. The user will need to re-register MFA the next time a sign-in challenges them for it. This is typically used when a user has lost access to their MFA devices or when troubleshooting MFA issues.
What this tool does
When executed, the tool:
- Looks up the user in Entra by email address.
- Removes all of the user's registered authentication methods — Microsoft Authenticator, phone / SMS, software and hardware OATH tokens, FIDO2 security keys, Windows Hello for Business, email, temporary access pass, and platform credentials.
- Returns a summary of which methods were removed (and flags any that could not be removed, since a leftover method can still satisfy MFA).
The password method cannot be removed through this API and is always left intact. By default the tool only operates on the ticket requestor; this can be changed with the Restrict to Requestor Only setting so IT staff can reset MFA on behalf of other users.
What the user sees
The next time the user signs in, Microsoft walks them through registering MFA again. When they finish, Microsoft shows a Set up complete confirmation listing the methods they can now use to verify their identity (for example, Phone with the registered number and Microsoft Authenticator), with a link to view, add, or edit methods in their account security settings.
Prerequisites
This tool calls Microsoft Graph with an Entra app registration using application (client credentials) permissions. The app registration must have:
| Requirement | Value |
|---|---|
| API permission | UserAuthenticationMethod.ReadWrite.All (application, with admin consent) |
| API permission | User.Read.All (application, to look up the user by email) |
| Directory role | Authentication Administrator assigned to the app's service principal |
Setup
You have two options for providing credentials. Adding the permissions to your existing Entra app is preferred — it reuses the connection you already configured under your Identity Provider integration.
Option A — Add permissions to your existing Entra app (recommended)
If you already connected Microsoft Entra ID as an Identity Provider, extend that same app registration:
Add the API permissions
- In the Azure Portal, open Microsoft Entra ID > App registrations and select your Risotto app registration.
- Go to API permissions > Add a permission > Microsoft Graph > Application permissions.
- Add
UserAuthenticationMethod.ReadWrite.Alland (if not already present)User.Read.All. - Click Grant admin consent for [Your Organization] and confirm.
Assign the Authentication Administrator role
- In Microsoft Entra ID, go to Roles and administrators. 2. Open the Authentication Administrator role and click Add assignments. 3. Search for your app registration by name and assign it.
Leave the tool credentials blank in Risotto
When the tool's credential fields (Entra Tenant ID (Optional), Entra Client ID (Optional), Entra Client Secret (Optional)) are left empty, Risotto automatically falls back to your organization's Entra credentials. No further configuration is needed.
Option B — Create a dedicated Entra app
If you prefer to isolate this tool with its own credentials and only the permissions it needs:
Register an application
- In the Azure Portal, open Microsoft Entra ID > App registrations > New registration.
- Name it (e.g.
Risotto Entra MFA Reset), choose Accounts in this organizational directory only, and click Register. - Copy the Application (client) ID and Directory (tenant) ID.
Add the API permissions
- Go to API permissions > Add a permission > Microsoft Graph > Application permissions.
- Add
UserAuthenticationMethod.ReadWrite.AllandUser.Read.All. - Click Grant admin consent for [Your Organization] and confirm.
Assign the Authentication Administrator role
- In Microsoft Entra ID > Roles and administrators, open the Authentication Administrator role.
- Click Add assignments, search for the new app registration, and assign it.
Create a client secret
- Go to Certificates & secrets > New client secret.
- Add a description and expiration, then click Add.
- Copy the secret value immediately — it is only shown once.
Configure the tool in Risotto
Select Tools in the sidebar and select Entra in the Tool groups list. Open the tool and click Edit. In Tool Configuration, fill in:
Field Value Entra Tenant ID (Optional) Directory (tenant) ID Entra Client ID (Optional) Application (client) ID Entra Client Secret (Optional) The secret value you copied Click Save.
Tool options
When using this tool in a runbook, you can configure:
- Restrict to Requestor Only (default: on) — when enabled, the tool can only reset the ticket requestor's MFA. Disable to allow resets on behalf of other users.
For an approval step before the reset runs, use the standard tool approval setting on the tool itself — approval gating is handled at the platform level rather than per-tool options.
Troubleshooting
- "Microsoft Graph rejected all deletion(s)" or
403 "Request Authorization failed"— the app registration is most likely missing theUserAuthenticationMethod.ReadWrite.Allpermission, admin consent, or the directory role. Re-check the setup steps above, and remember the role must be on the app's service principal with an active assignment. - Resets work for most users but fail for one specific user — check whether that user holds an admin role. Resetting an admin's MFA requires Privileged Authentication Administrator; plain Authentication Administrator returns the same 403. Quick isolation test: run the reset on a non-admin user — if that succeeds and the admin fails, it's the role tier.
- "No resettable MFA methods were found" — the user had no removable MFA registered (for example, only a password). Nothing was changed.
- "could not be removed and may still satisfy MFA" — some methods were removed but at least one was rejected. Review the listed methods, since a leftover method can keep MFA satisfied.
- "User not found in Microsoft Entra ID" — verify the email matches the user's
mailoruserPrincipalNamein Entra.
Related
Something wrong or missing? Report an issue · View as Markdown