The short version: A Dataverse for Teams environment caps out at 2 GB of combined storage and about 1 million rows, as at 22 September 2026. Past that, existing apps keep running but nothing new can be built until a tenant admin upgrades the environment to full Dataverse, a one-way move that requires standalone Power Apps or Power Automate licences and can never be reversed.
2 GB, about 1 million rows, no way back
| Setting | Value | What happens at the limit |
|---|---|---|
| Storage per environment | 2 GB, database and file combined | Portion reserved for system use |
| Approximate row capacity | ~1 million rows | Depends on row size and attachments |
| At 80% of capacity | Warning shown to users | Encouraged to reduce usage or contact admin |
| At 100% of capacity | Existing apps, agents, flows keep running | New apps, agents, flows and tables blocked |
| Upgrade to Dataverse | One-way, tenant admin only | Can never be converted back |
Dataverse for Teams gives every Microsoft Team a free environment with 2 GB of combined database and file storage, enough for roughly 1 million rows depending on how wide each row is. At 100% of that 2 GB limit, existing apps, agents and flows keep working, but no new app, agent, flow or table can be created or installed in that environment, as at 22 September 2026. The storage doesn't count against your tenant's main Dataverse capacity at all; it's a separate pool, capped per environment and un-extendable within Dataverse for Teams itself.
What actually triggers an upgrade
Two things force the move to full Dataverse: hitting the 2 GB ceiling, or needing a capability Dataverse for Teams simply doesn't have, such as direct API access, plug-ins, model-driven apps, or any standalone Power Apps or Power Automate usage outside of Teams. A tenant admin runs the upgrade from the Power Platform admin center, and the tenant needs at least as much available Dataverse capacity as the environment being upgraded before it will proceed; if it doesn't, the upgrade is blocked with an error rather than partially applied. Once confirmed, the consumed capacity of that environment starts counting against the tenant's normal Dataverse pool from that point on. If the tenant's included capacity is already spoken for elsewhere, extra database capacity is a NZ$64.70 per GB a month add-on, the same rate covered in full in Dataverse pricing for a small NZ business.
What changes, and why it's one-way
The upgrade is deliberately irreversible: a Dataverse for Teams environment can never be converted back once it's been upgraded. Practically, four things change. The environment's lifecycle stops being tied to the Team; deleting the Team no longer deletes the data. Every user needs a standalone Power Apps or Power Automate licence to keep using it, since the free Teams-bundled access ends at the upgrade. The Microsoft 365 Group association, previously fixed, becomes editable. And the apps can now run both inside and outside Microsoft Teams, through make.powerapps.com like any other environment. Team owners keep System Administrator rights on the upgraded environment automatically, so nobody loses access at the point of the switch, but the governance model around it changes for good.
Common questions
What happens when a Dataverse for Teams environment hits its 2 GB limit?
At 80% of the 2 GB, users see a warning that capacity is running out. At 100%, existing apps, agents and flows keep working and can still be updated, but no new app, agent, flow or table can be created or installed in that environment until a tenant admin upgrades it or usage is reduced.
Can you undo an upgrade from Dataverse for Teams to Dataverse?
No. The upgrade is one-way. Once it's complete, the environment has full Dataverse capabilities and can never be converted back to a Dataverse for Teams environment; its lifecycle also stops being tied to the Microsoft Team it was created in, so deleting that Team no longer deletes the environment.
What licence do I need after upgrading Dataverse for Teams to Dataverse?
Every user accessing the upgraded environment needs a standalone Power Apps or Power Automate licence, per-app, per-user or an equivalent entitlement; the free ride that came bundled with Dataverse for Teams stops at the point of upgrade. The upgrade itself also requires the tenant to have at least as much available Dataverse capacity as the environment being upgraded.
Team app running out of room?
Free 30-minute call. Tell me how close it is to the 2 GB mark and I'll tell you what an upgrade actually costs and changes for your team.