TLS 1.2 Upgrade

Hi, don't worry: .NET Framework 4.6.1 already supports TLS 1.2, and Azure SQL has been requiring it for some time, so if your site talks to Azure SQL today, it's already negotiating TLS 1.2; it only breaks if you force old protocols (TLS 1.0/1.1) or use outdated clients. Do this quick check: look in the ServicePointManager.SecurityProtocol/SslProtocols/WCF binding code and remove the pinning to old protocols (if necessary, set SecurityProtocolType.Tls12); verify the connection string with Encrypt=True; TrustServerCertificate=False;; in App Service, set Minimum TLS version = 1.2 and test; if you call third parties, test a TLS 1.2 handshake (from dev: openssl s_client -tls1_2 -connect your_site:443). Seeing TLS 1.3 in the browser is normal (browser → front-end), while the app running to backends like Azure SQL will use TLS 1.2. In the medium term, you can retarget to .NET 4.8 to stay in line, but come September 1st, nothing should break unless you're forcing TLS 1.0/1.1.