Dataverse for Teams environment needed for Stakeholder

(2) Share

Report

Posted on by Karintie

Hi,

I cannot seem to get a simple Analytics Viewer setting to work for a M365 user, without adding a Dataverse for Teams environment (Select a team).

The user does not have to build anything, he just needs to check an agent in a totally different environment.

When we delete the Dataverse for Teams environment (as not being used), the analytics viewer again gets the Select a team view and creates yet another Dataverse for Teams environment with the same name.

How can we avoid this behavior?

Categories:

Bot analytics

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Suggested answer

sannavajjala87 515 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi,

What you're seeing is expected behavior in many cases. The Analytics Viewer experience relies on the user having a Microsoft Dataverse-backed environment available. If the user doesn't already have one (such as a Personal Developer environment or a Dataverse for Teams environment), the platform may prompt them to select a Team and automatically provision a Dataverse for Teams environment.

If you delete that environment, the dependency still exists, so the next time the user accesses Analytics Viewer, the platform attempts to create it again.

A few questions that may help narrow this down:

Is the user only assigned the Analytics Viewer security role in the target environment?

Does the user already have access to a regular Dataverse environment (Developer, Sandbox, or Production), or is the Dataverse for Teams environment their only Dataverse-backed environment?

Is this occurring in Copilot Studio analytics or another Power Platform analytics experience?

For enterprise scenarios, my recommendation is to avoid relying on auto-created Dataverse for Teams environments. Instead, provide users access to a managed Dataverse environment (where appropriate) with the minimum required security role. This typically results in a more predictable administration experience and avoids unnecessary creation of Dataverse for Teams environments.

I'm interested to know whether others have seen the same behavior recently, as it appears to be tied to how the analytics experience initializes for first-time users.

Was this reply helpful? Yes No
Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!
This happens because Copilot Studio still requires a valid environment context, even for Analytics Viewer access.

If the user has never used Copilot Studio before, the system may prompt “Select a team” and automatically create a Dataverse for Teams

environment. Deleting it doesn’t stop the behavior, because it gets recreated when the user accesses Copilot Studio again.

Key points:

Analytics Viewer role alone is not enough to avoid Dataverse for Teams provisioning.

The system still needs an environment for the user to operate in.

If the user enters via Teams or a Teams-based entry point, Dataverse for Teams is triggered.

Recommended fix:

Add the user directly to the environment where the agent exists.

Assign Analytics Viewer permissions there.

Ensure the user accesses Copilot Studio directly in that environment (not via Teams entry flow).

You cannot fully avoid Dataverse for Teams creation if the user is routed through the Teams-first experience.

The workaround is to ensure users access analytics directly from the target environment with proper permissions.

Was this reply helpful? Yes No
Suggested answer

Valantis 6,735 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Karintie,

The auto-creation happens because the user is entering Copilot Studio through the Teams-first flow, which always provisions a Dataverse for Teams environment when the user has no other default environment context. Deleting it doesn't help because the next entry recreates it.

The fix is to change how the user lands in Copilot Studio so they never hit the Select a team prompt:
1. Have the user go directly to https://copilotstudio.microsoft.com in a browser, not through the Teams app or any Teams-based entry point. The Teams entry point is what triggers the Dataverse for Teams provisioning.

2. Once in the web app, they use the environment switcher (top right) to select the target environment where the agent lives.

3. In that target environment, make sure the user has the right access. For analytics-only viewing they need a security role with read access to the agent and its analytics. Assign that role in the target environment directly (PPAC > target environment > Users > assign role).

Key point: the Analytics Viewer permission alone doesn't prevent the Dataverse for Teams creation. It's the entry path that matters. As long as the user enters via the web app and has a real environment selected, they won't get the Select a team prompt and no Dataverse for Teams environment gets created.

If the user genuinely has no default environment assigned at all, the platform falls back to the Teams provisioning. Giving them a security role in a real Dataverse environment (the target one) gives them a valid environment context and stops the fallback.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Suggested answer

Haque 3,653 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Karintie,

Probably this happening due to how Power Platform and Microsoft 365 handle user-level analytics and permissions.

Instead of letting the system auto-create a Dataverse for Teams environment on-demand, can you please proactively create and assign a Dataverse environment for the user? This can be a dedicated environment (not necessarily tied to a team) where the user has the Analytics Viewer role assigned. This will avoid “Select a team” prompt.

Also, ff your organization has existing Dataverse environments, assign the user the Analytics Viewer role in one of those environments. This will give the option to access analytics scoped to that environment without needing to create a new Dataverse for Teams environment.

Finally, lets ensure the user has the necessary Power Platform licenses and environment permissions to access analytics without triggering environment creation.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Karintie 19 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi all,

Thank you for your answers!

I already had added the user to the environment where the agent belongs to, as else the Agent Viewer role is not assigned.

I had given the complete url, so the right environment was in there.

Is there some hidden license needed for these stakeholder analytics? This M365 user just needs to check, not work in Copilot Studio. I cannot find license information on these specific type of actions.

Kind regards,

Karin

Was this reply helpful? Yes No