KB: Azure SSO User Provisioning Fails with 400 Error Due to Existing Account Conflict in AltiumLive
Created: November 12, 2025 | Updated: November 12, 2025
A365
User provisioning via Azure SSO to AltiumLive may fail with a 400 Bad Request error if the user already exists in the AltiumLive database under a different organization or as a self-registered account. This conflict prevents the Identity Provider (IDP) from creating the user in the intended company account. The issue typically arises when the same email address is already associated with another organization in AltiumLive. This article explains the root cause and provides resolution steps, including reviewing provisioning logs, configuring email domains, and contacting support for account transfers.
Solution Details
Azure user provisioning for SSO access fails with a 400 Bad Request error. The error message typically reads:
"Failed to Create user xxxx in Company account name."
This occurs during automated user provisioning from the IDP to the AltiumLive company account.
Why the 400 Error Happens
This error is caused by a user conflict in the AltiumLive database. The user may already exist due to:
- Self-registration with AltiumLive using the same email address.
- Association with a different company account in AltiumLive.
In such cases, the IDP attempts to create the user under Company A, but the user is already registered under Company B, resulting in a provisioning failure.
Quick Checks:
- Review provisioning logs in your IDP (e.g., Microsoft Entra, Okta).
- Confirm if the user is already registered in AltiumLive.
- Verify if your company email domain is configured in AltiumLive.
- Check if the user is part of another organization in AltiumLive.
How to Resolve the Provisioning Conflict
- Prefer user creation through your IDP.
- Manually add the user to your AltiumLive company account if needed.
- Configure your company email domain to allow users to send joining requests.
- Review provisioning logs to confirm the error.
- If the user is registered under a different company, contact Altium Support to request a user transfer.
Resolution Steps
1. Check Provisioning Logs
- Use Microsoft Entra or Okta logs to identify errors.
- Look for messages like: “Failed to create user xxx in company account” with a 400 error.
2. Self-Registered Accounts
- Ensure your company domain is configured in AltiumLive.
- Ask the user to send a joining request.
- Accept the request to add them to your company account.
- The user will then sync with Azure AD.
3. Users in a Different Company
- If Step 2 doesn’t help, confirm the user is under a different company account.
- Contact Altium Support to request a user transfer.
Note: This requires user consent and acknowledgment from both organizations due to access changes.
🛠️ Troubleshooting Tip Box
- Error Message to Look For:
"Failed to create user xxx in company account"
Status Code: 400 Bad Request - Common Causes:
- User already exists in AltiumLive under a different company account.
- User has self-registered using the same email address.