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
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.
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!