Finding & fixing Azure resource using Azure SQL Database 2014-04-01 APIs

Hi @Mikael Karlgren

Thanks for contacting to Microsoft QA, we have reviewed your concern and below is the detailed solution -  

The Azure SQL Database REST API version 2014-04-01, which is part of the control plane used for managing Azure SQL resources (servers, databases, elastic pools, etc.), not the data plane (your actual queries or connections). This API version is being retired, and any ARM templates, scripts, SDKs, or tools referencing it will eventually fail after the retirement date.

Updated Retirement Timeline

Originally scheduled for 31 October 2025, the retirement date has been extended to 30 June 2026 based on customer feedback. See official notice: Azure SQL Database REST API 2014-04-01 Retirement Notice. [free.blessedness.top]

How to Identify Resources Using the Old API Version

Export ARM Template from Azure Portal

Go to Azure Portal → Resource → Export Template.

  Search for "apiVersion": "2014-04-01" in the exported JSON. If found, update it to a newer version like 2021-11-01 or 2023-08-01. [Reference: Retirement notice Q&A](https://free.blessedness.top/en-us/answers/questions/1073330/retirement-notice-azure-sql-database-2014-04-01-ap).
  
  Azure Resource Graph Explorer Run this query to check across subscriptions:
  

kusto isn’t fully supported. Syntax highlighting is based on Plain Text.

Resources

| where type =~ 'microsoft.sql/servers/databases'

| where apiVersion contains '2014-04-01'

https://free.blessedness.top/en-us/azure/governance/resource-graph/samples/advanced?tabs=azure-cli Azure CLI

Shell

az graph query -q "Resources | where type =~ 'microsoft.sql/servers/databases' | where apiVersion contains '2014-04-01'"

How to Upgrade

Update ARM/Bicep Templates Change:

"apiVersion": "2014-04-01"

To:

"apiVersion": "2021-11-01" // or latest stable version

See REST API reference for latest versions

Update SDKs and Tools If you use Microsoft.Azure.Management.Sql, note that it’s deprecated. Switch to Azure.ResourceManager.Sql. GitHub discussion on SDK migration. [github.com]

Verify Resource Provider In Azure Portal → Subscriptions → Resource Providers, ensure Microsoft.Sql is registered. If you don’t use SQL resources, you can unregister to stop notifications. Microsoft Q&A guidance. [free.blessedness.top]

Important Points

This change does not affect your database runtime or connectivity (e.g., JDBC, ODBC, SSMS).

It only impacts management operations via ARM templates, REST API calls, CLI, PowerShell, or SDKs.

If your queries return no results, you likely have no active resources using the old API version—but double-check templates and automation scripts.

References for further reading:

Azure SQL Database REST API Retirement Notice

How to identify usage of old API version

Update ARM template API version

Hope the above steps were helpful. If you have any other questions, please feel free to contact us.

Thanks,
Vrishabh

Hello,

Thanks for the detailed answer!

I followed your instructions to search for "2014-04-01" in all related subscribtion id export templates, but could not find this unfortunately. I also went to Azure Resource Graph Explorer and ran the query you recommended this - same here, no results. Lastly, also checked running your Shell query with Azure CLI - no results here either.

C:\Users\mikae>az graph query -q "Resources | where type =~ 'microsoft.sql/servers/databases' | where apiVersion contains '2014-04-01'" { "count": 0, "data": [], "skip_token": null, "total_records": 0 }

C:\Users\mikae>az graph query -q "Resources | where apiVersion contains '2014-04-01'" { "count": 0, "data": [], "skip_token": null, "total_records": 0 }

I've done lots of digging previously also, with similar queries - but nothing found.

Is it possible that you from Microsoft review my potential usings of this API version, to help find where this api version is used?

BR, Mikael

Hi Mikael Karlgren

Thank you for sharing your feedback. Here’s a detailed explanation addressing your additional question.

Why You’re Still Seeing These Alerts

These notifications usually pop up when something in your subscription—like a policy, role, or automation script—references the old API version, even if it’s not actively being used. If your searches returned nothing, the reference might be buried in an Azure Policy, a custom role, or an automation script. In some cases, it’s tied to Microsoft-managed resources (like Log Analytics), which you can’t directly change.

What You Should Do Next

Check Azure Policies

Run this command:

az policy definition list --query "[?contains(policyRule, '2014-04-01')]" -o json

If you find any policies using the old API, update them to a newer version.

Check Custom Roles

Run:

az role definition list --query "[?contains(to_string(permissions), '2014-04-01')]" -o json

Update any roles that reference the old API.

Review Automation Accounts

If you use Automation Accounts, search your runbooks for 2014-04-01:

PowerShell

Get-AzAutomationRunbook | Select-String -Pattern "2014-04-01"

Look at Deployment History

Shell

az deployment group list --query "[?contains(properties.templateLink.uri, '2014-04-01')]" -o json

If Everything Comes Back Clean

If none of these checks show results, the warning is likely for an internal Microsoft-managed dependency. In that case:

• You don’t need to take any action—Microsoft will update those internal calls before the retirement date.
• If you don’t use SQL resources at all, you can stop the notifications by unregistering the provider:

Shell

az provider unregister --namespace Microsoft.Sql

This change only affects management operations (like ARM templates, REST API calls, CLI, PowerShell). It does not impact your database runtime or connectivity.

  In case if You Find References

Replace:

"apiVersion": "2014-04-01"

with:

"apiVersion": "2023-08-01" // latest stable version

  Hope the above steps were helpful. If you have any other questions, please feel free to contact us.

Thanks,Vrishabh

Hi Mikael Karlgren

We hope the above steps were helpful. If you have any other questions, please feel free to contact us.

Thank you,
Vrishabh

Hello Vrishabh,

Thanks for your detailed answer!I ran all commands you suggested (with slight modifications as some returned errors), but received empty array responses - no finds.

az policy definition list --query "[?contains(to_string(policyRule), '2014-04-01')]" -o json

[]

az role definition list --query "[?contains(to_string(permissions), '2014-04-01')]" -o json

[]

az deployment sub list --query "[?properties.templateLink && properties.templateLink.uri && contains(properties.templateLink.uri, '2014-04-01')]" -o json

[]

There exists no automation accounts in our Azure organizaiton. So I guess it's like I initally thought, some internal tool on Microsoft's end, right?

Quite problematic that Microsoft if so haven't fixed this yet, and that I'm keeping getting these emails that we're supposed to take action. Can you please forward this ticket internally to try make the Microsoft Azure team aware of this issue, if it's indeed some tool needing to be updated on Microsoft's end? So that this can be updated ASAP, before the deadline date.

Best regards,

Mikael