Scan Details - Linux-first Docs for Azure

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 instructions for all major lifecycle tasks (install, upgrade, uninstall, proxy config), but Windows examples and tooling (PowerShell, Control Panel, Msiexec, Group Policy, WSUS, Configuration Manager) are often presented first and in greater detail. The cleanup script for stale resources is provided only in PowerShell, with no Linux shell or Azure CLI equivalent. Windows-specific management patterns (e.g., Group Policy, WSUS) are described at length, while Linux equivalents (e.g., configuration management, package automation) are not mentioned.

Recommendations

Provide Azure CLI/bash equivalents for PowerShell-only scripts, especially for resource cleanup.
Where possible, present Linux and Windows examples side-by-side or alternate which comes first.
Add Linux automation guidance for agent upgrades and removals (e.g., using Ansible, cron, or systemd).
Include links or references to Linux-native management tools for package updates and configuration.
Clarify when a method is Windows-only and suggest Linux alternatives.

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 examples and scenarios that reference Windows-centric tools and patterns (such as Group Policy Objects and WSUS) before or instead of Linux equivalents. There are no explicit Linux management examples, and Windows tools are mentioned as the default or primary legacy systems. This creates subtle friction for Linux users, who may need to infer how their existing tools fit into the Azure Arc transition.

Recommendations

Include examples of legacy Linux management tools (e.g., Ansible, Chef, Puppet, cron jobs) alongside Windows tools when discussing phased adoption and overlap scenarios.
Provide explicit Linux onboarding and verification steps, such as mentioning supported Linux distributions and any OS-specific considerations.
When listing resource organization or automation examples, clarify that these apply to both Windows and Linux servers, or provide Linux-specific examples where appropriate.
Reference Linux equivalents for patching and compliance (e.g., using Azure Update Manager with Linux, mapping Azure Policy to Linux configuration management).

Create Pull Request

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 page provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, several examples and troubleshooting steps are presented with a Windows-first bias. PowerShell is used for network troubleshooting and proxy validation, and Windows paths are shown in error messages and instructions before Linux equivalents. Some CLI instructions and troubleshooting steps lack explicit Linux/macOS examples, and Windows-specific tools (such as Remote PowerShell, RDP) are mentioned without Linux alternatives. Linux troubleshooting is only briefly addressed (e.g., glibc version errors), and Linux/macOS users may need to infer how to adapt instructions.

Recommendations

Provide Linux/macOS equivalents for all CLI and troubleshooting commands, especially for network and DNS validation (e.g., show both nslookup/ping for Windows and dig/host/ping for Linux).
Include Linux/macOS paths and error message formats alongside Windows paths in CLI error examples.
When referencing PowerShell or RDP, also mention Linux/macOS alternatives (e.g., SSH, console access).
Expand troubleshooting steps for Linux-specific issues (such as glibc errors) and provide more detailed guidance for Linux users.
Ensure that all CLI commands are shown with syntax that works on both Windows and Linux shells, or explicitly note any OS-specific differences.

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: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides ARM template examples for both Linux and Windows VM extensions, ensuring parity in template content. However, all deployment commands and walkthroughs use Azure PowerShell exclusively, with no Azure CLI or Bash examples. PowerShell commands are shown first and only, which may create friction for Linux/macOS users who prefer Bash or Azure CLI. Additionally, file path examples use Windows-style paths (e.g., D:\Azure\Templates\...), and command execution patterns (such as 'powershell -ExecutionPolicy Unrestricted -File ...') are Windows-centric in the Windows custom script extension template.

Recommendations

Add Azure CLI deployment examples alongside PowerShell commands, especially for deploying ARM templates.
Include Linux/macOS file path examples (e.g., /home/user/Azure/Templates/...) where appropriate.
Clarify that both PowerShell and Azure CLI can be used for deployments, and link to CLI documentation.
Where custom script execution is shown, provide equivalent Bash/sh examples for Linux.
Consider showing CLI/Bash commands before or alongside PowerShell commands to avoid Windows-first impression.

Create Pull Request

Container Registry Azure Container Registry Authentication Options Explained ...ontainer-registry/container-registry-authentication.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides both Azure CLI and Azure PowerShell examples for authentication, but PowerShell is given equal prominence to CLI, despite being Windows-centric. Most command examples are cross-platform (Azure CLI, Docker), but PowerShell examples are included throughout, and in some cases, CLI and PowerShell are presented as equivalent options. There is no explicit mention of Linux/macOS shell usage (e.g., Bash), and the order of examples often lists PowerShell alongside or immediately after CLI, rather than prioritizing cross-platform tools. There are no Linux-specific authentication patterns or troubleshooting notes, and the 'Next steps' section links to PowerShell and CLI guides, but not to Linux/macOS shell-specific guides.

Recommendations

Prioritize Azure CLI and Docker examples, as these are cross-platform, and list them before PowerShell examples.
Explicitly mention that Azure CLI and Docker commands work on Linux/macOS, and provide sample Bash syntax where appropriate (e.g., environment variable usage, piping).
Add troubleshooting notes or tips for Linux/macOS users, such as file permission issues with Docker config, or differences in environment variable syntax.
Consider adding a 'Linux/macOS authentication' section or callout to reassure non-Windows users of parity.
Review the 'Next steps' section to include links to Linux/macOS getting started guides, if available.

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 page provides command-line examples for managing Helm charts in Azure Container Registry, but several commands use Windows-style syntax (e.g., 'set' for environment variables) and do not provide Linux/macOS equivalents. The environment variable setup uses 'set', which is only valid in Windows CMD, while most other commands use Bash syntax. No explicit PowerShell examples are present, and most Azure CLI and Helm commands are cross-platform, but the initial environment variable example may confuse Linux/macOS users.

Recommendations

Provide both Windows (CMD/PowerShell) and Linux/macOS (Bash) syntax for environment variable setup. For example, use 'export ACR_NAME=<container-registry-name>' for Bash and 'set ACR_NAME=<container-registry-name>' for CMD.
Add a note clarifying which commands are platform-specific and which are cross-platform.
Ensure all example commands are shown in both Bash and Windows syntax where differences exist.
Consider using Bash syntax as the default, since most cloud-native and Kubernetes users are on Linux/macOS.

Create Pull Request

Azure Portal Use Azure Copilot with the Azure mobile app ...main/articles/azure-portal/mobile-app/azure-copilot.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell (Windows-centric) alongside CLI without specifying Linux/macOS equivalents or giving parity to Bash or shell scripting. No explicit Linux/macOS examples or tools are referenced, and PowerShell is mentioned before any Linux-native scripting options.

Recommendations

Clarify that Azure Copilot can generate scripts for Bash, Azure CLI, and other Linux/macOS environments, not just PowerShell.
Explicitly mention Bash or shell scripting as supported output formats when discussing script generation.
Provide examples or scenarios for Linux/macOS users, such as generating Bash scripts or using Azure CLI on non-Windows platforms.
Avoid listing PowerShell before CLI or Bash unless there is a technical reason for prioritizing Windows tools.

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: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation generally presents Windows download links and version numbers before Linux equivalents and occasionally references Windows-specific tools (e.g., PowerShell, msiexec) and installer behaviors. However, Linux support is clearly present, and Linux-specific changes are documented. There are no critical sections that exclude Linux users, but some minor friction exists due to Windows-first ordering and references to Windows tools.

Recommendations

Alternate the order of Windows and Linux download links and version numbers, or present them together to avoid implying priority.
Where installer troubleshooting is discussed, provide equivalent Linux instructions or clarify when an issue is Windows-only.
When referencing Windows tools (e.g., PowerShell, msiexec), provide Linux equivalents (e.g., shell commands, package managers) where relevant, or explicitly state when an issue or instruction is Windows-specific.
Consider adding a brief section summarizing Linux-specific installation or troubleshooting tips, similar to the Windows installer guidance.

Create Pull Request

Azure Arc Run command on Azure Arc-enabled servers (Preview) ...cs/blob/main/articles/azure-arc/servers/run-command.md

Low 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 for Run command on Azure Arc-enabled servers, but there is a subtle bias toward Windows: PowerShell is highlighted as a primary experience alongside Azure CLI and REST, and examples or next steps list PowerShell before REST API, with no explicit mention of Bash or Linux shell scripting. The documentation does not provide Linux-specific examples or tools, and minor Linux limitations (e.g., name length) are relegated to notes.

Recommendations

Add explicit Linux/Bash scripting examples and workflows alongside PowerShell examples.
Highlight Linux shell usage in the 'Experiences' section, e.g., Bash or sh, not just PowerShell.
Ensure parity in next steps by including a dedicated Linux example page or section.
Mention Linux-specific considerations or best practices more prominently, not just in notes.

Create Pull Request

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

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools

Summary

The documentation generally presents authentication options and usage patterns that apply to both Windows and Linux. However, there is a mild Windows bias: Windows-specific authentication methods (interactive browser login, certificate store usage) are described before Linux equivalents, and PowerShell tools (Get-AzAccessToken) are mentioned for access token retrieval without Linux alternatives. The interactive browser login is called out as Windows-only, but Linux options are present and described. Windows certificate store usage is detailed, while Linux certificate handling is only briefly mentioned. Examples and usage instructions are mostly OS-neutral, but some flags and workflows are explained with Windows-first language.

Recommendations

Add explicit Linux/macOS instructions for obtaining access tokens (e.g., using Azure CLI: 'az account get-access-token') alongside PowerShell examples.
Clarify certificate handling for Linux (e.g., where to store PEM/PFX files, recommended permissions, sample file paths).
Where authentication methods differ by OS, present Linux/macOS options first or in parallel with Windows options.
If possible, provide example commands for Linux/macOS shells (bash/zsh) alongside any Windows/PowerShell-specific examples.
For certificate-based authentication, include a Linux example for specifying the certificate path and permissions.

Create Pull Request

Azure Arc VM Extension Management with Azure Arc-Enabled Servers ...ain/articles/azure-arc/servers/manage-vm-extensions.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation presents Windows VM extensions before Linux VM extensions, listing a more extensive set of Windows extensions and providing more detailed descriptions and links for Windows scenarios. However, Linux extensions are also covered with equivalent tables and links, and partner extensions are shown for both platforms. No CLI or PowerShell command examples are present, and deployment methods are listed in a neutral order.

Recommendations

Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side to emphasize parity.
Ensure that the number and detail of Linux extension entries matches Windows where possible, or clarify if certain extensions are Windows-only.
Add explicit examples or links for deploying extensions on Linux using Azure CLI, PowerShell, and templates, if such examples exist for Windows.
Highlight cross-platform deployment methods and note any platform-specific limitations.

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 shown first. The PowerShell example is included, but there is a slight bias in the formatting and explanation: the Bash example is more detailed and uses the canonical file name ('protected-settings-extension.json'), while the PowerShell example uses 'settings.json' and includes a workaround for carriage returns. The rest of the documentation uses Azure CLI and kubectl commands, which are cross-platform and do not show Windows-specific tools or patterns. No Linux examples are missing, and Linux users can complete all tasks.

Recommendations

Ensure both Bash and PowerShell examples use consistent file naming and structure.
Add brief notes clarifying that Azure CLI and kubectl commands work on Linux, macOS, and Windows.
Consider providing a short explanation for PowerShell users about handling carriage returns, or use a more cross-platform approach.
If possible, provide parity in example detail and output formatting between Bash and PowerShell tabs.

Create Pull Request

Scan Information

Problematic Pages