A Microsoft file hosting and synchronization service.
Dear @Regina,
I am incredibly sorry to hear about the stress and immense frustration this situation has caused you, especially with your exams coming up. I completely understand how critical it is to get your study materials back, and it is incredibly exhausting to be passed back and forth between support teams for months when your data is clearly right there.
Because this community forum operates as a public Q&A platform, I and my fellow moderators do not have backend administrative access to Microsoft’s account databases, servers, or tenant identity systems. Since this issue involves a broken permission binding deep within your Microsoft Account identity token after the primary alias change, it can unfortunately only be resolved by internal Microsoft engineering teams who have the tools to inspect and manually re-bind account security identifiers (SIDs).
I strongly urge you to contact Microsoft Support again, but this time, use the specific phrasing and immediate data-saving steps below to bypass the frontline automated loops and force an escalation.
Before trying anything else, do not log out, clear data, or uninstall OneNote from your Android tablet. Since you mentioned some pages are cached locally, please manually copy and paste that text or take screenshots of those critical study materials immediately. If you log out or reset the app, those cached pages will be permanently lost because the tablet cannot re-authenticate with the server to fetch them again.
When you changed your primary email alias, your unique account identifier (Puid/User SID) remained the same, but the SharePoint/OneDrive resource URL and the internal People Picker cache broke. The notebook path is still looking for the old email's security token.
- The HTTP 403 (Forbidden) and SharePoint Status 400 (Bad Request) errors confirm that the server recognizes the file exists, but completely rejects your new email identity token as an unauthorized user.
- The Error 0x2bdf5f indicates a local sync engine authentication block caused by an identity mismatch.
I know it is deeply frustrating to have to reach out to support yet again, but because this requires backend server manipulation, their specialized cloud engineers are the only ones with the administrative permissions to fix this identity link.
I hope the above information is clear. Thank you for your understanding and cooperation.