Applies to Product- Power Automate
What’s happening?
Customers are experiencing issues with the activation of the Common DataService for Teams license, specifically regarding the control of app visibility and the use of Dataverse within Teams.
Reason:
The activation of the Common DataService for Teams license does not automatically create a Dataverse environment in Teams. Instead, a Dataverse for Teams environment is created when a user first creates an app or bot within the Teams environment. Additionally, users without the Common DataService for Teams license can still enable Power Apps and Workflows apps in Teams.
Resolution:
- To control the visibility of specific apps within Teams, utilize the "App Permission Policies" to restrict access to designated applications. For detailed steps, refer to the following documentation: Using app permission policies to control user access to apps.
- If there is a need to prevent the creation of a Dataverse for Teams environment, note that it is automatically created when a user first creates an app or bot. Therefore, controlling the use of the Power Apps and Microsoft Copilot Studio (Power Virtual Agents) apps through the Teams "App Permission Policies" is recommended.
- For controlling operations on tables (such as creation and editing) within an existing Dataverse for Teams environment, refer to the following documentation: Granting table permissions for Dataverse for Microsoft Teams.