Monitoring your user synchronization
Azure provides logs and tools to monitor user synchronization to Bizagi, offering the following options:
Progress Bar
You can review the provisioning progress bar:
Audit logs
See the audit log of the provisioning options:
Provisioning Logs
You can review the Entra ID provisioning logs. For further information click here.
Troubleshooting
I can't read or provision a user - Error AADSTS50105 - The signed in user is not assigned to a role for the application
This incident occurs because Entra ID can only read and provision users that are immediate members of an explicitly assigned group. Therefore, the user must be assigned directly to the application. Also, you can use scoping filters to define attribute-based rules that determine which users are provisioned to an application.
I have noticed some users are not being synchronized
Entra ID handles its own cache memory. If you have issues, and some users are not being synchronized (specially after changes in your Development or Test environment), we recommend to delete the application in Entra ID and create it again.
For further information about error synchronization in Entra ID, check the article Understanding errors during Entra ID synchronization from the Microsoft documentation.
An error message was displayed, where can I look up for further information about it?
You can find AADSTS error descriptions, fixes, and some suggested workarounds in the Entra ID Authentication and Authorization Error Codes article from Microsoft's official documentation. However, since errors and messages are subject to change, check the instructions in the Lookup current error code information section.
What to do if my application is paused or under quarantine?
This error is generated when the assigned time in the Token lifetime property has expired. When this happens, the application throws an error message indicating that the application is paused and has problems accessing the token. To avoid this, assign a value of 0 to this field during the bearer token generation.
Considerations
•Groups and roles synchronization is not supported.
•To deactivate users, you need to UPDATE the user information and set the Active attribute as false.
•The first time you synchronize users using the SCIM protocol, you must restart your Bizagi BPM server.
Last Updated 9/11/2024 10:24:54 AM