November 13, 8:17am GMT

Good morning,

We are aware of a major incident in relation to Microsoft services. Please see the following details from their own status page, which we will be referencing throughout:

"User impact: Users may be unable to connect to multiple Microsoft 365 services.

November 13, 9:39am GMT

Update from Microsoft status page

Current status: Recovery efforts are ongoing across impacted infrastructure. We are seeing early signs of stabilization, but service capacity has not yet returned to normal levels and health remains variable as traffic is carefully reintroduced.Our primary mitigation path continues to focus on service stability and controlled recovery. Engineering teams are cycling affected infrastructure through traffic drain, restart, remediation, and staged return-to-service while monitoring closely. We are also evaluating additional mitigation options to improve recovery speed and consistency. Network and traffic-management actions remain in progress, and we continue to prioritize backlog and queue health to preserve delayed mail during recovery. As part of this effort, we are extending the email timeout window to 48 hours to help protect delayed messages while service recovery continues. At this time, we are not aware of any malicious activity causing 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 recovery is complete.

Kind regards,

Giacom Cloud - Service Desk

November 13, 10:18am GMT

Update from Microsoft status page:

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.

Kind regards,

Giacom Cloud - Service Desk

November 13, 11:30am GMT

Latest updated from Microsoft Status Page:

"Current status: We've made additional progress toward service recovery, with recovery actions completed across portions of the affected infrastructure in the Asia Pacific region. Traffic is being gradually restored, and we're seeing improvements in key customer scenarios, including mailbox access and delayed email processing. However, some users may continue to experience intermittent issues.

Our focus is now on extending these recovery actions across affected infrastructure in other regions, while continuing stabilization efforts and adding supporting capacity to improve service consistency.

Reducing email queues and backlogs remains a priority, and the extended 48-hour email timeout window remains in place to help protect delayed messages as delivery catches up.

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."

Kind regards,

Giacom Cloud - Service Desk

November 13, 12:12pm GMT

Update from Microsoft Status Page:

"Current status: We’re seeing encouraging recovery progress in Europe, with service availability and email delivery performance improving across a growing portion of affected Microsoft 365 infrastructure. Japan remains comparatively more stable, while North America is also improving; however, some users may still experience intermittent issues as recovery actions continue.

We're focused on addressing the remaining areas of disruption and improving service consistency across affected regions. Reducing email queues and backlogs remains a priority, and the extended 48-hour email timeout window remains in place to help protect delayed messages as delivery catches up.

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."

Kind regards,

Giacom Cloud - Service Desk

November 13, 1:08pm GMT

Update from Microsoft Status Page:

"Current Status: We're seeing continued recovery progress across affected regions, with broader improvements now observed in North America and sustained improvements across much of Europe. We're also seeing encouraging recovery signals in Asia Pacific, although some users may continue to experience intermittent access issues or delayed email delivery as mitigation progresses across the remaining affected infrastructure.

Our focus remains on stabilizing recovered infrastructure, completing mitigation in the remaining impacted areas, and reducing delayed email queues and backlogs. We're closely monitoring service consistency and validating recovery across different connection methods as we work toward full mitigation.

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."

Kind regards,

Giacom Cloud - Service Desk

November 13, 2:12pm GMT

Update from the Microsoft Status Page:

"Current Status: We're continuing to see improvements in service availability, with email queues significantly reduced and approaching normal levels. Some users may still experience intermittent access issues or delayed email delivery as recovery continues.

We've implemented additional mitigation measures and are restoring the remaining affected infrastructure while investigating residual service issues. We're closely monitoring service health and validating recovery across affected connection methods to ensure sustained service stability.

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."

Kind regards,

Giacom Cloud - Service Desk

November 13, 3:03pm GMT

Update from Microsoft Status Page:

November 13, 4:02pm GMT

Update from Microsoft Status Page:

"Current status: We remain focused on addressing residual impact and ensuring reliable service restoration. We continue to assess recovery across various connection methods and are closely monitoring service health to verify sustained stability.

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.

Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

Next update by: Friday, November 13, 2026, at 6:00 PM UTC"

Kind regards,

Giacom Cloud - Service Desk

November 13, 6:09pm GMT

Update from Microsoft Status Page:

"Current status: We are deeply sorry for the disruption this incident has caused you and your business. We know the trust you place in our services and take that responsibility extremely seriously.

We are seeing broad recovery and stability across our services. This was a technical issue not related to cyber or AI / agents.

The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change. We have addressed the underlying issue and continue to restore service to remaining customers and regions.

Given the scale of demand, we restored services gradually, validating stability at each stage. While this took longer, it helped ensure a stable restoration. We will provide a full post-incident report once our review is complete."

Kind regards,

Giacom Cloud - Service Desk

November 13, 8:55pm GMT

Update from Microsoft Status Page:

"Current status: As infrastructure stabilizes, we're still draining queued messages and rebalancing traffic, so customers may see improved sign-in/access while delivery and processing continue to catch up. We do not have an ETA for full recovery yet. Service access can recover before mail flow fully normalizes."

Kind regards,

Giacom Cloud - Service Desk

November 13, 11:58pm GMT

Update from the Microsoft Status Page, please note that the next update from Giacom will be at, or before 10am (GMT) 14/11/26.. Should you wish to follow this in the mean time please refer directly to https://status.cloud.microsoft :

"Current status: We continue to observe sustained service recovery across the previously affected environments. Due to the severity of impact this incident caused, we're monitoring for an extended period to ensure no additional mitigative actions are required. In parallel, we're monitoring the backlog of email messages accrued during this event to ensure all process successfully before considering the issue resolved.

We're addressing all impact scenarios for dependent and related Microsoft 365 products as listed in the "More info" section below, and believe the majority of those impacted scenarios have been addressed.

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."

Kind regards,

Giacom Cloud - Service Desk