Dataverse Environment Permissions for Power Platform

📺 In this 15 minute maker-focused video, Michael shares how to leverage Dataverse environment permissions (aka Dataverse Teams) in order to bulk manage user permissions in Power Platform environments. Dataverse group teams are a way to add security roles to a group, in order to customise permission level. Comprehensive walkthrough to concept and Power Platform Admin Center.
This demo is taken from the Power Platform Monthly Community call 20th of July 2023. Join the next call! Download recurrent invite from aka.ms/community/calls
✨ Presenter
Michael Roth (Avanade) | @michaelroth42
📖 Supporting materials
• Documentation - Microsoft Power Platform security and governance documentation | learn.microsoft.com/power-pla...
• Documentation - Configure user security in an environment | learn.microsoft.com/power-pla...
• Documentation - Associate a business unit with an Azure AD security group | learn.microsoft.com/power-pla...
• Documentation - Security in Microsoft Dataverse | learn.microsoft.com/power-pla...
• Documentation - Security concepts in Microsoft Dataverse | learn.microsoft.com/power-pla...
💡 Learn more about the Microsoft 365 & Power Platform community
• Microsoft 365 & Power Platform Unified Sample gallery - aka.ms/community/samples
• Microsoft 365 & Power Platform Community in RUclips - aka.ms/community/videos
• Microsoft 365 & Power Platform - aka.ms/community/home
Sharing is caring! You are awesome! 🧡

[@murkyriver]

I think you missed showing how you link Azure AD security group to a Dataverse Team. Instead of selecting "Owner" in the Team type, you should have selected "Azure AD group team".. otherwise quite a nice video to get the concept going

[@jayapandurangaraobs6839]

Can you help me know at which time stamp , have we shown how to hook up the AD group with the Team in this demo ?

[@inesaoues5464]

I have a table 'users' on dataverse with an 'access rights' column how I can use this column to limit access on power pages (power portals)

[@johnfromireland7551]

Loading is very cool. The spinning icon means everything to me.

[@anthonyleduc]

Well presented. Easy to understand but i think you forgot one thing and sometimes it's confusing.
When you share an app to a AAD security group, it creates a new team but the owner is a service principle #PowerAppsDataBackend.
So you can have two teams - 1 is created with the owner and an other that is created by the SPN.

[@eladdieyo84]

There is a lot missing here. Redo this with a bit more detail please. Some of the things you may want to address. How to set up the naming conventions of the different groups so admits can easily navigate.
What is an admin
What is a maker
What is a read only user
What are least priv access roles and how can they be managed here.
How to add a user
How to delete a user.
Can we do security audits on a quarterly or monthly basis...
Just to name a few... we are all in this together

[@mccardj41]

I think you missed the whole point of the video - connecting a Security Group to a Team

[@AdamHaas]

I fail to understand why Microsoft invented Dataverse Teams when Security Groups already exist. What is the point of putting a Security Group in a Dataverse Team? Why didn't they just allow you to assign a Security Group instead of adding an additional layer only to have it undermined by making the sole member of that Dataverse Teams, a Security Group! If anything I would think this video shows how pointless it was of them to do so. This feels like a workaround for a nonsense feature.