Troubleshooting details

Hi @Dinesh T,

Please understand that our forum is a public platform, and we will modify your question to cover your personal information including your ID in the description. Please notice to hide these personal information next time you post error to protect personal data.    

I have moved the information to the Private message if you need to add any more privacy information please add it in there.

Regarding your issue, this usually means that Teams is having trouble using saved sign‑in information on the device. It commonly happens after a password change, device change, Windows update, or when cached credentials become out of sync. 

Here are a few steps you can try: 

1. Repair Windows Account Manager (WAM).  

To re-register the authentication broker component, open Windows PowerShell by typing PowerShell in the search bar, then right-click and select Run as administrator. Copy and paste the following command for work or school accounts:  

Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode –ForceApplicationShutdown

Press Enter and wait for completion. After that, run this second command:  

Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode –ForceApplicationShutdown

Once both commands have finished, close PowerShell.  

For more details, please refer to: Can't sign in to Microsoft 365 desktop applications

2. Remove the Account from Windows  

• Go to Start > Settings > Accounts.  
• Select Access work or school.  
• 
• Find the account associated with the error and click Disconnect. 
• 
• Restart your computer.  

3. Clear the Windows Credentials Manager  

• Open the Control Panel and go to User Accounts > Credential Manager.  
• Select Windows Credentials.  
• Remove any Microsoft/Office‑related credentials. 
• 
• Restart your PC and try signing in to Teams again.  

Hopefully it will help work with your issue and if you have any other questions or need further assistance, feel free to ask.  

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".    

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

The error details provided (Correlation Id, Timestamp, DPTI, Tag, Code) are diagnostic identifiers only and cannot be used directly to resolve the issue without access to the service’s logs and backend tools.

For Microsoft 365 services such as Microsoft Teams, the correlation ID and timestamp are used by support or administrators to trace what happened at the time of the error in the service logs. They do not, by themselves, describe the cause of the problem or provide a client-side fix.

To proceed:

1. If this is in a work or school environment:
   • Provide the Correlation Id, Timestamp, and error message to the organization’s IT/admin team.
   • The admin can use these values when opening a support case with Microsoft or when reviewing tenant logs and telemetry.
2. If this is in a personal/consumer context (no IT admin):
   • Collect the Correlation Id, Timestamp, and the exact action being performed (for example, signing in to Teams mobile, joining a meeting, sending a message).
   • Open a support request through the Microsoft 365/Teams support channel and include these details so support can look up the failure in backend logs.

The correlation ID and related fields are intended as “breadcrumbs” for administrators and Microsoft support to trace the failing request; they do not map to a public error catalog and cannot be troubleshot solely from the client side.

References:

• SharePoint Correlation ID in error messages: what it is and how to use it
• Microsoft Q&A Correlation Id: