MS-102 Deploy and manage a Microsoft 365 tenant Practice Question
Your company recently acquired a subsidiary that uses a different Microsoft 365 tenant. You are tasked with merging the two tenants into one. The subsidiary has 1,500 users with unique email domains. You need to migrate all users, mailboxes, and SharePoint data while minimizing downtime and preserving data integrity. You have access to both tenants as global admin. What should you do first?
⚠ Common exam trap
It's easy for candidates to assume Microsoft provides a native 'merger' tool or that PowerShell alone can handle a full tenant merge, overlooking the lack of built-in cross-tenant SharePoint migration capabilities and the need for specialized third-party solutions.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a third-party migration tool such as BitTitan MigrationWiz to perform the migration
Microsoft does not provide a native tool for merging two tenants; third-party tools like BitTitan MigrationWiz are designed specifically for cross-tenant migrations, supporting mailbox, SharePoint, and user data migration with minimal downtime and data integrity. These tools handle directory synchronization, mailbox rehydration, and SharePoint content mapping, which are critical for a 1,500-user migration with unique domains.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Add the subsidiary's domain to the primary tenant, then delete the subsidiary tenant and recreate users
Why it's wrong here
Adding the subsidiary's domain to the primary tenant would first require removing that domain from the subsidiary tenant, and then the suggested step of deleting the subsidiary tenant and recreating users is a destructive 'rebuild', not a migration. Deleting the subsidiary tenant destroys all existing mailboxes, OneDrive/SharePoint content, Teams data, and compliance/retention records, and the recreated users would receive entirely new identities and object GUIDs with no data payload. This option is wrong because it discards the very data the acquisition is intended to consolidate.
- ✗
Use the Microsoft 365 Merger Center in the admin portal
Why it's wrong here
The 'Microsoft 365 Merger Center' does not exist anywhere in the Microsoft 365 admin center, Microsoft Entra admin center, or the broader M365 architecture. Microsoft provides no portal-based 'merge tenant' operation; tenant consolidation is a migration project, not a built-in admin studio feature. While a few domain-sharing or cross-tenant mailbox features exist, there is no single management UI that can combine two tenants into one, so selecting this option is based on a fictional tool.
- ✓
Use a third-party migration tool such as BitTitan MigrationWiz to perform the migration
Why this is correct
BitTitan MigrationWiz is an established third-party platform that performs cross-tenant mailbox, OneDrive, SharePoint, and Teams migrations by connecting to both tenants and running staged delta-sync batches. It minimizes downtime by pre-staging content and then synchronizing only changes during the cutover window, preserving item-level fidelity, metadata, and permissions. This is the standard recommended approach for consolidating two Microsoft 365 tenants after an acquisition.
- ✗
Use Microsoft's native tenant-to-tenant migration by moving mailboxes via PowerShell and exporting SharePoint content
Why it's wrong here
Native Exchange Online cross-tenant mailbox migration is available, but it is workflow-heavy: you must use PowerShell to configure an organization relationship, create a migration endpoint, and satisfy licensing and tenant restrictions, and even then it does not move SharePoint, OneDrive, or Teams data. Exporting SharePoint content via PnP PowerShell or the SharePoint Migration API and then importing it is a manual, error-prone process that loses permissions, version history, and content types while causing user-facing disruption. Because native tooling cannot handle the complete dataset with acceptable continuity, third-party tools are recommended as the practical migration path.
Go deeper
Related to this question
Learn chapter
Microsoft 365 Admin Center
Key term
Mailbox
A mailbox is a storage location on a mail server where incoming and outgoing email messages are kept for a user or group.
Key term
Microsoft 365
Microsoft 365 is a subscription-based cloud service from Microsoft that combines productivity tools like Office apps with security, device management, and online storage.
About these practice questions
This MS-102 question is part of Courseiva's 712-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This MS-102 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the MS-102 exam.