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 1126-1150 of 2334 flagged pages
Azure Arc Migrate Existing Target Resources to General Availability ...s/azure-arc/workload-orchestration/migration-script.md
Medium Priority View Details →
Scanned: 2026-02-13 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) and instructs users to run it in PowerShell, with no mention of Bash, Linux shell, or cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and the migration script appears to be Windows-centric.
Recommendations
  • Provide a Bash or shell script equivalent for Linux/macOS users, or clarify if the PowerShell script can be run cross-platform (e.g., with PowerShell Core on Linux/macOS).
  • Add explicit instructions for Linux/macOS users, including how to install PowerShell Core if required.
  • Mention any prerequisites for running the script on non-Windows platforms, or state if Windows is required.
  • If the migration process is Windows-only, clarify this up front to set user expectations.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The troubleshooting guidance heavily favors PowerShell syntax and Windows command patterns throughout most sections, especially in the 'Troubleshoot staging' and registry/token troubleshooting. Linux/Bash equivalents are missing for many critical steps, and PowerShell is used even for commands that could be cross-platform. Bash examples are only provided in the 'Troubleshoot service groups' section, and are presented after the PowerShell-heavy sections. This creates friction for Linux/macOS users, who may not have PowerShell installed or prefer Bash.
Recommendations
  • Provide Bash equivalents for all PowerShell commands, especially for Azure CLI and Docker/Kubectl operations.
  • Use cross-platform syntax for Azure CLI commands (e.g., avoid PowerShell-specific variable assignment and piping where possible).
  • Clearly indicate which steps require PowerShell and which can be performed in Bash or other shells.
  • Add notes or tabs for Linux/macOS users where file encoding or text manipulation is required.
  • Review all troubleshooting steps to ensure Linux parity, especially for edge device and registry management.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Windows and Linux instructions for uninstalling the Arc agent, but the deboarding script section is heavily Windows/PowerShell-centric. Only Windows/PowerShell instructions are given for running the deboarding script, with no mention of how to run it on Linux or macOS. Additionally, Windows instructions are presented first and in greater detail.
Recommendations
  • Provide explicit instructions for running the deboarding script on Linux/macOS, including prerequisites (e.g., PowerShell Core, Azure CLI) and any OS-specific considerations.
  • Clarify whether the deboarding script is cross-platform or Windows-only. If it is cross-platform, include sample commands for Linux/macOS users.
  • If the script is Windows-only, state this clearly and offer alternative manual steps for Linux/macOS users.
  • Consider presenting Windows and Linux instructions in parallel sections or tables for parity and clarity.
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-12 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 pod using PowerShell syntax (e.g., `kubectl exec ...` with PowerShell prompt and formatting), and does not offer equivalent Linux/macOS shell examples. The use of PowerShell formatting and prompts may create friction for Linux/macOS users, even though the underlying commands are cross-platform. Additionally, PowerShell examples are presented first and exclusively, suggesting a Windows-first bias.
Recommendations
  • Provide Linux/macOS shell (bash) examples alongside PowerShell examples for commands such as `kubectl exec` and SQL queries.
  • Use generic shell prompts (e.g., `$`) instead of PowerShell-specific prompts (e.g., `PS C:\>`), or clarify that the commands work in any shell.
  • Explicitly state that the commands are cross-platform and can be run from any OS with kubectl and sqlcmd installed.
  • Add notes or sections for Linux/macOS users, including any OS-specific considerations for decoding secrets or connecting to the pod.
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-12 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 configuring AKS Edge Essentials on Linux, but it uses Windows-centric tools (Invoke-AksEdgeNodeCommand) and PowerShell-style commands for Linux node configuration. There are no native Linux shell (bash/ssh) examples for critical sysctl configuration steps, which may confuse or hinder Linux users.
Recommendations
  • Provide native Linux command-line examples (e.g., using ssh, bash, or direct sysctl commands) for configuring Linux nodes.
  • Clarify when Windows tools (like Invoke-AksEdgeNodeCommand) are required, and offer Linux alternatives or explain their availability on Linux.
  • Ensure all steps can be completed using standard Linux administration tools, not just Windows/PowerShell-based tools.
  • Show both Windows and Linux command examples side-by-side where cross-platform support is intended.
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-12 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 assume a Windows environment, such as backup paths using Windows-style (C:\Backupfiles\...), and references to Windows tools like SQL Server Management Studio (SSMS) and Notepad. There are no explicit Linux/macOS equivalents or examples for backup file creation, file paths, or alternative tools, which may create friction for users on non-Windows platforms.
Recommendations
  • Include Linux/macOS examples for backup file creation, such as using '/home/user/backup/test.bak' or '/tmp/test.bak' as file paths.
  • Mention cross-platform alternatives to SSMS, such as Azure Data Studio, and provide instructions for using these tools on Linux/macOS.
  • When referencing text editors (e.g., Notepad), suggest platform-agnostic options like VS Code, nano, or TextEdit.
  • Clarify that the backup and restore SQL commands work identically on Linux-based SQL Server installations, and provide sample commands with Linux file paths.
  • Add notes or sections highlighting any platform-specific considerations for Linux/macOS users.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows Authentication
Summary
The documentation references Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and features (Windows Authentication, PowerShell scripting support) without providing Linux/macOS alternatives or clarifying cross-platform support. PowerShell scripting is highlighted as a manageability feature, but Azure PowerShell is marked as 'No' in the tools table, which may confuse Linux users. Windows Authentication is listed as supported, but Microsoft Entra authentication (cross-platform) is not. There are no explicit Linux/macOS examples or guidance.
Recommendations
  • Clarify which tools are cross-platform (e.g., Azure CLI, VS Code extension) and which are Windows-only.
  • Add Linux/macOS alternatives for manageability and scripting (e.g., Bash, sqlcmd, Azure CLI).
  • Explicitly state platform support for authentication methods (e.g., Entra ID, Windows Authentication).
  • Provide guidance or links for Linux/macOS users to manage SQL Managed Instance enabled by Azure Arc.
  • Mention limitations or workarounds for Linux/macOS users where Windows-only tools/features are referenced.
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-12 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 commands and walkthroughs exclusively use Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell is presented as the primary (and only) deployment method, which may create friction for Linux/macOS users who prefer CLI or Bash. Windows-style file paths are used in examples, and PowerShell is referenced before any mention of CLI alternatives (which are only linked in 'Related content').
Recommendations
  • Add Azure CLI deployment command examples alongside PowerShell for template deployment (e.g., az deployment group create ...).
  • Include Bash or shell script snippets for Linux/macOS users where relevant.
  • Use platform-neutral file path examples (e.g., ./AzureMonitorAgent.json) or show both Windows and Linux path styles.
  • Explicitly mention that both PowerShell and CLI can be used, and link to CLI instructions earlier in the article.
  • Consider a section or callout for Linux/macOS users explaining how to install and use Azure PowerShell or CLI.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only a PowerShell script for migration and instructs users to run it in PowerShell, with no mention of Bash, Linux shell alternatives, or cross-platform scripting. This creates friction for Linux/macOS users, as PowerShell is not natively available and may require additional setup.
Recommendations
  • Provide a Bash or shell script alternative for Linux/macOS users.
  • Document how to run the PowerShell script on Linux/macOS (e.g., using PowerShell Core).
  • Clarify whether the script is cross-platform and, if so, provide explicit instructions for Linux/macOS environments.
  • Mention any prerequisites for running PowerShell on non-Windows systems.
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-12 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 issues, which is a cross-platform feature. However, there are several instances of Windows bias: Windows/PowerShell examples are given for network troubleshooting (e.g., Invoke-WebRequest), Windows paths are referenced in error messages, and Windows tools (RDP, PowerShell) are mentioned for remote access. Linux equivalents (such as curl, SSH, or Linux CLI commands) are not provided, and in some cases, Windows-specific troubleshooting steps are listed before or instead of Linux alternatives.
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell and Windows command examples (e.g., use curl or wget for HTTP troubleshooting, SSH for remote access).
  • Include Linux/macOS-specific troubleshooting steps where relevant (e.g., file permissions, SSH folder access).
  • Mention Linux/macOS tools and patterns alongside Windows tools, not after or instead of them.
  • Ensure error messages and paths reference both Windows and Linux conventions where applicable.
  • Add explicit guidance for Linux users in sections about Azure CLI installation, proxy configuration, and network troubleshooting.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides recovery instructions and a downloadable script exclusively for Windows, using PowerShell. There are no Linux/macOS examples, nor is there mention of equivalent recovery steps or scripts for non-Windows platforms. The section is explicitly titled 'Recover Arc resource bridge from a Windows machine', and no alternative is offered.
Recommendations
  • Provide equivalent recovery instructions for Linux/macOS, including a Bash or Python script if possible.
  • Clarify whether the recovery process can be performed from non-Windows machines, or explicitly state if Windows is required.
  • If the script is Windows-only, explain why and offer guidance for Linux users (e.g., using a Windows VM or container).
  • Add a section titled 'Recover Arc resource bridge from a Linux/macOS machine' if feasible.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page provides multiple methods for installing Arc agents at scale for VMware VMs, but exhibits notable Windows bias. The primary automation script is PowerShell-based, with instructions to use Windows Task Scheduler for cron jobs, and references to Windows tools and patterns (e.g., Group Policy, Configuration Manager). Linux-specific guidance is minimal and secondary, with only a brief mention of Ansible playbooks and a sudo configuration note for Linux VMs. Windows examples and tools are presented first and in greater detail, while Linux equivalents are not equally covered.
Recommendations
  • Provide a Bash or Python-based automation script for Linux/macOS users, with equivalent functionality to the PowerShell script.
  • Include examples for scheduling automation on Linux (e.g., using cron) alongside Windows Task Scheduler instructions.
  • Expand documentation for Linux tools and patterns (e.g., using Ansible, shell scripts) for Arc agent installation at scale.
  • Ensure parity in example commands and step-by-step instructions for both Windows and Linux environments.
  • Mention cross-platform Azure CLI usage explicitly and provide sample commands for both OS types.
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-12 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 Azure CLI commands, 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 examples, and the PowerShell syntax is used even though Azure CLI is cross-platform. This creates friction for Linux/macOS users, who may not be familiar with PowerShell or .ps1 scripts.
Recommendations
  • Provide Azure CLI command examples in Bash syntax (e.g., using $ variables and shell quoting) alongside PowerShell examples.
  • Offer equivalent Bash shell scripts for bulk deployment and workflow deletion, or note how to run the PowerShell scripts on Linux/macOS (e.g., via pwsh).
  • Clarify that Azure CLI commands can be run on any platform, and avoid using PowerShell-specific syntax unless the task is Windows-only.
  • Add notes or tabs for Linux/macOS users, highlighting any platform-specific considerations.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page provides only PowerShell examples and instructions for running and editing the onboarding script, with no mention of Bash, shell, or cross-platform alternatives. The script usage and editing steps are presented in a Windows-centric manner, assuming the user is on Windows or using PowerShell. There is no guidance for Linux/macOS users, and PowerShell is shown as the default/only option.
Recommendations
  • Provide Bash or shell script equivalents for onboarding and recovery operations, or clarify if the onboarding script is cross-platform.
  • Explicitly state platform requirements for the onboarding script (e.g., if PowerShell Core is supported on Linux/macOS).
  • Add instructions for running the onboarding script on Linux/macOS, including any prerequisites or installation steps.
  • Mention any limitations or required adaptations for non-Windows environments.
  • If the onboarding script is Windows-only, clearly indicate this limitation at the start of the article.
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-12 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 shows PowerShell commands for resource clean-up. There are no Bash, shell, or cross-platform script examples, nor any mention of how Linux or macOS users can perform the same clean-up tasks. The script and instructions are Windows-centric, which may hinder non-Windows users.
Recommendations
  • Provide a Bash or shell script equivalent (e.g., RGCleanScript.sh) for Linux/macOS users, or document how to run the PowerShell script using PowerShell Core (pwsh) on non-Windows platforms.
  • Include explicit instructions or examples for running the script on Linux/macOS (e.g., using pwsh, or adapting the script for Bash).
  • Mention any prerequisites for non-Windows users, such as installing PowerShell Core, and provide installation links.
  • If the script is truly Windows-only, clearly state this limitation and suggest alternative manual clean-up steps 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-02-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides extensive PowerShell examples and scripts for diagnostics and log collection, with no equivalent Bash or Linux shell examples. Paths in JSON templates and scripts use Windows-style (e.g., C:\, E:\), and PowerShell is the only scripting language shown for orchestration tasks. There is no mention of Linux/macOS alternatives, and Windows tools/patterns (PowerShell, Windows file paths) are referenced exclusively and before any Linux equivalents.
Recommendations
  • Provide Bash or Linux shell equivalents for all PowerShell commands and scripts, especially for az CLI usage.
  • Use cross-platform file path examples in JSON templates (e.g., /home/user/config.yaml) or clarify how to adapt for Linux/macOS.
  • Explicitly state if PowerShell scripts are required, or offer alternatives using Bash or Python for Linux/macOS users.
  • Add notes or sections for Linux/macOS users, highlighting any differences or requirements.
  • Ensure that az CLI commands are shown in a cross-platform way (without PowerShell-specific syntax like backticks or variables).
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits Windows bias in several areas. The example for installing kubectl uses Windows-only tooling (winget), with no Linux/macOS alternative. The file extraction example under the Bash tab incorrectly uses PowerShell's Expand-Archive, which is not available on Linux/macOS Bash shells. Throughout, Windows-centric tools and patterns are presented first or exclusively, and Linux/macOS users are left to infer their own equivalents.
Recommendations
  • Provide Linux/macOS alternatives for installing kubectl (e.g., using curl or package managers like apt, brew, or snap).
  • Correct the Bash example for extracting ZIP files to use native Bash/Linux commands (e.g., unzip, tar) instead of PowerShell's Expand-Archive.
  • Ensure that examples under Bash tabs use commands available on Linux/macOS, not Windows-only tools.
  • Where Windows-specific instructions are given, add equivalent steps for Linux/macOS users.
  • Consider listing Linux/macOS examples before or alongside Windows/PowerShell examples to avoid implicit prioritization.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The release notes for Workload Orchestration in Azure Arc generally use cross-platform Azure CLI commands and reference features available in both portal and CLI. However, in the May 2025 release, CLI examples are provided exclusively in PowerShell syntax (with backticks for line continuation), which is Windows-centric. Bash examples are used elsewhere, but PowerShell appears first and is the only example for some CLI tasks. There are no Linux-specific tools or commands mentioned, but the exclusive use of PowerShell in some sections may create friction for Linux/macOS users.
Recommendations
  • Provide Bash equivalents for all CLI examples, especially where only PowerShell syntax is shown.
  • Ensure CLI instructions are platform-neutral and avoid using Windows-specific line continuation (backticks) in examples.
  • Add a note clarifying that Azure CLI is cross-platform and can be used on Linux/macOS, with examples for those environments.
  • Where possible, show Bash and PowerShell examples side-by-side for parity.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-02-12 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 are provided only in PowerShell syntax, even for tasks that are cross-platform (e.g., Azure CLI, Docker, kubectl). Linux/Bash equivalents are missing for critical troubleshooting steps, except in the 'Troubleshoot service groups' section, where both Bash and PowerShell tabs are provided. This creates friction for Linux/macOS users, who must translate PowerShell-specific commands and scripting patterns to their environment.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell command examples, especially for Azure CLI, Docker, and kubectl commands.
  • Avoid using PowerShell-specific scripting constructs (e.g., variable assignment, ConvertTo-Json, Out-File) without offering a Bash alternative.
  • Ensure cross-platform parity by showing Bash examples first or side-by-side with PowerShell.
  • Clarify when a command is Windows-only or cross-platform.
  • Review and update sections where only PowerShell is used for tasks that are not Windows-specific.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only a PowerShell migration script (WOGAMigration.ps1) and instructs users to run it in PowerShell, with no mention of Bash, Linux shell, or cross-platform alternatives. There is no guidance for Linux/macOS users on how to perform the migration or run the script, creating friction for non-Windows environments.
Recommendations
  • Provide instructions for running the migration script on Linux/macOS, such as using PowerShell Core (pwsh) on those platforms.
  • Clarify whether the script is compatible with PowerShell Core and, if so, add example commands for Linux/macOS users.
  • If the script is Windows-only, offer an alternative migration method for Linux/macOS users or explicitly state the limitation.
  • Include troubleshooting tips for non-Windows users attempting to run the script.
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-10 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 it uses Windows/PowerShell-centric tools (Invoke-AksEdgeNodeCommand) for Linux node configuration. No native Linux shell or SSH examples are provided for sysctl changes, and Notepad is mentioned as the default editor for JSON files, which is a Windows tool.
Recommendations
  • Provide native Linux command-line examples for sysctl configuration (e.g., using SSH and bash).
  • Mention Linux text editors (such as nano, vim, or gedit) alongside Notepad for editing JSON files.
  • Clarify whether Invoke-AksEdgeNodeCommand is required or if direct Linux commands can be used.
  • Add explicit Linux shell examples for file editing and configuration steps.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides command-line examples for connecting to the SQL Server instance using sqlcmd, but these examples are shown exclusively with PowerShell syntax (e.g., using PowerShell prompt and conventions). There is no explicit mention of Linux/macOS alternatives or shell syntax, and the use of PowerShell is presented first and exclusively, which may create friction for Linux/macOS users.
Recommendations
  • Provide equivalent examples using Bash shell syntax for Linux/macOS users, especially for commands involving kubectl exec and sqlcmd.
  • Clarify that sqlcmd and kubectl commands can be run from any OS with the appropriate tools installed, and provide OS-agnostic instructions.
  • Add notes or sections indicating any OS-specific requirements or differences, such as path conventions or environment setup.
  • Ensure that examples do not use PowerShell-specific syntax unless the task is Windows-only.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides backup examples and file paths using Windows conventions (e.g., C:\Backupfiles\test.bak) and does not offer equivalent Linux/macOS examples for creating or handling backup files. The use of tools like Visual Studio Code and Azure Storage Explorer is cross-platform, but the backup/restore steps and file copy examples are Windows-centric, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit examples for creating SQL Server backups on Linux (e.g., using /var/opt/mssql/backup/test.bak as the backup path).
  • When showing file paths or commands, provide both Windows and Linux/macOS variants side-by-side.
  • Clarify that tools like Visual Studio Code and Azure Storage Explorer are cross-platform, and link to installation instructions for Linux/macOS.
  • In the kubectl cp example, show a Linux/macOS source path (e.g., /home/user/backup/test.bak) in addition to the Windows path.
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-10 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 approaches for base64 encoding files, but the Windows example (using certutil) is more detailed and includes additional steps (removing headers with findstr). The Linux example is brief and lacks equivalent guidance for header removal. The Windows tools are mentioned explicitly, and the Windows workflow is described in greater depth. The rest of the documentation is platform-neutral, focusing on Azure CLI, kubectl, and OpenSSL, which are cross-platform.
Recommendations
  • Expand the Linux example to include instructions for removing certificate headers from base64 output, similar to the Windows example.
  • Mention Linux/macOS alternatives for header removal, such as using grep or sed.
  • Present Linux and Windows examples with equal detail and in parallel, rather than giving more steps for Windows.
  • Consider showing Linux/macOS examples first, or side-by-side, to avoid 'windows_first' bias.
GitHub Create Pull Request
Azure Arc Azure Arc resource bridge system requirements ...icles/azure-arc/resource-bridge/system-requirements.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references Azure CLI installation with a direct link to the Windows installation page and does not mention Linux or macOS management machines or provide explicit instructions/examples for those platforms. There are no PowerShell-specific commands or Windows-only tools, but the lack of parity in examples and links may cause confusion for Linux/macOS users.
Recommendations
  • Provide explicit mention that the management machine can be Windows, Linux, or macOS, as Azure CLI is cross-platform.
  • Add links to Azure CLI installation instructions for Linux and macOS, not just Windows.
  • Clarify that all CLI commands shown are valid on all supported platforms.
  • If there are any platform-specific requirements (such as 32-bit/64-bit), specify them for each OS.
  • Consider including a short example or note for Linux/macOS users to reinforce parity.
GitHub Create Pull Request
← Previous Page 46 of 94 Next →