First things First
To enable SCIM in the Yodeck app, you first have to enable SSO successfully.
Also, log in to your account as the Account Owner.
This guide describes the process of enabling SSO for SCIM.
Enable SCIM
- Log in to Azure
- Go into Entra ID.
- Enterprise applications
- New application
- Create your own application
- Give a name to your application and click Create
- Click “Provisioning”
- Click “Get started”
- Select Automatic provisioning mode and click on admin credentials.
- Switch to your Yodeck account
- Navigate to your account settings
- Click “SSO (Single Sign On)”
- Click “Advanced Settings” Tab
- Turn on Deprovision using SCIM
- Generate your secret token and click save.
- Go again into the Provisioning page and paste the Secret Token and Identifier
- Click “Test Connection”
- You should be notified that the supplied credentials are authorized to enable provisioning.
- You are all set. Click save.
User provisioning/de-provisioning
To assign users to your SCIM application, please follow the steps below:
- Go to the application and click on “Users and groups”
- Click “Add user/group”
- Click “None Selected” and select the users you want to assign to your SCIM application.
To provision the user, you have to assign him to your SCIM application first.
Bulk provision/de-provision
For Bulk provision/de-provision (create/delete many users), you can follow the steps below:
- Assign the users you want to provision to the SCIM application.
- Go to the provisioning tab and toggle the provision status to on. (If it is on, you have to toggle it off and on again.)
- Click save. The provisioning status will trigger the action that corresponds to the Yodeck app.
Bulk de-provision
- Switch to the tab “Users” in Microsoft Azure.
- To de-provision the users, go to the user section, select the users you want to de-provision, and click Delete.
- Go to the provisioning tab and toggle the provision status to on. (If it is on, you have to toggle it off and on again.)
- Click Save. With this action, the deleted users from AD will be deleted in the Yodeck app as well.
Troubleshooting
Test Connection fails with “CredentialValidationUnavailable”
If Test Connection in Microsoft Entra ID fails with the error code CredentialValidationUnavailable and the message “An error occurred while sending the request”, Entra didn’t get a usable response from Yodeck. This is a network-level error that Entra reports. It doesn’t mean that Yodeck rejected your Secret Token.
- Click Test Connection again.
- If it fails again, note the exact time of the attempt, with your time zone, and the Request ID that Entra shows for the failed test.
- Contact our Support team and send them both, so they can trace the request.
Testing the Tenant URL returns 404 or 401
If you send a request to the Tenant URL yourself (the Identifier you copied from the Yodeck Portal), for example with curl, the response code tells you what happened:
- 404 Not Found with your Secret Token: this is expected. The Tenant URL is a base address, not a resource, so it has nothing to return. Entra calls specific paths under it, such as /Users. The 404 also confirms that Yodeck accepted your token.
- 401 Unauthorized: the request had no Secret Token or the token isn’t valid.
The Secret Token stays the same after you turn Deprovision using SCIM off and on
This is expected. Your SCIM token is tied to your account’s SSO configuration and stays the same by design. It doesn’t change when you turn Deprovision using SCIM off and on again, so you don’t need to update it in Entra.
If you need a new token, for example for security reasons, contact our Support team and they will help you replace it.
A user is never created and Entra ID retries the user on every sync
Each email address belongs to one Yodeck user, and each user belongs to one Yodeck account. If someone already has their own Yodeck account with the same email address, for example one they created when they signed up on their own, Yodeck rejects the request to create them in your account. This is a security measure: SCIM never moves a user out of an account it doesn’t manage. Entra ID then retries that user on every sync cycle, with the same result.
- Contact our Support team and send them the email addresses of the users who aren’t created.
- Support checks what each separate account contains and confirms the next step with you before changing anything. They either change the login email of the separate account, which keeps that account and its content as they are, or move its content into your account and close the separate account. Nothing is deleted without your approval.
- On the next sync cycle, Entra ID creates the users in your account.
Entra ID shows errors for groups
Yodeck provisions users only. Groups aren’t supported, so Yodeck rejects every group that Entra ID sends, and Entra ID retries them on every sync cycle. These errors don’t affect user provisioning, but repeated failures can lead Entra ID to put the provisioning job in quarantine. To stop them, turn off group provisioning:
- In Microsoft Entra ID, open your Yodeck application and go to Provisioning.
- Under Mappings, select Provision Microsoft Entra ID Groups.
- Set Enabled to No and click Save.
Need Help?
The Yodeck Support Team can help you out! Log in to your Yodeck account and send us a message from the bottom right corner!