This article covers common questions and troubleshooting tips for managing users provisioned via SCIM (System for Cross-domain Identity Management). For initial setup instructions, see the SCIM 2.0 Entra ID setup guide.
- Inactive users & license counting
- Group-based provisioning: verify your mapping
- Accessing provisioning logs
- FAQ
1. Inactive users & license counting
Users in deskbird can be either Active or Inactive. Only Active users count toward your license total, Inactive users do not.
When a user is removed from your SCIM provisioning scope (e.g., removed from the synced group in Entra ID), they will be set to Inactive in deskbird during the next provisioning cycle. Inactive users cannot log in or make bookings.
Best practice
Only include users and groups in your SCIM provisioning scope that actually need access to deskbird. Regularly review your user list under Admin Portal > Users to ensure it matches your provisioning scope.
2. Group-based provisioning: verify your mapping
If you use group-based SCIM provisioning with Microsoft Entra ID, it is important to verify the group attribute mapping. Without the correct configuration, users removed from Entra ID groups may not be correctly deactivated in deskbird.
How to verify:
- In the Microsoft Entra ID portal, go to your deskbird SCIM application.
- Navigate to Provisioning > Mappings.
- Select Provision Microsoft Entra ID Groups.
- Scroll to the bottom and click Show advanced options.
- Locate the attribute with the target attribute members.
- Ensure the following:
- ❌
urn:ietf:params:scim:schemas:core:2.0:Groupis not selected - ✅
urn:ietf:params:scim:schemas:extension:enterprise:2.0:Userremains selected
- ❌
- Save the changes and allow a few minutes for Entra ID to apply them.
With this configuration, users removed from Entra ID groups will be correctly set to Inactive in deskbird during the next provisioning cycle. For the full setup walkthrough, see the SCIM 2.0 Entra ID setup guide.
3. Accessing provisioning logs
If users are not being provisioned or deactivated as expected, the Entra ID provisioning logs are the first place to check. These logs show the status of each sync operation and can help identify issues before contacting support.
To learn how to access and interpret provisioning logs, see the official Microsoft documentation:
👉 Microsoft Entra ID: Provisioning logs
When contacting deskbird support about provisioning issues, please include a screenshot or export of the provisioning logs for the affected user(s). This significantly speeds up diagnosis.
4. FAQ
This is most commonly caused by a group attribute mapping issue in Entra ID. Verify the mapping as described in section 2 of this article. Also check the provisioning logs in Entra ID to confirm whether the removal was sent to deskbird. If the logs show a successful deactivation but the user is still Active in deskbird, please contact support.
The initial SCIM provisioning cycle can take 1–2 hours depending on the number of users and groups. After the initial sync, Entra ID runs incremental syncs approximately every 40 minutes. Changes to user attributes or group memberships will be reflected in deskbird after the next sync cycle.
Yes. deskbird supports SCIM provisioning with both Microsoft
Entra ID and Okta. The SCIM endpoint is the same
(https://api.deskbird.app/v2/scim). Follow
Okta's standard SCIM provisioning setup and use the deskbird
SCIM token generated under
Admin Portal > API keys.
To help us resolve your issue as quickly as possible, please include:
- The email address of 2–3 affected users.
- A screenshot or export of the provisioning logs from Entra ID for those users.
- A description of the expected behaviour vs. the actual behaviour.