Azure Database for PostgreSQL Preview API Retirement – API Usage by Azure Data Protection Backup Vault Service: Azure Database for PostgreSQL Flexible Server Resource: biolabs-production-primary-server Retirement deadline: 30 January 2027 API version obs

2026-11-16T07:53:40.1366667+00:00

Issue Description

We received an Azure Service Health notification regarding the retirement of Azure Database for PostgreSQL Preview APIs, including versions 2025-06-01-preview and earlier, by 30 January 2027.

During our investigation, we reviewed the Azure Activity Logs for the last 30 days and identified recurring requests using API version 2023-03-01-preview.

Investigation Findings

The affected resource is biolabs-production-primary-server.

The following operations were observed:

Microsoft.DBforPostgreSQL/flexibleServers/ltrPreBackup/action

  `Microsoft.DBforPostgreSQL/flexibleServers/startLtrBackup/action`
  
  The requests originate from the system-assigned managed identity of our Azure Data Protection Backup Vault named `database-backups`.
  
  Two backup instances are configured in the vault, and both currently show `ProtectionConfigured`.
  
  No other PostgreSQL API versions were observed in the matching Activity Log requests during the 30-day review.
  

Clarification Required

We would appreciate guidance on the following:

Are these API calls generated internally by the Azure Data Protection backup service?

Will Microsoft automatically migrate this integration to a supported API version before 30 January 2027?

Is any manual action required from our side?

Which supported API version should be used for these long-term backup operations?

Could this retirement affect existing backup schedules, recovery points, or backup protection?

We have not made any changes to the existing backup configuration.

We would appreciate your guidance on the recommended remediation steps to ensure uninterrupted backup operations before the retirement deadline.

Azure Database for PostgreSQL
0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-11-16T07:54:54.9833333+00:00

    The ltrPreBackup and startLtrBackup requests are generated by Azure Backup through the Backup vault’s managed identity, so there is no customer-side API version to change; keep protection configured, validate backup and restore operations, and obtain Microsoft Support confirmation that the managed integration will be upgraded before 30 January 2027.

    What the Activity Log entries mean

    The observed pattern matches the documented Azure Backup v1 long-term retention (LTR) workflow:

    • Azure Backup invokes the PostgreSQL Flexible Server ARM API on each policy schedule.
    • It authenticates with the Backup vault’s managed identity.
    • ltrPreBackup/action checks whether the server is ready for an LTR backup.
    • The start operation initiates that backup.

    The built-in PostgreSQL Flexible Server Long Term Retention Backup Role explicitly grants the vault identity ltrPreBackup/action and other LTR operations.^1^ The documented backup flow also states that Azure Backup invokes the PostgreSQL ARM API according to the configured policy.^2^

    Therefore, these are service-managed calls, not calls from your own ARM, Bicep, Terraform, CLI, or SDK implementation.

    API retirement and supported versions

    2023-03-01-preview is explicitly scheduled for retirement on 30 January 2027. Deprecated preview APIs eventually stop functioning.^3^

    For LTR operations, Microsoft currently documents:

    • 2025-08-01 as a stable API containing LTR resources and operations.^4^
    • 2026-10-01 as a newer stable API supporting long-term retention operations.^5^
    • 2026-04-01-preview as the default API for the current .NET StartLtrBackupFlexibleServer method.^6^

    If you own code that invokes these operations directly, prefer a stable API that exposes the required operation—currently 2026-10-01, or 2025-08-01 where compatibility with that release is required. The REST release notes identify both stable and preview API releases and list LTR among the supported stable operations.^7^

    For calls made by Azure Backup, however, you cannot select or override the API version.

    Is Microsoft guaranteed to migrate the integration automatically?

    The public documentation does not currently provide an explicit commitment or migration schedule for Azure Backup’s internal caller from 2023-03-01-preview to a supported API. Consequently, an automatic transition should not be treated as confirmed solely because the caller is a Microsoft-managed service.

    Do not delete and recreate the backup instances merely to try to change the API version. Backup configuration does not expose such a setting, and recreating protection is not documented as remediation for this retirement.

    1. Leave both backup instances in ProtectionConfigured.
      No configuration change is currently documented for service-generated API usage.
    2. Verify recent jobs, not only protection status.
      In Azure portal → Backup vault → Backup instances, open each instance and confirm that recent scheduled jobs completed successfully and produced recovery points.
    3. Run an on-demand backup and track it to completion.
      This provides an end-to-end validation of the same managed integration. The supported configuration guidance documents on-demand backup and job tracking after protection is configured.^8^
    4. Perform a restore test in a nonproduction workflow.
      Microsoft recommends testing LTR backup and restore immediately after configuration. For the v1 logical-backup solution, restore is currently Restore as Files.^9^
    5. Open an Azure support request before the deadline.
      Include:
      • the Service Health tracking ID;
      • the Backup vault resource ID and region;
      • the two backup-instance names;
      • representative Activity Log correlation IDs and timestamps;
      • the observed 2023-03-01-preview URIs and operation names;
      • a request for written confirmation of the Azure Backup rollout timeline.
    6. Continue monitoring the Activity Log.
      The retirement guidance specifically recommends Activity Log inspection to identify API versions. Once the managed service is updated, new backup runs should show a supported API version.^3^

    Potential effect if the caller is not updated

    Existing recovery points are governed by the configured retention policy and are not documented as being deleted by this API retirement. The risk is to control-plane operations attempted after retirement: because deprecated APIs cease functioning, future pre-check, backup initiation, job tracking, or restore requests using the retired version could fail.^3^

    That makes successful backup and restore testing—and confirmation from Azure Support about the service-managed caller—the appropriate remediation. Migrating from backup v1 to the v2 preview is a separate, one-way product migration and should not be undertaken solely to address this notice.^10^


    References

    1. Azure built-in roles for Databases
    2. About Azure Database for PostgreSQL - Flexible Server backup
    3. Azure Database for PostgreSQL REST APIs life cycle
    4. Microsoft.DBforPostgreSQL flexibleServers/ltrBackupOperations 2025-08-01 (deployment-language-bicep)
    5. Microsoft.DBforPostgreSQL flexibleServers/ltrBackupOperations 2026-10-01 (deployment-language-bicep)
    6. PostgreSqlFlexibleServerResource.StartLtrBackupFlexibleServer Method-Definition
    7. Release notes for the REST APIs for Azure Database for PostgreSQL ...
    8. Configure backup for Azure Database for PostgreSQL - Flexible Server using Azure portal
    9. Backup and restore in Azure Database for PostgreSQL flexible server
    10. Migrate Azure Database for PostgreSQL flexible server v1 backups to v2 experience by using Azure portal (preview)
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.