Blog Post

Microsoft Copilot Blog
5 MIN READ

Evolution of the Copilot pricing model

Nicole Herskowitz's avatar
Sep 25, 2026

You need to know what AI is going to cost so you can plan for it and manage it. That’s a fair ask. As AI becomes more agentic, we’re committed to delivering predictable value for everyday AI, while enabling state-of-the-art AI experiences that deliver more value and cost more to run. That’s why Copilot pricing is evolving to combine predictable per-user pricing with usage-based pricing

Everyday AI

Everyday AI is what you give your whole workforce. It's covered by the Copilot user subscription license (USL), priced per user per month (the way you've bought software for years), and there are no changes to the value you already have.

We price it this way on purpose. Some vendors put everyday AI work on a meter. We think that's the wrong deal, because when every task has a meter, companies may ration access and only some people get to use AI. We think everyone should.

Microsoft internal analysis, September 2026. Cost comparison modeled two user profiles across 40 prompts, with each prompt tested 10 times: everyday AI users (15 prompts: 9 Chat, 6 across Word, Excel, and PowerPoint) and advanced AI users (25 prompts: 5 Cowork plus 20 everyday work prompts: 11 Chat, 9 across Word, Excel, and PowerPoint, with a higher proportion of app-based tasks to reflect the advanced user’s broader use of AI across Microsoft 365 apps). Copilot used Auto for Chat and Microsoft 365 apps; Copilot Cowork used Opus 5 and GPT-5.6 Sol with high effort. Claude used Opus 5 with medium effort for Chat, extended thinking for Microsoft 365 add-ins, and Opus 5 with high effort for Claude Cowork. ChatGPT used GPT-5.6 Sol with medium effort for Chat and Microsoft 365 add-ins, and GPT-5.6 Sol with high effort for ChatGPT Work. Copilot costs reflect subscription list pricing, with Copilot Cowork costs calculated using variable rates based on model, context, tools, and runtime. Claude and ChatGPT costs were modeled using publicly available list pricing and API rates at the time of analysis. Costs exclude discounts, promotions, negotiated rates, and other special pricing. Actual results may vary based on customer usage, configuration, pricing, and other factors.

A fixed price fits everyday AI because of what we call saturation: the point where a more capable model stops changing the result, because the task never needed it. Tasks like turning a meeting transcript into bullet points or summarizing a document from a teammate are saturated.

Auto in the Copilot model picker is built around that idea. When you use Auto, it weighs accuracy, speed, and cost on each request to route to the model and level of reasoning effort best suited to the job. You get the best quality for a fixed price without thinking about which model to pick. If you'd rather choose, you can, because model selection is part of the USL. GPT-5.6 and Sonnet 5 are included—and new models like Opus 5 will be included with limits.

The USL has always come with fair use, and that won’t change. We're setting usage limits so that the vast majority of people never reach a limit. For the heaviest users, hitting a limit is not hitting a wall. You get a clear warning first, then a choice: switch your model selection to Auto at no additional cost or move to credits.

The USL is the foundation of Copilot, and we remain committed to adding more everyday value to it.

Advanced AI

Advanced AI is work you hand off: agents that run for hours, workflows without supervision, business processes rebuilt with agents doing much of the work. A multi-step financial model running all afternoon. Cowork, Code, Autopilot, new advanced experiences in apps like SharePoint, and frontier models like Fable and Astra. When you need the best possible quality or the best model for a task, that work runs on usage-based billing (UBB) with Copilot Credits. UBB builds on the USL, which is required to access these capabilities.

Both the USL and UBB run on models from multiple labs. Today that means OpenAI and Anthropic, with more labs and open-weight models coming soon. The benefit goes beyond choice. Models from different labs have different strengths, so they complement each other.

Think of our commercial model as a plug-in hybrid. The USL is the battery: it covers most of your driving at a fixed monthly cost. UBB is the gas tank, there when a task needs more range than the battery can give. The choice is yours, task by task.

FinOps

You stay in control. UBB capabilities are visible in the product, because we want everyone to see what Copilot can do. For enterprise customers, UBB services stay off until an admin creates a spending policy in the Microsoft 365 admin center, and nothing is billed before that.

The spending policy is where the decisions get made. Admins set budgets at the tenant and group level, including user-level caps inside group policies, and set alerts when spend hits a threshold. You decide what happens when someone approaches a limit: a warning, a way to request more, or no prompt at all if you'd rather users never see it.

Spend maps to your org the way the rest of your budget does. If you manage departmental costs through Azure subscriptions or resource groups, you can assign usage to the right one, so AI shows up in the same place as everything else that team spends money on. Reporting follows the same logic, broken out by user, group, workload, policy, and payment method.

We’re listening to customers and moving quickly to improve FinOps. Today, we’re rolling out additional capabilities to make AI spend easier to understand, manage, and optimize:

  • More workloads under cost management: Cost management now covers Code and Managed Runtime alongside Cowork and the Work IQ APIs, with Copilot Studio agents coming in October. More AI workloads will follow.
  • Manage model choice: Tailor model family access for different groups, giving admins the ability to match the right models to the right user or scenario to maximize value generated. Rolling out in Cowork with plans to expand to additional workloads.
  • Consumption insights for Cowork: See which scenarios are driving credit consumption and what they produced, so you can decide where to sustain, expand, or optimize.
  • Programmatically manage policies with APIs: Use Microsoft Graph API to manage spending policies at scale in your own business intelligence and FinOps tools of choice. This helps organizations automate with the systems and processes they already work in.
  • Spend visibility for end users: Your people can view credit usage, remaining credits, and usage history directly within Microsoft Copilot to manage their own use.

 

For more information, see here.

What's next

Models keep getting better and more efficient, so some capabilities will start on UBB and move into the USL as the economics allow. Sometimes they'll arrive with a usage limit at first, which lets people use them sooner than they otherwise could.

Most customers already use Copilot for everyday work. As you hand off more complex work, compare the total cost with the alternatives, the way you would for any other investment in getting work done.

To learn more about the new Copilot, see here.

Updated Sep 28, 2026
Version 7.0

12 Comments

  • dunklezhan's avatar
    dunklezhan
    Tin Contributor

    "UBB capabilities are visible in the product, because we want everyone to see what Copilot can do. "

    Well that's lovely for you, and a nightmare for us as an IT department in public sector with zero additional budget for point-of-use billing. Give us ways to hide this stuff we do NOT have time or budget to be fielding staff queries for usage based billing all the time, let alone monitoring the requests that come in to the admin centre instead of through our ITSM tool.  This is the kind of thing that 100% makes us look for other products to use and actually stalls uptake of yours because your desire to market direct to end users actively makes us look bad when we can't oblige them. Pack it in, you have account managers for a reason they can handle the advertising to the IT department or exec layer. We don't pay exorbitant license fees in order for you to advertise to our users. That's what is known as 'abuse of power' because you know we're locked in. But push too far and you'll find we're not as locked in as you think we are, particularly given the drives for us to move towards European open source. You increase the effort we have to put in to managing users like this, and eventually it will tip to 'why not spend that effort getting away from Microsoft instead'.

    In fact, you should be giving us a massive discount for the privilege at least that way we could decide to pay for a service with ads or one without. But an E5 plus a copilot premium license is a very high price to pay to also then put up with microsoft creating aggravation for administrators. Give your heads a wobble, eh?

  • KPKing's avatar
    KPKing
    Iron Contributor

    UBB desperately needs better data integration options, such as an OData endpoint. We need to be able to plumb it to typical enterprise analytics platforms for dashboarding and other workflows. The juvenile "FinOps" interface does not contain adequate reporting mechanisms to enable at enterprise scale. This is a huge blocker to adoption.

    • Eric_VanAelstyn's avatar
      Eric_VanAelstyn
      Icon for Microsoft rankMicrosoft

      Thanks KPKing​ for the feedback! We recognize how critical FinOps will be moving forward and want to be able to best support customers. We'll share this feedback, especially the piece about the OData endpoint and desire to use other enterprise analytics platforms, to the team as they plan for the next wave of FinOp capabilities for AI.

  • MarkRussell's avatar
    MarkRussell
    Brass Contributor

    I think there needs to be greater transparency and better controls out of the box.  Currently, a person doesn't know where they are in relation to any limits - appreciate that might be coming soon, but not sure why it isn't there out of the gate.  Also, as an administrator I still can't control which models are and are not available to my user base - again something that's coming but not there.  Sometimes it feels like the reason these capabilities are not transparent is because it makes them easier for Microsoft to change without having to notify customers.  The Opus limits in Copilot have been there for a couple of months already with no public statement of what they are....

    • RossK1's avatar
      RossK1
      Brass Contributor

      Microsoft introduced the same issue with Cowork; usage-based billing and policy-driven spending limits, but provided no visibility for users to see their actual consumption or how close they were to reaching those limits. I raised this through a DCR at the time because it's the equivalent of giving someone a car without a fuel gauge. Users have no way to understand their current usage, monitor consumption trends, or know when they're about to run out of capacity. Very poor planning and typical cart before the horse rollout. 

  • Does the below sentence mean that Copilot in SharePoint gets under UBB?

    Cowork, Code, Autopilot, new advanced experiences in apps like SharePoint, and frontier models like Fable and Astra. When you need the best possible quality or the best model for a task, that work runs on usage-based billing (UBB)

    • julieseto's avatar
      julieseto
      Icon for Microsoft rankMicrosoft

      Pierre-Yves_Delacote​ The everyday AI capabilities in Copilot in SharePoint that have been in public preview stay included with a Microsoft 365 Copilot user subscription license. New advanced experiences and the ability to work at greater scale than was possible in preview will be available through usage-based billing and consume Copilot Credits. You can learn more in the Copilot in SharePoint docs  or blog. 

  • dazzawho's avatar
    dazzawho
    Copper Contributor

    Why did you use Opus 5 High (not medium as it recommends) and why not try Sonnet? as most everyday AI tasks can also be completed with Sonnet which is significantly cheaper?
    Why did you also not include Grok Bot Pricing comparison?

    Seems like you Cherry Picked higher expensive models when not needed.
    You also make all these claims why not show a video demonstration of any of it actually working instead of stories and screenshots. 

    • Robert Woods's avatar
      Robert Woods
      Steel Contributor

      yea i run agentic tasks in claude code all day long and rarely hit limits. I have never had to buy credits. I have daily briefings coming from cowork as well as a friday task that scrapes sharepoint and emails me the files that have been updated... never had to buy the credits they are claiming you need and im on the 20 dollar teams plan.

  • CarlM6's avatar
    CarlM6
    Tin Contributor

    What Microsoft has actually done, is give chat access for free, use us as guinea pigs then slap a pricing system on.  You've essentially, used Windows users as exploited labour. I've used copilot for years, you've done some upgrade, and now after around 8 prompts, I've been given a "daily chat limit reached" message. Not picture generation, chat.  I'm not a business, I'm someone whose used Microsoft for 35 years, had everything from the phone, to your watch, and now you're locking down AI after we tested it out for you for free. It's bad enough you've destroyed the planet, sticking perfectly good tech into landfill with windows 11 upgrade, blocking poor people from access now you've removed access for those who can't afford a 365 upgrade. A bunch of oxygen thieving thugs. 

  • MxxCon's avatar
    MxxCon
    Copper Contributor

    Could you please clarify if USL indicates availability exclusively through paid Copilot add-on licenses, or if it also comes with the free licenses included with E3/E5?

    • Eric_VanAelstyn's avatar
      Eric_VanAelstyn
      Icon for Microsoft rankMicrosoft

      Hi MxxCon​, USL stands for user subscription license and refers to the paid Copilot add-on license. This blog details how everyday AI is included as part of the USL and advanced AI will be available through usage-based billing (UBB). The USL is required to access UBB capabilities.