Live training: next batches coming soon. Join the waitlist:Waitlists open:Developer Training →Developer →Copilot Studio Training →Copilot Studio →

Power Apps Dataverse vs SharePoint List: Which One Should You Use?

Two people on your team want to build the same Power Apps request tracker. One says use a SharePoint list, the other says Dataverse, and both sound completely sure.

In this tutorial, we’ll settle the dataverse vs sharepoint list question the way we do it for client projects: licensing first, then security, row limits and delegation, relationships, and lifecycle. Every number comes from our own SPGuides tests or Microsoft Learn.

Quick answer: Use a SharePoint list for simple team apps with flat data, a few thousand rows and Microsoft 365 licenses only. Use Dataverse when you need role-based, row-level or column-level security, real table relationships, model-driven apps or solutions, and your users have a premium license such as Power Apps Premium.

What You Need Before You Start

  • A rough row count for year one and year three. It decides more than any feature list.
  • A list of who may read, edit or never see each piece of data. That drives the security choice.
  • Your users’ licenses. Check the Microsoft 365 admin center before you design anything.
  • Basic Dataverse vocabulary (tables, rows, columns, environments). Our guide on what Microsoft Dataverse is covers it in ten minutes.

Step 1: Check Licensing Before Anything Else

Most Microsoft 365 licenses include limited Power Apps rights for Microsoft 365 data and standard connectors. SharePoint is a standard connector, so a canvas app on a SharePoint list usually costs nothing extra.

Dataverse is different. Using it from a custom app needs a standalone premium license such as Power Apps Premium, or a pay-as-you-go plan tied to an Azure subscription. The “Dataverse” service plan you may see in the Microsoft 365 admin center doesn’t give those rights.

Two more licensing notes. Since 01/02/2026, the Power Apps per app license isn’t sold to new customers through some channels. And the free Developer Plan is for building and testing only, never for production. If you’re still on SharePoint, our ways to display a SharePoint list in Power Apps work with standard licenses.

Service Requests SharePoint list on the SPGuides team site with Title, Status and Priority columns

Step 2: Compare the Security Models

Security is where the two really split, and it’s the question we get most often. SharePoint secures containers: the site, the list, and individual items. Dataverse secures data through roles, ownership and columns, enforced on the server for every app and flow.

How SharePoint List Security Works

List items inherit permissions from the list, which inherits from the site. You can break inheritance on single items, but Microsoft supports up to 50,000 unique permissions per list and recommends staying under 5,000. Once a list passes 100,000 items, you can’t break inheritance on the list itself anymore.

Two gaps matter for apps. SharePoint lists have no column-level permissions, so hiding a column in a form or view isn’t security. And because the app writes as the signed-in user, everyone who edits through the app also needs edit rights on the list, so they can open it in the browser and skip your app.

How Dataverse Security Works

Dataverse groups privileges into security roles: Create, Read, Write, Delete, Append, Append To, Assign and Share. Each privilege gets an access level: user, business unit, parent-child business unit or organization. So “read every request, edit only your own” is one role setting, not a script. Our Dataverse privileges error fix shows what happens when a role is missing.

  • Business units split users and data into security boundaries under one root unit.
  • Teams: owner teams own rows; access teams get rows shared with them.
  • Column-level security: a column security profile grants Read, Create or Update on secured columns, such as salary.
  • Record sharing covers one-off exceptions. Microsoft recommends it only for exceptions because it’s slower.
  • Privileges add up: a user gets the broadest access from all roles and teams.

One test note: column security never grants access to a row. The user needs row access first, and then the profile opens the protected columns.

Step 3: Size Your Data and Check Delegation

A SharePoint list can hold 30 million items, so raw capacity is rarely the problem. Large lists bite in two other places: the 5,000-item list view threshold in SharePoint itself (see our list view threshold error fix) and delegation in Power Apps.

Delegation means Power Apps sends the query to the data source. When a formula can’t be delegated, Power Apps pulls only the first 500 rows by default; you can raise the Data row limit in Settings to 10,000. Rows beyond that are silently ignored.

SharePoint delegates less. Text columns support = but not < or >, the ID column delegates only with =, and Person columns delegate only Email and DisplayName. Dataverse delegates more, but not everything. We filtered our Dataverse Service Requests table on Len(Subject) > 12 and got two delegation warnings, as our Power Apps delegation guide explains.

CountRows(Filter('Service Requests', Len(Subject) > 12))
Power Apps Studio delegation warning under a Len filter on a Dataverse table

CountRows surprised us too. On Dataverse it showed “CountRows may return a cached value. Use CountIf(DataSource, true) to get the latest count.” and returned 0, while this formula returned the correct 8:

CountIf('Service Requests', true)
CountRows cached value warning tooltip in Power Apps Studio on the Service Requests Dataverse table

In Power Automate, the Dataverse List rows action returns up to 5,000 rows; turn on Pagination to raise the threshold to 100,000. We cover more flow patterns in our Dataverse row count flow.

Step 4: Map Relationships and Data Types

SharePoint gives you lookup columns that point to another list. Dataverse has real one-to-many, many-to-one and many-to-many relationships. A model-driven app (Dataverse only) lets users move between related rows without any formulas; see our model-driven app build guide.

Dataverse columns are richer too. Our Asset table’s New column list offers Text, Number, Date and time, Lookup, Choice, Currency, Autonumber, File, Formula and Prompt.

Dataverse New column panel with the data type list Text, Number, Lookup, Choice, Autonumber and File

An autonumber column filled our Asset Tag as ASSET-1000, ASSET-1001 and up with no flow at all; our Dataverse autonumber walkthrough shows the setup.

Dataverse Assets grid with Asset Tag autonumber values from ASSET-1000

Dataverse also runs business rules, workflows and calculated logic on the server, so every app gets the same validation. SharePoint relies on column validation and whatever your app or flow checks.

Step 5: Plan Capacity, Auditing and Deployment

SharePoint storage comes from the tenant pool: 1 TB plus 10 GB per license, with up to 250 MB per list attachment. Dataverse capacity is separate, split into Database, File and Log, pooled per tenant, and it grows with licenses and add-ons. Ask your admin how much is free.

For history, SharePoint keeps version history (up to 50,000 major versions). Dataverse adds auditing you turn on per environment, table and column. For dev, test and production, Dataverse tables, apps and flows travel in a Dataverse solution; list-based apps usually need their data source repointed after a move.

Dataverse vs SharePoint List Cheat Sheet

AreaSharePoint listDataverse
License for custom appsMicrosoft 365 license (standard connector)Premium, such as Power Apps Premium, or pay-as-you-go
SecuritySite, list and item permissions; no column securityRoles, business units, teams, row and column security
Unique permissions50,000 per list (5,000 recommended)Role-based; sharing only for exceptions
Size30 million items; 5,000-item view thresholdCapacity-based (Database, File, Log)
DelegationFewer delegable operationsMore delegable operations; Len etc. still local
RelationshipsLookup columns1:N, N:1 and N:N relationships
App typesCanvas appsCanvas and model-driven apps
Server-side logicColumn validationBusiness rules, workflows, plug-ins
DeploymentRepoint the data sourceSolutions (managed and unmanaged)

Common Mistakes to Avoid

  • Hiding a column and calling it secure. In SharePoint, anyone with list access can still read it in the browser.
  • Trusting a count without testing. Our CountRows label read 0 on a table with 8 rows.
  • Raising the Data row limit instead of fixing formulas. 10,000 is the ceiling, and big pulls slow the app down.
  • Breaking inheritance on thousands of items. Past 5,000 unique permissions, the list gets hard to manage.
  • Assuming Microsoft 365 includes Dataverse for custom apps. Check licenses before the build, not after.

Do You Need SharePoint to Use Power Apps?

No. Canvas apps connect to Dataverse and many other sources through connectors, and model-driven apps use Dataverse only. SharePoint is just the cheapest place to start when everyone already has Microsoft 365. More options are on our Power Apps tutorials hub.

Can You Move From a SharePoint List to Dataverse Later?

Yes, and we did it on 10/22/2026. A dataflow copied our 623-item Service Requests list into a new Dataverse table: 623 rows created, 0 failed, in 1 minute 31 seconds. The Create with SharePoint list (preview) option returned “Couldn’t import” twice in our environment.

The full walkthrough is in how to create a Dataverse table from a SharePoint list, and Dataflow in Dataverse covers refresh settings.

Next Steps

If Dataverse won, start small: create your first Dataverse table, add one security role, and test it with a user who isn’t an admin.

We’d keep these guides open while you decide:

Frequently Asked Questions

Is Dataverse more secure than a SharePoint list?

Dataverse is more granular. It adds security roles with access levels, business units, teams and column-level security, all enforced on the server. SharePoint secures sites, lists and items, with no column-level permissions.

Do I need a premium license to use Dataverse in Power Apps?

Yes, for custom apps. Users need a premium license such as Power Apps Premium, or the environment uses a pay-as-you-go plan. Microsoft 365 licenses cover standard connectors like SharePoint.

What is the delegation limit for SharePoint and Dataverse?

Both share the app’s Data row limit: 500 by default, up to 10,000, for formulas that can’t be delegated. Microsoft explains it in Understand delegation in a canvas app.

What is the default limit for Dataverse List rows in Power Automate?

List rows returns up to 5,000 rows. Turn on Pagination in the action’s settings and set a threshold of up to 100,000.

Where does Microsoft document Dataverse security?