Merge pull request #225984 from rolyon/rolyon-mto-configure-portal-feedback

[Azure AD MTO] Configure steps update

Author: prmerger-automator[bot]

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

@@ -8,7 +8,7 @@ ms.service: active-directory
 ms.workload: identity
 ms.subservice: multi-tenant-organizations
 ms.topic: how-to
-ms.date: 01/31/2023
+ms.date: 02/01/2023
 ms.author: rolyon
 ms.custom: it-pro
 
@@ -21,7 +21,7 @@ ms.custom: it-pro
 > Cross-tenant synchronization is currently in PREVIEW.
 > See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
 
-This article describes the keys steps to configure cross-tenant synchronization using 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 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).
 
 :::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":::
 
@@ -158,7 +158,7 @@ These steps describe how to use Microsoft Graph Explorer (recommended), but you
     Content-Type: application/json
     
     {
-      "tenantId": "376a1f89-b02f-4a85-8252-2974d1984d14",
+      "tenantId": "376a1f89-b02f-4a85-8252-2974d1984d14"
     }
     ```
     

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

@@ -8,7 +8,7 @@ ms.service: active-directory
 ms.workload: identity
 ms.subservice: multi-tenant-organizations
 ms.topic: how-to
-ms.date: 01/23/2023
+ms.date: 02/01/2023
 ms.author: rolyon
 ms.custom: it-pro
 
@@ -82,7 +82,7 @@ By the end of this article, you'll be able to:
 
 In this step, you automatically redeem invitations so users from the source tenant don't have to accept the consent prompt. This setting must be checked in both the source tenant (outbound) and target tenant (inbound). For more information, see [Automatic redemption setting](cross-tenant-synchronization-overview.md#automatic-redemption-setting).
 
-1. Select  the **Trust settings** tab.
+1. In the target tenant, on the same **Inbound access settings** page, select the **Trust settings** tab.
 
 1. Check the **Suppress consent prompts for users from the other tenant when they access apps and resources in my tenant** check box.
 
@@ -96,7 +96,7 @@ 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 target 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**.
 
@@ -122,7 +122,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. Select **Azure Active Directory** > **Cross-tenant synchronization (Preview)**.
+1. In the source tenant, select **Azure Active Directory** > **Cross-tenant synchronization (Preview)**.
 
     :::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":::
 
@@ -140,7 +140,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 configuration list, select your configuration. 
+1. In the source tenant, in the configuration list, select your configuration. 
 
     :::image type="content" source="./media/cross-tenant-synchronization-configure/configuration-select.png" alt-text="Screenshot that shows the Cross-tenant synchronization Configurations page and a new configuration." lightbox="./media/cross-tenant-synchronization-configure/configuration-select.png":::
 
@@ -177,7 +177,7 @@ The Azure AD provisioning service allows you to define who will be provisioned i
 
 Start small. Test with a small set of users before rolling out to everyone. When the scope for provisioning is set to assigned users and groups, you can control it by assigning one or two users to the configuration. You can further refine who is in scope for provisioning by creating attribute-based scoping filters, described in the [next step](#step-8-optional-define-who-is-in-scope-for-provisioning-with-scoping-filters).
 
-1. Select **Provisioning** and expand the **Settings** section.
+1. In the source tenant, select **Provisioning** and expand the **Settings** section.
 
     :::image type="content" source="./media/cross-tenant-synchronization-configure/provisioning-settings-edit.png" alt-text="Screenshot of the Provisioning page that shows the Settings section with the Scope and Provisioning Status options." lightbox="./media/cross-tenant-synchronization-configure/provisioning-settings-edit.png":::
 
@@ -214,7 +214,7 @@ Start small. Test with a small set of users before rolling out to everyone. When
 
 Regardless of the value you selected for **Scope** in the previous step, you can further limit which users are synchronized by creating attribute-based scoping filters.
 
-1. Select **Provisioning** and expand the **Mappings** section.
+1. In the source tenant, select **Provisioning** and expand the **Mappings** section.
 
 1. Select **Provision Azure Active Directory Users**.
 
@@ -244,7 +244,7 @@ Regardless of the value you selected for **Scope** in the previous step, you can
 
 Attribute mappings allow you to define how data should flow between the source tenant and target tenant. For information on how to customize the default attribute mappings, see [Tutorial - Customize user provisioning attribute-mappings for SaaS applications in Azure Active Directory](../app-provisioning/customize-application-attributes.md).
 
-1. Select **Provisioning** and expand the **Mappings** section.
+1. In the source tenant, select **Provisioning** and expand the **Mappings** section.
 
 1. Select **Provision Azure Active Directory Users**.
 
@@ -296,7 +296,7 @@ Attribute mappings allow you to define how data should flow between the source t
 
 ![Icon for the source tenant.](./media/common/icon-tenant-source.png)<br/>**Source tenant**
 
-1. Select **Provisioning** and expand the **Settings** section.
+1. In the source tenant, select **Provisioning** and expand the **Settings** section.
 
     :::image type="content" source="./media/cross-tenant-synchronization-configure/provisioning-settings-edit.png" alt-text="Screenshot of the Provisioning page that shows the Settings section with the Scope and Provisioning Status options." lightbox="./media/cross-tenant-synchronization-configure/provisioning-settings-edit.png":::