Live status of all services Advisory

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

Microsoft Teams TM1545775

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

Status
Service degradation
Feature
Teams and Channels
Region
Not specified (all regions)
Started
Oct 26, 2026, 13:53 CET
Duration
15 days 5 h
Last update
Nov 10, 2026, 06:29 CET
Next update
Nov 10, 2026, 21:30 CET

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.

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.

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.

Timeline

Every update Microsoft posted for this issue, newest first.

  1. Nov 10, 2026, 06:29 CET

    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.

  2. Nov 10, 2026, 01:35 CET

    We're continuing our fix deployment and expect the process to finish in a few hours.

  3. Nov 9, 2026, 22:11 CET

    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.

  4. Nov 9, 2026, 20:09 CET

    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.

  5. Nov 9, 2026, 18:20 CET

    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.

  6. Nov 9, 2026, 17:15 CET

    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.

  7. Nov 9, 2026, 16:58 CET

    We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

When Microsoft 365 goes down

The live overview shows the current state of every Microsoft 365 service, refreshed every minute from Microsoft Graph.

To see whether your own tenant is affected, check Service health in the Microsoft 365 admin center. Only a backup outside Microsoft protects against data loss, and only a tested break-glass account against locked-out admins. We set up both in fixed-scope sprints.

Source: Microsoft Graph, Service Communications API. This is the view of a Swiss Microsoft 365 tenant: services not licensed there are missing, and individual issues may affect your tenant differently. Microsoft names the region only in the issue text. The Switzerland view shows issues for Switzerland, for Europe in general and those without a region, but not issues that only name other countries such as Germany or the UK. This page is not provided by Microsoft.