Merge pull request #292653 from AbdullahBell/private-link-freshness-2

Jill Grant · web-flow · commit 56a6d12f857e · 2025-01-07T13:10:25.000-07:00
Private Link: Freshness: Image Review: 5 articles updated for freshness
diff --git a/articles/private-link/private-endpoint-export-dns.md b/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
 ---
 
diff --git a/articles/private-link/troubleshoot-private-link-connectivity.md b/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're 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're 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 virtual machine 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 virtual machine.
 
-       - 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:
 
@@ -123,6 +109,6 @@ Contact the [Azure Support](https://portal.azure.com/#blade/Microsoft_Azure_Supp
 
 ## Next steps
 
- * [Create a private link service (CLI)](./create-private-link-service-cli.md)
+* [Create a private link service (CLI)](./create-private-link-service-cli.md)
  
 * [Azure Private Endpoint troubleshooting guide](troubleshoot-private-endpoint-connectivity.md)
diff --git a/articles/private-link/tutorial-private-endpoint-sql-cli.md b/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
 ---
@@ -49,9 +49,9 @@ az group create \
 
 ## Create a virtual network and bastion host
 
-In this section, you'll create a virtual network, subnet, and bastion host. 
+In this section, you create a virtual network, subnet, and bastion host. 
 
-The bastion host will be used to connect securely to the virtual machine for testing the private endpoint.
+The bastion host is used to connect securely to the virtual machine for testing the private endpoint.
 
 Create a virtual network with [az network vnet create](/cli/azure/network/vnet#az-network-vnet-create)
 
@@ -130,7 +130,7 @@ It can take a few minutes for the Azure Bastion host to deploy.
 
 ## Create test virtual machine
 
-In this section, you'll create a virtual machine that will be used to test the private endpoint.
+In this section, you create a virtual machine that is used to test the private endpoint.
 
 Create a VM with [az vm create](/cli/azure/vm#az-vm-create). When prompted, provide a password to be used as the credentials for the VM:
 
@@ -155,7 +155,7 @@ az vm create \
 
 ## Create an Azure SQL server
 
-In this section, you'll create a SQL server and database.
+In this section, you create a SQL server and database.
 
 Use [az sql server create](/cli/azure/sql/server#az-sql-server-create) to create a SQL server:
 
@@ -189,7 +189,7 @@ az sql db create \
 
 ## Create private endpoint
 
-In this section, you'll create the private endpoint.
+In this section, you create the private endpoint.
 
 Use [az sql server list](/cli/azure/sql/server#az-sql-server-list) to place the resource ID of the SQL server into a shell variable.
 
@@ -220,9 +220,9 @@ az network private-endpoint create \
 
 In this section, you'll create and configure the private DNS zone using [az network private-dns zone create](/cli/azure/network/private-dns/zone#az-network-private-dns-zone-create).  
 
-You'll use [az network private-dns link vnet create](/cli/azure/network/private-dns/link/vnet#az-network-private-dns-link-vnet-create) to create the virtual network link to the dns zone.
+You use [az network private-dns link vnet create](/cli/azure/network/private-dns/link/vnet#az-network-private-dns-link-vnet-create) to create the virtual network link to the dns zone.
 
-You'll create a dns zone group with [az network private-endpoint dns-zone-group create](/cli/azure/network/private-endpoint/dns-zone-group#az-network-private-endpoint-dns-zone-group-create).
+You create a dns zone group with [az network private-endpoint dns-zone-group create](/cli/azure/network/private-endpoint/dns-zone-group#az-network-private-endpoint-dns-zone-group-create).
 
 * Zone named **privatelink.database.windows.net**
 * In virtual network **myVNet**.
@@ -253,7 +253,7 @@ az network private-endpoint dns-zone-group create \
 
 ## Test connectivity to private endpoint
 
-In this section, you'll use the virtual machine you created in the previous step to connect to the SQL server across the private endpoint.
+In this section, you use the virtual machine you created in the previous step to connect to the SQL server across the private endpoint.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
  
@@ -271,19 +271,19 @@ In this section, you'll use the virtual machine you created in the previous step
 
 8. Open Windows PowerShell on the server after you connect.
 
-9. Enter `nslookup <sqlserver-name>.database.windows.net`. Replace **\<sqlserver-name>** with the name of the SQL server you created in the previous steps.  You'll receive a message similar to what is displayed below:
+9. Enter `nslookup <sqlserver-name>.database.windows.net`. Replace **\<sqlserver-name>** with the name of the SQL server you created in the previous steps. You receive a message similar to what is displayed below:
 
     ```powershell
     Server:  UnKnown
-    Address:  168.63.129.16
+    Address:  172.63.129.16
 
     Non-authoritative answer:
     Name:    mysqlserver8675.privatelink.database.windows.net
     Address:  10.0.0.5
     Aliases:  mysqlserver8675.database.windows.net
     ```
 
-    A private IP address of **10.0.0.5** is returned for the SQL server name.  This address is in the subnet of the virtual network you created previously.
+    A private IP address of **10.0.0.5** is returned for the SQL server name. This address is in the subnet of the virtual network you created previously.
 
 
 10. Install [SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms?preserve-view=true&view=sql-server-2017) on **myVM**.
@@ -328,6 +328,6 @@ In this tutorial, you created a:
 
 You used the virtual machine to test connectivity securely to the SQL server across the private endpoint.
 
-As a next step, you may also be interested in the **Web app with private connectivity to Azure SQL database** architecture scenario, which connects a web application outside of the virtual network to the private endpoint of a database.
+As a next step, review the **Web app with private connectivity to Azure SQL database** architecture scenario, which connects a web application outside of the virtual network to the private endpoint of a database.
 > [!div class="nextstepaction"]
 > [Web app with private connectivity to Azure SQL database](/azure/architecture/example-scenario/private-web-app/private-web-app)
diff --git a/articles/private-link/tutorial-private-endpoint-sql-portal.md b/articles/private-link/tutorial-private-endpoint-sql-portal.md
@@ -47,7 +47,7 @@ In this section, you create a SQL server in Azure.
 
 1. In **SQL databases**, select **+ Create**.
 
-1. In the **Basics** tab of **Create SQL Database**, enter or select the following information:
+1. In the **Basics** tab of **Create SQL Database**, enter, or select the following information:
 
     | Setting | Value |
     |---|---|
@@ -64,7 +64,7 @@ In this section, you create a SQL server in Azure.
 
 1. Select **Next: Networking**.
 
-1. In the **Networking** tab of **Create SQL Database**, enter or select the following information:
+1. In the **Networking** tab of **Create SQL Database**, enter, or select the following information:
 
     | Setting | Value |
     |---|---|
@@ -92,7 +92,7 @@ In this section, you create a SQL server in Azure.
 1. Select **Create**.
 
 > [!IMPORTANT]
-> When adding a Private endpoint connection, public routing to your Azure SQL server is not blocked by default. The setting "Deny public network access" under the "Firewall and virtual networks" blade is left unchecked by default. To disable public network access ensure this is checked.
+> When adding a Private endpoint connection, public routing to your Azure SQL server isn't blocked by default. The setting "Deny public network access" under the "Firewall and virtual networks" blade is left unchecked by default. To disable public network access, ensure this is checked.
  
 ## Disable public access to Azure SQL logical server
 
@@ -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.
@@ -169,6 +169,6 @@ In this tutorial, you learned how to create:
 
 You used the virtual machine to test connectivity privately and securely to the SQL server across the private endpoint.
 
-As a next step, you may also be interested in the **Web app with private connectivity to Azure SQL Database** architecture scenario, which connects a web application outside of the virtual network to the private endpoint of a database.
+As a next step, review the **Web app with private connectivity to Azure SQL Database** architecture scenario, which connects a web application outside of the virtual network to the private endpoint of a database.
 > [!div class="nextstepaction"]
 > [Web app with private connectivity to Azure SQL Database](/azure/architecture/example-scenario/private-web-app/private-web-app)
diff --git a/articles/private-link/tutorial-private-endpoint-sql-powershell.md b/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
 ---
@@ -42,9 +42,9 @@ New-AzResourceGroup -Name 'CreateSQLEndpointTutorial-rg' -Location 'eastus'
 
 ## Create a virtual network and bastion host
 
-In this section, you'll create a virtual network, subnet, and bastion host. 
+In this section, you create a virtual network, subnet, and bastion host. 
 
-The bastion host will be used to connect securely to the virtual machine for testing the private endpoint.
+The bastion host is used to connect securely to the virtual machine for testing the private endpoint.
 
 Create a virtual network and bastion host with:
 
@@ -93,7 +93,7 @@ It can take a few minutes for the Azure Bastion host to deploy.
 
 ## Create test virtual machine
 
-In this section, you'll create a virtual machine that will be used to test the private endpoint.
+In this section, you create a virtual machine that is used to test the private endpoint.
 
 Create the virtual machine with:
 
@@ -148,7 +148,7 @@ New-AzVM -ResourceGroupName 'CreateSQLEndpointTutorial-rg' -Location 'eastus' -V
 
 ## Create an Azure SQL server
 
-In this section, you'll create a SQL server and database using:
+In this section, you create a SQL server and database using:
 
 * [New-AzSqlServer](/powershell/module/az.sql/new-azsqlserver)
 * [New-AzSQlDatabase](/powershell/module/az.sql/new-azsqldatabase)
@@ -181,7 +181,7 @@ New-AzSqlDatabase @parameters2
 
 ## Create private endpoint
 
-In this section, you'll create the private endpoint and connection using:
+In this section, you create the private endpoint and connection using:
 
 * [New-AzPrivateLinkServiceConnection](/powershell/module/az.network/New-AzPrivateLinkServiceConnection)
 * [New-AzPrivateEndpoint](/powershell/module/az.network/new-azprivateendpoint)
@@ -217,7 +217,7 @@ New-AzPrivateEndpoint @parameters2
 ```
 ## Configure the private DNS zone
 
-In this section you'll create and configure the private DNS zone using:
+In this section you create and configure the private DNS zone using:
 
 * [New-AzPrivateDnsZone](/powershell/module/az.privatedns/new-azprivatednszone)
 * [New-AzPrivateDnsVirtualNetworkLink](/powershell/module/az.privatedns/new-azprivatednsvirtualnetworklink)
@@ -263,7 +263,7 @@ New-AzPrivateDnsZoneGroup @parameters4
 
 ## Test connectivity to private endpoint
 
-In this section, you'll use the virtual machine you created in the previous step to connect to the SQL server across the private endpoint.
+In this section, you use the virtual machine you created in the previous step to connect to the SQL server across the private endpoint.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
  
@@ -281,19 +281,19 @@ In this section, you'll use the virtual machine you created in the previous step
 
 8. Open Windows PowerShell on the server after you connect.
 
-9. Enter `nslookup <sqlserver-name>.database.windows.net`. Replace **\<sqlserver-name>** with the name of the SQL server you created in the previous steps.  You'll receive a message similar to what is displayed below:
+9. Enter `nslookup <sqlserver-name>.database.windows.net`. Replace **\<sqlserver-name>** with the name of the SQL server you created in the previous steps. You receive a message similar to what is displayed below:
 
     ```powershell
     Server:  UnKnown
-    Address:  168.63.129.16
+    Address:  172.63.129.16
 
     Non-authoritative answer:
     Name:    mysqlserver8675.privatelink.database.windows.net
     Address:  10.0.0.5
     Aliases:  mysqlserver8675.database.windows.net
     ```
 
-    A private IP address of **10.0.0.5** is returned for the SQL server name.  This address is in the subnet of the virtual network you created previously.
+    A private IP address of **10.0.0.5** is returned for the SQL server name. This address is in the subnet of the virtual network you created previously.
 
 
 10. Install [SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms?preserve-view=true&view=sql-server-2017) on **myVM**.
@@ -338,6 +338,6 @@ In this tutorial, you created a:
 
 You used the virtual machine to test connectivity securely to the SQL server across the private endpoint.
 
-As a next step, you may also be interested in the **Web app with private connectivity to Azure SQL database** architecture scenario, which connects a web application outside of the virtual network to the private endpoint of a database.
+As a next step, review the **Web app with private connectivity to Azure SQL database** architecture scenario, which connects a web application outside of the virtual network to the private endpoint of a database.
 > [!div class="nextstepaction"]
 > [Web app with private connectivity to Azure SQL database](/azure/architecture/example-scenario/private-web-app/private-web-app)
