-
Notifications
You must be signed in to change notification settings - Fork 21.8k
Update DDoS option for secure hub. #127524
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
Conversation
|
@cgoenka1 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 84b98fd: ✅ Validation status: passed
For more details, please refer to the build report. |
|
@duongau - Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
|
@duongau Could you review this proposed update to your article and enter Thanks! |
|
I sent an email to the content owner today. @MicrosoftDocs/public-repo-pr-review-team |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Updates documentation to reflect that Azure DDoS Protection is now supported for secure hubs when using Customer Provided IP option.
- Modified DDoS Protection support documentation for secure hubs
- Added clarification that DDoS support requires Customer Provided IP option
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
Learn Build status updates of commit 420b4d3: ✅ Validation status: passed
For more details, please refer to the build report. |
|
I sent an email to the content owner today. @MicrosoftDocs/public-repo-pr-review-team |
| |**Web Application Firewall on Application Gateway** |Supported in Virtual Network|Currently supported in spoke network| | ||
| |**Network Virtual Appliance**|Supported in Virtual Network|Currently supported in spoke network| | ||
| |**Azure DDoS Protection support**|Yes|No| | ||
| |**Azure DDoS Protection support**|Yes|Yes (With Customer Provided IP)| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| |**Azure DDoS Protection support**|Yes|Yes (With Customer Provided IP)| | |
| |**Azure DDoS Protection support**|Yes|Yes ([With customer provided public IP](../firewall/secured-hub-customer-public-ip.md))| |
|
Hi @v-dirichards and @v-ccolin, please update the PR with my suggested fix. We can go merge after that. #sign-off |
Updated the description for Azure DDoS Protection support to include details about customer-provided public IP address.
|
Learn Build status updates of commit 56666e0: ✅ Validation status: passed
For more details, please refer to the build report. |
|
#sign-off |
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @duongau |
|
Due to the upcoming conference, all merging and publishing is on hold until the morning of November 18, 2025. This PR is ready for merge on November 18, 2025. #label: "event-triaged-to-10AM" |
With the Customer Provided IP option, DDoS should be enabled for secure hub.