Hi DonsterG,
Welcome to Microsoft Q&A.
For classic Outlook for Windows, Microsoft documented that many [4usqa] sign‑in errors that started around May 7, 2025 were caused by a backend service configuration issue (a disabled service principal for the Microsoft Information Protection API).
Microsoft implemented a service‑side fix on May 14, 2025, so for most users, fully closing and restarting Outlook is enough to pick up the change.
For reference: Errors CAA2000B, 4usqa, and 49dvs when trying to sign in to classic Outlook and Outlook for Mac
What to try (home users):
- Fully close Outlook (right‑click Outlook in the taskbar > Close, and if needed end
OUTLOOK.EXEin Task Manager), then restart Outlook. - Make sure Windows and Office are fully updated, then reboot once.
- If it’s still happening after multiple restarts, local sign‑in data can sometimes contribute. Try clearing saved Office/OneDrive credentials in Credential Manager, then sign in again.
If you’re using a work or school mailbox: The same article also lists an admin‑side resolution (re‑enabling sign‑in for the Microsoft Information Protection API in Microsoft Entra), which requires an IT administrator.
If you can paste the exact last line of the error dialog (in quotes) and confirm whether this is a home or work/school account, I can point you to the most appropriate next step.
Please let me know if this proves useful to you, or if you would like further assistance.
I'm looking forward to your reply.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment”.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.