Microsoft Has Nine Products Called Copilot. I Nearly Built the Wrong One Twice.

Count the products Microsoft currently sells with “Copilot” in the name: the free consumer chatbot, the paid enterprise add-on, Microsoft 365 Copilot Chat, a separate Business Chat that is not the same product, Copilot for Sales, for Service, for Finance, for Security, Copilot in Windows, and GitHub Copilot, which shares nothing with the rest except the name. Nine by the narrowest count. Closer to 80 once you count every variant.

This isn’t just me being grumpy. In June 2025 the US ad-standards body, the BBB’s National Advertising Division, reviewed Microsoft’s Copilot marketing and ruled parts of it misleading, because consumers “would not necessarily understand the differences between the various Copilot services.” Microsoft softened some claims. It renamed nothing.

The afternoon it actually cost

An acquaintance of mine spent an afternoon building an AI assistant in this ecosystem. It worked, he was proud of it, he showed his team. Half of them couldn’t open it.

Microsoft gives you at least two places to build your own agent: a lightweight builder inside the everyday Copilot chat, and a separate, fuller platform called Copilot Studio. On a screenshot they look near-identical. And they have opposite rules about who gets to use what you build. The lightweight one only works for people who personally hold a paid Copilot seat; the license lives with the person, not the tool. Copilot Studio is licensed at team level and built to be shared. Nothing on screen tells you which one you’re in, or that the difference exists.

He’d built in the lightweight one. Colleagues without their own seats got nothing that explains anything, just: not available. He rebuilt the same assistant from scratch in Copilot Studio, and it worked for everyone the same day. One afternoon, spent entirely on a distinction the product never surfaces. The same week I found the same confusion in a different person building a different tool. Same wrong assumption, same fix.

It doesn’t stop at seats

Here’s the part that actually gets under my skin. Rebuilding in Copilot Studio doesn’t end the licensing story, it just swaps one opaque rule for another. Copilot Studio doesn’t check a seat at all. It burns credits, from a pool shared across the whole tenant, and it burns them at different rates depending on what the agent does: a plain answer costs around one credit, a generative one about two, and an autonomous action, the whole reason you’d build an agent instead of a chatbot, can run twenty-five or more. If everyone using it already holds a paid Microsoft 365 Copilot seat, none of that pool gets touched. The moment one person without a seat shows up, and on a real team someone always does, you’re metering against a number nobody budgeted for, on a bill nobody’s watching.

Then there’s the trap that isn’t even about licensing. Publish an agent and Copilot Studio hands you a demo link by default, a small test site meant for your own team to poke at while you’re still building. Microsoft says so plainly in its own documentation: not for production, don’t send it to customers. Nothing in the product itself says that at the moment you’re about to send the link. I’ve watched someone proudly demo a “finished” agent to an actual client on exactly that link, because it looked done, it answered questions, it had their branding on it. It was never meant to leave the building.

None of this is hard to explain. It’s three sentences: this one needs a seat, this one meters credits per action, this one is a test link, not a product. Microsoft ships none of those three sentences where you’d read them at the moment you’d actually need them.

What Microsoft should actually do about this

None of this is a knock on what these tools can do. My acquaintance’s rebuilt assistant genuinely worked, his whole team used it, and building it took an afternoon instead of a contractor and a purchase order. That’s the actual promise of this generation of AI tooling, and it’s real. The mess is entirely on the packaging around it.

The fix isn’t hard to describe, even if Microsoft won’t enjoy doing it. Collapse the product count. Nine things called Copilot, closer to eighty counting variants, isn’t nine ways to serve nine real needs, it’s one brand stretched over a decade of separate acquisitions and side projects. Draw one clear line first: consumer Copilot on one side, everything a business builds or pays for on the other, nothing that can be mistaken for the wrong side. Then name what’s left so the name itself signals the license model, not just the feature set, the way “Pro” or “Enterprise” already does everywhere else in software. Nobody should need a blog post to find out whether the thing they built needs a seat, a credit pool, or neither.

The one question that saves the rebuild

You don’t need to understand the product map. You need one question, asked before anyone opens a build screen:

Who, specifically, needs to use this when it’s done, and does each of them already have their own paid seat?

Everyone has a seat and the job is simple: the built-in builder is fine. Even one person without a seat, or anything that reaches outside Microsoft’s own apps: Copilot Studio, budgeted at team level. Get the answer in writing before anyone builds.

Ask two more before you publish anything. What does one real interaction cost once this is live, in credits, not in licenses. And is the link you’re about to send the actual product, or the demo site Copilot Studio hands you by default. Both take thirty seconds to check, and both have already burned people I know.

It’s a five-minute question up front and thirty extra seconds before you hit publish; the alternative is the afternoon my acquaintance lost, or a week, or a demo that quietly embarrasses you in front of a client.

Microsoft didn’t build a bad tool. It built nine tools with one name, gave two of them completely different ways of charging for the same action, and left everyone else, including its own ad regulator, to work out which is which. If you’re about to greenlight an AI project inside Microsoft’s world, ask who gets to use it, what it costs them to use it, and whether what you’re about to show anyone is even real.