MSP

We are currently investigating reports of backup performance degradation on x360Cloud. We will follow up with more information soon. What is impacted: - Backup processing and status reporting for Microsoft 365 and Google What is not impacted: - x360Cloud web application accessibility - Previously protected backup data

The Microsoft 365 service outage is ongoing. Until it is resolved, Microsoft 365 backups and restores may fail, and new tenant onboarding may not complete. You can still view and export your backup data. We are monitoring and will share updates as the situation develops. For Microsoft’s latest status, see https://status.cloud.microsoft/

Title: Users may be unable to connect to multiple Microsoft 365 services User impact: Users may be unable to connect to multiple Microsoft 365 services. More info: Features of the Microsoft 365 services below that interact with Exchange Online and email services are impacted. Elements of those services that do not depend on interaction with Exchange Online remain functional. - Exchange Online: Users may be unable to access their mailbox using Outlook on the web, Outlook desktop (MAPI), Exchange ActiveSync (EAS), or REST-based connections, and email delivery may be delayed. - Microsoft 365 admin center: Admins may be unable to load some admin center pages. - Microsoft 365 apps: Users may be unable to view their recently used files. - Microsoft 365 Apps Admin Center: Multiple services including Cloud Update, Cloud Policy, and Inventory are affected. - Microsoft 365 Education: Features including Assignments, Reading Progress, and Speaker Progress may be impacted. - Microsoft Copilot 365: Users may be unable to load Copilot Chat or receive responses in the web and desktop apps, and Copilot experiences may be unable to access work data such as email, calendar, and files. - Microsoft Defender for Office 365: Some Defender for Office 365 experiences that rely on Purview DLP/Information Protection signals may experience delays or failures in policy evaluation and governance action enforcement. Admins/SOCs may experience delays or failures when accessing NHI features that rely on Data Classification Sensitivity Labels, including Tenant Metrics, Policy, and Data Usage, across the Identity, OAuth, and App Governance pages in the Security portal on Microsoft Defender for Cloud Apps - Microsoft Defender XDR: Users may be unable to load Microsoft Defender portal pages or solution tabs. - Microsoft Fabric: Users may encounter failures when exporting reports with sensitivity labels to PDF or PowerPoint, when updating artifacts with sensitivity labels, or opening pbix with sensitivity label in Power BI Desktop. As a workaround, users can remove the sensitivity label from the affected item to complete the operation, if their organization's data protection policies allow it. - Microsoft Graph: API requests that access Exchange Online data, such as mail, calendar, and contacts, may time out and prevent users from managing Teams, Channels, Membership, Apps management and send activity notifications using Graph API. - Microsoft Intune: Scenarios including device enrollment, device check-in, and device compliance policies may have been intermittently impacted. - Microsoft Planner: Users are experiencing Plan and Task operation reliability issues. - Microsoft Power Apps: Users may be intermittently unable to sign-in to the Power Apps or Field Service mobile apps. Affected users may be able to utilize Power Apps or Field Service on the web as a way to circumvent impact, and users who are already signed in can potentially avoid impact by not signing out, clearing app data, or reinstalling while the issue is ongoing. - Microsoft Purview: Multiple Purview services including Authorization, auto-labeling, Data Loss Prevention (DLP) across Microsoft 365 services, Communication Compliance, Information Protection label and auto-labeling policies, Role-Based Access Control (RBAC) and Data Classification are impacted, and users may be unable to open or load Microsoft Purview portal pages or protected content. Audit searches, protected content creation, eDiscovery tasks such as search and export, Data Classification and On Demand Scan features may also be impacted. - Microsoft Teams: Most of the core functionality including joining calls, meetings, group chats, and channel messages are not impacted. Scenarios that depend on Exchange Online, including Calendar related failures with scheduling, invites, viewing, and meeting edits. Creation of Live or Virtual events fail. Failures with Copilot responses for outlook, calendar, or M365 files, read history, or adding to new chats. Navigating to App chats, adding new contacts or syncing contacts in settings fail. Standard channels are working fine but users may experience the inability to create or delete private or shared channels. - Microsoft To Do: The app may not load, and users may see operation failures. - Power BI: All users may intermittently be unable to export reports with MIP sensitivity labels to PDF in Power BI. - SharePoint Online: Some users may experience issues when sharing SharePoint Online files with people outside their organization, where external sharing is permitted by both organization-level and site-level settings. Additionally, features that depend on Exchange Online may be impacted. Accessing files stored directly in SharePoint Online remains functional. - Universal Print: Users may encounter errors submitting print jobs or using admin features. - Windows 365: Customers who have configured their tenant and Cloud PCs to use Microsoft Purview Customer Key for Windows 365 Cloud PCs may have users who are unable to connect to their Cloud PCs. Current status: Recovery actions are ongoing and have progressed in phases across affected Microsoft 365 infrastructure. Global telemetry and customer reports show incremental improvement in several workloads; however, service health remains variable and capacity has not yet fully returned to baseline. Network and traffic-management actions remain active. To protect email during recovery, we’re continuing to prioritize queue and backlog processing, and the email timeout window has been extended to 48 hours to preserve delayed messages. At this time, we have no evidence of malicious activity associated with this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete. Next update by: Friday, November 13, 2026, at 11:00 AM UTC

Microsoft's investigation has found that a process on the affected servers responsible for establishing secure connections becomes overwhelmed, causing the servers to stop processing requests. Microsoft is preparing a configuration change to address this behavior that can be applied across all affected servers, and they're validating it on a subset of servers before applying it more broadly alongside restarts of the affected infrastructure. In parallel, Microsoft begun reverting a recent network configuration change that correlates with the start of impact and are monitoring to determine whether this contributes to recovery. The temporary traffic limitations Microsoft previously described at https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect are now in effect in specific locations. They are monitoring the affected servers in those locations to confirm whether they remain stable while handling a narrower set of connections, after which they'll gradually reintroduce additional traffic. For more up to date information from Microsoft see https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect

Repair vessel arrived at the Australia Singapore Cable (ASC) fault location on 5 November 2026 and is preparing to begin repairs. Repair operations require a temporary ASC power-down, interrupting all remaining services on the cable, including temporary restoration arrangements.

We are providing an update on the disruption affecting the Middle East (UAE) (me-central-1) Region. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in the mec1-az2 Availability Zone. We continue to work on recovering regional resources, as well as zonal resources hosted in the other affected Availability Zones (mec1-az1 and mec1-az3). Since the disruption began in March, most customers have been able to re-establish their operations in other Regions by restoring backups or copying data that remained accessible. AWS Support remains available to help customers who need assistance moving their applications to alternate Regions. We remain committed to supporting our customers in the UAE. We are working on replacing the affected infrastructure and will provide an update on the restoration of our services in the coming months. We have notified the relevant authorities and continue to work with them toward that goal.