Automanage

25
Total Pages
9
Linux-Friendly Pages
16
Pages with Bias
64.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

102 issues found
Showing 1-25 of 102 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-14 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 with Automanage best practices. All instructions and examples are Windows-centric, with no mention of Linux or macOS support, alternatives, or equivalent tooling. The only external link for further information points to Windows Server documentation. There is no guidance for non-Windows environments.
Recommendations
  • Clarify whether SMB over QUIC and Automanage best practices are supported on Linux or macOS VMs. If not supported, explicitly state this limitation.
  • If partial support exists, provide Linux/macOS-specific instructions or note differences in feature availability.
  • Include links to relevant Linux documentation or alternative approaches for secure SMB connectivity on non-Windows platforms.
  • Present any cross-platform considerations or roadmap for future support if applicable.
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-13 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 with Automanage best practices. All instructions and linked resources are Windows-centric, with no mention of Linux or macOS support, equivalents, or alternative steps. The only example and screenshots are for Windows VMs, and the core feature (SMB over QUIC) is described solely in the context of Windows Server.
Recommendations
  • Explicitly state whether SMB over QUIC and Automanage best practices are supported or unsupported on Linux/macOS VMs.
  • If Linux support exists, provide parallel instructions and examples for enabling Automanage best practices on Linux VMs.
  • If Linux is unsupported, add a clear note at the top of the page to inform users.
  • Reference or link to any Linux/macOS equivalents or alternative secure file sharing solutions if relevant.
  • Consider including a comparison table of supported OS images for Automanage and SMB over QUIC.
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-12 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 operating systems first in the supported OS section and highlights Windows-specific tools such as Microsoft Antimalware, which is only available for Windows Server. There are no Linux-specific examples or tools mentioned, and no guidance is provided for Linux anti-malware or security solutions. The configuration and onboarding instructions are generic and do not include Linux-specific steps or considerations.
Recommendations
  • List supported operating systems in alphabetical order or alternate the order to avoid implicit prioritization of Windows.
  • Include Linux-specific security and anti-malware recommendations or mention third-party solutions commonly used on Linux.
  • Provide examples or guidance for enabling Automanage on Linux systems, including any differences in configuration or troubleshooting steps.
  • Ensure that service descriptions clarify platform-specific limitations and offer alternatives for Linux where Windows-only features exist.
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-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 describes enabling SMB over QUIC with Azure Automanage for Windows Server 2022 Datacenter: Azure Edition VMs. All examples, prerequisites, and instructions are Windows-centric, with no mention of Linux support, Linux-compatible tools, or cross-platform considerations. References and links point only to Windows Server documentation.
Recommendations
  • Explicitly state whether SMB over QUIC and Automanage best practices are supported on Linux VMs. If not supported, clarify this early in the documentation.
  • If Linux support exists or is planned, provide equivalent instructions and examples for Linux VMs, including any required packages, configuration steps, and portal settings.
  • Include references to Linux documentation or tools where applicable, and ensure parity in guidance for certificate management and compliance monitoring.
  • If feature is Windows-only, consider a section explaining why, and suggest alternative secure file sharing solutions for Linux environments.
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-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 tooling (Invoke-RestMethod, PowerShell syntax) for all examples and instructions. There are no equivalent examples for Linux users (e.g., using Bash, curl, or Azure CLI), nor is there mention of cross-platform alternatives. This creates a bias toward Windows users and may hinder Linux administrators from following the guide easily.
Recommendations
  • Add equivalent Linux/Bash examples using curl or Azure CLI for all PowerShell instructions.
  • Explicitly mention that the API calls can be performed from any platform, not just Windows.
  • Provide guidance for Linux and macOS users, including environment setup and authentication steps.
  • Consider reordering examples to present cross-platform (e.g., REST API, Azure CLI) instructions before platform-specific ones like PowerShell.
GitHub Create Pull Request
Automanage Tutorial - python ...ticles/automanage/tutorial-create-assignment-python.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively providing examples for creating Windows virtual machines and referencing Windows-centric tools (PowerShell). There are no Linux VM creation examples, nor any mention of Linux-specific patterns or considerations. The Azure CLI installation link defaults to Windows instructions, and PowerShell is presented as an equal alternative to Azure CLI, which is more cross-platform. No Linux shell or VM examples are given.
Recommendations
  • Add examples for creating Linux virtual machines using both Azure CLI and PowerShell (e.g., using --image UbuntuLTS).
  • Include Linux shell (bash) instructions and clarify cross-platform usage for Azure CLI.
  • Provide parity in documentation for Linux environments, such as mentioning SSH key authentication and Linux-specific VM configuration.
  • Update installation instructions for Azure CLI to reference cross-platform guides, not just Windows.
  • Balance the use of PowerShell and CLI by clarifying platform compatibility and suggesting CLI for Linux/macOS users.
GitHub Create Pull Request
Automanage Create a custom profile in Azure Automanage for VMs ...articles/automanage/virtual-machines-custom-profile.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation displays a Windows bias by referencing Windows-specific features (such as Windows Admin Center and audit modes for Windows machines only) without mentioning Linux equivalents or providing Linux-specific guidance. There are no examples or instructions tailored for Linux VMs, and Windows tools are referenced exclusively. The documentation assumes a Windows-centric use case, omitting Linux-specific configuration or parity.
Recommendations
  • Add explicit guidance and examples for Linux VMs, including any differences in supported services and settings.
  • Clarify which features are Windows-only and provide Linux alternatives or note limitations for Linux users.
  • Include Linux-specific tools or configuration instructions where relevant (e.g., mention Linux security baselines, antimalware options, or monitoring agents).
  • Ensure that examples and feature lists are presented in a cross-platform manner, not prioritizing Windows features or tools.
  • Add a section or table comparing feature support between Windows and Linux VMs in Azure Automanage.
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-12 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 alongside Azure CLI, listing PowerShell before Linux-friendly alternatives, and referencing Windows-centric tooling (PowerShell modules) without providing equivalent Linux shell examples. While Azure CLI is cross-platform, the explicit inclusion and prioritization of PowerShell and lack of Linux shell (bash) or scripting examples indicate a preference for Windows workflows.
Recommendations
  • Add explicit bash shell examples for ARM deployments, showing how to use Azure CLI in a Linux environment.
  • When listing command-line options, alternate or randomize the order of PowerShell and CLI, or group them as 'cross-platform' and 'Windows-specific'.
  • Include notes clarifying that Azure CLI commands work on Linux, macOS, and Windows, and provide sample bash scripts for common tasks.
  • If PowerShell is mentioned, also mention bash or other Linux-native shells for parity.
  • Avoid referencing Windows-specific modules (e.g., New-AzDeployment) without Linux equivalents or alternatives.
GitHub Create Pull Request
Automanage Tutorial - python ...ticles/automanage/tutorial-create-assignment-python.md
High Priority View Details →
Scanned: 2026-01-11 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. Both Azure CLI and Azure PowerShell are presented, but PowerShell is a Windows-centric tool. There are no Linux-specific instructions, nor are Linux images or shell patterns mentioned.
Recommendations
  • Include examples for creating Linux virtual machines using both Azure CLI and PowerShell, specifying popular Linux images (e.g., Ubuntu, CentOS).
  • Add instructions or notes for Linux users, such as using Bash shell syntax for Azure CLI commands.
  • Present CLI examples before PowerShell, or provide parity in both, to avoid implying Windows-first workflows.
  • Clarify that Azure CLI is cross-platform and provide installation links for Linux and macOS, not just Windows.
  • Add screenshots or portal navigation steps for Linux VMs where relevant.
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-11 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 provided, and the only security tool mentioned is exclusive to Windows. The documentation lacks parity in describing or recommending Linux alternatives for antimalware or other OS-specific management tools.
Recommendations
  • List supported Linux operating systems before or alongside Windows versions to avoid implicit prioritization.
  • Include Linux-specific security and management tools (e.g., ClamAV, auditd, or other supported antimalware solutions) in the participating services table, or clarify if/why they are not supported.
  • Provide examples or guidance for both Windows and Linux environments, especially for configuration, onboarding, and troubleshooting steps.
  • Explicitly state any differences in service behavior or limitations for Linux systems, and offer links to relevant Linux documentation.
  • Ensure that recommendations and next steps are inclusive of both Windows and Linux users, possibly by offering CLI or script examples for Linux (e.g., Bash, shell commands) in addition to portal instructions.
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 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 for SMB over QUIC and Automanage best practices, with no mention of Linux support, examples, or equivalents. All steps, images, and links are Windows-centric, and the only referenced documentation is for Windows Server. There are no Linux instructions, prerequisites, or clarifications about cross-platform compatibility.
Recommendations
  • Explicitly state whether SMB over QUIC and Automanage best practices are supported on Linux VMs. If not supported, clarify this early in the documentation.
  • If Linux support exists or is planned, add equivalent instructions and examples for enabling and managing SMB over QUIC with Automanage on Linux VMs.
  • Include links to Linux SMB/QUIC documentation and tools where relevant.
  • Provide a comparison table or section outlining feature parity and differences between Windows and Linux environments for SMB over QUIC and Automanage.
  • Ensure that any referenced tools, commands, or portal options are described for both Windows and Linux users where applicable.
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-11 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 scripting) for all examples and instructions. There are no Linux or cross-platform CLI (e.g., Azure CLI, curl) equivalents provided, nor any mention of how to perform these steps on Linux or macOS systems. This creates a strong Windows bias and may hinder Linux users from following the guide.
Recommendations
  • Add equivalent examples using Azure CLI (az rest) and/or curl for REST API calls, which are cross-platform.
  • Explicitly mention that the steps can be performed on Linux/macOS and provide sample commands for those environments.
  • Reorganize examples so that cross-platform tools (Azure CLI, curl) are presented before or alongside PowerShell examples.
  • Include notes or links to platform-specific prerequisites (e.g., installing Azure CLI on Linux).
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by mentioning PowerShell as a deployment option before Linux alternatives, providing explicit PowerShell module references, and omitting Linux-specific command examples (such as Bash or shell scripting). While Azure CLI is referenced (which is cross-platform), PowerShell is given equal or greater prominence, and there are no examples tailored to Linux users (e.g., Bash scripts, package installation instructions, or Linux-specific troubleshooting).
Recommendations
  • Provide explicit Bash or shell script examples alongside PowerShell commands for deployment steps.
  • Clarify that Azure CLI commands work on both Windows and Linux, and offer installation instructions for Linux users.
  • When listing deployment options, alternate the order or explicitly state cross-platform compatibility before mentioning Windows-specific tools.
  • Include troubleshooting or usage notes relevant to Linux environments, such as file permissions or shell differences.
  • Add links to Linux-specific documentation or guides where appropriate.
GitHub Create Pull Request
Automanage Azure Automanage Machine Best Practices ...articles/automanage/virtual-machines-best-practices.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and concepts (such as Microsoft Antimalware and Windows security baselines) without mentioning Linux equivalents or clarifying Linux support. The 'Guest configuration' section specifically states that Windows security baselines are installed, with no mention of Linux baseline options. There are no explicit examples or guidance for Linux VMs, and the documentation implicitly assumes a Windows environment in several service descriptions.
Recommendations
  • Explicitly mention Linux support for each participating service, including any differences in configuration or capabilities.
  • For sections referencing Windows-specific tools (e.g., Microsoft Antimalware, Windows security baselines), add parallel information about Linux equivalents (such as supported Linux antimalware solutions or CIS baselines for Linux).
  • Where configuration or onboarding steps differ between Windows and Linux VMs, provide clear, side-by-side instructions or tables.
  • Include examples or links to documentation that demonstrate Automanage best practices for Linux VMs.
  • Review and update service descriptions to clarify cross-platform applicability and avoid implying Windows exclusivity unless accurate.
GitHub Create Pull Request
Automanage Create a custom profile in Azure Automanage for VMs ...articles/automanage/virtual-machines-custom-profile.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page displays a Windows bias by referencing Windows-specific features (such as Windows Admin Center and Microsoft Antimalware) and explicitly stating that certain configuration options (audit modes for Azure security baselines in Guest Configuration) are available only for Windows machines. There are no Linux-specific examples, tools, or equivalent configuration options mentioned, and the documentation does not clarify Linux support or provide parity in examples.
Recommendations
  • Add explicit information about Linux VM support in Azure Automanage, including which services and settings are available for Linux.
  • Provide Linux-specific examples or clarify which configuration options apply to Linux VMs (e.g., security baseline, antimalware, backup).
  • Mention Linux equivalents for Windows-only tools and features, or state if no equivalent exists.
  • Ensure that documentation sections do not assume Windows as the default platform; present information for both Windows and Linux VMs in parallel where applicable.
  • Include sample ARM template snippets or portal screenshots for Linux VM scenarios, if supported.
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 OS for SMB over QUIC with Automanage best practices. All instructions, examples, and links are Windows-centric, with no mention of Linux support, equivalents, or alternative workflows. The only referenced tools and features are specific to Windows environments.
Recommendations
  • Explicitly state whether SMB over QUIC with Automanage is supported or unsupported on Linux VMs. If unsupported, clarify this early in the documentation.
  • If Linux support exists or is planned, provide parallel instructions for enabling and managing SMB over QUIC with Automanage on Linux VMs.
  • Include references or links to relevant Linux documentation, tools, or best practices for SMB over QUIC and certificate management.
  • If Windows-only features are being described, add a note to clarify the scope and suggest alternatives for Linux users where possible.
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 equivalent anti-malware recommendations. The page lacks parity in guidance for Linux users, especially regarding security tooling and operational best practices.
Recommendations
  • List Linux operating systems before or alongside Windows in the supported OS section to avoid Windows-first ordering.
  • Include Linux-specific security tooling (e.g., recommendations for anti-malware or endpoint protection for Linux) in the participating services table.
  • Provide examples or guidance for Linux users, such as integration with Linux-native tools or configuration steps relevant to Linux environments.
  • Clarify which services and features are available or recommended for Linux, especially where Windows-only services are mentioned.
  • Add links to Linux-focused documentation or best practices where relevant.
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 scripting) for all examples and instructions. There are no equivalent examples for Linux users (e.g., using Bash, curl, or Azure CLI), nor is there any mention of how to perform these steps on Linux or macOS platforms. This creates a strong Windows bias and may exclude or confuse users working on non-Windows systems.
Recommendations
  • Add equivalent Linux/macOS examples using Bash and curl, or Azure CLI commands for all steps shown in PowerShell.
  • Explicitly mention cross-platform options and clarify that the process can be performed on any OS with appropriate tools.
  • Reorder or parallelize examples so that Linux/Bash and Windows/PowerShell instructions are presented together, or at least ensure Linux examples are not omitted.
  • Reference Azure CLI documentation and provide sample commands for resource manipulation via CLI, which is cross-platform.
  • Include a note about tool availability on different operating systems and recommend installation steps for required tools.
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 page demonstrates a Windows bias by exclusively providing examples for creating Windows virtual machines, omitting Linux VM creation steps. The Azure PowerShell tool is presented alongside Azure CLI, but all CLI and PowerShell examples focus on Windows images and configurations. There are no Linux-specific instructions, images, or parity in example commands.
Recommendations
  • Include examples for creating Linux virtual machines using both Azure CLI and Azure PowerShell (e.g., using --image UbuntuLTS).
  • Add a section or tab for Linux VM creation, showing relevant image names and any Linux-specific configuration steps.
  • Ensure that instructions and screenshots reflect both Windows and Linux VM scenarios where applicable.
  • Mention Linux compatibility and best practices in the context of Automanage profiles, clarifying any differences.
  • Balance the use of Azure PowerShell and CLI by highlighting cross-platform usage and noting that CLI works natively on Linux.
GitHub Create Pull Request
Automanage Create a custom profile in Azure Automanage for VMs ...articles/automanage/virtual-machines-custom-profile.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 page demonstrates a Windows bias by referencing Windows-specific features (e.g., Windows Admin Center, Microsoft Antimalware, audit modes for Windows machines) without providing equivalent Linux examples or explicitly mentioning Linux support. Windows tools and configuration options are highlighted, while Linux-specific options, patterns, or differences are omitted.
Recommendations
  • Add explicit examples and guidance for Linux VMs, including supported services and configuration differences.
  • Clarify which features are Windows-only and which are cross-platform, ideally with a comparison table.
  • Include Linux equivalents for tools and settings (e.g., mention Linux antimalware options, Linux security baselines, or monitoring agents).
  • Provide ARM template snippets or portal walkthroughs tailored for Linux VM scenarios.
  • Ensure documentation language is inclusive of both Windows and Linux, avoiding Windows-first phrasing.
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 Windows bias by mentioning PowerShell as a primary method for ARM template deployment before Linux alternatives, referencing PowerShell modules, and listing PowerShell alongside Azure CLI as the main automation tools. There are no explicit Linux shell (bash) examples, and PowerShell is presented as a default automation pattern, which may disadvantage Linux users.
Recommendations
  • Add explicit bash shell examples for ARM template deployment using Azure CLI.
  • List Azure CLI and bash examples before PowerShell to avoid 'windows_first' ordering.
  • Clarify that PowerShell examples are for Windows users and provide equivalent Linux instructions.
  • Reference cross-platform tools (e.g., Azure CLI in bash) wherever PowerShell is mentioned.
  • Ensure screenshots and UI references are not Windows-specific unless necessary.
GitHub Create Pull Request
Automanage Azure Automanage Machine Best Practices ...articles/automanage/virtual-machines-best-practices.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 demonstrates a Windows bias by referencing Windows-specific tools and features (such as Microsoft Antimalware and Windows security baselines) without mentioning Linux equivalents or clarifying Linux support. There are no explicit Linux examples or references to Linux-specific best practices, and the only security baseline mentioned is for Windows. This may give the impression that Automanage is primarily or exclusively for Windows VMs.
Recommendations
  • Include explicit references to Linux support for each participating service, clarifying which features are available for Linux VMs.
  • Mention and link to Linux security baselines or compliance options if available, or state if they are not currently supported.
  • For services like Microsoft Antimalware and Guest Configuration, specify Linux alternatives (e.g., integration with common Linux antimalware solutions or CIS baselines).
  • Provide Linux-specific examples or documentation links where appropriate to ensure parity.
  • Add a table column or section indicating OS compatibility (Windows/Linux) for each service.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows Server, specifically the Windows Server 2022 Datacenter: Azure Edition image, and does not mention Linux support or provide any Linux-specific instructions or examples. All steps, prerequisites, and references are tailored to Windows environments, and the only external documentation linked is for Windows Server. There is no discussion of SMB over QUIC on Linux, nor any mention of Linux-compatible tooling or configuration.
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 relevant images, configuration steps, and screenshots.
  • Include links to Linux documentation for SMB over QUIC, if available, or note the absence of such support.
  • Discuss any differences in certificate management or policy enforcement for Linux environments.
  • Ensure that future updates to the documentation address cross-platform parity and highlight any platform-specific requirements.
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: 2026-01-09 00:34
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) without mentioning Linux equivalents or alternatives. There are no Linux-specific examples, tools, or guidance provided, and the configuration and onboarding instructions reference only the Azure portal, which may not address Linux-specific management patterns or command-line usage.
Recommendations
  • List supported Linux operating systems before or alongside Windows versions to avoid implicit prioritization.
  • For services like antimalware, mention Linux alternatives (e.g., integration with third-party Linux antivirus solutions) or clarify the lack of support.
  • Provide Linux-specific examples, such as onboarding via CLI (az, bash scripts) or configuration via SSH, to improve parity.
  • Include references to Linux management tools and patterns where relevant (e.g., systemd, package managers, log locations).
  • Ensure that instructions for enabling and configuring Automanage cover both portal and command-line approaches, especially for Linux administrators.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively uses PowerShell and Windows-centric tooling (Invoke-RestMethod) for all code examples and workflow descriptions. There are no Linux or cross-platform CLI examples (e.g., Bash, curl, Azure CLI), nor any mention of how to perform these steps on non-Windows systems. The structure and language assume the user is on Windows and familiar with PowerShell, which may exclude or inconvenience Linux and macOS users.
Recommendations
  • Add 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 process can be performed on Linux/macOS and provide instructions for those environments.
  • Reorder or parallelize examples so that Windows and Linux approaches are presented together, rather than Windows-first.
  • Clarify that PowerShell Core is available cross-platform, but still provide native Bash/curl examples for Linux users.
GitHub Create Pull Request
← Previous Page 1 of 5 Next →