What is Microsoft Dataverse, and when is it worth the premium licence?

29 October 2026
By Matt Weston
A vast, orderly archive hall of labelled drawers in navy and gold, representing how Microsoft Dataverse stores business data in structured tables

Most people meet it by accident. A template asks for it, a little premium diamond appears next to a connector, or a colleague opens your shiny new app and gets a licence prompt. The usual mistakes run in opposite directions: some teams treat Dataverse as the automatic grown-up choice, others avoid it on principle and then strain a SharePoint list far past what it was designed for. And with two Microsoft changes landing on 15 November 2026, the timing matters more than usual.

So here’s the plain version: what Dataverse actually is, when a SharePoint list or Excel genuinely does the job, what it costs to put an app in front of real users, and how to start without paying for capacity you don’t need.

Quick summary

Dataverse is a database, not a feature: tables with typed columns, relationships and server-side rules that every app and flow must respect.
SharePoint lists are enough for simple trackers, but the 5,000-item list view threshold and weak relationships bite as apps grow.
Excel is a poor app back end because files get locked, renamed and copied; use it to import or report, not as the live store.
Every user needs premium rights to run a Dataverse app, and Power Apps Premium is £15.40 per user per month, paid yearly, excluding VAT.
New Dataverse for Teams environments stop on 15 November 2026, and unupgraded ones are decommissioned on 30 October 2027.

Treat it less as a technology choice and more as a running commitment: once your data lives in Dataverse, the licence follows each user for as long as the app is in service.

What is Microsoft Dataverse, in plain terms?

Dataverse is a cloud database that Microsoft runs for you. Your data lives in tables; each table has columns (a name, a date, a currency amount) and rows (one customer, one order, one site visit). It ships with a set of standard tables such as Account and Contact, and you add your own custom tables for anything specific to your business. If you read older blogs and see “entities”, “fields” and “records”, that’s the same thing: Microsoft renamed them to tables, columns and rows in November 2020.

What separates it from a list or a spreadsheet is what happens around the data. Tables can be related to each other, so an order knows which customer it belongs to and a customer can show all of their orders. Business rules run on the server, so a rule like “a discount over 20 per cent needs an approver” applies whether someone uses your app, a flow or an Excel add-in. And security is layered: roles control which tables people can touch, and row-level and column-level security control which records and which fields they see. That’s the difference between hoping people keep data tidy and making untidy data impossible to save.

It’s also where Dynamics 365 keeps its data. If your organisation already runs Dynamics 365 Sales or Customer Service, your customer records are already in Dataverse, which means you can build apps on that data without any integration work at all.

Where you’ll meet it in Power Apps and Power Automate

For most people learning the Power Platform, Dataverse shows up in four places:

  • Canvas apps can use Dataverse as one data source among many, alongside SharePoint, Excel or SQL.
  • Model-driven apps are built on Dataverse and nothing else; the tables, forms and views are the app.
  • Power Automate has Dataverse triggers and actions, such as starting a flow when a row is added, modified or deleted.
  • Copilot Studio agents and many Microsoft templates create Dataverse tables behind the scenes.

If you’re still getting to grips with the tools themselves, start with our guides to Microsoft Power Apps and Microsoft Power Automate, then come back to the data question. The data decision is easier once you know what kind of app you’re building.

Dataverse vs SharePoint list vs Excel: which should you use?

Our verdict first: for a simple internal tracker used by a team who already have Microsoft 365, start with a SharePoint list. Move to Dataverse when the data has real relationships, real security needs or real volume. Don’t use Excel as the live back end of an app at all. Here’s how the three compare on the points that actually decide it:

SharePoint listExcel workbookDataverse
Licence to run an app on itIncluded with most Microsoft 365 plansIncluded with most Microsoft 365 plansPremium for every user
Comfortable data sizeUp to 30 million items, but views struggle past 5,000 without indexingSmall, and one file at a timeBuilt for large, growing data sets
Relationships between tablesLookup columns only, and they get slowNone worth relying onProper one-to-many and many-to-many
SecurityList, folder or item permissionsWhole file, or nothingRoles, row-level and column-level
Rules that always applyBasic column validationFormulas anyone can overwriteServer-side business rules
Best forTeam trackers, requests, simple registersImports, one-off analysis, reportingLine-of-business apps, model-driven apps

Notice that the top row decides more projects than any of the technical rows below it.

When a SharePoint list is the right answer

A SharePoint list costs nothing extra, uses a standard connector and is familiar to almost everyone. Microsoft’s SharePoint limits allow up to 30 million items in a list, which sounds limitless, but the practical ceiling is the 5,000-item list view threshold: past that, unindexed views and filters start to fail. For a holiday tracker, an equipment register or an IT request form, a list is the sensible choice and we’d tell most small teams to stop there.

When Excel is the right answer

As the live data source behind an app, almost never. Workbooks get locked while someone has them open, renamed, moved and quietly copied, and none of that is visible to the app until it breaks. Excel is excellent at the edges, though: Dataverse can import Excel and CSV files, so a spreadsheet is a perfectly good way to load starting data, and it remains a great place to analyse data once it’s been exported.

When Dataverse earns its cost

These are the signals that a list has stopped being enough:

  • Your data naturally splits into several related tables, such as customers, sites, jobs and invoices.
  • Different people must see different rows, for example managers seeing only their own team’s records.
  • You expect thousands of rows that users need to search and filter quickly.
  • You want a model-driven app, or you need an audit trail of who changed what.
  • You already pay for Dynamics 365 or Power Apps Premium, so the licence question is already answered.

Two or more of those and Dataverse usually pays for itself in time saved fixing bad data. Just one, and a well-designed list is probably still fine.


Worth knowing

The licence check happens when people run your app, not when you build it.

You don’t need a licence to build a canvas app, so it’s entirely possible to finish an app on Dataverse and only discover at launch that nobody can open it. Before you share anything, open the app’s Details page in Power Apps and check the License designation. If it says Premium, every user needs premium rights. Also, Microsoft is clear that a Dataverse service plan appearing against a Microsoft 365 licence in the admin centre does not give users the right to run standalone custom apps.


Dataverse licensing: what it really costs

Most Microsoft 365 plans include limited Power Apps and Power Automate rights for Microsoft 365 data and standard connectors. Dataverse isn’t one of those. Microsoft’s Power Apps licensing FAQ lists Dataverse tables alongside premium connectors, on-premises gateways and custom APIs as features that need premium rights, and states that model-driven apps are premium by default because they use Dataverse.

On Microsoft’s UK pricing page today, Power Apps Premium is £15.40 per user per month, paid yearly, excluding VAT (£9.20 if you buy at least 2,000 seats). Microsoft has also announced a list price rise from 1 January 2027 without yet publishing the UK figure, so budget with some headroom. The per-app plan is no longer available to new customers through some purchasing channels from 2 January 2026, so for most small organisations it’s per-user or nothing.

Each Power Apps Premium licence also adds 250 MB of database capacity and 2 GB of file capacity to a pool shared across your tenant. If you outgrow that, extra database capacity is £30.80 per GB per month on the same UK page, which is a good reason not to store files and images in database tables when file columns exist.

A quick worked example

A 25-person operations team wants a job-tracking app on Dataverse. That’s 25 × £15.40 = £385 a month, or £4,620 a year before VAT, and it adds 6.25 GB of database capacity to the pool. If only six of those people will ever use the app, the honest answer may be a SharePoint list for everyone plus a better-designed process, rather than 25 premium seats.

Flows follow similar logic. A Microsoft 365 licence covers flows with standard connectors. A flow that uses the Dataverse connector needs Power Automate Premium, unless it’s tied to a premium Power App and runs in that app’s context.

Two changes landing on 15 November 2026

Microsoft’s list of important changes includes two that directly affect anyone starting with Dataverse this autumn.

First, Dataverse for Teams, the cut-down version that came free with many Microsoft 365 plans, is being retired. From 15 November 2026 you can’t create new Dataverse for Teams environments. Existing ones are suspended on 15 September 2027 and decommissioned on 30 October 2027 unless they’re upgraded to full Dataverse, at which point the apps and flows inside them need Power Apps, Power Automate or Copilot Studio licences. If your team built something useful in Teams, start the licensing conversation now rather than next September.

Second, the free Power Apps Developer Plan changes. From 15 November 2026, signing up no longer creates a developer environment, unmanaged developer environments are suspended from 15 December 2026, and each user can create only one managed developer environment. For learners, that means asking your admin for a managed developer environment instead of signing yourself up.

How to start with Dataverse without wasting money

A sensible first project follows the same order every time:

  1. Sketch the data on paper first: the things you track (your tables) and how they relate, before you open any tool.
  2. Count the people who will actually use the app, and check who already holds Power Apps Premium or a Dynamics 365 licence.
  3. Build a prototype in a trial, sandbox or managed developer environment, never in the default environment.
  4. In Power Apps, select Tables, then New table; start blank or import your existing Excel or CSV file to save typing.
  5. Before sharing, open the app’s Details page and confirm the License designation matches the licences you’ve budgeted for.
  6. Set up security roles so each person sees only the rows they should, then test as a real user before go-live.

Step one is where most projects are won or lost. A clear table design makes every later screen and flow simpler, and a muddled one can’t be rescued by clever formulas. Our PL-900 Power Platform Fundamentals course covers exactly this ground if you’d like a structured start.

Not sure whether your next app needs Dataverse or just a SharePoint list?

The bottom line on Microsoft Dataverse

Dataverse is the right home for business data that has structure, relationships and people who should only see part of it. It’s the wrong home for a simple team tracker, and it’s never free once real users are involved.

Decide on the licence before the design, design the tables before the screens, and don’t start anything new in Dataverse for Teams. Get those three right and the rest of the Power Platform becomes much easier to learn.

When you’re ready to build properly on Dataverse, our PL-7003 model-driven apps course takes you from tables and relationships to a working app your team can use.

Frequently asked questions

Is Dataverse free with Microsoft 365?

Not for custom apps. Most Microsoft 365 plans let you build and run Power Apps on standard data sources such as SharePoint lists, but an app or flow that uses Dataverse tables needs premium rights for every user, for example Power Apps Premium. A Dataverse service plan showing in the admin centre doesn't change that. The free Developer Plan is for learning and testing only, not production use.

Is Dataverse a database?

Yes, in practice. Dataverse stores data in tables made of rows and columns, with relationships between tables, and Microsoft manages the storage, backups and scaling for you. It adds things a raw database doesn't give you out of the box, such as business rules, role-based security, auditing and a ready-made interface for model-driven apps, which is why Microsoft describes it as a data platform.

What is Dataverse used for?

Storing the business data behind Power Apps, Power Automate flows, Copilot Studio agents and Dynamics 365. Typical uses are line-of-business apps such as job tracking, case management, asset registers and customer records, where the data has several related tables, needs row-level security, or will grow beyond what a SharePoint list handles comfortably.

Should I use Dataverse or a SharePoint list?

Use a SharePoint list for simple, single-table trackers where everyone already has Microsoft 365 and the data stays modest. Use Dataverse when you need related tables, row-level or column-level security, a model-driven app, an audit trail, or fast filtering across thousands of rows, and you're prepared to license every user for premium.

Is Dataverse part of Microsoft Power Platform?

Yes. Dataverse is the shared data layer of the Power Platform, used by Power Apps, Power Automate, Copilot Studio and Power Pages, and connected to by Power BI. Dynamics 365 customer engagement apps such as Sales and Customer Service also store their data in Dataverse.

What is a Dataverse table?

A table is a set of rows and columns that holds one kind of thing, such as customers or orders. Each column has a data type, such as text, date, choice or lookup, and lookups link one table to another. Dataverse includes standard tables like Account and Contact, and you can create custom tables for your own data. Older material calls tables entities.

Shopping Basket