This post is part of the Microsoft Dynamics GP Fall 2020 Release New Features series where I am going to echo the posts from the Dynamics GP Support and Services Blog, while adding some commentary, on the new features introduced in the Microsoft Dynamics GP Fall 2020 Release which is now available.
This post is on the TLS 1.2 System enhancement.
I discovered in January 2020 that I’d encountered problems with the workflow email actions due to TLS 1.0 being retired from browsers and mobile pgones (cellphones). With the Fall 2020 release, this issue with web services is resolved along with the following features which will now be able to function with TLS 1.0 and 1.1 disabled:
- E-mailing from within Dynamics GP when using both the Exchange Server Type as well as the SMTP e-mail that is used for the Workflow feature in Dynamics GP
- The Microsoft Dynamics GP Web Client
- Web Services for Microsoft Dynamics GP
Web Services for Microsoft Dynamics GP still requires TLS 1.0 when using a SQL Server database for the Authorization Store. If you reinstall Web Services for Microsoft Dynamics GP to an Active Directory partition per this blog article you can operate with TLS 1.0 and 1.1 disabled.
This strikes me as odd that the Dynamics Security Data Store on SQL Server, which is the recommended location, still requires TLS 1.0. Microsoft haven’t explained why this is the case, but I assume there is some sort of technical reason.
In terms of functionality that still requires TLS 1.0, the refreshable Excel reports that can be deployed from Dynamics GP are still using the SQLOLEDB provider, which requires TLS 1.0. You can manually update the connection string in your Excel files to use the SQLNCLI11 provider as a workaround.