# Canvas vs model-driven vs code apps vs Copilot apps

> Four ways to build a Power App, and who pays to run each one. Pick by the job, then check licences before Microsoft starts blocking users in February 2027.

[( Insights)](https://tenantcraft.ca/insights)

## Canvas, model-driven, code app or Copilot: which Power App to build

Microsoft now gives you four ways to build a business app: canvas, model-driven, code apps, and Copilot Managed Runtime. Pick by the job, then check who needs a licence to open it, because Microsoft starts blocking unlicensed users in February 2027.

Stage

Plan

Topic

Power Platform

Published

Nov 4, 2026

Written by

[Geri Crroj](https://tenantcraft.ca/about)

Tested in a live tenant, November 3, 2026

(Short version)

Pick canvas for a task app on data you already have, model-driven for a process that lives in Dataverse, a code app when a developer owns the experience, and Copilot Managed Runtime when speed matters more than mature lifecycle tools. Only a canvas app with standard connectors, outside a managed environment, runs on Microsoft 365 rights alone. The other cases always needed a premium licence, and from February 2027 Microsoft blocks users who don't have one.

The request comes in on a Monday. “Can we get an app for vehicle bookings? Nothing fancy.” The person asking has seen a demo. Someone typed a sentence into Copilot and got a working app back. They want that.

Then you open Microsoft’s docs and find four doors. **Canvas apps**. **Model-driven apps**. **Code apps**. And a new one called **Copilot Managed Runtime**, which is where the old “vibe coding” idea went. Each has its own licence rules and its own admin switch.

Most people pick the door they already know. That works until the licence bill arrives.

The 5-minute version

1.  **Start with the job, not the tool.** A task, a process, a custom experience, or speed.
2.  **Only canvas can run on Microsoft 365 rights alone.** And only under three conditions, listed below.
3.  **Model-driven and code apps need a premium licence for every user.**
4.  **Copilot Managed Runtime is still a preview.** Microsoft 365 rights don’t cover it at all.
5.  **Microsoft starts blocking unlicensed users in February 2027.** Run the report at the end of this post before then.

## Pick yours in 30 seconds

Answer these in order. Stop at the first yes.

1.  **Will people outside your organization use it?** Then none of the four. That’s Power Pages, a separate product for public sites.
2.  **Does work move through stages, with roles and an audit trail?** Build a **model-driven app**.
3.  **Does a developer on your team want to own the code?** Build a **code app**.
4.  **Do you need it this week, and can you live with preview software?** Try **Copilot Managed Runtime**.
5.  **None of the above?** Build a **canvas app**. For most small teams, this is the answer.

Three words come up a lot below:

-   **Dataverse** is Microsoft’s database for Power Platform. It holds real tables with relationships. It costs extra.
-   A **managed environment** is a Power Platform environment where an admin has turned on Microsoft’s extra governance features. It changes who needs a licence.
-   A **connector** is how an app talks to another service, like SharePoint or Outlook. Some are standard. Some are premium.

## The four side by side

AI now helps you build all four, so build effort isn’t what separates them. The bill is. Here is who pays to run each one.

Who pays to run it

-   Canvas app

    Free

    with Microsoft 365, if all three conditions hold

    Best for a task: one team, one form. Stays free only with standard connectors, no Dataverse, and outside a managed environment.

-   Model-driven

    Premium

    every user and every maker

    Best for a process with stages and roles. Needs Dataverse, so it is premium from day one.

-   Code app

    Premium

    every user

    Best for a custom app your developer owns. Off until an admin turns it on.

-   Copilot Managed Runtime

    Premium or credits

    Microsoft 365 doesn't cover it

    Best for speed: an app this week. Still a preview, and only Microsoft's own connectors work by default.

The canvas conditions, and what each premium licence includes, are in the sections below.

## Canvas apps: start from the screen

**What it is:** you drag buttons, lists and forms onto a blank screen. You wire them up with Power Fx, which feels like Excel formulas. The app can use SharePoint, Excel, SQL, Dataverse and many other services. It runs in a browser, on a phone, in Teams and in SharePoint.

**Pick it when:** you have a task for one team. Vehicle bookings. Equipment checkout. Site inspections.

**Who pays:** building one is free. Running one on your Microsoft 365 licences is free only when all three of these are true:

1.  Every connector is a standard one, like SharePoint, Excel or Outlook.
2.  The app doesn’t use Dataverse, an on-premises data gateway or a custom API.
3.  The environment isn’t a managed environment.

Break any one, and every user needs a premium licence. Microsoft’s [licensing FAQ](https://learn.microsoft.com/en-us/power-platform/admin/powerapps-licensing-faq) lists the triggers. To check an app, publish it, then open its **App Details** page in the maker portal. The label only updates after you publish.

**Watch out for:** the SharePoint row limit. Some filters can’t run inside SharePoint. When that happens, Power Apps reads only the first 500 rows by default, 10,000 at most, and ignores the rest without an error. That limit is usually what pushes a canvas app to Dataverse. The [SharePoint to Dataverse move](https://tenantcraft.ca/insights/power-apps-sharepoint-to-dataverse-migration) covers what changes next. And before you share the app, [lock down the list behind it](https://tenantcraft.ca/insights/lock-down-sharepoint-list-power-apps).

**The AI option:** Microsoft’s canvas apps plugin lets a coding agent, such as GitHub Copilot or Claude Code, build screens for you. Create and save a blank app first. Turn on **Coauthoring** under **Settings**, then **Updates**. Keep Studio open while the agent works. You’ll need the .NET 10 SDK.

## Model-driven apps: start from the data

**What it is:** you don’t draw screens. You build tables, forms and views in Dataverse, and Power Apps builds the screens for you. You give up control of the layout. In return, every screen looks the same, and Microsoft’s [model-driven overview](https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/model-driven-app-overview) says it’s responsive and accessible by default.

**Pick it when:** work moves through stages and several roles touch it. Onboarding. Case tracking. Approvals that have to hold up in an audit.

One common mix-up: security roles and table rules belong to Dataverse, not to the model-driven app. A canvas app on the same tables gets them too. What model-driven adds is the screens and the links between related records.

**Who pays:** every user needs a premium licence. Power Apps Premium, a per-app pass, pay-as-you-go, or some Dynamics 365 licences, including Business Central, all count. Makers need one too. You can’t build a model-driven app for free.

**The AI option:** generative pages let you describe a page in plain words and get it built, with no extra AI credits. Each page can use up to six Dataverse tables.

**Watch out for (Canada):** the in-browser version of generative pages only works in environments in the United States, Great Britain, Australia or Singapore. Don’t create a US environment just for this. An environment is tied to its region, so your data would leave Canada. Use the coding agent route instead. Microsoft says it works on all public clouds.

**Watch out for (Dataverse for Teams):** this was the free way to get Dataverse-style tables. It’s going away. You can’t create new Dataverse for Teams environments starting November 15, 2026. Ones that aren’t upgraded are suspended on September 15, 2027, and after the upgrade every user needs a licence. If you have apps there, read [Dataverse for Teams vs a SharePoint list](https://tenantcraft.ca/insights/dataverse-for-teams-vs-sharepoint-list).

## Code apps: start from the code

**What it is:** a developer builds a web app in React, Vue or a similar framework. They publish it to Power Platform with the Power Apps CLI. Microsoft made code apps generally available in February 2026. The app still gets Microsoft sign-in, Dataverse and 1,500+ connectors. It follows your data policies, sharing limits and Conditional Access.

**Pick it when:** you need a screen canvas can’t build, and you have a developer who wants to own the code. They’ll need Node.js, Git and the Power Apps CLI.

**Who pays:** every user needs a premium licence, whatever the app connects to. Power Apps Premium, pay-as-you-go, an App Pass or auto-claim all count. Auto-claim hands a spare Premium licence to a user automatically.

**The admin switch:** code apps are off until an admin turns them on. In the Power Platform admin center, open the environment’s **Settings**, then **Product**, then **Features**. Environment groups let you switch it on for many environments at once.

![The Features settings page for an environment in the Power Platform admin center. The Power Apps Code Apps section has an Enable code apps toggle, circled in red and set to Off. Below it, the Power Apps Generative Pages section has Enable generative pages set to On.](https://tenantcraft.ca/images/pa4-01-enable-code-apps-off.png)

Power Platform admin center · Features

The default environment in a test tenant: code apps are off, generative pages are on. Until an admin flips the first toggle, nobody can run a code app here.

**Watch out for:**

-   **No SharePoint forms.** A code app can’t replace the form on a SharePoint list. If you’re [replacing an old InfoPath form](https://tenantcraft.ca/insights/infopath-replacement-power-apps), use canvas.
-   **Public files.** The app’s files sit on a public web address that can’t be locked to your office IP. Microsoft says not to store sensitive data in the app itself. Keep it in the data source, behind sign-in.
-   **Git and solutions.** The code lives in your own Git repository, but code apps don’t support Power Platform Git integration. Without Dataverse in the environment, they publish without a solution.

## Copilot Managed Runtime: start from a prompt

**What it is:** you describe an app in Copilot Studio, Copilot Cowork or Copilot Code, and you get a working web app back. Developers can also use its own SDK and CLI. Microsoft hosts the app. Users sign in with their work account and open it from one portal. Admins see every app in one list in the Microsoft 365 admin center. It’s built outside Power Apps, but it runs on Power Platform managed environments underneath.

If your staff used App Builder or vibe.powerapps.com, this is where those apps move. Both retire on November 30, 2026. The steps are in [the App Builder and vibe post](https://tenantcraft.ca/insights/app-builder-vibe-powerapps-retirement).

**Pick it when:** speed matters most. You want a working app this week, with governance already in place.

**Who pays:** building in Copilot Studio spends Copilot Credits. To run an app, each user needs Power Apps Premium or Copilot Credits. Microsoft 365 licences don’t count, even for an app that only uses SharePoint.

-   **Users with Premium** run apps without spending credits, up to their daily Power Platform request limits. Work IQ calls are still charged.
-   **Everyone else** spends 0.1 Copilot Credits per API call, which is roughly each action the app takes. Opening the app counts as one. An admin must first turn on usage-based billing and add those users to a spending policy in the Microsoft 365 admin center. Until then, they can’t open the app.

**What it connects to:** out of the box, 18 Microsoft connectors, like SharePoint, OneDrive, Teams, Outlook, Excel and Dataverse. Third-party and custom connectors stay blocked until an admin opens up the policy.

**The admin switch:** making these apps from Copilot Studio is on by default. Find it under **Apps**, then **Overview**, then **Choose app-creation spaces**. The CLI route is off by default.

![The Choose where people can create apps panel in the Microsoft 365 admin center. Under Available in preview, Copilot Studio is set to On (recommended), circled in red. A Command line interface option sits below it. Under Available with Frontier, marked Off, are Copilot Cowork and Copilot Code.](https://tenantcraft.ca/images/pa4-02-app-creation-spaces.png)

Microsoft 365 admin center · Apps

Copilot Studio app creation arrives switched on. Cowork and Copilot Code stay off until the tenant joins the Frontier program.

**Watch out for:**

-   **A setting you can’t undo.** The first time someone builds an app, Microsoft creates a rule that gives each maker their own environment. Microsoft says it’s permanent. Decide who should build here before anyone starts. You can limit Copilot Studio app creation to chosen security groups with the Power Platform CLI.
-   **No guests.** Guest users can’t open these apps, even with guest sharing on. Microsoft lists it as a known issue.
-   **No solutions yet.** Apps move with Git, not solutions. If your team moves everything through solutions and pipelines, this won’t fit yet.

## Mixing them

You don’t have to pick only one. A model-driven app can hold canvas pages. Most jobs also need a flow for the steps that run on their own.

Flows have their own licence rule. A flow that runs inside an app is covered by the app’s premium licence. An instant flow, the kind a person starts with a button, needs premium for every user who runs it.

## February 2027: the rule isn’t new, the blocking is

The premium rules above aren’t new. What’s new is that Microsoft will enforce them. Starting **February 2027**, Microsoft’s licensing FAQ says users without a premium licence will be blocked in these places, among others:

1.  **Model-driven apps.** Anyone opening one needs a premium licence.
2.  **Apps in managed environments.** Every user of every app there needs one, even for a plain canvas app on SharePoint. Microsoft 365 licences never covered those apps. From February 2027, the app stops opening for people without a licence.
3.  **Dynamics 365-only users.** Their app rights cover apps in the Dynamics environment only.

The warnings have already started. Admin notices began in March 2026. In-app banners began in June 2026. A user without a licence sees a banner that goes from informational to warning to error, seven days apart. In February 2027 the app stops opening. Nothing is deleted, and access comes back once a licence is assigned.

Test environments count too. Microsoft stops creating unmanaged developer environments on November 15, 2026, and suspends existing ones from December 15, 2026. Managed developer environments need premium licences to run apps and flows, so your testers need them too. The one exception is makers who only build Copilot Managed Runtime apps.

**Do this before February 2027:**

1.  In the Power Platform admin center, go to **Licensing**, then **Power Apps**, then **Download report**.
2.  Pick **Users requiring licenses in Managed Environments** and the latest month.
3.  For each person on the list, assign a licence, move the app, or retire it.

The report only lists people who opened an app that month, so run it every month until February. Power Automate Premium also counts, so check what people already have before you buy.

## What this does not fix

The right app type won’t fix a bad data model. A canvas app on a SharePoint list that should have been three related tables will still fight you. So will a model-driven app with no clear process behind it.

Preview software can still let you down. During the Copilot Managed Runtime preview, a user without enough credits gets a warning first. After 20 app operations or five minutes, whichever comes first, they’re blocked.

And every app needs an owner. An app someone made in an afternoon still needs a person to fix it when a column changes. Pick the type your team can still look after a year from now.

## The bottom line

Answer the five questions at the top, and you have your app type. Before anyone builds, check who will need a licence to open it. Then download the **Users requiring licenses in Managed Environments** report this month, not in January.

Got a form to rebuild? The decision tree sorts it into canvas, a list form, or a bigger app before you pick a door.

InfoPath Forms Decision Tree

PDF · 7 pages

[Email me the PDF](https://tenantcraft.ca/resources/guides/infopath-forms-decision-tree)

---

_Canonical HTML: https://tenantcraft.ca/insights/power-apps-canvas-vs-model-driven-vs-code-apps · Agent guide: https://tenantcraft.ca/llms.txt · Site map: https://tenantcraft.ca/sitemap-index.xml_
