Azure Arc

465
Total Pages
253
Linux-Friendly Pages
212
Pages with Bias
45.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

2334 issues found
Showing 1401-1425 of 2334 flagged pages
Azure Arc How to organize and inventory servers using hierarchies, tagging, and reporting ...ticles/azure-arc/servers/organize-inventory-servers.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation describes organizing and inventorying servers using Azure Arc, hierarchies, tagging, and reporting. While it mentions support for both Windows and Linux, examples, tooling, and usage patterns are presented in a generic or Azure-centric way, with no platform-specific examples. However, where tools are mentioned (Azure CLI, PowerShell), Windows-centric tooling (PowerShell) is listed before Linux-friendly alternatives (CLI), and there are no explicit Linux command-line or shell examples. No Linux-specific patterns or tools are discussed.
Recommendations
  • Provide explicit Linux examples, such as Bash or shell commands for tagging and querying resources.
  • List Azure CLI before PowerShell when suggesting cross-platform tools, or clarify platform applicability for each tool.
  • Include examples or references for managing Linux servers (e.g., onboarding, tagging) with Linux-native tools or scripts.
  • Highlight any differences or considerations for Linux environments in Azure Arc workflows.
  • Add links to Linux-specific documentation or guides where relevant.
GitHub Create Pull Request
Azure Arc Data and privacy ...in/articles/azure-arc/servers/security-data-privacy.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally provides parity between Windows and Linux in log file locations and descriptions. However, there is evidence of Windows bias: in the section about retaining activity logs, the link specifically references PowerShell tabs, which are Windows-centric, and Windows log paths are consistently listed before Linux equivalents. There are no Linux-specific CLI or shell examples, and the documentation does not mention Linux-native tools or patterns for log management.
Recommendations
  • Provide Linux shell (bash) examples alongside or instead of PowerShell examples, especially for tasks like sending activity log data.
  • Alternate the order of Windows and Linux log path listings, or group them together to avoid implicit prioritization.
  • Include references to Linux-native tools (e.g., journalctl, tail, grep) for viewing or managing logs.
  • Ensure that documentation links and tabs include both PowerShell and Bash/CLI options where relevant.
  • Explicitly state that all features and troubleshooting steps apply equally to Linux and Windows, and highlight any differences.
GitHub Create Pull Request
Azure Arc Azure Resource Graph sample queries for Azure Arc-enabled servers ...n/articles/azure-arc/servers/resource-graph-samples.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references running queries via Azure PowerShell, Azure CLI, and the Azure portal, but lists Azure PowerShell first and does not provide explicit Linux-specific examples or mention Linux-native tools. There is no discussion of Linux shell usage, nor are there examples tailored for Linux environments, which may suggest a subtle Windows-first bias and a lack of Linux parity.
Recommendations
  • Provide explicit Linux shell (bash) examples for running Azure CLI commands.
  • Mention that Azure CLI is cross-platform and can be used natively on Linux and macOS, not just Windows.
  • Include instructions or examples for running queries from Linux terminals, such as using bash scripts or integrating with Linux automation tools.
  • Avoid listing Windows-specific tools (e.g., PowerShell) before cross-platform alternatives unless contextually necessary.
  • Add a note clarifying platform compatibility for all tools mentioned.
GitHub Create Pull Request
Azure Arc Quickstart - Connect a Linux machine with Azure Arc-enabled servers (package-based installation) ...main/articles/azure-arc/servers/quick-onboard-linux.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows Reference Windows Terms
Summary
The documentation is focused on Linux onboarding and provides Linux-specific instructions and examples throughout. However, there are minor references to Windows terminology, such as mentioning 'Windows computer name' alongside Linux hostname in prerequisites, and using terms like 'Windows' in resource naming conventions. No Windows-specific tools, examples, or PowerShell commands are present, and Linux is clearly the primary platform for this guide.
Recommendations
  • Remove or clarify references to 'Windows computer name' in prerequisites to avoid confusion in a Linux-focused guide.
  • Ensure that all terminology and examples are strictly Linux-centric unless cross-platform considerations are necessary.
  • If mentioning reserved words or trademarks, provide Linux-specific context or examples.
  • Continue to avoid Windows/Powershell examples and tools in Linux-specific documentation to maintain platform parity.
GitHub Create Pull Request
Azure Arc Identity and authorization ...s/azure-arc/servers/security-identity-authorization.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally presents Windows paths and group names before their Linux equivalents, and refers to Windows-specific concepts (such as 'Hybrid agent extension applications' group) before mentioning Linux ('himds'). File paths are listed with Windows first, and directory/group names are explained with a Windows-first approach. There are no command-line examples, but the overall pattern prioritizes Windows terminology and organization.
Recommendations
  • Alternate the order of Windows and Linux references, or present Linux examples first in some sections.
  • Provide parallel explanations for both platforms, ensuring equal prominence and clarity.
  • Where possible, use platform-neutral language before specifying OS-specific details.
  • Add explicit Linux group and file path explanations before or alongside Windows ones.
  • Include Linux-specific best practices or troubleshooting notes if Windows ones are present.
GitHub Create Pull Request
Azure Arc Customer intent: "As a system administrator managing Azure Arc-enabled servers, I want to understand the required endpoints for Extended Security Updates so that I can ensure proper connectivity and compliance during installation and updates." ...azure-arc/servers/includes/esu-network-requirements.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on Windows Server 2012 and SQL Server 2012, with all examples and endpoint descriptions tailored to Windows workloads. There are no references to Linux servers, Linux equivalents, or cross-platform considerations, and the installation package is specified as 'Windows installation package' without mention of Linux packages or endpoints.
Recommendations
  • Include information about Linux server support for Azure Arc-enabled servers, if applicable.
  • Provide endpoint requirements and examples for Linux workloads, including package download sources and update mechanisms.
  • Clarify whether Extended Security Updates are available for Linux servers, and if not, explicitly state this to avoid ambiguity.
  • If Linux is not supported for ESU, consider adding a note to inform users and guide them to relevant documentation for Linux scenarios.
GitHub Create Pull Request
Azure Arc Terraform based SCVMM VM management ...ter-virtual-machine-manager/terraform-vm-management.md
Medium Priority View Details →
Scanned: 2026-01-11 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 exclusively referencing SCVMM (a Windows-only virtualization manager) and using Windows-centric terminology (e.g., 'Administrator' as the default username). There are no examples or guidance for Linux-based SCVMM VMs, nor are Linux-specific patterns, usernames, or OS profiles mentioned. All sample configurations and instructions assume Windows environments, and there is no mention of Linux equivalents or considerations.
Recommendations
  • Include explicit examples for Linux-based SCVMM VMs, such as using a Linux username (e.g., 'ubuntu', 'root') and Linux OS profiles in Terraform templates.
  • Add notes or sections describing differences in provisioning Linux VMs via SCVMM, including required variables and configuration changes.
  • Provide sample Terraform code blocks for Linux VM creation and management, highlighting any required changes (e.g., SSH keys instead of passwords, Linux-specific settings).
  • Clarify whether SCVMM supports Linux VMs and, if so, document any prerequisites or limitations for Linux VM management.
  • Ensure that instructions and variable names do not assume Windows defaults (e.g., avoid only using 'Administrator' as the username).
GitHub Create Pull Request
Azure Arc Set up and manage self-service access to SCVMM resources ...manager/set-up-and-manage-self-service-access-scvmm.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation is focused exclusively on SCVMM, a Windows-centric virtualization management tool, and provides instructions only for Azure portal GUI workflows. There are no Linux-specific examples, CLI commands, or references to Linux management tools or patterns. The documentation assumes a Windows/SCVMM environment and does not address Linux-based virtualization or cross-platform access scenarios.
Recommendations
  • Include equivalent instructions for managing access to Linux-based virtualization platforms (e.g., KVM, libvirt) if supported by Azure Arc.
  • Provide Azure CLI or PowerShell command examples for role assignments, and clarify cross-platform compatibility.
  • Add a section comparing SCVMM (Windows) and Linux virtualization management within Azure Arc, highlighting differences and parity.
  • Explicitly state platform limitations and suggest alternatives for Linux administrators where SCVMM is not applicable.
  • Ensure future documentation covers both GUI and CLI workflows, with notes on OS compatibility.
GitHub Create Pull Request
Azure Arc Enable VM extensions to Arc-enabled servers from the Azure portal ...icles/azure-arc/servers/manage-vm-extensions-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page generally presents VM extension management in a platform-neutral way, focusing on the Azure portal. However, when providing configuration examples, it specifically mentions 'deploy the Azure Monitor agent for Windows by using a proxy' without offering a Linux equivalent. There are no explicit Linux-specific examples or references, and Windows is mentioned first in the context of extension configuration. This may subtly reinforce a Windows-centric perspective and leave Linux users without clear guidance for their scenarios.
Recommendations
  • Include explicit examples or notes for deploying extensions on Linux machines, especially where configuration steps differ from Windows.
  • When mentioning Windows-specific scenarios (e.g., proxy configuration for the Azure Monitor agent), also provide Linux equivalents or clarify if the steps are identical or different.
  • Ensure that references to platform-specific tools or patterns (such as PowerShell) are balanced with Linux alternatives (such as Bash or CLI commands), even in related content.
  • Review screenshots and illustrations to ensure they represent both Windows and Linux environments where applicable.
GitHub Create Pull Request
Azure Arc Multiple Solutions with a Single Shared Dependency at Different Levels ...oad-orchestration/tutorial-service-group-scenario-4.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all steps, but PowerShell is given equal prominence and detail as Bash, which can indicate a Windows bias, especially since PowerShell is primarily a Windows shell (though cross-platform now). Additionally, in several places, PowerShell examples are presented before or alongside Bash, rather than Bash or Linux-native tools being prioritized. There are no Linux-specific tools or patterns (such as native Linux utilities, file paths, or shell scripting idioms) beyond Bash, and no mention of Linux desktop environments or distributions. The use of the Azure CLI and Helm is cross-platform, but the presence of PowerShell throughout may signal a bias toward Windows users.
Recommendations
  • Prioritize Bash examples and ensure they are presented first, as Bash is the default shell on most Linux systems.
  • Clearly state that all CLI commands work on Linux, macOS, and Windows, and highlight any platform-specific differences.
  • Limit PowerShell examples to a separate section or appendix, or provide them only where necessary for Windows-specific workflows.
  • Include Linux-specific troubleshooting tips or notes, such as file permissions, environment variables, or common Linux errors.
  • Reference Linux distributions (Ubuntu, CentOS, etc.) in prerequisites or validation steps where appropriate.
  • Use Linux-style file paths and conventions in examples unless Windows-specific paths are required.
GitHub Create Pull Request
Azure Arc Perform ongoing maintenance and administration for Azure Arc-enabled System Center Virtual Machine Manager ...center-virtual-machine-manager/administer-arc-scvmm.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses on Azure Arc-enabled System Center Virtual Machine Manager (SCVMM), a Windows-centric technology. All operational examples use Azure CLI, which is cross-platform, but the instructions and context are tailored to Windows environments (e.g., SCVMM, Azure portal screenshots, resource bridge VM management). There is no mention of Linux-specific tools, patterns, or alternative workflows, nor are there examples showing how to perform maintenance or troubleshooting from a Linux workstation. The documentation implicitly assumes a Windows administrative context and does not address Linux parity.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide example command lines for Linux environments (e.g., file paths, SSH usage).
  • Include instructions for securely storing and managing kubeconfig and YAML files on Linux systems, such as using chmod for permissions.
  • Add examples of connecting to the resource bridge VM via SSH from Linux, including typical SSH command syntax.
  • Mention Linux-native tools (e.g., curl, scp) for log collection and file transfer, and provide sample usage.
  • Clarify any prerequisites or limitations for Linux administrators, such as required CLI extensions or compatibility notes.
  • Provide screenshots or descriptions of Azure portal workflows that are OS-agnostic, or note that the portal is accessible from any OS.
GitHub Create Pull Request
Azure Arc Azure built-in roles for Azure Arc-enabled SCVMM ...ystem-center-virtual-machine-manager/built-in-roles.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation is focused exclusively on Azure Arc-enabled SCVMM, which is inherently a Windows-centric technology (System Center Virtual Machine Manager). All roles and actions described are specific to SCVMM and related Microsoft services, with no mention of Linux equivalents, cross-platform management, or examples for Linux environments. There are no references to Linux tools, commands, or patterns, nor any guidance for Linux administrators.
Recommendations
  • Clearly state at the beginning that SCVMM is a Windows-only technology and that the documentation is intended for Windows environments.
  • If Azure Arc supports Linux-based virtualization platforms (such as VMware, KVM, or others), provide parallel documentation and role definitions for those platforms.
  • Include guidance or references for Linux administrators on how to manage hybrid environments, if applicable.
  • Add cross-platform notes or links to Azure Arc documentation for Linux servers and workloads to help users understand the broader context.
  • Ensure that any future documentation for Azure Arc covers both Windows and Linux scenarios where possible, with examples and role definitions for each.
GitHub Create Pull Request
Azure Arc Create custom roles with Azure Arc-enabled SCVMM ...-center-virtual-machine-manager/create-custom-roles.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page focuses exclusively on Azure Arc-enabled SCVMM, a Windows-centric technology, and all examples and instructions are given using the Azure portal. While it mentions Azure PowerShell and Azure CLI as alternatives, the main walkthrough is portal-based and does not provide any Linux-specific examples or mention Linux-native tools or patterns. The documentation assumes familiarity with SCVMM, which is a Windows-only management tool, and does not discuss Linux VM management or cross-platform considerations.
Recommendations
  • Include explicit instructions or examples for managing custom roles using Azure CLI, which is cross-platform and commonly used on Linux.
  • Clarify whether the steps and role management apply only to SCVMM-managed Windows VMs or if there is parity for Linux VMs managed via Azure Arc.
  • Add notes or links for Linux administrators on how to perform similar RBAC operations for Linux resources in Azure Arc environments.
  • If possible, provide examples of JSON role definitions that include permissions relevant to Linux workloads or resource providers.
  • Ensure that references to PowerShell are balanced with CLI examples, and avoid assuming users are on Windows unless required by the technology.
GitHub Create Pull Request
Azure Arc Enable SCVMM inventory resources in Azure Arc center ...al-machine-manager/enable-scvmm-inventory-resources.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation is focused exclusively on SCVMM (System Center Virtual Machine Manager), a Windows-centric management tool, and provides instructions only for managing SCVMM resources via the Azure portal. There are no references to Linux-based virtualization platforms, nor are there examples or guidance for users managing Linux VMs or using Linux management tools.
Recommendations
  • Include guidance or references for managing Linux-based virtualization platforms (such as KVM, oVirt, or VMware on Linux) in Azure Arc, if supported.
  • Provide examples or links for enabling inventory resources for Linux VMs, or clarify if the feature is Windows/SCVMM-only.
  • Add a comparison table or section outlining differences and parity between Windows SCVMM and Linux virtualization management in Azure Arc.
  • Explicitly state platform limitations and suggest alternative workflows for Linux environments where applicable.
GitHub Create Pull Request
Azure Arc Perform ongoing maintenance and administration for Azure Arc-enabled VMware vSphere ...cles/azure-arc/vmware-vsphere/administer-arc-vmware.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently provides Azure CLI examples and instructions without specifying or demonstrating platform-specific steps for Linux or macOS. All operational guidance assumes use of the Azure CLI, but does not clarify whether commands are cross-platform or highlight differences for Linux users. Additionally, GUI instructions (e.g., Azure portal navigation) are presented without mentioning platform parity or alternatives for Linux environments. There are no PowerShell-specific commands, but the absence of Linux-specific examples or notes creates a subtle Windows-first bias.
Recommendations
  • Explicitly state that Azure CLI commands are cross-platform and provide any necessary Linux/macOS prerequisites (e.g., installation steps, environment variables).
  • Include example commands or screenshots for Linux terminal environments where relevant, especially for SSH and file management operations.
  • Clarify any platform-specific differences in file paths, permissions, or CLI usage between Windows and Linux.
  • Add notes or links for Linux users regarding Azure CLI installation and usage.
  • Where GUI steps are described, mention that the Azure portal is accessible from any OS and provide alternatives (e.g., Azure CLI or REST API) for users who prefer command-line operations.
GitHub Create Pull Request
Azure Arc Create a virtual machine on VMware vSphere using Azure Arc ...les/azure-arc/vmware-vsphere/create-virtual-machine.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily describes VM creation via the Azure portal, with administrator account setup focused on username/password authentication (typical for Windows). Linux-specific guidance is limited to a brief mention that SSH keys can be used for authentication, without further details or examples. No Linux-specific screenshots, step-by-step instructions, or parity in configuration options are provided. The reference to PowerShell in the 'Reference' section is generic, but no Linux CLI or shell examples are given.
Recommendations
  • Provide explicit Linux VM creation examples, including screenshots showing SSH key authentication and Linux-specific options.
  • Include step-by-step instructions for Linux VM setup, such as configuring SSH keys, setting hostnames, and post-deployment steps relevant to Linux.
  • Ensure parity in documentation for both Windows and Linux, such as describing differences in guest management, agent installation, and connectivity for Linux VMs.
  • Add references and examples for Linux command-line tools (e.g., Bash, Azure CLI on Linux) alongside PowerShell.
  • Clarify any differences in VM template usage or customization for Linux guests.
GitHub Create Pull Request
Azure Arc Create a virtual machine on VMware vCenter using Infrastructure as Code methods ...es/azure-arc/vmware-vsphere/quick-start-create-a-vm.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. VM templates and sample values consistently use Windows-centric naming conventions (e.g., 'contoso-template-win22', 'Administrator' as the default username), and all examples assume a Windows guest OS. There are no Linux-specific examples, usernames, or template references, nor any mention of Linux guest customization or provisioning. This may unintentionally signal that Windows is the primary or only supported OS for these workflows.
Recommendations
  • Include Linux VM template examples alongside Windows ones (e.g., 'contoso-template-ubuntu22').
  • Provide sample variable values and code snippets using typical Linux usernames (e.g., 'ubuntu', 'root') and passwords.
  • Add notes or sections describing any Linux-specific configuration steps, such as SSH key injection, cloud-init usage, or differences in agent installation.
  • Clarify in the documentation that both Windows and Linux VMs are supported, and link to resources for Linux guest customization.
  • When listing templates or sample IDs, alternate between Windows and Linux examples to avoid implicit prioritization.
GitHub Create Pull Request
Azure Arc External Validation for Workload Orchestration ...zure-arc/workload-orchestration/external-validation.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation consistently provides both Bash and PowerShell examples for all CLI operations, but PowerShell is always presented as the second tab after Bash. There are no examples or references to Windows-specific tools outside of PowerShell, and no exclusive use of Windows-only patterns. However, the presence of PowerShell examples throughout, and the explicit separation of Bash and PowerShell, may signal a slight Windows bias, especially for users who expect cross-platform parity beyond just CLI syntax. No Linux-specific tools or workflows are mentioned, and the focus is entirely on Azure CLI and PowerShell, which are available on both platforms but may be more familiar to Windows users.
Recommendations
  • Clarify that all CLI examples work identically on both Windows and Linux when using Azure CLI.
  • Consider including a note or section on using Azure CLI in native Linux environments, such as with package managers or shell integration.
  • If relevant, add troubleshooting tips for common Linux shell issues (e.g., quoting, environment variables) when running Azure CLI commands.
  • Ensure that PowerShell examples do not assume Windows-only features and clarify cross-platform compatibility.
  • If possible, add examples using other popular Linux shells (e.g., zsh, fish) or highlight any differences in command syntax or environment setup.
GitHub Create Pull Request
Azure Arc Set Up Workload Orchestration .../workload-orchestration/initial-setup-configuration.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for setting up workload orchestration, but the PowerShell tab is given equal prominence to Bash, which is not typical for cross-platform Azure CLI documentation. The PowerShell examples are extensive and use Windows-centric variable syntax, which may suggest a bias toward Windows users. There are no Linux-specific tools or patterns mentioned, and the Bash examples do not reference Linux-specific nuances or troubleshooting. The documentation does not mention Linux distributions, shell environments, or provide guidance for Linux-specific issues, which could leave Linux users underserved.
Recommendations
  • Prioritize Bash examples and ensure they are fully tested on common Linux distributions (Ubuntu, CentOS, etc.).
  • Add Linux-specific troubleshooting tips (e.g., file permissions, environment variables, shell differences).
  • Mention supported shell environments (e.g., Bash, Zsh) and clarify that Bash examples are intended for Linux/macOS.
  • If PowerShell is included, clarify its cross-platform nature and provide guidance for installing and using PowerShell on Linux.
  • Include notes on differences in file path formats, environment variable usage, and common errors on Linux.
  • Reference Linux-native tools or patterns where appropriate (e.g., using jq for JSON manipulation, curl/wget for downloads).
GitHub Create Pull Request
Azure Arc Create a Solution with Multiple Dependencies with Workload Orchestration ...quickstart-solution-multiple-shared-adapter-dependency.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for every CLI command, but PowerShell examples are always presented immediately after Bash, with equal prominence and detail. There is no evidence of exclusive use of Windows tools or patterns, nor are Windows-specific tools mentioned before Linux equivalents. However, the presence of PowerShell examples throughout, and their parity with Bash, may signal a slight Windows bias, especially for users who expect Linux-first documentation in cloud and Kubernetes contexts.
Recommendations
  • Explicitly state that all commands work on both Linux and Windows, and clarify any platform-specific differences if present.
  • Consider listing Bash examples first, as Bash is the default shell on most Linux and macOS systems and is commonly used in cloud-native environments.
  • Add a note about how to run PowerShell on Linux and macOS, if relevant, to avoid implying PowerShell is Windows-only.
  • If possible, provide a single set of CLI examples (Bash syntax) and mention that PowerShell users can adapt variable syntax as needed, unless there are significant behavioral differences.
  • Review the documentation for any subtle assumptions about file paths, environment variables, or shell behavior that may differ between Windows and Linux.
GitHub Create Pull Request
Azure Arc Create a Basic Solution with Workload Orchestration ...on/quickstart-solution-without-common-configuration.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, but PowerShell examples are always presented immediately after Bash, and variable naming conventions (e.g., $childName) are more Windows-centric. There is no explicit Linux bias, but the presence of PowerShell examples throughout and the use of Windows-style variable names and patterns may suggest a slight Windows bias. No Linux-specific tools, patterns, or troubleshooting are mentioned, and the documentation does not address Linux-specific nuances (such as shell differences or file permissions).
Recommendations
  • Add explicit notes about Linux compatibility, including any differences in CLI behavior, file permissions, or environment setup.
  • Include troubleshooting tips for common Linux issues (e.g., file permissions, path separators).
  • Ensure variable naming and examples are equally representative of Linux conventions (e.g., avoid camelCase for Bash variables, use lowercase with underscores).
  • Consider providing a generic 'CLI' tab for commands that are identical across platforms, reducing the perception of Windows/Powershell bias.
  • Mention any Linux-specific dependencies or prerequisites if applicable.
GitHub Create Pull Request
Azure Arc Create a Solution with Shared Adapter Dependency with Workload Orchestration ...ation/quickstart-solution-shared-adapter-dependency.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for every CLI operation, but PowerShell is always presented as a first-class citizen, with equal prominence and detail as Bash. There is a subtle Windows bias in the structure: PowerShell examples are always present, and sometimes appear before or with Bash, which is less common in cross-platform documentation. There are no Linux-specific tools, troubleshooting steps, or environment setup instructions; the only Linux parity is the Bash tab. No explicit Linux-only examples, nor are Linux-specific nuances discussed.
Recommendations
  • Ensure Bash examples are presented first, as Bash is the default shell on most Linux systems.
  • Add explicit notes about running commands in Linux environments, including common troubleshooting steps (e.g., file permissions, environment variables).
  • Include guidance for Linux package managers or dependencies if any are required.
  • Mention differences in file paths, environment variable syntax, or CLI behavior between Windows and Linux where relevant.
  • Consider adding a section on running the CLI in WSL or native Linux, if applicable.
  • Clarify that PowerShell examples are for Windows users, and Bash for Linux/macOS, to help users choose the right tab.
GitHub Create Pull Request
Azure Arc Upgrade a Shared Application with Workload Orchestration ...orchestration/quickstart-upgrade-shared-application.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, but PowerShell is given equal prominence to Bash, which is uncommon in cross-platform documentation. The PowerShell tab appears immediately after Bash, and variable assignment and command syntax are tailored for Windows/PowerShell users. There is no mention of Linux-specific tools, patterns, or troubleshooting, and the overall structure assumes parity between Windows and Linux, but with a slight emphasis on PowerShell scripting.
Recommendations
  • Add explicit notes about platform compatibility for the Azure CLI commands, clarifying any differences in behavior or prerequisites between Windows and Linux.
  • Include troubleshooting steps or environment setup instructions specific to Linux (e.g., permissions, shell differences, package dependencies).
  • Consider listing Bash examples first, as Bash is the default shell on most Linux and macOS systems.
  • Add a section on running the commands in WSL (Windows Subsystem for Linux) for Windows users who prefer Bash.
  • Ensure that any file path or environment variable usage is cross-platform (e.g., use $HOME instead of %USERPROFILE% in examples).
GitHub Create Pull Request
Azure Arc Service Groups for Workload Orchestration ...cles/azure-arc/workload-orchestration/service-group.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all command-line operations, but PowerShell examples are always listed after Bash, and in some cases, PowerShell code is more elaborate (e.g., using ConvertFrom-JSON, Select-Object, etc.). There is no evidence of exclusive use of Windows tools or missing Linux examples, as all commands use the cross-platform Azure CLI. However, the PowerShell examples are sometimes more detailed, and the documentation assumes familiarity with PowerShell-specific patterns (backticks, object manipulation), which may be less accessible to Linux users. There is a mild 'windows_first' bias in the sense that PowerShell is given parity but with more complexity, and some advanced steps are only shown in PowerShell.
Recommendations
  • Ensure that Bash and PowerShell examples are equally detailed and cover all advanced scenarios in both tabs.
  • Where PowerShell-specific object manipulation is shown (e.g., working with JSON, arrays), provide equivalent Bash/jq examples for Linux users.
  • Add a note clarifying that Azure CLI commands work cross-platform and that Bash examples are suitable for Linux/macOS users.
  • Avoid PowerShell-specific idioms (like backticks for line continuation) in shared explanations, or provide Bash equivalents.
  • Consider listing Bash examples first, or alternating the order, to avoid implicit prioritization of Windows/PowerShell.
GitHub Create Pull Request
Azure Arc Solution with a Leaf Target ...oad-orchestration/tutorial-service-group-scenario-1.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, ensuring coverage for both Linux and Windows users. However, PowerShell examples are given equal prominence as Bash, and in some cases, PowerShell syntax is used for Azure CLI commands that are platform-agnostic. There is a slight Windows bias in the sense that PowerShell is featured as the primary alternative to Bash, rather than including other Linux-native shells or scripting environments. No explicit Windows-only tools or patterns are used, and Linux examples are not missing.
Recommendations
  • Clarify that Azure CLI commands work identically in Bash and PowerShell, and that PowerShell is not required on Windows if Bash is available.
  • Consider including a note that Bash examples can be run on Windows using WSL or Git Bash, to encourage Linux parity for Windows users.
  • If possible, add examples for other Linux shells (e.g., zsh) or scripting environments, or clarify that Bash syntax is representative of most Linux shells.
  • Avoid implying that PowerShell is the default or preferred scripting environment for Windows users unless there is a technical reason.
  • Ensure that any platform-specific nuances (e.g., file path separators, environment variable syntax) are highlighted where relevant.
GitHub Create Pull Request
← Previous Page 57 of 94 Next →