Blob Metadata Terraformlockid Was Empty May 2026

az storage blob metadata show \ --account-name <storage-account-name> \ --container-name <container-name> \ --name <path-to-tfstate> Then force-unlock:

terraform plan Terraform should now successfully acquire a fresh lock (you’ll see a new valid terraformlockid with a UUID value). Only if you are absolutely sure no Terraform process is using the state and the above fix doesn’t work, you can force-unlock. blob metadata terraformlockid was empty

If you manage Azure infrastructure with Terraform, you might have encountered a frustrating error when running terraform plan or terraform apply : Error: Error acquiring the state lock: blob metadata

If problems persist, check for network policies blocking blob metadata access or consider migrating to a new state file via terraform state push (advanced). When using the Azure backend (Azure Storage Account

Error: Error acquiring the state lock: blob metadata terraformlockid was empty This error prevents Terraform from executing because it cannot confirm whether the state file is currently locked by another process. Below, we’ll break down what this error means, why it happens, and how to fix it. Terraform uses state locking to prevent concurrent modifications to your infrastructure. When using the Azure backend (Azure Storage Account with a blob container), the lock is stored as metadata on the state blob (typically terraform.tfstate ). The metadata key is terraformlockid .

This error is alarming at first, but it’s usually safe to fix by simply removing the empty metadata. Once cleared, Terraform will resume normal locking behavior.

First, find the current (empty) lock ID. The error message may show it, or you can inspect metadata via Azure CLI: