Completed-transient-objects during full synchronization on AAD connector

Usually, transient means when an object is imported to the connector space that has the same distinguished name attribute as an existing connector space object but a different anchor attribute, the existing connector space object is marked as transient.

If more objects are imported with the same distinguished name and a different anchor attribute, each one will become transient. Only the last object imported with that distinguished name will be non-transient. Objects marked as transient remain in the connector space until they are updated with a new distinguished name or are deleted from the connector space during a full import.

In this case, AD connect sync engine assumes that because the object does not exist in the connected data source, it was deleted, therefore it will be deleted in the connector space.

In your case you can initiate a full sync through PowerShell so that all the sync cycles get completed in an order. This will fix the issue.

Connector space in AAD connect

In Azure Active Directory (AAD) Connect, the connector space refers to a specific data structure that holds the information about the objects being synchronized between your on-premises Active Directory and Azure Active Directory. It acts as an intermediary space for managing and processing directory data during synchronization.

Key Features of Connector Space

1. Data Storage:
   • The connector space stores the data for each connected directory. This includes user accounts, groups, and other directory objects that are either imported from the on-premises Active Directory or created in Azure AD.
2. Synchronization:
   • During the synchronization process, AAD Connect pulls data from the on-premises Active Directory into the connector space. It then processes this data before exporting it to Azure AD.
3. Object Management:
   • Each object in the connector space has a unique identifier, which is used to track its state and changes. This allows AAD Connect to manage updates, deletions, and new objects efficiently.
4. Change Tracking:
   • AAD Connect tracks changes made to objects in the on-premises Active Directory. When changes occur, they are reflected in the connector space, enabling the synchronization process to detect and apply updates to Azure AD.
5. Conflict Resolution:
   • The connector space also plays a role in conflict resolution during synchronization. If there are conflicts between on-premises and Azure AD data, AAD Connect uses rules defined in the synchronization process to determine how to resolve these conflicts.

Azure AD Connect Sync Engine

Azure AD Connect has an important component which helps it to work. You can say this component is the heart of Azure AD Connect. This component is called Sync Engine. Sync Engine has 4 components:

1. Connected Data Source or connected directories
2. Connectors
3. Connector Space
4. Metaverse

These 4 components help sync engine to perform all the activities. If you are synchronizing an object from Active Directory to Azure Active Directory, or if passwords are getting synchronized from Azure Active Directory to on-premises, all these activities are performed by these 4 components. So let’s understand each component in detail.

Connected Data Source: In Azure AD Connect, connected data source can be any data repository that organizes data in a database, like Active Directory or SQL server. In a standard Azure AD Connect configuration, connected data sources are Active Directory and Azure Active Directory. If you are using SQL server in your on-premises, you can use SQL server database as a connected data source in Azure AD Connect. So in nutshell, connected data source or connected directories are a storage space where your objects are stored. For example, Active Directory, Azure Active Directory or SQL server.

Connectors: The second component of sync engine is connectors. Each connected data source has a dedicated connector. Connectors are a medium through which data flows from connected data sources to connector space, or from connector space to another connected data sources. At one time data can flow in one direction only. That means at one time data can flow either from Active Directory to Azure Active Directory or from Azure Active Directory to on-premises Active Directory.

Connector Space: The next component of sync engine is connector space. Connector space stores a replica of all objects that are present within connected data sources. For example, if we have 2 users in active directory, connector space will store these objects and their attributes. If we make any changes in these 2 users within Active Directory, these changes will be updated within connector space as well. If we add another user in Active Directory, during sync cycle connector space will copy the new object and will store this object and its attributes. With the help of connector space, sync engine evaluates whether the data has already been synchronized.

Metaverse: The fourth component of sync engine is Metaverse. Metaverse is a storage area that provides a global view of both connectors. It shows what changes are picked from Active Directory, and what changes are going to be exported to Azure Active Directory.

So, that’s all in this blog. I will meet you soon with next stuff. Have a nice day!!!

Guys please don’t forget to like and share the post. Also join our WindowsTechno Community and where you can post your queries/doubts, and our experts will address them.

You can also share the feedback on below windows techno email id.

If you have any questions, feel free to contact us on admin@windowstechno.com also follow us on facebook@windowstechno to get updates about new blog posts.