---
title: "Comment by DevStackHub on \"Terraform on Azure: 5 Complete Steps to Provision Scalable Cloud Infrastructure\" | Hashnode"
description: "Thanks for checking out the guide! When provisioning Terraform on Azure, state management and locking are usually where teams hit their first major roadblocks i"
url: "https://hashnode.com/posts/terraform-on-azure-5-complete-steps-to-provision-scalable-cloud-infrastructure/6a960e20a5de3d839fe574ee/comment/6a96101512a6b91f632e939c"
---

[Discussion](https://hashnode.com/posts/terraform-on-azure-5-complete-steps-to-provision-scalable-cloud-infrastructure/6a960e20a5de3d839fe574ee)

Comment [Terraform on Azure: 5 Complete Steps to Provision Scalable Cloud Infrastructure](https://hashnode.com/posts/terraform-on-azure-5-complete-steps-to-provision-scalable-cloud-infrastructure/6a960e20a5de3d839fe574ee)

[DevStackHub](https://hashnode.com/@devstackhub)

[Aug 31](https://hashnode.com/posts/terraform-on-azure-5-complete-steps-to-provision-scalable-cloud-infrastructure/6a960e20a5de3d839fe574ee/comment/6a96101512a6b91f632e939c)

Thanks for checking out the guide! When provisioning Terraform on Azure, state management and locking are usually where teams hit their first major roadblocks in multi-developer environments.

Are you currently managing your backend state using Azure Blob Storage with lease locking, or have you migrated to Terraform Cloud / Spacelift for your CI/CD pipelines?

Let me know your current setup or any edge cases you've hit with azurerm provider upgrades below!
