Microsoft has officially begun rolling out the unified Copilot app, merging the previously separate consumer and Microsoft 365 Copilot experiences into a single application. First confirmed back in May, this strategic shift aims to eliminate the friction of switching between two distinct AI assistants depending on whether you are handling personal tasks or productivity work. According to a newly published Microsoft Support document, the company is updating Copilot to create a simpler, more cohesive experience for everyone, with changes to appearance, navigation, and sign-in flows depending on your account type.
What Is Changing in the Unified Copilot App
For years, Microsoft maintained a clear divide between its consumer-grade Copilot and the commercial Microsoft 365 Copilot. One lived in your personal Microsoft account, while the other sat behind an enterprise license. That boundary is now dissolving. When the unified experience lands on your device, both account types will be accessible within the same interface, though Microsoft emphasizes that work and personal accounts remain strictly separate. Data from your organization will not cross over into your personal profile, and vice versa. Your organization’s security, privacy, compliance, and administrative controls will continue to apply when you use Copilot with a work or school account.
Visually, the consumer-facing version of the app will adopt a UI that more closely mirrors the Microsoft 365 Copilot layout. Users of the commercial app will notice minimal visual changes, aside from the app being rebranded to simply “Copilot” and receiving a slightly refreshed icon. Microsoft has shared the updated branding, which retains the familiar visual language while streamlining the logo for cross-platform consistency.

On the backend, the unification also standardizes how the app handles authentication and feature availability. Depending on your account and device, you will see adjustments to navigation, feature availability, or the sign-in experience. Microsoft confirmed that all existing Copilot data will migrate automatically to the new experience, meaning your chat history, saved prompts, and personalized settings will carry over without requiring manual intervention. The only exceptions are the features being officially retired, which will be phased out on August 18, 2026.
Features Being Retired
Unifying two separate apps inevitably means some overlap must be cut. Microsoft has outlined three specific features that will no longer be available after August 18, 2026. Group Chat is being fully deprecated, meaning all group chat threads, messages, and shared images will not carry forward. Users are advised to manually copy or download any content they want to preserve before the cutoff date.
The Podcasts feature is also being completely retired on the same date. After August 18, 2026, you will no longer be able to create or access podcasts within Copilot. Individual podcast files can still be downloaded ahead of the retirement, but the discovery and playback functionality will be removed entirely.
Deep Research is being retired specifically for consumer users starting August 18, 2026. While existing Deep Research content will remain accessible for review, the feature itself will no longer be available for generating new reports. For enterprise users, Microsoft has not indicated that this capability will be removed, suggesting the retirement is tied to the consumer app’s scope rather than the underlying AI model.
How the Rollout Is Scheduled
The unified Copilot app is not launching everywhere at once. Microsoft is deploying the update in waves to manage server load and gather feedback from early adopters. Worldwide rollout for mobile and web apps begins today, with an early-access opt-in opening for Windows and Mac apps in the coming weeks.
The full deployment timeline breaks down as follows:
- Mid‑August 2026 — Worldwide rollout begins for mobile and web apps; early‑access opt‑in opens for Windows and Mac apps; copilot.cloud.microsoft URL available in Frontier for testing.
- Late August 2026 — Standard rollout of the URL redirect begins.
- Mid‑September 2026 — Worldwide rollout begins for Windows and Mac apps.
- Late September 2026 — Deferred rollout of the URL redirect begins for the web app.

For IT administrators and power users, the phased approach means the copilot.cloud.microsoft URL will serve as the primary access point during testing. The standard URL redirect will eventually replace legacy endpoints, streamlining how users reach the unified experience across browsers.
What This Means for You
If you regularly switch between personal AI assistance and productivity tools, this unification removes a long-standing friction point. You will no longer need to juggle two separate apps or wonder which Copilot instance holds your recent context. The strict separation of work and personal data also addresses a common enterprise concern, ensuring that organizational policies remain intact even as the consumer and commercial surfaces merge.
However, the August 18, 2026 retirement date for Group Chat, Podcasts, and consumer Deep Research requires attention. If you rely on these features for workflow automation or content archiving, you will need to export your data before the deadline. Microsoft’s decision to retire Deep Research for consumers while keeping it for enterprise users also signals a clear monetization strategy: advanced research capabilities will remain a premium commercial feature.
How to Get It
Mobile and web users will receive the unified experience automatically as Microsoft rolls it out worldwide. Desktop users on Windows and macOS will need to opt into the early-access program when it opens in mid-August, or wait for the standard mid-September deployment. You can monitor the official Microsoft Support page for the latest availability status and update your Copilot app through your device’s standard app store or Windows Update settings.
Source: Latest from Windows Central
Over to you: Are you glad to see the consumer and M365 Copilot apps finally merging, or do you prefer keeping them strictly separate?



