Feature
Microsoft
Microsoft is deprecating Dataverse for Teams environments: new ones can no longer be created, and existing environments not upgraded to full Dataverse are eventually decommissioned
departs 15 Nov 2026
Quick answers
- Is it true that Microsoft Dataverse for Teams environments are being deprecated?
- Yes. Microsoft has officially announced it, effective 15 Nov 2026. If you build Power Apps, Power Automate flows, or Copilot Studio agents in a Microsoft Dataverse for Teams environment, that environment type is being retired in phases.
- When does it take effect?
- 15 Nov 2026. Verified against the vendor's own announcement.
- What should I use instead?
- Microsoft's recommended path is to upgrade each Dataverse for Teams environment you still need to a full Dataverse environment before 30 October 2027 — the upgrade keeps the environment's apps, flows, agents, and data and unlocks the full Dataverse capability set.
What this means for you
If you build Power Apps, Power Automate flows, or Copilot Studio agents in a Microsoft Dataverse for Teams environment, that environment type is being retired in phases. Per Microsoft's official Power Platform "important changes" page, you can no longer create new Dataverse for Teams environments starting 15 November 2026 — this includes the environment Teams auto-creates the first time you build an app or agent in a team, or install a Dataverse for Teams app from the Teams app catalog. Existing environments that are not upgraded to full Dataverse are suspended (apps, flows, agents, and data no longer available) and later decommissioned on 30 October 2027. Dataverse for Teams was the free, lightweight tier — 2 GB per environment, no direct API access, no custom connectors, desktop flows, or AI Builder — so the people affected are makers and small teams who used it to ship low-code apps inside Teams without a paid Power Platform license. The team, its channels, chats, SharePoint sites, and files are not affected; only the Dataverse for Teams environment and its resources go away.
Where to go
Microsoft's recommended path is to upgrade each Dataverse for Teams environment you still need to a full Dataverse environment before 30 October 2027 — the upgrade keeps the environment's apps, flows, agents, and data and unlocks the full Dataverse capability set. An admin does this from the Power Platform admin center (Manage > Environments, filter Type = Microsoft Teams). Two prerequisites: your tenant needs at least as much available Dataverse capacity as the environment's size, and users need Power Apps, Power Automate, or Copilot Studio licenses afterward (the free tier's licensing no longer applies). Alternatively, export your apps, flows, and tables as a solution and import them into an existing Dataverse environment. Apps, flows, and agents built in Dataverse can still be embedded in Microsoft Teams. Environments you no longer need require no action — they are decommissioned on 30 October 2027.
- Upgrade the Dataverse for Teams environment to a full Dataverse environment (Microsoft's recommended path; requires Dataverse capacity and premium Power Platform licenses)
- Export apps, flows, and tables as a solution and import them into an existing Dataverse environment
Microsoft is retiring the free, lightweight Dataverse for Teams environment type in Power Platform. Per Microsoft’s official Important changes coming in Power Platform page, the change happens in three published phases.
What is changing, and when
Microsoft’s timeline table lists these phases exactly:
- Creation ends — 15 November 2026. You can’t create new Dataverse for Teams environments from Microsoft Teams, including the environment Teams auto-creates when you build your first app or agent in a team, or install a Dataverse for Teams app from the Teams app catalog.
- Environments suspended — 15 September 2026. Dataverse for Teams environments that aren’t upgraded to Dataverse are suspended; their apps, flows, agents, and data are no longer available.
- Environments decommissioned — 30 October 2027. Un-upgraded environments are decommissioned and their apps, flows, agents, and data are permanently gone.
Microsoft publishes the suspension date (15 September 2026) as earlier than the creation-end date (15 November 2026). We record the dates exactly as stated and have not re-ordered or inferred them; check the source page for the authoritative current timeline.
Who this affects
Dataverse for Teams was the no-cost, in-Teams tier of Power Platform: each environment capped at 2 GB of storage, with no direct API access and no support for custom connectors, desktop flows, or AI Builder. It let makers and small teams ship low-code apps, flows, and agents inside Teams without a paid Power Platform license. Those are the users who need to act — anyone relying on a Dataverse for Teams environment to run or build something will lose it unless the environment is upgraded.
What is not affected: the team itself and its channels, chats, SharePoint sites, and files; production, sandbox, trial, and default environments; and anything already built in a full Dataverse environment and embedded in Teams.
What to do
Microsoft’s recommended path is to upgrade each Dataverse for Teams environment you still need to a full Dataverse environment before 30 October 2027. The upgrade preserves the environment’s apps, flows, agents, and data and unlocks the complete Dataverse feature set, but it has two prerequisites: your tenant must have at least as much available Dataverse capacity as the environment’s size (that consumption then counts against your tenant capacity), and users need Power Apps, Power Automate, or Copilot Studio licenses afterward — the free tier’s licensing no longer covers it. An admin runs the upgrade from the Power Platform admin center under Manage > Environments, filtering where Type is Microsoft Teams.
If you’d rather not upgrade in place, you can export your apps, flows, and tables as a solution and import them into an existing Dataverse environment. Environments you no longer need require no action — they’re decommissioned on 30 October 2027.
Source: Microsoft Learn — Important changes coming in Power Platform.
Entry changelog
- — last reviewed.
- — Entry created from Microsoft's official "Important changes coming in Power Platform" page on Microsoft Learn. The three published phases are quoted exactly: creation ends 15 November 2026, environments not upgraded are suspended 15 September 2026, and decommissioned 30 October 2027. (Microsoft lists the suspension date as 15 September 2026, earlier than the creation-end date of 15 November 2026; the dates are recorded here exactly as published and not re-ordered or inferred.) sunsetDate set to the imminent, upcoming milestone — 15 November 2026, when creation ends — with the 30 October 2027 decommission (the final data-loss date) stated in full in the impact and migration notes. No detect: fingerprint — a Dataverse for Teams environment is a Power Platform environment type, not something a repository scan can match.
Put this countdown in your README
Building on Microsoft? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/microsoft-dataverse-for-teams-deprecation)Spot an error or a changed date? Tell us and it’s corrected the same night.