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
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I configured the CRM Email Router on my machine where I connect to Dynamics CRM Online. I retrieved list of mailboxes which I want to Test Access for.
Somehow, when I Test Access for the same, I get an error for a mailbox saying: 'The underlying connection was closed. An unexpected error occurred on a send. The handshake failed due to an unexpected packet format.'
And for Server, I get the error saying: 'The underlying connection was closed. An unexpected error occurred on a send. The handshake failed due to an unexpected packet format.'
I've kept Auto-discover on for the Email server which points to https://autodiscover-red003.mail.apac.microsoftonline.com/ews/exchange.asmx (email@example.com)
What could have been wrong here? Kindly help.
Check whether you are able to access the auto discover URL from IE in Email Router server.
There are 2 possible reasons for the error message:
1. You are not able to access the auto discover URL (May be the URL is not getting resolved or no internet access in EMail Router server).
2. The credentials provided in the configuration profile don't have the required access.
The best way is to test in IE from Email router server and provide credentials used in configuration profile when prompted.
Turning on Auto-discover helped.
Business Applications communities