-
Notifications
You must be signed in to change notification settings - Fork 21.8k
Added additional information about the order of precendence for outbo… #127925
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
base: main
Are you sure you want to change the base?
Conversation
…und rules where a VM is added to more than one backend pool.
|
@simonpainter : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
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
This PR updates the Azure Load Balancer documentation to clarify the order of precedence for outbound connections when a VM belongs to multiple backend pools with different outbound rules and frontend IP configurations.
- Adds documentation explaining that the first backend pool a VM is added to determines which outbound rule is used
- Clarifies that VMs in the same backend pools can have different outbound IPs based on the order of pool addition
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Updated to US English spelling. Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
Learn Build status updates of commit 4137566: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 0f64606: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
This pull request updates the Azure Load Balancer documentation to clarify outbound connection behavior when a VM is part of multiple backend pools with different outbound rules and frontend IP configurations.
Documentation clarification: