Microsoft has stopped the clock on Ubuntu 22.04 LTS for Intune-managed Linux devices. In a quiet documentation update on April 27, 2026, the company confirmed that support for the aging release will end in August 2026. After that point, Ubuntu 22.04 desktops enrolled in Intune will be outside the official support boundary, leaving administrators with a hard deadline to move devices to a supported version—most likely Ubuntu 24.04 LTS.

The announcement, first spotted by the WindowsForum community and confirmed by Microsoft’s own Linux enrollment guide, gives organizations only a few months to inventory, validate, and upgrade affected endpoints. The road is narrower than many realize: it’s not simply an OS upgrade but a full identity, compliance, and access management project that risks breaking Conditional Access if handled poorly.

What Exactly Is Changing

Microsoft’s updated Intune Linux enrollment guidance now lists only two supported Ubuntu Desktop releases: Ubuntu 24.04 LTS and Ubuntu 26.04 LTS, both running on x86/64 hardware with the GNOME graphical environment. Ubuntu 22.04 LTS, which has been a mainstay for Linux management in Intune, is officially deprecated. The change does not affect Ubuntu Server deployments, which were never supported for Intune enrollment.

During the deprecation period—between the April announcement and the August cutoff—devices already enrolled with Ubuntu 22.04 will continue to function and receive policy updates. But Microsoft is telling administrators to notify affected users and begin moving them to a supported release. After August 2026, no further testing, updates, or support guarantees will apply to those devices. The exact date in August hasn’t been specified, nor has Microsoft detailed any automatic enforcement action, such as blocking access or removing devices.

A critical technical detail that complicates this migration: the Microsoft Identity Broker, which ships with version 2.0.2 and later of the Intune app for Linux, handles re‑registration and re‑enrollment differently from earlier versions. When a device goes through this process—whether during an in-place upgrade or a fresh enroll—it may receive a new Intune device ID and a new Microsoft Entra device ID. This means that even though the hardware and user remain the same, the management‑plane identity changes. Any group memberships, conditional access policies, filters, or automation workflows that rely on the old device ID can silently break.

What the Deadline Means for You

For IT Administrators

The August 2026 deadline transforms Ubuntu 22.04 migration from a background task into an immediate project. You need to:

  • Inventory every Ubuntu 22.04 device enrolled in Intune. Rely on Intune’s reporting and export features to build a full list, but verify the data first—operating system fields aren’t always uniform across tenants.
  • Decide on a target release. For the vast majority of devices, Ubuntu 24.04 LTS is the safe, low-risk default. It has been in the field long enough for hardware, driver, and application ecosystems to stabilize. Reserve Ubuntu 26.04 LTS only for devices that have completed a full validation cycle covering business applications, VPN clients, certificate workflows, endpoint security tools, and post‑enrollment Conditional Access behavior.
  • Plan for identity reconciliation. Because the migration can generate new device IDs, you must map old and new IDs and update any local dependencies—assignments, exception records, integration scripts—to reference the new objects. Otherwise, you risk creating “zombie” devices that appear healthy but fail behind the scenes.

For End Users

Users may experience a short maintenance window during the upgrade. They should expect to back up local data, log in again with their organizational account during enrollment, and verify that key applications (including Microsoft Edge, VPN, and line-of-business tools) work correctly afterward. If your organization uses smart cards, certificates, or custom peripheral drivers, those workflows need especially careful post‑migration testing.

For Developers and Linux Workstation Power Users

If you run Ubuntu 22.04 on a developer workstation enrolled in Intune, you have a few extra concerns. Custom toolchains, container runtimes, and locally compiled applications may behave differently on Ubuntu 24.04’s newer kernel and libraries. Docker, Podman, and other development environments should be validated early. Additionally, the enrollment flow itself requires the Microsoft Intune app for Linux and Microsoft Edge browser version 102.x or later—both must be installed and working before the device can be re‑managed.

How We Got Here

Microsoft’s tightening of Ubuntu support isn’t happening in a vacuum. Intune for Linux first arrived as a public preview in 2022, initially supporting only Ubuntu 20.04 LTS and 22.04 LTS. Since then, the service has matured, adding Conditional Access, compliance policies, and tighter integration with Microsoft Entra. But just as with Windows and macOS, Microsoft is following a predictable pattern: drop older operating system releases to focus testing and engineering resources on current versions.

Canonical’s own support lifecycle plays a role, too. Ubuntu 22.04 LTS receives standard support until April 2027 (with Extended Security Maintenance available beyond that through an Ubuntu Pro subscription). However, Microsoft isn’t bound by Canonical’s timeline. The August 2026 cutoff lets Intune sunset 22.04 well before Canonical’s own end of standard support, similar to what’s happening with Red Hat Enterprise Linux 8, which Intune will drop in July 2026.

The context here is enterprise endpoint management convergence. More organizations are bringing Linux desktops under the same identity‑aware, zero‑trust umbrella as Windows and Mac. That means the OS platform isn’t just a convenience layer anymore—it’s a critical node in the security architecture. Old OSes with unpatched attack surfaces simply don’t fit the model.

Your Migration Game Plan

A successful migration is more than an apt dist-upgrade. It’s a sequenced project with clear checkpoints. Here’s how to structure the work.

1. Inventory and Classify Devices

Start by exporting your Intune device inventory. Filter for Ubuntu 22.04 endpoints. For each, record:

  • Device name, serial number, and asset tag
  • Primary user and business owner
  • Last check‑in timestamp and compliance status
  • Device role (productivity, engineering, kiosk, admin workstation)
  • Current managed device ID and Entra device ID

Sort the list into three buckets:

  • Active devices that are syncing regularly—schedule these into migration waves.
  • Stale or inactive devices that haven’t checked in for weeks—decide whether they’re retired, reassigned, or just abandoned.
  • Specialized devices with unique hardware or software that need extra testing before migration.

2. Choose Your Target: 24.04 vs. 26.04

For most organizations, Ubuntu 24.04 LTS is the default choice. It has been a supported Intune target for over a year, and the ecosystem of third‑party drivers, VPN clients, and endpoint security agents is well established.

Reserve Ubuntu 26.04 LTS for devices that pass an explicit “pilot” gate: hardware must be certified, all business applications validated, security agents and VPN tooling confirmed, and post‑enrollment Conditional Access behavior tested. Until every box is checked, stick with 24.04.

3. Pre‑Migration Checklist per Device

Before touching the operating system, complete these steps for every device:

  • Confirm the device is an x86/64 Ubuntu Desktop system running GNOME.
  • Capture the existing Intune device ID and Entra device ID; store both in your migration register.
  • Verify the user, asset owner, and support contact.
  • Ensure user data is backed up and restorable.
  • List every required application, VPN, certificate, smart card, printer, driver, and security tool.
  • Document all compliance policies, configuration profiles, and Conditional Access rules that apply.
  • Identify any automation scripts or group memberships that reference the current device object.
  • Obtain the organization’s approved upgrade or rebuild procedure (in‑place upgrade or clean image).
  • Schedule a maintenance window and inform the user.

4. Execute the Upgrade

If your organization permits in‑place upgrades, follow these baseline steps (always follow your own internal change‑control procedures):

  1. Log in locally with an authorized account.
  2. Apply all current updates: sudo apt update && sudo apt full-upgrade and reboot if needed.
  3. Launch the release upgrade: sudo do-release-upgrade and follow interactive prompts.
  4. Watch for warnings about third‑party repositories or unmanaged packages—pause if anything critical appears untested.
  5. After the upgrade completes and the system reboots, verify the new OS: cat /etc/os-release.
  6. Test local functionality: user login, network, disk access, apps, VPN, certificates, peripherals.
  7. Install or update the Microsoft Intune app for Linux and Microsoft Edge (version 102.x+), then enroll with the user’s organizational credentials.
  8. Proceed to identity reconciliation.

For a clean rebuild, replace steps 1‑4 with deployment of your approved Ubuntu 24.04 image and restoration of user data, then continue with enrollment.

Important: Ubuntu running under WSL2 is not a supported enrollment scenario. Do not attempt to migrate Intune-managed desktop workloads to a WSL2 instance.

5. Post‑Enrollment Identity Reconciliation

Once the device is enrolled, you must validate that the new identity works correctly with all management and security systems. This is the most commonly overlooked step, and the one that generates help desk calls.

  • Confirm the new device record appears in Intune and is associated with the correct user.
  • Record the new Intune device ID and Entra device ID in your migration register.
  • Compare old and new IDs and keep a mapping for audit.
  • Check that the device receives the expected compliance and configuration policies.
  • Wait for the device to report its compliance state, then verify it accurately.
  • Test the user’s normal access path to protected resources through Microsoft Edge.
  • Test VPN, certificate‑based authentication, smart‑card logins, and endpoint security tooling.
  • Update any local inventory integrations, automation, or group memberships that referenced the old device ID.
  • Before retiring the old device record, confirm that Conditional Access conditions (like “require compliant device” or “require hybrid joined”) fire correctly against the new device.
  • Only after all checks pass should you clean up the old management record.

Looking Ahead

Microsoft has grown more disciplined about publishing deprecation timelines, but the lack of a specific August date means organizations should treat the entire month as a hard finish line. Don’t bank on a grace period. While the company hasn’t said it will automatically block or remove Ubuntu 22.04 devices on day one, any support request, policy processing failure, or enrollment quirk will be handled from an unsupported starting point—a position no enterprise wants.

Longer term, this deprecation cadence hints at a 24‑month managed life for Ubuntu LTS releases inside Intune. If that pattern holds, Ubuntu 24.04 LTS might face its own sunset around mid‑2028, giving organizations a planning horizon. In the meantime, the August 2026 deadline is a forcing function: get your Linux fleet onto a supported, tested, and identity‑verified foundation, and keep Ubuntu 26.04 as a deliberate, controlled rollout for the devices that can truly handle it.