Live status of all services Advisory · resolved

Some users may experience intermittent audio and video degradation when using Microsoft Teams through VDI 2.0

Microsoft Teams TM1489450

Users may have experienced intermittent audio and video degradation when using Microsoft Teams through VDI 2.0

Status
Service restored
Feature
General
Region
Not specified (all regions)
Started
Oct 1, 2026, 14:00 CEST
Resolved
Oct 7, 2026, 01:10 CEST
Duration
5 days 11 h

More info

Users also intermittently may have been unable to leverage certain feature optimizations provided by VDI 2.0

As a workaround, users could have restarted Microsoft Teams to resolve the issue.

Scope of impact

Users who were using Microsoft Teams VDI 2.0 in a Citrix VDI environment may have been impacted.

Root cause

A recent configuration update to the VDI Bridge component responsible for VDI optimization introduced a regression, resulting in impact.

Next steps:
- We're reviewing the impacting configuration update to understand why impact to audio and video quality wasn't identified during our pre-deployment testing processes. This investigation will help us to prevent similar issues from occurring in the future.

This is the final update for the event.

Final status

We've monitored service health telemetry for an extended period and confirmed that the impact has been remediated on build version 26246.1604.5133.838. We recommend any user still facing impact to download this specific build version to apply the remediation.

Timeline

Every update Microsoft posted for this issue, newest first.

  1. Oct 13, 2026, 17:58 CEST

    We've monitored service health telemetry for an extended period and confirmed that the impact has been remediated on build version 26246.1604.5133.838. We recommend any user still facing impact to download this specific build version to apply the remediation.

  2. Oct 12, 2026, 19:07 CEST

    We're seeing continued success from our mitigation of moving users to a specific build version that doesn't contain the regression, and more monitoring time is needed to ensure this provides a stable resolution for users.

  3. Oct 9, 2026, 16:55 CEST

    We’ve implemented an interim mitigation to provide immediate relief and have observed initial signs of improvement. However, we’re continuing to monitor its effectiveness while progressing with validation of a longer-term fix before proceeding with deployment.

  4. Oct 8, 2026, 16:22 CEST

    We’re proceeding to validate the fix before deploying it to the affected infrastructure. Once available, we’ll provide a deployment timeline.

  5. Oct 7, 2026, 18:45 CEST

    We’re continuing to validate the fix before deploying it to the affected infrastructure. Once available, we’ll provide a deployment timeline.

  6. Oct 7, 2026, 10:59 CEST

    We’ve identified that a recent configuration update to the VDI Bridge component responsible for VDI optimisation introduced a regression, resulting in impact. We’ve developed a fix and are currently validating it before deploying it to the affected infrastructure. We expect to provide a deployment timeline by our next scheduled update.

  7. Oct 6, 2026, 18:59 CEST

    As we progress with our root cause analysis and isolate the source for this event, we've isolated an offending code regression that is believed to be producing the problems. We've internally validated a solution that is expected to remediate the impact. We're deploying our solution, and we'll provide an updated timeline for its deployment once it has become available.

  8. Oct 6, 2026, 15:20 CEST

    We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.

When Microsoft 365 goes down

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

Live status of all services Subscribe to incidents in LEXOJ

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.