Microsoft Team Error CAA50021 - Resolution requested

Sam M Franklin 6

Hi Team,

 Microsoft Team reports the following error on system running Windows 10 Pro.

 Error Code: CAA50021


 Resolution would be appreciated.

Best Regards,
Sam

Sharon Zhao-MSFT 25,051 Reputation points Microsoft Vendor

2020-08-07T10:05:30.32+00:00

Do you find the solution for this issue?

If there is any news, please feel free to share with us.
Stéphanie Lemejouk Sonfack 21 Reputation points

2022-10-11T15:24:53.227+00:00

I encountered this same problem with one of my users for at least 2 weeks after enabling multi-factor authentication.
On Azure Ad Online, I noticed that the user was not attached, but I could see that the user's account had been added to the Microsoft accounts under E-mails and accounts and also Professional or School Access

Here are the steps I did:

1- open cmd in admin and type: dsregcmd /debug /leave
2- In the console https://admin.microsoft.com/, users, I selected the user and disconnected him from all sessions on the devices he was using
3- On his windows computer, I disconnected him again from office365 online and I deleted all his work accounts (on the computer)
4- Under the "Generic IDs" section, search for msteams_adalsso/adal_context_segments and right click and delete this generic ID.
5- Update the computer from 1809 to 21h2 and update the antivirus.
6- Restart the computer
7- Reconnexion of the user, everything works, there are no more errors.
dmc 0 Reputation points

2023-10-07T03:34:25.0733333+00:00

I was able to FINALLY get 365 working again. After forcing a logoff FOR ALL my microsoft 365 accts (my COMPANY and my personal protonmail acct), that fixed my issue. I was able to get 365 working for my COMPANY acct again

11 answers

The 5th's Pledger 70 Reputation points

2023-06-29T12:41:30.28+00:00

I tried the answers here but neither worked. What actually worked out for me was:
dsregcmd /cleanupaccounts

After that I had to login again in all my WAM accounts (Default account was not affected). Also didn't need to reboot the machine.

To me, it's clearly a conflict between the organization managing your device and some other WAM account running in the machine. Could've been triggered by an organization level change (but I can't confirm that).

PS: When relogging I chose the account that was having issues first and the others afterwards. Not sure if it would've worked if I redid my other WAM accounts first, so keep that in mind.

PS2: If you're not sure which is your Default Account, you can run

dsregcmd /listaccounts

and read the last line.
Please sign in to rate this answer.

14 people found this answer helpful.
Martijn (Logiza) 10 Reputation points

2023-08-02T10:13:56.0233333+00:00

Thx! Running the cleanupaccounts command in an elevated PowerShell solved my issue with signing in to MS Teams for work/school.

Pedro de Freitas Moreira 0 Reputation points

2023-08-03T22:20:06.92+00:00

Everything he'd done so far hadn't worked.

Your solution was perfect for my problem.

Thanks a lot, you saved me.

Peter Moreira.

André Luís Rodrigues Ferreira 0 Reputation points

2023-08-08T12:50:13.31+00:00

Also works on OneDrive! Thanks!

Thiago Mendes Pereira 0 Reputation points

2023-08-16T15:44:08.6233333+00:00

Also works in outlook ans teams issues with this kind of account. Thanks.

H. Nguyen 0 Reputation points

2023-09-19T13:26:10.4166667+00:00

Thanks a lot! I have this issue for a week now. I've tried several things. Cleanupaccounts finally solved the problem.

magina.li 李志伢 0 Reputation points

2023-09-21T10:14:20.2633333+00:00

So good!

Guillaume Nicolas 0 Reputation points

2023-10-04T19:31:43.26+00:00

Thanks! I spent 2 hours without success, before I tried your solution. It solved immediatly the problem. I used :

dsregcmd /cleanupaccounts

and I opened Word, I connected with my account without problem.

No reboot necessary.
Sign in to comment
Derek Webber 31 Reputation points

2021-09-22T15:01:22.19+00:00

Have you tried re-registering the device with Azure AD?

On the device run this cmd as admin

dsregcmd /debug /leave

Reboot

dsregcmd /status
Please sign in to rate this answer.

6 people found this answer helpful.
nd5 11 Reputation points

2021-11-04T02:28:43.717+00:00

Thanks, this seems to have resolved the issue. I had to re-add the users microsoft account after rebooting but they no longer had errors when trying to log into teams and outlook.

Henson, Anthony 21 Reputation points

2021-11-11T16:27:56.207+00:00

Solution and likely root cause.

The above solution worked for me as well!

@Derek Webber Thank you!

**> On the device run this cmd as admin

dsregcmd /debug /leave

Reboot

dsregcmd /status**

The machine will need to become Hybrid Joined to Azure again, which depending on your Azure Active Directory sync, can take a while depending on scheduling or bulk of the scheduled sync.

Possible Root cause
Based on my research of the issue, the root cause seems to be a very recent security patch, I have not verified which one yet, but it was recent near the beginning of november. Possibly the October Security patch.

This is a concerning issue for me, and probably many.

Thank you for this collaboration!
Tony

SIAPO Andrea Geraldine 1 Reputation point

2022-11-29T22:57:49.007+00:00

Thanks, it works.

Chris Judson 5 Reputation points

2023-07-17T16:10:42.0966667+00:00

I have used this solution for the very first time on a user who had returned to the business after being off on Maternity leave....it worked first time after rebooting! i am exceptionally greatful to you sir for posting this. I was nearly having to replace her desktop so you have saved me hours of time!

Vinayak Gunjikar 0 Reputation points

2023-10-30T07:43:50.1333333+00:00

If you run command dsregcmd /debug /leave, your security policy will be collapsed and your organisation will not be able to manage your machine through intune.

But you can remove the machine from the domain to work group - restarat machine and then reconnect to the domain the issue will get resolve.
Sign in to comment
Demetri 16 Reputation points

2020-11-26T17:17:22.86+00:00
I had this issue for two days. I have several Microsoft accounts that I use and access for my business using a Surface. I completed the following steps to sign out of all my devices and no longer receive the Teams login error.

Open Microsoft outlook and signed out of all accounts except for your primary account (the one you use to login to Teams with).

Accessed my computer settings and selected "Accounts". Then I selected "Email & Accounts". Under the heading "Accounts used by other apps" I selected my primary account and clicked on "Manage". From there a separate webpage opens up (ttps://account.activedirectory.windowsazure.com/r/#/profile). On the right side of the webpage there is a link to "Sign out everywhere". Once you click on this link a message box pops up and requires confirmation that you want to sign out of all devices. I selected yes. I haven’t had an issues since. I hope this helps.
Please sign in to rate this answer.

3 people found this answer helpful.
Kaveendra Ukwattage 46 Reputation points

2020-12-18T17:06:11.197+00:00

I also got this error few days back. When I checked in Azure AD, the device was registered.
However when I checked from device side it said not connected to azure (dsregcmd /status in cmd).
Then went to Settings -> Accounts -> Access work or School
In there the Microsoft account is visible. above the account there is Connect option. In there you have two options to connect the device to Azure.
The issue did not came back again.
Hope this will help anybody

Henrique Alexandre da Silva Santos 6 Reputation points

2021-04-20T12:04:11.567+00:00

It works, thanks!!! =)

iRoberto 6 Reputation points

2021-05-19T21:49:49.72+00:00

OOOOOOOHHHH MY!!!
After searching all over for this problem where people suggested invasive solutions,
this actually worked seamlessly and it was so simple.

THANK YOU SO MUCH!

iR

Elisabeth Ebert 1 Reputation point

2021-08-19T18:23:07.76+00:00

Thank you so much! Great and easy to solve.

Fadhilatul Aulia 1 Reputation point

2021-10-21T10:34:04.327+00:00

Thank you so much :)

Fadhilatul Aulia 1 Reputation point

2021-10-21T10:35:03.923+00:00

Thank you so much :)

Shoaib Nawaz 1 Reputation point

2022-09-15T15:11:18.333+00:00

Thanks for the solution. In my case, there are two O365 users account were connected.
I disconnected both users and connect the correct user. Issue resolved.

Paul Brindusa 1 Reputation point

2022-12-13T16:02:50.64+00:00

Spot on ! well done, you have just saved our desktop team a lot of time in re-imaging machines.

Like someone commented, compared to other workarounds this worked like a charm.

John Breen 0 Reputation points

2023-04-21T13:38:59.54+00:00

Brilliant, thank you Kaveendra
Sign in to comment
Emīls Lipkovs 15 Reputation points

2023-07-18T04:53:04.87+00:00

We have a hybrid setup with local ad for windows authentication and azure ad for email.

What helped for me was to remove the ms account from Access work or school in windows settings, then revoke all sessions in Azure AD. After this was able to log in web outlook and also on the windows app.
Please sign in to rate this answer.

3 people found this answer helpful.
Xavier Bouchard 0 Reputation points

2023-08-11T14:30:53.7233333+00:00

Best answer!!

WhatAmIDoingWrong 21 Reputation points

2023-08-29T13:57:25.4666667+00:00

This worked for me too. Thank you!
Sign in to comment
Shaun Sell 11 Reputation points

2021-01-11T14:15:01.047+00:00

Had this issue where even office doesn't work anymore. Fix for me was to redo the windows account.

Steps:
Removed user under user accounts on control panel
Removed the Profile list under registry
restarted and added ad user again to computer accounts with administrator rights as before
logged in to the account and was able to activate office and login to teams without issues.

Hope this helps.

PS. I didn't get the root of the problem just a quick fix
Please sign in to rate this answer.

2 people found this answer helpful.

0 comments No comments
Sign in to comment