Entra ID: Expansion of WhatsApp as an MFA one-time passcode delivery channel
From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Rollout
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
What the notice says
Microsoft’s text, safely structuredIn late 2023, Microsoft Entra started leveraging WhatsApp as an alternate channel to deliver multifactor authentication (MFA) one-time passcodes (OTPs) to users in India and Indonesia. We saw improved deliverability, completion rates, and satisfaction when leveraging the channel in both countries. The channel was temporarily disabled in India in early 2024. Starting early December 2024, we will be re-enabling the channel in India and expanding its use to additional countries.
When this will happen
Starting December 2024, users in India and other countries may start receiving MFA text messages via WhatsApp. Only users that are enabled to receive MFA text messages as an authentication method and already have WhatsApp on their phone will get this experience. If a user with WhatsApp on their device is unreachable or doesn’t have internet connectivity, they will quickly fall back to the regular SMS channel. In addition, users receiving OTPs via WhatsApp for the first time will be notified of the change in behavior via SMS text message.
The sender agent in WhatsApp where users will see the OTPs will be branded as Microsoft with a verified checkmark.
How this will affect your organization
If you’re a Microsoft Entra workforce customer and currently leverage the text-message authentication method, we recommend you notify your helpdesk about this upcoming change.
Additionally, if you don’t want your users to receive MFA text messages through WhatsApp, you may disable text messages as an authentication method in your organization. Please note that we highly encourage organizations move to using more modern, secure methods like Microsoft Authenticator and passkeys in favor of telecom and messaging app methods.
This feature update is available by default.
For more information, see Phone authentication methods in Entra ID.
What you need to do to prepare
This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.
What changed
Between archive captures, newest firstThe archive supplies one version of this notice.
Learn more
Links from the notice and their documentation checks- disableChecked 15 Nov 2026
- encourageNot read yet
- Phone authentication methods in Entra IDNot read yet
- Notice image
Related public changes
- Official documentation · 12 Oct 2026Authentication methods policy Shared reference: https://learn.microsoft.com/entra/identity/authentication/concept-authentication-methods-manage
- Public source · 13 Nov 2026MC1551151: Microsoft Entra ID: Risk-based anti-bot verification (CAPTCHA) for SMS and voice multi-factor authentication Microsoft 365 Message Center Archive by Merill Fernando
- Public source · 11 Nov 2026MC1509782: Microsoft Entra ID: Updates to SMS and voice verification experiences in MFA flows Microsoft 365 Message Center Archive by Merill Fernando
- Public source · 6 Nov 2026MC1325414: (Updated) Microsoft Entra ID SSPR will require registered authentication methods starting November 9, 2026 Microsoft 365 Message Center Archive by Merill Fernando
- Official documentation · 30 Oct 2026Combined security information registration
- Public source · 27 Oct 2026MC1450134: (Updated) Microsoft Entra: Windows Hello for Business and macOS Platform SSO as standalone MFA factors Microsoft 365 Message Center Archive by Merill Fernando
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.
- 2 linked pages have not been read yet.