You might be able to use Azure Resource Graph Explorer to query for resources interacting with deprecated API versions. Below is a sample Kusto query to filter HTTP incoming requests by API version:
HttpIncomingRequests
| where TIMESTAMP > ago(30d)
| where targetResourceProvider == 'MICROSOFT.SQL'
| where subscriptionId == 'update-this-to-your-subid' //make sure you update this
| where apiVersion == "2014-04-01" or apiVersion == "2014-01-01" or apiVersion == "2014-04-01-preview"
Note: The HttpIncomingRequests
table is typically used for tracking HTTP requests handled by Azure services. You can use this query when you have Azure services like API Management, Azure Functions, or other HTTP-triggered services interacting with your resources. This will allow you to monitor and identify any usage of deprecated API versions.
To use this query:
- Search for "Resource Graph Explorer" on the Azure portal.
- Open Resource Graph Explorer and paste the query into the query window.
- Execute the query to see if any resources are using the deprecated API versions.
If you're only connecting to Azure SQL Database through connection strings in tools like SQL Server Management Studio (SSMS), Azure Data Factory (ADF), ODBC and similar resources, I would say generally safe to assume that you're not directly interacting with deprecated APIs. These tools typically use standard connection protocols (like TDS for SQL Server) rather than specific REST APIs that might have deprecated versions.
Please see this similar post https://learn.microsoft.com/en-us/answers/questions/1455624/how-to-identify-usage-of-azure-sql-database-2014-0. You might also consider reaching out to Microsoft directly for further confirmation.
Just noting that my reposonse was typed out then and then partially reworded by AI (ChatGPT) for better articulation. Before posting I did also read over and validated the information to ensure it was still accurate.