Copilot Credits cost controls are here: what IT admins need to know about Work IQ GA billing
Work IQ API hits GA on June 16 with consumption-based Copilot Credits billing. Here's what admins must configure before agents start running up charges.
Update, 23 June 2026: Microsoft 365 Business Standard and Premium with Copilot become permanent SKUs on July 1 — lock in current pricing before then
July 1 is now a two-pronged deadline for IT admins and CSP partners. First, the Work IQ billing cutoff covered in this article remains hard: enable usage-based Copilot Credits billing before July 1 or Cowork access is suspended. Second, Microsoft is converting the M365 Business Standard with Copilot ($23.50/user/month) and Business Premium with Copilot ($32/user/month) promotional bundles into permanent SKUs on the same date. Customers renewing before July 1 can lock in current pre-increase pricing until their next renewal date.
Base plan prices also rise on July 1: Business Standard moves from $12.50 to $14, Business Basic from $6 to $7. Existing customers stay on current pricing until renewal.
SMB admins now have two clean paths: the permanent bundled SKUs with Copilot on every seat, or the standalone Copilot Business add-on, whose 15% promotional rate ($18/user/month) has been extended through December 31, 2026. CSP-managed tenants face an additional step: customers cannot configure Copilot Credits billing themselves and will see a prompt directing them to their partner. Partners must complete billing setup on the customer’s behalf before the July 1 cutoff.
Update, 22 June 2026: OpenAI Adds Cost API and Per-Group Credit Caps to Enterprise Admin Console
The original post focused on Microsoft’s Work IQ Copilot Credits billing going live on June 16. Four days later, OpenAI shipped its own enterprise spend controls, making the broader question of agent cost governance relevant across both platforms simultaneously.
OpenAI’s June 18 announcement adds three layers of control to the Global Admin Console: workspace-wide credit defaults, group-level caps for different teams, and individual overrides for power users. OpenAI’s own guidance suggests power user limits should sit four to five times above standard allocations. A new Cost API exposes the same consumption data programmatically, so finance and observability pipelines can pull breakdowns by user, product, and model without manual exports.
The urgency here mirrors the Work IQ situation. ChatGPT Workspace Agent billing is set to go live on July 6, 2026, with a typical GPT-5.5 agent run consuming between 5 and 25 credits. Agent runs invoked outside ChatGPT, such as those triggered inside Slack, remain in free preview for now with no announced end date.
IT admins managing both Microsoft and OpenAI enterprise deployments now have parallel billing deadlines within weeks of each other. The per-group caps and Cost API are the primary controls available before the July 6 rates take effect.
Update, 18 June 2026: Microsoft Confirms Heavy Copilot Power-User Costs Are ‘Very High’ as Credits Billing Rolls Out
Work IQ API reached GA on June 16 as reported, but a statement from Microsoft leadership now reframes why the consumption-based billing model exists in the first place. Speaking to Axios, Microsoft EVP Charles Lamanna said directly: “We have users who do hundreds of tasks a week, which is great, they’re way productive, but the consequence is the costs can go very high.” That admission shifts this story from a billing mechanics update to confirmation that structural cost pressure at the power-user level drove the Credits model into existence.
The practical stakes are not hypothetical. GitHub Copilot’s move to token-based billing on June 1 saw some users jump from $29 to nearly $750 per month, according to TechCrunch. Enterprise teams should treat that as a reference point when modeling exposure under Credits billing. EY’s June 2026 analysis puts the average cost per AI interaction at $1.20, up from $0.04 in 2023, a roughly 30x increase driven by agentic workflows that chain multiple model calls per task.
The admin configuration steps covered in the original article remain accurate and remain required before any Work IQ consumption can begin. Admins should also note the new cost management dashboard in the Microsoft 365 admin center, which supports Credit usage review, prepaid or pay-as-you-go billing selection, and spending limits. Those controls are worth configuring before power users find their stride.
Work IQ API reaches general availability on June 16, and billing is off by default
Work IQ is the intelligence layer underneath Microsoft 365 Copilot. It handles the context, relationships, and reasoning that lets Copilot and agents understand your work, your data, and your organisation. From June 16, 2026, the Work IQ API reaches general availability and moves to consumption-based billing using Copilot Credits, Microsoft’s unified currency for AI service consumption across Copilot Studio, Dynamics 365 agents, and now Work IQ.
The important immediate point for IT admins: nothing is charged automatically. Billing is off by default. But if your organisation is running custom agents or third-party applications that ground in Microsoft 365 data through Work IQ, someone needs to turn it on before June 16, or those agents stop working.
Who is affected, and who is not
There is a clean split here, and it matters.
Microsoft 365 Copilot licensed users accessing Microsoft-built agents and experiences (the standard Copilot in Teams, Outlook, Word, and so on) are not affected. Work IQ usage in those pre-built agents is covered by the existing M365 Copilot licence. No additional Copilot Credits required, no new billing configuration needed for that slice of your user base.
Third-party and custom agent users are a different story. If your organisation has built agents in Microsoft Copilot Studio, Microsoft Foundry, or any third-party AI platform that calls the Work IQ API to ground responses in Microsoft 365 data, those calls move to consumption-based billing. That billing flows through your Copilot Credit balance, and it will not work at all until an admin configures it.
There is no separate Work IQ SKU. There is no per-user licence to buy. All charges simply draw from the Copilot Credit pool.
What admins need to configure
Microsoft has introduced new cost management controls inside the Microsoft 365 Admin Center specifically for this. The steps are not especially complex, but skipping any of them has real consequences.
Step one: enable consumptive billing. Navigate to the Microsoft Admin Center, go to Copilot, then Billing and usage, and turn on credit-based billing for Work IQ. This is the gate. Nothing flows until you do this.
Step two: set up a billing policy. A billing policy defines the billing infrastructure for the pay-as-you-go service. A new Copilot Credit policy type is now available alongside the classic billing policy type, which means you no longer need to connect an Azure subscription for supported services. Creating the policy alone is not enough, though. You must also connect the billing policy to the Copilot service to complete the setup.
Step three: configure spend policies and usage limits. This is the new cost management layer Microsoft has built out. Admins can set monthly consumption limits at the tenant level, for specific groups, or for individual users. You can add budget limits to billing policies and configure email notifications to fire when you hit percentage milestones, say 50%, 80%, and 100% of a budget. For Copilot Studio agents specifically, monthly consumption limits can be defined per agent regardless of whether the environment uses prepaid capacity or pay-as-you-go billing.
Step four: monitor via the Copilot Credits report. The Copilot Credits report in the Admin Center gives you total credits used, daily and cumulative time series, and breakdowns per user, per agent, per billing policy, and per agent-user pair. One small gotcha: the Billing Policy ID is anonymised by default in the report. Global admins can change that setting if you need the full picture.
How the pricing actually works
Work IQ API charges have two components. There is a variable charge for query-style consumption, covering grounding, retrieval, and reasoning. There is also a static usage component for actions and tools invoked through Work IQ. The two together make up the per-call cost.
To give you a rough sense of scale, Microsoft has published scenario-based pricing examples. A light query, something like pulling tasks assigned to you and compiling a checklist, runs approximately $0.20 to $0.40 per call. A medium query, such as reviewing customer interview emails to surface themes and roadmap implications, runs $0.30 to $0.75 per call. Heavier reasoning scenarios sit above that range.
Copilot Credits themselves can be obtained two ways. Pay-as-you-go billing draws on an Azure subscription and charges as you go. Prepaid capacity packs are available through Copilot Studio licensing at $200 per pack of 25,000 credits per month. The same credit pool covers Work IQ API usage, Copilot Studio agents, Dynamics 365 first-party agents, and Microsoft 365 Copilot Chat for users without a licence.
The governance angle
The controls Microsoft has built here are genuinely useful for large organisations. A single place to switch on credit-based billing, set policy limits across users and groups, and monitor consumption is a meaningful improvement over piecing that together from Azure cost management tooling. Work IQ API is the first product managed through this experience, with Copilot Studio and other products following.
There is also a security layer worth noting. Work IQ ships with a Rego-based policy engine that evaluates every request against resource paths, methods, user identity, and content. Agents cannot access data that the requesting user cannot access. There is no privilege escalation path. Admins manage Work IQ MCP servers centrally in the Admin Center and can allow or block servers across the organisation.
The practical to-do list
If you are responsible for Microsoft 365 administration and your organisation has any custom or third-party agents grounded in Microsoft 365 data, the actions before June 16 are straightforward. Enable consumptive billing in the Admin Center. Create a billing policy using Copilot Credits. Connect it to the relevant service. Set spend limits and alert thresholds so you are not flying blind. Pull the Copilot Credits report into your regular monitoring rotation.
If your organisation is purely using Microsoft-built Copilot experiences with M365 Copilot licences, there is nothing urgent here. Keep an eye on the Admin Center as Microsoft extends these controls to Copilot Studio and other services in the coming months, because the same billing framework will apply.
The broader shift is that Microsoft is consolidating AI service billing under one currency and one management interface. Work IQ GA is the first product to land in that framework at general availability. It will not be the last.