Microsoft 365
June 19, 8:00pm ADT
Network Access and WiFi
Acadia Website
Printing Services
Student Services
Campus Administrative Services
Teaching and Learning Services
Library Services
Browser Services
Colleague Administrative System
Catalog & Accounts
Slate Enrollment Service
Inter Library Loan Services
Moodle (ACORN)
Lime Survey
StarRez Residence Services
myAcadia Online Self Service
WiFi
VPN
Off Campus Access
Co-Op Education Portal (Orbis)
Informer Reporting
Turnitin
WiFi Residence Buildings
Timetable & Exam Scheduling Services
Web Systems
Wifi Administrative/Academic Buildings
HUB Service Portal
Live Chat & Remote Support
Eduroam
Meal Plan Services
Email Services
Door Access & Lock Services
Network Access
Box Office Ticketing & Registration (AudienceView)
Event Management Services (Legend)
Cybersecurity Awareness Training
Acadia Emergency Alert Services
Jun-19, 8:00pm ADT
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.
Jun-19, 11:55pm ADT
Please note that services have been restored. If you continue to experience issues, please contact the Service Desk.
May 02, 6:00pm ADT
Network Access and WiFi
Acadia Website
Printing Services
Student Services
Campus Administrative Services
Library Services
Browser Services
Colleague Administrative System
Catalog & Accounts
Slate Enrollment Service
Inter Library Loan Services
StarRez Residence Services
myAcadia Online Self Service
WiFi
VPN
Off Campus Access
Co-Op Education Portal (Orbis)
Informer Reporting
WiFi Residence Buildings
Timetable & Exam Scheduling Services
Web Systems
Wifi Administrative/Academic Buildings
HUB Service Portal
Live Chat & Remote Support
Eduroam
Meal Plan Services
Email Services
Door Access & Lock Services
Network Access
Box Office Ticketing & Registration (AudienceView)
Event Management Services (Legend)
Cybersecurity Awareness Training
Acadia Emergency Alert Services
May-2, 6:00pm ADT
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.
May-2, 8:15pm ADT
Please note that services have been restored. If you continue to experience issues, please contact the Service Desk.
Apr-12, 11:21am ADT
[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
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 =
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
Mar-31, 5:14pm ADT
Title: Most users may be unable to access the OneDrive for Business sync client from the desktop version
User impact: Users may be unable to access the OneDrive for Business sync client from the desktop version.
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: Users may be unable to access the OneDrive for Business sync client from the desktop version.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
Mar-31, 5:31pm ADT
User impact: Users can't access the OneDrive for Business sync client from the desktop version.
Current status: We're reviewing system logs to isolate the origin of this issue and working with affected users to collect some additional Web Access Management (WAM) logs to further our understanding of the impacting scenario.
Scope of impact: Some users are unable to access the OneDrive for Business sync client from the desktop version.
Next update by: Friday, March 31, 2023, at 10:30 PM UTC
Current status: We're reviewing system logs to isolate the origin of this issue and working with affected users to collect some additional Web Access Management (WAM) logs to further our understanding of the impacting scenario.
Scope of impact: Some users are unable to access the OneDrive for Business sync client from the desktop version.
Next update by: Friday, March 31, 2023, at 10:30 PM UTC
Mar-31, 7:20pm ADT
User impact: Users can’t sync local content through the OneDrive for Business sync client desktop version.
More info: Users can still access their OneDrive account using the web application, but may be unable to sync changes to or from their local OneDrive desktop client.
Current status: We’re reaching affected users to collect the necessary Web Access Management (WAM) logs to further our investigation into the underlying cause of this issue and determine our next troubleshooting steps.
Scope of impact: Some users are unable to access the OneDrive for Business sync client from the desktop version.
Next update by: Monday, April 3, 2023, at 7:00 PM UTC
More info: Users can still access their OneDrive account using the web application, but may be unable to sync changes to or from their local OneDrive desktop client.
Current status: We’re reaching affected users to collect the necessary Web Access Management (WAM) logs to further our investigation into the underlying cause of this issue and determine our next troubleshooting steps.
Scope of impact: Some users are unable to access the OneDrive for Business sync client from the desktop version.
Next update by: Monday, April 3, 2023, at 7:00 PM UTC
Mar-31, 11:10pm ADT
User impact: Users can’t sync local content through the OneDrive for Business sync client desktop version.
More info: Users can still access their OneDrive account using the web application but may be unable to sync changes to-or-from their local OneDrive desktop client.
Current status: We've identified and subsequently disabled a client-side configuration setting that we expect was linked to this issue. We're monitoring the telemetry signals for the change to determine the efficacy of this mitigation path. In parallel, we're continuing our investigation into the underlying cause of this issue and determining any additional actions that may be required.
Scope of impact: Some users are unable to access the OneDrive for Business sync client from the desktop version.
Next update by: Monday, April 3, 2023, at 7:00 PM UTC
More info: Users can still access their OneDrive account using the web application but may be unable to sync changes to-or-from their local OneDrive desktop client.
Current status: We've identified and subsequently disabled a client-side configuration setting that we expect was linked to this issue. We're monitoring the telemetry signals for the change to determine the efficacy of this mitigation path. In parallel, we're continuing our investigation into the underlying cause of this issue and determining any additional actions that may be required.
Scope of impact: Some users are unable to access the OneDrive for Business sync client from the desktop version.
Next update by: Monday, April 3, 2023, at 7:00 PM UTC
Apr-1, 9:00pm ADT
Title: Some users can’t sync local content through the OneDrive for Business desktop sync client
User impact: Users couldn’t sync local content through the OneDrive for Business desktop sync client.
More info: Users could still access their OneDrive account using the web application but may have been unable to sync changes to-or-from their local OneDrive desktop client. Users reporting receiving a 1001 error code.
Final status: After extended monitoring, we've confirmed that the client-side configuration setting that was previously disabled has successfully fixed the issue.
Scope of impact: Some users were unable to sync local content through the OneDrive for Business desktop sync client.
Start time: Sunday, March 19, 2023, at 12:00 PM UTC
End time: Sunday, April 2, 2023, at 12:00 AM UTC
Preliminary root cause: An authorization problem prevented users from syncing content through the OneDrive for Business desktop client.
Next steps: - We're continuing to investigate the underlying cause of the issue to determine whether additional action is required. - We're also continuing to monitor telemetry to ensure that the issue does not recur.
We’ll publish a post-incident report within five business days.
User impact: Users couldn’t sync local content through the OneDrive for Business desktop sync client.
More info: Users could still access their OneDrive account using the web application but may have been unable to sync changes to-or-from their local OneDrive desktop client. Users reporting receiving a 1001 error code.
Final status: After extended monitoring, we've confirmed that the client-side configuration setting that was previously disabled has successfully fixed the issue.
Scope of impact: Some users were unable to sync local content through the OneDrive for Business desktop sync client.
Start time: Sunday, March 19, 2023, at 12:00 PM UTC
End time: Sunday, April 2, 2023, at 12:00 AM UTC
Preliminary root cause: An authorization problem prevented users from syncing content through the OneDrive for Business desktop client.
Next steps: - We're continuing to investigate the underlying cause of the issue to determine whether additional action is required. - We're also continuing to monitor telemetry to ensure that the issue does not recur.
We’ll publish a post-incident report within five business days.
Apr-1, 9:00pm ADT
Resolved
Apr-3, 3:21pm ADT
User impact: Users can’t sync local content through the OneDrive for Business desktop sync client.
More info: Users can still access their OneDrive account using the web application but may be unable to sync changes to-or-from their local OneDrive desktop client.
Current status: Initial review indicates that disabling the client-side configuration change we identified has not had a positive affect on the end-user impact. As such, we're reviewing diagnostic data recently collected from affected users alongside service telemetry to identify the source of this issue and our next mitigation steps.
Scope of impact: Some users are unable to sync local content through the OneDrive for Business desktop sync client.
Next update by: Tuesday, April 4, 2023, at 12:00 AM UTC
More info: Users can still access their OneDrive account using the web application but may be unable to sync changes to-or-from their local OneDrive desktop client.
Current status: Initial review indicates that disabling the client-side configuration change we identified has not had a positive affect on the end-user impact. As such, we're reviewing diagnostic data recently collected from affected users alongside service telemetry to identify the source of this issue and our next mitigation steps.
Scope of impact: Some users are unable to sync local content through the OneDrive for Business desktop sync client.
Next update by: Tuesday, April 4, 2023, at 12:00 AM UTC
Apr-3, 8:01pm ADT
User impact: Users can’t sync local content through the OneDrive for Business desktop sync client.
More info: Users can still access their OneDrive account using the web application but may be unable to sync changes to-or-from their local OneDrive desktop client.
Current status: We're continuing our work to review diagnostic data and error logs recently collected from affected users. Due to the complexity of this issue the investigation is taking some additional time to complete. We’re correlating several sources of service telemetry to better identify the source of this issue, along with our next mitigation steps. We’ll provide an estimated time to resolve as soon as one becomes available.
Scope of impact: Some users are unable to sync local content through the OneDrive for Business desktop sync client.
Next update by: Tuesday, April 4, 2023, at 11:00 PM UTC
More info: Users can still access their OneDrive account using the web application but may be unable to sync changes to-or-from their local OneDrive desktop client.
Current status: We're continuing our work to review diagnostic data and error logs recently collected from affected users. Due to the complexity of this issue the investigation is taking some additional time to complete. We’re correlating several sources of service telemetry to better identify the source of this issue, along with our next mitigation steps. We’ll provide an estimated time to resolve as soon as one becomes available.
Scope of impact: Some users are unable to sync local content through the OneDrive for Business desktop sync client.
Next update by: Tuesday, April 4, 2023, at 11:00 PM UTC
March 27, 11:27am ADT
Mar-27, 11:27am ADT
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.
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
Mar-27, 12:25pm ADT
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
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
Mar-27, 1:13pm ADT
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.
This quick update is designed to give the latest information on this issue.
Mar-27, 1:25pm ADT
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
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
Mar-27, 1:30pm ADT
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.
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.
Mar-27, 1:30pm ADT
Resolved
Mar-27, 2:17pm ADT
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
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
Mar-24, 1:00pm ADT
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: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
Mar-24, 1:23pm ADT
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
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
Mar-24, 2:19pm ADT
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 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
Mar-24, 2:40pm ADT
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.
This is the final update for the event.
March 17, 6:15am ADT
Mar-17, 6:15am ADT
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: 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.
Mar-17, 6:46am ADT
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
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
Mar-17, 7:19am ADT
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.
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.
Mar-17, 7:19am ADT
Resolved
Mar-17, 7:27am ADT
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
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
March 16, 8:19am ADT
Mar-16, 8:19am ADT
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
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
Mar-16, 9:30am ADT
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.
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.
Mar-16, 9:30am ADT
Resolved
Mar-16, 9:46am ADT
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
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
March 08, 10:49am AST
Mar-8, 10:49am AST
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
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
Mar-8, 12:26pm AST
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.
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.
Mar-8, 12:26pm AST
Resolved
February 17, 1:57pm AST
Feb-17, 1:57pm AST
Title: Delays or problems loading OneDrive for Business content
User impact: Users may experience intermittent delays or navigation errors when accessing OneDrive for Business content.
Current Status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within one hour.
Feb-17, 2:53pm AST
User impact: Users may experience intermittent delays or navigation errors when accessing OneDrive for Business content.
Current Status: We've determined that a portion of OneDrive for Business infrastructure that facilitates content access entered into an unhealthy state, resulting in impact. We've rerouted traffic to an alternative infrastructure and are in the process of monitoring the environment to confirm resolution.
Scope of impact: Any user may be affected by this event, and users may experience intermittent delays or navigation errors when accessing OneDrive for Business content.
Start time: Friday, February 17, 2023, at 4:40 PM UTC
Root cause: A portion of OneDrive for Business infrastructure that facilitates content access entered into an unhealthy state, resulting in impact.
Next update by: Friday, February 17, 2023, at 8:00 PM UTC
Current Status: We've determined that a portion of OneDrive for Business infrastructure that facilitates content access entered into an unhealthy state, resulting in impact. We've rerouted traffic to an alternative infrastructure and are in the process of monitoring the environment to confirm resolution.
Scope of impact: Any user may be affected by this event, and users may experience intermittent delays or navigation errors when accessing OneDrive for Business content.
Start time: Friday, February 17, 2023, at 4:40 PM UTC
Root cause: A portion of OneDrive for Business infrastructure that facilitates content access entered into an unhealthy state, resulting in impact.
Next update by: Friday, February 17, 2023, at 8:00 PM UTC
Feb-17, 3:59pm AST
Title: Some users may experience intermittent delays or navigation errors when accessing OneDrive for Business content
User impact: Users were experiencing intermittent delays or navigation errors when accessing OneDrive for Business content.
Final status: We've confirmed through service health monitoring that redirecting traffic to alternate infrastructure has resolved the issue.
Scope of impact: Any user may have been experiencing intermittent delays or navigation errors when accessing OneDrive for Business content.
Start time: Friday, February 17, 2023, at 4:40 PM UTC
End time: Friday, February 17, 2023, at 7:59 PM UTC
Root cause: A portion of OneDrive for Business infrastructure that facilitated content access entered into an unhealthy state, resulting in impact.
Next steps: - We're further reviewing health telemetry and logs from the portion of affected infrastructure to better understand what caused it to enter and unhealthy state and find solutions for preventing similar impact like this from happening in the future.
This is the final update for the event.
User impact: Users were experiencing intermittent delays or navigation errors when accessing OneDrive for Business content.
Final status: We've confirmed through service health monitoring that redirecting traffic to alternate infrastructure has resolved the issue.
Scope of impact: Any user may have been experiencing intermittent delays or navigation errors when accessing OneDrive for Business content.
Start time: Friday, February 17, 2023, at 4:40 PM UTC
End time: Friday, February 17, 2023, at 7:59 PM UTC
Root cause: A portion of OneDrive for Business infrastructure that facilitated content access entered into an unhealthy state, resulting in impact.
Next steps: - We're further reviewing health telemetry and logs from the portion of affected infrastructure to better understand what caused it to enter and unhealthy state and find solutions for preventing similar impact like this from happening in the future.
This is the final update for the event.
Feb-17, 3:59pm AST
Resolved
Feb-17, 4:02pm AST
Current Status: We're continuing to monitor the environment to confirm resolution.
Scope of impact: Any user may be affected by this event, and users may experience intermittent delays or navigation errors when accessing OneDrive for Business content.
Start time: Friday, February 17, 2023, at 4:40 PM UTC
Root cause: A portion of OneDrive for Business infrastructure that facilitates content access entered into an unhealthy state, resulting in impact.
Next update by: Friday, February 17, 2023, at 10:00 PM UTC
Scope of impact: Any user may be affected by this event, and users may experience intermittent delays or navigation errors when accessing OneDrive for Business content.
Start time: Friday, February 17, 2023, at 4:40 PM UTC
Root cause: A portion of OneDrive for Business infrastructure that facilitates content access entered into an unhealthy state, resulting in impact.
Next update by: Friday, February 17, 2023, at 10:00 PM UTC