What you’re seeing
- The sign-in page says a request was sent to Microsoft Authenticator, but nothing appears on the phone.
- Prompts appear only after manually opening the Authenticator app.
- Notifications arrive minutes late, after the sign-in has already timed out.
- It works on Wi-Fi but not on mobile data, or the reverse.
Common causes
Every environment is different, but these are the causes our engineers find most often:
- The phone's notification permissions for Authenticator were turned off or restricted by battery-saving settings.
- The Authenticator registration is tied to an old phone or an earlier install of the app.
- Do Not Disturb, focus modes or work-profile settings silence the notifications.
- The phone's connection to Apple or Google push services is blocked by a network or restrictive firewall.
- The account has several authentication methods registered and the wrong default is being used.
Why it matters
If MFA prompts don't arrive, users can't sign into email, Teams or business apps, which halts their work. Frustrated staff push for weaker sign-in methods like SMS, or ask admins to disable MFA, which removes one of the strongest protections against account takeover. Repeated unexpected prompts can also mask MFA fatigue attacks if users get used to approving whatever eventually shows up.
How AskTechGurus fixes it
Skip the trial and error. A certified engineer works on your actual system, finds the root cause, and fixes it properly.
Tell us what’s happening
Submit a ticket in about two minutes. Paste the error, describe what changed, and pick your tier. No charge to submit.
A certified engineer diagnoses it
A vetted, US-based systems engineer claims your ticket, usually within minutes during business hours, and investigates over a secure remote session you can watch and end at any time.
Fixed and verified with you
The engineer resolves the root cause and confirms with you that it’s working. You don’t just get a workaround, and you get a plain-English summary of what was wrong.
Pay only when it’s resolved
Fixed price from $99, invoiced only after you approve the fix. If it isn’t resolved, you don’t pay.
Frequently asked questions
Is our MFA system down?
Rarely. When only some users are affected, the cause is almost always on the phone or its registration rather than the service itself.
Should we switch to text-message codes instead?
We don't recommend it as a long-term fix; text codes are easier to intercept. It's better to get the app working reliably.