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 inConfigure a Cisco Multicloud Defense service VNet and attach it to an Azure Virtual WAN vHub with the required route tables.
You can create a service VPC with VWAN attachment using the Easy Setup wizard when you secure your account. For more information, refer to Centralized Model: Add a VPC or VNet.
Follow this procedure to create a service VPC and attach a VWAN.
From the Multicloud Defense Controller, navigate to Infrastructure > Gateways > VPCs/VNets.
Click Create Service VPC/VNet to create a Service VPC.
Enter a Name.
From the Region drop-down list, select a region.
From the CSP Account drop-down list, select an account.
Enter details for CIDR Block.
From the Availability Zones drop-down list, select a zone.
From the Resource Group drop-down list, select a resource group.
Check the Use NAT Gateway check box to direct traffic through the NAT gateway.
In the vWAN Attachment section, set the toggle to Enabled.
From the vHub drop-down list, select a hub.
From the Associate Route Table drop-down list, select a route table to associate.
From the Propagate Route Tables drop-down list, select route tables to propagate.
Click Save.
NoteIf you delete a service VPC in Multicloud Defense, the vHub connection between the VWAN and the Azure service VPC is also deleted.
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.