It’s all about the Hybrid Azure AD and the Azure Active Directory Connector (AADC) sync here.
If you are leveraging an AADC server to sync your accounts to Azure AD, one of the most important technical properties is the source anchor. This is the value that matches the on-prem account with the cloud account. The nature of this match was discussed here in detail in another blog post: The ImmutableID Match […]
In one of my older posts, I explained the great importance of the ImmutableID attribute for the AADC sync: The ImmutableID Match in AADC environments. So you learned that in the ImmutableID property, the hybrid sync stores a value from the on-premises AD object to ensure the match between the local object and the cloud […]
Most Azure AD tenants are synchronized from an on-premises Active Directory environment. The AADC server synchronizes accounts from different organizational units (OUs), different domains – possibly even from different forests. However, you lose all hierarchical information up there – Azure AD stores all accounts in the same flat structure. So, wouldn’t it be nice to […]
This is about environments where an AADC (Azure Active Directory Connector) server syncs a local AD to AzureAD / O365. There are matching rules and key attributes that handle the sync relationship between a cloud object and it’s corresponding local AD object. AADC does its job fairly well and you don’t need to care about […]
The Azure AD Connector (AADC) syncs user objects between local ADs and the Azure AD / O365. In most situations, the user sync uses the GUID (Global Unique Identifiers) values as a matching attribute that connects the local and the cloud account. Just because the GUID is globally unique and it (usually) does not change […]