Skip to content

Commit ac1ec22

Browse files
Merge pull request #110547 from curtand/dirind0407
[Azure AD licensing] tenant to organization
2 parents 69b1020 + 5865191 commit ac1ec22

File tree

1 file changed

+21
-16
lines changed

1 file changed

+21
-16
lines changed
Lines changed: 21 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Characteristics of multiple tenant interaction - Azure AD | Microsoft Docs
3-
description: Manage your Azure Active tenant tenants by understanding your tenants as fully independent resources
3+
description: Understanding your Azure Active Directory tenants as fully independent organizations
44
services: active-tenant
55
documentationcenter: ''
66
author: curtand
@@ -9,40 +9,45 @@ ms.service: active-directory
99
ms.topic: article
1010
ms.workload: identity
1111
ms.subservice: users-groups-roles
12-
ms.date: 11/08/2019
12+
ms.date: 04/07/2020
1313
ms.author: curtand
1414
ms.custom: it-pro
1515
ms.reviewer: sumitp
1616
ms.collection: M365-identity-device-management
1717
---
1818

19-
# Understand how multiple Azure Active Directory tenants interact
19+
# Understand how multiple Azure Active Directory organizations interact
2020

21-
In Azure Active Directory (Azure AD), each tenant is a fully independent resource: a peer that is logically independent from the other tenants that you manage. There is no parent-child relationship between tenants. This independence between tenants includes resource independence, administrative independence, and synchronization independence.
21+
In Azure Active Directory (Azure AD), each tenant is a fully independent organization: a peer that is logically independent from the other Azure AD organizations that you manage. This independence between organizations includes resource independence, administrative independence, and synchronization independence. There is no parent-child relationship between organizations.
2222

2323
## Resource independence
24-
* If you create or delete a resource in one tenant, it has no impact on any resource in another tenant, with the partial exception of external users.
25-
* If you use one of your domain names with one tenant, it cannot be used with any other tenant.
24+
25+
* If you create or delete an Azure AD resource in one organization, it has no impact on any resource in another organization, with the partial exception of external users.
26+
* If you register one of your domain names with one organization, it can't be used by any other organization.
2627

2728
## Administrative independence
28-
If a non-administrative user of tenant 'Contoso' creates a test tenant 'Test,' then:
2929

30-
* By default, the user who creates a tenant is added as an external user in that new tenant, and assigned the global administrator role in that tenant.
31-
* The administrators of tenant 'Contoso' have no direct administrative privileges to tenant 'Test,' unless an administrator of 'Test' specifically grants them these privileges. However, administrators of 'Contoso' can control access to tenant 'Test' if they control the user account that created 'Test.'
32-
* If you add/remove an administrator role for a user in one tenant, the change does not affect the administrator roles that the user has in another tenant.
30+
If a non-administrative user of organization 'Contoso' creates a test organization 'Test,' then:
31+
32+
* By default, the user who creates a organization is added as an external user in that new organization, and assigned the global administrator role in that organization.
33+
* The administrators of organization 'Contoso' have no direct administrative privileges to organization 'Test,' unless an administrator of 'Test' specifically grants them these privileges. However, administrators of 'Contoso' can control access to organization 'Test' if they control the user account that created 'Test.'
34+
* If you add or remove an Azure AD role for a user in one organization, the change does not affect the roles that the user is assigned in any other Azure AD organization.
3335

3436
## Synchronization independence
35-
You can configure each Azure AD tenant independently to get data synchronized from a single instance of either:
37+
38+
You can configure each Azure AD organization independently to get data synchronized from a single instance of either:
3639

3740
* The Azure AD Connect tool, to synchronize data with a single AD forest.
38-
* The Azure Active tenant Connector for Forefront Identity Manager, to synchronize data with one or more on-premises forests, and/or non-Azure AD data sources.
41+
* The Azure Active Directory Connector for Forefront Identity Manager, to synchronize data with one or more on-premises forests, and/or non-Azure AD data sources.
3942

40-
## Add an Azure AD tenant
41-
To add an Azure AD tenant in the Azure portal, sign in to [the Azure portal](https://portal.azure.com) with an account that is an Azure AD global administrator, and, on the left, select **New**.
43+
## Add an Azure AD organization
44+
45+
To add an Azure AD organization in the Azure portal, sign in to [the Azure portal](https://portal.azure.com) with an account that is an Azure AD global administrator, and select **New**.
4246

4347
> [!NOTE]
44-
> Unlike other Azure resources, your tenants are not child resources of an Azure subscription. If your Azure subscription is canceled or expired, you can still access your tenant data using Azure PowerShell, the Microsoft Graph API, or the Microsoft 365 admin center. You can also [associate another subscription with the tenant](../fundamentals/active-directory-how-subscriptions-associated-directory.md).
48+
> Unlike other Azure resources, your Azure AD organizations are not child resources of an Azure subscription. If your Azure subscription is canceled or expired, you can still access your Azure AD organization's data using Azure PowerShell, the Microsoft Graph API, or the Microsoft 365 admin center. You can also [associate another subscription with the organization](../fundamentals/active-directory-how-subscriptions-associated-directory.md).
4549
>
4650
4751
## Next steps
48-
For a broad overview of Azure AD licensing issues and best practices, see [What is Azure Active tenant licensing?](../fundamentals/active-directory-licensing-whatis-azure-portal.md).
52+
53+
For Azure AD licensing considerations and best practices, see [What is Azure Active Directory licensing?](../fundamentals/active-directory-licensing-whatis-azure-portal.md).

0 commit comments

Comments
 (0)