지금 지원 담당자와 채팅
지원 담당자와 채팅

On Demand Migration Current - Active Directory GAL Sync Setup Quick Start Guide

How to create a Cloud to Cloud Target to Source template

  1. Navigate to Templates.
  1. Click New.
  2. Enter the Name and Description of the template.
  3. In our example, we will name our template “Cloud to Cloud GAL Sync Target to Source”. Click Next.
  4. Click Cloud as the source environment type. Click Next.
  5. Click Cloud as the target environment type. Click Next.
  6. Set CREATE NEW USERS AS = CONTACT
  7. Set UPDATE CREATED USERS= ENABLE
  8. Set UPDATE MATCHED USERS= DISABLE
  9. Click Next.
  10. Set CREATE GROUPS AS = SKIP
  11. Set UPDATE CREATED GROUPS = DISABLE
  12. Set UPDATE MATCHED GROUPS = ENABLE
  13. Click Next.
  14. Set CREATE OFFICE365 GROUPS AND TEAMS AS = SKIP
  15. Set UPDATE CREATED CONTACTS = DISABLE
  16. Set UPDATE MATCHED CONTACTS = DISABLE
  17. Click Next.
  18. Set CREATE NEW CONTACTS AS = DO NOT CREATE
  19. Set UPDATE CREATED CONTACTS = DISABLE
  20. Set UPDATE MATCHED CONTACTS = DISABLE
  21. Click Next.
  22. Enter a default password. Click Next.
  23. Under mappings, we need to make several modifications to the default template in order to make the MailContact to be compatible with Tenant to Tenant.
    • Select mapping for ‘EmailAddresses’ and double click, enter the below expression under value field.

      GetProxyAddresses(null, null, prefix(Result("WindowsEmailAddress"), "SMTP:"), prefix(LegacyExchangeDN, "x500:"))

    • Select Contact as the Target Object Type
    • Select mapping for ‘CustomAttribute1 and double click, enter the below expression under value field.

      "s.WindowsEmailAddress"

    • Select All as the Target Object Type
  24. Leave rest of the mappings as default.
  25. Click Next.
  26. Click Finish.

How to create a Local to Local template

  1. Navigate to Templates.
  1. Click New.
  1. Enter the Name and Description the template.
  2. In our example, we will name our template “Local to Local GAL Sync”. Click Next.
  3. Click Local as the source environment type. Click Next.
  4. Click Local as the target environment type. Click Next.
  5. Set CREATE NEW USERS AS = CONTACT
  6. Set UPDATE CREATED USERS= ENABLE
  7. Set UPDATE MATCHED USERS= DISABLE
  8. Set IF TARGET ADDRESS EXISTS setting as OVERWRITE ONCE.
  9. Click Next.
  10. Set CREATE GROUPS AS = SKIP
  11. Set UPDATE CREATED GROUPS = DISABLE
  12. Set UPDATE MATCHED GROUPS = DISABLE
  13. Click Next.
  14. Set CREATE NEW CONTACTS AS = DO NOT CREATE
  15. Set UPDATE CREATED CONTACTS = DISABLE
  16. Set UPDATE MATCHED CONTACTS = DISABLE
  17. Click Next.
  18. Set CREATE NEW DEVICES AS = SKIP
  19. Set UPDATE CREATED CONTACTS = DISABLE
  20. Set UPDATE MATCHED CONTACTS = DISABLE
  21. Click Next.
  22. Enter a default password. Click Next.
  23. Leave SYNCHRONIZE SID HISTORY unchecked. Click Next.
  24. Under mappings, we need to make several modifications to the default template in order to make the MailContact to be compatible with Tenant to Tenant.  
    • Select mapping for ‘ExtensionAttribute1 and double click, enter the below expression under value field.

      "s.mail"

    • Select Contact as the Target Object Type
    • Select mapping for ‘DistinguishName and double click, enter the below expression under value field.

      GetDn(NewGuid())

    • Select mapping for ‘targetAddress’ and double click, enter the below expression under value field.

      prefix(S.mail, "SMTP:")

    • Select mapping for ‘msExchRecipientDisplayType’ and double click, enter the below expression under value field.

      "6"

    • Select mapping for ‘msExchRecipientTypeDetails’ and double click, enter the below expression under value field.

      "64"

  25. Leave rest of the mappings as default or update them based on your project needs.
  26. Click Next.
  27. Click Finish.

Setup Workflow

Follow these steps to create one (1) new workflow for reading, matching, staging and writing data. 

How to create a one-way sync workflow for Cloud to Cloud

  1. Navigate to Workflows.
  2. Click New.
  3. Enter the Name and Description for the template. Click Next.
  4. Select the all four environments (Cloud and Local environments per each hybrid tenant) created previously. Click Next.
  5. Select ONE-WAY SYNC. Click Next.
  6. The workflow task wizard opens. It is a pre-configured set of workflow steps to facilitate the flow of objects and attributes between your directories.

    Step 1: READ FROM

    1. Click Select.
    2. Select all four environments created previously.
    3. Click OK.

    Step 2: MATCH OBJECTS: SOURCE CLOUD TO TARGET CLOUD

    • In this step you decide on how to match existing objects across your hybrid tenant directories
    • Matching is conducted by pairing sets of attributes to find corresponding objects
    • The environments may already have some attributes that can be used to find similar objects between the different directories, or you may need to set some to ensure accurate matching
    • For the purpose of GAL Sync, it is most important that email addresses do not conflict before attempting to create new objects in either environment
    1. Click Select.

    2. Select your source cloud environment from the drop-down menu.
    3. Select your target cloud environment from the drop-down menu.
    4. Choose your first attribute pairings. For example, we will use WindowsEmailAddress for our first match criteria.
    5. Choose the WindowsEmailAddress attribute for the source and target fields.
    6. To add more attribute pairs, click Add Attribute.
    7. Additional pairings are evaluated as “OR” conditions. After the first match is found, the additional pairings are not assessed.
    8. Let's add three additional attribute pairings to our criteria
      1. UserPrincipalName – UPN was added to ensure uniqueness of the local part of the address string. If creating new mail-enabled users in a destination directory it will be important to define any UPN conflicts that may exist
      2. ExternalEmailAddress – This attribute was added to ensure no existing MEUs or Mail Contacts have existing objects with the same external or target address
      3. WindowsEmailAddress to CustomAttribute1 – This matching pair is needed to create matching records for new objects created by Directory Sync. 
    9. Match Across all object types - select this option to ensure the workflow is evaluating conflicts regardless of the object type because in two-way GAL sync there may be instances where this condition is true, and we want to ensure you have identified these matches before deciding to create new objects or keep the matche.
    10. There is no need in this guide to add another pair, so click OK to close this configuration.

    Step 3: MATCH OBJECTS: TARGET CLOUD TO SOURCE CLOUD

    1. Drag another Match Objects workflow task from the left panel to the right under the Match Object task mentioned above. Click Select.

    2. Select your target cloud environment from the drop-down menu on the left as target will now become the source in a bi-directional setup.
    3. Select your source cloud environment from the drop-down menu on the right as source will now become the target in a bi-directional setup.
    4. Choose your first attribute pairings. For example, we will use WindowsEmailAddress for our first match criteria.
    5. Choose the WindowsEmailAddress attribute for the source and target fields.
    6. To add more attribute pairs, click Add Attribute.
    7. Additional pairings are evaluated as “OR” conditions. After the first match is found, the additional pairings are not assessed.
    8. Let's add three additional attribute pairings to our criteria
      1. UserPrincipalName – UPN was added to ensure uniqueness of the local part of the address string. If creating new mail-enabled users in a destination directory it will be important to define any UPN conflicts that may exist
      2. ExternalEmailAddress – This attribute was added to ensure no existing MEUs or Mail Contacts have existing objects with the same external or target address
      3. WindowsEmailAddress to CustomAttribute1 – This matching pair is needed to create matching records for new objects created by Directory Sync. 
    9. Match Across all object types - select this option to ensure the workflow is evaluating conflicts regardless of the object type because in two-way GAL sync there may be instances where this condition is true, and we want to ensure you have identified these matches before deciding to create new objects or keep the matches.
    10. There is no need in this guide to add another pair, so click OK to close this configuration.

    Step 4: MATCH OBJECTS: SOURCE LOCAL TO TARGET LOCAL

    1. Drag another Match Objects workflow task from the left panel to the right under the Match Object task mentioned above. Click Select.

    2. Select your source local environment from the drop-down menu on the left.
    3. Select your target local environment from the drop-down menu on the right.
    4. Choose your first attribute pairings, we will use mail for our first match criteria
    5. Choose the mail attribute for the source and target fields
    6. To add more attribute pairs, click the Add Attribute button
    7. Additional pairings are evaluated as “OR” conditions. After the first match is found, the additional pairings are not assessed.
    8. In our case we are adding two additional attribute pairings to our criteria
      • mail to targetAddress – This matching pair created to ensure the system can match onto existing mail contacts in the target with targetAddress pointed to the source mail attribute.
      • mail to extensionattribute1 – This matching pair is needed to create matching records for new objects created by Directory Sync.  
    9. Match Across all object types - select this option to ensure the workflow is evaluating conflicts regardless of the object type because in two-way GAL sync there may be instances where this condition is true, and we want to ensure you have identified these matches before deciding to create new objects or keep the matches.
    10. There is no need in this guide to add another pair, so click OK to close this configuration.

    Step 5: MATCH OBJECTS: TARGET LOCAL TO SOURCE LOCAL

    1. Drag another Match Objects workflow task from the left panel to the right under the Match Object task mentioned above. Click Select.

    2. Select your target local environment from the drop-down menu on the left as target will now become the source in a bi-directional setup.
    3. Select your source local environment from the drop-down menu on the right as source will now become the target in a bi-directional setup.
    4. Choose your first attribute pairings, we will use mail for our first match criteria
    5. Choose the mail attribute for the source and target fields
    6. To add more attribute pairs, click the Add Attribute button
    7. Additional pairings are evaluated as “OR” conditions. After the first match is found, the additional pairings are not assessed.
    8. In our case we are adding two additional attribute pairings to our criteria
      • mail to targetAddress – This matching pair created to ensure the system can match onto existing mail contacts in the target with targetAddress pointed to the source mail attribute.
      • mail to extensionattribute1 – This matching pair is needed to create matching records for new objects created by Directory Sync.  
    9. Match Across all object types - select this option to ensure the workflow is evaluating conflicts regardless of the object type because in two-way GAL sync there may be instances where this condition is true, and we want to ensure you have identified these matches before deciding to create new objects or keep the matches.
    10. There is no need in this guide to add another pair, so click OK to close this configuration.

    Step 6: STAGE DATA: SOURCE CLOUD TO TARGET CLOUD

    1. Click Select to configure the first STAGE DATA workflow task for your Source Cloud to Target Cloud synchronization rule.
    2. Select the “Cloud to Cloud GAL Sync Source to Target” template. Click Next.
    3. Select the source cloud environment as your source. Click Next.
    4. Select the target cloud environment as your target. Click Next.
    5. Select the default target domain name. Click Next.
    6. Configure any Stage Data filter you like, it is highly recommended to setup filter to limit the scope to perform a test on the first sync as part of the validation.  Click Next.
    7. Click Finish.

    Step 7: STAGE DATA: TARGET CLOUD TO SOURCE CLOUD

    1. Drag another Stage Data workflow task from the left panel to the right under the PREVIOUS Stage Data task. Click Select to configure the second STAGE DATA workflow task for your target Cloud to source Cloud synchronization rule.
    2. Select the “Cloud to Cloud GAL Sync Source to Target” template. Click Next.
    3. Select the source cloud environment. Click Next.
    4. Select the target cloud environment. Click Next.
    5. Select the default target domain name. Click Next.
    6. Configure any Stage Data filter you like, it is highly recommended to setup filter to limit the scope to perform a test on the first sync as part of the validation.  Click Next.
    7. Click Finish.

    Step 8: STAGE DATA: SOURCE LOCAL TO TARGET LOCAL

    1. Drag another Stage Data workflow task from the left panel to the right under the Stage Data task mentioned above. Click Select to configure the third STAGE DATA workflow task for your source local to target local synchronization rule.
    2. Select the “Local to Local GAL Sync” template. Click Next.
    3. Select the source local environment. Click Next.
    4. Select the target local environment. Click Next.
    5. Select the default target domain name. Click Next.
    6. Click ADD OUS in the Select the source Organizational Units step. In the OU pop-up window, select the OU that will be in-scope, check the INCLUDE ALL SUB OUS checkbox. Click OK to close the pop-up.

    7. Configure any Stage Data filter you like by double click on the OU in the OUs list, it is highly recommended to setup filter to limit the scope to perform a test on the first sync as part of the validation.  Click Next.
    8. Select the default OU for newly created objects for Users, Groups, Contacts, and Devices.  In our case, we can select the same OU for all object types as we are only syncing user as contact.

    9. Click Finish.

    Step 9: STAGE DATA: TARGET LOCAL TO SOURCE LOCAL

    1. Drag a Stage Data workflow task from the left panel to the right under the Stage Data task mentioned above.  Click Select to configure the fourth STAGE DATA workflow task for your target local to source local synchronization rule.
    2. Select the “Local to Local GAL Sync” template. Click Next.
    3. Select the target local environment as your source. Click Next.
    4. Select the source local environment as your target. Click Next.
    5. Select the default target domain name. Click Next.
    6. Click ADD OUS in the Select the source Organizational Units step. In the OU pop-up window, select the OU that will be in-scope, check the INCLUDE ALL SUB OUS checkbox. Click OK to close the pop-up.

    7. Configure any Stage Data filter you like by double click on the OU in the OUs list, it is highly recommended to setup filter to limit the scope to perform a test on the first sync as part of the validation.  Click Next
    8. Select the default OU for newly created objects for Users, Groups, Contacts, and Devices.  In our case, we can select the same OU for all object types as we are only syncing user as contact.

    9. Click Finish.

    Step 9: WRITE TO

    1. Click Select.
    2. Ensure all four environments are selected. Click OK.
  7. When you are done with the workflow wizard, you are ready to schedule this workflow.
    1. Click Next.
    2. Select Manual for now and we can setup a sync schedule once the test sync has completed. 
    3. Click Next.
  8. You can set up workflow alerts if needed. For now, click SKIP.
    1. Click Finish.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택