Apparently this single outage means Office 365 uptime this year drops to 3 nines (2 nines for this month). You can claim SLA credit worth 50% service fee by applying before December 31.

▲

tuom1s a day ago | parent | next [-]

Do you have official reference for this?

▲

Arbortheus a day ago | parent | next [-]

There's two parts, the actual downtime and the SLA agreement...

At my day job, we have a calendar integration that polls Microsoft's Graph API across hundreds of Microsoft 365 tenants. We saw our first metric spike in 5xx errors at 2026/11/12 17:33 UTC. As of writing it's 2026/11/13 09:44 UTC and we are still encountering a full outage, so 16 hours and 11 minutes.

With a SLA calculator [1], assuming no other downtime this month and entering 16h11m, we get:

* Yearly SLA: 99.82%

* Monthly SLA: 97.78%

Next, what is the actual agreement? I found an SLA document list here [2].

I downloaded Service Level Agreement for Microsoft Online Services (WW) English (2026/10/01). There's a heading for Exchange Online that says:

Uptime Percentage : Service Credit

< 99.9% : 25%

< 99% : 50%

< 95% : 100%

Which seems to agree with what the original commenter said for this month.

[1] https://uptime.is/reverse

[2] https://www.microsoft.com/licensing/docs/view/Service-Level-...

▲

sugarkjube a day ago | parent [-]

> Uptime Percentage : Service Credit > < 99.9% : 25% > < 99% : 50% > < 95% : 100%

These targets feel very very low nowadays.

99% uptime for email means 3.5 days/ year no email.

(although 99.9 = about 8 hours/year would seem bearable - but maybe not for a company like microsoft)

	▲	moebrowne a day ago \| parent [-]
		> 99% uptime for email means 3.5 days/ year no email Depends on how it appears, if it was one or several large chunks that is much more disruptive than minutes per day. 3.5 days/year is equivalent to less than 15 minutes/day. It sucks no matter how you slice it, but the severity/impact depends on more than the aggregate downtime.

▲

agilob a day ago | parent | prev [-]

https://old.reddit.com/r/sysadmin/comments/1xuqu5y/microsoft...

▲

igleria a day ago | parent | prev | next [-]

Thanks for the tip!

▲

tyingq a day ago | parent | prev | next [-]

"Office 364" is apparently a trending term.

▲

devsda a day ago | parent | next [-]

We need to get beyond the arguments of 364 vs 365 and develop a new equilibrium in terms of availability that accounts for humans being equipped with these new found breaks as we spend time off of work.

https://techcrunch.com/2026/01/05/microsofts-nadella-wants-u...

▲

sierra1011 a day ago | parent | prev | next [-]

The running joke in my last shop a few years ago was "Office 265"

	▲	daef a day ago \| parent [-]
		(shameless self plug) the microsoft 362 extension[0]: replaces all occurances of microsoft/office 365 with microsoft/office 362 (not in links, just in the visible text) [0] https://addons.mozilla.org/en-US/firefox/addon/microsoft-362...

▲

ljm a day ago | parent | prev | next [-]

Microsoft Outofluck

▲

DANmode 18 hours ago | parent | prev [-]

Office 360 at one point in history.

We just don’t know how good we’ve got it, that’s all!

▲

JumpCrisscross a day ago | parent | prev [-]

I couldn't specifically say since my admin.microsoft.com fails pukes on a wildcard certificate for azureedge.net.

Also, multiple bankers I'm speaking to about Anthropic's IPO can't send or receive work e-mails. So that's a thing.

	▲	bix6 a day ago \| parent \| next [-]
		I just realized your name is the entire song / artist. Are you Jermaine Dupri?
	▲	DANmode 13 hours ago \| parent \| prev [-]
		Has someone got you at gunpoint, to be using Azure? https://isolveproblems.substack.com/p/how-microsoft-vaporize... https://www.binarysecurity.no/posts/2026/10/one-root-case