Microsoft will pull the plug on its long-standing Mobile Plans app on February 27, 2026. The app will be removed from the Microsoft Store and cease all functionality on that date, officially ending the in-OS storefront that allowed Windows users to discover and purchase cellular data plans directly from their laptops and tablets. Instead, plan discovery and checkout will move entirely to mobile operators’ websites, while Windows Settings will take over secure eSIM provisioning and device-identifier consent.

The transition marks the culmination of a strategic shift Microsoft began signaling months ago. The company has already started testing the new activation flow with Windows Insiders, and carriers are expected to progressively roll out support through late 2025 and into 2026. Existing cellular profiles and modem drivers will remain unaffected—only the user interface for plan purchases is changing.

What the Mobile Plans App Was—and Why It’s Going Away

Mobile Plans arrived in Windows 10 as a convenience layer for Always Connected PCs: devices with embedded LTE or 5G modems. It provided a unified interface where users could browse participating operators, buy short-term data passes, and have eSIM profiles provisioned automatically—all without leaving the operating system. The app streamlined the discovery→checkout→provisioning funnel that had previously required QR codes or manual activation keys.

Behind the scenes, however, the arrangement created overlapping responsibilities. Carriers wanted full control over billing, refunds, identity verification, and SKU management—tasks that an in-OS storefront could never handle as flexibly as their own web portals. Microsoft, for its part, has long maintained the low-level plumbing to install and manage eSIMs through Windows Settings; preserving that provisioning capability while shedding the commerce layer reduces engineering overhead and avoids maintaining a user-facing store that competes with carrier channels.

The official line frames the change as a simplification. In a blog post quoted by TechRadar, Microsoft said it wants to “simplify how you connect your PC to mobile data,” emphasizing that users will still be able to link to mobile networks—just not through the old app. A “more integrated experience” is promised, with “just a direct link between Windows and your mobile operator’s website.”

The retirement does not mean Windows loses eSIM support. Instead, the purchase and subscription management piece moves to the browser, while Windows Settings becomes the gatekeeper for provisioning. The flow works like this:

  1. A user visits a carrier’s website on their Windows PC and selects a cellular plan.
  2. During checkout, the carrier offers to “Activate on this device.”
  3. Clicking that option triggers a secure Windows Settings prompt asking the user to share their device identifiers—specifically the EID (eUICC identifier) and IMEI—with the carrier.
  4. Once the user consents, the carrier’s backend server pushes an eSIM profile directly to the device’s embedded eUICC chip. No QR code, no activation code, no manual entry.

The entire process hinges on that consent prompt. It is the new touchpoint where the OS mediates between the user, the carrier’s web storefront, and the hardware. The relevant controls reside under Settings > Network & Internet > Cellular, where eSIM profiles have been managed for several Windows releases already.

Microsoft says the identifier-sharing function has been available to Windows Insiders for months and is expected to reach general availability before the end of 2025. The public rollout will depend partly on carrier enablement, which remains a work in progress.

Timeline: What’s Happening When

  • Windows Insider testing: Ongoing. The Settings-based provisioning flow is already in Insider channels.
  • Public availability: Microsoft targets the second half of 2025 for broad rollout of the new integration.
  • Mobile Plans app end-of-life: February 27, 2026. On that date, the app will stop working and be removed from the Microsoft Store.
  • Documentation updates: Microsoft promises to refresh its support articles and IT documentation ahead of the retirement.

These dates are drawn from multiple industry reports and Microsoft’s own communications. Enterprise administrators should treat February 27, 2026 as a hard operational deadline, but validate against official Message Center notifications and partner timelines.

Impact Analysis: Who Benefits and Who Bears the Friction

What Improves

  • Clearer responsibilities: Carriers own the entire customer relationship, from marketing to billing to refunds. They can iterate web portals faster than an in-app store.
  • Richer carrier experiences: Operators can implement custom bundling, identity verification, and cross-product offers without working around a limited OS app.
  • OS stays secure: Windows retains control over the actual eSIM installation, ensuring that only cryptographically signed profiles are loaded onto the device.

What Gets Worse

  • Fragmented user experience: Carrier websites vary dramatically in design, accessibility, and reliability. A user familiar with one operator’s flow may be lost on another’s.
  • Carrier readiness uncertainty: Smaller carriers and MVNOs may delay implementing the Windows-specific activation trigger. Users of those providers could be stuck with manual QR codes or activation codes indefinitely.
  • Privacy consent inconsistency: If some carriers support the Settings prompt while others require manual codes, the consent and data-sharing experience will differ, potentially confusing users and complicating compliance.
  • Enterprise operational friction: IT helpdesks that built scripts around the Mobile Plans UI will need to retrain staff and update MDM workflows. Some corporate provisioning scenarios might break entirely until carriers catch up.

Despite these risks, the change is unlikely to cause widespread connectivity outages. The cellular hardware in Windows devices remains fully functional; only the storefront changes. For occasional users who buy a data plan once or twice a year, the transition may be nearly invisible once carriers enable the new path.

Practical Checklist for Consumers and IT Admins

For Individual Users

  • Inventory every cellular-capable Windows device you own. Note the carrier, plan type, and expiration date.
  • While the Mobile Plans app still works, test any plan purchases you rely on. Save QR codes, activation keys, or carrier support pages as fallback references.
  • Visit your carrier’s website now and look for a dedicated eSIM activation page. Bookmark it.
  • If possible, perform a dry-run purchase on a spare device to confirm the carrier’s flow.
  • If your carrier doesn’t document a Windows-specific process, contact their support and ask whether they plan to support the Settings-based provisioning and when.

For IT Administrators

  • Audit your fleet for devices that have ever used the Mobile Plans app. List the users who depend on cellular connectivity for critical work (sales, field engineers, journalists).
  • Update helpdesk scripts and knowledge base articles to include carrier web activation steps, QR fallback procedures, and the exact Settings path for eSIM management.
  • Test the new flow on corporate images, especially those with custom OEM drivers or security software, to surface compatibility issues early.
  • If you use Intune or another MDM, check whether any enrollment profiles reference the Mobile Plans app. Adjust automation accordingly. Consider bulk activation paths if your carrier supports them.
  • Communicate timelines to affected users. Arrange a migration window before the February 2026 deadline so high-priority personnel aren’t caught off guard.

Fallback Options

  • QR codes and manual activation codes remain universally supported fallbacks. Save them in a secure vault for quick retrieval.
  • In a pinch, tethering to a phone hotspot or inserting a physical SIM from a local prepaid provider can provide immediate connectivity while you sort out carrier activation.
  • For enterprise devices, keep a small stock of corporate-issued mobile hotspots or spare SIMs for critical failover until carrier readiness is confirmed.

Carrier Readiness: The Big Unknown

For the new activation model to work smoothly, mobile operators must add two capabilities to their web portals:

  1. A “Windows activation” trigger that invokes the Settings consent prompt during checkout.
  2. Backend integration to map the checkout session to the device’s EID/IMEI and push the eSIM profile via Microsoft’s provisioning endpoints.

Microsoft has published technical guidance for partners and ran early trials with “select partners” starting in June 2025. However, the company declined to name which carriers are already participating. This opacity means real-world support will be staggered: Tier-1 operators in North America and Western Europe are likely to move first, while smaller MVNOs and regional carriers may drag their feet.

Users and admins should expect a patchwork landscape throughout 2026. Some carriers will offer seamless, one-click activation through the browser; others will still ask you to type an activation code or scan a QR code. The worst-case scenario is a carrier that stops supporting Windows entirely if they deem the integration too costly—though most operators that already supported the Mobile Plans app have an incentive to preserve the revenue stream.

Security, Privacy, and Compliance

The new consent prompt places Windows squarely in the middle of sensitive identifier exchange. When a user agrees to share their EID and IMEI, those identifiers travel from the device’s modem to the carrier’s provisioning server. Several privacy and security implications merit attention:

  • Consent transparency: Administrators and privacy officers should verify exactly what language the Settings prompt displays. Is it clear that the identifiers will be used only for eSIM provisioning and not for tracking?
  • Data minimization: Carriers should request only the identifiers necessary to install the profile. Enterprises should ask carriers for a data flow diagram and retention policy covering EID/IMEI exchange.
  • Regulatory compliance: In jurisdictions with strict subscriber-data laws, confirm that the Settings flow complies with local regulations. Involve legal and compliance teams early.
  • Secure channels: Microsoft already requires HTTPS for eSIM provisioning traffic, but organizations may want to audit endpoints and ensure the carrier’s backend meets their security posture.

What Microsoft Is Saying—and Not Saying

Public messaging emphasizes simplicity and continuity. “Your existing cellular connections will continue to work,” promises the TechRadar article, “but you’ll use the operator’s website to manage your plan.” Microsoft also assures that documentation will be updated and that the Settings integration will be ready well before the app’s removal.

Behind the scenes, the decision shines a light on the economics of maintaining an in-OS storefront that reaches a niche audience. The number of Always Connected PC users who actually purchased plans through the app was likely small, and the engineering effort required to keep the app compatible with evolving carrier APIs was disproportionate. By offloading commerce to the web and focusing on the core provisioning protocol, Microsoft can still claim Windows offers “seamless cellular connectivity” without shouldering the full user experience burden.

Final Recommendations

The Mobile Plans retirement is not a catastrophe, but it is a planned migration that demands proactive preparation. Begin with a simple inventory and test carrier flows now, while the old app still provides a safety net. Update documentation, train helpdesk staff, and push your carrier for a clear timeline on supporting the new Settings-based provisioning. For most users, the transition will be a UI shuffle rather than a connectivity loss—provided carriers, OEMs, and IT teams do their homework before February 2026.

Treat this as an opportunity to harden your failover strategies, audit your cellular procurement practices, and build stronger relationships with your mobile operators. The underlying eSIM technology isn’t going anywhere; only the storefront is changing.