It's been a while so I don't remember the specifics, but we did eventually have some but not all parts in the cloud.
Look for the equivalent of https://www.microsoft.com/en-us/TrustCenter/Transparency#Tra...
(Full disclosure: I work at Microsoft)
Maybe I'm too cynical these days, but I find it pretty laughable that a statement regarding 'data sovereignty' has any real meaning at all these days.
Unless you control the hardware, you have no idea what the hypervisors are doing on your rented vm's. The idea that national actors don't / wouldn't pull anything they want from them seems comically naive to me. Christ, we can barely trust our own hardware anymore with backdoored firmware crap, IME and such..
Realistically though, most companies don't care so it's not a problem if you keep the blinkers on; their compliance folks just want the document which says it's not happening and they'll never know when it does so who cares. Their ops folks can barely use the APIs probably, let alone contemplate the impact of someone reading the memory of my databases from the hypervisors.
As an individual and someone who cares for my data or that of my clients though, that's not enough for me, and I'd never trust tnese folks with any data, only mindless compute and serving public content...
Most things are CRUD;
Current gig is a load of on-prem DBs' -- AWS boxes might hit an API in one of the datacentres which can query it for a given user, I think there's a difference between using AWS to serve HTTPS vs Hosting the whole db there (this is marketing/tracking data)
It's the difference between AWS/USGVT being able to decrypt a HTTP convo to a specifc user after we've combined a lot of data and having access to all 200TB of it..
Q. Don't you share this data over networks from time to time? A. Hell no.
Q. Is all your data siloed and bolted down to one place never to move anywhere A. Yes that is the plan actually.
Q. How do you trust the data to not take a hike in some random direction you don't fully trust A. Easy, it never gets out of my data center.
An IT director that works in a pharma company, will simply laugh after reading the "don't build private clouds" article
1> Google deleted People's account who bought Pixel from reseller. They have to beg google to restore their data, contacts. Not going to happened if you have it in your own cloud.
2> Windows 10 is full of telemetry. Imagine someone knows exactly what software you used, when you used it, for how long. Advertisement are built-in with system level. You don't own your machine anymore, Windows 10 can decide when it want to upgrade itself then lock you out from using it for hours. Your data now is in Microsoft's cloud, but you don't decide how they can use it, who they are going to sell to.
For depository reason? Sure of course, cloud is reliable on up time, expandable with a few click. But if Cloud provider decided to wipe the account with whatever reason, what you are going to do?
> Erm, no.
That can come across as a rude way to disagree with someone (it does to me).
> There is no uncertainty, only lack of awareness […]
That's dismissive (it reads as “you are not uncertain about this matter, you just think you are”) and not very helpful either.