AgentIndex · traderszone

AgentIndex · News

Microsoft Ends Flat-Rate Billing for Enterprise Agents

Microsoft's Copilot restructuring moves the enterprise agent tier to usage-based billing, with an auto-router selecting models by accuracy, speed, and cost. The buyer of your agent service is increasingly an algorithm, not a developer.

· 342 words

Microsoft launched a new version of Copilot this week that separates consumer-style chat from enterprise agent work, and for enterprise agents, it is switching to usage-based billing.

The change is direct: the standard Copilot license now covers chat and Office integrations only. The agent tier, called Autopilot (formerly Scout), runs on usage-based pricing. Each Autopilot instance gets its own cloud computer, workspace, storage, and identity. It can monitor Teams channels, coordinate supplier evaluations, or run recurring tasks without human approval. Code, the section for building apps and automations, is also metered.

The auto-router matters for builders of agent services. Microsoft describes it as selecting models based on accuracy, speed, and cost for Office integration requests. For premium usage-based work, the company says it will tap frontier models. For standard tasks, it will route to its own models, which it says are optimized for efficiency. The company has been moving away from third-party models in cost-sensitive paths for months.

What this signals: the enterprise buyer calling your endpoint is now inside a cost-optimized routing layer. The agent making the purchase decision is not indifferent to price. It operates in a system where model selection already happens based on accuracy, speed, and cost, and where IT admins control which model families are eligible at all.

A developer evaluating your endpoint makes a deliberate integration decision. An automated router evaluating your endpoint compares it against alternatives every time it routes a request. The winning criteria are not the same. Schema compatibility, latency consistency, and declared pricing matter in the routing layer in a way they do not when a person is deciding.

This also sharpens the vertical integration question. Microsoft's router will prefer Microsoft's models for cost-sensitive requests. Third-party services earn their place only on tasks where the premium is justified. That is a narrower target than the model where any developer who reads documentation is a potential buyer.

Microsoft Copilot has a large enterprise footprint. This pricing shift, across that footprint, makes per-use billing the default model for enterprise agent work, not an experiment.

Sources

https://the-decoder.com/microsoft-gives-copilot-another-makeover-adding-an-autopilot-agent-and-usage-based-billing/

This came from the index.

AgentIndex probes agentic endpoints rather than repeating their listings. Browse what we measured, or point your agent at it.