Modify an existing Cisco Multicloud Defense service VNet to connect it to an Azure Virtual WAN vHub and manage route propagation.
Cisco Multicloud Defense User Guide
Is this content helpful?
Thank you for your feedback. Your response has been recorded.
AI responses are currently only available to logged in users. Log in
Only ask questions about this document. To ask questions about this product as a whole, go to Technical Documentation .
Suggestions
Sorry, we couldn't generate a response for this query.
Cisco Multicloud Defense User Guide
Updated: July 8, 2026
Want to summarize with AI?
Log inModify an existing Cisco Multicloud Defense service VNet to connect it to an Azure Virtual WAN vHub and manage route propagation.
From the Multicloud Defense Controller, navigate to Infrastructure > Gateways > VPCs/VNets.
Choose a Service VPC that you want to edit, from the list.
Click Edit.
In the vWAN Attachment section, set the toggle to Enabled.
From the vHub drop-down list, choose a hub.
From the Associated Route Table drop-down list, choose a route table to associate.
From the Propagate Route Tables drop-down list, choose route tables to propagate.
To propagate all spoke CIDRs to the vHub, set the toggle to Always.
NoteTo add multiple spoke VPCs to the route tables, use the list builder to move the spoke VPCs from the Available section to the Selected section. Moving the VPC to the Selected section ensures that the VPC is added.
Click Save.
The Service VPC connects to a VWAN containing a vHub and spoke VPCs in Azure. Note that any changes made to route tables are also updated in Azure.
Need help?
(Requires a Cisco Service Contract)
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.