A business application described in one sentence, under control

Building a business application on Dataverse takes expertise: before the application itself, you have to design the tables, link the data, think about security and load test data. Each step happens in a different tool, and each handoff costs time.

Microsoft has just announced a plugin that brings these steps together in Copilot Cowork, its work assistant. I'll explain what it is, what it changes and what I would check before relying on it.

What the plugin builds from one sentence

In Microsoft's demo, someone asks for an event registration application for a team. An event has a venue, a date, times and a capacity. Each person can register only once. When the event is full, the next people go on a waiting list.

The plugin gives Cowork access to your Dataverse environment. Dataverse is the Microsoft 365 database. The assistant creates the two tables needed, then adds the links between them, step by step, in a way you can review.

Important point: it links the registrations to the contacts table that already exists. It doesn't invent a second list of people. For executives, that's the detail that matters: the application relies on data the company already knows.

The assistant also adds four sample events, one of them filled to capacity to test the waiting list. These rows are marked as sample data, so they're easy to find and delete.

Control stays with you

An assistant that writes to your data has to earn your trust. Microsoft describes three safeguards.

• The connection uses your identity. The assistant only sees and changes what your rights allow.
• Dataverse checks every request on the server side. The plugin can neither bypass nor widen your permissions.
• Every change is first presented to you as an approval card. Nothing is done behind your back.

One example from the demo pleased me. The default environment had no Dataverse database. The assistant didn't guess: it asked for the right environment, then created the application next to its data. For a compliance officer, that's reassuring, because security applies in the same place.

From the database to the published application

Once the data is in place, Cowork creates the application, connects it to the two tables and applies a theme. Before publishing, it runs checks: code verification, a full build and a visual review of the display.

The published application runs in Microsoft Copilot Managed Runtime, currently in preview. It uses Microsoft Entra sign-in and follows your company's governance rules from the moment it's created. Administrators see and manage it in the Microsoft 365 admin center.

The result of the demo: one view for the organizer and one view for the front desk. Each event shows its date, its venue and how full it is. With three places, the fourth person to register does go on the waiting list, as the request required.

Everything is written to Dataverse. No separate database, no copy to synchronize. The same data then serves Power Automate, Copilot Studio agents and reports.

What I won't hide from you

It's a demo on a simple case. I haven't seen this plugin handle a multi-level purchase approval or a compliance check. I stay cautious until I've done it.

Two prerequisites to know. Creating applications in Cowork currently requires enrollment in the Frontier program. And the application runtime is in preview. Microsoft gives no general availability timeline and no licensing details here: ask before planning.

A generated application isn't a designed application. Someone has to review the approval cards and know what they're approving. That's where experience in the field is still needed. On this subject, see our business applications and our Copilot AI agents. For an example of data brought together in one place, see one single truth for treasury.

What it changes for you

A real case: for a CAC 40 energy group, I delivered a purchase request application. It checks the supplier, gets the request approved by the line manager and alerts the person in charge of SAP in the entity. At the start, suppliers were being created twice. That's the trap the demo avoids with contacts: recreating what already exists.

With this plugin, the first version of a tool like this could be described in one sentence: requests, suppliers, their links, sample rows. Each table and each link would arrive as an approval card, with your rights. I haven't tried it on this case yet.

The gain to aim for is the result of the delivered project: a supplier is created only once, checked against the national register. That result comes from controls designed with the business, such as the "Verify" button and the "Possible duplicate" alert.

First step, next week: write a simple need of your department in one sentence, then list the data that already exists in your company. On the approval cards, check that the assistant links to it instead of copying it.

What this means for you

Starting Monday, you can ask your IT department three questions.

• Is our company enrolled in the Frontier program, and if not, who can request it?
• Do we have a test Dataverse environment, separate from the one where our production data lives? Microsoft suggests a Power Apps Developer Plan environment to try it.
• Who will review the approval cards, and with what access rights?

Start with a small internal need, with no sensitive data: request tracking or a simple register. Keep the preview out of critical processes until its status is clear.

If you want an opinion before you start, a consulting and audit engagement helps you choose the right first case and check the prerequisites.

Based on Microsoft

"Cowork can only see and change what your Dataverse security roles allow."

Based on: From one prompt to a governed Dataverse app: the Dataverse plugin lands in Copilot Cowork, Microsoft, 28 October 2026, https://www.microsoft.com/en-us/power-platform/blog/2026/10/28/dataverse-plugin-copilot-cowork/