Dataverse plugin for Copilot Cowork builds apps

Key insights

• The demonstration requires access to the Frontier program and enough environment admin access to add plugins.
• The demonstrated plugin worked in Copilot Cowork, not regular Copilot chat or Copilot Code.
• A generated app may fail to connect if Cowork and the app target different Dataverse environments.
• An app-level rule can block a third activity in the app without enforcing that limit in Dataverse.
• The demonstration tested natural-language questions against a table containing 56,000 hotel records.

The Microsoft Dataverse plugin for Copilot Cowork can query connected Dataverse data and generate a working app from a natural-language request. It matters to Dataverse makers, Power Apps users and administrators assessing how to enable end-user app creation while keeping data and business rules governed. Sean Astrakhan (Untethered 365) demonstrates the workflow and tests its behavior against real Dataverse tables.

What it does

The plugin connects Copilot Cowork to a Dataverse environment, letting a user ask questions about the environment’s data and request an app. In the demonstration, it answered questions about hotel records and instructors, then generated an instructor assignment app with instructors, certificates and outdoor activities. The app supported dragging related records onto an instructor to assign them.

This moves beyond generating instructions or snippets: Cowork acted on connected Dataverse data and produced an app that could be tested and published. The demonstration also shows why a generated result still needs review. A request to limit instructors to two outdoor activities led to a rule in the app, but that rule did not prevent someone from adding a third activity through a separate Power Apps form.

The creator’s test included semantic questions about hotel descriptions, rather than only exact word matches or structured counts. The demonstration description says the test also used 56,000 hotel records. That is an individual test, not a guarantee of performance or accuracy for other environments.

Who it is for and what you need

The video says users need to be part of the Frontier program and need enough admin access in their environment to add plugins. It does not specify a particular license, regional availability, or a broader rollout stage. Check Microsoft’s list of available Copilot Cowork plugins for current product details.

The demonstration used the Dataverse plugin in Copilot Cowork. The speaker reports that it did not work in regular Copilot chat or Copilot Code at the time of the test. These observations describe the demonstrated setup and should not be treated as a statement about availability for every tenant or a permanent product limitation.

Choosing the right Dataverse environment matters. The first attempt generated an app that could not load data because it was pointed at a developer environment different from the user’s Cowork account environment. Repeating the request while explicitly targeting the user’s own environment produced an app connected to the intended data.

How it works

The demonstrated setup starts in Cowork, where the Dataverse plugin is installed and connected to an environment. The user then asks a question or describes the app and its relationships in ordinary language. Cowork may ask for approval before carrying out an action, as it did when the user requested a business rule.

1. In Copilot Cowork, install the Dataverse plugin and confirm the installation.
2. Enter the Dataverse environment URL, connect, and complete the sign-in prompt.
3. Ask a question about data or describe the app, the records it should display, and how they relate. Explicitly identify the intended environment.
4. Review any proposed action or permission request. Test the generated app against Dataverse, including changes to related records.
5. Publish the app when it is ready, then verify that it opens with the expected data and permissions.

Testing should include more than the app’s own interface. In the example, a two-activity limit blocked a third assignment through the generated app, but the user could still add another activity through a separate Dataverse form. The demonstration’s response explained that the limit applied only inside that app and would need a Dataverse plugin to be enforced across other routes.

Limitations and open questions

The clearest limitation is the boundary between an app’s interface and Dataverse-level enforcement. A rule that only blocks an action in one app does not necessarily prevent the same change through a form, flow, import or another app. Makers should verify where a rule is enforced before relying on it as a business control.

Environment selection and connections also require attention: the initial generated app could not display data until the request targeted the user’s own environment. The demonstration does not establish which licenses are required, how widely the plugin is available, or whether its behavior has changed since the test. Microsoft’s Cowork plugin guidance and Dataverse MCP configuration documentation are useful references for checking current setup and controls.

The video reports an estimated $10–$11 to finish the example app, but the speaker notes that the usage total included other Cowork operations. Treat that as a personal estimate, not a standard price. The broader takeaway for makers is practical: generated apps can reduce setup work, but environment choice, testing, server-side enforcement and governance still need informed review.

Sources

• Microsoft documentation: Available plugins for Copilot Cowork
• Microsoft documentation: Use plugins with Copilot Cowork
• Microsoft documentation: Configure the Dataverse MCP server for an environment
• Sean Astrakhan (Untethered 365): Dataverse plugin demonstration

Frequently asked questions

What do I need to use the Dataverse plugin in Copilot Cowork?

The demonstration says users need to be part of the Frontier program and have enough admin access in the environment to add plugins. It does not specify a license or region.

Can the Dataverse plugin enforce a business rule everywhere?

The demonstrated app-level limit blocked a third activity inside that app, but not through a separate Power Apps form. The demonstration says enforcement across routes would require a Dataverse plugin.

Why might a Cowork-generated app fail to load Dataverse data?

In the demonstration, Cowork and the app targeted different environments. Explicitly selecting the user's own environment resolved the connection issue.

Does the Dataverse plugin work in regular Copilot chat or Copilot Code?

The speaker reports that it worked in Cowork but not regular Copilot chat or Copilot Code during the demonstration. The material does not establish whether that has since changed.