Work IQ APIs Are a Metered Surface, Not a Feature

Integration layers have typically been a fixed cost. You build a connector, host it, pay for the compute. The bill barely moves when usage does. That is why an architect can add one more call without asking anybody.
The Work IQ API breaks that habit, and it does so somewhere no architecture diagram shows.
What Are the Work IQ APIs?
A programmatic surface onto Microsoft 365 work intelligence, split into four domains.
Microsoft announced them on 2 June 2026, with general availability on 16 June 2026. The four are Chat, Context, Tools and Workspaces. Chat returns the answer Copilot would give a user, citations included. Context returns the raw material instead, shaped for an agent to use. Tools covers actions such as sending mail or booking a meeting. Workspaces gives an agent somewhere inside the tenant to park working state.
Useful capability. The thing to notice is how you pay for it.
How Is the Work IQ API Billed?
By consumption, in Copilot Credits.
Microsoft’s licensing note says the Work IQ API “will be billed through a consumption-based model using Copilot Credits.” It calls those credits “a unified consumption currency that also covers Copilot Studio and other Microsoft AI services.” Microsoft Learn repeats the model in its cost guidance. So this is not a feature that arrives with a licence. It is a meter.
What Does “No Per-User Licence” Actually Change?
Everything about who forecasts it. Microsoft states that “There is no separate Work IQ API subscription, SKU, or per-user license.” Nothing to buy means nothing to count. Most Microsoft forecasts a finance team has built start from a headcount. This one offers none.
Microsoft also names when you pay directly. You pay when you build your own agent or app that calls the APIs. You pay again when a third-party agent grounds in your Microsoft 365 data through them. That second case is easy to miss, because somebody else built the agent.
Which Calls Cost What?
Two components, and only one has a published rate. Microsoft splits consumption in two. A variable charge covers query-style work: grounding, retrieval and reasoning. A static charge covers actions and tools. The Chat API and the Context API carry the variable half. The Tool API sits at 0.1 Copilot Credits per API call.
That gap is the planning problem. Tool volume is arithmetic. Count the calls, multiply, get a floor. Chat and Context are not. Microsoft says plainly that prices “will vary based on the complexity of the scenario.” Its own worked examples are marked illustrative.
Who Does the Call Run As?
A signed-in person, in every supported flow. Microsoft Learn states that Work IQ “uses Microsoft Entra ID delegated authentication.” Requests “run in the context of the signed-in user.” On-behalf-of flows work. Application-only authentication does not. Microsoft 365 permissions, sensitivity labels and compliance policies apply on their own.
So there is no per-user licence, yet every call carries a user identity. A layer that once ran as a service account now runs as people. That helps governance and hurts forecasting. Consumption now follows adoption rather than infrastructure.
Where Do You Put a Ceiling On It?
In the Microsoft 365 admin center, and you should do it first. Microsoft is launching a cost management dashboard there. Admins can review credit usage and choose between prepaid and pay-as-you-go billing. They can set spending limits for tenants, groups and users across agents and services. They can also monitor credit requests. Microsoft says the Work IQ APIs are the first product managed through it.
Set the limit before the first call ships. A meter with no ceiling and no owner is simply an invoice you have not met yet.
What Has Microsoft Not Said Yet?
Two things that matter, so plan around the gaps rather than through them. Microsoft has not published a credit rate for Chat or Context. It has also not said what happens to a Work IQ call once a tenant runs out of credits. What it has said is that “The Copilot Credit balance can now be drawn down via your Work IQ APIs.” So the balance your agents already draw on is the balance your integration layer now draws on.
Copilot Studio documents its own rules, including agents blocked once a tenant passes a prepaid capacity threshold, and a monthly reset on agent flow enforcement. Do not assume those carry across. Check in your own tenant and write down what you find.
Frequently Asked Questions
Is the Work IQ API included with a Microsoft 365 Copilot licence?
No. Microsoft states there is no separate Work IQ API subscription, SKU or per-user licence. You pay through a consumption-based model using Copilot Credits.
When did the Work IQ API become generally available?
It reached general availability on 16 June 2026. Microsoft announced the date in a post published on 2 June 2026.
What does a Work IQ Tool API call cost?
The Tool API is listed at 0.1 Copilot Credits per call. Chat and Context carry a variable charge instead.
Can a Work IQ API call run without a user?
No. Work IQ uses Entra ID delegated authentication, and Microsoft states that application-only authentication is not supported.
Where do you cap Work IQ API spending?
In the new cost management dashboard in the Microsoft 365 admin center, where admins can set spending limits across tenants, groups and users.
What to Settle Before the First Call
The Work IQ API is a good capability in an unfamiliar cost shape. Nothing here is expensive on its own. The risk is that a design choice made in a sprint sets the bill.
So do four things. Count the tool calls, because that half is arithmetic. Measure the rest against real traffic, not a spreadsheet. Set the spending limit before the first call ships. Then name the person who watches it. We have argued before that the line between included and metered sits inside Copilot extensibility. Work IQ moves that line again. The integration layer used to be the part of the estate whose cost stayed still.
Microsoft’s licensing and pricing material is informational and changes without notice. Confirm your own position against your agreement, or with the partner who holds your contract, before you act on any of this.
At DAX Software Solutions, integration and agentic strategy sit in one conversation, because the call volume and the invoice come from the same design. If a team in your organization already builds against the Work IQ API, the budget question belongs in the design review. Talk to our team.