Power Platform: When and Why to Use Canvas, Model-Driven, Power Pages and Code Apps 

When someone says, “just build it in Power Apps,” the next question should always be: which one? 

Power Apps isn’t a single tool. It’s four different app types, each built for a different audience, a different data scale and a different level of technical skill. Picking the wrong app costs real time and money.  

This guide helps you pick the right one before you start building. 

The Backbone: Dataverse and Connectors 

Before choosing an app type, understand what sits underneath all of them. 

Dataverse is Microsoft’s cloud data platform, a managed relational database with built-in security, relationships, audit history and a native API that every Power Platform product uses. It’s required for model-driven apps and Power Pages. It’s optional, but strongly recommended, for Canvas apps. Code Apps access it via connector or the Dataverse Web API. 

Connectors are pre-built integrations to external services. Power Platform has 900+, split into two tiers: 

Standard: Included with most Microsoft 365 (M365) licenses. Covers SharePoint, Teams, OneDrive, Outlook and Excel. 

Premium: Requires a Power Apps Premium license. Covers Dataverse (full capabilities), SQL Server, Salesforce, SAP, ServiceNow and the HTTP connector for any custom REST API. 

The licensing trip wire most teams miss: the moment your app uses a premium connector, including a call to an external REST API via the HTTP connector, every user of that app needs a premium license. Figure this out before development starts, not after. 

Calling external APIs is supported across all four app types, but the mechanism differs: 

Canvas Apps 

Start Here When: You need a custom user experience like a specific layout, a specific workflow or an original design. 

Canvas apps give you a blank screen and a drag-and-drop builder. You connect to data sources (SharePoint, Dataverse, SQL, REST APIs and 900+ others) and design every screen yourself using Power Fx formulas. 

Best for:

Field team mobile apps with custom flows and offline sync 

Internal tools connecting multiple data sources in one view 

Lightweight approvals, submissions or data collection apps

Limitations to Know:

Large data sets are challenging, and delegation support varies by connector. SharePoint hits limits at 2,000 rows for non-delegable queries 

Complex grids and views require more configuration than model-driven apps provide out of the box 

What’s New in 2026:

Responsive Layouts: Apps built with modern controls now adapt to screen sizes automatically. The old fixed-screen-size limitation is gone for modern control apps. 

Microsoft 365 Copilot is Embedded: Users can ask natural language questions about the app’s data directly inside the app. 

New Modern Controls: Responsive Card control, updated Text Input, Date Picker, Combo Box, Tab List and more, all Fluent UI-aligned. 

Model-Driven Apps 

Start Here When: Your data is complex, relational, lives in Dataverse and you want the platform to handle the UI scaffolding for you. 

You define your Dataverse tables, relationships, forms and views. Power Platform generates the application from that data model. The result looks and behaves like Dynamics 365 because it’s built on the same framework. 

Best for: 

CRM-style applications: accounts, contacts, cases and opportunities 

Enterprise process apps: purchase orders, project tracking and compliance workflows 

Large data sets where everything is server-side in Dataverse without delegation worries 

Limitations to Know: 

You don’t control the overall layout, header, navigation or control styling 

Dataverse is mandatory. There is no way around this 

For custom UI on a specific form, embed a Canvas App component 

What’s New in 2026:

Copilot Side Panel: Users can ask questions about the record they’re viewing, summarize history, surface what’s pending and see related records.  

Copilot Form-Fill: Suggests field values as users complete new records, showing the source of each suggestion before applying. 

Generative Pages via External Tools (GA April 2026): Developers can use GitHub Copilot CLI or Claude Code to build custom UI pages inside model-driven apps via PAC CLI.  

Power Pages (formerly Power Apps Portals) 

Start Here When: your users are outside your organization. 

Power Pages builds external-facing websites and portals backed by Dataverse. Customers, partners, vendors and the public can register, authenticate, submit forms and interact with your data. No M365 account or tenant license required. 

Important Product Change: Power Apps Portals was renamed to Power Pages in October 2022 and is now a standalone Power Platform product. Power Apps Portals Studio was retired February 2024. If your team still calls this “Portals,” the tooling and capabilities have moved on significantly. 

Best for: 

Customer self-service portals that handle support requests, order tracking and account access 

Partner and vendor portals with controlled external access 

Event registration and public information sites 

Built-in Capabilities Worth Knowing: 

Native authentication: Microsoft Entra ID, Azure AD B2C, Google, LinkedIn, Facebook or any OAuth 2.0 / SAML 2.0 provider 

Table permissions and web roles control exactly what each user can see and do with row-level security out of the box 

Low-code design studio for structure and content; Liquid templating, JavaScript and CSS for deeper customization 

Limitations to Know: 

Dataverse is required 

Complex multi-step branching workflows get involved quickly (Liquid + JS + Power Automate flows working together) 

Pricing is different from Power Apps and based on authenticated users and/or anonymous page views per site 

June 2026 Deadline: Microsoft is enforcing table permissions on all forms and lists across all Power Pages sites. If your organization has existing portals with this setting disabled, audit them before this takes effect. 

Code Apps (New — GA February 2026) 

Start Here When: your team writes code, canvas apps aren’t expressive enough but you still want IT governance. 

Code Apps let developers build full web applications in their preferred framework (React, Vue and others), then deploy them inside Power Platform. The developer experience is entirely code-based. The deployed app runs under the same DLP policies, Managed Environments and admin controls as any other app in the tenant. 

This Solves a Real Problem. Before Code Apps, developer teams had two options: build inside low-code constraints or build outside Power Platform and lose governance. Code Apps removes that trade-off. 

Best for: 

Complex, custom web applications that need full front-end control 

Dev teams already using React/Vue who want their apps inside Power Platform governance 

Organizations using AI code generation tools (GitHub Copilot, Claude Code) to accelerate development 

What’s Supported as of May 2026: 

Dataverse integration: CRUD, FetchXML, relationships 

Power Automate flow invocation 

Copilot Studio agent integration 

Solution-aware deployment via PAC CLI (ALM, source control, environment promotion) 

Limitations to Know: 

Requires coding skills. Not a low-code option 

Native Copilot integration is not yet at the same level as Canvas and Model-Driven apps 

Still maturing, but tracked monthly; release notes and capabilities are shipping regularly 

One Governance Note: When a Code App calls an external API natively in JavaScript, DLP policies don’t apply in the same way as they do for connector-based calls in Canvas apps. If your organization has strict data egress controls, flag this with your admin team. 

Decision Table — Updated June 2026 

 
*Canvas and model-driven apps support external users, but those users must be licensed — either as a guest in your tenant or as a named user. Power Pages allows truly anonymous or self-registered external users with no per-user license requirement. 

Which One Do You Choose? 

One question simplifies most decisions: Are your users inside or outside the organization? 

Inside the Org → Canvas or Model-Driven.
Complex Data with Standard Navigation → Model-Driven.
Custom UI or Multi-Source Data → Canvas. 

Outside the Org → Power Pages. 

Your Team Writes Code → Code Apps. 

Mixed requirements are common. A model-driven app for data management with a canvas component embedded for a specific form. An internal tool (model-driven) with a customer-facing portal (Power Pages) on the same Dataverse data. A bespoke front end (Code App) invoking a Copilot Studio agent and writing back to Dataverse. 

The platform supports these combinations by design. The key is knowing which tool owns which part before anyone writes a line of code. 

A Note on Where the Platform Is Heading 

Microsoft’s entire investment across all four app types in 2025–2026 points in one direction: AI inside the apps your organization already runs. 

Model-driven app users can ask Copilot about the record in front of them. Canvas app users can query data in natural language. Power Pages is gaining AI-powered capabilities. Code Apps can invoke Copilot Studio agents as part of application logic. 

The practical implication for anyone building today: your data foundation determines what AI can do on top of it. Clean Dataverse tables and column descriptions, properly permissioned SharePoint, well-documented custom connectors aren’t just good practice for app performance; they’re the prerequisites for everything AI can do once it’s sitting inside your apps.