The phrase Work IQ has started turning up in places an IT manager cannot ignore. It is the label on a new button in the top left of Microsoft 365 Copilot Chat. It appears in the PowerPoint release notes. It sits in the Microsoft 365 roadmap as a set of APIs with pay-as-you-go billing. And it is now in the Viva Insights consumption dashboard as a line item alongside Cowork. Clients have been asking Frontrow the obvious question: is this a new product, a new licence, or a new name for something that was already running? The short answer is mostly the third, with one genuinely new commercial element attached.
This note sticks to what Microsoft has published. Where the documentation is thin, it says so rather than filling the gap with guesswork.
What Microsoft means by Work IQ
Microsoft's own definition, from the Work IQ API overview on Microsoft Learn, is that "Work IQ is a workplace intelligence layer that combines Microsoft 365 data with contextual understanding so agents can reason over work and take action." The Microsoft IQ documentation hub positions it as one of four related capabilities: Work IQ for "live understanding of how employees work, with context on people, collaboration, and workflows", Fabric IQ for the live state of the business, Foundry IQ for curated institutional knowledge, and Web IQ for fresh web intelligence.
In plainer terms: Work IQ is the name Microsoft now gives to the grounding layer under Copilot. The same Learn page lists what it can reason over, and the list is familiar to anyone who has run a Copilot pilot: email messages, meetings and calendar data, documents in OneDrive and SharePoint, Teams messages, people and organisational context, Planner plans and enterprise search results. None of those sources is new. What is new is that Microsoft has given the layer a name, put a user-facing switch on it, and opened it to developers as an API with its own billing.
Where a user actually sees it
The most visible change landed in the 25 August 2026 release notes. Web and work chats in Microsoft 365 Copilot Chat were unified into a single interface with a dedicated Work IQ button in the top left, used to switch access to work data on or off without leaving the chat. Work data is on by default. For a user, this replaces the old habit of flipping between separate web and work tabs, and it is worth telling staff about: the button is the simplest way to confirm whether a given answer was grounded in tenant data or only the web.
The second place is PowerPoint. Roadmap item 555886, launched with general availability listed as March 2026, lets a user "reference an email with Work IQ when using Edit with Copilot in PowerPoint to create a presentation" on Mac. The 25 August release notes describe the matching Windows capability: a user references an email by its subject, the senders, and the time frame or date it was sent, and Copilot uses that email as context for the deck. This is a small feature with a large implication, because it means the email store is now a first-class input to document creation, not only to chat.
The Work IQ APIs and pay-as-you-go
Roadmap item 559017, Work IQ APIs: Pay-As-You-Go usage, is marked launched with general availability listed as June 2026. Microsoft's description: it "enables metered, pay-as-you-go access to Work IQ endpoints, allowing developers to invoke agents and capabilities without requiring pre-assigned licenses, with usage billed based on the agents and models invoked per request." The 25 August release notes add a unified REST endpoint for Work IQ (roadmap 559021) that serves as a single entry point for invoking agents and workflows in place of the older Copilot Chat endpoints.
The Learn documentation describes three protocols: Agent-to-Agent (A2A) for one agent delegating a task to Work IQ, Model Context Protocol (MCP) for an AI assistant calling Work IQ as a tool, and REST for an application that sends a prompt and renders the reply. The REST overview is candid about limits that matter for scoping: it returns text only, it does not create files, send email or schedule meetings, it does not support long-running tasks, and it is subject to the limitations of the Microsoft 365 Copilot semantic index. Anyone imagining an autonomous back-office agent built on the REST API alone should read that list first.
Enabling the API in a tenant is a one-time job. The Learn guide lists the prerequisites as a usage-based billing plan set up in Copilot Studio with an Azure subscription and resource group assigned, plus a Global Administrator to create the Work IQ service principal. Frontrow's read is that this is deliberately an admin decision, not something a developer can switch on quietly from a workstation.
What "work context" means for permissions
This is the part the CISO should care about, and the documentation is clear. The Work IQ API overview states that access to Microsoft 365 data is "automatically permission-trimmed and policy-enforced". The REST overview says that within an organisation "the permissions model in Microsoft 365 ensures that individuals can only get results from the content they're allowed to access." Work IQ does not create a new access path. It surfaces what the signed-in user can already open.
That is reassuring and alarming in equal measure, because in most Australian SMB tenants the set of things a user can already open is far wider than anyone intended. A site shared with Everyone except external users in 2019, a finance library inherited from a migration, a Teams channel with a forgotten guest: all of it is in scope the moment Work IQ is reasoning for that user. Microsoft's 6 October release notes add a useful tool here, a SharePoint Advanced Management report giving item-level detail of permissions granted to the Everyone and Everyone except external users groups (roadmap 561038).
The practical consequence is that two unglamorous jobs decide what Work IQ can reach: SharePoint permission hygiene and sensitivity labels. Frontrow's SharePoint and OneDrive permissions checklist before Copilot (/insights/sharepoint-onedrive-permissions-checklist-before-copilot) covers the first. The stale content cleanup guide (/insights/sharepoint-stale-content-cleanup-before-copilot) covers the second-order problem, which is Copilot confidently citing a superseded policy because nobody archived it. The DLP and sensitivity label recipes (/insights/copilot-dlp-sensitivity-labels-policy-recipes) cover the controls that actually block, and the broader question of whether company data is safe with Copilot is answered at /insights/is-microsoft-365-copilot-safe-company-data.
What pay-as-you-go means for the bill
Pay-as-you-go here means usage is metered per request and billed according to the agents and models invoked, with no requirement for the calling user to hold a pre-assigned Copilot licence. For a CFO that is the important sentence. A per-seat licence has a ceiling. A metered API does not, and the cost of a request depends on what the request turns out to require.
Microsoft has shipped the visibility to go with it. The 11 August release notes describe a Consumption Dashboard in Viva Insights that tracks Copilot credit usage for Cowork and Work IQ API services (roadmap 566302). It is enabled by default, requires usage-based billing to be set up via Cost Management in the Microsoft 365 admin centre, and is scoped to managers with at least five direct reports, Insights analysts and Global Administrators. Nothing in the material Frontrow has reviewed states a unit price for Work IQ API calls, so this note does not quote one. The same credit-based model applies to Copilot Cowork, and the spending limits, alerts and pilot scoping in Frontrow's Cowork pre-enablement checklist (/insights/copilot-cowork-spending-limits-before-enabling) apply to Work IQ API usage in exactly the same way: set the limits before the first developer gets a token.
What Frontrow recommends
- Tell staff what the Work IQ button does. It is on by default, and a surprising number of users will assume the opposite.
- Treat the API enablement as a change request with a named owner, because it requires a Global Administrator and a billing plan with an Azure subscription behind it.
- Run the Everyone except external users permission report before any Work IQ API project, and fix what it finds.
- Put a spending cap and an alert on the usage-based billing plan on day one, and check the Consumption Dashboard weekly for the first month.
- Scope developer pilots to the REST API's actual capabilities: text answers grounded in tenant and web data, nothing that acts.