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)
In Windows 10 when I open or work with mail in the Outlook desktop app (local installation) the message no access keeps coming up.
Then I get a message that I have to select continue to sign in to this account, or manage to remove the account.
Then the message something went wrong, try again later 0x80049dd3 comes up.
I can then select send feedback or cancel as I choose, and then I get logged in and can continue working.
Can something be done to get this away, so that I don't often get interruptions with this?
Is it a known bug, and/or could it pose a security risk?
***Moved From Windows / Windows 10 / Security and privacy***
Using New Outlook on Windows for professional communication and productivity
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.
I Am Having The Same Issues On Windows 11 Desktop Getting error code 0x80049dd3 . Hope You Can Fix It Soon. Is This a Security Risk.! ?.
If it is happening on Windows 10 and 11, it does kind of rule out the update causing it, unless they both have an update that is very similar.
I do wonder how people with this problem use passwordless login for these accounts.
Good point. I use passwordless login and had this issue for the first time today. (Windows 11 Pro)
i am getting the exact same problem with my windows 10 laptop and also my windows 11 latest version desktop. Extremely annoying
I've unlocked the PC using a Microsoft account password and the issue is still there. So far, this issue is not mentioned on the global status page: https://admin.microsoft.com/servicestatus though.