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 1051-1075 of 2334 flagged pages
Azure Arc Back up controller database .../articles/azure-arc/data/backup-controller-database.md
Medium Priority View Details →
Scanned: 2026-02-16 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 and references the use of sqlcmd via PowerShell, without offering equivalent Linux/macOS shell examples. The use of PowerShell for kubectl exec commands may create friction for Linux/macOS users, as Bash or other shells are more common in those environments.
Recommendations
  • Provide Linux/macOS shell (e.g., Bash) equivalents for all PowerShell examples, especially for kubectl exec and sqlcmd commands.
  • Ensure that examples are presented in a cross-platform manner, or explicitly note when a command is platform-specific.
  • Consider showing Bash examples first or alongside PowerShell to improve parity.
  • Clarify that sqlcmd and kubectl commands can be run from any shell, not just PowerShell.
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-02-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides recovery instructions exclusively for Windows, including a PowerShell script and Windows-specific steps. There are no equivalent instructions, scripts, or examples for Linux or macOS users, and the section is titled 'Recover Arc resource bridge from a Windows machine,' implying Windows is the only supported platform for recovery.
Recommendations
  • Provide equivalent recovery instructions for Linux/macOS, including Bash or Python scripts.
  • Clarify if recovery is possible from non-Windows platforms; if not, explicitly state Windows is required.
  • If the script is Windows-only, consider offering a cross-platform version or documenting manual steps for Linux users.
  • Add a section titled 'Recover Arc resource bridge from a Linux/macOS machine' if supported.
GitHub Create Pull Request
Azure Arc Perform disaster recovery operations ...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides only PowerShell examples and references the onboarding script as a PowerShell (.ps1) script, with no mention of Linux/macOS-compatible alternatives or instructions. All command-line examples are Windows-centric, and there is no guidance for users on Linux or macOS platforms. The onboarding workflow assumes the use of PowerShell and does not address cross-platform usage.
Recommendations
  • Provide Bash or shell script equivalents for onboarding and recovery steps, or clarify if the onboarding script is cross-platform.
  • Explicitly state platform requirements for the onboarding script and offer guidance for Linux/macOS users (e.g., using PowerShell Core, prerequisites, or alternative steps).
  • Add examples or notes for running the onboarding script on Linux/macOS, including any necessary modifications or dependencies.
  • Mention Azure CLI usage where possible, as it is cross-platform, and provide relevant command examples.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is focused on Linux preparation for AKS Edge Essentials, but uses Windows-centric tools (Invoke-AksEdgeNodeCommand) for Linux node configuration, and does not provide native Linux shell or SSH command alternatives. The text editor example (Notepad) is also Windows-specific, and Linux-native editors are not mentioned.
Recommendations
  • Provide native Linux shell/SSH command examples for sysctl configuration, such as using 'ssh' and 'sudo sysctl ...' directly.
  • Mention Linux text editors (e.g., nano, vim) alongside Notepad for editing configuration files.
  • Clarify if Invoke-AksEdgeNodeCommand is required even for Linux hosts, or provide Linux-native alternatives.
  • Ensure all steps can be completed from a Linux admin workstation without reliance on Windows tools.
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-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server Profiler, SQL Server PowerShell) and explicitly mentions PowerShell scripting support as a manageability feature. While Azure CLI and Visual Studio Code are included, there are no Linux-specific tools or examples, and Windows tools are referenced without Linux alternatives or parity discussion.
Recommendations
  • Add explicit mention of cross-platform tools such as Azure Data Studio, which runs on Linux/macOS.
  • Clarify which tools are Windows-only and which are cross-platform.
  • Provide examples or links for using SQL Managed Instance enabled by Azure Arc from Linux/macOS environments (e.g., using Azure CLI, sqlcmd, or Azure Data Studio).
  • Consider listing Azure CLI and Visual Studio Code before Windows-only tools to reduce Windows-first impression.
  • Note PowerShell scripting support is primarily for Windows, and suggest Bash/CLI alternatives for Linux/macOS users.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation frequently presents Windows-centric tools and paths first (e.g., SSMS, C:\ paths, Windows file copy examples) and does not provide equivalent Linux/macOS examples for key steps such as database backup and file copying. This creates friction for users on non-Windows platforms.
Recommendations
  • Provide explicit examples for Linux/macOS users, such as using sqlcmd or Azure Data Studio for backup/restore operations.
  • When showing file paths, include both Windows (C:\...) and Linux (/home/user/...) examples.
  • For file copy steps, show both Windows (C:\...) and Linux/macOS (~/ or /tmp/) source paths in kubectl cp commands.
  • Mention cross-platform tools like Azure Data Studio alongside SSMS.
  • Clarify that Visual Studio Code, Azure Storage Explorer, and kubectl are cross-platform, and provide installation links for all OSes.
GitHub Create Pull Request
Azure Arc Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc ...articles/azure-arc/data/rotate-user-tls-certificate.md
Medium Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides both Linux and Windows methods for base64 encoding files, but the Windows example is more detailed and includes additional steps (removing headers) that are not explained for Linux. The Linux example is presented first, but the Windows section is more prominent and includes links to Windows-specific tools. There is no PowerShell bias, but Windows tools (certutil, findstr) are mentioned, and the Linux equivalent for header removal is missing. All other steps use cross-platform tools (OpenSSL, Azure CLI, kubectl), and the overall workflow is platform-neutral.
Recommendations
  • Add Linux/macOS equivalent commands for removing certificate headers after base64 encoding (e.g., using grep or sed).
  • Clarify that the base64 encoding step can be performed on both Linux and Windows, and provide parity in instructions for both platforms.
  • Consider linking to documentation for Linux/macOS base64 and text processing utilities, similar to the Windows certutil link.
  • Ensure that examples for Linux/macOS are as detailed as Windows examples, especially for multi-step tasks.
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-16 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 HTTP2 issues, Windows-style paths and error messages are shown first, and Linux-specific troubleshooting steps (such as using bash or Linux CLI commands) are rarely provided. For example, the PowerShell cmdlet is given for HTTP2 troubleshooting, but no equivalent Linux curl command is shown. The GLIBC error is explained, but Linux troubleshooting is minimal compared to Windows/PowerShell. Windows terminology (RDP, PowerShell, Windows paths) appears more frequently and often before Linux equivalents.
Recommendations
  • Provide Linux/macOS equivalents for PowerShell troubleshooting commands (e.g., curl with HTTP2 for HTTP2 errors).
  • Show Linux CLI commands (such as nslookup, dig, curl) alongside Windows commands for network/DNS troubleshooting.
  • Ensure error messages and troubleshooting steps reference both Windows and Linux paths and environments.
  • Add explicit guidance for Linux users where only Windows instructions are given (e.g., for Azure CLI installation/downgrade, SSH folder permissions, proxy configuration).
  • Balance the order of examples so Linux/macOS instructions are not always secondary to Windows/PowerShell.
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-16 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 all VM extensions, ensuring parity in template content. However, all deployment commands and walkthroughs exclusively use Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell commands are presented first and only, which may create friction for Linux/macOS users who prefer Bash or Azure CLI. The documentation is not Windows-only, but the deployment workflow is PowerShell-centric.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell commands, especially for template deployments (e.g., az deployment group create).
  • Explicitly mention that Azure PowerShell can be used on Linux/macOS, but also provide Bash/CLI alternatives.
  • Consider showing CLI examples before or alongside PowerShell to avoid 'windows_first' bias.
  • Clarify in prerequisites that either PowerShell or CLI can be used, and link to installation guides for both.
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-02-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates notable Windows bias, especially in the 'Auto Arc-enablement script' section, which exclusively provides PowerShell-based automation and references Windows Task Scheduler for cron jobs. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned first and exclusively, with no equivalent Linux/macOS automation examples. While Linux is referenced in prerequisites and out-of-band methods, the main scalable automation script is Windows-centric, creating friction for Linux/macOS users.
Recommendations
  • Provide a Bash or Python version of the batch enablement script for Linux/macOS users.
  • Include examples for running the script as a cron job on Linux (using crontab) alongside Windows Task Scheduler.
  • Clarify whether the helper script can be run cross-platform, and if not, offer guidance or alternatives for Linux/macOS environments.
  • Ensure that out-of-band automation methods (e.g., Ansible) are highlighted as viable for Linux users, and provide links or examples.
  • Where PowerShell is used, note if PowerShell Core (cross-platform) is supported, and provide installation guidance for Linux/macOS.
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-02-16 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 steps and examples for Windows users, especially for running the deboarding script, with PowerShell-specific instructions and notes. There is no equivalent guidance for Linux/macOS users on how to run the deboarding script, and Windows instructions are presented first and in greater detail. While uninstall instructions for the agent are given for both Windows and Linux, the script execution section is Windows-centric.
Recommendations
  • Add explicit instructions for running the deboarding script on Linux/macOS, including shell commands and prerequisites.
  • Clarify whether the deboarding script can be run cross-platform (e.g., if it's a PowerShell script, mention PowerShell Core support and provide Linux/macOS usage examples).
  • Present Windows and Linux/macOS instructions in parallel sections or clearly indicate platform-specific steps.
  • Add notes about any limitations or requirements for Linux/macOS users (such as needing PowerShell Core or Azure CLI).
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-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently uses PowerShell syntax for all CLI examples and references PowerShell scripts (.ps1) for automation, without providing equivalent Bash or shell script examples. There is no mention of Linux/macOS-specific instructions or alternative scripting approaches, and PowerShell is presented as the default/only option for scripting and command execution.
Recommendations
  • Provide CLI command examples in Bash syntax (e.g., az ... with Bash variable usage) alongside PowerShell examples.
  • Offer equivalent shell scripts (e.g., bulk_deployment.sh) for Linux/macOS users, or clarify if the .ps1 scripts are cross-platform via PowerShell Core.
  • Explicitly state that the Azure CLI commands work on all platforms and clarify any platform-specific requirements for scripts.
  • Add notes or tabs indicating how to run these commands/scripts on Linux/macOS, including installation instructions for PowerShell Core if required.
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-16 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 provides almost exclusively PowerShell-based examples and scripts for enabling diagnostics, onboarding clusters, and managing settings. Paths in JSON templates use Windows-style backslashes and drive letters. There are no Bash, shell, or Linux/macOS CLI examples, nor guidance for running scripts on non-Windows platforms. The use of PowerShell and Windows file paths is pervasive, and Linux/macOS users are not provided with equivalent instructions or examples.
Recommendations
  • Add Bash/shell script equivalents for all PowerShell examples, especially for az CLI commands and onboarding scripts.
  • Provide Linux/macOS file path examples in JSON templates (e.g., /home/user/config.yaml) alongside Windows paths.
  • Clarify whether the onboarding scripts (infra_onboarding.ps1) can be run cross-platform, or provide alternatives for Linux/macOS users.
  • Explicitly mention OS requirements for scripts and tools, and link to cross-platform installation instructions for Azure CLI.
  • Where possible, use az CLI commands in a platform-neutral way (without PowerShell-specific syntax or variables).
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-16 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 and instructs users to run it in PowerShell, without mentioning or providing alternatives for Linux/macOS users (such as Bash or cross-platform scripting). This creates friction for non-Windows users, as PowerShell is not natively available on Linux/macOS and may require additional setup.
Recommendations
  • Provide a Bash or cross-platform script for migration, or document how to run the PowerShell script using PowerShell Core on Linux/macOS.
  • Explicitly mention PowerShell Core compatibility and provide installation instructions for Linux/macOS users.
  • Offer alternative commands or scripts if possible, or clarify if the script is Windows-only and why.
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-16 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 a PowerShell script (RGCleanScript.ps1) and only PowerShell-based usage examples, with no mention of Bash, shell, or cross-platform alternatives. There is no guidance for Linux/macOS users on how to run the script or whether it is compatible with PowerShell Core or Azure CLI, creating friction for non-Windows users.
Recommendations
  • Clarify whether RGCleanScript.ps1 is compatible with PowerShell Core (pwsh) on Linux/macOS.
  • Provide explicit instructions for running the script on Linux/macOS, including installation steps for PowerShell Core if needed.
  • Offer equivalent Bash or Azure CLI examples/scripts, or note if none exist.
  • Add a note about cross-platform support or limitations for the script.
  • If the script is Windows-only, state this clearly and suggest alternatives for Linux/macOS users if possible.
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-16 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 'winget' command is provided as the only example for installing kubectl, which is a Windows-specific tool, with no Linux/macOS installation instructions. In the section about extracting ZIP files, the Bash tab uses the Windows-native 'Expand-Archive' command (which is not available on Linux/macOS Bash), and all example paths are Windows-style (e.g., 'C:\path\to\archive.zip'). There are no Linux/macOS-specific instructions or examples for these steps, and the documentation consistently presents Windows tools and patterns first or exclusively.
Recommendations
  • Provide Linux/macOS installation instructions for kubectl, such as using 'curl' or 'apt/yum/brew'.
  • For extracting ZIP files, include Linux/macOS Bash commands (e.g., 'unzip archive.zip -d /path/to/workspace') and use POSIX-style paths.
  • Add explicit notes or tabs for Linux/macOS users throughout, especially in sections where Windows tools are referenced.
  • Ensure that all code examples are cross-platform or clearly indicate which OS they are for.
  • Consider showing Linux/macOS examples before or alongside Windows examples to avoid 'windows_first' bias.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-02-16 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 throughout the troubleshooting sections are provided only in PowerShell syntax, with no equivalent Bash or Linux shell examples. Windows-specific scripting patterns (e.g., variable assignment, ConvertTo-Json, Out-File, Base64 encoding in PowerShell) are used exclusively. Only in the 'Troubleshoot service groups' section are Bash examples provided alongside PowerShell, but the rest of the document lacks Linux parity. This creates friction for Linux/macOS users, who must translate PowerShell commands to Bash or other shells themselves.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell command examples, especially for az CLI, kubectl, and docker commands.
  • Use cross-platform scripting patterns (e.g., environment variables, file encoding, Base64 encoding) and document both PowerShell and Bash approaches.
  • Where PowerShell-specific constructs are used (e.g., ConvertTo-Json, Out-File), show how to achieve the same result in Bash (e.g., using jq, echo, cat, etc.).
  • Ensure variable assignment and usage examples are shown for both Windows (PowerShell) and Linux (Bash) environments.
  • Review the troubleshooting steps to confirm that all tasks can be completed on Linux/macOS and clarify any OS-specific requirements.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides command examples for connecting to the SQL Server instance using PowerShell syntax, specifically for running sqlcmd via kubectl exec. No equivalent Linux/macOS shell examples (e.g., Bash) are provided, and PowerShell is used as the default/only shell for these steps. This may create friction for Linux/macOS users unfamiliar with PowerShell syntax.
Recommendations
  • Add Bash shell examples alongside PowerShell for kubectl exec and sqlcmd commands.
  • Clarify that the commands can be run from any OS with kubectl and sqlcmd installed, and provide OS-agnostic instructions.
  • Ensure that all steps involving shell commands are demonstrated in both Windows (PowerShell) and Linux/macOS (Bash) contexts.
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-15 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 examples or guidance for running the script on Linux/macOS systems, nor is there mention of Bash, shell, or cross-platform alternatives. The script appears to require PowerShell, which is available on Linux/macOS, but this is not clarified or demonstrated.
Recommendations
  • Clarify that PowerShell Core (pwsh) can be used on Linux/macOS and provide example commands for those platforms.
  • Add instructions for installing PowerShell on Linux/macOS if not already present.
  • Show example usage with 'pwsh' rather than only Windows-style '.\RGCleanScript.ps1', e.g., 'pwsh RGCleanScript.ps1 ...' or './RGCleanScript.ps1 ...' for Unix shells.
  • Mention any platform-specific requirements or limitations of the script, if any.
  • If the script is truly cross-platform, explicitly state this in the documentation.
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-15 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 (WOGAMigration.ps1) for migration, with instructions to run it in PowerShell. There are no examples or guidance for Linux/macOS users, such as Bash or cross-platform alternatives, nor mention of how to execute the migration on non-Windows platforms.
Recommendations
  • Provide a Bash or shell script alternative for Linux/macOS users, or document how to run the PowerShell script using PowerShell Core on Linux/macOS.
  • Explicitly state platform requirements and, if possible, offer cross-platform migration instructions.
  • Include notes or troubleshooting for Linux/macOS users who may need to install PowerShell Core.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides CLI examples using PowerShell syntax (with backticks for line continuation and $variable notation), which is specific to Windows environments. There are no equivalent Bash or Linux/macOS shell examples, and the CLI installation/update instructions are shown in Bash only in some sections, but configuration examples are exclusively PowerShell. There is no mention of Linux-specific tools or patterns, nor any explicit guidance for Linux/macOS users. This creates friction for non-Windows users who may not be familiar with PowerShell syntax or variable usage.
Recommendations
  • Provide equivalent Bash examples for all CLI commands, especially where PowerShell syntax is used.
  • Include notes clarifying that CLI commands work on Linux/macOS and provide sample variable usage for those platforms.
  • Avoid using PowerShell-specific line continuation (backticks) and variable notation in generic CLI documentation, or show both styles side-by-side.
  • Add a section or callout for Linux/macOS users to ensure parity and clarity.
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-15 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 a notable Windows bias. All CLI/script examples are provided exclusively 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 any of the automation steps, and the onboarding scripts are referenced as PowerShell (.ps1) files. The documentation assumes a Windows environment for scripting and file management, which creates friction for Linux/macOS users who may need to adapt commands and paths.
Recommendations
  • Provide Bash/zsh shell equivalents for all PowerShell script examples, especially for az CLI commands.
  • Use cross-platform file path examples (e.g., /home/user/config.yaml) or clarify how to adapt paths for Linux/macOS.
  • Mention that onboarding scripts are available in PowerShell and provide guidance or alternative scripts for Linux/macOS users (e.g., Python, Bash).
  • Add notes or sections explicitly addressing Linux/macOS environments, including any prerequisites or limitations.
  • Ensure JSON templates reference generic or platform-neutral file paths.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is focused on configuring AKS Edge Essentials for Linux, but uses Windows-specific PowerShell cmdlets (Invoke-AksEdgeNodeCommand) to perform Linux node configuration tasks. There are no native Linux shell examples for checking or setting sysctl values, and the text editor recommendation (Notepad) is Windows-centric. This creates friction for Linux users who may not have access to PowerShell or Windows tools.
Recommendations
  • Provide native Linux shell commands for checking and setting sysctl values (e.g., 'cat /proc/sys/fs/inotify/max_user_instances' and 'echo ... | sudo tee ...').
  • Recommend Linux text editors (e.g., nano, vim) alongside Notepad for editing configuration files.
  • Clarify whether PowerShell is required on Linux, or provide alternative instructions for Linux environments.
  • Ensure all steps can be completed using standard Linux tools without reliance on Windows/PowerShell.
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-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation page lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and explicitly mentions PowerShell scripting support as a manageability feature. While Azure PowerShell is marked as unsupported, SQL Server PowerShell is listed as supported. There are no Linux-specific tools or examples, and Linux-native management approaches (such as sqlcmd, mssql-cli, or Azure Data Studio) are not mentioned. However, the core features are platform-agnostic, and the page does not provide step-by-step examples favoring Windows.
Recommendations
  • Add Linux-native tools such as Azure Data Studio, sqlcmd, and mssql-cli to the Tools section.
  • Clarify that SQL Server PowerShell is available cross-platform via PowerShell Core, or provide Linux/macOS alternatives.
  • Include references or links to documentation for managing SQL Managed Instance enabled by Azure Arc from Linux/macOS environments.
  • Balance tool recommendations to highlight cross-platform options alongside Windows tools.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides several examples and instructions that default to Windows tools, paths, and workflows (e.g., using C:\ paths, referencing Notepad/OneNote, and SQL Server Management Studio), with little or no mention of Linux/macOS equivalents. Linux users are left to infer how to adapt the instructions, especially for backup file creation and local file path usage.
Recommendations
  • Include Linux/macOS equivalents for file paths (e.g., /home/user/backup/test.bak) alongside Windows examples.
  • Mention cross-platform editors (e.g., VS Code, nano, vim) instead of or in addition to Notepad/OneNote for copying SAS tokens.
  • Explicitly state that SQL Server Management Studio (SSMS) is Windows-only and suggest Azure Data Studio or sqlcmd as cross-platform alternatives.
  • Provide example backup commands for Linux-based SQL Server installations (e.g., using /var/opt/mssql/backup/ as the backup path).
  • When referencing tools like Azure Storage Explorer or Visual Studio Code, clarify their cross-platform availability.
GitHub Create Pull Request
← Previous Page 43 of 94 Next →