← Back to Dashboard
173
Pages Scanned
37
Pages Flagged
173
Changed Pages
21.4%
% Pages Flagged

Scan Information

Started At: 2026-02-10 00:00:10

Finished At: 2026-02-10 18:00:39

Status: completed

Target Repo: Azure Management

Current Phase: discovery

Files Queued: 173

Files Completed: 173

Problematic Pages

40 issues found
Azure Arc Migrate Existing Target Resources to General Availability ...s/azure-arc/workload-orchestration/migration-script.md
High Priority View Details →
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, or cross-platform alternatives. There are no Linux/macOS instructions or equivalent shell scripts provided, which may prevent non-Windows users from completing the migration.
Recommendations
  • Provide a Bash or cross-platform shell script equivalent to WOGAMigration.ps1, or clarify if the PowerShell script is compatible with PowerShell Core on Linux/macOS.
  • Explicitly document how Linux/macOS users can perform the migration, including any prerequisites (e.g., installing PowerShell Core).
  • If only PowerShell is supported, state this clearly and provide guidance for Linux/macOS users on installing and running PowerShell Core.
GitHub Create Pull Request
Azure Arc Onboarding Scripts for Workload Orchestration ...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page is heavily biased toward Windows/PowerShell environments. All onboarding scripts and usage examples are provided only as PowerShell scripts (.ps1), and all command-line instructions reference PowerShell syntax. The prerequisites instruct users to use 'winget', a Windows-only package manager, for installing required tools. There are no Bash, shell, or Linux/macOS equivalents or instructions. The documentation does not mention how to run the onboarding scripts or set up the environment on Linux or macOS, nor does it clarify if such support exists.
Recommendations
  • Provide Bash or shell script equivalents for the onboarding scripts, or clarify if the scripts are Windows-only.
  • Include installation instructions for Azure CLI and kubectl using cross-platform methods (e.g., apt, yum, Homebrew, or direct downloads) instead of only 'winget'.
  • Add explicit instructions or notes for Linux/macOS users, including any prerequisites or limitations.
  • If the onboarding scripts are truly Windows-only, state this clearly at the top of the page to set expectations.
  • Consider providing Docker-based or cross-platform automation options if possible.
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 →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation is focused on configuring AKS Edge Essentials on Linux, but it uses PowerShell cmdlets (Invoke-AksEdgeNodeCommand) to interact with the Linux node, rather than providing native Linux shell commands. This approach assumes the user is operating from a Windows environment with PowerShell, which may not be the case for all Linux administrators. There are no native Linux shell examples for checking or setting sysctl parameters.
Recommendations
  • Provide native Linux shell command examples (e.g., using 'sysctl' directly) for checking and setting 'fs.inotify.max_user_instances', in addition to or instead of PowerShell/Invoke-AksEdgeNodeCommand.
  • Clarify whether the steps are intended to be run from a Windows management host or directly on the Linux node, and offer Linux-native alternatives where possible.
  • If PowerShell is required, explain why and provide guidance for Linux users on how to install and use PowerShell if needed.
GitHub Create Pull Request
Azure Arc Back up controller database .../articles/azure-arc/data/backup-controller-database.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 command-line examples using PowerShell syntax (e.g., code blocks labeled as 'powershell'), and does not provide explicit Linux/macOS shell examples or mention cross-platform alternatives. The use of PowerShell code blocks for commands that are not inherently Windows-specific (e.g., kubectl, sqlcmd) may confuse Linux/macOS users and suggests a Windows-first bias. There are no Linux/macOS-specific instructions or clarifications, even though the tasks are Kubernetes- and SQL Server-based and likely to be performed on Linux clusters.
Recommendations
  • Replace 'powershell' code block labels with 'console' or 'bash' where appropriate, especially for kubectl and sqlcmd commands that are cross-platform.
  • Add explicit Linux/macOS shell examples where relevant, or clarify that the commands are the same across platforms.
  • If any commands require PowerShell-specific syntax, provide equivalent bash/zsh examples.
  • Mention that sqlcmd and kubectl are available on all major platforms, and provide installation links for Linux/macOS if not already present.
  • Review for any Windows tool references (e.g., base64 decoding) and suggest Linux/macOS equivalents (e.g., 'base64 --decode').
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 →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides backup examples using Windows file paths (e.g., C:\Backupfiles\test.bak) and references Windows tools (e.g., Notepad, OneNote) without offering equivalent Linux/macOS examples or instructions. This creates friction for non-Windows users, especially in the backup step and when copying files into pods.
Recommendations
  • Provide equivalent backup examples using Linux/macOS file paths (e.g., /home/user/backup/test.bak) alongside Windows examples.
  • Mention and show how to use common Linux/macOS text editors (e.g., nano, vim, TextEdit) when instructing users to save credentials.
  • Clarify that Visual Studio Code, Azure Storage Explorer, and kubectl are cross-platform, and provide any relevant platform-specific installation links or notes.
  • Instruct users on how to perform backup and file copy operations from Linux/macOS terminals, including example commands.
  • Explicitly state that the process is supported on all major OSes, and highlight any OS-specific considerations.
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 →
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 methods for base64 encoding files, but the Windows example (using certutil) is more detailed and includes additional steps (manual header removal and use of findstr). The Linux example is brief and lacks equivalent troubleshooting or manipulation guidance. Windows tools are mentioned explicitly, while Linux commands are referenced generically. The rest of the documentation uses cross-platform tools (OpenSSL, Azure CLI, kubectl), but the Windows encoding section is more prominent.
Recommendations
  • Expand the Linux base64 example to include guidance on removing headers or manipulating output, if needed, to match the detail provided for Windows.
  • Mention Linux-specific troubleshooting steps or common issues, similar to the Windows section.
  • Present Linux and Windows encoding examples side-by-side for parity.
  • Clarify that Azure CLI and kubectl commands are cross-platform and provide any OS-specific caveats if relevant.
GitHub 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 provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances of Windows bias: PowerShell is referenced for troubleshooting network issues (e.g., Invoke-WebRequest, Resolve-DnsName), Windows paths are shown in error messages, and Windows tools (RDP, remote PowerShell) are discussed. Linux-specific troubleshooting commands (such as curl, dig, or nslookup) are rarely mentioned, and Linux CLI examples are minimal. Windows tools and patterns are often mentioned first or exclusively, creating friction for Linux/macOS users.
Recommendations
  • For every PowerShell example, provide an equivalent Linux/macOS command (e.g., curl for Invoke-WebRequest, dig/nslookup for Resolve-DnsName).
  • When referencing error messages with Windows paths, clarify that Linux/macOS users may see different paths.
  • Include troubleshooting steps and commands for Linux/macOS management machines (e.g., how to check SSH folder permissions, how to test network connectivity).
  • Mention Linux/macOS remote access methods (e.g., SSH, VNC) alongside Windows RDP.
  • Ensure all CLI commands are platform-neutral and clarify any OS-specific requirements.
GitHub 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 comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstallation, and proxy configuration. However, there are several areas where Windows bias is evident: Windows examples and instructions are often presented first, Windows-specific tools (PowerShell, Group Policy, Microsoft Update, WSUS, Configuration Manager) are described in detail, and a cleanup script is only provided in PowerShell with no Linux equivalent. While Linux instructions are present and generally clear, Windows-centric tools and scripting are emphasized, and some automation guidance (e.g., stale resource cleanup) is Windows-only.
Recommendations
  • Provide Linux/bash equivalents for automation scripts, such as the stale resource cleanup PowerShell script.
  • Present Linux and Windows instructions in parallel or alternate the order to avoid 'windows_first' bias.
  • Where Windows tools (e.g., Group Policy, WSUS, Configuration Manager) are discussed, offer Linux alternatives or clarify their absence.
  • Include more examples of using Azure CLI for automation, which is cross-platform.
  • Ensure that Linux-specific troubleshooting and management scenarios are covered with equal depth.
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 →
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 instructions exclusively use Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell commands are presented first and as the only method for deploying templates, which may create friction for Linux/macOS users who prefer CLI or Bash. The use of Windows-style file paths in examples (e.g., 'D:\Azure\Templates\...') further reinforces a Windows-first bias.
Recommendations
  • Add Azure CLI deployment command examples alongside PowerShell, e.g., 'az deployment group create --resource-group <resource-group-name> --template-file <template-filename.json> --parameters <parameter-filename.json>'.
  • Include Bash shell examples for Linux/macOS users, especially for template deployment.
  • Use platform-neutral file path examples (e.g., './Azure/Templates/...') or provide both Windows and Linux path formats.
  • Explicitly mention that both Azure PowerShell and Azure CLI can be used for deployment, linking to relevant CLI documentation.
  • Consider reordering or balancing the presentation of deployment methods so that CLI and PowerShell are given equal prominence.
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 →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation consistently uses PowerShell syntax for Azure CLI commands and provides only PowerShell-based scripts (e.g., .ps1 files) for automation. There are no Bash or Linux shell examples, and no mention of Linux/macOS equivalents for the provided scripts. This creates friction for Linux/macOS users, who must adapt the examples and cannot use the automation scripts as-is.
Recommendations
  • Provide Azure CLI command examples using Bash syntax (e.g., $ az ... or az ...), not just PowerShell.
  • Offer equivalent Bash shell scripts for bulk deployment and workflow deletion, or clearly state if only PowerShell is supported.
  • Explicitly mention cross-platform compatibility for the CLI commands, and note any Windows-only limitations.
  • If the provided .ps1 scripts are Windows-only, suggest alternative approaches or tools for Linux/macOS users.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides only a Windows/PowerShell-based recovery script and instructions, with no mention of Linux or cross-platform alternatives. All recovery steps assume the use of a Windows machine and PowerShell, and the provided script is Windows-specific.
Recommendations
  • Provide equivalent recovery instructions and scripts for Linux/macOS environments, using Bash or cross-platform tools such as Azure CLI.
  • Clearly state if the recovery process is only supported on Windows, and explain why (e.g., dependency on SCVMM or Windows-only tooling).
  • If possible, offer a cross-platform version of the disaster recovery script, or document manual steps that Linux/macOS users can follow.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation exclusively provides instructions and examples for running a PowerShell script (RGCleanScript.ps1) to clean up Azure Arc workload orchestration resources. There are no examples or guidance for Linux/macOS users, such as using Bash or cross-platform alternatives. The script and its usage are presented as PowerShell-only, with no mention of compatibility or workarounds for non-Windows environments.
Recommendations
  • Clarify whether RGCleanScript.ps1 can be run with PowerShell Core (pwsh) on Linux/macOS, and provide explicit instructions for those platforms if supported.
  • If the script is Windows PowerShell-only, offer a Bash or cross-platform equivalent, or provide guidance for Linux/macOS users on how to achieve the same cleanup tasks using Azure CLI or other tools.
  • Add example commands for Linux/macOS environments, including how to install PowerShell Core if needed.
  • Mention any script dependencies or limitations regarding platform compatibility.
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 →
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-based examples and scripts for diagnostics and onboarding, with file paths and script usage patterns that are Windows-centric. There are no equivalent Bash, shell, or Linux/macOS examples for critical tasks such as onboarding, enabling diagnostics, or collecting logs. The JSON template and script instructions reference Windows file paths and PowerShell scripts exclusively, creating friction for Linux/macOS users.
Recommendations
  • Provide Bash or shell script equivalents for all PowerShell examples, especially for onboarding and diagnostics tasks.
  • Use cross-platform file path conventions in JSON templates and examples, or provide separate Linux/macOS examples.
  • Explicitly note which commands/scripts are cross-platform (e.g., az CLI) and which are Windows-only, and provide alternatives where possible.
  • Add Linux/macOS-specific instructions for running onboarding scripts, handling file paths, and collecting logs.
  • Include examples using Bash or zsh for common tasks, and clarify any OS-specific requirements.
GitHub Create Pull Request
Azure Arc Prepare the Environment for Workload Orchestration ...rc/workload-orchestration/initial-setup-environment.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 exhibits Windows bias in several areas. The example for installing kubectl uses the Windows-specific 'winget' tool, with no Linux/macOS equivalent provided. In the section on extracting ZIP files, the Bash tab uses the Windows-native 'Expand-Archive' command, which is not available on Linux/macOS, and the examples consistently use Windows-style file paths (e.g., 'C:\path\to\archive.zip'). There are no Linux/macOS-specific instructions or examples for these steps, and the documentation assumes a Windows environment for Bash usage. PowerShell examples are provided throughout, but no Linux shell (e.g., native Bash, zsh) examples for Linux/macOS users. This creates friction for non-Windows users, especially in the initial setup steps.
Recommendations
  • Provide Linux/macOS-specific instructions for installing kubectl, such as using 'apt', 'yum', 'brew', or downloading from the official Kubernetes site.
  • For extracting ZIP files, include Linux/macOS Bash commands (e.g., 'unzip archive.zip -d /path/to/workspace') and use POSIX-style file paths in examples.
  • Clarify which commands are platform-specific and offer alternatives for each major OS.
  • Add a note or section indicating supported platforms and any limitations.
  • Review all Bash examples to ensure they are cross-platform or clearly indicate when they are Windows-only.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.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 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). Bash/Linux equivalents are missing for critical troubleshooting steps, except in the 'service groups' section, where both Bash and PowerShell tabs are provided. This creates friction for Linux/macOS users, especially since many Azure CLI and Kubernetes operations are natively cross-platform.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell command examples, especially for Azure CLI, Docker, and kubectl commands.
  • Ensure that cross-platform tools (e.g., az, kubectl, docker) are demonstrated in both Bash and PowerShell contexts.
  • Where PowerShell-specific syntax is used (e.g., variable assignment, piping, Base64 encoding), offer Bash alternatives (e.g., export, echo, base64).
  • Review the troubleshooting steps to ensure Linux/macOS users can follow along without needing to translate PowerShell syntax.
  • Consider showing Bash examples first or side-by-side with PowerShell to reinforce parity.
GitHub 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 examples for Helm and Azure CLI, which are cross-platform, but in several places (e.g., setting environment variables), Windows-style commands (e.g., 'set ACR_NAME=<container-registry-name>') are shown without Linux/macOS equivalents. Additionally, the order of presenting options for creating AKS clusters lists Azure CLI, PowerShell, and Portal, with PowerShell (Windows-centric) mentioned before Portal. There are no explicit Linux/macOS-specific instructions or examples for setting environment variables or other OS-dependent steps.
Recommendations
  • Provide both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) command examples for setting environment variables, e.g., use 'export ACR_NAME=<container-registry-name>' for bash/zsh.
  • Clarify that Azure CLI commands are cross-platform and can be run on Linux/macOS terminals.
  • When listing options for creating AKS clusters, consider mentioning Azure CLI and Portal first, or explicitly note PowerShell is Windows-specific.
  • Add notes or callouts for any OS-specific differences, especially for shell commands.
  • Ensure all code blocks that are OS-dependent (e.g., environment variable setting) have both Windows and Linux/macOS variants.
GitHub Create Pull Request
Azure Arc Delete Resources in Workload Orchestration ...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Bash and PowerShell examples for every command, ensuring parity between Linux/macOS and Windows users. However, in several sections, the Bash example is presented before the PowerShell example, which is the reverse of the typical 'Windows-first' bias. No exclusive Windows tools or patterns are used, and Linux examples are not missing.
Recommendations
  • Maintain the current approach of providing both Bash and PowerShell examples for all commands.
  • Consider clarifying in the introduction that all commands are cross-platform via Azure CLI, and that both Bash and PowerShell examples are provided for user convenience.
  • Ensure that any future additions continue to provide parity for both platforms.
GitHub 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 both Azure CLI and Azure PowerShell examples for deploying dashboards, but the PowerShell section is given equal prominence to the CLI section, and PowerShell is mentioned in the overview before the CLI. There are no Linux/macOS-specific instructions or notes, but the CLI examples are cross-platform. The PowerShell section could be perceived as Windows-centric, especially since it is not clarified that Azure PowerShell is available cross-platform. No Linux-specific tools or shell examples are provided, but the CLI coverage mitigates this.
Recommendations
  • Clarify that Azure PowerShell is available on Linux/macOS, or provide a link to installation instructions for non-Windows platforms.
  • Explicitly state that Azure CLI commands work on Windows, Linux, and macOS.
  • Consider listing Azure CLI before PowerShell in the overview to avoid a Windows-first impression.
  • Optionally, provide shell script examples (e.g., Bash) for common deployment scenarios to further improve Linux parity.
GitHub Create Pull Request
Azure Arc Connect to SQL Managed Instance enabled by Azure Arc ...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation page primarily references SQL Server Management Studio (SSMS), a Windows-only tool, as the first example for connecting to SQL Managed Instance enabled by Azure Arc. While sqlcmd is mentioned and a Linux-compatible example is provided, SSMS is presented first and no Linux-native GUI tools (such as Azure Data Studio or DBeaver) are referenced. The documentation does not provide parity in client tool recommendations or examples for Linux/macOS users, but does include a cross-platform sqlcmd example.
Recommendations
  • Mention cross-platform GUI tools such as Azure Data Studio or DBeaver alongside SSMS for Linux/macOS users.
  • Provide explicit Linux/macOS connection examples (e.g., using Azure Data Studio or other SQL clients) in addition to sqlcmd.
  • Clarify that SSMS is Windows-only and suggest alternatives for Linux/macOS users.
  • Ensure that examples and instructions are not Windows-first, but rather platform-neutral or inclusive.
GitHub Create Pull Request
Azure Arc Install client tools ...b/main/articles/azure-arc/data/install-client-tools.md
Low 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 installation links for all major platforms for most tools, but there are subtle Windows biases: Windows installation links are often listed first, and there are specific notes about using cmd.exe instead of PowerShell for curl on Windows, but no equivalent Linux/macOS troubleshooting. The curl installation instructions for Linux are less explicit ("install curl package") compared to a direct link for Windows. There are also PowerShell-specific notes, but no Bash/zsh equivalents.
Recommendations
  • List installation links for Linux, macOS, and Windows in a consistent order (e.g., alphabetical or rotating which is first).
  • Provide explicit installation instructions or links for curl on Linux and macOS, not just 'install curl package'.
  • Where PowerShell-specific notes are given, consider adding Bash/zsh equivalents or clarifying when platform-specific issues may arise.
  • Ensure troubleshooting notes are balanced across platforms, not just Windows/PowerShell.
GitHub Create Pull Request
Azure Arc Data collection and reporting | Azure Arc-enabled data services ...zure-arc/data/privacy-data-collection-and-reporting.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation is generally cross-platform and does not provide command-line examples or instructions that are Windows-specific. However, in the 'Arc-enabled SQL Server' billing data example, the sample payload includes 'osType': 'Windows', 'manufacturer': 'Microsoft', and 'model': 'Hyper-V', which may give the impression that Windows is the primary or only supported platform for this scenario. There are no Linux/macOS-specific examples or explicit parity statements, and the only OS-specific reference is to Windows.
Recommendations
  • Add Linux-based examples in the billing data section, e.g., with 'osType': 'Linux', and a non-Hyper-V manufacturer/model.
  • Explicitly state that Azure Arc-enabled data services support both Windows and Linux environments where applicable.
  • If the data collection and reporting process is identical across platforms, clarify this to reassure Linux/macOS users.
  • Consider including a table or section summarizing OS/platform support for all resource types discussed.
GitHub Create Pull Request
Azure Arc Azure Arc resource bridge system requirements ...icles/azure-arc/resource-bridge/system-requirements.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation refers to Azure CLI as the required management tool and links to both general and Windows-specific installation pages, but does not clarify or provide explicit instructions/examples for Linux or macOS users. The 'Management machine requirements' section links to the Windows Azure CLI installation page and does not mention Linux or macOS, which may lead Linux users to believe Windows is required. No PowerShell or Windows-only commands are present, but the lack of Linux parity in examples and links is a minor bias.
Recommendations
  • Explicitly state that the management machine can be Windows, Linux, or macOS.
  • Provide links to Azure CLI installation instructions for all supported platforms, not just Windows.
  • Add a note or section confirming that all CLI commands work on Linux/macOS and that no Windows-specific tools are required.
  • If there are any platform-specific considerations (e.g., file paths, permissions), document them for Linux/macOS users.
GitHub 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 examples in a cross-platform manner, but there is a mild Windows bias in the authentication section. The 'Interactive browser login' is labeled as 'Windows only' and described first, while the Linux default ('Device code login') is described second. The access token section references the PowerShell cmdlet 'Get-AzAccessToken' as the only example for obtaining a token, with no Linux/CLI equivalent. Additionally, certificate authentication from the Windows certificate store is described in detail, but there is no equivalent Linux-specific guidance for certificate storage.
Recommendations
  • Reorder authentication options to present cross-platform or Linux-default methods (such as device code login) before Windows-only options.
  • When referencing PowerShell cmdlets (e.g., Get-AzAccessToken), also provide equivalent Azure CLI commands (e.g., 'az account get-access-token') for Linux/macOS users.
  • For certificate-based authentication, add Linux-specific instructions for storing and referencing certificates (e.g., using PEM files in the filesystem) and clarify any platform-specific differences.
  • Where features are Windows-only (such as using the Windows certificate store), clearly label them as such and, where possible, provide Linux/macOS alternatives or explicitly state if none exist.
GitHub Create Pull Request
Azure Arc Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge." ...e-arc/resource-bridge/includes/network-requirements.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation includes references to Windows-specific tools and services, such as 'time.windows.com' for NTP and 'sts.windows.net' for authentication, and lists Windows NTP as the default in the notes. Windows-related endpoints (e.g., login.windows.net, servicebus.windows.net) are mentioned alongside generic Azure endpoints. However, Linux-specific requirements are also present (e.g., packages.microsoft.com for Linux installation packages, log collection for Linux components, SSH as a connectivity requirement), and the documentation does not provide command-line examples or instructions that are Windows-only. The Windows bias is mostly in the listing of Windows endpoints and defaults, rather than in actionable steps or guidance.
Recommendations
  • Clarify when Windows-specific endpoints (e.g., time.windows.com) are only required for Windows deployments, and provide equivalent Linux guidance (e.g., mention typical Linux NTP servers like pool.ntp.org).
  • Where Windows is listed as the default (e.g., NTP), explicitly state Linux alternatives and when to use them.
  • Ensure parity in notes and explanations for both Windows and Linux management machines and appliance VMs.
  • If possible, provide a summary table or section that distinguishes Windows-only, Linux-only, and cross-platform requirements.
GitHub 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 ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides both Windows and Linux release notes and download links, but there is a consistent pattern of Windows being listed first in download links and feature tables. Some improvements and known issues reference Windows-specific tools (e.g., PowerShell, msiexec) and workflows, with explicit instructions for Windows installer elevation, while Linux equivalents are not always described. There are several Windows-only features or bug fixes, but Linux-only changes are also called out when present. Overall, the documentation is usable for Linux users, but the ordering and some instructions show a mild Windows bias.
Recommendations
  • Alternate the order of Windows and Linux in download links and feature tables, or present them in parallel to avoid the perception of Windows-first bias.
  • Where Windows-specific installation or troubleshooting steps are given (e.g., using msiexec or PowerShell), provide equivalent Linux instructions (e.g., using rpm, dpkg, or systemctl) when relevant.
  • Highlight Linux-only changes or known issues as clearly as Windows-only ones.
  • Consider a short section or callout for Linux/macOS users with links to relevant installation and troubleshooting guides.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Connected Machine agent connection issues ...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation covers troubleshooting for both Windows and Linux Azure Connected Machine agent installations. However, there are minor signs of Windows bias: Windows log file locations and PowerShell/Windows command syntax are mentioned first in several sections, and Windows-specific tools (e.g., PowerShell, Windows environment variables) are referenced. Linux equivalents are provided, but Windows examples and terminology often precede Linux, and some remediation steps reference Windows paths or tools before Linux alternatives.
Recommendations
  • Alternate the order of Windows and Linux examples so Linux is not consistently second.
  • Where file paths or tools are referenced, provide both Windows and Linux equivalents side-by-side.
  • Ensure remediation steps mention Linux commands and paths equally, not just as an afterthought.
  • Where PowerShell or Windows environment variables are used in examples, provide corresponding Bash/Linux shell examples.
  • Consider grouping Windows and Linux troubleshooting sections separately for clarity and parity.
GitHub Create Pull Request
Azure Arc Upgrade the Azure Arc resource bridge ...l-machine-manager/upgrade-azure-arc-resource-bridge.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation is focused on upgrading the Azure Arc resource bridge in the context of System Center Virtual Machine Manager (SCVMM), a Windows-only product. The instructions reference running commands from the SCVMM server and managing VHDX files (a Hyper-V/Windows VM disk format). All command-line examples use the Azure CLI, which is cross-platform, but the context and environment are inherently Windows-centric.
Recommendations
  • Clarify early in the article that SCVMM is a Windows-only environment, and that the instructions are intended for Windows administrators.
  • Where possible, note if any steps (such as using Azure CLI) can be performed from non-Windows machines, or if they must be run from the SCVMM server.
  • If any steps (such as managing configuration files or running Azure CLI commands) are possible from Linux/macOS, explicitly state this and provide any relevant cross-platform guidance.
  • If all steps must be performed on Windows due to SCVMM or Hyper-V dependencies, make this explicit to set expectations for non-Windows users.
GitHub Create Pull Request
Azure Arc What's new in Azure Arc-enabled VMware vSphere ...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page provides a chronological list of new features for Azure Arc-enabled VMware vSphere. While most features are platform-neutral or explicitly mention both Windows and Linux, there are a few instances where Windows-specific features or tools are mentioned first or exclusively. For example, the June 2025 entry highlights customization of Windows VMs, and the October 2024 entry lists Windows-centric tools (System Center Configuration Manager, Group Policy) before mentioning Ansible (a cross-platform tool). Azure PowerShell is also listed alongside Azure CLI and REST APIs, but not prioritized. Linux is mentioned in May 2025 for Arc agent installation, but overall, Windows tools and patterns appear before their Linux equivalents in some sections.
Recommendations
  • When listing at-scale agent installation methods, mention cross-platform tools (e.g., Ansible) before or alongside Windows-specific tools (e.g., Group Policy, SCCM).
  • Ensure Linux and macOS examples or tools are given equal prominence, especially in sections about agent installation and VM management.
  • Where possible, clarify which features are Windows-only and which are cross-platform, to help users quickly identify relevant information.
  • Add explicit Linux/macOS examples or references for VM customization and management where applicable.
GitHub Create Pull Request
Azure Arc Staging Resources Before Deployment ...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring parity for Linux/macOS and Windows users. Bash examples are consistently presented before PowerShell, and Linux-specific notes (such as removing carriage returns) are included. No Windows-only tools or patterns are used, and all commands are cross-platform (az CLI, docker, kubectl). The only minor bias is that PowerShell examples are given, but Bash is always shown first.
Recommendations
  • Continue to provide Bash and PowerShell examples side-by-side.
  • Consider clarifying that Bash examples are suitable for Linux/macOS and Windows users using WSL or Git Bash.
  • Explicitly mention that az CLI, docker, and kubectl commands are cross-platform.
  • Add a brief note at the top indicating that Bash examples are for Linux/macOS and PowerShell for Windows, for user clarity.
GitHub Create Pull Request
Azure Arc External Validation for Workload Orchestration ...zure-arc/workload-orchestration/external-validation.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Bash and PowerShell examples for every CLI operation, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash, which is a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used, and all instructions are cross-platform via Azure CLI. There are no missing Linux examples or Windows-only tools mentioned.
Recommendations
  • Maintain the current approach of providing both Bash and PowerShell examples.
  • Consider clarifying that Azure CLI commands work equally well on Linux, macOS, and Windows.
  • Optionally, alternate the order of Bash and PowerShell tabs or explicitly state that Bash is for Linux/macOS and PowerShell for Windows to reinforce parity.
GitHub Create Pull Request
Azure Arc Set Up Workload Orchestration .../workload-orchestration/initial-setup-configuration.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 all steps, but the Bash tab is presented first. Both tabs are fully fleshed out and parity is maintained in the commands. There is no exclusive use of Windows tools or patterns, and no missing Linux examples. However, the inclusion of PowerShell as the only alternative to Bash (rather than, for example, zsh or fish) may indicate a slight Windows bias. The use of the Azure CLI (az), which is cross-platform, mitigates most friction.
Recommendations
  • Ensure the Bash tab remains the default or first tab, as Bash is the most common shell for Linux/macOS users.
  • Consider clarifying in the introduction that all commands are cross-platform and that Azure CLI is supported on Windows, Linux, and macOS.
  • Optionally, add a note for macOS users that Bash commands are directly usable in Terminal.
  • If possible, provide a generic shell tab (e.g., 'Shell') to indicate compatibility with other POSIX shells.
GitHub Create Pull Request
Azure Arc Create a Solution with Multiple Dependencies with Workload Orchestration ...quickstart-solution-multiple-shared-adapter-dependency.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 every command and script section, but PowerShell examples are consistently shown immediately after Bash, and in some cases, variable naming and explanations are duplicated for PowerShell. There is no evidence of Windows-only tools or patterns being prioritized, nor are Linux equivalents missing. All CLI commands are cross-platform (Azure CLI, kubectl), and Bash is always presented first. However, the presence of PowerShell examples throughout may create a slight perception of Windows bias.
Recommendations
  • Ensure Bash and PowerShell examples are equally prominent and clearly labeled.
  • Consider adding a brief note at the start clarifying that all commands are cross-platform and that Bash is suitable for Linux/macOS users, while PowerShell is for Windows users.
  • If possible, provide a single unified CLI example where the command syntax is identical, to reduce duplication and potential confusion.
  • Review variable naming conventions to ensure they are platform-agnostic and do not favor Windows/PowerShell patterns.
GitHub Create Pull Request
Azure Arc Solution with Multiple Shared Dependencies at Different Hierarchy Levels ...oad-orchestration/tutorial-service-group-scenario-3.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 every step, ensuring parity between Linux/macOS and Windows users. However, PowerShell examples are always present and sometimes shown immediately after Bash, which may create a slight perception of Windows preference. There are no Windows-only tools or patterns; all commands use the Azure CLI and Helm, which are cross-platform. No Linux examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
  • Ensure Bash examples are always shown first, as Bash is the default shell for Linux/macOS and is also available on Windows via WSL or Git Bash.
  • Clarify in the introduction that all steps are cross-platform and that PowerShell is provided for Windows users, while Bash is suitable for Linux/macOS and also for Windows users with Bash environments.
  • Consider adding a brief note about using Bash on Windows (e.g., via WSL or Git Bash) for users who prefer Bash.
  • If possible, provide a generic 'Azure CLI' tab for steps where the syntax is identical, to reduce duplication and emphasize cross-platform parity.
GitHub Create Pull Request
Azure Arc Release Notes for Workload Orchestration ...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page provides CLI examples primarily in PowerShell syntax, especially in the May 2025 release section, and does not offer equivalent Bash or Linux shell examples for those commands. While the Azure CLI is cross-platform, showing only PowerShell syntax can create friction for Linux/macOS users. However, most other CLI instructions use Bash syntax, and there is no mention of Windows-specific tools or patterns outside of PowerShell.
Recommendations
  • For every CLI example shown in PowerShell, provide a Bash/Linux shell equivalent.
  • Clarify that Azure CLI commands work on all platforms and note any OS-specific syntax differences.
  • Use generic CLI syntax (without PowerShell backticks or variable notation) where possible, or show both Windows and Linux/macOS variants side by side.
GitHub Create Pull Request
Azure Arc Solution with a Leaf Target ...oad-orchestration/tutorial-service-group-scenario-1.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are presented before PowerShell, which is a minor 'windows_first' bias in the opposite direction (Linux-first). No Windows-specific tools or patterns are used, and all commands are cross-platform (az CLI, Helm). There are no missing Linux examples or Windows-only instructions.
Recommendations
  • No changes needed for Linux parity. The documentation already provides Bash (Linux/macOS) and PowerShell (Windows) examples for all steps.
  • If desired, clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users quickly identify their relevant section.
  • Consider explicitly mentioning that all tools used (az CLI, Helm) are cross-platform.
GitHub Create Pull Request
Azure Portal Get subscription and tenant IDs in the Azure portal ...in/articles/azure-portal/get-subscription-tenant-id.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 Azure PowerShell and Azure CLI options for programmatically retrieving subscription and tenant IDs. However, PowerShell is consistently mentioned before Azure CLI, and the PowerShell module is linked first. This ordering may subtly prioritize Windows/PowerShell users, even though Azure CLI is fully cross-platform. No Windows-only tools or patterns are used, and Linux/macOS users can complete all tasks described.
Recommendations
  • Alternate the order of PowerShell and CLI mentions, or mention Azure CLI first to emphasize cross-platform support.
  • Explicitly note that Azure CLI works on Windows, Linux, and macOS.
  • Add brief examples for both Azure PowerShell and Azure CLI commands to further clarify parity.
  • Consider linking to Azure CLI documentation before PowerShell where appropriate.
GitHub 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 capability, listing PowerShell alongside CLI. While this is a minor bias, PowerShell is primarily associated with Windows, and its mention before Bash or Linux shell scripting could subtly prioritize Windows users. However, the page does not provide actual script examples or instructions exclusive to Windows/PowerShell, and the overall content is platform-neutral, focusing on the Azure mobile app available for both iOS and Android.
Recommendations
  • When listing scripting capabilities, clarify that Azure Copilot can generate both Bash (for Linux/macOS) and PowerShell scripts, or use 'CLI and shell scripts' instead of 'CLI and PowerShell scripts'.
  • If examples are added in the future, ensure parity by providing both PowerShell and Bash examples.
  • Explicitly state that the Azure mobile app and Copilot features are available and supported on all major mobile platforms.
GitHub Create Pull Request
Container Registry Azure Container Registry Authentication Options Explained ...ontainer-registry/container-registry-authentication.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ minor_missing_linux_example
Summary
The documentation provides authentication instructions for Azure Container Registry using both Azure CLI and Azure PowerShell, with PowerShell examples and references featured throughout. While Azure CLI is cross-platform, PowerShell is primarily associated with Windows, and its examples may not be relevant for Linux/macOS users. The CLI and PowerShell examples are presented in parallel, but PowerShell is mentioned in tables and sections alongside CLI, potentially implying parity. There are no explicit Linux/macOS-specific examples (e.g., shell scripting, environment variable usage in Bash), and the 'Next steps' section links to PowerShell and CLI guides, but not to Linux/macOS-specific workflows. The documentation does mention alternative container tools like podman, which is a positive step for Linux parity.
Recommendations
  • Add explicit Bash/Linux/macOS shell examples for authentication flows, especially for scripting scenarios.
  • Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
  • Consider adding a 'Linux/macOS authentication workflow' section or linking to relevant guides.
  • Reduce prominence of PowerShell in tables and summaries unless it is equally relevant for Linux/macOS users.
  • Expand 'Next steps' to include Linux/macOS-specific getting started guides.
GitHub Create Pull Request
Container Registry Import Container Images to ACR using Azure APIs ...container-registry/container-registry-import-images.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell throughout, but does not show any Linux/macOS-specific commands, tools, or shell patterns. Azure PowerShell is featured equally alongside Azure CLI, which is cross-platform, but PowerShell is historically associated with Windows and its inclusion may suggest Windows bias. In some sections, PowerShell examples are presented immediately after CLI, and the documentation references PowerShell module installation, which is more common on Windows. No Linux/macOS-specific shell (bash/zsh) or OS-specific guidance is provided, and there are no explicit Linux-first examples.
Recommendations
  • Clarify that both Azure CLI and Azure PowerShell are cross-platform and can be used on Linux/macOS as well as Windows.
  • Add explicit bash/zsh shell examples or notes for Linux/macOS users, especially for command-line usage.
  • Mention that Azure CLI is available natively on Linux/macOS and provide installation links for those platforms.
  • Consider including troubleshooting or environment setup notes for Linux/macOS users (e.g., authentication, file paths, environment variables).
  • If PowerShell is recommended, highlight its cross-platform availability and provide installation instructions for Linux/macOS.
GitHub 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
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but Bash is presented first and is more concise. The PowerShell example is included, but it uses Unix-style commands (e.g., tr -d '\r') and does not leverage native Windows/PowerShell idioms. All other steps use Azure CLI and kubectl commands, which are cross-platform and do not exhibit Windows-specific bias. No Windows-only tools or patterns are mentioned, and Linux parity is generally maintained.
Recommendations
  • Clarify that both Bash and PowerShell examples are supported on Windows, Linux, and macOS, and indicate which environments each example is intended for.
  • Provide a native PowerShell example that does not rely on Unix utilities (e.g., 'tr'), using PowerShell's own string manipulation features.
  • Consider adding a note about running Azure CLI and kubectl commands on Linux/macOS and Windows, including any minor differences (such as file path separators or shell syntax).
GitHub Create Pull Request