SCIM with Microsoft Entra ID
The purpose of this document is to guide admins through the setup and daily use of SCIM at Secomea for automated user lifecycle management with Entra ID.
For base API documentation and troubleshooting, please refer to the separate guide provided on this.
Key Abbreviations
| Abbreviation | Definition |
|---|---|
| SCIM | System for Cross-domain Identity Management |
| CRUD | Create, Read, Update and Delete |
| IdP | Identity Provider (e.g. Microsoft Entra ID) |
| RFC | Request for Comments |
Base use cases we cover
- Provision and deprovision users from an Identity Provider (IdP)
- Create groups and assign users to them in the Identity Provider
- Specify which Secomea role a provisioned user should get
- Specify domain location for a user or group
Importantly: Managing which end devices a user is able to access will be handled directly in the Secomea system, by Admin users there.
Prerequisites
- A Secomea user with the domain admin role and SSO as the authentication method, which has been granted permission to handle a SCIM integration by the Secomea team.
- Pricing tier Professional or higher
- Access to Secomea Prime
- The required Entra role (Application Administrator or higher)
Daily Use
After the SCIM connection is established, the Entra ID automatically manages user lifecycle operations such as:
Create: When a user is added to an authorized group in the IdP, the account is automatically created in Secomea, including in all relevant GateManager(s). By default, a user will be assigned the LinkManager User role.
Update: Any attribute updates (e.g., name, email, department) are synchronized in real-time.
Deactivate/Delete: When a user is removed from a group or deleted in Entra ID, the account is disabled or deleted in GateManager depending on the configured policy. The default is that the user is initially disabled, to retain audit log records. You can configure recurring cleanup jobs that fully remove (delete) disabled user accounts after a set period.
The synchronization runs continuously based on the polling frequency set in Entra ID (every 40 minutes is common), but synchronization can also be triggered on demand.