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 Release Notes Known Limitations Support

Manage Scope

What is project scope?  

In this context, project scope represents the users and groups defined as required for migration and integration services. This includes the users and groups data.

In other words, when a user is defined as in-scope this includes the user’s scope of data.


How do I manage scope?  

Managing scope in Power365 is very flexible. Pick the best fit for your project needs, you have several options or methods to choose from.

During project setup for Advanced and Premium project types, you will be asked to choose which users and which groups will be discovered.

During these steps you have two (2) options.

  1. Discover Everyone
  2. Discover based on Group

The best way to manage scope is by choosing to discover objects based on group membership. Anyone outside of the group membership will not be displayed in the application and cannot be acted upon at any time. Only authorized Client Administrators are permitted to modify the scope of users or groups in a project.


May I manage scope from a local AD group?  

Yes, when managing scope by group membership that group may be in the local Active Directory or a cloud only group within Microsoft 365. Power365 always discovers the objects within the Azure directory, therefore any local AD group used must be synchronized up to Microsoft 365 with Azure AD connect or similar technology.


May I manage scope from a cloud group?  

Yes, when managing scope by group membership that group may be in the local Active Directory or a cloud only group within Microsoft 365. Power365 always discovers the objects within the Azure directory, therefore any local AD group used must be synchronized up to Microsoft 365 with Azure AD connect or similar technology.


Are nested groups supported?  

Yes, nested groups are fully supported. However, we recommend they remain as simple as possible because the more complexity the longer discovery may take. So, when possible create new discovery or wave groups or use single nested existing groups. Dynamic groups are not supported.


How do I manage scope for Basic Migration Projects?  

Basic migration projects do not provide discovery services; therefore, scope is controlled by the list uploaded during project setup. Only authorized client administrators may add new users to the scope of a project.


How can I ensure scope remains unchanged during a divestiture project?  

Unlike typical migrations or consolidation projects where all users and groups are being moved, it is very important during divestiture projects that scope be securely managed to reduce risk and human error. That is why Power365 offers different methods to manage scope for divestiture projects.

First, Power365 provides a role-based access model that only grants permission to add, modify or remove the scope definitions for users and groups to authorized client administrators. In other words, only assign the client admin role to users who you trust to control the scope of a project.

Second, Power365 offers a parallel divestiture solution whereby, parallel Migration and Domain Sharing projects are running but each parallel project has different goals and timelines, is managed by different teams that don’t communicate and project ownership is separated. Therefore, this type of one-to-many divestiture must have isolated experiences but share the same single source tenant without overlapping or conflicting with one another’s efforts or licensing. To find out more about Email Rewrite Services parallel divestiture solutions, contact Support or contact your account manager.


Additional Information  

Application Permissions


Tenant Environments





What is matching?  

Matching is a process in Power365 that provides a method for objects between different directories to be paired together for migration and synchronization purposes.


Why is matching required?  

Matching is required because it provides a mapping between source and target objects for the purposes of group membership synchronization and email address translation during migration.


What is matched?  

All Users and Groups are matched between a source tenant environment and a target.


What projects types support automatic matching and discovery?  

The Premium and Advanced projects types support discovery and matching services. The Basic project type supports uploading of mapping lists for matching users and groups.


When does matching occur?  

Matching automatically occurs during the discovery process and can be run manually at any time by an authorized project administrator.


How does matching work?  

Power365 will attempt to match users and groups in the source tenant with users and groups in the target tenant.

During project setup, you may choose up to 3 attribute pairs that Power365 will use to make this object pairing determination.

Matching is processed in the order listed. If there is no match on the first attribute, Power365 moves down the list.

With the Integration project type, if no match is found, Power365 may create the users and groups for you.


What are the projects requirements for matching?  

To complete the project setup and match objects, you will be required to setup pairs for Tenant Environments, Domains and Attributes for Users and Groups.


Can I run a match myself?  

Yes, there is an action available called Match. This action will match an unmatched user or group against the target environment without the need to run a full discovery in source and target.


How do I run the match action?  

It’s easy, navigate to the users or group you would like to match. Select the item then select the Match action from the action drop-down menu. Once selected, click the Apply Action button to begin. The status of the object will change to Matching. When successfully complete, the status will change to Matched.


Are there matching logs?  

Yes, within the discovery logs, matched objects will be logged. However, the easier method is to export all discovered users and groups. The export of all discovered objects will provide a list of all matched and unmatched objects. Navigate to the user or group management view then select all the objects. Afterwards, select the Export action from the action drop-down menu.


Additional Information  


How to Match Groups



What is discovery?  

The discovery service is used to collect user and group identity and properties for the purposes of migration preparation.


What is discovered?  

When discovery is complete, it will have collected all user, group, and contact information within the configured Azure directory environments. It will use this data based on project configuration to find matching objects between environments for the purposes of data migration and synchronization.


When does discovery occur?  

The Power365 Directory Discovery Service runs by default every twenty-four (24) hours. This frequency may be changed as needed.


Should I change the default discovery frequency?  

After the initial discovery has successfully completed, subsequent discovery jobs will be deltas, which are quicker. Monitor the time it takes to run a delta sync. If the total discovery time exceeds 24 hrs., adjust the frequency to fit the environment size. The more directory objects, the more time a discovery will take. Be sure the initial discovery completed successfully. Otherwise, each new discovery job will run a full discovery again.


When can I run discovery?  

The Power365 Directory Discovery Service may be run at any time by an authorized project administrator.


Can I run a full discovery?  

Yes, a full discovery may be run after the initial discovery has completed when required. However, it is recommended that delta discovery be allowed to run to ensure new and modified object changes are processed quickly.


How do I run full discovery?  

To manually run Discovery and adjust the Discovery Delta Timestamp,

  1. Click the drop-down menu located in the top left corner.

  2. Click the Discovery link from menu.

  3. Hover over the desired tenant environment.
  4. Click RUN DISCOVERY to begin the process.

    Run Discovery link

  5. In the pop-up window displayed, adjust the Delta Timestamp via the date time control text box.

    Run Discovery Delta Timestamp option


When should I run a full discovery?  

Full discovery should only be run when previously skipped objects are now required for the project. To discover the previously skipped objects, set the delta timestamp to a time before the initial discovery, when the objects were created or last modified.


Who is authorized to run discovery?  

The Client Administrator, Power User and Operator may manually run a new discovery.


Who is authorized to modify the Delta Timestamp?  

Only the Client administrator role may adjust the Delta Timestamp.


What is the Delta Timestamp?  

After the first full tenant discovery is completed, only new or modified objects are discovered during subsequent delta discovery jobs. The Delta Timestamp field allows authorized administrators to set the timestamp so that previously skipped objects will now be added to the scope of the project. Essentially, objects created, or modified before the timestamp will be skipped.


Can I suspend discovery?  

Yes, the Power365 Directory Discovery Service can be disabled at any time by an authorized project administrator. Click DISABLE for the desired tenant while in the discovery management page.


How do I suspend discovery?  

To manually disable all future discoveries, follow these steps.

  1. Click the drop-down menu located in the top left corner.

  2. Click the Discovery link from menu.

  3. Hover over the desired tenant environment.
  4. Click DISABLE to stop all future the processes.

    Disable link


When should I disable discovery?  

In most cases, discovery services should not be disabled during an active project. Inactive projects can either be archived if they are no longer required, which will end all related services, or the discovery service can be disabled until the project becomes active.

It is recommended that discovery services be disabled before a Domain Cutover event is started. For more information about Domain Cutovers, review this help article.


Is there a discovery log?  

Yes, Power365 provides authorized administrators access to the discovery and tenant logs. To download the logs, simply navigate to the DISCOVERY section from your project dashboard then click the LOGS link for the desired environment.


After discovery has ran, is there a report?  

Yes, after the initial discovery is complete there is a discovery report designed to help with migration planning.


What is in the discovery report?  

The purpose of the discovery report is to provide an overall view of your environment’s data size and scope to help with migration planning.

Pages 1 – 3 focus on data derived from the designated source tenant environment(s). Providing an easy view of data in scope and user averages across different workloads. Data includes mailboxes, archives, OneDrive/OneNote files and other shared resources like, Office 365 Groups. You may also filter collections of data based on the desired project, on the tenants needed or by project type.

Page 4 goes beyond the scope of only the source environments. During discovery, Power365 collects all tenant environment information required to prepare for migration activities. This page lists all configured projects, all accepted domains, discovery history and tenant details to help keep track of all the different projects and environments configured. Select an item in any table to filter the other tables. For example, when selecting a single project, only the domains related to that project will be displayed.

Pages 5 – 8 provide exportable lists of directory objects by type and their corresponding known properties. Additional filter options are available based on object types. You can easily export all your environment data for migration planning and tracking activities.

Please note, all filters selected on a page will remain when navigating between pages.


How do I access the discovery report?  

Authorized project users and administrators may go to the following URL to access reports for all their projects.

You may also click the Reports action in the dashboard menu. The default report is the discovery report. Additional reports can be selected from the dropdown menu in reports.

Reports action


Can I export data from the report?  

Yes, any visual that has an export option can be exported. Click the top right menu of the desired visual within the report for options.

For additional help with exporting data from visualizations, please read this MS article.


Additional Information  

Domain Cutover

How to export data from visualizations

Create your Project

Add your Tenants

Pair your Environments, Domains, and Attributes


What is a Migration Profile?  

A Migration Profile allows you to customize all migration parameters related to Prepare, Sync and Cutover. A Migration Profile can be assigned to a single user or by Migration Wave. You can customize the existing Default profile or create as many as you need to fit your project.


When should I create my Migration Profiles?  

We recommend after project set up you review and update the default migration profile. However, you may modify and add profiles at any time.


What migration options are available?  

The wizard will take you through the available options. Actual options vary by project type, as noted below.

Outlook Configuration

  • Choose Power365 Setup Pro for Outlook, cutover options.

    • Enable or Disable Feature

      • Choose the delivery options:

        • Silent Installer

        • Self-Service Installer

    • Choose if you want to “Wait for User to Finish” before cutover completes

Create Users, Office 365 Groups and Teams

  • Decide if you want to allow Users, Office 365 Groups and Teams to be created for non-matches. (Premium Projects Only)

GAL Sync (Deprecated with DSLite)

  • Choose personal contact information sync options.

  • Decide if you want to allow distribution groups to be created for non-matches.
  • Choose distribution groups sync options.

Additional Workloads (Advanced and Premium Only)

  • Choose whether to sync Mailbox Archives (All Project Types) and OneDrive for Business Files.

  • Choose to Send OneDrive Cutover Email.

  • Choose to use Accelerated Velocity Mode for increased throughput.


Litigation Hold

  • Choose if to copy Litigation Hold settings and data to destination.

Mailbox Content

  • Define the Mailbox content types to migrate.

    • Email

    • Calendar

    • Tasks

    • Notes

    • Deleted Items

    • Rules

    • Automatic Replies (Out of Office)

    • Signatures (Desktop Setup Pro Required)

Mailbox Filters

  • Define Content Filter options for Email, Calendar, Tasks and Notes
    • Filter by Date Range

    • Filter by Age Range

  • Define thresholds for handling of "large items." This setting specifies the maximum item size in MB. This applies to all mailbox items, e.g. emails, meetings, tasks, etc. The default option is “include all”. The recommendation is to meet your destination environments item size policies.

Error Thresholds

  • Specify how to handle bad items for mailboxes and OneDrive for Business. These settings specify the number of corrupt items that is allowed before marking a sync job as failed. The default is 0, which means the sync will fail if any bad items are detected. The recommendation is 10 or lower.

  • Specify how to handle folders that cannot be synced for mailboxes and OneDrive for Business. These settings specify the number of folders that can be skipped due to bad items or permission issues before marking a sync job as failed. The default is 0, which means the sync will fail if any bad folders are detected. The recommendation is 10 or lower.


Power365 can help you optimize your sync cycles by allowing you to choose when mailbox Delegation and Litigation Hold (LH) settings are migrated to the destination. By default, Power365 will sync your delegation and LH settings during every sync, including cutover. This ensures mailbox and folder permissions, along with LH settings remain in sync during the entire migration life cycle.

  • Determine your optimization options.

    • Optimize Prestaging – Choose “Optimize Prestaging” to speed up all preliminary syncs jobs, prior to cutover. This option will reduce the initial and delta sync times during the preparation stage, by keeping the sync of permission and litigation hold settings until the cutover event, at the very end. Use this option if you wish to ramp-up fast to a cutover event. Keeping plenty of time for each cutover.

    • Optimize Cutover – Choose “Optimize Cutover” to reduce the cutover event time. This option will reduce the overall time of a cutover event by skipping the permission and LH settings, which have been previously migrated. Use this option if you want to control the amount of time a single cutover event will take. Maybe you need to fit more users into a cutover event, this option was designed to do just that.

    • Skip Permission Clean-up – Choose this option to skip the automated clean-up process after cutover where all application related accounts are removed from the source and target accounts.

Please Note: If you choose both options, then folder and mailbox permissions and mailbox litigation-hold settings are never synchronized.

User Licensing (Premium Projects Only)

  • Define your destination User’s Microsoft 365 licensing options.

Custom Cutover Emails

  • Choose the default email or customize it.
    • Download a template.
    • Customize the template.
    • Upload the new template.


What options are available to cutover my user’s Outlook Profiles?  

With Outlook Setup Pro a project administrator may choose:

  1. To automatically configure the end-user’s new Outlook profile.
  2. The agent delivery options.
  3. If to wait for end-user before continuing cutover process.

Choose No if you do not desire to send the end-user a cutover email or provide a method to configure their Outlook profiles. Otherwise, choose Yes.

Figure 1: Migration Profile Outlook Setup Pro Options


What happens if you wait for the users to update their applications?  

If you choose to wait for an end-user to complete their Outlook Profile, the cutover process will wait for end-user to complete the application reconfiguration before moving onto the next cutover stage.

Figure 2: Migration Profile Outlook Cutover Options


Are Outlook Signatures migrated?  

Yes, to migrate your users Outlook signatures files, simply choose to send the cutover email to your end-users during cutover. The Desktop Setup Pro agents provides the ability to add your existing signatures to your new outlook profile.


What options are available to create users, Office 365 Groups and Teams?  

For integrated Directory Sync projects, unmatched users can be created as either as regular members or as B2B guest users. By creating these users as guests, they may be granted access to shared resources during the coexistence phase prior to any migration activities. More information about B2B guest users can be found at

Figure 3: Migration Profile Create Target Objects Options


What litigation hold options are available?  

For more information about Litigation Hold options and implications, see the Litigation Hold topic.

Figure 4: Litigation Hold Options


What user license options are available?  

Figure 5: License Options

Power365 Premium Integration project types provide automatic license assignment for destination users. For the Basic Migration and Advanced Migration project type, license assignments are a prerequisite and the responsibility of the administrator’s setting up the project.

During the first synchronization job of a user, the Provisioning job runs. During this step, user licenses are assigned to the destination user based on the migration profile options.

Power365 only enables the associated service plan for the Product License selected. For example, if you choose the E3 license, only the Exchange Online service plan will be enabled. All other service plans will be left to the administrator to enable when desired. Optionally, the SharePoint Online server plan is enabled if OneDrive is being migrated.

The migration profile provides two options to assign Microsoft 365 product licenses and the associated service plans needed for Exchange Online Mailbox or OneDrive migrations.

  • Default – A license that matches your source mailbox will be used. NOTE: this applies only for E3, E4 or E5 licenses.
  • Preferred SKU – Determines which SKU should be applied to your target mailbox.

If your preferred SKU is not available, please contact Support for assistance.


What options are available to optimize my syncs?  

Figure 6: Optimize Options


What happens during automated clean-up at Cutover?  

One of the final steps of the cutover process is to clean-up any permission artifacts on the source and/or target objects that were required to migrate content but are no longer required now that the cutover process is complete. During this step any migrated Mailboxes, Office 365 Groups or Microsoft Teams and Teams Channels are purged of any Binary Tree account that was automatically created during set up and will also remove the client’s Application account used to Connect their tenants and grant permissions to tenant resources.

Caution, if you used a personal administrator account, instead of an application specific account to grant Power365 permissions to the tenant resources, this account will be removed during this process which may result in your personal account being removed from a resource you did not intend.

See Application Permissions and Requirements for more information.


Additional Information  

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating