Microsoft's Work IQ preview for Dynamics 365 and Power Platform builds Copilot's understanding of your business from the views, forms and relationships your CRM already has, including the outdated ones. Agents can then update records within each user's permissions. If your Dynamics configuration has ten years of abandoned views and half-retired relationships in it, the agent will learn from those too. So before you switch it on, prune the configuration, decide which environments take part, and set a Copilot Credits limit. ERP customers should not plan production use until Finance and Operations support actually arrives.
The public preview opened September 30, 2026 and rolls out through October, covering Dynamics 365 Sales, Customer Service, Power Apps and third-party line-of-business apps. Microsoft marks Dynamics 365 Finance and Operations as "rolling out in late October 2026."
What Work IQ Actually Adds to Dynamics 365
Work IQ for business applications is a shared semantic model plus reusable procedures plus write access, sitting between your Dataverse data and every agent that asks a question about it. Microsoft's announcement by James Oleinik describes three parts:
- A semantic model. It combines a scenario-based scope of tables and columns with semantic indexing, and it takes business logic "from views, forms, and relationships" plus a business glossary. Every agent that uses the model gets the same reading of what a record means.
- Business skills. A skill is a packaged procedure: instructions, context and supporting resources. Microsoft's example is a four-step renewal skill (check unresolved critical cases, confirm a service-plan owner, document the customer commitment, get approval before offering a concession). Skills are reusable across any agent connected to the Work IQ MCP server, Copilot Studio agents included.
- Governed actions. Copilot and agents propose a change, route it through required approvals, and then update the source record "within the user's permissions." The examples are reassigning ownership, escalating a case to Critical priority and updating a contract record.
A semantic model, in this sense, is a machine-readable map of what your records mean and how they connect, so an agent can answer "which renewals are at risk" without someone writing per-agent instructions about which tables hold renewals. Dataverse stores the models and skills and exposes a new Dataverse Ask API. Developers also get a Work IQ MCP server, a CLI and a plugin for coding agents.
This extends the Work IQ APIs Microsoft announced on June 2, which grounded agents in Microsoft 365 email, meetings, chats and files. We covered that layer in Microsoft IQ's data silo pitch. The September preview adds the half most enterprises actually run the business on: CRM records and line-of-business apps.
Why Stale CRM Configuration Becomes Agent Error
Stale configuration becomes agent error because the model takes its meaning from the configuration you have now, not the configuration you meant to clean up. ERP Today's write-up puts it plainly: Work IQ "learns from existing views, forms, and relationships, including outdated ones," so accuracy depends partly on how well that configuration has been maintained.
Think about what a typical Dynamics 365 tenant holds after a few years. There are system views nobody uses, personal views promoted to system views during a reorg, a "Key Accounts" view whose filter still points at a territory that no longer exists, and lookup relationships kept alive because deleting them would break a report. A person ignores those because they know the history. A semantic model treats each one as a signal about what your business considers important.
The controls exist. Microsoft says admins can enable or disable signals, exclude outdated views or relationships, and add business vocabulary the system cannot infer. What the controls cannot do is tell you which views are outdated. That takes an inventory and someone who owns the CRM's data model.
The stakes rise once agents write. A wrong answer in a chat pane wastes a user's time. A wrong write (a case escalated to Critical, an account reassigned, a contract record changed) lands in the system of record, triggers whatever workflows hang off that field, and runs under a real user's permissions. Microsoft routes those writes through "required approvals," but the approval is only as good as the reviewer's attention. Our guide to human-in-the-loop gates covers how quickly those turn into rubber stamps.
To be fair to Microsoft, deriving context from existing configuration is also the reason this could work at all. John Siefert at Cloud Wars calls reusable skills the "unglamorous plumbing" that separates production AI from demo AI. Grab's analytics agents hit the same limit, where metric context set the ceiling. Work IQ gives you a head start built from work you already did. It also inherits whatever debt is in that work.
It May Already Be On in New Environments
Work IQ is not purely opt-in. Message Center post MC1483492, published September 30, 2026, says Business Applications in Work IQ (Dataverse data search and query, semantic modeling, business skills and declarative agent access to Dataverse) is "enabled by default" for all new environments where Microsoft Copilot Premium and either Power Apps Premium or Dynamics 365 products are active.
The same notice lists what is excluded: environments created before September 30, 2026, EU and EEA regions, non-production types (trial, developer, sandbox), government clouds and FedRAMP environments. EEA and FedRAMP tenants get an opt-in instead. It also warns that enabling the feature creates "additional supporting indexes" and causes token consumption, without giving numbers.
Read that list against your provisioning habits. Your existing production environments stay off. A new production environment that a business unit spins up next month, in a US region, with the right licences, starts with Work IQ on. That contrasts with Dynamics Communities' summary of Microsoft's position that the preview "isn't meant for production use." If your Power Platform environment strategy lets makers create production-type environments, that default is now a governance setting you own.
Who Holds Which Control
Control is split across three roles with no new portal, and that split is the part most likely to fall between teams. Per Microsoft's post:
- The AI admin manages who can use AI and sets AI policy in the Microsoft 365 admin center.
- The Power Platform admin decides which business environments participate and who has access.
- Makers and developers shape how specific business data is exposed, inside those boundaries.
Work IQ agents run under Microsoft Agent 365, which Microsoft says makes their use of business data observable to IT. In many companies the first role sits with the Microsoft 365 team, the second with a business-apps or CoE team, and the third with whoever built the CRM customizations. Nobody in that chain owns "is this view still correct." Microsoft's own Customer Zero rollout to 20,000 agent makers relied on environment routing and a cleanup cycle to stay in control; plan for the same.
The data-access side has a known failure pattern too. When Salesforce customers learned that a public web form could become an Agentforce data leak, the root cause was agent tool scope wider than anyone had mapped. Work IQ's governed actions respect user permissions, but an agent acting for a user with broad security roles inherits all of them.
What It Will Cost
Work IQ bills through Copilot Credits, and Microsoft has not published a per-scenario rate for the business-apps preview. ERP Today confirms usage-based billing through Copilot Credits; Microsoft's post links to its usage billing documentation but gives no prices.
What is published comes from Microsoft's Copilot Credits licensing guidance:
- Pay-as-you-go is $0.01 per Copilot Credit, billed in arrears at the end of the month.
- The Work IQ Tools API costs 0.1 credit per call. The Chat and Context APIs are variable, with no fixed per-call rate.
- Dynamics 365 agents, prebuilt and custom, consume credits. Agents and Work IQ APIs on Power Apps Premium are not covered by its request limits.
- Credits pool at the tenant level. Pre-purchase plans run from 300,000 credits at 5% off to 300,000,000 at 20% off, and unused credits expire at the end of the annual term.
Tenant-level pooling is the line to watch. A Dynamics agent that runs variable-cost Chat and Context calls on every renewal review draws from the same pool as everything else billed in Copilot Credits. The June Work IQ API launch added a cost dashboard in the Microsoft 365 admin center with prepaid or pay-as-you-go billing and spending limits. Set the limit before the first pilot, as we argued when Copilot Autopilot moved outside the $30 seat. Siefert notes that usage-based billing "will need to keep adoption affordable."
Finance and Operations Support Has Not Shipped Yet
Finance and Operations support is a late-October rollout, and nothing about it is in the current preview. ERP Today calls ERP scenarios a planned capability, and Dynamics Communities advises Finance and Supply Chain customers to "use the coming months to prepare rather than deploy." That piece also reports Work IQ is replacing Dataverse intelligence, which is being retired as a standalone service; we could not find a Microsoft deprecation notice with a date, so treat it as reported, not confirmed.
Some of the groundwork predates this preview. Microsoft's March 9 Dataverse post added a semantic layer to Dataverse Search and put Copilot in Power Apps and Dynamics as a sidecar. Work IQ formalizes that layer and adds write-back. ERP records (journal entries, vendor master data, purchase orders) carry a different risk profile from a CRM case. Wait until you can test the F&O semantic model against your own chart of accounts before you let any agent near it.
What to Do Before You Enable It
This Week:
- Ask your Power Platform admin to list every production environment created on or after September 30, 2026 in a non-EEA region with Copilot Premium and Power Apps Premium or Dynamics 365 active. Per MC1483492, those have Work IQ on by default. Decide for each one whether it stays on.
- Name one owner for each of the three control layers (AI policy, environment participation, data exposure) and write the names down. If one person holds two roles, say so explicitly.
- Set a Copilot Credits spending limit in the Microsoft 365 admin center before any Work IQ pilot starts.
This Month:
- Inventory system views, forms and relationships on the tables your pilot will touch (Account, Opportunity, Case and Contract at minimum). Mark each as current, outdated or unknown, and exclude the outdated ones in Work IQ.
- Write the business glossary for the twenty terms your sales and service teams argue about: what "at-risk renewal," "key account" and "critical case" actually mean in your filters.
- Run the pilot read-only first. Ask the same twenty questions a sales manager would ask and grade the answers against what the manager says is true. Turn on governed actions only for the scenarios that grade well, and keep approvals on.
Before Late October:
- If you run Finance and Operations, document the two or three processes you would want as business skills (supplier recommendation is Microsoft's example) and stop there until F&O support is live and testable in a sandbox.
- Price a realistic pilot by counting the agent calls your renewal or case process would make per week, then compare it with your true Copilot cost per seat and the consumption caps we recommend for agentic pricing.
The Bottom Line
Work IQ is Microsoft's most direct attempt yet to turn the configuration enterprises already built in Dynamics 365 into context an agent can use, and Microsoft pitches it as a way to cut per-agent instruction writing. The cost of that shortcut is that every agent reads your business through whatever configuration you have today. Self-service BI went through the same cycle, and the fix there was a certified semantic layer with a named owner. Prune the views, cap the credits and keep F&O in a sandbox until late October delivers what it promised.
Continue Reading
- Microsoft IQ Cracks AI's 600TB Data Silo Problem
- Microsoft Hit 20,000 Agent Makers on a Risk Rubric It Didn't Publish
- Microsoft's New Copilot Bills Autopilot Outside the $30 Seat
- True Cost of a Copilot Seat: The Licence Is the Floor
- Human-in-the-Loop for AI Agents: Most Approval Gates Rubber-Stamp
- Grab Ran Analytics Agents 5 Months. Context Was the Ceiling.