微软是不是裁到大动脉了， Outlook 故障好几个小时了，美国客户会议都开不起来了

世界就是个巨大的草台班子 AI 统治一切

居然敢给民主党上眼药水！！！
下一个就收拾他

Outlook 真是一个版本一个全新独立的软件，完全没有啥子承父业的精神

收不到邮件咋干活，直接开摆

+1
会议室都预约不了

别急，人家工程师正在问 copilot 呢

@AlohaV2 #6 那完蛋了

@AlohaV2 copilot 也是挂的

我还以是我电脑出问题了～

我靠，我说怎么半天打不开邮件了，原来是服务挂了？？

我说为啥我的邮件一直离线

VibeCoding 了一个黑盒

我在想未来会不会出现这一幕：
出问题了！服务器宕机了！
让 AI 解决，卧槽 AI 也挂了！
打开 AI 写的代码人工修复！
卧槽 AI 写的代码看不懂了！

@AlohaV2 copilot 赶紧修复这个 bug ，他们盯着我呢！

13 日凌晨 2 点就出问题了，垃圾邮件/草稿等文件夹加载不出来

可能微软工程师自己都用不明白 azure

哈哈 我刚发帖子，就看到你这个帖子了。

我还以为是我网络有问题，正战战兢兢尝试登录 claude 呢

比尔盖茨也是出轨了么

@zhujiaofan111 这已经不是未来了🤗

我他妈 excel cloud 半天没打开，什么鬼， 我还要记账呢

@zhujiaofan111 肯定会的，所以说 AI 最终会毁灭人类文明

我刚刚问了，是一个同事上班的时候带娃，娃不小心踢了电源线，然后系统就崩溃了

@huruiqing001122 谁家黑网吧

@zhujiaofan111 没了张屠户，就吃带毛猪？总会有办法的，充分发挥人的主观能动性 🐶

别急，AI 已经在处理了。

三哥 + vibe coding ，以后日子是越来越精彩了

我邮箱刚刚刷不出来，我以为要用梯子，然后连了梯子，发现还是刷不出来，以为梯子出问题了，打开了 v 站

AI 在路上

一天没收到邮件，都快下班了

@huruiqing001122 不是都上岛了吗，出轨的新闻也很久了

别急，已经在问 AI 大人了

Microsoft 364

。。。不是还没好吗原来

@brom111 没啊。啥都干不了。整个微软的在线服务没一个能用的😂

中午好了一会儿，现在又不行了

这是好事啊 哈哈哈哈哈哈

@yyzh 我就说我下午怎么又没邮件了。。夸张哇

说明卡买的还不够

不是，之前大家的论调都是认为 AI 会把所有码农替换掉吗？怎么现在又都开始怪裁员，三哥和 vibe coding 了?

看服务器状态页面，似乎他们还没定位到原因： https://status.cloud.microsoft/

社交媒体上说，最初的故障源于服务器意外离线，然后切换到备用线路的服务器后，备用的也下线，然后就一直没定位到原因了。

难道是 Ai 运维搞的鬼，然后没工程师知道 Ai 过去干嘛了？

Users may be unable to connect to multiple Microsoft 365 services

Issue ID: MO1550821
Affected services: Exchange Online, Microsoft 365 suite, Microsoft Defender XDR, Microsoft Teams, SharePoint Online
Status: Service degradation
Issue type: Incident
Start time: Nov 13, 2026, 2:26 AM GMT+8

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: Failures may occur for scenarios including access to Safe Links, Safe Attachments, protection and submission policies, and attempts to view Quarantine, Threat Explorer, and Email remediation events. Additionally, delays may occur for Tenant Allow / Block list changes, unified Role-Based Access Control, reporting, message traces, content extraction, and outbound protection. Users clicking on wrapped/rewritten URLs typically processed by Safe Links will result in a failure to navigate, as Safe Links fails to process it. Users who are able to successfully access the Quarantine portal may encounter failures when attempting to release items from quarantine.
- 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 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: 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.

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


Current status
Nov 13, 2026, 2:14 PM GMT+8
As part of our ongoing efforts to advance the recoverability of our frontend servers, we’re evaluating traffic controls that can be applied to increase capacity and stability. This includes traffic optimization actions such as traffic throttling, protocol adjustments, and failover routing intended to improve stability in active regions. In parallel, were expanding internal testing to track activity within a contained environment to improve traffic monitoring and issue detection capabilities.

As of now, we are not aware of any malicious activity that is causing this incident. We will continue to treat this incident with urgency and priority until full resolution. Once mitigated, we will provide full details of the root cause, defense-in-depth repair items, and more within a Post-Incident Report.
Next update by:
Friday, November 13, 2026 at 3:00 PM GMT+8


History of updates
Nov 13, 2026, 1:43 PM GMT+8
We’re continuing to pursue multiple workstreams to pinpoint the underlying cause of the traffic influx and advance the recoverability of the backend servers. We’re taking a measured approach to identify and repair affected infrastructure to improve the ability to confirm the developed changes were applied. We’re tracking the results of this approach to verify the servers are showing the anticipated recovery and performance intended.

As of now, we are not aware of any malicious activity that is causing this incident. We will continue to treat this incident with urgency and priority until full resolution. Once mitigated, we will provide full details of the root cause, defense-in-depth repair items, and more within a Post-Incident Report.
Nov 13, 2026, 12:56 PM GMT+8
We appreciate your organization’s patience and understanding while we work with urgency to resolve this incident.

As we’ve applied our current ongoing mitigation actions, we’ve observed a surge in outbound call volume from our routing services to our backend servers. This occurs when the backend servers outbound service cannot properly route to the backend machines. We’re continuing to observe heightened volume due to traffic rebalancing actions that we have taken throughout this event. We’re working on multiple workstreams to pinpoint the underlying cause of this traffic influx and address it.

Current actions we are taking include scaling up virtual machines to increase capacity and reduce load. Additionally, we’re querying for machines in a bad state to perform a force sync for our recent network change, which may improve service availability. However, we are encountering issues with the machines being stuck in a bad state, preventing our changes from syncing as expected. We’ll continue to monitor the effectiveness of changes applied so we can determine what refinements are necessary.
Nov 13, 2026, 12:12 PM GMT+8
We’re continuing our efforts to improve server stability to improve traffic flow. This includes adjusting traffic protocols, redistributing traffic, and applying strategic traffic blocking measures.

We're observing partial recovery across regions in which we've applied these adjustments; however, these actions aren't resulting in sustained recovery, so we're reviewing what additional actions we can take to improve overall infrastructure stability.
Nov 13, 2026, 11:36 AM GMT+8
As part of our investigation into the sustained traffic management imbalances, we’re reviewing traffic flows and affected infrastructure to identify opportunities to optimize routing. This includes verifying the reasons for service failures so we can develop specific actions to improve stability.

We will continue to share more information as soon as we have it, and for now we can confirm that there is no indication this is the result of malicious activity. We’ll continue to apply learnings towards remediation actions as we confirm effectiveness mitigation actions.
Nov 13, 2026, 10:58 AM GMT+8
We’ve monitored the status of the changes applied to improve serviceability and confirmed that change is not taking as expected. We’re identifying alternate workstreams that can be applied to increase capacity in the face of sustained traffic management imbalances.
Nov 13, 2026, 10:10 AM GMT+8
We’re applying infrastructure capacity improvements where possible in an effort to help support traffic in regions coming online. We’re continuing to monitor the results of changes applied so we can identify strategic actions that can help to improve service health across all affected regions.
Nov 13, 2026, 9:48 AM GMT+8
We’re seeing positive results with our efforts to restart affected infrastructure. We’re actively monitoring the performance of these to verify stability which will support improved availability. Remediation actions will be expanded as we confirm stability with the changes applied.
Nov 13, 2026, 9:12 AM GMT+8
Our investigation has found that a process on the affected servers responsible for establishing secure connections become

估计不修了，一直没好

微软这么大的企业也会出问题吗？什么时候我能看到的邮件啊，以后重要的数据还是慢慢迁移出来吧

离谱，outlook 还没恢复。
一些依赖邮箱验证码的网站直接没法用了。

未来这种事情会越来越多的，到处都是 vibo coding ，慢慢见怪不怪了。。。

卧槽，今天 copilot 挂掉之后，如然之间不知道怎么写 ppt 了，连写段话都懒得写了。

真的，ai 依赖性太强了， 这才养成习惯一年啊

EDGE 浏览器三个大版本都没修好一个同步问题，而且这一年坏了第二次了，真的草台

还没好,我 codex 也登不上了

@chunqiuyiyu 一帮阿三啥也不懂，全权交给 AI 意思意思，出事是意料之中的，不知道怎么修也是合理的

刚在 X 上看到官方的回复，相比起修不好，更夸张的是他们可能都不知道问题在哪

都是 ai 写的，出了问题难找的很。

一方面呢，Copilot 挂了，普通工程师问不了 Copilot ，连排查问题都做不到；另一方面呢，给资深工程师发了 Outlook 邮件，但 Outlook 也挂了，他们看不到

看不懂 ai 写的内容了，运维也交给 ai 了

当写代码的 ai 跟随某个系统一起挂了 那么这个系统就永远修复不了啦

我说怎么登不上了

一天了，还没修好啊。不行让克劳德帮忙看看吧

十几个小时了啊，微软到底行不行

不是被黑客攻击的么 有人发推 想让黑客搞 然后就出现了今天这个局面

@helloword123 不是啊。M$自己说的

头一次睡觉前到下班后一次 outlook 都没成功看过的

还刚好是周五，直接周末走起吧

这下这周的 ms 的 DRI 要睡不好觉了

现在还上不去

下班了还没修好，这微软的 SLA 怎么赔啊，也不知道会不会有故障报告

我就说怎么邮箱打不开了 原来是故障了

坏一天了还没好，这是不修了吗

teams 还活着，怎么不一起挂了完事

多发生点这种大规模故障，这样 AI 替代程序员能慢一点

还没好，微软拉完了

让克劳德帮忙看看 -> 结果发现刚刚克劳德也炸了🤣

笑死了，今天办公室贼安静，没有会议哈哈

微软 谷歌 做的产品都是咖喱味

鬼故事：现在仍然没有确定 root cause

还没好，todo 同步到现在也还没法用
很难想象这种规模的企业和服务能捅这么大娄子，还半天没有修复

我还以为我的 IP 被封了，又是切换环境又是买新 ip ，结果是 outlook 下线了，活久见。AI 时代一切都有可能

AI 到现在都还没能分析出原因解决问题嘛，看来 AI 也不咋样嘛

o365 已经挂成 o364 了

从早上四点到现在了

分享个今天早上看到的视频
《我们有一条规矩……绝对不要重启这台服务器》
https://www.bilibili.com/video/BV1LQW966Eto/

微软出这么大事, 一天都没修好啊