230
Pages Scanned
58
Pages Flagged
230
Changed Pages
25.2%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:07
Scan Information
Started At: 2026-03-01 00:00:07
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 230
Files Completed: 230
Problematic Pages
58 issues found
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 â
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation is focused on Linux preparation for AKS Edge Essentials, but it uses Windows-specific PowerShell cmdlets (Invoke-AksEdgeNodeCommand) to configure Linux nodes. This assumes the administrator is working from a Windows environment and does not provide native Linux shell alternatives for critical steps, creating friction for Linux/macOS users.
Recommendations
- Provide equivalent Linux-native commands for sysctl configuration steps, such as using SSH or direct shell access.
- Clarify whether Invoke-AksEdgeNodeCommand is required, and if so, offer guidance for Linux/macOS users (e.g., using SSH or Azure CLI).
- Ensure all configuration steps can be performed from a Linux or macOS workstation, not just Windows/PowerShell.
- Add Linux shell examples alongside PowerShell examples where applicable.
Create Pull Request
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides command-line examples for connecting to the SQL Server instance using PowerShell syntax, specifically with the sqlcmd tool, but does not offer equivalent Linux/macOS shell examples. The use of PowerShell syntax (e.g., command blocks labeled as 'powershell') and the absence of bash or Linux shell alternatives may create friction for Linux/macOS users. Additionally, Windows-oriented command blocks are presented first and exclusively, despite the Azure Arc Data Controller being a cross-platform Kubernetes workload.
Recommendations
- Provide Linux/macOS shell (bash) examples alongside PowerShell examples, especially for commands using kubectl and sqlcmd.
- Label command blocks appropriately (e.g., 'console', 'bash', 'powershell') to clarify which platforms are supported.
- Explicitly mention that sqlcmd is available cross-platform and provide installation instructions for Linux/macOS if needed.
- Ensure that all steps can be performed on Linux/macOS, and highlight any platform-specific differences.
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 â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation frequently presents Windows-centric paths and examples first (e.g., backup file paths like C:\Backupfiles\test.bak), and omits explicit Linux/macOS equivalents for key steps such as database backup and file copying. Tools like Visual Studio Code and Azure Storage Explorer are cross-platform, but all file path and command examples default to Windows conventions, which may confuse Linux/macOS users.
Recommendations
- For every example using a Windows file path (e.g., C:\Backupfiles\test.bak), provide a Linux/macOS equivalent (e.g., /home/user/backup/test.bak) alongside.
- Explicitly mention that Visual Studio Code and Azure Storage Explorer are cross-platform, and provide links or notes for Linux/macOS installation if relevant.
- In kubectl cp examples, show both Windows and Linux/macOS source file path formats.
- Clarify that SQL Server Management Studio (SSMS) is Windows-only, and suggest Azure Data Studio or sqlcmd as alternatives for Linux/macOS users.
- Add a note in prerequisites or relevant steps indicating that all steps are supported on Linux/macOS unless otherwise stated.
Azure Arc
Data collection and reporting | Azure Arc-enabled data services
...zure-arc/data/privacy-data-collection-and-reporting.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is generally cross-platform, focusing on Azure Arc-enabled data services, which run on Kubernetes and are managed via Azure CLI. However, in the 'Arc-enabled SQL Server' billing data example, the payload includes 'osType': 'Windows', 'manufacturer': 'Microsoft', and 'model': 'Hyper-V', which are Windows-specific. There are no Linux/macOS equivalents or examples provided for this section, and Windows terminology appears first and exclusively in this context.
Recommendations
- Add Linux-based billing data examples for Arc-enabled SQL Server, showing payloads with 'osType': 'Linux', and relevant Linux VM details.
- Clarify whether the billing data structure is identical for Linux-based SQL Server instances, or note any differences.
- Where possible, provide parity in examples for both Windows and Linux environments, especially in sections where OS-specific fields are shown.
- Explicitly state if certain features or reporting fields are Windows-only, to avoid confusion for Linux users.
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation page lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and explicitly mentions PowerShell scripting support as a manageability feature. However, it also includes cross-platform tools such as Azure CLI and Visual Studio Code extension. No Linux/macOS-specific tools or examples are provided, and Windows tools are presented as standard options without Linux alternatives.
Recommendations
- Add examples or mention of Linux/macOS-compatible tools for managing SQL Managed Instance enabled by Azure Arc, such as sqlcmd, Azure Data Studio, or relevant open-source SQL management tools.
- Clarify which tools are cross-platform and which are Windows-only, especially for SSMS, SQL Server PowerShell, and SQL Server Profiler.
- Include guidance or links for Linux/macOS users on how to perform common management tasks (e.g., scripting, backup, monitoring) using supported tools.
- Consider listing Azure CLI and Visual Studio Code extension before Windows-only tools to emphasize cross-platform options.
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 are several instances of Windows bias: PowerShell is referenced for troubleshooting network issues (e.g., Invoke-WebRequest), Windows paths are shown in error messages, and Windows-specific tools (RDP, remote PowerShell) are discussed. Linux troubleshooting commands are rarely provided, and Linux equivalents for CLI operations or network diagnostics are missing. In some sections, Windows tools and patterns are mentioned first or exclusively, creating friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS equivalents for PowerShell commands (e.g., use curl or wget for HTTP/2 troubleshooting).
- Include Linux/macOS examples for CLI operations, such as collecting logs, checking DNS resolution, and network connectivity (e.g., use nslookup, dig, ping, curl).
- Mention Linux file paths and permission troubleshooting alongside Windows paths.
- Clarify when instructions are platform-specific and offer alternatives for other OSes.
- Add troubleshooting steps for common Linux/macOS issues (e.g., glibc errors, SSH folder permissions).
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent. However, Windows examples, tools, and troubleshooting steps are often presented first or exclusively (e.g., command prompt and PowerShell commands for editing config files, installer instructions for Windows). Windows-specific improvements and issues are described in detail, while Linux equivalents are sometimes missing or less emphasized. Download links and version tables consistently list Windows before Linux.
Recommendations
- Include Linux-specific troubleshooting steps and command examples alongside Windows instructions, especially in the 'Known Issues' section.
- When listing download links, alternate the order or present both platforms equally.
- Add Linux command-line examples (e.g., chmod/chown for config file permissions) where only Windows commands are given.
- Ensure parity in explanations for installer issues (e.g., provide guidance for Linux package managers or service management).
- Highlight Linux improvements and bug fixes with equal detail as Windows items.
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
windows_tools
Summary
The documentation provides authentication options for both Windows and Linux, but it introduces Windows-specific methods first and references Windows tools (such as Get-AzAccessToken) without mentioning Linux equivalents. The 'Interactive browser login' is labeled as Windows-only and described first, and certificate store authentication is only detailed for Windows. Access token acquisition is shown via PowerShell, with no Linux CLI example. Overall, Linux parity is mostly present, but Windows-specific methods and tools are prioritized or exclusively described.
Recommendations
- Present authentication options in a neutral order (not Windows-first).
- For access token acquisition, provide both PowerShell (Windows) and Azure CLI (Linux/macOS) examples (e.g., 'az account get-access-token').
- Clarify certificate-based authentication for Linux (e.g., how to use PEM/PFX files on Linux, file permissions, etc.).
- Explicitly state which authentication options are available on Linux/macOS and provide relevant examples.
- Where Windows certificate store options are described, mention Linux equivalents or clarify that they are not available.
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
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, and uninstall instructions for multiple Linux distributions. However, Windows examples and tools (such as PowerShell scripts, Microsoft Update, Group Policy, and Control Panel) are often presented first or in greater detail. The cleanup script for stale Arc resources is only provided in PowerShell, with no Linux/bash equivalent. Windows-specific management tools are discussed in depth, while Linux equivalents (e.g., using bash or shell scripts for automation) are not mentioned.
Recommendations
- Provide bash or shell script examples for resource cleanup, similar to the PowerShell script, to assist Linux users.
- Where possible, present Linux and Windows instructions in parallel or in a neutral order, rather than Windows first.
- Include references to Linux-native automation tools (e.g., cron, systemd, shell scripting) for agent lifecycle management.
- Expand guidance for Linux users on managing agent upgrades and configuration at scale, similar to the Windows Group Policy and WSUS sections.
- Consider adding notes or links for Linux users on how to automate tasks using Azure CLI or scripting.
Azure Arc
Azure Connected Machine Agent Deployment Options
.../main/articles/azure-arc/servers/deployment-options.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page presents both Linux and Windows onboarding options for the Azure Connected Machine agent, but there is a notable emphasis on Windows-specific tools and PowerShell-based methods. PowerShell is mentioned as a cross-platform option, but several onboarding methods (e.g., Windows Admin Center, Configuration Manager, Group Policy) are Windows-only and listed separately. Additionally, the PowerShell method is highlighted before Linux-native automation tools like Ansible, and Windows-specific methods are detailed more extensively.
Recommendations
- Ensure Linux-native automation tools (e.g., Bash scripts, shell commands, Ansible, Puppet, Chef) are given equal prominence and example coverage as PowerShell.
- Add explicit Linux/macOS onboarding examples for each method where possible, especially for interactive and at-scale deployments.
- Consider grouping Windows-only methods in a separate section to clarify their scope and avoid overshadowing cross-platform options.
- Where PowerShell is used as a cross-platform tool, clarify its compatibility and provide alternative Linux-native command/script examples.
- Review linked pages to ensure Linux onboarding steps are as detailed as Windows ones.
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 both Linux and Windows ARM template examples for all VM extensions, ensuring parity in template content. However, all deployment instructions and sample commands are exclusively given in PowerShell, with no Azure CLI or Bash equivalents. PowerShell is a Windows-centric tool, although it is available cross-platform. Additionally, PowerShell deployment commands are presented first and exclusively, which may create friction for Linux/macOS users who prefer Azure CLI or Bash. Minor bias is also present in the ordering of Windows examples (sometimes Windows template shown before Linux), but both OSes are covered.
Recommendations
- Add Azure CLI deployment command examples alongside PowerShell for deploying ARM templates, e.g., 'az deployment group create --resource-group <resource-group-name> --template-file <template-filename.json> --parameters @<parameter-filename.json>'.
- Explicitly state that PowerShell commands work cross-platform, but provide CLI/Bash alternatives for Linux/macOS users.
- Where possible, alternate the order of Linux and Windows template examples, or group them together to avoid implicit prioritization.
- Clarify in the prerequisites or intro that both PowerShell and Azure CLI can be used for deployment, linking to relevant docs.
Azure Arc
Recover from accidental deletion of resource bridge VM
...em-center-virtual-machine-manager/disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides recovery instructions exclusively for Windows, including a PowerShell script and Windows-centric steps. There are no Linux/macOS examples, nor is there mention of equivalent recovery scripts or procedures for non-Windows platforms. The section is titled 'Recover Arc resource bridge from a Windows machine,' and no alternative is offered for Linux users.
Recommendations
- Provide equivalent recovery instructions for Linux/macOS, including Bash or Python scripts.
- Clarify whether the recovery process is supported or unsupported on Linux/macOS platforms.
- If Windows is required, explicitly state this limitation and explain why.
- Offer guidance for Linux users, such as alternative tools or manual steps, if possible.
Azure Arc
Run command on Azure Arc-enabled servers (preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation claims support for both Windows and Linux Arc-enabled servers, but the majority of concrete examples (especially in PowerShell and REST API sections) are Windows-centric. PowerShell examples dominate, and REST API examples exclusively show Windows commands (e.g., New-NetFirewallRule), with no Linux shell or firewall (e.g., iptables, firewalld) equivalents. The Azure CLI section uses a PowerShell command as its script example, and there are references to Windows tools (e.g., .ps1 scripts, New-AzStorageBlobSASToken) without Linux alternatives. Linux-specific guidance is minimal and often relegated to notes or brief mentions.
Recommendations
- For every PowerShell example, provide a parallel Bash/shell example for Linux (e.g., using bash scripts, sh, or common Linux commands).
- In the REST API section, include Linux-focused scenarios (e.g., using iptables or ufw to configure firewall rules) alongside the Windows examples.
- In Azure CLI examples, use Linux shell scripts (e.g., echo "Hello World!" or id) as the script payload, not PowerShell.
- When referencing script files, show both .ps1 (PowerShell) and .sh (Bash) file examples.
- When discussing SAS token generation, mention az CLI equivalents (e.g., az storage blob generate-sas) for Linux users.
- Add a table or section summarizing any OS-specific limitations or differences in parameter handling.
Azure Arc
Install Arc agent at scale for your VMware VMs
...arc/vmware-vsphere/enable-guest-management-at-scale.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page provides multiple methods for installing Arc agents at scale on VMware VMs, but shows notable Windows bias. The primary automation script is PowerShell-based, with instructions for running it in PowerShell and scheduling via Windows Task Scheduler. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned exclusively, and Linux equivalents (such as Bash or cron) are not provided. Windows terminology and examples appear first and more frequently, while Linux-specific guidance is minimal and only in a single note about sudo configuration.
Recommendations
- Provide a Bash or shell script equivalent for the automation script, or clarify if the script is cross-platform.
- Include instructions for running the script on Linux/macOS, such as using cron for scheduling instead of Windows Task Scheduler.
- Add Linux/macOS-specific examples for agent installation and automation, including how to set execution permissions and run scripts.
- Ensure parity in prerequisites and troubleshooting for both Windows and Linux VMs.
- Clarify whether the helper script is PowerShell-only or can be run in other environments.
Azure Arc
Remove your VMware vCenter environment from Azure Arc
...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides detailed Windows/PowerShell instructions for running the deboarding script, including execution policy guidance and script invocation. There are no equivalent instructions for running the script on Linux or macOS, nor is there mention of cross-platform compatibility for the script. Windows steps are presented first and in greater detail, while Linux users are left without guidance for script execution.
Recommendations
- Add explicit instructions for running the deboarding script on Linux/macOS, including prerequisites (e.g., PowerShell Core, Azure CLI), script invocation, and any required permissions.
- Clarify whether the deboarding script is cross-platform (PowerShell Core compatible) or Windows-only. If Windows-only, provide a Bash or Python alternative for Linux/macOS users.
- Present Windows and Linux/macOS instructions in parallel or clearly indicate platform-specific steps.
- Include troubleshooting tips for Linux/macOS environments, such as handling script execution permissions and Azure CLI authentication.
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation exhibits Windows bias in several areas. The Bash example for extracting ZIP files uses the Windows-native Expand-Archive command and Windows file paths, which is not available on Linux/macOS. The recommended installation method for kubectl uses winget, a Windows-only package manager, with no Linux/macOS alternative provided. Throughout the page, file paths and examples default to Windows conventions. While Azure CLI and kubectl are cross-platform, the documentation does not consistently provide Linux/macOS-specific instructions or alternatives, especially for initial setup steps.
Recommendations
- Provide Linux/macOS alternatives for extracting ZIP files (e.g., 'unzip archive.zip -d /path/to/workspace').
- Offer Linux/macOS installation instructions for kubectl (e.g., using 'curl' or 'apt', 'brew', etc.), not just winget.
- Use generic or platform-neutral file paths in examples, or show both Windows and Linux/macOS paths.
- Ensure all critical steps have Linux/macOS equivalents, especially for setup and installation.
- Consider adding explicit tabs or sections for Linux/macOS users where commands differ.
Azure Arc
Perform disaster recovery operations
...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation page provides only PowerShell examples and references the onboarding script as a PowerShell script (.ps1), with no mention of Bash, Linux, or macOS equivalents. All command-line instructions and code snippets are Windows/PowerShell-centric, and there is no guidance for Linux/macOS users on how to perform the same operations. The script editing and execution steps assume a Windows environment, creating friction for non-Windows users.
Recommendations
- Provide equivalent Bash or shell script examples for Linux/macOS users, or clarify if the onboarding script is cross-platform.
- Explicitly state platform requirements for the onboarding script (e.g., if it requires PowerShell Core, which is available on Linux/macOS, or if it is Windows-only).
- Add guidance for Linux/macOS users on how to edit and run the onboarding script, including prerequisites and installation instructions for PowerShell Core if needed.
- Mention any limitations or alternative approaches for Linux/macOS users if the script or process is not fully supported.
Azure Arc
Bulk Review, Publish, and Deploy with Workload Orchestration
...es/azure-arc/workload-orchestration/bulk-deployment.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation consistently presents all CLI command examples and automation scripts using PowerShell syntax (e.g., `$rg`, `$subId`, `.ps1` scripts), and only references PowerShell scripts for bulk operations and workflow cleanup. There are no Bash or Linux/macOS shell equivalents, nor are there instructions for running these tasks on non-Windows platforms. This creates friction for Linux/macOS users, especially since Azure CLI is cross-platform.
Recommendations
- Provide all Azure CLI command examples in both PowerShell and Bash syntax, or use syntax-agnostic variable notation.
- Offer Bash (.sh) script equivalents for the referenced PowerShell scripts (bulk_deployment.ps1, workflow-delete.ps1), or clarify if the scripts are cross-platform.
- Explicitly state if the scripts are Windows-only, or provide instructions for running them on Linux/macOS.
- Add notes or tabs indicating how to perform the same tasks on Linux/macOS, including any required dependencies or differences.
Azure Arc
Clean-Up Script for Workload Orchestration
...es/azure-arc/workload-orchestration/clean-up-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation exclusively provides a PowerShell (.ps1) script for resource cleanup, with all usage examples and instructions tailored to Windows/PowerShell environments. There are no Bash, shell, or cross-platform alternatives, nor any mention of how Linux or macOS users can perform the same cleanup.
Recommendations
- Provide a Bash or cross-platform shell script equivalent to RGCleanScript.ps1, or document how Linux/macOS users can run the script (e.g., via PowerShell Core on Linux).
- Include explicit instructions or examples for running the cleanup process on Linux/macOS, such as using pwsh (PowerShell Core) or Azure CLI commands if possible.
- Clarify script requirements and compatibility (e.g., does it require Windows PowerShell, or is it compatible with PowerShell Core on all platforms?).
- If only PowerShell is supported, add a note for Linux/macOS users on how to install and use PowerShell Core to run the script.
Azure Arc
Diagnostics of Edge-Related Logs and Errors in Workload Orchestration
.../azure-arc/workload-orchestration/diagnose-problems.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. All CLI/script examples are provided exclusively in PowerShell syntax, with no Bash or Linux shell equivalents. Paths in JSON templates use Windows-style (C:\, E:\) and the onboarding scripts are referenced as PowerShell (.ps1) only. There are no instructions or examples for Linux/macOS users, even though the Azure CLI and Kubernetes tools are cross-platform. This creates friction for non-Windows users, who must adapt commands and scripts themselves.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell CLI examples (e.g., az commands with Bash syntax and environment variables).
- Use platform-neutral file paths in JSON templates, or provide examples for both Windows and Linux/macOS.
- Document onboarding steps for Linux/macOS, including how to run scripts (e.g., using Bash or Python instead of PowerShell).
- Clarify any platform requirements for scripts and tools, and link to cross-platform alternatives where available.
- If PowerShell scripts are required, offer guidance for Linux PowerShell Core users, or provide Bash alternatives.
Azure Arc
Migrate Existing Target Resources to General Availability
...s/azure-arc/workload-orchestration/migration-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only a PowerShell script (WOGAMigration.ps1) for the migration process and instructs users to run it in PowerShell, with no mention of Linux/macOS-compatible alternatives or instructions. This creates friction for non-Windows users, as PowerShell is not natively available on Linux/macOS and the script may not be cross-platform.
Recommendations
- Provide a Bash or Python script alternative for Linux/macOS users, or clarify if the PowerShell script is compatible with PowerShell Core on Linux/macOS.
- Include explicit instructions for running the migration script on Linux/macOS, including any prerequisites (e.g., installing PowerShell Core).
- Mention any limitations or required adaptations for non-Windows environments.
- If the script is Windows-only, offer guidance for Linux/macOS users to perform the migration manually or request support.
Azure Arc
Troubleshooting for Workload Orchestration
...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority
View Details â
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-line examples use PowerShell syntax and variables, even for cross-platform Azure CLI and Kubernetes tasks. There are no explicit Linux/bash equivalents for critical troubleshooting steps, except for the 'service groups' section, which provides both Bash and PowerShell tabs. Some commands (e.g., Docker, kubectl) are shown in PowerShell context, but these tools are cross-platform. This bias creates friction for Linux/macOS users, who must adapt PowerShell syntax and variable usage to their environments.
Recommendations
- Provide Bash/Linux equivalents for all troubleshooting steps, especially for Azure CLI, Docker, and kubectl commands.
- Use cross-platform variable syntax (e.g., $VAR for Bash, $var for PowerShell) or clarify variable usage for each platform.
- Where possible, avoid PowerShell-specific constructs (e.g., ConvertTo-Json, Out-File) and offer alternatives for Bash/Linux (e.g., jq, echo, cat).
- For file encoding instructions, specify cross-platform editors and commands.
- Clearly indicate which steps are platform-specific and which are cross-platform.
Azure Arc
Onboarding Scripts for Workload Orchestration
...azure-arc/workload-orchestration/onboarding-scripts.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily oriented toward Windows environments, with all onboarding scripts and examples provided exclusively in PowerShell (.ps1) format. Prerequisites reference Windows-specific tools (winget), and there are no Bash, shell, or Linux/macOS equivalents or instructions. All command-line examples and script usage assume a Windows/PowerShell context, creating friction for Linux/macOS users.
Recommendations
- Provide equivalent Bash or shell scripts for Linux/macOS users, or document how to run the onboarding process on those platforms.
- Replace or supplement 'winget' installation instructions with cross-platform alternatives (e.g., apt, yum, brew, or direct download links).
- Explicitly state if the onboarding scripts are Windows-only, or clarify cross-platform support if available.
- Add Linux/macOS command-line examples alongside PowerShell examples.
- Document any prerequisites or dependencies for non-Windows environments (e.g., PowerShell Core, Azure CLI installation on Linux/macOS).
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Medium Priority
View Details â
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 or greater prominence than Linux-native workflows. In several sections, PowerShell commands are presented as a primary method, and there is no explicit mention of Linux/macOS shell equivalents (e.g., Bash scripting for automation). The use of PowerShell-centric cmdlets (e.g., Connect-AzContainerRegistry) may not be familiar or available to Linux/macOS users. While Azure CLI is cross-platform, the documentation does not clarify this or provide explicit Bash/Linux shell examples for scripting scenarios. The 'Next steps' section also lists PowerShell before any Linux-native workflow. There are no examples using native Linux tools or shell scripting outside of Azure CLI.
Recommendations
- Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Provide Bash shell scripting examples for automation scenarios, especially where PowerShell is shown.
- Clarify that PowerShell examples are primarily for Windows users, and suggest Azure CLI for Linux/macOS.
- In 'Next steps', add links to Linux/Bash-focused getting started guides or tutorials.
- Where PowerShell cmdlets are shown, provide equivalent Bash/Azure CLI script snippets for parity.
Azure Arc
Azure Arc resource bridge system requirements
...icles/azure-arc/resource-bridge/system-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation consistently references Azure CLI installation, but in the 'Management machine requirements' section, the link for Azure CLI x64 installation points specifically to the Windows installation page. There are no explicit Linux/macOS examples or instructions, and no mention of Linux/macOS management machines, even though Azure CLI is cross-platform. The CLI commands shown are generic and not Windows-specific, but the documentation implicitly assumes Windows as the primary environment for deployment.
Recommendations
- Add explicit guidance for Linux and macOS management machines, including links to their Azure CLI installation pages.
- Clarify that the management machine can be Windows, Linux, or macOS, and provide any OS-specific requirements or considerations.
- Include example CLI commands for Linux/macOS where relevant, or note that the commands are identical across platforms.
- Ensure that references to CLI installation do not default to Windows unless the feature is Windows-only.
Azure Arc
Access Azure resources with managed identity on Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for acquiring access tokens via managed identity on Azure Arc-enabled servers. However, Windows/PowerShell instructions and output are presented first, and PowerShell is referenced in the 'Related content' section before Azure CLI. The Linux Bash example is present and complete, but Windows tools and patterns are slightly prioritized.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to ensure equal visibility.
- In 'Related content', list Azure CLI and Bash examples before or alongside PowerShell to improve parity.
- Explicitly mention that both Windows and Linux are fully supported at the top of the article.
- Where possible, provide cross-platform guidance (e.g., using Azure CLI or REST API) before platform-specific tools.
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for each command, but consistently lists Bash examples first. No Windows-specific tools or patterns are mentioned, and Linux parity is maintained throughout. There is a minor bias in the ordering of examples, but no functional impact for Linux/macOS users.
Recommendations
- Continue to provide both Bash and PowerShell examples for all commands.
- Consider clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, if not already clear.
- Ensure that any referenced scripts (e.g., 'Clean-up script') are available in both Bash and PowerShell versions, or note their compatibility.
Container Registry
Quickstart - Create Registry in Portal
...iner-registry/container-registry-get-started-portal.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for signing in to the registry, but does not show a clear Linux parity in the order of examples. Azure PowerShell is primarily a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) may create a subtle Windows bias, especially since PowerShell is presented as equally relevant. However, Docker installation instructions are provided for Mac, Windows, and Linux, and all Docker commands are platform-agnostic. There are no Windows-only tools or patterns, and Linux users can complete all tasks using Azure CLI and Docker.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- Present Azure CLI instructions first and emphasize its cross-platform nature.
- Consider removing Azure PowerShell instructions or placing them after Azure CLI as an optional path for Windows users.
- Add a note for Linux/macOS users that Azure CLI is the preferred method.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority
View Details â
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 it does mention sqlcmd and provides a cross-platform sqlcmd example, SSMS is emphasized and listed first. No Linux-native GUI tools (such as Azure Data Studio) are mentioned. The documentation does not provide Linux/macOS-specific guidance or troubleshooting, and the overall tone assumes familiarity with Windows-centric tools.
Recommendations
- Mention Azure Data Studio as a cross-platform GUI alternative to SSMS for connecting to SQL Managed Instance.
- Provide explicit examples for connecting from Linux/macOS using sqlcmd, including installation instructions if needed.
- Include troubleshooting tips for Linux/macOS users, such as firewall or network configuration differences.
- List cross-platform tools first or equally, rather than prioritizing Windows-only tools.
- Clarify that SSMS is Windows-only and suggest alternatives for non-Windows users.
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
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation provides both Linux and Windows methods for base64 encoding, but the Windows instructions (using certutil and findstr) are given after the Linux example. The Windows tools are mentioned explicitly, but Linux is presented first and the overall workflow is cross-platform. All other commands (openssl, Azure CLI, kubectl) are platform-agnostic or Linux-oriented.
Recommendations
- Clarify that certutil and findstr are Windows-specific and provide equivalent Linux/macOS commands for removing headers if needed.
- Consider grouping Linux/macOS and Windows instructions more clearly, or providing a table comparing commands for each OS.
- Explicitly mention macOS compatibility where relevant (e.g., base64, openssl).
- Add a note that Azure CLI and kubectl commands work on all platforms.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides installation instructions for client tools used with Azure Arc-enabled data services. While it includes links for Windows, Linux, and macOS for some tools, there are subtle signs of Windows bias: Windows links are listed first, PowerShell/cmd.exe is referenced for Windows-specific instructions, and Linux installation instructions for curl are less explicit. There are no Linux-specific examples or troubleshooting tips, and some notes focus on Windows shell behaviors.
Recommendations
- Present installation links for all platforms in a consistent order (e.g., alphabetical or Linux first).
- Provide explicit Linux/macOS installation instructions for curl (e.g., 'sudo apt install curl' for Ubuntu, 'brew install curl' for macOS).
- Add Linux/macOS shell usage notes where Windows-specific shell behaviors are mentioned (e.g., clarify curl usage in Bash/zsh).
- Include troubleshooting tips or version checks for Linux/macOS environments, not just Windows.
- Avoid referencing Windows-specific shells (cmd.exe, PowerShell) without providing equivalent Linux/macOS guidance.
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 â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page lists network requirements for Azure Arc Resource Bridge, but exhibits mild Windows bias. Windows-specific services (e.g., Windows NTP, sts.windows.net, login.windows.net, servicebus.windows.net) are mentioned, and Windows terminology appears in several URLs and notes. The 'Windows NTP Server' is called out specifically, with no mention of Linux NTP alternatives. Azure CLI installation is referenced, but no OS-specific guidance is given. Linux tools and patterns (e.g., Linux NTP, Linux CLI installation) are not mentioned, and Windows-related endpoints are listed before Linux equivalents. However, the documentation does reference Linux package sources (packages.microsoft.com) and log collection for Linux components, indicating some Linux support.
Recommendations
- Add explicit mention of Linux NTP servers (e.g., pool.ntp.org) alongside Windows NTP.
- Clarify that Azure CLI installation instructions apply to both Windows and Linux, or link to OS-specific guides.
- Where Windows-specific endpoints are listed (e.g., sts.windows.net, login.windows.net), clarify if Linux equivalents exist or if these are required for all OSes.
- Ensure examples and notes reference both Windows and Linux management machines, not just Windows terminology.
- Add guidance for Linux firewall/proxy configuration if only Windows tools are referenced elsewhere.
Azure Arc
Simplify network configuration requirements with Azure Arc gateway
...zure-arc/kubernetes/arc-gateway-simplify-networking.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all critical tasks. However, PowerShell examples are given equal prominence to Azure CLI, and in some sections (such as onboarding clusters), PowerShell is presented immediately after CLI. PowerShell is a Windows-centric tool, and its inclusion alongside CLI may create friction for Linux/macOS users, especially since Azure CLI is cross-platform and more commonly used outside Windows. No Linux-specific commands or shell examples (e.g., Bash scripts) are provided, but the CLI examples are sufficient for Linux/macOS users. There are minor instances where Windows/PowerShell environment variable syntax is shown alongside Linux export syntax, but no Linux-specific tools or patterns are highlighted.
Recommendations
- Consider explicitly stating that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Where environment variables are set, clarify the syntax differences between Bash (Linux/macOS) and PowerShell (Windows), or provide both syntaxes side-by-side.
- Add a brief note that Azure PowerShell is primarily for Windows users, while Azure CLI works on all platforms.
- Ensure that CLI examples are shown first and are clearly marked as the default for non-Windows environments.
- Optionally, provide Bash script examples for common tasks to further improve Linux parity.
Azure Arc
Quickstart: Connect an existing Kubernetes cluster to Azure Arc
...les/azure-arc/kubernetes/quickstart-connect-cluster.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for connecting a Kubernetes cluster to Azure Arc. Azure CLI is cross-platform, while Azure PowerShell is primarily used on Windows, though it is available for Linux/macOS. The CLI and PowerShell instructions are presented in parallel tabs throughout, but Azure PowerShell is mentioned equally and sometimes before Linux-native alternatives. There are no Linux-specific examples or shell scripts provided, and Windows/PowerShell environment variable syntax is shown alongside Bash, but not prioritized. The documentation does mention Docker for Linux/Mac/Windows and emphasizes that clusters must have Linux nodes, but overall, the bias is minor and mostly in the order and prominence of PowerShell examples.
Recommendations
- Consider clarifying that Azure CLI is the recommended, cross-platform tool for Linux/macOS users.
- Add explicit notes or links for Linux/macOS users about Azure PowerShell installation and compatibility.
- Where environment variables are set, ensure both Bash (Linux/macOS) and PowerShell (Windows) syntax are shown side-by-side, not just in separate tabs.
- Provide more Linux/macOS-specific troubleshooting tips or examples if relevant.
- If possible, add a short section at the top indicating which tool is best for which OS, to help users choose the most appropriate instructions.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation presents Windows and Linux VM extensions in separate sections, but Windows extensions are listed first and in greater detail. However, Linux extensions are also comprehensively covered, and deployment methods (Azure CLI, PowerShell, Portal, ARM templates) are presented neutrally. There are no Windows-only examples or tools mentioned exclusively, and both OSes are treated with parity in extension support.
Recommendations
- Consider alternating the order of Windows and Linux sections, or presenting them together in a unified table for direct comparison.
- Ensure that deployment examples in linked pages (not shown here) provide both Windows and Linux command-line usage.
- Explicitly state that all deployment methods (CLI, PowerShell, Portal, ARM templates) are available for both Windows and Linux extensions.
Azure Arc
Simplify Network Configuration Requirements with Azure Arc Gateway
...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
minor_windows_tools
Summary
The documentation provides both Windows (PowerShell) and Linux (Azure CLI) examples throughout, but Windows/PowerShell examples are often presented before Linux/CLI equivalents. Some instructions reference Windows-specific paths or tools (e.g., PowerShell, ProgramData), and minor notes are given for Windows PowerShell usage. However, Linux parity is generally maintained, and Linux-specific instructions (e.g., log file locations, package URLs) are included.
Recommendations
- Alternate the order of CLI and PowerShell examples so Linux users see their platform first in some sections.
- Explicitly clarify that Azure CLI commands work on both Windows and Linux, and provide Bash syntax where relevant.
- Ensure all file path references (logs, agent folders) are shown for both Windows and Linux side-by-side.
- Add brief notes for Linux users where Windows-specific instructions (e.g., PowerShell syntax, ProgramData paths) are mentioned.
- Consider including macOS-specific notes if relevant, especially for CLI usage.
Azure Arc
Automatic extension upgrade for Azure Arc-enabled servers
...e-arc/servers/manage-automatic-vm-extension-upgrade.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation covers both Windows and Linux Arc-enabled servers and provides parity in feature descriptions and Azure CLI examples. However, there is a mild Windows bias: PowerShell examples are given equal prominence to Azure CLI, and PowerShell is inherently Windows-centric (though available on Linux, it's less commonly used there). In several sections, Windows is mentioned first (e.g., 'Windows and Linux'), and PowerShell is presented as a primary management option alongside CLI, which may not reflect typical Linux administrator workflows.
Recommendations
- Clarify that Azure CLI is the recommended cross-platform tool for Linux and macOS users.
- Consider listing Azure CLI examples before PowerShell examples, or explicitly note PowerShell's cross-platform availability.
- Add brief guidance for Linux users who may not use PowerShell, such as linking to instructions for installing PowerShell on Linux if needed.
- Where possible, use 'Linux and Windows' instead of 'Windows and Linux' to avoid subtle ordering bias.
- Ensure all screenshots and portal instructions are generic and not Windows-specific.
Azure Arc
How to migrate from legacy Log Analytics agents in non-Azure environments with Azure Arc
...in/articles/azure-arc/servers/migrate-legacy-agents.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux context, but Windows-specific tools (Windows Admin Center, Windows Server Graphical Installer) are mentioned explicitly, and PowerShell is referenced before Bash. Windows deployment options are described in more detail, while Linux equivalents (such as Linux graphical installers or Linux-specific management tools) are not mentioned. The order and depth of Windows examples/tools create a mild Windows bias.
Recommendations
- Add explicit Linux deployment examples, such as using Bash scripts, Ansible, or Linux-native tools for onboarding Azure Arc.
- Mention Linux graphical installers or clarify if only command-line options are available for Linux.
- Provide parity in describing Linux management workflows (e.g., using Ansible, SSH, or other Linux-native automation tools) alongside Windows Admin Center and Group Policy.
- Ensure that PowerShell and Bash examples are given equal prominence, ideally side-by-side.
- Clarify any limitations or differences for Linux users in the deployment and management process.
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides troubleshooting guidance for both Windows and Linux, including error codes, exit codes, and log file locations. However, in the 'Agent verbose log' section, Windows examples are presented first and use PowerShell syntax, while Linux examples follow. Windows-specific tools and paths (e.g., PowerShell, %ProgramData%) are mentioned before their Linux equivalents. There is a minor bias in ordering and tool emphasis, but Linux parity is generally maintained.
Recommendations
- Alternate the order of Windows and Linux examples in sections to avoid always showing Windows first.
- Where possible, present Windows and Linux examples side-by-side for easier comparison.
- Explicitly mention Linux log file locations and commands before or alongside Windows equivalents.
- Ensure all troubleshooting steps reference both Windows and Linux paths/tools equally.
- Add clarifying notes when a tool or path is Windows-only, and provide Linux alternatives where applicable.
Azure Arc
Support matrix for Azure Arc-enabled System Center Virtual Machine Manager
...pport-matrix-for-system-center-virtual-machine-manager.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation is primarily focused on System Center Virtual Machine Manager (SCVMM), a Windows-centric technology. Windows tools and patterns (such as WinRM, Windows Management Framework, and Windows Server versions) are mentioned first and in detail. Linux support is referenced, but only as a secondary option for installing Arc agents, and Linux prerequisites are listed after Windows ones. There are minor notes about Linux workstations, but Windows is clearly the primary platform throughout.
Recommendations
- Where Linux is supported (e.g., installing Arc agents), provide Linux examples and instructions with equal prominence to Windows ones.
- Clarify any limitations or performance differences for Linux users (e.g., deployment scripts running slower on Linux), and suggest workarounds or optimizations.
- Include explicit guidance for Linux-based environments where relevant, such as network configuration or firewall rules.
- Ensure that Linux prerequisites and steps are not only listed, but also explained and linked to relevant documentation.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, 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. No critical sections are Windows-only.
Recommendations
- Continue to provide Bash and PowerShell examples side-by-side.
- Consider clarifying that Azure CLI commands work on Linux, macOS, and Windows equally.
- Optionally, add a note for macOS users if there are any OS-specific caveats (none detected here).
- If desired, alternate the order of Bash and PowerShell tabs in future documentation to avoid perceived bias.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally presents Azure Arc-enabled VMware vSphere as a cross-platform solution, supporting both Windows and Linux VMs. However, there is a subtle Windows bias: Windows-specific tools, features, and examples (such as PowerShell, Windows Server management, and Windows registry/files) are often mentioned first or in more detail than their Linux counterparts. Some links and tabs default to Windows-focused content, and automation examples reference PowerShell before other options. Linux is supported, but parity in examples and tool coverage could be improved.
Recommendations
- Ensure that all automation and configuration examples (e.g., Azure Automation, Update Manager) explicitly mention and provide parity for Linux, including Bash/CLI and Linux daemon examples where applicable.
- When listing supported tools or interfaces (e.g., CLI, PowerShell, SDKs), alternate the order or explicitly state cross-platform support.
- For links that default to Windows tabs or content, ensure Linux tabs/examples are equally visible or referenced.
- Expand on Linux-specific management scenarios (e.g., managing Linux daemons, file systems) alongside Windows registry/files.
- Highlight Linux support in self-service and automation scenarios, not just as an afterthought.
Azure Arc
Connect VMware vCenter Server to Azure Arc by using the helper script
...ere/quick-start-connect-vcenter-to-arc-using-script.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) onboarding script options and instructions. However, Windows/PowerShell examples and guidance are consistently presented first, and additional notes are given for Windows users (e.g., avoiding PowerShell ISE). The troubleshooting and retry sections also show Windows commands before Linux equivalents. There is no evidence of missing Linux examples or exclusive mention of Windows tools; Linux parity is maintained, but Windows is prioritized in ordering and detail.
Recommendations
- Alternate the order of Windows and Linux instructions, or present them side-by-side to avoid implicit prioritization.
- Add Linux-specific troubleshooting notes if relevant, similar to the PowerShell ISE note for Windows.
- Ensure screenshots and UI guidance are not Windows-centric if possible.
- Explicitly state that both Windows and Linux are equally supported at the start of relevant sections.
Azure Arc
Whats new in Azure Arc-enabled VMware vSphere
...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page lists new features for Azure Arc-enabled VMware vSphere. While most features are platform-neutral or mention both Windows and Linux, there are instances where Windows-specific features (such as customizing guest OS settings for Windows VMs and Windows Server Management) are highlighted before Linux equivalents. Windows tools like Azure PowerShell are mentioned alongside cross-platform tools, but Windows-specific management features are sometimes listed first. Overall, Linux support is present (e.g., SSH-based agent installation, Ansible playbook), but Windows examples and tools tend to be mentioned before or more prominently.
Recommendations
- Ensure Linux-specific features and tools are mentioned with equal prominence and ordering as Windows features.
- Where Windows tools (e.g., PowerShell, Group Policy) are listed, include Linux equivalents (e.g., Bash scripts, Ansible, Puppet) and clarify their applicability.
- Add explicit Linux/macOS examples where possible, especially for agent installation and VM management.
- Review ordering of features to avoid consistently listing Windows features first unless justified by usage statistics.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details â
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. However, in most sections, Bash examples are presented before PowerShell, which is a minor bias ('windows_first') in favor of Linux/macOS users rather than Windows. There are no Windows-only tools, PowerShell-heavy sections, or missing Linux examples. All CLI commands are cross-platform, and Docker/kubectl usage is universal.
Recommendations
- No significant changes needed. The current structure ensures Linux/macOS and Windows users are equally supported.
- If desired, alternate the order of Bash and PowerShell tabs in some sections to further balance presentation.
- Explicitly mention that all CLI commands are cross-platform and can be run on both Linux/macOS and Windows, except where noted.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash (Linux/macOS) examples are consistently presented before PowerShell (Windows) examples. There are no sections or features that are Windows-only, nor are there any missing Linux examples or exclusive references to Windows tools.
Recommendations
- No significant changes needed. The documentation already provides full parity for Linux/macOS and Windows users.
- Optionally, clarify in the introduction that both Bash and PowerShell examples are provided for cross-platform support.
- If desired, alternate the order of Bash and PowerShell tabs in different sections to avoid any perception of bias toward one platform.
Azure Arc
Create a Solution with Shared Adapter Dependency with Workload Orchestration
...ation/quickstart-solution-shared-adapter-dependency.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every CLI command and variable definition, but consistently presents Bash examples first. There are no Windows-specific tools or patterns used, and all commands are cross-platform via the Azure CLI. No Linux examples are missing, and Linux parity is maintained throughout. However, the presence of PowerShell examples alongside Bash may create minor friction for Linux/macOS users due to the extra content, but does not prevent task completion.
Recommendations
- Continue to provide Bash examples first, as Bash is the default shell for Linux/macOS.
- Consider grouping PowerShell examples in a collapsible section or secondary tab to reduce visual clutter for Linux/macOS users.
- Explicitly state that all commands are cross-platform and can be run on Linux, macOS, or Windows.
- Mention that Azure CLI is available on all major platforms, reinforcing Linux parity.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides CLI examples primarily using PowerShell syntax (with backticks for line continuation), especially in the May 2025 release section. Bash examples are used elsewhere, but there is inconsistency in the shell syntax. There are no Linux-specific tools or patterns mentioned, but the use of PowerShell syntax may create friction for Linux/macOS users. Azure CLI is inherently cross-platform, but the documentation could better reflect this by consistently providing Bash syntax or noting cross-platform compatibility.
Recommendations
- Standardize CLI examples to use Bash syntax (with \ for line continuation) or provide both Bash and PowerShell examples.
- Add a note clarifying that Azure CLI commands work on Windows, Linux, and macOS, and that the examples are not OS-specific.
- Avoid using PowerShell-specific syntax (backticks) unless the feature is Windows-only.
- Where possible, include explicit Bash examples for Linux/macOS users, especially in sections where PowerShell is used.
Low Priority
View Details â
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 first, followed by PowerShell. There are no Windows-specific tools or patterns, and all commands use the Azure CLI or Helm, which are cross-platform. No Linux/macOS examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Maintain the current structure, as Bash and PowerShell parity is excellent.
- Consider explicitly stating that all examples are cross-platform and that Azure CLI and Helm work on Linux, macOS, and Windows.
- If desired, alternate the order of Bash and PowerShell tabs in some sections, or clarify that Bash is shown first for consistency, not preference.
Azure Arc
Solution with Multiple Shared Dependencies at Different Hierarchy Levels
...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are included throughout, and in some sections (such as variable naming and file paths), Windows conventions (e.g., backslashes in PowerShell) are used. Bash examples are always presented first, but the presence of PowerShell examples may indicate a slight Windows bias, especially since PowerShell is primarily used on Windows, though it is also available on Linux/macOS. No Windows-only tools or patterns are used, and all commands are cross-platform (Azure CLI, Helm).
Recommendations
- Clarify that PowerShell examples are also valid for PowerShell Core on Linux/macOS, or explicitly mention cross-platform compatibility.
- Consider adding a note about file path conventions (e.g., backslash vs. forward slash) for users on different platforms.
- Ensure that Bash and PowerShell examples are equally maintained and that Bash is always presented first for Linux/macOS parity.
- If possible, provide a brief explanation for users who may be unfamiliar with PowerShell on non-Windows systems.
Azure Portal
Programmatically create Azure Dashboards
...tal/azure-portal-dashboards-create-programmatically.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides examples for deploying Azure dashboards using Azure CLI and Azure PowerShell. While Azure CLI is cross-platform and appears first, the PowerShell section is included and uses Windows-centric terminology (cmdlets, PowerShell syntax). However, there are no exclusive Windows tools or patterns, and the CLI examples are suitable for Linux/macOS users. The PowerShell section is presented after the CLI, but its inclusion may signal a slight Windows bias, especially since there is no explicit mention that PowerShell Core is cross-platform. All instructions are otherwise platform-neutral, and no critical steps are Windows-only.
Recommendations
- Clarify that Azure PowerShell can be used on Linux/macOS via PowerShell Core, not just Windows.
- Add a note that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider including Bash shell scripting examples alongside PowerShell for parity.
- Explicitly mention that all JSON templates and Azure REST API methods are platform-agnostic.
Azure Portal
Get subscription and tenant IDs in the Azure portal
...in/articles/azure-portal/get-subscription-tenant-id.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatic access, but PowerShell is consistently mentioned first and linked before Azure CLI. This ordering may subtly prioritize Windows users, as PowerShell is most commonly associated with Windows, even though Azure CLI is cross-platform. No Windows-only tools or patterns are used, and Linux/macOS users can complete all tasks via the Azure portal or Azure CLI.
Recommendations
- Alternate the order of PowerShell and Azure CLI mentions, or list Azure CLI first to highlight its cross-platform nature.
- Explicitly note that Azure CLI works on Windows, Linux, and macOS, and provide links to installation guides for all platforms.
- Consider including brief example commands for both PowerShell and Azure CLI in the main text, not just in tips.
- Ensure screenshots and instructions do not assume Windows-specific UI elements (e.g., clipboard icons or text editors).
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images into Azure Container Registry, but consistently presents Azure CLI (cross-platform) examples first. However, Azure PowerShell is highlighted as a primary tool alongside Azure CLI, which may create friction for Linux/macOS users since PowerShell is less commonly used on those platforms. No Windows-only tools or patterns are mentioned, and Linux/macOS users can complete all tasks using Azure CLI. There are no missing Linux examples, and the documentation avoids Windows-specific terminology or tools.
Recommendations
- Clarify that Azure PowerShell is optional and primarily used by Windows users, while Azure CLI is recommended for cross-platform scenarios.
- Explicitly state that Azure CLI works natively on Linux/macOS and is the preferred tool for those environments.
- Consider adding a brief note about Azure CLI's cross-platform compatibility in the 'Import images' section.
- If possible, provide a Bash shell example for Docker commands (e.g., docker login) to further reinforce Linux parity.
Container Registry
Quickstart - Create Registry - Bicep
...ainer-registry/container-registry-get-started-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides deployment instructions using both Azure CLI and PowerShell, but PowerShell is presented as a primary option alongside CLI, and references to opening PowerShell or the Visual Studio Code terminal (which defaults to PowerShell on Windows) are made. There are no explicit Linux/macOS-specific instructions or examples (e.g., Bash), and PowerShell is mentioned before any Linux shell alternatives. However, the Azure CLI instructions are cross-platform, and most tasks can be completed on Linux/macOS.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux/macOS and provide Bash-specific instructions or terminal references.
- Clarify that PowerShell is Windows-centric and suggest Bash or zsh for Linux/macOS users.
- Add a note or section for Linux/macOS users on how to open their terminal and run Azure CLI commands.
- Consider showing CLI (Bash) examples first, or at least equally, to avoid Windows-first bias.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell throughout, but consistently presents Azure CLI examples first, followed by PowerShell. There are no Windows-specific tools or patterns, and all commands are cross-platform (Azure CLI and PowerShell are available on Linux/macOS). No Windows-only tools or instructions are present, and Linux/macOS users can fully complete the tasks described.
Recommendations
- Consider explicitly mentioning that Azure CLI and Azure PowerShell are cross-platform and supported on Linux/macOS.
- Add a brief note in the prerequisites section clarifying that both Azure CLI and PowerShell examples work equally well on Linux, macOS, and Windows.
- If possible, include a short example showing Azure CLI usage in a Linux/macOS terminal to reinforce parity.
Container Registry
Push & Pull Container Image using Azure Container Registry
...-registry/container-registry-get-started-docker-cli.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication and image removal, but PowerShell examples are given equal prominence to CLI, and Windows terminology (e.g., 'PowerShell') is used throughout. There is minor Windows bias in the ordering and explicit mention of Windows tools, but Linux/macOS users are not blocked from completing any tasks. Docker commands are platform-neutral, and links to Docker installation for Linux/macOS/Windows are provided.
Recommendations
- Ensure that Azure CLI examples are shown first in all sections, as CLI is cross-platform.
- Explicitly mention that Azure CLI works on Linux/macOS/Windows, while PowerShell is primarily for Windows users.
- Consider adding Bash shell examples where appropriate, especially for scripting scenarios.
- Clarify that Docker commands are identical across platforms, and highlight any OS-specific considerations (e.g., file paths, Ctrl+C behavior).
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
missing_linux_example
Summary
The documentation is generally cross-platform, focusing on Helm and Azure CLI, which are available on Windows, Linux, and macOS. However, there are subtle Windows biases: the environment variable example uses the Windows 'set' command instead of the cross-platform 'export', and the order of Kubernetes cluster creation options lists Azure CLI, PowerShell, and Portal, with PowerShell (Windows-only) mentioned before Portal. No Linux/macOS-specific commands or examples are provided, and the 'set' command may confuse Linux/macOS users.
Recommendations
- Replace 'set ACR_NAME=<container-registry-name>' with 'export ACR_NAME=<container-registry-name>' or provide both commands for Windows and Linux/macOS.
- Explicitly state that all CLI commands are cross-platform and, where relevant, provide Linux/macOS equivalents.
- When listing options for creating AKS clusters, mention Azure CLI and Portal first, then PowerShell, or clarify PowerShell is Windows-only.
- Add a note or section for Linux/macOS users to ensure parity and reduce confusion.
Container Registry
Azure Container Registry SKU Features and Limits
...articles/container-registry/container-registry-skus.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations, such as viewing registry usage and changing registry SKU. However, PowerShell (a Windows-centric tool) is mentioned alongside Azure CLI in several places, and in the 'Show registry usage' section, PowerShell is listed before REST API and after CLI, which may subtly prioritize Windows tools. There are no Linux/macOS-specific examples or explicit mentions of Bash or shell scripting, but Azure CLI is cross-platform and generally sufficient. No critical sections are Windows-only, and Linux/macOS users can complete all tasks using Azure CLI.
Recommendations
- Ensure Azure CLI examples are always shown first, as it is cross-platform.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, while PowerShell is primarily Windows-centric.
- Consider adding Bash or shell scripting examples for common tasks, or clarify that Azure CLI commands can be run in any shell.
- Where PowerShell is referenced, add a note that Linux/macOS users should use Azure CLI.
- Avoid listing PowerShell before Azure CLI unless the task is Windows-specific.