求助：Terraform无法在Azure创建虚拟网络问题

Hey there, sorry to hear you're stuck on creating Azure virtual networks—let's dig into this together! You've already checked the common basics (name tweaks, IP ranges, fresh resource groups, Terraform workspace cleanup), so let's cover some less obvious angles.

1. Subscription-Level Quota Limits #

Azure enforces per-subscription quotas for resources like virtual networks, network interfaces, or public IPs. Even with a new resource group, your subscription might be hitting a cap.

• To check your quota status:
  1. Open the Azure Portal, search for Subscriptions
  2. Select your subscription, then navigate to Usage + quotas under the Settings menu
  3. Filter for "Virtual Networks" or related resources (like "Virtual Network Gateways" if you're adding gateways to your VNet)
• If you're at the limit, you can request a quota increase directly through the portal.

2. Hidden Terraform Configuration Issues #

Cleaning the workspace is a good first step, but your config might have subtle bugs you missed:

• Double-check if you're accidentally referencing existing locked resources (like a route table or NSG) that don't have proper permissions.
• Verify your AzureRM provider version: Outdated providers can clash with newer Azure API versions. Try updating your provider block:

  provider "azurerm" {
    features {}
    version = ">= 3.0.0" # Use a recent stable release
  }
  

• Enable Terraform debug logging to get granular error details:

  export TF_LOG=DEBUG
  terraform apply
  

  Look for specific API error codes (like QuotaExceeded or InvalidTemplateDeployment)—these will point you straight to the root issue.

3. Permission & Policy Restrictions #

Even with subscription access, your account might lack specific permissions, or Azure Policies could be blocking creation:

• Ensure your user/service principal has Network Contributor or Contributor roles assigned at the subscription or resource group level.
• Check Azure Policy assignments: Go to the Policy section in the Azure Portal, review assigned policies for your subscription/resource group. Look for policies that restrict IP ranges, enforce mandatory tags, or block VNet creation in certain regions.

4. Regional Resource Shortages #

Occasionally, specific regions might have temporary resource shortages that prevent new VNet deployments. Test creating a VNet in a different region to rule this out.

5. Azure Session/Backend Glitches #

Sometimes Azure's backend cache or your local session can get corrupted:

• Log out and back into the Azure Portal/CLI
• Run az account clear followed by az login to refresh your CLI session
• For Terraform, run terraform init -reconfigure to reset the backend connection

If you can share the exact error message (including any error codes) you're receiving, that would help narrow this down even faster!

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