Skip to content

Conversation

cgoenka1
Copy link
Contributor

@cgoenka1 cgoenka1 commented Oct 8, 2025

Removed the capability which was contradicting.

Removed the capability which was contradicting.
@prmerger-automator
Copy link
Contributor

@cgoenka1 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit cef89ee:

✅ Validation status: passed

File Status Preview URL Details
articles/firewall/secured-hub-customer-public-ip.md ✅Succeeded

For more details, please refer to the build report.

@ttorble ttorble requested a review from Copilot October 8, 2025 15:01
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR resolves a contradiction in the documentation about customer-provided public IP addresses for Azure Firewall in Virtual WAN secured hubs. The changes remove conflicting information and improve clarity about deployment availability.

  • Removes contradictory statement about new deployment limitations
  • Clarifies that the feature is available for both new and existing deployments
  • Improves grammar and readability in the feature description

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@ttorble
Copy link
Contributor

ttorble commented Oct 8, 2025

@duongau

Can you review the proposed changes?

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

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Oct 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants