2026-11-15
Microsoft Dataverse for Teams - Simply Explained

Show notes
Dataverse for Teams holds two gigabytes of real data, and it sits inside a license most companies already pay for. It arrived in September of 2020 as a free way to build apps right inside Microsoft Teams. In this episode of Simply Explained you will learn:
- The Free Database Hiding Inside Microsoft Teams
- How It Shows Up Inside Microsoft Teams
- What You Can Actually Build With It
- It's the Real Dataverse, Just Trimmed Down
- The Limits You Hit First
- The Mistake That Catches Almost Everyone
- What Microsoft Changed in 2026
- What This Means for You
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
Related articles
Transcript
Read the full transcript
Welcome to the M365 FM podcast, where we explore the people, ideas and technologies shaping the future of work. The free database hiding inside Microsoft Teams Dataverse for teams holds two gigabytes of real data, and it sits inside a license most companies already pay for. It arrived in September of twenty twenty as a free way to build apps right inside Microsoft Teams. You might assume it's a stripped down toy, but it runs on the same engine behind dynamics three hundred sixty five. That's enough to build a help desk, an inventory tracker, or an approval app without buying anything extra. The catch is that Microsoft has put an end date on it, and almost no explainer mentions that part. The plain English version is this Dataverse for teams is a data platform Microsoft built straight into teams, so a team can store structured information and build simple apps on top of it without ever leaving the app they already have open. Picture the problem it solves. A small team needs to track something, so someone starts a spreadsheet and drops it into a channel. Two people edit it at the same time. The formulas break and nobody trusts the numbers anymore. A shared list runs into the same wall once the data gets complicated. Because lists are built for simple tracking, not for linked records that have to hold together Dataverse for teams, was Microsoft's answer to that exact mess. It hands a team real tables with columns, data types, and relationships between them, so a table of orders can point at a table of customers instead of copying the same names over and over. The price is the part that surprises people. This comes included with most Microsoft three hundred sixty five and office three hundred sixty five plans that already include teams. So for a lot of organizations, it costs nothing extra to switch on the same platform that powers. Dynamics three hundred sixty five sits underneath, just trimmed down for team sized work. That's a real database inside the tool your team already uses for no extra money. But there are two things I want you to hold on to. The platform has hard limits. You'll feel sooner than you expect, and Microsoft has already announced that it's going away with real dates attached. How it shows up inside Microsoft Teams. The strange part is that nobody switches it on. There's no button labeled create a database. The first time someone builds an app or an agent inside a team, or installs a PowerApps build app from the catalog, Microsoft sets up the environment behind the scenes. You usually find out it exists when someone mentions it in a meeting. Each team gets exactly one of these environments. It's tied to that team and the Microsoft three hundred sixty five group behind it. And that link is not something you can move. You can't spin up a second one for the same team, and you can't have two teams share a single environment. So the rule really is one team and one data space. Two things get mixed up here. The environment is the whole data space for the team, and the app is just one thing that runs on it. A single environment can hold several apps, several flows, and several tables that all share the same data underneath, which is why two apps built in the same team can read from the same table. This was built for the person who has never made software before, which means you don't write code, you don't learn a query language, and you don't stand up a server anywhere. You drag a screen together, point it at a table, and publish. Inside that space sits a set of tables. Each table is a category of thing you care about, like laptops or support tickets or new hires. Every table has columns and each column holds one kind of data. So a laptop name is text, a purchase date is a date and a price is a number. Columns can also be choices, which stops people from typing the same state as five different ways. Relationships are where it stops feeling like a spreadsheet. A laptop can be linked to the person who has it, so the two tables stay connected instead of you retyping a name in both places. When you update the owner in one table, the link holds and you never end up with two versions of the truth. Security works the way teams already works, which is the whole point. Owners, members, and guests keep the roles they already have. Owners get made administrators automatically, and there's no separate permission system to learn. If you can see the team, you can generally see the app. Microsoft also added a simple grid editor for these tables. You can type data in directly and see it the way you would in a spreadsheet, which matters more than it sounds for a beginner. That's the difference between something approachable and something that feels like homework. Provisioning is the one detail worth knowing about. Because it isn't instant, it usually takes a few minutes for the environment to be ready. So if your first app feels slow to appear, that's normal and not a sign that something broke. That's the whole setup. And it's easy to miss because nobody announces it. What people actually build with it is the next thing, and it's more ordinary than you'd guess what you can actually build with it. This is where it stops being theory. The list of things teams actually build is very ordinary. They build help desk apps where people log issues and track them to done inventory trackers for equipment and licenses, and onboarding checklists that walk a new hire through their first week. There are leave request forms that route to a manager, approval flows for spending or time off event registration apps and asset trackers that know who has which laptop. None of that needs a developer. You build a canvas app, which is the drag and drop kind, and you build it right inside teams. When it's ready, you hit publish and every member of the team sees a new tab with the app in it. There's no App Store submission, no install step, and no ticket to your IT department. Let me make that concrete with one small example. Say your team keeps losing track of its laptops. You create a table for laptops with columns for the model, the serial number and the status. And then you create a second table for people. You add a link so each laptop points at one person, and you build a simple flow that sends a message when a laptop is checked out. That whole thing is an afternoon, not a project. You can also connect power BI to the data and put a chart on top of it. That helps. Once the table has more rows than anyone wants to read. Teams can even hold a basic chatbot built with Copilot Studio that answers questions from the data you stored, which is a simple assistant rather than a full AI product. Lists and this platform are different tools. A SharePoint list is great for quick tracking. While this is built for solutions with files, images, and related tables that might need to grow later, that distinction matters because it's the moment your simple tracker starts turning into a small application. The pattern holds across all of it. You're taking a repetitive, list shaped chore and giving it a proper home. Once the data lives in a table instead of a spreadsheet, you can filter it, link it, and automate around it. And that's where the real time savings show up. The automation is what makes people stop and pay attention. A flow can watch a table and react, so a new row can trigger a message, an approval, or an update somewhere else, all without anyone remembering to do it by hand. That's the moment a boring tracker starts feeling like a real tool. So far, this sounds like a free win, and that's exactly why the limits catch people off guard. It's the real Dataverse just trimmed down. This is not a toy database bolted onto teams as an afterthought, Dataverse for teams runs on the same underlying platform as Microsoft Dataverse, which is the data layer behind Power Platform and Dynamics three hundred sixty five. Microsoft took that engine, stripped out the parts most departmental apps never touch, and put the rest inside teams in the Microsoft world. It sits in a narrow but useful spot. It rides on the teams license you already have, and it draws from its own separate pool of storage that doesn't eat into the paid Dataverse capacity your tenant buys. In plain terms, this is a side pocket of Microsoft's cloud set aside for teams and using it doesn't take space from anything else. Azure is doing the heavy lifting underneath, but you never see it. When an environment is created, Microsoft Provisions and hosts it for you in a data center and keeps the servers running. You never open the Azure portal, never pick a server size, and never manage a single virtual machine. The cloud part is real. It's just invisible. The honest comparison is with full Dataverse and the gap is wide. Full Dataverse gives you unlimited environments, direct access through APIs, plug ins, model driven apps, richer security auditing, and integrations that push your data into Azure services like event hubs or synapse. Dataverse for teams gives you a slice of that, which is exactly why it was free. That gap is also the escape hatch. A tenant administrator can promote a teams environment up to full Dataverse and the apps, flows, agents and data come along for the ride. So the platform was never a dead end. It was built as a starting point that could grow into the full product. For a beginner, the practical upshot is simple you get enterprise plumbing. Without the enterprise setup, you're borrowing the same foundation that runs billion dollar business systems, and the only thing you're asked to do is build inside a team you already have. None of this means you should rush out and build on it today. It means you should understand it because it explains why Microsoft designs its data platforms the way it does, and where the next version of this idea is heading. The limits you hit first. But here's the part almost no one tells you about Dataverse. For teams, it has real edges and beginners run into them faster than they expect. The first limit is size. Each environment gives you two gigabytes of combined database and file storage, which Microsoft says is usually enough for about a million rows of data. That sounds like a lot. And for a small team it often is, but files and images eat into it faster than rows do. The second limit is how many environments a tenant can have. By default, you get five plus one more for every twenty eligible Microsoft three hundred sixty five licenses. So if you're a large organization that wants a database per team, that's ceiling arrives sooner than you'd like. Microsoft also watches the storage line closely. At eighty percent of that two gigabytes, makers start seeing a warning banner at one hundred percent your existing apps and flows keep running, but nobody can create or install a new app, agent flow or table until space is freed or the environment is upgraded. There's a tenant wide version of the same pressure. When a whole organization approaches its teams environment limit, admins get a notification, and once it's full, the creation of new Dataverse for teams environments is blocked entirely for everyone. So the ceiling isn't only per team, it's also per company. Now think about what the missing auditing actually costs you. If a value changes and someone asks who changed it, you have no record to point at. So any team that needs a paper trail for compliance has already outgrown this tier. Then there are the features that simply aren't there. There's no direct API access, which means other systems can't talk to the data directly. There are no plugins, no component framework, no model driven apps, and no AI builder. There's also a connector limit because this tier only works with standard connectors, and anything premium needs a paid PowerApps license on top. There's no auditing and no field level security, so you can't track who changed what, or hide a single column from a group. And there's no mobile offline, so the app always needs a connection. Apps embedded in teams also have to load within 30s or teams shows a timeout error, and the whole thing isn't available in the version of the cloud Microsoft runs in China. None of that is a bug. Every one of those cuts is what made the platform free, and simple enough for a beginner to use. The trade off is the whole deal, so you just have to know which side of it you're standing on before you build something your team depends on. The mistake that catches almost everyone. If you only remember one thing from this episode, make it this one. The life of a Dataverse for teams environment is tied to the team it lives in. So if that team gets deleted, the environment and everything in it gets deleted too. Backups exist, but they last up to seven days and you can only restore back into the same environment, which is the mistake that catches first time makers more than any other. That single fact leads to the next mistake it's building. Before you talk to the team owner who controls whether the team lives or dies. If your app becomes business critical while the owner is about to clean house, you have a problem that has nothing to do with your app. Then there's duplication. It's tempting to copy the same app into five different team environments, so each group has its own, but that splits your data into five places and multiplies the maintenance by five. If several teams need the same thing, the smarter move is one app in full Dataverse with shared access. Waiting for the warning is another one. The eighty percent banner is a nudge, not a surprise party, and the people who get caught out are the ones who never check their storage until the day they couldn't create a table. And the last mistake is treating the upgrade as an undo button. Upgrading to full Dataverse is a one way door that keeps your data and unlocks the missing features, but it can't be reversed, and it changes who has to pay for licenses. Every one of these comes back to the same truth, which is that this data layer was always meant to be temporary. The uncomfortable part is how little warning you get. Nobody emails you the day before a team is deleted and the environment disappears right along with it. Which is why the fix is a habit rather than a setting. What Microsoft changed in twenty twenty six. Microsoft has deprecated Dataverse for teams, and the change happens in three phases starting November fifteen, twenty twenty six. You can't create new Dataverse for teams environments, including when you build your first app or agent in a team, or install one from the catalog. Existing environments keep working after that date, but no new ones are born. The second date is September fifteen, twenty twenty seven. That's when environments that haven't been upgraded to Dataverse are suspended and their apps, flows, agents and data stop being available. The third is October thirtieth, twenty twenty seven, when those same environments are decommissioned for good. Microsoft's own reason is straightforward Dataverse for teams only ever offered a subset of Dataverse, so consolidating on the full platform gives makers and admins one place for data. With the full set of capabilities and controls. The direction of travel is one data platform, Not a special one just for teams. What doesn't change is just as important. Your team stays and the channels, the chats, the SharePoint site and the files all stay exactly where they are. The deprecation only touches the Dataverse for teams, environment, and the resources built on it. If you already have data here, the recommended path is to upgrade the environment to full Dataverse before the deadlines. That keeps everything and unlocks the rest of the platform. But two things have to be true. First. Your tenant needs enough Dataverse capacity for the environment, and users need the right power platform licenses afterward. There's also a quieter alternative, which is to export your work as a solution and import it into a Dataverse environment you already run. If you do nothing and you have data here, the outcome isn't neutral. The environment is suspended, then decommissioned, and at that point the apps and the data are simply gone. So the team survives and the data doesn't. For anyone who just built something here, the work isn't wasted. Upgrade the environment and everything you made comes along with it. Still running now sitting on the full platform, which is where it needs to be anyway. For anyone starting fresh today, the honest advice is simple don't begin new work here because Microsoft is pointing everyone toward full Dataverse. So build your app there and then add it to teams. What this means for you. Let me pull it together. Dataverse for teams was a real database tucked inside teams included with the license most organizations already pay for. It was genuinely good at small team apps like Helpdesks, inventory trackers and approvals, and it came with honest limits on storage connectors and features. Now, Microsoft is retiring it in favor of full Dataverse, and the dates are already on the calendar. The bigger lesson isn't about this one product, it's that Microsoft keeps pushing the data layer toward one place, and the tools that live inside teams are expected to grow up into that place or move aside before you build on any free data layer. Find out how long it's meant to live, because the tools that feel permanent are the ones that catch people off guard. That's the habit worth keeping. So my question for you is this does your team have data sitting in a shared spreadsheet or a small teams app right now that would need a plan if it had an end date? If this made the topic feel less intimidating, subscribe to M365 FM to master the tools and the mindset shaping the future of work.