Hi Hannish Parayil Gopalakrishnan,
I understand how worrying it is to secure your Hotmail account (password changed and MFA enabled) and still keep receiving unexpected “Approve sign-in request” prompts in Microsoft Authenticator.
I also noticed there is a Q&A Assist answer in the thread. Its core direction (reviewing sign-in activity and securing the account) is generally aligned with the official account-security flow. Have you had a chance to try the Q&A Assist steps yet? If you did and the prompts continue, I would like to add a few key actions.
1, Use the “Recent activity” page actions, not just a password change
On the Recent activity page, you can expand entries and use actions like “This wasn’t me” (when available) and “Secure your account” to trigger the built-in protection flow. This is separate from simply changing the password, and it’s the right place to validate whether any access looks unfamiliar. What happens if there's an unusual sign-in to your account - Microsoft Support
2, Sign out everywhere (force all sessions to re-authenticate)
Even after a password change, previously signed-in sessions may remain active until they are revoked. The account security dashboard includes “Sign out everywhere” under Advanced security options to sign out browsers and apps on trusted devices. How to sign out of your Microsoft account everywhere - Microsoft Support
3, If you have multiple aliases, restrict which one can be used to sign in
If the account has more than one alias, you can block sign-in for specific aliases using Sign-in preferences. This helps reduce unwanted sign-in attempts targeting an older email/alias while keeping the alias on the account. Block an email address from signing in - Microsoft Support
4, Check for app passwords (only if you have older apps/devices connected)
If two-step verification is enabled and older apps/devices are connected, the account may be using app passwords (created under Advanced security options). Reviewing that section can help you identify whether an older device/app is still attempting to authenticate.
5, Treat unexpected codes/prompts as “deny and secure,” not something you must approve
If you receive verification codes or prompts you did not initiate, do not use those codes and do not approve the request. The verification-code guidance explains that unrequested codes can happen when someone is trying to access the account or when information is entered incorrectly, and it points back to securing the account and strengthening sign-in methods.
Please note that this is a user-to-user forum, so there is no access here to investigate the account directly on the service side, but the steps above are the correct self-service security paths for this situation.
I hope this helps you fully lock down the account and reduce those unexpected prompts.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.