Update routing intent prerequisites in documentation

[MikeWedderburn-Clarke]

Clarified conditions for enabling routing intent in Azure Firewall and added details about User Defined Routes in Spokes. Many customers have interpreted the original statement to say that they cannot have UDRs in Spokes.

[prmerger-automator]

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

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit ad64484:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/virtual-wan/how-to-routing-policies.md	✅Succeeded

For more details, please refer to the build report.

[ttorble]

@wtnlee

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

[wtnlee]

@ttorble and @MikeWedderburn-Clarke

Please make the following changes to the PR:

• Add a hyperlink for User-Defined Routing to the UDR documentation on VNET team (https://learn.microsoft.com/en-us/azure/virtual-network/virtual-networks-udr-overview#user-defined-routes)

• Replace "enabled on the VWAN Virtual Hub" with "enabled on the Virtual WAN hub" for consistent branding and terminology

• However it is supported to have User Defined Routes (UDR) in the Spokes connected to the Hub, as long as "Propagate gateway routes" is set to "Yes" for that custom Route Table. For more information, see troubleshooting data path. --> please re-word to:

However, you can associate User Defined Routes (UDR) to spoke Virtual Networks connected to the Virtual WAN hub. To ensure the spoke Virtual Network learns routes from Virtual WAN, ensure "Propagate gateway routes' is set to "Yes" for the user-defined route table. For more information, see troubleshooting data path.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[MikeWedderburn-Clarke]

Requested changes have been made.

[learn-build-service-prod]

Learn Build status updates of commit 024a085:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
articles/virtual-wan/how-to-routing-policies.md	⚠️Warning		Details

articles/virtual-wan/how-to-routing-policies.md

• Line 170, Column 279: [Warning: file-not-found - See documentation] Invalid file link: 'virtual-networks-udr-overview.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.

[learn-build-service-prod]

Learn Build status updates of commit 0177a9d:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/virtual-wan/how-to-routing-policies.md	✅Succeeded

For more details, please refer to the build report.

[MikeWedderburn-Clarke]

Tagging @aparnabhat-msftgh who helped with troubleshooting the original customer issue and also with writing the proposed updates. Thanks Aparna!

[v-dirichards]

@wtnlee Could you review this proposed update to your article and enter #sign-off in a comment if it's ready to merge?

Thanks!

[aparnabhatms]

Tagging @aparnabhat-msftgh who helped with troubleshooting the original customer issue and also with writing the proposed updates. Thanks Aparna!

thanks @MikeWedderburn-Clarke. :)