Using Classic Outlook on Windows for personal email, calendar, and contact management
Yes I have the same issue windows!
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello,
We encounter an issue with M365 apps (Outlook, Work, Excel) on a specific environment ( Remote Desktop Service)
Sometime, when an user open his application (Outlook for instance) on a RDS, an authentification pop and ask for credentials. If the user enter his credentials, he encounter a 1001 error.
« We encountered an issue [1001] »
https://learn-attachment.microsoft.com/api/attachments/5a947921-955a-4688-ad93-acc305bf77c6?platform=QnA
We already try some step to resolve the issue that help in some case but not all the case, and not defintely for a same user ( Issue occur again) :
The main issue is that the error can occur again few day laterfor the same user.
We also generate some log from M365 apps client during the signin process with this link to help : https://learn.microsoft.com/en-us/office/troubleshoot/diagnostic-logs/how-to-enable-office-365-proplus-uls-logging
In the log I find the reference to the 1001 error but the log is a bit complex to understand or analyse.
0xa3e4 Microsoft Outlook Identity Authentication Client 48cmb Monitorable OneAuth log {"Message": "[MSAL:0004]\tERROR \tErrorInternalImpl:134\tCreated an error: 58tm1, StatusInternal::Unexpected, InternalEvent::None, Error Code 2147942403, Context '(pii)'", "IsError": true}
07/07/2023 09:04:21.440 OUTLOOK (0x8b30) 0xa3e4 Microsoft Outlook Identity Authentication Client 48cmb Monitorable OneAuth log {"Message": "[OneAuth:Error:58tm1:db6d7d6e-a557-4465-a968-a874c5e456e5] (Code:1001) An unexpected error occurred.", "IsError": true}
07/07/2023 09:04:21.440 OUTLOOK (0x8b30) 0xa3e4 Microsoft Outlook Identity Authentication Client 48cmb Monitorable OneAuth log {"Message": "[OneAuth:Error:9vdpp:db6d7d6e-a557-4465-a968-a874c5e456e5] Unexpected error code: 1001", "IsError": true}
Environment :
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.
Yes I have the same issue windows!
So a few things. I haven't read all 18 pages of reply's but i wanted to post a few things that seem to work here.
1.) We've tried "revoke sessions" in Azure (this seemed to work for 1 user has anyone else tried?) it did take a little while though. Not quite sure if it was the fix. (we will be trying again next time it shows up)
2.) I did see mentions of logging into last "sever" we had users login to the last PC they were on, our environment is individual PC's. Then sign-out again. This seems to of resolved the issue when logging into the new PC they were visiting. (leading me to suspect that OneDrive (our issue) has a hanging session or something tied to the original PC and their signoff didn't close it out properly. <Just logic nothing more) This does seem to line up with a few others on this thread.
Note: we have the PC reboot after a users signs out of windows so no reason they should be logged in elsewhere... (you never know though)
I haven't seen anything besides OneDrive as of today and it JUST started happening to us last week.
We had an issue in our Citrix Xenapp virtual Desktops environment, with Outlook and other O365 Office applications. Where it would prompt for login, followed by some other errors/prompts. Also, there was a yellow banner in Outlook “RESTART REQUIRED Restart Office to apply changes to your privacy settings”. This would happen every time after a fresh Citrix login, subsequently opening Outlook worked fine, but the issue reappeared after a fresh Citrix login again.
I found that including the folder AppData\Local\Microsoft\OneAuth to sync with the roaming profile, resolved the issue.
Though it may work, the reason I didn't push this is for security and also to find a permanent fix. Appreciate the suggestion though!
We are now investigating a solution that involves blocking the 'WorkplaceJoined' option by adding the following registry keys:
I have deployed those registry keys 2 months ago thinking it would help resolve the issue but it still persisted.