Dynamics 365 F&O/AX Dynamics 365 CE / CRM Dynamics GP Business Central / NAV UG Dynamics SL Power Platform Fabric UG MS Copilot UG

[Jeff Woodard]

Up

0

Down

::

I can’t speak specifically to BC, but I suspect your major impacts will be on the SQL server, web server, and web clients rather than NAV/BC. It is a very good security measure to adopt. We did this about 2 years ago with on-prem SQL and web servers, and didn’t have any major issues. I recall we did have some unexpected issues with MS Office (I can’t recall specifically what), and had a couple of PC clients that got missed. Research any specific settings needed if you’re running older versions of SQL or Windows Server. Here’s the official documentation from MS including the registry key settings: https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-server. We found this handy tool that made the updates a lot easier than manually adjusting the reg keys: https://www.nartac.com/Products/IISCrypto. There is a lot of rebooting needed, so be mindful of your backup schedules. Windows event viewer will also be your friend to identify servers and/or software that might not be using the expected TLS version.

learn.microsoft.com

404 - Content Not Found

404 - Content Not Found

[Lewis Rosenberg]

Up

0

Down

::

Thank you Jeff. Right now this only concerns the service tier server and not the SQL server, so hopefully nothing to be concerned about….yet.

[Sean Nguyen]

Up

0

Down

::

Yes like Jeff said I would monitor for any issues in the event log. We recently made the change thinking it’s only our SQL server without realizing we have third party integrations that weren’t “TLS” ready and ended up undoing the change and reenabled SSL until our vendor updated their code.

[Lewis Rosenberg]

Up

0

Down

::

Thanks for all of the responses.

I just learned that TLS can affect SMTP functionality from BC/NAV and that BC 14 Service defaults to using TLS 1.2 but this is controlled within the customsettings.config.