Dataverse for Teams is going away: 15 November 2026, 15 September 2027, 30 October 2027
If someone in your tenant ever built an app, flow or agent from inside a Teams team, there is probably a Dataverse for Teams environment behind it that nobody in IT created on purpose. Microsoft is deprecating them. Creation ends this Sunday. Nothing breaks for existing ones until September 2027, and the apps, flows, agents and data are gone on 30 October 2027 unless the environment was upgraded to full Dataverse first. The upgrade has two prerequisites that cost money: spare Dataverse capacity and licences.
The three dates
| Date | What happens |
|---|---|
| 15 November 2026 | Creation ends. Nobody can create a Dataverse for Teams environment from Teams any more, including by building a first app or agent in a team or installing an app from the Teams app catalog. Existing environments keep working. |
| 15 September 2027 | Environments that have not been upgraded to Dataverse are suspended. Their apps, flows, agents and data are no longer available. |
| 30 October 2027 | Environments that have not been upgraded are decommissioned. Apps, flows, agents and data are no longer available. |
Learn is explicit about what is not touched: the teams, channels, chats, SharePoint sites and files stay. Decommissioning applies only to the Dataverse for Teams environment and what lives in it. Apps, flows and agents built in a regular Dataverse environment and added to Teams are also unaffected.
What an upgrade needs
Learn gives the supported path as upgrading the environment to a full Dataverse environment, done by a tenant admin such as a Power Platform admin in the admin center. Two prerequisites decide whether that is cheap or not:
- Capacity. The tenant must have at least as much available Dataverse capacity as the size of the environment being upgraded. Dataverse for Teams has its own pool that does not count toward your tenant capacity, and each environment is limited to 2 GB. After the upgrade, the environment's consumption counts toward your tenant's Dataverse capacity. If there is not enough, the upgrade is blocked with an error.
- Licences. After the upgrade, users need Power Apps, Power Automate or Copilot Studio licences to use the apps, flows and agents in the environment. The rights that came with the Microsoft 365 subscription for Teams-only use end at that point.
That second point is the licensing hook. A team that built a small approvals app on a free, Teams-bound environment becomes, after the upgrade, a set of users who each need a licence to keep using it. The question per environment is whether the app is worth that.
What Learn tells admins to do
- In the Power Platform admin center go to Manage, Environments, and filter where Type is Microsoft Teams. Use the Last activity column to see which environments are still in use.
- For each one you still need, check available Dataverse capacity against the environment size, and check that its users will have the licences they need after the upgrade.
- Upgrade it before 30 October 2027. For agents built with Copilot Studio there is a separate Learn page on upgrading a Dataverse for Teams environment.
- Tell the team owners. After the upgrade, makers find and edit their apps and flows in Power Apps and Power Automate, not inside Teams. The upgraded environment is no longer tied to the team's lifecycle, so deleting the team does not delete it, and team owners get the System Administrator role.
- Do nothing for the environments you do not need.
To see how much of the 2 GB each environment uses, Learn points to Licensing, Capacity add-ons, and the Microsoft Teams tab in the admin center.
Dataflows stop sooner
One piece has an earlier date. The preview Power Platform dataflows integration with Dataverse for Teams is retiring in phases: new dataflows were disabled on 1 September 2026, refresh of existing dataflows stops on 1 December 2026, and the entry points in Teams and Power Apps Maker are removed on 1 January 2027 or shortly after. Existing dataflows are not deleted, but they stop refreshing. If a team relies on a dataflow into a Teams environment, that is the first thing to find.
Connecting it to the premium-seat count
This is a sixth date next to those in our article on the Power Platform licensing calendar and a sibling of the developer environment deadlines: another free, hidden place where people built things is closing, and the replacement needs licences. Before you assign new premium seats to cover upgraded Teams apps, check the seats already assigned to people who never open an app.
Free: premium seats assigned to nobody, and disabled accounts that still hold one
PowerScout Lite is a read-only PowerShell audit of Power Platform premium licences. It does not inventory Dataverse for Teams environments, their size or their last activity. The admin center filter above does that. It finds the seats you could reuse before you buy more.
Download PowerScout Lite — free See what Solo addsDisclosure: PowerScout is our product. PowerScout is independent and not affiliated with or endorsed by Microsoft. Dates and rules are quoted from the Microsoft Learn pages listed below as read on 10 November 2026; check them again before you act, because Microsoft changes these pages.
Sources
- Important changes coming — deprecation of Microsoft Dataverse for Teams environments — the three dates, what is not affected, admin actions, FAQ
- About the Microsoft Dataverse for Teams environment — upgrade process — capacity prerequisite, post-upgrade licensing, 2 GB limit, capacity view
- Power Platform dataflows in Microsoft Teams (deprecated) — 1 September 2026, 1 December 2026, 1 January 2027