Microsoft Outage Disrupts Congressional Offices, Hospitals, Schools for Hours
A single-vendor dependency on Microsoft Outlook created simultaneous operational failures across government and private institutions, raising questions about federal IT resilience policy.
A Microsoft Outlook outage that began Thursday evening and extended into Friday morning disrupted email operations at Congressional offices in Washington, hospitals, schools, and businesses across the United States, according to reporting by The New York Times.
Hundreds of Microsoft engineers and senior executives spent late Thursday in a video conference attempting to diagnose and resolve the failure, the Times reported. The outage affected Microsoft's own internal staff as well, leaving employees unable to use the company's core email product during the response effort.
Congressional offices rely on Microsoft Outlook for constituent correspondence, interoffice communication, and coordination with federal agencies. The duration of the disruption during an active legislative period is not yet quantified in public records. The House Chief Administrative Officer and Senate Sergeant at Arms, the offices responsible for chamber technology infrastructure, had not issued public statements as of the publication of this report. Requests to those offices for comment would be the appropriate channel to establish the precise scope of impact on legislative operations.
Hospitals affected by the outage depend on email systems for internal clinical coordination, scheduling, and administrative functions. The specific facilities affected and the clinical impact, if any, have not been confirmed in publicly available incident reports. The Department of Health and Human Services has not issued a statement as of publication.
Microsoft is the dominant provider of enterprise email and productivity software in the United States federal government. According to USASpending.gov, federal agencies hold multiple active contracts with Microsoft for cloud and software services, including under the Microsoft 365 Government product line. The total value of active federal Microsoft contracts is publicly searchable at USASpending.gov but was not aggregated for this report.
The incident follows a pattern of cloud-concentration risk that federal technology policy officials have discussed for several years. The Office of Management and Budget's cloud security strategy, issued under prior administrations, identified single-vendor concentration as a risk factor in federal IT architecture. Whether current OMB guidance addresses this specific risk category is documented in OMB Memorandum M-19-17 and subsequent cloud security guidance, which are publicly available.
The Cybersecurity and Infrastructure Security Agency, which monitors critical infrastructure disruptions, had not posted a formal advisory related to the Microsoft outage on its public website as of the publication of this report. CISA advisories are publicly available at cisa.gov.
The cause of the outage has not been confirmed in any official Microsoft statement cited in available source material. The Times identified the incident as a triage scenario involving top executives but did not specify a root cause in the excerpted reporting. Microsoft's Azure status history page and Microsoft 365 service health dashboard are the primary public records that would document the technical cause, affected services, and resolution timeline.
The outage coincides with a period of heightened operational pressure in Washington. Democrats won the House in the 2026 midterms, as covered previously by The Congressional Times in Republican Redistricting Effort Falls Short as Democrats Win House in 2026, and the new Congress is in a transition period with active leadership and committee structure questions.
What remains unknown: the precise start and end time of the outage, the number of Congressional offices affected, any clinical consequences at affected hospitals, and whether Microsoft has filed an incident report with any federal oversight body. The Microsoft 365 service health dashboard, CISA's incident log, and any forthcoming Microsoft public post-mortem would be the documents to establish those facts.