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: Some users may be unable to render apps or web parts leveraging the SharePoint Framework (SPFx) in SharePoint Online
User Impact: Users may be unable to render apps or web parts leveraging the SPFx in SharePoint Online.
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: Our investigation has determined that a recent configuration change in the SharePoint Online infrastructure responsible for fulfilling web part content requests contained a conflict that prevented some requests from reaching the appropriate database, resulting in impact. We've reverted the configuration to its most recent healthy state to repair this issue, and we're testing to confirm that the affected web parts have been restored and impact is remediated.
Scope of impact: Some users accessing a SharePoint Online site containing apps or web parts may be affected.
Start time: Monday, October 31, 2022, at 12:30 PM UTC
Root cause: A recent configuration change in the SharePoint Online infrastructure responsible for fulfilling web part content requests contained a conflict that prevented some requests from reaching the appropriate database, resulting in impact.
Next update by: Tuesday, November 1, 2022, at 8:00 PM UTC

Current status: We're awaiting word from affected customers to confirm that the affected web parts have been restored and impact is remediated.
Scope of impact: Some users accessing a SharePoint Online site containing apps or web parts may be affected.
Start time: Monday, October 31, 2022, at 12:30 PM UTC
Root cause: A recent configuration change in the SharePoint Online infrastructure responsible for fulfilling web part content requests contained a conflict that prevented some requests from reaching the appropriate database, resulting in impact.
Next update by: Tuesday, November 1, 2022, at 10:30 PM UTC

Current status: While our telemetry suggests that the majority of impact has been resolved, we see some errors occurring that could be due to apps and web parts accessing cached data storage, which should automatically refresh after a 24-hour period. We're initiating an extended monitoring period to ensure that the affected web parts have been restored and impact is remediated.
Scope of impact: Some users accessing a SharePoint Online site containing apps or web parts may be affected.
Start time: Monday, October 31, 2022, at 12:30 PM UTC
Root cause: A recent configuration change in the SharePoint Online infrastructure responsible for fulfilling web part content requests contained a conflict that prevented some requests from reaching the appropriate database, resulting in impact.
Next update by: Wednesday, November 2, 2022, at 9:00 PM UTC

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

Title: Admins may be unable to perform migrations to Microsoft Teams channels via the SharePoint Migration Tool (SPMT) User impact: Admins may be unable to perform migrations to Microsoft Teams channels via the SPMT.
More info: This issue also affects admins when performing migrations via the Migration Manager tool.
Admins may see this error when migrating content to Microsoft Teams channels: "Errors or timeout for Server Processing the file: Not all the items in the package have been migrated".
Current status: We're investigating system logs to isolate the origin of this issue.
Scope of impact: Any admin that's performing migrations to Microsoft Teams channels utilizing the SPMT or Migration Manager tool are impacted.
Next update: Wednesday, October 26, 2022, at 11:30 PM UTC

More info: This issue also affects admins when performing migrations via the Migration Manager tool.
Admins may see this error when migrating content to Microsoft Teams channels: "Errors or timeout for Server Processing the file: Not all the items in the package have been migrated".
Current status: We're continuing our investigation of system logs that capture the impact to isolate the source of the errors and formulate a strategy for remediation.
Scope of impact: Any admin that's performing migrations to Microsoft Teams channels utilizing the SPMT or Migration Manager tool are impacted.
Next update by: Thursday, October 27, 2022, at 3:30 AM UTC

More info: This issue also affects admins when performing migrations via the Migration Manager tool.
Admins may see this error when migrating content to Microsoft Teams channels: "Errors or timeout for Server Processing the file: Not all the items in the package have been migrated".
Current status: After further review, we identified that there are errors when using the SPMT for migrations to Microsoft Teams channels. We're reviewing system logs to identify what is triggering the migration failures, which will help us determine our next troubleshooting steps.
Scope of impact: Any admin that's performing migrations to Microsoft Teams channels utilizing the SPMT or Migration Manager tool are impacted.
Next update by: Friday, October 28, 2022, at 3:30 AM UTC

More info: This issue also affects admins when performing migrations via the Migration Manager tool.
Admins may see this error when migrating content to Microsoft Teams channels: "Errors or timeout for Server Processing the file: Not all the items in the package have been migrated". Current status: We've determined that an update error is blocking SharePoint Online folder data from being updated in Microsoft Teams channels when admins attempt migrations via the SPMT. We're developing a code change to fix the error and allow migration jobs to update folder data in channels. Scope of impact: Any admin that's performing migrations to Microsoft Teams channels utilizing the SPMT or Migration Manager tool are impacted. Start time: Wednesday, October 19, 2022, at 12:00 AM UTC Root cause: An update error is blocking SharePoint Online folder data from being updated in Microsoft Teams channels when admins attempt migrations via the SPMT. Next update by: Friday, October 28, 2022, at 11:00 PM UTC

More info: This issue also affects admins when performing migrations via the Migration Manager tool.
Admins may see this error when migrating content to Microsoft Teams channels: "Errors or timeout for Server Processing the file: Not all the items in the package have been migrated". Current status: We're continuing to develop a fix for this issue, which we expect will take some time to complete testing and validation. Once complete, we'll prepare the fix for deployment and evaluate possible expeditions to the fix to ensure impact is remediated as soon as possible. Scope of impact: Any admin that's performing migrations to Microsoft Teams channels utilizing the SPMT or Migration Manager tool are impacted. Start time: Wednesday, October 19, 2022, at 12:00 AM UTC Root cause: An update error is blocking SharePoint Online folder data from being updated in Microsoft Teams channels when admins attempt migrations via the SPMT. Next update by: Monday, October 31, 2022, at 9:00 PM UTC

Title: Admins can't perform migrations to Microsoft Teams channels via SharePoint Migration Tool (SPMT) and Migration Manager
User Impact: Admins were unable to perform migrations to Microsoft Teams channels via the SPMT and the Migration Manager tool.
More info: Admins may have seen the following error when migrating content to Microsoft Teams channels: "Errors or timeout for Server Processing the file: Not all the items in the package have been migrated".
Final status: While working to prepare a code fix, we determined that disabling the offending code portion would be a more efficient and expeditious means of remediating impact. The code portion was successfully disabled, and we've confirmed with previously affected users that the issue is now resolved. Scope of impact: Any admin performing SharePoint Online content migrations to Microsoft Teams channels utilizing the SPMT or Migration Manager tool was impacted. Start time: Wednesday, October 19, 2022, at 12:00 AM UTC End time: Saturday, October 29, 2022, at 2:20 AM UTC Preliminary root cause: An error was blocking SharePoint Online folder data from being updated in Microsoft Teams channels when admins attempted content migrations. Next steps: - We're continuing to investigate how the error which blocked the migrations was introduced to prevent similar issues from happening in the future. We’ll publish a post-incident report within five business days.

Resolved

Title: Users creating or editing list items with multi-line text fields can't save changes in SharePoint Online
User Impact: Users creating or editing list items with multi-line text fields can't save changes in SharePoint Online.
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're reviewing screenshots and video detailing impact reproduction, and are attempting to perform our own reproduction of impact for further insight into how the issue manifests to assist with formulating our next investigating steps. Scope of impact: This issue affects all users creating or editing list items with multi-line text fields with Nucleus sync enabled. Next update by: Tuesday, October 11, 2022, at 8:30 PM UTC

More info: This issue is specific to lists with Nucleus sync enabled. Users' can self-mitigate with the following steps:
Go to their List home page (App menu in the upper right of SharePoint -> All Apps -> Lists).
Find the list you'd like to stop syncing.
Click the ... button.
If the list is syncing, there will be a menu option for "Stop Syncing". If the "Stop Syncing" button isn't present, please wait for 30 seconds, refresh the page, and try again. Current status: We've successfully reproduced the issue and suspect a code bug in the optional Nucleus service, which runs on users' machines and allows the web app to send requests to the Nucleus service for syncing to SharePoint Online cloud and across local devices, may be contributing to impact. We're disabling the Nucleus service to restore sync functionality as we investigate recent changes to determine the source of impact. Scope of impact: This issue affects all users creating or editing list items with multi-line text fields with Nucleus sync enabled. Next update by: Wednesday, October 12, 2022, at 6:30 PM UTC

More info: This issue is specific to lists with Nucleus sync enabled. Users can self-mitigate with the following steps:
Go to their List home page (App menu in the upper right of SharePoint -> All Apps -> Lists).
Find the list you'd like to stop syncing.
Click the ... button.
If the list is syncing, there will be a menu option for "Stop Syncing". If the "Stop Syncing" button isn't present, please wait for 30 seconds, refresh the page, and try again. Current status: We've identified a recent service update that was intending to improve multi-list generation within the Nucleus sync that is preventing users from saving changes when creating or editing list items with multi-line text fields. We've deployed a fix to correct the recent service update, and we're confirming with affected users if impact has been remediated. Scope of impact: This issue affects all users creating or editing list items with multi-line text fields with Nucleus sync enabled. Start time: Tuesday, October 4, 2022, at 6:36 PM UTC Root cause: A recent service update intending to improve multi-list generation within the Nucleus sync has resulted in impact. Next update by: Thursday, October 13, 2022, at 6:30 PM UTC

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

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

Title: Users can't access SharePoint Online sites via Microsoft Edge
User Impact: Users can't access SharePoint Online sites via Microsoft Edge.
More info: Users can access SharePoint Online sites from other browsers and users can temporarily restore access to sites through Microsoft Edge by clearing their cache.
Users see the following error message when they encounter this issue:
"AADSTS900411: The request is not properly formatted. The parameter 'login_hint' is duplicated" Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes. Scope of impact: Impact may occur for any user attempting to access SharePoint Online sites via Microsoft Edge.

More info: Users can access SharePoint Online sites from other browsers and users can temporarily restore access to sites through Microsoft Edge by clearing their cache.
Users see the following error message when they encounter this issue:
"AADSTS900411: The request is not properly formatted. The parameter 'login_hint' is duplicated" Current status: We're reviewing available diagnostic data, such as recent service changes and Unified Logging Service (ULS) logs, to isolate the source of this problem and identify our troubleshooting actions. Scope of impact: Impact may occur for any user attempting to access SharePoint Online sites via Microsoft Edge. Next update by: Thursday, September 1, 2022, at 5:00 PM UTC

More info: Users can access SharePoint Online sites from other browsers and users can temporarily restore access to sites through Microsoft Edge by clearing their cache.
Users see the following error message when they encounter this issue:
"AADSTS900411: The request is not properly formatted. The parameter 'login_hint' is duplicated" Current status: We're continuing to assess available diagnostic data, such as recent service changes and Unified Logging Service (ULS) logs, to isolate the source of this problem and identify an optimal solution. Scope of impact: Impact may occur for any user attempting to access SharePoint Online sites via Microsoft Edge. Next update by: Thursday, September 1, 2022, at 7:00 PM UTC

More info: Users can access SharePoint Online sites from other browsers and users can temporarily restore access to sites through Microsoft Edge by clearing their cache.
Users see the following error message when they encounter this issue:
"AADSTS900411: The request is not properly formatted. The parameter 'login_hint' is duplicated" Current status: Due to the complexity of this issue, our review of recent service changes has been inconclusive so far. We're continuing our extensive review of available diagnostic data, such as Unified Logging Service (ULS) logs and Evolved Security Token Service (ESTS) logs to isolate the source of this problem. Scope of impact: Impact may occur for any user attempting to access SharePoint Online sites via Microsoft Edge. Next update by: Thursday, September 1, 2022, at 9:00 PM UTC

More info: Users can access SharePoint Online sites from other browsers and users can temporarily restore access to sites through Microsoft Edge by clearing their cache.
Users see the following error message when they encounter this issue:
"AADSTS900411: The request is not properly formatted. The parameter 'login_hint' is duplicated" Current status: We've identified that a recent change in Microsoft Edge build 104.0.1293.70 caused a feature issue within the Edge browser’s ability to allow users to automatically sign into sites with a current work or school account, which is causing the browser to send multiple login hints when users attempt to sign into SharePoint Online sites. This is occurring only for users operating Edge stable build version 104.0.1293.70 on devices with multiple registered Azure Active Directory (Azure AD) accounts, and users in this condition will be shown an error message stating that the login hint is duplicated. Additionally, we've identified that the fix for this problem will be included in the upcoming release for Microsoft Edge build 105.0.1343.23, and we'll provide a remediation timeline once available. Scope of impact: Impact may occur for any user attempting to access SharePoint Online sites via Microsoft Edge build 104.0.1293.70. Start time: Thursday, August 4, 2022, at 12:00 AM UTC Root cause: A recent change in Microsoft Edge build 104.0.1293.70 caused a feature issue within the Edge browser’s ability to allow users to automatically sign into sites with a current work or school account, which is causing the browser to send multiple login hints when users attempt to sign into SharePoint Online sites. Next update by: Friday, September 2, 2022, at 6:30 PM UTC

More info: As a workaround, users can go to: edge://settings/profiles/multiProfileSettings and turn off the following feature: "Automatically sign in to sites with your current work or school account?"
Please note that turning off the feature will stop disambiguation but not stop Single Sign On (SSO).
Users can access SharePoint Online sites from other browsers and users could temporarily restore access to sites through Microsoft Edge by clearing their cache.
Users see the following error message when they encountered this issue:
"AADSTS900411: The request is not properly formatted. The parameter 'login_hint' is duplicated"
Current status: Upon further investigation, we’ve determined that a Microsoft Edge browser client feature that streamlines Azure AD SSO for users with multiple Azure AD accounts on one machine utilizes the URL property “login_hint” to disambiguate between accounts during the authentication process. We found an interaction that occurred between SharePoint Online sites and the Edge client browsers running builds 102-104 in which this property is escaped to “login5%hint” and the Edge clients don't correctly identify this as the required property, inserting a duplicate, non-escaped version when authenticating to these sites. Both versions of the property were then recognized and the user would be shown a duplicate property error which prevented them from accessing SharePoint Online sites. We’ve successfully deployed an updated version of Microsoft Edge that includes the fix to address this issue. Affected users need to be on version 105 of Microsoft Edge to experience impact resolution, which may require a manual update. If users are unable to update to the latest version of Microsoft Edge, they need to utilize the proposed workaround until they are able to update the browser and receive the fix. We’re working with affected users to ensure that this issue is no longer occurring after updating their browser, with the expectation that service should be restored.
Scope of impact: Impact may occur for any user attempting to access SharePoint Online sites via Microsoft Edge build 102-104.0.1293.70.
Start time: Wednesday, August 10, 2022, at 1:14 PM UTC
Root cause: A Microsoft Edge browser client feature that streamlines Azure AD SSO for users with multiple Azure AD accounts on one machine utilizes the URL property “login_hint” to disambiguate between accounts during the authentication process. An interaction that occurred between SharePoint Online sites and the Edge client browsers running on builds 102-104 where the property is escaped to “login5%hint” and the Edge clients don't correctly identify this as the required property, inserting a duplicate, non-escaped version when authenticating to these sites.
Next update by: Tuesday, September 6, 2022, at 7:00 PM UTC

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

Title: Users can't open recently created Excel files from within SharePoint Online lists
User Impact: Users are encountering an error when attempting to open Excel workbooks from SharePoint Online lists.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.

More info: Affected users will see the following error:
"The workbook cannot be opened"
Current status: We're reviewing recent service updates which may be contributing to impact.
Scope of impact: Any user hosted on the affected infrastructure will be impacted.
Next update by: Monday, August 8, 2022, at 10:00 PM UTC

More info: Affected users will see the following error:
"The workbook cannot be opened"
Current status: We've confirmed that a recent service update contains a code error within the previewing function which is causing an exception, resulting in impact. We're in the process of developing and validating a fix and expect to have a deployment timeline by the next scheduled update.
Scope of impact: Any user hosted on the affected infrastructure will be impacted.
Root cause: A recent service update contains a code error within the previewing function which is causing an exception, resulting in impact.
Next update by: Tuesday, August 9, 2022, at 6:30 AM UTC

More info: Affected users will see the following error:
"The workbook cannot be opened"
Current status: The fix has been submitted and we anticipate that deployment of the fix will start within the next one to three days. We're monitoring its progress to ensure the fix gets deployed and saturates throughout the affected environment.
Scope of impact: Any user hosted on the affected infrastructure will be impacted.
Root cause: A recent service update contains a code error within the previewing function which is causing an exception, resulting in impact.
Next update by: Thursday, August 11, 2022, at 9:00 AM UTC

More info: Users may encounter the error message "The workbook cannot be opened", when attempting to open Office 365 files from SharePoint Online lists, resulting in read-only view.
Current status: The previously submitted fix does not fully address the outlying issue. We're looking into Unified Logging Service (ULS) logs and recent changes, to form a remediation plan.
Scope of impact: Any user hosted on the affected infrastructure and attempting to open or save Office 365 files in edit mode from SharePoint Online lists may be impacted.
Root cause: A recent change contains a code error within the previewing function which is causing an exception, resulting in impact.
Next update by: Thursday, August 11, 2022, at 6:00 PM UTC

More info: Users may encounter the error message "The workbook cannot be opened", when attempting to open Office 365 files from SharePoint Online lists, resulting in read-only view.
Current status: We suspect that a file locking issue may be causing this impact. We're reviewing an internal reproduction of the issue to deepen our understanding and formulate appropriate next steps.
Scope of impact: Any user hosted on the affected infrastructure and attempting to open or save Office 365 files in edit mode from SharePoint Online lists may be impacted.
Next update by: Tuesday, August 9, 2022, at 10:30 PM UTC

More info: Users may encounter the error message "The workbook cannot be opened", when attempting to open Office 365 files from SharePoint Online lists, resulting in read-only view.
Current status: We've confirmed that a recent service update contained a code error that resulted in a file locking scenario within the file preview feature. The impact of this is preventing users from opening or saving Office 365 files in edit mode from SharePoint Online lists. We've developed and are in the process of validating a fix via our internal testing environment to confirm it effectively remediates this issue for newly created files. In parallel, we are in the process of determining if additional actions are required to fully resolve this issue.
Scope of impact: Any user hosted on the affected infrastructure and attempting to open or save Office 365 files in edit mode from SharePoint Online lists may be impacted.
Preliminary Root cause: A recent service update contained a code error that resulted in a file locking scenario within the previewing function, preventing users from opening or saving Office 365 files in edit mode from SharePoint Online lists.
Next update by: Wednesday, August 10, 2022, at 12:30 AM UTC

More info: Users may encounter the error message "The workbook cannot be opened", when attempting to open Office 365 files from SharePoint Online lists, resulting in read-only view.
Current status: We've validated the fix for net new files via our internal testing environment and have completed targeted deployments to remediate impact. We've confirmed that additional actions are required to fully resolve this issue for previously impacted files, and we're in the process of developing a fix to repair the affected files. In parallel, we're reviewing our telemetry and signals to identify all files that were affected prior to completion of the aforementioned fix.
Scope of impact: Any user hosted on the affected infrastructure and attempting to open or save Office 365 files in edit mode from SharePoint Online lists may be impacted.
Start time: Wednesday, August 3, 2022, at 12:00 PM UTC
Preliminary Root cause: A recent service update contained a code error that resulted in a file locking scenario within the previewing function, preventing users from opening or saving Office 365 files in edit mode from SharePoint Online lists.
Next update by: Wednesday, August 10, 2022, at 7:30 PM UTC

More info: Users may encounter the error message "The workbook cannot be opened", when attempting to open Office 365 files from SharePoint Online lists, resulting in read-only view.
Current status: Our efforts to deploy a fix to repair files affected prior to the previous mitigation activity are ongoing. We have since developed two fixes, one that will auto-mitigate this issue, and the other that will ensure we have resolved all impacted files. We're currently in the process of testing and validating these fixes in our pre-production environments, and once it has been confirmed they are successful, we will proceed with deploying them Worldwide.
Scope of impact: Any user hosted on the affected infrastructure and attempting to open or save Office 365 files in edit mode from SharePoint Online lists may be impacted.
Start time: Wednesday, August 3, 2022, at 12:00 PM UTC
Preliminary Root cause: A recent service update contained a code error that resulted in a file locking scenario within the previewing function, preventing users from opening or saving Office 365 files in edit mode from SharePoint Online lists.
Next update by: Thursday, August 11, 2022, at 7:30 PM UTC

If you continue to experience issues, please contact the Service Desk.

Title: Users may see 'Access Denied' errors when using Graph APIs for SharePoint Online
User Impact: Users may see 'Access Denied' errors when using Graph APIs for SharePoint Online.
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're analyzing system logs to help identify the source of the 'Access Denied' errors.
Scope of impact: Your organization is affected by this event, and the issue may impact any user utilizing Graph APIs for SharePoint Online.
Next update by: Tuesday, May 17, 2022, at 6:30 AM UTC

Current status: We reviewed the logs and identified a potential authentication issue with the Graph APIs. We're continuing our analysis of the authentication requests to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and the issue may impact any user utilizing Graph APIs for SharePoint Online.
Next update by: Tuesday, May 17, 2022, at 8:30 AM UTC

Current status: We've identified that a specific feature, responsible for authenticating and authorizing user requests, is not performing as expected and causing some access Graph API access requests to fail. We're reviewing the affected feature to develop a remediation plan.
Scope of impact: Your organization is affected by this event, and the issue may impact any user utilizing Graph APIs for SharePoint Online.
Next update by: Tuesday, May 17, 2022, at 10:30 AM UTC

Current status: We've identified that components of the authentication feature are unexpectedly not present in some users' environments thus resulting in the Graph API access requests to fail. We're redeploying the affected feature within impacted environments to remediate impact. In parallel, we're investigating recent feature changes to identity why the components are unexpectedly not present.
Scope of impact: Your organization is affected by this event, and any user utilizing Graph APIs for SharePoint Online may be impacted.
Next update by: Tuesday, May 17, 2022, at 5:00 PM UTC

Current status: We've confirmed that a recent feature deployment misconfiguration has prevented components associated with the authentication feature from being available in a group of customer environments, which is producing 'Access Denied' errors when using Graph APIs for SharePoint Online. We've confirmed that our redeployment of the authentication feature to some impacted environments has resolved the impact. We're now redeploying the feature to all affected remaining environments, which is expected to remediate impact.
Scope of impact: This issue may potentially affect any of your users attempting to utilize Graph APIs for SharePoint Online.
Root cause: A recent feature deployment misconfiguration has prevented an authentication feature from being available in a group of customer environments, resulting in impact.
Next update by: Tuesday, May 17, 2022, at 9:30 PM UTC

Current status: We've completed redeploying the feature to all affected remaining environments. While we've received confirmation from multiple affected users that the impact is now remediated, our review of telemetry revealed errors continuing to persist for some environments. We're implementing additional tooling to extract logging that will assist us in determining why these errors persist and formulate appropriate steps to remediate these remaining environments.
Scope of impact: This issue may potentially affect any user attempting to utilize Graph APIs for SharePoint Online.
Root cause: A recent feature deployment misconfiguration has prevented an authentication feature from being available in a group of customer environments, resulting in impact.
Next update by: Wednesday, May 18, 2022, at 2:30 AM UTC

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

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

Current status: We're analyzing service monitoring telemetry to determine the root cause and develop a mitigation plan.
Scope of impact: Impact is specific to External users who are served through the affected infrastructure.
Next update by: Tuesday, April 26, 2022, at 1:30 PM UTC

Current status: We're continuing to analyze service monitoring telemetry, in addition to network trace logs to help us determine the next troubleshooting steps.
Scope of impact: Impact is specific to external users who are served through the affected infrastructure.
Next update by: Tuesday, April 26, 2022, at 3:30 PM UTC

Final status: We've identified that a recent standard service update unexpectedly introduced a code regression which resulted in impact. We've reverted the change and confirmed by monitoring service telemetry that the impact has been remediated.
Scope of impact: Impact was specific to external users who were served through the affected infrastructure.
Start time: Friday, April 22, 2022, at 5:02 AM UTC
End time: Tuesday, April 26, 2022, at 2:36 PM UTC
Root cause: A recent standard service update unexpectedly introduced a code regression which may have prevented external users from accessing shared SharePoint Online folders or files.
Next steps: - We're reviewing our standard service update procedures to avoid similar impact in the future.
This is the final update for the event.

Title: External users who attempt to access a SharePoint Online site which was shared to them are experiencing errors
User Impact: External users who attempt to access a SharePoint Online site which was shared to them are experiencing errors.
More info: Impact is specific to newly invited external users. External users attempting to access a SharePoint Online site that is shared to them are seeing the following error: "Something went wrong We're sorry, but we couldn't accept the invitation for (insert user's email that is attempting to access) at this time. Please try again later, while we try to automatically fix this for you"
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 30 minutes.
Scope of impact: Any external user attempting to access shared SharePoint Online sites is affected.

More info: Impact is specific to newly invited external users. External users attempting to access a SharePoint Online site that is shared to them are seeing the following error: "Something went wrong We're sorry, but we couldn't accept the invitation for (insert user's email that is attempting to access) at this time. Please try again later, while we try to automatically fix this for you"
Current status: We're investigating service side logs to understand where impact is occurring. In parallel, we're investigating if there have been any recent changes which are causing impact to our service.
Scope of impact: Any external user attempting to access shared SharePoint Online sites is affected.
Next update by: Friday, April 22, 2022, at 3:00 AM UTC

More info: Impact is specific to newly invited external users. External users attempting to access a SharePoint Online site that is shared to them are seeing the following error: "Something went wrong We're sorry, but we couldn't accept the invitation for (insert user's email that is attempting to access) at this time. Please try again later, while we try to automatically fix this for you"
Current status: We've identified a potential cause in our service logs so we're attempting to reproduce this issue to better understand what sites are affected and how we can remediate impact.
Scope of impact: Any external user attempting to access shared SharePoint Online sites is affected.
Next update by: Friday, April 22, 2022, at 5:00 AM UTC

Current status: We've discovered a recent change intended to improve customer experience has inadvertently caused impact to our service. We've stopped the offending code change, which we have confirmed internally, will remediate impact. We're reaching out to some affected tenants to confirm impact is remediated.
Scope of impact: Any external user attempting to access shared SharePoint Online sites is affected.
Start time: Tuesday, April 19, 2022, at 7:11 AM UTC
Root cause: A recent change intended to improve customer experience has inadvertently caused impact to our service.
Next update by: Friday, April 22, 2022, at 7:00 AM UTC

Final status: We've determined that stopping the offending code change was successfully completed and have received confirmation from some impacted users that the service is restored.
Scope of impact: Any external user attempting to access shared SharePoint Online sites was affected.
Start time: Tuesday, April 19, 2022, at 7:11 AM UTC
End time: Friday, April 22, 2022, at 4:39 AM UTC
Root cause: A recent change intended to improve customer experience inadvertently caused impact to our service.
Next steps: - We're reviewing the offending code change in order to prevent this from occurring in the future.
This is the final update for the event.