Entra ID field reference - Blinq Docs

The Blinq gallery app in Entra pre-populates these mappings. You can remove any you don’t want to send, but you shouldn’t need to add any.

Attribute mapping

Entra attribute	SCIM field	Schema
`userPrincipalName`	`userName`	Core — required
`Switch([IsSoftDeleted], , "False", "True", "True", "False")`	`active`	Core — required
`displayName`	`displayName`	Core
`mail`	`emails[0].value`	Core
`givenName`	`name.givenName`	Core
`surname`	`name.familyName`	Core
`jobTitle`	`title`	Core
`telephoneNumber` / `mobile`	`phoneNumbers`	Core — map one, not both
`companyName`	`organization`	Enterprise extension
`department`	`department`	Enterprise extension

Enterprise-extension attributes are sent under urn:ietf:params:scim:schemas:extension:enterprise:2.0:User. To control which card fields the directory manages, see How provisioning works.

Profile photos

Blinq can sync profile images over SCIM, but Entra ID doesn’t expose them. Photos are added to a card by the card owner or a workspace admin.

Microsoft’s Blinq provisioning tutorial lists a broader attribute set than this page, including employee number and additional email and address types. This page is the authority on what Blinq does with an attribute once it arrives.

Need help?

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