CSS-Networking Update virtual-networks-udr-overview.md #127980
Conversation
I worked on a case there wasn't documentation on these other default routes therefore I added more default routes. I also added a sentence at the end of the "None" paragraph to explain that changing the default 0.0.0.0/0 "none" next hop will be removed.
prmerger-automator
bot
requested review from
AbdullahBell,
asudbring and
cherylmc
|
@carinaleonMS : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 2821e66: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
This PR enhances the documentation for Azure virtual network default routes by adding four previously undocumented default system routes and clarifying the behavior when the default route is modified.
- Added four new default routes: 157.59.0.0/16, 127.0.0.0/8, 104.147.0.0/16, and 104.146.0.0/17
- Clarified that setting a default route (0.0.0.0/0) with next hop type "Virtual Network Gateway" removes default system routes with next hop type "None"
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| * **100.64.0.0/10**: Reserved in RFC 6598. | ||
|
|
||
| If you assign any of the previous address ranges within the address space of a virtual network, Azure automatically changes the next hop type for the route from **None** to **Virtual network**. If you assign an address range to the address space of a virtual network that includes, but isn't the same as, one of the four reserved address prefixes, Azure removes the route for the prefix and adds a route for the address prefix you added, with **Virtual network** as the next hop type. | ||
| If you assign any of the previous address ranges within the address space of a virtual network, Azure automatically changes the next hop type for the route from **None** to **Virtual network**. If you assign an address range to the address space of a virtual network that includes, but isn't the same as, one of the four reserved address prefixes, Azure removes the route for the prefix and adds a route for the address prefix you added, with **Virtual network** as the next hop type. Default Route (0.0.0.0/0) with Next Hop Type = Virtual Network Gateway will cause these Default System Routes with Next Hop Type = None to be removed. |
There was a problem hiding this comment.
The reference to 'four reserved address prefixes' is now inaccurate since eight default routes with next hop type 'None' are now documented (the original four RFC ranges plus the four newly added routes). This reference should be updated to accurately reflect the total number of reserved address prefixes or be rephrased to avoid a specific count.
| If you assign any of the previous address ranges within the address space of a virtual network, Azure automatically changes the next hop type for the route from **None** to **Virtual network**. If you assign an address range to the address space of a virtual network that includes, but isn't the same as, one of the four reserved address prefixes, Azure removes the route for the prefix and adds a route for the address prefix you added, with **Virtual network** as the next hop type. Default Route (0.0.0.0/0) with Next Hop Type = Virtual Network Gateway will cause these Default System Routes with Next Hop Type = None to be removed. | |
| If you assign any of the previous address ranges within the address space of a virtual network, Azure automatically changes the next hop type for the route from **None** to **Virtual network**. If you assign an address range to the address space of a virtual network that includes, but isn't the same as, one of the reserved address prefixes listed above, Azure removes the route for the prefix and adds a route for the address prefix you added, with **Virtual network** as the next hop type. Default Route (0.0.0.0/0) with Next Hop Type = Virtual Network Gateway will cause these Default System Routes with Next Hop Type = None to be removed. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
3 participants
I worked on a case there wasn't documentation on these other default routes therefore I added more default routes. I also added a sentence at the end of the "None" paragraph to explain that changing the default 0.0.0.0/0 "none" next hop will be removed.