MicrosoftFor the first time, MS had a good feedback system, called GitHub issues. I won't rephrase all the benefits that others here mentioned here. The only drawback of GH issues, is that issues were not cleaned in a timely manner by the MS employees, and accumulated over the years. It was the same problem with the old "UserVoice" system, which MS used few years back for various products such as Intune. Bugs and product enhancement were not cleaned or officially discarded, and over the years, the intention of the requestor was barely understandable (the voting system was a disaster to be honest...), or there were tons of duplicates and the poor guy hired to triage these feedbacks had no real deep product expertise.
The advantage of a public feedback system, available on a web page and with markdown!, is that you can get traction from other MS customers, or you can share temp hints to workaround a specific issue. It is sometimes also useful when you hit cases opened thru MS support tickets, where the only reply you get from PG is that it is "closing ticket because by-design" (understand "broken by-design" or "suboptimal by-design", "unusable-in-reality-by-design" but as it is by-design, your feedback lands in the bin). One thing is sure : if there is a wrong or outdated info on the MS Learn articles, and if I need to spend more than 10 min to write my feedback and prepare proper screenshots, there are 0 chances I do this if my feedback is not public (typically, I wrote this one only because it is public).
Something tells me that every 3 years, someone at MS decides to choose yet another feedback system, because it is faster to spawn a new one and put the old one in the "early retirement program" 
, rather than addressing the real problems. This disease certainly exists in my company as well, so looks nothing new to me.
