Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

β“πŸ‘‚ Question/Feedback - VPN Gateway missing recs for resource lock and maintenance configurations #30

Open
judyer28 opened this issue Apr 11, 2024 · 3 comments
Assignees
Labels
Area: Resource Guidance πŸ“ Improvements or additions to documentation Enhancement πŸ†• New feature or request

Comments

@judyer28
Copy link
Contributor

Question/Feedback

Under network/virtualNetworkGateways there are a couple recommendations that apply to ExpressRoute that should also be applied to VPN Gateways.

Possible Answers/Solutions?

I suggest creating similar recommendations for VPN Gateway for the following 2:

https://azure.github.io/Azure-Proactive-Resiliency-Library-v2/azure-resources/Network/virtualNetworkGateways/#configure-an-azure-resource-lock-for-expressroute-gateway-to-prevent-accidental-deletion

https://azure.github.io/Azure-Proactive-Resiliency-Library-v2/azure-resources/Network/virtualNetworkGateways/#configure-customer-controlled-expressroute-gateway-maintenance

@ejhenry ejhenry added Area: Resource Guidance πŸ“ Improvements or additions to documentation Enhancement πŸ†• New feature or request labels Apr 15, 2024
@ejhenry
Copy link
Contributor

ejhenry commented Apr 15, 2024

cc @JefferyMitchell

@JefferyMitchell
Copy link
Contributor

@fguerri Could you comment on thoughts for these additions'.

@ejhenry
Copy link
Contributor

ejhenry commented Jun 20, 2024

@fguerri any update to share on this?

cc @JefferyMitchell

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Resource Guidance πŸ“ Improvements or additions to documentation Enhancement πŸ†• New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants