Provision and Deactivate Users with Microsoft Entra ID and SCIM - Article
Summary
Directory-led provisioning reduces repeated account maintenance when learners join, change details or leave. The supported Microsoft Entra ID and SCIM connection supplies user changes to Eurekos in one direction. It manages the account lifecycle; it does not replace single sign-on configuration or automatically define which training the person must attend.
Use this article to:
- Plan directory-owned account provisioning
- Configure the supported SCIM endpoint and credential relationship
- Verify creation, updates and deprovisioning
- Maintain credentials and investigate provisioning evidence
Separate account lifecycle, sign-in and enrollment
An organization may want partner users maintained from Microsoft Entra ID, authenticated with an existing identity and enrolled in relevant product training. Treat those as three connected decisions. SCIM supplies the account lifecycle; OIDC or SAML supplies the configured sign-in route; the appropriate enrollment process supplies access to training.
The Eurekos connection supports provisioning from Microsoft Entra ID to Eurekos. It is not a general promise of bidirectional directory synchronization or compatibility with every provider that uses the SCIM name.
Agree the account population and mapping
Choose which directory users belong in Eurekos and who owns their profile information. Prepare the relevant Entra application assignment and attribute mapping with the directory administrator. Use a representative pilot before assigning a large population.
The provisioning flow creates users as Participant. Do not assume that a directory attribute grants an administrative role or assigns a Training Activity. Establish those requirements separately through supported platform configuration.
Use stable identity matching and test an update to an existing person. An email or user-principal-name change must be checked against the intended account rather than treated as a reason to create a duplicate learner.
Configure the supported connection
- Ask Eurekos to confirm SCIM activation and the supported setup for your platform. Coordinate with an administrator of the relevant Microsoft Entra tenant.
- In Entra’s Enterprise applications, create or select the non-gallery enterprise application used for Eurekos provisioning. Open its Provisioning configuration.
- Use the Eurekos platform address followed by /scim/v2 as the tenant URL. Use your own agreed platform domain, rather than an example or another environment’s address.
- In Eurekos, open Settings → Third party integrations → API and create the client required for provisioning. Select the supported user-management scopes for the agreed operations. The set includes user read, create, update, block and delete scopes; review the exact current scope choices with the integration owner.
- Copy the generated bearer token into Entra’s Secret token field through your approved credential-handling process. Use Test connection in Entra before enabling the intended provisioning population.
- Review the attribute mappings and assignments, then start the agreed provisioning process. Inspect Entra’s provisioning evidence and the resulting Eurekos user record.
The scope configuration is an operational dependency. Removing scopes used by provisioning can cause 403 errors. Credential expiration is also separate from the directory’s schedule: replace an expiring token in the Entra configuration and test the connection before the existing credential stops working.
Understand the supported changes
| Directory action | Documented Eurekos result | What to verify |
|---|---|---|
| Provision a new assigned user | A Participant account is created | Identity, mapped profile values and the intended account population |
| Update the user | Supported mapped information is updated | The existing learner is updated without unintended duplication |
| Deprovision the user | The Eurekos account is blocked | Account state and the actual sign-in consequence |
Deprovisioning in this connection means blocking, rather than assuming the learner and all historical training evidence are permanently deleted. Do not use a directory deletion as a substitute for a separately governed retention decision.
Allow for scheduled processing
Provisioning is processed on the provider’s schedule; it is not a promise that every directory edit is immediately visible. Entra provides Provision on demand for supported create/update checks. The deprovisioning flow still relies on scheduled processing.
Use Provisioning logs and the details of a specific operation to see success or failure and the reported error. Then inspect the corresponding Eurekos account. A successful connection test proves that the credential and endpoint can connect; it does not prove that every assigned user and mapping has been processed.
Verify the configuration
| Scenario or check | Expected result or evidence |
|---|---|
| A representative assigned directory user | One correct Participant account appears in Eurekos |
| A mapped profile change | The existing account receives the intended change |
| An unassigned or out-of-scope user | The assignment and mapping rules do not create an unintended learner |
| Scheduled deprovisioning | The intended Eurekos account is blocked |
| Credential replacement | Test connection succeeds and a representative operation still processes |
| Training access | The separately configured enrollment and sign-in journey works as intended |
Troubleshooting
| Problem | What to check |
|---|---|
| Test connection fails | Tenant URL, current bearer token, feature activation and supported scopes |
| Connection succeeds but a user is absent | Entra assignment, mapping, provisioning logs and processing schedule |
| A request receives 403 | Required scopes, effective permissions and credential state |
| A directory update creates an unexpected account | Review matching identifiers and attribute mapping before expanding the population |
| A removed user is still active | Check scheduled deprovisioning evidence; do not assume an on-demand update covers blocking |
| The account exists but training is absent | Provisioning is separate from enrollment and the intended training-assignment process |
FAQ
-
Does SCIM replace SSO?
No. SCIM maintains the supported account lifecycle. OIDC or SAML sign-in is configured separately.
-
Does deprovisioning delete all learner history?
Entra-to-Eurekos deprovisioning blocks the account. Historical-data retention or deletion is a separate governed decision.