Scan Details - Linux-first Docs for Azure

Azure Arc Troubleshoot Azure Arc resource bridge issues ...re-arc/resource-bridge/troubleshoot-resource-bridge.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances of Windows bias: PowerShell is used for network troubleshooting and proxy validation examples, Windows-specific terminology (e.g., 'Remote Desktop Protocol', 'time.windows.com') appears before Linux equivalents, and some CLI troubleshooting steps reference Windows paths or behaviors. Linux-specific troubleshooting (e.g., shell commands, Linux file permissions, or proxy configuration) is rarely shown, and examples for Linux users are missing or less prominent.

Recommendations

Provide Linux/macOS equivalents for PowerShell commands, such as using curl, wget, or openssl for network/proxy validation.
Include Linux/macOS file system paths and permission troubleshooting steps alongside Windows examples.
When referencing system requirements or troubleshooting steps, explicitly mention Linux/macOS scenarios (e.g., how to check glibc version, how to resolve SSH folder permission errors on Linux).
Show both Windows and Linux/macOS commands in CLI examples, or clarify which OS each example applies to.
Avoid using Windows-specific terminology (like 'Remote Desktop Protocol') without mentioning Linux/macOS alternatives (like SSH or console access).

Create Pull Request

Azure Arc CLI reference for `azcmagent connect` ...b/main/articles/azure-arc/servers/azcmagent-connect.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools

Summary

The documentation page for `azcmagent connect` demonstrates some Windows bias. Windows authentication options (interactive browser login, certificate store usage) are described first and in more detail, and PowerShell tooling (`Get-AzAccessToken`) is referenced for access token acquisition without mentioning Linux/macOS equivalents. Windows certificate store options are explained, but Linux certificate handling is not covered in equivalent detail. Examples and instructions generally do not show Linux-specific shell commands or highlight Linux workflows.

Recommendations

Add explicit Linux/macOS examples for authentication flows, especially for certificate-based authentication (e.g., storing and referencing PEM/PFX files on disk).
When referencing access token acquisition, include cross-platform methods (e.g., Azure CLI: `az account get-access-token`) alongside PowerShell.
Balance the order of authentication options so that Linux-default methods (device code login, file-based certificates) are described first or equally.
Clarify Linux/macOS certificate handling, including file permissions, recommended storage locations, and any OS-specific caveats.
Where Windows-specific features (like certificate store usage) are described, provide a parallel Linux/macOS section or explicitly state their absence.

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 →

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 guidance for all major lifecycle tasks (install, upgrade, uninstall, proxy config), using tabbed sections for each OS/package manager. However, there is a mild Windows bias: Windows instructions and examples often appear first, PowerShell is used for scripting and automation examples (e.g., stale resource cleanup), and Windows-specific tools (Control Panel, Group Policy, WSUS, Configuration Manager) are described in detail, while Linux equivalents for at-scale management are not discussed. The cleanup script is only provided in PowerShell, with no Bash or cross-platform alternative.

Recommendations

Alternate the order of Windows and Linux sections, or present them in parallel to avoid Windows-first perception.
Provide equivalent Linux automation examples (e.g., Bash scripts for stale resource cleanup using Azure CLI or azcmagent).
Mention Linux-native management tools (such as Ansible, systemd, or package manager automation) where Windows tools like Group Policy or WSUS are discussed.
Where PowerShell is used for Azure automation, note that Azure CLI is cross-platform and provide CLI examples for Linux/macOS users.
Clarify when a method is Windows-only and suggest Linux alternatives for at-scale management and automation.

Create Pull Request

Azure Arc Next steps for cloud-native server management with Azure Arc-enabled servers .../articles/azure-arc/servers/cloud-native/next-steps.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example

Summary

The documentation page presents several examples and scenarios that reference Windows-centric tools and patterns (such as Group Policy Objects and WSUS) without providing equivalent Linux examples or mentioning Linux-native tools. Windows management approaches are described first and in detail, while Linux-specific management strategies are not addressed, which may create friction for Linux users seeking parity.

Recommendations

Include examples of Linux management tools and practices (e.g., mention Ansible, Chef, or native Linux configuration management for comparison alongside GPOs).
When discussing patching, reference Linux patching workflows (such as using Azure Update Manager with apt/yum/zypper) and provide links to relevant documentation.
Add scenarios that illustrate how Azure Arc-enabled servers can be used to manage Linux servers, including compliance and configuration drift remediation.
Ensure that resource organization, automation, and training sections explicitly mention Linux server considerations and tools where applicable.

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 →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_first

Summary

The documentation provides ARM template examples for both Linux and Windows VM extensions, but all deployment instructions and command-line examples use Azure PowerShell exclusively, with no Azure CLI or Bash equivalents. The deployment commands are shown only in PowerShell, and file paths in examples use Windows-style syntax. This creates friction for Linux/macOS users who may prefer Bash or Azure CLI. Additionally, in some sections, Windows examples or concepts (such as PowerShell command construction) are presented first or exclusively.

Recommendations

Add Azure CLI deployment command examples alongside PowerShell for template deployments, especially for Linux/macOS users.
Include Bash-style file path examples or clarify that file paths should be adapted for Linux/macOS environments.
Explicitly mention that ARM template deployment can be performed using Azure CLI, and link to relevant CLI documentation.
Where possible, alternate the order of Linux and Windows examples, or present them in parallel.
Add a note clarifying that PowerShell commands are shown for convenience, but equivalent CLI commands are available.

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 →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation mentions both Windows and Linux support, but the examples and next steps prioritize Windows-centric tools (PowerShell) and list Windows/PowerShell before Linux/Azure CLI. There is no explicit Linux example or parity guidance, and PowerShell is emphasized as a primary experience.

Recommendations

Add explicit Linux-focused examples and workflows, especially in the main documentation and linked pages.
Ensure Azure CLI examples (which are cross-platform) are presented before or alongside PowerShell examples.
Clarify any OS-specific limitations or differences, and provide guidance for Linux users where applicable.
Include screenshots or walkthroughs for Linux environments, not just Windows/PowerShell.
Highlight any Linux-specific considerations (such as the note about name length) more prominently.

Create Pull Request

Container Registry Store Helm Charts in Azure Container Registry ...es/container-registry/container-registry-helm-repos.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides command-line examples for Helm and Azure CLI, which are cross-platform, but some environment variable setting instructions use Windows-style syntax (e.g., 'set ACR_NAME=<container-registry-name>') without showing Linux/macOS equivalents. The order of Kubernetes cluster creation instructions lists Azure CLI, PowerShell, and Portal, with PowerShell (Windows-centric) mentioned before Portal. No explicit Linux/macOS shell examples are provided for environment variables, which may cause confusion for non-Windows users.

Recommendations

For all environment variable instructions, provide both Windows (cmd.exe) and Linux/macOS (bash/zsh) syntax, e.g., 'set ACR_NAME=...' and 'export ACR_NAME=...'.
When listing options for creating resources (e.g., AKS clusters), consider listing cross-platform tools (Azure CLI, Portal) before Windows-specific tools (PowerShell), or clarify platform applicability.
Add a note clarifying that all Azure CLI and Helm commands work on Linux/macOS and Windows, and provide shell-specific guidance where relevant.
Where sample commands use shell features (e.g., heredoc, environment variables), clarify syntax differences for Windows and Linux/macOS users.

Create Pull Request

Azure Arc What's new with Azure Connected Machine agent ...main/articles/azure-arc/servers/agent-release-notes.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy

Summary

The documentation generally provides both Windows and Linux information for each release, including download links and feature parity tables. However, there is a consistent pattern of listing Windows before Linux in download links, tables, and feature descriptions. Some instructions and troubleshooting notes reference Windows-specific tools (e.g., PowerShell, msiexec) without equivalent Linux examples. Occasional improvements or bug fixes are described only for Windows (e.g., installer GUI, PATH variable), and troubleshooting steps for Linux are absent.

Recommendations

Alternate the order of Windows and Linux in download links and tables, or present them side-by-side to avoid implicit prioritization.
When referencing Windows-specific tools or commands (e.g., PowerShell, msiexec), provide equivalent Linux commands (e.g., bash, rpm, systemctl) where applicable.
Include troubleshooting steps and known issues for Linux where relevant, not just for Windows.
Ensure that Linux-specific improvements or bug fixes are described with the same detail as Windows ones.
Where features or fixes are Windows-only, clearly label them as such, and do the same for Linux-only items.

Create Pull Request

Container Registry Deploy the Connected Registry Arc Extension ...iner-registry/quickstart-connected-registry-arc-cli.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but Bash is presented first. The PowerShell example is included, but there is a slight bias in favor of Bash (Linux/macOS) by order, and no Windows-specific tools or patterns are used outside of the PowerShell example. All other commands use Azure CLI and kubectl, which are cross-platform. No critical steps are Windows-only, and Linux/macOS users can follow all instructions without friction.

Recommendations

Ensure that both Bash and PowerShell examples are equally visible and clearly marked as platform-specific.
Consider adding a note clarifying which example to use based on the user's operating system.
Verify that all Azure CLI commands work identically on Windows, Linux, and macOS, and mention any platform-specific caveats if they exist.

Create Pull Request

Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides deployment instructions for both Azure CLI and Azure PowerShell, but the PowerShell section is given its own dedicated heading and example, while Bash or Linux shell scripting is not mentioned. The Azure CLI section is platform-agnostic, but PowerShell is called out separately, which may suggest a slight Windows bias. However, all critical tasks can be completed using the Azure CLI, which is fully supported on Linux/macOS. The order of presentation (CLI before PowerShell) is appropriate, but the lack of explicit Bash/shell scripting examples or mention of cross-platform scripting in the PowerShell section is a minor bias.

Recommendations

Clarify that Azure CLI commands work on Windows, Linux, and macOS, and can be used in Bash or other shells.
Consider adding a short Bash script example for deploying dashboards using Azure CLI, to reinforce Linux parity.
In the PowerShell section, note that Azure PowerShell is also available cross-platform (via PowerShell Core), or link to installation instructions for Linux/macOS.
If possible, add a table summarizing deployment options by platform (Portal, CLI, PowerShell) to make parity explicit.

Create Pull Request

Scan Information

Problematic Pages