Azure DevOps Services will require Server Name Indication (SNI) for all HTTPS connections starting April 23, 2025. SNI, a TLS extension, is widely supported, with about 99.995% of traffic already compatible. However, certain outdated client software and configurations may not support SNI, potentially resulting in connection errors such as SSL protocol errors or trust relationship issues. Users can test their SNI compatibility via the Azure DevOps status endpoint to ensure their systems will function correctly post-migration.
Starting April 23rd, 2025, SNI will be required for all incoming HTTPS connections to Azure DevOps Services, affecting some outdated client software.
SNI allows clients to specify the hostname they're connecting to, with more than 99.995% of existing traffic already supporting this feature.
Outdated or misconfigured libraries, older Java versions, and certain proxies may cause compatibility issues with SNI, leading to connection errors.
To check SNI compatibility, use the Azure DevOps status endpoint, successful calls confirm that your system is SNI-compatible.
Collection
[
|
...
]