But El Reg didn't use the poll-leading "Micros~1" moniker.
Nothing like that ~# ambiguity to parallel with those wrong search results.
Microsoft had to warn a subset of Office 365 administrators over the weekend that their organisation might have inadvertently featured in an outsider's internal search results. Register reader Dusty shared the notification, which read: "Under extremely rare circumstances, users performing internal search queries may have …
Out of curiosity, why are you continuing to pay them all that money? They have had decades to get it right, and yet somehow they never have. Their shit constantly leaks, has never been secure, and has never really worked right. Release after release after release. For decades. Yet you continue to pay into their brokenware. Are you a glutton for punishment? Or is it simply a case of hope springs eternal?
Not only them. I think just about every cloud out there has had some form of breach over the years.
The problem is, if it is your data behind your firewall, you have somebody you can shout at and, in the worst case, fire. With the big clouds, they just give a shrug of their Teflon-coated shoulders and carry on as if nothing happened.
When managing co-located facilities you might want to ensure that there is sufficient separation of network data and app layers not to allow any cache sharing. It might cost extra to have multiple instances for multiple customers but at least you did the sane thing of keeping the actual data not just logically separate but somewhat isolated at least. It is like using 127.0.0.1 for all customers and wondering why everyones data is exposed...
Those first two sentences are word-for-word what I was going to say.
I'd add that I've learnt a mantra from the great commentards of El Reg which is simply: There is no cloud, only someone else's computer!
I'm not at all surprised that this has happened. You put a bunch of private stuff from several different customers on the same physical hardware and it's only a matter of time before there's a leak due to a human error or some unforeseen bug.