Follow these steps when:
- You get an error when setting up SCIM provisioning with Microsoft Entra ID
Suggested troubleshooting steps
Please find setup errors below with their related causes and troubleshooting steps.
| Error | Cause | Fix |
|---|---|---|
| Test Connection fails with a 401 error | Invalid or revoked API key. | Regenerate it in Riverside and re-enter it as the Secret Token. |
|
For Microsoft Entra ID only: "Invalid SCIM PATCH request" on every update |
The ?aadOptscim062020 flag is missing from the URL. |
Add it to your base URL, save, then restart provisioning. |
| "Missing required attribute: productions" | The productions mapping is missing, or resolves to empty for that user. | Revisit the step Add the required productions attribute. |
| "Productions not found or do not belong to this account" | A production slug is wrong, or the production belongs to a different account. | Confirm each slug against the production URL. |
| "Unsupported PATCH operation" | An unsupported attribute is still mapped. | Remove every mapping not listed in step Configure your user attribute mappings — including name.formatted. |
| Provisioning stops after repeated failures | Mapping error. | Fix the underlying mapping error, then select Restart provisioning. |
| Duplicate user error (409) | A user with that email already exists and is active in the account. | Remove the duplicate in Riverside, or align your matching attribute. |
| Group provisioning errors | Group provisioning isn't supported. | Turn it off as described in step Turn off group provisioning. |
| "Account has reached its seat limit (X of Y seats in use)" | The account is out of seats. | Contact Sales to increase your seat count in Riverside, then retry. |
If the issue persists, please contact Support.