Greenwood

We are currently monitoring elevated capacity utilization at the Europe (France) data center. To maintain service quality, this location has been temporarily removed from rotation for new connections. Customers with existing connections will remain connected and can continue using the service without interruption. New connection attempts will be automatically redirected to the nearest available data center configured for your organization. Customers connecting using a location-specific address may receive a certificate warning. We recommend using the automatic selection address to ensure seamless connectivity. Our engineering team will continue to monitor capacity throughout the day and will provide further updates as more information becomes available. We sincerely appreciate your patience and understanding. We're Here to Help If you have any questions, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.

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're continuing our restoration efforts regarding this issue affecting a subset of channels with custom message retention settings. While we work to resolve this issue, data retention processing remains paused for affected customers. We will provide another update as additional information becomes available.

The issue causing 5xx errors for IncomingPhoneNumbers API affecting Hosted Number has been identified. We are actively working with our engineers to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available.