About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
When the text message or voice call carrying your Microsoft Entra multifactor authentication (MFA) code does not arrive, you cannot finish signing in to Microsoft 365, Azure or Intune. Choose another verification method on the sign-in page if you registered one. If you did not, ask another global administrator to check your phone numbers and whether your account is blocked.
The code itself is not the fault. The cause is the number on file, the way the carrier or handset treats the message or call, a rate limit, or a block on the account. Work through them in that order, and record the state of the account before changing it.
What the error means
There is no error code to search for. The sign-in page waits for a text or call that never comes. Microsoft's troubleshooting page describes the scenario as a global administrator with Microsoft Entra MFA enabled who does not receive the text message or voice call containing the verification code, and so cannot sign in to a work or school account such as Office 365, Azure or Microsoft Intune.
A text message carries a verification code that the user types into the sign-in page. A phone call is automated: the user answers and is prompted to press # on the keypad. The phone-options page says text messages can be sent over SMS, Rich Communication Services (RCS) or WhatsApp, and that WhatsApp is used only if the user has it and has internet connectivity; otherwise the user receives SMS codes.
Microsoft states several limits that explain missing messages. It "doesn't guarantee consistent text message or voice-based Microsoft Entra multifactor authentication prompt delivery by the same number". It may add or remove short codes at any time. It does not support short codes for countries or regions other than the United States and Canada. Phone call verification "isn't available for Microsoft Entra tenants with trial subscriptions", and elsewhere the same page says tenants on a free or trial subscription may receive a text message or voice call because of delivery optimisations. Read the current page for your own subscription type.
Microsoft also recommends that users move away from text messages and voice calls to methods such as Microsoft Authenticator.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Wrong number, wrong country code, or work number confused with personal | Nothing arrives, or arrives on the wrong phone | The registered numbers on the user object; format must be +CountryCode PhoneNumber with a space, such as +1 4251234567 |
| Blocked caller ID or blocked numbers on the handset | Call or text never rings | Blocked-number list on the phone; spam-filter settings; Microsoft's default caller numbers are for the United States only |
| Call forwarded to voicemail, handset off or no signal | Call goes to voicemail, or times out | Test from the same location; poor signal is on Microsoft's list |
| Text platforms not set up on the device | No SMS, RCS or WhatsApp message | Device messaging settings |
| Rate limiting | "You've hit our limit on verification calls" or "You've hit our limit on text verification codes" | The wording on the sign-in page |
| Verification blocked or limited | "Sorry, we're having trouble verifying your account" | The wording on the sign-in page |
| Country code blocked for voice MFA | No voice call to a number in that country | Whether the administrator opted in to that country code |
| User account blocked | Sign-in fails after other causes are cleared | Block sign in on the user's profile, and risk state |
| Telecom provider faults | Missing keypad tones, blocked caller ID on several handsets, or no text across several handsets | Several attempts on more than one handset |
Prove the cause before changing anything
All of these only read.
- Ask the user which wording they see on the sign-in page, and what time they tried. Rate-limit wording points to the limit, not to the phone.
- Ask another global administrator to open the user's profile and read the registered numbers. Compare the format with
+CountryCode PhoneNumber. - On the handset, check blocked numbers, spam filters, forwarding and signal. For the United States, Microsoft's MFA settings page lists default caller numbers: +1 (855) 330-8653, +1 (855) 336-2194 and +1 (855) 341-5605, and says users with spam filters should exclude them. The page's table of numbers for other countries does not list Australia as of its date; read the current page for your country.
- Check whether the user pressed 0 followed by # during a call. The call prompt says "If you are not trying to sign in, press 0 and #". Microsoft says users who report an MFA prompt as suspicious are set to High User Risk, and an administrator can then use risk-based policies to limit their access.
- Check Block sign in on the user's profile in the Azure portal, under Microsoft Entra ID > Users. Write down its current value.
Example (illustrative): Lee at Contoso (contoso.com.au) is a global administrator who changed handsets. His mobile number in the directory reads 0400 000 000, without a country code. No text arrives. Another global administrator changes the number to +61 400000000, and Lee uses the Other verification options link to sign in with Authenticator while the change takes effect.
Fix
Use the lowest-impact step that fits the cause. The steps run from the user's own actions to changes an administrator makes on the account, so stop at the first one that gets the user signed in. A user who is locked out of the only account that can change settings needs a second global administrator for steps 2 and 6, which is why Microsoft's troubleshooting page tells the user to ask one.
- Select Other verification options on the sign-in page and try another method. Make sure the phone numbers in the account settings are correct.
- Save first: copy the current numbers into a note. Risk: editing a user's phone number changes how they prove who they are. Ask a different global administrator to correct the numbers. To undo it: type the old numbers back.
- For rate limits, wait a few minutes and sign in again, or use the Authenticator app or a verification code. Microsoft says the limit does not apply to Authenticator or verification codes.
- For a suspected telecom fault, Microsoft's voice call authentication page asks that the user try the method at least five times within five minutes and keep the user's information ready when contacting Microsoft support.
- For blocked voice countries, Microsoft says the administrator must opt in for those country codes, or the user can use Authenticator. Microsoft's pages give no portal path for the opt-in, so use Authenticator, or ask Microsoft support to make the opt-in with you. Do not look for the setting and change it on your own.
- First ask who blocked this account, and why. If the answer is a suspected compromise, stop and involve whoever handles security. If Block sign in is on and the block was a mistake, a global administrator can switch it off. Disruptive step: unblocking an account. It lets someone sign in who was deliberately stopped, including after a suspected compromise. Save first: record who blocked it and why, and the value you read in the previous section. Back-out: switch Block sign in on again. Microsoft's MFA settings page says the legacy Block/unblock users feature was removed on 1 March 2025 and replaced by Report suspicious activity, and the troubleshooting page still names Block sign in on the user's profile. If the portal in front of you differs, follow what it shows.
For tenants with Office 365 but no Microsoft Entra MFA or Microsoft Entra ID P1 or P2 subscription, Microsoft's troubleshooting page says to contact Office 365 Support.
Confirm the fix
- Ask the user to sign in using the original method, from the same phone, and note the time the text or call arrives.
- Check that the sign-in log shows a successful MFA step.
- If you changed a number, test with a second handset or a second method so the user is not dependent on one.
- Make sure the user has registered at least one method that does not depend on the carrier, such as Authenticator.
What to watch afterwards
- Repeat reports on the same carrier or country, which point to routing or telecom faults.
- Users who changed handsets or numbers without telling IT.
- Accounts that reported suspicious activity, which Microsoft sets to High User Risk.
- Custom voice greetings. Microsoft's MFA settings page, dated 2026-02-27, says custom voice messages "will be retired on February 28, 2026". That date has passed, so all voice call greetings should now use Microsoft's standard recordings; confirm on a test call before you tell users what they will hear.
Read next
Related articles you may want next.
- HostingKeeping email notifications and MFA working when the application server movesKeep email notifications and staff sign-in working through a hosting move. Check mail relays, registered application addresses and authentication dependencies with controlled tests.Read article
- CloudEntra ID Conditional Access: tenant lockout, break-glass accounts and how to test policy safelyHow Conditional Access locks administrators out, how to build emergency accounts that work under mandatory MFA, and a safe order for testing policy.Read article
- TroubleshootingSelf-service password reset fails with SSPR_0029 or SSPR_0030: fixing password writeback on Microsoft Entra ConnectSSPR_0029 or SSPR_0030 on a self-service password reset: read the Entra Connect events, find the writeback cause and fix it with a back-out.Read article
Risks and limits
- No commands are given. The portal steps have not been run or lab-tested.
- Microsoft's pages disagree in part about blocks and trial subscriptions, as noted above; the portal in front of you decides.
- Phone call and text delivery depend on carriers that Microsoft and you do not control.
- Do not remove the only working method from an administrator account before another is tested.
Sources
- You don't receive a text or voice call that contains the verification code for Microsoft Entra multifactor authentication — Microsoft Learn, page dated 2026-01-15, accessed 20 November 2026
- Authentication methods in Microsoft Entra ID - Voice call — Microsoft Learn, page dated 2025-10-26, accessed 20 November 2026
- Configure Microsoft Entra multifactor authentication settings — Microsoft Learn, page dated 2026-02-27, accessed 20 November 2026
This article was originally published on .