Power365 Current - Power365 Premium Integration Pro (Cloud to Cloud) Quick Start Guide

Introduction - Premium Integration Pro (Cloud to Cloud)

This guide is designed to provide a quick reference for getting set up with a Power365 Premium Integration Pro project.

At the end of this guide you will be familiar with supported setups, basic requirements, and deployment components.

Assumptions - Premium Integration Pro (Cloud to Cloud)

This guide covers the setup of migration and integration services from one source (1) source Cloud Only Microsoft 365 Worldwide Tenant between another (1) target Cloud Only Microsoft 365 Tenant. However, additional environment scenarios are supported as outlined below.

This guide does not cover Domain Sharing or Domain Moves specifically but these services can easily be enabled without amendments to the information provided in this guide. The migration of servers and workstations are also not covered in this guide.

Supported Migration and Integration Setups

The following describes the supported migration project models.

1. Merge (One to One) – Covered in this guide. This is the classic Tenant-to-Tenant migration project when one cloud or hybrid environment is migrating to another.

2. Divest (One to Many) – When one Cloud or Hybrid environment is migrating resources to many different cloud or hybrid environments.

3. Divest in Parallel (One to Many) – 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.

4. Consolidate (Many to One) – When many different cloud or hybrid environments are migrating to a single environment.

These setup scenarios may include the entire tenant or just a subset of resources.

Supported Environment Setups

The following describes the supported migration and integration deployment models.

1. Hybrid to Hybrid – All the features and services of Premium Integration but now supporting the Integrated Directory experience where directory orchestration operations are managed from a single web interface, there isn’t any SQL server to install, and best of all troubleshooting doesn’t require access to local machines to review event logs.

2. Cloud to Cloud – Covered in this guide. All the features and services of Premium Integration Pro but now supporting cloud only Microsoft 365 tenant migration and integration project scenarios. This includes Domain Sharing and Moves.

3. Hybrid to Cloud – All the features and services of Premium Integration Pro but now supporting migration and integration between a source Hybrid Microsoft 365 tenant and a target Cloud only tenant. This includes Domain Sharing and Moves.

4. Cloud to Hybrid – All the features and services of Premium Integration but now supporting migration and integration between a source Cloud only Microsoft 365 tenant and a target Hybrid tenant. This includes Domain Sharing and Moves.

Definitions: The term “Hybrid” in this instance is referring to a local On-Premises Active Directory that is coupled with a Microsoft 365 tenant to create a hybrid integration of services. The term “Cloud” is denoting a Microsoft 365 tenant that does not have any on-premises Active Directory component currently attached.