A 78 page buyer side guide to the Copilot family in 2026. Copilot for Microsoft 365, Copilot Studio, GitHub Copilot Enterprise, the agent metering model, the prerequisites that lock in spend, and the renewal traps that surface after the first deployment year.
Copilot is not a single product. Copilot is a brand applied to nine distinct AI offerings with nine distinct metering models, and the buyer side mistake is treating them as one. This guide separates them and prices them.
By the start of 2026, most enterprises were running three or four flavours of Microsoft Copilot in parallel without realizing it. Copilot for Microsoft 365 sits on top of every E3 or E5 seat that opted in. GitHub Copilot Enterprise is invoiced separately through GitHub. Copilot Studio runs on the agent message metering model that did not exist when most EAs were signed. Sales Copilot, Service Copilot, and the Dynamics 365 Copilot agents each carry their own SKUs, prerequisites, and renewal terms. The first procurement function to consolidate these into a single Copilot inventory always finds at least three SKUs that nobody had on the radar.
The Copilot pricing story has shifted twice in the last twelve months. The original Copilot for Microsoft 365 price held at thirty dollars per user per month for a year before Microsoft added the Copilot Pro tier and the agent metering on top. Copilot Studio moved to a message based capacity model that requires a careful read to understand the actual unit economics. GitHub Copilot Enterprise moved to a billing model that integrates with the Azure Consumption Commitment for some buyers and not others. The realized cost per Copilot active user is not what the published price suggests, and this guide quantifies the gap.
The compliance story has shifted too. Several Copilot products require specific Microsoft 365 prerequisites that buyers do not always have. Some Copilot agents require the Microsoft Graph connector tier. Copilot Studio requires Power Platform capacity or the new agent flex billing. The eligibility map is not always clear to the account team selling the product, which means buyers often sign Copilot orders against entitlements they do not actually own. This guide untangles the prerequisites and shows where the typical contract has gaps.
The playbook opens with the SKU map. We split the Copilot product family into five categories: productivity Copilots that bolt on to Microsoft 365, developer Copilots in the GitHub family, agent Copilots through Copilot Studio, role specific Copilots in Dynamics 365, and security Copilots in the Defender and Sentinel family. Each category has a distinct metering model, a distinct prerequisite stack, and a distinct renewal cadence. The SKU map is the foundation for every other chapter.
The middle of the playbook covers the metering math. Copilot Studio agent messages are not a familiar unit to most procurement teams. The playbook walks through the conversion logic, the typical message volume per active agent, and the three patterns of message inflation that surprise buyers in the first deployment year. We also cover the GitHub Copilot Enterprise billing model and the way it interacts with the Azure Consumption Commitment for buyers who route their developer spend through Azure.
The prerequisites chapter is the one most buyers wish they had read before they signed. Copilot for Microsoft 365 requires a Microsoft 365 E3 or E5 base, plus a small number of additional SKUs for full functionality. Copilot Studio requires either Power Platform capacity or the agent flex billing path. GitHub Copilot Enterprise requires GitHub Enterprise Cloud or Server seats. The playbook documents every prerequisite in a single table and shows the gaps that typically appear when an EA is mapped against a planned Copilot rollout.
The renewal chapter integrates Copilot into the broader EA cycle. Copilot is currently sold as a one or three year subscription with auto renewal in most enrolments. The price protection is weaker than buyers assume, the seat reduction rules are stricter, and the cancellation triggers are documented in places most procurement teams do not read. We close with the negotiation patterns that survive the next renewal. Cross reference the Microsoft EA Renewal Playbook for the broader EA negotiation context.
Email gated. Corporate addresses only. We will send you a direct PDF link and add you to the buyer side intelligence list. Unsubscribe in one click.
Prefer to talk to a human first?
Schedule a Microsoft Advisory Call →
Talk to a buyer side advisor. No pitch. No sales theatre. Thirty minutes, your numbers, our framework.
One letter a month. Negotiation moves, audit signals, and price book shifts.
