Skip to content

Commit 217f28f

Browse files
authored
Fix link at secure-with-azure-ad-multiple-tenants.md
1 parent ae759b8 commit 217f28f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/active-directory/fundamentals/secure-with-azure-ad-multiple-tenants.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.collection: M365-identity-device-management
1717

1818
# Resource isolation with multiple tenants
1919

20-
There are specific scenarios when delegating administration within a single tenant boundary won't meet your needs. In this section, we'll discuss requirements that may drive you to create a multi-tenant architecture. Multi-tenant organizations might span two or more Azure AD tenants. This can result in unique cross-tenant collaboration and management requirements. Multi-tenant architectures increase management overhead and complexity and should be used with caution. We recommend using a single tenant if your needs can be met with that architecture. For more detailed information, see [Multi-tenant user management]../fundamentals/multi-tenant-user-management-introduction.md).
20+
There are specific scenarios when delegating administration within a single tenant boundary won't meet your needs. In this section, we'll discuss requirements that may drive you to create a multi-tenant architecture. Multi-tenant organizations might span two or more Azure AD tenants. This can result in unique cross-tenant collaboration and management requirements. Multi-tenant architectures increase management overhead and complexity and should be used with caution. We recommend using a single tenant if your needs can be met with that architecture. For more detailed information, see [Multi-tenant user management](multi-tenant-user-management-introduction.md).
2121

2222
A separate tenant creates a new boundary, and therefore decoupled management of Azure AD directory roles, directory objects, conditional access policies, Azure resource groups, Azure management groups, and other controls as described in previous sections.
2323

@@ -183,4 +183,4 @@ Devices: This tenant contains a reduced number of devices; only those that are n
183183

184184
* [Resource isolation in a single tenant](secure-with-azure-ad-single-tenant.md)
185185

186-
* [Best practices](secure-with-azure-ad-best-practices.md)
186+
* [Best practices](secure-with-azure-ad-best-practices.md)

0 commit comments

Comments
 (0)