Resolved -
This incident has been resolved.
Mar 12, 10:38 EDT
Monitoring -
A fix has been implemented and we are monitoring the results.
Mar 12, 09:47 EDT
Update -
We are aware that some customers are unable to apply the previously communicated workaround due to the error: "Entra Tenant Id is already in use."
We are currently working to deploy a permanent fix that will resolve this issue without requiring customers to apply the workaround. We will provide a further update once the fix has been successfully deployed.
We apologize for the inconvenience and thank you for your patience.
Mar 12, 07:16 EDT
Update -
We have verified a fix for this issue and will be deploying a hotfix at the earliest opportunity.
Once the hotfix is applied, affected customers who applied the workaround will be able to revert their "Map federated user to existing directory user" setting back to Disabled.
We will provide an update once the hotfix has been successfully deployed.
Mar 12, 02:15 EDT
Identified -
We have identified that affected customers have their "Map federated user to existing directory user" setting configured as Disabled, which is not the default setting. The default value for this setting is Optional.
1. From the left navigation, click Settings, then select Federation Providers.
2. Click the name of your federation provider.
3. On the Settings tab, click Edit.
4. Under User Mappings, locate the "Map federated user to existing directory user" option.
5. Change the value from Disabled to Optional.
6. Click Save.
We are currently working on a remediation and will provide an update once it is complete.
Mar 12, 00:59 EDT
Update -
We are continuing to investigate this issue.
Mar 11, 22:57 EDT
Investigating -
We are currently investigating an issue affecting SSO authentication for some customers. Impacted users are encountering Federation Error 102 during login.
Our team is actively investigating.
Mar 11, 21:49 EDT