This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 31%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
Can somebody explaine what is the join-type called "Sticky Join" in Azure AD Connect ISRs and OSRs
How is it different from regular Join ?
Thanks.
In Azure AD Connect, an "Sticky Join" is a feature that allows a device to be joined to on-premises Active Directory (AD) and Azure Active Directory (AAD) using the same device identity. This feature is typically used in scenarios where an organization has multiple forests or domains and wants to ensure that a device remains joined to the same on-premises AD domain after it is registered in AAD.
A "Sticky Join" is accomplished by creating a unique identifier for the device in AD and storing that identifier in AAD. This allows the device to be matched to the same AD domain when it is registered in AAD.
A regular join is a standard process of joining a device to a specific domain, it is not a feature of Azure AD Connect, it is just a normal way of joining a device to a specific AD domain, after that device should be registered in AAD using Azure AD Connect.
It's important to note that "Sticky Join" is not enabled by default in Azure AD Connect, it must be configured manually by an administrator.
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
Thanks @Santhi Swaroop Naik Bukke
I believe you are explaining some different stickyjoin.
I am talking about the link-type = sticky-join when you create Inbound Synchronization Rule in AAD-Connect Rule Editor.
You will find a drop-box to select the link-type.
I do not find the use-case when should I select sticky-join.
When you create an Inbound Synchronization Rule in the AAD Connect Rule Editor, the "link-type" option allows you to specify how objects in your on-premises Active Directory (AD) will be linked to objects in Azure Active Directory (AAD).
The "sticky-join" link-type option is used to ensure that the same on-premises AD object is always linked to the same AAD object, even if the matching attributes (such as the user's email address or UPN) change. This can be useful in scenarios where you have multiple domains or forests that are being federated to AAD, and you want to ensure that the same user object is not accidentally created multiple times in AAD.
When you choose "sticky-join" option, AAD Connect will create a unique identifier called an "ImmutableID" for each AD object and will use this ID to link the objects together. The ImmutableID is a string that is derived from the objectGUID attribute of the AD object and is stored in the AAD object's msDS-ConsistencyGuid attribute. This allows AAD Connect to link the two objects together even if the matching attributes change.
It's important to note that once you choose "sticky-join" link-type, it can't be changed later. So it's important to decide on the correct link-type before you begin the synchronization.
Thanks @Santhi Swaroop Naik Bukke for your prompt answer.
I am not sure why did you bring the ImmutableID and msDS-ConsistencyGuid
They are always used WITHOUT stikcy-join. for eg., msDS-ConsistencyGuid is the sourc-anchor so that we can mvoe the user object from one domain to other.
My point is how can we protect the deletion of metaverse object with the help of sticky-join.
A metaverse object remains as long as there is one sync rule in scope with Link Type set to Provision or StickyJoin. A StickyJoin is used when a Connector is not allowed to provision a new object to the metaverse, but when it has joined, it must be deleted in the source before the metaverse object is deleted.
I am not able to interpret and simulate above statement. If you could put some concrete example , I have a full set up in my lab and I can try to replicate it.
Thanks.