Android 15 - Cannot set default password app

[tngvmd]

We use Microsoft Intune to manage devices. For the devices which have upgraded to Android 15, the end users can no longer select Microsoft Authenticator as their default application for auto filling passwords. I cannot find any settings in Intune to allow it. All devices are fully managed corporate owned devices. The devices are all Google Pixel 8 or 8a devices. 

Is this a bug in 15 or am I missing something?

 

[HalvorsonD]

I have the same problem, looking for a solution. 

[Lizzie]

Hello @tngvmd and @HalvorsonD,

Lovely to meet you. Thanks so much for highlighting this. 

I've fed this back to our team to investigate a little more, I'll keep you updated when I have more information. Have you also raised this via Intune? 

Thanks again, speak soon.

Lizzie

[tngvmd]

@Lizzie  HI! I was wondering if you had any update on this? I have continued to experiment without success. I did post to Intune's customer message board, but have not seen any responses. My remaining users are anxious to upgrade to 15 and those who have upgraded are upset that they can't use their password managers to log in. 

[jasonbayton]

I'm looking into this. Android 15 added new functionality for credentialmanager - 

Not directly related to your issue. You're seeing a work policy block, suggesting there's a policy default at play perhaps.

This applies for 14 and above:  CredentialProviderPolicyDefault and gives me the same behaviour you're seeing when it's unconfigured or blocked. Can you verify this config in Intune? 

[tngvmd]

@Lizzie - I have not raised this with Intune. I am not certain how to do that, but will see what I can figure out. I have done A LOT of experimentation, and the issue is limited to Android 15. I have done the following:

1 - There are only two configured items that apply to the phones. One is a device compliance policy that sets requirements for the lock screen. The other is the device restriction policy. I deleted both completely and reset a phone twice. The first time I re-enrolled it as a personal device with work profile. The personal section worked fine. The ability to set the password service in the work profile was still blocked despite no policies being applied. I then reset the phone and reenrolled it as a corporate owned fully managed device and still had the same outcome despite the device compliance and device configuration policies having been deleted and therefore not having been applied. 

2 - The second thing that I did that makes it very clear that this is an issue that is specific to 15 and Intune is the following. I took a Pixel 7a running Android 14 while my device configuration and device compliance settings were deleted. I factory reset it while on 14 and re-joined it as a fully managed corporate owned device. Everything worked fine. I set Authenticator to be the password provider. I updated the phone to 15. The phone went back to not having a password provider and the setting being blocked. 

After doing this, I recreated my device config and device compliance policies from scratch to make certain that I did not find any new settings. There were no new settings and nothing changed on the devices with regards to this issue once the policies were reapplied. 

I looked for the setting that @jasonbayton mentioned above and cannot find it. I am wondering if there is some issue with Intune and their handling of this setting in 15.

Thanks,

Tom

[tngvmd]

I have now also posted this in the Microsoft Intune community. A link to that is here. I will post back if a solution is found on that side. 

Android 15 - CredentialProviderPolicy not surfaced by Intune - Microsoft Community Hub

[HalvorsonD]

I didn't have this issue in Android 14 (or earlier either).

The policy has been gone through multiple times, and nothing is set via that portal.  I wish there was an easy way to 'dump' the policy on the phone to see what is being set, and from where.  I have also communicated with the Intune side, but initial comments is that it's an OS policy problem.

[psiniemi]

Just upgraded to Android 15 and ran into the same issue. Can't find an Intune policy that I could change this with...

[geekhelp_grant]

I'm having this same issue in Android 15, using Google Workspace for business. Been through all the options and policies (even though nothing's changed) and can't find a reason. Worked fine in A14.

[Lizzie]

Hey everyone,

Thanks for your patience on this. I just wanted to say that I have been speaking with our team internally about this. The information you highlighted here has been super helpful. The team is still looking into this and so I will come back as soon as I can with an update - but I did want to just let you know that it is being looked into. 

Thanks,

Lizzie 

[Kiendeleo]

I am having the same issue.  It seems to be affecting widget support as well. 

[ofer_shnitzer]

I'm still experiencing this issue, are there any updates?

I'm also seeing the services listed under my personal account instead of under my work account, I think this might be related to the issue.

[tngvmd]

Update - This started working today FOR MICROSOFT AUTHENTICATOR ONLY. Still no go for Dashlane or any other service. Since we use Authenticator, this was very good new for us. 

[Kiendeleo]

This still does not work with Google's own MDM and Google's own password manager.