Error Code CAA50021

Question

Good Afternoon,

I am unable to sign into any of my Microsoft Desktop apps. When I attempt to open the app, it asks me to sign in through my work account and after I successfully enter my name & password, the message "Hold on while we register this device with your company and apply policy. This may take some time" appears. After some time, the error message returns "We couldn't sign you in. If this error persists, contact your system administrator and provide the error code CAA50021."

I have already checked with my work administrator for issues on that end, uninstalled and reinstalled apps, signed out and tried to sign back into apps, and enabled the "Automatic-Device-Join" feature in Task Scheduler.

What am I missing?

Answer 1

I lost access to my desktop microsoft apps as well. Wednesday 11/22 everything worked when I logged off and shut down. Then when I went back on Friday 11/24 I have been trying to fix this issue. Hopefully someone helps. I've run every single one of the suggestions above. I can access everything through a web browser.

Answer 2

Hello Ms. M,

Unfortunately, I'm really sorry I don't have any further troubleshooting to offer.

There are many knowledgeable users active on the forum and I hope that someone else can offer further insight into your issue.

Thank you, Ibhadighi

Answer 3

Thanks so much Ibhadighi,

Unfortunately, after applying your suggestions and contacting my IT department, I am still having the same issue.

Answer 4

Hello Ms. M,

I'm Ibhadighi and I'd happily help you with your question. In this forum, we are Microsoft consumers just like yourself.

The error code CAA50021 you're encountering with Microsoft Desktop apps is typically related to issues with Azure Active Directory (AAD) registration or device management policies. Since you've already checked with your work administrator and attempted common troubleshooting steps like reinstalling apps and adjusting settings, here are some additional steps you might consider:

1. **Check Device Registration Status**:
   • Ensure your device is properly registered with Azure Active Directory. You can check this by going to the "Access work or school" settings in Windows and seeing if your device is listed under your organization's account.
2. **Examine Group Policy Settings**:
   • Sometimes, group policy settings might restrict or affect the device's ability to connect to AAD. Verify with your IT department that the appropriate group policies are applied.
3. **Internet Connectivity and Network Restrictions**:
   • Ensure your internet connection is stable. Sometimes, network policies or firewalls can block the necessary connections for AAD registration.
4. **Update Windows and Office Apps**:
   • Make sure your Windows operating system and Microsoft Office apps are up to date. Pending updates can sometimes cause compatibility issues.
5. **Clear Credential Manager**:
   • Go to Windows Credential Manager and remove any stored credentials related to your work account. This can sometimes resolve conflicts.
6. **Check for Azure AD Connect Issues**:
   • If your organization uses Azure AD Connect, there might be synchronization issues. This would typically be something your IT department would need to investigate.
7. **Review Azure AD Conditional Access Policies**:
   • Conditional Access policies set in Azure AD can sometimes cause these types of issues. Confirm with your IT department if any Conditional Access policies might be affecting your device.
8. **Check for Multi-Factor Authentication Requirements**:
   • If your organization requires Multi-Factor Authentication (MFA), ensure it's properly set up and working for your account.
9. **Review Event Viewer Logs**:
   • Check the Event Viewer on your PC for any related error messages or logs that can provide more insight.

Please note that since this is a work account, many of these steps might require coordination with your IT department, as they have administrative control over many aspects of your organization's Azure AD and device management policies.

I hope this helps.

Best Regards, Ibhadighi