Some users’ Microsoft Teams clients may freeze when attempting to access the Teams menu in the sidebar

Title: Some users’ Microsoft Teams clients may freeze when attempting to access the Teams menu in the sidebar

User impact: Users’ Microsoft Teams clients may have frozen when attempting to access the Teams menu in the sidebar.

More info: Users received an unexpected error message stating “You don’t have access to this channel. Contact the owner … to get access.” despite having proper permissions. If users didn’t receive this error message, it wasn’t related to this event and needs to be investigated independently.

This could’ve affected users on both the web and desktop clients running the new Microsoft Teams. While we were focused on remediation, users may have been able to avoid impact by utilizing the Microsoft Teams classic experience.

Impacted users may have been able to resolve the frozen client issue by proceeding with the following steps:

1. Sign out of Microsoft Teams.
2. Completely close out of the Microsoft Teams client by right-clicking on the system tray and hitting “Quit Teams”, or by closing the browser window.
3. Reopen the Teams client and sign back in

Final status: We’ve completed our deployment of the fix to the affected environments, and we’ve verified with affected users that this solution has successfully remediated the problem.

Scope of impact: Some users attempting to access the Teams menu through the sidebar in the new Microsoft Teams web and desktop clients may have been impacted.

Start time: Tuesday, March 26, 2024, at 5:09 AM UTC

End time: Thursday, April 25, 2024, at 10:44 PM UTC

Root cause: A recent service update introduced an issue where users’ default channel information wasn’t being called as expected in the new Microsoft Teams, resulting in impact.

Next steps:
– We’re investigating how the recent service update introduced an issue where users’ default channel information wasn’t being called as expected in the new Microsoft Teams to prevent this problem from happening again.

This is the final update for the event.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *