Article demonstrates checks to help resolve the above error if all Azure sync is correct. This document can also help to resolve issues with “no dashboard found” if they’re in the correct group
Error example:
...
Error
...
Explanation:
The error indicates that myday is unable to identity identify the account the user has tried to logged in as and therefore treat treats it as an unauthorised myday user. This is because the user has fell out of Azure provisioning scope of authrooirsed user(s) or group.
Possible causes for the issue and fix
Possible Cause | Resolution steps |
|---|---|
Check if user(s) is within the User and groups section if you have the scope enabled to bring in assigned users and groups. | Within the left menu panel of myday enterprise app, go to User’s and Group and search for the X user. If the user is not within the list then that mean they are outside of the scope and will need to be added in there or be member of group that's within User’s and Groups.
|
Object ID and External ID doesn’t match | You’ll need to manually delete the user(s) within myday and resync the user by provision on demand, see here for steps on resyncing a user. NOTE group membership will not be provisioned until the initial sync which happens every 40 minutes. |
They have logged in using the incorrect account (Face ID can be issue if they have more than one Microsoft account stored in the apple Keychain) | As admin search within user or identity management for the user and confirm the email address or username. If it’s Face ID then they’ll need to manually sign in |