MFA Code Not Showing in Phone Link Windows 11: Fix It

A one-time passcode lands on the Android phone as a text, but it never shows up in Phone Link on the 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 does not cover codes that never arrive on the phone at all, and it does not cover a Microsoft Authenticator code not showing on Windows 11, since Authenticator-generated codes are a separate path from SMS mirroring and don't depend on this syncing process.

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 works with Phone Link to make phone notifications available on the PC (Microsoft Q&A). Much of the diagnostic framework below comes from a single Microsoft Q&A thread posted earlier this year; treat it as community troubleshooting rather than official Microsoft documentation, since menu names and behavior can shift between Phone Link versions.

Phone Link displayed a warning about this limitation on its own, according to The Verge: certain Android notifications, including two-factor codes, won't reach the PC because of a newer Android privacy feature, though the reporting doesn't spell out every affected device or OS build. Separately, one user described a different symptom in a Microsoft Q&A thread: the code already showed up inside Phone Link, but no banner ever appeared on the Windows desktop. Those two symptoms likely require different checks, which is why sorting out which one applies matters before touching 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.

1. Does the code arrive on the phone as a text at all? If not, check the sender, the messaging app, the carrier, and the account before assuming Phone Link is at fault. Skip to the backup-method section below while troubleshooting that separately.
2. Does the code show up inside Phone Link on the PC? If yes, but no desktop banner appears, that points more toward Phone Link or Windows notification handling than message delivery. Jump to "Code visible in Phone Link but no Windows banner appears" below.
3. Is the code missing from Phone Link entirely, even though it arrived on the phone? That points toward something on the Android side: a notification permission, or possibly Android 15's sensitive-notification behavior, depending on the phone and Android build. Jump to the Android notification-access section below.
4. Have all messages stopped syncing, not just codes? That's a broader pairing or compatibility issue, not something tied to MFA codes specifically. Jump to the Android 17 section below.

Applying the Android 15 workaround to what's actually a Windows display setting won't fix anything, and running the check in reverse wastes just as much time.

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. These are settings worth checking first, based on a Microsoft Q&A thread describing the same symptom.

1. On the PC, open Phone Link, go to Settings > Features > Notifications, and make sure Phone Link notifications are enabled.
2. On the PC, go to Settings > System > Notifications and turn off Do Not Disturb and Focus Assist. Either one can suppress Phone Link's banner the same way it suppresses any other app's alerts. Windows 11 has reshuffled notification controls across versions, so this may show up as a notification-priority or automatic-rules setting instead of two separate toggles; check whatever's labeled for interrupting notifications.

These are community-sourced steps, not confirmed Microsoft documentation, and menu labels may differ depending on the Phone Link version installed. If the banner still doesn't show after checking both, testing again after a restart is worth trying as an optional step, not a researched fix. If the code never showed up inside Phone Link in the first place, none of this will help; move to the next section instead.

Fix Phone Link not receiving SMS codes: check Android notification access first

This section applies only if the code never shows up inside Phone Link at all, not just the desktop banner. Start on the phone, not the PC.

Open Settings > Apps > Link to Windows on the Android phone and check two things: that notifications are turned on for the app, and that notification access is still granted under the phone's special app-access settings (Microsoft Q&A). Menu names vary across Samsung, Pixel, and other Android builds, so look for "Notification access" or "Apps with notification access" if the exact path above doesn't match the phone.

The Q&A response notes that an Android update may have silently removed this permission, so verify it manually rather than assuming it's still on (Microsoft Q&A).

If access checks out and the code is still missing from Phone Link, the Android 15 limitation becomes another possibility to investigate.

Why Android 15 may hide MFA notifications from Phone Link

The Verge reported that Android 15 includes a privacy feature that automatically classifies notifications containing two-factor codes as sensitive, which blocks third-party apps, Phone Link included, from reading them.

That's reported behavior tied specifically to Android 15's notification-mirroring policy. It doesn't confirm that every missing Phone Link code on Android 15 or later shares this cause, and the cited reporting doesn't specify every affected device or OS build.

The restriction isn't universal, either. Mishaal Rahman and Windows Central reported that phones where Phone Link came preinstalled with Android's Companion Device Role already granted, including some Samsung phones running One UI 6.1.1, may still display sensitive notifications normally (The Verge, citing Mishaal Rahman/Windows Central). Pixel and Nothing Phone users, the report said, weren't getting that same exception.

A reported workaround is turning off Enhanced Notifications in Android's notification settings, typically found under Settings > Notifications (The Verge). Treat it as a possible fix, not a guaranteed one. It changes Android's notification privacy behavior broadly, which may reduce Android's protection against other apps reading sensitive notification content, not just Phone Link. Check which apps currently have notification access, under Settings > Apps > Special app access > Notification access, before switching it off, since the trade-off applies to every one of them.

One reported Android 17 SMS-sync failure

If Phone Link has stopped showing any messages at all, with no new-message notifications firing either, that doesn't match a problem limited to sensitive MFA notifications, and it warrants a broader sync investigation. One user described exactly that in a Microsoft Community Hub thread a few months ago, after updating to Android 17: Phone Link SMS messages stopped showing on Windows 11 entirely following the update (Microsoft Community Hub).

Treat this as a single reported case, not a confirmed Android 17 compatibility bug. There's no independent corroboration yet of how widespread it is or what's causing it.

The same user had already removed and re-paired the device, signed out, reset app data, and confirmed SMS permission was still enabled, all without success (Microsoft Community Hub). The same PC worked normally when paired with a separate Android 12 device; in that report, this narrowed the problem to the newer phone or OS rather than proving the cause (Microsoft Community Hub).

Anyone hitting this exact scenario should check for app updates to Phone Link and Link to Windows as a standard first step, separate from anything confirmed in this specific report, before trying anything more drastic. There's no confirmed fix yet, so treat any workaround as something to test, not something to count on.

Set up a backup so a missing code doesn't lock you out

SMS mirroring depends on carrier delivery, Android permissions, and Windows notification settings all working at the same time. That's why SMS mirroring shouldn't be the only way to see a sign-in code.

Microsoft Authenticator is not a fix for Phone Link's SMS mirroring. It's a separate sign-in method that skips SMS entirely, generating its own time-based codes on the phone.

For Microsoft account sign-ins specifically, a Q&A thread posted earlier this year lists a few possible explanations when codes or calls fail to arrive: verification limits, high request volume, and risk-based blocking tied to a specific phone number (Microsoft Q&A). That thread mixes several overlapping issues, including iPhone pairing and Microsoft 365 admin lockouts, and it carries Microsoft's own disclosure that its answers may be AI-generated. Treat the SMS-delivery explanations as plausible leads to check, not a settled diagnosis, and confirm anything account-recovery related directly with Microsoft support before relying on it. The same thread warns that retrying repeatedly can extend a block instead of clearing it.

According to that source, Microsoft Authenticator can generate a verification code over Wi-Fi, cellular data, or with no signal at all (Microsoft Q&A). That applies to the app's own time-based codes; it doesn't mean every Microsoft sign-in flow works without any connection at all.

Add and test Authenticator, or another backup sign-in method, while still signed in and able to receive SMS codes normally, not after one has already failed. Keep the existing SMS method enabled until the new one is confirmed working, and save any recovery codes a service offers during setup; those are the fallback if both the phone and the new method run into trouble at the same time.

If a phone ever gets replaced, don't remove the old device's entry from the account's security info page until the replacement method is confirmed and tested (Microsoft Q&A). The exact page differs for a personal Microsoft account versus a work or school account, so follow the path that matches the account type. Removing the old entry first, before the new one is verified, risks locking the account out entirely.

Check Phone Link itself before assuming a code is gone for good. A code visible in the app with no banner needs a Windows or Phone Link notification fix; a code missing from Phone Link entirely needs an Android access check and, possibly, the Android 15 workaround; messages that have stopped syncing altogether are an unresolved compatibility report, not a setting to flip. Either way, add Microsoft Authenticator or another backup sign-in method now, while access still works, rather than after the next code goes missing.