Forum Discussion
Android 15 - Cannot set default password app
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?
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.
This still does not work with Google's own MDM and Google's own password manager.
are there any updates? having the same issue here
This still only works with Microsoft Authenticator for me. Neither Dashlane nor Google's own Password Manager work. Given the fact that the Beta for Android 16 is out, I am wondering if they are going to just fix it in 16.
If it works for MS Authenticator, it's on the app level, I suppose. Maybe they are fixing it in Google Play Services or in Google app?
Hello tngvmd, Kiendeleo, geekhelp_grant, psiniemi, HalvorsonD, ct-nremez, tmeyers, nzbiship, thomask
Thanks again for continuing to investigate this. I've been exploring this too and would recommend to contact your specific EMM/MDM, as this appears to be working slightly differently from one partner to another.
I know this isn't the most useful answer here, and I will continue to follow-up on this. Please do continue to discuss what you are experiencing, I will continue to feed it back to our team.
Thanks so much,
Lizzie
This is a particularly useless response, as my MDM provider is Google Workspace. A Google Product Provided by Google. Google Workspace support already has a ticket open that says it is an Android issue, which is another Google product.
We use Google Workspace and Google Pixel phones. I AM the owner/admin of our Google Workspace. Is there a setting we need to change in the Admin Console? This broke when I simply upgraded our phones to Android 15.
Google Workspace would need to implement the APIs released for 15 as it's a default-disable. Lizzie could probe for answers internally but if you have an active support agreement with them you'll encourage a better response by reaching out as it increases demand generation for their product folks.
would recommend to contact your specific EMM/MDM
Sure... 🙄
Hey Google. Your Google Workspace MDM is broken with Android 15 on Pixel 7 Pro.
As mentioned by others, this was working perfectly fine in Android 14, but the update to 15 broke it.
So I've received a note that Google Workspace has an internal feature request (381410766) to create a policy setting for the credentialProviderPolicy field. This field was optional in A14 but became mandatory in A15. Apparently, this policy change has caught Workspace completely flat footed, as the timeline for the feature request was said to be "...a few months" from now (even though I raised it when A15 was released). Apparently, we'll all be on A16 by the time Google Workspace realizes that there's been a security change in the Android requirements.
The answer that I was given by Google was to turn off passkey usage and simply use 2SV. I assume that Google also recommends us using simple, memorable passwords since we can't use the high-entropy passwords that password managers allow us to use. I'm going to use "hunter2" since I seem to remember it really easily.
I do have a suggestion for the developers: there's this really cool new AI coding tool called "Gemini" by a company, I can't remember who it is but I'm sure they have the highest security standards. Maybe ask it, something like: "Provide me with the necessary code to enable changing the credentialProviderPolicy under the Android Management API". A few questions later, and you'll probably have everything you need.
Hello everyone,
Thanks again for your continued feedback on the change to the authenticator experience and how it's been rolled out. I am relaying your frustrations and broader experiences back internally.
I'm working to get a more detailed explanation of the change for you. Hopefully this context would be helpful.
In the meantime, let's continue the conversation on this - I will continue to ensure they are heard internally.
Thank you,
Lizzie
