It’s been a while since we posted something about this blog site itself.
We wanted to gather some direct feedback from you, our readers, on how we are doing with this blog. Be honest!...
Updated Jul 01, 2019
Version 2.0
Blog Post
Although this echos most of the other opinions here, the fact is that this blog is truly one of the better technical blogs out there and very probably the best being done by MS. I've been advising it as a "must read" for our Exchange admins and would be content to continue reading it at its current quality level.
The only things I can think of would be possibly a few more posts concerning some of the support issues that MS may encountering that, while not as common as the top issues, are odd enough and happening often enough that are worth commenting on.
Another would be so see a post or two regarding a recent KB article concerning a recent issue followed with a history of how the problem was discovered and documented. It would be interesting to follow this process from discovery to resolution or work-around (say, was it discovered internally by MS or did it start as an issue in the field that was researched and resolved either by the admins, MS or both?) I know that I've been very curious on occasion when I've run into an issue that I could not find an answer for via KB or newsgroups, then see a KB turn up a few weeks or months later that matches or closely matches the issue that no one else could initially confirm or duplicate.
The only things I can think of would be possibly a few more posts concerning some of the support issues that MS may encountering that, while not as common as the top issues, are odd enough and happening often enough that are worth commenting on.
Another would be so see a post or two regarding a recent KB article concerning a recent issue followed with a history of how the problem was discovered and documented. It would be interesting to follow this process from discovery to resolution or work-around (say, was it discovered internally by MS or did it start as an issue in the field that was researched and resolved either by the admins, MS or both?) I know that I've been very curious on occasion when I've run into an issue that I could not find an answer for via KB or newsgroups, then see a KB turn up a few weeks or months later that matches or closely matches the issue that no one else could initially confirm or duplicate.