Merge pull request #294839 from AbdullahBell/private-link-freshness

Private Link: Freshness: Image Deletion: 7 articles

Author: prmerger-automator[bot]

articles/private-link/configure-asg-private-endpoint.md

@@ -6,7 +6,7 @@ author: abell
 ms.author: abell
 ms.service: azure-private-link
 ms.topic: how-to 
-ms.date: 06/14/2022
+ms.date: 02/18/2024
 ms.custom: template-how-to, devx-track-azurepowershell, devx-track-azurecli
 ---
 
@@ -84,8 +84,6 @@ You can associate an ASG with a private endpoint when it's created. The followin
     | **Application security group** |   |
     | Application security group | Select **myASG**. |
 
-    :::image type="content" source="./media/configure-asg-private-endpoint/asg-new-endpoint.png" alt-text="Screenshot that shows ASG selection when creating a new private endpoint.":::
-
 1. Select **Next: DNS** at the bottom of the page.
 
 1. Select **Next: Tags** at the bottom of the page.
@@ -171,8 +169,6 @@ You can associate an ASG with an existing private endpoint. The following proced
 
 1. In **Application security groups**, select **myASG** in the dropdown box.
 
-    :::image type="content" source="./media/configure-asg-private-endpoint/asg-existing-endpoint.png" alt-text="Screenshot that shows ASG selection when associating with an existing private endpoint.":::
-
 1. Select **Save**.
 
 # [**PowerShell**](#tab/powershell)

articles/private-link/how-to-approve-private-link-cross-subscription.md

@@ -6,7 +6,7 @@ author: abell
 ms.author: abell
 ms.service: azure-private-link
 ms.topic: how-to 
-ms.date: 01/11/2024
+ms.date: 01/18/2025
 # Customer intent: As a network administrator, I want to approve Private Link connections across Azure subscriptions.
 
 ---

articles/private-link/inspect-traffic-with-azure-firewall.md

@@ -5,7 +5,7 @@ description: Learn about different scenarios to inspect traffic destined to a pr
 author: abell
 ms.service: azure-private-link
 ms.topic: concept-article
-ms.date: 08/14/2023
+ms.date: 02/18/2025
 ms.author: abell
 ms.custom: template-how-to
 ---

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

@@ -4,7 +4,7 @@ description: Step-by-step guidance to diagnose private endpoint connectivity
 author: abell
 ms.service: azure-private-link
 ms.topic: troubleshooting
-ms.date: 03/28/2023
+ms.date: 02/18/2025
 ms.author: abell
 ---
 
@@ -31,12 +31,8 @@ Review these steps to make sure all the usual configurations are as expected to
 1. Review private endpoint configuration by browsing the resource.
 
     a. Go to [Private Link Center](https://portal.azure.com/#blade/Microsoft_Azure_Network/PrivateLinkCenterBlade/overview).
-      
-      :::image type="content" source="./media/private-endpoint-tsg/private-link-center.png" alt-text="Screenshot of Private Link Center.":::
 
     b. On the left pane, select **Private endpoints**.
-    
-      :::image type="content" source="./media/private-endpoint-tsg/private-endpoints.png" alt-text="Screenshot of private endpoints.":::
 
     c. Filter and select the private endpoint that you want to diagnose.
 
@@ -47,8 +43,6 @@ Review these steps to make sure all the usual configurations are as expected to
      - Make sure the VM has connectivity to the virtual network that hosts the private endpoints.
 
      - Check that the FQDN information (copy) and Private IP address are assigned.
-        
-       :::image type="content" source="./media/private-endpoint-tsg/vnet-dns-configuration.png" alt-text="Screenshot of virtual network and DNS configuration.":::
 
 1. Use [Azure Monitor](/azure/azure-monitor/overview) to see if data is flowing.
 
@@ -57,30 +51,22 @@ Review these steps to make sure all the usual configurations are as expected to
      - Select **Bytes In** or **Bytes Out**. 
 
      - See if data is flowing when you attempt to connect to the private endpoint. Expect a delay of approximately 10 minutes.
-    
-      :::image type="content" source="./media/private-endpoint-tsg/private-endpoint-monitor.png" alt-text="Screenshot of verify private endpoint monitor.":::
 
 1.  Use **VM Connection troubleshoot** from Azure Network Watcher.
 
     a. Select the client VM.
 
     b. Select **Connection troubleshoot**, and then select the **Outbound connections** tab.
 
-      :::image type="content" source="./media/private-endpoint-tsg/network-watcher-outbound-connection.png" alt-text="Screenshot of Network Watcher - Test outbound connections.":::
-    
     c. Select **Use Network Watcher for detailed connection tracing**.
-    
-      :::image type="content" source="./media/private-endpoint-tsg/network-watcher-connection-troubleshoot.png" alt-text="Screenshot of Network Watcher - Connection troubleshoot.":::
 
     d. Select **Test by FQDN**.
 
      - Paste the FQDN from the private endpoint resource.
 
      - Provide a port. Typically, use 443 for Azure Storage or Azure Cosmos DB and 1336 for SQL.
 
-    e. Select **Test**, and validate the test results.
-
-      :::image type="content" source="./media/private-endpoint-tsg/network-watcher-test-results.png" alt-text="Screenshot of Network Watcher - Test results.":::    
+    e. Select **Test**, and validate the test results. 
 
 1. DNS resolution from the test results must have the same private IP address assigned to the private endpoint.
 
@@ -100,8 +86,6 @@ Review these steps to make sure all the usual configurations are as expected to
     b. If connectivity is failing because of network security groups (NSGs) or user-defined routes:
      - Review the NSG outbound rules, and create the appropriate outbound rules to allow traffic.
 
-       :::image type="content" source="./media/private-endpoint-tsg/nsg-outbound-rules.png" alt-text="Screenshot of NSG outbound rules.":::
-
 1. Source virtual machine should have the route to private endpoint IP next hop as InterfaceEndpoints in the network interface effective routes. 
 
     a. If you aren't able to see the private endpoint route in the source VM, check if 

articles/private-link/tutorial-dns-on-premises-private-resolver.md

@@ -6,7 +6,7 @@ author: abell
 ms.author: abell
 ms.service: azure-private-link
 ms.topic: tutorial
-ms.date: 08/29/2023
+ms.date: 02/18/2025
 ms.custom: template-tutorial
 ---
 
@@ -235,16 +235,12 @@ In this section, you use the virtual machine you created in the previous step to
 
 9. Verify you receive the default web app page.
 
-    :::image type="content" source="./media/tutorial-dns-on-premises-private-resolver/web-app-default-page.png" alt-text="Screenshot of Microsoft Edge showing default web app page." border="true":::
-
 10. Close the connection to **vm-1**.
 
 11. Open a web browser on your local computer and enter the URL of your web app, `https://<webapp-name>.azurewebsites.net`.
 
 12. Verify that you receive a **403** page. This page indicates that the web app isn't accessible externally.
 
-    :::image type="content" source="./media/tutorial-dns-on-premises-private-resolver/web-app-ext-403.png" alt-text="Screenshot of web browser showing a blue page with Error 403 for external web app address." border="true":::
-
 [!INCLUDE [portal-clean-up.md](~/reusable-content/ce-skilling/azure/includes/portal-clean-up.md)]
 
 ## Next steps

articles/private-link/tutorial-inspect-traffic-azure-firewall.md

@@ -6,7 +6,7 @@ ms.author: abell
 ms.service: azure-private-link
 ms.topic: tutorial
 ms.custom: mvc, linux-related-content
-ms.date: 10/13/2023
+ms.date: 02/18/2025
 ---
 # Tutorial: Inspect private endpoint traffic with Azure Firewall