Skip to content

Commit e86a092

Browse files
author
Jill Grant
authored
Merge pull request #275764 from mbender-ms/wb-pp-vv2
virtual network manager - Public Preview - VNet Verifier
2 parents 63569dc + ddf2c86 commit e86a092

12 files changed

+224
-0
lines changed

articles/virtual-network-manager/TOC.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -69,6 +69,8 @@
6969
href: concept-virtual-network-flow-logs.md
7070
- name: Query Azure Virtual Network Manager using Azure Resource Graph (ARG)
7171
href: query-azure-resource-graph.md
72+
- name: Verify resource reachability with Virtual Network Verifier
73+
href: concept-virtual-network-verifier.md
7274
- name: Samples
7375
items:
7476
- name: Resource Manager Templates
@@ -117,6 +119,8 @@
117119
href: how-to-view-applied-configurations.md
118120
- name: Define dynamic network group membership with Azure Policy
119121
href: how-to-define-network-group-membership-azure-policy.md
122+
- name: Verify resource reachability
123+
href: how-to-verify-reachability-with-virtual-network-verifier.md
120124
- name: Common issues
121125
href: common-issues.md
122126
- name: Reference
Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
---
2+
title: What is Virtual Network Verifier?
3+
description: Learn how Virtual Network Verifier helps you verify your network policies allow or disallow traffic between your Azure network resources.
4+
author: mbender-ms
5+
ms.author: mbender
6+
ms.topic: concept
7+
ms.service: virtual-network-manager
8+
ms.date: 05/20/2024
9+
---
10+
11+
# How does Virtual Network Verifier work?
12+
13+
In Azure Virtual Network Manager, Virtual Network Verifier enables you to check if your network policies allow or disallow traffic between your Azure network resources. It can help you answer simple diagnostic questions to triage why reachability isn't working as expected and prove conformance of your Azure setup to your organization’s security compliance requirements. When you run a reachability analysis in Virtual Network Verifier, it can answer questions such as why two virtual machines can't communicate with each other.
14+
15+
[!INCLUDE [virtual-network-verifier-preview](../../includes/virtual-network-verifier-preview.md)]
16+
17+
## How does Verifier Workspace work?
18+
19+
Virtual Network Verifier is available in every network manager instance through a resource called a verifier workspace, which acts as a container for Virtual Network Verifier's child resources and capabilities. A network manager can have one or more verifier workspaces and these verifier workspaces can be delegated to non-network manager users. A verifier workspace uses the following workflow to gather and analyze network data.
20+
21+
### Create a verifier workspace
22+
23+
A verifier workspace is a child resource of a network manager. Its permissions can be delegated to non-network manager admin users and it's discoverable from the Azure portal. The verifier workspace includes its own child resources of reachability analysis intents and reachability analysis results, and it uses its parent network manager's scope as the boundary to run analysis.
24+
25+
### Delegate a verifier workspace resource
26+
27+
By default, users with permissions to a network manager have permissions to create, delete, and extend permissions of a verifier workspace. A user that doesn't have permission to a verifier workspace's parent network manager can be granted permissions through the verifier workspace's access control by assigning them the role of "Contributor." Granting a user permission to a verifier workspace in this way doesn't give that user access to the rest of the network manager instance.
28+
29+
### Create a reachability analysis intent
30+
31+
Within a verifier workspace, you create a reachability analysis intent to define the traffic path between a source and destination that you want to verify. The reachability analysis intent includes the following fields:
32+
33+
| **Field** | **Description **|
34+
|-------|-------------|
35+
| **Source** | The source of the traffic that can be a virtual machine, subnet, or the internet. |
36+
| **Source ports** | The source ports of the traffic. |
37+
| **Source IP addresses** | The source IP addresses of the traffic. |
38+
| **Destination** | The destination of the traffic that can be a virtual machine, subnet, Cosmos DB, storage account, SQL server, or the internet. |
39+
| **Destination ports** | The destination ports of the traffic. |
40+
| **Destination IP addresses** | The destination IP addresses of the traffic. |
41+
| **Protocol** | The protocol of the traffic. |
42+
43+
You can create multiple reachability analysis intents within a verifier workspace and run them in parallel. Any user with permissions to a given verifier workspace can create, view, and delete its reachability analysis intents.
44+
45+
### Run a reachability analysis
46+
47+
After defining a reachability analysis intent, you need to perform an analysis to get verification results. This static analysis checks if various resources and policy configurations in the network manager's scope preserve reachability between the given source and destination of the reachability analysis intent. Once the analysis is done, it produces a reachability analysis result.
48+
49+
The reachability analysis result is a JSON object that indicates whether packets can reach the reachability analysis intent's destination from its source. It provides details about the path of connectivity, showing where traffic was blocked if the source and destination couldn't connect. It includes information about the resources on the path and their metadata regardless of the reachability analysis result's outcome.
50+
51+
In the Azure portal, this reachability analysis result is visualized to show the forward path of the reachability analysis intent's defined connectivity. Any user with access to the verifier workspace can run a reachability analysis on any reachability analysis intent within that verifier workspace.
52+
53+
## Supported features of the reachability analysis
54+
55+
When run, a reachability analysis evaluates the following features:
56+
57+
- Network security group (NSG) rules
58+
- Application security group (ASG) rules
59+
- Azure Virtual Network Manager security admin rules
60+
- Azure Virtual Network Manager mesh topology (connected group)
61+
- Virtual network peering
62+
- Route tables
63+
- Service endpoints & access control lists
64+
- Private endpoints
65+
- Virtual WAN
66+
67+
This list is subject to expand.
68+
69+
## Limits
70+
71+
The limitations in the public preview of Virtual Network Verifier are as follows:
72+
- A reachability analysis can only be run on a single reachability analysis intent.
73+
- Subnets selected as the source and/or destination of a reachability analysis intent must have at least one running virtual machine for a reachability analysis result to be provided.
74+
- Reachability analysis results are based on the evaluation of supported Azure services, resources, and policies listed as supported features here. Actual traffic behavior resulting from services not explicitly listed above can vary from the reachability analysis result.
75+
76+
## Next steps
77+
78+
> [!div class="nextstepaction"]
79+
> [Learn to analyze resource reachability with Virtual Network Verifier in Azure Virtual Network Manager](how-to-verify-reachability-with-virtual-network-verifier.md)
Lines changed: 110 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,110 @@
1+
---
2+
title: 'Verify resource reachability with Virtual Network Verifier - Azure portal'
3+
description: 'Learn how to use Virtual Network Verifier in the Azure portal to verify the reachability from one VM to another VM based on your applied network policies.'
4+
author: mbender-ms
5+
ms.author: mbender
6+
ms.topic: how-to
7+
ms.service: virtual-network-manager
8+
ms.date: 05/20/2024
9+
ms.custom: references_regions
10+
---
11+
12+
# Verify resource reachability with Virtual Network Verifier - Azure portal
13+
14+
In this article, you learn how to use Virtual Network Verifier in the Azure portal to verify the reachability of a storage account from a VM based on your applied network policies. As part of the process, you create a verifier workspace, create a reachability analysis intent, run a reachability analysis, and view the reachability analysis results. This article also demonstrates how you can delegate verifier workspaces to other users in your organization so they gain the ability to use a permitted verifier workspace.
15+
16+
[!INCLUDE [virtual-network-verifier-preview](../../includes/virtual-network-verifier-preview.md)]
17+
18+
## Prerequisites
19+
20+
- An Azure subscription. If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/) before you begin.
21+
- An existing network manager instance. If you don't have a network manager instance, create one by following the instructions in [Create a virtual network manager](create-virtual-network-manager-portal.md).
22+
- A verifier workspace is a child resource of a network manager, so it must be created from a network manager instance. Once a verifier workspace exists, it can be accessed directly from the Azure portal by searching **Verifier workspaces**.
23+
- Resources to verify reachability between. In this example, two virtual machines are used.
24+
25+
## Create a Virtual Network Verifier
26+
27+
In this step, you create a verifier workspace in your network manager to set up the reachability analysis intent needed to verify whether your virtual machine can reach your other virtual machine.
28+
29+
1. In the Azure portal, type **Network managers** into the search box on the task bar and select the desired network manager instance.
30+
2. Within the network manager instance, navigate to the **Verifier workspace** pane to create a new verifier workspace.
31+
3. Select **Create** to create a new verifier workspace.
32+
4. On the **Create a virtual network manager verifier workspace** page, provide a name and optional description for your verifier workspace.
33+
34+
35+
## Create a reachability analysis intent
36+
37+
In this step, you create a reachability analysis intent in your verifier workspace. This analysis intent describes the traffic path being checked for reachability.
38+
39+
1. Within the verifier workspace you created, select **Define an analysis intent** directly, or navigate to **Reachability analysis intents** under *Settings* and select **+ Create**.
40+
2. Enter or select the following information, then select **Create** to create the reachability analysis intent.
41+
42+
| Setting | Value |
43+
| --- | --- |
44+
| **Name** | Enter a name for the reachability analysis intent. |
45+
| **Protocol** | Select the protocol of the traffic you want to verify. |
46+
| **Source type** | Select the source type of either **Public internet**, **Virtual machines**, or **Subnet**. Select **Virtual machines** for this example. |
47+
| **Source** | If a virtual machine is selected as the source type, use the selection picker to select an instance from the parent network manager's scope. |
48+
| **Source IP address** | Enter an IPv4 or IPv6 address or a range using CIDR notation of the source you want to verify. |
49+
| **Source port** | Enter a port or a range of the source you want to verify. To specify any port, enter *. |
50+
| **Destination type** | Select the destination type of either **Public internet**, **Cosmos DB**, **Storage Account**, **SQL Server**, **Virtual machines**, or **Subnet**. Select **Virtual machines** for this example. |
51+
| **Destination** | If a Cosmos DB, storage account, SQL server, or virtual machine is selected as the destination type, use the selection picker to select an instance from the parent network manager's scope. |
52+
| **Destination IP address** | Enter an IPv4 or IPv6 address or a range using CIDR notation of the destination you want to verify. |
53+
| **Destination port** | Enter a port or a range of the destination you want to verify. To specify any port, enter *. |
54+
55+
:::image type="content" source="media/how-to-verify-reachability-with-virtual-network-verifier/create-analysis-intent.png" alt-text="Screenshot of Create analysis intent window with settings and values.":::
56+
57+
3. Repeat the process to create more reachability analysis intents in the verifier workspace.
58+
59+
## Start an analysis
60+
61+
After setting up a reachability analysis intent, you can initiate an analysis. This analysis checks if a path exists between the source and destination specified in the intent, considering the network policies and resources that are currently in place. This analysis evaluates policies and resources within the scope of the verifier workspace's parent network manager.
62+
63+
1. Under **Reachability analysis intents**, select the checkbox next to the reachability analysis intent you want to analyze and select **Start analysis**.
64+
2. In the **Start analysis** pane, enter a name and optional description for the analysis, and then select the **Start analysis** button.
65+
66+
:::image type="content" source="media/how-to-verify-reachability-with-virtual-network-verifier/start-analysis-run.png" alt-text="Screenshot of Start analysis window for analysis intent run job.":::
67+
68+
> [!NOTE]
69+
> The analysis run may take a few minutes to complete. You can monitor the progress of the analysis in the Azure Portal.
70+
71+
## View reachability analysis results
72+
In this step, you view the results of the analysis you started in the previous step.
73+
74+
1. In the verifier workspace, select **Reachability analysis intents** under *Settings* and select the corresponding **View results** for your reachability analysis intent. Alternatively, navigate to **Reachability analysis results** and select the name of the result you want to view.
75+
76+
:::image type="content" source="media/how-to-verify-reachability-with-virtual-network-verifier/select-analysis-results.png" alt-text="Screenshot of Reachability analysis intent windows showing analysis intent run to view.":::
77+
2. In the **View analysis results** pane, you can view the results of the analysis, including the status of the analysis, the path taken by the traffic, the resources traversed, and the result outcome.
78+
79+
:::image type="content" source="media/how-to-verify-reachability-with-virtual-network-verifier/view-analysis-results.png" alt-text="Screenshot of Reachability analysis results window with analysis results.":::
80+
81+
3. On the **Reachability analysis results** tab in the **View analysis results** pane, you see the results in a visual format. The visualization shows the path taken by the traffic and the resources traversed.
82+
83+
:::image type="content" source="media/how-to-verify-reachability-with-virtual-network-verifier/view-analysis-results-visualization.png" alt-text="Screenshot of Reachability analysis results window with visualization of analysis results.":::
84+
85+
4. Select one of the resources in the visualization to view the resource details. You can also select any of the lengths in the visualization to view details of that step.
86+
87+
:::image type="content" source="media/how-to-verify-reachability-with-virtual-network-verifier/network-manager-reachability-results-details.png" alt-text="Screenshot of resource details for network manager from analysis intent results.":::
88+
89+
5. Select the **JSON output** tab to view the full JSON output of the analysis result. The beginning of the JSON object details the outcome of the result, which indicates whether all packets reached, some packets reached, or no packets reached. Explanations are provided for each outcome and each reachability step.
90+
91+
:::image type="content" source="media/how-to-verify-reachability-with-virtual-network-verifier/view-json-results.png" alt-text="Screenshot of JSON output for reachability analysis results.":::
92+
93+
6. Select **Close** to close the analysis results.
94+
95+
96+
## Delegate a verifier workspace to other users
97+
98+
Optionally, you can delegate a verifier workspace to other users. This allows other users to use a network verifier's capability by granting them access to the verifier workspace, reachability analysis intents, analysis ability, and reachability analysis results. Each verifier workspace in a network manager has its own permissions, so granting a user access to one verifier workspace doesn't result in access to all verifier workspaces under the same network manager. Granting a user permission to a verifier workspace also doesn't result in any access to the rest of the parent network manager.
99+
100+
1. In the verifier workspace, select **Access control (IAM)**.
101+
2. Select **+ Add** and **Add role assignment**.
102+
3. Within *Add role assignment* and the *Role* tab, select the **Privileged administrator roles** tab and select the **Contributor** role.
103+
4. Select the **Members** tab and add the users you want to have access to the verifier workspace to by clicking **+ Select members**.
104+
5. Select **Review + assign**.
105+
106+
107+
## Next steps
108+
109+
> [!div class="nextstepaction"]
110+
> [What is Virtual Network Verifier](concept-virtual-network-verifier.md)
Loading
Loading
Loading
Loading
Loading
Loading
Loading

0 commit comments

Comments
 (0)