Update storage-network-security-limitations.md#128131
Update storage-network-security-limitations.md#128131vikedesai wants to merge 2 commits intoMicrosoftDocs:mainfrom
Conversation
The customer has activated NSG flow logs using Network Watcher in the Azure portal. NSG flow logging lets you record details about IP traffic passing through a network security group, and these logs are stored in an Azure storage account. If the customer encounters a SASIpAuthorizationError, they can check for and remove any Azure backend IP addresses, including physical host IPs, from the storage account firewall.
|
@vikedesai : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 4360653: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
There was a problem hiding this comment.
Pull request overview
This PR adds a warning about Azure backend IP addresses in storage account firewalls when using NSG Flow Logs to help customers avoid SASIpAuthorizationError issues and high transaction costs.
Changes:
- Added a new bullet point warning about removing Azure backend IP addresses from storage account firewalls when using NSG Flow Logs
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
articles/storage/common/storage-network-security-limitations.md
Outdated
Show resolved
Hide resolved
articles/storage/common/storage-network-security-limitations.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
Learn Build status updates of commit a45c5f6: ✅ Validation status: passed
For more details, please refer to the build report. |
The customer has activated NSG flow logs using Network Watcher in the Azure portal. NSG flow logging lets you record details about IP traffic passing through a network security group, and these logs are stored in an Azure storage account. If the customer encounters a SASIpAuthorizationError, they can check for and remove any Azure backend IP addresses, including physical host IPs, from the storage account firewall.