Skip to content

Update expressroute-howto-gateway-migration-portal.md #127448

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

kakazon
Copy link
Contributor

@kakazon kakazon commented Jul 31, 2025

Due to the new specifications for ExpressRoute, customers are no longer required to create public IP addresses on their end. Therefore, the relevant statement is no longer necessary and should be removed. I would appreciate it if you could kindly review and confirm.

----------the relevant statement ---------
Public IP address | Select Add new, provide a name for the new public IP, choose an availability zone, and select OK.

Reference:
https://learn.microsoft.com/en-us/azure/expressroute/expressroute-about-virtual-network-gateways#auto-assigned-public-ip

Due to the new specifications for ExpressRoute, customers are no longer required to create public IP addresses on their end. Therefore, the relevant statement is no longer necessary and should be removed. I would appreciate it if you could kindly review and confirm.

Reference:
https://learn.microsoft.com/en-us/azure/expressroute/expressroute-about-virtual-network-gateways#auto-assigned-public-ip
Copy link
Contributor

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

Copy link
Contributor

Learn Build status updates of commit d3f926a:

✅ Validation status: passed

File Status Preview URL Details
articles/expressroute/expressroute-howto-gateway-migration-portal.md ✅Succeeded

For more details, please refer to the build report.

@ttorble
Copy link
Contributor

ttorble commented Jul 31, 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 Jul 31, 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