Automanage

50
Total Pages
35
Linux-Friendly Pages
15
Pages with Bias
30.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

44 issues found
Showing 1-25 of 44 flagged pages
Automanage SMB over QUIC with Azure Automanage machine best practices ...b/main/articles/automanage/automanage-smb-over-quic.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively references Windows Server 2022 Datacenter: Azure Edition as the required VM image for enabling Automanage best practices for SMB over QUIC. All instructions and examples are tailored to Windows environments, with no mention of Linux or macOS support, alternatives, or examples. The only deep link for further learning is to a Windows Server documentation page, reinforcing the Windows-centric approach.
Recommendations
  • Clarify whether SMB over QUIC and Automanage best practices are supported on Linux or macOS VMs. If not, explicitly state this limitation.
  • If Linux support exists or is planned, provide equivalent instructions and examples for Linux VMs, including required images and configuration steps.
  • Include links to relevant Linux documentation or best practices for secure file sharing and certificate management.
  • If only Windows is supported, consider adding a comparison table or FAQ section addressing platform support and alternatives for non-Windows users.
GitHub Create Pull Request
Automanage SMB over QUIC with Azure Automanage machine best practices ...b/main/articles/automanage/automanage-smb-over-quic.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively references Windows Server 2022 Datacenter: Azure Edition as the required VM image for SMB over QUIC and Automanage best practices. All examples and instructions are tailored to Windows environments, with no mention of Linux or macOS support, equivalent tooling, or configuration steps. The only external reference is to Windows Server documentation, reinforcing a Windows-centric approach.
Recommendations
  • Clarify whether SMB over QUIC and Automanage best practices are supported on Linux or macOS VMs. If not, explicitly state this limitation.
  • If Linux support exists or is planned, provide equivalent instructions and examples for Linux VM images, including relevant configuration steps and tooling.
  • Reference Linux documentation or tools where appropriate, such as Samba or other SMB implementations.
  • Consider including a comparison table showing feature parity (or lack thereof) between Windows and Linux VM images for SMB over QUIC and Automanage.
GitHub Create Pull Request
Automanage Tutorial - python ...ticles/automanage/tutorial-create-assignment-python.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates a Windows bias by exclusively providing examples for creating Windows virtual machines, omitting Linux VM creation steps. Both Azure CLI and PowerShell instructions are included, but PowerShell is a Windows-centric tool. There are no Linux-specific commands, nor is there mention of creating or managing Linux VMs, which are common in Azure environments.
Recommendations
  • Add examples for creating Linux virtual machines using both Azure CLI and PowerShell, e.g., using --image UbuntuLTS.
  • Explicitly mention Linux support and provide guidance for Linux VM scenarios.
  • Include Linux shell (bash) command examples where relevant, not just PowerShell.
  • Balance the documentation by presenting Windows and Linux options side-by-side in all relevant sections.
GitHub Create Pull Request
Automanage Azure Automanage for Azure Arc-enabled servers ...e-docs/blob/main/articles/automanage/automanage-arc.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation lists Windows Server versions first in the supported operating systems section and includes a Windows-only service (Microsoft Antimalware) in the participating services table. There are no Linux-specific examples, tools, or configuration patterns mentioned, and the guidance does not provide parity for Linux anti-malware or security tooling. The 'ms.collection' metadata references Linux, but the content and examples are Windows-centric.
Recommendations
  • List Linux operating systems before or alongside Windows in supported OS sections to avoid Windows-first bias.
  • Include Linux-specific security and anti-malware solutions in the participating services table, or clarify their absence and recommend alternatives.
  • Provide examples or guidance for configuring Automanage on Linux systems, including command-line or automation patterns relevant to Linux (e.g., Bash, systemd, package managers).
  • Highlight any differences in service behavior or limitations for Linux systems, ensuring users are aware of platform-specific considerations.
  • Add links to Linux-focused documentation or best practices for Azure Automanage and related services.
GitHub Create Pull Request
Automanage SMB over QUIC with Azure Automanage machine best practices ...b/main/articles/automanage/automanage-smb-over-quic.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively references Windows Server 2022 Datacenter: Azure Edition as the required VM image for SMB over QUIC and Automanage best practices, with no mention of Linux support, equivalents, or examples. All configuration steps and links point to Windows-specific resources, and there are no instructions or guidance for Linux-based VMs or cross-platform scenarios.
Recommendations
  • Explicitly state whether SMB over QUIC and Automanage best practices are supported or not on Linux VMs.
  • If Linux support exists, provide equivalent examples and instructions for deploying and managing SMB over QUIC on Linux-based Azure VMs.
  • Include references to Linux tools, commands, or configuration patterns where applicable.
  • If support is Windows-only, clarify this limitation early in the documentation to set user expectations.
  • Consider adding a comparison table outlining feature parity and differences between Windows and Linux VM support for SMB over QUIC and Automanage.
GitHub Create Pull Request
Automanage Move an Azure Automanage configuration profile across regions ...s/automanage/move-automanaged-configuration-profile.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses PowerShell and Windows-centric tooling (Invoke-RestMethod, PowerShell syntax) for all examples and instructions. No Linux or cross-platform alternatives (such as Bash, curl, or Azure CLI) are provided, making the guidance inaccessible or less clear for Linux users. The use of Windows tools is implicit and not balanced by Linux equivalents.
Recommendations
  • Provide equivalent examples using Bash and curl for REST API calls.
  • Include Azure CLI commands for each step, as Azure CLI is cross-platform.
  • Explicitly mention that the steps can be performed on Linux/macOS and provide sample scripts.
  • Add a note or section on platform compatibility, clarifying that REST API calls can be made from any OS.
  • Ensure that Linux examples appear alongside or before Windows/PowerShell examples to avoid implicit prioritization.
GitHub Create Pull Request
Automanage Repair a broken Azure Automanage Account .../main/articles/automanage/repair-automanage-account.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by mentioning PowerShell as a primary method for ARM deployments before Linux alternatives, listing PowerShell modules alongside Azure CLI, and referencing Windows-centric tooling patterns. There are no explicit Linux-specific examples, and PowerShell is presented as a default option, which may disadvantage Linux users.
Recommendations
  • Provide explicit Bash and Linux shell examples for ARM deployments, not just Azure CLI.
  • List Azure CLI commands before PowerShell commands to avoid implying Windows-first workflows.
  • Clarify that Azure CLI is cross-platform and highlight its use on Linux and macOS.
  • Avoid referencing PowerShell modules as a primary method unless parity is shown for Bash/shell users.
  • Include notes or sections for Linux users, such as installation and usage tips for Azure CLI on Linux.
GitHub Create Pull Request
Automanage 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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation lists Windows Server versions first in the supported operating systems section and includes a Windows-only service (Microsoft Antimalware) in the participating services table. There are no Linux-specific examples, tools, or configuration patterns provided, and the guidance does not mention Linux alternatives for antimalware or other OS-specific management tasks.
Recommendations
  • List Linux distributions before or alongside Windows Server versions in the supported operating systems section to avoid 'windows_first' bias.
  • For services like antimalware, mention Linux equivalents (e.g., integration with third-party Linux antivirus solutions) or clarify that the feature is Windows-only and suggest alternatives for Linux users.
  • Provide Linux-specific examples, configuration patterns, or troubleshooting steps where relevant, especially for services that behave differently on Linux.
  • Include links to Linux best practices or documentation for configuring and managing supported Linux distributions with Automanage.
  • Highlight any limitations or differences in feature support between Windows and Linux, so users are aware of OS-specific considerations.
GitHub Create Pull Request
Automanage 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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively references Windows Server 2022 Datacenter: Azure Edition as the required VM image for SMB over QUIC and Automanage capabilities. All examples and instructions are tailored to Windows environments, with no mention of Linux support, equivalents, or alternative tooling. The only deep link for further learning is to Windows Server documentation, reinforcing the Windows-centric approach.
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 deploying and managing SMB over QUIC on Linux VMs.
  • Include references to Linux documentation or tooling where applicable, such as Samba or other SMB implementations.
  • Present platform options side-by-side, rather than Windows-only, to ensure parity and reduce bias.
  • If only Windows is supported, add a section explaining why and what alternatives Linux users can consider.
GitHub Create Pull Request
Automanage 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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively uses PowerShell and Windows-centric tooling (Invoke-RestMethod, PowerShell syntax) for all examples and instructions. There are no Linux or cross-platform CLI (e.g., Bash, curl, Azure CLI) equivalents provided, which may disadvantage users on Linux or macOS systems. The page assumes familiarity with PowerShell and does not mention alternative approaches for non-Windows environments.
Recommendations
  • Add equivalent examples using Bash and curl for REST API calls.
  • Provide Azure CLI commands for profile management, which are cross-platform.
  • Explicitly mention that the process can be performed from Linux/macOS and provide sample commands.
  • Consider a 'Platform parity' section highlighting differences and options for Windows, Linux, and macOS users.
  • Avoid assuming PowerShell as the default or only method; present alternatives side-by-side.
GitHub Create Pull Request
Automanage 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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates Windows bias by exclusively providing examples for creating a Windows virtual machine, omitting Linux VM creation steps. Both Azure CLI and PowerShell instructions are given, but PowerShell (a Windows-centric tool) is presented as an equal alternative, and no Linux-specific shell or command examples are provided. The tutorial does not mention or show how to use Linux images or create Linux VMs, nor does it address Linux-specific considerations for Automanage.
Recommendations
  • Add examples for creating a Linux virtual machine using both Azure CLI and PowerShell, including specifying a Linux image (e.g., Ubuntu, CentOS).
  • Explicitly mention Linux support in the prerequisites and steps, clarifying that Automanage can be used with both Windows and Linux VMs.
  • Include screenshots or portal instructions that show Automanage applied to Linux VMs.
  • If there are differences in Automanage profile assignment or prerequisites for Linux VMs, document those clearly.
  • Consider adding bash or shell script equivalents for steps where PowerShell is used, to improve accessibility for Linux users.
GitHub Create Pull Request
Automanage 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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by mentioning PowerShell as a primary method for ARM deployments before Linux alternatives, providing explicit PowerShell module references, and omitting Linux-specific shell examples (e.g., Bash). Windows tools and patterns (PowerShell, Azure portal screenshots) are referenced directly, while Linux equivalents are not discussed or shown.
Recommendations
  • Add explicit Bash shell examples for ARM template deployment alongside PowerShell, using Azure CLI commands suitable for Linux/macOS.
  • When listing command-line options, present Azure CLI (cross-platform) before PowerShell, or at least in parallel, to avoid Windows-first ordering.
  • Include screenshots or instructions for Azure portal usage on non-Windows platforms (if relevant), or clarify that the portal is platform-agnostic.
  • Reference Linux/macOS environments in prerequisites or notes, and provide troubleshooting tips for those platforms.
  • Avoid referring to PowerShell modules as the default or primary method; instead, present both PowerShell and Bash/Azure CLI as equal options.
GitHub Create Pull Request
Automanage Tutorial - python ...ticles/automanage/tutorial-create-assignment-python.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows by exclusively providing examples for creating Windows virtual machines, omitting Linux VM creation steps. Additionally, the Azure CLI and PowerShell installation links default to Windows instructions, and PowerShell examples are shown alongside CLI, which may not be as relevant for Linux/macOS users.
Recommendations
  • Include examples for creating Linux virtual machines (e.g., using --image UbuntuLTS in az vm create).
  • Provide installation instructions for Azure CLI and PowerShell for Linux/macOS platforms, or link to cross-platform guides.
  • Explicitly mention that Azure CLI works cross-platform and highlight its usage for Linux/macOS users.
  • When presenting code tabs, consider showing Azure CLI first, as it is more universally available than PowerShell.
GitHub Create Pull Request
Automanage Move an Azure Automanage configuration profile across regions ...s/automanage/move-automanaged-configuration-profile.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses PowerShell and Windows-centric command examples (Invoke-RestMethod, PowerShell syntax) for all steps, without mentioning or providing equivalent Linux/macOS shell commands (such as curl or Azure CLI). This creates friction for users on non-Windows platforms, who must translate the instructions themselves.
Recommendations
  • Add equivalent examples using Bash and curl for Linux/macOS users.
  • Include Azure CLI commands where possible, as it is cross-platform.
  • Explicitly state that the REST API can be accessed from any OS and provide generic HTTP request examples.
  • Present Linux/macOS examples alongside or before Windows/PowerShell examples to improve parity.
GitHub Create Pull Request
Automanage Azure Quickstart SDK for Java ...e-docs/blob/main/articles/automanage/quick-java-sdk.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing only Windows virtual machines in the prerequisites and linking exclusively to the Windows VM creation guide. There are no examples or instructions for Linux virtual machines, nor is there mention of Linux-specific considerations or links to Linux VM documentation.
Recommendations
  • Include links to both Windows and Linux VM creation guides in the prerequisites.
  • Clarify that Automanage can be used with both Windows and Linux VMs, if applicable.
  • Add examples or notes for Linux VM scenarios where relevant.
  • Ensure terminology and instructions are platform-neutral unless a feature is Windows-specific.
GitHub Create Pull Request
Automanage Azure Quickstart SDK for Python ...docs/blob/main/articles/automanage/quick-python-sdk.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by linking only to the Windows VM creation guide in the prerequisites and omitting references or examples for Linux VMs. There are no Linux-specific instructions, nor is there guidance for users managing Linux virtual machines, which are common in Azure environments.
Recommendations
  • Include links to both Windows and Linux VM creation guides in the prerequisites.
  • Clarify that the Python SDK works for both Windows and Linux VMs, if applicable.
  • Add examples or notes for Linux VM users, such as differences in configuration profile applicability or any platform-specific considerations.
  • Ensure terminology and instructions are platform-neutral unless a step is truly Windows-specific.
GitHub Create Pull Request
Automanage Azure Automanage Machine Best Practices ...articles/automanage/virtual-machines-best-practices.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page for Azure Automanage Machine Best Practices displays a Windows bias primarily through its references to Windows-specific features (e.g., Windows security baselines) and the lack of explicit mention or examples for Linux VM configurations. The 'Guest configuration' section only references Windows security baselines, with no mention of Linux equivalents or how Linux VMs are handled. There are no examples or guidance specific to Linux, and Windows terminology appears first or exclusively in several sections.
Recommendations
  • Add explicit information about how Automanage handles Linux VMs, including supported features and any differences from Windows VMs.
  • Include references to Linux security baselines or compliance standards in the 'Guest configuration' section.
  • Provide examples or links to documentation for configuring and managing Linux VMs with Automanage.
  • Clarify which services and features are available for Linux VMs, and note any limitations or differences compared to Windows VMs.
GitHub Create Pull Request
Automanage Azure Quickstart SDK for JavaScript .../blob/main/articles/automanage/quick-javascript-sdk.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing only Windows virtual machines in the prerequisites and linking exclusively to the Windows VM quick-create guide. There are no mentions or examples for Linux virtual machines, nor links to Linux VM documentation. This could mislead users into thinking the SDK or Automanage is Windows-only, or create friction for Linux users seeking parity.
Recommendations
  • Include links to both Windows and Linux VM quick-create documentation in the prerequisites.
  • Clarify that Automanage and the JavaScript SDK support both Windows and Linux VMs, if applicable.
  • Add example resource IDs or configuration profile assignments for Linux VMs, if there are differences.
  • Explicitly mention any platform-specific considerations for Linux users.
GitHub Create Pull Request
Automanage Create a custom profile in Azure Automanage for VMs ...articles/automanage/virtual-machines-custom-profile.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific features (such as Windows Admin Center and audit modes for Windows machines only), mentioning Windows capabilities before Linux equivalents, and omitting explicit Linux/macOS examples or guidance. There are no Linux-specific configuration options, nor is there clarification on how Automanage custom profiles behave for Linux VMs.
Recommendations
  • Add explicit notes or sections describing how custom profiles apply to Linux VMs, including any limitations or differences.
  • Provide examples or configuration options relevant to Linux VMs (e.g., Linux-specific security baselines, antimalware settings, or supported services).
  • Clarify which features are Windows-only and which are cross-platform in both the ARM template and portal instructions.
  • Include Linux/macOS command-line deployment examples (e.g., bash/CLI) alongside or before Windows-specific tools.
  • Ensure parity in documentation structure, so Linux users can easily identify supported features and steps.
GitHub Create Pull Request
Automanage Tutorial - python ...ticles/automanage/tutorial-create-assignment-python.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows by exclusively providing examples for creating Windows virtual machines and omitting Linux VM creation steps. The Azure CLI and PowerShell instructions use Windows-centric syntax (backticks for line continuation), and there are no Linux or macOS-specific instructions or examples for VM creation or command usage.
Recommendations
  • Include examples for creating Linux virtual machines (e.g., using --image UbuntuLTS in az vm create).
  • Provide command syntax examples compatible with Linux/macOS shells (e.g., using \ for line continuation in bash).
  • Explicitly mention cross-platform compatibility of Azure CLI and provide links to Linux/macOS installation guides.
  • Add notes or tabs for Linux/macOS users where command syntax or tooling differs.
GitHub Create Pull Request
Automanage Azure Quickstart SDK for Python ...docs/blob/main/articles/automanage/quick-python-sdk.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by linking only to the Windows VM creation guide in prerequisites and omitting any mention or example for Linux virtual machines. There are no Linux-specific instructions or references, which may cause confusion or extra effort for Linux users.
Recommendations
  • Add a link to the Linux VM creation guide alongside the Windows guide in the prerequisites section.
  • Clarify that the Python SDK works with both Windows and Linux VMs, if applicable.
  • Include examples or notes for Linux VM scenarios where relevant.
  • Ensure terminology and instructions are platform-neutral unless a step is truly Windows-specific.
GitHub Create Pull Request
Automanage Move an Azure Automanage configuration profile across regions ...s/automanage/move-automanaged-configuration-profile.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses PowerShell and Windows-centric tooling (Invoke-RestMethod, PowerShell syntax) for all examples and instructions. No Linux/macOS shell (bash, curl, etc.) equivalents are provided, nor is there mention of cross-platform alternatives. This creates friction for users on Linux or macOS, who must translate the steps themselves.
Recommendations
  • Provide equivalent bash/curl examples for all REST API interactions.
  • Explicitly mention that the API calls can be made from any platform and provide guidance for Linux/macOS users.
  • Add a section or note highlighting cross-platform approaches and tools (e.g., Azure CLI, curl, httpie).
  • Avoid assuming PowerShell as the default shell; present examples for both Windows and Linux/macOS users.
GitHub Create Pull Request
Automanage Azure Quickstart SDK for JavaScript .../blob/main/articles/automanage/quick-javascript-sdk.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by linking only to the Windows VM quick-create guide in the prerequisites and not mentioning or linking to the equivalent Linux VM documentation. No Linux-specific examples, instructions, or references are provided, which may cause confusion or extra effort for Linux users.
Recommendations
  • Add a link to the Linux VM quick-create documentation alongside the Windows link in the prerequisites.
  • Clarify that the JavaScript SDK works for both Windows and Linux virtual machines, if applicable.
  • Include examples or notes relevant to Linux VM users, such as any differences in configuration or supported features.
  • Ensure parity in documentation references and examples for both Windows and Linux environments.
GitHub Create Pull Request
Automanage Azure Automanage Machine Best Practices ...articles/automanage/virtual-machines-best-practices.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Azure Automanage Machine Best Practices demonstrates a Windows bias by referencing Windows-specific features (such as Windows security baselines) without mentioning Linux equivalents, omitting explicit Linux-focused examples or guidance, and generally framing best practices around Windows tooling and concepts. There is no discussion of Linux security baselines, configuration, or differences in supported features for Linux VMs.
Recommendations
  • Add explicit sections or notes describing how Automanage applies to Linux VMs, including supported features and any limitations.
  • Include references to Linux security baselines or compliance frameworks (such as CIS or OS-specific hardening guides) in the Guest configuration section.
  • Provide examples or links for configuring and monitoring Linux VMs, ensuring parity with Windows-focused documentation.
  • Clarify which services and features are available or behave differently for Linux VMs, especially in areas like antimalware, guest configuration, and update management.
GitHub Create Pull Request
Automanage Create a custom profile in Azure Automanage for VMs ...articles/automanage/virtual-machines-custom-profile.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page displays a moderate Windows bias. Windows-specific features (such as audit modes for Azure security baselines in Guest Configuration) are explicitly called out as 'Windows machines only', and Windows tools like Windows Admin Center are included in the configuration profile. There are no Linux/macOS-specific examples, nor is there guidance for Linux users regarding equivalent configuration or limitations. The order and focus of features suggest Windows is the primary platform considered.
Recommendations
  • Add explicit notes or sections describing Linux/macOS support and limitations for custom profiles in Azure Automanage.
  • Provide examples or configuration options relevant to Linux VMs (e.g., mention supported services, clarify which features are Windows-only, and offer Linux equivalents where possible).
  • Where features are Windows-only, suggest alternative approaches for Linux users or link to relevant documentation.
  • Include Linux-specific configuration samples in ARM templates or portal walkthroughs, or clarify which settings are ignored/applied differently on Linux.
  • Avoid listing Windows tools (e.g., Windows Admin Center) without mentioning Linux alternatives or stating their platform specificity.
GitHub Create Pull Request
← Previous Page 1 of 2 Next →