# Phone Link: what actually syncs, and what it never will

> Pairing, the notification and photo features that work, the ones that depend on the phone OS, and why it is not a backup.

**Tested on**

- Build: 26300.9457
- Edition: Pro (26H2)
- Architecture: x64
- Evidence: E1
- Verified: 2026-10-29

## The short answer

Phone Link is a **bridge, not a sync engine**. It mirrors a subset of phone features onto the PC while the phone is reachable:

| Feature | Android | iPhone |
|---|---|---|
| Notifications | yes | yes (limited actions) |
| Messages (SMS) | yes | yes |
| Calls | yes | yes (via Bluetooth) |
| Photos (recent) | yes | yes (recent only) |
| Apps on screen | yes (selected devices) | no |
| File transfer | limited | limited |
| Full backup | **no** | **no** |

The last row matters: a photo that appears in the Phone Link gallery is a *view* of the phone's recent items, not a copy on your PC.

## What it needs

- Same Microsoft account on phone and PC (or QR pairing).
- Bluetooth for calls, Wi-Fi/LTE for the rest.
- The phone app installed and granted notification/message permissions.
- **Not** the same network — it works across the internet, which is also why corporate networks sometimes block it.

```powershell
Get-AppxPackage *YourPhone* | Select-Object Name,Version,Status
Get-AppxPackage *CrossDevice* | Select-Object Name,Version,Status
```

The app has been renamed more than once (`Your Phone`, then `Phone Link`); the package name is the stable identifier.

## Where it breaks

| Symptom | Cause |
|---|---|
| Notifications arrive late | battery optimisation killing the phone app |
| Photos do not appear | permission revoked by the phone OS update |
| Calls fail | Bluetooth pairing separate from the app pairing |
| Works at home, not at work | firewall/proxy blocking the service |
| "Phone disconnected" constantly | phone on a VPN, or aggressive power saving |

> **Caution: It is not a backup and not a file sync**
>
> Do not treat the photo view as a backup of your camera roll. Use the phone's own cloud backup or a cable transfer. See [backup that survives ransomware](https://windows.homes/en/windows/security/backup/) for the PC side.

## When Phone Link is genuinely useful

- **Notifications while working** — the main everyday win.
- **SMS two-factor codes** without picking up the phone.
- **Copy a photo quickly** for a chat or document.
- **Answer a call** on the laptop with a headset.

When it is not: bulk file transfer, backup, or anything where reliability matters.

## Corporate machines

On a managed device, Phone Link may be blocked by policy (`AllowPhonePCXApp`-style settings) or by conditional access. That is deliberate: linking a personal phone to a work PC is a data-flow decision, not a preference.

## Related

- [Remote Desktop host setup](https://windows.homes/en/windows/remote/rdp-host/)
- [Bluetooth audio](https://windows.homes/en/windows/peripherals/bluetooth-audio/)
- [Backup that survives ransomware](https://windows.homes/en/windows/security/backup/)

## Lab boundary

E1. Phone Link capabilities are documented by Microsoft and vary by phone OS version and region. The lab VMs have no paired phone, so no pairing flow was exercised.

## Sources

- [Microsoft Learn — Windows 11 overview](https://learn.microsoft.com/en-us/windows/whats-new/windows-11-overview)
- [Microsoft Learn — Mobile device management](https://learn.microsoft.com/en-us/windows/client-management/mdm/)
- [Microsoft Learn — Accounts CSP](https://learn.microsoft.com/en-us/windows/client-management/mdm/accounts-csp)

---

Source: https://windows.homes/en/windows/remote/phone-link/