SCIM Provisioning
Configure SCIM 2.0 provisioning from Microsoft Entra ID to Incident Tracker: tenant URLs, attribute mappings, user assignment, logs and troubleshooting.
On this page
Purpose#
This guide provides instructions for configuring SCIM (System for Cross-domain Identity Management) user provisioning between Microsoft Entra ID and Incident Tracker. SCIM provisioning automates account lifecycle management by synchronizing user data from your identity provider (IdP) to Incident Tracker in a secure and scalable manner.
Key Benefits#
- β Automated Account Creation: Assigned users in Entra ID are automatically created in Incident Tracker.
- π Ongoing Synchronization: User updates in Entra ID are automatically reflected in Incident Tracker.
- π« Automatic Deactivation: Users removed or unassigned in Entra are automatically disabled in Incident Tracker.
- π Enterprise-Grade Security: Built using standard SCIM 2.0 protocol for modern identity management.
Prerequisites#
Ensure the following prerequisites are met before beginning the setup:
| Requirement | Description |
|---|---|
| Microsoft Entra Admin Access | Permissions to manage Enterprise Applications |
| SCIM Bearer Token | Provided by Incident Tracker Support |
| SCIM Tenant URL | Cloud (US): https://public-api.incident-tracker.com/scim/v2/; Cloud (UK): https://public-api.incident-tracker.co.uk/scim/v2/; Cloud (Canada): https://canada-public-api.incident-tracker.com/scim/v2/; On-prem: Customer-specific base URL |
Use the Tenant URL for the region your Incident Tracker account is hosted in.
Configuration Steps#
1. Create the Enterprise Application#
- Sign in to the Microsoft Entra Admin Center
- Go to Enterprise Applications
- Click + New Application
- Choose Create your own application
- Name the application (e.g.,
Incident Tracker Provisioning) - Select Integrate any other application you don't find in the gallery
- Click Create
2. Configure Provisioning#
- Open the Enterprise Application
- Navigate to the Provisioning tab
- Click Get Started
- Set the SCIM Connection fields below.
SCIM Connection Settings
| Field | Value |
|---|---|
| Tenant URL | Cloud (US): https://public-api.incident-tracker.com/scim/v2/; Cloud (UK): https://public-api.incident-tracker.co.uk/scim/v2/; Cloud (Canada): https://canada-public-api.incident-tracker.com/scim/v2/; On-prem: Customer-specific base URL |
| Secret Token | Provided by Incident Tracker Support |
Use the Tenant URL for the region your Incident Tracker account is hosted in.
Click Test Connection to verify the configuration.
3. Configure Attribute Mappings#
- In the Provisioning tab, click Attribute mapping
- Select Provision Microsoft Entra ID Groups
- Change Enabled to No and save
- Select Provision Microsoft Entra ID Users
- Review and configure the recommended mappings in the table below. All other mappings can be removed.
| Azure AD Attribute (Source) | SCIM Attribute (Target) | Notes |
|---|---|---|
userPrincipalName |
userName |
Primary login identifier |
givenName |
name.givenName |
Required |
surname |
name.familyName |
Required |
mail |
emails[type eq "work"].value |
Primary email |
manager |
urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:manager.value |
Manually added as a Direct mapping type |
accountEnabled |
active (or enabled) |
Maps Entra account status to Incident Tracker enabled status |
objectId |
externalId |
Maps user's GUID (immutable identifier) |
βΉοΈ Manager Notes
- Uses Azure AD
objectId(GUID)- GUID must match an existing user in Incident Tracker
- If unmatched, field is ignored
- If Manager is empty in Entra, but exists in Incident Tracker, it remains in Incident Tracker
βΉοΈ Enabled Field Notes
accountEnabledin Entra controls active/disabled state- Mapped to
enabledin Incident Tracker- Users set to
falsein Entra will be disabled in Incident Tracker
Click Save when finished.
4. Assign Users or Groups#
- Go to the Users and Groups tab
- Click + Add user/group
- Select the users or groups to provision
- Click Assign
β οΈ Group-based provisioning triggers user-level provisioning events. Group membership data is not included in SCIM payloads.
5. Start Provisioning#
- Return to the Provisioning tab
- Click Start Provisioning
Provisioning runs automatically on a scheduled interval (approximately every 40 minutes by Entra default).
Monitoring & Maintenance#
View Logs#
Use the Provisioning Logs tab to monitor:
- β Successful provisioning events
- β οΈ Skipped records
- β Errors or misconfigurations
Logs can be filtered by status, user, and timestamp.
Deactivation Handling#
Incident Tracker automatically disables user accounts when:
- They are unassigned from the SCIM application, or
- They are disabled in Microsoft Entra ID
No manual cleanup is required.
Troubleshooting & Errors#
| Issue | Resolution |
|---|---|
| Test connection fails | Verify SCIM URL and token. Contact support if needed. |
| Users not provisioning | Ensure they are assigned to the SCIM application. |
| Attribute changes not syncing | Confirm mappings match Incident Tracker requirements. |
| Manager field not syncing | Ensure manager has a valid objectId and exists in Incident Tracker. |
Technical reference (for developers)
PATCH Response Codes#
When a PATCH request is made with a user object and ID, the API may return:
- 200 OK β Request succeeded.
- Returns updated user object as JSON.
- Partial updates apply: if one attribute (e.g., first name) is updated successfully but another (e.g., email) fails, a
200is still returned.
- 400 Bad Request β Invalid request payload or parameters.
- 401 Unauthorized β Authentication failure. Token may be invalid or expired. Re-enter and retry.
- 404 Not Found β User not found.
- 409 Conflict β Update failed due to attribute conflicts.
- No attributes are updated when all attempted updates fail (e.g., only email or username updates were attempted and all conflicted).
- 500 Internal Server Error β Unexpected server exception.
Supported Endpoints#
Incident Tracker supports the following SCIM 2.0 endpoints:
| Method | Endpoint | Description |
|---|---|---|
GET |
/Users |
Returns a paginated list of users. Supports filtering, sorting, and pagination parameters. |
POST |
/Users |
Creates a new user (single user only; bulk operations are not supported). Requires standard attributes. |
PATCH |
/Users/{id} |
Updates an existing user's attributes. Soft delete sets user inactive. |
DELETE |
/Users/{id} |
Deletes a user in Incident Tracker. Runs if user is completely deleted in Entra. |
β οΈ POST attempts made to endpoint
/Usersfor account creation will only attempt when the meta field attribute resourceType = "User"
β οΈ Bulk Operations Not Supported
The SCIM/Bulkendpoint is not currently supported.
- Only single-user create, update, or delete requests are accepted.
- Multiple users must be provisioned individually.
GET /Users β Filtering, Sorting, and Pagination#
The /Users endpoint supports optional query parameters for filtering, sorting, and pagination.
π Filter Support
- Only the
eq(equals) operator is supported - Supported attributes:
userNameexternalIdemails.valueactive
Format:
filter={attribute} eq "{value}"
Examples:
GET /scim/v2/Users?filter=userName eq "john.doe@example.com"
GET /scim/v2/Users?filter=active eq "true"
β οΈ Operators such as ne, co, or sw are not accepted.
βοΈ Sorting Support
Sort users by creation date using the sortBy parameter:
| Value | Behavior |
|---|---|
newest |
Newest to oldest |
oldest |
Oldest to newest (default) |
If an invalid value or no value is passed,
sortBydefaults tooldest.
π Pagination Support
Pagination is controlled by the startIndex and itemsPerPage parameters:
| Parameter | Description |
|---|---|
startIndex |
1-indexed starting position. "1" represents the first record. Defaults to "1" if invalid or not supplied. |
itemsPerPage |
Number of results to return from startIndex. Defaults to 100 if invalid or not supplied. Maximum allowed value is 100. |
sortBy |
Sort order (newest or oldest). Defaults to oldest if invalid or not supplied. |
Pagination Examples
First 50 newest users#
GET /scim/v2/Users?startIndex=1&itemsPerPage=50&sortBy=newest
25 users starting from the 101st, oldest first#
GET /scim/v2/Users?startIndex=101&itemsPerPage=25&sortBy=oldest
Active users only, first 50, newest first#
GET /scim/v2/Users?filter=active eq "true"&startIndex=1&itemsPerPage=50&sortBy=newest
β Filtering, sorting, and pagination can be combined in a single request.
SCIM User object example#
{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:User",
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"
],
"id": "test-user-001",
"userName": "test.user@example.com",
"name": {
"givenName": "TestFirstName",
"familyName": "TestLastName"
},
"emails": [
{
"value": "test.user@example.com",
"type": "work",
"primary": true
}
],
"active": true,
"manager": {
"id": "test-manager-001",
"ref": "/Users/test-manager-uuid",
"displayName": "TestManagerName",
"email": "manager@example.com",
"externalId": "test-manager-uuid"
},
"meta": {
"resourceType": "User",
"created": "2025-01-01T00:00:00",
"lastModified": "2025-01-02T00:00:00",
"location": "https://test-api.example.com/scim/v2/Users/test-user-uuid",
"version": "W/\"2025-08-13T16:13:35.6964556Z\""
},
"externalId": "test-user-uuid"
}