Forum Discussion
Passwordless failing on Work Profile Authenticator
Seeing an odd issue when attempting to enable passwordless using the Microsoft Authenticator app on an Android phone. The policy is definitely applying as we're seeing other indicators such as geo location and app information in the MFA request, but when we attempt to enable passwordless for that account it returns "Device not registered".
Device is corporate in Intune and showing recent last checking time.
When we use the Authenticator App outside of the work profile it works fine.
Possibly an App Protection policy causing it to fail? Although I don't see Microsoft Authenticator in the list of apps targeted by App Protection policy. Also our CA policy indicates "one of" for corporate or require app protection policies and the device is definitely enrolled using work profile.
Anyone else come across this or have ideas?
3 Replies
Thanks, this is a similar experience on one device that wasn't registered, so had applied an require app protection policy. On the other device it was marked as corporate so was excluded from the CA policy. We're migrating the second case to a new phone and just using the Authenticator App outside of the work profile for the time being.
Hi, sometimes authenticator in the work profile isn’t recognized as “registered” by Azure AD, even though Intune shows it as compliant.
Check the following:
-Make sure no MAM/CA policy blocks Authenticator in the work profile
-Confirm in Azure AD that the device is listed as “Registered” and “Compliant”
-Try reinstalling or clearing the cache for Authenticator in the work profile.
-Review the CA policy settings (“one of” vs. “Require App Protection”) for potential conflictsIf the issue persists, contact Microsoft support in case there are known bugs with Android work profiles
