Someone (or a script) may have edited the blob metadata via Azure Portal, AzCopy, or the Azure CLI, accidentally clearing the lock ID value while leaving the key present.
If Terraform falsely reports a lock and the metadata is empty, you may need to manipulate the local .terraform.tfstate.lock.info file (if it exists locally) or reset the state environment. blob metadata terraformlockid was empty
Before making any changes, ensure no other team member or CI/CD pipeline is running Terraform with that state file. Someone (or a script) may have edited the
An administrator manually cleared the metadata key to "force unlock" the state after a previous stuck operation. An administrator manually cleared the metadata key to
Terraform utilizes a state locking mechanism to prevent concurrent operations (e.g., two users running terraform apply simultaneously) which could corrupt the state file. When a lock is acquired, Terraform writes a unique identifier to the storage backend.