Merge pull request #298438 from mbender-ms/vnet-freshness-updates

virtual Network | Freshness | April 2025

Author: prmerger-automator[bot]

articles/virtual-network/troubleshoot-vm-connectivity.md

@@ -4,11 +4,10 @@ description: Learn how to diagnose and resolve connectivity problems that affect
 author: asudbring
 ms.author: allensu
 manager: dcscontentpm
-audience: ITPro
 ms.topic: troubleshooting
 ms.service: azure-virtual-network
 ms.localizationpriority: medium
-ms.date: 08/29/2019
+ms.date: 04/17/2025
 ---
 
 # Troubleshoot Azure VM connectivity problems
@@ -17,9 +16,9 @@ This article helps administrators diagnose and resolve connectivity problems tha
 
 ## Problems
 
-- [An Azure VM that’s deployed by using Resource Manager can't connect to another Azure VM in same virtual network](#azure-vm-cannot-connect-to-another-azure-vm-in-same-virtual-network).
-- [An Azure VM can't connect to the second network adapter of an Azure VM in same virtual network](#azure-vm-cannot-connect-to-the-second-network-adapter-of-an-azure-vm-in-same-virtual-network).
-- [An Azure VM can't connect to the internet](#azure-vm-cannot-connect-to-the-internet).
+- [An Azure VM that’s deployed by using Resource Manager can't connect to another Azure VM in same virtual network](#azure-vm-cant-connect-to-another-azure-vm-in-same-virtual-network).
+- [An Azure VM can't connect to the second network adapter of an Azure VM in same virtual network](#azure-vm-cant-connect-to-the-second-network-adapter-of-an-azure-vm-in-same-virtual-network).
+- [An Azure VM can't connect to the internet](#azure-vm-cant-connect-to-the-internet).
 
 To resolve these problems, follow the steps in the following section.
 
@@ -31,7 +30,7 @@ To resolve these problems, follow the steps in the following section.
 > 
 ## Resolution
 
-### Azure VM cannot connect to another Azure VM in same virtual network
+### Azure VM can't connect to another Azure VM in same virtual network
 
 #### Step 1: Verify that VMs can communicate with each other.
 
@@ -51,10 +50,10 @@ To resolve these problems, follow the steps in the following section.
 
 #### Step 2: Check the Network security group settings.
 
-For each VM, check for default Inbound port rules ("Allow VNet Inbound" and "Allow Load Balancer Inbound"). Make sure to also check that there are no matching blocking rules that are listed below a lower-priority rule.
+For each VM, check for default Inbound port rules of *Allow VNet Inbound* and *Allow Load Balancer Inbound*. Make sure to also check that there are no matching blocking rules that are listed below a lower-priority rule.
 
 > [!NOTE]
-> Rules that have a lower number will be matched first. For example, if you have a rule that has priority 1000 and 6500, the rule that has priority 1000 will be matched first.
+> Rules that have a lower number are matched first. For example, if you have a rule that has priority 1000 and 6500, the rule that has priority 1000 is matched first.
 
 After that, try to ping the destination from the source VM again:
 
@@ -136,20 +135,20 @@ Hops             : [
     |Issue type  |Value  |Resolution action |
     |---------|---------|---------|
     |NetworkSecurityRule|Name of the blocking NSG|You can [delete the NSG rule](./manage-network-security-group.md#delete-a-security-rule) or modify the rule as described [here](./manage-network-security-group.md#change-a-security-rule).|
-    |UserDefinedRoute     |   Name of the blocking UDR      | If you do not require this route, delete the UDR. If you can’t delete the route, update the route by using the appropriate address prefix and next hop. You can also adjust the Network Virtual Appliance to forward traffic appropriately. For more information, see: [Virtual network traffic routing](./virtual-networks-udr-overview.md) and [Route network traffic with a route table using PowerShell](./tutorial-create-route-table-powershell.md).|
+    |UserDefinedRoute     |   Name of the blocking UDR      | If you don't require this route, delete the UDR. If you can’t delete the route, update the route by using the appropriate address prefix and next hop. You can also adjust the Network Virtual Appliance to forward traffic appropriately. For more information, see: [Virtual network traffic routing](./virtual-networks-udr-overview.md) and [Route network traffic with a route table using PowerShell](./tutorial-create-route-table-powershell.md).|
     |CPU    |    Usage     |     Follow these recommendations that describe in [Generic performance troubleshooting for Azure Virtual Machine running Linux or Windows](https://support.microsoft.com/en-in/help/3150851/generic-performance-troubleshooting-for-azure-virtual-machine-running).|
     |Memory    |      Usage   |    Follow the recommendations that are described in [Generic performance troubleshooting for Azure Virtual Machine running Linux or Windows](https://support.microsoft.com/en-in/help/3150851/generic-performance-troubleshooting-for-azure-virtual-machine-running).|
-    |Guest Firewall    |      Name of the firewall blocking   |      Follow these steps: [Turn Windows Defender Firewall on or off](https://support.microsoft.com/help/4028544/windows-turn-windows-firewall-on-or-off).|
+    |Guest Firewall    |      Name of the firewall blocking   |      Follow these steps: [Turn Windows Firewall on or off](https://support.microsoft.com/help/4028544/windows-turn-windows-firewall-on-or-off).|
     |DNS Resolution     |    Name of the DNS     |    Follow these steps: [Azure DNS troubleshooting guide](../dns/dns-troubleshoot.md) and [Name resolution for resources in Azure virtual networks](./virtual-networks-name-resolution-for-vms-and-role-instances.md).     |
     |Socket Error    |      Not applicable   |     The specified port is already in use by another application. Try to use a different port.    |
 
 3. Run the connectivity check again to determine whether the problem is resolved.
 
-### Azure VM cannot connect to the second network adapter of an Azure VM in same virtual network
+### Azure VM can't connect to the second network adapter of an Azure VM in same virtual network
 
 #### Step 1: Make sure that the second network adapter is enabled to talk outside the subnet.
 
-By default, secondary network adapters (also known as network interface cards, or network adapters) are not configured to have a default gateway. Therefore, the traffic flow on the secondary adapter will be limited to the same subnet.
+By default, secondary network adapters (also known as network interface cards, or network adapters) aren't configured to have a default gateway. Therefore, the traffic flow on the secondary adapter will be limited to the same subnet.
 
 ![IP configures](media/troubleshoot-vm-connectivity/ipconfig.png)
 
@@ -168,15 +167,15 @@ If users want to enable secondary network adapters to talk outside their own sub
     Route add 0.0.0.0 mask 0.0.0.0 -p 192.168.0.1
     ```
 
-3. Run route print. If the entry is added successfully, you will see an entry that resembles the following:
+3. Run route print. If the entry is added successfully, you'll see an entry that resembles the following:
 
     ![IP route](media/troubleshoot-vm-connectivity/iproute.png)
 
 Now, try to connect to secondary network adapter. If the connection is still unsuccessful, go to next step.
 
 #### Step 2: Check NSG settings for the network adapters.
 
-For both the primary and secondary network adapters, check the default Inbound port rules (Allow VNet Inbound, Allow Load Balancer) to inbound on both network adapters. You should also make sure that there are no matching blocking rules that have a lower-priority rule above them.
+For both the primary and secondary network adapters, check the default Inbound port rules of **Allow VNet Inbound** and  **Allow Load Balancer** allow inbound on both network adapters. You should also make sure that there are no matching blocking rules that have a lower-priority rule above them.
 
 ![Screenshot shows the Networking settings for a virtual machine where you can see Allow V net Inbound and Allow V net OutBound.](media/troubleshoot-vm-connectivity/nsg.png)
 
@@ -229,7 +228,7 @@ Hops             : [
 
 #### Step 4: Refer the table under [Step 5](#step-5-fix-the-issue-in-the-connectivity-check-result), and follow these steps to resolve the issues.
 
-### Azure VM cannot connect to the internet
+### Azure VM can't connect to the internet
 
 #### Step 1: Check whether the network adapter is in a failed state.
 

articles/virtual-network/tutorial-tap-virtual-network-cli.md

@@ -1,26 +1,26 @@
 ---
-title: Create, change, or delete a VNet TAP - Azure CLI
+title: Create, change, or delete a virtual network TAP - Azure CLI
 description: Learn how to create, change, or delete a virtual network TAP using the Azure CLI.
 services: virtual-network
 author: asudbring
 manager: ganesr
 ms.service: azure-virtual-network
 ms.topic: how-to
-ms.date: 03/18/2018
+ms.date: 04/17/2025
 ms.author: allensu
 ms.custom: devx-track-azurecli
 ---
 
 # Work with a virtual network TAP using the Azure CLI
 
 > [!IMPORTANT]
-> Virtual network TAP Preview is currently in Preview in select Azure regions. You can sign up for our Previews using the sign form (https://forms.office.com/r/EWqbgLGNcV) and we will notify you when you are selected. In the interim, you can use agent based or NVA solutions that provide TAP/Network Visibility functionality through our [Packet Broker partner solutions](virtual-network-tap-overview.md#virtual-network-tap-partner-solutions) available in [Azure Marketplace Offerings](https://azuremarketplace.microsoft.com/marketplace/apps/category/networking?page=1&subcategories=appliances%3Ball&search=Network%20Traffic&filters=partners).
+> Virtual network TAP Preview is currently in Preview in select Azure regions. You can sign up for our Previews using the sign form (https://forms.office.com/r/EWqbgLGNcV) and we'll notify you when you're selected. In the interim, you can use agent based or NVA solutions that provide TAP/Network Visibility functionality through our [Packet Broker partner solutions](virtual-network-tap-overview.md#virtual-network-tap-partner-solutions) available in [Azure Marketplace Offerings](https://azuremarketplace.microsoft.com/marketplace/apps/category/networking?page=1&subcategories=appliances%3Ball&search=Network%20Traffic&filters=partners).
 
 Azure virtual network TAP (Terminal Access Point) allows you to continuously stream your virtual machine network traffic to a network packet collector or analytics tool. The collector or analytics tool is provided by a [network virtual appliance](https://azure.microsoft.com/solutions/network-appliances/) partner. For a list of partner solutions that are validated to work with virtual network TAP, see [partner solutions](virtual-network-tap-overview.md#virtual-network-tap-partner-solutions). 
 
 ## Create a virtual network TAP resource
 
-Read [prerequisites](virtual-network-tap-overview.md#prerequisites) before you create a virtual network TAP resource. You can run the commands that follow in the [Azure Cloud Shell](https://shell.azure.com/bash), or by running the Azure CLI from your computer. The Azure Cloud Shell is a free interactive shell that doesn't require installing the Azure CLI on your computer. You must sign in to Azure with an account that has the appropriate [permissions](virtual-network-tap-overview.md#permissions). This article requires the Azure CLI version 2.0.46 or later. Run `az --version` to find the installed version. If you need to install or upgrade, see [Install Azure CLI 2.0](/cli/azure/install-azure-cli). Virtual network TAP is currently available as an extension. To install the extension you need to run `az extension add -n virtual-network-tap`. If you are running the Azure CLI locally, you also need to run `az login` to create a connection with Azure.
+Read [prerequisites](virtual-network-tap-overview.md#prerequisites) before you create a virtual network TAP resource. You can run the commands that follow in the [Azure Cloud Shell](https://shell.azure.com/bash), or by running the Azure CLI from your computer. The Azure Cloud Shell is a free interactive shell that doesn't require installing the Azure CLI on your computer. You must sign in to Azure with an account that has the appropriate [permissions](virtual-network-tap-overview.md#permissions). This article requires the Azure CLI version 2.0.46 or later. Run `az --version` to find the installed version. If you need to install or upgrade, see [Install Azure CLI 2.0](/cli/azure/install-azure-cli). Virtual network TAP is currently available as an extension. To install the extension you need to run `az extension add -n virtual-network-tap`. If you're running the Azure CLI locally, you also need to run `az login` to create a connection with Azure.
 
 1. Retrieve the ID of your subscription into a variable that is used in a later step:
 
@@ -30,21 +30,21 @@ Read [prerequisites](virtual-network-tap-overview.md#prerequisites) before you c
    --out tsv)
    ```
 
-2. Set the subscription id that you will use to create a virtual network TAP resource.
+2. Set the subscription ID that you'll use to create a virtual network TAP resource.
 
    ```azurecli-interactive
    az account set --subscription $subscriptionId
    ```
 
-3. Re-register the subscription ID that you'll use to create a virtual network TAP resource. If you get a registration error when you create a TAP resource, run the following command:
+3. Re-register the subscription ID that you use to create a virtual network TAP resource. If you get a registration error when you create a TAP resource, run the following command:
 
    ```azurecli-interactive
    az provider register --namespace Microsoft.Network --subscription $subscriptionId
    ```
 
-4. If the destination for the virtual network TAP is the network interface on the network virtual appliance for collector or analytics tool -
+4. If the destination for the virtual network TAP is the network interface on the network virtual appliance for collector or analytics tool:
 
-   - Retrieve the IP configuration of the network virtual appliance's network interface into a variable that is used in a later step. The ID is the end point that will aggregate the TAP traffic. The following example retrieves the ID of the *ipconfig1* IP configuration for a network interface named *myNetworkInterface*, in a resource group named *myResourceGroup*:
+   - Retrieve the IP configuration of the network virtual appliance's network interface into a variable that is used in a later step. The ID is the end point that aggregates the TAP traffic. The following example retrieves the ID of the *ipconfig1* IP configuration for a network interface named *myNetworkInterface*, in a resource group named *myResourceGroup*:
 
       ```azurecli-interactive
        IpConfigId=$(az network nic ip-config show \
@@ -67,7 +67,7 @@ Read [prerequisites](virtual-network-tap-overview.md#prerequisites) before you c
 
 5. If the destination for the virtual network TAP is an Azure internal load balancer:
   
-   - Retrieve the front end IP configuration of the Azure internal load balancer into a variable that is used in a later step. The ID is the end point that will aggregate the TAP traffic. The following example retrieves the ID of the *frontendipconfig1* front end IP configuration for a load balancer named *myInternalLoadBalancer*, in a resource group named *myResourceGroup*:
+   - Retrieve the front end IP configuration of the Azure internal load balancer into a variable that is used in a later step. The ID is the end point that aggregates the TAP traffic. The following example retrieves the ID of the *frontendipconfig1* front end IP configuration for a load balancer named *myInternalLoadBalancer*, in a resource group named *myResourceGroup*:
 
       ```azurecli-interactive
       FrontendIpConfigId=$(az network lb frontend-ip show \
@@ -78,7 +78,7 @@ Read [prerequisites](virtual-network-tap-overview.md#prerequisites) before you c
       --out tsv)
       ```
 
-   - Create the virtual network TAP using the ID of the frontend IP configuration as the destination and an optional port property. The port specifies the destination port on front end IP configuration where the TAP traffic will be received :  
+   - Create the virtual network TAP using the ID of the frontend IP configuration as the destination and an optional port property. The port specifies the destination port on front end IP configuration where the TAP traffic will be received:  
 
       ```azurecli-interactive
       az network vnet tap create \
@@ -153,3 +153,6 @@ Read [prerequisites](virtual-network-tap-overview.md#prerequisites) before you c
    --resource-group myResourceGroup \
    --name myTap
    ```
+
+## Next steps
+- [Virtual network TAP overview](virtual-network-tap-overview.md)