Skip to main content
Level 1.6: Donut
October 17, 2024
Question

Android 15 - Cannot set default password app

  • October 17, 2024
  • 20 replies
  • 9 views

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?

 

20 replies

tngvmdAuthor
Level 1.6: Donut
November 30, 2024

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. 

Level 1.6: Donut
December 2, 2024

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

New Member
January 28, 2025

are there any updates? having the same issue here

tngvmdAuthor
Level 1.6: Donut
January 28, 2025

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. 

New Member
January 29, 2025

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?

Lizzie
Community Manager
February 12, 2025

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

Welcome to the Community everyone!Have a question or want to start a conversation, click here.
Level 1.6: Donut
February 12, 2025

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. 

Lizzie
Community Manager
February 26, 2025

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

Welcome to the Community everyone!Have a question or want to start a conversation, click here.
New Member
March 25, 2025

Hi @Lizzie , any updates you can share? Anxiously awaiting this fix! 

Lizzie
Community Manager
April 8, 2025

Hello everyone,

 

@tngvmd, @bholmquist11, @thomask, @Kiendeleo, @ofer_shnitzer, @tmeyers, @geekhelp_grant, @RobCordon, @ct-nremez, @nzbiship, @psiniemi, @HalvorsonD 

 

Thank you once again for your feedback here. As mentioned above, I wanted to provide you with a bit more context on this change. 

 

A credential manager is a great way to manage passwords, and I can see from the comments here how important this is to many of you here, but from a work perspective we’ve heard concern from customers that end-users could save work-related passwords in non-approved credential managers - which could add additional risk. 

 

Based on this, the ability to control credential managers for work was introduced in Android 14, and a corresponding AMAPI EMM policy was released. 

 

As mentioned by several of you, this now means an EMM or IT admin needs to specifically select an allowlist for credential manager. If an approved credential manager is not set, employees will be blocked from using a credential manager in Work Profile and Fully Managed devices.

 

Our partner team has been working with EMMs to help support them in enabling IT Admins to configure the settings required for this policy.

 

We know that many EMMs have made, and continue to make, updates around this policy, hence I would still recommend it is best to contact your specific EMM to find out the latest information.

 

For those of you who are using GEM (Google Endpoint Manager), I understand your frustration here - the team is actively working on building support for allowlisting Google Password Manager for users’ credentials. I have been following this closely and can see that they are making progress and I hope to update when I have more news on this.

 

Please continue to share information on this here in the community, your feedback is really helpful and I hope this will be running a lot smoother for you all shortly. 

 

Thanks so much,

Lizzie

Welcome to the Community everyone!Have a question or want to start a conversation, click here.
Level 1.6: Donut
April 8, 2025
Lizzie wrote:

the team is actively working on building support for allowlisting Google Password Manager for users’ credentials.

Am I understanding this right in reading that the intention is to only allow Google Password Manager if we're using Google Endpoint Manager? As in, we will not have the ability to whitelist e.g. Bitwarden outside of enterprise/EMM setups?

Lizzie
Community Manager
April 8, 2025

Hey @tmeyers,

 

Thanks for your reply.

 

Not necessarily. Really at the moment, our partner team in general is helping to support GEM and other EMMs, where possible, to enable the settings required for this policy. I don't currently have more of an update on the specifics. 

I have seen some EMM enable only one or two to start with, so there is potential for this to be the case, at the beginning.

 

I would continue to provide your feedback directly to GEM on your desired outcome here and other EMMs if anyone reading this isn't with GEM. 

 

Out of interest your example here 'Bitwarden outside of enterprise/EMM setups' is this for a particular management mode only? 

 

 

Welcome to the Community everyone!Have a question or want to start a conversation, click here.
Level 1.5: Cupcake
April 8, 2025

Google Password Manager now works (Android 16). All other apps still say blocked by work policy. Is this really that hard to fix?

Level 1.6: Donut
November 6, 2025

Hoping that this comment can be used to close this topic. Without anyone notifying us here, the standard Workspace systems (for those of us without a proper EMM) has finally been updated to allow any app to work. I've just done this with Bitwarden, so I can confirm that it's working.

 

  1. Log in to your admin console as a super admin or admin with appropriate admin privileges.
  2. Navigate to Apps > Web and Mobile Apps and locate your 3p password manager app. If it is not here, please go ahead to add the app.
  3. Once you have it added or it is in the listing, open the password manager app. "Apps->Web and mobile apps-><3rdPartyAppYouAdded>"
  4. Click on Settings "Apps->Web and mobile apps-><3rdPartyAppYouAdded>->Settings"
  5. Scroll down to the option Password manager for Android 15+ and enable this. You can adjust this for the different OUs as needed
Level 1.5: Cupcake
November 14, 2025

This setting is not showing for Dashlane. This thread is definitely not to be closed, it's still a complete and total mess.

 

That "Password manager for Android 15+" does not exist for Dashlane and other password managers still.

AM_IT
New Member
March 5, 2026

Seems to me that Microsoft is actively prioritising Apple over Android, it has been a year and all Intune updates have been supporting Apple configuration settings.  Meanwhile, we are considering moving away from Pixel phones to iPhones because we cannot apply appropriate security settings. Maybe Google want to reach our to Microsoft and ask why it’s taking so long?