A Microsoft file hosting and synchronization service.
Hi, it turned out to be something related to the network isolation & detection of the corporate network as public network.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi all,
We've been kind of stuck here with an issue. We have around 800 devices, mostly laptops, with Windows 10 & Office 2016. 99% is AD-joined, a small test-group running Intune.
We are looking into migrating towards MS 365, specifically OneDrive. We have no issues with upgrading Office 2016 to 365, but when users start OneDrive, it gives errors, specifically:
Some observations: - It happens as well on the same device when someone else logs in (that didn't login in before previously, no userfolder)
And it all seems to come down to the Microsoft.AAD.BrokerPlugin, changing the name or removing the folder from C:\Windows\SystemApps seems to solve the problem, but since it's needed for modern auth, which will become enforced in the future, it's more of a workaround.
What we've tried: - Re-registering the brokerplugin, no results
Re-installing 800 devices is not viable for us, anyone here that has any other ideas?
EDIT Two relevant entries in the event viewer:
A Microsoft file hosting and synchronization service.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi, it turned out to be something related to the network isolation & detection of the corporate network as public network.
Dear J. Zegers
Good day! Thank you for posting to Microsoft Community. We are happy to help you
We understand that you have tried many suggestions. Based on the error information you provided, I am inclined to possibly hook up with the server side. In that case, we kindly recommended you can raise a service request in Microsoft 365 admin center, which the support there has the related permission and resource to help you check from the backend.
Thanks for your cooperation.
Sincerely,
Tin | Microsoft Community Moderator
I am curious if you were able to find a solution for this? We have a few clients who have started to experience this same issue.
(This post is amongst the top search results for the error described, and none other have this level of detail....)