Updated: October 19, 2020 (October 19, 2020)

  Analyst Report

Azure TLS Enforcement Varies by Service

My Atlas / Analyst Reports

492 wordsTime to read: 3 min
Rob Sanfilippo by
Rob Sanfilippo

Before joining Directions on Microsoft, Rob worked at Microsoft for 14 years where he designed technologies for Microsoft products and... more

  • Azure services vary widely in their enforcement of the TLS 1.2 encryption protocol, which eliminates vulnerabilities of earlier protocols.
  • Organizations should review the types of Azure services they have deployed and the TLS support policies for those services.
  • Services could discontinue support for older protocols, which may require organizations to update or reconfigure software.

Azure offers dozens of services, and although they communicate internally using Transport Layer Security (TLS) 1.2, there is no overall standard regarding the encryption protocol they use to communicate with external applications.

TLS 1.2 Recommended, Updates May Be Required

The TLS protocol replaced Secure Sockets Layer (SSL) for encrypting network communications. SSL and versions of TLS prior to 1.2 have been found to have vulnerabilities, and it is a best practice to use TLS 1.2 or later. (TLS 1.3 is the latest version.)

Certain software, such as OSs and Web browsers, requires configuration to use TLS 1.2 or later. Windows 8 and later and Windows Server 2012 and later use TLS 1.2 by default. Applications may require code changes to work with TLS 1.2 in cases where earlier encryption protocols were expected or hard-coded.

Atlas Members have full access

Get access to this and thousands of other unbiased analyses, roadmaps, decision kits, infographics, reference guides, and more, all included with membership. Comprehensive access to the most in-depth and unbiased expertise for Microsoft enterprise decision-making is waiting.

Membership Options

Already have an account? Login Now

Not a member but want to see the full content? Contact us.