Azure SCIM Integration

swimlane turbine supports scim 2 0 integration with azure active directory (microsoft entra) this integration enables administrators to automatically provision users and groups to swimlane using the scim standard high level configuration steps in the azure portal, create an enterprise application and enable scim provisioning under the provisioning tab set the provisioning mode to automatic enter your swimlane tenant url and secret token to create a secret token, see https //learn microsoft com/en us/rest/api/eventhub/get azure active directory token use provision on demand to manually sync a user or group if needed assign users and groups under the users and groups tab in the azure application user provisioning provisioning users from microsoft entra id to swimlane turbine takes approximately 40 minutes this interval is controlled by microsoft and applies to all user related operations, such as updating user details or removing user assignments these changes are synced to swimlane at the end of the next 40 minute cycle group provisioning provisioning groups, with or without users, typically takes 20 minutes to sync with swimlane this applies to changes such as adding or removing users from a group updating group details deleting groups or removing group assignments from the scim application understanding provisioning cycles in the overview tab of your azure scim configuration, you can view provisioning cycle timestamps the most relevant fields are last cycle start time and last cycle completed time any user or group related changes made after the last cycle start time will be processed in the next provisioning run—approximately 40 minutes later for users and 20 minutes later for groups immediate provisioning (provision on demand) to sync a user or group immediately, use the provision on demand feature available in the left navigation pane of the azure scim configuration this triggers an instant provisioning attempt for the selected user or group keep the following in mind provision on demand only supports provisioning; it does not support updates, deletions, or group membership changes when provisioning groups, you can select individual users rather than syncing the entire group attribute handling azure requires only the userprincipalname and displayname attributes swimlane expects additional attributes, including firstname , lastname , email , and displayname if any required attribute is missing, swimlane uses the userprincipalname value as a fallback for more information, see https //learn microsoft com/en us/azure/active directory/app provisioning/how provisioning works on microsoft learn