This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
Myself and others would just like to say we are very grateful for all of you taking the time to run these tests and explain all the steps you've gone through in order to try to solve this issue. I've been following this thread for weeks now and it does seem that we are getting towards a better place.
Thank you all
Update for everyone regarding our setup in case someone is running into something similar...
Past Setup
This setup was a functional 1001 workaround for us for a week or so, but suddenly started locking people out of Outlook with an authentication loop. Signing out of Word then back in wouldn't fix. Moving to another RDSH didn't fix. We had to move people to OWA for a bit until we made some changes. My best guess why this behavior started was that Microsoft was changing things on the backend to try and fix the issue, but older versions of Office (March 2023) builds didn't like these changes. I'm guessing this because we started having these authentication issues around the same time others on this forum started posting about the issue going away on its own and having made no changes. Any other older Office users see the same thing?
Current Setup
- (NEW) Microsoft 365 Apps for Business (x86) 16.0.16827.20166
After upgrading Office, running Windows updates (nothing significant), and implementing all of Microsoft's recommended workarounds, things are better but not perfect. 1001 and WAM errors have been gone for 3 days now, but some, not all, users are prompted to sign into Office every time they open a fresh RDSH session. Ironically this was the original issue that started my troubleshooting of 1001 errors; however, I'm so fed up and burnt out on babysitting this RDS environment that a daily login for users is a vast improvement for me. I can't care anymore if Microsoft isn't going to care...
My current plan is to give this "fix" more time to settle and update everyone once we have 1-2 weeks of no authentication issues (other than being prompted each login). After X time, we will revisit the daily re-authentication issue; in the meantime, hopefully we can coast until Microsoft puts out a fix.
We have the exact same behaviour on six Server2019 RDS Servers in a farm and some users getting this error every day. We just guide them in to one of the other servers.
Really hope MS take this error more serious and provide a fix!
Unfortunately, I tried the NoDomainUser key but I was still able to get the error 1001 after deleting these folders and opening up outlook:
The 4th step provided by Microsoft support to you appears to be contradicting with the "Roam Identity" key. Excluding the AAD Broker Plugin and Token Broker folders defeats the purpose of the "Roam Identity" registry key, isn't it?
To add to this, you appear to still be using older version of FSLogix.
Lastly, to everyone else, after FSLogix upgrade and enabling Roam Identity, we've experienced less cases of error 1001 but we still get it like once a week. Fix is to delete the 5 folders mentioned above and sign them out and back in to the RDS.
Hello Guys
My update since 1 Week and more no more issue with 1001 Error after we downgraded the Office.
But i forget one important point pay attention if you use the config.xml on the :
16.0.16026.20200 -> MS Teams is not included ;)