This might not be the most breaking news blog post I’ve done, but the question once in a while pops up so I guess it has some relevans.
When activating a POS (being either C or M) in a newly installed environment you can end up with this error:
“DA1023 – Could not resolve identity. The Azure AD account is not mapped to an employee in Retail headquarters”
What’s missing is the relation between the Azure AD account you typed in in the activation login and a worker in Dyn365O. To fix this go to workers:
Locate the worker you’d like to associate your AAD account with. In this case we pick Emma:
On the Retail ribbon pick “Associate existing identity”:
Select the AAD account:
Verify that the worker and the AAD account is linked:
Go back to the installer and click Retry:
That should bring you passed the error.
When trying to associate a worker with an AAD user in New Dynamics AX you can in some of the releases get an error saying “The service you are trying to reach is currently unavailable. Please contact your System Admin…”.
Now in the New Dynamics AX the System Admin is often pretty hard to find unless you have a mirror so here is something that might get you passed that error. There’s no fancy stuff here. More a matter of how to approach the task.
Click “Associate existing account”:
Change “Filter using columns” to “Search using email” and put in the email of the user:
Click Search and select the user on the list:
Click OK and you’re back on the worker with a association to your user:
The good part is that you can do this within a few seconds compared to having to wait for the full AAD to be loaded before you can pick the user, which you are going to be searching for anyways.
There is a hot fix released for this error, but if you just need to get it fixed now then the above work-around could help you out.