Date Correction:
Technology Services will be performing scheduled network maintenance on June 19, 8:00pm ADT. The outage is expected to last approximately 60 minutes . During this time, access to campus resources will be unavailable.   

Please note that services have been restored. If you continue to experience issues, please contact the Service Desk.

Technology Services will be performing scheduled network maintenance on May 02, 6:00pm ADT. The outage is expected to last approximately 2h minutes. During this time, access to campus resources may become unavailable.   

Please note that services have been restored. If you continue to experience issues, please contact the Service Desk.

[In Progress] User impact: Users recently migrated to Microsoft Teams may not see the dial pad for up to 72 hours after being migrated.
More info: This issue is intermittent and specifically impacts users migrated from an on-premises environment to the cloud, and users that were assigned a new number or changed numbers in Microsoft Teams. The issue occurs in all Microsoft Teams connection methods.
As a workaround, admins are able to use the following script to manually implement the Voice Policy change: $UserSip = $policy = Get-CsOnlineUser -Identity $UserSip Grant-CsTeamsMediaLoggingPolicy -Identity $UserSip $null Grant-CsTeamsMediaLoggingPolicy -Identity $UserSip -PolicyName Enabled Grant-CsTeamsMediaLoggingPolicy -Identity $UserSip $policy.TeamsMediaLoggingPolicy
Current status: We've developed, validated and are now working on final approvals and preparations prior to the deployment of the fix, which we anticipate will succeed in remediating the impact.
Scope of impact: Any Microsoft Teams user who was recently migrated from an on-premises environment to the cloud, or that recently received a new number or whose number was recently changed, may intermittently experience delays of up to 72 hours in accessing the Microsoft Teams dial pad.
Root cause: An update to optimize cache processing on the underlying infrastructure responsible for supporting Microsoft Teams functionality subsequently increased the length of time that the dial pad takes to become visible to users after migrations, number assignments, and number changes.
Next update by: Thursday, April 13, 2023, at 10:30 AM UTC

Title: Some users may encounter delays or failures when opening links scanned by Safe Links
User impact: Users may encounter delays or failures when opening links scanned by Safe Links.
Current status: We've identified unexpected latency in a section of infrastructure which facilitates the Safe Links feature. We've restarted a section of the affected infrastructure to mitigate impact, but a period of monitoring indicates this has not provided full relief. We're reviewing further telemetry and system logs to isolate the cause of the latency.
Scope of impact: Impact is specific to some users served through the affected infrastructure who are attempting to open links scanned by Safe Links. Next update by: Monday, March 27, 2023, at 3:30 PM UTC

User impact: Users may encounter delays or failures when opening links scanned by Safe Links.
More info: Affected users may experience the following error 'We can't check the safety of this website right now.'
Current status: We've identified a potential root cause scenario which may be responsible for causing the unexpected latency within the affected infrastructure. We’re continuing to investigate telemetry and system logs further to verify and determine our remediation actions.
Scope of impact: Impact is specific to some users served through the affected infrastructure who are attempting to open links scanned by Safe Links.
Next update by: Monday, March 27, 2023, at 4:30 PM UTC

While our investigation continues, we're conducting additional targeted restarts within a section of the affected infrastructure and our telemetry is indicating that some customers may be experiencing a reduction or remediation in impact.
This quick update is designed to give the latest information on this issue.

User impact: Users may encounter delays or failures when opening links scanned by Safe Links.
More info: Affected users may experience the following error 'We can't check the safety of this website right now.'
Current status: We’re continuing to review telemetry and system logs to verify the identified potential root cause scenario. Additionally, we’re completing targeted restarts of a section of the affected infrastructure and this process is progressing as expected.
We've identified a potential root cause scenario which may be responsible for causing the unexpected latency within the affected infrastructure. We’re continuing to investigate telemetry and system logs further to verify.
Scope of impact: Impact is specific to some users served through the affected infrastructure who are attempting to open links scanned by Safe Links. Next update by: Monday, March 27, 2023, at 5:30 PM UTC

Title: Some users may encounter delays or failures when opening links scanned by Safe Links
User impact: Users may have encountered delays or failures when opening links scanned by Safe Links.
More info: Affected users may have experienced the following error: 'We can't check the safety of this website right now.'
Final status: As our investigation into the underlying cause was ongoing, we confirmed through system telemetry that the restarts performed on the affected infrastructure successfully mitigated the issue, and that users are no longer experiencing impact when opening links. 
Scope of impact: Impact was specific to some users served through the affected infrastructure who were attempting to open links scanned by Safe Links. 
Start time: Sunday, March 26, 2023, at 9:50 PM UTC
End time: Monday, March 27, 2023, at 4:30 PM UTC
Preliminary root cause: Infrastructure responsible for handling Safe Links requests wasn't processing traffic as efficiently as expected. 
Next steps:  - We're continuing to investigate what caused the infrastructure to operate inefficiently.  - We're monitoring system telemetry to confirm impact to end users does not recur.
We’ll publish a post-incident report within five business days.

Resolved

User impact: Users may encounter delays or failures when opening links scanned by Safe Links.
More info: Affected users may experience the following error: 'We can't check the safety of this website right now.'
Current status: Our analysis of telemetry and system logs thus far indicates that infrastructure responsible for handling Safe Links requests isn't processing traffic as efficiently as expected. As we investigate the underlying cause for the degradation, we continue to perform restarts in stages on the affected infrastructure in an attempt to mitigate the end-user impact.
Scope of impact: Impact is specific to some users served through the affected infrastructure who are attempting to open links scanned by Safe Links. Preliminary root cause: Infrastructure responsible for handling Safe Links requests isn't processing traffic as efficiently as expected.
Next update by: Monday, March 27, 2023, at 7:00 PM UTC

Title: Anonymous users may be unable to join Microsoft Teams meetings through the Safari browser
User impact: Anonymous users may be unable to join Microsoft Teams meetings through the Safari browser.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.

User impact: Anonymous users may be unable to join Microsoft Teams meetings through the Safari browser.
Current status: Our investigation determined that a recent update to service components facilitating authentication and meeting joining for anonymous users contains a code conflict that's causing impact. We're determining how best to remediate this issue. Scope of impact: This issue may affect any anonymous user attempting to join Microsoft Teams meetings through the Safari browser. Start time: Thursday, March 23, 2023, at 11:00 AM UTC Root cause: A recent update to service components facilitating authentication and meeting joining for anonymous users contains a code conflict that's causing impact. Next update by: Friday, March 24, 2023, at 5:30 PM UTC

User impact: Anonymous users may be unable to join Microsoft Teams meetings through the Safari browser.
More info: This issue is specific to non-authenticated Microsoft Teams meeting joins through the Safari browser. Current status: We've reverted the impacting update and we're monitoring service telemetry to ensure availability recovers completely. Scope of impact: This issue may affect any anonymous user attempting to join Microsoft Teams meetings through the Safari browser. Start time: Thursday, March 23, 2023, at 11:00 AM UTC Root cause: A recent update to service components facilitating authentication and meeting joining for anonymous users contains a code conflict that's causing impact. Next update by: Friday, March 24, 2023, at 7:30 PM UTC

More info: This issue was specific to non-authenticated Microsoft Teams meeting joins through the Safari browser. Final status: We've confirmed through service telemetry that anonymous users are able to join Microsoft Teams meetings through the Safari browser, remediating impact. Scope of impact: This issue may have affected any anonymous user attempting to join Microsoft Teams meetings through the Safari browser. Start time: Thursday, March 23, 2023, at 11:00 AM UTC End time: Friday, March 24, 2023, at 5:40 PM UTC Root cause: A recent update to service components facilitating authentication and meeting joining for anonymous users contained a code conflict that was causing impact. Next steps: - We're reviewing the impacting update to identify how this issue wasn't caught during testing and validation, which will allow us to prevent similar impact in the future.
This is the final update for the event.

Title: Possible delays or problems when accessing Microsoft Teams
User impact: Some customers have reported issues with accessing the service, or using features in Microsoft Teams.
Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.

User impact: Admins may be unable to manage users in the Microsoft Teams Admin center.
Current status: We’re reviewing diagnostic data to determine the root cause of impact.
Scope of impact: Impact is specific to admins affected through the affected infrastructure and may impact any admin attempting to manage users in the Microsoft Teams Admin center.
Next update time: Friday, March 17, 2023 at 11:00 AM UTC

Title: Admins may have been unable to manage users in the Microsoft Teams Admin center
User impact: Admins may have been unable to manage users in the Microsoft Teams Admin center.
Final status: We've determined that a recent configuration change, designed to improve backend service operations, caused an issue where invalid data was being forwarded to internal services, which resulted in requests failing, causing impact. We've reverted the change to mitigate impact.   Scope of impact: This issue may have impacted any admin attempting to manage users in the Microsoft Teams Admin center.
Start time: Friday, March 17, 2023, at 5:02 AM UTC
End time: Friday, March 17, 2023, at 10:19 AM UTC
Preliminary root cause: A recent configuration change, designed to improve backend service operations, caused an issue where invalid data was being forwarded to internal services, which resulted in requests failing, causing impact.
Next steps: - We're reviewing our standard service update procedures to avoid similar impact in the future.
We’ll publish a post-incident report within five business days.

Resolved

User impact: Admins may be unable to manage users in the Microsoft Teams Admin center.
User impact: Admins may be unable to manage users in the Microsoft Teams Admin center.
Current status: We've identified a recent configuration change that may be contributing to impact, whilst we work to isolate the root cause we're reverting the change to mitigate impact.   Scope of impact: This issue may impact any admin attempting to manage users in the Microsoft Teams Admin center.
Start time: Friday, March 17, 2023, at 5:02 AM UTC
Next update time: Friday, March 17, 2023 at 11:30 AM UTC

Title: Some users may be unable to update their presence within Microsoft Teams
User impact: Users may be unable to update their presence within Microsoft Teams.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Thursday, March 16, 2023, at 1:30 PM UTC

Title: Some users may be unable to update their presence within Microsoft Teams
User impact: Users may have been unable to update their presence within Microsoft Teams.
Final status: Additional analysis into the offending service change, we've determined that the deployment process itself was causing the impact. Due to this, the planned revert and fix weren't necessary. After halting the change, our internal validation confirmed that impact had been remediated.  Scope of impact: Impact was specific to some users who were served through the affected infrastructure. Start time: Thursday, March 16, 2023, at 4:10 AM UTC End time: Thursday, March 16, 2023, at 12:30 PM UTC Root cause: A deployment process problem for a recent service update caused an error causing unexpected failures when updating presence within Microsoft Teams. Next steps: - We're further analyzing our service update and change deployment processes to better understand why it caused the failures in updating presence to avoid similar problems in the future.
This is the final update for this event.

Resolved

User impact: Users may be unable to update their presence within Microsoft Teams.
Current status: We've identified that a recent update intended to enhance service functionality has inadvertently introduced an error causing unexpected failures in updating presence within Microsoft Teams. We're currently in the process of developing the fix to revert the offending update and expect to have a remediation timeline by our next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Wednesday, March 15, 2023, at 9:13 AM UTC
Root cause: A recent update intended to enhance service functionality has inadvertently introduced an error causing unexpected failures in updating presence within Microsoft Teams.
Next update by: Thursday, March 16, 2023, at 10:00 PM UTC

Title: Some users are unable to renew authentication tokens in Microsoft Teams
User impact: Users are unable to renew authentication tokens in Microsoft Teams.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to users who are served through the affected infrastructure.
Next update by: Wednesday, March 8, 2023, at 5:00 PM UTC

Title: Some users may be unable to access the Microsoft Teams service
User impact: Users may be unable to access the Microsoft Teams service.
Final status: The investigation is complete, and we've determined the service is healthy. A service incident did not actually occur. This communication will expire in 24 hours.
This is the final update for the event.

Resolved

More info: This issue only affects the Teams desktop client and Windows Microsoft Teams Room (MTR) devices, and only when those devices had an HID connected during a recently terminated meeting. Users may experience the following impact scenarios: - Device peripheral call indicators, such as an LED display, may not turn off as expected when a Teams meeting ends. - For users utilizing on-premises Skype for Business with Microsoft Teams in coexistence mode, a persistent dial-tone during Microsoft Teams calls may be experienced. - If users were muted during a meeting, users may experience being unable to unmute during subsequent meetings. Users may restart their Microsoft Teams client to mitigate this impact.
This commonly affects users with a HID such as an audio headset. More information regarding HIDs can be found here: https://learn.microsoft.com/en-us/windows-hardware/drivers/hid/
While the fix is being deployed, we can disable the HID feature for your organization to temporarily mitigate this issue if requested. However, users won't be able to use Mute/Unmute or Hook/OffHook controls from their headset devices until the full fix is available.
Current status: We've completed development of the updated fix and are monitoring as it progresses through our validation procedures. We expect to have an updated deployment timeline by the next scheduled update.
Scope of impact: This issue specifically affected Microsoft Teams users with a HID connected, and only impacted the Microsoft Teams desktop client and Windows MTR devices.
Start time: Wednesday, December 7, 2022, at 1:34 AM UTC
Root cause: Changes to improve the HID feature for Microsoft Teams users introduced a code issue, causing degraded functionality to some users with these device types attached to their Teams client.
Next update by: Saturday, February 18, 2023, at 12:00 AM UTC

More info: This issue only affects the Teams desktop client and Windows Microsoft Teams Room (MTR) devices, and only when those devices had an HID connected during a recently terminated meeting. Users may experience the following impact scenarios: - Device peripheral call indicators, such as an LED display, may not turn off as expected when a Teams meeting ends. - For users utilizing on-premises Skype for Business with Microsoft Teams in coexistence mode, a persistent dial-tone during Microsoft Teams calls may be experienced. - If users were muted during a meeting, users may experience being unable to unmute during subsequent meetings. Users may restart their Microsoft Teams client to mitigate this impact.
This commonly affects users with a HID such as an audio headset. More information regarding HIDs can be found here: https://learn.microsoft.com/en-us/windows-hardware/drivers/hid/
While the fix is being deployed, we can disable the HID feature for your organization to temporarily mitigate this issue if requested. However, users won't be able to use Mute/Unmute or Hook/OffHook controls from their headset devices until the full fix is available.
Current status: We're continuing our validation of the updated fix and expect deployment to start by the next scheduled update.
Scope of impact: This issue specifically affected Microsoft Teams users with a HID connected, and only impacted the Microsoft Teams desktop client and Windows MTR devices.
Start time: Wednesday, December 7, 2022, at 1:34 AM UTC
Root cause: Changes to improve the HID feature for Microsoft Teams users introduced a code issue, causing degraded functionality to some users with these device types attached to their Teams client.
Next update by: Tuesday, February 21, 2023, at 10:00 PM UTC

[In Progress] User impact: Users with HIDs attached when disconnecting from a Teams meeting may subsequently experience degraded functionality.
More info: This issue only affects the Teams desktop client and Windows Microsoft Teams Room (MTR) devices, and only when those devices had an HID connected during a recently terminated meeting. Users may experience the following impact scenarios: - Device peripheral call indicators, such as an LED display, may not turn off as expected when a Teams meeting ends. - For users utilizing on-premises Skype for Business with Microsoft Teams in coexistence mode, a persistent dial-tone during Microsoft Teams calls may be experienced. - If users were muted during a meeting, users may experience being unable to unmute during subsequent meetings. Users may restart their Microsoft Teams client to mitigate this impact.
This commonly affects users with a HID such as an audio headset. More information regarding HIDs can be found here: https://learn.microsoft.com/en-us/windows-hardware/drivers/hid/
While the fix is being deployed, we can disable the HID feature for your organization to temporarily mitigate this issue if requested. However, users won't be able to use Mute/Unmute or Hook/OffHook controls from their headset devices until the full fix is available.
Current status: We've initiated the deployment of our updated fix and we're monitoring as it progresses, with current observations indicating that it's 40 percent complete. We expect that it will finish and remediate impact on Wednesday, February 22, 2023.
Scope of impact: This issue specifically affects Microsoft Teams users with a HID connected, and only impacts the Microsoft Teams desktop client and Windows MTR devices.
Start time: Wednesday, December 7, 2022, at 1:34 AM UTC
Root cause: Changes to improve the HID feature for Microsoft Teams users introduced a code issue, causing degraded functionality to some users with these device types attached to their Teams client.
Next update by: Wednesday, February 22, 2023, at 10:00 PM UTC

Title: Users' Public Switched Telephone Network (PSTN) calls may be unexpectedly disconnected in Microsoft Teams
User impact: Users' PSTN calls may be unexpectedly disconnected in Microsoft Teams.
More info: This is affecting PSTN calls within voice applications.
Current status: We're reviewing service monitoring determine the root cause of impact and our next steps towards remediation.
Scope of impact: Your organization is affected by this event, and any user making PSTN calls in calling applications may be impacted.
Next update: Thursday, February 16, 2023 at 11:30 AM UTC

User impact: Users' PSTN calls may be unexpectedly disconnected in Microsoft Teams.
More info: This is affecting PSTN calls within voice applications.
Current status: We're analyzing a sample of failed calls to locate the cause of impact and identify a mitigation plan.
Scope of impact: Your organization is affected by this event, and any user making PSTN calls in calling applications may be impacted.
Next update: Thursday, February 16, 2023 at 1:30 PM UTC

User impact: Users' PSTN calls may be unexpectedly disconnected in Microsoft Teams when transferred.
More info: Only transferred call queue and auto attendant PSTN calls are affected.
Current status: We're continuing to review failed call samples to aid our investigation into the root cause.
Scope of impact: Our telemetry indicates that approximately 9% of PSTN call transfers to call queues or auto attendants are affected.
Next update by: Thursday, February 16, 2023, at 2:30 PM UTC

User impact: Users' PSTN calls may be unexpectedly disconnected in Microsoft Teams when transferred.
More info: Only transferred call queue and auto attendant PSTN calls are affected.
Current status: Our investigation thus far into failed call samples has been inconclusive. We're reviewing any ongoing and recent deployments that may be contributing to impact.
Scope of impact: Our telemetry indicates that approximately 9% of PSTN call transfers to call queues or auto attendants are affected.
Next update by: Thursday, February 16, 2023, at 4:30 PM UTC

Title: Some users' calls may unexpectedly disconnect in Microsoft Teams when made or transferred to the call queue
User impact: Users' calls may have been unexpectedly disconnected in Microsoft Teams when made or transferred to the call queue.
More info: Only transferred call queue and auto attendant calls were affected.
Final status: We identified that a configuration set in a recent service update disrupted a network routing component, resulting in impact when calls were made to Microsoft Teams call queues. We corrected this configuration and used internal monitoring telemetry to confirm that impact is remediated.
Scope of impact: Approximately nine percent of call transfers to call queues or auto attendants were affected.
Start time: Monday, February 13, 2023, at 10:16 PM UTC
End time: Thursday, February 16, 2023, at 3:38 PM UTC
Root cause: A configuration set in a recent service update disrupted a network routing component, resulting in impact when calls were made to Microsoft Teams call queues.
Next steps: - We're reviewing the service update validation process to improve the detection of similar issues in the future.
This is the final update for the event.

Resolved