Difference between User (systemuser) vs AAD User (aaduser)

(0) Share

Report

Posted on by ynaing

I am totally confusing between User (systemuser) and AAD User (aaduser).

Please kindly explain me what is different those 2 entities.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Verified answer

v-chengfen-msft on at

Like (0)

Report

Hi @ynaing ,
The main difference between a User (systemuser) and an AAD User (aaduser) is that they belong to different identity systems in the Microsoft ecosystem.

A User (systemuser) is a user record in Dynamics 365, which is a customer relationship management (CRM) platform developed by Microsoft. It represents a person or entity that interacts with the system, such as a sales representative, customer, or vendor. The User (systemuser) entity in Dynamics 365 stores information about the user, such as their name, email address, security role, and other metadata.

An AAD User (aaduser), on the other hand, is a user record in Azure Active Directory (Azure AD), which is Microsoft's cloud-based identity and access management service. Azure AD provides authentication and authorization services for a variety of Microsoft and third-party applications, including Office 365, Dynamics 365, and other cloud services. The AAD User (aaduser) entity in Azure AD stores information about the user, such as their user principal name (UPN), email address, group membership, and other metadata.

While there are some similarities between User (systemuser) and AAD User (aaduser) entities, they are distinct and separate from each other. User (systemuser) entities are specific to Dynamics 365, while AAD User (aaduser) entities are part of the broader Azure AD ecosystem. In some cases, it may be necessary to link or synchronize User (systemuser) records with AAD User (aaduser) records to enable seamless authentication and authorization across multiple systems and applications.

Hope these explanations are useful to you

Best Regards
Cheng Feng

Was this reply helpful? Yes No
ynaing 91 on at

Like (0)

Report

Hi @v-chengfen-msft,

If I have an entity which contain a column called "Resolver".
Resolver column lets the end user choose "People".
Which entity should I make relationship? AAD or Systemuser

Was this reply helpful? Yes No
v-chengfen-msft on at

Like (0)

Report

Hi @ynaing ,
If your entity's "Resolver" column lets the end user choose "People," then the relationship should be made with the AAD User entity rather than the SystemUser entity.

This is because the AAD User entity represents user accounts that are stored in Azure Active Directory, which is the cloud-based identity and access management service used to manage access to Microsoft cloud services and applications. AAD Users are global identities that can be used to access multiple resources and services within Azure.

However, if you only need to restrict the end user to select from a list of users specific to a particular resource or service, then you may consider using the SystemUser entity.

Hope these explanations are useful to you

Best Regards
Cheng Feng

Was this reply helpful? Yes No
ynaing 91 on at

Like (0)

Report

Hi @v-chengfen-msft,
Thaks for your time.

Just one last question.

I have made relationship between AAD User and my custom entity.
But I cannot retrieve any data from AAD User in Power Automate.
Is it limitation or am I facing an issue?

My case is :
When a record is created in custom entity, I want to send email or teams notification to resolver. But I cannot retrieve data from AAD User entity.

My current workaround is:
Retrieve data from User (systemuser) entity by using GUID which comes along with the custom entity record.

Was this reply helpful? Yes No