Share via

Feedback for Entra ID - Tenant Transfer across accounts and Renaming Default Domain

Rajesh Swarnkar 1,236 Reputation points
2026-05-19T15:36:02.44+00:00

Hi there,

As a long user for Azure and Entra ID, I have noted project few edge cases where entra id fails to support these lift and shift. So I would like to mention those here, just in case if someone lookups up ;)

  • For a merge case, Contoso is being acquired by the new entity Litware (which may or may not have Azure Account). Such case it becomes impossible to rename the default domain contoso.onmicrosoft.com leaving only option to create new with some other name
  • Currently its not possible to simply lift and shift the Entra Tenant. From the layman perspective this must be supported case, whether from the API or via a support case.

Thanks

Microsoft Security | Microsoft Entra | Microsoft Entra ID

Answer accepted by question author

Rukmini 42,510 Reputation points Microsoft External Staff Moderator
2026-05-19T16:29:40.22+00:00

Hey Rajesh, you’ve hit two common “lift-and-shift” pain points with Microsoft Entra ID (formerly Azure AD). Here’s the low-down and what you can do today:

  1. You can’t rename the built-in <tenantName>.onmicrosoft.com domain
    • That default onmicrosoft.com namespace is immutable by design—you’ll always have one, and you can’t change its prefix.
    • Workaround: add a custom domain (for example, “litware.com”), verify it, then set that as your primary/default domain for users and apps. The original onmicrosoft.com stays behind but won’t be used for new objects.
  2. You can’t “move” or “rehome” an entire Entra tenant across two Azure accounts
    • Tenants are bound to a billing account/subscription boundary. There’s no API or support case today that detaches a tenant wholesale from one Azure billing root and drops it into another.
    • What you can do instead: • Transfer each Azure subscription from one directory to another (via the Transfer Subscription guidance). Note resources will need post-transfer reconfiguration (role assignments, managed identities, etc.). • Invite the new account’s Global Admin as a co-admin of the tenant and shift management there.

If your main goal is to preserve users, groups, apps, etc., you’ll often end up doing a combination of: export/import, cross-tenant synchronization (B2B), or script-driven reprovisioning rather than a true “lift‐and‐shift.”

Hope that helps! Let me know if you need more specifics on any of these steps.

Reference list

  1. Manage domain names (add custom domains, PowerShell/Graph): https://docs.microsoft.com/azure/active-directory/active-directory-domains-manage-azure-portal#use-powershell-or-graph-api-to-manage-domain-names
  2. Transfer an Azure subscription to a different Entra directory: https://docs.microsoft.com/azure/role-based-access-control/transfer-subscription
  3. Transfer ownership of an Azure subscription to another account: https://docs.microsoft.com/azure/billing/billing-subscription-transfer

Note: This content was drafted with the help of an AI system. Please verify the information before relying on it for decision-making.

Was this answer helpful?

1 person found this answer helpful.
0 comments

Answer accepted by question author

AI answer

2026-05-19T15:36:18.6166667+00:00

Microsoft Entra ID tenants are designed as isolated identity and access management boundaries and cannot be renamed, moved, or “lifted and shifted” between accounts or organizations.

Key points based on current capabilities:

  1. Default *.onmicrosoft.com domain rename
    • The default contoso.onmicrosoft.com domain in a tenant cannot be renamed or transferred to another tenant.
    • For mergers and acquisitions, guidance is to either:
      • Keep both tenants and integrate them (for example, using B2B collaboration, cross-tenant synchronization, or multitenant organization features), or
      • Consolidate into a single tenant and migrate identities, apps, and data, leaving the original *.onmicrosoft.com name as-is in the background.
    • Tenants are the core identity and collaboration boundary for Microsoft 365 and Entra ID; the default domain is part of that boundary and is not a movable asset.
  2. Tenant “lift and shift” across accounts or organizations
    • A Microsoft Entra tenant is an instance that contains users, groups, devices, apps, and policies, and it is securely isolated from other tenants. It also can be bound to a specific region or cloud for data residency and compliance.
    • Because of this isolation and residency model, there is no supported mechanism (portal, API, or support case) to move an entire tenant wholesale to another account, subscription owner, or organization.
    • For M&A or restructuring scenarios, Microsoft provides patterns instead of tenant transfer, such as:
      • Keeping multiple tenants in parallel and integrating them (for example, maintaining Litware’s tenant while Contoso keeps its own, and using cross-tenant access, B2B, and app provisioning).
      • Using multitenant user management and cross-tenant synchronization to provide seamless access to apps across tenants.
  3. Recommended approaches for M&A and multi-tenant scenarios
    • When one company acquires another (for example, Contoso and Litware), options include:
      • Maintain both tenants and:
        • Use B2B collaboration and cross-tenant synchronization to provision users from one tenant into another for app access.
        • Use parallel provisioning where each tenant provisions its own users into shared SaaS apps (where supported).
      • Consolidate tenants over time by migrating workloads and identities into a chosen “primary” tenant, accepting that the original *.onmicrosoft.com names remain in the background.
    • Microsoft explicitly recommends a single tenant wherever possible, and when that is not possible, to use the multitenant patterns documented for user lifecycle management and app access instead of attempting to move or rename tenants.

These behaviors (non-renamable default domain and non-movable tenants) are by design and are handled today through integration and migration patterns rather than tenant transfer or renaming operations.

References:

AI-generated content may be incorrect. Read our transparency notes for more information.

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.