How to configure SCIM with Azure directory (EntraID)

Last updated on November 12th, 2026

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

  1. Log in to Azure
  2. Go into Entra ID.
Azure portal home with Microsoft Entra ID selected under Azure services
  1. Enterprise applications
Microsoft Entra ID Manage menu with Enterprise applications selected
  1. New application
Enterprise applications All applications page with New application selected
  1. Create your own application
Browse Microsoft Entra Gallery with Create your own application selected
  1. Give a name to your application and click Create
Create your own application panel with the Create button selected
  1. Click “Provisioning”
Enterprise application Manage menu with Provisioning selected
  1. Click “Get started”
Enterprise application Provisioning overview with the Get started button selected
  1. Select Automatic provisioning mode and click on admin credentials.
Provisioning Mode set to Automatic with the Admin Credentials section selected
  1. Switch to your Yodeck account
  2. Navigate to your account settings
Yodeck profile menu with Account Settings selected
  1. Click “SSO (Single Sign On)”
Account Settings list with SSO (Single Sign On) selected
  1. Click “Advanced Settings” Tab
SSO (Single Sign On) settings with the Advanced Settings tab selected
  1. Turn on Deprovision using SCIM
SSO Advanced Settings with the Deprovision using SCIM toggle selected
  1. Generate your secret token and click save.
SSO Advanced Settings with the Generate Token button selected next to the SCIM base URL
  1. Go again into the Provisioning page and paste the Secret Token and Identifier
  2. Click “Test Connection”
Entra Admin Credentials with the Yodeck Tenant URL and Secret Token entered and Test Connection selected
  1. You should be notified that the supplied credentials are authorized to enable provisioning.
  1. You are all set. Click save.
Entra Provisioning page with the Save button selected

User provisioning/de-provisioning

To assign users to your SCIM application, please follow the steps below:

  1.  Go to the application and click on “Users and groups”
Enterprise application Manage menu with Users and groups selected
  1. Click “Add user/group”
Users and groups page with the Add user/group button selected
  1. Click “None Selected” and select the users you want to assign to your SCIM application.
Add Assignment panel with the Users None Selected link selected

 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:

  1. Assign the users you want to provision to the SCIM application.
Users and groups list with two users selected for provisioning
  1. 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.)
Entra Provisioning Settings with the Provisioning Status set to On
  1. Click save. The provisioning status will trigger the action that corresponds to the Yodeck app.
Entra Provisioning page with the Save button selected

Bulk de-provision

  1. Switch to the tab “Users” in Microsoft Azure.
  1. To de-provision the users, go to the user section, select the users you want to de-provision, and click Delete.
Entra users list with two users selected for bulk de-provisioning
Entra users list toolbar with the Delete button selected
  1. 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.)
Entra Provisioning Settings with the Provisioning Status set to On
  1. Click Save. With this action, the deleted users from AD will be deleted in the Yodeck app as well.
Entra Provisioning page with the Save button selected

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.

  1. Click Test Connection again.
  2. 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.
  3. 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.

  1. Contact our Support team and send them the email addresses of the users who aren’t created.
  2. 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.
  3. 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:

  1. In Microsoft Entra ID, open your Yodeck application and go to Provisioning.
  2. Under Mappings, select Provision Microsoft Entra ID Groups.
  3. 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!