Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Entra ID: Risk-based anti-bot verification (CAPTCHA) for SMS and voice multi-factor authentication

Returned by 2 reference tenants · Corroborated by Microsoft 365 Message Center Archive by Merill Fernando

Microsoft category: Prevent or fix issues. Read the notice and linked documentation for any recommendations or required actions; whether your tenant is affected is not known here.

What the notice says

Microsoft’s text, safely structured

What and why

Microsoft Entra ID is adding safeguards to protect telephony-based multifactor authentication (MFA) from automated fraudulent activity. Some users who use SMS or voice for MFA may be asked to complete a risk-based anti-bot verification step (CAPTCHA) before Microsoft sends an SMS verification code or initiates a verification call.

This change is separate from the planned retirement of SMS and voice authentication and does not affect the retirement timeline.

Rollout schedule

  • Worldwide: Beginning in mid-November 2026.

Impact on your organization

Who is affected

  • Users who use SMS or voice for Microsoft Entra ID multifactor authentication

Platforms and services

  • Microsoft Entra ID
  • SMS and voice authentication methods

What will happen

  • Some users may be prompted to complete a risk-based anti-bot verification step (CAPTCHA) before Microsoft sends an SMS verification code or initiates a verification call.
  • The verification step will appear only for authentication attempts that meet sufficiently high-risk thresholds.
  • Users with restrictive network or firewall settings may be unable to complete SMS or voice MFA if the verification experience cannot load.

Action required and recommendations

We recommend that administrators take the following actions:

  • Prepare your help desk and notify users that some SMS and voice MFA attempts may require an additional CAPTCHA verification step.
  • Review the risk-based anti-bot verification documentation for network-readiness guidance. If your organization uses restrictive firewalls, proxies, or web filtering, ensure that the required resources can load during authentication.
  • Continue moving users to phishing-resistant authentication methods, such as passkeys, where possible.

Compliance considerations

No compliance considerations identified. Review as appropriate for your organization.

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 13 Nov 2026. Later changes will show here.

These are the archive's capture times. They are separate from the versions returned by our reference tenants.

Read the archive's current copy

What and why Microsoft Entra ID is adding safeguards to protect telephony-based multifactor authentication (MFA) from automated fraudulent activity. Some users who use SMS or voice for MFA may be asked to complete a risk-based anti-bot verification step (CAPTCHA) before Microsoft sends an SMS verification code or initiates a verification call. This change is separate from the planned retirement of SMS and voice authentication and does not affect the retirement timeline. Rollout schedule Worldwide: Beginning in mid-November 2026. Impact on your organization Who is affected Users who use SMS or voice for Microsoft Entra ID multifactor authentication Platforms and services Microsoft Entra ID SMS and voice authentication methods What will happen Some users may be prompted to complete a risk-based anti-bot verification step (CAPTCHA) before Microsoft sends an SMS verification code or initiates a verification call. The verification step will appear only for authentication attempts that meet sufficiently high-risk thresholds. Users with restrictive network or firewall settings may be unable to complete SMS or voice MFA if the verification experience cannot load. Action required and recommendations We recommend that administrators take the following actions: Prepare your help desk and notify users that some SMS and voice MFA attempts may require an additional CAPTCHA verification step. Review the risk-based anti-bot verification documentation for network-readiness guidance. If your organization uses restrictive firewalls, proxies, or web filtering, ensure that the required resources can load during authentication. Continue moving users to phishing-resistant authentication methods, such as passkeys, where possible. Learn more Passkeys by default and retirement of Microsoft-provided SMS and voice authentication - Microsoft Entra ID | Microsoft Learn Risk-based anti-bot verification (CAPTCHA) for telephony-based sign-in - Microsoft Entra ID | Microsoft Learn Understanding telephony fraud risk for Microsoft Entra multifactor authentication - Microsoft Entra ID | Microsoft Learn Compliance considerations No compliance considerations identified. Review as appropriate for your organization.

  1. Microsoft Entra ID: Risk-based anti-bot verification (CAPTCHA) for SMS and voice multi-factor authentication Action date: Not supplied

Learn more

Links from the notice and their documentation checks

This site links to Microsoft's pages instead of copying them. Installations inside an organization can keep a copy for comparison.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • Some history or links were left out of the website export to keep it within its size limits.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 13 Nov 10:02 UTC · 274 of 275 readable · 272 fully read · documentation 469/469 current