The user with this email does not exist in Microsoft Entra ID

The title of this blog is an error that you may encounter when maintaining users in Microsoft Dynamics 365 Finance and Operations. In this blog, I will explain when this error will be triggered, how it might impact your licensing reports, and how to solve this error.

The error explained

Each user who will be imported or manually added to Dynamics 365 F&O is sourced from Microsoft Entra ID. The link between the user in Entra ID and in Dynamics 365 F&O is based on the object ID of the user in Entra ID. This is retrieved by a search using the email address used for the login and stored in the field Telemetry ID in Dynamics 365.

In case the user can’t be found in Entra ID based on the email address you will get the error: The user with this email does not exist in Microsoft Entra ID.

Before saving the user details using the user interface or via a data entity, it will perform the next validation. In case the Telemetry ID field contains an empty GUID and the field isMicrosoftAccount (hidden field) is not true, the error is thrown to the user. You can then check if there is a typo in the Email field. On purpose, in the screenshot above, I made a mistake in the email address.

Existing users and possible impact

In some scenarios, you might have existing users in your application with an enabled state that are not working anymore in your organization. As long as the Telemetry ID has a value, you can disable the user or make any other changes. When the Telemetry ID has an empty GUID, you get the same error, regardless of any change on that user. You are then not allowed to disable the user.

This can have an impact on your licensing reports. Enabled users with security roles are listed on these reports. As such, the user will not log in to the application anymore; no license assignment is required, but the report indicates that there are pending actions on your side.

When the Entra ID account is deleted, and the user has the original Object ID stored, the validation is passed, and you can disable the user without any problem.

Edit existing users without Telemetry ID

As mentioned, there is no option to edit an existing user in case the Telemetry ID does not have a GUID value. In case you need to edit details, like disabling the user, there are two workarounds possible without creating an X++ script.

1. JIT database access and set the value of the field enable in the table UserInfo to 0. This option is not possible for production environments. For LCS-managed sandbox environments, you can read how to get direct database access here: Enable just-in-time database access – Finance & Operations | Dynamics 365 | Microsoft Learn.
   In case your environment is created on PPAC, you can read the next page to get database access: Request credentials to access D365 product database – Power Platform | Microsoft Learn. At this moment in time, only development environments have write permissions. A sandbox has reader permissions only, but this will be changed to have write permissions in the future.
2. Create a user account in Entra ID and link the current F&O user. This option will be explained in detail below and can be used for all environments, including production environments.

In my demo environment, there is a user still enabled, while the Entra ID user has been deleted. The email of this user is willem@dynamicspedia.com.

The first step to be done is to recreate the user in Entra ID. You might need to contact your system administrator or create an internal request to get a user added. Note that the account should be enabled. There is no need to send the created user account and password to anyone, as this user needs to be deleted later. In this demo, I created the user via the Azure portal, but this can also be done from, e.g., the Microsoft 365 admin center.

When this user is added, you still can’t edit the user, as the Provider ID field does not contain the correct GUID value. To get this fixed, you need to go to the Invalid users page, which you can find in the System administration > Users menu. I wrote a blog before on the Invalid users feature when it was newly introduced in Dynamics 365. If you can’t find the user directly, click on the Refresh menu item in the action menu bar.

To get a Telemetry value, click on Repair Telemetry IDs. This will open a dialog page where you can choose to run it in the background via the batch framework or on the client. There is no need to select individual records; it will loop through all records where it could not find the user in Entra ID.

This task may also be the reason why the GUID value will be cleared in case the user is not found in Entra ID. So, ensure that in your procedures, you not only disable or remove the user in Entra ID, but also at least disable them in Dynamics 365 F&O. Now you can go to the Users page, find the user, and disable the account.

Don’t forget to delete the temporary Entra ID user as last step.

Note that adding or removing security roles for this user does not trigger the validation if the user exists in Entra ID.

I do hope you liked this post and will add value for you in your daily work as a professional. If you have related questions or feedback, don’t hesitate to use the Comment feature below.


That’s all for now. Till next time!