Merge pull request #232743 from asudbring/prvlink-review

Review of Private Link connectivity troubleshooting article - image and acrolinx fixes

Author: v-regandowner

articles/private-link/troubleshoot-private-link-connectivity.md

@@ -1,37 +1,35 @@
 ---
 title: Troubleshoot Azure Private Link Service connectivity problems
 description: Step-by-step guidance to diagnose private link connectivity
-services: private-link
-author: rdhillon
-manager: narayan
+author: asudbring
 ms.service: private-link
 ms.topic: troubleshooting
-ms.workload: infrastructure-services
-ms.date: 01/31/2020
-ms.author: rdhillon
+ms.date: 03/29/2020
+ms.author: allensu
 ms.custom: ignite-2022
 ---
 
 # Troubleshoot Azure Private Link Service connectivity problems
 
 This article provides step-by-step guidance to validate and diagnose connectivity for your Azure Private Link setup.
 
-With Azure Private Link, you can access Azure platform as a service (PaaS) services, such as Azure Storage, Azure Cosmos DB, and Azure SQL Database, and Azure hosted customer or partner services over a private endpoint in your virtual network. Traffic between your virtual network and the service traverses over the Microsoft backbone network, which eliminates exposure from the public internet. You can also create your own private link service in your virtual network and deliver it privately to your customers.
+With Azure Private Link, you can access Azure platform as a service (PaaS) services and Azure hosted customer or partner services over a private endpoint in your virtual network. Traffic between your virtual network and the service traverses over the Microsoft backbone network, which eliminates exposure from the public internet. You can also create your own private link service in your virtual network and deliver it privately to your customers.
 
 You can enable your service that runs behind the Standard tier of Azure Load Balancer for Private Link access. Consumers of your service can create a private endpoint inside their virtual network and map it to this service to access it privately.
 
 Here are the connectivity scenarios that are available with Private Link:
 
 - Virtual network from the same region
+
 - Regionally peered virtual networks
+
 - Globally peered virtual networks
+
 - Customer on-premises over VPN or Azure ExpressRoute circuits
 
 ## Deployment troubleshooting
 
-Review the information on [Disabling network policies on the private link service](./disable-private-link-service-network-policy.md) for troubleshooting cases where you're unable to select the source IP address from the subnet of your choice for your private link service.
-
-Make sure that the setting **privateLinkServiceNetworkPolicies** is disabled for the subnet you're selecting the source IP address from.
+For more information on troubleshooting when you're unable to select the source IP address from the subnet of your choice for your private link service, see [Disabling network policies on the private link service](./disable-private-link-service-network-policy.md).
 
 ## Diagnose connectivity problems
 
@@ -40,78 +38,92 @@ If you experience connectivity problems with your private link setup, review the
 1. Review Private Link configuration by browsing the resource.
 
     a. Go to [Private Link Center](https://portal.azure.com/#blade/Microsoft_Azure_Network/PrivateLinkCenterBlade/overview).
-
-      ![Private Link Center](./media/private-link-tsg/private-link-center.png)
+      
+      :::image type="content" source="./media/private-link-tsg/private-link-center.png" alt-text="Screenshot of Private Link Center.":::
 
     b. On the left pane, select **Private link services**.
 
-      ![Private link services](./media/private-link-tsg/private-link-service.png)
+      :::image type="content" source="./media/private-link-tsg/private-link-service.png" alt-text="Screenshot of Private link services.":::
 
     c. Filter and select the private link service that you want to diagnose.
 
     d. Review the private endpoint connections.
+
      - Make sure that the private endpoint that you're seeking connectivity from is listed with an **Approved** connection state.
+
      - If the state is **Pending**, select it and approve it.
 
-       ![Private endpoint connections](./media/private-link-tsg/pls-private-endpoint-connections.png)
+       :::image type="content" source="./media/private-link-tsg/pls-private-endpoint-connections.png" alt-text="Screenshot of Private endpoint connections.":::
 
      - Go to the private endpoint that you're connecting from by selecting the name. Make sure the connection status shows as **Approved**.
 
-       ![Private endpoint connection overview](./media/private-link-tsg/pls-private-endpoint-overview.png)
+       :::image type="content" source="./media/private-link-tsg/pls-private-endpoint-overview.png" alt-text="Screenshot of private endpoint connection overview.":::
 
      - After both sides are approved, try the connectivity again.
 
     e. Review **Alias** on the **Overview** tab and **Resource ID** on the **Properties** tab.
      - Make sure the **Alias** and **Resource ID** information matches the **Alias** and **Resource ID** you're using to create a private endpoint to this service.
 
-       ![Verify Alias information](./media/private-link-tsg/pls-overview-pane-alias.png)
+       :::image type="content" source="./media/private-link-tsg/pls-overview-pane-alias.png" alt-text="Screenshot of verify alias information.":::
 
-       ![Verify Resource ID information](./media/private-link-tsg/pls-properties-pane-resourceid.png)
+       :::image type="content" source="./media/private-link-tsg/pls-properties-pane-resourceid.png" alt-text="Screenshot of verify resource ID information.":::
 
     f. Review **Visibility** information on the **Overview** tab.
+
      - Make sure that your subscription falls under the **Visibility** scope.
 
-       ![Verify Visibility information](./media/private-link-tsg/pls-overview-pane-visibility.png)
+       :::image type="content" source="./media/private-link-tsg/pls-overview-pane-visibility.png" alt-text="Screenshot of verify visibility information.":::
 
     g. Review **Load balancer** information on the **Overview** tab.
+
      - You can go to the load balancer by selecting the load balancer link.
 
-       ![Verify Load balancer information](./media/private-link-tsg/pls-overview-pane-ilb.png)
+       :::image type="content" source="./media/private-link-tsg/pls-overview-pane-ilb.png" alt-text="Screenshot of verify load balancer information.":::
 
      - Make sure that the load balancer settings are configured as per your expectations.
+
        - Review **Frontend IP configuration**.
+
        - Review **Backend pools**.
+
        - Review **Load balancing rules**.
 
-       ![Verify load balancer properties](./media/private-link-tsg/pls-ilb-properties.png)
+       :::image type="content" source="./media/private-link-tsg/pls-ilb-properties.png" alt-text="Screenshot of verify load balancer properties.":::
 
      - Make sure the load balancer is working as per the previous settings.
+
        - Select a VM in any subnet other than the subnet where the load balancer back-end pool is available.
+
        - Try accessing the load balancer front end from the previous VM.
+
        - If the connection makes it to the back-end pool as per load-balancing rules, your load balancer is operational.
+
        - You can also review the load balancer metric through Azure Monitor to see if data is flowing through the load balancer.
 
 1. Use [Azure Monitor](../azure-monitor/overview.md) to see if data is flowing.
 
     a. On the private link service resource, select **Metrics**.
+
      - Select **Bytes In** or **Bytes Out**.
+
      - See if data is flowing when you attempt to connect to the private link service. Expect a delay of approximately 10 minutes.
 
-       ![Verify private link service metrics](./media/private-link-tsg/pls-metrics.png)
+       :::image type="content" source="./media/private-link-tsg/pls-metrics.png" alt-text="Screenshot of verify private link service metrics.":::
 
 1. Use [Azure Monitor - Networks](../network-watcher/network-insights-overview.md#resource-view) for insights and to see a resource view of the resources by going to:
+
      - Azure Monitor
+
      - Networks
-     - Private Link services
-     - Resource view 
 
-![AzureMonitor](https://user-images.githubusercontent.com/20302679/135001735-56a9484b-f9b4-484b-a503-cfb9d20b264a.png)
+     - Private Link services
 
-![DependencyView](https://user-images.githubusercontent.com/20302679/135001741-8e848c52-d4bb-4646-b0d3-a85614ebe16c.png)
+     - Resource view 
 
-4. Contact the [Azure Support](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview) team if your problem is still unresolved and a connectivity problem still exists.
+Contact the [Azure Support](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview) team if your problem is still unresolved and a connectivity problem still exists.
 
 ## Next steps
 
  * [Create a private link service (CLI)](./create-private-link-service-cli.md)
- * [Azure Private Endpoint troubleshooting guide](troubleshoot-private-endpoint-connectivity.md)
+ 
+* [Azure Private Endpoint troubleshooting guide](troubleshoot-private-endpoint-connectivity.md)