Power Apps for Finance Teams: Canvas Apps, Model-Driven Apps and Dataverse Explained

Finance teams often live in spreadsheets and email, and Microsoft Power Apps is a tool for building business applications, such as a request form, a review screen or a small tracker. Microsoft's documentation describes canvas apps and model-driven apps, and a data platform called Dataverse that is used by many apps. This guide explains what each is, when Microsoft's pages say one suits a task better than the other, and what a finance team should settle before building. Names, features and availability change by version and licence, so check the linked Microsoft Learn pages for your own environment. If the apps will use Copilot or other Microsoft 365 data, read our guide to Microsoft 365 Copilot data governance and permissions alongside this one.

Canvas apps: you design the screen

Microsoft Learn's canvas app guide (page updated 16 April 2026) describes canvas apps as custom business applications built in Power Apps without writing code. A canvas is a blank design surface on which you drag and drop components to build the interface you need. The page says canvas apps can be shared with specific users or groups, and can run in a browser, on Windows, and on iOS and Android. It also describes two ways to start: generate an app automatically from a data source and then customise it, or build from scratch for more control over design, flow and controls.

On data, the page lists Microsoft Dataverse, SharePoint lists, Excel workbooks stored in OneDrive or SharePoint, SQL Server and Azure SQL, and "hundreds" of other connectors, including Dynamics 365 and Salesforce. Logic in a canvas app is written with Power Fx. Microsoft's Power Fx overview (updated 6 August 2026) describes it as the low-code language of the Power Platform, with Excel-like formulas that makers write in a formula bar in Power Apps, and that can also be stored in YAML source files and edited in Visual Studio Code.

Model-driven apps: the data model drives the screen

Microsoft's model-driven app overview (page updated 9 January 2026) describes a different approach. Model-driven apps are built by adding components such as forms, views, charts and dashboards to tables using an app designer. Relationships between tables allow navigation and avoid unnecessary data repetition. The page says they suit data-dense, process-driven apps, such as employee onboarding, sales processes or member relationships at a bank. It also states that without a data model housed within Dataverse you cannot create a model-driven app, and that Dataverse is the only data platform supported.

The page includes a comparison table. In summary, as Microsoft puts it:

• Data platform: model-driven apps use Dataverse only; canvas apps use Dataverse plus many other sources via connectors.
• Design: model-driven is no-code and component-focused; canvas controls are set through properties using Power Fx.
• Control of the interface: limited and mostly customisation for model-driven; full control for canvas.
• Consistency: high for model-driven; often low for canvas.
• Responsiveness and navigation: automatic for model-driven (navigation follows table relationships if they exist); for canvas, only if designed that way.

The page adds that accessibility is built in for model-driven apps and has to be designed into canvas apps.

Dataverse: the data underneath

Microsoft's "What is Microsoft Dataverse?" page (updated 31 March 2026) says Dataverse lets you securely store and manage data used by business applications. Data is stored in tables made up of rows and columns, with standard tables for common scenarios and custom tables you can create. On security, the page describes role-based security controlling table access by user, and says the overall model combines business units, role-based security, row-based security and column-based security. It also covers business rules, which validate data across columns and tables, and says Power Apps, Power Automate, Power BI and Excel can use Dataverse data. Pricing and plans are not covered here; the page points to Microsoft's pricing information.

A Power Platform reference architecture page on using Dataverse with canvas apps (updated 15 July 2025) gives useful context. It says Dataverse is a good data source for canvas apps because it supports complex data and security models, and that canvas apps can also combine Dataverse with other sources such as SharePoint lists. It warns that performance depends on table design and delegation, and that the delegation limits when searching and filtering need attention. It also notes that canvas apps use Power Fx for logic by default, and that because each operation is independent and not atomic, a failure can leave partial data behind. Its example is a venue row that remains even if the session row fails to create. For a finance team, that kind of partial write is exactly the thing to think about before an app posts anything that matters.

Choosing between them

Microsoft does not give a single rule, but its pages suggest a way to think. Our summary, based on those pages: if you need a custom layout, or need to combine several data sources in one view, the canvas pages point that way. If your process is built around structured tables and relationships, such as a supplier master with linked contacts, contracts and reviews, the model-driven page describes that as its home territory. The two can also be combined; the model-driven page notes that canvas apps are commonly included among its other elements.

Questions to settle before you build

The following are our suggestions, not Microsoft requirements. They come from the governance side of finance work:

• Where is the system of record? If an app writes to Dataverse, SharePoint or a spreadsheet, say which is the source of truth and who can change it.
• Who owns the app? Name an owner and a backup, and record what happens when they leave.
• What data will it hold? If it includes personal data about staff or customers, involve whoever looks after data protection in your organisation. This article does not cover legal requirements.
• Who can see what? Dataverse describes role, row and column security. Agree the roles before building screens, not after.
• How good is the input data? An app is only as reliable as the data it reads. See our guide to financial data quality management.
• Which connectors are allowed? Microsoft's page on data policies (updated 8 April 2026) says administrators can restrict connectors, and that makers cannot save an app or flow that uses a blocked connector. Ask your administrator what policies apply.

Apps that trigger back-office steps often pair with automation. For an overview of how app builders, flows and bots differ, see our guide to RPA in accounting and finance.

Learnsignal's offices are off Baggot Street in Dublin, and we offer in-person training from there. For current details, see our CPD pages.

Frequently asked questions

What is the main difference between canvas and model-driven apps?

Microsoft's model-driven app page says canvas apps give full control of the interface and can use many data sources through connectors, while model-driven apps are built from components added to Dataverse tables and give more limited control but higher consistency.

Do I need Dataverse for a canvas app?

No. Microsoft lists other data sources for canvas apps, including SharePoint lists, Excel, SQL Server and many connectors. Model-driven apps, however, need a Dataverse data model.

What language do canvas apps use for logic?

Power Fx, which Microsoft describes as an Excel-like low-code formula language.

Can an IT administrator restrict what we connect to?

According to Microsoft's data policies page, administrators can restrict connectors through the Power Platform admin center, and blocked connectors cannot be saved into apps or flows.

Does this article cover licensing?

No. Licences and plans change, so check Microsoft's current pages for your tenant.

In short: pick the app type that matches how your process is shaped, decide ownership and data rules first, and check Microsoft's current documentation as features change.