This article lists the attributes that are used by Active Directory synchronization in your organizational account such as Office 365, Windows Azure, and Windows Intune.
This contents of this article are as follows:
The following table lists the attributes that are synced from the on-premises AD DS to Windows Azure AD.
Be aware that objects must contain values in the following attributes to be considered for sync:
↑ Back to top
The following table lists the synced attributes that are written back to the on-premises AD DS from Office 365 in an Exchange hybrid deployment scenario.
These attributes are written back only if Exchange federation for the hybrid deployment is enabled for the organization.
This section contains info about how directory synchronization determines what isn't synced from the on-premises environment to Windows Azure AD.
Any object is filtered if:
Contact objects are filtered if:
SecurityEnabledGroup objects are filtered if:
MailEnabledGroup objects are filtered if:
User objects are filtered if:
The article mentions account with sAMaccount name 'MSOL_AD_Sync'.
We dont see this account create through our DirSync installation.
Has this been replaced by MSOL_XXXXXXXXXXXX account?
Yes, newer versions of DirSync appliance changed the account from MSOL_AD_Sync to MSOL_<identifier>
This article mentions that the Company attribute is synchronized. However, I'm not able to see it on my O365 user profile attributes after the DirSync tool runs (although I can see other attributes such as Department)
The SamAccountName value of mail-enabled groups is indeed read by the DirSync tool. The technical article is incorrect.