25
Pages Scanned
13
Pages Flagged
25
Changed Pages
52.0%
% Pages Flagged
Scan Information
Started At: 2025-12-14 04:58:25
Finished At: 2025-12-14 05:06:35
Status: completed
Target Repo: Azure
Current Phase: discovery
Files Queued: 25
Files Completed: 25
Problematic Pages
13 issues found
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/tutorial-create-assignment-python.md
...ticles/automanage/tutorial-create-assignment-python.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates Windows bias by only providing examples for creating a Windows virtual machine (no Linux VM example is shown), and by referencing Windows-specific tools and patterns (e.g., PowerShell, Windows image names). The Azure CLI installation link defaults to the Windows tab, and there is no mention of Linux-specific instructions or parity in VM creation or management.
Recommendations
- Add examples for creating a Linux virtual machine (e.g., using Ubuntu or CentOS images) alongside the Windows VM example.
- Ensure that Azure CLI installation instructions are platform-neutral or provide clear tabs for Windows, Linux, and macOS.
- Include Azure CLI and PowerShell examples for both Windows and Linux VM creation, or clarify that the CLI commands work cross-platform.
- Explicitly mention that the Python SDK and Automanage features are available for both Windows and Linux VMs, if applicable.
- Add screenshots or portal navigation steps for Linux VMs where relevant.
Create Pull Request
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/automanage-arc.md
...e-docs/blob/main/articles/automanage/automanage-arc.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation lists Windows Server operating systems first and provides a Windows-only security tool (Microsoft Antimalware) without mentioning Linux equivalents. There are no Linux-specific examples or guidance, and the participating services table includes a Windows-only service without clarifying Linux alternatives or parity.
Recommendations
- List supported operating systems in alphabetical order or alternate between Windows and Linux to avoid implicit prioritization.
- For Windows-only services like Microsoft Antimalware, explicitly mention that there is no Linux equivalent and, if possible, suggest commonly used Linux alternatives (e.g., ClamAV, ESET, etc.) or clarify the security approach for Linux.
- Include Linux-specific examples, tools, or notes where relevant, especially in sections describing services or features that behave differently on Linux.
- Add a section or table column indicating OS support for each participating service to clarify which are Windows-only, Linux-only, or cross-platform.
- Provide links to Linux security best practices or documentation for parity with Windows-focused guidance.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/automanage-smb-over-quic.md
...b/main/articles/automanage/automanage-smb-over-quic.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exclusively references Windows Server 2022 Datacenter: Azure Edition for enabling SMB over QUIC with Automanage best practices. All instructions, examples, and links are Windows-centric, with no mention of Linux support, equivalents, or alternative tools. The only referenced documentation is for Windows Server, and there are no Linux-specific steps or considerations.
Recommendations
- Clarify whether SMB over QUIC and Automanage best practices are supported on Linux VMs. If not, explicitly state this limitation.
- If Linux support exists or is planned, provide equivalent instructions and examples for Linux VMs, including supported distributions and configuration steps.
- Include links to relevant Linux documentation or tools for managing SMB over QUIC, if available.
- If only Windows is supported, consider adding a section on alternatives or workarounds for Linux users, or reference Azure features that provide similar functionality for Linux.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/move-automanaged-configuration-profile.md
...s/automanage/move-automanaged-configuration-profile.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation exclusively uses PowerShell and Invoke-RestMethod for all examples, which are Windows-centric tools. There are no examples or instructions for Linux users (e.g., using curl, wget, or Azure CLI), and the workflow assumes a PowerShell environment. This presents a clear bias towards Windows users and may hinder Linux or cross-platform users from following the guide.
Recommendations
- Provide equivalent examples using common Linux tools such as curl or wget for REST API calls.
- Include Azure CLI examples, which are cross-platform and widely used on both Windows and Linux.
- Explicitly mention that the steps can be performed from any platform, and provide code blocks for both PowerShell and Bash.
- Add a section or callout for Linux/macOS users, ensuring parity in instructions and tool recommendations.
- Avoid assuming the use of PowerShell as the default; present cross-platform options first or side-by-side.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/repair-automanage-account.md
.../main/articles/automanage/repair-automanage-account.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for ARM template deployment, but PowerShell is mentioned before Linux-native alternatives. The PowerShell module ('New-AzDeployment') is referenced directly after the Azure CLI, and no explicit mention is made of Bash or Linux shell scripting. The Azure portal is referenced, which is cross-platform, but there are no Linux-specific command-line examples or guidance. The documentation assumes familiarity with PowerShell and Windows-centric tools, and does not provide parity for Linux users beyond the Azure CLI.
Recommendations
- Add explicit Bash/Linux shell examples for ARM template deployment, such as using Azure CLI in Bash.
- When listing command-line options, alternate the order or mention Linux-native tools (e.g., Bash, shell scripting) before or alongside PowerShell.
- Clarify that Azure CLI commands work cross-platform and provide sample Bash scripts for automation.
- If PowerShell is mentioned, also mention that PowerShell Core is available on Linux, or provide equivalent Bash commands.
- Consider including a section or note for Linux administrators, highlighting any OS-specific considerations.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/virtual-machines-best-practices.md
...articles/automanage/virtual-machines-best-practices.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools and configurations (such as Windows security baselines in Guest Configuration) without mentioning Linux equivalents. There are no explicit Linux examples or references to Linux-specific best practices, and Windows tools are mentioned exclusively or first in relevant sections.
Recommendations
- Include information about Linux security baselines or compliance policies in the Guest Configuration section, or clarify Linux support.
- Add explicit examples or notes for Linux VMs where applicable, especially for services that support both Windows and Linux.
- Where Windows-specific tools or baselines are mentioned, provide parallel Linux guidance or reference to relevant documentation.
- Review the documentation for other Windows-centric language or assumptions and ensure Linux parity in descriptions and recommendations.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-java-sdk.md
...e-docs/blob/main/articles/automanage/quick-java-sdk.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exhibits Windows bias by linking only to the Windows-specific virtual machine quickstart in the prerequisites and not mentioning or providing equivalent Linux VM documentation or examples. There are no Linux-specific instructions or references, which may lead Linux users to feel unsupported or confused.
Recommendations
- Add a link to the Linux virtual machine quickstart documentation alongside the Windows link in the prerequisites section.
- Clarify that the Java SDK works with both Windows and Linux virtual machines.
- Include an explicit example or note for users managing Linux VMs, or mention any differences if they exist.
- Review other sections for implicit Windows assumptions and ensure Linux parity in all instructions and references.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/move-automanaged-vms.md
.../blob/main/articles/automanage/move-automanaged-vms.md
Medium Priority
View Details →
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation page describes moving Azure Automanage VMs across regions but only references actions performed in the Azure portal (e.g., using the Automanage blade). There are no command-line examples, and no mention of Linux-specific tools or CLI workflows. The instructions implicitly assume a GUI workflow, which is more common for Windows users, and do not provide parity for Linux users who may prefer Azure CLI, Bash, or automation scripts.
Recommendations
- Add Azure CLI and PowerShell command examples for disabling and re-enabling Automanage on VMs.
- Explicitly mention Linux-compatible workflows, such as using Bash scripts or the Azure CLI.
- Provide step-by-step instructions for both GUI (portal) and command-line approaches.
- Ensure that references to tools and workflows do not assume a Windows environment by default.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-go-sdk.md
...ure-docs/blob/main/articles/automanage/quick-go-sdk.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by linking only to the Windows virtual machine quick-create guide in the prerequisites, without mentioning or linking to the equivalent Linux VM documentation. There are no Linux-specific instructions or examples, and the content implicitly assumes a Windows VM context.
Recommendations
- Include links to both Windows and Linux virtual machine quick-create guides in the prerequisites section.
- Clarify that the Automanage SDK and instructions apply to both Windows and Linux VMs, if applicable.
- Add examples or notes for Linux VM scenarios where relevant.
- Ensure parity in documentation references and avoid defaulting to Windows-only resources.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-python-sdk.md
...docs/blob/main/articles/automanage/quick-python-sdk.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by linking exclusively to the Windows VM quick-create documentation in the prerequisites and not mentioning or providing examples for Linux virtual machines. There are no Linux-specific instructions, links, or examples, and the only VM creation link points to a Windows guide.
Recommendations
- Include links to both Windows and Linux VM creation guides in the prerequisites section.
- Clarify that the instructions apply to both Windows and Linux VMs, or specify any differences if present.
- Provide at least one Linux VM example or explicitly state that the process is identical for Linux VMs.
- Review all links and references to ensure Linux parity and inclusivity.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/automanage-upgrade.md
...cs/blob/main/articles/automanage/automanage-upgrade.md
Low Priority
View Details →
Detected Bias Types
missing_linux_example
Summary
The documentation does not explicitly show Windows bias in terms of mentioning Windows tools, PowerShell, or Windows-first patterns. However, it lacks any explicit mention of Linux-specific instructions, tools, or examples. All instructions are generic and portal-based, but there is no confirmation or reassurance that the process is the same for Linux VMs, nor are there any Linux command-line examples or references to Linux-specific considerations.
Recommendations
- Add explicit statements confirming that the upgrade process applies equally to both Windows and Linux VMs, or note any differences.
- Include examples or screenshots that show Linux VMs being upgraded, or clarify that the portal experience is identical for both OS types.
- If there are CLI or automation options (e.g., Azure CLI, Bash scripts), provide Linux-friendly command-line examples alongside any PowerShell or Windows examples.
- Mention any Linux-specific prerequisites, caveats, or troubleshooting steps if they exist.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/how-to-disable-automanage.md
.../main/articles/automanage/how-to-disable-automanage.md
Low Priority
View Details →
Detected Bias Types
missing_linux_example
Summary
The documentation provides instructions only for disabling Azure Automanage via the Azure portal and does not include any command-line examples. There is no mention of PowerShell, Windows tools, or CLI commands, but there is also no coverage of Linux-specific tools or scenarios. The absence of command-line examples (such as Azure CLI or Bash) may disadvantage Linux users who often prefer or require non-GUI methods.
Recommendations
- Add Azure CLI examples for disabling Automanage, which can be used on both Windows and Linux.
- Explicitly mention that the process is platform-agnostic when using the portal, but provide parity by including command-line instructions.
- If PowerShell or Windows-specific tools are ever referenced, ensure equivalent Bash/Linux instructions are also provided.
Unknown
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/overview-about.md
...e-docs/blob/main/articles/automanage/overview-about.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation generally presents Windows and Linux as supported platforms, but there is a subtle Windows-first bias. Windows Server is mentioned before Linux in the prerequisites and in the links to platform-specific documentation. No explicit examples, commands, or tools are shown for either platform, but the ordering and phrasing prioritize Windows.
Recommendations
- List Linux and Windows platforms in parallel or alternate the order to avoid implicit prioritization.
- Provide equal prominence and detail for both Linux and Windows in all sections, including links and references.
- If examples or platform-specific instructions are added in the future, ensure both Linux and Windows are covered with equivalent detail and clarity.
- Consider adding a table or section that summarizes support and differences for both Windows and Linux to reinforce parity.