A couple of months ago, I wrote a post about changes on the creation of Application Users and the ability to manage this via the Power Platform Admin Center. Not much time has passed, and a few additions have been added to the Admin Center, which allows to manage Users, Teams and Security Roles. We are still missing some functionality to reach parity with the classic interface, but we are on our way.
In late 2019, I wrote a blog article on how to configure oAuth authentication for Dataverse by creating an App Registration record in Azure, and the configuring the App Registration/User account in your Dataverse environment so that it can be consumed as an Application User or Service Principal.
In a recent implementation I was working on a Canvas app that was supposed to display records to the users in a Nested Gallery. The users that would be accessing the gallery would always have permission to see the parent gallery, but not everyone had permissions to view the child gallery.
I have encountered many engagements in which the client needed to migrate data from other systems which had users that were not longer within the organization, and those users did not require access to Dynamics 365, but the client wanted to keep track of who the original owners or users that created the records were.
Many times we are asked by our customers to disable Bulk Edit to certain users or groups of users/teams within the system. That requirement is pretty straight forward and can easily be understood. The resolution to this of course is also easy, and can easily be accomplished by changed the Bulk Edit privilege for a particular security role. What happens though when the requirement is to disable bulk edit from a user only on a particular entity. This becomes a little more complicated.
