2026-11-17
Power Apps with Dataverse - Simply Explained

Show notes
Most Power Apps projects don't fail on the app. They fail on the data. In this episode of Simply Explained you will learn:
- Why a simple spreadsheet starts to break
- What Power Apps actually is
- What Dataverse actually is
- How the two fit together
- What this looks like in real life
- The mistakes beginners make
- The honest limits
- Where it fits in Microsoft 365 and Azure
- What to remember about Power Apps with Dataverse
Simply Explained by M365.FM breaks down Microsoft 365, Azure and modern IT topics in clear, jargon-free language. Hosted by Mirko Peters. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support. This episode includes AI-generated content.
Host: Mirko Peters
Guests
Transcript
Read the full transcript
Welcome to the M365 FM podcast, where we explore the people, ideas and technologies shaping the future of work. Why a simple spreadsheet starts to break most power apps projects don't fail on the app, they fail on the data. You can drag together a form in an afternoon, and it'll work beautifully on your desk until real people start using it. The table grows and it starts giving wrong answers without telling you. The culprit is usually where the data lives and how it's set up, which is exactly what Dataverse is for. This is M365 FM, where we explore the people, ideas and technologies shaping the future of work. By the end, you'll understand what power apps with Dataverse actually is, and the one setting that decides your bill. Think about how most teams really track the things that matter. It's a spreadsheet or a SharePoint list or a shared file sitting in teams. It works fine at the start, and that's the trap because it works right up until it doesn't. Then the team grows. Two people open the same file, one overwrites the other, and someone makes a copy because they don't trust the original. Now you're juggling three versions and nobody can tell you which one is correct. The tool was never the problem. The problem is that nothing owns the truth, so there's no single place holding the real numbers and no rules that apply to everyone who touches them. To be fair, spreadsheets are brilliant and they aren't the villain here. They're built for one person working at a desk, not for a team that needs shared rules and one trusted number. The moment your process depends on other people getting it right, you've outgrown the file. Picture the Friday afternoon version of this. Someone exports the sheet, tidies it up by hand, and emails it around, and by Monday the numbers are already stale. That clean up is a job nobody enjoys, and it's the first thing a small app can take off their plate. That's the gap. A business app is supposed to close. You get one place for the data, one set of rules, and one view that everybody shares. The arguing about which file is right simply stops because there's only one. One choice you make at the very beginning decides whether this stays cheap or quietly gets expensive. And it isn't the obvious one. Most beginners pour their energy into how the app looks when the decision that matters is sitting one layer below the screen, we'll come back to that choice because it changes how you think about the whole project. What Power Apps actually is. PowerApps is Microsoft's tool for building business apps. Without a development team. You drag buttons, forms, and lists onto a screen, connect them to your data, and you have something people can actually use. It's one piece of a bigger family called the Power Platform, which also includes Power Automate for automation and power BI for reporting. The word you'll hear thrown around is low code, and it means what it sounds like. You do most of the work visually by dragging and dropping, and you only reach for code if you genuinely need something custom. You don't have to start from nothing either. Microsoft ships ready made templates for common jobs like help desk, asset checkout, and site inspection, so your first app can be a template you adjust rather than a blank page. You stare at two kinds of apps come out of it, and the difference matters later. The first is a canvas app where you start with a blank screen and build whatever you want from many different data sources. The second is a model driven app where you start with your data model, and PowerApps generates the screens and forms from it. A quick example makes it real. Say your team inspects equipment so you build an app with a form, a photo field, and a submit button, and a technician fills it in on a phone while standing next to the machine. The canvas version gives you freedom and it can connect to almost anything. The model driven version gives you consistency because the structure comes straight from the data itself, and that pays off when the data gets complex. Once it's built, the app runs in a browser and on phones and tablets, which matters more than it sounds. The people using it are often standing on a factory floor or sitting in a van, not parked at a desk, and the app has to meet them where they are. Power apps can reach data in plenty of places, and Dataverse is only one of them. SharePoint, Excel, and SQL are all fair game, and if you have a premium license, Microsoft says you get access to over three hundred and fifty standard and premium connectors. Put simply, it can talk to a huge range of other systems. Notice that the app keeps connecting to data because the app is the easy part. Where that data lives is what decides everything else. What Dataverse actually is. Dataverse is Microsoft's data layer, and in plain terms, it's a database you rarely have to treat like a database. Microsoft describes it as a secure, cloud based place to store and manage the data. Your business apps use your data lives and tables. A table is just a set of rows and columns, the same shape as a spreadsheet with one important difference. Each column is built to hold one specific kind of data. So a date column stays a date and a number column stays a number. The days of someone typing not applicable into a date field are over. Some tables come built in and you don't have to invent them. Microsoft ships a base set of standard tables for common business things like contacts and accounts, and you create custom tables for whatever is unique to your organization. Those tables aren't just text, either. A column can hold a file, an image, a date, a choice from a fixed list, or a link to a row in another table. The shape of your data is something you design, not something you type and hope for. The tables can also point at each other, which is where a spreadsheet quietly falls apart. You can have a customers table and an orders table, and each order links back to the customer who placed it. Change that customer's phone number once and every order pointing at them sees the update. Because there's only one copy of that phone number in the whole system. Dataverse is also where the rules live. You can set a business rule that says a field can't be left empty, or a workflow that fires. When a rule changes, those rules apply. No matter which app or which person is reading the data, you set it once and every app obeys it. Security works the same way, which is a relief once you see it. Access is controlled centrally, so you decide who can see which rows and which columns. Instead of rebuilding permissions inside every app you make, getting data in is handled. Two. You can import a spreadsheet once or set up a scheduled sync with another system. Microsoft's Power Query tool, the same one you may know from Excel and Power BI, can clean and reshape the data on the way in. The same data, then feeds more than one tool. Power apps reads it, Power Automate, triggers on it, power BI reports on it, and dynamics three hundred sixty five stores its own business data in Dataverse two. That gives you one source of truth and a whole family of tools that can share it. If that sounds like heavy governance, that's exactly the point. Data versus the layer that makes an app trustworthy and trust is the thing you're really paying for. How the two fit together. Put them together and the picture is simple. PowerApps is the front door people open and Dataverse is the back office where the records actually live. Walk through it once end to end, a technician opens your app and fills in an inspection form, and that form saves a row into a Dataverse table. A power automate flow notices the new row and emails the manager, while power BI reads the same table and charts how many inspections failed this month? That's four tools. Reading one set of data with no copying between them. Contrast that with the spreadsheet version there the app, the reminder email, and the report each lean on their own copy of the list, and the moment one copy changes, the others are wrong. In the Dataverse version, there's nothing to keep in sync because there was only ever one copy. That's what the pairing buys you. The app becomes disposable in a good way, because you can redesign the screens or replace the app entirely, and your data doesn't go anywhere. It was never trapped inside the app in the first place. A second benefit shows up later once the team gets comfortable, because the rules and validation live in Dataverse, every app and every flow respects them, so you don't fix the same mistake in five different places. There's only one place where the rule lives. Think of those rules as house rules when they live in the data. A new app someone builds next year inherits them for free. And that's how a small project stays consistent as the team adds more tools around it. And it isn't a closed box. Other Microsoft tools and outside systems can read the same data through connectors, so Dataverse can sit at the center of a small team's app today and still feed bigger reporting later. That's the theory. And this is also where it stops being abstract. Real teams use this every day for small, focused things, and those examples make it click. What this looks like in real life. Take a facilities team. They used to inspect buildings with a paper form and a clipboard, and someone typed the results into a spreadsheet at the end of the week. That meant the data was always a few days old, and problems waited until Friday to get noticed. They rebuilt it as a phone app backed by Dataverse, so the inspector fills in the form on the spot. The row saves instantly and the manager sees problems the same day. Then there's a small sales team. They tracked leads in a spreadsheet and the app, the follow up reminders and the weekly Report, all pulled from different copies of the same list. Moving those leads into Dataverse meant the app, the automations, and the reports all read the same records. So when a lead state is changed, everything updated at once. Onboarding works the same way. A new hires record sits in Dataverse, and that single record drives a chain of approvals. A welcome email and a task list in teams. Nobody. Ricky's the person's name into four different systems, and nobody wonders which spreadsheet has the latest start date. Notice what these have in common. They're small, focused apps that replace a messy manual process, and they don't pretend to be a full enterprise system. That's part of why they're quick to build. The payoff shows up in small ways to the manager stops chasing updates, the report builds itself, and the team finally trusts the number on the screen. None of it required writing code either. The data lives in Dataverse, the screens come from PowerApps and the glue comes from Power Automate. Here's the encouraging part. If you're brand new to this, you don't start with the whole company. You pick one annoying process, build the smallest app that fixes it, and let the wind speak for itself. The teams that succeed usually start smaller than they think they should. And if that's your team, you're in good company. Real projects still go wrong, though, and they tend to go wrong in the same few places. The mistakes beginners make start with the mistake that costs the most people later. They build in the default environment and call it production because it's already sitting there. Every Microsoft tenant gets a default environment created automatically, and it's meant for experimenting and trying things out. Microsoft is clear that it offers no backup guarantees and shouldn't hold work you depend on. So the moment an app matters, it belongs in a proper production environment. Then there's the file problem. People dump everything, including big files, into Dataverse, and files and images live in a different storage bucket from your table data. That bucket has its own price. So if your app is mostly attachments, SharePoint is often the cheaper home for them. With Dataverse holding the record that points to the file delegation is the one that hides best when a query can't be handled by the data source. PowerApps pulls the first five hundred rows and works with those. It doesn't warn you loudly and it just shows part of the table while looking completely fine. You can raise that limit up to ten thousand rows. But the real fix is writing queries that Dataverse can handle directly. The trap is that everything looks perfect while you test, because your test table is small and then it breaks the day the real data shows up. A quieter mistake is treating it like a spreadsheet and skipping the data model. People built the app first, then realized the tables were wrong and rebuilt the whole thing. A little thinking about the tables up front saves a painful rebuild later. The last trap is sharing the app with everyone by default. It's easy to hand an app to the whole company, but not everyone should see every row. Dataverse gives you row level and column level control, and it only helps if you actually use it. So give people the access they need rather than the access that's convenient. All five have the same root cause. The data design was an afterthought, and Dataverse is the part that punishes afterthoughts. The flip side is that getting the design right also controls what this costs you. And that's where we go next. The honest limits cost is the limit people ask about first. So let's put real numbers on it. Power apps premium runs about twenty dollars per user per month billed yearly, and that includes Hundred and fifty megabytes of Dataverse database and two gigabytes of file storage per user. Microsoft pulls that capacity across your whole tenant, which softens the blow for a small team. If you're only learning, you can start free. There's a PowerApps developer plan that costs nothing and gives you environments to build and test in as long as you remember that a real app for real users needs a paid license. If you'd rather not commit to a per user license upfront, there's also a pay as you go option that runs through Azure, where you pay for what you use instead of buying seats. It suits seasonal or experimental projects, and it's worth knowing it exists before you sign a yearly contract. Extra database capacity is where it gets expensive. The add on list price is around forty dollars per gigabyte per month, so read that number twice, because it's the one that turns a design choice into a budget line. A gigabyte of table data is a huge number of rows, so most small apps stay inside their included capacity. But files, images and audit logs can quietly push you over. It helps to know that Dataverse counts three kinds of storage. There's database storage for your tables, file storage for attachments and images, and log storage for things like audit records. Microsoft even includes a starter amount in the default environment, with three gigabytes of database, three gigabytes of file, and one gigabyte of log capacity, which is plenty for a small first project. When you do go over, Microsoft doesn't delete your data. It warns you first when less than fifteen percent of your capacity remains, then again below five percent. And finally, when you're in overage at that point, it can block some environment operations like creating or copying an environment, because each of those needs at least a gigabyte of free capacity. There are other honest limits worth knowing. Model driven apps need Dataverse as their data source, so that style of app isn't available without it. Canvas apps are flexible, but they carry that delegation ceiling once your tables get large. And while Microsoft says there's no technical limit on the size of an environment, there is very much a limit on what you're willing to pay for. None of this is meant to scare you off. It's meant to show that in Dataverse, the design decisions are also money decisions, and knowing that upfront is the whole game where it fits in Microsoft three hundred sixty five and Azure Dataverse isn't a separate universe you have to sign into. It lives inside your Microsoft Entra tenant, the same identity system behind teams, outlook, and everything else in Microsoft three hundred sixty five. It's also tied to a geographic region, so your data stays where your organization expects it to be. That detail matters if you're new to all this, because it means you're not adding a new login or a new security world, the people who can use your app are the same people already in your organization's Microsoft account, and the access rules come from the same place. From there, it reaches the tools your team already opens every day. Power automate can trigger off a row and post to teams or send an email, and power BI can build a report on the same data. The Microsoft three hundred sixty five apps you already pay for can read from it through connectors. It's the shared data layer under the Power Platform, Power Apps, Power Automate, and Power BI all read from IT and dynamics three hundred sixty five stores its own business data there, too. That's why you can build an app directly on data that already lives in the dynamics three hundred sixty five system, without setting up a separate integration between the two. The Azure side is where it opens up. Dataverse data can flow out to Azure for bigger analytics and event work. Microsoft lists integrations like Azure Synapse Link for Dataverse, exporting to Azure SQL, and pushing events to Azure Event Hubs or Service Bus. You don't need any of that on day one, but it's the bridge from a small app to a company wide data picture. So the honest answer to where Dataverse fits is this. It isn't. Instead of Microsoft three hundred sixty five or Azure, and it's a layer inside the same Microsoft cloud, close enough that the tools you already use can read from it. What to remember about PowerApps with Dataverse. So let's pull it together. PowerApps builds the app. Dataverse holds and governs the data, and the choice of where that data lives is the one that decides whether this stays affordable and trusted or quietly gets expensive. Here's the question I'll leave you with. What's one process in your work that still lives in a spreadsheet? Two people fight over. If this made the topic feel less intimidating, subscribe to M365 FM to master the tools and the mindset shaping the future of work.