Microsoft quietly added a capability to the Microsoft 365 roadmap on 12 November 2026 that most partners will scroll past. They should not. Tenant to tenant migration is moving into the Microsoft 365 admin center as a first-party feature, with a general availability target of December 2026.

If you have ever run a tenant-to-tenant move, you already know why that sentence matters. If you have not, this is the year it becomes your problem.

What the roadmap actually says

The item is titled "Microsoft 365 admin center: Cross-Tenant Orchestrated Migration". According to the roadmap data, it lets customers move their Microsoft 365 data from one Microsoft tenant to another, in two halves:

- User Data Migration (UDM): user mailboxes, OneDrive accounts, Teams chats, and Teams meetings
- Shared Data Migration (SDM): Microsoft 365 Groups, SharePoint sites, group mailboxes, and Teams and channels

The rest of the record is just as important as the description:

- Release ring: General Availability
- Availability: Worldwide (Standard Multi-Tenant)
- Platforms: Desktop and Web
- Target: December 2026
- Status: In development
- Documentation: TBD

Read that last line twice. There is no documentation yet. Microsoft has put a date on the roadmap before publishing the manual.

Why this is bigger than one roadmap line

Tenant to tenant migration has always been the awkward cousin of Microsoft 365 work. Customers change shape constantly, through mergers, acquisitions, divestitures, rebranding, and simple tenant sprawl built up over a decade of well-intentioned decisions.

Moving the user half has been largely achievable, with Teams chat as the usual exception. Mailboxes, OneDrive, and Teams chat have been handled through a mix of first-party tooling, third-party platforms, and a lot of scripted patience.

The shared half is where projects die. Microsoft 365 Groups, SharePoint sites, Teams and channels, and group mailboxes carry the structure of how an organisation actually works. Permissions, ownership, taxonomy, site collections, channel history. When that half is incomplete or manual, the migration "finishes" and the customer spends the next year discovering what did not come across.

So the news is not that Microsoft can move mailboxes. The news is that orchestration for both halves is being placed inside the admin center, as one flow, in a product admins already use.

The commercial shift nobody has priced yet

Today, tenant migration is a services engagement wrapped around third-party tooling. The tool is the hard dependency, the project plan exists to manage that tool, and the partner's margin lives in the gap between what the tool does and what the customer expects.

Native orchestration changes the shape of that engagement:

- The plumbing gets cheaper. When Microsoft ships the transport, nobody pays a premium for transport.
- The planning gets more valuable. Deciding what moves, what gets left behind, what gets re-architected, and in which order is not something a product decides for you.
- The validation gets critical. Post-migration verification, permission reviews, and evidence that the move did not open a side door become the deliverable a customer will actually pay for.
- The governance conversation arrives. A tenant move touches identity, conditional access, retention, and compliance boundaries. That is design work, not data copy work.

For Cloud Factory partners, there is a second and less comfortable layer. When a customer changes tenant, the commercial relationship changes with it: seat counts, subscription ownership, the CSP linkage, and which partner holds the relationship on the other side. A migration is a licensing event disguised as an IT project. Handle only the data and you will lose the account to whoever handled the paperwork.

As AI workloads and usage-based billing add more licensing dependencies, tenant moves increasingly require commercial design as well as technical execution.

What we do not know, and will not pretend to

This is a roadmap entry, not a shipped product. Three honest caveats:

  1. "In development" means exactly that. Scope can change, and features can shrink between roadmap and release.
  2. The date is an estimate. Microsoft moved the Copilot Business usage-based billing date from 1 December 2026 into FY27 Q3, and it removed an entire Partner Center announcement the same day it published it. Treat December 2026 as a planning input, not a commitment.
  3. No documentation exists yet. Until the admin center documentation lands, nobody knows which workloads move natively, what requires manual follow-up, what the throttling looks like, or what the supported scenarios are.

What to tell customers right now

Nothing about dates. Say this instead: tenant consolidation is becoming a normal, supported Microsoft operation, and the planning is where the risk sits. Then use that to open the conversation you have been avoiding with every customer that has more than one tenant.

Inventory first. Decide second. Migrate third.

Key Takeaways

- Microsoft has put tenant to tenant migration on the roadmap as a first-party capability in the Microsoft 365 admin center, with a general availability target of December 2026, covering both user data and shared data.
- Shared data is the hard half. Groups, SharePoint sites and Teams channels are where migration projects usually stall, and they are explicitly in scope.
- Orchestration moves the money. When Microsoft ships the transport, the premium shifts from plumbing to planning, validation and governance.
- A tenant move is a licensing event. Seat counts, subscription ownership and the CSP relationship change with the tenant, so handle only the data and you can lose the account.
- The date is an estimate and the documentation is not written yet. Treat December 2026 as a planning input, not a promise.

Partner Play

Monday morning, in this order:

  1. Inventory the estate. List every customer with more than one Microsoft 365 tenant, and every customer with an M&A, divestiture, or rebranding event in the next 18 months. Most partners discover that this list is longer than they thought.
  2. Find the stuck projects. Ask where a tenant move has been proposed, budgeted, or quietly abandoned. Those are live opportunities today, with or without a Microsoft feature.
  3. Map the commercial side. For each one, document seat counts, subscription ownership, CSP linkage, and who holds the relationship on the other tenant. This is the part that decides whether you keep the account.
  4. Position the service, not the tool. Sell planning, validation, and governance. If Microsoft ships transport in December, the partner selling transport has a shrinking business.
  5. Bookmark the source. The roadmap entry is live and machine readable. Watch it, and wait for the documentation before you promise a customer anything specific.
Tenant migrations have been a services business hiding inside an IT problem for more than a decade. Microsoft just walked into the room with a product. Decide now whether you are selling the pipe or the plan.

Sources

- Microsoft 365 roadmap API, item 576273: https://www.microsoft.com/releasecommunications/api/v2/m365?$filter=id eq 576273
- Microsoft 365 roadmap, feature 576273: https://www.microsoft.com/en-us/microsoft-365/roadmap?id=576273
- Microsoft 365 roadmap, all features: https://www.microsoft.com/en-us/microsoft-365/roadmap

Deep Microsoft licensing, incentive, and Partner Center guidance for resellers is published on Cloud Factory. Planning a tenant move, or want it validated before you commit? Talk to Cloud Factory.


Ready to grow your Microsoft practice? Explore Cloud Factory's partner platform →

Looking for your local Cloud Factory team? Find your country's contact →