MC1551151: Microsoft Entra ID Adds Risk-Based CAPTCHA to SMS and Voice Multifactor Authentication

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
59
0 25 50 75 100
HIGH IMPACT • REVIEW RECOMMENDED
Recommended Action:
Review the update and plan any required actions before rollout.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Tenant AdminsMicrosoft 365 AdminsSecurity TeamsCompliance TeamsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
The update confirms rollout of a risk-based CAPTCHA for SMS and voice MFA to counter automated fraud. Admins need to check firewall and proxy configurations to ensure the CAPTCHA service can load, and prepare help desks for user enquiries. End users will only occasionally encounter the CAPTCHA when risk is high, giving moderate user impact. Effort involves preparation, communication and verifying network readiness, but no major reconfiguration.
65
🛡️ Admin Impact
45
👥 User Impact
60
⚡ Urgency
55
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Microsoft Entra ID is adding CAPTCHA checks for risky SMS and voice MFA attempts to reduce automated fraud. Worth checking your network readiness and updating user guidance accordingly.
👥

END USERS

Some users may be asked to complete a CAPTCHA before receiving MFA codes or calls.
🛡️

IT ADMINS

Review network settings, ensure CAPTCHA can load, and notify users and support teams about this new step.
📅

ROLLOUT TIMELINE

Start:
Mid-November 2026

📢 Official Microsoft Message Center Announcement


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

Updated November 19, 2026: We have updated the content. Thank you for your patience. 

[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.

If your organization has restrictive network or firewall settings, make sure to follow the guidance covered in this documentation (Risk-based anti-bot verification (CAPTCHA) for telephony-based sign-in – Microsoft Entra ID | Microsoft Learn) to prepare for this change.

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

[Compliance considerations]

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

Source: Microsoft Message Center • Analysed by MWPro

<<< [MC1551151] Archive
Tooltip: View earlier revisions of this post