Microsoft's Ignite post says Business Applications in Work IQ, now generally available, adds CRM and ERP records to the grounding set, giving agents a fuller view of the business. The Azure Updates entry for this launch, marked "Launched", sits alongside that. In Azure's terms, "Launched" means fully released and production-ready. The Azure Updates page itself returned "0 Updates found" when we inspected it, so the Ignite posts and Microsoft Learn documentation are the working evidence here.
What was announced
Work IQ is Microsoft's context layer for Copilot and agents. Business Applications in Work IQ extends it from Microsoft 365 content (mail, meetings, chats, files) to line-of-business systems. Microsoft's Work IQ post says it brings ERP (preview) and CRM from Dynamics 365, and Power Platform data, together with Microsoft 365 context. The practical example Microsoft gives is an agent that reasons across your opportunities, emails and meetings at once.
The Foundry angle comes from the same post. It says Work IQ is generally available in Foundry and in Copilot Studio, and available over MCP, REST and A2A protocols. In plain terms, developers building agents in Foundry can use the same business context that Copilot uses.
The ERP caveat
Microsoft's own pages don't line up cleanly:
- The Azure Ignite post describes CRM and ERP records as part of the GA announcement.
- The Work IQ post tags ERP as preview.
- The Microsoft Learn page for Business Applications in Work IQ lists Dynamics 365 ERP as preview. It lists Dynamics 365 Customer Service, Dynamics 365 Sales and Power Apps model-driven apps as the supported line-of-business sources. Learn also still carries a general preview notice for the feature, and its last-updated date is November 17, 2026.
- A WindowsForum analysis of the same material reached the same reading: the ERP piece may still be preview even where CRM is generally available.
My reading is that CRM and Power Platform grounding is the safe production assumption. Treat ERP as preview until Microsoft's documentation says otherwise. That is an inference from the mismatched labels, not a Microsoft statement.
Choosing an integration path
The Learn documentation separates several ways to bring business context into an agent:
- Work IQ MCP: for an agent or coding client that needs Microsoft 365 and supported business-application context through one MCP server. Administrators control availability for the whole server, and environment, app and data permissions still decide what is reachable.
- Dataverse MCP: direct, environment-specific Dataverse tools or business skills, without the broader Work IQ layer. It is configured per environment.
- Dataverse Ask API: application code that needs a response grounded in a chosen Dataverse semantic model.
- Dataverse plugin for coding agents: development guidance while building a solution, not end-user data grounding.
Microsoft says these can coexist with other enterprise data sources, and you don't have to move everything into Dataverse. One limit matters for architects: Work IQ MCP currently has no retrieval-only parameter that skips response generation. If you need deterministic retrieval, Microsoft advises using the source API or another targeted integration.
Connecting a Foundry project to Work IQ
Microsoft's Foundry quickstart (last updated July 1, 2026) documents the project-level flow. It covers Microsoft 365 context, not a dedicated Business Applications procedure. Treat it as the connection mechanism, and check the Business Applications setup guidance separately.
Prerequisites
- A Foundry project with a deployed model.
- The Foundry Project Manager role, to create the connection.
- The Foundry User role for the developer identity, the agent runtime identity and users in OAuth flows.
- A Microsoft 365 Copilot license for each user who calls Work IQ through the agent. This is what the quickstart lists. The GA announcement doesn't spell out licensing, so confirm current terms before budgeting.
- An Entra Global Administrator who can grant admin consent for the delegated
WorkIQAgent.Askpermission. - Delegated Entra authentication. Application-only authentication isn't supported.
Steps
- In the Entra admin center, create or open an app registration. Copy the application (client) ID and directory (tenant) ID, and add a client secret.
- Add the delegated
WorkIQAgent.AskAPI permission and grant tenant admin consent. If Work IQ doesn't appear in the permissions search, its service principal may not be provisioned in your tenant yet. - In Foundry, open Tools, choose Connect a tool, and pick Work IQ MCP from the Catalog tab.
- Confirm the endpoint
[url]https://workiq.svc.cloud.microsoft/mcp[/url]. Then configure OAuth with your client ID, secret, tenant-specific authorize, token and refresh URLs, and the scopesapi://workiq.svc.cloud.microsoft/WorkIQAgent.Askandoffline_access. - Save the connection. Foundry then shows an OAuth redirect URL. Add it to the app registration under Authentication, as a Web platform redirect URI.
- Add the Work IQ MCP tool, or a toolbox containing it, to your agent. Decide whether MCP tool calls need approval or are auto-approved.
- Test with a prompt such as summarizing today's meetings. The first call may trigger sign-in and consent.
What success looks like: the agent returns a grounded answer, and Microsoft says that answer depends on the signed-in user's Microsoft 365 permissions, the app's OAuth permissions and tenant policy.
Common failure points
- Work IQ missing from the API permissions list, which points to an unprovisioned service principal.
- A redirect URI that doesn't match the one Foundry displays.
- Missing admin consent, or a user without the Foundry User role.
- Trying to use application-only auth.
Governance: what Microsoft says and what you still owe
Microsoft describes access control as enforced outside the language model. The company calls this a fundamental requirement for agentic security. The controls it lists include:
- A tenant-wide ceiling on agent actions, which individual agent policies can narrow but not exceed.
- For agents registered in Agent 365, maker-proposed policies that administrators approve or deny, with Work IQ checking policy on every call.
- Honoring existing CRM and ERP security, permissions and business skills.
- New
WorkIQ.ReadandWorkIQ.Actpermissions that separate reading from acting, with policies that can allow, block or require human approval.
These are Microsoft's descriptions. Your own agents and data still need configuration and testing. The Learn page says Power Platform administrators must enable Work IQ in the environments that provide business context. It also notes that the older "Dataverse intelligence (preview)" setting is now the Work IQ setting in the Power Platform admin center. AI administrators manage Copilot and Work IQ MCP availability, and makers manage which model-driven apps participate.
What IT teams should do now
- Don't read "GA" as "every data source is on." Enablement is explicit, per environment and per app.
- Inventory which Dynamics 365 and Power Apps environments you would expose, and who owns the permissions behind them.
- Pilot with read-only scopes first. Use the read/act permission split before letting an agent update CRM records.
- Verify the ERP status in your tenant's documentation before committing to production plans.
- Confirm licensing, since the Foundry quickstart lists Microsoft 365 Copilot licenses per calling user and Microsoft points to separate licensing documentation.
Microsoft's GA announcement lacks regional, pricing and Foundry-specific limit details, so don't assume any. The main takeaway is that CRM-backed agent context is now a supported production option in Foundry. The ERP side is still a point to verify.
References
- (Launched) Generally Available: Microsoft Foundry Support for Business Applications in Work IQ Azure Updates · 2026-11-17T20:00:32Z
- Introducing the new Microsoft IQ: Putting your organization's intelligence to work in every agent azure.microsoft.com
- Business Applications in Work IQ - Power Apps | Microsoft Learn learn.microsoft.com