![]() ![]() ![]() Again, the installation wizard does this configuration for you. For example, the sAMAccountName attribute must be included in the attribute inclusion list to export a user object to Active Directory because all user objects in Active Directory must have a sAMAccountName attribute defined. To export objects to a connected data source, the attribute inclusion list must include at least the minimum attributes required to create a specific object type in a connected data source. When you use the Azure AD Connect installation wizard, these settings are configured for you. These settings can be changed any time in response to changes to your business rules. The next step is to select the attributes to synchronize, which is known as an attribute inclusion list. Specifying the object types defines the scope of objects that are included in the synchronization process. To configure a Connector, you specify the object types that you want to synchronize. The direction can be different for different objects and for different attributes. In other words, a Connector can be configured to allow data to flow from the connected data source to sync engine or from sync engine to the connected data source, but only one of those operations can occur at any one time for one object and attribute. The following illustration shows how a Connector connects a connected data source to the sync engine.ĭata can flow in either direction, but it cannot flow in both directions simultaneously. It is also possible to add a custom Connector using the extensible connectivity framework. The Connector translates a required operation into the format that the connected data source understands.Ĭonnectors make API calls to exchange identity information (both read and write) with a connected data source. Each type of connected data source has a specific Connector. The sync engine encapsulates interaction with a connected data source within a module called a Connector. The data repositories that are synchronized by sync engine are called connected data sources or connected directories (CD). Every data repository that organizes its data in a database-like format and that provides standard data-access methods is a potential data source candidate for the sync engine. The sync engine processes identity information from different data repositories, such as Active Directory or a SQL Server database. This integrated view is determined by the identity information retrieved from connected data sources and a set of rules that determine how to process this information. The sync engine creates an integrated view of objects that are stored in multiple connected data sources and manages identity information in those data sources. It is however not a requirement to know the details of this topic to be successful in making customizations to Azure AD Connect sync (called sync engine in this topic). If you are new to synchronization, then this topic is for you. If you are familiar with any of these earlier technologies, the content of this topic will be familiar to you as well. Azure AD Connect sync is the evolution of these technologies. In many aspects, it is similar to its predecessors MIIS 2003, ILM 2007, and FIM 2010. This topic covers the basic architecture for Azure AD Connect sync. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |