CRM 2013 emails not being generated with TLS 1.2 protocol

(0) Share

Report

Posted on by Naumi

TLS 1.0 and 1.1 were disabled on the Exchange servers. This affected outgoing email processing on CRM 2013. Ultimately TLS must be upgraded to version 1.2. Please can you advice on the workaround for this, while we are still looking into upgrading CRM to the latest version

I have the same question (0)

All responses (1)

Answers (0)

Gustavo Longo on at

Like (0)

Report

RE: CRM 2013 emails not being generated with TLS 1.2 protocol

Hello Naumi,

Hope you are well.

Essentially, Dynamics 365 has full compatibility with TLS 1.2 only 8.2.2.1663 or v9.

https://www.microsoft.com/en-us/download/details.aspx?id=57079

https://cloudblogs.microsoft.com/dynamics365/bdm/2017/09/28/updates-coming-to-dynamics-365-customer-engagement-connection-security/?source=crm

I suppose you are using E-mail Router to integrate Exchange servers with Dynamics.

TLS is not controlled by the E-mail router but of the security settings on the machine through the registry entries that would be used similar to a server that .Net would leverage.

If you have TLS 1.2 enabled, TLS 1.1 and TLS 1.0 disabled for client on the server, and the SystemDefaultTLS registry keys configured – then the outgoing communication for .Net will be TLS 1.2.

You can use the following registry key to enforce the TLS 1.2 rather than other versions.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727]
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727]
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

Regards,

Was this reply helpful? Yes No