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

# Troubleshooting Entra ID provisioning

> Connection failures, values that don't reach the card, and provisioning that stops unexpectedly.

| Symptom | Cause and fix |
| - | - |
| Test Connection fails | Wrong tenant URL or token. Regenerate the token in Blinq and re-enter both values in Entra. |
| Provisioning job stuck in Quarantine | The token has expired or been revoked. Generate a new token in Blinq and update it in Entra. |
| Provisioning stopped after a staff change | The token belongs to the admin who created it. If that admin was deactivated or lost the admin role, a current workspace admin must generate a new token and re-enter it. |
| A user isn't appearing in Blinq | The sync cycle hasn't run yet. Use on-demand provisioning to push them immediately, and check that Provisioning Status is **On**. |
| A phone number won't update | Both `mobile` and `telephoneNumber` are mapped to the same card field. Entra only re-sends on a real source change, so remove one mapping and make a small edit to the one you keep. |
| A directory value isn't on the card | Check three things in order: the attribute has an active mapping in Entra, the applied team template has a field for it, and the field on the card is still **linked**. A field that was hand-edited in Blinq becomes unlinked and stops accepting directory updates. |
| A field shows as Linked but the value is stale | Contact Blinq support with the user's email address and the field. Don't assume the change didn't arrive from your directory — it may have reached Blinq without reaching the card. |
| The wrong number appears on a card | Check whether your directory is populating a fax number. If it is, remove that mapping in Entra. |
| A template didn't apply | Set the default template under **Team Card Provisioning** card settings. Template choices made during a bulk-invite CSV upload don't carry over to SCIM-provisioned users. |
| A user signed in first and landed on a Free personal account | Contact Blinq support for an account merge — don't delete the account. Enforced SSO prevents this by directing domain users into your workspace. |

## Reading the provisioning logs

In Entra, open **Enterprise applications → Blinq → Provisioning → Provisioning logs**. Logs show each user operation, whether it succeeded, and which attributes were sent.

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


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.