0
Skip to content

How to Claim Your Microsoft 365 Outage Credit

email inbox incoming mailSecureGovernComply’s Jonathan Goldberger explains the Nov. 12 Microsoft 365 outage, including the service credits you may be owed and how to build a smarter backup plan before the next disruption.

11/16/2026 4:00 P.M.

Microsoft’s Nov. 12 outage showed how much of a collection agency’s day runs through Microsoft 365. Jonathan Goldberger, CEO of SecureGovernComply, details what happened, the service credit you may be owed, and how to prepare for next time.

What Happened and What to do Next

On Thursday, Nov. 12, 2026, starting around 11:17 a.m. ET, Microsoft 365 went down worldwide. Outlook, Teams, SharePoint, OneDrive, and Copilot failed or ran unreliably for hours. Microsoft attributed the outage to a large group of servers that went offline unexpectedly. Nothing so far points to a cyberattack. Service returned gradually through Nov. 13, and some email arrived hours late.

On Thursday, Nov. 12, 2026, starting around 11:17 a.m. ET, Microsoft 365 went down worldwide. Outlook, Teams, SharePoint, OneDrive, and Copilot failed or ran unreliably for hours. Microsoft attributed the outage to a large group of servers that went offline unexpectedly. Nothing so far points to a cyberattack. Service returned gradually through Nov. 13, and some email arrived hours late.

For ARM organizations, payment files, remittance reports, and dispute documents often move by email. When email stops, so do those processes.

1. Ask for your service credit

Microsoft promises 99.9% monthly uptime for most Microsoft 365 services. When it falls short, you can request a credit, but it isn’t automatic.

Monthly uptime Credit on the affected service 
Below 99.9% 25% 
Below 99% 50% 
Below 95% 100% 

Your managed service provider (MSP) should have already reached out to you — SGC proactively contacted each of our clients. If you haven’t heard from your provider, take the steps below.

If you haven’t heard from your MSP:

  • Contact whoever sells you your Microsoft 365 licenses. That’s usually your MSP. If you buy directly from Microsoft, your IT administrator files the request in the Microsoft 365 admin center.
  • Send a written request from your company’s email address. Include when you were affected, how many staff couldn’t work, and which services were down.
  • Act soon. Claims are likely due by the end of December 2026.
  • Know what to expect. Affected organizations may qualify for a 25% to 50% credit. Under Microsoft’s SLA, 99.9% uptime allows roughly 43 minutes of downtime per month. Exceeding that threshold may qualify you for a 25% credit; exceeding about 7 hours may qualify you for 50%. Microsoft measures downtime for your organization and decides whether the incident qualifies. For a 50-person agency paying about $20 per user per month, $250 to $500 in credits is the most to expect. The actual credit is likely lower because it covers only the affected services. Any credit is applied to a future bill.

2. Don’t let email be a single point of failure

Credit card settlement files, ACH batches, remittance files, and payment confirmations often arrive by email. If email stops, so does the money.

  • List your critical email processes in each department.
  • Move critical files to secure file transfer (SFTP) or a vendor portal.
  • Set up a manual fallback and decide who confirms each file arrived.
  • Watch for late or duplicate files, so payments aren’t posted twice or missed.

3. Have a backup way to talk to your team

When Outlook and Teams both go down, staff need to know who to call.

  • Text message (SMS) tree. Keep staff mobile numbers outside Microsoft 365.
  • A second chat tool. Set up and test Slack, Google Chat, or a group-texting app now.
  • A direct line to your MSP. Keep their emergency number somewhere other than email.
  • A one-page “email is down” playbook covering who declares an outage and which tasks pause.

These channels are for internal staff only. Texts to consumers must still follow the Telephone Consumer Protection Act and Regulation F.

4. Check on your vendors

Payment processors, letter vendors, dialers, and client portals can all depend on Microsoft 365.

  • List vendors that had delays or errors on Nov. 12 and 13.
  • Ask each in writing what was affected and what they are changing.
  • Keep their answers in your vendor management records.

Golberger will also present on the service credit and other steps to take after the Microsoft outage during the ACA Huddle announcements for members on Wednesday, Nov. 18.

About SecureGovernComply (SGC)

SecureGovernComply (SGC) is the only Alliance ACA partner that provides managed cybersecurity, managed IT, and managed compliance. We help ACA members keep their technology secure, compliant, and running. We’re here to reduce risk for our clients, and when something does go wrong, like the Microsoft outage, we proactively file Microsoft SLA credit claims on their behalf.

ACA members can reach SGC at 757-734-0753 or sales@securegoverncomply.com.

Related Content from ACA:

 

Remember to subscribe to ACA Daily and Member Alerts under your My ACA Assistant profile when logged in to acainternational.org. 

If you have executive leadership updates or other member news to share with ACA, contact our communications department at comm@acainternational.org. View our publications page for more information and our news submission guidelines here.

One moment please...

Share Profile

This site utilizes cookies as included in our Privacy Policy and User Agreement.