Microsoft's New Copilot Bills Autopilot Outside the $30 Seat

The $30 Microsoft 365 Copilot seat now covers only the everyday part of Copilot. Everything Microsoft demoed on September 25 (Autopilot, Code, Cowork and the Fable and Astra frontier models) runs on Copilot Credits billed per use, so your FY27 Copilot budget is the seat count plus a metered line nobody has forecast yet.

Microsoft introduced the new Copilot with three surfaces: Home (Chat and Cowork inside Word, Excel and PowerPoint), Code (apps, dashboards and workflows for people who don't write software) and Autopilot, a persistent agent with its own identity and workspace. In the same post it split the bill in two. The user subscription license covers "Copilot in Chat and across Word, Excel, PowerPoint, Outlook and Teams; model selection; and new capabilities and models." Usage-based billing covers "Cowork, Code, and Autopilot, new long-running agentic capabilities, and frontier models like Astra and Fable."

What that means on Monday: the features your executives saw in the keynote will not work until an admin turns on a billing policy, and once one is on, the admin's defaults decide how much they cost.

What Moves Off the Seat, and When?

Microsoft now sells Copilot as two products: a fixed seat for "everyday AI" and a meter for "advanced AI." Its own licensing explainer, dated September 25, defines advanced AI as "complex, long-running agentic work you hand off," and says the metered experiences "consume Copilot Credits and require a USL for access." So the meter is billed on top of the $30 seat.

The seat keeps Auto, the default mode that routes each request to a model and reasoning level. It also keeps model selection, with a caveat in the same document: some models, "such as GPT 5.6 and Sonnet," are included "with fair use," while others, "such as Opus," are included "with limits." A second change is marked "coming soon." Users who reach a USL limit will get the choice to keep going on Copilot Credits or reroute to Auto.

Timing comes from outside Microsoft's blog. Topedia's summary of the pricing update puts the advanced features' rollout at October to December 2026 and lists the SharePoint capabilities that move to credits (image generation, site analytics, metadata autofill). It cites the Teams Interpreter agent, capped at 20 hours a month per user, as an example of a seat limit where users could continue on credits. Microsoft's blog says Autopilot expands to private preview at the end of September and Home and Code reach the Frontier program "in the coming weeks."

That gives you about one quarter between the announcement and metered agents showing up in production tenants. Futurum reports that usage-based billing is default-off for enterprise tenants, so nothing is metered until someone in your admin center switches it on.

What Does a Copilot Credit Actually Cost?

A Copilot Credit is the unit Microsoft meters agent work in: about one cent at list price. The Copilot Studio pricing page sells prepaid capacity packs of 25,000 credits at $200 a pack per month, which works out to $0.008 a credit. Microsoft's pre-purchase plan documentation uses $0.01 as the pay-as-you-go rate in its worked example. Futurum's Keith Kirkpatrick, reading Microsoft's September credits guide, reports $0.01 a credit with pre-purchase discounts of up to 20%.

The rate is the easy part. Nobody, Microsoft included, publishes what an Autopilot hour or a Code build consumes. For Cowork, the closest thing to a rate card is a partner estimate: Quisitive's Cowork pricing guide puts light tasks at roughly 100 to 300 credits, medium tasks at 400 to 700 and heavy tasks above 700. Treat those as one partner's ranges, not Microsoft's.

Run the arithmetic on them anyway. A user who runs two medium Cowork tasks a day at 500 credits each burns 1,000 credits a day. Over 20 working days that is 20,000 credits, or $200 a month at the pay-as-you-go rate: more than six times the $30 seat for one person. Ten such users would exhaust a 25,000-credit pack in two and a half working days.

Users cannot see the price first, either. Microsoft's /cost documentation answers "Can I check the cost before running a task?" with "No." The command reports what a task has already used, calls itself "not an authoritative billing record," and credits "reset monthly and do not carry over."

Kirkpatrick's critique is the one to take into negotiation. Credits track "compute, model choice, and runtime," he writes, so "an agent that spends four hours producing a flawed output costs the same as one that nails the task." Microsoft's counter-argument, as Kirkpatrick summarizes it, has merit too: rivals that meter everyday work force companies to ration access, and Microsoft keeps that work on the flat seat. For a budget owner, that leaves a fixed seat cost and a variable agent cost with no published upper bound.

---

Which Admin Defaults Spend Money for You?

Three settings in the setup flow decide how far the bill can run, and Microsoft's defaults lean toward spending. The controls live in the Microsoft 365 admin center under Copilot > Cost management, and Microsoft's admin guide, updated September 30, documents each one.

First, the default policy covers everyone. "The default setup targets your entire organization and all users." The first billing choice the wizard offers is "Don't limit monthly spending." A per-user cap is labeled optional, though Microsoft itself advises setting one "to prevent runaway spending of Copilot Credits by one individual user."

Second, new services join existing policies automatically. "Auto-apply new services" is "turned on by default," and it adds "newly supported Microsoft Copilot services and agents" to the policy as they ship. A policy you write in October for Cowork will cover Autopilot and Code when they reach your tenant, under whatever limit you set for Cowork. Microsoft's cost management overview tells admins to "review existing spending policies to determine whether automatic coverage is appropriate."

Third, running out of prepaid credits does not stop the meter. "When credits run out for that subscription, usage automatically continues on a pay-as-you-go basis." Billing order is capacity packs first, then any pre-purchase plan, then pay-as-you-go on the linked Azure subscription.

Some guardrails do hold. When a user hits a limited policy, they "lose access to agents and services for the rest of the month until credits reset on the first of the month." Moving a user to another Entra group does not reset their count. Model profiles let you restrict which models a group can call, but only for Cowork today, and each profile needs at least two models. A task that runs past a user's limit can finish, and Microsoft says that excess is not billed "at Microsoft's sole discretion."

Watch two smaller traps. Capacity packs are shared with the Power Platform admin center, so credits already allocated to Copilot Studio environments reduce what Cowork and its successors can draw. And Copilot credit pre-purchase plans are one-year commitments where "cancel and exchange operations aren't supported," per the P3 terms. Buying a year of credits before you have a month of usage data is a bet on a forecast you don't have.

Why Won't Agent 365 Cap This Bill?

Microsoft Agent 365 is a governance product with no spending controls. Its product page prices it at $15 a user per month (or bundled into the $99 E7 suite) for an agent registry, Entra identity, Defender and Purview coverage, and usage insights. The caps that actually stop consumption are the Cost management policies described above.

That matters for ownership. If your security team runs Agent 365 and your licensing team runs Cost management, an Autopilot can be properly registered and fully compliant while nobody owns its monthly credit burn. We made the same point when Agent 365 shipped and the $99 SKU turned out not to be the bill; the new Copilot adds a third invoice line.

Microsoft's own explainer hints at who it expects to pay. Usage-based billing "may be better funded by business units that can manage UBB along with cost-benefit tradeoffs." Read that as a chargeback model. IT buys seats, business units buy credits. If your finance team has no mechanism for that split, build one before the first invoice.

---

What to Do Before Usage-Based Billing Turns On

This Week:

1. Check whether usage-based billing is already active. Open Copilot > Cost management in the admin center. If a default policy exists, look at its scope, its monthly limit and its Auto-apply setting before Autopilot reaches your tenant.
2. Turn off Auto-apply new services on every policy until you have priced Autopilot and Code separately. Re-enable it service by service.
3. Set a per-user monthly limit on the default policy, even a generous one. Microsoft recommends it and nothing else stops one user's loop from draining a pack.

This Month:

1. Create one spending policy per pilot group (security groups only, per Microsoft's guide) with its own limit and billing method, so the Consumption tab shows cost by team instead of one tenant total.
2. Route credit requests through custom request policies to your existing ServiceNow or IT portal workflow, so a business owner, not IT, approves spend above the cap.
3. Pull 30 days of Cowork usage from the Consumption tab and use /cost on real tasks to build your own credits-per-task table. Compare it with the partner ranges and use your own numbers in the budget.

Before Renewal:

1. Price the seat and the meter together. Put both in the FY27 plan as separate lines with separate owners.
2. Ask Microsoft for written commitments on two things Kirkpatrick flags: where the fair-use and "with limits" lines sit for models in the seat, and how and when capabilities move from the meter back into the seat.
3. Size any pre-purchase plan from at least one quarter of real consumption. It cannot be cancelled.

The Bigger Picture

Microsoft has repriced Copilot the way cloud vendors priced compute a decade ago: a commitment for the base load and a meter for the bursts. The base load stays affordable, and the bursts are where the agents are. The last time we priced a Copilot seat, the licence was already only the floor of the bill. The September split makes that official and moves the newest features above it.

Autopilot was previewed at Build as Scout, and both its name and its packaging have changed in the four months since. Plan on the meter rates and the seat's fair-use limits moving again during your contract term, and keep the controls you set in October under quarterly review.

Open Cost management and switch off Auto-apply before Autopilot lands in your tenant.

Continue Reading

• True Cost of a Copilot Seat: The Licence Is the Floor
• Copilot Cowork Is Billing Now: What Each Task Costs
• Agentic AI Pricing: Don't Buy Consumption Without a Cap
• Microsoft Agent 365 Ships: The $99 SKU Is Not Your Bill
• M&T Published 3 Copilot Counts. None Was Weekly Actives.
• Best FinOps Tools for AI Spend: No Dashboard Fixes an Untagged Key