-
Notifications
You must be signed in to change notification settings - Fork 517
DeploymentFlowVWAN
github-actions edited this page Mar 9, 2022
·
5 revisions
This deploys a hub and spoke network topology with Azure Virtual WAN to the Azure Landing Zone foundation. This connectivity approach uses Virtual WAN (VWAN) to replace hubs as a managed service. Spoke virtual networks peer with the VWAN virtual hub.
Please review and run the Deployment Flow before running these modules.
Modules in this reference implementation must be deployed in the following order to ensure consistency across the environment:
Order | Module | Description | Prerequisites | Module Documentation |
---|---|---|---|---|
1 | Virtual WAN Connectivity | Deploys the Virtual WAN network topology and its components according to the Azure Landing Zone conceptual architecture. | Management Groups, Subscription for vWAN connectivity. | infra-as-code/bicep/modules/vwanConnectivity |
2 | VNet Peering with vWAN | Connect a virtual network to a Virtual WAN hub. | Management Groups, Subscription for spoke VNet, vWAN Connectivity Module | Coming soon |
If you discover any documentation bugs or would like to request new content, please raise them as an issue on the repo.
Contributions to this wiki are done through the main repo under docs/wiki.
- Wiki Home
- Deployment Flow
- Consumer Guide
- How Does ALZ-Bicep Implement Azure Policies?
- How Does ALZ-Bicep Implement resilient deployments across availability zones?
- Contributing
- Telemetry Tracking Using Customer Usage Attribution (PID)
- Azure Container Registry Deployment - Private Bicep Registry
- Sample Pipelines
- Code tours