The flag raised by the Microsoft-saga

Time to do the scenarios on the true cost of a technology dependancy.

The flag raised by the Microsoft-saga

One should never let a good warning sign go to waste, and on Friday Microsoft sent the world a valuable signal that should have every organisation's attention.

The global Microsoft disruption last week (irrespective of the cause) highlights a significant risk factor that cannot be ignored - choosing to become operationally dependent on tech and IT services that are not under your own control carries with it a cost that doesn't show up outside of a possible disruption.

But when the inevitable happens, the true costs of the dependancy are made clear.

And just the same as being dependent on a powerful service provider that carries no responsibility for potential outages, assigning large chunks of your productivity value chain to AI companies, where there is also zero recourse for accuracy or service availability, is equally alarming.

So before you willingly assign much of your valuable intellectual property and dependable productivity to foreign hyperscalers who bare no accountability for the service they provide, run the possible scenarios for extended periods of disruption and data breaches to assess the true cost of the dependancy.


BTW - Microsoft aren't just sorry, oh no - they're actually deeply sorry (but that's where any recourse ends).