Approximately 4 days ago I began experiencing problems with OneDrive and Microsoft 365.
I can load the OneDrive website with no problems. I cannot, however, create new documents or load existing documents.
Doing so results in the attached screenshot.
This happens with shields, and without shields on. It also happens in Private windows.
It also happens with or without any extensions installed or enabled.
It seems to be specific to the latest build of Brave. [Brave 1.80.115 (Official Build) (64-bit)]
Chromium: 138.0.7204.97
I have checked this same situation in Google Chrome (which I hate), and it works flawlessly, so this problem is unique to Brave only.
I have spent close to 2 hours trying various suggested options found online, and using ChatGPT to suggest things that I might not think of, but all to no avail.
While I wait for the Brave team to fix this, is there a way for me to downgrade to a previous version of Brave?
The only way I could get to OneDrive personal was by opening a Brave private window and typing in the url.
But, it needs to be fixed–it has been too long for it not to work in regular Brave.
Thank goodness someone else is experiencing the same problem. I’ve failed multiple ways trying to get this to work. The links still work in other browsers so hopefully the brilliant minds behind the scenes can get this working again.
I’ve been unable to open or create files using OneDrive or Office.com in Brave for over a week. The interface loads, files display, but clicking to open/edit results in failure.
Conclusion:
This appears to be a server-side change by Microsoft that breaks OneDrive/Office functionality in Brave, possibly due to telemetry endpoints or unsupported browser detection.
Today, 8 days after making my original post, I finally solved the mystery!
The problem turned out not to be Brave, but Avast antivirus.
It was a long process of elimination to figure it all out, but the HTTPS scanning in Avast was blocking the HTTPS requests in Brave and causing OneDrive not to open or create files.
I simply disabled the HTTPS scanning and the problem instantly went away.