Users sync requests may fail in OneNote desktop Win32 clients
Users sync requests may fail in OneNote desktop Win32 clients
September 28, 7:37pm
September 28, 7:37pm
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.
September 28, 7:58pm
September 28, 7:58pm
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
September 28, 8:28pm
September 28, 8:28pm
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.
September 28, 8:28pm
September 28, 8:28pm
Resolved