Take control of AI spend across Microsoft Copilot, Cowork, and agents inside and outside of Microsoft. Track your own Copilot Credit usage task by task, pin down your top cost drivers by service and model provider in Agent 365 Business Analytics, and weigh each use case's cost against its measured AI value. Forecast month-end spend, model a shift to lower-cost models, and enforce hard budgets with spending policies scoped to users, groups, or shared agents in the Microsoft 365 admin center. Delegate budget control to the owners closest to the work. Jeremy Chapman, Microsoft 365 Director, shares how users, budget owners, and IT admins each play a part in turning AI spend into measurable value.
π₯ Who it's for:
IT admins and Microsoft 365 admins setting up usage-based billing and AI budgets, FinOps and budget owners managing Copilot and agent spend, and CIOs and business leaders measuring AI ROI across their organization.
β±οΈ Chapters:Β
00:00 Control AI spend across Copilot and agents
00:46 Track your own Copilot usage and limits
01:22 How Copilot Credits measure AI consumption
01:36 Measure AI ROI in Agent 365 Business Analytics
02:52 Pin down top cost drivers by model
03:35 Spot top users and spread best practices
03:57 Weigh use case cost against AI value
05:04 Forecast month-end cost and model scenarios
05:51 Raise spending limits as a budget owner
06:37 Enable usage-based billing in Microsoft 365
07:19 Create spending policies with hard limits
08:35 Delegate budget roles to owners outside IT
09:32 Start with Business Analytics and admin setup
Every advanced AI task in Microsoft Copilot, from a simple prompt to a complex Cowork or agent workflow, consumes Copilot Credits. One Copilot Credit currently equals one cent in US dollars. Users check their own consumption under Usage details in Copilot, with a seven-day view, remaining monthly limit, and credits used per task.
Agent 365 Business Analytics gives managers, budget owners, and CIOs an organization-wide or filtered view of AI usage and cost by manager hierarchy, organization, or job function. Break down spend by service, model provider, and use case. Compare services like GitHub Copilot and Cowork, and use the combined view to see which models each service relies on and how that adds up to cost. The Use cases view maps sessions, cost, and AI value by business domain, with AI value calculated from the time it would take a person to do comparable work, using official sources including the US Department of Labor.
Cost & Forecast projects month-end cost and shows what drives increases and decreases by job function, model, and service. Model what-if scenarios, such as a spending cap, expanded access, or a shift to lower-cost models, and compare the results with current usage.
In the Microsoft 365 admin center, IT admins enable usage-based billing with an Azure subscription on pay-as-you-go or prepaid billing, then create spending policies under Cost Management. Scope policies by identity or by resource, such as a shared agent, set cumulative and per-user monthly limits, configure alerts, and control which models are allowed with templates. Assign Delegator, Writer, and Reader roles so budget owners outside IT manage policies directly from Agent 365 Business Analytics.Β
π Related links:
β Check out Agent 365 Business Analytics at https://aka.ms/A365Analytics
β Activate usage-based billing and set up your policies at https://admin.microsoft.com
βΊ Unfamiliar with Microsoft Mechanics?Β
Microsoft's Official Video Series for IT
β Subscribe https://www.youtube.com/c/MicrosoftMechanicsSeries
β Microsoft Tech Community: https://techcommunity.microsoft.com/t5/microsoft-mechanics-blog/bg-p/MicrosoftMechanicsBlog
β Podcast:Β https://microsoftmechanics.libsyn.com/podcast
βΊJoin us on social:
β https://twitter.com/MSFTMechanics
ββ https://www.linkedin.com/company/microsoft-mechanics/