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 726-750 of 2334 flagged pages
Azure Arc Remove your VMware vCenter environment from Azure Arc ...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed Windows/PowerShell instructions for running the deboarding script, including execution policy changes and script invocation, but does not offer equivalent Linux/macOS guidance. The script appears to be a PowerShell script, and no Bash or cross-platform alternatives are mentioned. Windows instructions are given first and in more detail, while Linux users are left without clear steps for running the script or workarounds.
Recommendations
  • Explicitly state whether the deboarding script can be run on Linux/macOS (e.g., via PowerShell Core), and provide instructions for those platforms if supported.
  • If the script is Windows-only, mention this limitation clearly and offer alternative manual steps or a Bash version for Linux/macOS users.
  • Provide parity in example commands and troubleshooting notes for Linux/macOS users, including how to install and use PowerShell Core if needed.
  • Consider offering a cross-platform script or Azure CLI-based approach for deboarding.
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-03-06 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 using Bash or cross-platform scripting tools. The script itself is a Windows/PowerShell artifact, and the page does not mention alternatives or compatibility for non-Windows environments.
Recommendations
  • Provide information about whether RGCleanScript.ps1 can be run using PowerShell Core (pwsh) on Linux/macOS, or clarify if it is Windows-only.
  • If possible, offer a Bash or cross-platform script alternative, or document how Linux/macOS users can perform equivalent clean-up tasks.
  • Add explicit notes about script compatibility and prerequisites for non-Windows users.
  • Include example commands for Linux/macOS environments, or reference Azure CLI commands for resource deletion.
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-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently presents Azure CLI commands in PowerShell syntax (e.g., `$rg`, `$subId`, and `.ps1` scripts), and all example scripts are PowerShell (.ps1) files. There are no Bash or Linux/macOS shell examples, and the use of PowerShell variables and scripts may create friction for Linux/macOS users. The documentation does not mention Linux equivalents or provide guidance for running these commands in Bash or on non-Windows platforms.
Recommendations
  • Provide Azure CLI command examples in Bash syntax alongside PowerShell, using Bash-style variables (e.g., `$rg` vs. `RG=mygroup`).
  • Offer equivalent Bash scripts for bulk deployment and workflow deletion, or clarify that the PowerShell scripts can be run cross-platform with PowerShell Core.
  • Explicitly state that Azure CLI commands are cross-platform and provide guidance for Linux/macOS users.
  • Add notes or tabs for Linux/macOS users, showing how to adapt the commands and scripts.
  • Avoid using only PowerShell-specific syntax in documentation unless the feature is Windows-only.
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-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits Windows bias in several areas. The example for installing kubectl uses Windows-specific tooling (winget), with no Linux/macOS alternative. In the file extraction step, the Bash tab uses the Windows-native Expand-Archive command, which is not available on Linux/macOS, and no Linux-native alternative (like unzip) is provided. Throughout, Windows paths (e.g., C:\path\to\archive.zip) are used in examples, and Windows tools are mentioned first or exclusively. While Azure CLI and kubectl are cross-platform, the instructions and examples are skewed toward Windows environments, creating friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS alternatives for installing kubectl (e.g., curl, apt, brew).
  • In Bash examples, use cross-platform commands (e.g., unzip) instead of Windows-native Expand-Archive.
  • Include Linux/macOS file path examples alongside Windows paths.
  • Ensure that all steps are clearly cross-platform, or explicitly note any Windows-only steps.
  • Consider adding a dedicated section or tab for Linux/macOS users where relevant.
GitHub Create Pull Request
Azure Arc Onboarding Scripts for Workload Orchestration ...azure-arc/workload-orchestration/onboarding-scripts.md
Medium Priority View Details →
Scanned: 2026-03-06 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 focused on Windows/PowerShell usage. All onboarding scripts are provided as PowerShell (.ps1) scripts, and all command-line examples use PowerShell syntax. The prerequisites reference Windows-specific tools like 'winget'. There are no examples or instructions for running the scripts on Linux or macOS, nor are there any Bash or shell script equivalents provided. This creates friction for non-Windows users, who may not be able to follow the instructions directly.
Recommendations
  • Provide Bash or shell script equivalents for the onboarding scripts, or clarify if the scripts are cross-platform (e.g., compatible with PowerShell Core on Linux/macOS).
  • Include Linux/macOS installation instructions for prerequisites (e.g., using 'apt', 'brew', or direct download for Azure CLI and kubectl) instead of only 'winget'.
  • Add explicit guidance for Linux/macOS users on how to run the scripts (e.g., using pwsh if scripts are compatible, or provide alternative scripts).
  • If the scripts are Windows-only, clearly state this limitation at the top of the documentation.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-03-06 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 command examples, including those for Azure CLI, Kubernetes, and Docker, are presented in PowerShell syntax, with no equivalent Bash or Linux shell examples for critical troubleshooting steps. Only the 'service group' section provides both Bash and PowerShell tabs, while all other sections default to PowerShell. There are also PowerShell-specific patterns (e.g., variable assignment, ConvertTo-Json, Out-File, Base64 encoding) that are not translated for Linux/macOS users.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell examples, especially for Azure CLI, Docker, and Kubernetes commands.
  • Avoid using PowerShell-specific syntax (e.g., variable assignment with $var, ConvertTo-Json, Out-File) in generic Azure CLI or Docker commands; use cross-platform syntax where possible.
  • Where file encoding or manipulation is required, offer Linux/macOS alternatives (e.g., using 'cat', 'jq', 'iconv', or 'base64').
  • Ensure troubleshooting steps are platform-neutral unless Windows-specific functionality is required.
  • Add a note clarifying that all commands are cross-platform unless otherwise stated, and provide guidance for Linux/macOS users.
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-03-05 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 page provides nearly all CLI and scripting examples using PowerShell syntax, assumes Windows-style file paths in JSON templates, and references PowerShell scripts for orchestration tasks. There are no Bash or Linux shell equivalents, and Windows file paths (e.g., C:\, E:\) are used throughout. This creates friction for Linux/macOS users, who must adapt examples and scripts to their environments.
Recommendations
  • Provide Bash or Linux shell equivalents for all PowerShell CLI examples, especially for az commands.
  • Use cross-platform file path conventions in JSON templates (e.g., /home/user/...), or clarify how to adapt for Linux/macOS.
  • Offer sample onboarding scripts in Bash or Python, or note how Linux users can run the same orchestration steps.
  • Mention that PowerShell scripts can be run on Linux/macOS with PowerShell Core, or provide guidance for native shell usage.
  • Add notes or sections for Linux/macOS users, highlighting any differences or adaptations needed.
GitHub Create Pull Request
Azure Arc Perform disaster recovery operations ...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page for disaster recovery operations of the Azure Arc resource bridge VM provides only PowerShell examples and instructions, with no mention of Bash, Linux, or macOS equivalents. The onboarding script is referenced and shown as a PowerShell script (.ps1), and all command-line instructions are given in PowerShell syntax. There is no guidance for Linux or macOS users, nor any indication of cross-platform compatibility for the onboarding script.
Recommendations
  • Clarify whether the onboarding script can be run on Linux/macOS, or if it is strictly Windows/PowerShell-only.
  • If the onboarding script is cross-platform, provide Bash or shell examples and instructions for Linux/macOS users.
  • If the onboarding script is Windows-only, explicitly state this limitation early in the documentation.
  • Mention any prerequisites for Linux/macOS users, such as needing PowerShell Core or alternative tools.
  • Consider providing a table or section comparing Windows and Linux/macOS steps, or linking to Linux-specific guidance if available.
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-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally Linux-focused, but it uses Windows-centric Azure PowerShell cmdlets (Invoke-AksEdgeNodeCommand) for Linux node configuration, without providing native Linux shell alternatives. There is an assumption that the user is running commands from a Windows environment, even when targeting Linux nodes. No Linux-native commands (e.g., SSH, direct sysctl usage) are shown for critical configuration steps.
Recommendations
  • Provide native Linux shell commands for sysctl configuration, such as 'ssh user@linux-node sudo sysctl ...' or direct shell access.
  • Clarify whether Invoke-AksEdgeNodeCommand is required, or if Linux users can perform these steps directly on the node.
  • Add examples using Linux tools and patterns (e.g., nano/vim for editing files, direct bash commands) alongside PowerShell/Windows-centric examples.
  • Explicitly state if the workflow assumes a Windows management workstation, and offer Linux/macOS alternatives if possible.
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-03-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides examples and instructions that are primarily Windows-centric, such as using Windows file paths (C:\Backupfiles\test.bak), referencing Windows tools (SQL Server Management Studio, Notepad/OneNote), and omitting explicit Linux/macOS equivalents for backup and file copy operations. Linux/macOS users are left to infer how to adapt steps for their platforms, creating friction.
Recommendations
  • Include Linux/macOS file path examples (e.g., /home/user/backup/test.bak) alongside Windows paths.
  • Mention cross-platform alternatives to Notepad/OneNote (e.g., gedit, nano, TextEdit) when suggesting where to save credentials.
  • Clarify that SQL Server Management Studio (SSMS) is Windows-only and suggest Azure Data Studio or command-line tools (sqlcmd) for Linux/macOS users.
  • Provide explicit instructions or examples for backing up databases on Linux/macOS SQL Server instances.
  • Show kubectl cp examples using Linux/macOS source paths.
  • Add notes or sections highlighting any platform-specific differences or prerequisites.
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-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows Authentication
Summary
The documentation references several Windows-centric tools and features, such as PowerShell scripting support, SQL Server Management Studio (SSMS), SQL Server Data Tools (SSDT), and Windows Authentication. PowerShell scripting is listed as a manageability feature, and Windows Authentication is included as a security feature. While Azure PowerShell is marked as 'No' in the tools table, SQL Server PowerShell is marked as 'Yes'. The documentation does not provide Linux/macOS-specific examples or mention cross-platform alternatives (e.g., Bash scripting, Linux authentication mechanisms, or Linux-native SQL tools). However, the overall impact is moderate, as most features are platform-agnostic and Azure Arc SQL Managed Instance is intended to be cross-platform.
Recommendations
  • Add examples or references for Linux/macOS users, such as Bash scripting or cross-platform CLI usage.
  • Mention cross-platform tools like Azure Data Studio, which runs on Windows, Linux, and macOS.
  • Clarify the limitations of Windows Authentication for non-Windows environments and suggest alternatives (e.g., Microsoft Entra authentication, SQL authentication).
  • Highlight Linux-native management patterns or tools where applicable.
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-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux release notes and download links, but consistently lists Windows first in download links and tables. Known issues and troubleshooting steps are exclusively for Windows, with only Windows/PowerShell/Command Prompt commands provided. Some improvements and bug fixes are described only for Windows tools (e.g., MSI installer, PowerShell scripts), with no Linux equivalents or troubleshooting guidance. Linux-specific issues are less detailed, and Linux users may need to consult external links for installation or troubleshooting.
Recommendations
  • Alternate the order of Windows and Linux in download links and tables, or present them side-by-side to avoid implicit prioritization.
  • For troubleshooting and known issues, provide Linux equivalents or explicitly state if the issue is Windows-only. If Linux users may encounter similar issues, include Linux commands (e.g., chmod/chown for file permissions) where appropriate.
  • When referencing Windows tools (e.g., PowerShell, MSI), add Linux equivalents (e.g., shell scripts, RPM/DEB package management) or clarify if a feature/fix is Windows-only.
  • Ensure Linux-specific known issues and troubleshooting steps are as detailed as Windows ones, or state explicitly if there are none.
  • Consider a dedicated section for Linux troubleshooting if parity is not possible in-line.
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-03-05 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 is evidence of Windows bias: PowerShell is referenced for troubleshooting HTTP/2 issues, and Windows-specific tools (e.g., Remote PowerShell, RDP) are mentioned. Linux-specific troubleshooting commands are largely absent, and Windows terminology (e.g., 'management machine', 'console session', 'RDP') is used preferentially. Examples for checking DNS resolution and connectivity are often given using Windows tools (PowerShell, ping, nslookup) with Linux equivalents missing or mentioned second. The GLIBC error is the only section directly referencing Linux, but overall, Linux/macOS users may face friction due to lack of parity in examples and troubleshooting steps.
Recommendations
  • Add Linux/macOS equivalents for all troubleshooting commands (e.g., curl, wget, dig, ping, ssh) alongside Windows/PowerShell examples.
  • When referencing PowerShell, also provide Bash or shell script alternatives for Linux/macOS users.
  • Clarify that 'management machine' can be Windows, Linux, or macOS, and provide guidance for each platform.
  • Include troubleshooting steps for Linux-specific issues (e.g., file permissions, SSH folder access) and reference common Linux distributions.
  • Ensure that CLI commands and environment variable configuration examples (e.g., HTTPS_PROXY, NO_PROXY) are shown for both Windows and Linux/macOS shells.
GitHub Create Pull Request
Azure Arc Simplify Network Configuration Requirements with Azure Arc Gateway ...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation generally provides both Azure CLI and PowerShell examples for resource creation and management, but PowerShell (a Windows-centric tool) is consistently presented as a primary option. In several sections, PowerShell commands are shown alongside CLI, but there is no explicit mention of Bash or Linux shell usage for the CLI commands, nor are there Linux-specific command-line nuances or troubleshooting tips. The 'Monitor Azure Arc gateway traffic' section does provide both Windows and Linux log file locations, but overall, the documentation assumes familiarity with Windows tools and sometimes omits Linux-first perspectives.
Recommendations
  • Explicitly state that Azure CLI commands can be run on Linux/macOS and provide Bash-style command examples where appropriate.
  • Add Linux/macOS-specific notes or troubleshooting steps where differences exist (e.g., file paths, permissions, environment variables).
  • When listing command-line options, consider showing Bash (Linux/macOS) syntax first or equally alongside PowerShell.
  • Clarify that PowerShell is not required for Linux/macOS users and that all operations can be performed with Azure CLI.
  • In sections referencing Windows tools or paths, always provide the Linux/macOS equivalent immediately after or in parallel.
GitHub Create Pull Request
Azure Arc Azure Connected Machine Agent Deployment Options .../main/articles/azure-arc/servers/deployment-options.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides deployment options for both Linux and Windows, but several onboarding methods are Windows-specific or use Windows-centric tools (e.g., PowerShell, Windows Admin Center, Configuration Manager, Group Policy). PowerShell is mentioned as a cross-platform option, but Windows-specific methods are listed separately and in greater detail. Linux-specific automation tools (like Bash scripts or cloud-init) are not highlighted, and PowerShell is presented as a primary automation method, which may create friction for Linux users.
Recommendations
  • Add Linux-specific onboarding examples using Bash scripts, shell commands, or cloud-init, especially for at-scale deployments.
  • Clarify which PowerShell methods are cross-platform and provide equivalent Linux command-line examples where possible.
  • Highlight Ansible and other Linux-native automation tools earlier in the onboarding methods table to improve parity.
  • Consider adding a section or links for Linux/macOS users outlining recommended tools and workflows for onboarding.
  • Ensure that Linux and Windows onboarding options are presented with equal prominence and detail.
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-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux instructions for all major lifecycle tasks (install, upgrade, uninstall, proxy config), using clear tabbed sections. However, Windows examples and tools (PowerShell, Group Policy, Microsoft Update, Control Panel, Msiexec) are often described first and in greater detail, with more step-by-step guidance and scripting. The cleanup script for stale resources is only provided in PowerShell, with no Linux shell equivalent. Windows-specific tools and patterns (e.g., Group Policy, Control Panel, Msiexec, Windows Update) are mentioned exclusively, while Linux instructions rely on standard package managers but lack advanced scripting or automation examples.
Recommendations
  • Provide Linux shell (bash) equivalents for the PowerShell cleanup script, using Azure CLI or azcmagent.
  • Ensure scripting and automation examples are available for Linux, not just Windows/PowerShell.
  • Where possible, present Windows and Linux instructions in parallel, rather than Windows-first.
  • Add more detail to Linux instructions, such as troubleshooting, automation, and advanced usage.
  • Mention Linux-native tools for update automation (e.g., cron, unattended-upgrades) where relevant.
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-03-05 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 VM extension, ensuring parity in template usage. However, all deployment commands and walkthroughs exclusively use Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell commands and Windows-style file paths are shown first and exclusively in deployment sections, which may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell commands, especially for template deployment.
  • Mention that Azure CLI can be used on Linux/macOS and provide equivalent CLI syntax.
  • Use platform-neutral file paths (e.g., './Templates/AzureMonitorAgent.json') or clarify path conventions for different OSes.
  • Explicitly state that PowerShell is cross-platform, but highlight CLI as a native option for Linux/macOS users.
GitHub Create Pull Request
Azure Arc How to migrate from legacy Log Analytics agents in non-Azure environments with Azure Arc ...in/articles/azure-arc/servers/migrate-legacy-agents.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux context, but Windows-specific tools (Windows Admin Center, Windows Server Graphical Installer) and PowerShell are mentioned first or exclusively in several deployment sections. Linux equivalents (e.g., Bash, Ansible) are referenced, but Windows approaches are prioritized or described in more detail. Some deployment options and standalone agent installation guidance are Windows-centric.
Recommendations
  • Ensure Linux deployment examples (e.g., Bash scripts, Ansible) are given equal prominence and detail alongside Windows/PowerShell examples.
  • Add explicit instructions or links for Linux graphical installers or management tools, if available.
  • When listing deployment methods, alternate the order or group by OS rather than listing Windows tools first.
  • Provide standalone Azure Monitor Agent installation guidance for Linux client machines, if supported, or clarify OS limitations.
GitHub Create Pull Request
Azure Arc Run command on Azure Arc-enabled servers (preview) ...cs/blob/main/articles/azure-arc/servers/run-command.md
Medium Priority View Details →
Scanned: 2026-03-05 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 provides extensive PowerShell-based examples and references to Windows-specific tools (e.g., New-NetFirewallRule, .ps1 scripts, New-AzStorageBlobSASToken), with Windows scenarios and terminology often appearing first or exclusively. Linux-specific examples and guidance are minimal or missing, especially in REST API and PowerShell sections, making it harder for Linux users to follow or adapt the instructions.
Recommendations
  • Add Linux-specific script examples (e.g., using bash or shell scripts) alongside PowerShell examples in all sections.
  • In REST API examples, include a Linux scenario (e.g., configuring iptables or ufw) and reference .sh scripts.
  • Balance PowerShell and Azure CLI coverage, ensuring both Windows and Linux use cases are equally represented.
  • When referencing tools like New-AzStorageBlobSASToken, clarify alternatives for Linux users (e.g., Azure CLI commands).
  • Where possible, avoid defaulting to Windows terminology or examples; alternate order or provide parallel examples.
GitHub Create Pull Request
Azure Arc Recover from accidental deletion of resource bridge VM ...em-center-virtual-machine-manager/disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides recovery instructions and a downloadable script exclusively for Windows environments, using PowerShell syntax and terminology. There are no examples or guidance for performing the recovery from Linux or macOS systems, nor is there mention of cross-platform alternatives.
Recommendations
  • Provide equivalent recovery instructions and scripts for Linux/macOS environments, using Bash or cross-platform tools where possible.
  • Clearly indicate if the recovery process is only supported from Windows, and explain why (e.g., dependencies on Windows-only tools or APIs).
  • If feasible, offer a platform-agnostic version of the recovery script (e.g., written in Python or using Azure CLI) to support non-Windows users.
  • Add a section or note addressing Linux/macOS users, even if only to clarify current limitations or provide workarounds.
GitHub Create Pull Request
Azure Arc Install Arc agent at scale for your VMware VMs ...arc/vmware-vsphere/enable-guest-management-at-scale.md
Medium Priority View Details →
Scanned: 2026-03-05 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 demonstrates a notable Windows bias, especially in the 'Auto Arc-enablement script' section, where only PowerShell scripts and Windows Task Scheduler are referenced for automation, with no equivalent Linux shell or cron job examples. The instructions for running the helper script assume a Windows environment (e.g., PowerShell, Set-ExecutionPolicy), and there is no guidance for Linux/macOS users on how to automate at scale. Out-of-band methods mention Ansible, but the primary at-scale automation path is Windows-centric.
Recommendations
  • Provide equivalent Bash/shell script examples for Linux/macOS environments, including instructions for running the helper script on those platforms.
  • Include examples for scheduling the script with Linux cron, not just Windows Task Scheduler.
  • Clarify whether the helper script is cross-platform (PowerShell Core or Bash), and if not, provide a Linux-compatible version.
  • In sections where PowerShell is used, add parallel Linux/macOS command examples or explicitly state if only Windows is supported.
  • Ensure that links to automation methods (e.g., Ansible) are surfaced as equally viable, not just as out-of-band alternatives.
GitHub Create Pull Request
Azure Arc Remove your VMware vCenter environment from Azure Arc ...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed Windows/PowerShell instructions for running the deboarding script, including execution policy steps and script invocation. There are no equivalent instructions or examples for running the script on Linux/macOS, nor is it clarified whether the script is cross-platform. Windows instructions are presented first and in greater detail, while Linux users are left without guidance for script execution.
Recommendations
  • Clarify whether the deboarding script can be run on Linux/macOS (e.g., with PowerShell Core or Azure CLI).
  • Provide explicit instructions for running the script on Linux/macOS, including prerequisites and command examples.
  • Mention any platform-specific limitations or requirements for the script.
  • Present Windows and Linux/macOS instructions in parallel or note platform differences clearly.
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-03-05 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 clean up Azure Arc workload orchestration resources. There are no Bash, shell, or Linux/macOS command examples, nor any mention of how to run the script or achieve equivalent functionality on non-Windows platforms. The script is distributed only as a .ps1 file, which is a Windows/PowerShell format.
Recommendations
  • Provide instructions for running the PowerShell script on Linux/macOS using PowerShell Core (pwsh), including example commands.
  • Offer a Bash or shell script alternative for Linux/macOS users, or clarify if PowerShell Core is required and how to install it.
  • Explicitly state platform requirements and compatibility for the script.
  • Add a section addressing Linux/macOS users, including troubleshooting or prerequisites for using PowerShell scripts on those platforms.
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-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits Windows bias in several ways: Windows tools (winget) are used for kubectl installation without Linux/macOS alternatives; archive extraction instructions use Expand-Archive (a Windows/PowerShell cmdlet) in both Bash and PowerShell tabs, with no Linux/macOS equivalent (e.g., unzip); Bash examples frequently use Windows-style file paths (C:\path\to\...), and Windows tools are mentioned before Linux-native ones. These patterns create friction for Linux/macOS users, especially in initial setup steps.
Recommendations
  • Provide Linux/macOS installation instructions for kubectl (e.g., using curl or package managers like apt, brew, or yum).
  • Replace or supplement Expand-Archive with unzip or tar commands for Bash/Linux/macOS users.
  • Use platform-appropriate file path examples in Bash sections (e.g., /home/user/archive.zip for Linux/macOS).
  • Explicitly mention cross-platform alternatives and clarify which commands are Windows-only.
  • Ensure Bash examples are truly Bash/Linux/macOS compatible, not just PowerShell syntax reused.
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-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation consistently uses PowerShell syntax for all CLI examples (e.g., variable references like $rg, $subId, and .ps1 scripts), and provides only PowerShell scripts for automation (bulk_deployment.ps1, workflow-delete.ps1). There are no Bash/Linux shell equivalents or instructions for Linux/macOS users, and no mention of how to run the provided scripts or commands on non-Windows platforms.
Recommendations
  • Provide all Azure CLI command examples in both PowerShell and Bash syntax, or use cross-platform syntax (e.g., az CLI commands with Bash-style variable references).
  • Offer Bash shell script equivalents for automation tasks currently only available as .ps1 PowerShell scripts, or clarify if the .ps1 scripts are cross-platform (e.g., via PowerShell Core).
  • Explicitly state whether the provided PowerShell scripts can be run on Linux/macOS using PowerShell Core, and provide installation instructions if so.
  • Add notes or tabs for Linux/macOS users where relevant, especially for automation and scripting sections.
  • Avoid using Windows-specific variable syntax (e.g., $var) in generic CLI examples, or provide both Windows and Linux/macOS variants.
GitHub Create Pull Request
← Previous Page 30 of 94 Next →