Skip to content

Commit 6e84889

Browse files
authored
Update packet-capture-overview.md
Adding SAS token check onto the storage
1 parent 126e42b commit 6e84889

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,6 +51,8 @@ Use filters to capture only the traffic that you want to monitor. Filters are ba
5151

5252
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.
5353

54+
Packet capture currently supports SAS authentication when writing completed packet captures to storage accounts. SAS authentication is required if choosing to write to storage. If SAS authentication is not an option, then writing to the local file storage on the virtual machine where the packet capture is taken is the alternative.
55+
5456
## Related content
5557

5658
- To learn how to manage packet captures, see [Manage packet captures with Azure Network Watcher](packet-capture-manage.md).

0 commit comments

Comments
 (0)