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 1451-1475 of 2334 flagged pages
Azure Arc Use private connectivity for Azure Arc-enabled Kubernetes clusters with private link (preview) ...lob/main/articles/azure-arc/kubernetes/private-link.md
Medium Priority View Details →
Scanned: 2026-01-10 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 using Azure Portal (GUI) and Azure CLI examples, with no mention of Linux-specific tools or command-line patterns outside of Azure CLI. There are no PowerShell examples, but the instructions and screenshots are focused on the Azure Portal, which is most commonly used on Windows. There is no reference to Linux-native tools (such as curl, dig, or Linux firewall configuration), nor are there examples of configuring DNS or firewall rules using Linux commands. The troubleshooting section uses nslookup, which is available on both Windows and Linux, but does not mention alternatives like dig or provide Linux-specific guidance.
Recommendations
  • Add Linux-specific command-line examples for DNS configuration and troubleshooting (e.g., using dig, systemd-resolved, or BIND).
  • Include instructions for configuring firewalls on Linux (e.g., using iptables, nftables, or ufw) alongside references to Azure NSG and Windows firewalls.
  • Provide guidance for managing DNS forwarding and records on common Linux DNS servers (such as BIND or dnsmasq), not just generic 'consult your vendor' advice.
  • Clarify that Azure CLI is cross-platform and provide installation instructions for Linux users.
  • Include screenshots or walkthroughs for Linux environments where relevant, especially for on-premises steps.
GitHub Create Pull Request
Azure Arc Add a public cloud with the multicloud connector in the Azure portal ...les/azure-arc/multicloud-connector/add-public-cloud.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page presents steps for connecting AWS and GCP to Azure using the Azure portal, with template-based onboarding. While the page is generally cloud-agnostic, there is subtle Windows bias: when describing how to run Terraform for GCP onboarding, it mentions Azure Cloud Shell and local execution but does not provide explicit Linux CLI examples or mention Linux-specific tools. Additionally, the order of instructions and examples tends to present Windows/Azure-centric workflows first (e.g., Azure portal, Azure Cloud Shell), with Linux alternatives only implied or omitted.
Recommendations
  • Explicitly provide Linux CLI examples for running Terraform and interacting with GCP, including commands for common Linux shells (bash, zsh).
  • Mention Linux-native tools (e.g., gcloud CLI on Linux, Linux Cloud Shell) alongside Azure Cloud Shell and Windows tools.
  • Ensure parity by listing Linux and Windows options together when discussing where and how to execute onboarding steps.
  • Add troubleshooting or FAQ sections for Linux-specific issues that may arise during onboarding.
  • Clarify that all steps can be performed from Linux environments, not just Azure Cloud Shell or Windows.
GitHub Create Pull Request
Azure Arc Azure Arc resource bridge system requirements ...icles/azure-arc/resource-bridge/system-requirements.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page for Azure Arc resource bridge system requirements exhibits Windows bias by referencing Azure CLI installation instructions specifically for Windows (with a direct link to the Windows install page), and by omitting explicit Linux or macOS management machine requirements or examples. There are no Linux-specific instructions, examples, or parity checks for CLI installation, usage, or environment setup, despite Azure CLI being cross-platform.
Recommendations
  • Include explicit instructions and links for installing Azure CLI on Linux and macOS alongside Windows.
  • Clarify that the management machine can be Windows, Linux, or macOS, and provide minimum requirements for each OS.
  • Provide example deployment commands and file paths for Linux/macOS environments (e.g., default CLI directory locations, file permissions).
  • Mention any OS-specific considerations (such as SSH client availability, firewall configuration, or package dependencies) for Linux and macOS.
  • Ensure all CLI commands and configuration steps are validated and documented for Linux and macOS, not just Windows.
GitHub Create Pull Request
Azure Arc Programmatically deploy and manage Azure Arc Extended Security Updates licenses ...les/azure-arc/servers/api-extended-security-updates.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows Server 2012 scenarios and does not provide any Linux-specific examples or mention Linux equivalents for license management. All examples, parameters, and instructions are tailored to Windows environments, with no guidance for Linux systems or workloads.
Recommendations
  • Add explicit examples for Linux machines, such as provisioning and managing ESU licenses for Linux servers if supported.
  • Clarify whether the APIs and Azure CLI commands can be used for Linux workloads, and if so, provide relevant parameter values and scenarios.
  • Include Linux-specific notes or sections to address cross-platform usage, even if the feature is Windows-only, to inform users of platform limitations.
  • If the feature is not available for Linux, state this clearly at the beginning of the documentation to avoid confusion.
GitHub Create Pull Request
Azure Arc CLI reference for `azcmagent extension` ...main/articles/azure-arc/servers/azcmagent-extension.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows-first bias by listing Windows service management commands (Stop-Service/Start-Service) before their Linux equivalents (systemctl stop/start), and by referencing a Windows-specific extension ('AzureMonitorWindowsAgent') in the example. Windows tools and patterns are mentioned first and more prominently, while Linux examples and extension names are less visible.
Recommendations
  • Alternate the order of Windows and Linux commands when describing service management (e.g., list systemctl before Stop-Service in some places).
  • Provide Linux-specific extension examples (e.g., use an extension name relevant to Linux in the remove example).
  • Explicitly state cross-platform applicability in examples and usage notes.
  • Include a table or section summarizing both Windows and Linux commands for common operations.
  • Ensure that extension names and scenarios are balanced between Windows and Linux environments.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on Windows Server 2012 and SQL Server 2012, with all endpoint descriptions and examples tailored to Windows environments. There are no references to Linux servers, Linux-based Azure Arc scenarios, or Linux-specific endpoints, tools, or patterns. The documentation assumes the reader is managing Windows workloads, omitting Linux parity and guidance.
Recommendations
  • Include equivalent guidance for Linux servers managed by Azure Arc, specifying required endpoints for Extended Security Updates (if applicable).
  • Add examples and notes for Linux installation/update processes, including package sources, certificate handling, and extension management.
  • Clarify whether Extended Security Updates via Azure Arc are available for Linux workloads, and if not, explicitly state this to avoid confusion.
  • If Linux is not supported for ESU in this scenario, provide links or references to general Azure Arc Linux documentation for completeness.
GitHub Create Pull Request
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page describes organizing and inventorying servers using Azure Arc, hierarchies, tagging, and reporting. While it mentions support for both Windows and Linux, all examples and tool references (Azure CLI, PowerShell, ARM templates) are generic or Windows-centric, with no Linux-specific examples, commands, or considerations. The documentation implicitly assumes Windows environments by referencing tools and patterns more common to Windows administrators, and does not provide parity for Linux users in terms of examples or operational guidance.
Recommendations
  • Add explicit Linux-specific examples for tagging, querying, and reporting (e.g., using Bash with Azure CLI, Linux shell scripts, or integration with Linux-native tools).
  • Include sample commands for both Windows (PowerShell) and Linux (Bash) when demonstrating Azure CLI or other tool usage.
  • Highlight any differences or considerations for Linux servers when onboarding to Azure Arc, tagging, or reporting.
  • Reference Linux-native management tools or patterns where appropriate, and provide guidance for integrating them with Azure Arc.
  • Ensure that screenshots, diagrams, and sample outputs reflect both Windows and Linux environments.
GitHub Create Pull Request
Azure Arc Identity and authorization ...s/azure-arc/servers/security-identity-authorization.md
Medium Priority View Details →
Scanned: 2026-01-10 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 references Windows-specific concepts (e.g., 'local administrators', 'C:\ProgramData', 'Hybrid agent extension applications') prior to or more prominently than Linux ones. There are no Linux-specific command examples or tool references, and the structure tends to favor Windows terminology and patterns.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them side-by-side for parity.
  • Include Linux-specific command-line examples (e.g., using 'ls', 'chmod', 'chown') where relevant.
  • Reference Linux group names and file paths with equal prominence to Windows equivalents.
  • Add guidance for managing permissions and access control on Linux systems, not just referencing Windows ACLs.
  • Ensure screenshots and walkthroughs include Linux scenarios where applicable.
GitHub Create Pull Request
Azure Arc Quickstart - Connect a machine to Arc-enabled servers (Windows or Linux install script) ...n/articles/azure-arc/servers/quick-enable-hybrid-vm.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Windows onboarding instructions before Linux, and provides explicit PowerShell usage for Windows, while Linux instructions are more generic. Windows-specific tooling (PowerShell) is mentioned by name, whereas Linux instructions do not specify shell or package manager details. Both platforms are covered, but Windows is given primacy and more detailed command context.
Recommendations
  • Alternate the order of Windows and Linux instructions or present them in parallel to avoid implicit prioritization.
  • Provide equally detailed Linux instructions, specifying the shell (e.g., Bash) and mentioning common package managers (apt, yum, zypper) where relevant.
  • Include example output or troubleshooting steps for Linux similar to those for Windows.
  • Explicitly mention that both Windows and Linux scripts are generated and clarify any differences in script usage or prerequisites.
  • Where PowerShell is referenced for Windows, mention the equivalent shell (Bash) for Linux and provide parity in command specificity.
GitHub Create Pull Request
Azure Arc Extensions security for Azure Arc-enabled servers ...main/articles/azure-arc/servers/security-extensions.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally maintains parity between Windows and Linux, but Windows examples and terminology are often presented first, and PowerShell commands are highlighted for Windows while Bash is used for Linux. In some sections, Windows tools and scenarios are described before their Linux equivalents, and links to PowerShell documentation precede CLI references. However, most examples are provided for both platforms, and Linux is not omitted.
Recommendations
  • Alternate the order of Windows and Linux examples to avoid consistently prioritizing Windows.
  • Present CLI and Bash examples before or alongside PowerShell examples, especially in cross-platform contexts.
  • Ensure links to CLI and Linux documentation are given equal prominence as PowerShell and Windows links.
  • Explicitly state platform parity in introductory sections to reinforce equal support.
  • Where possible, use platform-neutral language and avoid referring to Windows-specific tools or scenarios before their Linux equivalents.
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-10 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 any examples or guidance for users managing Linux environments or using Linux tools.
Recommendations
  • Include references or links to equivalent Azure Arc onboarding processes for Linux-based virtualization platforms (e.g., KVM, oVirt, Proxmox).
  • Provide examples or documentation for managing Linux VMs and resources in Azure Arc, ensuring parity in instructions and screenshots.
  • Clearly state the Windows/SCVMM scope in the introduction and suggest alternative documentation for Linux users.
  • If possible, add a comparison table highlighting supported features and onboarding steps for both Windows (SCVMM) and Linux virtualization environments.
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-10 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 focusing exclusively on Azure portal GUI steps and Azure CLI commands, without mentioning or providing examples for Linux-specific workflows, shell environments, or tools. There is no reference to PowerShell, but the absence of Linux command-line examples (e.g., bash, SSH usage details, Linux file paths) and the use of Windows-centric terminology (e.g., 'workstation', 'current CLI directory') suggest a Windows-first perspective. No Linux-specific troubleshooting, credential management, or log collection patterns are discussed.
Recommendations
  • Add explicit Linux shell (bash) examples for all CLI commands, including notes on file path differences and environment setup.
  • Clarify that Azure CLI commands work cross-platform and provide guidance for Linux users (e.g., installing Azure CLI on Linux, using SSH from Linux, storing kubeconfig in Linux home directories).
  • Include screenshots or instructions for Linux desktop environments where GUI steps are referenced.
  • Mention Linux-specific troubleshooting steps, such as using journalctl or systemd for log collection on the resource bridge VM.
  • Ensure terminology is platform-neutral (e.g., use 'machine' or 'host' instead of 'workstation', specify both Windows and Linux locations for configuration files).
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-10 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 a Windows-centric technology (System Center Virtual Machine Manager). All roles and permissions described are for managing SCVMM resources, with no mention of Linux equivalents, Linux-based management tools, or cross-platform scenarios. There are no examples, references, or guidance for Linux environments or tools. The documentation assumes a Windows infrastructure and does not address Linux users or administrators.
Recommendations
  • Add context or guidance for users managing hybrid environments, including Linux hosts managed via Azure Arc.
  • Include references or links to Azure Arc documentation for Linux servers and VMs, highlighting role definitions and permissions for Linux resources.
  • Provide examples or scenarios where Linux resources are managed alongside SCVMM, and clarify role differences or similarities.
  • Explicitly state the Windows-only scope of SCVMM and direct Linux users to relevant Azure Arc documentation.
  • If possible, add a section comparing SCVMM roles with those available for Linux-based Azure Arc resources, to help users understand cross-platform role management.
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-10 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 primarily through its exclusive focus on SCVMM (a Windows-centric virtualization manager) and the use of Windows-specific conventions (e.g., 'Administrator' username, domain/workgroup references) in examples. There are no Linux-specific instructions, examples, or considerations, and all sample Terraform configurations assume Windows VM patterns. The documentation does not mention Linux VMs, Linux authentication, or Linux-specific provisioning steps, nor does it provide parity for Linux users in terms of examples or troubleshooting.
Recommendations
  • Add explicit examples for managing Linux-based VMs via SCVMM, including sample variables.tf, tfvars, and main.tf files with Linux conventions (e.g., 'root' or other Linux usernames, SSH key authentication, Linux OS profile settings).
  • Include notes or sections describing differences in provisioning Linux VMs versus Windows VMs, such as initialization scripts, agent installation, and credential management.
  • Provide troubleshooting tips or best practices for Linux VM lifecycle management in SCVMM environments.
  • Ensure that prerequisites and steps are inclusive of both Windows and Linux workstation environments (e.g., mention that Terraform can be installed and used on Linux, macOS, and Windows).
  • Where domain or workgroup settings are referenced, clarify their applicability or alternatives for Linux VMs.
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-10 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 generic steps, but in the 'Administrator account' section, it defaults to username/password authentication (typical for Windows) and only mentions Linux/SSH as an alternative. No Linux-specific examples, screenshots, or guidance are provided, and Windows patterns are implicitly prioritized.
Recommendations
  • Provide explicit Linux VM creation examples, including screenshots showing SSH key authentication.
  • Clarify Linux-specific steps, such as cloud-init support, SSH configuration, and post-deployment access.
  • Mention Linux guest customization options in the 'Advanced' section, such as script injection or OS-specific settings.
  • Balance authentication guidance by presenting SSH key as a primary method for Linux VMs, not just as an alternative.
  • Include references to Linux management tools or patterns where relevant (e.g., package updates, monitoring agents).
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by exclusively using Windows-centric examples and patterns, such as 'Administrator' as the VM username, and VM templates named with 'win22'. There are no examples or references to Linux VM templates, Linux usernames, or Linux-specific provisioning steps. The documentation does not mention Linux tools, patterns, or provide Linux-focused sample values, making it less accessible for users intending to deploy Linux VMs.
Recommendations
  • Add Linux VM template examples alongside Windows examples (e.g., use a template named 'contoso-template-ubuntu20' or similar).
  • Provide sample variable values for Linux VMs, such as 'vm_username = "ubuntu"' or 'vm_username = "root"'.
  • Include notes or sections that describe differences in provisioning Linux VMs, such as SSH key usage instead of passwords.
  • Explicitly mention Linux compatibility and provide guidance for Linux-specific configuration (e.g., cloud-init, SSH setup).
  • Ensure that both Windows and Linux scenarios are covered equally in code samples and explanations.
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-10 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 commands, but PowerShell (Windows) examples are always presented immediately after Bash, and sometimes with slightly more detail. There is no evidence of exclusive Windows tools or patterns, but the presence of PowerShell examples throughout the page may signal a slight Windows bias, especially as Linux-specific shell environments (e.g., zsh, fish) are not mentioned, nor are native Linux tools beyond Bash. The Azure portal instructions are platform-neutral, but the CLI instructions focus only on Bash and PowerShell, omitting other Linux shells or macOS-specific considerations.
Recommendations
  • Add explicit mention that Bash examples apply to Linux and macOS environments, and clarify any differences if present.
  • Consider including examples for other popular Linux shells (e.g., zsh) or note that Bash commands are compatible.
  • Ensure parity in detail and explanation between Bash and PowerShell sections.
  • If platform-specific issues exist (e.g., file path formats, authentication differences), call them out in notes.
  • Add a brief section on running Azure CLI commands on macOS and Linux, including installation and environment setup tips.
GitHub Create Pull Request
Azure Arc Set Up Workload Orchestration .../workload-orchestration/initial-setup-configuration.md
Medium Priority View Details →
Scanned: 2026-01-10 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 section is given equal prominence and detail as Bash, despite PowerShell being primarily a Windows tool. There is no explicit mention of Linux-specific tools, nor are Linux-native patterns (such as shell scripting, environment variables, or file system conventions) discussed. The documentation does not clarify which examples are recommended for Linux users, nor does it address differences in environment setup or command syntax between Windows and Linux platforms.
Recommendations
  • Clearly indicate which examples are intended for Linux and which for Windows, and recommend Bash for Linux users and PowerShell for Windows users.
  • Provide Linux-specific guidance, such as using native Linux tools (e.g., jq, sed, grep) for JSON manipulation or file operations.
  • Add notes about environment differences (e.g., file paths, environment variable syntax) between Windows and Linux.
  • Ensure that Bash examples are comprehensive and do not assume familiarity with PowerShell.
  • Consider adding troubleshooting tips for common issues encountered on Linux (e.g., permissions, shell compatibility).
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation consistently provides both Bash and PowerShell examples side-by-side for every CLI operation. However, PowerShell is given equal prominence to Bash, which may suggest a Windows-centric approach, especially since PowerShell is primarily a Windows shell (though it is available cross-platform). There are no Linux-specific tools, patterns, or troubleshooting steps mentioned, nor are there any examples using native Linux utilities or shell scripting beyond Bash. No Linux-only workflows or considerations are discussed, and PowerShell examples are always present, which can imply a bias toward Windows environments.
Recommendations
  • Clarify that PowerShell examples are intended for cross-platform PowerShell (pwsh), not Windows-only PowerShell, if applicable.
  • Add explicit notes or sections for Linux-specific considerations, such as file permissions, environment setup, or troubleshooting common Linux issues.
  • Include examples using native Linux utilities or shell scripting (e.g., using grep, awk, sed for output parsing) where relevant.
  • Provide guidance for users working in Linux-only environments, such as using Bash exclusively or integrating with Linux package managers.
  • Consider adding troubleshooting steps for common Linux deployment issues (e.g., SELinux, systemd, networking differences).
  • If PowerShell is not required for Linux users, clarify that Bash is the recommended shell for Linux and macOS.
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-10 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 is always presented as a first-class citizen alongside Bash, rather than as a secondary or alternative option. In some cases, PowerShell examples are given equal prominence, which can be interpreted as a Windows bias, especially since Linux users typically use Bash and Windows users use PowerShell. There are no Linux-specific tools, patterns, or troubleshooting steps mentioned, and no explicit references to Linux environments or considerations. The documentation does not mention WSL, Linux file paths, or shell differences, and does not address potential issues that may arise when running these commands on Linux versus Windows. All CLI commands are cross-platform (Azure CLI), but the parity in examples does not extend to Linux-specific guidance.
Recommendations
  • Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and clarify any OS-specific considerations.
  • Provide troubleshooting tips for common Linux-specific issues (e.g., file permissions, path formats, environment variable syntax differences).
  • Include Linux-specific notes where relevant, such as differences in shell behavior, quoting, or file handling.
  • Consider adding a dedicated Linux section for advanced users, or at least a note about compatibility with Linux distributions.
  • Mention that Bash examples are suitable for Linux/macOS, and PowerShell for Windows, to guide users to the correct tab for their OS.
  • If possible, add examples using native Linux tools (e.g., jq for JSON parsing, curl for REST calls) where appropriate.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation consistently presents both Bash and PowerShell examples for all command-line instructions, but PowerShell examples are always listed after Bash. However, the PowerShell examples are detailed and use Windows-specific scripting constructs (e.g., backticks for line continuation, PowerShell variables, and cmdlets like ConvertFrom-JSON, Select-Object, Set-Content), which are only relevant for Windows users. There is no evidence of exclusive use of Windows tools or missing Linux examples, as Bash instructions are provided throughout. The documentation does not mention Windows-specific tools or patterns before their Linux equivalents, but the PowerShell examples are more elaborate in some places, which may encourage a Windows-centric workflow for advanced scenarios.
Recommendations
  • Ensure that Bash and PowerShell examples are equally detailed and cover advanced scenarios in both shells.
  • Consider alternating the order of Bash and PowerShell tabs in different sections to avoid implicit prioritization.
  • Add a brief note clarifying that both Bash and PowerShell examples are supported equally on Azure CLI, and that users should choose based on their environment.
  • Where PowerShell-specific constructs are used (e.g., ConvertFrom-JSON, Set-Content), provide equivalent Bash alternatives (e.g., jq, cat/echo) to ensure Linux users have parity for complex tasks.
  • Review all examples to ensure that neither shell is given more advanced or complete coverage than the other.
GitHub Create Pull Request
Azure Arc Solution with a Non-Leaf Target ...oad-orchestration/tutorial-service-group-scenario-2.md
Medium Priority View Details →
Scanned: 2026-01-10 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 steps, but PowerShell examples are consistently presented after Bash, and the PowerShell examples use Windows-specific scripting conventions. There is no evidence of exclusive use of Windows tools or missing Linux examples, but the presence of PowerShell tabs and scripts throughout the page indicates a bias toward Windows users and workflows.
Recommendations
  • Ensure Bash examples are fully tested and use idiomatic Linux shell scripting.
  • Consider providing cross-platform notes for users running Bash on Windows (e.g., WSL, Git Bash) and PowerShell on Linux.
  • Explicitly mention that all commands are supported on both Linux and Windows, and clarify any platform-specific caveats.
  • Add troubleshooting tips for common issues on Linux environments (e.g., file permissions, path separators).
  • If possible, include a generic CLI tab for commands that are identical across platforms, reducing duplication and emphasizing parity.
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-10 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 steps, but consistently lists PowerShell examples after Bash. However, the PowerShell examples are written in a way that assumes familiarity with Windows conventions (e.g., backtick line continuations, Windows-style paths), and there is no mention of Linux-specific tools or troubleshooting. The overall structure and language subtly prioritize Windows/PowerShell usage, and there is no explicit guidance for Linux users regarding environment setup, shell differences, or potential issues.
Recommendations
  • Add explicit notes about Linux environment setup, including prerequisites such as Bash shell, package managers, and file path conventions.
  • Provide troubleshooting tips for common Linux issues (e.g., file permissions, path separators, environment variables).
  • Ensure that Bash examples use Linux-style paths and conventions throughout, and clarify any differences in command syntax or output between Bash and PowerShell.
  • Consider adding a 'Linux-specific considerations' section to highlight any nuances or best practices for Linux users.
  • Where relevant, mention Linux-native tools or alternatives (e.g., using jq for JSON manipulation, grep for searching output) alongside Azure CLI commands.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/connectivity.md ...docs/blob/main/articles/azure-arc/data/connectivity.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page presents examples and tooling in a platform-neutral way for most operations, referencing Azure Data Studio, CLI, and Kubernetes-native tools. However, there is a subtle Windows bias in the authentication section, where Active Directory (AD) and Active Directory Federation Services (ADFS) are mentioned as alternatives to Microsoft Entra ID, without mentioning Linux-native authentication options (such as LDAP or Kerberos). Additionally, the documentation does not provide explicit Linux command-line examples or reference Linux-specific tools, which may leave Linux administrators without clear guidance.
Recommendations
  • Add explicit Linux authentication options (e.g., LDAP, Kerberos) alongside Active Directory/ADFS in the authentication section.
  • Provide Linux-specific command-line examples for provisioning, configuration, and management tasks (e.g., using bash, curl, kubectl on Linux).
  • Reference Linux-native tools and patterns where appropriate, such as systemd, cron, or Linux file paths for backup/restore operations.
  • Ensure that any mention of Windows-centric technologies (Active Directory, ADFS) is balanced with Linux equivalents or alternatives.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/managed-instance-disaster-recovery-portal.md ...-arc/data/managed-instance-disaster-recovery-portal.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes disaster recovery configuration using the Azure portal UI, which is platform-agnostic but implicitly assumes a GUI workflow common to Windows users. There are no examples or mentions of Linux-specific tools, CLI commands, or cross-platform alternatives within the main content. The only reference to CLI-based configuration is in the 'Related content' section, which is listed after the portal instructions, suggesting a secondary priority. There is no mention of Linux shell commands, nor is there guidance for users who may prefer or require non-GUI workflows.
Recommendations
  • Include explicit references to cross-platform CLI workflows (e.g., Azure CLI, az commands) within the main documentation, not just as related links.
  • Provide example commands for disaster recovery configuration using Azure CLI or PowerShell, and clarify which are available on Linux, macOS, and Windows.
  • Add notes or sections highlighting how Linux users can perform equivalent actions, including screenshots or terminal output where appropriate.
  • Ensure that non-Windows workflows are presented with equal prominence and detail as portal-based instructions.
GitHub Create Pull Request
← Previous Page 59 of 94 Next →