Skip to content

Commit 4f8d6bd

Browse files
Update cross-tenant-synchronization-overview.md
1 parent 7024a87 commit 4f8d6bd

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,8 @@ Here are the primary goals of cross-tenant synchronization:
2929
- Automate lifecycle management of B2B collaboration users in a multi-tenant organization
3030
- Automatically remove B2B accounts when a user leaves the organization
3131

32+
> [!VIDEO https://www.youtube.com/embed/7B-PQwNfGBc]
33+
3234
## Why use cross-tenant synchronization?
3335

3436
Cross-tenant synchronization automates creating, updating, and deleting B2B collaboration users. Users created with cross-tenant synchronization are able to access both Microsoft applications (such as Teams and SharePoint) and non-Microsoft applications (such as [ServiceNow](../saas-apps/servicenow-provisioning-tutorial.md), [Adobe](../saas-apps/adobe-identity-management-provisioning-tutorial.md), and many more), regardless of which tenant the apps are integrated with. These users continue to benefit from the security capabilities in Azure AD, such as [Azure AD Conditional Access](../conditional-access/overview.md) and [cross-tenant access settings](../external-identities/cross-tenant-access-overview.md), and can be governed through features such as [Azure AD entitlement management](../governance/entitlement-management-overview.md).

0 commit comments

Comments
 (0)