Azure Arc

926
Total Pages
755
Linux-Friendly Pages
171
Pages with Bias
18.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

432 issues found
Showing 226-250 of 432 flagged pages
Azure Arc Prepare the Environment for Workload Orchestration ...rc/workload-orchestration/initial-setup-environment.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows notable Windows bias, especially in the initial setup and extraction steps. The only example for installing kubectl uses Windows-specific 'winget', and the zip extraction instructions use 'Expand-Archive', a Windows/PowerShell command, even in the Bash tab. There are no Linux/macOS equivalents for these steps, and Windows tools/patterns are presented first or exclusively. While the Azure CLI and kubectl commands themselves are cross-platform, the setup instructions create friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS equivalents for installing kubectl (e.g., 'curl' or 'apt/yum/brew' commands).
  • Replace or supplement 'Expand-Archive' with cross-platform zip extraction commands (e.g., 'unzip archive.zip -d /path/to/dir').
  • Ensure Bash tab examples use native Bash/Linux commands, not PowerShell/Windows commands.
  • Add explicit notes or sections for Linux/macOS users where platform-specific steps differ.
  • List installation and extraction instructions for all major platforms, not just Windows.
GitHub Create Pull Request
Azure Arc Migrate Existing Target Resources to General Availability ...s/azure-arc/workload-orchestration/migration-script.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only a PowerShell migration script and example, with no mention of Bash, shell, or cross-platform alternatives. This assumes users are on Windows or have PowerShell installed, which may not be the case for Linux/macOS users.
Recommendations
  • Provide a Bash or shell script alternative for Linux/macOS users.
  • Clarify whether the PowerShell script is compatible with PowerShell Core on Linux/macOS, and provide installation instructions if so.
  • Explicitly mention cross-platform support or limitations for the migration script.
  • Include Linux/macOS command-line examples alongside PowerShell.
GitHub Create Pull Request
Azure Arc Bulk Review, Publish, and Deploy with Workload Orchestration ...es/azure-arc/workload-orchestration/bulk-deployment.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation consistently uses PowerShell syntax for all CLI examples, references .ps1 scripts (Windows PowerShell), and does not provide Linux/macOS shell equivalents or guidance. Script tooling is Windows-centric, and there is no mention of Bash, shell, or cross-platform alternatives. This creates friction for Linux/macOS users who may not use PowerShell or .ps1 scripts.
Recommendations
  • Provide CLI examples using Bash/sh syntax alongside PowerShell, especially for az CLI commands.
  • Offer Linux/macOS-compatible versions of deployment scripts (e.g., bulk_deployment.sh) and document their usage.
  • Clarify whether .ps1 scripts can be run with PowerShell Core on Linux/macOS, or provide native shell alternatives.
  • Explicitly state cross-platform compatibility for all commands and scripts.
  • List Linux/macOS instructions and examples before or alongside Windows/PowerShell ones, not after.
GitHub Create Pull Request
Azure Arc Azure Arc agent ...n/articles/azure-arc/vmware-vsphere/azure-arc-agent.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page presents Windows agent installation details before Linux, with more granular information about Windows-specific tools, services, accounts, and troubleshooting. Windows paths, service names, and security group details are more extensively described, while Linux coverage is briefer and lacks equivalent detail (e.g., no mention of Linux user/group management or troubleshooting tips). Windows-centric terminology and patterns (MSI, Download Center, Group Policy) are used, and Windows examples are consistently listed first.
Recommendations
  • Present Linux and Windows installation details in parallel, or alternate which OS is described first in each section.
  • Expand Linux documentation to match Windows detail, including user/group management, service configuration, and troubleshooting tips.
  • Include Linux-specific commands and configuration patterns (e.g., systemd unit files, SELinux/AppArmor considerations, package manager commands).
  • Provide parity in troubleshooting guidance, log file locations, and artifact cleanup steps.
  • Avoid Windows-centric terminology (e.g., 'Group Policy') without Linux equivalents or explanations.
GitHub Create Pull Request
Azure Arc Quickstart - Deploy Azure Arc-enabled data services - directly connected mode - Azure portal ...ttps://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-complete-managed-instance-directly-connected.md
Medium 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 demonstrates a Windows bias by referencing Windows-specific file paths (e.g., C:<current path>\.kube\config), using Azure portal and CLI examples that implicitly assume Windows environments, and omitting explicit Linux/macOS instructions or examples. No Linux/macOS-specific guidance is provided for steps such as accessing the kubeconfig file, installing client tools, or using the Azure CLI, which may behave differently on non-Windows platforms.
Recommendations
  • Include Linux/macOS-specific instructions and examples, such as typical file paths (e.g., ~/.kube/config) and command syntax differences.
  • Add screenshots or terminal outputs from Linux/macOS environments alongside Windows examples.
  • Explicitly state that the instructions apply to all platforms, and note any platform-specific differences in tool installation or usage.
  • Provide guidance on installing Azure Data Studio, Azure CLI, and Kubernetes CLI on Linux/macOS.
  • Avoid using Windows-only file path formats in example outputs, or provide both Windows and Linux/macOS variants.
GitHub Create Pull Request
Azure Arc Resize persistent volume claim (PVC) for Azure Arc-enabled data services volume ...icles/azure-arc/data/resize-persistent-volume-claim.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides shell command examples for Kubernetes operations, but the PVC patching step uses a variable assignment syntax ($newsize='...') that is specific to PowerShell or Windows command line environments. There are no equivalent examples for Linux/macOS shells (e.g., Bash), and the Windows/PowerShell syntax is presented exclusively and first, which may confuse or block Linux/macOS users.
Recommendations
  • Provide equivalent Bash/Linux/macOS command examples for variable assignment and kubectl patch usage.
  • Clarify which shell environment each example is intended for, and present both Windows/PowerShell and Linux/Bash examples side-by-side.
  • Add a note explaining the differences in shell syntax for variable assignment and command execution.
  • Consider using shell-agnostic kubectl patch commands (e.g., inline JSON patching) where possible.
GitHub Create Pull Request
Azure Arc Configure "BYOM" Endpoint Authentication for Edge RAG ...zure-arc/edge-rag/configure-endpoint-authentication.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page provides all command-line examples using PowerShell syntax and Windows-specific patterns (e.g., '.\kubectl.exe'), with no mention or examples for Linux/macOS shells. This creates friction for non-Windows users, who must adapt commands and may encounter issues with syntax and executable naming.
Recommendations
  • Add equivalent bash/zsh examples for Linux/macOS users, using standard shell syntax.
  • Use platform-neutral command formats (e.g., 'kubectl' instead of '.\kubectl.exe') where possible.
  • Explicitly note any platform-specific differences in command usage.
  • Provide guidance for both Windows and Linux/macOS environments in all steps.
GitHub Create Pull Request
Azure Arc Configure DNS for Edge RAG Preview Enabled by Azure Arc ...s/blob/main/articles/azure-arc/edge-rag/prepare-dns.md
Medium 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 provides only Windows-specific instructions for updating the hosts file (using Notepad, referencing the Windows hosts file path), with no mention of Linux or macOS equivalents. This creates friction for non-Windows users who need to perform the same DNS configuration.
Recommendations
  • Add instructions for editing the hosts file on Linux (e.g., using nano or vim to edit /etc/hosts with sudo).
  • Include macOS-specific guidance (editing /etc/hosts with TextEdit or terminal editors).
  • Present cross-platform steps in parallel or clearly labeled sections (e.g., 'Windows', 'Linux', 'macOS').
  • Avoid referencing Windows tools (Notepad, Administrator privileges) exclusively; mention alternatives for other platforms.
GitHub Create Pull Request
Azure Arc Connect hybrid machines to Azure at scale ...rticles/azure-arc/servers/onboard-service-principal.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Windows and Linux options for connecting hybrid machines to Azure Arc, but exhibits a Windows-first bias in several areas. Windows tools (PowerShell) are emphasized, examples and notes often mention Windows before Linux, and PowerShell-specific instructions are detailed. Linux instructions are present but sometimes less prominent, and Linux-specific automation or troubleshooting is not covered in equal depth.
Recommendations
  • Alternate the order of Windows and Linux instructions/examples throughout the documentation to avoid Windows-first presentation.
  • Provide Linux-specific automation and troubleshooting guidance, including common errors and solutions for Linux environments.
  • Expand on Linux command-line usage, such as using Bash scripts or Ansible for at-scale onboarding, not just referencing .sh scripts.
  • Ensure parity in example outputs and screenshots for both Windows and Linux onboarding processes.
  • Include references to Linux-native tools and package managers (e.g., apt, yum) where appropriate, not just PowerShell or Windows tools.
GitHub Create Pull Request
Azure Arc Connected Machine agent prerequisites .../blob/main/articles/azure-arc/servers/prerequisites.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates several Windows biases: Windows-specific examples (PowerShell) are provided for critical tasks like agent installation and resource provider registration, with Linux equivalents either missing or shown after Windows. Windows tools (e.g., Local Group Policy Editor) are described in detail, while Linux configuration steps are not covered. The onboarding script modification example is only given for Windows, and the permissions section references Windows-specific accounts and procedures. Linux users may need to infer or seek external guidance for equivalent steps.
Recommendations
  • Provide Linux-specific command examples for onboarding limited support servers, including explicit instructions for specifying agent versions.
  • Include Linux equivalents for Windows tools and configuration steps (e.g., how to check service permissions or configure systemd for the agent).
  • Present CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Add troubleshooting and configuration guidance for Linux environments, matching the detail given for Windows.
  • Ensure all critical procedures have both Windows and Linux instructions.
GitHub Create Pull Request
Azure Arc Troubleshoot SSH access to Azure Arc-enabled servers ...ain/articles/azure-arc/servers/ssh-arc-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a notable Windows bias, with troubleshooting steps and examples heavily focused on Azure PowerShell modules and commands. Windows-specific error messages and PowerShell-centric instructions are prevalent, while Linux/macOS equivalents are either missing or mentioned secondarily. The use of PowerShell modules (Az.Ssh, Az.Ssh.ArcProxy) and references to Windows error codes (WinError) further reinforce this bias. Although some Linux-related errors and paths are referenced, actionable Linux/macOS guidance is limited.
Recommendations
  • Provide equivalent Linux/macOS troubleshooting steps and examples alongside PowerShell instructions, including bash and shell commands.
  • Include installation and update instructions for Az.Ssh and Az.Ssh.ArcProxy modules on Linux/macOS (e.g., using pip, apt, or manual download).
  • Offer clear guidance for configuring PATH and environment variables on Linux/macOS, not just Windows.
  • Present CLI and shell examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Expand on Linux-specific error messages and resolutions, such as file permissions and executable flags.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Arc-enabled servers VM extension issues ...ticles/azure-arc/servers/troubleshoot-vm-extensions.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation demonstrates a moderate Windows bias. The only explicit command-line example for extension removal uses Azure PowerShell, with no Linux shell or CLI equivalent shown. In several sections, Windows file paths and procedures are listed before Linux equivalents. However, Linux troubleshooting steps and log locations are generally included, and the CLI command for extension deletion is mentioned later.
Recommendations
  • Provide Linux shell (bash) or Azure CLI examples alongside PowerShell commands, especially for extension management tasks.
  • Alternate the order of Windows and Linux instructions or present them in parallel to avoid 'Windows first' bias.
  • Explicitly mention that both PowerShell and CLI commands are cross-platform where applicable.
  • Include screenshots or examples from Linux environments in addition to Windows.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Arc-enabled servers in disconnected scenarios ...rticles/azure-arc/servers/troubleshoot-connectivity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a Windows bias by exclusively mentioning Windows-specific tools (Windows Admin Center, Configuration Manager) as local management options for disconnected servers. There are no references to equivalent Linux/macOS tools or management patterns, nor are Linux examples provided for troubleshooting or contingency actions. Windows tools are presented as the default or only option, which may leave Linux/macOS users without clear guidance.
Recommendations
  • Include Linux/macOS management options, such as Cockpit, Ansible, or native command-line tools for local server management.
  • Add troubleshooting examples and contingency steps relevant to Linux environments.
  • Present Windows and Linux/macOS options side-by-side, or clarify which instructions apply to which platforms.
  • Explicitly mention that Configuration Manager and Windows Admin Center are Windows-only, and suggest alternatives for other operating systems.
GitHub Create Pull Request
Azure Arc Support matrix for Azure Arc-enabled System Center Virtual Machine Manager ...pport-matrix-for-system-center-virtual-machine-manager.md
Medium 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 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a Windows bias by focusing primarily on Windows Server and SCVMM environments, referencing Windows tools (WinRM, Windows Management Framework), and providing detailed requirements and recommendations for Windows systems. Linux is mentioned only as an alternative for running the helper script, with a note about performance issues, and Linux-specific requirements are listed without examples or guidance. No Linux/macOS-specific deployment examples, troubleshooting, or parity guidance are provided.
Recommendations
  • Provide step-by-step Linux/macOS deployment instructions for the Resource Bridge and Arc agent installation, including troubleshooting tips.
  • Include Linux/macOS CLI examples and clarify any differences in workflow or performance.
  • List Linux/macOS equivalents for Windows tools (e.g., alternatives to WinRM, PowerShell, Windows Management Framework).
  • Address performance issues on Linux with recommendations or workarounds.
  • Ensure that all requirements and steps are equally documented for Linux/macOS environments, not just Windows.
GitHub Create Pull Request
Azure Arc Deliver ESUs for VMware VMs through Arc ...r-extended-security-updates-for-vmware-vms-through-arc.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is focused exclusively on Windows Server 2012/2012 R2 VMs and their ESU management through Azure Arc. All examples, screenshots, and instructions pertain to Windows environments, with no mention of Linux VM support, Linux patching tools, or cross-platform considerations. Windows-specific tools (WSUS, Microsoft Updates, Configuration Manager) are referenced, and Linux alternatives are absent.
Recommendations
  • Clarify early in the document that ESUs are only available for Windows Server 2012/2012 R2, if that is the case, and explicitly state that Linux VMs are not in scope.
  • If Azure Arc supports similar lifecycle management or patching for Linux VMs, provide links or references to those workflows.
  • Mention Linux-compatible patch management solutions (e.g., Azure Update Manager for Linux, third-party Linux patching tools) where patching solutions are discussed.
  • If any steps or features are applicable to Linux VMs, include parallel examples or notes.
  • Add a section on cross-platform support and limitations to help administrators managing mixed environments.
GitHub Create Pull Request
Azure Arc Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge." ...e-arc/resource-bridge/includes/network-requirements.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific services (e.g., time.windows.com, login.windows.net, sts.windows.net, servicebus.windows.net) are referenced without mentioning Linux alternatives or providing parity for Linux/macOS environments. The NTP server example is Windows-centric, and several endpoints (such as those for diagnostic data and authentication) use 'windows.net' domains, which may imply a Windows-first approach. There are no explicit Linux/Powershell command examples, but the lack of Linux-specific guidance or alternatives for time synchronization and authentication is notable. The only explicit Linux reference is for package downloads (packages.microsoft.com), but this is not balanced with the Windows focus elsewhere.
Recommendations
  • Include Linux/macOS equivalents for time synchronization (e.g., pool.ntp.org) alongside time.windows.com, and clarify which NTP server should be used for Linux-based management machines or appliance VMs.
  • Explicitly state whether endpoints like login.windows.net, sts.windows.net, and servicebus.windows.net are required for Linux/macOS environments, or if alternatives exist.
  • Add examples or notes for configuring outbound/inbound connectivity on Linux/macOS management machines, including relevant tools and commands.
  • Ensure that Linux-specific requirements (such as firewall rules, package sources, and diagnostic endpoints) are documented with equal prominence as Windows-specific ones.
  • Review all endpoint references for platform neutrality, and clarify any platform-specific requirements.
GitHub Create Pull Request
Azure Arc Choosing the right Azure Arc service for machines ...nt-docs/blob/main/articles/azure-arc/choose-service.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (SCVMM, Azure VMware Solution, Extended Security Updates for Windows Server, Microsoft Defender for Endpoint) are mentioned frequently and sometimes exclusively. PowerShell is highlighted as an automation tool, and onboarding instructions for Azure VMware Solution link to Windows-specific tabs. Linux is referenced as supported, but examples, capabilities, and recommendations often prioritize Windows scenarios or tools. There are no explicit Linux onboarding or automation examples, and Windows features (like ESUs) are given dedicated sections.
Recommendations
  • Provide Linux-specific onboarding and automation examples (e.g., Bash, shell scripts, Ansible).
  • Include Linux equivalents for Windows tools and features, or clarify parity (e.g., mention Linux security update management alongside ESUs for Windows).
  • Ensure documentation links and tabs are available for Linux (not just Windows) in onboarding guides.
  • Balance examples and recommendations between Windows and Linux, showing both platforms in tables and workflows.
  • Highlight Linux-specific capabilities or limitations where relevant, not just Windows features.
GitHub Create Pull Request
Azure Arc Deploy Active Directory integrated SQL Managed Instance enabled by Azure Arc using Azure CLI ...ta/deploy-active-directory-sql-managed-instance-cli.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation assumes the use of Active Directory (AD) for authentication, which is a Windows-centric technology. All examples and instructions are based on Azure CLI commands and AD integration, with no mention of Linux-native identity providers or alternatives to AD. There are no explicit Windows-only commands (e.g., PowerShell), but the focus on AD may create friction for Linux/macOS users who do not have access to a Windows AD environment.
Recommendations
  • Clarify that Active Directory integration is a Windows-centric requirement and mention alternatives for Linux environments if available (e.g., LDAP, Kerberos).
  • Provide guidance or references for integrating with Linux-based identity providers, if supported.
  • Explicitly state platform requirements and limitations for AD integration.
  • If possible, include examples or notes for users deploying on Linux/macOS, especially regarding prerequisites and AD connectivity.
GitHub Create Pull Request
Azure Arc Features and Capabilities of SQL Managed Instance enabled by Azure Arc ...n/articles/azure-arc/data/managed-instance-features.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows Authentication Windows First
Summary
The documentation page shows moderate Windows bias. Windows-centric tools (SSMS, SQL Server PowerShell, SQL Server Profiler) are listed prominently, and PowerShell scripting is highlighted as a manageability feature. Windows Authentication is explicitly supported, while there is no mention of Linux/macOS equivalents (e.g., Kerberos, local authentication). Linux-native tools and patterns are not discussed, and examples or guidance for Linux/macOS users are missing.
Recommendations
  • Add explicit mention and examples of Linux/macOS-compatible management tools (e.g., Azure Data Studio, Azure CLI) and clarify their parity with Windows tools.
  • Provide scripting examples using Bash, Azure CLI, or cross-platform tools alongside PowerShell.
  • Discuss authentication options for Linux environments (e.g., Kerberos, certificate-based, or Microsoft Entra ID where available).
  • Reorder tool lists to present cross-platform options (Azure Data Studio, Azure CLI) before Windows-only tools.
  • Clarify any limitations or differences for Linux/macOS users in manageability and security sections.
GitHub Create Pull Request
Azure Arc Migrate a database from SQL Server to SQL Managed Instance enabled by Azure Arc ...articles/azure-arc/data/migrate-to-managed-instance.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 providing backup examples that use Windows file paths (e.g., C:\Backupfiles\test.bak) and does not offer equivalent Linux/macOS examples (e.g., /home/user/test.bak). All file path references and copy commands use Windows conventions first, with no mention of Linux or macOS alternatives. This may cause confusion or friction for users on non-Windows platforms.
Recommendations
  • Include Linux/macOS examples alongside Windows examples for file paths and backup commands (e.g., /home/user/test.bak).
  • Explicitly mention that Azure Data Studio and Azure Storage Explorer are cross-platform, and provide installation links for Linux/macOS.
  • Show kubectl cp examples with Linux/macOS source paths (e.g., ~/Backupfiles/test.bak).
  • Add a note clarifying that all steps can be performed on Linux/macOS, and highlight any platform-specific considerations.
GitHub Create Pull Request
Azure Arc Resize persistent volume claim (PVC) for Azure Arc-enabled data services volume ...icles/azure-arc/data/resize-persistent-volume-claim.md
Medium 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 demonstrates Windows bias by providing PVC patching examples using PowerShell variable syntax (e.g., $newsize='...'), which is not directly usable on Linux/macOS shells. No Linux/macOS shell equivalents (such as bash or sh) are provided, and the PowerShell example is presented as the default approach for patching PVCs.
Recommendations
  • Include Linux/macOS shell (bash/sh) examples for patching PVCs, e.g., using single quotes and echo or cat for JSON payloads.
  • Clearly indicate which example is for Windows/PowerShell and provide a parallel example for Linux/macOS users.
  • Add a note explaining differences in shell syntax and how to adapt commands for different platforms.
  • Consider listing Linux/macOS examples first or side-by-side to avoid implicit prioritization of Windows.
GitHub Create Pull Request
Azure Arc Deploy the Edge RAG Extension ...t-docs/blob/main/articles/azure-arc/edge-rag/deploy.md
Medium 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 for deploying the Edge RAG extension shows a notable Windows bias in the Azure CLI section: all CLI examples use PowerShell syntax and variables, which are specific to Windows environments. There are no Bash or Linux/macOS shell examples, nor any mention of how to adapt the commands for those platforms. The PowerShell examples appear before any Linux alternatives (which are missing entirely), making it harder for Linux/macOS users to follow the instructions.
Recommendations
  • Provide equivalent Bash examples for all Azure CLI commands, using standard Bash variable syntax and line continuation.
  • Explicitly mention that the Azure CLI commands can be run on Linux/macOS and provide guidance for adapting PowerShell-specific syntax.
  • Add a note clarifying which examples are for Windows/PowerShell and which are for Linux/macOS/Bash.
  • Consider listing Bash examples first or side-by-side with PowerShell to avoid implicit prioritization of Windows.
GitHub Create Pull Request
Azure Arc Prepare AKS Cluster on Azure Local for Edge RAG Preview Enabled by Azure Arc ...ain/articles/azure-arc/edge-rag/prepare-aks-cluster.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples use PowerShell syntax, and Windows-specific tools and patterns (such as Restart-Service and Start-Sleep) are referenced exclusively. There are no Bash or Linux shell equivalents provided, nor are Linux/macOS management scenarios described. The instructions for setting up a driver machine only link to a Windows setup script, with no mention of Linux/macOS alternatives.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell commands, especially for GPU checks and node pool creation.
  • Include instructions and scripts for configuring a Linux/macOS driver machine to manage Azure Arc-enabled Kubernetes clusters.
  • Reference cross-platform tools and patterns where possible, or clarify OS-specific requirements.
  • Present examples for both Windows and Linux/macOS environments, or indicate which steps are OS-dependent.
GitHub Create Pull Request
Azure Arc Verify Contributor Role for Edge RAG Preview Enabled by Azure Arc ...s/azure-arc/edge-rag/prepare-contributor-permission.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides only PowerShell CLI examples for verifying contributor permissions, without mentioning or demonstrating equivalent Linux/macOS shell usage. There is no indication that the commands work cross-platform, nor are Linux-specific instructions or screenshots provided. Windows-centric terminology and examples are presented first and exclusively.
Recommendations
  • Clarify that the 'az' CLI commands work on Linux/macOS as well as Windows.
  • Provide example commands using bash/zsh syntax, or explicitly state that the commands are platform-agnostic.
  • Include screenshots or terminal output from Linux/macOS environments.
  • Mention installation instructions for the Azure CLI on Linux/macOS.
  • Avoid referring to PowerShell unless necessary, and use neutral shell syntax where possible.
GitHub Create Pull Request
Azure Arc Configure DNS for Edge RAG Preview Enabled by Azure Arc ...s/blob/main/articles/azure-arc/edge-rag/prepare-dns.md
Medium 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 provides only Windows-specific instructions for updating the hosts file (using Notepad, referencing the Windows hosts file path), with no mention of Linux or macOS equivalents. This creates friction for non-Windows users, who must infer how to perform the same task on their platforms.
Recommendations
  • Add explicit instructions for Linux and macOS users, including the hosts file path (typically /etc/hosts) and required permissions (e.g., using sudo and a text editor like nano or vim).
  • Present platform-specific instructions in parallel or in separate sections, rather than only describing the Windows workflow.
  • Mention cross-platform text editors or command-line methods for editing the hosts file.
GitHub Create Pull Request
← Previous Page 10 of 18 Next →