Microsoft began the worldwide rollout of its merged Copilot app on 18 August, combining the consumer and Microsoft 365 Copilot apps into a single product simply called Microsoft Copilot. The commercial web address is moving from m365.cloud.microsoft to the new copilot.cloud.microsoft, with automatic redirects arriving in the next couple of weeks. At the same time, three features started retiring on the same day: Group Chat, Podcasts, and Deep Research.

We flagged this merger back in July as something worth preparing for. It’s now actually happening, and the practical question for UK businesses has shifted from “what should I check before this lands” to “what’s different right now.”

What’s actually changing for your business

The headline change is that staff will sign into one app rather than two, using a personal account, a work or school account, or both, and switching between them inside the same interface. Microsoft says data doesn’t flow between personal and work contexts, employers can’t see personal activity, and enterprise security, compliance, and admin controls carry over unchanged. That’s the claim — it’s worth treating it as something to verify against your own tenant settings rather than take on trust, particularly if any of your Copilot usage touches client data or anything covered by a data processing agreement.

The more immediate issue is the feature retirements. If any team has built a workflow around Group Chat, Podcasts, or Deep Research inside Copilot, that workflow needs a replacement now, not eventually. These aren’t being paused for review — Microsoft has started the retirement process as of the same date the new app began rolling out.

Three things to check this week

Check what’s actually rolled out to your tenant. The worldwide rollout is landing in phases across mobile, web, and desktop, with early-access opt-in for Windows and Mac apps still ramping up. Don’t assume every user in your organisation is on the same version — check the admin centre for your tenant’s actual status before you brief staff on what’s changed.

Audit use of the three retiring features before staff notice they’re gone. A quick message to team leads asking “does anyone use Copilot’s Group Chat, Podcasts, or Deep Research features” is cheap insurance against a workflow quietly breaking mid-project. If someone does rely on one of these, you have a short window to find or build an alternative.

Re-confirm data-handling settings once the merged app lands on your tenant. Consumer and enterprise app merges have a track record of resetting or softening default permissions during transition. If your Copilot deployment touches customer or financial data, get written confirmation — from Microsoft’s own documentation for your tenant, or from your IT partner — that nothing shifted in the move.

If you want a straight answer on whether your current AI tooling is actually earning its keep versus just being “the thing that shipped with Microsoft 365,” BuildApps works with UK SMEs on exactly that kind of review. And if the merged app’s new permission model needs a technical once-over before you trust it with sensitive workflows, CoolCoding can check the implementation rather than the marketing claims.

The takeaway

A product merger that was still a forecast in July is now live, with real, dated feature cuts attached. The businesses that come out of this cleanly are the ones checking their actual tenant status and retired-feature exposure this week, not the ones assuming Microsoft’s rollout notes cover their specific setup. Don’t wait for the redirect to force the issue — go and look now.