Subscribe to Help Center RSS FeedAfter you’ve authorized sync with Microsoft 365 (M365), you can choose the attributes that you want to import or export with Microsoft.
If you are trying to integrate with Entra ID, see Configure Real-time User Provisioning from Entra ID to JumpCloud.
Prerequisites:
- You must have sync authorized and active on the M365 directory. See M365/Entra ID Directory Sync
Attribute Data Flow
How does attribute data flow between M365 and JumpCloud after integration?
Data flow for synced user attributes:
- When you import a user from M365: If data exists for a user’s attributes in M365, only the following data is written to the equivalent user attributes in JumpCloud:
- First Name
- Last Name
- Username
- When you bind that user to M365 in JumpCloud: Attributes in M365 are automatically overwritten with data from JumpCloud. Further, any subsequent changes made to the user’s attributes in JumpCloud are automatically pushed to the corresponding attributes in M365
User Attribute Export
With the exception of several attributes that are selected by default, you can choose the user attributes you would like to export to M365. Selected attributes are automatically synced with M365. This means that after you export an attribute to M365, data for that attribute is sent from JumpCloud to M365. Likewise, if you choose to stop exporting data for an attribute, it is no longer synced with M365. Subsequent changes made to that attribute in JumpCloud are not exported to M365.
Take caution when selecting attributes to export. After you select an attribute to export to M365 it is immediately overwritten with data from JumpCloud, and you could potentially lose data stored for that attribute in M365. See Attribute Data below to learn about how attribute data is exported to M365.
Attributes that are always exported to M365:
| JumpCloud attribute | M365/Entra ID attribute |
|---|---|
| firstname | givenName |
| lastname | surname |
| password | password |
| Company Email | userPrincipalName |
| firstname + lastname | displayName |
*A user's first name and last name are exported together as M365's Display name field. If a user's first or last name is changed in JumpCloud, M365's Display name field updates with the new name value.
Attributes that can optionally be exported to M365:
| JumpCloud attribute | M365/Entra ID attribute |
|---|---|
| addresses.work.country | country |
| addresses.work.locality | city |
| addresses.work.postalCode | postalCode |
| addresses.work.region | state |
| addresses.work.streetAddress | streetAddress |
| alternateEmail | otherEmails |
| department | department |
| jobTitle | jobTitle |
| location | officeLocation |
| manager | manager |
| phoneNumbers.mobile.number | mobilePhone |
| phoneNumbers.work.number | businessPhone |
Attribute Data
The following table outlines how attribute data is exported from JumpCloud’s API and UI to M365’s API and UI. The attribute listed in the JumpCloud API Attribute Name column is exported to the attribute listed in the M365 API Attribute Name column. The attribute listed in the JumpCloud UI Attribute Name column is exported to the attribute listed in the M365 UI Attribute Name column. Be aware that M365 and Entra ID use multiple UI labels for the same data. The following M365 UI Attribute names represent what is used when an administrator adds or edits details for a user in M365.
See related API documentation: Manage the associations of an Office 365 instance.
User Attribute Syncing with M365
|
JumpCloud API Attribute Name |
M365 API Attribute Name |
JumpCloud UI Attribute Name |
M365 UI Attribute Name |
Notes |
|---|---|---|---|---|
| Calculated: First Name + Last Name | displayName | Calculated: First Name + Last Name | Display name | - |
| firstname | givenName | First Name | First name | - |
| lastname | surname | Last Name | Last name | - |
| password | password | Password | Password | - |
|
email OR alternateEmail |
userPrincipalName | Company Email | The userPrincipalName attribute can be used to specify an alternate email address for cross-domain application access. | |
| jobTitle | jobTitle | Job Title | Job title | - |
| department | department | Department | Department | - |
| location | officeLocation | Location | Office | - |
| addresses.work.streetAddress | streetAddress | Work Street Address | Street Address | - |
| addresses.work.locality | city | Work City | City | - |
| addresses.work.region | state | Work State | State or province | - |
| addresses.work.postalCode | postalCode | Work Postal Code | ZIP or postal code | - |
| addresses.work.country | country | Work Country | Country or region | - |
| phoneNumbers.work.number | businessPhone | Work Phone | Business Phone | - |
| phoneNumbers.mobile.number | mobilePhone | Personal Cell | Mobile Phone | - |
Selecting Attributes to Export
To select attributes to export to M365:
- Log in to the JumpCloud Admin Portal.
- Go to Directory Integrations > Cloud Directories.
- Select the M365 directory you want to select user attributes for.
- In the User Attributes Export section, select the non-default user attributes you want to export to M365. You can’t clear default user attributes.
- Click save.
After you configure user attributes to sync from JumpCloud to Microsoft, bind users to M365. See Giving JumpCloud Users Access to M365.
Directory Insights Events
Anytime you change the direction of an attribute, a Directory Insights event is generated.
Directory Insights events generated from attribution selections are:
- integrationattribute_exclude
- Generated when an attribute is set to “Exclude”.
- Ex: You change the Department attribute from “Import” to “Exclude”
- Generated when an attribute is set to “Exclude”.
- integrationattribute_include
- Generated when an attribute is set to “Import” or “Export”.
- Ex: You change the Department attribute from “Exclude” to “Import”
- Ex: You change the Department attribute from “Import” to “Export”
- Generated when an attribute is set to “Import” or “Export”.
These events will capture attribute ownership/direction changes, including the admin that made the change, and the directory integration in which the change occurred.
Step 2
In this Article
Learn More