An Azure managed PostgreSQL database service for app development and deployment.
Hi @Andrey L - welcome to the Microsoft Azure QnA.
I do not think the AVM module is what references that API version.
The API versions declared by avm/res/data-protection/backup-vault are:
resource backupVault 'Microsoft.DataProtection/backupVaults@2024-04-01'
resource backupInstance 'Microsoft.DataProtection/backupVaults/backupInstances@2024-04-01'
There is no Microsoft.DBforPostgreSQL API version in the module. The dataSourceInfo values are passed through as resource IDs, types, and URIs, with no PostgreSQL API version attached.
So the module itself does not make the ltrPreBackup call and does not appear to reference 2023-03-01-preview. Azure Backup performs that operation during backup jobs, using an API version chosen by the service rather than by your template.
The tooling that identifies affected resources likely points to the vault because Azure Backup is acting through the vault’s managed identity, and that vault happened to be deployed by the AVM module.
That would mean there is no module update required and nothing for you to change in the AVM deployment. The API transition would sit with Microsoft inside the Azure Backup workflow.
That does not mean you should ignore it. If Azure Backup is still calling a retiring API version close to the deadline, that is worth a support case raised against Azure Backup rather than against PostgreSQL or AVM, since it is their workflow to transition.
You can confirm this from the Activity Log. Open one of the ltrPreBackup operations and check the caller. If the caller is an Azure Backup service identity, the request is coming from the service. If the caller is your deployment identity or pipeline principal, then it is coming from your side.
Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.