Today, when I browsed to Azure DevOps I was welcomed with the following warning:
Over night something had changed and Microsoft stopped accepting TLS 1.0 / TLS 1.1 connections. It seems that I missed this blog post.
Due to the potential for future protocol downgrade attacks and other Transport Layer Security (TLS) protocol versions 1.0 and 1.1 vulnerabilities not specific to Microsoft’s implementation, it is required that dependencies on all security protocols older than TLS 1.2 be removed wherever possible.
Impact should be minimable unless you are still using Visual Studio 2010, 2012 or 2013. It also may impact Git operations in Visual Studio 2017(if you didn’t install the latest update).
In case you are still using these older Visual Studio versions, you can use the following registry change to force TLS 1.2 for all(!) .NET applications on your machine: https://docs.microsoft.com/en-us/troubleshoot/azure/active-directory/enable-support-tls-environment?tabs=azure-monitor#registry-strings
Remark: At the moment this only applies to Azure DevOps and NOT Azure DevOps Server.
More information: https://devblogs.microsoft.com/devops/deprecating-weak-cryptographic-standards-tls-1-0-and-tls-1-1-in-azure-devops/