Microsoft Merges Its Copilot Apps Into One and Retires Three Features: What It Means for Your Business

What exactly did Microsoft announce?

In mid-August 2026 Microsoft began merging two apps that used to be separate: the consumer Copilot app people use with a personal Microsoft account, and the Microsoft 365 Copilot app built for work accounts. They are now a single app that keeps the Microsoft Copilot name, ships with a new icon, and lets you move between your work account and your personal account through an account switcher inside the same shell. Alongside the merge, three features are retired permanently on August 18, 2026: Podcasts, Group Chat, and Deep Research in the consumer experience.

The announced schedule starts with mobile and web worldwide in mid-August, with the Windows and Mac apps following in mid-September 2026. Most updates happen automatically with no action from the user, and that is exactly why this matters to any company that uses Copilot in daily work: the change reaches your employees whether you prepared for it or not.

Work and personal separation: the part your IT lead cares about

The first question any technology manager asks when a personal app merges with a work app is about data. The official answer is clear: personal accounts (Microsoft account) and work accounts (Microsoft Entra) remain distinct by design, data entered into the work experience does not flow into the personal experience or the other way around, and your organization's controls continue to apply to the work account exactly as before.

Technical separation is one thing and human behaviour is another. Once both accounts live in one app behind a simple switcher, the odds rise that an employee pastes an internal document or customer data into the wrong surface without noticing. That is not a product flaw; it is an interface change that deserves a short internal reminder: anything belonging to the company is handled from the work account only. One message to the team channel is enough, but it needs to go out before the update lands, not after.

The three retired features and what happens to their content

• Podcasts: gone after August 18, 2026, with no way to create new episodes or reach existing ones. Anyone who used it to turn training material or summaries into audio should download what they want to keep before the date.
• Group Chat: group threads become individual chats, and the messages and images created inside them are not carried forward. Microsoft's explicit guidance is to download any media shared by other participants that you want to keep.
• Deep Research: retired in the consumer experience. Users on professional subscriptions have Researcher available inside the work experience instead.

The rest of your content moves across: chat history, images and content you created, and files that lived in the standalone app move to OneDrive. Content tied to the retired features specifically is handled differently, and that is the piece that needs action from you within days rather than weeks.

The real lesson: never build an operational process inside a feature

On its own this is an ordinary product update. What matters more is the pattern it exposes, and that pattern has repeated more than once this year across more than one vendor: a feature appears, your team adopts it, it works its way into the weekly routine, and then it disappears on a few days' notice because its global usage numbers did not convince its owner to keep it alive.

A Microsoft executive said the app needed to earn the right to exist by removing underperforming features. From Microsoft's seat that is sound product discipline. From your seat as a business owner it means one thing: the feature you rely on is not a contract, and the measure of its survival is how millions of users worldwide behave, not how much you need it.

The practical rule: if a step in one of your operational processes depends entirely on a feature inside a third-party app, you do not own that process — you rent it on terms that can change at any time.

How to tell what can stay in an off-the-shelf tool and what belongs in a system you own

The answer is not to build everything in-house; that is waste. The answer is deliberate classification. Ask three questions about every use of AI in your company:

• Would an operational process stop if the feature vanished tomorrow? If yes, its natural home is a system you own, not a feature in a general-purpose app.
• Are the outputs stored with you or only inside the tool? Whatever you cannot export today in one click may be unrecoverable tomorrow.
• Do you know who actually depends on it? Most companies discover that a whole team relied on a small tool only on the day it shuts down.

Assistive uses such as drafting a message, summarizing a meeting, or generating an image can stay in off-the-shelf tools without worry: alternatives are plentiful and switching costs nothing. But anything that has moved into the core of your business — triaging customer requests, classifying complaints, extracting invoice data, feeding your reports — needs a system with a stable API and data sitting in your own database.

An execution checklist before August 18

• Send an internal notice today: anyone using Podcasts or Group Chat in Copilot should download what they need immediately.
• Ask your teams one direct question — is there a weekly step in your work that depends on any of the three retired features? Then fix whatever surfaces.
• Remind employees of the two-account rule after the merge: company content is handled from the work account only.
• Review the mid-September rollout for Windows and Mac with your IT team so nobody is caught off guard.
• Write a short list of every AI tool your operations depend on, and answer for each one: what happens if it disappears next week?

The Origami view

We see this often with clients: a team builds an excellent working habit around a free feature or one bundled into an existing subscription, then finds itself without a plan the day it changes. Our position does not move — off-the-shelf tools are excellent for experimentation and assistive tasks, but anything touching your revenue cycle or your customer service should live in a system whose data and logic you own.

In practice that means every AI model call passes through an internal layer in your system, outputs are stored in your database rather than in a chat log at a vendor, and switching a model or a provider is a configuration decision rather than a rebuild project. Companies that work this way read news like today's as information, not as an operational crisis to solve in three days.

Sources

• Microsoft Support — updates to Copilot and the Microsoft Copilot app, including retired features: support.microsoft.com
• Microsoft Support — frequently asked questions about retired Copilot features: support.microsoft.com
• TechCrunch — Microsoft kills off features while merging its Copilot apps, August 13, 2026: techcrunch.com