3.4.1. Managing and Monitoring AI Costs
💡 First Principle: Some AI is paid for by seat (a Copilot license) and some by consumption (credits or metered pay-as-you-go). Seat costs are predictable; consumption costs need limits, alerts and a clear rule for who's allowed to consume. In Microsoft's model, those rules are spending policies — which is why they double as access controls.
There are two metering systems, and the exam expects you to keep them apart:
1. Usage-based billing with Copilot Credits — Microsoft 365 admin center > Copilot > Cost Management (Overview, Consumption and Configuration tabs). It covers usage-billed services such as Copilot Cowork, advanced work in SharePoint and OneDrive, the Work IQ API and the Teams Phone agent; Copilot Studio can opt in. Billing methods are prepaid capacity packs, the P3 annual pre-purchase plan (layered on pay-as-you-go, not a separate option) and pay-as-you-go through an Azure subscription.
- Set it up as a Global Administrator or Billing Administrator: Get started, then activate the default spending policy (all users).
- A spending policy has a scope (all users or groups), the agents and services it covers (with auto-apply new services on by default), limits and alerts, and a billing method. The minimum per-user limit is 2,000 credits a month.
- When a user hits their limit, they lose access to the governed services until credits reset on the 1st of the month. Limits are enforced asynchronously.
- If a user falls under several policies, the one with the highest per-user limit applies (then the largest overall limit, then the newest); settings from different policies aren't combined.
- Policy-level threshold alerts are emailed daily until the reset. The overview refreshes about every four hours.
- Reader roles such as AI Reader and Global Reader can view the dashboards.
2. Microsoft Copilot pay-as-you-go (billing policies) — for Copilot Chat agents used by unlicensed users, SharePoint agents and the Copilot Retrieval API. It's off by default. You create a billing policy (an Azure subscription plus a set of users, optionally with a budget and email alerts), then connect it to a Copilot service. Costs appear in the admin center and in Azure Cost Management.
Copilot Studio has its own model: the maker license is free, but the tenant needs prepaid Copilot Credit capacity (or pay-as-you-go through a Power Platform billing policy linked to environments). Unused credits don't carry over. Copilot-licensed users using agents in Copilot Chat, Teams or SharePoint for grounded answers are zero-rated.
⚠️ Exam Trap: An Azure budget only sends alerts — it doesn't stop spending. To cap consumption, set limits in spending policies. And remember that a spending policy that selects Cowork grants Cowork access, whatever its limit.
Reflection Question: Finance wants Cowork consumption capped at a fixed monthly amount per user, with alerts as the cap approaches, and for usage to draw first on credits already prepaid. Which object do you configure, and in what order are credits charged?