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
2023 Release Wave 1Check out the latest updates and new features of Dynamics 365 released from April 2023 through September 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
Hi all, not sure if anything has changed in the last day or two but our connection from NAV2017 (CU26) to Dynamics 365 online has stopped working. It's been working fine for a few years and just stopped working yesterday. The error we get when we try the 'test connection' is "Unable to login to Dynamics CRM". I have checked the login credentials and these are ok to login to CRM directly. Has anyone else had problems recently?
I am having the exact same problem as you had. I assume that it's because of deprecation of the Regional Discovery Service . I recommend that you open a service request for Microsoft, and tell them when it happened and the impact of this issue on your business.
In the case of Japan region, the integration has stopped working suddenly last week (May 27 JST). I wish I found the latest CRM SDK, but I still couldn't find a feasible solution.
Hope this helps,
After a bit of investigation, I think it might be related to this. docs.microsoft.com/.../important-changes-coming
Looks like I may need to change from the authentication type of "Office365" to "OAuth" authentication. I am not sure how to do this though
You can try to change from "Office365" to "OAuth" in the page "CRM Connection Setup" (Page 5330)
Could you please let me know if it works for you? I tried it before and it did not work for us.
To verify the connection, you can build the connection yourself via this tool:
It is a bit of a puzzle when you do this for the first time, but after a while you should be able to figure it out. If the connection works from there, it is an issue with Dynamics 365 BC / Dynamics NAV. if XRM Toolbox connection is not able to connect either, it is an issue with CRM. Note that not all older releases of Dynamics NAV have added support for OAUTH(2) yet.
The link Andrew shared will indeed happen but does not explain why connection stopped working for an existing CRM tenant.
The way to ensure you can use OAUTH / OAUTH2 is to upgrade to later release of Dynamics 365 BC. OAUTH will also be added for older Dynamics NAV releases, but it requires you to ensure you are running latest CU so that you can easily move to the one that will have the supported added. I do not believe it is yet there, but we are working on it.
We are having this same issue - has anyone successfully fixed this?
We are facing this issue with NAV 2018 version as well. We created a ticket to support and waiting for some technical solutions. If there is any improvement , i'll up to date this post.
We are experiencing the same problem since today. Especially struggling with the connection string and different parameters such as AppID and RedirectURI. All possible values/combinations fail. Spoke to Microsoft today but didn’t get any further yet. I hope they have an answer soon.
Good day all,
Please have a look at this blog posting. We got hit by this issue yesterday.
Later this afternoon we will update the blog posting with mitigation steps.
Marco - any update on this?
I am having the same issue with NAV2017 (technical upgrade to BC14) and D365 CRM
see SOLUTION SCENARIOS RELATED TO D365 INTEGRATION THAT ARE USING O365 LEGACY INTEGRATION AND CRM SDK THAT VALIDATE URL AGAINST RDS - Dynamics 365 Business Central Forum Community Forum
I got through the deprecation of the Regional Discovery Service (RDS) by deploying the newer version of CRM SDK exactly as Duilio posted. I believe that his post should be the answer to this question. Thank you!
Business Applications communities