Unanswered

Dataverse for Teams - User table automatically populated with ALL Tenant App Makers when "Share with your colleagues" is enabled

(0) Share

Report

Posted on by robby_freeze

I encountered a very strange issue in our Dataverse for Teams environments that are being shared with Colleagues through an Azure AD Group.

As per the following documentation, users are added to the Dataverse for Teams User table once they start accessing resources.
https://learn.microsoft.com/en-us/power-platform/admin/about-teams-environment

I am experiencing now the following scenario:

Dataverse for Teams environments that haven't been shared with "Colleagues" work as expected.

The Dataverse for Teams environments that HAVE been shared with "Colleagues" are adding now randomly users to the User table that are neither in the AD Security Group, nor in the Teams itself.

The users are the same ones in all shared environments and they´re being updated on a daily basis.

It seems that these users that are being added are all App Makers from the tenant.

It is making the apps we´ve built unfunctional that rely on (non-Application) users table as picklists are now populated with all imported users.

This behaviour started on 5 November 2022 on our tenant.

"Modified by" is blank for these records and they seem to be updated daily (each environment at a different time, but with the same users).

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Community Power Pla... on at

Like (0)

Report

Hi @robby_freeze,
I may have misunderstood your post, but I think that the Users table contains all the Azure AD users that are registered in the environment by design. Maybe users are accessing another PowerApp from Teams, and because they have a valid license they're automatically added as Dataverse users in the Teams environment?

Anyway, if you want a subset of users in a picklist, maybe you could try and create a new Users View with a filter on group membership and use it throughout the app.

Let me know if I missed something or this helped you!

Kind regards,
Davide
If my previous post solved your question, please consider clicking on "Accept as solution" to help the other members find it more quickly. Thanks! 🙂

Was this reply helpful? Yes No
robby_freeze 19 on at

Like (0)

Report

Hi Davide,

thank you for your quick reply.

In a full Dataverse instance, this is correct. All AAD Users are being created in the Users table as long as the environment doesn´t have an Environment Security Group.

In Teams, it´s the M365 Group + the AD Group used for "Shared with Colleagues".
Also, in Dataverse for Teams Users are not automatically mapped, but they´re being created the first time a user from the AD Group / M365 Group is accessing the resource.

However, this behaviour seems broken. I´m getting a subgroup (likely Power Platform Makers and Users) mapped into the Dataverse for Teams User table (but only when SHaring with colleagues is enabled)

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Uh, okay @robby_freeze!

I thought Dataverse for Teams was behaving the same way as "plain" Dataverse, but apparently, I was wrong. 😁 Still, maybe the filtered view could work anyway, no? Other than that, I have no idea how to followup, so I hope someone else will do! 🙂

Best,
Davide
If my previous post solved your question, please consider clicking on "Accept as solution" to help the other members find it more quickly. Thanks! 🙂

Was this reply helpful? Yes No