Hey everyone, I've run into a perplexing issue with my Microsoft account that I think might be more of a system glitch than a typical support problem, and I'm hoping to find some insight.
Back in September 2024, my Microsoft account got hacked. The attacker messed with key security settings like my password and recovery information. Luckily, I was able to regain control of my account the same day through Microsoft's recovery process, which should have fixed everything, right?
However, after about two weeks, my account got permanently suspended for 'Abuse of Services.' Since then, every time I've tried to recover it or appeal the ban, I'm hit with an 'ownership verification failure.' I reached out to support, and they confirmed that my case is still open and has been escalated, but it seems stuck in limbo without any manual review.
From what I can see, this looks like a mismatch in how the system tracks ownership:
- I was hacked, which changed my security details.
- Then I successfully recovered my account, supposedly restoring everything.
- But now, some enforcement action is kicking in, possibly based on earlier data.
- My attempts to confirm ownership are failing because the system can't seem to align old and new information.
I'm not looking for direct help but rather trying to grasp if anyone else has faced similar issues with identity systems post-recovery, if this kind of desynchronization happens often, and whether such systems have a way to reset ownership after conflicting information surfaces. It feels like an odd case where different automated systems (security, enforcement, validation) aren't on the same page. Any thoughts would be greatly appreciated! Thanks!
2 Answers
Totally get where you're coming from. There are many cases in identity systems where enforcement actions aren't swayed by recent activity, especially if there were prior flags against the account. It's a common problem where automated systems don’t talk well enough to each other. Unfortunately, it's usually up to support teams to manually resolve these issues, but unfortunately, that can take time. Keep pushing for updates from Microsoft support!
It sounds like you're experiencing a pretty frustrating loop there. I've seen situations where accounts get stuck in automated processes like that, especially post-recovery. Sometimes, when accounts are flagged, the system fails to update with the new ownership data even after successful recovery, leading to issues like what you're facing. It seems like there’s a disconnect between their enforcement logic and the recovery logs, especially if they aren’t re-checking the current status of the account after a recovery.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures