This guide is broken into 4 easy steps to get started quickly.
Verify Setup Requirements
Set up Premium Project
Deploy Agents
Set up Read and Match Workflow (Groups & Teams Only)
At a minimum there are two (2) areas that must be ready before starting, the accounts to grant access and a member server to install an agent.
Application Accounts
Before starting have Global Administrator account credentials ready for all source and target tenants that are in scope.
Have at least one (1) available Microsoft 365 license for our application account to consume for the duration of the project. Once the project is closed, the account license can be reclaimed.
In addition, the local agent will require Active Directory credentials to read and write to the desired Domain for reading and modifying objects.
Visit the Help Center for more details about accounts and permissions requirements .
Directory Sync Agents
For hybrid deployments where on-premises Active Directory is being used as the source for identity and security management, at least one (1) local agent is required to be installed on a local domain member server.
For additional information about the directory sync prerequisites, read the Power365 Directory Sync Requirements here.
Domain Sharing
There are additional requirements if Email Rewrite Services (ERS) are required for your Premium Integration Project. ERS setup is not covered in this guide. To find out more about Domain Sharing ERS requirements, download our Tenant-to-Tenant prerequisites guide.
Power365 Tenant-to-Tenant new project setup is automated making it easy and quick to get started. To begin follow these steps for creating your first Power365 Premium Integration project.
Login to Power365.
Choose Tenant-to-Tenant.
Click New Project.
Choose Premium Integration Project type. Click Next.
Enter Project Name and Description. Click Next.
Click New to add your Tenant Environments.
Have your Microsoft 365 Global Administrator’s credentials ready.
If there is more than 1 administrator, both administrators must be present to continue set up.
Click Connect.
Enter your Global Administrator’s credentials for first tenant environment.
Accept the permissions requested.
Repeat steps 6 – 11 for all subsequent tenant environments.
Select your environment pairs. Click Next.
Select your domain pairs. Click Next.
Choose Discovery options. Click Next.
Choose Matching options. Click Next.
Choose Create options. Click Next.
Enter New Users Default Password. Be sure it meets requirements. Click Next.
Choose Free/Busy options. Click Next.
Click Download Agent.
Each environment administrator should download a copy of this agent to install in their local member server.
See section three (3), “Install Agent(s)” for detailed agent installation and configuration details.
Once all agents are installed and configured, click Next.
Choose Domain Sharing options.
Choose No, Maybe Later if you don’t have your ERS requirements ready. Click Next.
The Project Setup Summary will open.
Review the configurations, click the header to modify the options.
When ready, click Next.
Enter a valid email address to receive your discovery notifications.
Click Start Discovery.
Environment discovery will now begin. When it completes an email will be sent to you. The larger and more complex the environment, the longer initial discovery will take. After a successful initial discovery has completed, delta discoveries will be run every 24 hours by default. Discovery intervals are configurable. If your discovery takes longer than 24 hours on average, be sure to adjust the schedule.
Need more information about projects, permissions, or other topics? Then visit our online help center.
In this next section the on-premises directory sync agent will be installed and configured. At least one (1) agent must be installed in each environment, however a maximum of five (5) agents are supported per environment for redundancy. Each agent must be installed on an independent server, but this server is not required to be dedicated to this function. This agent should not be installed on a Domain Controller in a production environment.
To continue, follow these steps to complete the installation of your Directory Sync Agent.
Each administrator should login to a local server to install the agent.
Copy the agent installer to a shared folder or copy directory to server desktop.
Double-click to begin installation.
The installation wizard will open. Click Next.
Enter the Domain, Global Catalog server FQDN, the local domain administrator account and password. Click Next.
Installation will begin.
When complete, click Finish.
To modify the configuration, find and launch the BTAgent Configuration application.
Repeat steps 3 – 7 for each agent installation across environments.
For additional details about the directory sync agent prerequisites, read the Power365 Directory Sync Requirements here.
Now that the Premium Integration Project is set up there is one final step to ensure a successful migration experience for Office 365 Groups and Teams. One of the key features of Groups and Teams migration services is synchronizing Team and Channel membership, ownership, and additionally for Office 365 groups their subscribers. To accomplish this, Power365 Directory Sync must have a set of matches to determine who is a member. To do so, a single workflow must be set up to read from your tenant environments and match objects between them. Follow these steps to set up the workflow.
While logged in to Power365.
Navigate to the Directory Sync Dashboard.
Click New under Workflows or click Create a Workflow from the left menu.
Enter a Workflow Name and Description.
Select your source and target cloud environments. Click Next.
Choose One-Way Sync. Click Next.
Delete the Stage Data and Write To steps displayed in the right panel.
Confirm deletions by clicking Yes.
Click Select on the Read From step.
Select both cloud environments. Click OK.
Click Select on the Match Objects step.
Choose the source environment.
Choose the target environment.
Choose the desired matching attribute(s).
It is recommended that the same attribute pairings used for Tenant-to-Tenant matching be used in this case.
Do not check the Match Across All Object Types option. Click OK. Click Next.
Choose your Schedule options.
‘Manually’ is recommended for testing purposes and big bang Groups and Teams migrations where changes to the matching table won’t impact the migration event. ‘Scheduled’ is recommended if migrating Groups and Teams along with your users over time. Click Next.
Choose your Alert options. Click Skip to set up later if required.
Review your workflow summary.
Click Edit to modify any desired configurations.
When ready, click Finish.
From the Directory Sync Dashboard, select the workflow which was just created. Click Run.
When the workflow run is complete, verify the users are matching as expected and there are no errors that need to be resolved.
The workflow will need to be run again after your users and groups have been created in the target environment.
Environment Filters Tip: Be sure to set the environment filters to determine the scope of what objects would be matched. For more details about filters, check out our online help center.
This guide is broken into 4 easy steps to get started quickly.
Verify Setup Requirements
Set up Premium Project
Deploy Agents
Set up Read and Match Workflow (Groups & Teams Only)
At a minimum there are two (2) areas that must be ready before starting, the accounts to grant access and a member server to install an agent.
Application Accounts
Before starting have Global Administrator account credentials ready for all source and target tenants that are in scope.
Have at least one (1) available Microsoft 365 license for our application account to consume for the duration of the project. Once the project is closed, the account license can be reclaimed.
In addition, the local agent will require Active Directory credentials to read and write to the desired Domain for reading and modifying objects.
Visit the Help Center for more details about accounts and permissions requirements .
Directory Sync Agents
For hybrid deployments where on-premises Active Directory is being used as the source for identity and security management, at least one (1) local agent is required to be installed on a local domain member server.
For additional information about the directory sync prerequisites, read the Power365 Directory Sync Requirements here.
Domain Sharing
There are additional requirements if Email Rewrite Services (ERS) are required for your Premium Integration Project. ERS setup is not covered in this guide. To find out more about Domain Sharing ERS requirements, download our Tenant-to-Tenant prerequisites guide.
Power365 Tenant-to-Tenant new project setup is automated making it easy and quick to get started. To begin follow these steps for creating your first Power365 Premium Integration project.
Login to Power365.
Choose Tenant-to-Tenant.
Click New Project.
Choose Premium Integration Project type. Click Next.
Enter Project Name and Description. Click Next.
Click New to add your Tenant Environments.
Have your Microsoft 365 Global Administrator’s credentials ready.
If there is more than 1 administrator, both administrators must be present to continue set up.
Click Connect.
Enter your Global Administrator’s credentials for first tenant environment.
Accept the permissions requested.
Repeat steps 6 – 11 for all subsequent tenant environments.
Select your environment pairs. Click Next.
Select your domain pairs. Click Next.
Choose Discovery options. Click Next.
Choose Matching options. Click Next.
Choose Create options. Click Next.
Enter New Users Default Password. Be sure it meets requirements. Click Next.
Choose Free/Busy options. Click Next.
Click Download Agent.
Each environment administrator should download a copy of this agent to install in their local member server.
See section three (3), “Install Agent(s)” for detailed agent installation and configuration details.
Once all agents are installed and configured, click Next.
Choose Domain Sharing options.
Choose No, Maybe Later if you don’t have your ERS requirements ready. Click Next.
The Project Setup Summary will open.
Review the configurations, click the header to modify the options.
When ready, click Next.
Enter a valid email address to receive your discovery notifications.
Click Start Discovery.
Environment discovery will now begin. When it completes an email will be sent to you. The larger and more complex the environment, the longer initial discovery will take. After a successful initial discovery has completed, delta discoveries will be run every 24 hours by default. Discovery intervals are configurable. If your discovery takes longer than 24 hours on average, be sure to adjust the schedule.
Need more information about projects, permissions, or other topics? Then visit our online help center.
In this next section the on-premises directory sync agent will be installed and configured. At least one (1) agent must be installed in each environment, however a maximum of five (5) agents are supported per environment for redundancy. Each agent must be installed on an independent server, but this server is not required to be dedicated to this function. This agent should not be installed on a Domain Controller in a production environment.
To continue, follow these steps to complete the installation of your Directory Sync Agent.
Each administrator should login to a local server to install the agent.
Copy the agent installer to a shared folder or copy directory to server desktop.
Double-click to begin installation.
The installation wizard will open. Click Next.
Enter the Domain, Global Catalog server FQDN, the local domain administrator account and password. Click Next.
Installation will begin.
When complete, click Finish.
To modify the configuration, find and launch the BTAgent Configuration application.
Repeat steps 3 – 7 for each agent installation across environments.
For additional details about the directory sync agent prerequisites, read the Power365 Directory Sync Requirements here.
Now that the Premium Integration Project is set up there is one final step to ensure a successful migration experience for Office 365 Groups and Teams. One of the key features of Groups and Teams migration services is synchronizing Team and Channel membership, ownership, and additionally for Office 365 groups their subscribers. To accomplish this, Power365 Directory Sync must have a set of matches to determine who is a member. To do so, a single workflow must be set up to read from your tenant environments and match objects between them. Follow these steps to set up the workflow.
While logged in to Power365.
Navigate to the Directory Sync Dashboard.
Click New under Workflows or click Create a Workflow from the left menu.
Enter a Workflow Name and Description.
Select your source and target cloud environments. Click Next.
Choose One-Way Sync. Click Next.
Delete the Stage Data and Write To steps displayed in the right panel.
Confirm deletions by clicking Yes.
Click Select on the Read From step.
Select both cloud environments. Click OK.
Click Select on the Match Objects step.
Choose the source environment.
Choose the target environment.
Choose the desired matching attribute(s).
It is recommended that the same attribute pairings used for Tenant-to-Tenant matching be used in this case.
Do not check the Match Across All Object Types option. Click OK. Click Next.
Choose your Schedule options.
‘Manually’ is recommended for testing purposes and big bang Groups and Teams migrations where changes to the matching table won’t impact the migration event. ‘Scheduled’ is recommended if migrating Groups and Teams along with your users over time. Click Next.
Choose your Alert options. Click Skip to set up later if required.
Review your workflow summary.
Click Edit to modify any desired configurations.
When ready, click Finish.
From the Directory Sync Dashboard, select the workflow which was just created. Click Run.
When the workflow run is complete, verify the users are matching as expected and there are no errors that need to be resolved.
The workflow will need to be run again after your users and groups have been created in the target environment.
Environment Filters Tip: Be sure to set the environment filters to determine the scope of what objects would be matched. For more details about filters, check out our online help center.
This guide is broken into 4 easy steps to get started quickly.
Verify Setup Requirements
Set up Premium Project
Deploy Agents
Set up Read and Match Workflow (Groups & Teams Only)
At a minimum there are two (2) areas that must be ready before starting, the accounts to grant access and a member server to install an agent.
Application Accounts
Before starting have Global Administrator account credentials ready for all source and target tenants that are in scope.
Have at least one (1) available Microsoft 365 license for our application account to consume for the duration of the project. Once the project is closed, the account license can be reclaimed.
In addition, the local agent will require Active Directory credentials to read and write to the desired Domain for reading and modifying objects.
Visit the Help Center for more details about accounts and permissions requirements .
Directory Sync Agents
For hybrid deployments where on-premises Active Directory is being used as the source for identity and security management, at least one (1) local agent is required to be installed on a local domain member server.
For additional information about the directory sync prerequisites, read the Power365 Directory Sync Requirements here.
Domain Sharing
There are additional requirements if Email Rewrite Services (ERS) are required for your Premium Integration Project. ERS setup is not covered in this guide. To find out more about Domain Sharing ERS requirements, download our Tenant-to-Tenant prerequisites guide.
Power365 Tenant-to-Tenant new project setup is automated making it easy and quick to get started. To begin follow these steps for creating your first Power365 Premium Integration project.
Login to Power365.
Choose Tenant-to-Tenant.
Click New Project.
Choose Premium Integration Project type. Click Next.
Enter Project Name and Description. Click Next.
Click New to add your Tenant Environments.
Have your Microsoft 365 Global Administrator’s credentials ready.
If there is more than 1 administrator, both administrators must be present to continue set up.
Click Connect.
Enter your Global Administrator’s credentials for first tenant environment.
Accept the permissions requested.
Repeat steps 6 – 11 for all subsequent tenant environments.
Select your environment pairs. Click Next.
Select your domain pairs. Click Next.
Choose Discovery options. Click Next.
Choose Matching options. Click Next.
Choose Create options. Click Next.
Enter New Users Default Password. Be sure it meets requirements. Click Next.
Choose Free/Busy options. Click Next.
Click Download Agent.
Each environment administrator should download a copy of this agent to install in their local member server.
See section three (3), “Install Agent(s)” for detailed agent installation and configuration details.
Once all agents are installed and configured, click Next.
Choose Domain Sharing options.
Choose No, Maybe Later if you don’t have your ERS requirements ready. Click Next.
The Project Setup Summary will open.
Review the configurations, click the header to modify the options.
When ready, click Next.
Enter a valid email address to receive your discovery notifications.
Click Start Discovery.
Environment discovery will now begin. When it completes an email will be sent to you. The larger and more complex the environment, the longer initial discovery will take. After a successful initial discovery has completed, delta discoveries will be run every 24 hours by default. Discovery intervals are configurable. If your discovery takes longer than 24 hours on average, be sure to adjust the schedule.
Need more information about projects, permissions, or other topics? Then visit our online help center.
In this next section the on-premises directory sync agent will be installed and configured. At least one (1) agent must be installed in each environment, however a maximum of five (5) agents are supported per environment for redundancy. Each agent must be installed on an independent server, but this server is not required to be dedicated to this function. This agent should not be installed on a Domain Controller in a production environment.
To continue, follow these steps to complete the installation of your Directory Sync Agent.
Each administrator should login to a local server to install the agent.
Copy the agent installer to a shared folder or copy directory to server desktop.
Double-click to begin installation.
The installation wizard will open. Click Next.
Enter the Domain, Global Catalog server FQDN, the local domain administrator account and password. Click Next.
Installation will begin.
When complete, click Finish.
To modify the configuration, find and launch the BTAgent Configuration application.
Repeat steps 3 – 7 for each agent installation across environments.
For additional details about the directory sync agent prerequisites, read the Power365 Directory Sync Requirements here.
Now that the Premium Integration Project is set up there is one final step to ensure a successful migration experience for Office 365 Groups and Teams. One of the key features of Groups and Teams migration services is synchronizing Team and Channel membership, ownership, and additionally for Office 365 groups their subscribers. To accomplish this, Power365 Directory Sync must have a set of matches to determine who is a member. To do so, a single workflow must be set up to read from your tenant environments and match objects between them. Follow these steps to set up the workflow.
While logged in to Power365.
Navigate to the Directory Sync Dashboard.
Click New under Workflows or click Create a Workflow from the left menu.
Enter a Workflow Name and Description.
Select your source and target cloud environments. Click Next.
Choose One-Way Sync. Click Next.
Delete the Stage Data and Write To steps displayed in the right panel.
Confirm deletions by clicking Yes.
Click Select on the Read From step.
Select both cloud environments. Click OK.
Click Select on the Match Objects step.
Choose the source environment.
Choose the target environment.
Choose the desired matching attribute(s).
It is recommended that the same attribute pairings used for Tenant-to-Tenant matching be used in this case.
Do not check the Match Across All Object Types option. Click OK. Click Next.
Choose your Schedule options.
‘Manually’ is recommended for testing purposes and big bang Groups and Teams migrations where changes to the matching table won’t impact the migration event. ‘Scheduled’ is recommended if migrating Groups and Teams along with your users over time. Click Next.
Choose your Alert options. Click Skip to set up later if required.
Review your workflow summary.
Click Edit to modify any desired configurations.
When ready, click Finish.
From the Directory Sync Dashboard, select the workflow which was just created. Click Run.
When the workflow run is complete, verify the users are matching as expected and there are no errors that need to be resolved.
The workflow will need to be run again after your users and groups have been created in the target environment.
Environment Filters Tip: Be sure to set the environment filters to determine the scope of what objects would be matched. For more details about filters, check out our online help center.
This guide is broken into 4 easy steps to get started quickly.
Verify Setup Requirements
Set up Premium Project
Deploy Agents
Set up Read and Match Workflow (Groups & Teams Only)
At a minimum there are two (2) areas that must be ready before starting, the accounts to grant access and a member server to install an agent.
Application Accounts
Before starting have Global Administrator account credentials ready for all source and target tenants that are in scope.
Have at least one (1) available Microsoft 365 license for our application account to consume for the duration of the project. Once the project is closed, the account license can be reclaimed.
In addition, the local agent will require Active Directory credentials to read and write to the desired Domain for reading and modifying objects.
Visit the Help Center for more details about accounts and permissions requirements .
Directory Sync Agents
For hybrid deployments where on-premises Active Directory is being used as the source for identity and security management, at least one (1) local agent is required to be installed on a local domain member server.
For additional information about the directory sync prerequisites, read the Power365 Directory Sync Requirements here.
Domain Sharing
There are additional requirements if Email Rewrite Services (ERS) are required for your Premium Integration Project. ERS setup is not covered in this guide. To find out more about Domain Sharing ERS requirements, download our Tenant-to-Tenant prerequisites guide.
Power365 Tenant-to-Tenant new project setup is automated making it easy and quick to get started. To begin follow these steps for creating your first Power365 Premium Integration project.
Login to Power365.
Choose Tenant-to-Tenant.
Click New Project.
Choose Premium Integration Project type. Click Next.
Enter Project Name and Description. Click Next.
Click New to add your Tenant Environments.
Have your Microsoft 365 Global Administrator’s credentials ready.
If there is more than 1 administrator, both administrators must be present to continue set up.
Click Connect.
Enter your Global Administrator’s credentials for first tenant environment.
Accept the permissions requested.
Repeat steps 6 – 11 for all subsequent tenant environments.
Select your environment pairs. Click Next.
Select your domain pairs. Click Next.
Choose Discovery options. Click Next.
Choose Matching options. Click Next.
Choose Create options. Click Next.
Enter New Users Default Password. Be sure it meets requirements. Click Next.
Choose Free/Busy options. Click Next.
Click Download Agent.
Each environment administrator should download a copy of this agent to install in their local member server.
See section three (3), “Install Agent(s)” for detailed agent installation and configuration details.
Once all agents are installed and configured, click Next.
Choose Domain Sharing options.
Choose No, Maybe Later if you don’t have your ERS requirements ready. Click Next.
The Project Setup Summary will open.
Review the configurations, click the header to modify the options.
When ready, click Next.
Enter a valid email address to receive your discovery notifications.
Click Start Discovery.
Environment discovery will now begin. When it completes an email will be sent to you. The larger and more complex the environment, the longer initial discovery will take. After a successful initial discovery has completed, delta discoveries will be run every 24 hours by default. Discovery intervals are configurable. If your discovery takes longer than 24 hours on average, be sure to adjust the schedule.
Need more information about projects, permissions, or other topics? Then visit our online help center.
In this next section the on-premises directory sync agent will be installed and configured. At least one (1) agent must be installed in each environment, however a maximum of five (5) agents are supported per environment for redundancy. Each agent must be installed on an independent server, but this server is not required to be dedicated to this function. This agent should not be installed on a Domain Controller in a production environment.
To continue, follow these steps to complete the installation of your Directory Sync Agent.
Each administrator should login to a local server to install the agent.
Copy the agent installer to a shared folder or copy directory to server desktop.
Double-click to begin installation.
The installation wizard will open. Click Next.
Enter the Domain, Global Catalog server FQDN, the local domain administrator account and password. Click Next.
Installation will begin.
When complete, click Finish.
To modify the configuration, find and launch the BTAgent Configuration application.
Repeat steps 3 – 7 for each agent installation across environments.
For additional details about the directory sync agent prerequisites, read the Power365 Directory Sync Requirements here.
Now that the Premium Integration Project is set up there is one final step to ensure a successful migration experience for Office 365 Groups and Teams. One of the key features of Groups and Teams migration services is synchronizing Team and Channel membership, ownership, and additionally for Office 365 groups their subscribers. To accomplish this, Power365 Directory Sync must have a set of matches to determine who is a member. To do so, a single workflow must be set up to read from your tenant environments and match objects between them. Follow these steps to set up the workflow.
While logged in to Power365.
Navigate to the Directory Sync Dashboard.
Click New under Workflows or click Create a Workflow from the left menu.
Enter a Workflow Name and Description.
Select your source and target cloud environments. Click Next.
Choose One-Way Sync. Click Next.
Delete the Stage Data and Write To steps displayed in the right panel.
Confirm deletions by clicking Yes.
Click Select on the Read From step.
Select both cloud environments. Click OK.
Click Select on the Match Objects step.
Choose the source environment.
Choose the target environment.
Choose the desired matching attribute(s).
It is recommended that the same attribute pairings used for Tenant-to-Tenant matching be used in this case.
Do not check the Match Across All Object Types option. Click OK. Click Next.
Choose your Schedule options.
‘Manually’ is recommended for testing purposes and big bang Groups and Teams migrations where changes to the matching table won’t impact the migration event. ‘Scheduled’ is recommended if migrating Groups and Teams along with your users over time. Click Next.
Choose your Alert options. Click Skip to set up later if required.
Review your workflow summary.
Click Edit to modify any desired configurations.
When ready, click Finish.
From the Directory Sync Dashboard, select the workflow which was just created. Click Run.
When the workflow run is complete, verify the users are matching as expected and there are no errors that need to be resolved.
The workflow will need to be run again after your users and groups have been created in the target environment.
Environment Filters Tip: Be sure to set the environment filters to determine the scope of what objects would be matched. For more details about filters, check out our online help center.
© ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center
