There is one major breaking change in the 10.1 preview over previous releases. Similar to the HTTP to HTTPS default changes made in web browsers a few years back (and the security reasons for them), we are changing the default value of the `Encrypt` connection option from `false` to `true`. With the increased emphasis on secure-by-default, the growing use of cloud databases, and the need to ensure connections are secure, it's time for this backwards-compatibility-breaking change. We realize this will cause some disruption, but letting clients try to connect without encryption by default leaves them open to attack from malicious actors.
The action item if you are affected by the Encrypt change is to either (in order of recommendation):
Install a trusted certificate on your server.
Change your client's Encrypt connection string setting to false.
If you maintain an application that uses the Microsoft JDBC Driver for SQL Server and you don't expose the Encrypt setting to your users, it's recommended that you make application changes to allow users to opt-in to non-encrypted connections.
Add the JDBC preview driver to your Maven project by adding the following code to your POM file to include it as a dependency in your project (choose .jre8, .jre11, or .jre17 for your required Java version).