![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/note-icon.png\"){kind=icon}
<\/p><\/div>
If you are trying to integrate with Entra ID, see Configure Real-time User Provisioning from Entra ID to JumpCloud<\/a>.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n Prerequisites<\/strong>:<\/p>\n\n\n\n How does attribute data flow between M365 and JumpCloud after integration?<\/strong><\/p>\n\n\n\n Data flow for synced user attributes:<\/p>\n\n\n\n With the exception of several attributes that are selected by default, you can choose the user attributes\u00a0you 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.<\/p>\n\n\n\n Take caution when selecting attributes to export. After you select an attribute to export to M365 it is\u00a0immediately\u00a0overwritten<\/strong>\u00a0with data from JumpCloud, and you could potentially lose data stored for that attribute in M365. See\u00a0Attribute Data<\/a>\u00a0below to learn about how attribute data is exported to\u00a0M365.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n Attributes that are\u00a0always<\/strong>\u00a0exported to M365:<\/p>\n\n\n\n *\u200bA user’s first name and last name are exported together as M365’s\u00a0Display name<\/strong>\u00a0field. If a user’s first or last name is changed in JumpCloud, M365’s\u00a0Display name<\/strong>\u00a0field updates with the new name value.<\/p>\n\n\n\n Attributes that can\u00a0optionally\u00a0<\/strong>be\u00a0exported to M365:<\/p>\n\n\n\n The following table outlines how attribute data is exported from JumpCloud\u2019s API and UI to M365\u2019s 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.<\/p>\n\n\n\n\n
Attribute Data Flow<\/strong><\/h2>\n\n\n\n
\n
\n
User Attribute Export<\/strong><\/h2>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/warning-icon.png\"){kind=icon}
<\/p><\/div>\n\n
\n \n JumpCloud attribute <\/th>\n \n M365\/Entra ID attribute <\/th>\n <\/tr>\n \n \n firstname <\/td>\n \n givenName <\/td>\n <\/tr>\n \n \n lastname <\/td>\n \n surname <\/td>\n <\/tr>\n \n \n password <\/td>\n \n password <\/td>\n <\/tr>\n \n \n Company Email <\/td>\n \n userPrincipalName <\/td>\n <\/tr>\n \n \n firstname + lastname <\/td>\n \n displayName <\/td>\n <\/tr>\n <\/table>\n<\/div><\/div>\n\n\n\n \n\n
\n \n JumpCloud attribute <\/th>\n \n M365\/Entra ID attribute <\/th>\n <\/tr>\n \n \n addresses.work.country <\/td>\n \n country <\/td>\n <\/tr>\n \n \n addresses.work.locality <\/td>\n \n city <\/td>\n <\/tr>\n \n \n addresses.work.postalCode <\/td>\n \n postalCode <\/td>\n <\/tr>\n \n \n addresses.work.region <\/td>\n \n state <\/td>\n <\/tr>\n \n \n addresses.work.streetAddress <\/td>\n \n streetAddress <\/td>\n <\/tr>\n \n \n alternateEmail <\/td>\n \n otherEmails <\/td>\n <\/tr>\n \n \n department <\/td>\n \n department <\/td>\n <\/tr>\n \n \n jobTitle <\/td>\n \n jobTitle <\/td>\n <\/tr>\n \n \n location <\/td>\n \n officeLocation <\/td>\n <\/tr>\n \n \n manager <\/td>\n \n manager <\/td>\n <\/tr>\n \n \n phoneNumbers.mobile.number <\/td>\n \n mobilePhone <\/td>\n <\/tr>\n \n \n phoneNumbers.work.number <\/td>\n \n businessPhone <\/td>\n <\/tr>\n <\/table>\n<\/div><\/div>\n\n\n\n Attribute Data<\/strong><\/h2>\n\n\n\n