Resolving Links

Author: whhender

articles/data-factory/how-to-access-secured-purview-account.md

@@ -21,8 +21,8 @@ If your Azure Purview account is protected by firewall and denies public access,
 
 | Scenario                                                     | Required Azure Purview private endpoints                           |
 | ------------------------------------------------------------ | ------------------------------------------------------------ |
-| [Run pipeline and report lineage to Azure Purview](tutorial-push-lineage-to-purview.md) | For Data Factory pipeline to push lineage to Azure Purview, Azure Purview ***account*** and ***ingestion*** private endpoints are required. <br>- When using **Azure Integration Runtime**, follow the steps in [Managed private endpoints for Azure Purview](#managed-private-endpoints-for-azure-purview) section to create managed private endpoints in the Data Factory managed virtual network.<br>- When using **Self-hosted Integration Runtime**, follow the steps in [this section](../purview/catalog-private-link-end-to-end.md#option-2---enable-account-portal-and-ingestion-private-endpoint-on-existing-azure-purview-accounts) to create the *account* and *ingestion* private endpoints in your integration runtime's virtual network. |
-| [Discover and explore data using Azure Purview on ADF UI](how-to-discover-explore-purview-data.md) | To use the search bar at the top center of Data Factory authoring UI to search for Azure Purview data and perform actions, you need to create Azure Purview ***account*** and ***portal*** private endpoints in the virtual network that you launch the Data Factory Studio. Follow the steps in [Enable *account* and *portal* private endpoint](../purview/catalog-private-link-account-portal.md#option-2---enable-account-and-portal-private-endpoint-on-existing-azure-purview-accounts). |
+| [Run pipeline and report lineage to Azure Purview](tutorial-push-lineage-to-purview.md) | For Data Factory pipeline to push lineage to Azure Purview, Azure Purview ***account*** and ***ingestion*** private endpoints are required. <br>- When using **Azure Integration Runtime**, follow the steps in [Managed private endpoints for Azure Purview](#managed-private-endpoints-for-azure-purview) section to create managed private endpoints in the Data Factory managed virtual network.<br>- When using **Self-hosted Integration Runtime**, follow the steps in [this section](../purview/catalog-private-link-end-to-end.md#option-2---enable-account-portal-and-ingestion-private-endpoint-on-existing-microsoft-purview-accounts) to create the *account* and *ingestion* private endpoints in your integration runtime's virtual network. |
+| [Discover and explore data using Azure Purview on ADF UI](how-to-discover-explore-purview-data.md) | To use the search bar at the top center of Data Factory authoring UI to search for Azure Purview data and perform actions, you need to create Azure Purview ***account*** and ***portal*** private endpoints in the virtual network that you launch the Data Factory Studio. Follow the steps in [Enable *account* and *portal* private endpoint](../purview/catalog-private-link-account-portal.md#option-2---enable-account-and-portal-private-endpoint-on-existing-microsoft-purview-accounts). |
 
 ## Managed private endpoints for Azure Purview
 

articles/purview/catalog-private-link-account-portal.md

@@ -35,7 +35,7 @@ Using one of the deployment options from this guide, you can deploy a new Micros
    - Deploy new Azure DNS zones using the steps explained further in this guide.
    - Add required DNS records to existing Azure DNS zones using the steps explained further in this guide.
    - After completing the steps in this guide, add required DNS A records in your existing DNS servers manually.
-3. Deploy a [new Microsoft Purview account](#option-1---deploy-a-new-azure-purview-account-with-account-and-portal-private-endpoints) with account and portal private endpoints, or deploy account and portal private endpoints for an [existing Microsoft Purview account](#option-2---enable-account-and-portal-private-endpoint-on-existing-azure-purview-accounts).
+3. Deploy a [new Microsoft Purview account](#option-1---deploy-a-new-microsoft-purview-account-with-account-and-portal-private-endpoints) with account and portal private endpoints, or deploy account and portal private endpoints for an [existing Microsoft Purview account](#option-2---enable-account-and-portal-private-endpoint-on-existing-microsoft-purview-accounts).
 4. [Enable access to Azure Active Directory](#enable-access-to-azure-active-directory) if your private network has network security group rules set to deny for all public internet traffic.
 5. After completing this guide, adjust DNS configurations if needed.
 6. Validate your network and name resolution from management machine to Microsoft Purview. 

articles/purview/catalog-private-link-end-to-end.md

@@ -37,7 +37,7 @@ Using one of the deployment options explained further in this guide, you can dep
    - Deploy new Azure DNS zones using the steps explained further in this guide.
    - Add required DNS records to existing Azure DNS zones using the steps explained further in this guide.
    - After completing the steps in this guide, add required DNS A records in your existing DNS servers manually.
-3. Deploy a [new Microsoft Purview account](#option-1---deploy-a-new-azure-purview-account-with-account-portal-and-ingestion-private-endpoints) with account, portal and ingestion private endpoints, or deploy private endpoints for an [existing Microsoft Purview account](#option-2---enable-account-portal-and-ingestion-private-endpoint-on-existing-azure-purview-accounts).
+3. Deploy a [new Microsoft Purview account](#option-1---deploy-a-new-microsoft-purview-account-with-account-portal-and-ingestion-private-endpoints) with account, portal and ingestion private endpoints, or deploy private endpoints for an [existing Microsoft Purview account](#option-2---enable-account-portal-and-ingestion-private-endpoint-on-existing-microsoft-purview-accounts).
 4. [Enable access to Azure Active Directory](#enable-access-to-azure-active-directory) if your private network has network security group rules set to deny for all public internet traffic.
 5. Deploy and register [Self-hosted integration runtime](#deploy-self-hosted-integration-runtime-ir-and-scan-your-data-sources) inside the same VNet or a peered VNet where Microsoft Purview account and ingestion private endpoints are deployed.
 6. After completing this guide, adjust DNS configurations if needed.

articles/synapse-analytics/catalog-and-governance/how-to-access-secured-purview-account.md

@@ -22,8 +22,8 @@ If your Azure Purview account is protected by firewall and denies public access,
 
 | Scenario                                                     | Required Azure Purview private endpoints                           |
 | ------------------------------------------------------------ | ------------------------------------------------------------ |
-| [Run pipeline and report lineage to Azure Purview](../../purview/how-to-lineage-azure-synapse-analytics.md) | For Synapse pipeline to push lineage to Azure Purview, Azure Purview ***account*** and ***ingestion*** private endpoints are required. <br>- When using **Azure Integration Runtime**, follow the steps in [Managed private endpoints for Azure Purview](#managed-private-endpoints-for-azure-purview) section to create managed private endpoints in the Synapse managed virtual network.<br>- When using **Self-hosted Integration Runtime**, follow the steps in [this section](../../purview/catalog-private-link-end-to-end.md#option-2---enable-account-portal-and-ingestion-private-endpoint-on-existing-azure-purview-accounts) to create the *account* and *ingestion* private endpoints in your integration runtime's virtual network. |
-| [Discover and explore data using Azure Purview on Synapse Studio](how-to-discover-connect-analyze-azure-purview.md) | To use the search bar at the top center of Synapse Studio to search for Azure Purview data and perform actions, you need to create Azure Purview ***account*** and ***portal*** private endpoints in the virtual network that you launch the Synapse Studio. Follow the steps in [Enable *account* and *portal* private endpoint](../../purview/catalog-private-link-account-portal.md#option-2---enable-account-and-portal-private-endpoint-on-existing-azure-purview-accounts). |
+| [Run pipeline and report lineage to Azure Purview](../../purview/how-to-lineage-azure-synapse-analytics.md) | For Synapse pipeline to push lineage to Azure Purview, Azure Purview ***account*** and ***ingestion*** private endpoints are required. <br>- When using **Azure Integration Runtime**, follow the steps in [Managed private endpoints for Azure Purview](#managed-private-endpoints-for-azure-purview) section to create managed private endpoints in the Synapse managed virtual network.<br>- When using **Self-hosted Integration Runtime**, follow the steps in [this section](../../purview/catalog-private-link-end-to-end.md#option-2---enable-account-portal-and-ingestion-private-endpoint-on-existing-microsoft-purview-accounts) to create the *account* and *ingestion* private endpoints in your integration runtime's virtual network. |
+| [Discover and explore data using Azure Purview on Synapse Studio](how-to-discover-connect-analyze-azure-purview.md) | To use the search bar at the top center of Synapse Studio to search for Azure Purview data and perform actions, you need to create Azure Purview ***account*** and ***portal*** private endpoints in the virtual network that you launch the Synapse Studio. Follow the steps in [Enable *account* and *portal* private endpoint](../../purview/catalog-private-link-account-portal.md#option-2---enable-account-and-portal-private-endpoint-on-existing-microsoft-purview-accounts). |
 
 ## Managed private endpoints for Azure Purview