A one-time passcode arrives on your Android phone as a text, but it never shows up in Phone Link on your PC, and no desktop notification appears either. That's the specific symptom this guide fixes: an MFA code not showing in Phone Link on Windows 11, specifically SMS-based codes that already reached the phone.
It doesn't cover codes that never arrive on the phone, and it doesn't cover a Microsoft Authenticator code not showing on Windows 11. Authenticator-generated codes are a separate path from SMS mirroring and don't depend on Phone Link syncing.
Two apps are involved, and mixing them up burns a lot of troubleshooting time. Phone Link runs on the Windows 11 PC and shows mirrored texts and notifications from the phone. Link to Windows is the companion app on the Android phone that connects those features to the PC.
There is also an important Android limitation to know before changing settings. Microsoft's current Phone Link documentation says Android 15 and later can classify notifications containing two-factor authentication codes, one-time passcodes, and other sensitive information as Sensitive Notifications. Phone Link can't currently display those notifications.
Another issue can occur when a message already appears in Phone Link, but no notification banner appears on the Windows desktop. Those two symptoms require different checks, so it matters which one applies before you change any settings.
What follows is a short sequence for narrowing down where the code is getting stuck, a fix to try at each stage, and a way to make sure a missing text never turns into a locked account.
Why an MFA code is not showing in Phone Link on Windows 11
Work through these questions in order. Each answer points toward a different cause, not a vague "notifications are broken" diagnosis.
Does the code arrive on the phone as a text at all? If not, check the sender, messaging app, carrier, and account before assuming Phone Link is at fault. Skip to the backup-method section below while troubleshooting delivery separately.
Does the code show up inside Phone Link on the PC? If yes, but no desktop banner appears, that points toward Phone Link or Windows notification handling rather than message delivery. Jump to "Code visible in Phone Link but no Windows banner appears" below.
Is the code hidden or missing from Phone Link even though it arrived on the phone? On Android 15 or later, Sensitive Notifications may be responsible. Microsoft says notifications containing two-factor authentication codes and other sensitive information can be blocked from appearing in Phone Link.
Have all messages stopped syncing, not just codes? That's a broader Phone Link messaging or pairing problem rather than something tied specifically to MFA codes.
Applying a Windows notification fix to a code Android deliberately hides won't solve anything, and troubleshooting Android's Sensitive Notifications feature won't help if the message already appears in Phone Link but Windows simply isn't showing a banner.
Code visible in Phone Link but no Windows banner appears
Start here only if the code shows up inside Phone Link but never triggers a desktop banner.
On the PC, open Phone Link and go to Settings > Features > Messages. Microsoft provides controls there for message alerts, including Show notification banners and Badge on taskbar.
Also check Settings > Features > Notifications in Phone Link to make sure notification syncing is enabled.
If notifications more broadly have stopped syncing, Microsoft recommends resetting Link to Windows' notification access on the Android phone:
Open Android Settings and search for Notification access.
Find Link to Windows and turn its access off.
Turn it back on and select Allow when prompted.
Return to Phone Link on the PC, open Notifications, and wait for notifications to refresh.
On Windows, also check whether Do Not Disturb is suppressing notification banners.
If the code itself is visible in Phone Link but no banner appears, these notification settings are relevant. If the sensitive code isn't available inside Phone Link at all, move to the Android section instead.
Fix Phone Link not receiving SMS codes: check Android access first
If ordinary messages and notifications aren't reaching Phone Link, start on the Android phone.
Microsoft says Link to Windows requires Android notification permission for notification syncing. On Android 13 or later, that permission can be checked under Settings > Apps > Link to Windows > Notifications.
For notification mirroring, also search Android Settings for Notification access and confirm Link to Windows is allowed. Microsoft specifically recommends toggling this permission off and back on when notifications stop syncing.
Messages have their own Phone Link controls as well. On the PC, go to Phone Link > Settings > Features > Messages and make sure Allow this app to show text messages from my phone is enabled.
Microsoft also recommends installing the latest version of Phone Link when messages are missing.
If normal SMS messages work but MFA notifications are hidden, however, changing these general permissions may not solve the problem. Android 15's Sensitive Notifications behavior needs to be considered separately.
Why Android 15 may hide MFA notifications from Phone Link
Android 15 introduced Sensitive Notifications, a privacy feature designed to prevent sensitive notification content from being exposed through notification-listener apps.
Microsoft's current Phone Link documentation says notifications containing two-factor authentication codes, one-time passcodes, and other sensitive information can be identified and hidden by Android. When that happens, Phone Link may show "Sensitive notification content hidden" instead of the actual contents.
Microsoft currently says this behavior affects Android devices running Android 15 or later.
The company's guidance is also straightforward: notifications Android marks as sensitive are currently blocked from being displayed in Phone Link, so users need to check those notifications directly on the phone.
Older reporting described device-specific exceptions and a possible workaround involving Android's Enhanced Notifications setting. Microsoft's current support documentation no longer recommends that as a solution, so it shouldn't be relied on as the standard fix for missing MFA notifications.
That privacy restriction also means a missing MFA notification isn't necessarily evidence that Phone Link or Link to Windows is malfunctioning. If ordinary notifications continue to sync while only authentication codes are hidden, Android's sensitive-content protection is a stronger possibility.
One reported Android 17 SMS-sync failure
If Phone Link has stopped showing any messages at all, with no new-message notifications appearing either, that doesn't match a problem limited to sensitive MFA notifications and warrants a broader sync investigation.
One user described that scenario in a Microsoft Community Hub thread after updating to Android 17: Phone Link SMS messages stopped appearing on Windows 11 entirely after the update.
Treat that as a single reported case, not a confirmed Android 17 compatibility bug. There's no authoritative evidence establishing that Android 17 broadly breaks Phone Link SMS syncing.
The user reported removing and re-pairing the device, signing out, resetting app data, and confirming SMS permission was enabled without resolving the problem. The same PC reportedly worked with a separate Android 12 device, which narrowed the problem in that individual case without establishing its cause.
Anyone experiencing a broader messaging failure should first update both Phone Link and Link to Windows and check the message and notification permissions described above.
Microsoft also notes that missing messages can occur when a third-party app is being used as the primary messaging platform and that slow network connections can delay message syncing.
There's no confirmed Android 17-specific fix documented by Microsoft, so don't treat a full messaging failure after an Android upgrade as the same issue as Sensitive Notifications hiding an MFA code.
Set up a backup so a missing code doesn't lock you out
SMS mirroring depends on SMS delivery and Phone Link's messaging or notification features working as expected. On Android 15 or later, sensitive-notification protections can introduce another limitation.
That's why Phone Link shouldn't be the only way to access a sign-in code.
Microsoft Authenticator isn't a fix for Phone Link's SMS mirroring. It's a separate authentication method that can avoid relying on a mirrored SMS code.
For accounts and services that support it, add and test Authenticator, a passkey, security key, or another backup sign-in method while you're still signed in and able to use the existing method.
Keep the existing authentication method until the replacement has been configured and tested successfully, and save any recovery codes the service provides somewhere secure.
If a phone is being replaced, make sure the new authentication or recovery method works before removing access associated with the old device. Exact security settings and recovery procedures differ between personal Microsoft accounts and work or school accounts.
The key is identifying where the failure occurs before trying to fix it.
A code visible in Phone Link with no banner points toward Phone Link or Windows notification settings. Ordinary messages and notifications failing to sync calls for checking Link to Windows permissions and Phone Link's messaging controls. A sensitive authentication notification hidden on Android 15 or later may simply be subject to Android's privacy protection and need to be viewed directly on the phone.
Either way, set up another authentication or recovery method while account access still works rather than waiting until the next missing code becomes an account-recovery problem.
Comments
Be the first, drop a comment!