A cloud-based identity and access management service for securing user authentication and resource access
A few things to clarify:
- A Microsoft 365 tenant = an Entra ID tenant.
- A **custom domain (like
company.com) can only be verified and assigned to one tenant at a time. - The initial
something.onmicrosoft.comdomain is unique and permanently tied to that tenant—it can’t be duplicated or moved.
So, in your scenario:
- The customer already has a Microsoft 365 tenant (
company.onmicrosoft.com) where the custom domaincompany.comis registered. - You can absolutely create a brand-new Entra ID / Azure tenant (
company2.onmicrosoft.com). That part is straightforward. - However, you cannot attach
company.comto both tenants at the same time. Microsoft enforces this to prevent conflicts in user identity and sign-in. - To use the same
@company.comaddresses in the new tenant, you would first need to removecompany.comfrom the existing tenant, which would break the customer’s Microsoft 365 services tied to that domain.
Options you have:
- Keep a single tenant: Recommended if the customer wants unified identity and access with their
@company.comaccounts. - Create the second tenant (
company2.onmicrosoft.com) but only use its default domain or add a different custom domain (e.g.,apps.company.com,company2.com). - If the reason is separation of workloads (e.g., testing, dev, or isolation), you can use multi-tenant apps, guest access (B2B), or cross-tenant synchronization instead of moving the domain.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin