How can I verify which Azure SQL Database API version my EF Core Azure Functions app is using?

The APIs mentioned in the email aren’t ones that your application directly invokes from within Entity Framework Core. In your app the connection to Azure SQL Database is done through the Microsoft.Data.SqlClient (and ultimately TDS) rather than an explicit REST API call that uses version strings like 2014-04-01.

That is, when you use EF Core (with the SqlServer provider) and Microsoft.Data.SqlClient you aren’t opting into a specific “Azure SQL Database API version” in your code. The driver itself abstracts the underlying wire protocol and connectivity. In other words, the API “version” you’re really using is controlled by the package version (for example, 2.1.4 or later) and by the defaults within that driver. There isn’t a separate setting that tells the driver to use the 2014-04-01 endpoints.

That said, here are some ways you can verify what’s in use:

• Check your project’s dependency versions:
  Make sure your project’s package references show that you’re using the expected versions (e.g. Microsoft.Data.SqlClient ≥ 2.1.4). You can inspect your .csproj or your NuGet package manager to confirm this.

• Inspect the assembly version at runtime:
  You can use reflection to print out the version of the Microsoft.Data.SqlClient assembly that is loaded. For example:

  CSHARPCopied
  using System;
  using System.Reflection;
  using Microsoft.Data.SqlClient;
  
  public class Program
  {
      public static void Main()
      {
          Version sqlClientVersion = typeof(SqlConnection)
              .Assembly
              .GetName()
              .Version;
          
          Console.WriteLine($"Microsoft.Data.SqlClient version: {sqlClientVersion}");
      }
  }

  Running this snippet will display the assembly version at runtime, which reflects the version of the underlying driver your app is using.

• Review Documentation and Release Notes:
  Check the release notes for Microsoft.Data.SqlClient and EF Core to see if there has been any mention of deprecating or changing the API endpoints (or underlying connectivity) for Azure SQL Database. Typically, if an API is being deprecated on the backend (like the 2014-04-01 management API) but your client library isn’t directly calling that API, no changes are required on your side.

Since your app’s connection to Azure SQL Database is established via the client driver rather than via an explicit REST management API call, you aren’t directly selecting a version that would be affected by the deprecation. Just verify that you’re running a supported release of Microsoft.Data.SqlClient (and that your EF Core app targets a supported TFM), and monitor the release announcements in case the driver’s implementation changes its defaults.

If you have any concerns about the impact of the deprecation, consider reaching out via the appropriate Azure support channels for clarification on whether your connectivity (and not management) calls are affected.