original
The Naval Sea Systems Command (NAVSEA) Made Itself a Prisoner of Microsoft, a Back Doors Vendor
The Register MS has this new article discussing so-called 'cloud' "stuck in Azure without rebuild". I experienced this sort of thing at work - companies that locked themselves inside Microsoft and wanted to get out.
Quoting The Register MS:
Microsoft has the US Navy over a barrel, as the service admits it can't separate its custom-built cloud environment from Azure infrastructure without a complete rebuild "from the ground up."The Naval Sea Systems Command (NAVSEA) published a sole-source justification letter on Tuesday (with award amounts redacted, naturally) explaining how it can't transition its custom cloud platform to a higher Department of Defense (DoD) security level without Microsoft.
Per the justification letter, NAVSEA Cloud was built with total dependency on services like Azure Data Transfer, Azure Kubernetes Service, Azure SQL PaaS, and others.
"Without the use of these services, the NAVSEA Cloud Program mission systems would be unable to provide critical mission capabilities," the letter argued. "It is infeasible to modify Microsoft's unique applications to work within another cloud service provider's environment."
An associate has dubbed that "part of the TCO" (beyond just Windows) and "vendor lock-in," suggesting that we "please link to earlier EU documents on the exit cost being part of the TCO".
It's important for companies not to allow Microsofters to make any decisions and get themselves wrapped up in Microsoft to begin with. █