LowCodeStacks™
Sign in

Dataverse for Teams is retiring: upgrade your environments before they're deleted

Dataverse for Teams environments are deprecated — unupgraded ones were suspended on September 15, 2026 and are decommissioned on October 30, 2027. How to find yours, upgrade them to Dataverse, and what the upgrade changes.

DataverseFix a problem4 min read

Checked against Microsoft Learn · 4 sourcesPosted by the Maker DeskHow we write guides

Thousands of teams built approval apps, trackers and bots on Dataverse for Teams because it came free inside Microsoft Teams. Microsoft has now deprecated the whole environment type, and the schedule has a sting: environments that weren't upgraded were already suspended on September 15, 2026 — their apps, flows, agents and data unavailable — and everything still not upgraded is decommissioned on October 30, 2027. Suspension is reversible by upgrading; decommissioning is not.

The timeline

From suspension to the point of no return
  1. Sep 15, 2026 · unupgraded environments suspended
  2. Nov 15, 2026 · no new environments
  3. Oct 30, 2027 · decommissioned for good
DateWhat happens
September 15, 2026Environments not upgraded to Dataverse are suspended. Apps, flows, agents and data stop being available — but the environment can still be upgraded.
November 15, 2026Creating a new Dataverse for Teams environment stops working, including the automatic creation when someone builds their first app in a team.
October 30, 2027Environments still not upgraded are decommissioned. Their apps, flows, agents and data are gone. The team itself — channels, chats, files — is untouched.

Find your Dataverse for Teams environments

  1. In the Power Platform admin center, open Manage > Environments.
  2. Filter the list where Type is Microsoft Teams.
  3. Use Last activity to tell the environments people still rely on from the ones nobody will miss.

Environments you don't need require no action — they simply get decommissioned.

Before you upgrade: capacity and licences

Two prerequisites decide whether the upgrade goes through and whether anyone can use the result:

  • Capacity. Your tenant must have at least as much available Dataverse capacity as the environment's size. Without it, the upgrade is blocked with an error. After the upgrade, the environment counts against tenant capacity.
  • Licences. Dataverse for Teams came with Microsoft 365. A full Dataverse environment doesn't: after the upgrade, people need Power Apps, Power Automate or Copilot Studio licences to use the apps, flows and agents.

Warning

Budget for the licence change before upgrading, not after. An upgraded environment whose users have no premium licences trades "suspended" for "unusable".

Upgrade an environment

  1. In the admin center's environment list, select the Dataverse for Teams environment.
  2. Start the upgrade from the environment's page and confirm the implications dialog.
  3. Watch the notifications as the operation moves through its states.

After the upgrade, everything stays: apps can run inside and outside Teams, makers find and edit their work in Power Apps and Power Automate, team owners hold the System Administrator role, and the environment outlives the team — deleting the team no longer deletes the environment. From there, apply your normal governance: environment groups, data policies, Managed Environments.

The alternative: move the solutions

If an upgrade doesn't fit — capacity is tight, or the work belongs with other solutions anyway — export instead:

  1. In the Dataverse for Teams environment, export the apps, flows and tables as a solution.
  2. Import the solution into an existing Dataverse environment.
  3. Re-point anything that referenced the old environment and retire it.

Note

Build new work in a Dataverse environment and add it to Teams from there — that path keeps working and is where Microsoft is consolidating. Embedding an app in Teams does not require the app to live in a Dataverse for Teams environment.

Sources

Did this fix it?

Comments

No comments yet. Share what worked for you.

Sign in to comment. Comments show under a display name you choose, never your email.