Single post
In my previous job I was occationally reading Microsoft Azure documentation and always complained that it's bad - written poorly, no proper structure and highlights. I guess there's why
Thanks for the contribution here and appreciate your attention to detail. We have decided to keep as-is.. part of that decision is that more and more folks are using AI chat to access guidance and tables don't always translate well in that context.
Microsoft prefers bots over people as primary documentation consumers
As mentioned by @davidgerard