After acquisition - we were handed down the order to migrate to AWS.
This was after (in the mess of the merger) the colo contracts were basically ignored and not renewed. Once someone within the company realized the issue, it was the 11th hour.
After many, many attempts to discuss our (Operations team) concerns, we abandoned our protests. It was clear the new CTO wouldn't cave and sign the contract.
Some superficial testing was conducted and the order came down to move...NOW.
We began moving hundreds (maybe thousands) of very resource hungry DB servers first (there was no way to use something like RDS without major app/config changes).
Once the AWS bill came in, the CFO blew their lid and within 90 days we were migrating BACK to our DCs (and the millions of dollars of hardware we left idling).
Anecdotal experience - Good friend of mine who struggles with weight was taking Ozempic for about two months.
He described nausea quite often when I saw him but the results were pretty astounding.
He then hit a wall where gastroparesis would happen quite often and I happened to be at his house when one of these bouts got very severe. He went from feeling bad, to hunched over in pain and started projectile vomiting in the span of 30 minutes. He said it was clearly the meal he had eaten several days ago...it was awful.
I believe this happened to him several more times - and AFAIK he stopped taking it, and promptly regained some weight back.
Our GIS clients run WS as a Deskstop OS with ESRIs ArcGIS Pro. Incredibly common.
And once you have that - add in Active directory, DFS and random Windows Servers for running archaic proprietary licensing services.