Start free trial
Collaboration Governance

Microsoft Dataverse for Teams: Double the Power

Microsoft Dataverse for Teams: Double the Power

Microsoft Dataverse for Teams is a built-in, low-code data platform that gives a Teams team its own Dataverse environment for tables, Power Apps and Power Automate flows. Microsoft has deprecated it. New environments cannot be created from 15 November 2026, and environments not upgraded to Dataverse are suspended on 15 September 2027 and decommissioned on 30 October 2027.

Rencore Governance gives you one inventory of the apps, flows and owners across your Power Platform environments, including those tied to Teams, so you can decide what to upgrade and what to retire.

Microsoft has deprecated Dataverse for Teams; the timeline is on Microsoft Learn under Deprecation of Microsoft Dataverse for Teams environments. This 2023 post describes the product as it was introduced.

In my last blog, Microsoft Teams as a (Power) Platform, I covered the lowest level of integrating Power Platform tools into Microsoft Teams. Now we are doubling the Power by taking the integration options to the next level!

With Dataverse for Teams, we get the most important Dataverse features included within the context of our Microsoft Teams team without the need for additional licensing. When using Dataverse for Teams we are actually getting a Dataverse environment linked to the Office Group of our Microsoft Teams team.

Within this Dataverse for Teams environment we can create Tables, Power Apps, Power Automate Flows and even Power Virtual Agents. Should you want to know more about the full Dataverse features versus the features of Dataverse for Teams please see Dataverse for Teams vs. Dataverse, Power Apps | Microsoft Docs. Even though there is some flexibility, the main concept is that you get all these Premium Power Platform goodies for all your team members.

The added value

A lot of the Microsoft 365 people starting with Power Platform, first discovered Power Platform tools by customizing SharePoint for their smaller business applications. The two first tools in sight being Power Apps for customizing list and library forms plus Power Automate for adding workflow automation to items in lists and libraries.

From this moment on, you as a Citizen Developer have probably discovered some limitations in using SharePoint, Microsoft Lists, or Microsoft Excel as a database. For example, some limitations on data types, text search, item number thresholds and data query features. For a basic comparison please see Comparing Microsoft Lists, Dataverse for Teams, and Dataverse, Power Apps | Microsoft Docs.

With Dataverse for Teams all Citizen Developers can take their Business Application building skills up a notch. And the best part is: no additional licensing!

Getting started

Because the Dataverse for Teams environment is linked to the Office Group of a Microsoft Teams team, we need to have a Microsoft Teams team created. With an already existing Microsoft Teams team, the first step is to open up the Power Apps App present in your Microsoft Teams Client:

From within the Power Apps App of Microsoft Teams, the Start now button will take you to a wizard guiding you to provision a Dataverse for Teams environment linked to your Microsoft Teams team:

For a step-by-step guide, please see Enable Power Apps and Dataverse for Teams in Microsoft Teams (contains video), Power Apps | Microsoft Docs.

Once you have taken these first steps, you can always return to existing Dataverse for Teams environments by using the Build tab of the Power Apps App in Microsoft Teams:

Tips:

  • When starting out with Dataverse for Teams, I highly recommend to create a testing Team and install one of the sample apps to learn about the possibilities: Use sample apps from teams store, Power Apps | Microsoft Docs.
  • If you are a heavy Microsoft Teams user and still want to use Microsoft Teams for meetings and chats while building, make use of the Microsoft Teams web application or use the new Pop out app feature opening a new window of your locally installed Microsoft Teams client:

If you are more familiar with the Power Apps Portal you can easily open up the Dataverse for Teams environment in a browser by using the Open in Power Apps feature:

Power Platform Governance

Although we rightly champion the successful adoption of Power Platform, IT self-service in general, lives outside of IT governance’s traditional reach and therefore needs special attention. Therefore, a specialized Power Platform governance strategy is required to provide visibility across apps and flows, simplify power user management, and enable IT operations teams to react fast. Without one, company data becomes vulnerable, administration and licensing permissions go unchecked, and monitoring the apps becomes an insurmountable task.

I highly recommend the following whitepaper: Microsoft Power Platform governance best practices. It gives you the fundamentals for governing the Power Platform as part of the wider Microsoft 365 ecosystem.

Free Download

Common questions on this

Is Microsoft Dataverse for Teams being retired, and when?
Yes. Microsoft has deprecated it: new environments cannot be created from 15 November 2026, and environments that are not upgraded to Dataverse are suspended on 15 September 2027 and decommissioned on 30 October 2027. Microsoft's timeline leaves roughly 10 months between the end of new environments and the first suspension, which is enough time to plan if you know what you have and too little if you find out in the summer of 2027.
What happens to apps and flows in an environment that is not upgraded?
The environment is suspended and later decommissioned, and the tables, Power Apps and Power Automate flows inside it go with it. Anything a team still relies on has to be upgraded to Dataverse, moved to another platform or retired on purpose before the dates above. The risky objects are the ones nobody remembers building, because nobody will ask for them until they stop working.
Did Dataverse for Teams need extra licensing?
When it was introduced, the post's point was that a Teams team got the most important Dataverse features without additional licensing. An upgraded Dataverse environment is a different setup, so check the licensing terms of the target environment with Microsoft before you commit. Budget for it as a decision per app: some apps are worth upgrading, some are better rebuilt on a simpler store, and some should simply be retired.
How do we find every Dataverse for Teams environment in our tenant?
Each one is linked to the Microsoft 365 group of a single Teams team and was often created by a citizen developer with the Start now wizard, without IT being asked. Start from the Power Platform admin center, then reconcile it with your Teams list. Rencore Governance gives you one inventory of the apps, flows and owners across your Power Platform environments, including those tied to Teams, so you can decide what to upgrade and what to retire.
Who owns these apps and flows when the maker leaves or the team is archived?
The environment belongs to one team's Microsoft 365 group, so ownership of the apps follows team ownership, and in many tenants that is not actively maintained. Name an owner for every app that survives the migration, and record why it exists. An app with no named owner is a candidate for retirement, not for a paid upgrade.
Do Purview, Entra and the Power Platform admin center already cover this?
They cover real parts of it: data loss prevention policies control which connectors apps may combine, Entra governs the identity a flow runs as, and the admin center shows environments and their settings. They do not decide whether an app is still needed, who answers for it, or which of them to upgrade before 15 September 2027. That decision needs an owner per object and a lifecycle, which is the operating-model part of Power Platform governance.

Last updated 12 November 2026

Related articles

Rencore newsletter

Subscribe to our newsletter

Get the latest insights on governing Microsoft 365, Copilot and AI agents, delivered to your inbox.

Loading form