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 1151-1175 of 2334 flagged pages
Azure Arc Troubleshoot Azure Arc resource bridge issues ...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances of Windows bias: PowerShell is referenced for troubleshooting network issues (e.g., Invoke-WebRequest, Resolve-DnsName), and Windows paths (e.g., C:\Program Files\...) are used in error messages. Linux-specific troubleshooting commands and examples are largely missing or appear after Windows ones. The GLIBC error is the only explicit Linux troubleshooting section, but most CLI and network troubleshooting steps default to Windows tools and terminology.
Recommendations
  • Add Linux/macOS equivalents for PowerShell commands (e.g., curl, dig, nslookup) wherever PowerShell is used for troubleshooting.
  • Provide Linux/macOS file path examples alongside Windows paths in error messages.
  • Include explicit instructions for managing Azure CLI and extensions on Linux/macOS, such as package manager commands (apt, yum, brew).
  • Ensure troubleshooting steps reference both Windows and Linux tools equally, or group them by OS.
  • Where CLI commands are shown, clarify any OS-specific prerequisites or differences (e.g., SSH folder permissions, glibc requirements).
GitHub Create Pull Request
Azure Arc Manage and maintain the Azure Connected Machine agent ...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstall, and proxy configuration. However, Windows examples and tools (such as PowerShell scripts, Group Policy, Microsoft Update, and Control Panel) are often presented first or in greater detail. The cleanup script for stale resources is only provided in PowerShell, with no equivalent Bash or CLI example for Linux users. Windows-specific tools and patterns (e.g., Msiexec, Registry Editor, Group Policy) are described in depth, while Linux instructions are more concise and rely on standard package managers.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for resource cleanup and automation tasks, not just PowerShell.
  • Where possible, present Linux and Windows instructions in parallel or with equal prominence, rather than Windows-first.
  • Expand Linux sections to include troubleshooting tips, automation examples, and references to Linux-native tools.
  • Consider adding a summary table of methods/scripts for both platforms at the start of each major section.
GitHub Create Pull Request
Azure Arc CLI reference for `azcmagent connect` ...b/main/articles/azure-arc/servers/azcmagent-connect.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides authentication options for both Windows and Linux, but there is a notable Windows bias. The 'Interactive browser login' is described as Windows-only and appears first. Windows certificate store usage is detailed, while Linux equivalents are not mentioned. The access token example references PowerShell's Get-AzAccessToken, but does not mention Linux alternatives. Overall, Linux users can complete the task, but Windows-specific tools and patterns are referenced more prominently and earlier.
Recommendations
  • Add explicit Linux/macOS guidance for certificate-based authentication, such as storing certificates in standard filesystem locations and using PEM/PFX files.
  • Provide Linux/macOS alternatives for obtaining access tokens, such as using Azure CLI (az account get-access-token) or other cross-platform tools.
  • Reorder authentication options so that cross-platform methods (device code, service principal, Azure CLI) are presented before Windows-only options.
  • Clarify that most examples and flags are applicable to both Windows and Linux, and highlight any OS-specific differences.
  • Include Linux/macOS-specific examples where relevant, such as using $(hostname) in shell scripts.
GitHub Create Pull Request
Azure Arc Enable VM Extensions Using Azure Resource Manager Template ...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides ARM template examples for both Linux and Windows Arc-enabled servers, ensuring parity in template content. However, all deployment command examples use Azure PowerShell exclusively, with no Azure CLI or Bash equivalents shown. Additionally, PowerShell commands and Windows-style file paths are presented first and throughout, which may create friction for Linux/macOS users who typically use Azure CLI or Bash. The documentation does mention Azure CLI in the 'Related content' section, but does not provide any CLI examples or guidance in the main workflow.
Recommendations
  • Add Azure CLI deployment command examples alongside PowerShell commands, especially for template deployments (e.g., az deployment group create ...).
  • Include Linux/macOS-friendly file path examples (e.g., /home/user/Azure/Templates/...) in addition to Windows-style paths.
  • Consider presenting CLI and PowerShell examples side-by-side or alternating their order to avoid Windows-first bias.
  • Explicitly state that both PowerShell and CLI can be used, and link to relevant CLI documentation in the main workflow, not just in 'Related content'.
GitHub Create Pull Request
Azure Arc Clean-Up Script for Workload Orchestration ...es/azure-arc/workload-orchestration/clean-up-script.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides instructions for running a PowerShell script (RGCleanScript.ps1) to clean up Azure Arc workload orchestration resources. All examples and guidance are PowerShell-based, with no mention of Linux/macOS-compatible alternatives, such as Bash scripts or cross-platform instructions. There is no indication that the script can be run on Linux or macOS, nor are there examples for those platforms.
Recommendations
  • Clarify whether RGCleanScript.ps1 can be executed on PowerShell Core (pwsh) on Linux/macOS, and provide explicit instructions if so.
  • If the script is Windows-only, offer a Bash or cross-platform alternative for Linux/macOS users, or note the limitation clearly.
  • Add example commands for running the script on Linux/macOS, or provide equivalent scripts in Bash.
  • Mention prerequisites for Linux/macOS users, such as installing PowerShell Core or dependencies.
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-02-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation consistently uses PowerShell syntax for all CLI examples and references PowerShell scripts (e.g., bulk_deployment.ps1, workflow-delete.ps1) as the only automation options. There are no Bash or Linux shell script equivalents provided, and the use of PowerShell syntax may confuse Linux/macOS users, even though the Azure CLI is cross-platform. The documentation does not mention or demonstrate Linux/macOS usage patterns, nor does it provide alternative scripts or instructions for non-Windows environments.
Recommendations
  • Provide CLI command examples in standard shell syntax (e.g., Bash) or clarify that the Azure CLI commands work identically on Linux/macOS and Windows.
  • Offer equivalent Bash scripts for bulk deployment and workflow deletion, or at least provide guidance for running the provided PowerShell scripts on Linux/macOS (e.g., using PowerShell Core).
  • Explicitly state that the Azure CLI commands are cross-platform and can be run from any OS.
  • If only PowerShell scripts are available, mention how Linux/macOS users can install and use PowerShell Core, or provide links to cross-platform script alternatives.
GitHub Create Pull Request
Azure Arc Diagnostics of Edge-Related Logs and Errors in Workload Orchestration .../azure-arc/workload-orchestration/diagnose-problems.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates notable Windows bias. All CLI/script examples are provided in PowerShell syntax, and references to file paths in JSON templates use Windows-style paths (e.g., C:\, E:\). There are no Bash or Linux shell equivalents for commands, nor guidance for Linux/macOS users. The onboarding scripts and instructions assume a Windows environment, making it difficult for Linux/macOS users to follow or replicate the steps without adaptation.
Recommendations
  • Provide Bash or shell script equivalents for all PowerShell commands, especially for az CLI usage.
  • Use platform-agnostic file path examples in JSON templates, or provide both Windows and Linux/macOS variants.
  • Clarify whether the onboarding scripts (e.g., infra_onboarding.ps1) are available in cross-platform formats (such as .sh or Python), or provide alternatives.
  • Explicitly mention any Windows-only requirements, and offer Linux/macOS guidance where possible.
  • Add notes or sections for Linux/macOS users, including troubleshooting or adaptation tips.
GitHub Create Pull Request
Azure Arc Prepare the Environment for Workload Orchestration ...rc/workload-orchestration/initial-setup-environment.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation shows evidence of Windows bias in several areas. The example for installing kubectl uses 'winget', a Windows-only tool, with no Linux/macOS alternative provided. The file extraction example under the Bash tab uses 'Expand-Archive', which is a PowerShell/Windows command, not a native Bash/Linux command. There are no Linux/macOS-specific instructions for extracting ZIP files or installing kubectl, and Windows paths (e.g., 'C:\path\to\archive.zip') are used in Bash examples. The PowerShell tab is present throughout, but Linux/macOS users are left to infer their own commands for certain steps.
Recommendations
  • Provide Linux/macOS-specific instructions for installing kubectl, such as using 'apt', 'yum', 'brew', or downloading from the official Kubernetes site.
  • Replace 'Expand-Archive' in Bash examples with 'unzip' or 'tar' commands, and use Linux-style paths (e.g., '/home/user/archive.zip') in Bash examples.
  • Add explicit Linux/macOS examples for file extraction and directory navigation.
  • Ensure that Bash examples use commands and paths appropriate for Linux/macOS environments.
  • Consider including a table or section that summarizes installation steps for both Windows and Linux/macOS platforms.
GitHub Create Pull Request
Azure Arc Release Notes for Workload Orchestration ...cles/azure-arc/workload-orchestration/release-notes.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides release notes for Azure Arc Workload Orchestration, which is a cross-platform service. Most CLI examples use Bash syntax, but the May 2025 release section exclusively provides PowerShell examples for CLI usage, despite the Azure CLI being cross-platform. No Linux/macOS-specific examples or shell alternatives are given in that section, and PowerShell syntax is shown first and only, which may create friction for Linux/macOS users.
Recommendations
  • For CLI examples, provide both Bash and PowerShell syntax, or use Bash as the default unless the feature is Windows-specific.
  • Add a note clarifying that Azure CLI commands work on Linux/macOS and Windows, and show examples in both environments where syntax differs.
  • Review all CLI example blocks to ensure Linux/macOS users are not excluded or confused by Windows-centric syntax.
  • Where PowerShell is used, offer equivalent Bash commands, especially for file paths and variable assignment.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The troubleshooting guidance for workload orchestration is heavily biased toward Windows/PowerShell. Most examples and commands are provided in PowerShell syntax, even for tasks that are cross-platform (e.g., Azure CLI, Docker, Kubernetes). Linux/Bash equivalents are missing for critical troubleshooting steps, except for the 'service groups' section, which includes both Bash and PowerShell tabs. This bias creates friction for Linux/macOS users, who must translate PowerShell commands to Bash or their shell of choice.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell commands, especially for Azure CLI, Docker, and Kubernetes operations.
  • Clearly indicate when a command is cross-platform and provide syntax for both PowerShell and Bash.
  • Review and update troubleshooting steps to ensure Linux/macOS users can follow along without needing to translate PowerShell-specific syntax.
  • Where PowerShell is used for string manipulation or file operations, offer Bash alternatives (e.g., using sed, awk, base64, jq).
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-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page consistently uses PowerShell syntax for all CLI examples, and references PowerShell scripts (.ps1) for automation. There are no Bash or Linux/macOS shell examples, nor are Linux-friendly scripts (e.g., .sh) provided. The CLI commands are presented in PowerShell format, which may not be directly usable on Linux/macOS terminals. This creates friction for non-Windows users, especially since bulk deployment automation is only demonstrated via a PowerShell script.
Recommendations
  • Provide CLI command examples in Bash syntax alongside PowerShell, or use generic shell syntax where possible.
  • Offer equivalent Bash (.sh) scripts for bulk deployment and workflow deletion, or document how to use the PowerShell scripts on Linux/macOS (e.g., via PowerShell Core).
  • Explicitly note that the Azure CLI commands are cross-platform and clarify any OS-specific requirements.
  • Add a section or callout for Linux/macOS users, highlighting any differences or additional steps needed.
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-02-09 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 script for migration, with instructions to run it in PowerShell. There are no examples or guidance for Linux/macOS users, nor is there mention of a Bash or cross-platform alternative. This creates friction for non-Windows users who may not have PowerShell installed or prefer native shell environments.
Recommendations
  • Provide a Bash or cross-platform script for migration, or document how to run the PowerShell script on Linux/macOS (e.g., using PowerShell Core).
  • Explicitly mention if the script is compatible with PowerShell Core on Linux/macOS, and provide installation instructions if needed.
  • Add examples for running the migration on Linux/macOS, including any prerequisites or differences.
  • Clarify if the migration is Windows-only; if not, ensure Linux/macOS parity in instructions.
GitHub Create Pull Request
Azure Arc Customer intent: As a system administrator, I want to configure a single-node Kubernetes cluster with adequate resources and storage provisions, so that I can deploy and manage applications effectively using Azure IoT Operations and Azure Container Storage. ...tainer-storage/includes/single-node-edge-essentials.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is intended for Linux preparation but uses Windows-centric Azure PowerShell cmdlets (Invoke-AksEdgeNodeCommand) for Linux node configuration, without providing native Linux shell alternatives. The text editor example references Notepad, a Windows tool, and does not mention Linux editors. There are no Linux-native command examples for sysctl configuration or file editing.
Recommendations
  • Provide native Linux shell command examples for sysctl configuration (e.g., 'sudo sysctl ...', 'echo ... | sudo tee ...').
  • Mention Linux text editors such as nano, vim, or gedit instead of or alongside Notepad.
  • Clarify whether Invoke-AksEdgeNodeCommand is required or if direct Linux shell access is possible, and provide both options if so.
  • Ensure all critical steps can be completed using Linux-native tools and commands.
GitHub Create Pull Request
Azure Arc Back up controller database .../articles/azure-arc/data/backup-controller-database.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides SQL connectivity examples using PowerShell syntax (e.g., kubectl exec ... -- /opt/mssql-tools/bin/sqlcmd ...) and labels these blocks as 'powershell', despite the commands being cross-platform. There are no explicit Linux/macOS shell examples, and the PowerShell label may mislead Linux/macOS users. The documentation does not mention Linux tools or shell patterns, and Windows-style command blocks are shown first and exclusively.
Recommendations
  • Replace 'powershell' code block labels with 'console' or 'shell' where appropriate, since the commands are cross-platform.
  • Add explicit Linux/macOS shell examples or clarify that the commands work identically on Linux/macOS terminals.
  • Mention that the sqlcmd tool is available on Linux/macOS and provide installation instructions or links for those platforms.
  • Ensure that any references to decoding base64 secrets include Linux/macOS command examples (e.g., 'echo <base64> | base64 -d').
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-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides backup and restore examples using Windows tools and file paths (e.g., SSMS, Visual Studio Code, Azure Storage Explorer, and 'C:\Backupfiles\test.bak'), but does not offer equivalent Linux/macOS examples or mention cross-platform alternatives. Windows file paths and tools are referenced first and exclusively, creating friction for Linux/macOS users.
Recommendations
  • Add Linux/macOS examples for database backup, such as using sqlcmd or Azure Data Studio.
  • Provide sample file paths for Linux/macOS (e.g., '/home/user/Backupfiles/test.bak') alongside Windows paths.
  • Mention cross-platform tools (e.g., Azure Data Studio, sqlcmd) where SSMS or Visual Studio Code are referenced.
  • Clarify that Azure Storage Explorer and Visual Studio Code are available on Linux/macOS, and provide installation links for those platforms.
  • Where commands reference Windows paths, add equivalent Linux/macOS commands and paths.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Arc resource bridge issues ...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances of Windows bias: PowerShell is referenced for troubleshooting network issues (e.g., http2 errors), Windows paths and error messages are shown first, and Linux-specific troubleshooting steps are limited. While Linux is acknowledged (e.g., glibc errors, Azure Linux OS), CLI examples and troubleshooting commands are often Windows-centric or lack explicit Linux alternatives.
Recommendations
  • Provide Linux/macOS equivalents for PowerShell troubleshooting commands (e.g., use curl or wget for http2 tests).
  • Include Linux/macOS-specific guidance for SSH folder permissions and DNS resolution (e.g., use chmod, chown, dig, nslookup).
  • Ensure CLI examples are cross-platform, and clarify any OS-specific requirements or steps.
  • Balance error message examples to include both Windows and Linux/macOS outputs.
  • Explicitly mention that Azure CLI and az arcappliance commands are cross-platform, and provide installation/downgrade instructions for Linux/macOS alongside Windows.
GitHub Create Pull Request
Azure Arc What's new with Azure Connected Machine agent ...main/articles/azure-arc/servers/agent-release-notes.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The release notes for Azure Connected Machine agent generally provide parity between Windows and Linux, with download links and feature tables for both platforms. However, Windows examples and tools (such as PowerShell and MSI installer instructions) are often mentioned first or exclusively, especially in installation and troubleshooting sections. Some improvements and bug fixes reference Windows-specific tools (e.g., PowerShell scripts, MSI installer, GUI application) without Linux equivalents or guidance. The known issues section provides detailed Windows installer instructions but lacks similar troubleshooting for Linux RPM/DEB installers.
Recommendations
  • Ensure troubleshooting and installation instructions are provided for Linux (RPM/DEB) installers, not just Windows MSI.
  • When referencing Windows tools (e.g., PowerShell, msiexec), also mention Linux equivalents (e.g., shell commands for RPM/DEB installs).
  • Present download links and feature tables with Linux and Windows side-by-side, rather than Windows first.
  • Where improvements reference Windows-specific scripts (e.g., ExtensionCleanup.ps1), clarify if Linux has an equivalent or explicitly state if not applicable.
  • Add Linux-specific troubleshooting guidance for common installer issues, similar to the Windows installer section.
GitHub Create Pull Request
Azure Arc Enable VM Extensions Using Azure Resource Manager Template ...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Linux and Windows ARM template examples for each extension, ensuring parity in template content. However, all deployment instructions and sample commands exclusively use Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell commands and Windows-style file paths are shown first and throughout, which may create friction for Linux/macOS users who prefer CLI or Bash. The documentation does mention that extensions can be deployed to Linux or Windows machines, but the tooling focus is Windows-centric.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell commands, especially for template deployments.
  • Include Bash shell command samples for Linux/macOS users.
  • Use neutral file path examples (e.g., relative paths or Linux-style paths) in addition to Windows-style paths.
  • Explicitly state that Azure CLI can be used for deployments and link to relevant CLI documentation.
  • Consider alternating the order of Linux and Windows examples or grouping them together to avoid Windows-first impression.
GitHub Create Pull Request
Azure Arc Manage and maintain the Azure Connected Machine agent ...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstallation, and proxy configuration. However, there is a mild Windows bias: Windows examples and tools (such as PowerShell scripts and Microsoft Update) are often presented first or in greater detail, and some advanced automation (like stale resource cleanup) is only shown in PowerShell. Windows-specific tools (Control Panel, Group Policy, WSUS, Configuration Manager) are discussed in depth, while Linux equivalents (such as package manager automation or scripting) are not. Linux instructions are present and clear, but less detailed in some areas.
Recommendations
  • Provide equivalent automation scripts for Linux (e.g., Bash scripts for stale resource cleanup using Azure CLI).
  • Balance the order of examples so Linux and Windows are alternated or grouped equally.
  • Expand Linux sections to include more details about package manager automation, logging, and integration with configuration management tools (e.g., Ansible, Puppet, Chef).
  • Where PowerShell is used for Azure automation, offer Azure CLI examples for Linux/macOS users.
  • Mention Linux-specific update automation tools (e.g., unattended-upgrades, cron jobs) alongside Windows Update/WSUS.
  • Clarify that all major tasks can be completed on Linux as well as Windows, and highlight any parity gaps.
GitHub Create Pull Request
Azure Arc Clean-Up Script for Workload Orchestration ...es/azure-arc/workload-orchestration/clean-up-script.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides instructions and examples for running a PowerShell script (RGCleanScript.ps1) to perform clean-up tasks. There are no examples or guidance for Linux/macOS users, such as running the script with PowerShell Core (pwsh) or alternative shell environments. The documentation implicitly assumes a Windows environment and does not mention cross-platform usage.
Recommendations
  • Add instructions for running the PowerShell script using PowerShell Core (pwsh) on Linux/macOS.
  • Explicitly state whether the script is compatible with non-Windows platforms, and note any limitations.
  • Provide example commands for Linux/macOS users, including how to invoke the script with pwsh and handle file permissions.
  • If the script is Windows-only, clarify this in the prerequisites section.
GitHub Create Pull Request
Azure Arc Diagnostics of Edge-Related Logs and Errors in Workload Orchestration .../azure-arc/workload-orchestration/diagnose-problems.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page consistently uses PowerShell scripts and Windows-style file paths in examples, with no equivalent Bash or Linux/macOS command-line instructions. Windows tools and conventions (e.g., PowerShell, backslash file paths, .ps1 scripts) are referenced exclusively or before any cross-platform alternatives. This creates friction for Linux/macOS users, who must translate examples and scripts themselves.
Recommendations
  • Provide Bash or shell script equivalents for all PowerShell examples, especially for az CLI commands and onboarding scripts.
  • Use cross-platform file path conventions (forward slashes or note both styles) in JSON and script examples.
  • Clarify that az CLI commands can be run on any OS, and show both Windows (PowerShell) and Linux/macOS (Bash) syntax where relevant.
  • Offer onboarding scripts in both PowerShell (.ps1) and Bash (.sh) formats, or note how Linux/macOS users can adapt them.
  • Avoid referencing Windows-specific file paths (e.g., C:\Users\...) in templates; provide Linux/macOS alternatives (e.g., /home/user/...).
GitHub Create Pull Request
Azure Arc Prepare the Environment for Workload Orchestration ...rc/workload-orchestration/initial-setup-environment.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias in several areas. The 'winget' command is used as the sole example for installing kubectl, which is a Windows-only tool, with no Linux/macOS installation guidance. In the 'Extract ZIP' section, the Bash tab uses the Windows-native 'Expand-Archive' command, which is not available on Linux/macOS, and all example paths are Windows-style (e.g., C:\path\to\archive.zip). Linux-native tools (like unzip or tar) are not mentioned. Throughout, Windows tools and patterns are presented first or exclusively, and Linux/macOS users must infer or research their own equivalents.
Recommendations
  • Provide Linux/macOS installation instructions for kubectl (e.g., using curl, apt, brew, or direct download).
  • In the 'Extract ZIP' section, add Linux/macOS Bash examples using 'unzip' or 'tar', and use POSIX-style paths.
  • Ensure that Bash examples are cross-platform, or clearly indicate when a command is Windows-specific.
  • Where PowerShell and Bash are shown, ensure Bash examples are not using Windows-only commands.
  • Add notes or links for Linux/macOS users where Windows-specific tools are referenced.
GitHub Create Pull Request
Azure Arc Onboarding Scripts for Workload Orchestration ...azure-arc/workload-orchestration/onboarding-scripts.md
Medium Priority View Details →
Scanned: 2026-02-09 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 is heavily oriented toward Windows and PowerShell environments. All onboarding scripts and usage examples are provided exclusively as PowerShell (.ps1) scripts, with instructions to run them in a PowerShell terminal. Prerequisites reference Windows-specific tools like 'winget' for installing dependencies, and there are no equivalent instructions or examples for Linux or macOS users (e.g., bash scripts, shell commands, or alternative installation methods). This creates significant friction for non-Windows users attempting to follow the onboarding process.
Recommendations
  • Provide equivalent onboarding scripts in bash or shell for Linux/macOS environments, or document how to run the PowerShell scripts cross-platform (e.g., using PowerShell Core).
  • Include Linux/macOS installation instructions for prerequisites (e.g., using apt, yum, brew, or direct downloads instead of 'winget').
  • Add explicit notes or sections for Linux/macOS users, clarifying any differences or additional steps required.
  • If the scripts are intended to be cross-platform via PowerShell Core, state this clearly and provide guidance for installing and using PowerShell on Linux/macOS.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The troubleshooting guidance for workload orchestration is heavily biased toward Windows/PowerShell usage. Most examples and command snippets are provided in PowerShell syntax, with only a few Bash examples appearing in the 'Troubleshoot service groups' section. Many steps, especially those involving Azure CLI, Docker, and Kubernetes, are shown exclusively in PowerShell, even though these tools are cross-platform and commonly used on Linux/macOS. There are missing Linux/Bash equivalents for critical troubleshooting steps, which creates friction for non-Windows users.
Recommendations
  • Provide Bash/Linux equivalents for all PowerShell command snippets, especially for Azure CLI, Docker, and Kubernetes commands.
  • Use cross-platform syntax (e.g., az CLI, kubectl, docker) in examples, and avoid PowerShell-specific constructs unless necessary.
  • Clearly indicate when a command is platform-specific, and offer alternatives for Linux/macOS users.
  • Review and update the troubleshooting steps to ensure Linux/macOS users can follow them without needing to translate PowerShell syntax.
  • Where PowerShell is used for scripting (e.g., variable assignment, Base64 encoding), provide Bash alternatives (e.g., export, base64 commands).
GitHub Create Pull Request
Azure Arc Enable VM Extensions Using Azure Resource Manager Template ...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides deployment instructions exclusively using Azure PowerShell commands, with no Azure CLI or Bash examples. While ARM templates for both Linux and Windows are included, the deployment workflow is PowerShell-centric, which may create friction for Linux/macOS users who prefer Azure CLI or Bash. Additionally, PowerShell examples are presented first and referenced throughout, reinforcing a Windows-first approach.
Recommendations
  • Add equivalent Azure CLI deployment examples alongside PowerShell, especially for template deployment (e.g., az deployment group create ...).
  • Explicitly mention that PowerShell commands can be run cross-platform, but highlight Azure CLI as a native option for Linux/macOS users.
  • Consider providing Bash script samples for Linux users where relevant.
  • Clarify in the prerequisites or introduction that both PowerShell and CLI are supported, and link to cross-platform installation guides.
GitHub Create Pull Request
← Previous Page 47 of 94 Next →