Microsoft Work IQ APIs go GA on June 16: what agent builders get
Microsoft says Work IQ APIs will reach general availability on June 16, 2026, giving enterprise agents a governed way to use Microsoft 365 context, tools, workspaces, and Copilot intelligence.
Microsoft says the Work IQ APIs will become generally available on June 16, 2026. The APIs are designed for agents that need Microsoft 365 context, actions, and workspace state without building a separate retrieval and governance stack. The most important detail for builders is that Work IQ combines agent-facing protocols with tenant-bound permissions, auditability, and consumption-based pricing through Copilot Credits.
Key takeaways
- Work IQ APIs are scheduled for general availability on June 16, 2026.
- Microsoft positions Work IQ as the Microsoft 365 intelligence layer for agents, built around Chat, Context, Tools, and Workspaces.
- The developer blog says GA will include A2A, a redesigned remote MCP server, and REST API access.
- Licensing guidance says Work IQ API usage is consumption-based through Copilot Credits, with no separate Work IQ API subscription, SKU, or per-user license.
- Security controls matter because Work IQ agents can act on workplace data; Microsoft emphasizes tenant boundaries, permission trimming, audit logs, and admin cost controls.
Practical LinkLoot angle
Work IQ is useful if your agent needs to reason over email, calendar, meetings, Teams, files, people, SharePoint, OneDrive, and related work context. It is less useful if you only need a generic RAG layer over a few documents.
| Use case | Work IQ fit | Why it fits | Limitation to check |
|---|---|---|---|
| Enterprise assistant | Strong | Uses Microsoft 365 context and user permissions | Requires Microsoft ecosystem access and identity setup |
| Developer MCP workflow | Strong | Microsoft says Work IQ supports MCP patterns for tool access | Check whether local or remote MCP fits your rollout date |
| Lightweight document Q&A | Mixed | It can ground answers, but may be more platform than needed | Compare cost against simple vector search |
| Third-party agent grounding | Strong | Licensing says third-party agents can call Work IQ APIs | Verify data handling, auditability, and Copilot Credit billing |
The decision point is governance. If an agent needs to send mail, schedule meetings, fetch files, or write intermediate state, the control plane matters more than the model choice. If the workflow only summarizes a static PDF folder, Work IQ may be unnecessary overhead.
What to verify before you act
Check three things before committing a build plan. First, confirm which Work IQ protocol you need: A2A for agent delegation, REST for app integration, or MCP for tool-style access. Second, verify authentication and permission behavior with a real tenant because Microsoft Learn notes delegated user context and existing Microsoft 365 governance controls. Third, model usage cost with the licensing examples instead of assuming it behaves like a flat API subscription.
Also verify the GA surface on or after June 16. Microsoft Learn pages still reference preview behavior in places, while the June 2 announcements describe the upcoming GA endpoint set.
Source check
The Microsoft 365 Blog confirms the June 16 GA date, Work IQ's four API domains, and the agent-focused value proposition. The Microsoft 365 Developer Blog corroborates GA scope across A2A, remote MCP, and REST, while Microsoft Licensing Resources confirms the Copilot Credits consumption model and example usage ranges.
For practical agent design, pair this with LinkLoot's guide to AI workflow automation. The useful build pattern is to start with one narrow workflow, measure tool calls and Copilot Credit draw, then widen access only after audit logs and budget controls match the risk.
Microsoft says Work IQ APIs will reach general availability on June 16, 2026.