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 Office 365. Power365 always discovers the objects within the Azure directory, therefore any local AD group used must be synchronized up to Office 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 Office 365. Power365 always discovers the objects within the Azure directory, therefore any local AD group used must be synchronized up to Office 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 Binary Tree Support or contact your Binary Tree account manager.

 

Additional Information

Quick-Start Guide (PDF)

Prerequisites (PDF)

Application Permissions

Projects

Tenant Environments

Pairing

Matching

Discovery