Skip to content

Commit a265b90

Browse files
Merge pull request #259740 from halkazwini/nw-vnet
Update storage account considerations
2 parents 08d2468 + c9cb4be commit a265b90

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

articles/network-watcher/vnet-flow-logs-overview.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,9 @@ author: halkazwini
66
ms.author: halkazwini
77
ms.service: network-watcher
88
ms.topic: concept-article
9-
ms.date: 08/16/2023
9+
ms.date: 11/29/2023
10+
11+
#CustomerIntent: As an Azure administrator, I want to learn about VNet flow logs so that I can log my network traffic to analyze and optimize the network performance.
1012
---
1113

1214
# VNet flow logs (preview)
@@ -208,8 +210,9 @@ For continuation (`C`) and end (`E`) flow states, byte and packet counts are agg
208210

209211
### Storage account
210212

211-
- **Location**: The storage account used must be in the same region as the virtual network.
212-
- **Performance tier**: Currently, only standard-tier storage accounts are supported.
213+
- **Location**: The storage account must be in the same region as the virtual network.
214+
- **Subscription**: The storage account must be in a subscription associated with the same Microsoft Entra tenant as the virtual network's subscription.
215+
- **Performance tier**: The storage account must be standard. Premium storage accounts aren't supported.
213216
- **Self-managed key rotation**: If you change or rotate the access keys to your storage account, VNet flow logs stop working. To fix this problem, you must disable and then re-enable VNet flow logs.
214217

215218
### Cost

0 commit comments

Comments
 (0)