How to Stop Microsoft Authenticator Prompts for Removed Accounts

Microsoft Authenticator can keep receiving approval requests even after an old work account is removed from the app. The reason is that deleting the visible app entry does not always remove the device from the organization’s Microsoft 365 or Azure AD multi-factor authentication registration.

Why deleted app entries still trigger approval prompts

If the former tenant still has that phone registered as an authentication method, push notifications may continue. Opening the prompt can then show an account-not-found message because the local app entry is gone while the cloud-side binding still exists.

Approval prompts keep arriving for former work or shared service accounts.

The MFA method may still be linked to the old organization on the backend.

Removing the app entry alone does not guarantee that cloud-side MFA is removed.

Reset the old MFA method from the organization side

For Microsoft 365 business or education accounts, the supported fix is an admin-side reset of the authentication methods. This is a cloud account operation, not a local app repair.

Ask a tenant administrator to reset your authentication methods

If the account belongs to a company or school tenant and another admin still exists, that administrator should use the Microsoft Learn guidance for managing Azure AD Multi-Factor Authentication methods and reset the affected account’s MFA options.

• Supported entry point: the organization’s Microsoft 365 or Azure AD admin flow for managing authentication methods.
• Expected result: the old device binding is cleared on the backend.
• Verification: approval prompts to the removed account should stop after the reset is completed.

Relevant references include Manage authentication methods for Azure AD Multi-Factor Authentication and the O365 Portal for reconfiguration when access still exists.

Use Microsoft business support if you are the only administrator

If the affected account is the only admin account and sign-in is no longer possible, a available guidance cannot reset it. The supported route is Microsoft’s Data Protection or business support team, which can verify identity and handle the reset request.

• Use Microsoft 365 for business support phone numbers by country or region.
• Or use Global Customer Service or Global Customer Service phone numbers.
• The source indicates that phone routing may ask for product type, company account status, and whether another administrator exists.

What removing the app account does not do

Deleting the account from Microsoft Authenticator removes it from the phone interface. It does not guarantee that the old Microsoft 365 tenant stops sending MFA requests.

Cloud registration remains

If the former organization still has that device registered as an authentication method, the behavior is consistent with a backend binding that was never reset.

This also explains why the prompt can open to an error saying the account cannot be found. The local app no longer has the account entry, but the organization-side MFA workflow may still be targeting the registered device.

Android cleanup worth checking first

These steps only remove local remnants on Android. They can help if an old work account still exists on the device, but they do not replace an admin-side MFA reset.

Remove any leftover Microsoft or work account from Android settings

• Open Settings.
• Go to Users & accounts or Accounts and backup, depending on Android version.
• Find the old Microsoft account or work account entry.
• Tap the account, then choose More or the two-dot menu.
• Select Remove account. Repeat if needed until the account is fully gone.

Clear the Microsoft Authenticator app cache

• Close Microsoft Authenticator if it is open.
• Press and hold the Microsoft Authenticator app icon.
• Open App info.
• Go to Storage usage.
• Under Cache, tap Clear cache.

Verify the local cleanup result

Reopen Microsoft Authenticator and confirm that the old account entries no longer appear. If notifications still arrive after the local account and cache are cleared, the remaining issue is most likely the organization-side MFA registration.

Removed from the app does not mean removed from Microsoft 365

If Microsoft Authenticator still sends approval requests for deleted work accounts, the most likely cause is an MFA method still registered in the old tenant. Clear any leftover Android account data first, but expect the lasting fix to come from a tenant admin or Microsoft business support.

Use WPS Office as a Free Microsoft Office Alternative

Use Word, Excel, and PPT for FREE

Free Download

Backend reset is the real fix

If the old tenant still trusts that device for MFA, only an admin reset or Microsoft business support can remove the cloud-side dependency.

No local editor can change tenant MFA

This is a Microsoft 365 account-service setting. A document app or local office suite cannot remove Microsoft cloud authentication bindings.

Best verification check

After admin-side removal, wait for normal sign-in activity on the old account. If no new prompts reach the device, the stale registration was successfully cleared.

Where WPS Office fits in this scenario

WPS cannot repair Microsoft-side accounts, tenant MFA, billing, licensing, or Microsoft Authenticator controls. If you only need to keep working with local documents while the Microsoft 365 account issue is being resolved, WPS Office is a free, lightweight option for DOCX, XLSX, PPTX, and PDF files with a familiar ribbon-style UI, PDF tools, and WPS AI features for drafting, summarizing, and rewriting.

Compatibility is generally strong for common Office formats, but advanced Microsoft 365 cloud features, tenant policies, and some complex layout or macro scenarios may not behave exactly the same. Use it as a practical local-work alternative, not as a fix for the authentication binding itself.

Stop Microsoft Authenticator Prompts for Removed Accounts FAQs

Why do approval prompts continue after an account is removed from Microsoft Authenticator?

Removing an account from Microsoft Authenticator may not remove the MFA method registered on the organization's side, so push requests can still be sent.

What should be done for a Microsoft business or education account?

Ask the tenant administrator to reset the account's authentication methods, or contact Microsoft's Data Protection or business support team if no admin access is available.

Can I stop these notifications myself if I no longer have access to the old work account?

Only local cleanup is available on the phone. If the backend MFA method is still registered and you cannot sign in, an organization admin or Microsoft support must reset or remove it.

Does clearing cache in Android permanently remove the Microsoft 365 authentication binding?

No. Clearing cache only removes local app data remnants. It can clean the device view, but it does not guarantee that the Microsoft 365 tenant has removed the MFA method.