Skip to main content

​
Review the attribute mappings

Open Provisioning → Mappings → Provision Microsoft Entra ID Users. The gallery app pre-populates these mappings. Delete any attribute you don’t want sent to Blinq.
Check what your directory is putting in the phone fields. Map only one of telephoneNumber and mobile to avoid stale-value conflicts. Check whether a fax number is present too — a fax number in the directory feed can end up on a card where a phone number was expected.

​
Set your provisioning scope

Under Settings, choose Sync only assigned users and groups. This lets you pilot with a small group before rolling out more widely. Set Provisioning Status to On and save.

​
Assign users

On the app’s main page, open Users and groups → Add user/group and assign the people you want provisioned. Assigned users are picked up on the next provisioning cycle, up to 40 minutes, or immediately if you use on-demand provisioning.

​
Validate with a test user

1

Provision a single test account

Assign one test user, then use Provisioning → On-demand provisioning to push them straight away.
2

Check the result in Blinq

Confirm the user and their card exist, with the attributes you expect.
3

Change an attribute

Update something in Entra — job title is easy to check — and confirm it flows through on the next sync.
4

Read the provisioning logs

Open Provisioning → Provisioning logs for per-user create and update results.
Use a dedicated test account rather than a real employee’s, and turn activation emails off in Blinq while you’re testing so test users aren’t emailed.

​
Need help?

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