Greenwood

Title: Users may be unable to sign in to OneNote using iOS devices User impact: Users may be unable to sign in to OneNote using iOS devices. More info: Impact is specific to users with OneNote build 16.112.717.0 or higher. Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote. Current status: Our fix deployment is taking longer than anticipated but is ongoing. We're continuing to monitor as it progresses to establish a completion timeline. Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted. Start time: Monday, July 20, 2026, at 4:36 AM UTC Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact. Next update by: Friday, August 21, 2026, at 4:00 AM UTC

We have implemented corrective actions for customers impacted by this issue, including backend updates to help restore scheduled provisioning. We are currently monitoring service performance and are seeing provisioning activity resume successfully. If your organization continues to experience issues with scheduled provisioning or syncs are not running as expected, a reauthorization of the integration may be required. We strongly encourage School Administrators to review and follow the steps outlined in the Community article below: https://customercentral.powerschool.com/s/article/Schoology-SIS-Provisioning-Stops-Syncing-Due-to-Expired-OAuth-Token-Requiring-Reauthorization?language=en_US Once the reauthorization process is completed, scheduled provisioning should resume automatically. We will continue to monitor the service closely. If you continue to experience issues with your sync after following the guidance above, please contact PowerSchool Support for assistance. Further updates will be provided as needed.

We're continuing to work on restoring messages, message edits, and file shares for a limited number of workspaces that were affected by an issue with custom data retention settings. We've fixed what triggered the issue and are running data recovery using backup restoration methods. Custom retention settings have been restored for impacted channels, and we're gradually re-enabling retention jobs.We will provide another update as additional information becomes available.

Twilio customers may be experiencing voice call failures between a subset of Twilio Phone Numbers and network subscribers on multiple networks in Japan. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.