Service issues › TM1545775

Users may be unable to view previously deleted teams after restoration in Microsoft Teams

Resolved Microsoft Teams Teams and Channels advisory
Started
26 Oct 2026 12:53 UTC
Resolved
10 Nov 2026 19:34 UTC
Status
serviceRestored
Origin
microsoft

Timeline & resolution

10 Nov 2026 19:47 UTC · regular

Title: Users may be unable to view previously deleted teams after restoration in Microsoft Teams User impact: Users may have been unable to view previously deleted teams after restoration in Microsoft Teams. More info: As a workaround, changing an affected user's role (member to owner and then back to member) made the team visible for that user. Final status: We've confirmed that the fix has completed across all affected environments and validated this issue has been remediated with service telemetry and affected users. Scope of impact: This issue may have affected any user attempting to view previously deleted and restored teams. Start time: Monday, October 26, 2026, at 12:53 PM UTC End time: Tuesday, November 10, 2026, at 2:00 PM UTC Root cause: A recent change introduced a regression that resulted in restored teams remaining invisible due to a code check missing the “restored” tag, resulting in impact. Next steps: We're continuing our analysis of the impacting change to better identify and prevent similar impact in the future. This is the final update for the event.

10 Nov 2026 05:29 UTC · regular

Title: Users may be unable to view previously deleted teams after restoration in Microsoft Teams User impact: Users may be unable to view previously deleted teams after restoration in Microsoft Teams. More info: As a workaround, changing an affected user's role (member to owner and then back to member) makes the team visible for that user. Current status: The rollout of our fix is ongoing and will be completed in stages. Early deployment has been completed and we're seeing improvements in system health, but more time will be required to complete the full rollout and monitor for confirmation of impact resolution. Scope of impact: This issue may affect any user attempting to view previously deleted and restored teams. This information may be updated as our investigation continues. Start time: Monday, October 26, 2026, at 12:53 PM UTC Root cause: A recent change introduced a regression that resulted in restored teams remaining invisible due to a code check missing the “restored” tag, resulting in impact. Next update by: Tuesday, November 10, 2026, at 8:30 PM UTC

10 Nov 2026 00:35 UTC · regular

Title: Users may be unable to view previously deleted teams after restoration in Microsoft Teams User impact: Users may be unable to view previously deleted teams after restoration in Microsoft Teams. More info: As a workaround, changing an affected user's role (member to owner and then back to member) makes the team visible for that user. Current status: We're continuing our fix deployment and expect the process to finish in a few hours. Scope of impact: This issue may affect any user attempting to view previously deleted and restored teams. This information may be updated as our investigation continues. Start time: Monday, October 26, 2026, at 12:53 PM UTC Root cause: A recent change introduced a regression that resulted in restored teams remaining invisible due to a code check missing the “restored” tag, resulting in impact. Next update by: Tuesday, November 10, 2026, at 7:00 AM UTC

09 Nov 2026 21:11 UTC · regular

Title: Users may be unable to view previously deleted teams after restoration in Microsoft Teams User impact: Users may be unable to view previously deleted teams after restoration in Microsoft Teams. More info: As a workaround, changing an affected user's role (member to owner and then back to member) makes the team visible for that user. Current status: We're monitoring our fix deployment as it saturates throughout the affected environment, and we expect this process to complete by Tuesday, November 10, 2026, at 12:00 AM UTC. Once fully saturated, we'll validate whether impact is resolved or if any additional mitigative actions may be required to do so. Scope of impact: This issue may affect any user attempting to view previously deleted and restored teams. This information may be updated as our investigation continues. Start time: Monday, October 26, 2026, at 12:53 PM UTC Root cause: A recent change introduced a regression that resulted in restored teams remaining invisible due to a code check missing the “restored” tag, resulting in impact. Next update by: Tuesday, November 10, 2026, at 2:00 AM UTC

09 Nov 2026 19:09 UTC · regular

Title: Users may be unable to view previously deleted teams after restoration in Microsoft Teams User impact: Users may be unable to view previously deleted teams after restoration in Microsoft Teams. More info: As a workaround, changing an affected user's role (member to owner and then back to member) makes the team visible for that user. Current status: We’ve completed the development of our fix and have initiated its deployment. We’re working to establish an accurate timeline for deployment completion and impact remediation to provide with our next scheduled communication update. Scope of impact: This issue may affect any user attempting to view previously deleted and restored teams. This information may be updated as our investigation continues. Root cause: A recent change introduced a regression that resulted in restored teams remaining invisible due to a code check missing the “restored” tag, resulting in impact. Next update by: Monday, November 9, 2026, at 10:30 PM UTC

09 Nov 2026 17:20 UTC · regular

Title: Users may be unable to view previously deleted teams after restoration in Microsoft Teams User impact: Users may be unable to view previously deleted teams after restoration in Microsoft Teams. More info: As a workaround, changing an affected user's role (member to owner and then back to member) makes the team visible for that user. Current status: We’ve identified a recent change introduced a regression that resulted in restored teams remaining invisible due to a code check missing the “restored” tag, resulting in impact. We’re developing a fix to correct this issue and working to establish a timeline for the fix deployment. Scope of impact: This issue may affect any user attempting to view previously deleted and restored teams. This information may be updated as our investigation continues. Root cause: A recent change introduced a regression that resulted in restored teams remaining invisible due to a code check missing the “restored” tag, resulting in impact. Next update by: Monday, November 9, 2026, at 7:30 PM UTC

09 Nov 2026 16:15 UTC · regular

Title: Users may be unable to view previously deleted teams after restoration in Microsoft Teams User impact: Users may be unable to view previously deleted teams after restoration in Microsoft Teams. More info: As a workaround, changing an affected user's role (member to owner and then back to member) makes the team visible for that user. Current status: We’re reviewing screenshots of impact and client logs captured from an affected user to assist our investigation into the source of the issue. In parallel, we’ve successfully reproduced impact in our internal testing environment and are reviewing this reproduction to further assist our root cause efforts. Scope of impact: This issue may affect any user attempting to view previously deleted and restored teams. This information may be updated as our investigation continues. Next update by: Monday, November 9, 2026, at 5:30 PM UTC

09 Nov 2026 15:58 UTC · regular

Title: Users may be unable to view previously deleted teams after restoration in Microsoft Teams User impact: Users may be unable to view previously deleted teams after restoration in Microsoft Teams. More info: As a workaround, changing an affected user's role (member to owner and then back to member) makes the team visible for that user. Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

© Microsoft — archived from Microsoft 365 service health. Content notice