Microsoft 365 tenant · Identity & authentication

Disable one-time passcodes in Microsoft Authenticator

When it fails: Microsoft Authenticator one-time passcodes are allowed. Users can type a six-digit code from Authenticator instead of answering a number-matched notification, and a phishing page can collect and replay that code.

CB-M365-AUTH-007lowactivemanualprofile hardened

Description

In the Authentication methods policy, Allow use of Microsoft Authenticator OTP is set to No. Users of Microsoft Authenticator then complete MFA with a number-matched push notification or an Authenticator passkey, never with a typed time-based code.

Third-party software OATH tokens and hardware OATH tokens are separate methods in the policy; keep them disabled unless a documented population needs them.

Rationale

A one-time code shows no context and has no binding to the sign-in page: a phishing proxy asks for it and replays it within its validity window. Push with number matching at least shows the application, location and a number from the real sign-in screen.

Impact

Users can no longer sign in when the phone has no network connection, since push needs one. The NPS extension relies on codes for some VPN scenarios; check those first. Users with a passkey in Authenticator are not affected.

Setting

LocationMicrosoft Entra admin center > Entra ID > Authentication methods > Policies > Microsoft Authenticator > Configure > Allow use of Microsoft Authenticator OTP
DefaultYes
RecommendedNo

Audit

  1. Sign in to the Microsoft Entra admin center (https://entra.microsoft.com) as at least a Global Reader.
  2. Browse to Entra ID > Authentication methods > Policies and select Microsoft Authenticator.
  3. On the Configure tab, read Allow use of Microsoft Authenticator OTP.
  4. Read-only alternative with Microsoft Graph PowerShell (scope Policy.Read.All): (Get-MgPolicyAuthenticationMethodPolicyAuthenticationMethodConfiguration -AuthenticationMethodConfigurationId MicrosoftAuthenticator).AdditionalProperties.isSoftwareOathEnabled
  5. Fail if the setting is Yes (isSoftwareOathEnabled is true).

Remediation

  1. Check the NPS extension and other code-based integrations, and move their users to push.
  2. Sign in to the Microsoft Entra admin center as at least an Authentication Policy Administrator.
  3. Browse to Entra ID > Authentication methods > Policies > Microsoft Authenticator > Configure.
  4. Set Allow use of Microsoft Authenticator OTP to No and select Save. Graph equivalent: PATCH /policies/authenticationMethodsPolicy/authenticationMethodConfigurations/MicrosoftAuthenticator with "isSoftwareOathEnabled": false (send the whole configuration back).

Rollback

Set Allow use of Microsoft Authenticator OTP back to Yes.

References

Mappings

FrameworkIDRelation
NIST SP 800-53 Rev. 55.1.1IA-5related
NIST SP 800-53 Rev. 55.1.1IA-2(8)related

How this control relates to the other framework's: equivalent, stricter, looser, partial or related.

Threats mitigated

  • related CB-M365-AUTH-006 Show application name and location in Microsoft Authenticator notifications
  • related CB-M365-AUTH-009 Complete the migration to the Authentication methods policy

People and lifecycle

Authors
Introduced inv0.1.0
Created, updated2026-10-24, 2026-10-24
Translationsfr