Skip to content

Commit dee523c

Browse files
Update cross-tenant-synchronization-overview.md
1 parent 30ce50f commit dee523c

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/active-directory/multi-tenant-organizations/cross-tenant-synchronization-overview.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.workload: identity
99
ms.subservice: multi-tenant-organizations
1010
ms.topic: overview
11-
ms.date: 01/23/2023
11+
ms.date: 02/02/2023
1212
ms.author: rolyon
1313
ms.custom: it-pro
1414

@@ -121,7 +121,9 @@ For anyone that has used Azure AD to [provision identities into a SaaS applicati
121121

122122
## License requirements
123123

124-
Using this feature requires Azure AD Premium P1 licenses. Each user who is synchronized with cross-tenant synchronization must have a P1 license in their home/source tenant. To find the right license for your requirements, see [Compare generally available features of Azure AD](https://www.microsoft.com/security/business/identity-access-management/azure-ad-pricing).
124+
In the source tenant: Using this feature requires Azure AD Premium P1 licenses. Each user who is synchronized with cross-tenant synchronization must have a P1 license in their home/source tenant. To find the right license for your requirements, see [Compare generally available features of Azure AD](https://www.microsoft.com/security/business/identity-access-management/azure-ad-pricing).
125+
126+
In the target tenant: Cross-tenant sync relies on the Azure AD External Identities billing model. To understand the external identities licensing model, see [MAU billing model for Azure AD External Identities](../external-identities/external-identities-pricing.md)
125127

126128
## Frequently asked questions
127129

0 commit comments

Comments
 (0)