Skip to content

Commit 303e4af

Browse files
committed
updates
1 parent 9919b18 commit 303e4af

File tree

2 files changed

+36
-37
lines changed

2 files changed

+36
-37
lines changed

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

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,26 @@
11
---
2-
title: Create, change, or delete a VNet TAP - Azure CLI
2+
title: Create, change, or delete a virtual network TAP - Azure CLI
33
description: Learn how to create, change, or delete a virtual network TAP using the Azure CLI.
44
services: virtual-network
55
author: asudbring
66
manager: ganesr
77
ms.service: azure-virtual-network
88
ms.topic: how-to
9-
ms.date: 03/18/2018
9+
ms.date: 04/17/2025
1010
ms.author: allensu
1111
ms.custom: devx-track-azurecli
1212
---
1313

1414
# Work with a virtual network TAP using the Azure CLI
1515

1616
> [!IMPORTANT]
17-
> 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).
17+
> 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).
1818
1919
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).
2020

2121
## Create a virtual network TAP resource
2222

23-
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.
23+
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.
2424

2525
1. Retrieve the ID of your subscription into a variable that is used in a later step:
2626

@@ -30,21 +30,21 @@ Read [prerequisites](virtual-network-tap-overview.md#prerequisites) before you c
3030
--out tsv)
3131
```
3232

33-
2. Set the subscription id that you will use to create a virtual network TAP resource.
33+
2. Set the subscription ID that you'll use to create a virtual network TAP resource.
3434

3535
```azurecli-interactive
3636
az account set --subscription $subscriptionId
3737
```
3838

39-
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:
39+
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:
4040

4141
```azurecli-interactive
4242
az provider register --namespace Microsoft.Network --subscription $subscriptionId
4343
```
4444

4545
4. If the destination for the virtual network TAP is the network interface on the network virtual appliance for collector or analytics tool -
4646

47-
- 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*:
47+
- 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*:
4848

4949
```azurecli-interactive
5050
IpConfigId=$(az network nic ip-config show \
@@ -67,7 +67,7 @@ Read [prerequisites](virtual-network-tap-overview.md#prerequisites) before you c
6767
6868
5. If the destination for the virtual network TAP is an Azure internal load balancer:
6969
70-
- 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*:
70+
- 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*:
7171
7272
```azurecli-interactive
7373
FrontendIpConfigId=$(az network lb frontend-ip show \
@@ -78,7 +78,7 @@ Read [prerequisites](virtual-network-tap-overview.md#prerequisites) before you c
7878
--out tsv)
7979
```
8080
81-
- 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 :
81+
- 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:
8282
8383
```azurecli-interactive
8484
az network vnet tap create \

0 commit comments

Comments
 (0)