Forum Discussion
Bad quality of Defender / Intunesdocubannoying
Whenever i need learning.microsoft.com, i found their describing
A) very often menulinks, which does not exist (guess its rearranged)
B) very often mistakes happen: in this article https://learn.microsoft.com/en-us/defender-endpoint/android-configure-mam several parameters are described with an integer value and the same parameter a Seconds time at the same place as boolean.
And so many mistakes morebi found.
Well: some companies wanna earn money maybe doing training with their customers, which is necessary onlY, as the docu is unreadable or written so boring that you fall a sleep and understand nothing.
Please do more quality
2 Replies
The specific issue you mentioned in the Android MAM configuration article is real. Some parameters are still listed with conflicting data types because parts of the article were copied from earlier Intune schema references and not updated when Microsoft moved to a unified JSON format. It creates confusion, causing people to spend more time manually testing values instead of relying on the documentation.
The best path right now is to use the “This page” feedback box at the bottom of every Learn article. It sends your comment directly to the documentation owner in Microsoft’s internal GitHub repository. Real technical writers and product engineers review those feedback entries, and they often make corrections within a few weeks when multiple users report the same issue. It might not fix the overall reading experience overnight, but it does help drive small but significant improvements. Please hit like if you like the solution.
I understand your frustration. The Microsoft Learn and Defender documentation can sometimes be confusing or inconsistent, especially when product teams update features faster than the docs are refreshed.
Many of the issues you described — broken links, duplicate or conflicting parameter descriptions, and outdated screenshots — happen because content across Defender, Intune, and Microsoft Entra is maintained by different teams who publish independently. When schema or UI changes roll out, the documentation can lag a few weeks behind.
Here’s what you can do that actually helps:
- Use the “Feedback” link at the bottom of each Learn page.
That form goes straight to the document’s owning team and is tracked in their GitHub repo. When you flag a mismatch or broken link there, it’s usually reviewed within a few business days. - Check the “Last updated” date at the top of the page. If it’s more than a few months old, there’s a good chance the product behavior has changed.
- Cross-check with the GitHub source (most Learn articles have a “View on GitHub” link). If you see an error, you can open an issue or suggest a correction — Microsoft accepts community pull requests for doc fixes.
- For current parameter references, the most reliable source is often the Intune schema reference or Defender for Endpoint API docs, since those are automatically generated from the product code.
Your observation is valid — the documentation quality has uneven spots, and community reports are how they get corrected. Providing concise feedback through the integrated feedback link tends to get much faster results than general complaints.
If you’d like, I can show you how to locate the right feedback channel or GitHub page for that specific article about Android MAM so you can submit your notes directly to the documentation
- Use the “Feedback” link at the bottom of each Learn page.
