Work IQ API GA: What Partners Should Prepare Before Consumption Billing Starts

Microsoft is moving Work IQ API into general availability on June 16, and the commercial model is now clear: usage will be metered through Copilot Credits rather than through a separate Work IQ subscription, SKU, or per-user license. For partners building agents, integrating Microsoft 365 context into applications, or advising customers on Copilot extensibility, this is an important operational change as well as a product milestone.

Partners should treat June 16 as both a launch milestone and a customer-readiness checkpoint. Customers that are already experimenting with Work IQ in preview, or that plan to use custom agents grounded in Microsoft 365 data, will need administrative and billing decisions in place before production usage begins.

What changed

Work IQ API is designed to let agents and applications use Microsoft 365 data, context, and tools in a secure and scalable way. With general availability, Microsoft is attaching Work IQ API usage to a consumption model based on Copilot Credits. Copilot Credits are Microsoft’s shared consumption currency for several AI services, including Microsoft Copilot Studio, and they will now apply to Work IQ API usage as well.

The practical result is that customers do not buy a standalone Work IQ API license. Instead, usage by eligible custom or third-party agents consumes Copilot Credits when users interact with those solutions. Billing is therefore tied to actual usage, payment configuration, and administrative controls in Microsoft Admin Center.

This matters because many customers have treated Copilot-related extensibility as a licensing conversation only. Work IQ API introduces a governance conversation too: who is allowed to use these APIs, which applications should have access, how spend is monitored, and what limits or alerts should be in place before production adoption expands.

Who is affected

The announcement is especially relevant for software development companies, systems integrators, and Cloud Solution Provider partners. These partner types are likely to build, resell, advise on, or support custom agents that use Microsoft 365 data through Work IQ APIs.

Customers using Microsoft 365 Copilot prebuilt agents are in a different position. Microsoft states that Work IQ usage for those prebuilt agents is covered by the relevant licensing, so Copilot Credits are not required for that scenario. The new billing consideration applies when customers use custom agents created in Microsoft Copilot Studio, Foundry, or third-party AI platforms that are grounded in Microsoft 365 data through Work IQ APIs.

That distinction should be made very clearly in customer conversations. A customer may have Microsoft 365 Copilot licenses and still need to configure consumption billing if they want to run custom Work IQ-powered agents. Conversely, a customer using only Microsoft’s prebuilt Copilot agents may not have any immediate Copilot Credit action to take for Work IQ.

Default behavior and customer impact

Before Work IQ API usage can begin at GA, an administrator must enable consumptive billing. In practice, that means customers should not assume that preview usage patterns will automatically continue unchanged after June 16. If a solution depends on Work IQ API and the customer has not configured the required billing and access controls, users may face disruption or be unable to use the custom agent as expected.

The default partner risk is not simply “the customer gets billed.” The more common risk is lack of readiness: no payment method configured, no policy owner identified, no consumption limits set, and no clarity on which groups should have access. These gaps can create support tickets, project delays, or uncomfortable spend-governance discussions after deployment.

For customers already piloting Work IQ API, partners should review every pilot and proof of concept before June 16. Identify which agents or applications call Work IQ, which users are involved, which environments are production-bound, and who owns the Microsoft Admin Center configuration. If the pilot is moving toward production, the billing and access setup should be part of the go-live checklist rather than an afterthought.

Recommended partner actions

First, inventory active and planned Work IQ API usage. This should include Copilot Studio agents, Foundry-based solutions, and third-party AI platforms connected to Microsoft 365 data. For each use case, document the business owner, expected user population, deployment timeline, and whether the workload is still experimental or production-facing.

Second, help customer administrators prepare Microsoft Admin Center. Customers should confirm the appropriate payment method, enable pay-as-you-go where required, and decide which services and users are allowed to consume Work IQ API. Partners should avoid treating this as a purely technical configuration. It is also a financial control and compliance control.

Third, define access policies before broad rollout. A good starting point is to grant access to named pilot groups or departments rather than the entire organization. This gives customers a controlled path to validate cost, security, and business value before expanding availability.

Fourth, configure limits and alerts. Consumption models work best when customers can see usage early and react before spend becomes a surprise. Partners should recommend practical alert thresholds for pilots and higher thresholds for production workloads, aligned to the expected value and scale of each agent.

Fifth, update customer-facing documentation and support runbooks. If your organization delivers managed services or custom agent projects, include Work IQ API billing readiness in onboarding, deployment, and renewal checklists. Support teams should know how to explain the difference between Microsoft 365 Copilot prebuilt agent coverage and custom agent consumption.

Bottom line

Work IQ API reaching general availability is a positive step for partners building intelligent applications around Microsoft 365 data. The key change is that production usage now requires a consumption-billing posture based on Copilot Credits. Partners should use the time before June 16 to identify affected customers, confirm billing setup, apply access controls, and put spend governance in place.

For customers, the message is simple: custom agents can unlock valuable Microsoft 365 context, but they should be deployed with the same discipline as any other metered cloud service.

Microsoft source: https://learn.microsoft.com/en-us/partner-center/announcements/2026-june#work-iq-api-and-consumptive-pricing-update