One would expect that.
Nah, MS needs Insiders - they laid off a bunch of Q&A folks last year:
Search results: Microsoft lays off quality assurance
From one of the articles:
but one victim group appears to have been the dedicated programmatic testers in the Operating Systems Group (OSG), as OSG is following Bing's lead and moving to a combined engineering approach. Prior to these cuts, Testing/QA staff was in some parts of the company outnumbering developers by about two to one. Afterward, the ratio was closer to one to one. As a precursor to these layoffs and the shifting roles of development and testing, the OSG renamed its test team to "Quality."
As I meniton in one of our other conversations - MS loves the Insider program (free testers) - the more participants, the better.
I've worn many hats throughout my corporate career and a 2:1 QA->Dev ratio is far too high - the change in personnel seems to be justified. On the other hand ... developers should develop, they are lousy test analysts.
Part of it is many developers don't believe documentation or thorough testing is part of their job description, but most of it is deadline pressure. There's simply no way a developer can efficiently and effectively design, write, test, and document a product (or piece of a product) given the demands of time. They can rough out documentation and component tests, filling in questions asked by other departments if needed.
QA can and should accept documentation as part of the test matrix, thereby augmenting Development and Documentation depts. Product creation and maintenance should be a team effort by all departments and not a means to 'pass the buck'.