Skip to main content
SCIM provisioning is available on Enterprise plans, and is enabled per workspace. Talk to your account team to switch it on. Once it’s enabled, generating your credentials is self-serve in the Blinq dashboard.
SCIM provisioning connects Microsoft Entra ID to Blinq so your directory drives your team’s digital business cards. Microsoft Entra ID was previously called Azure Active Directory (Azure AD). If your team still calls it Azure AD, it’s the same product and these pages apply. Assign a user to Blinq in Entra and their account and card are created automatically, pre-filled from their directory profile. Update the directory and the card follows. Remove the user and their access is revoked. Blinq is a pre-built app in the Microsoft Entra gallery, so the attribute mappings arrive pre-populated.

​
Prerequisites

  • An Admin or Owner role in your Blinq workspace, on an Enterprise plan with SCIM enabled.
  • An Entra role that can manage enterprise applications: Application Administrator, Cloud Application Administrator, or Global Administrator.
  • No Microsoft developer account is required.
SAML SSO and SCIM provisioning are configured separately. These pages cover SCIM only.

​
Feature overview

Sync is one-way, from Entra ID to Blinq. Changes made in Blinq don’t flow back to your directory.

​
Documentation for Entra ID provisioning

Connecting Entra ID

Generate credentials in Blinq, add the gallery app, and confirm the connection.

Configuring Entra ID

Choose which attributes to send, set your scope, and assign your first users.

Configuring Blinq

Control templates and activation emails for provisioned users.

Field reference

Which directory attributes Blinq accepts, and which SCIM schema they belong to.

Troubleshooting

Connection failures, values that don’t appear, and provisioning that stops.

​
Need help?

For any questions or issues, contact Blinq support or email support@blinq.me.