Post

So Microsoft put out three posts on Friday about the future of Copilot, tucked in at the end of the quarter. Everyone has done the headlines. This is three minutes on the bits underneath them. youtube.com/shorts/XYiCP...

🔹 Two terms to learn. USL is the user subscription licence, the M365 Copilot seat and everything in it. UBB is usage-based billing, credits and pay-as-you-go. Microsoft have now written that split down as the model, so it isn't going away.

🔹 Chat and Cowork are merging, and Copilot will decide which one runs your request. Chat is in the seat, Cowork is on the meter.

The switch you used to flick was the thing that started the bill. 🔹 If your spending policy has "auto-apply new services" on (it's the default), every new metered thing Microsoft ships lands in it without anyone touching the policy.

🔹 Code looks like App Builder reframed: dashboards and small line of business apps. Building them costs credits, and running them will too. 🔹 Scout is now Autopilot. Cloud-hosted, its own identity, its own memory, consumption based. Less "my Copilot got a memory", more "I've hired a colleague".

This is the enterprise story. The Copilot Business default-on change is a separate one, I posted on that last week. I'll be unpicking each of these properly over the next few weeks, starting with a map of what Copilot actually is now.

Food for thought 🤔 🔹 Copilot deciding when you pay extra is convenient right up until the invoice. Who set the router's budget? 🔹 "Start on credits, move into the licence later" is now written down. Early adopters fund the bundle. 🔹 An agent with its own identity is a new kind of account.

Nobody's leavers process was written for it. Sources- Official blog: blogs.microsoft.com/blog/2026/09...