Skip to content

Update public-ip-address-prefix.md #127391

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 3 commits into
base: main
Choose a base branch
from

Conversation

willstMSFT
Copy link
Contributor

I added a line to the VM, but in a couple of cases we have seen customers demand that any access to their network has to be with public IP space. To facilitate this in Azure we create the Public IP prefix, add it to the VNET, associate it with the Subnet, Assign it to the VM. BGP Routing will then send the prefix to the gateway and allow internal routing of the range.

I added a line to the VM, but in a couple of cases we have seen customers demand that any access to their network has to be with public IP space.  To facilitate this in Azure we create the Public IP prefix, add it to the VNET, associate it with the Subnet, Assign it to the VM.  BGP Routing will then send the prefix to the gateway and allow internal routing of the range.
Copy link
Contributor

@willstMSFT : 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 adfe00f:

⚠️ Validation status: warnings

File Status Preview URL Details
articles/virtual-network/ip-services/public-ip-address-prefix.md ⚠️Warning Details

articles/virtual-network/ip-services/public-ip-address-prefix.md

  • Line 52, Column 981: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/azure/virtual-network/how-to-multiple-prefixes-subnet?tabs=powershell' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
  • Line 52, Column 981: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/azure/virtual-network/how-to-multiple-prefixes-subnet?tabs=powershell' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@ttorble
Copy link
Contributor

ttorble commented Jul 17, 2025

@mbender-ms

Can you review the proposed changes? Note that https://learn.microsoft.com/en-us will need to be removed from the link to resolve the warning (and make the link relative), and link text needs to be added. Thanks.

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 17, 2025
Copy link
Contributor

@mbender-ms mbender-ms left a comment

Choose a reason for hiding this comment

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

Thanks for the update @willstMSFT!

@willstMSFT
Copy link
Contributor Author

willstMSFT commented Jul 17, 2025 via email

Copy link
Contributor

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @mbender-ms

Copy link
Contributor

@mbender-ms mbender-ms left a comment

Choose a reason for hiding this comment

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

Hi @willstMSFT one small change is needed before signoff. Thanks!

@mbender-ms
Copy link
Contributor

#please-close

@mbender-ms
Copy link
Contributor

#please-open

@prmerger-automator prmerger-automator bot reopened this Jul 18, 2025
Copy link
Contributor

Learn Build status updates of commit adfe00f:

⚠️ Validation status: warnings

File Status Preview URL Details
articles/virtual-network/ip-services/public-ip-address-prefix.md ⚠️Warning Details

articles/virtual-network/ip-services/public-ip-address-prefix.md

  • Line 52, Column 981: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/azure/virtual-network/how-to-multiple-prefixes-subnet?tabs=powershell' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
  • Line 52, Column 981: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/azure/virtual-network/how-to-multiple-prefixes-subnet?tabs=powershell' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

Copy link
Contributor

Learn Build status updates of commit 00d2185:

⚠️ Validation status: warnings

File Status Preview URL Details
articles/virtual-network/ip-services/public-ip-address-prefix.md ⚠️Warning Details

articles/virtual-network/ip-services/public-ip-address-prefix.md

  • Line 52, Column 938: [Warning: file-not-found - See documentation] Invalid file link: './how-to-multiple-prefixes-subnet.md'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

Copy link
Contributor

@mbender-ms mbender-ms left a comment

Choose a reason for hiding this comment

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

I had the wrong syntax for the URL. This should work.

Copy link
Contributor

Learn Build status updates of commit 49b5960:

⚠️ Validation status: warnings

File Status Preview URL Details
articles/virtual-network/ip-services/public-ip-address-prefix.md ⚠️Warning Details

articles/virtual-network/ip-services/public-ip-address-prefix.md

  • Line 52, Column 938: [Warning: file-not-found - See documentation] Invalid file link: './how-to-multiple-prefixes-subnet'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

Copy link
Contributor

@mbender-ms mbender-ms left a comment

Choose a reason for hiding this comment

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

I think this is the last one.

@@ -49,7 +49,7 @@ You can associate the following resources to a static public IP address from a p

|Resource|Scenario|Steps|
|---|---|---|
|Virtual machines| Associating public IPs from a prefix to your virtual machines in Azure reduces management overhead when adding IP addresses to an allowlist in the firewall. You can add an entire prefix with a single firewall rule. As you scale with virtual machines in Azure, you can associate IPs from the same prefix saving cost, time, and management overhead.| To associate IPs from a prefix to your virtual machine:</br> 1. [Create a prefix.](manage-public-ip-address-prefix.md)</br> 2. [Create an IP from the prefix.](manage-public-ip-address-prefix.md)</br> 3. [Associate the IP to your virtual machine's network interface.](./virtual-network-network-interface-addresses.md#add-ip-addresses)</br> You can also [associate the IPs to a Virtual Machine Scale Set](https://azure.microsoft.com/resources/templates/vmss-with-public-ip-prefix/).
|Virtual machines| Associating public IPs from a prefix to your virtual machines in Azure reduces management overhead when adding IP addresses to an allowlist in the firewall. You can add an entire prefix with a single firewall rule. As you scale with virtual machines in Azure, you can associate IPs from the same prefix saving cost, time, and management overhead.| To associate IPs from a prefix to your virtual machine:</br> 1. [Create a prefix.](manage-public-ip-address-prefix.md)</br> 2. [Create an IP from the prefix.](manage-public-ip-address-prefix.md)</br> 3. [Associate the IP to your virtual machine's network interface.](./virtual-network-network-interface-addresses.md#add-ip-addresses)</br> You can also [associate the IPs to a Virtual Machine Scale Set](https://azure.microsoft.com/resources/templates/vmss-with-public-ip-prefix/). In the event you'll need the public IP address to be available to route internally, the [Public IP Prefix can be added to the VNET](./how-to-multiple-prefixes-subnet), and then assigned to the Virtual Machine as an IP address from a subnet that the VM participates in.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
|Virtual machines| Associating public IPs from a prefix to your virtual machines in Azure reduces management overhead when adding IP addresses to an allowlist in the firewall. You can add an entire prefix with a single firewall rule. As you scale with virtual machines in Azure, you can associate IPs from the same prefix saving cost, time, and management overhead.| To associate IPs from a prefix to your virtual machine:</br> 1. [Create a prefix.](manage-public-ip-address-prefix.md)</br> 2. [Create an IP from the prefix.](manage-public-ip-address-prefix.md)</br> 3. [Associate the IP to your virtual machine's network interface.](./virtual-network-network-interface-addresses.md#add-ip-addresses)</br> You can also [associate the IPs to a Virtual Machine Scale Set](https://azure.microsoft.com/resources/templates/vmss-with-public-ip-prefix/). In the event you'll need the public IP address to be available to route internally, the [Public IP Prefix can be added to the VNET](./how-to-multiple-prefixes-subnet), and then assigned to the Virtual Machine as an IP address from a subnet that the VM participates in.
|Virtual machines| Associating public IPs from a prefix to your virtual machines in Azure reduces management overhead when adding IP addresses to an allowlist in the firewall. You can add an entire prefix with a single firewall rule. As you scale with virtual machines in Azure, you can associate IPs from the same prefix saving cost, time, and management overhead.| To associate IPs from a prefix to your virtual machine:</br> 1. [Create a prefix.](manage-public-ip-address-prefix.md)</br> 2. [Create an IP from the prefix.](manage-public-ip-address-prefix.md)</br> 3. [Associate the IP to your virtual machine's network interface.](./virtual-network-network-interface-addresses.md#add-ip-addresses)</br> You can also [associate the IPs to a Virtual Machine Scale Set](https://azure.microsoft.com/resources/templates/vmss-with-public-ip-prefix/). In the event you'll need the public IP address to be available to route internally, the [Public IP Prefix can be added to the VNET](../how-to-multiple-prefixes-subnet.md), and then assigned to the Virtual Machine as an IP address from a subnet that the VM participates in.

Copy link
Contributor

Choose a reason for hiding this comment

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

@willstMSFT - Can you respond to the requested changes or let us know if you would like us to commit them?

@mbender-ms - 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

@willstMSFT
Copy link
Contributor Author

willstMSFT commented Jul 22, 2025 via email

Copy link
Contributor

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @mbender-ms

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.

4 participants