InquirerKidapawan mayor bars LGU Christmas parties outside provinceDaily MaverickPARLEY UNDER THE PINES: Finally, the science is settled on Lower Tokai fynbos — what the experts sayThe Jerusalem PostNearly 60 years after MLK's canceled Israel trip, Black Christian leaders follow his visionPunchJAMB to refund UTME fees for candidates with disabilitiesInquirer EntertainmentJeremy G faces heat over Grammy nomination claim following BINI recognitionSky TG24Guerra Ucraina Russia, Putin: "Mi aspetto grandi benefici da incontro con Xi e Trump" LIVEWirtualna Polska"Niczym po konklawe". Lewandowski opublikował wpisZDF heuteAktuelle Pressemitteilungen des ZDFVilaWebAlerta Solidària presenta un recurs contra l’empresonament del vaguista detingut a CastellóColliderThis Is the MVP of the Lord of the Rings TrilogyABC NewsMullin faces congressional hearing in the wake of historic nationwide ground stopBBC News BrasilReunião de Trump, Putin e Xi pode dividir o mundo em três? Por que cúpula preocupa a Europa
The Daily Newsstand · Free, Always
Wednesday, November 18, 2026

Time for frustrated M365 customers to stage a 'distributed denial of satisfaction' action

Translate

Microsoft is asking customers to apply for reimbursement. They should protest

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. Microsoft responded to that mess with a message about security being a shared responsibility involving people, process, and technology.

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.

REG AD

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. The application page is buried deep in the Microsoft 365 Admin Center and the Outage ID is recorded elsewhere. 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.

REG AD

That’s outrageous because the implicit promise of the cloud is that it delivers more value for less effort. Yet Microsoft requires users to do extra work to seek redress for its mistakes.

Cloud also delivers fat profits for investors. 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.

I understand Microsoft thinks AI is quite good at that sort of integration. Maybe its enormously reduced workforce will need it to get the job done.

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.

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.

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. ®

View the original on The Register →

KioskNews shows a cleaned-up reading view extracted from the publisher’s page — the original always lives on their site, not ours.