PL-400 Exam Prep: Understanding Security in Microsoft Dataverse

Рет қаралды 7,847

Күн бұрын

In this video, I’ll walk through some of the key security concepts relating to Microsoft Dataverse. We’ll begin by looking at how to create Security Roles, and the features available to them. Next, we’ll discuss Teams and how they relate to Business Units. Finally, we’ll demonstrate how to secure specific columns on Dataverse tables using Column Security Profiles.
This video is part of my series focused on providing small, bite-size learning tools to prepare to sit Microsoft Exam PL-400: Microsoft Power Platform Developer. More details about the exam can be viewed below:
docs.microsoft.com/en-us/lear...
To view the accompanying blog post to this video, use the link below:
wp.me/p7cr4U-1MU
To find out more about the concepts discussed in this video, check out the following Microsoft Docs article:
docs.microsoft.com/en-us/powe...
docs.microsoft.com/en-us/powe...
docs.microsoft.com/en-us/powe...
docs.microsoft.com/en-us/powe...
Have any questions relating to security within Microsoft Dataverse? Let me know in the comments below, or you can reach out to me on Twitter instead:
/ joejgriffin
#PowerPlatform #CommonDataService #MicrosoftDataverse

Пікірлер: 16

@nathan5657 8 ай бұрын

Slight changes have occured for the copy role action, these are the steps to follow at the time of writing: Select the (basic user) role from the "Security Roles" screen and then select More Actions -> Copy Role

@netsena1775 Жыл бұрын

thanks Joe!

@sgeorge1642 2 жыл бұрын

Great video. Thanks very much.

@nice2skate 2 жыл бұрын

Well done

@MrCybergoku 2 жыл бұрын

Thanks !

@belkaaloulwahiba4770 2 жыл бұрын

excellent very useful

@side54723 3 жыл бұрын

Great video. Assuming ive set my entity permission. Where my record are shared with my team. Is it possible, lets say for a record, where a type is "for everyone" (a field created called type), would be shared to everyone. Or same question to share this record to a business unit instead. Thank you

@CRMChap 3 жыл бұрын

Hi Jeff, as far as I know, this would only be possible to do via code - on change of this field, you can then execute a request to share the record with all users in a business unit. Alternatively, you would have to create the table as Organization owned, but this would mean that no owner could ever be assigned to it and you would have to grant full or no access. Here are some articles on these topics: docs.microsoft.com/en-us/powerapps/developer/data-platform/security-sharing-assigning?WT.mc_id=BA-MVP-5003861 docs.microsoft.com/en-us/powerapps/developer/data-platform/webapi/use-web-api-actions?WT.mc_id=BA-MVP-5003861 docs.microsoft.com/en-us/powerapps/maker/data-platform/types-of-entities#standard-tables?WT.mc_id=BA-MVP-5003861 Hope this helps 😀

@side54723 3 жыл бұрын

@@CRMChap thank you ill explore that !

@johnbrennan8442 Жыл бұрын

Great video can I ask how to prevent other members of an environment from seeing your solution / tables please

@CRMChap Жыл бұрын

It's not possible to selectively control which user(s) can see and work with specific solutions, it's an "all or nothing" approach. The only way to implement something like this would be by using separate environments.

@johnbrennan8442 Жыл бұрын

@@CRMChap Thank you for the reply it’s not good that every developer can see each other’s solutions within our specified Dev env and not practical to have every developer have their own dev env

@CRMChap Жыл бұрын

This is actually better this way IMHO, because otherwise, how will developers know whether someone else has modified or altered the same component? 😉 Developers can setup their own personal environment free of charge via the developer plan, and this is the recommended approach to follow: docs.microsoft.com/en-us/powerapps/maker/developer-plan

@johnbrennan8442 Жыл бұрын

@@CRMChap We don’t want our developers having their own Dev Envs as they could bypass our governance easily

@CRMChap Жыл бұрын

Well, regardless, your developers can (if they want to) set up a Developer Plan environment at any time. And you have, as far as I know, no control or visibility over this. So my question would be, why is this such a huge governance concern for you?