LaunchedMicrosoft Copilot (Microsoft 365)RELEASE: June CY2026
The plumbing under custom Copilot agents just changed
A single REST endpoint for Work IQ replaces the older, more fragmented Copilot Chat endpoints that agent builders used to target.
Source: Microsoft Copilot (Microsoft 365): Work IQ APIs – Unified REST Endpoint for Agents and Workflows —
Microsoft 365 Roadmap, item 559021
Before you act on this: these entries are drafted with AI assistance from Microsoft's
own roadmap feed, in the interest of keeping this readable and current. AI can make mistakes — names,
dates and what a feature actually does can be summarised wrong. Treat everything below as a starting
point, not advice. Always check back to the source roadmap entry linked below, and do your own
human-in-the-loop validation before you tell anyone else what to do about it.
What it is
A new REST API endpoint for Work IQ, Microsoft's name for the layer that lets Copilot and custom agents query your organisation's Microsoft 365 data and workflows.
What it does
It gives developers one consistent entry point for invoking agents and workflows, replacing the older, more fragmented Copilot Chat endpoints.
Why I should care
You won't call this API yourself, but if your organisation is building custom Copilot agents through Copilot Studio, Agent Builder, or a direct integration, this is the plumbing those agents increasingly sit on. An agent built against the old endpoints isn't broken, but it's now built on a path Microsoft is investing less in.
What action I need to take
If you commission or oversee agent development work, ask whoever is building your agents whether they're targeting the new unified endpoint or the legacy one. It's a fair question to ask before you sign off on a build, not after it ships.
Your notes
Saved only in this browser — it never leaves your device.