Problem Retire Older Version Azure SQL APIs.

Question

Problem Retire Older Version Azure SQL APIs.

wwoodgeotech 0

We received a notice that MS is retiring the Azure SQL Database 2014-04-01 APIs. We have several database in the subscriptions identified in their letter. Each of these SQL databases are being only used with Azure VMs and connected to MS Access via ODBC. There is no other code or scripts used with them.

Do we need to be concerned about the API that is being retired?

TIA

Uwe Fuchs 140 Reputation points

2024-08-26T20:47:32.7833333+00:00
It's not always straightforward to determine whether your current ODBC driver uses the deprecated API version. Typically, ODBC drivers abstract API version details from the end-user (If they are in fact used). Here are some steps you can take to check:

Check the ODBC Driver Documentation: Review the documentation for your ODBC driver, as it often includes information about compatibility and supported API versions. This is usually the easiest way to determine the API versions supported by your driver.

Review ODBC Driver Settings: On Windows, open the ODBC Data Source Administrator (search for "ODBC" in the Start menu). Check the configuration for your data source or driver for any settings or version information that might indicate the API version being used.

Contact the Driver Vendor: If you’re still unsure, contacting the driver vendor or consulting their support resources can provide more detailed information about API compatibility.

Additionally, you can use Azure Resource Graph Explorer to query for resources interacting with deprecated API versions. Here’s a sample Kusto query to filter HTTP incoming requests by API version:

HttpIncomingRequests | where TIMESTAMP > ago(1d) | 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. By ensuring your ODBC driver and MS Access configurations are up-to-date (This is generally sufficient) and running the Kusto query, you can help avoid issues related to the deprecated API version.

These tools generally rely on standard connection protocols, such as TDS for SQL Server, rather than specific REST APIs that may have deprecated versions. As a result, it's usually safe to assume that you're not directly working with deprecated APIs.

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.
Dave Graham 0 Reputation points

2024-08-27T16:34:28.11+00:00

Is that query AI Generated? I haven't been able to find HttpIncomingRequests as a table anywhere.
Uwe Fuchs 140 Reputation points

2024-08-27T20:08:09.11+00:00

Hi @Dave Graham

Thank you for pointing this out. I have gone ahead and updated my comment accordingly. I've used this query with Service Bus, and I believe it should work for SQL as well, though I'm not entirely certain. I think you might only see this table if you're using HTTP requests to interact with Azure resources. Since you're accessing it via MS Access through ODBC, as long as you're using the latest supported driver versions, you should be fine. However, as I mentioned earlier, if you're still unsure or want 100% confirmation that you're not using the deprecated API, you might want to contact Microsoft support as the link suggests. I hope this answers your question.

1 answer

Your answer

Dave Graham 0 Reputation points

2024-08-27T16:34:28.11+00:00

Is that query AI Generated? I haven't been able to find HttpIncomingRequests as a table anywhere.
Uwe Fuchs 140 Reputation points

2024-08-27T20:08:09.11+00:00

Hi @Dave Graham

Thank you for pointing this out. I have gone ahead and updated my comment accordingly. I've used this query with Service Bus, and I believe it should work for SQL as well, though I'm not entirely certain. I think you might only see this table if you're using HTTP requests to interact with Azure resources. Since you're accessing it via MS Access through ODBC, as long as you're using the latest supported driver versions, you should be fine. However, as I mentioned earlier, if you're still unsure or want 100% confirmation that you're not using the deprecated API, you might want to contact Microsoft support as the link suggests. I hope this answers your question.

Answer 1

Hi @wwoodgeotech

You can open Azure portal -> Subscriptions -> Resource Providers, search for "Microsoft.Sql", if this is registered, you will receive the notification. If there is no SQL resource created in the subscription, you can ignore the notification email

The alert is on the azure advisory refers to an update that is being done on the APIs from azure.

The retirement notice is specifically about the API version used for managing and interacting with Azure SQL Database resources programmatically.

If you are currently using the Azure portal, Azure CLI, or Azure PowerShell to manage Azure SQL Database, you need not to take any action.

Someone has shared HttpIncomingRequests table query. I believe HttpIncomingRequests is a backend query that can be executed by the support agent.

Below query you can try running in Azure Resource Graph Explorer from Azure portal

resources

| where type == 'Microsoft.Sql/servers/databases'

| project apiVersion

Hope this help!

Thank You!

Share via

Problem Retire Older Version Azure SQL APIs.

1 answer

Your answer