Skip to content

Commit bc3c7a4

Browse files
authored
Merge pull request #232825 from halkazwini/nw-limits
Network Watcher: Updates: Network Watcher limits
2 parents fa3f281 + 6c4dae9 commit bc3c7a4

File tree

4 files changed

+19
-13
lines changed

4 files changed

+19
-13
lines changed

articles/azure-resource-manager/management/azure-subscription-service-limits.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -347,6 +347,10 @@ The following table applies to v1, v2, Standard, and WAF SKUs unless otherwise s
347347

348348
[!INCLUDE [azure-front-door-service-limits](../../../includes/front-door-limits.md)]
349349

350+
### Azure Network Watcher limits
351+
352+
[!INCLUDE [network-watcher-limits](../../../includes/network-watcher-limits.md)]
353+
350354
### Azure Route Server limits
351355

352356
[!INCLUDE [Azure Route Server Limits](../../../includes/route-server-limits.md)]
@@ -359,10 +363,6 @@ The following table applies to v1, v2, Standard, and WAF SKUs unless otherwise s
359363

360364
[!INCLUDE [nat-gateway-limits](../../../includes/azure-nat-gateway-limits.md)]
361365

362-
### Network Watcher limits
363-
364-
[!INCLUDE [network-watcher-limits](../../../includes/network-watcher-limits.md)]
365-
366366
### Private Link limits
367367

368368
[!INCLUDE [private-link-limits](../../../includes/private-link-limits.md)]

articles/network-watcher/frequently-asked-questions.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ sections:
8888
- question: |
8989
What are resource limits on Network Watcher?
9090
answer: |
91-
See the [Service limits](../azure-resource-manager/management/azure-subscription-service-limits.md#network-watcher-limits) page for all limits.
91+
See the [Service limits](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-network-watcher-limits) page for all limits.
9292
9393
- question: |
9494
Why is only one instance of Network Watcher allowed per region?

articles/network-watcher/network-watcher-packet-capture-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ To control the size of captured data and only capture required information, use
4646

4747
## Considerations
4848

49-
There's a limit of 10,000 parallel packet capture sessions per region per subscription. This limit applies only to the sessions and doesn't apply to the saved packet capture files either locally on the VM or in a storage account. See the [Network Watcher service limits page](../azure-resource-manager/management/azure-subscription-service-limits.md#network-watcher-limits) for a full list of limits.
49+
There's a limit of 10,000 parallel packet capture sessions per region per subscription. This limit applies only to the sessions and doesn't apply to the saved packet capture files either locally on the VM or in a storage account. See the [Network Watcher service limits page](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-network-watcher-limits) for a full list of limits.
5050

5151
## Next steps
5252

includes/network-watcher-limits.md

Lines changed: 13 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,17 @@
11
---
2-
author: rothja
2+
author: halkazwini
33
ms.service: network-watcher
44
ms.topic: include
5-
ms.date: 11/09/2018
6-
ms.author: jroth
5+
ms.date: 03/30/2023
6+
ms.author: halkazwini
7+
ms.custom: include file
78
---
8-
| Resource | Limit | Note |
9-
| --- | --- | --- | --- |
10-
| Azure Network Watcher | 1 per region | Network Watcher is created to enable access to the service. Only one instance of Network Watcher is required per subscription per region. |
11-
| Packet capture sessions |10,000 per region |Number of sessions only, not saved captures. |
9+
| Resource | Limit |
10+
| --- | --- |
11+
| Network Watcher instances per region per subscription | 1 (One instance in a region to enable access to the service in the region) |
12+
| Connection monitors per region per subscription | 100 |
13+
| Maximum test groups per a connection monitor | 20 |
14+
| Maximum sources and destinations per a connection monitor | 100 |
15+
| Maximum test configurations per a connection monitor | 20 |
16+
| Packet capture sessions per region per subscription | 10,000 (Number of sessions only, not saved captures) |
17+
| VPN troubleshoot operations per subscription | 1 (Number of operations at one time) |

0 commit comments

Comments
 (0)