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
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
For a test lab I have Dynamics 365 (D365) on premises installed. Internet facing.Microsoft Dynamics 365 Version 1612 (188.8.131.5234) (DB 184.108.40.20634) on-premises IFD. All green flagged.With only -one- IP address at my disposal I have installed Dynamics 365 and ADFS on the same box, meaning Dynamics 365 is using a different port than the standard port 443 which ADFS is using.
I don’t know if this is the root of my sorrows here.
The setup involves a completely green flagged PKI with an Offline Root and an Enterprise CA as a subordinate CA - certificates issued and in place.
This setup of course needs the relevant certificate to be copied to each clients Trusted Root Certification Authorities store in order to be able to connect without certificate warnings. But when done – it works. Flawlessly. From any PC.
..this scenario is completely different with the dedicated Android app “Dynamics 365 for Mobile”.
Trying this exact same approach (copying the certificate to the certificate store of the mobile phone) with Android v9 and trying to log on to Dynamics 365 on premises (on a different port than 443) throws an immediate error. The error unequivocally concerns a distrust with the “SSL” certificate and the mobile app refuses to connect.
The log on from Microsoft Dynamics 365 for Mobile would be: https://[org].[domain].com[:port]
Trying to connect exactly like this via the Android phones browser -also- complains about the certificate in place, but -does- allow for connection, although with the expected stripped down and not very functional mobile phone browser version.
Why does the dedicated Android app “Dynamics 365 for Mobile” not allow for the same seamless connection as the PCs in this setup, and is there no way to have the internal PKI issue a certificate that will satisfy Android and hence have “Dynamics 365 for Mobile” work without going through a third party certificate issuer? (..and will this last option even solve the issue of having the dedicated Android app connecting to D365 using a different port other than the standard 443?)
Sorry.. I realise this should have been posted in 365 and not here..
There does not seem to be a way to delete it.
Question re-posted at: community.dynamics.com/.../microsoft-dynamics-365-for-mobile---certificate-trusted-on-pcs-but-not-on-android
Business Applications communities