Microsoft 365 features that help users manage their subscriptions, account settings, and billing information.
You've already done a very thorough local cleanup. The detail that matters most is that it also fails on a brand-new laptop and for a new local Windows user. That rules out your profile, caches and Office install. When browser sign-in works but the Windows sign-in broker (the AAD/WAM log you found) gets invalid_grant / AADSTS9002313 on every device, the token request is being rejected on the identity side, for your account or by your university's sign-in policies. Nothing more on the laptop is likely to fix it.
What I'd do next:
- Send it to University of Calgary IT, not Microsoft. Only the school's Entra admins can open their sign-in logs, search by your correlation ID and timestamp (you already have both), and see which policy or account setting rejected the desktop request. Policies like Conditional Access, device compliance or token protection often block desktop apps while still allowing browser sign-in.
- Give them exactly what you posted here: AADSTS9002313, the event 1098/1097 errors, the timestamp, and the note that it fails on two laptops and a new local user. That saves them a lot of back-and-forth.
- In the meantime, use Word and Outlook on the web (office.com), which you've confirmed still work.
Please keep sharing the correlation and trace IDs only with your IT team, not publicly.
Did your university recently ask you to re-register for MFA or enrol your device, or did this start without any change on your side?
If your IT team finds the cause from the logs, please consider accepting this as the answer. If they find nothing on their side, let me know and I'll be happy to keep helping.
Reference: