32
Pages Scanned
9
Pages Flagged
32
Changed Pages
28.1%
% Pages Flagged
Scan Information
Started At: 2026-02-02 00:00:07
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 page provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, several sections show Windows bias: PowerShell is used for troubleshooting HTTP2 issues, Windows-specific error messages (e.g., 'connectex') appear in examples, and some instructions (such as proxy troubleshooting and DNS resolution) use Windows tools or syntax first, with Linux equivalents either missing or mentioned second. There are also CLI and pip examples, but Linux troubleshooting steps (such as shell commands for DNS or permissions) are less emphasized or absent.
Recommendations
- Provide Linux/macOS equivalents for all PowerShell and Windows command-line examples (e.g., use curl, wget, or openssl for HTTP2 troubleshooting, and dig/nslookup for DNS resolution).
- When showing troubleshooting commands, include both Windows and Linux/macOS syntax side-by-side.
- Ensure error messages and troubleshooting steps reference Linux/macOS scenarios (e.g., file permissions, SSH folder access, glibc errors) with concrete examples.
- Avoid presenting Windows tools or patterns first unless the majority of users are on Windows; otherwise, alternate or present both equally.
- Add explicit instructions for Linux/macOS users regarding CLI installation, proxy configuration, and file permissions.
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, with clear sections and examples for each. However, there is a notable Windows bias in several areas: (1) PowerShell scripts and Windows-specific tools (Control Panel, Msiexec, Group Policy, WSUS, Configuration Manager) are described in greater detail and with more step-by-step instructions than their Linux equivalents; (2) Windows examples and tooling are often presented first in multi-platform sections; (3) The cleanup script for removing stale resources is provided only in PowerShell, with no Linux shell or Azure CLI equivalent.
Recommendations
- Provide equivalent shell scripts or Azure CLI examples for resource cleanup tasks currently only documented in PowerShell.
- Ensure parity in the level of detail for Linux package manager instructions (e.g., troubleshooting, automation, logging) as is given for Windows tools.
- Where possible, present Windows and Linux instructions in parallel or alternate which platform is shown first.
- Add notes or links to Linux-native automation approaches (e.g., cron jobs, bash scripts) for tasks like agent upgrades and cleanup.
- For proxy configuration, clarify any Linux-specific service restart requirements and provide troubleshooting tips similar to those given for Windows.
Azure Arc
CLI reference for `azcmagent connect`
...b/main/articles/azure-arc/servers/azcmagent-connect.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally presents authentication options and examples in a cross-platform manner, but there are signs of Windows bias: Windows authentication methods are described first, Windows-specific certificate store options are detailed, and PowerShell is referenced for access token retrieval without mentioning Linux/macOS equivalents. Linux authentication flows are described, but Windows tools and patterns are often prioritized or exclusively mentioned.
Recommendations
- Present authentication options in a platform-neutral order, or alternate which OS is described first.
- When referencing access token retrieval, include cross-platform alternatives (e.g., Azure CLI, MSAL, or REST API) alongside PowerShell.
- For certificate-based authentication, clarify Linux/macOS certificate storage and retrieval options, not just Windows certificate stores.
- Where Windows-specific tooling is described (e.g., certificate stores), explicitly state Linux/macOS alternatives or limitations.
- Ensure all examples are runnable on both Windows and Linux, or clearly label platform-specific commands.
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 page presents several examples and scenarios that reference Windows-centric tools and patterns, such as Group Policy Objects (GPOs) and Windows Server Update Services (WSUS), without providing equivalent Linux examples or mentioning Linux-native management tools. Windows tools are mentioned first and exclusively in key sections, creating a subtle bias toward Windows environments and leaving Linux users without clear guidance on how to approach similar tasks.
Recommendations
- Include Linux-native management tools in examples, such as mentioning Ansible, Chef, or Puppet for configuration management, and apt/yum/dnf for patching.
- Provide parallel examples for Linux environments when discussing phased adoption and overlap scenarios (e.g., using Azure Update Manager alongside existing Linux patching solutions like unattended-upgrades or yum-cron).
- Clarify that Azure Arc supports both Windows and Linux servers, and offer guidance or links for Linux-specific onboarding and management practices.
- Balance references to Windows tools with Linux equivalents, especially in sections discussing legacy management overlap and migration.
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 command examples use Azure PowerShell exclusively, with no Azure CLI or Bash alternatives shown. Additionally, PowerShell deployment commands are presented before any mention of other tools, and Windows-style file paths are used in examples. This creates friction for Linux/macOS users who may prefer Azure CLI or Bash for deployments.
Recommendations
- Add equivalent Azure CLI deployment command examples alongside PowerShell, especially for template deployment (e.g., az deployment group create ...).
- Show Linux/macOS file path examples (e.g., /home/user/Azure/...) in addition to Windows-style paths.
- Explicitly state that both Azure PowerShell and Azure CLI can be used for deployments, and link to CLI documentation.
- Consider presenting CLI and PowerShell examples together or alternating which is shown first.
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, with most features and fixes listed for both platforms. However, there is a mild Windows bias: Windows download links and version numbers are consistently listed before Linux, and troubleshooting guidance (e.g., installer issues) references Windows tools and patterns (PowerShell, Command Prompt, msiexec) without Linux equivalents. Some improvements and bug fixes are described only for Windows (e.g., GUI accessibility, installer service configuration), and PowerShell scripts are mentioned without Linux shell alternatives.
Recommendations
- Alternate the order of Windows and Linux download links and version numbers, or present them together where possible.
- Where troubleshooting steps are given for Windows (e.g., using msiexec, PowerShell), provide equivalent Linux instructions (e.g., using rpm, dpkg, systemctl, or shell commands).
- When mentioning platform-specific scripts (e.g., ExtensionCleanup.ps1), clarify if there are Linux equivalents or note their absence.
- Explicitly state when a fix or feature is Windows-only or Linux-only, and provide context for platform differences.
- Consider including a summary table at the top showing parity and platform-specific changes for quick reference.
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 both CLI and PowerShell scripts as a key capability of Azure Copilot in the mobile app. PowerShell (a Windows-centric tool) is listed alongside CLI, but PowerShell is mentioned before CLI, which may subtly prioritize Windows tooling. No explicit Linux/macOS examples or tools are highlighted, and there is no mention of Bash or shell scripting, which are common on Linux/macOS.
Recommendations
- List CLI (az) examples before PowerShell, or present them together to avoid perceived prioritization.
- Explicitly mention Bash or shell scripting as supported output formats if applicable.
- Clarify that both Windows (PowerShell) and cross-platform (CLI, Bash) scripts can be generated, and provide examples for each.
- Add a note that Azure CLI is cross-platform and works on Linux/macOS as well as Windows.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation is generally cross-platform and uses standard Helm and Azure CLI commands, which work on Windows, Linux, and macOS. However, there is a minor Windows-first bias in the environment variable setting example, where 'set ACR_NAME=<container-registry-name>' is shown (Windows CMD syntax) before any mention of Linux/macOS alternatives. All other command examples use cross-platform syntax (bash, Azure CLI), and there are no PowerShell-specific or Windows-only tool references.
Recommendations
- Replace or supplement the 'set ACR_NAME=<container-registry-name>' example with the cross-platform 'export ACR_NAME=<container-registry-name>' (bash/zsh/fish) and note the difference for Windows CMD users.
- Add a short note clarifying environment variable syntax differences between Windows CMD, PowerShell, and Linux/macOS shells.
- Ensure all environment variable examples are shown in both Windows and Linux/macOS formats, or use the more common bash syntax first.
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 included in a separate tab, ensuring parity. The rest of the instructions use Azure CLI and kubectl, which are cross-platform tools. No Windows-only tools or patterns are present, and Linux/macOS users can follow all steps without friction.
Recommendations
- Continue to provide both Bash and PowerShell examples for cross-platform parity.
- Consider explicitly mentioning that Azure CLI and kubectl commands work on Windows, Linux, and macOS.
- Ensure that any future examples or troubleshooting steps do not assume a Windows environment unless necessary.