How to Import an Azure Monitor Scheduled Query Rule Alert (v2) into Terraform

Import Azure Monitor Scheduled Query Rule Alert (v2) with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Azure Monitor resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Azure Monitor Scheduled Query Rule Alert (v2) 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_monitor_scheduled_query_rules_alert_v2.main
  id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.Insights/scheduledQueryRules/prod-log-alert"
}

Example azurerm_monitor_scheduled_query_rules_alert_v2 configuration

Here is a realistic Azure Monitor Scheduled Query Rule Alert (v2) block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.

resource "azurerm_monitor_scheduled_query_rules_alert_v2" "main" {
  name                 = "prod-log-alert"
  resource_group_name  = "prod-rg"
  location             = "eastus"
  scopes               = [azurerm_log_analytics_workspace.main.id]
  severity             = 3
  evaluation_frequency = "PT5M"
  window_duration      = "PT5M"

  criteria {
    query                   = "AppExceptions | summarize count()"
    time_aggregation_method = "Count"
    threshold               = 10
    operator                = "GreaterThan"
  }

  action {
    action_groups = [azurerm_monitor_action_group.ops.id]
  }
}

Gotchas when importing a Azure Monitor Scheduled Query Rule Alert (v2)

• Both the v1 (azurerm_monitor_scheduled_query_rules_alert) and v2 resources map to the same ARM type Microsoft.Insights/scheduledQueryRules; import a given rule as exactly one of them, not both.
• evaluation_frequency and window_duration are ISO 8601 durations (PT5M, PT1H); Terraback defaults to PT5M when the source value is absent.
• The KQL query is emitted as a heredoc; preserve its formatting, since the provider compares the query string and reformatting causes diffs.
• The action block takes action_groups as a list of action group IDs, unlike the v1 resource and activity log alert which use a singular action_group_id.

Doing it manually with terraform import

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