Microsoft will retire its Mobile Plans app on February 27, 2026, pushing the purchase and management of cellular data plans for Windows laptops and tablets to carrier websites and the built‑in Windows Settings. Existing eSIM profiles will keep working, but the dedicated app—a holdover from the Windows 10 era—will cease functioning entirely on that date.

A low‑profile app bows out

The Mobile Plans app debuted years ago as a convenience layer for the small subset of Windows devices that ship with LTE or 5G modems. It detected a cellular‑capable PC, presented participating carriers, and walked users through plan selection, checkout, and eSIM provisioning—all without leaving the OS. But the app never escaped its niche. Its Microsoft Store listing still references Windows 10 rather than Windows 11, and updates were sparse.

Behind the scenes, Microsoft had already been nudging the ecosystem toward a different model. Windows 11’s Settings app can install eSIM profiles via QR code or activation code, and a new feature—currently in testing among Windows Insiders—will allow carrier websites to trigger eSIM provisioning through Settings after the user consents to share device identifiers. That feature is expected to reach general availability before the end of 2025, with carriers adding support throughout 2026.

Why Microsoft is killing the app

The reasons are pragmatic and mirror broader platform trends:

  • Reduce engineering burden: Maintaining an in‑OS storefront requires constant work on updates, payment systems, and regulatory compliance—work that carriers already do on their own portals.
  • Hand control back to carriers: Operators want to manage pricing, promotions, refunds, and identity verification directly. A web checkout gives them complete control over the purchase experience and lets them iterate faster than Microsoft’s app sandbox.
  • Leverage built‑in eSIM support: Windows already supports eSIM activation through Settings. By prompting users to approve the sharing of EID (eUICC ID) and IMEI from within Settings, the OS can orchestrate a zero‑touch installation when a carrier’s website requests it.

This aligns with a long‑running Microsoft practice: consolidate small, underused utilities into Settings or web experiences. The classical Mail and Calendar apps, for instance, are being replaced by the web‑based Outlook.

What changes for consumers

  • Existing plans live on: Any eSIM profile already installed on a device will continue working after February 27, 2026. Connections won’t drop.
  • New purchases move to the browser: To buy a plan, users will visit a carrier’s website. The self‑contained Mobile Plans store vanishes.
  • Settings becomes the provisioning hub: Windows Settings will be the sole OS surface for accepting privacy prompts and completing automatic eSIM installations. If a carrier supports the new web‑triggered flow, buying a plan on its site can cause Windows to ask, “Share your device identifiers with this carrier?” Approving it passes the EID and IMEI securely, and the eSIM profile downloads without scanning a QR code.
  • Fallback paths persist: Manual QR‑code scanning and activation‑code entry remain available in Settings > Network & Internet > Cellular > eSIM profiles.

What changes for IT administrators

  • MDM workflows must be audited: Organizations using Microsoft Intune or another MDM to push eSIM activation codes should verify that their current provisioning commands work independently of the Mobile Plans app. Most will be unaffected, but testing is prudent.
  • Deployment guides need updating: Any onboarding scripts, OOBE documentation, or help‑desk guides that point users to the Mobile Plans app must be rewritten to direct employees to carrier websites and the Settings app.
  • Fleet inventory: Identify every device that might rely on the app for plan discovery or activation. If a carrier’s web flow doesn’t yet support Desktop‑triggered provisioning, plan for QR‑code or activation‑code alternatives.

How eSIM provisioning works on Windows now

Windows 11 already supports multiple activation methods:

  1. Open Settings > Network & Internet > Cellular > eSIM profiles.
  2. Choose a method:
    - Carrier website + Settings (new): Complete purchase on the carrier’s site. When prompted, click “Approve” in the Windows Settings pop‑up to share EID and IMEI. The profile installs automatically.
    - QR code: Select “Use a QR code from your mobile operator” and point your camera at the code.
    - Activation code: Enter the code provided by the carrier.
  3. Confirm the download and enter any carrier‑specific confirmation codes.
  4. Manage profiles directly in Settings—switch between them, rename them, or delete ones you no longer need.

For enterprises, MDM tools can pre‑provision eSIM profiles or push activation codes silently. Intune, for example, supports a cellular configuration service provider that can deliver activation codes and control profile behaviors.

  • Explicit consent is the gatekeeper: Windows will never share device identifiers automatically. A clear, interruptive prompt appears, detailing exactly what will be sent (EID and IMEI). Users must actively approve.
  • Carrier data handling: Once identifiers leave the device, the carrier becomes their custodian. Users and enterprises should review the carrier’s privacy policy—particularly how long identifiers are retained, how they are linked to accounts, and whether they are shared with third parties.
  • Payment and refunds: Because purchases happen on carrier websites, any dispute or refund follows the carrier’s policies, not Microsoft’s in‑app purchase rules.
  • Web‑surface attack vectors: Shifting to browser‑based checkout introduces standard web threats—phishing sites, fake activation pages, and supply‑chain compromises. Carriers must implement robust anti‑fraud measures and clear referral validation.
  • Enterprise governance: Organizations with strict telemetry and identity policies should evaluate whether web‑triggered provisioning aligns with their security posture. Some may prefer to lock down identifier sharing via Group Policy or MDM.

Potential pitfalls during the transition

  • Fragmented carrier support: Not every operator will implement the Settings‑triggered provisioning flow immediately. Users may land on a carrier site that still requires a QR code or manual entry, creating confusion.
  • Broken deep links: Any micro‑interactions that previously launched the Mobile Plans app—promotional notifications, carrier onboarding wizards, help links—will fail.
  • Loss of one‑stop shop: The Mobile Plans app gave a cohesive, Microsoft‑branded storefront. Less tech‑savvy users may struggle to navigate disparate carrier websites, each with its own design and terminology.
  • MVNO and international gaps: Smaller virtual network operators or overseas carriers may not be optimized for desktop checkouts or may rely exclusively on mobile‑first activation flows.
  • Timing mismatches: If the Settings‑based feature arrives late and carriers drag their feet, there could be a window where users must fall back to QR codes or activation codes despite having bought a plan online.
  • Enterprise complexities: Organizations that standardized on Mobile Plans for rapid deployment will need to rebuild their provisioning pipeline, possibly integrating activation codes into MDM scripts and updating enrollment policies.

Migration checklist: what users and admins should do now

  • Inventory devices: List all corporate‑owned or personally‑owned Windows laptops and 2‑in‑1s that have a cellular modem.
  • Record carrier details: For each active line, note the carrier, account number, phone number, and any stored activation codes.
  • Bookmark carrier activation pages: Save direct URLs to the “Bring your own device” or “Activate eSIM” sections of your carriers’ sites.
  • Test early: If cellular connectivity is mission‑critical, run a trial checkout and provisioning on a representative device well before February 2026.
  • Back up information: Take screenshots of plan details, support contacts, and subscription IDs.
  • Request Windows‑specific guides: Ask carriers whether they have desktop‑optimized activation flows or documentation.
  • Update OOBE materials: If you deploy devices, incorporate new activation steps into setup guides, help‑desk scripts, and enrollment communications.

Guidance for carriers and OEMs

  • Publish a dedicated “Activate on Windows” page that supports desktop‑first checkout and, ideally, the Settings‑triggered provisioning protocol.
  • Always include fallback methods: Provide a QR code and activation code alongside the automated option.
  • Test thoroughly with Windows user agents to ensure the checkout flow detects the OS and presents a clear activation path.
  • Disclose identifier handling: Make privacy and retention policies for EID/IMEI transparent on the activation page.
  • Train support teams: Equip frontline staff with Windows‑specific activation guides and a FAQ.
  • OEMs should update quick‑start guides: Include carrier activation links in packaging, setup posters, and the out‑of‑box experience. Work with carrier partners to embed activation links that are aware of the new Settings flow.

5G laptops and always‑connected PCs are unaffected

The retirement does not remove cellular capability from Windows. LTE and 5G modems—found in devices like the Surface Pro 11, Surface Laptop 7 (business), Lenovo ThinkPad X1 Carbon, and others—will continue operating normally. Drivers, firmware, and the networking stack remain untouched. Only the method for buying and provisioning the data plan changes.

For mobile professionals, journalists, and remote workers, integrated 5G or LTE still offers lower latency and more consistent connectivity than tethering to a phone. The hardware benefit survives; the purchase pipeline simply moves to the web.

Transition timeline

  • Insider testing now: The Settings‑triggered identifier‑sharing flow is available in Windows Insider builds.
  • General availability by end of 2025: Microsoft aims to push the feature to stable Windows 11 installations before the year closes. Carriers are expected to add support throughout 2026.
  • February 27, 2026: The Mobile Plans app stops working. Users who try to open it will be met with a non‑functional interface. The app may eventually be removed from the Microsoft Store and from Windows images altogether.

Exact dates may vary based on partner readiness and enterprise communication channels (Message Center, OEM notifications). Companies and power users should monitor official Microsoft documentation and carrier announcements.

Step‑by‑step: setting up eSIM on Windows after the change

  1. Confirm eSIM support: Open Settings > Network & Internet > Cellular. If you see “eSIM profiles,” your device is ready.
  2. Choose your activation path:
    - Carrier website: Buy a plan using your preferred browser. Look for a “Download eSIM” or “Install profile” button. Accept the Windows Settings prompt that follows.
    - QR code: In Settings, select “Use a QR code from your mobile operator” and scan the code with your PC’s camera.
    - Activation code: Enter the alphanumeric code provided by the carrier.
  3. Follow on‑screen prompts: Provide any confirmation codes the carrier requires and wait for the profile to download.
  4. Manage profiles: Switch between eSIM lines, rename them, or delete unused profiles under Settings > Cellular > eSIM profiles.

Bottom line: streamlining, not abandoning

Killing the Mobile Plans app isn’t a retreat from cellular connectivity—it’s a consolidation of where commerce and provisioning live. Microsoft is offloading the storefront to carrier websites, where payment and customer relationships belong, while keeping the OS as the secure, consent‑driven installation engine.

This shift does demand coordinated action from carriers, OEMs, and enterprise IT teams to avoid a disjointed user experience. For most consumers, the change will be invisible. For power users and IT managers, proactive testing and carrier communication are the best insurance against last‑minute headaches.

The hardware, the protocols, and the eSIM standard remain. Only the control panel for acquiring data plans is moving to the open web—a pattern that will likely repeat as operating systems slim down and push specialized tasks to the browser.