为何无法通过Terraform创建Azure VM？VNet部署超时故障求助

Hey there, sorry to hear you're stuck with this VNet deployment timeout issue—especially since things ran smoothly before and the Azure Portal works without a hitch. Let's walk through some targeted fixes and checks to get to the bottom of this:

1. Audit Your VNet Configuration for Hidden Issues #

Sometimes subtle config details can trigger delays that the Portal handles more gracefully:

• Double-check your CIDR blocks: Are you using a range that overlaps with Azure reserved IP spaces (like 169.254.0.0/16) or existing networks in your subscription? Even a tiny overlap can cause silent deployment hangs.
• Are you enabling resource-heavy features like DDoS Protection Standard or Service Endpoints? These can extend deployment time beyond Terraform's default timeout. Try adding a custom timeout to your azurerm_virtual_network resource:

resource "azurerm_virtual_network" "your_vnet" {
  name                = "your-vnet-name"
  address_space       = ["10.1.0.0/16"]
  location            = azurerm_resource_group.your_rg.location
  resource_group_name = azurerm_resource_group.your_rg.name

  timeouts {
    create = "30m" # Extend timeout to accommodate slow-feature provisioning
  }
}

2. Verify Authentication & Permissions for Terraform #

Your Portal account works, but your Terraform setup might have permission gaps:

• If using a service principal, confirm it has the Network Contributor role assigned at the resource group or subscription level. Granular permissions sometimes miss hidden VNet-related actions that the Portal's built-in roles cover.
• If using Azure CLI auth, run az account show to ensure you're logged into the correct subscription. Accidentally switching subscriptions can lead to confusing timeouts when resources try to provision in the wrong tenant/region.

3. Dig Into Azure's Activity Log for Real Error Details #

Terraform's timeout message is generic—Azure's Activity Log will give you the actual root cause. Head to the Azure Portal:

1. Navigate to your target resource group
2. Select Activity log from the left menu
3. Filter for failed deployments around the time your Terraform run timed out
   Look for specific error codes (e.g., InvalidTemplateDeployment, QuotaExceeded)—these will point you directly to issues like subnet conflicts or unnoticeable quota limits.

4. Check Network Connectivity Between Terraform and Azure API #

Unstable network links between your Terraform machine and Azure's management API can cause partial deployments that hang until timeout:

• Use Azure Network Watcher's connectivity check tool to test if your machine can reach Azure's API endpoints reliably.
• Try running your Terraform apply from a different network (like a mobile hotspot) to rule out local firewall/proxy issues blocking API traffic.

One final tip: Enable debug logging for Terraform with TF_LOG=DEBUG terraform apply—this will show you every API call made, so you can see exactly where the deployment gets stuck before timing out.

内容的提问来源于stack exchange，提问作者zapatilla