Microsoft resets Copilot economics, ships agent framework inside Business Central base license

Copilot Credits get a published unit price across the Power Platform

A Microsoft-published Copilot Credits Guide, surfaced on 2026-08-25, sets a flat rate of $0.01 per Copilot Credit and notes that "actual pricing will vary based on workflows and usage patterns." A companion Power Platform pricing page translates that unit into a packaged purchase: a message pack at $200 per month for 25,000 Copilot Credits. The same pricing page lists Microsoft 365 Copilot at $30 per user, framing credits as the consumption layer beneath a per-seat subscription.

For practitioners, the practical question shifts from "is Copilot included?" to "how many credits does my workflow burn?" — the $0.01 unit makes spreadsheet math straightforward once a team knows its monthly message volume.

Microsoft 365 Copilot seat price cut to $21 with a year-two reversion

Independent reporting published on 2026-08-25 records that Microsoft cut Copilot from $30 to $21 per user per month on July 1, 2026, with the seat reverting to $21 in year two. The same item notes a $151,200 delta per year on 3,000 seats, a figure worth re-reading carefully: it frames the cut as the discount versus a baseline, not the cost of renewing at $21. For a knowledge-work lead modelling a 3,000-seat rollout, the decision now hinges on whether the $21 hold is treated as a temporary concession or a structural price, because the reversion language removes any certainty that the lower rate persists beyond year one.

Copilot and its agent framework ship inside the base Business Central license

A 2026 guide to Dynamics 365 Business Central AI Agents, surfaced on 2026-08-25, states that Microsoft ships Copilot with every Business Central license at no additional cost and that the built-in agent framework is now part of the base product. That changes the procurement story for operations and finance teams: there is no second SKU to negotiate for the AI features themselves, only the consumption costs measured in Copilot Credits. Teams already paying for Business Central seats inherit both the assistant and the agent scaffolding without a separate line item, which shifts budget conversations from "buy or skip" toward "how many credits will our month-end close burn."

How the three signals fit together for daily-work planning

The seat cut, the credit unit price, and the inclusion of Copilot in Business Central describe a layered model: per-seat access, per-message consumption, and bundled product inclusion. A practitioner who treats them as one number will mis-budget; the $0.01 per credit and the $200-per-month message pack are the consumption ceiling, while the $21 per user per month rate governs headcount. The Business Central inclusion means some teams will see zero marginal seat cost but a non-zero credit cost, the inverse of the Microsoft 365 pattern. Planning a quarter now requires modelling both layers separately rather than blending them into a single per-user estimate.

Workflow follow-up readers can act on

The next concrete step is to pin down a team's monthly message volume before sizing any seat purchase, because the $0.01 per credit rate only translates into a dollar figure once a workflow's per-user message count is known. Readers running Business Central should confirm with their partner whether existing seat entitlements already cover Copilot and the agent framework, removing the need for a separate purchase decision. Anyone modelling the Microsoft 365 Copilot line should track the year-two reversion language and plan two scenarios: one at $21 sustained, one reverting to the prior $30 baseline.

A Business Days Calculator helps size a pilot window, and the broader Copilot Credits Guide remains the reference document for any credit-based budgeting conversation.