Status Page

2026-04-20	Status	Description
02:14 PM		User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Teams web client. More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible. While we're working to remediate this issue, affected users can still perform screen sharing by: - Using the desktop or mobile apps - Adding another user to the call - Ending and restarting the call Current status: We're in the process of analyzing gathered logs and service telemetry to better understand the impact scenario and develop a remediation strategy. Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Teams web client may be affected. Next update by: Tuesday, April 21, 2026, at 1:00 PM AST
02:07 PM		User impact: Users may not have heard their Teams secondary ringer audio on specific devices. More info: Specifically, this issue affected the secondary ringer for users who were leveraging Citrix Virtual Desktop Infrastructure (VDI) 2 devices. Final status: We've confirmed with a subset of affected users that our code fix has successfully remediated all impact as expected for this issue. Scope of impact: Some users leveraging Citrix VDI 2 for their secondary ringer devices may have been impacted by this event. Start time: Thursday, March 19, 2026, at 9:16 AM AST End time: Wednesday, April 15, 2026, at 1:35 PM AST Root cause: A recent update made to VDI device management handling introduced a regression and was resulting in impact. Next steps: - We're reviewing our service update check and implementation processes to improve how we detect potential Teams VDI device management code regressions and prevent similar service events from occurring in the future.
02:05 PM		Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Teams web client Current status: We're investigating a potential issue with Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
09:33 AM		User impact: Users may be intermittently unable to browse apps in Teams. More info: Affected users are able to manage their existing apps without issue. Current status: We're investigating a recent service update deployment that we believe is causing intermittent errors when browsing apps in Teams. We've halted the deployment and are working on a fix. Once we validate the fix we'll begin deployment to the affected infrastructure. Scope of impact: This issue may intermittently impact some users attempting to browse apps in Teams. Next update by: Saturday, April 18, 2026, at 1:00 PM AST
09:28 AM		Title: Users may get incorrect or stale content when using Platform deep links in Teams User impact: Users may get incorrect or stale content when using Platform deep links in Teams. More info: Platform deep links may get incorrect or stale content for users who have opted into the Technology Adoption Program or Public Preview. Users can opt out to avoid this issue. Current status: We've identified the most recent platform update has introduced a regression that's causing impact. We're evaluating mitigation options to correct this regression in the most expedient way possible. Scope of impact: This issue may affect users who use Platform deep links and have opted into the Technology Adoption Program or Public Preview. Next update by: Monday, April 20, 2026, at 3:30 PM AST
09:20 AM		Title: Users may be unable to launch the Teams desktop client More info: When attempting to launch the Teams desktop client, users are stuck on the loading screen and receive an error message "We're having trouble loading your message. Try refreshing." Impacted users should restart their client to bypass impact. Current status: We've determined that a recent service update introduced a regression within the Teams client build caching system and is resulting in this transient issue's impact. We're reverting the offending update to remediate impact and will provide a timeline on this process as one becomes available. Scope of impact: Users attempting to launch the Teams desktop client may be impacted by this event. This section may be updated as our investigation continues. Root cause: A recent service update introduced a regression within the Teams client build caching system and is resulting in impact. Next update by: Monday, April 20, 2026, at 3:30 PM AST

02:14 PM

User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.

While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call

Current status: We're in the process of analyzing gathered logs and service telemetry to better understand the impact scenario and develop a remediation strategy.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Teams web client may be affected.
Next update by: Tuesday, April 21, 2026, at 1:00 PM AST

02:07 PM

User impact: Users may not have heard their Teams secondary ringer audio on specific devices.

More info: Specifically, this issue affected the secondary ringer for users who were leveraging Citrix Virtual Desktop Infrastructure (VDI) 2 devices.

Final status: We've confirmed with a subset of affected users that our code fix has successfully remediated all impact as expected for this issue.

Scope of impact: Some users leveraging Citrix VDI 2 for their secondary ringer devices may have been impacted by this event.

Start time: Thursday, March 19, 2026, at 9:16 AM AST
End time: Wednesday, April 15, 2026, at 1:35 PM AST

Root cause: A recent update made to VDI device management handling introduced a regression and was resulting in impact.

Next steps:
- We're reviewing our service update check and implementation processes to improve how we detect potential Teams VDI device management code regressions and prevent similar service events from occurring in the future.

02:05 PM

Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Teams web client

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

09:33 AM

User impact: Users may be intermittently unable to browse apps in Teams.

More info: Affected users are able to manage their existing apps without issue.

Current status: We're investigating a recent service update deployment that we believe is causing intermittent errors when browsing apps in Teams. We've halted the deployment and are working on a fix. Once we validate the fix we'll begin deployment to the affected infrastructure.
Scope of impact: This issue may intermittently impact some users attempting to browse apps in Teams.

Next update by: Saturday, April 18, 2026, at 1:00 PM AST

09:28 AM

Title: Users may get incorrect or stale content when using Platform deep links in Teams

User impact: Users may get incorrect or stale content when using Platform deep links in Teams.

More info: Platform deep links may get incorrect or stale content for users who have opted into the Technology Adoption Program or Public Preview. Users can opt out to avoid this issue.

Current status: We've identified the most recent platform update has introduced a regression that's causing impact. We're evaluating mitigation options to correct this regression in the most expedient way possible.
Scope of impact: This issue may affect users who use Platform deep links and have opted into the Technology Adoption Program or Public Preview.

Next update by: Monday, April 20, 2026, at 3:30 PM AST

09:20 AM

Title: Users may be unable to launch the Teams desktop client

More info: When attempting to launch the Teams desktop client, users are stuck on the loading screen and receive an error message "We're having trouble loading your message. Try refreshing."

Impacted users should restart their client to bypass impact.

Current status: We've determined that a recent service update introduced a regression within the Teams client build caching system and is resulting in this transient issue's impact. We're reverting the offending update to remediate impact and will provide a timeline on this process as one becomes available.

Scope of impact: Users attempting to launch the Teams desktop client may be impacted by this event. This section may be updated as our investigation continues.

Root cause: A recent service update introduced a regression within the Teams client build caching system and is resulting in impact.
Next update by: Monday, April 20, 2026, at 3:30 PM AST