What Microsoft announced
Work IQ is meant to ground Copilot and agents in business data from Dynamics 365 and Power Platform and reason across that data together with Microsoft 365 productivity data. The business applications remain the systems of record; Work IQ models their data and processes into context agents can reuse. In addition, 'business skills' let teams describe a procedure once and make it available to connected agents, such as a multi-step renewal-readiness check.
The preview started on 30 September 2026 and rolls out through October. Dynamics 365 Finance and Operations is slated for late October, per Microsoft. The post makes no statement on general availability. One trade report names November 2026 as a target; that's a secondary claim.
The line that matters: context from the existing configuration
Per Microsoft, Work IQ combines 'a focused data scope and semantic indexing with knowledge from your existing business applications' and draws on business logic in views, forms, and relationships plus a business glossary. Context is derived automatically from the existing configuration. Admins and makers can refine this: enable or disable signals, exclude outdated views or relationships, and add vocabulary the system can't infer itself.
Something obvious follows that isn't front and center in the announcement: a system that learns from configuration also learns from what has been sitting there for years. One trade report puts it as Work IQ learning from outdated elements too. That's the report's analysis, not Microsoft's statement. It's plausible anyway, because the mechanism is described by Microsoft itself. Anyone who has accumulated views, fields, and relationships over ten years of Dynamics use that nobody uses anymore hands those to the agent as context unless they're excluded.
The tool, and the gap next to it
Microsoft offers excluding outdated views and relationships. What the post doesn't describe is a way to find out which elements are outdated. That judgment stays with the people who know the system. In a grown CRM with several admins and generations of customization, that's exactly the laborious part: working out which views are still needed, which fields are still maintained, which relationships are still correct.
That's our reading. It rests on Microsoft's own description of the mechanism and on the post naming no detection tool; one may exist outside the post, and we couldn't rule that out. The practical consequence is independent of that: before switching it on, an inventory of the configuration is worthwhile.
What's only backed by secondary sources
Two points with practical impact aren't in Microsoft's post. First, activation: a trade outlet, citing Message Center item MC1483492 from 30 September, writes that the business-apps features are on by default in new production environments with the right licenses. Older environments, non-production types, and government cloud variants are excluded, with an opt-in in EU/EEA regions. The outlet, however, only links a third-party mirror of the item, not a Microsoft page. Second, billing: several reports name usage-based billing via Copilot Credits. Microsoft's post links a page on usage-based billing but names no prices itself.
At the same time, a community summary of Microsoft's position says the preview isn't meant for production use. Production environment and preview don't fit together easily. We therefore don't claim anything is active in your tenant, but recommend checking the item in your own Message Center.
What this means in practice
- Search your own Message Center for the Work IQ item and check in the Power Platform admin interface whether the feature is active for your environments before anyone deliberately switches it on.
- Before using it, inventory your Dynamics configuration: unused views, dead fields, outdated relationships, inconsistent terms. It's manual work, but it determines what the agent gets as context.
- Maintain a business glossary: if terms mean different things in different departments, the system can't infer that, as Microsoft itself writes.
- Run write-capable agent actions with mandatory approval at first, and check the permissions of the users on whose behalf the agent works.
- Clarify costs before broad use: Copilot Credits billing is only secondary-sourced, and we have no prices.
- Treat it as a preview and don't build production processes on it until Microsoft confirms general availability and pricing.
The core of this analysis: Work IQ shifts the work an AI project does in the CRM from model choice to configuration upkeep. That's a familiar pattern we saw in the NBER study on organizational support - here it gets a concrete technical mechanism. Whether the mechanism works in daily practice as described will only show with field reports from the preview.