Changes to Microsoft Learn’s public documentation repositories

Martin, I genuinely don’t understand how Microsoft can claim a continued commitment to high-quality technical content while simultaneously removing public contribution mechanisms and after laying off much of the technical writing organization.

I’ll acknowledge that some PRs were junk, and some GitHub issues were little more than support tickets in disguise. Anyone who worked in those repositories knows there was plenty of noise to sift through.

But let’s also be honest about the alternative. The documentation feedback control on Learn is effectively a black hole. Customers submit feedback and rarely know whether anyone saw it, understood it, acted on it, or simply closed it. GitHub wasn’t perfect, but it provided transparency, accountability, and a visible path from problem to resolution.

I say this as someone who spent nine and a half years as a technical writer at Microsoft, working on this content. I wasn’t an outside observer. I was one of the people creating, reviewing, and maintaining the documentation customers relied on.

The hardest documentation problems were never about generating more words. They were about answering the questions customers actually have:

• How does this change affect my existing deployment?

• What breaks when I migrate?

• Which authentication methods are impacted?

• What are the edge cases?

Those answers came from experienced writers partnering with engineering teams, challenging assumptions, finding gaps, and translating product knowledge into something customers could actually understand.

Community contributions helped close those gaps. I was one of the people who wanted to continue helping. Now public repositories are going away, the writing organization is dramatically smaller, and one of the few transparent feedback loops is disappearing.

Community contributions weren’t valuable because every contribution was good. They were valuable because the process was open.

I sincerely hope I’m wrong, but from where I sit, this feels less like an investment in documentation quality and more like a reduction in the people and processes that made that quality possible.