Some users conferenced into a Microsoft Teams E911 call may not be automatically muted or able to mute themselves
ID: TM1488543
Issue type: Incident
|
|
|---|
|
|
Status
Service Degradation
|
|
|---|
|
|
Impacted services
Microsoft Teams
|
|
|---|
|
|
Details
Title: Some users conferenced into a Microsoft Teams E911 call may not be automatically muted or able to mute themselves
User impact: Users conferenced into a Microsoft Teams E911 call may not be automatically muted or able to mute themselves.
More info: Users conferenced into a Microsoft Teams E911 are also unable to mute themselves and would need to leave the call.
Current status: After analyzing correlation and meeting IDs provided by a subset of affected users, we've isolated a code mismatch in the components utilized when marking a Microsoft Teams call as a multi-party call is causing the code to mute participants to not be enabled as expected. We've expanded our communications to all potentially affected tenants and updated the "Title", "User impact" and "Scope of impact" fields of our communications to reflect this change as we begin rolling out a code change to remediate the mismatch.
Scope of impact: Users conferenced into a Microsoft Teams E911 call and attempting to mute their audio are affected by this issue. This section may be updated as the investigation progresses.
Start time: Friday, September 25, 2026, at 8:09 PM UTC
Root cause: A code mismatch in the components utilized when marking a Microsoft Teams call as a multi-party call is causing the code to mute participants to not be enabled as expected.
Next update by: Monday, October 5, 2026, at 11:30 PM UTC
|
|
|---|
|
|
|
|
Did you find this email helpful?
Yes
No
|
|
|---|
|
|
To customize what’s included in this email, who gets it, or to unsubscribe, set your Service health preferences. If you are receiving this email because your Admin added you as a recipient, please contact your Admin to unsubscribe.
|
|
|---|
|
|
|
|
|
