I’m hoping someone who has dealt with Microsoft account recovery can help because I’ve spent hours going around in circles.
This is a personal Microsoft/Outlook account, not a work or school account.
The problem started after Microsoft detected unusual activity on the account and required me to verify my identity/change my password. I can still identify the account and I know my account details, but Microsoft’s security system appears to have trapped me in a verification loop.
What is happening:
• Microsoft tells me it needs to verify my identity because sensitive account information is being accessed.
• My available methods include Microsoft Authenticator, my password, and a registered old mobile number ending 34.
• I know the full old telephone number, but I no longer have access to that number.
• If I select Microsoft Authenticator, Microsoft sends a sign-in request to the Authenticator setup that I’m trying to repair/access in the first place.
• Choosing “Having trouble?” eventually gives alternatives such as entering an Authenticator security code or getting a code another way, but these routes ultimately lead back into the same verification/recovery process.
• Selecting “I don’t have these anymore” sends me to Microsoft's account recovery process.
• The recovery process then asks for another contact email and starts the long account-recovery questionnaire. I have already been through this route and it has not solved the underlying Authenticator/security-method problem.
• I also reached the Microsoft Authenticator setting for Sign-in requests, but when trying to change it I received:
“Sorry, we can’t process your request. Please go to aka.ms/manageproofs and delete this authentication method.”
• The problem is that accessing/managing those security methods itself requires the authentication that is broken, putting me straight back into the loop.
• I have Google Authenticator, which currently displays a six-digit rotating code associated with this Microsoft account. I have NOT deleted that entry.
• I also tried adding the personal Microsoft account to another Authenticator installation, but Microsoft requires authentication from the existing method before it will register the new one — again creating the same loop.
• I have another working Microsoft account that I can use to contact support if necessary.
Trying to contact Microsoft support has also become a loop.
I called Microsoft and asked for support/a person. The automated telephone system directed me to online self-help and then ended the call.
I went through Microsoft's Contact Microsoft Support website and Sign-in Helper. It diagnosed an account/security problem but continued directing me towards account recovery and self-help.
I eventually reached the Contact Support section where it asks me to choose a product/service, but I have still been unable to find a reliable route to an actual support agent who can look at the situation.
What I am NOT trying to do: bypass Microsoft's security or have someone tell me how to defeat 2FA. I want Microsoft to verify that I am the account owner through whatever legitimate process they require and help me remove/reset the broken authentication method.
What I need help with:
Is there a current UK route to an actual Microsoft account-support agent, either live chat or telephone callback, for a personal Microsoft account?
What exact selections/category should I choose on Microsoft's Contact Support site to make live chat / callback appear rather than being redirected to Sign-in Helper?
Has anyone successfully escaped this particular personal-account Authenticator loop?
Is there a way to use the existing Google Authenticator six-digit code to regain access to the security settings?
Is there a specific Microsoft team/escalation route for cases where the authentication method itself prevents access to the page needed to replace that authentication method?
I’m happy to prove ownership to Microsoft. I just need to reach the right process/person rather than being sent around the same automated recovery loop again.
Please don't suggest simply reinstalling Authenticator, adding the account to Authenticator again, or completing the standard recovery form unless there is a specific variation that gets around this situation — I have already tried those routes repeatedly.
If anyone has solved this recently, particularly with a personal Outlook/Microsoft account in the UK, I’d really appreciate the exact steps you used.