How to successfully create a static web app using Terraform apply?

Question

How to successfully create a static web app using Terraform apply?

Steven Bruce 0

I have a terraform configuration file that defines a azurerm_static_web_app. When I apply this template, the resource is created and I can successfully deploy a SWA; however, the the console seems to get stuck and the process never seems to finish.

I end up with this. Yes, it's doing the same for a linux web app too...
User's image

Ultimately, I'm asking for ideas and suggestions as to what could be causing this and how to fix it.

Here is the terraform configuration:

resource "azurerm_static_web_app" "res-503" {
  location            = "westeurope"
  name                = "swa-${var.instance_name}"
  resource_group_name = azurerm_resource_group.res-0.name
  sku_size            = "Standard"
  sku_tier            = "Standard"
  depends_on = [
    azurerm_resource_group.res-0
  ]
}

Siva Nair 345 Reputation points Microsoft External Staff Moderator

2025-07-31T17:29:27.6066667+00:00
Hi Steven Bruce,

Lets check few points below:

Ensure that all your resources have appropriate dependencies defined. You've already used depends_on for the resource group; however, double-check if your static web app might have other dependencies that need to be explicitly defined.

Make sure you're using the latest version of Terraform and the AzureRM provider. Sometimes older versions can have bugs that are resolved in newer releases. You can upgrade using:
terraform init -upgrade

If you haven’t done so recently, it’s always good practice to initialize Terraform again to ensure that all plugins are up to date:
terraform init

Run the Terraform apply command with debug logging enabled. This can give you more insight into what might be causing the process to hang. You can enable debug logging by setting the TF_LOG environment variable:
export TF_LOG=DEBUG terraform apply

Log into the Azure Portal and check the resource creation status. Sometimes issues with resource provisioning can cause the Terraform CLI to hang while waiting for Azure to finish processing the request.

Occasionally, network connectivity issues between your local setup and Azure can cause hangs. Ensure that there are no network issues or firewalls blocking your requests.

By default, Terraform runs operations in parallel. If you're experiencing issues, you might want to limit this by using the -parallelism flag:
terraform apply -parallelism=1

Let me know if you need further assistance, happy to help you.

Steven Bruce 0

Thanks for your reply.

I've completed all the steps you've suggested but the same problem persists.

The debug logs may be useful, in that I can see what I think is the response from the status check:

{
  "id": "/subscriptions/.../resourceGroups/rg-demo/providers/Microsoft.Web/staticSites/swa-demo",
  "name": "swa-demo",
  "type": "Microsoft.Web/staticSites",
  "location": "West Europe",
  "properties": {
    "defaultHostname": "thankful-pebble-0fa8b2603.1.azurestaticapps.net",
    "repositoryUrl": null,
    "branch": null,
    "customDomains": [],
    "stableInboundIP": "20.50.153.39",
    "privateEndpointConnections": [],
    "stagingEnvironmentPolicy": "Enabled",
    "allowConfigFileUpdates": true,
    "contentDistributionEndpoint": "https://content-am2.infrastructure.1.azurestaticapps.net",
    "keyVaultReferenceIdentity": "SystemAssigned",
    "userProvidedFunctionApps": null,
    "linkedBackends": [],
    "provider": "None",
    "enterpriseGradeCdnStatus": "Disabled",
    "publicNetworkAccess": "Enabled",
    "databaseConnections": [],
    "trafficSplitting": {
      "environmentDistribution": {
        "default": 100
      }
    },
    "targetResourceGroupResourceId": null,
    "trialExpirationTimeUtc": null,
    "prettyNameStatus": null,
    "prettyName": null,
    "prettyNameHostname": null,
    "backendRegion": {
      "regionName": null,
      "status": null
    },
    "stagingEnvironmentRegion": null,
    "deploymentAuthPolicy": "DeploymentToken",
    "federatedIdentityTenantId": null,
    "federatedIdentityClientId": null,
    "federatedIdentitySubscriptionId": null,
    "deploymentStorageAccountResourceId": null,
    "deploymentStorageAccountReferenceIdentity": null,
    "networkConfigurationProperties": null
  },
  "sku": {
    "name": "Standard",
    "tier": "Standard"
  }
}

This response continues to repeat every few seconds, after the "Still creating..." log.

I can see from the Azure Portal the resource has been created.

For reference, I'm using version 4.38.0 of the hashicorp/azurerm provider.

Any idea what deems the resource created from the perspective of that JSON response?

Steven Bruce 0 Reputation points

2025-08-01T11:03:36.7866667+00:00

Upgrading the azurerm provider to 4.38.1 seems to have fixed the issue.

1 answer

Your answer

Siva Nair 345 Reputation points Microsoft External Staff Moderator

2025-07-31T17:29:27.6066667+00:00

Hi Steven Bruce,

Lets check few points below:

Ensure that all your resources have appropriate dependencies defined. You've already used depends_on for the resource group; however, double-check if your static web app might have other dependencies that need to be explicitly defined.

Make sure you're using the latest version of Terraform and the AzureRM provider. Sometimes older versions can have bugs that are resolved in newer releases. You can upgrade using:
terraform init -upgrade

If you haven’t done so recently, it’s always good practice to initialize Terraform again to ensure that all plugins are up to date:
terraform init

Run the Terraform apply command with debug logging enabled. This can give you more insight into what might be causing the process to hang. You can enable debug logging by setting the TF_LOG environment variable:
export TF_LOG=DEBUG terraform apply

Log into the Azure Portal and check the resource creation status. Sometimes issues with resource provisioning can cause the Terraform CLI to hang while waiting for Azure to finish processing the request.

Occasionally, network connectivity issues between your local setup and Azure can cause hangs. Ensure that there are no network issues or firewalls blocking your requests.

By default, Terraform runs operations in parallel. If you're experiencing issues, you might want to limit this by using the -parallelism flag:
terraform apply -parallelism=1

Let me know if you need further assistance, happy to help you.
Steven Bruce 0 Reputation points

2025-08-01T11:03:36.7866667+00:00

Upgrading the azurerm provider to 4.38.1 seems to have fixed the issue.

Answer 1

Hi Steven Bruce,

Great! That you got the issue resolved.

Upgrading to AzureRM provider version 4.38.1 likely a great step to improved the lifecycle handling for azurerm_static_web_app and similar resources.

Lock provider versions in your Terraform config to avoid unexpected behavior:

  terraform {
    required_providers {
      azurerm = {
        source  = "hashicorp/azurerm"
        version = ">= 4.38.1"
      }
    }
  }

Check the changelog for provider updates: https://github.com/hashicorp/terraform-provider-azurerm/blob/main/CHANGELOG.md
Test upgrades in a staging environment if possible, especially for production-critical infrastructure.

Thanks!

Share via

How to successfully create a static web app using Terraform apply?

1 answer

Your answer