NSG flow log limitation with Storage service endpoints

[mamaejim]

Discussed NSG flow log limitation with thread below on July, but the limitation is not resolved as of now.

https://github.com/MicrosoftDocs/azure-docs/issues/29114

Could you please consider to indicate that in the document? A lot of users uses service endpoint for Azure storage and they cannot aware this limitation.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: bd699dac-d6e5-5a39-624f-2d3f77f92fca
• Version Independent ID: c922bcd2-0778-a7af-4855-1bff6c9ce380
• Content: Introduction to flow logging for network security groups with Azure Network Watcher
• Content Source: articles/network-watcher/network-watcher-nsg-flow-logging-overview.md
• Service: network-watcher
• GitHub Login: @KumudD
• Microsoft Alias: kumud

[SubhashVasarapu-MSFT]

@mamaejim , Thanks for your feedback. We are assigning this issue to the content author for updating the document accordingly. @KumudD , Could you please provide your insights here?

[KumudD]

reassign:damendo

[damendo]

Updated the considerations

[damendo]

please-close

[damendo]

FYI: NSG Flow Logs are now compatible with Secured/Firewalled storage accounts. With this update, Service Endpoints for Microsoft storage are also supported for NSG Flow Logs.

The “Allow trusted Microsoft services to access this storage account” toggle on the Storage account must be enabled for this to work.

From: https://feedback.azure.com/forums/217313/suggestions/33684529