When a Power App is shared with an AAD group, and that group is also a part of the environment’s security group, the intuitive expectation is that individual members of the AAD group would automatically appear in the environment’s user list.
However, this is often not the case!
Users from the AAD group aren’t instantly created as entries in the Dataverse User entity or the environment’s user list, leading to confusion and concerns about access and permissions.
Picture this: You’ve meticulously crafted a dropdown with the intention of showcasing #Azure AD group users. However, when you initially open the dropdown, it appears empty. The surprise comes when, after a bit of interaction with the application, the users suddenly appear as if they are eagerly awaiting their cue.
It’s a mystery that has left developers both baffled and intrigued. But fear not, we’ve got the recipe to fill that dropdown!
The list of team members listed in each group team only displays the user members who have accessed the environment who have accessed the environment.
When building a Power App that contains a dropdown meant to display users from an AAD group, developers might find the dropdown empty. Why?
- Users from the AAD group are not instantly created as entries in the Dataverse User entity or shown in the environment’s user list.
- Users appear only when they access a resource in the environment, be it the shared app or any other resource within that environment.
- Thus, if the dropdown relies on the environment’s user list or the Dataverse User entity, it remains empty until users access the environment.
Solution to persisting with the user entity:
If the Dataverse Users entity is your preference, and you’re keen on rectifying the empty dropdown dilemma, there’s a remedy: Power Automate.
By establishing a flow, you can enforce a sync between Azure AD users and the Users entity in #Dataverse. However, a word to the wise: This operation requires specific permissions!
If you’re aiming to use the Power Platform for Admin connector within your Power Automate flow, ensure the connector is added to the current Data Loss Prevention (DLP) policy.
If there’s an existing policy in the environment, it needs to be updated to include the Power Platform for Admin connector.
To avoid this problem and if you want to know when to use Users Entity vs AAD Users Entity, contact the team.
If you need any further assistance solving this mystery – or any other power app related one – get in touch with our Senior Business Applications Consultant, David Oliveira. This article is also available here.
