Personalized Community is here!
Quickly find the content you seek
Check out the latest Field Service updates!Learn about the key capabilities and features of Dynamics 365 Field Service and experience some of the new features.
Download overview guide | Watch Field Service video
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 am really hoping to get some help with a seemingly confusing issue. I have end users who use Field Service Mobile (on CRM online, Mobile app version is: 184.108.40.206) and they were able to login fine until something changed in our organization (we are not able to determine if something really changed).Now, when an end user logs into Field Service Mobile, they get the below error.
If the error is not visible in the above screenshot i have typed it here: "Http Error: AADSTS50079 Due to a configuration change made by your administrator, or because you moved to a new location, you must enroll in multi-factor authentication to access 00000009-0000-0000-000c-000000000000"
Based on the above error description, we tried to look for any kind of conditional access on Azure AD that is imposing MFA. Our AD team says they dont see any such policy that imposes MFA, they seem to be believing that its something on CRM that is causing this error.From my experience, this behavior is not managed on CRM.
Another observation was that, when users login using Resco mobile app, they are able to login fine, which kind of proves that issue dosent reside on CRM.
We have engaged Microsoft and but even they haven't been able to find out the issue so far.
Any help, suggestions or insights will be very much helpful.
Also, if possible can someone explain what would be the authentication flow when we login from a Field Service Mobile app?
Forgot to mention, we are using OAuth option on the Field Service Mobile App while we are logging in.
Business Applications communities