How to Import an Azure Proximity Placement Group into Terraform

Import Azure Proximity Placement Group with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Azure Compute resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Azure Proximity Placement Group 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_proximity_placement_group.main
  id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.Compute/proximityPlacementGroups/prod-ppg"
}

Example azurerm_proximity_placement_group configuration

Here is a realistic Azure Proximity Placement Group block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.

resource "azurerm_proximity_placement_group" "main" {
  name                = "prod-ppg"
  resource_group_name = "prod-rg"
  location            = "eastus"
}

Gotchas when importing a Azure Proximity Placement Group

• The ARM type is Microsoft.Compute/proximityPlacementGroups; the group is a placement constraint and contains no compute itself.
• VMs, availability sets, and scale sets reference the group via proximity_placement_group_id; importing the group does not import those members.
• allowed_vm_sizes and zone are optional, but if set, zone is only valid together with allowed_vm_sizes, which is why Terraback emits zone conditionally.
• All members of a proximity placement group are pinned to the same datacenter, so an unavailable VM size in that location can block scaling the group.

Doing it manually with terraform import

The native approach is to write the azurerm_proximity_placement_group block by hand, then run terraform import azurerm_proximity_placement_group.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