Time for frustrated M365 customers to stage a 'distributed denial of satisfaction' action
Thinks of this as a distributed denial of satisfaction attack signaling that Microsoft can't solve this particular outage with a glib apology and a blog post.
- Which is probably why Microsoft, which can clearly bill its customers regularly and reliably and therefore knows which services they use, hasn’t done the work to link its uptime meters and billing systems so it can automate crediting customers after outages.
- If Microsoft doesn’t get proactive, the magnitude of this outage represents a moment in which its customers can show the software giant it must do better – perhaps by filing so many applications for credit that managers who oversee Redmond’s systems and finances can’t help but notice a spike of activity.
- Yes, you read that right: “applications.” When Microsoft experiences an outage, customers must apply to get the service credits they’re entitled by finding the “Outage ID” related to each incident.
A quarter of a century later, Microsoft’s business practices still make its customers reluctantly share the cost of its failings – most recently last week’s massive M365 outage.
To protest that mess, Microsoft customers should create a new cloudy meltdown – on the pages the software giant uses to process applications for compensation after it fails to meet service level agreements.
- Microsoft appears not to offer a facility for bulk uploads, so the channel partners who manage so many M365 implementations have extra work to do.
- I briefly helped with Microsoft Australia’s PR efforts in the early 2000s, when IE 6 and Windows were so bug-prone they essentially represented a welcome mat for hackers and required a deluge of patches admins couldn’t handle.
- But rather than vibe-coding its way out of this, decency demands Microsoft quickly decide that all users impacted by last week’s automatically receive service credits, rather than asking them apply for their entitlements.
- Microsoft responded to that mess with a message about security being a shared responsibility involving people, process, and technology.
- The application page is buried deep in the Microsoft 365 Admin Center and the Outage ID is recorded elsewhere.
How this summary was made: extractive summary — built from the sources' own reporting. It is drawn only from the reporting of the sources listed below — read the originals for full detail. How we summarize →