[AVM Module Issue]: Issues when identity set to null

[teemukom]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

Bug

Module Name

avm/res/data-protection/backup-vault

(Optional) Module Version

No response

Description

Hi,

there is an interesting issue when the backup vault's identity is set to null. This can be achieved by not setting the managedIdentities parameter. After the initial deployment any update will cause an error "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'”. This can be reproduced also without AVM.

I opened a support case with MS and one possible fix would be to set the identity type to "none" (of course this is totally undocumented):

resource backupVault 'Microsoft.DataProtection/BackupVaults@2024-04-01' = {
  name: vaultName
  location: location
  identity: {
    type: 'None'
  }
  ...
}

Could this also be implemented to the AVM module so by not setting the managedIdentities parameter the identity would be set to "type: 'None'" instead of null?

(Optional) Correlation Id

No response

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[avm-team-linter]

@teemukom, thanks for submitting this issue for the avm/res/data-protection/backup-vault module!

Important

A member of the @Azure/avm-res-dataprotection-backupvault-module-owners-bicep or @Azure/avm-res-dataprotection-backupvault-module-contributors-bicep team will review it soon!