Casey is also responding to unprofessionalism initiated by MS. (Though admittedly the "they started it" defense isn't a great one)
I don't get where the big issue is, a guy smugly makes a suggestion, the devs argue with it and point out that his tone isn't helping. The guy turns out to be right, the devs implement his suggestion. They don't have a history of thanking people by name so they make a vague attribution. Guy continues to be hostile against them, dev calls him out and now he's the asshole? Come on.
That's... Not better?
EDIT: Actually, I thought of a way for that to be better, but it still doesn't make anything better here. If MS is used to working with b2b, where a customer comes in with a bug and MS fixes it and pushes the fix out, there it could be reasonable to not give credit; I don't condone it but it does match the culture there. The problem is that this very much does not translate to FOSS and/or public collaboration with individuals, where there very much is a culture of sharing credit.
Someone is upset and venting. This comment comes across to me as "Ugh we already said the right words. Their distress is so inconvenient to me, why isn't it stopping?"
EDIT: Typically in this community we denote when a comment has been edited to change a critical piece of the message...
I'm detecting very little genuine authentic empathy