Sturgis PS

UPDATE: The root cause of this issue has been identified. Our Engineering team will be testing a potential fix.

Title: Some users conferenced into a Microsoft Teams emergency call may not be automatically muted or able to mute themselves User impact: Users conferenced into a Microsoft Teams emergency call may not be automatically muted or able to mute themselves. More info: Users conferenced into a Microsoft Teams emergency call are also unable to mute themselves and would need to leave the call. Current status: We've initiated deployment of our code change to address the code mismatch causing users to not be automatically muted as expected or being able to mute themselves in emergency calls. We anticipate deployment to be completed by Monday, October 12, 2026, and we aim to provide updates on our timeline to remediation as deployment progresses. Scope of impact: Users conferenced into a Microsoft Teams emergency 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 Estimated time to resolve: We anticipate impact to be resolved by Monday, October 12, 2026. Root cause: A code mismatch in the components utilized when marking a Microsoft Teams emergency call as a multi-party call is causing the code to mute participants to not be enabled as expected. Next update by: Friday, October 9, 2026, at 11:00 PM UTC

We are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.

The issue has been identified and a fix is being implemented.