Update packet capture requirements in PowerShell guide #127906
Conversation
Clarified requirements for Azure VWAN VPN Gateway packet captures regarding storage account accessibility and endpoint limitations. Private endpoint and service endpoint work for regular VPN gateway captures but not for Azure VWAN VPN gateway as the CX has no ability to modify the gateway subnet
|
@MicrosoftAzureAaron : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 777c4d2: ✅ Validation status: passed
For more details, please refer to the build report. |
|
@cherylmc Can you review the proposed changes? Due to the upcoming conference, all merging and publishing is on hold until the morning of November 18th. Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
There was a problem hiding this comment.
Pull Request Overview
This PR updates the documentation for Azure Virtual WAN VPN Gateway packet captures to clarify storage account accessibility requirements. It explicitly states that public accessibility is required and explains why private endpoints and service endpoints are not supported for VWAN VPN Gateway scenarios.
Key Changes:
- Added requirement for publicly accessible Azure Storage Account
- Documented limitation regarding Private Endpoints for Blob Storage
- Documented limitation regarding Service Endpoints on Gateway subnet
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| * A Virtual WAN and a virtual hub. | ||
| * A site-to-site VPN gateway deployed in the virtual hub. | ||
| * You can also have connections connecting VPN sites to your site-to-site VPN gateway. | ||
| * A publically acessible Azure Storage Account. |
There was a problem hiding this comment.
Corrected spelling of 'publically' to 'publicly' and 'acessible' to 'accessible'.
| * A publically acessible Azure Storage Account. | |
| * A publicly accessible Azure Storage Account. |
| * Private Endpoints for Blob Storage will not work for Azure VWAN VPN Gateway packet captures, as the DNS for the VPN Gateway can not be modified by the customer. | ||
| * Serive Endpoints are not a valid connectivity method for Azure VWAN VPN Gateway packet captures as they can not be enabled on the Gateway subnet. |
There was a problem hiding this comment.
Corrected spelling of 'Serive' to 'Service' and changed 'can not' to 'cannot'.
| * Private Endpoints for Blob Storage will not work for Azure VWAN VPN Gateway packet captures, as the DNS for the VPN Gateway can not be modified by the customer. | |
| * Serive Endpoints are not a valid connectivity method for Azure VWAN VPN Gateway packet captures as they can not be enabled on the Gateway subnet. | |
| * Private Endpoints for Blob Storage will not work for Azure VWAN VPN Gateway packet captures, as the DNS for the VPN Gateway cannot be modified by the customer. | |
| * Service Endpoints are not a valid connectivity method for Azure VWAN VPN Gateway packet captures as they cannot be enabled on the Gateway subnet. |
3 participants
Clarified requirements for Azure VWAN VPN Gateway packet captures regarding storage account accessibility and endpoint limitations.
Private endpoint and service endpoint work for regular VPN gateway captures but not for Azure VWAN VPN gateway as the CX has no ability to modify the gateway subnet