Title: Some users are intermittently unable to access the Microsoft 365 suite portal User impact: Users are intermittently unable to access the Microsoft 365 suite portal. More info: Access eventually times out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long." Current status: We're investigating a potential issue with intermittent failures when accessing the Microsoft 365 suite portal and checking for impact to your organization. We'll provide an update within 30 minutes.
Title: Some users are intermittently unable to access the Microsoft 365 suite portal User impact: Users are intermittently unable to access the Microsoft 365 suite portal. More info: Access eventually times out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long." Current status: We're investigating a potential issue with intermittent failures when accessing the Microsoft 365 suite portal and checking for impact to your organization. We'll provide an update within 30 minutes.
Title: Users in Japan may experience issues accessing Microsoft services including Microsoft Teams and Microsoft 365 User impact: Users in Japan may have experienced issues accessing Microsoft Teams and Microsoft 365 services. Current status: We've investigated a problem in which users may have experienced issues accessing Microsoft 365 services including Microsoft Teams and confirmed that service is now restored. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.
Title: Due to a third-party networking issue, users in Australia may be unable to access Microsoft 365 services User impact: Due to a third-party networking issue, users in Australia may be unable to access Microsoft 365 services. Current status: We've identified through internal monitoring that users in Australia may be unable to access Microsoft 365 services. While we reach out directly to the involved third-party provider for further insight, we're working to manually reroute impacted traffic as a potential route to remediation, which we anticipate may take effect by our next scheduled update. Scope of impact: Users in Australia may be unable to access Microsoft 365 services. This information may be updated as our investigation continues. Root cause: A third-party regional networking issue is occurring, preventing users from accessing Microsoft 365 services as expected. Next update by: Thursday, July 2, 2026, at 3:00 AM UTC
Title: Potential issues accessing SharePoint Online sites User impact: Users may be unable to access SharePoint Online sites and may notice delays or navigation errors. Current Status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within one hour.
Title: We're looking into a potential problem impacting SharePoint Online User impact: We're checking for potential impact to your users. Current status: We're received reports indicating an issue with SharePoint Online. We're investigating the issue further, and we'll provide an update within 30 minutes.
Title: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com User impact: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com. More info: Admins may be able to access the Microsoft 365 admin center via admin.cloud.microsoft as a temporary solution. Additionally, Copilot in Microsoft Teams is not expected to be impacted and can be leveraged in the interim while we mitigate the issue. Current status: This is a continuation of a communication posted under CW1387674. We’ve identified an issue with a recent deployment for Microsoft Copilot. We’re reverting to a previous build to remediate impact as soon as possible. We expect this to be completed in the next 30 minutes. Scope of impact: Our investigation indicates that any user or admin may be affected by this event. This section is subject to change as the investigation continues. Start time: Thursday, June 11, 2026, at 8:00 PM UTC Estimated time to resolve: We expect the reversion to be complete in the next 30 minutes. Root cause: The root cause is still being investigated. We will provide more information in our next update. Next update by: Thursday, June 11, 2026, at 10:00 PM UTC