テクノロジー · Microsoft 365の障害継続報道 · 全5件中3件目のレポート
復旧が部分的なまま、マイクロソフト障害で医療検査や最終面接が延期
オーストラリアの人々は、検査の延期、医療関連業務の中断、最終面接がさらに1週間延期されたことを語っている。マイクロソフトは安定性の向上を報告しているが、世界規模で持続的に復旧したかどうかは確認されていない。
執筆 10分で読めます · 167件の情報源
原語の動画
英語の原文から翻訳されています。
前回のレポートからの変化
1時間後
今回
オーストラリアの人々は、検査の延期、医療関連業務の中断、最終面接がさらに1週間延期されたことを語っている。マイクロソフトは安定性の向上を報告しているが、世界規模で持続的に復旧したかどうかは確認されていない。
動いたこと
- アイリッシュ・タイムズは、夜間に何度も復旧したサーバーが再びクラッシュしたと報じた。それまでの安定性に関する説明は、新たな障害によって覆された。
- マイクロソフトは、トラフィックの最適化後にサービスの安定性と容量が向上したと報告し、持続的な復旧を目指して、影響を受けた地域全体に対策を拡大した。復旧を達成したとは宣言していない。
マリア・デローサさんは交通事故の後、医療検査を受ける必要があった。しかし、本人もメルボルンの診療所も、紹介状をメールやファクスで受け取ることができなかった。検査は中止または延期されたと、デローサさんはABCニュースに語った。患者と必要な検査との間に、通信の断絶が立ちはだかった。4
メルボルンのマニー・フローレスさんは、その面接のためにTeamsに入ることができなかった。彼はほぼ1年間失業しており、選考の最終段階まで進んでいたが、面接は翌週に再調整された。彼にとって接続障害は、仕事についての返事をさらに待つことを意味した。アデレードのピーター・ロッシュさんは、認証の問題で会計ソフトにアクセスできず、請求書を処理できなかったと述べた。注文は入らず、請求書も送れなかった。彼は数千ドルを失ったと語った。これは自身の事業についての証言であり、より広範な損失を監査した推計ではない。4
同じくメルボルンの作業療法士ローレン・ヴァン・インゲンさんはABCに、Outlookにアクセスできなくなったことで、運動ニューロン疾患、ハンチントン病、その他の神経疾患のある人々が自宅で安全に暮らすための機器を入手する支援業務が止まったと語った。デローサさんの証言は、医療検査を受けることが妨げられた状況を別途伝えているが、その結果として負傷や医療上の転帰が生じたとは示していない。4
教育にも固有の依存関係があった。メルボルンの学生エミリー・ユーさんは、残るVCE(ビクトリア州教育修了資格)言語科目の試験2つに備える中で、教師の助けや学習課題にアクセスできなくなったと話した。リズモアのスーザン・ウォレスさんは、TAFE NSWなどで使われているTeamsの仮想教室を利用できなくなったと語った。どちらの証言にも、中止になった授業や影響を受けた学生の総数は示されていない。4
復旧が定着していない理由
進展、後退、そして慎重な改善
この通知は、08:30 UTCまでに次の更新を行うと予告していた。これは情報提供の目標時刻であり、復旧期限ではない。その後に取得された文面にも、以前の作成時刻が記載されたままだった。完全復旧の時刻は示されていない。167
1つの依存関係、さまざまな障害
公開通知に記載されたのは、製品とサービスの20項目であり、20のアプリケーションが全面的に利用不能になったという意味ではない。分類には重複があり、中心となる違いは機能面にある。Exchange Onlineやメールに依存する機能は失敗する一方、同じ製品の他の部分は利用できた可能性がある。167
影響は、教育ツール、デバイス登録、タスク管理、業務情報へのCopilotアクセス、セキュリティおよびコンプライアンス機能にも及んだ。マイクロソフトは、DefenderのSafe Links、Safe Attachments、隔離メールのリリース、メールの修復に加え、Purviewのラベル付け、保護コンテンツへのアクセス、法的証拠開示で障害が起きた可能性を報告した。これらは保護機能やアクセスの障害であり、攻撃者が顧客に侵入した証拠ではない。167
影響範囲は、確認できる件数を超える
不明な点
- 障害を引き起こした原因、影響を受けた利用者や組織の監査済み総数、損失の総額、コネクターの完全復旧時刻は、いずれも未解明のままだ。
今後の展開
- トラフィックが戻る中で復旧した容量が応答性を保てるか、また、繰り返された復旧の試みがなぜ失敗したのかをマイクロソフトの約束したインシデント報告が明らかにするかどうか。
受信箱が一時的に使えるようになることがゴールではない。紹介状が届き、請求書を送れ、面接が実施されるまで、システムが利用可能な状態を保てるかが試される。
タイムライン
4日目 · 5 件のレポート
当社の放送 · 第3報現在地
復旧が部分的なまま、マイクロソフト障害で医療検査や最終面接が延期当社の放送 · 第4報続報あり
Microsoft、遅延メールを48時間保護 障害からの復旧は未完了Microsoftが発表した、顧客への影響が続いた期間の終了時刻。
Microsoftは、影響を受けた残る顧客と地域でサービスが復旧したと発表し、遅延メールの監視を続ける。
暫定報告書を公表。ラマンナ氏がXで謝罪。
情報源123
媒体別の全情報源
123媒体の167件の情報源· 引用の多い順
Workhorse Group, Inc.workhorse.com5
Google News Pakistan (PK:en)theguardian.com4
- 最初の報道
- A global Microsoft 365 outage has hit thousands – what happened and when will it be fixed? - The Guardian
- Microsoft begins restoring services as global outage affects Outlook and Teams
- Microsoft outage live: Microsoft scrambling for new ways to fix global outage after initial attempts fail to restore Outlook services | Microsoft | The Guardian
- ‘Looks like we’ll have to talk to people’: Australia sent back to time before email with major Microsoft outage | Microsoft | The Guardian
Google News Singapore (SG:en)channelnewsasia.com4
- 最初の報道
- Some Singapore government systems affected by Microsoft outage: GovTech - CNA
- Microsoft 365, Outlook down for thousands of users - CNA
- Microsoft outage drags on for hours, disrupting Outlook, Teams for thousands, including Singapore users - CNA
- Microsoft Outlook outage: Disruptions hit workers worldwide amid setback in recovery efforts - CNA
Google News السعودية (SA:ar)cnn.com4
- 最初の報道
- Global Microsoft outage leaves millions without access to Outlook email, Teams and other tools - CNN
- "عطل" يصيب مايكروسوفت 365 وأوتلوك.. والشركة تعلق - CNN Arabic
- Microsoft outage live updates: Services including Outlook down globally | CNN Business
- Massive Microsoft outage disrupts businesses, schools and governments around the world | CNN Business
BBCbbc.com3
- 最初の報道
- Outlook: falha na Microsoft deixa email fora do ar email e afeta Teams, Microsoft 365 e outras plataformas; o que se sabe
- Una falla en Microsoft deja fuera de servicio el correo electrónico de Outlook y otras plataformas
- Microsoft outage sees Teams, Outlook and Copilot suffer 'connectivity issues'
reddit.com3
- Microsoft 365 outage (EX1550543 / MO1550821): Microsoft's status updates so far, in order : r/sysadmin
- Microsoft 365 outage (EX1550543 / MO1550821): Microsoft's status updates so far, in order : r/Office365
- Yesterday's M365 outage (EX1550543 / MO1550821): Microsoft's updates in order, and the lessons for admins : r/Office365
365Fanatic365fanatic.com2
ABC Newsabcnews.com動画1本2
放送時の内容
- Microsoft's outage has delayed medical scans and a final job interview. The company reports better server stability, but it still classifies the incident as service degradation.
- On November 13, we reported repeated recovery failures and disruption to government correspondence and financial-sector work. The additional accounts show what those failures cost people. Can the repaired systems stay responsive as people return to work?
- Manny Flores couldn't get into Teams for his final job interview in Melbourne. He'd been unemployed for almost a year. The interview was moved to the following week, extending his wait for an answer about work.
- In Adelaide, Peter Roche said authentication problems blocked his accounting software and stopped him processing invoices. Orders weren't arriving and invoices weren't going out. He described losing thousands of dollars.
- Melbourne occupational therapist Lauren Van Ingen said she was locked out of Outlook. That stopped work helping people with motor neurone disease, Huntington's disease and other neurological conditions obtain equipment to live safely at home.
- Maria Derosa, also in Melbourne, said scans after a car accident were cancelled or delayed. She and the clinic couldn't retrieve referrals through email or fax. She described being unable to get the tests she needed to check that she was okay.
- Emilie Yu was preparing for two remaining VCE language exams in Melbourne when she lost access to teachers' help and work. In Lismore, Susan Wallace described losing Teams virtual classrooms used at TAFE NSW and elsewhere.
- Those accounts add specific interruptions to education and care. Earlier assurances about available clinical services applied to particular organizations and functions. They couldn't guarantee that every patient could obtain a referral or keep an appointment.
- The disruption crossed working days and continents. Public agencies lost communications in Los Angeles. Bank employees couldn't access email or Teams in Hong Kong. Government systems were affected in Singapore, while Melbourne residents described interrupted work, care and study.
- The incident began around noon on the US East Coast on November 12 and continued into November 13. The different dates in American and Japanese accounts describe the same continuing outage across time zones. By Friday morning, it had already lasted more than twelve hours.
- Outlook complaints peaked at nearly 140,000 worldwide. The US peak exceeded 130,000, with more than 25,000 still being logged that evening. These are complaint reports with different scopes, rather than a count of unique people.
- Complaints reached 74 countries and territories within about an hour. Nearly three in ten reports during an early reporting window came from outside the United States. Users in Denmark were among those affected; the number affected in Finland wasn't known.
- In Singapore, Outlook reports rose from about 730 to 1,130 in an hour. Microsoft 365 reports rose from 434 to 566 during a separate morning window. Different products and reporting windows can't be combined into one global outage curve.
- Microsoft says more than 430 million people use its Microsoft 365 apps, and more than 90 percent of Fortune 500 companies use Copilot. Those adoption figures explain the dependency. Nobody has supplied an audited total of affected users or a worldwide financial-loss figure.
- Subscribe to this channel to follow whether Microsoft's recovery holds and how essential services recover.
- Some restarted servers initially looked stable. Later, restored servers stopped responding again. A gradual-recovery announcement in Australia was followed about an hour later by renewed unresponsiveness. An inbox briefly working again couldn't guarantee that the repair would hold.
- Microsoft says servers unexpectedly became unavailable, leaving the remaining infrastructure carrying too much work across multiple regions. The company distinguished that loss of capacity from a surge in customer demand.
- Losing servers concentrated requests on the machines still operating. Some couldn't process requests reliably or pass their health checks. Restarting them restored capacity temporarily, but returning traffic sometimes made them unresponsive again.
- The investigation included automated health-check failures and an overwhelmed process responsible for establishing secure connections. A suspected problem in a component processing server health remains a hypothesis. Microsoft hasn't identified what first made the servers unavailable.
- Microsoft's early changes weren't taking as expected. Engineers continued recovering frontend servers and adjusting traffic. Later updates described positive server-stability results after a patch, followed by better stability and capacity from traffic optimization.
- Engineers paused deployments, redistributed traffic and restarted servers. They tested alternative health checks and configuration changes, then checked stability before bringing more traffic back. A repair involving authentication or routing doesn't tell us that a defective update caused the original failure.
- The patch brought positive stability results on part of Microsoft's infrastructure. Engineers were expanding it. The later traffic changes were also being broadened across affected regions to achieve persistent recovery. Microsoft still hadn't announced full restoration.
- The public notice promised another update by 08:30 UTC. That was a target for information, rather than a restoration deadline. The notice retrieved afterward still carried its earlier authored timestamp and service-degradation status.
- Microsoft executive Charles Lamanna said there was no indication of malicious or cyber activity. Microsoft's public notice used similarly limited language. The company hasn't presented a completed forensic exclusion of every possible security cause.
- Australian Home Affairs Minister Tony Burke compared the failure to an update going wrong while relaying Microsoft's assessment. That comparison didn't identify the initiating cause. Microsoft's own investigation into the server failures continued.
- Microsoft's public notice lists twenty product and service entries. An earlier local account counted nineteen. The snapshots and overlapping categories don't show that exactly one more standalone application failed. The notice describes email-dependent features failing while other functions remain available.
- Most core Teams calls, meetings, group chats and channel messages remained available. Calendar scheduling and invitations could fail, along with some event and channel actions. Standard channels worked, and SharePoint users could still access stored files directly.
- Exchange Online was central to the disruption. People could lose mailbox access through web, desktop and mobile connections, miss their newest messages or face delayed delivery. Some Microsoft 365 administration pages failed to load, and the apps could lose their recent-files view.
- Education assignments and reading and speaking tools could be impaired. Copilot could fail to respond or access work email, calendars and files. Device enrollment and compliance checks, Planner tasks and To Do operations could also become unreliable.
- Microsoft Graph requests for email, calendars and contacts could time out, interfering with Teams management and notifications. Some Power Apps and Field Service mobile sign-ins failed intermittently. Universal Print could fail to submit jobs, while some Windows 365 customers using Purview Customer Key could lose connectivity.
- For Power Apps and Field Service, web access could provide an alternative. Already signed-in users could potentially avoid disruption by staying signed in and avoiding data clearing or reinstallation. That advice applied to those applications, with no universal fix for the outage.
- Security and compliance tools also lost functions. Defender for Office 365 could fail on Safe Links, Safe Attachments, quarantine releases and email remediation. Message traces, reporting and protection changes could be delayed. Defender XDR portal pages might not load.
- Purview labeling, data-loss prevention, authorization and classification were affected. Protected content, audit searches and legal discovery could fail. Fabric and Power BI could also struggle with sensitivity-labeled files or exports. These were protection-feature failures; they don't demonstrate that attackers breached customers.
- Removing a sensitivity label was described as a possible workaround only where an organization's data-protection policies allowed it. The outage didn't make it safe to disregard those policies.
- The Los Angeles County Sheriff's Department lost essential communications and directed inquiries to its official website. The LAPD and county district attorney also had disrupted email. Torrance said municipal services would continue. Colorado's Arapahoe Sheriff's Office reported delayed bond payments for prisoners.
- Miami Beach, Austin and Jacksonville reported email failures while keeping emergency services available. Baltimore County urged people to telephone departments. Pasadena, Fremont, Burbank and Santa Barbara also warned that email was down.
- Japan's government switched to physical documents after email disruption. The Philippines' Supreme Court warned of delayed email responses and transactions. New Zealand's foreign ministry lost email reception, including at diplomatic offices worldwide. Australian intelligence and federal-police organizations were also affected.
- Singapore's earlier assessment kept emergency calls to 995 and 999, Singpass and public officers' internal Teams communications available. GovTech warned that some replies could be delayed. Service NSW advised postponing service-centre visits and using online transactions where possible.
- The University of Iowa hospital network directed patients to its online portal after email and voicemail disruption. Several UK general practices warned of possible problems and directed urgent queries to the telephone rather than email or web forms.
- A travel account showed another email dependency. Sydney resident Livinia Drummond said a colleague's flight to Papua New Guinea was delayed because the captain's documents had arrived through Outlook. Passengers waited on a tarmac bus while someone brought printed copies on foot.
- That second-hand account didn't identify the carrier or the delay's length. IndiGo, Akasa Air and CemAir described email or system difficulties without reporting flight disruptions. Air India rerouted email and said operations and communication channels remained unaffected.
- IndiGo directed customers to its website or mobile app while incoming email support was impaired. Those different experiences show why an email outage can't be expanded into a claim of worldwide flight groundings.
- Hong Kong employees at Morgan Stanley and Goldman Sachs described losing email or Teams from logging on through lunch. Nomura staff also reported problems. In Raleigh, a medical-supply salesperson couldn't send quotes, and legal work was interrupted.
- Microsoft-connected AI tools had their own problems. OpenAI said new Microsoft connector connections might break and tools might fail. Anthropic said its connector's mail, calendar and search tools were failing for most requests, with Claude for Outlook also affected.
- Those connector notices didn't mean every part of ChatGPT or Claude was down. Anthropic also described incomplete connections and Outlook add-in failures. Neither company had provided a confirmed full restoration of these Microsoft-connected functions.
- Banks warned that criminals could exploit the confusion. Standard Chartered Singapore, Bank of Queensland and ING Australia cautioned about fake technical support, requests for personal information or one-time passwords, and attempts to gain remote access to devices.
- Workhorse Group postponed both its third-quarter earnings release and its results-and-business-outlook call because of the disruption. The call moved from November 12 to November 16 at 4:30 p.m. Eastern. The release will precede it.
- The patch and traffic changes have improved stability, but Microsoft is still extending them across affected regions to achieve persistent recovery. It hasn't given a time for full restoration. Microsoft has promised a post-incident explanation once the incident is mitigated, without setting a publication date.
翻訳更新:





