Microsoft's unified Copilot desktop app rolls out to commercial customers from mid-September 2026
The single Copilot app merging consumer and M365 Copilot hits Windows and Mac from mid-September 2026. Here's what IT admins need to do now.
For the past two years, Microsoft shipped two separate Copilot apps that could sit side by side in the same taskbar: the consumer-facing Microsoft Copilot and the enterprise-focused Microsoft 365 Copilot. From mid-September 2026, that duplication ends. A single, unified Copilot desktop application replaces both, and if your organisation runs managed Windows or Mac devices, there are things you need to do before that happens automatically.
What’s actually changing
The new unified app is a Chromium-based desktop client that handles both personal Microsoft accounts and work or school Microsoft Entra ID accounts from a single interface. Users switch between the two using an account switcher in the navigation pane. A different background colour and a “Work” label under the profile icon help distinguish the contexts visually. Data from a personal account does not flow into the work account experience, and vice versa.
The app takes the simpler name “Microsoft Copilot” with a refreshed icon. Security, compliance, privacy, and enterprise controls carry over unchanged. The application ID is not changing, so existing policies continue to work.
The rollout timeline
The mobile and web versions began their worldwide rollout in mid-August 2026, and an early-access opt-in opened at the same time for Windows and Mac. The broader Windows and Mac rollout begins mid-September 2026. A deferred URL redirect for the web app follows in late September 2026.
Microsoft 365 Apps version 2511 or later is a prerequisite for automatic installation. Once a device reaches that version, the install or upgrade to the unified Copilot app can take up to seven days to occur.
What’s being retired
Three features do not survive the transition, and users should act before 18 August 2026 if they want to preserve anything:
- Group Chat threads, messages, and images created in Group Chats will not carry forward. Users should copy messages and download images before that date.
- Podcasts in Copilot is being retired entirely. Users will not be able to create or access Podcasts after 18 August 2026.
- Deep Research is being retired from the consumer Copilot app from 18 August 2026.
These retirements affect the consumer side of the experience. Enterprise Deep Research capabilities within Microsoft 365 Copilot are a separate matter.
What IT admins need to do before mid-September 2026
This is where the practical preparation sits. Microsoft has published a detailed deployment guide on Microsoft Learn, and the steps below are drawn from that.
Check your network allowlist. The unified app uses copilot.cloud.microsoft as its primary endpoint. If that domain is blocked in your environment, the app will not function. Review your allowlist against the Microsoft Copilot network requirements documentation before the rollout reaches your devices.
Verify EdgeUpdate is current. The unification mechanism is managed by EdgeUpdate, not the Microsoft Store. Devices need EdgeUpdate version 1.3.253.25 or higher. Apps installed via the Microsoft Store are not managed by this mechanism and will not receive the update through this route.
Configure the CopilotUnificationAllowed policy. This Group Policy setting (found at Administrative Templates/Microsoft Edge Update/Microsoft Copilot, ADMX file copilotupdate.admx) controls whether devices update on your schedule or on Microsoft’s standard rollout cadence. Setting it to 1 triggers unification at the next automatic EdgeUpdate check. Setting it to 0 or leaving it unconfigured means devices update according to the standard rollout. The policy only applies to Windows devices joined to an Active Directory domain, and it requires the Updater Experimentation And Configuration Service Control policy to be enabled.
For devices without any Copilot app installed, set the EdgeUpdate Install policy to Force Installs rather than relying on the unification path.
Deployment tooling. Microsoft supports deployment via Intune, Configuration Manager (Package or Application), Group Policy, or third-party management tools. The full deployment guide covers each option.
Two groups are excluded from automatic installation. Organisations in the European Economic Area will not have the Copilot app automatically installed to devices via Microsoft 365 Apps. Devices on the Semi-Annual Enterprise Channel are also excluded from the automatic install path.
What this means for your users
For most end users, the change will be transparent. They open Copilot, it looks slightly different, and they can see both their personal and work accounts in one place. The account switcher makes context switching explicit rather than requiring two separate apps.
The groups most likely to notice a disruption are those who have been using Group Chat or Podcasts features. If your organisation has users actively relying on either, it is worth a proactive communication before mid-August 2026 rather than after.
The bigger picture
Microsoft has signalled that this unification is a structural step toward a broader “super app” combining Copilot Chat, GitHub Copilot, Copilot Cowork, and AutoPilot agents into a single application, with Satya Nadella referencing an end-of-September 2026 target on the FY26 Q4 earnings call. The desktop app consolidation arriving now is the foundation for that, not the finished product.
For IT admins, the immediate priority is straightforward: check the network allowlist, confirm EdgeUpdate is at the right version, and decide whether you want to control the update timing through the CopilotUnificationAllowed policy or let the standard rollout handle it. The Microsoft Learn deployment guide is the definitive reference for working through each step.