Getting polling after CreateOrUpdate: `result.Status` was nil/empty - `op.Status` was "Requested" / `op.Properties.ProvisioningState` was "" when creating FHIR service using terraform.

Question

Getting polling after CreateOrUpdate: `result.Status` was nil/empty - `op.Status` was "Requested" / `op.Properties.ProvisioningState` was "" when creating FHIR service using terraform.

Devanshu Soni 0

Getting again and again polling after CreateOrUpdate: result.Status was nil/empty - op.Status was "Requested" / op.Properties.ProvisioningState was "". I am creating FHIR service using terraform.

0 comments

2 answers

Your answer

Answer 1

When creating a FHIR service using Terraform, encountering a situation where result.Status is nil or empty and op.Status is "Requested" with op.Properties.ProvisioningState being empty can indicate that the provisioning operation is still in progress or has not yet completed. This is common in asynchronous operations where the status may not be immediately available after the request is made.

To troubleshoot this issue:

Check the Azure Portal: Look at the Azure portal for the FHIR service to see if there are any errors or if the service is still being provisioned.
Increase Polling Interval: If you're polling for the status too frequently, consider increasing the interval to allow more time for the operation to complete.
Review Terraform Logs: Check the Terraform logs for any additional error messages or warnings that might give more context about the operation's status.
Provisioning State Values: Familiarize yourself with the possible values of ProvisioningState, which can include states like 'Updating', 'Succeeded', 'Failed', and 'Canceled'. If the state remains empty for an extended period, it may indicate a problem with the provisioning process.

If the issue persists, consider reaching out to Azure support for further assistance.

Answer 2

Hello Devanshu Soni,

Azure Health Data Services FHIR ARM API does not consistently return a terminal async-operation state, causing Terraform polling to never complete.

Please run below script:

az healthcareapis service show \

--resource-group <rg> \

--workspace-name <workspace> \

--name <fhir-name>

If it shows provisioningState: Succeeded, then end point reachable.

1. Upgrade AzureRM provider (recommended)

Some fixes landed in newer versions.

provider "azurerm" {
  features {}
}

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

If you’re already on latest → move on.

2. Force timeouts (most reliable workaround)

resource "azurerm_healthcare_fhir_service" "fhir" {
  name                = var.name
  workspace_id        = azurerm_healthcare_workspace.ws.id
  location            = var.location
  resource_group_name = var.rg

  kind = "fhir-R4"

  authentication {
    authority = "https://login.microsoftonline.com/${data.azurerm_client_config.current.tenant_id}"
    audience  = "https://${var.name}.azurehealthcareapis.com"
  }

  timeouts {
    create = "90m"
    update = "90m"
    delete = "90m"
  }
}

This doesn’t fix the root cause but prevents premature failure.

3. Use ignore_changes on non-critical fields

Sometimes Terraform re-enters polling because Azure mutates fields post-creation.

lifecycle {
  ignore_changes = [
    tags,
    identity,
  ]
}

terraform apply

wait for Azure portal to show Succeeded

terraform import azurerm_healthcare_fhir_service.fhir <resource-id>

Please accept as answer and do a Thumbs-up to upvote this response if you are satisfied with the community help. Your upvote will be beneficial for the community users facing similar issues.

User's image

Praveen Kumar Gudipudi 2,295 Reputation points Microsoft External Staff Moderator

2026-02-05T05:41:54.26+00:00

Hello Devanshu Soni,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.