Set up SCIM provisioning with Microsoft Entra ID
This guide connects Microsoft Entra ID to Autoheal with SCIM, so Entra creates, updates, suspends and removes your team's Autoheal accounts and keeps the groups you assign in sync.
For what provisioning does in Autoheal (existing people, groups, offboarding, more than one identity provider), see SCIM Provisioning.
Before you begin
You need:
- A SCIM connection in Autoheal and one of its keys, from Authentication → User provisioning. See Set up the connection.
- An Entra account that can create enterprise applications and configure their provisioning, such as an Application Administrator.
- Microsoft Entra ID P1 or P2 to assign groups. Without it you can assign people only.
Create the enterprise application
In the Microsoft Entra admin center, open Enterprise apps → New application → Create your own application. Name it, for example Autoheal, and choose Integrate any other application you don't find in the gallery.
Configure provisioning
- In the application, open Provisioning and set Provisioning Mode to Automatic.
- Under Admin Credentials, enter the connection's Tenant URL and the key as Secret Token. Select Test Connection. On Authentication → User provisioning, the connection changes from Waiting for first request to Connected.
- Under Mappings, open the user mapping. Keep
userName,active,displayName,emails[type eq "work"].value,name.givenName,name.familyNameandexternalId. Set theexternalIdmapping's source attribute toobjectId: Entra's default,mailNickname, can be the same for two people.- Autoheal ignores the other default attributes, such as manager, job title, addresses and phone numbers. You can leave them mapped.
- Leave Create, Update and Delete selected under Target Object Actions. Delete is how Entra removes someone.
- Set Scope to Sync only assigned users and groups, and assign the people and groups to sync under Users and groups.
- Try one person first with Provision on demand, and check they appear on Users in Autoheal. Then set Provisioning Status to On.
How Entra's changes reach Autoheal
After provisioning is on, Entra syncs about every 40 minutes. Provision on demand applies one person's changes at once.
| In Entra | In Autoheal |
|---|---|
| Assign a person, or a group they're in | They're created, or linked if they already have an account |
| Disable, soft-delete or unassign them | They're suspended: access stops, roles are kept |
| Re-enable, restore or reassign them | They're reactivated with the same account and access |
| Permanently delete them | They're removed from your organization |
| Change their name or email | Updated; an email change for someone who can manage access waits for another admin |
See Offboarding for what suspending and removing keep.
Replace the key
Rotate the key on the connection's card, paste the new key into Secret Token under Admin Credentials, select Test Connection, then Save: Entra saves only after a successful test. The old key keeps working through the rotation's grace window. See API Credentials.
Troubleshooting
Entra's Provisioning logs (P1 or P2) show each request and Autoheal's answer. Autoheal's own errors are listed in SCIM Provisioning troubleshooting.