Chat now with support
Chat with Support

Binary Tree Power365 Current - Help Center

Help Center Home Power365 Platform Tenant-to-Tenant Directory Sync Migration for Active Directory Support

Migration How-Tos

Power365 Migrations  

 

OneDrive and OneNote  

 

Office 365 Groups and Microsoft Teams  

Diagrams

Integration Project Phases  

The following diagrams (PDFs) illustrate the 6 typical phases of a Power365 Premium Integration Project. Each topic is summarized in 6 steps.

 

Integration Mail Flow  

 

Email Rewrite Services (ERS)  

During an Premium Integration Project, Domain Sharing may be used. These two diagrams outline those services and how they operate.

 

ERS Configurations  

 

Day 1 Mail Flow  

 

Day 2 Mail Flow  

Directory Sync

Requirements

Binary Tree Power365 Directory Sync is built with Microsoft Azure. Our Software-as-a-Service (SaaS) platform is designed to handle a variety of directory synchronization scenarios to meet your coexistence and collaboration needs.

Power365 Directory Sync can manage simple AD to AD, Cloud to Cloud, and more complex scenarios including combinations of local and cloud mixed environments.

 

What is required to get Power365 Directory Sync set up?  

You will need 2 items to get started with setting up Directory Sync.

  1. The authorized account(s) that allow changes to your local and/or cloud directories
  2. At least one (1) local on-premises server to host the local agent (if applicable)

The following information provides details around the specific component requirements.

 

Agents  

Power365 Directory Sync is a 100% SaaS platform but to commit changes to on-premises directories (if applicable) such as Active Directory, a local agent must be installed and configured.

You will need at least one Power365 Directory Sync Agent installed per forest (environment). You may have up to five agents per forest. Adding more agents can offer limited fault-tolerance and can improve synchronization throughput, especially for near real-time password synchronization.

Please Note: Directory Sync agents do not function with a proxy server configuration on the agent host.

Important Tip: If you are only connecting to Azure AD, local agents are not required.

 

Hardware  

This local agent must meet the following minimum requirements:

  • At least one (1) Windows Server 2012 R2, 2016 or 2019
  • Additional Windows servers may be deployed. Limit to 5.
  • CPU: 4 Cores
  • Memory: 4GB Free
  • Disk: 40GB Free Disk Space excluding Operating System.

Important Tip: Do not install any local agents on AD domain controllers in a production environment.

 

Software  

This local agent must meet the following minimum requirements:

  • Windows Server 2012 R2, 2016 or 2019
  • .NET 4.7.2 (will automatically be installed unless already present)
  • TLS 1.2 or higher

 

Domain and Forest Functional Levels  

  • 2012 R2 or 2016

 

Network  

  • Connecting to the Power365 Directory Sync web interface uses TCP port 443 (HTTPS).
  • Agent connections are initiated by the agent and require port 443 access to Power365 Directory Sync SaaS application.
  • Connecting to DCs uses TCP on ports 139, 389 (UDP), 445, and 3268.
  • Copying SID History uses TCP on ports 135, 137-139, 389 (UDP), 445, 1027, 3268, and 49152-65535.

 

Accounts  

Local Active Directory Account

  • The agent installer will prompt for a domain account with permission to read and write on-premises Active Directory.
  • An agent intended to sync all domains in a forest, must have access rights to all domains and objects used in workflows.

Azure AD Application Account

  • When creating a new Cloud Environment, an account with the Global Administrator Role is required to grant permissions and establish a connection.

Azure AD PowerShell Accounts

  • An OAuth token will be used by the application to create two (2) PowerShell accounts which are used to read and update objects in the cloud.
  • The accounts being used do not require any Microsoft 365 licenses.

 

Password Synchronization  

The following conditions must be met for Password Sync:

  • ADMIN$ must be accessible on the domain controller from the Directory Sync agent server.
  • The Password Sync functionality requires that either a domain admin role or built-in admin role be granted to the service account.
  • Any third-party anti-virus program that prevents access the LSASS process may need to be updated with a whitelist entry for the Password Sync executable.

 

SID History  

  • A trust between that source and target domain is not required to populate SID History on target objects, but is required to make use of the SID History when attempting to access source side resources. Typically, a trust is created by establishing a Forest level trust, but can also be done as a domain trust.

  • The target account must have administrator permissions in the source domain. To enable this, the target account of the Power365 Directory Sync agent should be added to the source PDC's built-in administrator group.

  • Auditing of the source and target domain must be enabled. This can be enabled as a global policy for all domain controllers or as a local policy on the specific source and target DCs involved. To enable auditing as a local policy, go to gpedit.msc > Computer Configuration > Windows Settings > Security Settings > Local Policies > Audit Policy and enable the “Audit account management” and “Audit directory service access” settings.

    Local Group Policy Editor

  • ‘Account Management’ and ‘DS Access’ Advance Audit policies of the source and target domain should be configured if Advance Auditing are configured in the environments. These settings can be enabled as a global policy for all domain controllers or as a local policy on the specific source and target DCs involved.

    • To enable advance audit policy for Account Management, go to gpedit.msc > Computer Configuration > Policies > Windows Settings > Security Settings > Advanced Audit Policy Configuration > System Audit Policies > Account Management enable Success and Failure audit for the below policies.
    • Audit Application Group Management
    • Audit Computer Account Management
    • Audit Distribution Group Management
    • Audit Other Account Management Events
    • Audit Security Group Management
    • Audit User Account Management

    • To enable advance audit policy for DS Access, go to gpedit.msc > Computer Configuration > Policies > Windows Settings > Security Settings > Advanced Audit Policy Configuration > System Audit Policies > DS Access and enable Success audit for the below policies.
    • Audit Directory Service Access
    • Audit Directory Service Changes
    • Audit Directory Service Replication
    • Audit Detailed Directory Service Replication

  • An empty Domain Local security group must be created in each source domain and named {SourceNetBIOSDomain}$$$.

  • The HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA\TcpipClientSupport registry key must be set to 1 on the source domain primary domain controller. You must restart the source domain primary domain controller after the registry configuration.

  • MigratesIDHistory permissions are required on the target domain. This is typically enabled for Domain Admins and Enterprise Admins, but can be enabled for a specific group or user by following the below steps:

    1. Right-click on your target domain in Active Directory Users and Computers.
    2. Select the Security tab and add or update the desired group or user and enable the “Migrate SID History” permission.

      Security tab of Properties

Important Tip: For further guidance from Microsoft about Using DsAddSidHistory, click here.

 

Workflow Alerts  

• To create a workflow alert, simply have a valid SMTP address ready.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating