Tenant Migration

Move Microsoft 365 Users Between Tenants with Azure AD Connect

Elise WilliamsElise Williams Nov 22, 2026 868 views

Question details

Move Company B users and their data into Company A's Microsoft 365 tenant and use Company A's domain for their accounts.

Move Microsoft 365 Users Between Tenants with Azure AD Connect
Product
Microsoft 365 and Microsoft Entra Connect Sync (Azure AD Connect)
Device & OS
not provided
Scenario
Company B users have accounts in a separate tenant using the Company B onmicrosoft.com domain, while Company A's domain is verified in the destination tenant.
Observed behavior
The users and their data remain in separate tenants; Azure AD Connect does not automatically merge tenants or transfer users between them.
Before you start

In the Microsoft 365 admin center, check Settings > Domains in Company A's tenant to confirm that its domain is verified. Inventory Company B's users, mailboxes, licenses, and other data, and confirm you have the required administrative access to both tenants.

Solution 1Recommended

Migrate Company B users and data to Company A's tenant

Use a tenant-to-tenant migration to establish destination identities and transfer data before configuring directory synchronization.

Azure AD Connect, now called Microsoft Entra Connect Sync, synchronizes on-premises directory identities with Microsoft Entra ID. It does not merge existing tenants or migrate mailboxes and files.

Destination accounts are new tenant identities. Plan to recreate or update permissions and application assignments that depend on the original accounts.

1
Confirm the destination domain

In Company A's Microsoft 365 admin center, open Settings > Domains and verify that companyA.com is available. Set it as the default domain if appropriate for the organization.

2
Plan destination identities

In the Microsoft 365 admin center, review Users > Active users in both tenants and map each Company B user to the intended Company A account and email address. Plan destination licenses and avoid creating duplicate identities.

3
Prepare the mailbox migration

Review Microsoft's cross-tenant mailbox migration documentation for prerequisites, licensing, organization relationships, and destination recipient requirements. Prepare the source and destination tenants as directed before creating or provisioning destination mailboxes.

4
Move mailboxes and other data

Follow Microsoft's cross-tenant mailbox migration procedure to configure the migration and run a batch. Separately plan and migrate OneDrive, SharePoint, Teams, and other data that mailbox migration does not transfer.

5
Validate access and update records

Sign in to destination accounts, test email and data access, and check permissions and application assignments. Update DNS or mail-routing records where required by the migration plan before retiring source accounts.

6
Configure directory synchronization if needed

If Company A needs on-premises identity synchronization, review Microsoft Entra Connect Sync prerequisites and identity-matching guidance, then use the Microsoft Entra Connect installation wizard to configure the supported synchronization setup. Verify that on-premises users match the intended destination accounts.

Migrate Company B users and data to Company A's tenant
The onmicrosoft.com domain stays with its tenant: Company B's onmicrosoft.com domain cannot be moved to Company A's tenant. Assign the intended Company A addresses to destination users as part of the migration plan.
Free Microsoft Office alternative

Work with Office documents in WPS Office after migration

WPS Office is a free, lightweight, easy-to-use Office alternative with a familiar interface and Microsoft Office format compatibility for a smoother move between productivity suites. It does not migrate Microsoft 365 tenants, identities, or mailboxes.

Open and edit Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTXContinue working with compatible documents after moving them to the destination environmentUse a familiar interface for documents, spreadsheets, and presentationsGet a free, lightweight alternative for everyday Office tasks
microsoft office alternative - wps office

Frequently Asked Questions

Can Azure AD Connect move users directly between Microsoft 365 tenants?

No. Microsoft Entra Connect Sync synchronizes on-premises directory identities with Microsoft Entra ID; it does not transfer users or merge tenants. Use a tenant-to-tenant migration plan instead.

Can Company B's onmicrosoft.com domain be moved to Company A's tenant?

No. The onmicrosoft.com domain remains associated with its original tenant. Create or prepare destination identities and assign the appropriate verified Company A domain addresses.

Does a mailbox migration also move OneDrive and Teams data?

No. Plan mailbox migration separately from OneDrive, SharePoint, Teams, and other workloads. Review Microsoft's migration guidance for each type of data.

Should I create destination mailboxes before starting a cross-tenant migration?

Follow Microsoft's cross-tenant mailbox migration prerequisites first. The destination recipient must be prepared in the required state, so avoid provisioning a mailbox prematurely.

When should I configure Microsoft Entra Connect Sync?

After planning destination identities and domain use, review the supported synchronization topology and identity-matching requirements. Configure Microsoft Entra Connect Sync only if Company A needs to synchronize its on-premises directory.