Merge pull request #295044 from duongau/patch-7

Azure Firewall - Multi hub and spoke (add note to clarify the address spaces in the route table)

Author: prmerger-automator[bot]

articles/firewall/firewall-multi-hub-spoke.md

@@ -30,6 +30,9 @@ Since this is a static routing architecture, the shortest path to another hub ca
 
 Each local firewall needs to know how to reach the other remote spokes, so you must create UDRs in the firewall subnets. To do this, you first need to create a default route of any type, which then allows you to create more specific routes to the other spokes. For example, the following screenshots show the route table for the two hub VNets:
 
+> [!NOTE]
+> The address prefix in the hub virtual route table should encompass the two spoke virtual network address spaces.
+
 **Hub-01 route table**
 :::image type="content" source="media/firewall-multi-hub-spoke/hub-01-route-table.png" alt-text="Screenshot showing the route table for Hub-01.":::