“We’re tired of Microslop”: Microsoft asked for AI tips on the day a Microsoft 365 outage hit millions, and the top reply said to “make sure that your product doesn’t fail”
Microsoft asked for AI tips as a Microsoft 365 outage took down Outlook and Teams. Image: Microsoft While Outlook, Teams and Exchange Online were falling over for businesses around the world on November 12, Microsoft Learn’s account on X asked, “What’s one AI habit beginners should build early on?” The post now has over 1.2 million views and more than 1,100 replies, and the top one says, “Make sure that your product doesn’t fail.”
Of course, Microsoft’s AI push already gets plenty of hate online, so a cheerful AI question during a Microsoft 365 outage that’s now stretched for nearly a day was always going to backfire. But is the backlash just about one badly timed post, or about how much the world depends on a company that’s betting everything on AI?
Microsoft 365, Outlook, Teams and other servicees are down (via Downdetector)Microsoft Learn asked about AI habits while Outlook and Teams were down
The Microsoft Learn post went live at 9:00 AM PT, about 40 minutes after Microsoft first confirmed Exchange Online issues. It was probably scheduled in advance, and the social media team likely had no idea what was coming. But the post is still up, and it’s now the unofficial complaint box for frustrated Outlook users.
The top reply, with over 4,000 likes, attached a screenshot of Microsoft’s Service Health Status page warning that users may be unable to connect to multiple Microsoft 365 services, including Exchange Online, Teams, SharePoint Online, Copilot and Defender XDR.
The top reply to Microsoft Learn’s AI question, with Microsoft’s own Service Health Status page. Image: X screenshotAnother reply with over 1,800 likes asked, “Not rely on Microsoft products?” Others went straight for the jugular, with suggestions like “To not YOLO server changes that cause global Outlook outages” and “To not blindly push AI generated code to production and take down half the world’s email.”
Funnily enough, one user said Outlook, Teams and Copilot all going down at once gave them “a free 4-hour tutorial” on working without AI. Another reminded the company that its Ignite conference next week “better have sessions on this.”
And of course, Microslop made an appearance, with one reply suggesting the habit should be “Not building AI Slop like Microslop!”
Users connected the outage to Microsoft’s 60,000-employee buyout offer
A big chunk of the replies went after Microsoft’s workforce decisions, from “Don’t fire staff who know how to fix stuff” to “Hire back the humans, maybe,” and the number 60,000 kept coming up.
Many replies blamed Microsoft’s workforce changes for the outage. Image: X screenshotYou probably know that Microsoft didn’t fire 60,000 people. On October 26, the company offered voluntary buyouts to around 60,000 employees, more than a quarter of its 223,000-strong workforce, at level 70 and below in the US, Canada, the UK and India.
Still, it’s easy to see why people are connecting the dots, as Microsoft is spending hundreds of billions of dollars on AI data centers while asking tens of thousands of employees whether they’d like to leave.
Also, the executive who apologized for the outage was Charles Lamanna, Microsoft’s EVP of Copilot, Agents and Platform. You might wonder why an Outlook outage got an apology from the Copilot boss. Well, since October, the Office and Teams organizations report to Lamanna’s Copilot team. So yes, Outlook is now technically under the Copilot umbrella!
Microsoft hasn’t blamed AI for the Microsoft 365 outage, and there’s no proof it did, but…
According to Microsoft’s updates, servers started failing automated health checks, and even the working ones that the company brought back became unresponsive again as traffic returned. At one point, Microsoft said a “core process on affected servers is becoming overwhelmed,” and admitted that its actions hadn’t provided “the anticipated relief.”
Microsoft paused all deployments, started rolling back a recent network configuration change that lined up with the start of the outage, and is now expanding a patch to an upstream authentication and routing component, starting with regions entering business hours. If all this sounds too complicated, just know that as of writing, the status page still shows service degradation.
User complain about the ads in Outlook while still not being able to receive email. Image: X screenshotMicrosoft says there’s no sign of a cyberattack (that would have escalated things to a whole new level), and whatever the company said so far doesn’t link the outage to AI-generated code or its workforce changes. We’ll know more when the post-incident report comes out. Meanwhile, if your business lost hours of work, you may be able to claim SLA credits from Microsoft. I highly recommend you claim this.
Microsoft needs Outlook to work before it teaches about AI habits
Outlook reports on Downdetector peaked at around 130,000 on Thursday, with businesses, airlines and government agencies among those hit, which shows how much of the world runs on Microsoft 365.
Microsoft Outlook issues reported in the last 24 hours (via Downdetector)Yes, I believe people should learn to use AI properly. But when your email, meetings and AI assistant all go down together, nobody wants a pop quiz on AI habits from the company responsible. The top reply already gave Microsoft the best kind of AI habit, and the software giant should probably build it first.