Specify the precedence value from 0 through 99 (the lower the number, the higher the precedence). Make your selections for the Connected System, Connected System Object Type, and Metaverse Object Type fields. For example, the description can be based on what the objective of the rule is, and why it's needed. Provide your own description of the rule, so that future maintenance of the rule is easy. This means that the rule is a custom rule, and is an inbound rule from the Active Directory connector space to the metaverse. Launch the Synchronization Rules Editor, select Inbound as the direction, and select Add new rule.įollow your own naming convention to name the rule. For example, to have a new attribute flow from on-premises Active Directory to Azure Active Directory, create a new inbound sync rule. Add an inbound sync ruleĪn inbound sync rule means the source for the attribute is a connector space, and the target is the metaverse. If the extensions don't work for you, try adding two new sync rules, described in the following sections. If you find that an attribute is not flowing from your source directory to the target directory, use the Azure AD Connect sync: Directory extensions to fix this. You can do these without altering standard default rules.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |