Copilot can choose the mode. Who explains the bill?

Microsoft plans to route requests between Chat, Cowork and Code. Easier navigation still needs a clear spending conversation.

Ask for the work. Let Copilot decide how to do it. That sounds considerably better than teaching everyone another menu.

There is one person I would invite to that demonstration: whoever has to explain the invoice.

The new bit is who chooses the mode

In its September 25 announcement, Microsoft introduced Home, Code and Autopilot. Home brings Chat and Cowork together. Microsoft also described a coming capability that would route a request to Chat, Cowork or Code without the employee choosing a mode.

The same announcement places Cowork, Code and Autopilot under usage-based billing. Easier navigation does not establish that every route has the same cost. Read Microsoft’s announcement.

This is a rollout announcement, not a description of what every employee has today. Microsoft says Home and Code start arriving through Frontier in the coming weeks, while Autopilot expands to private preview at the end of September. We have not tested the routing or its billing behavior.

One request, two expectations

Here is an illustrative situation. A manager asks for help with next week’s supplier review. They might mean “give me an outline.” They might mean “prepare the documents and carry out the whole process.” Those are very different assignments hiding inside a perfectly ordinary sentence.

A more capable assistant should help resolve that ambiguity. The employee should not need a purchasing qualification to ask for help.

Before introducing this to a department, I would want a small demonstration using that department’s actual, approved work:

• What does the employee see before a request becomes a longer task?
• Can they understand which work uses credits and see the consumption afterward?
• Who receives a request for more capacity, and who can approve the spending?
• What happens when the employee reaches the limit halfway through?

These are questions to test in your configuration, not claims that the preview already answers them.

Make the handoff visible

Microsoft also announced spending-policy APIs, routing credit requests into existing approval workflows, and user access to balances and usage history. Those are useful things to check as they become available in your environment.

We already wrote about Cowork’s separate usage bill. This adds another training question: what does an employee need to understand when the software chooses the path?

Let Copilot choose the tool. Make sure the person asking for help can still understand the commitment. “It picked that for me” is going to be a very popular explanation.