32
Pages Scanned
9
Pages Flagged
32
Changed Pages
28.1%
% Pages Flagged
Scan Information
Started At: 2026-02-01 00:00:11
Finished At: 2026-02-10 18:44:36
Status: completed
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 32
Files Completed: 32
Problematic Pages
9 issues found
Azure Arc
Troubleshoot Azure Arc resource bridge issues
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority
View Details →
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 used for network troubleshooting examples, Windows-specific terms (such as 'Remote PowerShell', 'RDP', and 'time.windows.com') are referenced, and Windows/PowerShell commands are often shown before or instead of Linux equivalents. Linux troubleshooting commands (e.g., nslookup, ldd --version) are mentioned but less frequently, and some examples (such as DNS resolution and proxy troubleshooting) lack Linux-specific instructions. The documentation does not consistently offer Linux/macOS alternatives for all CLI or troubleshooting steps.
Recommendations
- Provide Linux/macOS equivalents for all PowerShell and Windows command examples (e.g., use curl, wget, dig, or nslookup for network troubleshooting).
- When referencing Windows-specific tools (e.g., PowerShell, RDP), also mention SSH, terminal, or console access for Linux/macOS users.
- Clarify that Azure CLI and arcappliance extension are cross-platform and provide installation/downgrade instructions for Linux/macOS (e.g., apt, yum, brew).
- Include troubleshooting steps and error resolution commands for Linux/macOS environments alongside Windows steps.
- Avoid using Windows-specific endpoints (e.g., time.windows.com) without mentioning Linux alternatives (e.g., pool.ntp.org).
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 →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstall, and proxy configuration steps. However, there is a notable bias toward Windows in several areas: (1) PowerShell scripts and Windows-specific tools (Control Panel, Msiexec, Group Policy, WSUS, Configuration Manager) are described in greater detail, with full step-by-step instructions, while Linux instructions are more concise and rely on standard package manager commands; (2) The cleanup script for removing stale Arc resources is provided only in PowerShell, with no Linux shell or Azure CLI equivalent; (3) In some sections, Windows instructions or tools are presented first or in more depth than their Linux counterparts.
Recommendations
- Provide equivalent cleanup scripts for Linux users, using Bash and Azure CLI where possible.
- Where PowerShell scripts are given, offer Azure CLI or Bash alternatives for Linux/macOS users.
- Ensure that detailed step-by-step instructions are available for Linux package manager operations, not just Windows installer flows.
- When listing upgrade/uninstall methods, present Windows and Linux options in parallel, with similar depth and clarity.
- For proxy configuration, clarify any Linux-specific service restart requirements and provide troubleshooting tips as are given for Windows.
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 →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides examples and references that prioritize Windows-centric management tools and patterns, such as Group Policy Objects (GPOs) and Windows Server Update Services (WSUS), without offering equivalent Linux examples or mentioning Linux-native tools. Windows tools are referenced first and exclusively in scenarios where cross-platform alternatives exist, creating friction for Linux users seeking parity.
Recommendations
- Include Linux-native management tool examples (e.g., reference Ansible, Chef, or native package managers like apt/yum for patching).
- When discussing overlapping management scenarios, mention common Linux approaches (e.g., cron jobs, configuration management tools) alongside Windows tools.
- Provide example workflows or scripts for onboarding and managing Linux servers with Azure Arc.
- Ensure that resource organization, automation, and training sections explicitly address Linux server considerations and operational differences.
Azure Arc
Enable VM Extensions Using Azure Resource Manager Template
...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides ARM template examples for both Linux and Windows VM extensions, maintaining parity in template content. However, all deployment instructions and command-line examples use Azure PowerShell exclusively, with no Azure CLI or Bash examples. Additionally, PowerShell deployment commands are presented first and exclusively, which may create friction for Linux/macOS users who prefer Bash or Azure CLI.
Recommendations
- Add equivalent Azure CLI deployment examples alongside PowerShell commands for deploying ARM templates.
- Explicitly mention that both PowerShell and Azure CLI can be used, and link to Azure CLI documentation for template deployment.
- Consider providing Bash script snippets for Linux users, especially for common deployment scenarios.
- Reorder or parallelize command examples so that PowerShell and CLI/Bash are presented together, rather than PowerShell first.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page provides command-line examples for Helm and Azure CLI, which are cross-platform tools. However, there is a notable Windows bias in the use of the 'set' command for environment variable assignment, which is specific to Windows CMD. There are no Linux/macOS equivalents (e.g., 'export') shown for setting environment variables. All other commands are platform-agnostic, but the initial environment variable setup may confuse or hinder Linux/macOS users.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') examples when setting environment variables.
- Add a note clarifying which commands are platform-specific and which are cross-platform.
- Consider showing Linux/macOS examples first or side-by-side, as most Kubernetes/Helm users are on Linux/macOS.
Azure Arc
CLI reference for `azcmagent connect`
...b/main/articles/azure-arc/servers/azcmagent-connect.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation for `azcmagent connect` demonstrates mild Windows bias in several areas. Windows authentication options are described first, and Windows-specific certificate store usage is detailed before Linux equivalents. The only explicit tooling example for obtaining an access token references PowerShell (`Get-AzAccessToken`), with no Linux or cross-platform alternatives given. However, Linux usage is generally supported and described, and most examples are OS-neutral.
Recommendations
- When mentioning authentication options, present Linux and Windows defaults together or alternate which is described first.
- For access token acquisition, provide a cross-platform Azure CLI example (e.g., `az account get-access-token`) alongside the PowerShell example.
- Clarify certificate handling for Linux (e.g., where to store PEM/PFX files, recommended permissions) in parallel with Windows certificate store details.
- Explicitly state that all examples work on both Windows and Linux unless otherwise noted, and highlight any OS-specific flags or behaviors.
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The release notes for the Azure Connected Machine agent generally provide parity between Windows and Linux, listing features and fixes for both platforms. However, there is a mild Windows bias: Windows download links and version numbers are consistently listed before Linux, Windows installer issues and troubleshooting steps (e.g., UAC, PowerShell, msiexec) are described in detail, and Windows tools (PowerShell, Command Prompt) are referenced without Linux equivalents. Some improvements or fixes are Windows-only, but Linux-only changes are also noted. No critical functionality appears to be Windows-exclusive, and Linux users can access all major agent features.
Recommendations
- Alternate the order of Windows and Linux in tables and download links, or present them side-by-side.
- When describing installer troubleshooting, include equivalent Linux installation/upgrade troubleshooting steps (e.g., using rpm, dpkg, systemctl).
- Reference Linux tools (e.g., Bash, systemctl, rpm) alongside Windows tools when discussing installation or configuration.
- Ensure that any platform-specific improvements are clearly labeled as such, and provide parity in detail for both platforms.
Azure Portal
Use Azure Copilot with the Azure mobile app
...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation mentions generating CLI and PowerShell scripts as a key scenario, listing PowerShell alongside CLI (which typically refers to Azure CLI, a cross-platform tool). PowerShell is traditionally associated with Windows, and its mention before Bash or Linux shell scripting may suggest a slight Windows-first bias. However, the page does not provide actual examples or instructions that are Windows-specific, and it also references the Azure CLI, which is cross-platform.
Recommendations
- Clarify that both Azure CLI and PowerShell are supported, and explicitly mention Bash or Linux shell scripting if relevant.
- Provide example prompts for both PowerShell and Bash/Azure CLI to demonstrate parity.
- Avoid listing PowerShell before CLI unless contextually appropriate; consider grouping them as 'CLI (Azure CLI, Bash, PowerShell)' to emphasize cross-platform support.
Container Registry
Deploy the Connected Registry Arc Extension
...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority
View Details →
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 present and uses standard Azure CLI commands, but there is a slight emphasis on Windows/PowerShell by including a dedicated tab for it. All other commands and workflows are cross-platform (Azure CLI, kubectl), and there are no Windows-only tools or patterns. No Linux equivalents are missing, and the overall workflow is platform-agnostic.
Recommendations
- Clarify that both Bash and PowerShell examples are equivalent and suitable for their respective platforms.
- Consider adding a note that Azure CLI commands work on Windows, Linux, and macOS, and that users should select the example matching their shell environment.
- Ensure parity in example complexity and output file naming between Bash and PowerShell (e.g., both use protected-settings-extension.json).