Hi Team,

By design when a user is added in F&O, the user is fetched from AAD (display name). Whereas when a user is added in CRM, the list is fetched from AAD (First name + last name). We might have a scenario where the display name and first name + last name might not match. Due to this if a user whose display name and first name + last name doesn't match, the user will encounter an error while performing multiple operations in both CRM and F&O. (Sales order creation is one of the examples).

Below is an example.

First Name: John

Last Name: Carter

Display Name: John H. Carter

In the above example when the user is added to CRM, it's read as "John Carter". When the same user is added to F&O, it's read as "John H. Carter". As the CRM and F&O username doesn't match users will encounter a "username mismatch" error while performing actions.

It would be very helpful if F&O fetches the First name and last name from AAD, concatenates both fields, and assign the result to the username field. It's difficult for the client to make the display name the same as the first name + last name by making changes in AAD. They might have a large number of users list and it would be a time-consuming process to make changes to all those users from AAD.

F&O Navigation path: System Administrator>Users>Users. (Username column).

CRM: Power Platform Admin Center>Environments> (Open the environment)>Settings>Users. (Name column).

Kindly request you make the required design changes in the F&O instance where the username field fetches first name + last name fields from AAD so that it matches the CRM name field.

Regards,

Pavan