Spencer integrates with Microsoft Entra ID via the Microsoft Graph API to synchronize user data. The table below outlines how user fields in Spencer map to attributes in Microsoft Graph. Fields marked with ❌ are currently not supported or unavailable.
Field Mapping Table
Spencer Field | Entra ID (MS Graph API) |
First Name |
|
Last Name |
|
Username |
|
E-mail (business) |
|
E-mail (private) | Only supported in guest-mode using security groups. See below. |
Company Join Date |
|
Department |
|
Company |
|
Date of Birth |
|
External ID |
|
Job Title |
|
Preferred Language |
|
Mobile (business) |
|
Mobile (private) | ❌ |
Phone (private) | ❌ |
Phone (business) |
|
Workstation |
|
Default Site |
|
Employee Type | ❌ |
Manager(s) | ❌ |
Division | ❌ |
Subdivision | ❌ |
Domain | ❌ |
Contract Type | (In development, currently supported via extension attributes) |
Alias | ❌ |
Country |
|
Region | ❌ |
Zone | ❌ |
Tags | (In development, will be supported via extension attributes) |
Mapping Possibilities Using Extension Attributes
It is possible to sync any of the 15 available extension attributes within Entra ID as long as they can be mapped to one of the default fields within Spencer.
⚠️ Note: Custom or free-text fields in Spencer are not currently supported.
Using Security Groups for Targeted Synchronization
You can assign different user groups in Entra ID to specific security groups to control how and to whom synchronization is applied. Please share the relevant security group IDs with our team to configure synchronization appropriately.
Benefits of Using Security Groups:
Gradual rollout of Spencer across teams or departments
Limit synchronization to a specific subset of users.
Furthermore, Spencer supports custom actions tailored to specific security groups. Here are a few example use cases:
Guest-mode: Guest users are users that do not have SSO accounts, for instance blue collar workers. Their user data is synchronized via the Graph API but their email address will be saved in the private email field to prevent exposure of private data within Spencer.
Define the authentication type for users of the security group
In Spencer there are 2 authentication types username_password and company_account (SSO accounts). The default when synchronizing users via the Graph API is company_account but based on the security group we can set the other type as well.
company_account– for SSO-enabled users (default for Graph sync)username_password– for non-SSO users (e.g., guest-mode)
Authentication type can be customized based on the user’s security group.
[IN DEVELOPMENT] User Tagging Based on Groups
Based on the group we can auto-tag users, these tags can then be used as parameters for creating specific user lists within Spencer.
If you have questions, please contact our support team at [email protected]