IT Team

Our team has implemented a fix for this issue. Services have been restored in most areas and are working properly. We will continue to monitor all systems to ensure full restoration. Thank you for your patience! If you experience latency when opening Event Details from the Pending Events list, a workaround is available. Use the Event List, filter for Pending events, and open Event Details from there. This provides access to the same events through a faster path while our team continues investigating improvements to the Pending Events workflow. Please contact ams-events-support.si@siemens.com if you have any questions.

Backup operations remain healthy, with success rates staying high across all services and regions following the recent changes. Work on the EWS to Microsoft Graph API migration is ongoing, and our R&D team continues to monitor for any further issues.

The electrical isolation at Equinix FR5 in Frankfurt, DEU is now complete and our engineers have begun physically inspecting the impacted network equipment. We do not yet have a timeline for full resolution while we continue to assess the extent of impact to equipment. Direct Connect connections at this location remain impaired. Customers with connections exclusively at this location will continue to experience packet loss. Customers with multi-site or redundant configurations across other Direct Connect locations are not affected. We recommend that impacted customers failover to VPN until we have more clarity on next steps and a recovery timeline. For customers using Direct Connect gateway and Transit Gateway, you can create an AWS Site-to-Site VPN and attach it to your Transit Gateway, refer to steps <a href="https://aws.amazon.com/premiumsupport/knowledge-center/dx-configure-dx-and-vpn-failover-tgw/">here</a>. For other customers, we recommend establishing an AWS Site-to-Site VPN as a temporary backup path, refer to steps <a href="https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html">here</a>. We will provide another update by August 16 5:30 PM PDT, or sooner as new information becomes available.

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: We've identified that 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. We're deploying a code fix to correct this issue and expect that it'll complete deployment by the time of our next update. 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: Tuesday, August 18, 2026, at 6:00 AM UTC