Share via

MS Authenticator got compromised

Duke Jason Regular 0 Reputation points
2026-05-18T18:20:59.28+00:00

hi, i got some issue with my authenticator app. it seems like my authenticator got hacked for some reason. my authenticator is currently set up on my phone as my primary device and in my tablet as my backup device. both are running android. i noticed that im unable to turn on backup to cloud, in which im able to do this before both in my phone and tablet(reason why im able to synced both). both today when i checked i cant do this anymore. i tried to wiped out my authenticator's cache and data settings in my phone so its like a fresh installed one. (i got this tip from MS). however, when i tried to restore the data to my phone, im unable to do it. im getting the error, and the weird part is im unable to login to my account here; though i got no issue logging into other MS services (onedrive, microsoft.com, etc). how can i able to restore back my authenticator account so that i can recover back those sites i enrolled that uses 2FA. really appreciate the help i can get. thanks in advance.

Microsoft Security | Microsoft Authenticator
0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-05-18T18:21:21.1666667+00:00

    Based on the described behavior (unable to turn on cloud backup anymore, restore failing, and sign-in to the Authenticator backup account failing while other Microsoft services still work), the situation most likely involves either:

    • A sign-in / security issue on the account used for Authenticator backup, or
    • A protection/block specific to Authenticator on the device(s).

    From the available guidance, the following steps are supported:

    1. Verify device and app prerequisites
      1. Ensure both Android devices have:
        • Latest Microsoft Authenticator version installed. Microsoft does not support app versions older than 12 months. Use the in-app Settings → App updates and make sure it is turned on, or reinstall from the store.
        • Correct Date & time set to automatic, then restart the device.
        • No VPN active while testing (disconnect VPN and try again).
        • Battery optimization turned off for Authenticator (Settings → Turn off battery optimization) so sync/backup can work reliably.
        • Notifications enabled (Settings → Notification Settings → Show notifications on) because some flows depend on push.
    2. Check for platform/service blocks
      1. On Android, Authenticator features (including passwordless and push) require Google Play Services and Google Play Store to be installed and enabled. If these are disabled or missing, certain Authenticator operations fail. Confirm both are present and enabled.
      2. If using Android for Work / Work Profile, ensure the work profile has its own PIN/biometric configured and that Authenticator in that profile is allowed to use it.
    3. Re-register the device and account for Authenticator features If the backup/restore or passwordless setup is partially broken, follow the supported reset path:
      1. Open Authenticator → Settings → Device Registration.
      2. Confirm the work/school account (if applicable) is shown as registered and joined to the organization. If not, sign in on the Device Registration page and complete registration.
      3. After registration, try enabling the relevant advanced features again (such as passwordless sign-in) and then retry backup/restore.
    4. Handle common Authenticator errors during setup/restore If any of these specific messages appear while trying to restore or re-add accounts, use the corresponding actions:
      • “Google Play services are currently unavailable on this device” or “Sorry, only part of the set up completed successfully”:
        • Ensure push notifications are enabled for Authenticator.
        • Confirm Google Play Services and Google Play Store are downloaded and enabled.
        • Ensure the device requires a PIN or biometric to unlock, and that hardware encryption is enabled (see Encrypt your Android device).
        • Reboot the device and try again.
      • “Please ensure push notifications are enabled in Settings” or “We could not complete the sign-in at this time”:
        • Go to Android Settings → Notifications and confirm push is enabled for Authenticator and the device has network connectivity.
        • If still failing, remove the affected account from Authenticator and attempt to add it again.
    5. If the Microsoft account itself may be compromised Since there is concern that Authenticator is “hacked,” and there are unexplained changes (backup disabled, restore blocked), treat the Microsoft account as potentially compromised:
      1. Follow the official “How to recover a hacked or compromised Microsoft account” flow and the account recovery web form to secure the account (change password, review security info, remove unknown aliases, and add safer verification methods such as Microsoft Authenticator or passkeys once access is restored).
      2. If security info (alternate email/phone) was changed by an attacker and recovery fails, the documented guidance is that there is no additional backend method for consumer accounts beyond the recovery form.
    6. When still unable to restore Authenticator data
      • If backup cannot be re-enabled and the cloud backup cannot be restored, the stored Authenticator configuration cannot be recovered from the app side.
      • For each site or service that used Authenticator for 2FA, use that site’s own recovery options (backup codes, alternate email/phone, or their support) to remove the old 2FA registration and add a new one on a fresh Authenticator instance.
      • For work/school tenants where the only global admin is locked out due to Authenticator/MFA issues, the supported path is to contact Microsoft Support (Data Protection team) via phone or a support ticket from another tenant to request an admin MFA reset.

    If, after these steps, Authenticator still cannot sign in or restore while other Microsoft services work, the next supported actions are:

    • For personal Microsoft accounts: continue using the account recovery form and, if needed, contact Microsoft Support via the consumer support portal to report the issue.
    • For work/school accounts: contact the organization’s IT admin or open a support ticket so Microsoft can assist with tenant-level recovery.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.