Merge pull request #250944 from rolyon/rolyon-mto-portal-entra-admin-center

[Azure AD MTO] Azure portal to Microsoft Entra admin center

Author: v-shils

articles/active-directory/includes/user-type-workload-limitations-include.md

@@ -13,6 +13,6 @@ ms.custom: include file
 
 | App or service | Limitations |
 | --- | --- |
-| Microsoft Teams | - External member isn't supported in [Teams Connect shared channels](/microsoftteams/platform/concepts/build-and-test/shared-channels).<br/>- Converting an external guest into an external member or converting an external member into an external guest isn't currently supported by Teams. For more information, see [Guest access in Microsoft Teams](/microsoftteams/guest-access). |
+| Microsoft Teams | - Converting an external guest into an external member or converting an external member into an external guest isn't currently supported by Teams. For more information, see [Guest access in Microsoft Teams](/microsoftteams/guest-access). |
 | Power BI | - Support for UserType Member in Power BI is currently in preview. For more information, see [Distribute Power BI content to external guest users with Azure AD B2B](/power-bi/enterprise/service-admin-azure-ad-b2b#who-can-you-invite). |
 | Azure Virtual Desktop | - External member and external guest aren't supported in Azure Virtual Desktop. |

articles/active-directory/multi-tenant-organizations/TOC.yml

@@ -35,7 +35,7 @@
     items:
     - name: Configure cross-tenant synchronization
       items:
-      - name: Portal
+      - name: Admin center
         href: cross-tenant-synchronization-configure.md
       - name: PowerShell or Graph API
         href: cross-tenant-synchronization-configure-graph.md

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

@@ -17,7 +17,7 @@ ms.custom: it-pro
 
 # Configure cross-tenant synchronization using PowerShell or Microsoft Graph API
 
-This article describes the key steps to configure cross-tenant synchronization using Microsoft Graph PowerShell or Microsoft Graph API. When configured, Azure AD automatically provisions and de-provisions B2B users in your target tenant. For detailed steps using the Azure portal, see [Configure cross-tenant synchronization](cross-tenant-synchronization-configure.md).
+This article describes the key steps to configure cross-tenant synchronization using Microsoft Graph PowerShell or Microsoft Graph API. When configured, Azure AD automatically provisions and de-provisions B2B users in your target tenant. For detailed steps using the Microsoft Entra admin center, see [Configure cross-tenant synchronization](cross-tenant-synchronization-configure.md).
 
 :::image type="content" source="./media/common/configure-diagram.png" alt-text="Diagram that shows cross-tenant synchronization between source tenant and target tenant." lightbox="./media/common/configure-diagram.png":::
 

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

@@ -1,6 +1,6 @@
 ---
 title: Configure cross-tenant synchronization
-description: Learn how to configure cross-tenant synchronization in Azure Active Directory using the Azure portal.
+description: Learn how to configure cross-tenant synchronization in Azure Active Directory using the Microsoft Entra admin center.
 services: active-directory
 author: rolyon
 manager: amycolannino
@@ -17,7 +17,7 @@ ms.custom: it-pro
 
 # Configure cross-tenant synchronization
 
-This article describes the steps to configure cross-tenant synchronization using the Azure portal. When configured, Azure AD automatically provisions and de-provisions B2B users in your target tenant. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](../app-provisioning/user-provisioning.md).
+This article describes the steps to configure cross-tenant synchronization using the Microsoft Entra admin center. When configured, Azure AD automatically provisions and de-provisions B2B users in your target tenant. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](../app-provisioning/user-provisioning.md).
 
 :::image type="content" source="./media/common/configure-diagram.png" alt-text="Diagram that shows cross-tenant synchronization between source tenant and target tenant." lightbox="./media/common/configure-diagram.png":::
 
@@ -59,11 +59,9 @@ By the end of this article, you'll be able to:
 
 ![Icon for the target tenant.](./media/common/icon-tenant-target.png)<br/>**Target tenant**
 
-1. Sign in to the [Azure portal](https://portal.azure.com) as an administrator in the target tenant.
+1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) of the target tenant.
 
-1. Select **Azure Active Directory** > **External Identities**.
-
-1. Select **Cross-tenant access settings**.
+1. Browse to **Identity** > **External Identities** > **Cross-tenant access settings**.
 
 1. On the **Organization settings** tab, select **Add organization**.
 
@@ -101,11 +99,9 @@ In this step, you automatically redeem invitations so users from the source tena
 
 In this step, you automatically redeem invitations in the source tenant.
 
-1. Sign in to the [Azure portal](https://portal.azure.com) as an administrator of the source tenant.
-
-1. Select **Azure Active Directory** > **External Identities**.
+1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) of the source tenant.
 
-1. Select **Cross-tenant access settings**.
+1. Browse to **Identity** > **External Identities** > **Cross-tenant access settings**.
 
 1. On the **Organization settings** tab, select **Add organization**.
 
@@ -127,9 +123,7 @@ In this step, you automatically redeem invitations in the source tenant.
 
 ![Icon for the source tenant.](./media/common/icon-tenant-source.png)<br/>**Source tenant**
 
-1. In the source tenant, select **Azure Active Directory** > **Cross-tenant synchronization**.
-
-    :::image type="content" source="./media/cross-tenant-synchronization-configure/azure-ad-overview.png" alt-text="Screenshot that shows the Azure Active Directory Overview page." lightbox="./media/cross-tenant-synchronization-configure/azure-ad-overview.png":::
+1. In the source tenant, browse to **Identity** > **External Identities** > **Cross-tenant synchronization**.
 
 1. Select **Configurations**.
 
@@ -326,7 +320,7 @@ Attribute mappings allow you to define how data should flow between the source t
 
 Now that you have a configuration, you can test on-demand provisioning with one of your users.
 
-1. In the source tenant, select **Azure Active Directory** > **Cross-tenant synchronization**.
+1. In the source tenant, browse to **Identity** > **External Identities** > **Cross-tenant synchronization**.
 
 1. Select **Configurations** and then select your configuration.
 
@@ -364,7 +358,7 @@ Now that you have a configuration, you can test on-demand provisioning with one
 
 The provisioning job starts the initial synchronization cycle of all users defined in **Scope** of the **Settings** section. The initial cycle takes longer to perform than subsequent cycles, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running.
 
-1. In the source tenant, select **Azure Active Directory** > **Cross-tenant synchronization**.
+1. In the source tenant, browse to **Identity** > **External Identities** > **Cross-tenant synchronization**.
 
 1. Select **Configurations** and then select your configuration.
 
@@ -406,9 +400,7 @@ Once you've started a provisioning job, you can monitor the status.
 
 Even though users are being provisioned in the target tenant, they still might be able to remove themselves. If users remove themselves and they are in scope, they'll be provisioned again during the next provisioning cycle. If you want to disallow the ability for users to remove themselves from your organization, you must configure the **External user leave settings**.
 
-1. In the target tenant, select **Azure Active Directory**.
-
-1. Select **External Identities** > **External collaboration settings**.
+1. In the target tenant, browse to **Identity** > **External Identities** > **External collaboration settings**.
 
 1. Under **External user leave settings**, choose whether to allow external users to leave your organization themselves.
 
@@ -420,7 +412,7 @@ This setting also applies to B2B collaboration and B2B direct connect, so if you
 
 Follows these steps to delete a configuration on the **Configurations** page.
 
-1. In the source tenant, select **Azure Active Directory** > **Cross-tenant synchronization**.
+1. In the source tenant, browse to **Identity** > **External Identities** > **Cross-tenant synchronization**.
 
 1. On the **Configurations** page, add a check mark next to the configuration you want to delete.
 

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

@@ -84,7 +84,7 @@ To configure this setting using Microsoft Graph, see the [Update crossTenantAcce
 
 #### How do users know what tenants they belong to?
 
-For cross-tenant synchronization, users don't receive an email or have to accept a consent prompt. If users want to see what tenants they belong to, they can open their [My Account](https://support.microsoft.com/account-billing/my-account-portal-for-work-or-school-accounts-eab41bfe-3b9e-441e-82be-1f6e568d65fd) page and select **Organizations**. In the Azure portal, users can open their [Azure portal settings](../../azure-portal/set-preferences.md), view their **Directories + subscriptions**, and switch directories.
+For cross-tenant synchronization, users don't receive an email or have to accept a consent prompt. If users want to see what tenants they belong to, they can open their [My Account](https://support.microsoft.com/account-billing/my-account-portal-for-work-or-school-accounts-eab41bfe-3b9e-441e-82be-1f6e568d65fd) page and select **Organizations**. In the Microsoft Entra admin center, users can open their [Portal settings](../../azure-portal/set-preferences.md), view their **Directories + subscriptions**, and switch directories.
 
 For more information, including privacy information, see [Leave an organization as an external user](../external-identities/leave-the-organization.md).
 

articles/active-directory/multi-tenant-organizations/index.yml

@@ -70,7 +70,7 @@ landingContent:
     linkLists:
       - linkListType: how-to-guide
         links:
-          - text: Azure portal
+          - text: Admin center
             url: cross-tenant-synchronization-configure.md
           - text: PowerShell or Microsoft Graph API
             url: cross-tenant-synchronization-configure-graph.md

articles/active-directory/multi-tenant-organizations/media/cross-tenant-synchronization-configure/access-settings-organization-add.png

@@ -86,7 +86,7 @@ The experiences and issues described in this article have the following scope.
 
 - Microsoft 365 admin center / Azure AD: If you're using Azure AD cross-tenant synchronization to provision your users, rather than the Microsoft 365 admin center share users functionality, Microsoft 365 admin center indicates an **Outbound sync status** of **Not configured**. This is expected preview behavior. Currently, Microsoft 365 admin center only shows the status of Azure AD cross-tenant synchronization jobs created and managed by Microsoft 365 admin center and doesn't display Azure AD cross-tenant synchronizations created and managed in Azure AD.
 
-- Microsoft 365 admin center / Azure AD: If you view Azure AD cross-tenant synchronization in Azure portal, after adding tenants to or after joining a multi-tenant organization in Microsoft 365 admin center, you'll see a cross-tenant synchronization configuration with the name MTO_Sync_<TenantID>. Refrain from editing or changing the name if you want Microsoft 365 admin center to recognize the configuration as created and managed by Microsoft 365 admin center.
+- Microsoft 365 admin center / Azure AD: If you view Azure AD cross-tenant synchronization in Microsoft Entra admin center, after adding tenants to or after joining a multi-tenant organization in Microsoft 365 admin center, you'll see a cross-tenant synchronization configuration with the name MTO_Sync_<TenantID>. Refrain from editing or changing the name if you want Microsoft 365 admin center to recognize the configuration as created and managed by Microsoft 365 admin center.
 
 - Microsoft 365 admin center / Azure AD: There's no established or supported pattern for Microsoft 365 admin center to take control of pre-existing Azure AD cross-tenant synchronization configurations and jobs.
 

articles/active-directory/multi-tenant-organizations/media/cross-tenant-synchronization-configure/azure-ad-overview.png

@@ -169,8 +169,8 @@ Your multi-tenant organization is formed.
 Depending on your use case, you may want to synchronize users using one of the following methods:
 
 - [Synchronize users in multi-tenant organizations in Microsoft 365 (Preview)](/microsoft-365/enterprise/sync-users-multi-tenant-orgs)
-- [Configure cross-tenant synchronization using the Azure portal](cross-tenant-synchronization-configure.md)
-- [Configure cross-tenant synchronization using Microsoft Graph API](cross-tenant-synchronization-configure-graph.md)
+- [Configure cross-tenant synchronization](cross-tenant-synchronization-configure.md)
+- [Configure cross-tenant synchronization using PowerShell or Microsoft Graph API](cross-tenant-synchronization-configure-graph.md)
 - Your alternative bulk provisioning engine
 
 ## Limits