Skip to content
UltiblobStatus
Back to course
Expert120 to 150 minutesInstructor visible

Tenant migration and M&A integration plan

Contoso is acquiring Fabrikam Components and must consolidate domains, identities, mailboxes, Teams, SharePoint, OneDrive, devices, and licensing.

Business context

A bad migration would disrupt manufacturing operations and introduce security risk.

Technical objective

Create a migration wave plan with identity coexistence, domain consolidation, workload sequencing, cutover, rollback, communications, and hypercare.

Student instructions

  1. 1Gather discovery inputs from both simulated tenants.
  2. 2Map identity, mail, collaboration, endpoint, licensing, and compliance dependencies.
  3. 3Define pilot, cutover, rollback, and hypercare plans.
  4. 4Validate migration plan completeness.

Troubleshooting

  • If the plan is one big cutover, split by persona, dependency, domain, and risk.

Cleanup

  • Export migration workbook and cutover runbook.
Launch flow

Provisioning readiness

Pending
Waiting for launch

Click Launch lab to start the provisioning flow and watch each stage complete.

0%
  1. Request accepted
  2. Capacity reserved
  3. Templates queued
  4. Validation running
  5. Workspace ready
m365-migration-plan-complete
Pending

Required templates

  • Microsoft 365 simulated tenant layer - defined

Validation checks

  • Tenant migration plan complete: Plan includes discovery, identity coexistence, domain consolidation, mailbox and collaboration migration, cutover, rollback, communications, and hypercare.

Expected result

Migration plan is complete enough for executive approval and technical implementation planning.

Reset policy: Migration wizard artifacts can reset per cohort. Teardown policy: Simulated tenant state expires with the course lab TTL.