Forum Discussion
Excel Power Query / Analysis Services authentication fails after reopening workbook
Hi BIscoverer ,
Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.
Thank you for your understanding and assistance.
Best Regards,
Community Support Team.
Hi v-menakakota,
I have a significant update. I've since been updated to Version 2602 (Build 19725.20170), which is the same version my colleague is on. The issue persists for me, but not for him. To isolate further, we ran a test: my colleague logged into my laptop with his account and tried to refresh the same workbook (shared via OneDrive). He experienced the exact same failure: credentials work after manually re-entering them, but the token doesn't persist across sessions. On his own laptop, the same file refreshes without any issues.
This confirms the problem is machine-specific, not tied to user profile, Excel version, file, or AAS configuration.
Could you recommend additional steps on how to resolve this?
Hi BIscoverer ,
I think the Excel is reusing a stale Entra token from the Windows/Office auth layer (WAM) and not triggering a fresh sign-in, which is why it fails after reopen but works after clearing credentials.
Reset the local identity cache, not just Power Query credentials, sign out of Office, clear Credential Manager (Office/ADAL/Azure entries) and delete the Office identity cache folders (Identity / OneAuth). If it still fails, run an Online Repair or test with a new Windows profile.
Best Regards,
Community Support Team.Hi v-menakakota ,
Thank you for the response.
I have already gone through most of these steps. I've cleared credentials in Data Source Settings, cleared relevant entries in Credential Manager, performed a full Office sign-out/sign-in cycle, and had Office completely reinstalled on this machine. None of these resolved the issue persistently: credentials work after manually re-entering them, but the token does not survive a close/reopen cycle.
Hi BIscoverer ,
From what you are telling me, I think this maybe Windows auth layer (WAM) or a machine-level policy/security component interfering with token persistence. At this stage, the only meaningful checks left are to disconnect/reconnect the Work or School account in Windows, test with a new Windows profile and compare any endpoint security or GPO differences with the working machine. If it still persists, I suggest the issue with Microsoft as device level SSO/WAM issue.
Best Regards,
Community Support Team.