![]() Some organizations might have complex internal structures across multiple business units, or they might require a high level of isolation and autonomy between parts of their organization. Business unit or organizational isolation and autonomy requirements Most organizations can comply with the frameworks within a single Microsoft Entra tenant by using features, such as Privileged Identity Management and Administrative units. ![]() Like in the previous scenarios, if your organization has a regulatory or country/region compliance framework to comply with, you might not require multiple Microsoft Entra tenants as the default approach. Microsoft Entra authentication & national/regional clouds.Azure China Cross-border connectivity and interoperability.The Microsoft Entra tenants are solely for that national Azure cloud instance and are used for the Azure subscriptions identity and access management services within that Azure cloud instance.įor more information about Azure national/regional cloud’s identity scenarios, see: These national Azure cloud instances require their own Microsoft Entra tenants. But this particular requirement is usually addressed within a single Microsoft Entra tenant using features, such as Microsoft 365 Multi-Geo.Īnother scenario is when organizations require Azure Government (US Government) or Azure China (operated by 21Vianet). Some organizations that have offices and users around the globe with stricter data residency regulations might also create multiple Microsoft Entra tenants. Organizations might create multiple Microsoft Entra tenants to meet and comply with these frameworks. Some organizations have strict regulatory or country/region compliance controls and frameworks (for example, UK Official, Sarbanes Oxley (SOX), or NIST). Regulatory or country/region compliance requirements If an organization keeps the Microsoft Entra tenants isolated and they don't consolidate them, there's less work if there's a future merger or acquisition of a single entity. This scenario can also occur when the organizations or companies want to remain separate because other organizations might acquire their company in the future. So, consolidating tenants is preferred because a single custom domain name can be used by all identities when a merger or acquisition scenario occurs.īecause of the complexities of consolidating two Microsoft Entra tenants into one, sometimes the tenants are left alone and remain separate for an extended or indefinite period of time. This consolidation reduces the management overhead, improves the collaboration experience, and presents a single brand identity to other companies and organizations.Ī custom domain name (for example, ) can only be associated with one Microsoft Entra tenant at a time. Typically, in an acquisition, the two Microsoft Entra tenants are consolidated into a single Microsoft Entra tenant. ![]() These acquisitions are likely to have existing Microsoft Entra tenants already established that host and provide services, such as Microsoft 365 (Exchange Online, SharePoint, OneDrive, or Teams), Dynamics 365, and Microsoft Azure, to the company or organization. Tenant level testing / Microsoft 365 testingĪs organizations grow over time, they might acquire other companies or organizations.Independent software vendor (ISV) delivering SaaS applications from Azure.Business unit or organizational isolation and autonomy requirements.Regulatory or country/region compliance requirements.There are a few reasons why an organization might need, or might want to investigate, multiple Microsoft Entra tenants.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |