A good incident postmortem

The article doesn't appear to mention the root cause, its very long and somewhat difficult to read - but it might be me, its early sarurday morning here.

But,what was the root cause? I'd expect to see that in the first paragraph of a post-mortem. Was it a buffer overflow, an unhandled exception because xyz? Did I miss it?

I wouldn't say it was good at all, it's mostly a load of irrelevant charts showing mostly noise, and the actual cause of the problem is summed up as "Unfortunately, that telemetry had a bug in it."

I'm surprised they can ever figure anything out if they're using those charts

not a patch on some of the cloudflare, aws or google cloud postmortems

Note that the actual link is https://blogs.msdn.microsoft.com/vsoservice/?p=16295 but I am hesitant to call out the current link at https://blogs.msdn.microsoft.com/bharry/2018/03/02/a-good-in... as blogspam.

personal taste: i am missing reading about the root cause of the problem in the first paragraph. have spent 5 minutes reading and nothing yet.. stopped altogether