x

Microsoft recently updated the discovery services for dynamics 365, replacing them with a new service.

If your integration has stopped working and has gone down, there is a quick work around to get you up and running again quickly.

 

If you update your connection string to include the following at the end of your connection string this should get you up and running quickly.

 

;SkipDiscovery=true 

 

which will leave you with something like this:

 

<add key="CRMOnlineUri" value="Url=https://sample.crm4.dynamics.com; username=abc@xyz.com; Password=examplepass; authtype=Office365;SkipDiscovery=true"/>

 

If this doesn't work you may also need to update your Core Dynamics assembly/DLL

 

Longer term the goal is to move over to using Application Users, rather than a username/password to authenticate.

 

If this article was useful please share with the community

Want to keep informed?

Recent Articles

View all Articles

Popular Tags

Contact Us

Business Hours

  • Monday-Friday: 9.00am to 6pm

Our Featured Clients and Partners

Here are just a selection of our Partners and Clients