Dataverse for Teams is going away: what to keep, move or let go before September 2027

Microsoft is retiring Dataverse for TeamsdefinitionThe small database Teams sets up for a team the first time someone there builds an app or agent. You get one per team, and it stops at 2 GB., the little database behind apps, flows and agents that people built inside Microsoft Teams. Find every one of those environments now, decide which ones the business still needs, and upgrade or move those before 15 September 2027, when the rest stop working. Upgrading is a few clicks, but the licences and storage it pulls in are a budget line someone has to approve.

These apps rarely show up on anyone's systems list. A team built a leave tracker, a site inspection form or an FAQ bot years ago, and people use it every week without knowing where the data lives. When the environment is suspended, the app simply stops opening. The data goes with it. Microsoft's notice says that after decommissioning the apps, flows, agents and data are no longer available.

The other cost is money. After an upgrade, everyone who uses those apps, flows and agents needs a Power Apps, Power Automate or Copilot Studio licence, and the environment's storage moves into your tenant's paid Dataverse capacitydefinitionHow much Dataverse storage your tenant has paid for, counted separately for database, file and log. Upgraded Teams environments start eating into it.. For a team of fifteen that might be a rounding error. For an app the whole company opens to book leave, it's a real budget line, and someone in finance will want to see it before September.

Microsoft's upgrade deadline is 30 October, but users lose the apps on 15 September. Plan as if September is the real date. A failed upgrade in the last week of September leaves you explaining to a department why their app has been dark for a fortnight.

Microsoft's reason is consolidation. Dataverse for Teams was always a subset, and running two data platforms with different rules for storage, security and lifecycle is work for everyone. Apps built in a normal Dataverse environment can still be added to Teams, so users who only ever see the app as a tab in a channel may not notice anything changed, provided it's licensed and moved in time.

Plenty stays exactly as it is. Nobody touches the team, its channels, chats, files or SharePoint site. Apps, flows and agents someone already built in a full Dataverse environment and added to Teams aren't affected either. If that's all your inventory turns up, you're done.

Every Teams environment gets one of four answers. Most tenants end up using all four, because a busy approval app and a test someone abandoned in 2022 deserve different treatment.

Microsoft's public price list puts Power Apps Premium at $20 per user per month, paid yearly, or $12 with a 2,000-seat minimum, and extra Dataverse database capacity at $40 per GB per month. Each Premium licence comes with Dataverse entitlements of 250 MB database and 2 GB file. Your agreement may differ, so treat those as the starting point for the conversation with your licensing partner, then count the actual users of each app before you multiply anything.

Start in the Power Platform admin center. Under Manage, then Environments, filter the list where Type is Microsoft Teams. The Last activity column is updated daily and counts real use: someone opening an app, a flow running, a chat with an agent. A scheduled flow counts as activity on its own, so an environment can look alive while no human has touched it in a year.

Then ask the team owners. They get the inactivity warning emails and the System Administrator role in their environment, and they usually know which app matters. Members and guests don't get those emails. When the owners have left, the warnings go to tenant admins, who often have no idea what the app is.

# example: Windows PowerShell 5.x, admin module
Install-Module -Name `
  Microsoft.PowerApps.Administration.PowerShell `
  -Scope CurrentUser
Add-PowerAppsAccount
# count apps per environment
Get-AdminPowerApp |
  Select -ExpandProperty EnvironmentName |
  Group | Sort Count -Descending
# every flow in the tenant, for the owner list
Get-AdminFlow |
  Export-Csv -Path '.\FlowExport.csv'
# example output
Count Name
    7 6f2c1e0a-...
    1 a91d44b3-...

The admin module only runs on Windows PowerShell 5.x, not PowerShell 7. Match the environment IDs it returns against the Teams-type environments you filtered in the admin center, and you'll have a list with app and flow counts per team.

We do the inventory first, then sit with team owners and sort the apps people use from the ones nobody opens. Finance gets a licence and capacity figure per app. Then we upgrade or move environments in batches, test each app and flow, and hand you the owner list. See our Power Platform work, the engineers we place on Power Platform projects, or start with a free assessment.