Using Classic Outlook on Windows for personal email, calendar, and contact management
Thanks, this solution worked for me, Ive deleted the 2 folders, same error on the first time connection, and after all is working.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
When I try to add a new Office 365 email to my outlook I get the error below. I think it's because of my "Work or school account" which I want to remove. I'm not sure how my email was signed up for this second account. I set up this computer for home use only, I won't be using any of the Microsoft Azure features.
My question is, what will happen when I remove my “work account” and leave my Microsoft account? Everything is backed up on Onedrive, I just don’t know what to expect because when I went to remove it, it warned me about losing data and settings.
Any help would be appreciated. Thank you!
Using Classic Outlook on Windows for personal email, calendar, and contact management
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.
Thanks, this solution worked for me, Ive deleted the 2 folders, same error on the first time connection, and after all is working.
I managed fix the issue by going into the program folder and running the scanpst.exe. Soon as I closed Outlook and ran the exe the error is no longer being generated when signing into Outlook.
This is not a fix. It's a workaround. And a sloppy one that will cause you issues in the future. You're basically relaxing your security settings.
We are having this same issue. This is what fixed it for us. Create the following registry entries.
[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity "DisableADALatopWAMOverride"=dword:00000001
[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity "DisableAADWAM"=dword:00000001
This did the trick for me!!!
Thank god something so simple actually worked for once, just signed out of the account and re-signed in and it stopped showing the error.