Show table of contents Hide table of contents

SCIM with Microsoft Entra ID

SCIM support for Entra ID is currently in preview.

To configure SCIM with Entra ID, the Seq instance must be reachable via HTTPS from Azure. If the Seq instance is internal-only, you will need to deploy Microsoft Entra Connect Provisioning Agent.

In Seq

  1. Configure the Microsoft Entra ID authentication provider.
  2. In Settings > Users, review the New User Defaults: these will apply to any new user account created by Entra ID.
  3. In Settings > Security, under Automatic provisioning, select SCIM; save changes, make a note of the displayed SCIM endpoint address: this will be your SCIM tenant URL in Entra ID.
  4. Still in Settings > Security, generate a provisioning token and make a note of the value.

In the Microsoft Entra admin center

Review Microsoft's latest Entra ID SCIM provisioning documentation before configuring Entra ID.

  1. Create a new Enterprise app registration using the Create your own application flow. This should be separate from the app registration Seq uses for SSO.
  2. Connect the app in Provisioning > New configuration, using the URL and token recorded when configuring Seq above. Test the connection.
  3. Configure attribute mappings:
    • Disable Provision Microsoft Entra ID Groups.
    • In Provision Microsoft Entra ID Users:
      • Keep userPrincipalName → userName as the matching attribute.
      • Keep displayName → displayName, mail → emails[type eq "work"].value, and the IsSoftDeleted/Switch(...) → active mapping.
      • Replace mailNickname → externalId with objectId → externalId, which is stable and unique.
      • Remove any other default mappings.
      • Remove any custom schema mappings.
    • In Target Object Actions:
      • Keep Create and Update.
      • Configure Delete according to your requirements.
  4. Configure settings:
    • Scope should be Sync only assigned users and groups.
  5. Assign users and groups.
  6. Test with one provision-on-demand user, examine the result in Seq and ensure the user can log in successfully; if user accounts are already present in Seq, this should be an existing user: ensure that, when they log in, existing signals, preferences, etc. are preserved.
  7. Start provisioning.

Existing Seq user accounts that hold permissions not assigned to the SCIM Provisioning API key will not be updatable through SCIM. You can temporarily assign additional permissions to the API key in order to link these accounts, or permanently grant all permissions to the key so that all Seq accounts can be managed.