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
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
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.
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.
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
Exactly my observation as well. This is normally we do, create Microsoft Entra group team rather than the owner team.
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 ?
No that bit is missing from this video
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
Loading is very cool. The spinning icon means everything to me.
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)
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.
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.
I think you missed the whole point of the video - connecting a Security Group to a Team
I hate microsoft