New table in Dataverse - AADUser

[NHelgren]

Hey everyone, you may have noticed a new table is available in Dataverse: "AAD User" This is a virtual table that is included in all versions of Dataverse. It connects to the AAD for the tenant the Dataverse organization is created in. You can use it to easily find people in AAD and retrieve additional details about them as well like location, job position, email and more. 

I have recently put out a new video that provides an overview and an example of use. You can find it on the Dataverse YouTube channel about this: https://www.youtube.com/watch?v=GHlecOwrx0A

[JulienF]

Hello @NHelgren , 

any recent update to that matter?

[Eddkenny]

Any news on a timeline for custom attributes or extension attributes from AAD or AD Connect to on-prem?

Cheers,

Ed

[NHelgren]

Hi @Eddkenny 

There is no plan for custom attribute support, we do not have a timeline for supporting other existing AAD attributes yet but that feature will be in review shortly to see if it can be accomplished in the near future. 

There is currently no plans for an on premise update to include this feature.

[KC]

Hi,

Which Security Role needs to be given to another user in order for them to see the AADUser records?

I have given them Basic User & Dataverse Search Role but they still cannot view the data.

[NHelgren]

Out of the box, neither of those includes read access to AAD user. I believe the lowest default level is System Customizer. Or you can modify the roles to allow read to AAD. I will add this to the documentation.

[Hairy_Drumroll]

How do I need to modify the roles? What change do I need to make?

I have a user who is set as System Customizer but is unable to search the AAD records with an error saying 0x80040265 Business Process Error.

[SallyO]

Also you cannot filter by this field in Model driven apps.  It crashes.

[Rajeshree]

Anyone know how to resolve this? I have a lookup column which looks in AADUSER (now called Microsoft Entra ID). My regular users are able to search in power app main form. But guest users are not able to search in lookup field. it shows 0x80040265 Business Process Error. 

@Hairy_Drumroll did you get any solution? 

[classen]

We have the same issue with this lookup field. For some it works and for others it dont. If we open a guest browser profile in Edge (the browser where the field doesnt work on the personal profile) we have been able, to make it work. But we cant seem to find a pattern in where it goes wrong. Some dont get the error and others do, and it is not dependent on the browser either. Has anyone found a solution? 

[TheWebNurse]

I had this issue 2 times:

- 1ste time it solved the issue for me when i logged out, closed the browser, logged in as a different user, created a new record with the lookup column, logged back out and back in with my user. 2de time, this didn't work anymore.

- 2de time the solution was to clear browser history.

I'm curious to see what will be the solution next time it happens 🤦‍🤦‍