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.

Title: Users’ labels and classifications for Microsoft Word, Excel and PowerPoint documents may not function
User Impact: Users’ labels and classifications for Microsoft Word, Excel and PowerPoint documents may not function.
More info: This problem may inhibit the creation of new labels and classifications. Existing labels and classifications may fail to apply.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.

Title: Users’ labels and classifications for Microsoft Word, Excel and PowerPoint documents may not function
User Impact: Users’ labels and classifications for Microsoft Word, Excel and PowerPoint documents may not have worked as expected.
More info: This problem may have prevented sensitivity labels from being recommended or auto-applied. Existing labels and classifications may have failed to apply.
Final status: After monitoring service telemetry, we've confirmed that our traffic processing optimizations have resolved the issue. Labels and classifications now work as expected.
Scope of impact: Your organization was affected by this event, and any user creating or utilizing existing labels and classifications may have been impacted.
Start time: Monday, November 1, 2021, at 2:30 PM UTC
End time: Monday, November 1, 2021, at 6:25 PM UTC
Root cause: Infrastructure that facilitates label and classification functionality became unbalanced and began processing traffic inefficiently, leading to impact.
Next steps: - We’re reviewing performance and health levels for the portion of infrastructure that wasn’t processing traffic as efficiently as expected in addition to investigating potential automated request balancing actions to prevent similar label and classification problems in the future.
This is the final update for the event.

Resolved

More info: This problem may inhibit the creation of new labels and classifications. Existing labels and classifications may fail to apply.
Current status: We've identified that infrastructure that facilitates label and classification functionality became unbalanced and began processing traffic inefficiently. We’ve implemented traffic processing optimizations to balance service load and remediate impact. We're monitoring service side telemetry to ensure that the issue is resolved.
Scope of impact: Your organization is affected by this event, and any user creating or utilizing existing labels and classifications may be impacted.
Start time: Monday, November 1, 2021, at 2:30 PM UTC
Root cause: Infrastructure that facilitates label and classification functionality became unbalanced and began processing traffic inefficiently, leading to impact.
Next update by: Monday, November 1, 2021, at 8:00 PM UTC

Title: Users sync requests may fail in OneNote desktop Win32 clients
User Impact: Users sync requests may fail in OneNote desktop Win32 clients.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.

Current status: We identified a recent build deployment is causing a communications issue with OneNote sync requests. We're redeploying the build to correct the impacting configuration to remediate the impact.
Scope of impact: This issue may potentially affect any user performing syncs in OneNote desktop Win32 clients.
Start time: Tuesday, September 28, 2021, at 9:40 AM UTC
Root cause: A recent build deployment is causing a communications issue with OneNote sync requests, resulting in them to fail.
Next update by: Wednesday, September 29, 2021, at 3:30 AM UTC

Title: Users sync requests may fail in OneNote desktop Win32 clients
User Impact: Users sync requests may have failed in OneNote desktop Win32 clients.
Final status: While we're continuing the redeployment of the build to correct the impacting configuration, we remediated the impact by rerouting traffic to alternate infrastructure to process sync requests. We monitored the environment to verify that sync requests were being processed as expected.
Scope of impact: This issue may have potentially affected any user performing syncs in OneNote desktop Win32 clients.
Start time: Tuesday, September 28, 2021, at 9:40 AM UTC
End time: Wednesday, September 29, 2021, at 1:15 AM UTC
Root cause: A recent build deployment was causing a communications issue with OneNote sync requests, resulting in sync failures.
Next steps: -We're continuing our deployment of the build to correct the configuration. -We're performing additional analysis on the recent build deployment to better understand what caused the configuration issue to occur which will help us to develop ways to avoid similar situations in future deployments.
This is the final update for the event.

Resolved

Final status: We've confirmed that a recent deployment intended to provide optimizations for service stability inadvertently introduced a regression in service logic, resulting in impact. We've reverted the affecting change and confirmed that impact is mitigated.
Scope of impact: Your organization was affected by this event, and all users were impacted.
Start time: Wednesday, September 1, 2021, at 5:30 PM UTC
End time: Tuesday, September 7, 2021, at 7:00 PM UTC
Root cause: A recent deployment intended to provide optimizations for service stability inadvertently introduced a regression in service logic, resulting in impact.
Next steps: - We're reviewing our update procedures to identify how impact was missed during testing and validation to better prevent similar future impact.
This is the final update for the event.

User Impact: Users were unable to open notebooks in Microsoft OneNote.
More info: Impact is specific to all versions of Microsoft OneNote excluding OneNote 2016 and the web client. Windows 10 desktop client, iOS and Android mobile app versions were all impacted.
Current status: We've investigated a problem with the Microsoft OneNote service in which users were unable to open notebooks, and we’ve confirmed that service is now restored. We'll provide additional information in a closure summary within the “History” section of the “Service health” dashboard shortly.
Scope of impact: Your organization was affected by this event, and all users were impacted.

Title: Some OneNote content created between May 14th, and May 18th, 2021, is not accessible
User Impact: Users may notice that some OneNote edits created between May 14th, 2021, and May 18th, 2021, are unavailable.
More Info: While restoration of the impacted content progresses, users may notice an additional section added to their notebooks with the date in the following format (YY-MM-DD, e.g. 21-05-18(1)) that represents a snapshot of content from May 18th, 2021, prior to it becoming unavailable.
Current status: We’ve discovered an issue in which some of your users may notice that OneNote content that was edited by a user between May 14th, and May 18th, 2021, is unavailable. We’re currently working to restore access to the impacted OneNote content, and we’ll provide a timeline for restoration as soon as it becomes available.
Scope of impact: Your organization is affected by this event.
Start time: Friday, May 14th, 2021, at 12:00 AM UTC.
Root cause: A code issue caused OneNote content between May 14th, and May 18th, 2021, to not be saved properly. We’ve mitigated the issue going forward and included additional validations to prevent future occurrences of this issue.
Next update by: Friday, June 16, 2021, at 11:30 PM UTC

More Info: While restoration of the impacted content progresses, users may notice an additional section added to their notebooks with the date in the following format (YY-MM-DD, e.g. 21-05-18(1)) that represents a snapshot of content from May 18th, 2021, prior to it becoming unavailable.
Current status: We're continuing to restore access to the impacted OneNote content. We expect this process to take an extended period to ensure access is properly restored.
Scope of impact: Your organization is affected by this event.
Start time: Friday, May 14th, 2021, at 12:00 AM UTC.
Root cause: A code issue caused OneNote content between May 14th, and May 18th, 2021, to not be saved properly. We’ve mitigated the issue going forward and included additional validations to prevent future occurrences of this issue.
Next update by: Tuesday, July 20, 2021, at 11:30 PM UTC

More Info: While restoration of the impacted content progresses, users may notice an additional section added to their notebooks with the date in the following format (YY-MM-DD, e.g. 21-05-18(1)) that represents a snapshot of content from May 18th, 2021, prior to it becoming unavailable.
Current status: Our restoration efforts are progressing as expected. We continue to expect this work to take an extended period of time. At this point in the incident, we expect at least 95 percent of all users to be mitigated.
Scope of impact: Your organization is affected by this event.
Start time: Friday, May 14th, 2021, at 12:00 AM UTC.
Root cause: A code issue caused OneNote content between May 14th, and May 18th, 2021, to not be saved properly. We’ve mitigated the issue going forward and included additional validations to prevent future occurrences of this issue.
Next update by: Friday, July 23, 2021, at 11:30 PM UTC

More Info: While restoration of the impacted content progresses, users may notice an additional section added to their notebooks with the date in the following format (YY-MM-DD, e.g. 21-05-18(1)) that represents a snapshot of content from May 18th, 2021, prior to it becoming unavailable.
Current status: Our recovery efforts are ongoing and approximately 98 percent of all users are no longer impacted by this event. We'll continue to work on restoring the remaining two percent.
Scope of impact: Your organization is affected by this event.
Start time: Friday, May 14th, 2021, at 12:00 AM UTC.
Root cause: A code issue caused OneNote content between May 14th, and May 18th, 2021, to not be saved properly. We’ve mitigated the issue going forward and included additional validations to prevent future occurrences of this issue.
Next update by: Wednesday, July 28, 2021, at 11:30 PM UTC

More Info: While restoration of the impacted content progresses, users may notice an additional section added to their notebooks with the date in the following format (YY-MM-DD, e.g. 21-05-18(1)) that represents a snapshot of content from May 18th, 2021, prior to it becoming unavailable.
For clarity, an additional section will be created with a date after the name of the restored section(s).
Current status: We've completed the large majority of our restoration efforts. We're working on the very limited number of users that may remain impacted by this incident. We'll provide a more detailed update by our next update.
Scope of impact: Your organization is affected by this event.
Start time: Friday, May 14th, 2021, at 12:00 AM UTC
Root cause: A code issue caused OneNote content between May 14th, and May 18th, 2021, to not be saved properly. We’ve mitigated the issue going forward and included additional validations to prevent future occurrences of this issue.
Next update by: Wednesday, August 4, 2021, at 11:30 PM UTC

More Info: While restoration of the impacted content progresses, users may notice an additional section added to their notebooks with the date in the following format (YY-MM-DD, e.g. 21-05-18(1)) that represents a snapshot of content from May 18th, 2021, prior to it becoming unavailable.
For clarity, an additional section will be created with a date after the name of the restored section(s).
Current status: We've completed our restoration efforts and we're continuing to monitor the service and for any customer reports that the issue is persisting.
Scope of impact: Your organization is affected by this event.
Start time: Friday, May 14th, 2021, at 12:00 AM UTC
Root cause: A code issue caused OneNote content between May 14th, and May 18th, 2021, to not be saved properly. We’ve mitigated the issue going forward and included additional validations to prevent future occurrences of this issue.
Next update by: Monday, August 9, 2021, at 11:30 PM UTC

Title: Some OneNote content created between May 14th, and May 18th, 2021, was not accessible
User Impact: Users may have noticed that some OneNote edits created between May 14th, 2021, and May 18th, 2021, were unavailable.
More Info: While restoration of the impacted content progressed, users may have noticed an additional section added to their notebooks with the date in the following format (YY-MM-DD, e.g. 21-05-18(1)) that represented a snapshot of content from May 18th, 2021, prior to it becoming unavailable.
For clarity, an additional section was created with a date after the name of the restored section(s).
Final status: We've received confirmation via internal monitoring and customer reports that our restoration efforts were successful.
Scope of impact: Your organization was affected by this event.
Start time: Friday, May 14th, 2021, at 12:00 AM UTC
Root cause: A code issue caused OneNote content between May 14th, and May 18th, 2021, to not be saved properly. We’ve mitigated the issue going forward and included additional validations to prevent future occurrences of this issue.
Next update by: Tuesday, August 3, 2021, at 11:30 PM UTC

Resolved

Title: Sync errors when syncing notebooks
User Impact: Users may experience intermittent sync errors when syncing notebooks in Microsoft OneNote.
More Info: Users are recommended to retry their notebook sync to workaround the problem while we mitigate impact.
Current Status: We've discovered an issue that is causing sync errors when syncing notebooks across the service. We're working on reducing service throttle and server utilization to mitigate impact.
Scope of impact: Any user attempting to sync their notebook might be affected.
Root cause: A OneNote fix is causing intermittent sync issues when syncing notebooks.
Start time: Monday, May 25, 2021 at 1:15 AM UTC
Update time: Tuesday, May 26, 2021 at 2:30 AM UTC

More Info: Users are recommended to retry their notebook sync to workaround the problem while we mitigate impact.
Current Status: We’re continuing our work to improve server efficiency and service throttle. We expect this work to take an extended period of time while we continue to work on minimizing impact for this event.
Scope of impact: Any user attempting to sync their notebook might be affected. Root cause: A OneNote fix is causing intermittent sync issues when syncing notebooks.
Start time: Monday, May 25, 2021 at 1:15 AM UTC
Update time: Thursday, May 27, 2021 at 2:30 AM UTC

Title: Sync delays or errors when syncing notebooks
User Impact: Users may experience degraded sync speeds or errors when syncing notebooks in Microsoft OneNote.
More info: More Info: Users were recommended to retry their notebook sync to workaround the problem while we mitigate impact.
Final status: We've completed our work to improve the service and confirmed via extended monitoring that the issue has been fully resolved.
Scope of impact: Any user attempting to sync their notebook may have been affected.
Start time: Monday, May 24, 2021, at 1:15 AM UTC
End time: Tuesday, June 1, 2021, at 11:15 PM UTC
Root cause: A OneNote fix was causing intermittent sync issues when syncing notebooks.
Next steps: - We're working on improving our service load balancing to prevent future occurrences of the issue.
This is the final update for the event.

Resolved

Title: Some users may experience Office app crashes upon app launch or opening files on iOS devices.
User Impact: Users may experience Office app crashes upon app launch or when opening files on iOS devices.
More info: Impact is limited to some users that have release 2.49 of iOS Office apps including Office Mobile, Word, Excel, and PowerPoint.
While we are focused on remediation, users may follow these steps to mitigate impact:
-Go to "System Settings" -Select the Office app that is experiencing the issue -Click on "Reset [name of selected app]" -Enable "Clear all [documents, workbooks, presentations]"
Current status: We've identified that a recent feature update containing a code regression was deployed resulting in impact. We have reverted the update, which should mitigate impact for the majority of users. While we are in the process of releasing version 2.49.1 of the apps to the iOS App Store to fully remediate impact, users can manually reset their Office app preferences to resolve the issue.
Scope of impact: Impact is specific to iOS Office apps that attempt to open documents that were still open during the last session. The apps will continue to do this, causing a crash loop.
Start time: Monday, May 10, 2021, at 4:00 AM UTC
Root cause: A recent feature update contained a code regression, which may cause Office app crashes on iOS devices when opening documents.
Next update by: Tuesday, May 11, 2021, at 6:00 PM UTC

User impact: Users may experience Office app crashes upon app launch or when opening files on iOS devices.
More info: Impact is limited to some users that have release 2.49 of iOS Office apps including Office Mobile, Word, Excel, and PowerPoint.
While we are focused on remediation, users may follow these steps to mitigate impact:
-Go to "System Settings" -Select the Office app that is experiencing the issue -Click on "Reset [name of selected app]" -Enable "Clear all [documents, workbooks, presentations]"
Current status: We're continuing our efforts to expedite the release of version 2.49.1 of the apps to the iOS App Store for full remediation of the issue. Additionally, users can manually reset their Office app preferences as outlined in the More info section to mitigate impact.
Scope of impact: Impact is specific to iOS Office apps that attempt to open documents that were still open during the last session. The apps will continue to do this, causing a crash loop.
Start time: Monday, May 10, 2021, at 4:00 AM UTC
Root cause: A recent feature update contained a code regression, which may cause Office app crashes on iOS devices upon app launch or when opening documents.
Next update by: Tuesday, May 11, 2021, at 9:00 PM UTC

Resolved

Title: Some users may experience Office app crashes upon app launch or opening files on iOS devices
User Impact: Users may have experienced Office app crashes upon app launch or when opening files on iOS devices.
More info: Impact was limited to some users that had release 2.49 of iOS Office apps including Office Mobile, Word, Excel, and PowerPoint.
While we were focused on remediation, users may have followed these steps to mitigate impact:
-Go to "System Settings" -Select the Office app that was experiencing the issue -Click on "Reset [name of selected app]" -Enable "Clear all [documents, workbooks, presentations]".
Final status: We've deployed version 2.49.1 of the apps to the iOS App Store to remediate impact. Affected users without automatic updates can download the app update from the iOS App Store to remediate impact.
Scope of impact: Impact was specific to iOS Office apps that attempted to open documents that were still open during the last session. The apps were continuing to do this, causing a crash loop.
Start time: Monday, May 10, 2021, at 4:00 AM UTC
End time: Tuesday, May 11, 2021, at 7:00 PM UTC
Root cause: A recent feature update contained a code regression, which may have caused Office app crashes on iOS devices upon app launch or when opening documents.
Next steps: - We're reviewing our update procedures and the associated code regression to better identify similar issues during our development and testing cycles.
This is the final update for the event.