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.
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. That’s outrageous because the implicit promise of the cloud is that it delivers more value for less effort.






