<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Outages on Media Presser</title>
    <link>https://mediapresser.com/tags/outages/</link>
    <description>Recent content in Outages on Media Presser</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 07 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://mediapresser.com/tags/outages/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Microsoft 365 Outage Was an Authentication Failure, Which Is the Whole Problem</title>
      <link>https://mediapresser.com/the-microsoft-365-outage-was-an-authentication-failure-which-is-the-whole-problem/</link>
      <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
      
      <guid>https://mediapresser.com/the-microsoft-365-outage-was-an-authentication-failure-which-is-the-whole-problem/</guid>
      <description>Microsoft spent the first of September restoring 365 after an outage that took down Exchange Online, Teams, SharePoint, OneDrive and Copilot at the same time. Mail flow came back before search did. Users kept hitting failures across several services well after the headline recovery.
The cause was a configuration problem in a core authentication component shared by all of them.
That single sentence is the entire lesson, and it&amp;rsquo;s worth sitting with rather than filing under bad day at the office.</description>
    </item>
    
  </channel>
</rss>
