The "Setting up HTTPS" page for Azure DevOps is neither always accurate, nor up to date.
Consider replacing "Secure Sockets Layer (SSL)" with "Transport Layer Security (TLS)" where applicable, since SSL hasn't been relevant for many years.
Tone down the points about HTTP being faster than HTTPS, which is much less relevant these days as improvements in hardware and software has reduced the performance impact significantly, not to mention the HTTP/2 support in Windows Server 2016 which requires TLS but also would offer significant speedups in parallel requests.
"Disadvantages of Supporting or Requiring HTTPS with SSL" should not say that you must configure and manage your own CA, since you can use a third-party trusted certificate.
Verify the accuracy of claims made in "Disadvantages of Supporting or Requiring HTTPS with SSL", especially "you might have to reconfigure your deployment to stop supporting HTTPS with SSL before you can apply service packs or other updates" and "You must spend significant time setting up and testing either of these configurations, and troubleshooting your deployment will become more difficult", both which sound dubious.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 319f4e6c-2a0a-1d9f-8c5f-22b6676a828f
Version Independent ID: 37c5f853-546a-003e-9492-2d07d6894bb2
The "Setting up HTTPS" page for Azure DevOps is neither always accurate, nor up to date.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.