Microsoft has set a hard retirement date for its built-in Mobile Plans app: February 27, 2026. After that, the small storefront that lets cellular‑capable Windows laptops and tablets buy data plans directly from the OS will disappear from the Microsoft Store and documentation. In its place, Microsoft is pushing a web‑first model where carriers handle checkout on their own websites, while Windows Settings takes over the secure, consent‑driven provisioning of eSIM profiles.

Users who rely on the app to discover operators or purchase short‑term data bundles will no longer find it in Windows. But this is not a removal of cellular support. The underlying drivers, eSIM stack, and the APIs that let carriers push profiles over the air remain fully intact. Only the commerce and discovery layer is being carved out and handed to mobile operators.

Microsoft’s own announcement, distributed through its Windows OS Platform blog and Message Center, frames the retirement as a consolidation of effort. The change had been expected for several months after the company began moving low‑usage UWP experiences into Settings or web flows. Multiple industry reports, which WindowsNews.ai has corroborated with Microsoft’s public communications, agree on the February 2026 cutoff. The company will stop linking to the app in its documentation, and it will vanish from the Store. Enterprise IT administrators and power users now have an 18‑month window to migrate workflows and documentation before the plug is pulled.

A Quick History of the Mobile Plans App

The Mobile Plans app shipped as a system component on Windows 10 and 11 devices equipped with cellular radios or eSIM support. It acted as an in‑OS marketplace: users could browse a curated list of participating carriers, compare short‑term or recurring data plans, and complete a purchase without ever opening a browser. Once a plan was bought, the app would trigger the download and installation of an eSIM profile, getting the user online in minutes.

Over its life, the app remained a niche tool. Penetration was highest among corporate road warriors and students with Always Connected PCs powered by Qualcomm Snapdragon or Intel’s LTE/5‑enabled platforms. Yet for every active user, the app required Microsoft to maintain payment integrations, regional compliance for dozens of markets, carrier‑specific SKU logic, and a consistent UX across screen sizes. Those costs, combined with low usage, made it an early candidate for retirement as Microsoft accelerates its “Settings over apps” strategy.

What’s Actually Changing

The headline change is straightforward: the Mobile Plans app is going away. But four other shifts matter just as much.

  1. Commerce moves to carrier websites. When you want to buy new cellular data for your Windows laptop, you will visit your operator’s portal, pick a plan, and pay there. No Microsoft‑branded storefront will sit between you and the carrier.

  2. Provisioning stays inside Windows Settings. The secure eSIM installation that used to happen after an in‑app purchase will now be kicked off directly from the Settings app. Windows will show a consent prompt asking if you want to share your device’s cellular identifiers (EID and IMEI) with the carrier. If you agree, the carrier can push the eSIM profile to your PC without any QR code or manual activation code.

  3. Identifier sharing is consent‑based. The new Settings flow will always demand explicit user consent before sending persistent hardware identifiers to a carrier website. Microsoft has built the feature so that no identifiers are sent silently; the user must click an approve button inside a Settings dialog.

  4. Fallback methods remain. If a carrier hasn’t yet adopted the web‑triggered activation, customers can still scan QR codes or type activation codes obtained from the carrier. The QR‑based manual flow is unchanged.

Microsoft expects the Settings‑mediated identifier sharing to reach general availability before the end of 2025, well ahead of the Mobile Plans app’s retirement. Insiders already have access to the feature, and carrier enablement will continue through 2026.

Why Microsoft Is Making the Move

Three motivations drive the decision, according to Microsoft’s communications.

  • Reduce maintenance surface. Supporting an integrated storefront meant ongoing engineering for payment processing, operator onboarding, regional tax rules, and a custom UI. By removing the app, Microsoft can sunset that entire code path. The engineering effort can shift to making the core eSIM APIs and the Settings experience more robust.

  • Carrier control over commerce. Mobile operators have long wanted to own the full checkout experience: billing, refunds, promotions, identity verification, and plan evolution. Forcing users through a Microsoft app limited their ability to upsell, cross‑sell, or apply loyalty discounts. The new model lets carriers use their own mature e‑commerce platforms, which they can update without waiting for Microsoft’s app release cadence.

  • Leverage existing native plumbing. Windows 10 and 11 already contain all the components needed to manage eSIM profiles: a profile download engine, a secure element interface, and a user‑facing management page under Settings > Network & internet > Cellular. By cutting out the app store layer, Microsoft can preserve the best part of the experience—native provisioning—while delegating discovery and purchase to the web.

These motivations mirror broader platform shifts. Low‑usage UWP apps (3D Viewer, Paint 3D, Mail & Calendar) have been retired or absorbed into Settings and web experiences. Mobile Plans is simply the latest to go.

The New eSIM Activation Flow: Step by Step

To understand the new model, you need to know what an eSIM is and which identifiers matter. An eSIM (embedded SIM or eUICC) is a tiny, soldered‑down chip that stores one or more carrier subscription profiles. Carriers can program it over the air without you inserting a physical SIM card. Two device identifiers play a role:

  • EID (eUICC Identifier): A globally unique serial number burned into the eSIM controller.
  • IMEI (International Mobile Equipment Identity): The unique identifier of the cellular modem inside your PC.

Carriers need at least one of these to bind a new plan to your device. In the old Mobile Plans app, the app would collect these values and send them to the carrier behind the scenes after your purchase. In the new flow, you’ll see an explicit consent step.

Here’s the user journey once carriers support the web‑based activation trigger:

  1. Open your browser and go to your carrier’s website. Choose a data plan and go through the normal checkout.
  2. During or after checkout, the carrier’s site offers a button like “Activate on this Windows device.” Clicking that triggers a secure handoff to Windows.
  3. A Windows Settings dialog appears, asking: “Allow this site to access your device’s cellular identifiers?” It lists exactly which identifiers (EID, IMEI) will be shared.
  4. With your consent, the identifiers are sent via HTTPS to the carrier’s provisioning backend. The carrier then uses Windows eSIM APIs to push the profile over the air.
  5. A final Windows confirmation dialog asks you to confirm the eSIM download. Once accepted, the profile installs, and you’re connected.

If a carrier doesn’t support the web trigger, you’ll fall back to the traditional path: after purchase, the carrier provides a QR code or an activation code. You’ll go to Settings > Network & internet > Cellular > Add an eSIM and scan or type the code manually. That fallback ensures no user is left without a way to activate cellular service.

The new consent dialog is the heart of the security model. Before the change, the Mobile Plans app would ask for consent through its own interface. Now, the choice lives in a system‑level Settings surface—harder to spoof and easier to audit. Microsoft says the transport uses standard HTTPS/TLS encryption. The dialog clearly states what data is about to be transmitted and to which carrier.

However, a critical privacy boundary shifts. Microsoft’s old app had its own privacy policy and, presumably, its own data handling rules. In the new model, once identifiers leave the device, the carrier’s privacy policy applies. That means carriers will decide:

  • How long they retain EID/IMEI values.
  • Whether they link those identifiers to a customer’s wider profile.
  • Whether they share or sell that data to third parties.

Microsoft has publicly stated that the OS‑level consent only governs the transmission of identifiers. It does not control what carriers do afterward. This places a new burden on users—especially enterprise users subject to GDPR, CCPA, or internal security policies—to scrutinize carrier privacy terms before clicking “Allow.” During the transition, IT departments should add carrier privacy checks to their procurement and onboarding workflows.

Timeline and Rollout: What’s Confirmed, What’s Reported

Microsoft has provided a broad timeline, and multiple outlets have filled in details from partner conversations and embargoed briefings. Here’s the picture at the time of writing:

  • Now: Settings‑mediated identifier sharing is available to Windows Insiders in the Dev and Beta channels. Microsoft is collecting telemetry and feedback on the consent UX.
  • Late 2025: The feature is expected to reach general availability for all Windows 10 and 11 devices with eSIM support. The exact date will appear in a future Windows update’s release notes.
  • February 27, 2026: The final day the Mobile Plans app will be usable. After this date, Microsoft will pull it from the Store and scrub related links from its documentation. This date has been widely reported and is treated as the public target, though enterprise admins should double‑check against Microsoft’s official Message Center and carrier communications before making large‑scale changes.
  • 2026 onward: Carriers will continue to enable the web‑based activation trigger on their websites at their own pace. Microsoft is providing technical guidance, but participation is voluntary. Small regional carriers may lag, so users in some markets might not see the “no‑QR” experience until later.

There is no forced migration of active plans. Existing eSIM profiles and recurring subscriptions will continue to work through their normal lifecycles. Only the ability to discover new plans or buy them through the app is ending.

Impact on Consumers and Power Users

For the average laptop owner with built‑in cellular, the change will be nearly invisible unless they actively used Mobile Plans. If you never opened the app or only activated an eSIM once during setup, your experience won’t change. The cellular settings page remains accessible, and once‑installed profiles will keep functioning.

Travelers and power users who frequently switch operators or buy short‑term data bags will feel the shift more acutely. Instead of opening a familiar app, they’ll need to navigate carrier websites, which can vary wildly in design and speed. The upside is that many carriers already have polished, responsive web stores that are faster and richer than the old Microsoft app. If a carrier implements the Windows activation trigger, buying a plan could be
smoother than before: no QR codes, no copying keys. That frictionless experience, however, will depend entirely on each carrier’s execution.

One immediate practical tip: bookmark your carrier’s eSIM page. Before traveling, check whether the carrier lists Windows as a supported device. If it does, the web‑triggered activation should work. If not, you’ll need to retrieve a QR code or activation code from the carrier’s portal or customer support and use the manual fallback.

What Enterprises and IT Admins Need to Do

The retirement of Mobile Plans is a classic “small feature sunset” that can create disproportionate helpdesk noise if IT teams aren’t prepared. Here’s how to stay ahead.

Inventory Your Cellular Fleet

Run a report in Microsoft Intune, SCCM, or your asset management tool to find all Windows devices with cellular modems. Note which carriers and plans are assigned to each device. If any provisioning workflow relied on Mobile Plans—for example, OOBE instructions telling users to open the app and pick a carrier—those documents need updating.

Update Onboarding and OOBE Documentation

The old flow often said: “Open Mobile Plans and select carrier X.” Replace that with the carrier’s activation URL and instructions for the Settings‑mediated flow (when applicable) or the QR/manual fallback. Consider creating a one‑pager with screenshots of the consent dialog so users aren’t confused when they see it for the first time.

Test eSIM Deployment via MDM

Intune and other MDM platforms already support pushing eSIM profiles via CSPs (Configuration Service Providers). That mechanism is unrelated to the Mobile Plans app and won’t break. But if your helpdesk scripts reference the app for manual activations, they need an update. Run a pilot activation with your carrier partner using the new web flow. If the carrier hasn’t implemented it yet, document the QR fallback and ensure your helpdesk knows the difference.

Privacy and Compliance Check

Request clear written privacy statements from your carriers regarding EID and IMEI retention. This is especially critical for industries subject to data minimization rules. Enterprises may want to add a clause to carrier agreements that limits the use of device identifiers to provisioning only and requires deletion after de‑provisioning. The OS‑level consent alone is not enough for compliance; it only governs the moment of transmission.

Helpdesk Training

Train support staff to recognize two scenarios:
1. The user has a carrier that supports web‑triggered activation. The helpdesk should guide the user to the carrier’s site and then through the Settings consent dialog.
2. The carrier does not support the web trigger. The user must be given the correct QR code or activation code, and staff should be ready to walk them through Settings > Cellular > Add an eSIM.

A quick way to check: if the carrier’s site shows a “Activate on this device” button for Windows, the trigger is live. If not, fall back to manual entry.

Carrier and OEM Perspectives

For carriers, Microsoft’s move is a double‑edged sword. They gain full control over the checkout experience, which is valuable for branding, bundling with other services, and upselling. But they must invest in developing a Windows‑friendly activation trigger. That trigger is essentially a web API call that hands off the EID/IMEI to the carrier’s backend and then interacts with Windows’ eSIM profile download service. Microsoft has published technical guidance, but development and testing will take time, especially for smaller operators with legacy billing systems.

OEMs that ship cellular‑enabled laptops—Lenovo, HP, Dell, Microsoft itself with the Surface Pro 9 and Surface Go lines—need to ensure their out‑of‑box experiences no longer launch or reference the Mobile Plans app. Many OEMs preload a “Cellular Setup” widget that launched the app; those must be updated or redirected to carrier landing pages. Failing to do so will lead to broken links and customer confusion after February 2026.

Privacy Pitfalls and Unresolved Questions

The new consent model is a net positive for user transparency, but two issues remain unresolved:

  • Data linkage risk. EID and IMEI are permanent, unique identifiers. If a carrier stores them alongside a user’s personal account information, that creates a very granular tracking profile. Privacy‑conscious users may prefer to use QR codes manually—which avoid sending identifiers to the carrier’s web platform entirely—even if the web‑triggered option is available.
  • Fragmented consent UX. In the Mobile Plans app, consent was requested once, inside a single interface. In the web model, a user consents twice: once to the carrier’s terms (during checkout) and once to the Windows identifier sharing. Users might not understand the difference and may inadvertently grant excessive permissions. Clear, plain‑language prompts are essential, and early Insider builds show Microsoft is working on that.

Support Scenarios and Troubleshooting

If a user can’t provision an eSIM after completing a web purchase, follow this quick checklist:

  • Confirm carrier support. Ask the user if they saw an “Activate on this Windows device” button. If not, the carrier hasn’t implemented the trigger yet. Get the QR/manual activation code and use Settings > Cellular > Add an eSIM.
  • Windows updates. The new Settings prompts require a specific Windows update. Run Windows Update and ensure the device is on the latest available build. Insider builds have it now; mainstream builds will get it before end of 2025.
  • Identifier mismatch. If the carrier can’t find the device after consent, verify that the IMEI/EID shown in Windows (Settings > About, or use netsh mbn show readyinfo interface=cellular) matches the documentation from the carrier. Sometimes factory‑reset devices show different values if eSIM profiles weren’t properly cleaned. Removing and re‑adding the profile often resolves it.

For enterprise devices, if the device doesn’t appear in the carrier’s management portal, ensure that the IMEI you provided during the bulk onboarding process is correct. Many carriers will accept a file upload; double‑check the format and leading zeros.

The Bigger Picture: Windows’ App Retirement Trend

Mobile Plans is the latest in a string of built‑in Windows apps that Microsoft has either removed or decoupled. 3D Viewer, Paint 3D, the People app, and the Legacy Mail & Calendar apps have all been retired in recent years. The common pattern: low engagement, high maintenance cost, and a desire to move functionality into Settings or the web. This strategy shrinks the Windows footprint, reduces security surface, and lets partners innovate independently.

For eSIM, the timing aligns with a growing fleet of connected Windows devices. Arm‑based Copilot+ PCs and Intel Evo‑certified laptops increasingly come with built‑in 5G modems. Microsoft wants to ensure that the provisioning stack is solid and carrier‑agnostic, and that it doesn’t hold back carrier innovation with a one‑size‑fits‑all app. Handing commerce to the web, while keeping provisioning native, is a calculated trade‑off that, if executed well, could make Windows cellular setup better than it ever was. The next 12 to 18 months will reveal whether carriers rise to the occasion or leave users stranded with QR codes.