• State Verified Answer
  • Replies 8 replies
  • Subscribers 61 subscribers
  • Views 3037 views
  • Users 0 members are here
Options
Related

AR Azure/O365 BackSync is disabled?

Aidar.Karabalaev
over 3 years ago

Is it required to have scheduled and running AR Sync Azure/O365 BackSync (GUIDs etc.) from AAD/O365 to onprem\AD objects (VAs) with AADConnect in place (AD/O365 Hybrid Mode)?

Is it supported scenario for AR by design?

IF AR BackSync Scheduled job is required THEN for which supported scenario:

1) Non Federated Domain (AADconnect is not configured)
2) Federated Domain (AADconnect and ADFS is configured)
3) Synchronized Identity Domain (AADconnect is configured)

(*) My customer got AR 7.4.3 with (3) Synchronized Identity Domain (AADconnect is configured) and AR BackSync jobs are disabled (not scheduled) at all, and it seems like there is no problem, so far.

thank you,

Aidar K.

Parents
  • 0 over 3 years ago

    Yes, it's a requirement in a hybrid environment with AADConnect in play. It's most important in a Federated or Synchronized Tenant configuration, where most or all Azure-enablement is performed by AADConnect.

    Even in a Non-Federated Tenant, an administrator might be creating objects manually. I'd still recommend the Back Sync be configured to account for that.

Reply
  • 0 over 3 years ago

    Yes, it's a requirement in a hybrid environment with AADConnect in play. It's most important in a Federated or Synchronized Tenant configuration, where most or all Azure-enablement is performed by AADConnect.

    Even in a Non-Federated Tenant, an administrator might be creating objects manually. I'd still recommend the Back Sync be configured to account for that.

Children
No Data