Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
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
Hope you are well.
Essentially, Dynamics 365 has full compatibility with TLS 1.2 only 184.108.40.2063 or v9.
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.
Business Applications communities