I personally prefer not to do this but some teams do and it's a good way to collaborate and a cheap(est) alternative to using the Terraform Cloud with the intention of allowing a team to build cloud services.

I've only used one storage account per resource group assigned to a Terraform project, I haven't tested storing more than one Terraform project state on the same storage account but different container. I'd presume it's doable.

Terraform Backend

It starts with the terraform block:

terraform {

}

This blocks allows the configuration of Terraform's backend among many others not covered here:

backend. Specifically refers to the Terraform State. The state is the persistent data keeping track the resources Terraform manages. Note: The default backend is always local.

Some of the Cloud supported backends:

• AWS S3

• Azure Storage Account (blob storage)

• Google Cloud Storage

I didn't change anything on the main.tf where the logic for the password generator is. I added the backend.tf file:

terraform {
  backend "azurerm" {
    resource_group_name  = "RGTFSTAUPWD"       # Resource group of the storage account
    storage_account_name = "saauetfpwd"      # Name of the storage account
    container_name       = "terraform-state"       # Name of the container
    key                  = "terraform.tfstate"     # Name of the state file
  }
}

As a good practice enable versioning on the the blob as this will allow to roll back in case required or review the previews states (passwords):

Running the password generator:

On the command line:

Looking at the versions on the Azure portal

The 10 character password:

The 255 password:

Pre-requisites:

• As a very minimum you'd require an Azure account (obviously)

• Being logged into the Azure subscription when running this code