How to Import an Azure Load Balancer Probe into Terraform

Import Azure Load Balancer Probe with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Azure Load Balancer resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Azure Load Balancer Probe to managed Terraform.

terraback scan all azure --subscription-id YOUR_ID

terraback azure import --method bulk

The Terraform import block

Terraback emits a Terraform 1.5+ import block like the one below. Because the block lives in your configuration, the import is reviewable in a pull request and repeatable across environments.

import {
  to = azurerm_lb_probe.https
  id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.Network/loadBalancers/prod-lb/probes/https-probe"
}

Example azurerm_lb_probe configuration

Here is a realistic Azure Load Balancer Probe block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.

resource "azurerm_lb_probe" "https" {
  name                = "https-probe"
  loadbalancer_id     = azurerm_lb.prod.id
  protocol            = "Http"
  port                = 443
  request_path        = "/health"
  interval_in_seconds = 15
  number_of_probes    = 2
}

Gotchas when importing a Azure Load Balancer Probe

• The probe is a child of the load balancer (.../loadBalancers/<lb>/probes/<name>) and imports separately from azurerm_lb.
• request_path is required when protocol is Http or Https and must be omitted when protocol is Tcp.
• Load balancer rules reference the probe by probe_id; import the rules too or they will appear unmanaged.
• loadbalancer_id is immutable; a change recreates the probe.

Doing it manually with terraform import

The native approach is to write the azurerm_lb_probe block by hand, then run terraform import azurerm_lb_probe.example <import-id> for every resource, one at a time. That works for a handful of resources, but it does not scale: you author all the HCL yourself and repeat the command for each item. Terraback generates the HCL and the import blocks for your whole account in one pass.

Import other Azure resources