Microsoft JDBC Driver 13.2 End of Support: March 13, 2027
Microsoft JDBC Driver 13.2 for SQL Server must be upgraded by March 13, 2027 to keep Microsoft support. That is the upgrade-by date for 13.2 in Microsoft's support matrix for the Microsoft JDBC Driver for SQL Server, the com.microsoft.sqlserver:mssql-jdbc artifact that most Java applications use to reach SQL Server and Azure SQL. Version 13.2 was released on August 15, 2025, so it gets well under two years of support, far less than the five years every 12.x and older version received.
Why 13.2 ends years before major version 13
Microsoft's policy text reads: "The latest minor version must be installed within 12 months of the minor version release date to continue to receive full support for the duration of the major version mainstream support period." Version 13.4 shipped on March 13, 2026, which started the 12-month clock for 13.2. The matrix lists every 13.x minor with its deadline:
| mssql-jdbc | Released | Upgrade by (Microsoft) |
|---|---|---|
| 13.6 | September 10, 2026 | Current version; major version 13 mainstream support ends March 13, 2031 |
| 13.4 | March 13, 2026 | September 10, 2027 |
| 13.2 | August 15, 2025 | March 13, 2027 |
The current minor has no upgrade-by date yet; it gets one when the next minor ships. Versions 12.x and older keep the old rule of five years from each minor's release. Every version is on the Microsoft JDBC Driver for SQL Server page.
What 13.2 supports today
- Java: Microsoft's matrix lists JRE versions 1.8, 11, 17, 21 and 24 for 13.2, shipped as two jars:
mssql-jdbc-13.2.x.jre8.jarandmssql-jdbc-13.2.x.jre11.jar(the jre11 jar is for Java 11 and later). The 13.6 entry in the same table adds Java 25 and 26. - Databases: the matrix says every currently supported driver version supports all supported versions of SQL Server, Azure SQL Database, Azure Synapse Analytics, Azure SQL Managed Instance, SQL database in Microsoft Fabric and Fabric Data Warehouse. That statement covers 13.2 only while 13.2 is itself supported.
Why a forgotten driver matters
The JDBC driver sits between every Java service and the database and handles the connection's TLS and authentication. Teams pin it in a pom.xml or Gradle file, or get it bundled inside an application server or a vendor product, and then stop looking at it. The application keeps working after the deadline, which is why a 13.2 jar can stay in production long after support ends.
What ends is the fixes. Microsoft's release notes show what support has meant for this line: the 13.2.1 hotfix addressed CVE-2025-59250, a spoofing vulnerability in the JDBC Driver for SQL Server. The matrix also says vulnerable dependencies are updated in hot fixes of supported versions only. Once 13.2 is past its deadline, a fix for a newly found flaw lands in the supported driver versions, not in 13.2.
Microsoft does not sell more time on the driver. If an application cannot move before the deadline, the form above is how we check whether a third-party vendor covers your version, and we will tell you plainly if none does.
What to do
- Find every copy of 13.2. Search build files and dependency trees for
mssql-jdbc13.2 (version strings13.2.x.jre8or13.2.x.jre11), and check application servers and vendor products that ship their own copy. Our stack scanner reads apom.xmlor lock file and flags it. - Target 13.6, not 13.4. Microsoft's matrix lists 13.6 as the current version. Version 13.4 must itself be upgraded by September 10, 2027, so it buys only six months.
- Plan for a yearly driver update. Staying on major version 13 means taking each new minor within 12 months of its release; doing that keeps you supported until major version 13 ends on March 13, 2031. Teams that cannot keep that pace can use 12.10, which has a fixed end of mainstream support of January 31, 2030.
- Test connections before you switch. Run the new driver against each SQL Server or Azure SQL target, including encryption and authentication settings, and read Microsoft's release notes for each minor between 13.2 and your target.
Still on an older line? Our guide to Microsoft JDBC Driver 10.2 end of support covers the 12.x-and-older five-year rule.
Frequently Asked Questions
When does Microsoft JDBC Driver 13.2 for SQL Server reach end of support?
Microsoft's support matrix for the Microsoft JDBC Driver for SQL Server sets the upgrade deadline for version 13.2 at March 13, 2027. A 13.x minor version keeps support only until its upgrade-by date, so after that day 13.2 no longer receives support from Microsoft.
Why does 13.2 lose support before the 13.x major version ends?
From version 13, Microsoft supports the major version for at least five years, but only on its latest minor version. Each newer minor must be installed within 12 months of its release to keep support. Version 13.4 started 13.2's 12-month clock, so 13.2 ends years before major version 13 does.
Can I buy extended support for the Microsoft JDBC Driver from Microsoft?
No. Microsoft's support matrix says extended and custom support options are not available for the Microsoft JDBC Driver. When a version's support ends, the only Microsoft path is a newer driver version.
Which mssql-jdbc version should I upgrade 13.2 to?
Version 13.6, which Microsoft's matrix lists as the current version. Moving to 13.4 instead buys only months, because 13.4 already has its own upgrade-by date. Teams that cannot take a new minor every year can look at 12.10, which has a fixed five-year end date in the matrix.
Related
- Microsoft JDBC Driver for SQL Server — every version and its dates
- Microsoft JDBC Driver 10.2 end of support — the older five-year rule
- SQL Server — the database engine's own lifecycle
- Java end of life by vendor — the runtime versions the driver jars target