Hey You

Microsoft did it again… I was casually going through Microsoft Learn… you know… minding my own business when I saw this:

The Microsoft 365 Copilot app is now called Microsoft Copilot

Okay… Wait… Didn’t we already have an app called Microsoft Copilot?

Yes… Yup… we did. 

For the last couple of years Microsoft has been creating Copilots faster then I can keep track of them..

• Microsoft Copilot
• Microsoft 365 Copilot
• Copilot Chat
• Github Copilot
• Security Copilot
• Copilot Studio
• Copilot in Windows
• Copilot in Edge
• Copilot in probably my refrigerator somewhere…

(thank God they removed it from X-Box)

And now… Microsoft is doing something tat ACTUALLY MAKES SENSE.

They are briging the Microsoft Copilot and Microsoft 365 Copilot applications together into one unified Microsoft Copilot app.

FINALLY!

But…

Because… why the fuck not… of course there’s a “but”.

If you manage Windows devices there are a couple of things you probably want to know before the broad rollouts starts in September 2026.

So… let’s take a look…

So… what exactly is being unified?

Until now… we basically had 2 different worlds.

Microsoft Copilot – Mostly associated with the personal Microsoft account experience. And: Microsoft 365 Copilot

The work and school experience using Microsoft Entra ID.

Microsoft is now moving towards a single Microsoft Copilot client that can handle both. The account you sign in with determines the experience you get.

Personal Microsoft account? => Personal Copilot experience

Microsoft Entra ID account? => Work or school Copilot experience

And yes… users will be able to switch between them inside the same application.

Before every Security Officer reading this article has a small heart attack… Relax… Microsoft says that data entered in the personal Microsoft Account experience doesn’t flow into the work or school experience and vice versa.

There are also visual indicators.

When you’re signed in with your work accounts, for example, the application shows that you’re using the Work experience.

That is actually important. Because if we’re putting personal and corporate AI experiences inside the same application users REALLY need to know which one they’re using.

Trust me… (because I’m the one guy you should? IDK… just go with it okay?)

Somebody WILL paste company information in the wrong windows. We all did it… you know why?

Because… … users!

So… what’s changing?

Starting August 18th 2026 Microsoft started introducing updates across the web, desktop and mobile Copilot experiences.

The obvious changes are:

• One Microsoft Copilot name
• A simplified icon
• Better indicators for personal versus work accounts
• One client experience
• An account switcher
• New deployment and update controls for administrators

But… there is another change that I think administrators should REALLY REALLY REALLY pay attention to…

The URL.

The Microsoft 365 Copilot web experience is moving from:

https://m365.cloud.microsoft

to:

https://copilot.cloud.microsoft

Now… normally your browser will simply redirect the user… Great… unless…

1. Your proxy says no
2. Your firewall says no
3. Your Secure Web Gateways says no
4. Your allowlist says:

WHO ARE YOU AND WHY ARE YOU TRYING TO ACCESS MY NETWORK?

If copilot.cloud.microsoft is blocked in your environment… congratulations…

You may have just created a future Service Desk ticket.

September is where things get interesting.

We’re currently in the initial availability phase. Microsoft says the broad commercial rollout starts in September 2026.

That means RIGHT NOW is actually the perfect time to test this… not September… not when 4000 users suddenly have a different Copilot application. Not when your Service Desk starts asking you why everyone’s Copilot looks different.

NOW!

Microsoft gives organizations controls to test the unified application before the broad rollout. This is where things get interesting for us Endpoint people.

Microsoft Edge Update enters the chat

Plot twist… dun dun dun!!!!

The deployment mechanism heavily relies on Microsoft Edge Update… yes… EDGE UPDATE. Because apparently Edge Update looked at copilot and said:

Fuck yeah… I can manage that too!!!

For windows devices Microsoft currently requires Microsoft Edge Update 1.3.253.25 or higher. You can quickly check your version with Powershell:

(Get-Item "${env:ProgramFiles(x86)}\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe").VersionInfo.ProductVersion

If you’re below 1.3.253.25 fix that before spending three hours troubleshooting why the Copilot policies don’t work.

Future you will thank you!

New Copilot update policies

Microsoft also introduced specific Edge Update policies for Microsoft Copilot. At the moment these include:

• Install
• Update
• Uninstall
• TargetChannel
• CopilotUnificationAllowed

The last one… yeah… that is the interesting one… CopilotUnificationAllowed.

I’m pretty sure whoever named that policy gets paid per character.

The policy allows Microsoft Edge Update to unify the existing Microsoft Copilot and Microsoft 365 Copilot applications. For devices that already have one of the Copilot applications installed Microsoft says you can enable:

CopilotUnificationAllowed = 1

… to test the unified experience before the broad rollout. The registry location behind the policy is:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\EdgeUpdate

… with:

CopilotUnificationAllowed{C50565E9-CCCF-44B4-BA15-5AC5C6569197}

… as a REG_DWORD. Value: 1

Now… Before someone copies this registry key… creates an intune remediation… asigns it to ALL DEVICES and then blame me when 30000 computers explode…

Don’t…

Pilot…

Test…

Validate…

Then deploy… for the love of Cthulhu…

What if Copilot isn’t installed yet?

Well… Microsoft actually has thought about that too. There is an Install policy specifically for Copilot. If the application isn’t installed yet you can configure the Install policy as:

Fore Installs (Machine-Wide)

Which equals:

5

The registry value is:

Install{C50565E9-CCCF-44B4-BA15-5AC5C6569197}

under:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\EdgeUpdate

But there’s another requirement. Microsoft says you also need to enable Updater Experimentation and Configuration Service Control

That policy name sounds less like a Windows setting and a more like something Tony Stark would use to accidentally create Ultron.

What if I do nothing?

You can… Microsoft will progressively roll out the unified application to eligible devices… and… maybe that’s perfectly fine for your organization… but… there’s a difference between

We tested it and decided to let Microsoft handle the rollout

… and …

Wait… Microsoft changed Copilot?

Me… I prefer the first one.

One thing for European organizations

There is also an important distinction for organizations in the European Economic Area. Microsoft previously introduced automatic deployment of the Microsoft 365 Copilot app through Microsoft 365 Apps, but that automatic installation isn’t enabled for EEA customers.

That doesn’t mean you can’t deploy Copilot. You can still deploy it yourself, for example through Intune. Just don’t confuse automatic installation of Copilot with the unification of an existing Copilot installation.

They’re related changes, but they’re not the same thing.

TL;DR

Microsoft is combining Microsoft Copilot and Microsoft 365 Copilot into one application. The rollout has already started and broad commercial deployment is expected from September 2026.

If you’re managing corporate Windows devices, I would check four things:

• Is copilot.cloud.microsoft accessible?
• Is Microsoft Edge Update current?
• Do we want to allow personal Microsoft accounts?
• Have we tested the new Copilot experience on a small group?

That’s basically it… No huge migration project… No panic… Just something I’d rather test now than troubleshoot later.

Final Thoughts

I actually think Microsoft is moving in the right direction here.

The number of different things called “Copilot” was getting ridiculous, and having one application where your account determines the experience is easier to understand.

For users, this should eventually make Copilot simpler.

For administrators, it means we have a little homework to do first.

Luckily, not that much.

Cheers,

Engin