Azure SQL API version upgrade notification

Question

Hello Team,

We received a notification regarding the retirement of the Azure SQL REST API version 2014-04-01 (effective 30 June 2026), indicating that resources using this API version should be updated.

The following advisor resources are reported:

• DbParameterization (Microsoft.Sql/servers/advisors@2014-04-01)
• DefragmentIndex (Microsoft.Sql/servers/advisors@2014-04-01)
• DropIndex (Microsoft.Sql/servers/advisors@2014-04-01)
• ForceLastGoodPlan (Microsoft.Sql/servers/advisors@2014-04-01)

These resources appear when exporting an ARM template from the Azure portal; however, they are not explicitly defined in our Bicep/ARM templates or deployment pipelines.

Based on our understanding, these are Azure-managed resources associated with the Azure SQL Automatic Tuning/Advisor framework rather than resources deployed or maintained through our Infrastructure-as-Code.

We would appreciate your confirmation on the following points:

1. Since these advisor resources are system-generated and managed by Azure SQL, do they require any action from our side as part of the API version retirement?
2. Will the retirement of API version 2014-04-01 impact:
   • the runtime operation of Azure SQL databases, or
     • only management operations that explicitly invoke this API version?
     1. If any action is required, what is the recommended approach?
        • Should these advisor resources be migrated to a newer API version?
          • Or should they remain Azure-managed without any customer intervention?

Additionally, we have one further concern if these Automatic Tuning/Advisor resources are fully managed by Microsoft and are not customer-deployed, could you please explain why Azure continues to create or expose these resources using the retired 2014-04-01 API version, even for Azure SQL resources deployed recently in 2026.

This is confusing because the retirement notification indicates that resources using this API version require remediation, yet newly deployed Azure SQL resources still appear to reference the retired API version through Azure-managed advisor resources.

We would appreciate your clarification regarding the next steps, if any, that are required from our side within the Azure environment in relation to the retirement of Azure SQL REST API version 2014-04-01.