What Microsoft says is coming
The roadmap entry says information workers will be able to use a model-app-builder skill inside Copilot Cowork. The skill creates and refines model-driven apps from natural-language requirements. The flow runs in this order:
- You describe a business scenario.
- Cowork turns it into an app specification and build plan for you to review.
- Only after review does it create the model-driven app and its supporting Power Apps and Microsoft Dataverse artifacts.
- You keep iterating by chatting in Cowork, or open the generated artifacts in Power Apps and customize them directly.
The listed metadata:
| Field | Value |
|---|---|
| Status | In development |
| Preview | November 2026 |
| General availability | January 2027 |
| Applies to | Model-driven apps |
| Feature scope | Admins or makers |
| Platform | Web |
| Cloud | Worldwide (Standard Multi-Tenant) |
| Release channel | Not applicable |
Today is November 17, so November is the current month. That doesn't confirm that rollout has begun or that your tenant can see it. GA in January 2027 is still in the future.
Why model-driven matters
Model-driven apps start from the data model. Microsoft's Power Apps documentation says they automatically generate a UI that's responsive across devices, and that makers can use Dataverse to configure forms, business rules, and process flows. They are the data-heavy, form-and-view business apps, and building one by hand means a lot of repetitive setup: tables, columns, relationships, forms, views and so on. That setup is the work this feature aims to automate.
Cowork can already build apps. Microsoft's Cowork documentation describes a built-in App skill for lightweight, interactive apps. The roadmap item is about the heavier model-driven kind, built on Dataverse.
What the sibling skill tells us, with caveats
Microsoft has already documented a model app-builder skill for AI code-generation tools such as GitHub Copilot CLI and Claude Code. Microsoft's September 2026 Power Platform update says it's now generally available. One caveat: the Learn page and the September blog post label this feature differently, and the blog's own heading still says "preview". Check the current status before relying on either.
That documentation shows what such a skill does. It is not a spec for the Cowork version. The Cowork roadmap entry doesn't confirm any of the following for itself:
- Artifacts: The external-tool skill can create supporting tables, columns, relationships, forms, views, charts, business rules, business process flows and sample data. The documentation also lists generative pages, a sitemap, JavaScript validation rules and security roles based on planned personas.
- Plan before build: The skill presents a dry-run build plan, and no app artifacts are created until you approve the plan.
- Edits to existing apps: You can edit an existing model-driven app by describing the changes you want.
- Standard output: Artifacts created by the model app-builder skill are standard Power Apps and Dataverse artifacts. You can keep working in the Power Apps designers.
- Limits: The skill doesn't currently support every model-driven app artifact or concept. Changes made outside the skill can affect later AI-assisted edits.
Microsoft also tells makers to review and test generated artifacts for correctness, security, accessibility and compliance before sharing. The roadmap's "review before create" wording suggests Cowork follows a similar pattern, but treat that as an inference.
What isn't known yet
The roadmap entry says nothing about these points, so don't assume answers:
- Licensing and billing: Microsoft's separate Cowork app-building documentation lists a Microsoft 365 Copilot license, Cowork access and usage-based billing as prerequisites for the Cowork App skill. That page covers the lightweight App skill. Nothing confirms the same requirements for this feature.
- Admin controls: The "Admins or makers" scope is stated, but no governance settings are described for this feature. For the App skill, Microsoft documents an admin toggle. In the Microsoft 365 admin center it sits at Copilot > Cowork > Settings > Build apps in Copilot, and by default all users can build apps. Whether model-driven apps follow the same switch is unconfirmed.
- Supported scenarios and artifact coverage: The entry doesn't say which of the artifacts above Cowork will create.
- Tenant prerequisites: The entry doesn't list any.
How to prepare
This is general guidance from the documented external-tool workflow, not Cowork-specific instructions:
- Write the scenario like a brief. Cover who uses the app, what data it tracks, how records relate, and what each role may see or change. Microsoft's guidance is to start with the business process, users and goals.
- Treat the spec as the real deliverable. Check that the personas, tables, relationships and access needs match your intent. Microsoft's documentation says time spent on the plan reduces rework.
- Read the build plan before approving. Approve only when the proposed changes match what you want.
- Test in Power Apps. Run each persona's main tasks and inspect the generated security roles.
- Expect some manual work. Unsupported components will need the Power Apps designers.
Admins should watch their tenant's roadmap and message center for tenant-specific rollout details. They should also decide in advance who may build apps, and in which environments, since an AI-generated app creates Dataverse schema and security roles in a real environment.
Analysis
Microsoft's October 29 Power Platform blog post says people can now create apps in Copilot Cowork and in Copilot Studio. It also says the model-driven app-builder skill helps makers move from an idea to a working experience using natural language. This roadmap item fits that direction: the same app-building skill, reachable from the chat surface business users already use rather than a terminal.
The risk is that a chat-based builder lowers the barrier to creating Dataverse tables and security roles. If the Cowork version keeps the review gates described for the external-tool skill, that risk is manageable. Until Microsoft documents Cowork's behavior, treat the review-before-create step as a plausible design, not a promise. Pilot in a non-production environment once it appears.
References
- Power Apps: Build model-driven apps with Copilot Cowork Microsoft 365 Roadmap · 2026-11-17T18:36:41.967573Z
- Build and edit model-driven apps with AI code generation tools - Power Apps | Microsoft Learn learn.microsoft.com
- Microsoft Copilot Roadmap | Microsoft 365 microsoft.com