Your AI Spend Is Three Bills Now: Seats, Credits and Azure

Ask a finance leader what the business spends on Microsoft AI. Often, the answer is a pause. The number is not secret. However, it is not one number. In fact, it arrives as three bills.

Microsoft AI spend now comes as per-user seats, prepaid Copilot Credits and Azure pay-as-you-go use. Each one is bought, tracked and billed in a different place. Each one also runs on its own cycle. As a result, few teams add them up. So few can say what AI really costs per process. At DAX Software Solutions, we see this gap as the real issue for leaders. The price of any one line matters less.

What are the three bills?

Seats, credits and Azure use.

• Seats are per-user licences on subscription terms. Examples include Power Apps Premium and Dynamics 365.
• Credits are Copilot Credits. Microsoft’s Copilot Studio billing guidance calls them the common currency across Copilot Studio. Dynamics 365 agents in Business Central and Sales also draw on this capacity each time they run.
• Azure use starts when you link a Power Platform environment to an Azure subscription. After that, Azure meters bill the usage, as Microsoft’s pay-as-you-go guidance explains.

Where does each bill arrive?

In three different systems.

• Seats and prepaid Copilot Credit packs: you buy these in the Microsoft 365 admin center. Resellers use Partner Center instead.
• Credit capacity: admins assign it to environments and track its use in the Power Platform admin center.
• Azure use: it shows up on the Azure bill under a Power Platform account resource. For detail and budgets, Microsoft points to Microsoft Cost Management in the Azure portal.

This is because each system serves a different team. For example, licence admins use the Microsoft 365 admin center. Similarly, platform teams use the Power Platform admin center. Meanwhile, cloud finance uses Azure Cost Management. As a result, very few people look at all three.

Why do the cycles not line up?

Because each bill runs on its own clock.

• Seats follow subscription terms. For example, Microsoft’s Power Apps Premium price update applies to terms that start on or after 1 January 2027. Meanwhile, existing subscriptions keep their price until the term ends.
• Credits reset each month. Microsoft states that unused Copilot Credits do not carry over.
• Azure use is paid after the fact. Microsoft notes that Copilot Studio pay-as-you-go customers pay at the end of each monthly billing period.

So in any month, the three lines mean different things. A seat cost may reflect a deal signed a year ago. A credit cost reflects capacity you reserved in advance. An Azure cost reflects usage that has already happened. Therefore, comparing them line by line tells you very little.

How do the bills affect each other?

More than most budgets assume. Take Microsoft 365 Copilot licence holders. Some of their agent use in Copilot Chat, Teams or SharePoint does not use Copilot Studio capacity. Microsoft states it does not count against the pack or meter. This covers classic answers, generative answers and Microsoft Graph tenant grounding. In other words, a seat decision in one system can lower credit use in another.

Microsoft’s Dynamics 365 guidance also states that prepaid capacity gets used before pay-as-you-go. So a smaller credit pack moves cost onto the Azure bill. Similarly, a larger pack moves it back. However, you will not see either shift if you review each bill on its own.

What does an unreconciled AI budget cost?

Clarity about value. Reviewed alone, each bill looks fine. For example, the seat renewal matches headcount. Likewise, the credit pack matches last month’s use. And the Azure invoice sits within budget. Yet nobody asks the key question: does total AI spend match the value each process delivers? No single view can answer it.

The risk is not always runaway cost. Instead, the risk is that you cannot tell which AI investments work. As a result, it is hard to decide where to grow and where to stop.

How should leaders reconcile Microsoft AI spend?

Bring all three bills together on one cycle, sorted by business process.

1. Name an owner for total AI spend, not one owner per bill
2. List every source: seat SKUs, credit packs and Azure-linked environments
3. Tag consistently: Microsoft notes that Azure resource groups and tags help you organize Power Platform account resources and split costs
4. Map to processes: link credit use per environment, and Azure use, to the business processes they support
5. Review monthly: compare the total cost of each process with the outcome it should deliver

This links closely to the question of who owns your Copilot Credits. In fact, ownership is often the first gap that a review exposes.

Frequently asked questions

Are Copilot Credits and Azure use the same bill? No. You buy prepaid Copilot Credit packs in the Microsoft 365 admin center. By contrast, pay-as-you-go use is billed through an Azure subscription.

Do unused Copilot Credits roll over? No. Microsoft states that capacity resets monthly and unused credits do not carry over.

Can a Microsoft 365 Copilot licence reduce credit use? Yes, for some agent use in Copilot Chat, Teams and SharePoint. Microsoft states this use does not count against the Copilot Studio pack or meter.

How can I split pay-as-you-go costs? Microsoft notes that Azure resource groups and tags help you organize Power Platform account resources and track spend.

DAX Software Solutions: Outcomes Before Technology

DAX Software Solutions helps organizations that run Dynamics 365 adopt Agentic AI. We focus on business outcomes, governance and human oversight. Does your AI spend arrive in three places with nobody adding it up? Then that is the place to start. Talk to our team.

Microsoft’s licensing and billing guidance is for information and may change. Check the current terms for your tenant and agreement before you act.