In current weeks, I had to try this similar for a further consumer, however whereas going by the logic of implementing this, I notices some modifications.

After the creation of the Person account and the registration of the App in AD, after I went to create the account in my Dataverse surroundings. The username, full title (first and final names) and the e-mail addresses had been locked. The one setting that I used to be in a position to enter was the Consumer Id.

I even tried utilizing God Mode in order that I can enter my very own Person Title (for the AD account) that I specified, however after I saved the brand new Utility Person, the Person Title would retailer no matter title was entered within the App Registration report.

This transformation was carried out a couple of months again, as Microsoft was attempting to simplify the creation of App Customers, in order that the consumer might be created solely be getting into the Consumer Id. After the consumer account has been created we’re in a position to modify the e-mail deal with, first and final title, however the title (area title) and the final title can’t be modified. The final title appears to be configured to what’s saved in AAD because the App Registration title. May must mess around with this a little bit, however when you’ve got entry to AAD, you need to created this in the appropriate means

I requested round a little bit bit, and it looks as if a couple of days in the past there was a change in Microsoft Docs on how functions consumer ought to be created. The hyperlink is offered under:

The brand new modifications are that now Utility Customers might be created proper for the Energy Platform Admin Heart. As a prerequisite we now have to register the App in Azure Energetic Listing, however as soon as the app is registered, we will add in straight by following the steps under.

Navigate to Energy Platform Admin Heart, choose the surroundings, click on settings, and beneath Customers + permissions choose Purposes Customers as proven within the picture under

Dataverse - PPAC - User and Permissions - App Users

Within the Utility Customers settings you will notice a listing of all of the App Customers which are at present configured in your dataverse surroundings. Click on on the Command bar New app consumer button as proven under:

Dataverse - PPAC - Environments - Settings - New App User

It will pop up a panel the place you can begin creating the brand new App Person account. Underneath neither the App label, click on on the App an app hyperlink:

Dataverse - PPAC - New App User - Add an existing App

It will pop up a further panel which is able to present the entire apps which are registered in Azure Energetic Listing. Choose the Microsoft Dynamics CRM (Dataverse) app registration that you simply beforehand configured, and click on on the Add button

Dataverse - PPAC - Select app from Azure Active Directory

As soon as the app registration is added, we might want to choose the Enterprise Unit and so as to add the safety roles. Click on on the pencil icon subsequent to Safety position, which is able to pop up a further panel exhibiting the listing of accessible safety roles. Choose a number of roles that should be assigned to this consumer, as proven under:

Dataverse - PPAC - Add App User - Select Security Roles

The ultimate web page is proven under. Click on on the create button to create the app consumer in your Dataverse occasion, and it may be used after that.
Dataverse - PPAC - Create App User - Create

It is a nice step transferring ahead, however I nonetheless want the Person account particulars may very well be set on the creation of the App Person to an precise AAD consumer.


Please enter your comment!
Please enter your name here