Anyone faced the following error when opening Office365/OneDrive in the past and got a permanent fix by any chance: 58tm1 or 4nsvw

Permanent? No, but rebuilding the AAD.BrokerPlugin fixes it for quite a while.. I can provide more information later if needed, swamped at the moment.

Could be interested yeah We never faced it, and since 1 month, it's hitting us hard

Add-AppxPackage -Register  "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown

Run as the user should reset the AAD.BrokerPlugin folder with all Office applications shutdown.

remove-item $env:localappdata\packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\ -force -confirm:$false -Recurse

Sometimes have to remove everything first. Also had a client where they were getting slammed with these as well and the resets weren't working because the AppX deployment Service would hang. Running the first reset command would not get past the first step. Killing the service and restarting the reset command allowed things to work again. I built a monitor and reset process for them.

would it work for multi-session as well? Does it mean the user must log again in Office?

It does work in multi-session. We use multi-session here. Yes, the user must log back into Office afterwards.

Got it, thanks Dennis. We would impact all the users with the script, this is something we would like to avoid because some users just close the sign-in window and then complain having a license issue. With the number of users we have, would be a nightmare to manage this, even communicated ahead.

The Add-AppxPackage -Register ... should be run per user. It only applies to the user that runs the command.