updated for freshness and removed screenshots.

Author: AbdullahBell

articles/private-link/private-endpoint-export-dns.md

@@ -6,7 +6,7 @@ author: abell
 ms.author: abell
 ms.service: azure-private-link
 ms.topic: how-to 
-ms.date: 07/25/2021
+ms.date: 01/06/2025
 ms.custom: template-how-to
 ---
 

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

@@ -4,7 +4,7 @@ description: Step-by-step guidance to diagnose private link connectivity
 author: abell
 ms.service: azure-private-link
 ms.topic: troubleshooting
-ms.date: 03/29/2020
+ms.date: 01/06/2025
 ms.author: abell
 ---
 
@@ -42,8 +42,6 @@ If you experience connectivity problems with your private link setup, review the
 
     b. On the left pane, select **Private link services**.
 
-      :::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.
@@ -52,52 +50,40 @@ If you experience connectivity problems with your private link setup, review the
 
      - If the state is **Pending**, select it and approve it.
 
-       :::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**.
-
-       :::image type="content" source="./media/private-link-tsg/pls-private-endpoint-overview.png" alt-text="Screenshot of private endpoint connection overview.":::
+    - Select the private endpoint you are connecting from by clicking on its name. Ensure the connection status is **Approved**.
 
      - 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.
-
-       :::image type="content" source="./media/private-link-tsg/pls-overview-pane-alias.png" alt-text="Screenshot of verify alias information.":::
+    - Ensure that the **Alias** and **Resource ID** details match the ones you are using to create a private endpoint for this service.
 
-       :::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.
+    f. Review **Visibility** information on the **Overview** tab. Select **See more** in the overview pane to see the details.
 
      - Make sure that your subscription falls under the **Visibility** scope.
 
-       :::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.
-
-       :::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.
+     - View the load balancer by selecting the load balancer link in the *Overview* pane.
+      
+     -Confirm the load balancer settings are configured as per your requirements.
 
        - Review **Frontend IP configuration**.
 
        - Review **Backend pools**.
 
        - Review **Load balancing rules**.
 
-       :::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.
+     - Confirm 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.
+      - Choose a VM located in a subnet different from the one where the load balancer back-end pool resides.  
+      
+      - Access 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.
+      - If the connection reaches the back-end pool according to the load-balancing rules, then your load balancer is functioning correctly.    
 
-       - You can also review the load balancer metric through Azure Monitor to see if data is flowing through the load balancer.
+      - If the connection doesn't reach the back-end pool, then you need to troubleshoot the load balancer configuration.
+      
+      - Use Azure Monitor to review load balancer metrics and verify if data is flowing through the load balancer.
 
 1. Use [Azure Monitor](/azure/azure-monitor/overview) to see if data is flowing.
 
@@ -107,7 +93,7 @@ If you experience connectivity problems with your private link setup, review the
 
      - See if data is flowing when you attempt to connect to the private link service. Expect a delay of approximately 10 minutes.
 
-       :::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:
 

articles/private-link/tutorial-private-endpoint-sql-cli.md

@@ -6,7 +6,7 @@ author: abell
 # Customer intent: As someone with a basic network background, but is new to Azure, I want to create a private endpoint on a SQL server so that I can securely connect to it.
 ms.service: azure-private-link
 ms.topic: tutorial
-ms.date: 11/03/2020
+ms.date: 01/06/2025
 ms.author: abell
 ms.custom: template-tutorial, fasttrack-edit, devx-track-azurecli
 ---
@@ -275,7 +275,7 @@ In this section, you'll use the virtual machine you created in the previous step
 
     ```powershell
     Server:  UnKnown
-    Address:  168.63.129.16
+    Address:  172.63.129.16
 
     Non-authoritative answer:
     Name:    mysqlserver8675.privatelink.database.windows.net

articles/private-link/tutorial-private-endpoint-sql-portal.md

@@ -129,8 +129,8 @@ In this section, you use the virtual machine you created in the previous steps t
     You receive a message similar to the following example. The IP address returned is the private IP address of the private endpoint.
 
     ```output
-    Server:    127.0.0.53
-    Address:   127.0.0.53#53
+    Server:    unknown
+    Address:   172.0.0.53
 
     Non-authoritative answer:
     sql-server-8675.database.windows.netcanonical name = sql-server-8675.privatelink.database.windows.net.

articles/private-link/tutorial-private-endpoint-sql-powershell.md

@@ -6,7 +6,7 @@ author: abell
 # Customer intent: As someone with a basic network background, but is new to Azure, I want to create a private endpoint on a SQL server so that I can securely connect to it.
 ms.service: azure-private-link
 ms.topic: tutorial
-ms.date: 10/31/2020
+ms.date: 01/06/2025
 ms.author: abell
 ms.custom: template-tutorial, fasttrack-edit, devx-track-azurepowershell
 ---
@@ -285,7 +285,7 @@ In this section, you'll use the virtual machine you created in the previous step
 
     ```powershell
     Server:  UnKnown
-    Address:  168.63.129.16
+    Address:  172.63.129.16
 
     Non-authoritative answer:
     Name:    mysqlserver8675.privatelink.database.windows.net