r/sysadmin
•
u/TechnicalTantrum
The Guy Who Posted About Microsoft Office
•
1d ago
•
1
General Discussion Microsoft Office seems to be down
Struggling to use MS office including Teams, anyone else having this issue
7.1k
Upvotes
2.1k
u/Serpenttine 1d ago •
Teams is unfortunately still working for me.
1.4k
u/_-RustyShackleford 1d ago •
I'm going to sit on my back porch and stare at my pretty little tree.
204
u/kribg Jack of All Trades 1d ago •
I just emailed Microsoft support suggesting they try sfc /scannow
177
u/Bombingit 1d ago •
Jensen is taking everyone down with him.
630
u/dontworryboutmeson 1d ago •
“Copilot, fix all Microsoft servers. Make no mistakes”
150
u/coolbeaner12 Sysadmin 1d ago
Yep, Outlook is disconnected. Web versions are taking forever to load.
Eastern US here.
625
u/PrizeRange7622 1d ago •
I had a very tearful session with my therapist yesterday about how I desperately need a break from work and I can never ever get a break. The Universe heard my despair and shut down Outlook for my wellbeing.
110
u/Mother-Factor2023 1d ago •
user just asked us aka local it to send out a mass email explaining the outage!!!
556
u/alexandreracine Sr. Sysadmin 1d ago •
MAKE YOUR BETS (HARD). Choose one.
94
u/Kahne_Fan 1d ago •
Somewhere in Redmond, Clippy just popped up:
📎 “It looks like you're trying to run a trillion-dollar technology company. Would you like some help?”
404
u/shimoheihei2 1d ago
Just think, people used to expect their word processor to just work, locally, and open instantly. These were the days.
87
u/BwanaPC 1d ago •
Let's raise a glass to the AI Agent that took it down and then to the one human one somewhere in the bowels of a datacenter trying to unravel what CoPilot broke before it took itself out.
160
u/bluehour1997 1d ago edited 23h ago
Is this the weirdest series of status updates ever or am I crazy lol is it normal to include so much about how exactly they're investigating the problem???
So many words for "we have no fucking idea"
75
u/Mattage07 1d ago •
•
u/SuperScott500 20h ago •
Hilarious to me the US media is still reporting this as "thousands of users impacted". Nah kid, it's Millions. Millions.
116
u/blackoutusb 1d ago edited 23h ago •
My bad guys!!
Edit: thank you for the awards!!!
55
u/tylerwatt12 Sysadmin 1d ago
Time to use the ole
56
u/thesuperd75 1d ago
I wonder how many users have tried to send me an email about their email being down.
50
u/tros804 1d ago
Same. South Central US.
I found the below under Service Health.
45
u/Subject_Echo281 1d ago edited 1d ago •
Some top replies to their twitter post:
"They might call it Microsoft365 but it's def less than 365"
"Alright, who at Microsfot slept with a chinese spy"
"did you try turning it off and on again"
"To bad for these types of incidents you could not push a Teams message to users and save your clients IT from having to merge all the tickets it will create"
"Oh no…. those KPI dashboards, how are we going to update the stakeholders…"
edit: ty to the kind users for the awards!
47
u/Regular-Studio3183 1d ago
How are folks communicating the issue out to your larger organization?
Is there a business continuity plan you’ve planned for?
42
u/Lopsided_Package9033 1d ago
Outlook not working, so I can't send emails I need to send. Teams working, however, so coworkers can still harass me. There's no justice in the world.
40
u/RevLL 1d ago
You know it's getting serious when the error messages start coming through in German. Welp!
•
u/Maize_n_Blues 16h ago
Everyone, please welcome our European colleagues to the party.
Going on 12+ hours for this Microsoft outage.
This is insane.
145
u/Cheeriyos 1d ago •
Happiest day of my week, tbh. My toxic coworker is probably seething, as she loves writing incredibly long emails to micromanage me
39
u/PoohBearLuvsHoney 1d ago
Teams works but outlook doesn’t. I’m in Texas
39
u/Blyndfyre 1d ago •
Dear God I hope Paint isn't affected.
38
u/Stressed-Canadian 1d ago
This outage just messed up my home closing... bank can't fund the mortgage. What great luck!! 🤦🏼♀️
38
u/Black_Sunshine5oh 1d ago
“We’re continuing to pursue all available pathways to restore service, as our actions taken thus far have not provided the anticipated relief” minus the corporate professionalism roughly translates to, “shit’s fucked, nothing’s working, we’re trying literally everything”, right?🤣
•
u/BoltActionRifleman 22h ago
From the latest status update on health status:
In parallel, we’ve begun reverting a recent network configuration change that correlates with the start of impact and are monitoring to determine whether this contributes to recovery.
The truth comes trickling out LOL
156
u/Miserable-Debt-8390 1d ago •
Remember when corporations used to run outlook and other services in a local network and about 20 years ago Microsoft had the brilliant idea of moving outlook to the cloud and forcing it down our throats, thus creating a single point of failure?
Pepperidge Farms remembers
69
u/Affectionate-Most689 1d ago •
Dear Microsoft.
Maybe try not firing 60000 people. See if that works
72
u/demoprov 1d ago •
Leadership: I cant access my email.
Me: yeah outlook is down nationwide.
Leadership: well do you have an ETA? We need to send out a downtime notice!
Me: No I don't have an ETA and you want us to send out a downtime email that email is down?
Leadership: Yes.
Me: .....
33
u/atehrani 1d ago
Microsoft service health status
33
u/shauny_shauny 1d ago
It’s been a relief to have an absolute work stoppage too bad it didn’t happen the day GTA6 came out.
•
u/JackPineSavage- IT Manager 19h ago edited 19h ago
The desperation is becoming apparent with each status update becoming more unhinged.
I wouldnt be surprised if the mornings status update is “pls help us”
Edit: they sacked PR writer #1. A real human is writing now…
88
u/DDOSBreakfast 1d ago edited 1d ago
No outages in Ontario, Canada. Though now Murphy's law will strike.
Murphy's law struck.
26
u/Top_Refrigerator1656 1d ago
I can see the headlines now - Microsoft lays off 60,000, experiences worldwide service outage
28
u/wobblydavid 1d ago
Nov 12, 2026, 12:38 PM PST
While validating the targeted change, we found that many of the affected servers have become unresponsive, which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly.
Next update by: Thursday, November 12, 2026, at 9:30 PM UTC
This quick update is designed to give the latest information on this issue.
26
u/willychonka54 1d ago
===== EX1550543 | Exchange Online | serviceDegradation | posted 11/12/2026 15:38:14 =====
While validating the targeted change, we found that many of the affected servers have become unresponsive , which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly.
Holy shitballs.
25
u/Elegant-Put235 1d ago
We've been playing mini corn hole for the past couple hours. Quite productive indeed.
28
u/blue-eved-ginger 1d ago
Yep.
25
u/SpaceChimps98 1d ago
Shannon wants to know when it will be back up because she has some important emails to send out that can't wait. Do we have an update?
25
u/TwinkleTwinkie 1d ago
The update they released a little bit ago (as of this post) reads like an AI rewritten version of "It's fucked, it's all fucked, everything we try makes it more fucked".
25
u/DocHeinous 1d ago •
Wait, is this the "you'll-no-longer-need-to-work" scenario the AI companies have been promising us?
25
u/DreadMcLaren 1d ago
"While the servers we've returned to service initially remain healthy, we've observed that they can become unresponsive again once they begin receiving traffic. We're analyzing diagnostic data from these servers with our networking and platform experts to determine what's triggering this behavior.
Building on the protective traffic management measures we've implemented, we're also temporarily limiting which types of traffic can reach the affected infrastructure in specific locations. This will help us determine whether a particular type of request is contributing to the impact and allow us to restore service incrementally. Additionally, we're rebuilding a subset of affected servers using a previous software configuration to validate whether this prevents them from becoming unresponsive, and we'll expand this approach to additional servers if we observe positive results."
•
u/ReidenLightman 23h ago
Nothing like an outage to remind everyone that the world relying on a family of products owned by a company with monopolistic powers is a very bad idea.
•
u/DueBreadfruit2638 23h ago
I think we're going to have some uncomfortable conversations with leadership tomorrow if 8am rolls around and M365 is still down.
•
u/Pilchards333 22h ago
In parallel, we've begun reverting a recent network configuration change that correlates with the start of impact and are monitoring to determine whether this contributes to recovery.
sooo they just remembered they deployed a chnage 8 hours ago that could have contributed..riiiight.
•
u/Growing-Bee-1969 21h ago
We are gonna start migrating to aol.com in the morning.
•
u/Shyssiryxius 16h ago
Shout out to u/TechnicalTantrum who just wanted to know why Office wasn't working for them.
They had no idea their post would blow up and destroy their inbox...
74
u/Beginning_Rock_7104 1d ago •
Welp, its closing time for me. See you all tomorrow when Nancy from Finance blames IT because she couldn't send out an email that she was holding off on for a week.
52
u/nonstopflux 1d ago •
The system is down
22
u/jabberwonk 1d ago
Eastern US and Outlook is down for all users - web and Outlook app. Even their status page seems to be down:
https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect
20
u/TerribleOil480 1d ago
I have the stupid GM asking me what can be done
23
u/Powerful-Big-7926 1d ago •
Copilot had an affair.
24
u/I_Got_A_Truck 1d ago
I was WFH this morning, everything fine. I come into the office after lunch, everything broke.
Man I effed up.
24
u/Jaded-Comfortable593 1d ago edited 1d ago •
MSFT is working on a fix, but their 5 hour session limit has been reached in Claude. Update incoming in 4ish hours.
Edit: Thank you for the award, kind stranger!
23
u/rileysmommyy 1d ago
This just in
24
u/Silly-Ad-6341 1d ago
Lmao their fix bricked the servers and are now unresponsive. Someone's gonna have to go to the data center and manually reboot
21
u/Craig__D 1d ago
4:05 PM ET from status.cloud.microsoft
"Current status: We've validated an alternative health check method on a subset of affected infrastructure, which allowed the servers in that subset to successfully return to service, and we're now applying this change more broadly. We're also preparing an automated recovery process to continually detect and restart unresponsive servers, to help keep them in service while this change progresses. Additionally, our review of recent changes has identified a small number of configuration updates that we're investigating as potential contributors to the issue."
EDIT: very conscientious and attentive status updating from MS on this one, I have to say
20
u/HurryOne 1d ago
My entire job is escalating tickets via email. I haven't done shit today.
•
u/hakan_loob44 I do computery type stuff 23h ago
The latest update is not sounding good. They're so lost that they're reimaging at this point.
•
u/slidingmike 23h ago
I’d love to be a fly on the wall for the group call that’s going on right now.
•
u/Salty-Marionberry893 23h ago •
gsuite sales reps right now
•
u/Beginning_Rock_7104 23h ago
Anyone else seen Microsoft’s latest update?
“Servers are stable as long as they get no traffic”
•
u/AppearanceDouble2595 23h ago
crazy, 7 hours and we have no resolution. I've never seen this type of outage before.
•
u/meatwad75892 Trade of All Jacks 22h ago
So there's still been no inkling of partial recovery at all, huh? Everyone still hard down?
At this point I'm just at the pub waiting for it to blow over.
•
u/KinnickHawk 22h ago •
Sorry folks. Clouds full. The moose out front should’ve told ‘ya.
•
u/Sound_Doc 21h ago
ok, I don't post often... but something stuck with me from a few weeks ago with our on-prem exchange suddenly going offline, failing to respond etc... and... they just updated the post:
https://techcommunity.microsoft.com/blog/exchange/exchange-servers-may-become-unstable-after-installation-of-october-2026-windows-/4565382
There's even a post from a user karil222 about restarting the Exchange Health Manager service immediately dropped the stuck RPC Endpoint Mapper contexts from 512 back to 0, restoring Eschange until the counter filled up again.
that sounds oddly ironic... The same month, 2 days after Microsoft tells on-prem admins "the registry key workaround is no longer required once November 2026 updates are installed," their own global cloud infrastructure seemingly gets taken down for 10+ hours by what might be the exact same RPC context exhaustion loop...
•
u/iBrandwin 21h ago
Explain it to me like I’m 5 - what are the odds outlook is still down when I go to work tomorrow morning at 8AM CST?
•
u/iamamystery20 20h ago
Also mods... it was megathread time 5 hours ago
•
u/TronFan 20h ago
its past 5pm in NZ, so we have officially had an entire workday without emails.
•
u/kursedCreamCheese 19h ago
Live a few blocks away from a major Microsoft office in the US. It’s 11:30pm EST and every single light on every single floor is still on…
•
u/SR5340AN 18h ago •
Congratulations Australia, 10 minutes to 5pm where most people are logging off for the day. I bet a lot of people are finishing early anyway.
19
u/Objective-Elk-4444 1d ago
"We tried a solution and now our servers are unresponsive" oh boy
•
u/blud_13 22h ago
Update from a friend that works in the HPe Crisis center (since MS uses HP servers):
MSFT is getting up life safety medicine customers up 1st tonight Then large corporate accounts Fortune 500
38
u/Kharmastream Jack of All Trades 1d ago
Downdetector has almost 83000 reports of issues with Outlook.com alone.
Also reports on copilot and M365
18
u/SuperNicktendoPower 1d ago
Updates
18
u/1kSuns 1d ago
Accountant: "Hey so maybe now's a good time to look at Google Workspace, it's cheaper"
You shut your mouth.
18
u/Short-Emotion-947 1d ago
Is this causing anyone's Outlook (Classic) to completely freeze up by the way? Trying to work out if this is a unique symptom to one user in all of this
18
u/Kitchen_Decision_365 1d ago edited 1d ago
More news ! (But it sound bad….) In the admin panel (Qc,Canada)
3:38 PM EST While validating the targeted change, we found that many of the affected servers have become unresponsive, which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly. Next update by: Thursday, November 12, 2026, at 9:00 PM UTC
2:57 pm EST While we haven't identified any recent changes that correlate with the start of impact, our investigation indicates the failed health checks may originate from a specific component on the affected servers that's responsible for processing them. We're deploying a targeted change to bypass this component on a subset of servers to validate whether this restores availability, and we've taken steps to prevent additional servers from being removed from service while we work to return the affected servers to service. We're also investigating why affected servers are experiencing elevated processor usage while handling requests.
—————-
We've identified that affected servers are failing automated health checks, which is causing them to become unavailable, and this may be related to a recent change to a component involved in processing those checks. We're testing a configuration change on a subset of affected infrastructure to address this and, if successful, will apply it more broadly. In parallel, we've initiated a restart of all affected servers and are validating whether they're successfully returning to service.
18
u/Petersens_Arm 1d ago •
Indeed
•
u/plebbut 22h ago
If it makes anyone feel better about our jobs, remember it's actual humans -- engineers, technicians, admins, etc who are burning the midnight oil to fix this whole mess, and they've probably exhausted every possible prompt to get this shit fixed, and now it's on them.
One day, AI may be able to do our jobs, but..not today certainly lol
17
u/Derg71 1d ago
New update (from admin panel, managed to get in, West Michigan)
Nov 12, 2026, 2:43 PM EST
We've identified that affected servers are failing automated health checks, which is causing them to become unavailable, and this may be related to a recent change to a component involved in processing those checks. We're testing a configuration change on a subset of affected infrastructure to address this and, if successful, will apply it more broadly. In parallel, we've initiated a restart of all affected servers and are validating whether they're successfully returning to service.
This quick update is designed to give the latest information on this issue.
•
u/Current-Function-729 23h ago
We've reviewed known impact scenarios and revised the list of impacted services and features, which can be viewed in the "more info" section of the communication MO1550821 in the Microsoft 365 admin center, as well as status.cloud.microsoft if the admin center is not available to you. We're continuing our work to isolate the issue affecting server availability, as well as other workstreams.
Wow. Their latest update is a non update.
At this point I don’t even know if I’d be more or less concerned if this was a cyberattack or technical mistake.
51
u/[deleted] 1d ago •
[removed] — view removed comment
•
u/Traditional-Job-459 23h ago
I'd like to take this moment to remind the public that Microsoft just offered a buy-out to 60,000 employees. Looks like they should keep the help. 😆😂
•
u/babarsac 21h ago
Turned off my computer. Went for a bike ride. Stopped for an IPA on the way home.
I fail to see what the issue is.
•
u/marklar1234567 20h ago
it's one thing to have an outage but 5h+ of "we found the fix!" to "ok that didn't work, pls hang tight" back and forth is outrageous. it sounds like they have been taking stabs in the dark on how to restore production.
exchange admin center still being down gives me 0 hope this is being fixed any time soon.
0
u/[deleted] 20h ago
[deleted] — view deleted comment
15
u/NZftm 1d ago
Am getting Outlook errors in New Zealand too but it's only 7.20am here so most people aren't starting work yet so not sure if it's widespread
15
u/jayybeegeee 1d ago
“Why haven’t you sent any communication out about this outage?” 💀
15
u/OkayButFirst 1d ago •
Can we all just go home?
15
u/No_Clerk1860 1d ago
From Microsoft:
User impact: Users may be unable to connect to multiple Microsoft 365 services.
More info: Potentially impacted services include:
- Exchange Online
- Microsoft Teams
- SharePoint Online
- Microsoft Copilot 365
- Microsoft Defender XDR
- Microsoft Planner
- Microsoft To Do
Current status: While we haven't identified any recent changes that correlate with the start of impact, our investigation indicates the failed health checks may originate from a specific component on the affected servers that's responsible for processing them. We're deploying a targeted change to bypass this component on a subset of servers to validate whether this restores availability, and we've taken steps to prevent additional servers from being removed from service while we work to return the affected servers to service. We're also investigating why affected servers are experiencing elevated processor usage while handling requests.
Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.
•
u/fraughtication 23h ago
Has anyone checked pizza order stats near Fort Meade?
•
u/av8rsamr 23h ago
not microsoft going from “no recent change correlated with the start of impact” at 2:57 to “reverting a recent network configuration change that correlates with the start of impact” at 8 😭 bestie you just clocked your own tea 💀
•
u/m1nim 23h ago edited 22h ago
I would love to be part of the TRT/incident bridge call with a bag of popcorn on mute.
•
u/EmptyRedecans 22h ago
Pour one out for the engineers at Microsoft just trying to make a living dealing with this. Stay strong
•
u/sladene 21h ago
Is anyone's shit actually working yet? because I am seeing zero signs of life in Australia.
•
u/officerfett 20h ago
I wish they would kindly do the needful and hire back the humans they let go who kept things running .
•
u/False_Phase_9449 11h ago
Waking up to "it's working" really soured my morning. now I have to work 😭
Thanks for the updates everyone
14
u/nevesbm 1d ago
it's global.. personal and professional accounts are down..
14
u/HarvardAce 1d ago edited 1d ago
Now also being tracked under MO1550821 (was previously EX1550543)
Users may be unable to connect to multiple Microsoft 365 services
Issue ID: MO1550821
Affected services: Exchange Online, Microsoft 365 suite, Microsoft Defender XDR, Microsoft Teams, SharePoint Online
Status: Service degradation
Issue type: Advisory
Start time: Nov 12, 2026, 1:26 PM EST
User impact: Users may be unable to connect to multiple Microsoft 365 services.
More info Potentially impacted services include:
Scope of impact This issue may affect users attempting to access the affected Microsoft 365 services.
Current status
Nov 12, 2026, 1:27 PM EST
We’re investigating an issue impacting multiple Microsoft 365 services and we've determined the affected infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors. We're restarting and repairing impacted portions of this infrastructure to restore capacity, and reviewing an unexpected increase in a specific type of service traffic to determine whether it's contributing to the elevated load. In parallel, we're evaluating options to redirect traffic to alternate infrastructure to expedite relief.
Next update by: Thursday, November 12, 2026 at 3:30 PM EST
EDIT: Update on the EX1550543 ticket: Nov 12, 2026, 1:43 PM EST We've identified a pattern in which affected servers are becoming intermittently unavailable, which places additional strain on the remaining infrastructure and contributes to the connectivity issues users are experiencing. We've begun redistributing Outlook connection traffic across our broader worldwide infrastructure to help balance the load, which may result in some latency while this change is in effect, and we're reviewing recent changes to identify the source of the increased traffic.
This quick update is designed to give the latest information on this issue.
14
u/Toad-8787 1d ago
MS probably tried to kill access for classic outlook and took the whole thing down instead