> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blinq.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuring Entra ID

> Choose which attributes Blinq receives, set your provisioning scope, and assign your first users.

## 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.

<Warning>
  **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.
</Warning>

## 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

<Steps>
  <Step title="Provision a single test account">
    Assign one test user, then use **Provisioning → On-demand provisioning** to push them straight away.
  </Step>

  <Step title="Check the result in Blinq">
    Confirm the user and their card exist, with the attributes you expect.
  </Step>

  <Step title="Change an attribute">
    Update something in Entra — job title is easy to check — and confirm it flows through on the next sync.
  </Step>

  <Step title="Read the provisioning logs">
    Open **Provisioning → Provisioning logs** for per-user create and update results.
  </Step>

  <Check>
    **Your mappings are working.** You can now assign the rest of your users.
  </Check>
</Steps>

<Warning>
  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.
</Warning>

<hr />

### Need help?

For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me).