The schedule matters. The roadmap lists the item as In development, with preview in September 2026 and general availability in November 2026. It covers the Web platform in the Worldwide (Standard Multi-Tenant) cloud. Until November it is a preview feature, so treat it that way.
What the roadmap item promises
The entry describes a short, specific set of behaviors:
- Two entry points: the Work IQ (Preview) tool in Copilot Studio, and a chat experience built on Work IQ MCP.
- Record operations: list, read, create, update and delete, all from natural-language prompts.
- Field mapping: when you create or update a record, Work IQ matches the values you give it to the right app fields.
- Explicit confirmation: the user must approve the proposed values before a create or update is submitted.
One caveat: the roadmap text only mentions the confirmation step for create and update. Delete is on the list of operations, but the entry doesn't say whether a deletion asks for the same approval. Admins piloting this should test that themselves before anyone trusts the AI with a delete.
Section summary: chat-driven create, read, update and delete for model-driven apps, with a required confirmation step for creates and updates. Preview in September, GA targeted for November.
Microsoft's user documentation goes further
Microsoft Learn now has a user-facing page, "Use Business Applications in Work IQ (preview)," that matches the roadmap entry. It states that Power Apps model-driven apps are available as Business Applications in Work IQ and that users can use natural-language prompts to find and work with business data without opening the model-driven app.
It also explains how the feature works. According to Microsoft, you start a conversation, select an environment and app when prompted, and then describe the information or action you need. Work IQ uses the app's views, forms, and tables to complete the request. That is a meaningful design choice. The AI isn't working against raw Dataverse tables. It works through the app's own forms and views, which already reflect how makers wanted the data presented.
Security follows the same model. Microsoft says Work IQ applies Copilot reasoning to the data and app components that you already have permission to access. If a user couldn't see a record in the app, a chat prompt shouldn't reveal it either.
Prerequisites from Microsoft Learn
According to the user documentation:
- You need access to the Work IQ experience where you want to use Business Applications.
- A Power Platform administrator must enable Work IQ for the environment in the Power Platform admin center.
- For the model-driven app, the Enable M365 Copilot in model-driven apps setting (m365copilotmodelappenabled) must be set to Default or On.
- You need permission to access the Power Platform environment, model-driven app, and business data involved in your request.
The user workflow
Microsoft's steps are simple:
- Start a conversation in an experience that supports Business Applications in Work IQ.
- Select a Power Platform environment from the environments available to you.
- Select the model-driven app that contains the business data you want to use.
- Enter a prompt that describes the records you want to find or the action you want to perform.
- Review the response. For a create or update, confirm the proposed values before they're submitted.
Where this fits in Work IQ
Work IQ is Microsoft's name for the intelligence layer behind Copilot and agents. Business Applications in Work IQ is the extension that pulls line-of-business data into it. Microsoft Learn describes it as bringing the data, processes, and operational context from your business applications directly into Copilot and agents. The same page lists three supported data sources: Dynamics 365 Customer Service, Dynamics 365 Sales, and Power Apps model-driven apps.
The Copilot Studio half of the roadmap item lines up with Copilot Studio's own changelog. Its August 2026 entry added a preview option to add Work IQ to your agents to ground them in real-time, shared context across your organization, connecting signals from files, emails, meetings, chats, and Business Applications across Microsoft 365.
The confirmation requirement also matches what Microsoft has been saying more broadly. A September 25 post on the Dynamics 365 blog said that through governed actions, the Copilot and agents present the proposed changes, follow any required approval, and update the source records within the user's permissions. The roadmap item looks like that principle applied to model-driven apps specifically.
Don't confuse this with the separate preview Power Apps MCP Server, which gives agents custom tools for an individual app. That is a different product. Roadmap item 571888 is about model-driven apps reached through Work IQ.
Section summary: this is Work IQ's general business-data layer gaining read and write access to custom model-driven apps, with human approval required before records change.
The admin side: defaults and controls
The part admins need to know is that much of this turns on by default. Microsoft's default-settings documentation says that, starting September 30, 2026, Business Applications in Work IQ capabilities are on by default for new public production environments. Existing environments follow starting in November 2026. The exceptions are:
- trial, sandbox and developer environments
- EU and EEA environments during the preview
- government-related environments
The feature isn't currently available in sovereign or government clouds, including DoD, GCC and GCC High.
Control works at three levels:
| Level | Where | What it governs |
|---|---|---|
| Tenant | Microsoft 365 admin center > Copilot > Settings | Whether business-app data is available to Copilot: All users, Specific groups, or No users |
| Environment | Power Platform admin center > Manage > [environment] > Settings > Product > Features | The Work IQ toggle for that environment |
| App | Power Apps > Apps > Edit > Settings > Features | Whether that app's tables, forms and views are shared |
Two details are easy to miss:
- Shared tables: Microsoft notes that if a table appears in several apps, turning off one app doesn't hide the table. It stays available until every app using it is turned off.
- New apps opt in automatically: when you import a solution that contains an app into an environment where Work IQ is on, if the app's Enable Copilot in model-driven apps setting is On or Default, the setting is On in the destination environment. If the setting is Off, it remains Off. During the preview, Microsoft says new apps in a Work IQ-enabled environment automatically include Microsoft 365 Copilot Chat.
MCP access has its own control. According to Microsoft, admins can review or block the Work IQ MCP tool under Agents > Tools in the Microsoft 365 admin center. Separately, App Access under Security > Identity & access in the Power Platform admin center decides which applications can reach an environment's data. A Copilot audience setting alone won't lock down the MCP route.
Budget for storage, too: some features use extra storage for search indexes. These features include semantic modeling and access to Power Apps and Dynamics 365 data through Microsoft 365 Copilot Chat. Microsoft's compliance notes also warn that PCI DSS, HITRUST and FedRAMP scopes for Dataverse don't automatically carry over to Microsoft 365 when Copilot retrieves that data. Regulated organizations should take that seriously.
Analysis: useful, with real risks
For a busy front-line user, this is a clear win. Typing "update the Contoso case to high priority and set the follow-up date to Friday" beats clicking through a form you open twice a month. Matching values to fields through the app's own forms and views is a sensible design, and requiring confirmation before writes is the right default.
The risks are the usual ones for preview AI tools that can write data:
- Mapping errors: a value mapped to the wrong field is easy to approve if the user just clicks Confirm without reading. People skim confirmation prompts.
- Delete is unclear: until Microsoft documents how deletion confirmation works, test it before giving pilot users write access to important tables.
- Defaults reach further than you might expect: with default enablement and solution imports keeping apps switched on, admins who haven't reviewed their tenant, environment and app settings may find more apps exposed than they planned.
My recommendation, based on general Power Platform governance practice rather than anything Microsoft has said: run this in a non-critical environment, start with read-only scenarios, test create, update and delete against a test table, and confirm the MCP and App Access settings before November.
Bottom line: model-driven Power Apps are getting a chat interface that can also change records, and it requires approval before creates and updates. Admins have until the November GA to work out who gets it, which apps are included, and how deletes are handled.