Skip to content

Commit fe5ae3e

Browse files
Merge pull request #247195 from mbender-ms/avnm-vnet-flow-logs
virtual network manager - New Doc - Monitoring with VNet Flow Logs #newmb
2 parents fa440eb + c8f878d commit fe5ae3e

File tree

2 files changed

+105
-0
lines changed

2 files changed

+105
-0
lines changed

articles/virtual-network-manager/TOC.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,8 @@
6161
items:
6262
- name: Event Log Options for Azure Virtual Network Manager
6363
href: concept-event-logs.md
64+
- name: Monitoring security admin rules with Virtual Network Flow Logs
65+
href: concept-virtual-network-flow-logs.md
6466
- name: Samples
6567
items:
6668
- name: Resource Manager Templates
@@ -99,6 +101,8 @@
99101
items:
100102
- name: Configure Event Logs for Azure Virtual Network Manager
101103
href: how-to-configure-event-logs.md
104+
- name: Monitor security admin rules with Virtual Network Flow Logs
105+
href: concept-virtual-network-flow-logs.md
102106
- name: View applied configurations
103107
href: how-to-view-applied-configurations.md
104108
- name: Define dynamic network group membership with Azure Policy
Lines changed: 101 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,101 @@
1+
---
2+
title: Monitoring security admin rules with Virtual Network Flow Logs
3+
description: This article covers using Network Watcher and Virtual Network Flow Logs to monitor traffic through security admin rules in Azure Virtual Network Manager.
4+
author: mbender-ms
5+
ms.author: mbender
6+
ms.topic: conceptual
7+
ms.service: virtual-network-manager
8+
ms.date: 08/11/2023
9+
---
10+
11+
# Monitoring Azure Virtual Network Manager with VNet flow logs (Preview)
12+
13+
Monitoring traffic is critical to understanding how your network is performing and to troubleshoot issues. Administrators can utilize VNet flow logs (Preview) to show whether traffic is flowing through or blocked on a VNet by a [security admin rule]. VNet flow logs (Preview) are a feature of Network Watcher.
14+
15+
Learn more about [VNet flow logs (Preview)](../network-watcher/vnet-flow-logs-overview.md) including usage and how to enable.
16+
17+
> [!IMPORTANT]
18+
> VNet flow logs is currently in PREVIEW. This preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
19+
20+
> [!IMPORTANT]
21+
> Azure Virtual Network Manager is generally available for Virtual Network Manager and hub-and-spoke connectivity configurations. Mesh connectivity configurations and security admin rules remain in public preview.
22+
>
23+
> This preview version is provided without a service-level agreement, and we don't recommend it for production workloads. Certain features might not be supported or might have constrained capabilities. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
24+
25+
## Enable VNet flow logs (Preview)
26+
27+
Currently, you need to enable Virtual Network flow logs (Preview) on each VNet you want to monitor. You can enable Virtual Network Flow Logs on a VNet by using [PowerShell](../network-watcher/vnet-flow-logs-powershell.md) or the [Azure CLI](../network-watcher/vnet-flow-logs-cli.md).
28+
29+
Here's an example of a flow log
30+
31+
```json
32+
{
33+
"records": [
34+
{
35+
"time": "2022-09-14T09:00:52.5625085Z",
36+
"flowLogVersion": 4,
37+
"flowLogGUID": "a1b2c3d4-e5f6-g7h8-i9j0-k1l2m3n4o5p6",
38+
"macAddress": "00224871C205",
39+
"category": "FlowLogFlowEvent",
40+
"flowLogResourceID": "/SUBSCRIPTIONS/1a2b3c4d-5e6f-7g8h-9i0j-1k2l3m4n5o6p7/RESOURCEGROUPS/NETWORKWATCHERRG/PROVIDERS/MICROSOFT.NETWORK/NETWORKWATCHERS/NETWORKWATCHER_EASTUS2EUAP/FLOWLOGS/VNETFLOWLOG",
41+
"targetResourceID": "/subscriptions/1a2b3c4d-5e6f-7g8h-9i0j-1k2l3m4n5o6p7/resourceGroups/myResourceGroup/providers/Microsoft.Network/virtualNetworks/myVNet01",
42+
"operationName": "FlowLogFlowEvent",
43+
"flowRecords": {
44+
"flows": [
45+
{
46+
"aclID": "9a8b7c6d-5e4f-3g2h-1i0j-9k8l7m6n5o4p3",
47+
"flowGroups": [
48+
{
49+
"rule": "DefaultRule_AllowInternetOutBound",
50+
"flowTuples": [
51+
"1663146003599,10.0.0.6,52.239.184.180,23956,443,6,O,B,NX,0,0,0,0",
52+
"1663146003606,10.0.0.6,52.239.184.180,23956,443,6,O,E,NX,3,767,2,1580",
53+
"1663146003637,10.0.0.6,40.74.146.17,22730,443,6,O,B,NX,0,0,0,0",
54+
"1663146003640,10.0.0.6,40.74.146.17,22730,443,6,O,E,NX,3,705,4,4569",
55+
"1663146004251,10.0.0.6,40.74.146.17,22732,443,6,O,B,NX,0,0,0,0",
56+
"1663146004251,10.0.0.6,40.74.146.17,22732,443,6,O,E,NX,3,705,4,4569",
57+
"1663146004622,10.0.0.6,40.74.146.17,22734,443,6,O,B,NX,0,0,0,0",
58+
"1663146004622,10.0.0.6,40.74.146.17,22734,443,6,O,E,NX,2,134,1,108",
59+
"1663146017343,10.0.0.6,104.16.218.84,36776,443,6,O,B,NX,0,0,0,0",
60+
"1663146022793,10.0.0.6,104.16.218.84,36776,443,6,O,E,NX,22,2217,33,32466"
61+
]
62+
}
63+
]
64+
},
65+
{
66+
"aclID": "b1c2d3e4-f5g6-h7i8-j9k0-l1m2n3o4p5q6",
67+
"flowGroups": [
68+
{
69+
"rule": "BlockHighRiskTCPPortsFromInternet",
70+
"flowTuples": [
71+
"1663145998065,101.33.218.153,10.0.0.6,55188,22,6,I,D,NX,0,0,0,0",
72+
"1663146005503,192.241.200.164,10.0.0.6,35276,119,6,I,D,NX,0,0,0,0"
73+
]
74+
},
75+
{
76+
"rule": "Internet",
77+
"flowTuples": [
78+
"1663145989563,20.106.221.10,10.0.0.6,50557,44357,6,I,D,NX,0,0,0,0",
79+
"1663145989679,20.55.117.81,10.0.0.6,62797,35945,6,I,D,NX,0,0,0,0",
80+
"1663145989709,20.55.113.5,10.0.0.6,51961,65515,6,I,D,NX,0,0,0,0",
81+
"1663145990049,13.65.224.51,10.0.0.6,40497,40129,6,I,D,NX,0,0,0,0",
82+
"1663145990145,20.55.117.81,10.0.0.6,62797,30472,6,I,D,NX,0,0,0,0",
83+
"1663145990175,20.55.113.5,10.0.0.6,51961,28184,6,I,D,NX,0,0,0,0",
84+
"1663146015545,20.106.221.10,10.0.0.6,50557,31244,6,I,D,NX,0,0,0,0"
85+
]
86+
}
87+
]
88+
}
89+
]
90+
}
91+
}
92+
]
93+
}
94+
95+
```
96+
97+
98+
## Next steps
99+
> [!div class="nextstepaction"]
100+
> Learn more about [VNet Flow Logs](../network-watcher/vnet-flow-logs-overview.md) and how to use them.
101+
> Learn more about [Event log options for Azure Virtual Network Manager](concept-event-logs.md).

0 commit comments

Comments
 (0)