MicrosoftDocs
Update packet capture requirements in PowerShell guide
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.
![prmerger-automator[bot] avatar](https://avatars.githubusercontent.com/u/22479449?v=4 "Published by a pub.dev verified publisher"){kind=small}
Learn Build status updates of commit 777c4d2:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/virtual-wan/packet-capture-site-to-site-powershell.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
![learn-build-service-prod[bot] avatar](https://avatars.githubusercontent.com/in/237442?v=4 "Published by a pub.dev verified publisher"){kind=small}
@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 #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team
I sent an email to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
