Hello Xintong Mao,
Just following up. Your description lacks the environmental context necessary for a definitive fix. Are you utilizing the classic Outlook desktop client or the New Outlook app, and is this device personally owned or managed directly by the KTH IT department? Instead of immediately purging the global SSO state, the best practice is to isolate and clear the specific Office WAM cache. You can accomplish this by closing Outlook, navigating to %localappdata%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy, and deleting the LocalState folder. Follow this by forcing a fresh interactive prompt by clearing the cached identity string in the registry at HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity\Identities. If you are on a university-managed device, aggressive actions like disconnecting the work account can sever vital management certificates, so please clarify your device management state and client version before proceeding further.
VP