Consolidating two tenants: you pay twice before you pay less
Someone in the room says "we'll save a fortune by collapsing these two tenants into one." They are right — eventually. First there is a stretch where the same people are licensed in both places at once, and the bill goes up, not down.
New to cloud? CAMPUX is a free, build-first course. Start here →
Tenant consolidation gets sold as a cost-cutting move, and over a long enough horizon it is one. But the money does not run downhill the whole way. This note is part of the Azure tenant-to-tenant migration guide, and its job is the unglamorous part: the spend that lands before a single dollar of saving. If you pitch consolidation without owning that shape, you set an expectation the first invoice will embarrass.
The cost of coexistence: paying for the same person twice
Migrations are not instant, and a person cannot be half-moved. During the coexistence window a user often needs a working seat in both directions at once — the source tenant they still log into every morning, and the target tenant being provisioned around them. So both get licensed. Multiply that overlap by your headcount and you have the defining cost of a consolidation: every month the two tenants run in parallel is a month of doubled license spend, sitting on top of whatever the project itself costs. It is also open audit exposure, because you are now paying for entitlements in two billing accounts that have to reconcile to one workforce.
This is why the length of coexistence is not a scheduling detail — it is the budget. A tight cutover that closes the source tenant in weeks costs a fraction of a migration that drifts across two annual renewals, doubling seats the entire way. Whoever runs the plan is, whether they frame it this way or not, managing a meter.
Every month both tenants stay lit is a month you buy the same workforce twice.
The line items Microsoft charges for
The headline one is the migration license. To move a mailbox between tenants, Microsoft requires a Cross Tenant User Data Migration license — a per-user, one-time add-on you assign to either the source or the target user object, and which also covers that user's OneDrive migration. It is not optional plumbing you can skip: if neither the source nor the target object holds the license, the mailbox move fails outright with an error stating no Cross Tenant User Data Migration license was found. Shared, resource, and room mailboxes are the exception and do not need it. Budget it as a flat per-migrated-user cost, once, and stamp it before you cut over.
Around that sits tooling. Microsoft's native story covers mailbox and OneDrive; it does not hand you a single button that merges two tenants whole. Teams, SharePoint content, and identity re-mapping are where most teams reach for third-party migration software, and that licensing is a real line item you size to the scope, not an afterthought.
Four buckets, all spent before the saving starts. One, doubled subscription licenses for every user across the whole coexistence window. Two, the per-user Cross Tenant User Data Migration license for each mailbox and OneDrive you move. Three, third-party tooling for the workloads Microsoft's native path does not carry. Four, the labor — the engineers planning cutover waves, standing up mail flow and calendar coexistence, and babysitting the moves. The first bucket scales with time; the rest scale with scope.
The labor nobody lines up in the quote
The invoice from Microsoft is the easy part to forecast. The effort is not, and it is usually the larger number. Someone has to inventory both estates, map identities, sequence users into waves, configure cross-tenant trust and mail-flow coexistence so mail and calendars keep working mid-move, then run and verify each batch. That is weeks of senior time, and senior time is not cheap. When a consolidation "costs more than expected," the licenses rarely blew the budget — the project did. Treat the labor as a headline figure in the business case, not a footnote, or the finance conversation goes badly at exactly the wrong moment.
Where the money comes back
Now the good half. Once the source tenant is dark, you run one tenant instead of two, and the duplication that quietly drained money disappears. Redundant subscriptions collapse into one set of seats. Split purchasing becomes a single agreement — your whole user base counting toward one volume commitment on an Enterprise Agreement or Microsoft Customer Agreement, which is where negotiating power lives. Administration stops being done twice.
On the Azure side, a combined estate is a right-sizing opportunity. With everything under one billing account you can see consumption whole in Cost Management, then commit the steady baseline to reservations — one or three-year commitments that cut pay-as-you-go rates by up to 72% on matching resources — and cover variable compute with a savings plan. Two fragmented estates rarely each hit the consistent usage that makes those commitments pay; one consolidated estate does. The honest caveat: the payback timeline is entirely a function of how long coexistence ran. A short overlap pays back fast. A migration that dragged can spend a year of single-tenant savings just clawing back what the doubled licenses cost.
The takeaway
Consolidation is a real saving wearing an upfront cost as a disguise. You pay twice during coexistence, you pay the per-user Cross Tenant User Data Migration license for every mailbox and OneDrive you move, you pay for tooling Microsoft's native path does not cover, and you pay a large labor bill to run it. Then, and only then, the single-tenant economics arrive: one agreement, consolidated purchasing, reservations and savings plans on the combined estate, and half the administration. "It saves money after cutover, and the payback depends on how fast we close the second tenant" is the sentence that keeps the finance team on your side.
Questions people also ask
Does consolidating tenants actually save money?
Yes, but only after cutover. Running one tenant instead of two removes duplicated subscriptions, duplicated administration, and split purchasing. You consolidate onto a single agreement, so your whole user base counts toward one volume commitment, and you can right-size and buy reservations across the combined estate. The catch is that none of that lands while both tenants are still live.
What is the Cross Tenant User Data Migration license?
It is a per-user, one-time add-on license Microsoft requires to move a mailbox between tenants, and it also covers the matching OneDrive migration. You assign it to either the source or the target user object. If neither object has it, the migration fails with an error saying no Cross Tenant User Data Migration license was found. Shared, resource, and room mailboxes do not need it.
Why do you pay for licenses twice during a tenant migration?
Because migration is not instant. During coexistence a user often needs a working seat in both places at once — the old tenant they still log into and the new tenant being provisioned — so both are licensed for the overlap. Every month the two tenants run in parallel is a month of double license spend, which is why shortening coexistence is the single biggest lever on total cost.
How long should tenant coexistence last?
As short as you can safely make it, because the overlap is what you pay twice for. The honest answer is that it depends on user count, data volume, and how much mail flow and calendar coexistence you must stand up. A tightly run cutover of a few weeks costs far less in doubled licenses than a migration that drifts across two annual renewals.
Is there a native Microsoft tool to merge two tenants?
There is no single button that merges two tenants. Microsoft supports cross-tenant mailbox and OneDrive migration with the paid per-user license, but many organizations still add third-party tooling to move Teams, SharePoint, and identity, and to orchestrate the cutover. That tooling is a real line item you budget alongside the licenses and the labor.