azurerm_backup_policy_vm has no "Azure Backup Resource Group (Optional)" parameter

[stevanovic-milan]

Is there an existing issue for this?

• I have searched the existing issues

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 Version

1.3.4

AzureRM Provider Version

3.28.0

Affected Resource(s)/Data Source(s)

azurerm_backup_policy_vm

Terraform Configuration Files

resource "azurerm_backup_policy_vm" "daily_backup" {
  name                = "Daily_VM_Backup_Policy"
  recovery_vault_name = azurerm_recovery_services_vault.rsv.name
  resource_group_name = var.resource_group.name
  timezone = "W. Europe Standard Time"
  backup {
    frequency = "Daily"
    time      = "05:00"
  }
  retention_daily {
    count = 7
  }
  retention_monthly {
    count    = 3
    weekdays = ["Sunday"]
    weeks    = ["Last"]
  }
}

Debug Output/Panic Output

There is no parameter that allows you to set "Azure Backup Resource Group (Optional)" as you can do via the Azure portal.

Expected Behaviour

The expected behavior is to have the parameter.

Actual Behaviour

No response

Steps to Reproduce

No response

Important Factoids

No response

References

No response

[github-actions]

This functionality has been released in v3.45.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[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.