MS doesn't really have a role that focuses on the things you're talking about (though I'd really hoped the big DevAdvocate push would include "advocating on behlaf of devs" but doesn't seem that way) and they pretty much implicitly don't care about rewarding or even thanking the people that go out of their way to try to address those things or bring attention to them.

I'll just say it hurts, personally hurts, to be in Azure, bring up feedback, passionately advcate for it for the users sake, be ignored, and watch as the product is shipped ("we have as schedule!"). In at least one instance, they went so far as to basically discourage public use of the feature until theyd redone it exactly the way I'd suggested 18 months earlier. So much of it was just a result of having no idea what users wanted, where cloud computing was headed in terms of containerization and automation, and fundamental open ignorance of how and why GCE/AWS had designed similar features.