Work IQ grounds Copilot agents in your Dynamics 365 data

The reason your Copilot agent gives useless answers is that it has never seen your system of record. Microsoft is fixing that: Work IQ grounds Copilot and agents in core business data from Dynamics 365 and Power Platform, with public preview starting September 30, 2026. Email and Teams transcripts were never the hard part. Getting an agent to know what your company means by "account," "contract," and "equipment" is, and that is what this release goes after.

What actually happened

Per Microsoft's Dynamics 365 blog, Work IQ builds a semantic model over Dynamics 365 (Sales, Service, Finance, Operations), Power Platform, Microsoft 365, third-party line-of-business apps, and Dataverse as the storage layer.

The model does not just read schema. It derives meaning from business logic already sitting in views, forms, and relationships, and adds a business glossary for organization-specific terminology. Every agent drawing from the same model shares one definition of your entities.

Access is controlled on two levels: IT admins decide which users, agents, and applications can reach business data; makers shape how specific data is exposed within those boundaries. Responses are trimmed to the requesting user's permissions, governed across the Microsoft 365 and Power Platform admin centers.

The developer surface is the notable part — Microsoft named a Dataverse Ask API, a Work IQ MCP Server, a Work IQ CLI, and a Work IQ plugin for coding agents. Public preview begins September 30 with rollout through October; ERP apps arrive late October 2026.

Why grounded business data matters for your business

A semantic layer is the thing most agent projects skip and then die on. Pointing a model at raw tables produces an agent that confidently joins the wrong two things. Views, forms, and relationships already encode how your business actually thinks — mining those instead of the schema is the correct move, and you can do the same thing against Postgres without Microsoft.

The business glossary is a cheap idea you should steal today. Write down what your company means by "active customer," "closed," and "churned," in one file, and feed it to every agent. We have watched two agents at the same company report different revenue numbers because one counted refunds and the other did not. That is a glossary problem, not a model problem.

Permission-trimmed responses are the gate on ever shipping this. An agent that answers from the org's full dataset will eventually tell a support rep what the CFO makes. If your own stack does not enforce row-level access on the agent's queries the way your app does for users, you are one clever prompt from a disclosure.

An MCP server on your system of record is the part with legs. Once CRM data is behind MCP, it is reachable from Claude, from your own agents, from a coding assistant — not just from Copilot. That is a real portability gain, and it is also a new front door. Log every call and scope the token.

Preview means preview. Public preview September 30, rollout through October, ERP late October. Pilot it against a read-only slice. Do not put a finance workflow on a preview semantic layer this quarter.

Sources: Microsoft Dynamics 365 Blog, Microsoft Learn.