Azure routing tables are not created if the VNet and subnets already exist #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

DoctorBizzle opened this issue Jul 26, 2020 · 0 comments

DoctorBizzle commented Jul 26, 2020

Scenario:

Azure
Firewall VNet and 4 x subnets already created in rg1
vFTD deployed to Firewall VNet and rg2

Issue:

no routing tables are created for the FTD subnets

Why preconfigure the vnet and rg1?

The FTD deployment will not work if there are any objects in the target resource group
Some people use subnet segregation rather that hub and spoke / multiple vnets.
Some Azure services are unable to traverse VNets, e.g. Azure Bastion.
VNet & subnet can be provisioned by Terraform in advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment