%3CLINGO-SUB%20id%3D%22lingo-sub-1239463%22%20slang%3D%22en-US%22%3ESupport%20Tip%3A%20How%20to%20update%20your%20Intune%20Exchange%20Connector%20to%20use%20TLS%201.2%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1239463%22%20slang%3D%22en-US%22%3E%3CP%3EIntune%20has%20moved%20to%20%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23ffffff%3B%20color%3A%20%23333333%3B%20cursor%3A%20text%3B%20font-family%3A%20inherit%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3Esupport%20the%20Transport%20Layer%20Security%20%26nbsp%3B(TLS)%201.2%2B.%20However%2C%20the%20Intune%20Exchange%20Connector%20has%20not%20updated%20yet.%20We%20expect%20in%20the%20next%20month%20or%20so%20that%20we'll%20release%20an%20updated%20%3C%2FSPAN%3EMicrosoft%20Intune%20Exchange%20Connector%20to%20support%20the%20TLS%201.2%2B.%20If%20you%20don't%20want%20to%20wait%20until%20that%20connector%20is%20available%2C%20you%20can%20use%20the%20registry%20key%20changes%20from%20this%20docs%20page%3A%20%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fdotnet%2Fframework%2Fnetwork-programming%2Ftls%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdotnet%2Fframework%2Fnetwork-programming%2Ftls%3C%2FA%3E%20to%20update%20the%20connector.%20You'll%20have%20a%20Message%20Center%20post%20today%20-%20MC207032%20-%20if%20your%20organization%20is%20still%20using%20an%26nbsp%3B%20Exchange%20Connector%20with%20TLS%201.0.%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EHere's%20the%20set%20of%20registry%20key%20changes%20that%20will%20move%20your%20Connector%20to%20TLS%201.2.%20We've%20heard%20success%20from%20several%20customers%20that%20followed%20the%20steps%20listed%20on%20the%20docs%20page%20links%20above.%26nbsp%3B%3CBR%20%2F%3E%26nbsp%3B%3CBR%20%2F%3E%5BHKEY_LOCAL_MACHINE%5CSOFTWARE%5CWOW6432Node%5CMicrosoft%5C.NETFramework%5Cv2.0.50727%5D%3CBR%20%2F%3E%22SystemDefaultTlsVersions%22%3Ddword%3A00000001%3CBR%20%2F%3E%22SchUseStrongCrypto%22%3Ddword%3A00000001%3CBR%20%2F%3E%26nbsp%3B%3CBR%20%2F%3E%5BHKEY_LOCAL_MACHINE%5CSOFTWARE%5CWOW6432Node%5CMicrosoft%5C.NETFramework%5Cv4.0.30319%5D%3CBR%20%2F%3E%22SystemDefaultTlsVersions%22%3Ddword%3A00000001%3CBR%20%2F%3E%22SchUseStrongCrypto%22%3Ddword%3A00000001%3CBR%20%2F%3E%26nbsp%3B%3CBR%20%2F%3E%5BHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5C.NETFramework%5Cv2.0.50727%5D%3CBR%20%2F%3E%22SystemDefaultTlsVersions%22%3Ddword%3A00000001%3CBR%20%2F%3E%22SchUseStrongCrypto%22%3Ddword%3A00000001%3CBR%20%2F%3E%26nbsp%3B%3CBR%20%2F%3E%5BHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5C.NETFramework%5Cv4.0.30319%5D%3CBR%20%2F%3E%22SystemDefaultTlsVersions%22%3Ddword%3A00000001%3CBR%20%2F%3E%22SchUseStrongCrypto%22%3Ddword%3A00000001%3CBR%20%2F%3E%26nbsp%3B%3CBR%20%2F%3EThis%20registry%20key%20change%20will%20move%20the%20connector%20to%20TLS%201.2%2B.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20aren't%20on%20an%20urgent%20timeline%20to%20move%20to%20TLS%201.2%2B%2C%20then%20the%20updated%20Exchange%20Connector%20should%20be%20made%20available%20for%20your%20use%20in%20an%20upcoming%20release.%20Again%2C%20we'll%20post%20a%20Message%20Center%20post%20and%20update%20this%20blog%20when%20that%20releases.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1239463%22%20slang%3D%22en-US%22%3E%3CP%3ERead%20this%20article%20for%20the%20steps%20to%20move%20your%20Intune%20Exchange%20Connector%20to%20TLS%201.2%2B.%20We%20will%20be%20shipping%20an%20updated%20Exchange%20Connector%20too%3B%20just%20sharing%20the%20steps%20if%20you'd%20like%20to%20move%20now.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1239463%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%20Exchange%20Connector%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESupport%20Tip%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1241548%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20How%20to%20update%20your%20Intune%20Exchange%20Connector%20to%20use%20TLS%201.2%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1241548%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20for%20information.%3C%2FP%3E%3CP%3EWhen%20is%20the%20upgrade%20scheduled%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1250823%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20How%20to%20update%20your%20Intune%20Exchange%20Connector%20to%20use%20TLS%201.2%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1250823%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20currently%20testing%20the%20new%20connector%20with%20a%20few%20customers%20just%20to%20make%20sure%20it's%20ready%20for%20release.%20We%20anticipated%20releasing%20in%20April%20(per%20the%20message%20center%20post)%20but%20we%20wanted%20to%20get%20the%20info%20out%20how%20to%20make%20this%20change%20on%20your%20own%20so%20you%20could%20change%20earlier%20if%20you%20wanted.%20We'll%20post%20an%20MC%20post%20when%20the%20new%20connector%20is%20out.%3C%2FP%3E%3C%2FLINGO-BODY%3E

Intune has moved to support the Transport Layer Security  (TLS) 1.2+. However, the Intune Exchange Connector has not updated yet. We expect in the next month or so that we'll release an updated Microsoft Intune Exchange Connector to support the TLS 1.2+. If you don't want to wait until that connector is available, you can use the registry key changes from this docs page: https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls to update the connector. You'll have a Message Center post today - MC207032 - if your organization is still using an  Exchange Connector with TLS 1.0. 

 

Here's the set of registry key changes that will move your Connector to TLS 1.2. We've heard success from several customers that followed the steps listed on the docs page links above. 
 
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
 
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
 
This registry key change will move the connector to TLS 1.2+.

 

If you aren't on an urgent timeline to move to TLS 1.2+, then the updated Exchange Connector should be made available for your use in an upcoming release. Again, we'll post a Message Center post and update this blog when that releases.  

2 Comments
Occasional Contributor

Thank you for information.

When is the upgrade scheduled?

We are currently testing the new connector with a few customers just to make sure it's ready for release. We anticipated releasing in April (per the message center post) but we wanted to get the info out how to make this change on your own so you could change earlier if you wanted. We'll post an MC post when the new connector is out.