Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2022 Release Wave 2Check out the latest updates and new features of Dynamics 365 released from October 2022 through March 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We have Dynamics 365 and NAV 2017, and WS-Trust authentication security protocol has been deprecated and we don' know what we should change in the standard connector for the integration between Navision 2017 (onpremise) - Dynamics 365.
Thank you very much for the help!
Please do have a look here:
We will update this blog today with more information how to mitigate when working with Dynamics NAV 2017 OnPrem.
Thank you very much! :-)
Dynamics 365 Business Central On-Premise 17.x
Short Term Solution:
It will let the existing integration work until April 2022. Drop SDK 184.108.40.206 on the NST and update binding redirect in the server config file. Follow this link (99+) How to deploy manually the newer version of CRM SDK on premise to skip Regional Discovery Service (RDS) validation error - Dynamics 365 Business Central Forum Community Forum
Mid Term Solution:
Dynamics 365 Business Central product group is about to implement the new XRM SDK also with on-premises 17.x and it will be included in July 2021 upcoming CU.
This hotfix is related to use latest XRM SDK that allow for skipping URL verification and fall back using global discoverability service. This is a mid-term solution valid until April 2022 where legacy Office365 authentication method will be deprecated by Dynamics 365 team.
Long term solution:
Move to OAuth authentication (same as for Dynamics 365 Business Central SaaS).
Business Applications communities