![GossiTheDog](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="400" height="400"><rect fill-opacity="0"/></svg>)
I have my toots set to auto delete after a week unless I favourite them, so bringing back this one from Google cache.
Update; Microsoft snuck out a blog admitting DDoS, didn’t mention Microsoft 365, Outlook, Exchange, OneDrive or Azure impacts, posted it on Friday night after refusing to comment all week to media and customers, then didn’t link it on their social and news channels.
If anybody is wondering I have more to come on the Microsoft DDoS group, I’m just on vacation this week so haven’t written up. It’s the same people who go on about the “darknet parliament”, and who claimed they stopped European banking network (they didn’t).
None of the techniques used so far are new. MSFT response customer side has been horrible which is concerning.
@eljefedsecurit yeah I reupped it over that. Friday night news drop when nobody would cover it, forgetting to mention solutions impacted etc 
@GossiTheDog i always enjoy your reading conspiracies. 
@eljefedsecurit Friday night news drop without mentioning Azure or M365 impacts is less conspiracy and more ‘classic Microsoft’
@GossiTheDog just another example of no news in the truth and no truth in the news.
![jj@jjgadgets.tech](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="399" height="399"><rect fill-opacity="0"/></svg>)
@GossiTheDog why the auto delete? CYA?
@jj partly to save my own storage as I run my own mastodon instance
@GossiTheDog I'd do that if I wasn't both a hoarder and sentimental about my posts lol.
@GossiTheDog What do you use for the storage?
@GossiTheDog
Wonder how much ransom they paid.
@GossiTheDog absolutely fucking standard for Azure InfoSec comms. Disgusting
smh
@GossiTheDog you hate to see it.
Look how easy it is to throw away all the effort Microsoft had put into earning back trust with 10 or 15 years of improved comms and focused security initiatives.
I feel so sorry for the people toiling away to make that happen only to have the org to forget why they did it in the first place and make the same stupid decisions that dug them that awful hoke in the first place. 
@GossiTheDog Is that the one from the 16th? Just looked it up and it says "a network issue". That would be one massive understatement. Why would they be vague about it? That it could mean their DDoS mitigation is not up to snuff?
Edit: Ah wait, your mentions are for earlier cases in June.
@asmodai it was outages in Outlook (Exchange Online), OneDrive, Azure portal
@GossiTheDog Honestly I'm a little surprised anyone could provide a ddos but enough to effect a cloud provider. Don't they buy monstrous bandwidth for the outbound and get extra inbound capacity as a side effect?
@GossiTheDog interesting how often the (lack of) response is more concerning than the incident itself
@mkoek yep. Anybody can get DDoS’d or otherwise attacked.. it’s never the event that’s the problem, lack of transparency is, as you have to trust your provider. If you lose trust it’s a bad thing.
all the schools in Germany, running (illegally) 365, will be happy that holiday season is about to start :)
@GossiTheDog my guess is that a significant portion of the attack came from Azure-hosted systems. That would be very embarrassing and would explain why they haven’t said much about the attacks.
@GossiTheDog so where are we now? M361? M359?
@GossiTheDog This is justice standard Microsoft behaviour.