None known at present.
We are aware of 3 identity providers customers have used to date (Microsoft Azure, Okta & Google Cloud), though as a standard, any SAML identity providers are in theory compatible.
Most issues when setting up the integration are usually caused by incorrect field mapping configuration. Typically these will be related to the wrong field names or the email address being empty. Microsoft Azure Entra ID in particular can be confusing as it provides two different values. Asking customers for screenshots of their field mappings within their identity providers can help with clearing this confusion quickly.
Errors are logged in the event logs.