Skip to main content
GMenzies
GMenzies
Level 2.0: Eclair
July 7, 2026
Question

AMAPI - FRPadmin emails change

  • July 7, 2026
  • 3 replies
  • 104 views

Hey,
 

I’m trying to better understand this AMAPI release (May 2026), we currently have issues with our corporate owned personally enabled devices where if a users personal gmail account is added to the personal profile of the device if the device is reset via recovery mode the users pin / personal gmail account is required.

We started using EFRP admin emails to bypass this so we could get back into our own devices, we’re a large organisation so users generally don’t reset devices before handing them back or hand them back to their manager who is unaware of our process.

What I’d like to understand is what the below change did as after testing this it still seems to be the same that when setting the FRP admin emails setting to be not configured a recovery mode wipe still triggers consumer FRP.

AMAPI improves Factory Reset Protection (FRP) policy handling on COPE devices by explicitly disabling FRP and clearing account lists when no admin emails are configured, preventing unexpected lockouts after device resets.

Thanks.

    3 replies

    Kris
    Kris
    Level 1.6: Donut
    July 7, 2026

    Hey ​@GMenzies 

    it is a huge surprise for me to read that Microsoft Intune integrated AMAPI for FRP. ​@CoreyC do you confirm ?

    In my opinion, that’s not the case. You have to declare a FRP account in Intune but it is another problem.

    Kris

     

    Kris
    GMenzies
    GMenziesAuthor
    Level 2.0: Eclair
    July 7, 2026

    ​@Kris COPE devices use AMAPI within Intune, currently it’s only BYOD devices using DPC and that’s soon to change by the end of the year when devices move to Android Web Enrollment which will use AMAPI.

    Kris
    Kris
    Level 1.6: Donut
    July 7, 2026

    ​@GMenzies i agree with you, i just said i am not sure that Microsoft Intune has integrated this AMAPI Fonctionality. I have the same problem with FRP since ANDROID 15 in my company.

    Kris
    Lizzie
    LizzieCommunity Manager
    Community Manager
    July 7, 2026

    Hey ​@GMenzies, ​@Kris,

     

    Thanks for highlighting this is happening on COPE devices. I’m just looking into this, as it could be a bug, especially as you’re not seeing anything different. I’ll come back to you as soon as I have more information. 

     

    Lizzie

    Welcome to the Community everyone!
      GMenzies
      GMenziesAuthor
      Level 2.0: Eclair
      July 13, 2026

      ​@Lizzie  Did you hear anything back about this?

      Lizzie
      LizzieCommunity Manager
      Community Manager
      July 13, 2026

      Hey ​@GMenzies,

       

      Sorry for the delay, I’ve been looking into this and we do have a bug ticket open for this issue. The good news is believe that a fix has applied, but my delay here was actually because I’m awaiting a timeline for the full rollout of this fix. As soon as I have more details I’ll let you know.

       

      Thanks so much and speak soon,
      Lizzie

       

      FYI - ​@Marcel_K_XDMT, as I have a feeling this could be a similar issue to what you are experiencing (let me know if yours is different though). Thank you. 

      Welcome to the Community everyone!
      GMenzies
      GMenziesAuthor
      Level 2.0: Eclair
      July 13, 2026

      Thanks for the update ​@Lizzie do you know how this is expected to work after the fix is implemented should this completely disable consumer factory reset protection even via recovery mode device resets?

      Thanks!

      Lizzie
      LizzieCommunity Manager
      Community Manager
      July 14, 2026

      Thanks ​@GMenzies, I believe it should work in the following way...

      When a device is reset with the following:

      • COPE enrolled devices
      • With personal email on the device
      • No FRP admin account set

      It will no longer prompt for FRP.

       

      Is that what you are looking to happen here? 

       

      Thanks,
      Lizzie

      Welcome to the Community everyone!
      Terms & ConditionsAccessibility statement