Azure Database for PostgreSQL: Impact of retiring preview APIs on AVM module referencing old preview version

Andrey L 0 Reputation points
2026-11-15T23:07:01.28+00:00

Problem description

I am concerned about the retirement of preview APIs for Azure Database for PostgreSQL, specifically regarding my deployment that uses an AVM module referencing an older preview API version. I received a notice indicating that the preview API version 2025-06-01-preview and earlier will be retired, and I am using an AVM module that internally references this old preview API.

Environment

Azure Database for PostgreSQL flexible server in an unspecified region, managed through infrastructure-as-code using an AVM/Bicep module for the Microsoft.DBforPostgreSQL/flexibleServers resource type.

What I've already tried

I posted a github issue [AVM Question/Feedback]: Preview APIs of Azure Database for PostgreSQL will be retired. Transition from Preview APIs versions 2025-06-01-preview or earlier versions by 30 January 2027 · Issue #7590 · Azure/bicep-registry-modules to the AVM repository. The maintainer confirmed the issue and advised contacting Microsoft backup/postgress team. Raising azure support request didn't help - I am going in cycles, AI support bot is useless and does not understand the issue.

Current status

The issue is not resoled and it's unclear if microsoft is going to publish the required update to let the AVM module consume the correct API version or is it going to be broken

Azure Database for PostgreSQL
0 comments No comments

1 answer

Sort by: Newest
  1. SHOUMIK CHAKRAVARTY 1,535 Reputation points
    2026-11-16T00:59:24.8333333+00:00

    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.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.