Unable to destroy VM protected items with soft delete enabled

[mpjtaylor]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform (and AzureRM Provider) Version

Terraform 1.1.4
AzureRm 2.90 or 2.95

Affected Resource(s)

azurerm_backup_protected_vm

Terraform Configuration Files

data "azurerm_backup_policy_vm" "policy" {
  count               = local.backup
  name                = local.vm_backuppolicy
  recovery_vault_name = data.azurerm_recovery_services_vault.vault.name
  resource_group_name = data.azurerm_recovery_services_vault.vault.resource_group_name
  depends_on          = [data.azurerm_recovery_services_vault.vault]
}

resource "azurerm_backup_protected_vm" "backup" {
  count               = local.backup
  recovery_vault_name = data.azurerm_recovery_services_vault.vault.name
  resource_group_name = data.azurerm_recovery_services_vault.vault.resource_group_name
  source_vm_id        = local.virtual_machine_id
  backup_policy_id    = data.azurerm_backup_policy_vm.policy[0].id
}

resource "azurerm_recovery_services_vault" "support" {
  name                = var.vault_name
  location            = var.primary_location
  resource_group_name = var.resource_group_name
  sku                 = var.sku
  soft_delete_enabled = true
}

Debug Output

Error: waiting for Azure Backup protected VM context deadline exceeded

Expected Behaviour

The virtual machine and backup should be removed from the vault

Actual Behaviour

Virtual machine cannot be destroyed, the error
Error: waiting for Azure Backup protected VM context deadline exceeded

Steps to Reproduce

1. terraform plan
2. terraform apply

References

* #4276

[tombuildsstuff]

Duplicate of #4276

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.