<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>data-breaches</title>
    <link>https://www.atlassystems.com/complyscore/data-breaches</link>
    <description>data-breaches</description>
    <language>en</language>
    <pubDate>Fri, 20 Nov 2026 10:46:08 GMT</pubDate>
    <dc:date>2026-11-20T10:46:08Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Microsoft 365 Outage: Third-Party Risk Lessons for Enterprises</title>
      <link>https://www.atlassystems.com/complyscore/data-breaches/microsoft-365-outage</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.atlassystems.com/complyscore/data-breaches/microsoft-365-outage" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.atlassystems.com/hubfs/microsoft.webp" alt="Microsoft 365 Outage: Third-Party Risk Lessons for Enterprises" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;On November 12, 2026, a software defect that had sat quietly inside Microsoft's network gateway servers since July finally met the right conditions. Within two hours, more than 80% of those servers stopped responding, and Outlook users in 74 countries lost access to their mailboxes for most of a day.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.atlassystems.com/complyscore/data-breaches/microsoft-365-outage" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.atlassystems.com/hubfs/microsoft.webp" alt="Microsoft 365 Outage: Third-Party Risk Lessons for Enterprises" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;On November 12, 2026, a software defect that had sat quietly inside Microsoft's network gateway servers since July finally met the right conditions. Within two hours, more than 80% of those servers stopped responding, and Outlook users in 74 countries lost access to their mailboxes for most of a day.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=5981952&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.atlassystems.com%2Fcomplyscore%2Fdata-breaches%2Fmicrosoft-365-outage&amp;amp;bu=https%253A%252F%252Fwww.atlassystems.com%252Fcomplyscore%252Fdata-breaches&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <pubDate>Fri, 20 Nov 2026 10:46:08 GMT</pubDate>
      <author>anuja.k@atlassystems.com (Anuja K)</author>
      <guid>https://www.atlassystems.com/complyscore/data-breaches/microsoft-365-outage</guid>
      <dc:date>2026-11-20T10:46:08Z</dc:date>
    </item>
  </channel>
</rss>
