756
Pages Scanned
194
Pages Flagged
756
Changed Pages
25.7%
% Pages Flagged
Scan Information
Started At: 2026-01-12 00:00:07
Finished At: 2026-01-12 03:05:34
Status: completed
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 756
Files Completed: 756
Problematic Pages
198 issues found
Azure Arc
Customer intent: As a system administrator managing a multi-node cluster, I want to configure Linux with HugePages and NVME modules, so that I can optimize performance for AKS Edge Essentials.
...ntainer-storage/includes/multi-node-edge-essentials.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page presents all Linux configuration steps exclusively through Windows PowerShell commands (Invoke-AksEdgeNodeCommand), without providing native Linux shell equivalents. This assumes users are operating from a Windows environment and using Windows-specific tooling to manage Linux nodes, which may not be accessible or preferred by Linux/macOS users. There are no direct bash or shell commands shown for local execution on Linux systems.
Recommendations
- Provide native Linux shell/bash command examples for each step, so users can execute them directly on Linux nodes.
- Clarify whether Invoke-AksEdgeNodeCommand is required, or if manual SSH and shell commands are supported.
- Add a section or sidebar for Linux/macOS administrators, detailing how to perform these configurations without Windows tools.
- List Linux-native methods first, or at least in parallel, to avoid implying Windows is the primary platform.
Create Pull Request
Azure Arc
Configure Machine to Manage Arc-Enabled Kubernetes Cluster
...rticles/azure-arc/edge-rag/configure-driver-machine.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation is strongly biased towards Windows, providing only a PowerShell script and instructions for configuring a Windows machine. All tooling paths, downloads, and environment variable manipulations are Windows-specific, with no mention of Linux or macOS equivalents. There are no bash or shell script examples, nor guidance for non-Windows users.
Recommendations
- Add equivalent setup instructions and sample scripts for Linux/macOS, using bash or shell scripting.
- Provide download links and installation steps for Azure CLI, kubectl, and Helm on Linux/macOS.
- Include notes on environment variable management for Linux/macOS (e.g., modifying ~/.bashrc or ~/.profile).
- Clearly state cross-platform support in the introduction and link to OS-specific guides if available.
- Ensure all critical steps (e.g., authentication, extension installation, kubeconfig setup) are covered for Linux/macOS.
Azure Arc
Sample - Enable GPU for AKS on Azure Arc
...lob/main/articles/azure-arc/edge-rag/enable-gpu-aks.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively provides a PowerShell script using Windows-specific tools (e.g., Get-PnpDevice, pnputil, Restart-Service), with no mention of Linux/macOS equivalents or instructions. There are no examples or guidance for enabling GPU on AKS Arc nodes running Linux, and the workflow assumes a Windows environment throughout.
Recommendations
- Add equivalent Linux instructions and sample scripts (e.g., using lspci, lsmod, modprobe, systemctl, and relevant NVIDIA driver installation commands).
- Clearly indicate OS requirements and whether Linux hosts are supported for this workflow.
- Provide parity in troubleshooting and validation steps for Linux (e.g., checking GPU status, driver installation, service restarts).
- If the feature is Windows-only, explicitly state this in the prerequisites and summary.
Azure Arc
Prepare AKS Cluster on Azure Local for Edge RAG Preview Enabled by Azure Arc
...ain/articles/azure-arc/edge-rag/prepare-aks-cluster.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias: all command-line examples use PowerShell syntax, and Windows-specific tools (e.g., Restart-Service, Start-sleep) are referenced exclusively. There are no Bash or Linux/macOS command examples, and instructions for configuring a management machine only mention Windows, omitting Linux/macOS guidance. This creates friction for users on non-Windows platforms and may prevent them from completing key steps without additional research.
Recommendations
- Provide equivalent Bash command examples alongside PowerShell for all steps, especially for checking GPU status and managing services.
- Include instructions and scripts for configuring a Linux/macOS machine as a driver/management host, not just Windows.
- Reference cross-platform tools and commands (e.g., systemctl for service management on Linux) where applicable.
- Clearly indicate which steps are platform-specific and offer alternatives for other operating systems.
- Ensure that Azure CLI examples use syntax compatible with Bash/zsh/fish shells as well as PowerShell.
Azure Arc
Billing service for Extended Security Updates for Windows Server 2012 through Azure Arc
...azure-arc/servers/billing-extended-security-updates.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on Windows Server 2012 and its Extended Security Updates (ESUs) via Azure Arc, with no mention of Linux or macOS systems, examples, or equivalent scenarios. All billing, licensing, and migration guidance is specific to Windows environments and tools, and there are no cross-platform considerations or instructions for non-Windows users.
Recommendations
- Clarify early in the documentation that the service is Windows-specific, and explicitly state whether Linux/macOS servers are supported or not.
- If Azure Arc supports ESUs or similar billing for Linux servers, add equivalent sections, examples, and migration guidance for those platforms.
- Provide links or references to Azure Arc documentation for Linux server management and billing, if applicable.
- Add a comparison table or FAQ addressing differences between Windows and Linux server ESU management under Azure Arc.
Azure Arc
Cloud-native licensing and cost management with Azure Arc-enabled servers
...-arc/servers/cloud-native/licensing-cost-management.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page focuses exclusively on Windows Server and SQL Server licensing options via Azure Arc, with all examples, features, and workflows centered around Windows technologies. There are no references to Linux server licensing, Linux-specific tools, or parity in cost management for non-Windows platforms. Azure portal and Microsoft Cost Management are mentioned as central tools, but only in the context of Windows/SQL workloads.
Recommendations
- Add sections describing licensing and cost management options for Linux servers connected to Azure Arc, if available.
- Provide examples and workflows for Linux server onboarding, activation, and cost tracking.
- Clarify whether pay-as-you-go or ESU-like models exist for Linux workloads, or explicitly state their absence.
- Mention Linux-compatible update and compliance tools (e.g., Azure Update Manager for Linux) and how they integrate with Arc.
- Ensure that introductory and summary sections acknowledge both Windows and Linux server scenarios.
Azure Arc
Customer intent: "As a system administrator managing Azure Arc-enabled servers, I want to understand the required endpoints for Extended Security Updates so that I can ensure proper connectivity and compliance during installation and updates."
...azure-arc/servers/includes/esu-network-requirements.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page focuses exclusively on Windows Server 2012 and SQL Server 2012, with all endpoint descriptions referencing Windows installation packages and Extended Security Updates for Windows products. There are no examples, instructions, or endpoint details for Linux or macOS systems, nor any mention of Linux equivalents or patterns. The page assumes a Windows-centric environment and omits guidance for non-Windows platforms.
Recommendations
- Include endpoint requirements and examples for Linux-based Azure Arc-enabled servers, if supported.
- Clarify whether Extended Security Updates are available for Linux workloads, and if not, explicitly state this to avoid confusion.
- Provide parity in documentation structure by listing Linux/macOS endpoints and update mechanisms where applicable.
- Add notes or links to Linux-specific guidance for Azure Arc-enabled servers.
Azure Arc
Diagnostics of Edge-Related Logs and Errors in Workload Orchestration
.../azure-arc/workload-orchestration/diagnose-problems.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits a strong Windows bias, with all command-line and scripting examples provided exclusively in PowerShell. There are no bash, shell, or Linux/macOS-specific instructions, and file paths in JSON templates use Windows-style backslashes. The onboarding and configuration scripts are referenced as PowerShell (.ps1) files, with no mention of Linux-compatible alternatives. This creates friction for Linux/macOS users, who must adapt instructions and scripts themselves.
Recommendations
- Provide equivalent bash/shell examples for all PowerShell commands, using az CLI and compatible syntax.
- Offer onboarding scripts in cross-platform formats (e.g., bash, Python) or document how to run PowerShell scripts on Linux/macOS.
- Use platform-neutral file paths in JSON templates, or provide separate examples for Windows and Linux/macOS.
- Explicitly state OS requirements for scripts and tools, and link to instructions for installing PowerShell Core on Linux/macOS if required.
- Ensure that all steps can be completed on Linux/macOS, and highlight any platform-specific limitations.
Azure Arc
License provisioning guidelines for Extended Security Updates for Windows Server 2012
...azure-arc/servers/license-extended-security-updates.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on Windows Server environments, with all examples, scenarios, and licensing guidance tailored exclusively to Windows Server 2012 and its variants. There is no mention of Linux or macOS servers, nor any cross-platform tooling or patterns. All operational details, licensing models, and migration scenarios are described in terms of Windows Server, with references to Windows-specific technologies (e.g., MAK keys, Visual Studio subscription keys). The Azure Arc context is presented only as it relates to Windows Server ESUs, and there are no Linux or non-Windows server examples, nor guidance for mixed environments.
Recommendations
- Explicitly state the scope is limited to Windows Server if Linux/macOS are not supported, to avoid confusion.
- If Azure Arc ESU licensing is relevant for Linux servers, add equivalent examples and guidance for Linux environments.
- Provide cross-platform onboarding instructions for Azure Arc, including links or references to Linux/macOS documentation.
- Where possible, mention how mixed environments (Windows and Linux servers) should be handled in terms of ESU licensing and Azure Arc management.
- If certain features or benefits are Windows-only, clearly call this out and direct Linux/macOS users to relevant alternatives.
Azure Arc
Connect machines at scale with a Configuration Manager custom task sequence
...c/servers/onboard-configuration-manager-custom-task.md
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation is heavily focused on Windows environments, specifically Microsoft Configuration Manager and Windows Installer (.msi) packages. All examples, instructions, and screenshots pertain to Windows tools and workflows, with exclusive use of PowerShell scripts and no mention of Linux/macOS equivalents or alternative deployment methods. There are no instructions or examples for onboarding Linux/macOS machines at scale using Configuration Manager or other cross-platform tools.
Recommendations
- Add equivalent instructions for deploying the Connected Machine Agent to Linux/macOS devices, including supported agent packages (e.g., .deb, .rpm) and command-line installation steps.
- Provide examples using Bash scripts or other Linux-native automation tools for connecting to Azure Arc.
- Clarify whether Configuration Manager supports Linux/macOS onboarding at scale, and if not, suggest alternative cross-platform solutions (such as Ansible, Puppet, or Azure Automation).
- Include screenshots and workflow steps for Linux/macOS environments where applicable.
- Explicitly state platform limitations and link to Linux/macOS onboarding documentation if this workflow is Windows-only.
Azure Arc
REST API Requests for the Run Command on Azure Arc-enabled Servers (Preview)
...ob/main/articles/azure-arc/servers/run-command-rest.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page is heavily biased toward Windows environments. All example scenarios, scripts, and parameters are tailored for Windows Server (specifically Windows Server 2012/R2), using PowerShell cmdlets (New-NetFirewallRule) and referencing Windows-specific tools (New-AzStorageBlobSASToken). There are no examples or guidance for Linux or macOS Arc-enabled servers, nor any mention of how to execute equivalent tasks (such as configuring firewall rules) on non-Windows platforms.
Recommendations
- Add Linux/macOS example scenarios, including REST API payloads for running bash scripts or using Linux-native firewall tools (e.g., ufw, iptables).
- Explicitly mention support for Linux/macOS Arc-enabled servers and clarify any platform-specific limitations.
- Provide sample scripts and instructions for generating SAS tokens using cross-platform tools (e.g., Azure CLI) rather than only PowerShell.
- Reorder or balance examples so that Linux and Windows are equally represented, or provide parallel examples for both platforms.
Azure Arc
How to troubleshoot delivery of Extended Security Updates for Windows Server 2012 through Azure Arc
...-arc/servers/troubleshoot-extended-security-updates.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation is exclusively focused on troubleshooting Extended Security Updates for Windows Server 2012 via Azure Arc, with all examples, commands, and procedures tailored to Windows environments. Windows-specific tools (certutil, PowerShell), file paths, and error codes are used throughout, with no mention of Linux or macOS equivalents or scenarios. The troubleshooting steps and eligibility criteria are only applicable to Windows Server, and there are no Linux/macOS instructions or parity.
Recommendations
- Explicitly state that the procedures are Windows-only and clarify if Linux/macOS are unsupported for this feature.
- If Azure Arc supports Linux servers for other features, provide links or cross-references to relevant Linux troubleshooting guides.
- Where possible, include notes or alternative procedures for Linux/macOS users, or clarify why such steps are not applicable.
- Ensure future documentation for Azure Arc features includes Linux/macOS parity where supported, with examples and troubleshooting steps for those platforms.
Azure Arc
Troubleshoot Azure Arc-enabled servers networking issues
.../articles/azure-arc/servers/troubleshoot-networking.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation focuses exclusively on troubleshooting TLS configuration issues for Windows servers. All examples and instructions use Windows-specific tools (PowerShell, Group Policy, Registry Editor) with no mention of Linux or macOS equivalents. There are no steps or guidance for Linux-based Arc-enabled servers, leaving Linux users without actionable troubleshooting information for cipher suite configuration.
Recommendations
- Add a dedicated section for Linux (and optionally macOS) troubleshooting, including how to check and configure TLS cipher suites using OpenSSL, GnuTLS, or system configuration files.
- Provide command-line examples for Linux (e.g., using openssl ciphers, editing /etc/ssl/openssl.cnf, or updating system-wide TLS settings).
- Clarify which steps are Windows-only and offer parity for other platforms where possible.
- Reference relevant Linux documentation or tools for managing TLS settings.
Azure Arc
Deliver ESUs for SCVMM VMs through Arc
...ver-esus-for-system-center-virtual-machine-manager-vms.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on Windows Server 2012/2012 R2 and System Center Virtual Machine Manager (SCVMM), both of which are Windows-only technologies. All examples, screenshots, and instructions are tailored to Windows environments, with no mention of Linux or macOS equivalents, nor any cross-platform considerations. Patch management solutions referenced are predominantly Microsoft/Windows-centric, and no Linux-specific tools or scenarios are discussed.
Recommendations
- Clarify early in the documentation that the process is only applicable to Windows Server VMs managed by SCVMM, and that Linux/macOS VMs are not supported for ESUs in this scenario.
- If Azure Arc supports ESU-like mechanisms for Linux VMs, provide a separate section or links to relevant documentation.
- Where patch management solutions are discussed, explicitly mention whether non-Windows VMs can participate, and provide examples or references for Linux patching solutions if applicable.
- Consider adding a comparison table or FAQ clarifying platform support and limitations for ESU delivery via Azure Arc.
Azure Arc
Remove your SCVMM environment from Azure Arc
...virtual-machine-manager/remove-scvmm-from-azure-arc.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits notable Windows bias, primarily through the exclusive use of Windows tools and PowerShell scripts for key operations. The deboarding script is only available for Windows/PowerShell, with no Linux equivalent or instructions for Linux-based SCVMM management servers. Windows uninstall instructions are detailed and shown first, while Linux instructions are present but limited to agent removal. Critical automation steps (deboarding) are not accessible to Linux users, and all examples and tooling assume a Windows environment.
Recommendations
- Provide a Linux-compatible deboarding script or manual CLI instructions for Linux-based SCVMM management servers.
- Offer Bash or cross-platform CLI examples alongside PowerShell commands.
- Clarify platform requirements and limitations for each step, especially where Windows-only tooling is used.
- Present Linux and Windows instructions with equal prominence, possibly using side-by-side tabs.
- Explicitly state if SCVMM management server must be Windows, or document Linux alternatives if supported.
Azure Arc
Switch to the new version of Arc-enabled SCVMM
...ual-machine-manager/switch-to-the-new-version-scvmm.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily oriented toward Windows environments, with exclusive references to System Center Virtual Machine Manager (SCVMM), a Windows-only tool. All examples and instructions assume Windows infrastructure, and links to agent management are provided only for Windows. There is no mention of Linux or macOS equivalents, nor guidance for users managing non-Windows VMs.
Recommendations
- Clarify early in the documentation that SCVMM is a Windows-only solution, and provide links or references for Linux VM management under Azure Arc if relevant.
- Include notes or sections for users who may have Linux VMs managed through Azure Arc, outlining differences or alternative steps.
- If agent management is required for Linux VMs, provide equivalent instructions and links for disconnecting and uninstalling Linux agents.
- Consider adding a comparison table or FAQ addressing cross-platform scenarios and limitations.
Azure Arc
Troubleshoot SCVMM-specific Azure Arc resource bridge deployment errors
...m-center-virtual-machine-manager/troubleshoot-scvmm.md
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page is heavily focused on troubleshooting errors related to SCVMM (System Center Virtual Machine Manager), a Windows-only tool. All error examples reference PowerShell sessions (PSSession), which are specific to Windows environments. There are no Linux or macOS troubleshooting examples, nor any mention of equivalent Linux tools or commands. This creates a clear Windows bias, as Linux users are not provided with guidance or parity for troubleshooting similar Azure Arc resource bridge deployment errors.
Recommendations
- Explicitly state that SCVMM is a Windows-only tool and clarify platform requirements at the top of the documentation.
- If Azure Arc resource bridge supports Linux-based management platforms, add troubleshooting steps and examples for those platforms.
- Provide alternative troubleshooting guidance for Linux/macOS users where applicable, or link to relevant documentation.
- Include a comparison table or section outlining differences in troubleshooting between Windows (SCVMM) and Linux-based environments.
Azure Arc
Recover from accidental deletion of resource bridge VM
...em-center-virtual-machine-manager/disaster-recovery.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation exclusively provides recovery instructions and a downloadable script for Windows, using PowerShell. There are no examples, scripts, or guidance for Linux or macOS users, nor any mention of equivalent Linux tools or procedures. The recovery process is described only from the perspective of a Windows machine, creating a significant barrier for administrators using Linux or macOS.
Recommendations
- Provide equivalent recovery instructions and scripts for Linux/macOS environments, using Bash or Python.
- Explicitly state OS requirements and offer alternatives if the script is Windows-only.
- Include cross-platform examples and clarify any OS-specific limitations.
- If recovery is only possible from Windows, explain why and suggest workarounds (e.g., using a Windows VM).
Azure Arc
Enable VM CRUD and power cycle operational ability in an SCVMM managed Arc-enabled server machine
...rtual-machine-manager/enable-virtual-hardware-scvmm.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation is heavily focused on SCVMM (System Center Virtual Machine Manager), a Windows-only virtualization management tool. All instructions and screenshots pertain to Windows environments, with no mention of Linux or macOS equivalents, nor guidance for managing non-Windows VMs. There are no examples or steps for Linux-based management tools or command-line alternatives.
Recommendations
- Clarify early in the document that SCVMM is a Windows-only tool and that these instructions do not apply to Linux or macOS hosts.
- If Azure Arc supports similar VM CRUD and power cycle operations for Linux-based hypervisors (e.g., KVM, VMware on Linux), provide parallel documentation or links.
- Include notes or sections for Linux users, outlining alternative management paths or explicitly stating limitations.
- Provide command-line examples (e.g., Azure CLI, PowerShell Core on Linux/macOS) if possible, to improve cross-platform accessibility.
Azure Arc
Onboarding Scripts for Workload Orchestration
...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily biased towards Windows, with all onboarding scripts and examples provided exclusively in PowerShell (.ps1) format. Prerequisites use Windows-specific tools (winget), and there are no Bash, shell, or Linux/macOS instructions or script equivalents. All example commands and instructions assume a Windows environment and PowerShell terminal, creating friction for Linux/macOS users.
Recommendations
- Provide equivalent Bash/shell scripts for infra and CM onboarding, or document how to run the PowerShell scripts on Linux/macOS (e.g., via pwsh).
- List Linux/macOS installation commands for prerequisites (e.g., use apt, brew, or direct downloads for Azure CLI and kubectl).
- Include explicit notes or sections for Linux/macOS users, clarifying any differences in script execution, file paths, or environment setup.
- Avoid using Windows-specific tools like winget in prerequisites, or provide alternatives for other platforms.
- Present cross-platform examples side-by-side or indicate which commands/scripts are platform-specific.
Azure Arc
Troubleshooting for Workload Orchestration
...es/azure-arc/workload-orchestration/troubleshooting.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a strong Windows bias, especially in the troubleshooting sections for workload orchestration. Most command-line examples use PowerShell syntax and Windows-specific patterns (e.g., variable assignment, piping, file encoding), with no equivalent Bash/Linux examples provided. Windows tools and conventions (such as Out-File, ConvertTo-Json, and PowerShell variable assignment) are used exclusively or explained first, making it difficult for Linux/macOS users to follow. Only the 'service groups' section provides both Bash and PowerShell tabs; all other sections are Windows-centric.
Recommendations
- Provide Bash/Linux equivalents for all PowerShell commands, especially for az CLI, kubectl, docker, and file manipulation steps.
- Avoid using Windows-specific tools (e.g., Out-File, ConvertTo-Json) without offering cross-platform alternatives (e.g., jq, echo, cat, > operator).
- Document file encoding steps for Linux/macOS (e.g., using iconv or native editors).
- Ensure variable assignment and scripting examples use syntax compatible with Bash and PowerShell, or clearly separate them.
- Present Bash/Linux examples before or alongside PowerShell to reduce perceived Windows primacy.
Azure Arc
Choosing the right Azure Arc service for machines
...nt-docs/blob/main/articles/azure-arc/choose-service.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific features (e.g., Extended Security Updates for Windows Server, SQL Server management, SCVMM integration) are highlighted, and onboarding instructions for Azure VMware Solution link to Windows-specific tabs. Automation examples mention PowerShell before Python, and there is frequent reference to Windows-centric management tools (SCVMM, Microsoft Defender for Endpoint, Azure Update Manager). Linux is mentioned as supported, but Linux-specific examples, patterns, or tools are not provided, and Windows features are often described first or in more detail.
Recommendations
- Include Linux-specific onboarding instructions and examples, especially for agent installation and management tasks.
- Provide parity in automation examples, such as showing Bash or shell scripts alongside PowerShell.
- Highlight Linux management features and scenarios with equal detail as Windows (e.g., mention Linux security and update management tools).
- Ensure links and tabs for onboarding (e.g., Azure VMware Solution) include Linux-focused documentation, not just Windows.
- Add explicit Linux compatibility notes for features that are Windows-centric (e.g., ESUs, SCVMM).
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
missing_linux_example
Summary
The documentation page is focused on preparing Linux with AKS Edge Essentials, but it uses Windows-centric tools and patterns, notably the Invoke-AksEdgeNodeCommand cmdlet, which is a PowerShell command. There are no direct Linux shell command equivalents provided for critical configuration steps, and the use of Notepad as the default text editor is a Windows-first pattern. This creates friction for Linux users who may not have access to PowerShell or Windows tools.
Recommendations
- Provide Linux-native shell command equivalents for all PowerShell cmdlets, especially for sysctl configuration.
- Recommend Linux text editors (e.g., nano, vim) alongside Notepad for editing configuration files.
- Clarify whether Invoke-AksEdgeNodeCommand can be run from Linux, or provide alternative instructions for Linux-only environments.
- Ensure all steps can be completed using standard Linux tools without requiring Windows or PowerShell.
Azure Arc
Deploy Azure Arc-enabled data services in Active Directory authentication - prerequisites
...icles/azure-arc/data/active-directory-prerequisites.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation page demonstrates a notable Windows bias. All examples and instructions for creating and managing Active Directory objects rely exclusively on Windows tools (Active Directory Users and Computers GUI, PowerShell cmdlets). There are no Linux or cross-platform alternatives provided, and the only referenced guide for setting up a domain controller is Windows-specific. This creates friction for Linux/macOS users, as they cannot follow the steps without access to a Windows environment.
Recommendations
- Include instructions for managing Active Directory objects using cross-platform tools such as ldapadd, ldapmodify, or Samba utilities.
- Provide examples using Linux command-line tools (e.g., ldap-utils) for OU and user creation.
- Reference guides for setting up Active Directory domain controllers on Linux (e.g., using Samba as an AD DC).
- Clearly indicate which steps require Windows-only tools and suggest alternatives where possible.
- Add parity in example ordering, showing Linux/macOS approaches alongside or before Windows examples.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides SQL Server connectivity examples using Powershell syntax and Windows-style command lines (e.g., sqlcmd invocation), without offering equivalent Linux/macOS shell examples. Powershell is used for kubectl exec commands, and no mention is made of Linux-specific tools or shell syntax. The order of examples and instructions implicitly favors Windows users, potentially creating friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS shell (bash/sh) examples alongside Powershell, especially for kubectl exec and sqlcmd invocations.
- Clarify that sqlcmd and kubectl can be run from any OS, and provide OS-agnostic instructions where possible.
- Explicitly mention installation and usage of sqlcmd on Linux/macOS, including any differences in path or invocation.
- Avoid labeling command blocks as 'powershell' unless the syntax is truly Powershell-specific; use 'console' or 'bash' where appropriate.
- Add notes or sections for Linux/macOS users, highlighting any OS-specific considerations.
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_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a notable Windows bias. PowerShell is the only shell used in automation examples, and the helper script is presented for use in a PowerShell terminal with Windows Task Scheduler for cron jobs. There are no Linux shell (bash) or cron job examples, and Windows-centric tools and patterns (PowerShell, Task Scheduler, Group Policy) are mentioned before or instead of Linux equivalents. Linux-specific instructions are limited to a sudo configuration note, and Linux users are left to infer how to adapt Windows-centric steps.
Recommendations
- Provide equivalent bash shell examples for running the helper script on Linux/macOS.
- Include instructions for scheduling the script via Linux cron (crontab) rather than only Windows Task Scheduler.
- Offer explicit Linux/macOS usage steps for the helper script, including permission and execution policy guidance.
- Mention Linux-native automation tools (e.g., systemd timers, cron) alongside Windows tools.
- Ensure parity in example order and detail for both Windows and Linux/macOS environments.
Azure Arc
Deploy Active Directory-integrated SQL Managed Instance enabled by Azure Arc
...c/data/deploy-active-directory-sql-managed-instance.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation shows a moderate Windows bias. Windows tools and workflows (Active Directory Users and Computers, setspn, ktpass, PowerShell scripts) are mentioned first or exclusively in critical steps such as account creation and SPN registration. While Linux alternatives (adutil, ktutil, Bash scripts) are provided for keytab generation, the initial instructions and examples often assume Windows environments and tools, potentially creating friction for Linux/macOS users.
Recommendations
- Provide explicit Linux/macOS instructions for all steps, especially for Active Directory account creation and SPN registration (e.g., using Samba tools like 'samba-tool' or 'ldapmodify').
- List Linux tools and scripts before or alongside Windows equivalents, not after.
- Include examples using Linux command-line utilities for DNS record creation and management.
- Clarify which steps require Windows-only tools and offer workarounds or alternatives for Linux/macOS users.
- Add a parity table summarizing which tools/scripts are available for each OS.
Azure Arc
Deploy Active Directory integrated SQL Managed Instance enabled by Azure Arc using Azure CLI
...ta/deploy-active-directory-sql-managed-instance-cli.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation is focused on deploying Active Directory integrated SQL Managed Instance using Azure CLI, which is cross-platform. However, there is a notable Windows bias: Active Directory (AD) is a Windows-centric technology, and the documentation does not mention or provide guidance for Linux-based equivalents (such as using Samba for AD integration or Kerberos on Linux). All examples use Windows-style DNS names and AD accounts, and there is no discussion of Linux-specific setup, troubleshooting, or alternative patterns. There are no PowerShell-only examples, but the overall context assumes a Windows AD environment and omits Linux AD integration details.
Recommendations
- Add guidance or references for integrating with Linux-based AD-compatible services (e.g., Samba, MIT Kerberos).
- Include examples or troubleshooting steps for Linux environments, such as how to generate keytabs or configure AD accounts from Linux.
- Clarify cross-platform requirements and limitations, especially for users deploying on Linux-based Kubernetes clusters.
- Provide parity in documentation for Linux/macOS users, including any OS-specific caveats or configuration steps.
Azure Arc
Tutorial – Deploy Active Directory connector in system-managed keytab mode
...eploy-system-managed-keytab-active-directory-connector.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools (e.g., 'netdom query fsmo' for identifying the Primary Domain Controller) without providing Linux/macOS alternatives. The only example for determining the PDC uses a Windows command, and no Linux/macOS method is mentioned. Windows terminology and patterns (NetBIOS, domain controller discovery) are presented first and exclusively, with no cross-platform guidance.
Recommendations
- Provide Linux/macOS equivalents for Windows-only commands, such as using 'ldapsearch' or 'samba-tool' to discover the Primary Domain Controller.
- Include examples or references for performing Active Directory-related tasks from non-Windows systems.
- Add notes or sections clarifying how Linux/macOS administrators can obtain required AD information.
- Ensure that all critical steps (e.g., domain controller discovery, account management) are documented for both Windows and Linux environments.
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
windows_tools
powershell_heavy
windows_first
Summary
The documentation lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server Profiler, SQL Server PowerShell) and highlights PowerShell scripting support as a manageability feature. Windows Authentication is explicitly called out as supported, while Linux/macOS equivalents (e.g., Bash scripting, cross-platform authentication) are not mentioned. Windows tools are listed before cross-platform options, and there are no Linux-specific examples or tool recommendations.
Recommendations
- Add explicit mention and examples of Linux/macOS management options, such as Bash scripting, and clarify support for cross-platform authentication methods.
- Include Linux-native tools (e.g., sqlcmd, Azure Data Studio on Linux) and provide parity in documentation for their usage.
- Reorder tool lists to present cross-platform tools (Azure CLI, Azure Data Studio) before Windows-only tools.
- Clarify PowerShell support on Linux (PowerShell Core) or provide Bash/CLI alternatives for common management tasks.
- Document authentication options for non-Windows environments, such as Microsoft Entra ID or certificate-based authentication.
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 demonstrates a Windows bias by providing backup examples that use Windows file paths (e.g., C:\Backupfiles\test.bak) and omitting equivalent Linux/macOS examples (e.g., /home/user/test.bak). The instructions and code samples assume a Windows environment for local file operations, and do not mention or show how Linux/macOS users should perform these steps.
Recommendations
- Add explicit Linux/macOS examples for backup file creation, using appropriate file paths (e.g., /home/user/test.bak).
- Clarify that the backup process can be performed on both Windows and Linux, and provide platform-specific instructions where needed.
- When showing kubectl cp usage, include Linux/macOS source file paths in examples.
- Mention cross-platform tools (e.g., Azure Data Studio is available on Windows, Linux, and macOS) and provide installation links for all platforms.
- Avoid showing Windows paths exclusively; present both formats side-by-side or note the difference.
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_first
missing_linux_example
Summary
The documentation page focuses on Azure Arc-enabled data services data collection and reporting. While it is generally platform-neutral, there are subtle signs of Windows bias. For example, in the billing data section for Arc-enabled SQL Server, the JSON example includes 'osType': 'Windows', 'manufacturer': 'Microsoft', and 'model': 'Hyper-V', with no equivalent Linux example. There are no explicit Linux or macOS examples, nor are Linux-specific tools or patterns mentioned. The documentation does not provide parity for Linux environments in its examples or descriptions, which may create friction for non-Windows users.
Recommendations
- Include Linux-based examples in the billing data section, such as 'osType': 'Linux', and common Linux VM models.
- Add notes or examples for Linux/macOS environments wherever platform-specific properties are shown.
- Clarify that the data collection and reporting process applies equally to Linux-based SQL Server instances, if applicable.
- Mention Linux-compatible tools or commands (e.g., Bash, shell scripts) alongside Azure CLI and Kubernetes references.
- Ensure that all JSON examples reflect both Windows and Linux scenarios where relevant.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific management features (e.g., Windows Server management, Extended Security Updates) are highlighted, and Windows tools (PowerShell, Windows registry, etc.) are mentioned before or more prominently than Linux equivalents. Examples and links often default to Windows tabs or features, and Linux-specific instructions or parity are less visible or absent. PowerShell is listed as a primary automation tool, with less emphasis on Bash or Linux-native scripting. Some links and scenarios are Windows-centric, and Linux examples are missing or less detailed.
Recommendations
- Ensure all automation and management examples include both Windows (PowerShell) and Linux (Bash, shell) equivalents.
- Highlight Linux management features and parity (e.g., Linux VM extensions, Linux daemons, Linux update management) alongside Windows features.
- Provide links and tabs for Linux-specific documentation where Windows tabs are present.
- Explicitly mention Linux support in all relevant scenarios, especially in onboarding, configuration, and monitoring sections.
- Include Linux-focused use cases and examples in the 'Next steps' and 'Supported scenarios' sections.
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation exhibits Windows bias by referencing Windows-specific tools (ktpass.exe), providing a PowerShell script, and describing password rotation using Windows GUI tools (Server Manager, Active Directory Users and Computers). While a bash script is provided for Linux/macOS users, Windows tools and workflows are mentioned first and in more detail. There is no mention of Linux-native alternatives for Active Directory password changes, and the troubleshooting section assumes familiarity with Linux commands but does not provide parity for all steps.
Recommendations
- Provide Linux/macOS equivalents for Active Directory password rotation, such as using 'samba-tool' or 'ldapmodify' for password changes.
- Present bash and PowerShell scripts side-by-side, or alternate which is shown first, to avoid Windows-first ordering.
- Explicitly mention which steps are platform-specific and provide guidance for both Windows and Linux/macOS administrators.
- Include references to Linux-native tools for keytab management and Active Directory interaction.
- Clarify which scripts and tools are required for each OS, and provide installation instructions if needed.
Azure Arc
Verify Contributor Role for Edge RAG Preview Enabled by Azure Arc
...s/azure-arc/edge-rag/prepare-contributor-permission.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation provides only PowerShell/CLI examples for verifying contributor permissions, with no mention of Linux/macOS-specific shell usage or alternative commands. The use of PowerShell syntax and lack of explicit Linux/macOS instructions creates friction for non-Windows users.
Recommendations
- Include equivalent bash/zsh examples for Linux/macOS users (e.g., show az CLI commands in a generic shell context).
- Clarify that the az CLI commands work cross-platform and provide instructions for installing the Azure CLI on Linux/macOS.
- Avoid using PowerShell-specific formatting unless necessary; use generic shell examples when possible.
- Explicitly state platform compatibility for the commands shown.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation for deploying the Edge RAG extension provides Azure CLI instructions exclusively using PowerShell syntax and variable assignment, which is specific to Windows environments. There are no Bash or Linux/macOS shell examples, and the CLI section assumes a Windows/PowerShell context. This creates friction for Linux/macOS users who may not be familiar with PowerShell or its variable syntax.
Recommendations
- Add equivalent Bash examples for all CLI commands, using Bash variable assignment and syntax.
- Explicitly state that both PowerShell and Bash can be used, and provide tabs or sections for each.
- Avoid using Windows-specific variable assignment (e.g., $var) in generic CLI instructions; use cross-platform syntax where possible.
- Include notes or guidance for Linux/macOS users regarding any differences in command usage or prerequisites.
Azure Arc
Install Networking and Observability Components for Edge RAG Preview Enabled by Azure Arc
...azure-arc/edge-rag/prepare-networking-observability.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation exclusively provides PowerShell-based examples and commands, assuming a Windows environment. There are no bash, shell, or Linux/macOS-specific instructions, and all command snippets use Windows-centric syntax and tools. This creates friction for Linux/macOS users who may need to adapt the instructions themselves.
Recommendations
- Provide equivalent bash/shell command examples for Linux/macOS users alongside PowerShell examples.
- Clarify which commands are OS-agnostic (e.g., az CLI, kubectl, helm) and which require adaptation.
- Explicitly state platform requirements and offer guidance for non-Windows environments.
- Reorder examples or present both Windows and Linux instructions in parallel to avoid Windows-first bias.
Azure Arc
Quickstart: Install Edge RAG on Azure Kubernetes Service
...ain/articles/azure-arc/edge-rag/quickstart-edge-rag.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a Windows bias in several areas. Command examples consistently use PowerShell-style variable assignment and line continuation (`$var = ...`, backticks), which are specific to Windows/PowerShell and not compatible with Bash on Linux/macOS. The instructions for editing the hosts file are exclusively for Windows (Notepad, C:\windows\System32\drivers\etc\hosts) with no mention of Linux/macOS equivalents. There are no Bash or cross-platform examples for command syntax or host file editing, making it harder for Linux/macOS users to follow along.
Recommendations
- Provide Bash-compatible command examples alongside PowerShell, using Bash variable assignment and line continuation (e.g., export VAR=..., \ for line continuation).
- Include instructions for editing the hosts file on Linux (e.g., /etc/hosts with sudo nano or vi) and macOS.
- Clarify which commands are cross-platform and which require adaptation for non-Windows environments.
- Explicitly state when a step is OS-specific and offer alternatives for other platforms.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing all command-line examples in PowerShell syntax, referencing Azure PowerShell, and omitting equivalent Linux/macOS shell (bash) examples. The use of PowerShell variables and command formatting may confuse Linux users. The instructions for deleting the namespace also use PowerShell code block formatting, despite 'kubectl' being cross-platform.
Recommendations
- Provide bash/zsh shell examples alongside PowerShell, especially for az and kubectl commands.
- Clarify that az and kubectl commands work on Linux/macOS and show example variable usage in bash.
- Use generic code block formatting for cross-platform commands like kubectl.
- Explicitly mention Linux/macOS compatibility in the instructions.
Azure Arc
Use cluster connect to securely connect to Azure Arc-enabled Kubernetes clusters.
.../main/articles/azure-arc/kubernetes/cluster-connect.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions, but PowerShell examples and syntax are included throughout, and some command blocks use PowerShell variable assignment and output. There is no explicit mention of Linux/macOS shells (e.g., Bash), and examples for setting environment variables and extracting tokens use Windows/PowerShell syntax, which may not work on Linux/macOS. The use of PowerShell is prominent, and Linux/macOS users may need to adapt commands, especially for variable assignment and token extraction.
Recommendations
- Add explicit Bash/Linux/macOS shell examples alongside PowerShell, especially for variable assignment and token extraction.
- Clarify which commands are cross-platform and which require adaptation for Linux/macOS.
- Where PowerShell syntax is shown, provide equivalent Bash syntax (e.g., export CLUSTER_NAME=...) and token extraction using base64 and jq.
- Indicate in each code block which OS/shell it is intended for.
- Consider adding a dedicated Linux/macOS tab or section for parity.
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_tools
Summary
The documentation exclusively provides PowerShell script examples and instructions, with no mention of Linux or macOS equivalents (such as Bash or shell scripts). All scripting and command-line steps assume a Windows environment, and there are no references to cross-platform or Linux-native tools for onboarding or disaster recovery operations.
Recommendations
- Provide equivalent Bash or shell script examples for Linux/macOS users, or clarify if the onboarding script is cross-platform.
- Explicitly state OS requirements and whether the onboarding script can be run on Linux/macOS (e.g., via PowerShell Core or other means).
- If the onboarding script is Windows-only, offer alternative methods or tools for Linux users, or provide guidance on using PowerShell Core on Linux.
- Include notes or sections for Linux/macOS users, addressing any differences in the recovery workflow.
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
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. Scripted deboarding instructions are provided only for Windows/PowerShell, with no Linux/macOS equivalent or guidance. The Windows uninstall instructions are presented before Linux, and PowerShell is the only scripting environment referenced for automation. This may create friction for Linux/macOS users who need to perform the same tasks.
Recommendations
- Provide a Linux/macOS-compatible deboarding script or instructions for running the script using Bash or Azure CLI.
- Include explicit steps for running the deboarding process on Linux/macOS, such as using Azure CLI or shell scripts.
- Present Windows and Linux instructions in parallel, or alternate which platform is shown first.
- Clarify whether the PowerShell script can be run cross-platform (e.g., with PowerShell Core), and provide installation guidance if so.
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation page demonstrates a moderate Windows bias in several areas. Windows-specific tools (PowerShell, .NET Framework) are explicitly listed as requirements, while Linux requirements are mentioned with less detail. Windows tools are described first and with download links, whereas Linux requirements are listed more briefly. There are no Linux command examples or references to Linux-specific tooling, and the overall tone and ordering favor Windows environments.
Recommendations
- Provide Linux command-line examples (e.g., installation commands for the Arc agent using wget and systemd).
- List Linux requirements with equal detail and provide links to relevant documentation (e.g., systemd, wget installation guides).
- Present Windows and Linux requirements in parallel, rather than listing Windows first.
- Include troubleshooting steps or common issues for Linux environments.
- Clarify that both Windows and Linux are supported and provide parity in instructions and examples.
Azure Arc
Diagnose connection issues for Azure Arc-enabled Kubernetes clusters
...les/azure-arc/kubernetes/diagnose-connection-issues.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_example_in_linux_section
Summary
The documentation is generally cross-platform, using Azure CLI and kubectl as primary tools. However, there is a notable Windows bias in the DNS troubleshooting section: Windows-specific tools (Resolve-DnsName, PowerShell) and Windows node pool examples are included, while equivalent Linux/macOS troubleshooting steps are not given the same detail or prominence. The reference to nslookup links to Windows documentation, and the PowerShell/Windows example is presented after Linux steps but with more detail.
Recommendations
- Provide parity by including Linux/macOS equivalents for DNS troubleshooting (e.g., dig, host, nslookup) and link to their documentation.
- Balance the detail between Windows and Linux/macOS examples, ensuring both are equally covered.
- When referencing commands like nslookup, link to cross-platform or Linux documentation, not just Windows.
- If showing a Windows node pool example, also show how to run similar diagnostics in a Linux node pool.
- Clarify which steps are OS-specific and which are universal.
Azure Arc
Azure Arc-enabled Kubernetes system requirements
...n/articles/azure-arc/kubernetes/system-requirements.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation presents both Azure CLI and Azure PowerShell as management tools for connecting Kubernetes clusters to Azure Arc. However, Azure PowerShell (a Windows-centric tool) is mentioned alongside Azure CLI throughout, and PowerShell examples are given equal prominence to CLI examples. There is no mention of Linux/macOS-specific shell patterns (e.g., bash, zsh), nor are there explicit instructions or examples tailored for Linux users. The documentation assumes familiarity with Windows tools and does not clarify cross-platform compatibility for PowerShell or CLI commands.
Recommendations
- Explicitly state that Azure CLI and PowerShell are cross-platform, and clarify installation steps for Linux/macOS users.
- Provide bash/zsh shell examples where appropriate, especially for Linux/macOS users.
- List Azure CLI examples before PowerShell, as CLI is more universally available across platforms.
- Add notes or links about installing and using Azure CLI and PowerShell on Linux/macOS.
- Mention that PowerShell Core is available for Linux/macOS, if relevant, and clarify any limitations.
- Include troubleshooting tips or common issues for Linux/macOS environments.
Azure Arc
Tutorial: Implement CI/CD with GitOps (Flux v2)
...es/azure-arc/kubernetes/tutorial-gitops-flux2-ci-cd.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias, primarily through the prioritization and exclusive use of Azure DevOps (a Microsoft-centric tool) in the first and most detailed CI/CD workflow section. Azure DevOps concepts, terminology, and UI navigation are described in depth before the GitHub alternative is presented. There is a lack of explicit Linux/macOS-specific instructions or examples (e.g., no mention of platform-specific CLI installation, shell differences, or alternative tooling). The documentation assumes familiarity with Azure DevOps and its UI, which is most commonly used on Windows, and does not provide parity for Linux/macOS users in terms of troubleshooting, environment setup, or alternative workflows. While the actual Kubernetes and Azure CLI commands are cross-platform, the overall workflow and examples are Windows/Microsoft ecosystem-centric.
Recommendations
- Provide explicit instructions for Linux/macOS users, including any differences in Azure CLI installation, authentication, and environment setup.
- Include troubleshooting steps relevant to Linux/macOS environments (e.g., common permission issues, shell differences).
- Offer parity in workflow detail between Azure DevOps and GitHub sections, ensuring both are equally comprehensive.
- Mention alternative CI/CD tools or patterns that are popular in Linux/macOS environments (e.g., Jenkins, GitLab CI) or clarify the cross-platform nature of Azure DevOps and GitHub Actions.
- Add notes or examples for using the CLI in bash/zsh, and clarify that all commands work on Linux/macOS unless otherwise stated.
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
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page shows a moderate Windows bias. Windows services and endpoints (e.g., time.windows.com, login.windows.net, sts.windows.net, servicebus.windows.net) are referenced frequently, and Windows NTP is mentioned as the default for time sync. There is no mention of Linux/macOS equivalents for NTP or authentication endpoints, nor are Linux-specific tools or patterns discussed. The only explicit Linux reference is for package downloads, but no Linux/macOS-specific configuration guidance or examples are provided.
Recommendations
- Include Linux/macOS equivalents for services such as NTP (e.g., pool.ntp.org) and authentication endpoints.
- Provide examples or notes for configuring outbound/inbound connectivity on Linux/macOS management machines, not just Windows.
- Clarify whether endpoints like login.windows.net, sts.windows.net, and servicebus.windows.net are required for Linux/macOS, or if alternatives exist.
- Add explicit instructions or references for Linux/macOS users where configuration or tooling may differ.
- Balance references to Windows and Linux tools/services throughout the documentation.
Azure Arc
What's new in Azure Arc-enabled VMware vSphere
...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page shows a mild Windows bias: Windows-specific features (e.g., customizing Windows VM guest OS settings, Windows Server Management, Extended Security Updates for Windows Server/SQL Server) are highlighted, and Windows tools (PowerShell, System Center Configuration Manager, Group Policy) are mentioned explicitly for agent installation, often before Linux equivalents. Linux-specific details are less frequent and sometimes only briefly referenced (e.g., SSH-based agent install). Some sections lack explicit Linux parity or examples.
Recommendations
- Add equivalent Linux/macOS examples and tooling references wherever Windows tools (PowerShell, Group Policy, SCCM) are mentioned.
- Ensure Linux agent installation methods (e.g., Ansible, SSH, shell scripts) are described in equal detail and order as Windows methods.
- Highlight Linux-specific management features and cost benefits where applicable, not just Windows Server features.
- Where features are Windows-only (e.g., Extended Security Updates), clarify Linux support status.
- Alternate the order of Windows and Linux examples to avoid implicit prioritization.
Azure Arc
Troubleshoot Azure Arc resource bridge issues
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. Many troubleshooting steps and command-line examples are either Windows-centric or presented in a way that assumes a Windows environment. PowerShell is referenced for troubleshooting HTTP/2 issues, and Windows paths (e.g., C:\Program Files) are used in error messages. Linux-specific troubleshooting is limited, and Linux command examples are either missing or mentioned only as an afterthought. The GLIBC error is the only section that directly addresses Linux users, but most CLI and troubleshooting flows assume Windows or do not provide explicit Linux alternatives.
Recommendations
- Provide Linux/macOS equivalents for all PowerShell and Windows command examples (e.g., curl, wget, nslookup, dig, etc.).
- Include Linux-specific troubleshooting steps and error messages where relevant, especially for CLI installation, file paths, and permissions.
- When referencing file paths or environment variables, show both Windows and Linux/macOS formats.
- Avoid presenting Windows/PowerShell examples first; alternate or parallelize examples for both platforms.
- Expand on Linux-specific requirements and common issues (e.g., permissions, package dependencies, proxy configuration).
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
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively provides instructions and examples for running a PowerShell script (RGCleanScript.ps1) to clean up Azure resources. All usage examples are in PowerShell syntax, with no mention of Linux/macOS alternatives, such as Bash scripts or cross-platform usage. The script itself is a Windows-centric tool, and there is no guidance for Linux users on how to execute the script or whether it works with PowerShell Core on non-Windows platforms.
Recommendations
- Provide explicit instructions for running the script on Linux/macOS, including whether PowerShell Core (pwsh) is supported.
- Add Bash or shell script alternatives for users who do not use PowerShell.
- Clarify cross-platform compatibility of RGCleanScript.ps1 and note any prerequisites for non-Windows environments.
- Include Linux/macOS command examples alongside PowerShell examples.
- Consider distributing a platform-agnostic script (e.g., Python, Bash) if possible.
Azure Arc
Overview of the Azure Connected Machine agent
...blob/main/articles/azure-arc/servers/agent-overview.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation provides a reasonably balanced overview of the Azure Connected Machine agent for both Windows and Linux. However, there is a notable Windows-first bias in several sections: Windows installation details are presented before Linux, Windows-specific tools (MSI installer, Group Policy, NT SERVICE accounts) are described in detail, and some troubleshooting tips reference Windows concepts (antivirus exclusion, service rights) without Linux equivalents. Linux installation is covered, but with less detail on system integration and troubleshooting. Examples and commands are mostly generic, but Windows-specific patterns (service accounts, security groups) are explained more thoroughly than their Linux counterparts.
Recommendations
- Present Windows and Linux installation details in parallel or alternate order to avoid Windows-first perception.
- Provide equivalent Linux troubleshooting tips (e.g., SELinux/AppArmor exclusions, systemd service rights) where Windows Group Policy is discussed.
- Expand on Linux-specific system integration details, such as user/group management, permissions, and service configuration.
- Include Linux-first examples or highlight Linux-specific considerations where relevant.
- Ensure parity in the depth of explanation for both platforms, especially regarding post-install artifacts, service management, and security configuration.
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
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific issues, tools, and troubleshooting steps are described in detail, often before or without Linux equivalents. Windows installer instructions reference PowerShell and Command Prompt, while Linux installation and troubleshooting steps are not provided. Windows download links are direct MSI files, while Linux links redirect to another page. Several bug fixes and features are marked as Windows-only, and Windows terminology (e.g., 'Run as administrator', 'msiexec') is used without Linux parallels.
Recommendations
- Provide equivalent Linux troubleshooting instructions (e.g., how to run the installer with elevated privileges, common Linux installation issues).
- Include direct Linux download links alongside Windows MSI links for parity.
- When describing issues or fixes, mention Linux equivalents or explicitly state if not applicable.
- Add Linux/macOS command-line examples where PowerShell/Windows commands are shown.
- Balance the order of presentation so that Linux and Windows are treated equally (e.g., alternate which platform is listed first).
Azure Arc
Programmatically deploy and manage Azure Arc Extended Security Updates licenses
...les/azure-arc/servers/api-extended-security-updates.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively discusses licensing for Windows Server 2012 and Windows Server 2012 R2, with all examples and API payloads targeting Windows workloads. There are no Linux-specific examples, nor any mention of Linux or macOS equivalents for license management, even though Azure Arc supports hybrid scenarios including Linux. The Azure CLI example is generic and cross-platform, but all parameter values and context are Windows-centric.
Recommendations
- Clarify in the introduction that the instructions and APIs are specific to Windows Server ESU licensing, and note whether Linux workloads require or support similar licensing operations.
- If Azure Arc supports ESU or comparable lifecycle management for Linux, provide equivalent examples and API payloads for Linux machines.
- Add a section explicitly stating the scope is Windows-only if Linux is not supported, to avoid confusion for cross-platform administrators.
- If Linux is supported, include Linux-specific parameter values, examples, and any differences in workflow.
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The endpoint list documentation contains a notable number of endpoints that are Windows-specific or reference Windows services (e.g., windowsupdate.com, powershellgallery.com, windows.net, time.windows.com). The ordering of endpoints also places Windows-related endpoints and services before Linux-specific ones, such as linuxgeneva-microsoft.azurecr.io. There are no explicit Linux/macOS examples or references, and the documentation implicitly assumes familiarity with Windows services and patterns.
Recommendations
- Add a section clarifying which endpoints are relevant for Linux/macOS environments and which are Windows-only.
- Provide guidance or examples for Linux/macOS users, such as how to verify connectivity to these endpoints using Linux tools (e.g., curl, wget, dig).
- Reorder the endpoint list to group by platform relevance (Windows, Linux, cross-platform) or alphabetically to avoid implicit prioritization.
- Explicitly mention that some endpoints are only required for Windows-based Arc-enabled servers, if applicable.
Azure Arc
Simplify Network Configuration Requirements with Azure Arc Gateway
...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided for all command-line tasks, and Windows-specific instructions (such as log file locations and prerequisites) are often mentioned before or in more detail than Linux equivalents. While Linux is supported and referenced (e.g., log file paths, package URLs), Linux-specific examples and parity in instructions are sometimes lacking or less prominent. Windows tools and scenarios (e.g., Windows Admin Center, Windows OS Update Extension) are highlighted, and Windows terminology appears first in several sections.
Recommendations
- Provide explicit Linux shell (bash) command examples alongside PowerShell, especially for onboarding, configuration, and removal tasks.
- Ensure Linux prerequisites and scenarios are described with equal detail as Windows (e.g., mention Linux update manager equivalents, Defender for Linux, etc.).
- List Linux log file locations and troubleshooting steps with the same prominence as Windows.
- Avoid listing Windows scenarios and tools first; alternate or group by OS where possible.
- Include Linux-specific onboarding script generation and agent installation instructions.
- Clarify when instructions or commands are OS-agnostic versus OS-specific.
Azure Arc
Deploy Azure Monitor agent on Arc-enabled servers
...es/azure-arc/servers/azure-monitor-agent-deployment.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page describes deployment methods for the Azure Monitor Agent on Arc-enabled servers, claiming support for both Windows and Linux. However, it demonstrates bias by referencing PowerShell as a primary management tool, listing it before Azure CLI, and omitting explicit Linux-specific examples or tools (such as Bash or shell scripts). The documentation does not provide parity in examples or guidance for Linux/macOS users, and the workflow descriptions lean toward Windows-centric patterns.
Recommendations
- Add explicit Linux/macOS examples for each deployment method, such as Bash scripts or shell commands.
- Reference Linux-native tools (e.g., Bash, shell scripting) alongside PowerShell, and clarify which tools are recommended for each OS.
- Where PowerShell is mentioned, also mention Bash or other Linux-native alternatives, and provide example commands for both.
- Ensure that Azure CLI examples are shown before or alongside PowerShell, as CLI is cross-platform.
- Include a table or section summarizing OS-specific instructions, highlighting differences and best practices for Linux users.
Azure Arc
Cloud-native governance and policy with Azure Arc-enabled servers
...es/azure-arc/servers/cloud-native/governance-policy.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by focusing on Windows-centric scenarios (e.g., password policies, Windows Firewall, RDP ciphers), referencing Windows-specific tools (Group Policy, RSoP, gpresult), and mapping Azure Policy initiatives to Windows security baselines. There are no explicit examples or mentions of Linux/macOS policy enforcement, nor are Linux-specific settings or tools discussed.
Recommendations
- Include examples of Azure Policy auditing and enforcement for Linux servers (e.g., SSH configuration, Linux firewall rules, PAM password policies).
- Discuss how Azure Policy interacts with Linux configuration management tools (such as Ansible, Chef, or native DSC for Linux).
- Reference Linux equivalents to Windows tools (e.g., show how compliance can be checked via Linux command-line tools or logs).
- Provide parity in describing built-in policies for Linux, not just Windows (e.g., mention policies for systemd services, SELinux/AppArmor, etc.).
- Clarify whether Azure Policy machine configuration supports Linux/macOS, and if so, provide usage details.
Azure Arc
Identity and access management with Azure Arc-enabled servers
...cles/azure-arc/servers/cloud-native/identity-access.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric identity management patterns (Active Directory, Group Policy, LAPS) and tools before mentioning Linux equivalents. Examples for remote access and management are primarily described in the context of Windows (Remote Desktop, AD domain-join), with Linux access (SSH) mentioned only briefly and without detail. There are no Linux-specific examples or tools discussed for identity management, and the documentation assumes familiarity with Windows administration concepts.
Recommendations
- Provide Linux-specific examples for identity and access management, such as how to join Linux servers to Azure Arc and authenticate using Microsoft Entra ID.
- Include detailed instructions for SSH access to Linux servers, including role assignment and authentication flows.
- Mention Linux-native tools and patterns for local account management and password rotation, such as using sssd, PAM, or other open-source solutions.
- Balance the order of presentation so that Linux and Windows scenarios are introduced with equal prominence.
- Add troubleshooting and best practices sections for Linux environments.
Azure Arc
Cloud-native inventory and resource organization with Azure Arc-enabled servers
...s/azure-arc/servers/cloud-native/inventory-resource.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page frequently references Windows-centric tools and organizational patterns (Active Directory, SCCM, Group Policy Objects, Windows Server versions) as analogies for Azure concepts. Examples and comparisons are almost exclusively drawn from Windows environments, with no mention of Linux equivalents (such as LDAP, systemd, or Linux inventory tools). There are no Linux/macOS-specific examples or references, and Windows terminology is used as the primary frame of reference throughout.
Recommendations
- Include analogies and comparisons to Linux organizational tools (e.g., LDAP, FreeIPA, systemd units, Ansible inventory) alongside Active Directory and SCCM.
- Provide examples of resource queries or inventory management for Linux servers (e.g., finding all Ubuntu servers, tracking package changes).
- Mention Linux/macOS server management patterns when discussing tagging, grouping, and inventory (e.g., how tags can mimic labels in Linux or metadata in cloud-init).
- Balance references to Windows tools with equivalent open-source or Linux-native solutions.
- Add explicit examples showing how Azure Arc supports Linux/macOS servers, including screenshots or command-line queries relevant to those platforms.
Azure Arc
Cloud-native server management with Azure Arc-enabled servers
...in/articles/azure-arc/servers/cloud-native/overview.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-centric tools (Active Directory Group Policy, SCCM, MECM, WSUS, PowerShell remoting, RDP) as the primary on-premises management paradigms being replaced by Azure Arc, with Linux equivalents (such as Ansible, Chef, SSH, cron, yum/apt) not mentioned. Windows management concepts and tools are described first and in greater detail, while Linux-specific management patterns are absent. Examples and analogies are tailored to users familiar with Microsoft/Windows environments, which may create friction for Linux administrators.
Recommendations
- Explicitly mention Linux management tools and patterns (e.g., SSH, Ansible, Chef, cron, yum/apt) as paradigms that Azure Arc can unify or replace.
- Provide Linux-specific examples and analogies alongside Windows ones, such as how Azure Policy relates to Linux configuration management.
- Clarify that Run Command supports both PowerShell and Bash scripts, and give examples for each.
- Include references to Linux patching workflows and how Azure Update Manager integrates with them.
- Balance the introductory narrative to address both Windows and Linux administrators equally.
Azure Arc
Cloud-native patch management with Azure Arc-enabled servers
...les/azure-arc/servers/cloud-native/patch-management.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. Windows tools such as WSUS and SCCM are mentioned first and exclusively as traditional patch management solutions, with no Linux equivalents referenced. Hotpatching is described only for Windows Server, and examples for patching workflows and maintenance windows use Windows-centric terminology and analogies. Linux support is acknowledged, but Linux-specific tools, patterns, or examples are sparse and appear later in the document. There are no concrete Linux workflow examples or references to common Linux patch management tools (e.g., apt, yum, zypper) outside of agent updates.
Recommendations
- Include references to traditional Linux patch management tools (e.g., apt, yum, zypper, Landscape, Spacewalk) alongside WSUS/SCCM when discussing legacy approaches.
- Provide explicit Linux patching workflow examples, such as scheduling updates using Azure Update Manager for Ubuntu or RHEL servers.
- Add Linux-specific scenarios for pre/post event scripts (e.g., using shell scripts to stop/start services, snapshot LVM volumes, etc.).
- Clarify hotpatching support for Linux (if available), or explicitly state its absence.
- Balance the order of presentation so that Linux and Windows are treated equally in examples and tool references.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page primarily provides CLI examples using PowerShell syntax (backticks for line continuation, variable notation like $rg), which is specific to Windows environments. There are no equivalent Bash or Linux/macOS shell examples, and PowerShell is used exclusively in the only explicit code sample for configuration management. This creates friction for Linux/macOS users who may not be familiar with PowerShell syntax or conventions.
Recommendations
- Provide Bash shell equivalents for all CLI examples, using standard Bash line continuation (\) and variable notation (e.g., $rg without backticks).
- Clearly indicate which examples are for Windows/PowerShell and which are for Bash/Linux/macOS.
- Add a note or section explaining cross-platform CLI usage, including any differences in command syntax or environment setup.
- Ensure that future examples alternate or show parity between Windows and Linux/macOS usage.
Azure Arc
Next steps for cloud-native server management with Azure Arc-enabled servers
.../articles/azure-arc/servers/cloud-native/next-steps.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by mentioning Windows-specific tools (Windows Admin Center, Configuration Manager, WSUS, GPOs) exclusively or before any Linux equivalents. Examples and onboarding instructions are focused on Windows environments, with no explicit mention of Linux onboarding methods, tools, or configuration management solutions. This creates friction for Linux users seeking parity in guidance.
Recommendations
- Add explicit onboarding instructions and examples for Linux servers, such as using shell scripts, cloud-init, or Ansible for agent deployment.
- Mention Linux-native configuration management tools (e.g., systemd, cron, Ansible, Chef, Puppet) alongside Windows tools like GPOs.
- Provide patch management examples for Linux (e.g., using Azure Update Manager with apt/yum/zypper) and clarify how Azure Arc supports Linux patching.
- Include links to Linux-specific documentation or community resources for Azure Arc.
- Ensure that examples and tool references are presented in a platform-neutral order, or alternate between Windows and Linux examples.
Azure Arc
Cloud-native scripting and task automation with Azure Arc-enabled servers
...-arc/servers/cloud-native/scripting-task-automation.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools (RDP, PowerShell, SCCM, Task Scheduler) are mentioned first and in detail, while Linux equivalents (SSH, cron) are referenced briefly or only in passing. Examples and workflows are described primarily from a Windows perspective, with limited explicit Linux scripting or automation examples. The page lacks concrete Linux-specific examples and patterns, and the language often assumes familiarity with Windows administration.
Recommendations
- Provide explicit Linux-focused examples (e.g., using Bash scripts, cron jobs, Linux package managers) alongside Windows/PowerShell examples.
- Mention Linux-native tools and patterns (such as cron, systemd, SSH, shell scripting) with equal prominence to Windows tools.
- Ensure that example workflows and automation scenarios are described for both Windows and Linux environments.
- Add sample scripts for Linux (e.g., Bash) demonstrating Run Command, SSH, and automation tasks.
- Clarify cross-platform support and any differences in capabilities or limitations between Windows and Linux Arc-enabled servers.
Azure Arc
Azure Connected Machine Agent Deployment Options
.../main/articles/azure-arc/servers/deployment-options.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page lists deployment options for both Linux and Windows, but Windows-specific tools and methods (e.g., Windows Admin Center, Group Policy, Configuration Manager, PowerShell) are given dedicated sections and examples, while Linux-specific tools (such as Ansible) are mentioned only once and not highlighted equivalently. Windows methods are more numerous and detailed, and PowerShell is referenced as a cross-platform method but is primarily associated with Windows. Windows-specific onboarding options are listed after the general table, giving Windows users more tailored guidance.
Recommendations
- Add Linux-specific onboarding methods and tools (e.g., shell scripts, cloud-init, systemd units, or Linux-native configuration management tools like Chef/Puppet) to match the Windows-specific options.
- Provide Linux-first or Linux-equivalent examples for each onboarding method, especially for at-scale deployments.
- Clarify which PowerShell methods are cross-platform and provide explicit Bash or shell script alternatives for Linux users.
- Balance the number of Windows and Linux-specific onboarding options, or clearly indicate parity where possible.
- Consider listing Linux-specific methods before or alongside Windows-specific ones to avoid implicit prioritization.
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
windows_tools
powershell_heavy
Summary
The documentation provides both Windows and Linux instructions for managing the Azure Connected Machine agent, but Windows examples and tooling are frequently presented first and in greater detail. Windows-specific tools (e.g., Group Policy, WSUS, Configuration Manager, Control Panel, Msiexec, PowerShell) are described extensively, while Linux instructions are more concise and generic. Some advanced automation and enterprise scenarios (such as update management) are covered only for Windows, with no Linux equivalents discussed.
Recommendations
- Present Linux and Windows instructions in parallel, or alternate which platform is shown first in each section.
- Add equivalent Linux automation guidance for enterprise scenarios (e.g., using Ansible, Chef, or native package manager automation for updates and configuration).
- Expand Linux sections to include troubleshooting, logging, and advanced management comparable to Windows (e.g., systemd service management, package pinning, automated upgrades).
- Where Windows-specific tools are mentioned (Group Policy, WSUS, Configuration Manager), provide Linux alternatives or note that these are Windows-only.
- Include more Linux shell scripting examples for bulk operations, similar to PowerShell scripts provided for Windows.
Azure Arc
Customer intent: "As a network administrator, I want to configure secure outbound connectivity for the Azure Connected Machine agent so that I can ensure proper communication with Azure Arc while adhering to my organization's security policies."
...les/azure-arc/servers/includes/network-requirements.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and terminology (e.g., Windows Admin Center, Windows installation package, Windows TLS configuration) are mentioned first or exclusively in several places. While Linux is referenced (e.g., Linux installation package, OpenSSL), examples and troubleshooting guidance are more detailed for Windows, and Windows tools are often listed before their Linux equivalents. Linux-specific troubleshooting and configuration guidance is minimal or absent.
Recommendations
- Provide Linux-specific troubleshooting and configuration guidance, especially for TLS/cipher suite setup and verification.
- Include Linux command-line examples (e.g., using openssl or curl) for endpoint connectivity checks and TLS validation.
- Ensure parity in extension and agent management instructions for Linux, not just Windows.
- Mention Linux tools (such as systemd, journalctl, iptables, firewalld) where Windows tools are referenced.
- Present Linux and Windows examples side-by-side, or alternate which platform is listed first.
- Clarify proxy and firewall configuration steps for Linux environments, not just general statements.
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
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias in its deployment instructions. All command-line deployment examples use Azure PowerShell, with no equivalent Azure CLI or Bash examples provided. The PowerShell commands are presented as the sole method for deploying ARM templates, which may create friction for Linux/macOS users who typically use Azure CLI or Bash. Additionally, file path examples use Windows-style paths (e.g., D:\Azure\Templates), and the deployment workflow references PowerShell repeatedly. While ARM template JSON samples are provided for both Linux and Windows extensions, the operational instructions and command-line tooling are Windows-centric.
Recommendations
- Add equivalent Azure CLI deployment commands for ARM template deployment, with Linux/macOS shell syntax.
- Include Linux-style file path examples (e.g., /home/user/Azure/Templates) alongside Windows paths.
- Explicitly state that deployment can be performed from Linux/macOS using Azure CLI, and provide links or examples.
- Present both PowerShell and CLI examples side-by-side, or clarify which platforms each method supports.
- Consider mentioning Bash or shell scripting options for automation.
Azure Arc
Authenticate against Azure resources with Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally presents Windows and PowerShell examples before Linux and Bash equivalents, and references PowerShell as the primary tool for access policy assignment. Images and walkthroughs are Windows-first, and PowerShell is mentioned more frequently than Azure CLI or Bash. Linux instructions are present but often appear after Windows steps, and some links and examples default to Windows tools.
Recommendations
- Present Windows and Linux examples side-by-side or alternate which comes first in each section.
- Include Azure CLI and Bash examples wherever PowerShell is referenced, especially for access policy assignment and resource management.
- Ensure images and walkthroughs are provided for both Windows and Linux environments.
- Reference Linux and Windows tools equally in prerequisites and next steps.
- Explicitly mention macOS compatibility where relevant, or clarify if steps are applicable to macOS.
Azure Arc
Enable VM Extensions Using the Azure CLI (Windows and Linux)
...articles/azure-arc/servers/manage-vm-extensions-cli.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. Most command examples for enabling and updating VM extensions use PowerShell-specific syntax (e.g., 'powershell.exe' and PowerShell cmdlets in the Custom Script Extension), and several extension examples are Windows-only (Antimalware, DatadogWindowsAgent). There are no equivalent Linux shell or script examples, and Linux-specific extensions are mentioned only in passing or as alternatives in a single command. The examples and explanations prioritize Windows tools and patterns, making it harder for Linux/macOS users to follow or adapt the instructions.
Recommendations
- Provide Linux shell/bash script examples for the Custom Script Extension (e.g., using 'bash -c' or a Linux command in 'commandToExecute').
- Include examples for Linux-specific extensions (e.g., DependencyAgentLinux, KeyVaultForLinux) with relevant settings.
- Clearly distinguish between Windows-only and Linux-only extensions in the documentation.
- Alternate the order of examples, or provide parallel examples for both platforms.
- Add notes or tables summarizing extension compatibility with OS types.
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
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (Windows Admin Center, Windows Server Graphical Installer) are mentioned explicitly for Azure Arc deployment, while Linux equivalents are not described. Windows deployment options are listed before cross-platform or Linux-native tools (e.g., Bash, Ansible). There are no Linux-specific examples or guidance, and the standalone Azure Monitor Agent installation section only covers Windows clients, omitting Linux client scenarios.
Recommendations
- Add explicit Linux deployment examples and workflows, such as using Bash scripts, systemd, or package managers (apt, yum) for agent installation.
- Include Linux-native management tools (e.g., Cockpit, SSH, cloud-init) where relevant, alongside Windows Admin Center.
- Provide parity in standalone agent installation instructions for Linux client machines, not just Windows.
- Ensure that cross-platform options (e.g., Bash, Ansible) are described in detail and presented before or alongside Windows-specific tools.
- Clarify which steps and tools are applicable to both Windows and Linux, and highlight any OS-specific requirements.
Azure Arc
How to modernize server management from Configuration Manager to Azure Arc
...icles/azure-arc/servers/modernize-server-management.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation generally emphasizes cross-platform support, but several sections display Windows bias. Windows licensing and onboarding steps are described first and in detail, while Linux onboarding is not covered. Windows-specific tools (Scheduled Task, Windows Server Software Assurance) are mentioned without Linux equivalents. Examples and onboarding instructions focus on Windows, and there are no Linux-specific step-by-step examples or references to Linux-native tools or patterns.
Recommendations
- Add explicit onboarding instructions for Linux servers, including recommended automation methods (e.g., systemd timers, cron jobs) for agent installation.
- Provide Linux-specific examples and references alongside Windows ones, especially for initial connection, configuration, and management tasks.
- Mention Linux licensing considerations and clarify any differences in pricing or support for Linux environments.
- Ensure that tool references (e.g., Scheduled Task) are paired with Linux equivalents (e.g., cron, systemd) and that examples are presented in parallel.
- Highlight any Linux-specific features or limitations in Azure Arc and related services.
Azure Arc
Connect machines from Azure Automation Update Management
...zure-arc/servers/onboard-update-management-machines.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation describes onboarding both Windows and Linux machines to Azure Arc via Automation Update Management, but operational details and examples are Windows-centric. Runbook names and references (e.g., Add-UMMachinesToArc, Add-UMMachinesToArcWindowsChild) use PowerShell-style naming conventions, and instructions for verifying job status reference Azure PowerShell before CLI or Linux-native tools. No explicit Linux command-line examples or Linux-specific troubleshooting steps are provided, and Windows terminology appears first throughout.
Recommendations
- Provide explicit Linux command-line examples (e.g., Bash, shell commands) alongside or before Windows/PowerShell examples.
- Clarify that runbooks and automation steps support both Windows and Linux, and show sample output or logs from Linux systems.
- Include Linux-native tools or CLI alternatives for job status verification and troubleshooting.
- Balance terminology and example order so Linux users see their platform represented equally.
Azure Arc
How to organize and inventory servers using hierarchies, tagging, and reporting
...ticles/azure-arc/servers/organize-inventory-servers.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation describes organizational and inventory features for Azure Arc-enabled servers, claiming support for both Windows and Linux. However, examples and tool references (Azure CLI, PowerShell, ARM templates) are generic or Windows-centric, with no explicit Linux/macOS command-line examples or workflows. The order and phrasing tend to mention Windows tools and patterns before Linux equivalents, and there are no Linux-specific considerations or examples provided.
Recommendations
- Add explicit Linux/macOS command-line examples (e.g., Bash, shell scripts) alongside PowerShell examples.
- Clarify cross-platform compatibility for tools like Azure CLI and ARM templates, and provide usage notes for Linux/macOS environments.
- Include screenshots or walkthroughs from Linux systems where relevant.
- Mention any Linux-specific tagging or reporting considerations, such as differences in metadata collection or onboarding steps.
Azure Arc
How to evaluate Azure Arc-enabled servers with an Azure virtual machine
...-arc/servers/plan-evaluate-on-azure-virtual-machine.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides both Windows and Linux instructions, but Windows examples and tools (PowerShell, Windows-specific agent links) are often presented first or in more detail. Some steps (like firewall configuration) offer more explicit Windows guidance, while Linux instructions sometimes refer users to external documentation. Windows VM deployment is mentioned before Linux, and the agent download link for Windows is highlighted before Linux. The overall flow and examples tend to favor Windows users, with Linux users occasionally needing to consult distribution-specific docs.
Recommendations
- Alternate the order of Windows and Linux instructions to avoid always presenting Windows first.
- Provide equally detailed, step-by-step Linux instructions for all major distributions, not just Ubuntu and Red Hat/SLES.
- Include direct links to Linux agent packages for all supported distributions, similar to the Windows Download Center link.
- Offer example commands for common Linux firewall tools (iptables, nftables) with persistent configuration guidance.
- Ensure Linux VM deployment links are correct and equally prominent as Windows VM links.
- Where instructions say 'consult your documentation,' provide concrete examples or links for popular distributions.
Azure Arc
Azure CLI Requests for the Run Command on Azure Arc-enabled Servers (Preview)
...lob/main/articles/azure-arc/servers/run-command-cli.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by exclusively providing examples that use PowerShell syntax (e.g., 'Write-Host Hello World!') and omitting any Linux shell script examples. The only script shown is PowerShell-specific, and there is no mention of Bash, sh, or other Linux scripting patterns. The related content also highlights PowerShell before REST, reinforcing the Windows-first approach.
Recommendations
- Include Linux shell script examples (e.g., Bash, sh) alongside PowerShell examples for each command.
- Explicitly state that both Windows and Linux Arc-enabled servers are supported, and clarify any differences in script execution.
- Add notes or sections describing how to run Bash scripts and handle Linux-specific output or errors.
- Ensure that documentation does not assume PowerShell as the default scripting language.
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
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page references both Windows and Linux support, but the examples and guidance are oriented toward Windows-centric tools (PowerShell, Azure CLI) and do not provide Linux-specific examples or mention Linux shell scripting. The order of presentation and linked next steps prioritize Windows/PowerShell, and there is no demonstration of Linux workflows or shell commands.
Recommendations
- Add explicit Linux shell (bash/sh) script examples for Run command usage.
- Include guidance on running Linux-specific administrative tasks (e.g., apt/yum updates, firewall-cmd, systemctl) via Run command.
- Ensure parity in documentation structure: present Windows and Linux examples side-by-side or alternate order.
- Clarify any OS-specific limitations or differences in Run command behavior.
- Link to Linux-focused documentation or tutorials where appropriate.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell Desired State Configuration is presented as the foundational technology for Azure Machine Configuration, with no mention of Linux equivalents (such as Ansible, Chef, or native Linux DSC implementations). Windows Admin Center (WAC) is described in detail as a remote management tool, while no comparable Linux management tool is discussed. Windows-specific roles and patterns (WAC, PowerShell, Remote Desktop) are described before or in more detail than Linux/SSH scenarios. Although SSH access for Linux is covered, the overall framing and examples prioritize Windows technologies and workflows.
Recommendations
- Include examples or references to Linux-native configuration management tools (e.g., Ansible, Chef, or Linux DSC) alongside PowerShell DSC.
- Provide parity in remote management tooling by mentioning or recommending Linux equivalents to Windows Admin Center, such as Cockpit or Webmin.
- Balance the order and depth of examples: present SSH/Linux scenarios before or alongside Windows Admin Center scenarios.
- Clarify that Azure Machine Configuration supports both Windows and Linux, and provide explicit Linux command-line examples where relevant.
- Add troubleshooting or usage notes for Linux users, especially regarding agent context, role assignment, and remote access.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (Group Policy, Microsoft Configuration Manager, WSUS, BitLocker) are mentioned before or more prominently than their Linux equivalents. PowerShell is referenced for extension management and onboarding, with Linux alternatives less visible or deferred to links. Windows update mechanisms are described in detail, while Linux update instructions are summarized and referenced externally. Some onboarding methods are described as 'Windows-only'.
Recommendations
- Provide Linux-specific onboarding examples and clarify which methods are available on Linux (e.g., interactive logons).
- Include direct Linux automation tool guidance (e.g., Ansible playbook examples, systemd scripts) alongside Windows Group Policy and Configuration Manager.
- Present Linux update mechanisms (apt, yum, etc.) with equal detail as Windows Update/WSUS, including step-by-step instructions.
- Mention Linux disk encryption tools (dm-crypt, LUKS) with parity to BitLocker, including links to relevant documentation.
- Ensure CLI and Linux-native commands are shown alongside PowerShell, not only referenced via external links.
- Avoid describing Windows tools/patterns first; alternate or parallelize Windows and Linux guidance.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific terminology (e.g., NT SERVICE accounts, Local System, PowerShell Desired State Configuration) is used throughout, often before or more prominently than Linux equivalents. Examples and descriptions focus on Windows scenarios (such as domain controllers and Windows agent extensions) and use Windows-centric extension IDs. There are no explicit Linux/macOS examples or guidance, and Linux-specific security considerations are not addressed.
Recommendations
- Include Linux/macOS-specific examples, such as onboarding a Linux server and configuring agent security controls for Linux.
- Provide extension allowlist examples relevant to Linux (e.g., Linux agent extensions, Linux Defender extension IDs).
- Mention Linux/macOS service accounts and privilege models with equal detail and order as Windows equivalents.
- Describe guest configuration policies for Linux, including alternatives to PowerShell DSC (such as Ansible or native Linux configuration tools).
- Add security recommendations for Linux Tier 0 assets, such as hardening SSH, SELinux/AppArmor, and Linux-specific monitoring.
- Ensure that all CLI examples are cross-platform and clarify any OS-specific differences.
Azure Arc
SSH access to Azure Arc-enabled servers
...ob/main/articles/azure-arc/servers/ssh-arc-overview.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Windows and Linux instructions, but Windows-specific tools (PowerShell, Windows OpenSSH) are frequently referenced and often given equal or greater prominence than Linux equivalents. PowerShell examples are included throughout, sometimes with special notes for PowerShell users, while Linux shell examples are present but not always as detailed. Windows tools and patterns (such as Get-Service, Get-WindowsCapability) are described in detail, whereas Linux instructions are more concise. Some sections, such as enabling OpenSSH, link only to Windows documentation, and troubleshooting/next steps reference Windows resources first.
Recommendations
- Ensure Linux examples are as detailed as Windows ones, including troubleshooting and validation steps.
- Provide direct links to Linux OpenSSH documentation and troubleshooting resources alongside Windows links.
- When listing commands or tools, present Linux and Windows instructions in parallel, not with Windows first or as the default.
- Include explicit macOS instructions where relevant, especially for SSH client usage.
- Balance references to PowerShell and Bash, and avoid PowerShell-specific notes unless a Bash equivalent is also provided.
Azure Arc
Tutorial - Monitor a hybrid machine with Azure Monitor VM insights
...icles/azure-arc/servers/tutorial-enable-vm-insights.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation claims to support both Linux and Windows hybrid machines, but examples and details are notably Windows-centric. The 'Event' table is described as containing Windows event log data, with no equivalent Linux log example or query shown. There are no Linux-specific instructions or screenshots, and Windows terminology (event log, Event table) is used exclusively when discussing log collection and analysis.
Recommendations
- Add explicit examples and screenshots for Linux machines, showing how Linux logs (e.g., syslog, auth.log) are collected and queried in Log Analytics.
- Clarify what tables and data types are available for Linux machines, and provide sample queries for Linux logs.
- Avoid using Windows terminology exclusively; mention Linux equivalents where appropriate.
- Ensure parity in instructions and visuals for both platforms throughout the tutorial.
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page displays a moderate Windows bias. Windows Server and Windows client OS versions are listed first and in detail, while Linux support is mentioned as an exception. The Azure portal method is only available for Windows VMs, with Linux users directed to alternative methods. Windows-specific tools (PowerShell, Group Policy, Configuration Manager) are highlighted before Linux equivalents, and examples often use Windows-first ordering. However, Linux scripts and Ansible are mentioned, and manual/scripted installation instructions are provided for both platforms.
Recommendations
- Explicitly list supported Linux distributions and versions alongside Windows versions in all relevant sections.
- Provide parity in example ordering: show Linux and Windows examples side-by-side, or alternate which is shown first.
- Expand on Linux automation methods (e.g., Ansible, shell scripts) with equal detail as Windows tools like PowerShell and Group Policy.
- Clarify which features are Windows-only and which are cross-platform, and provide links to Linux-specific guidance where possible.
- Add troubleshooting and FAQ sections for Linux users, addressing common issues and differences.
Azure Arc
Overview of the Azure Arc-enabled System Center Virtual Machine Manager
...-arc/system-center-virtual-machine-manager/overview.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation is notably Windows-centric, referencing Windows Server management, Windows registry, and PowerShell as primary automation tools. Windows-specific features (like Extended Security Updates for Windows Server and SQL Server) are highlighted, and Windows terminology appears before Linux equivalents. Linux support is mentioned but lacks concrete examples or parity in tooling guidance, especially for automation and configuration tasks.
Recommendations
- Provide explicit Linux examples for automation and configuration tasks (e.g., bash scripts, Linux daemon management).
- Highlight Linux management features with equal prominence to Windows features, including links to Linux-specific documentation.
- Include Linux-first or cross-platform examples for SDK usage, CLI commands, and VM extension management.
- Clarify which features/tools are cross-platform and which are Windows-only, to help Linux/macOS users understand applicability.
- Add guidance for Linux administrators on onboarding, monitoring, and managing Linux VMs via Azure Arc-enabled SCVMM.
Azure Arc
Quickstart for Azure Arc-enabled System Center Virtual Machine Manager (SCVMM)
...t-connect-system-center-virtual-machine-manager-to-arc.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates moderate Windows bias. Windows-specific tools (PowerShell, WinRM, OpenSSH for Windows, tar.exe) are referenced in prerequisites and examples. Windows instructions and troubleshooting steps are presented first, with more detail and context than Linux equivalents. Linux instructions are present but less detailed, and there are warnings about performance issues on Linux. Some required tools for Windows (tar.exe, archiveint.dll) are described in detail, but Linux prerequisites are not. The documentation assumes familiarity with Windows environments and patterns.
Recommendations
- Provide equally detailed prerequisites for Linux, including required packages and configuration steps.
- List Linux instructions and examples alongside or before Windows ones, or alternate their order.
- Include troubleshooting steps and retry commands for Linux with the same level of detail as Windows.
- Avoid language that discourages Linux usage unless there are technical limitations, and clarify any such limitations.
- Reference Linux-native tools and patterns where appropriate (e.g., SSH, tar, bash), and avoid Windows-centric terminology when describing cross-platform steps.
Azure Arc
What's new in Azure Arc-enabled SCVMM
...arc/system-center-virtual-machine-manager/whats-new.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation page for Azure Arc-enabled SCVMM features a notable Windows bias. Many enhancements and management options reference Windows-centric tools (e.g., PowerShell, Windows Server Management, Group Policy, System Center Configuration Manager). Windows tools and patterns are mentioned before Linux equivalents, and some features (like Windows Server Management and Extended Security Updates for WS 2012/2012 R2) are exclusively Windows-focused. While some cross-platform tools (Terraform, Bicep, ARM templates, SDKs, Ansible) are mentioned, Windows-specific methods and terminology dominate the page.
Recommendations
- Add explicit Linux/macOS management examples and workflows where possible.
- Include Linux-native automation tools (e.g., shell scripts, cloud-init) alongside Windows tools like PowerShell and Group Policy.
- Ensure parity in agent installation instructions for Linux VMs, not just SCVMM/Windows VMs.
- Highlight cross-platform SDKs and CLI tools earlier or alongside Windows tools.
- Clarify which features are Windows-only and provide alternatives or workarounds for Linux environments.
Azure Arc
Upgrade the Azure Arc resource bridge
...l-machine-manager/upgrade-azure-arc-resource-bridge.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation is heavily oriented toward Windows environments, specifically SCVMM (System Center Virtual Machine Manager), and assumes the use of Windows tools and patterns. All example commands are given for Azure CLI, but the context and instructions (such as running commands from the SCVMM server and handling VHDX files) are Windows-centric. There are no Linux/macOS-specific instructions, examples, or considerations, and prerequisites and steps reference Windows-only components and locations.
Recommendations
- Add explicit instructions for performing the upgrade from Linux/macOS workstations, including any differences in file handling, CLI usage, or configuration file paths.
- Clarify whether the Azure Arc resource bridge upgrade can be managed from non-Windows environments, and if so, provide examples and troubleshooting steps for those platforms.
- If SCVMM is strictly Windows-only, clearly state this limitation at the beginning of the documentation so Linux/macOS users understand the platform requirements.
- Include notes on cross-platform compatibility for the Azure CLI and the arcappliance extension, and document any limitations or workarounds for Linux/macOS users.
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation shows notable Windows bias, especially in the initial setup and extraction steps. The only example for installing kubectl uses Windows-specific 'winget', and the zip extraction instructions use 'Expand-Archive', a Windows/PowerShell command, even in the Bash tab. There are no Linux/macOS equivalents for these steps, and Windows tools/patterns are presented first or exclusively. While the Azure CLI and kubectl commands themselves are cross-platform, the setup instructions create friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS equivalents for installing kubectl (e.g., 'curl' or 'apt/yum/brew' commands).
- Replace or supplement 'Expand-Archive' with cross-platform zip extraction commands (e.g., 'unzip archive.zip -d /path/to/dir').
- Ensure Bash tab examples use native Bash/Linux commands, not PowerShell/Windows commands.
- Add explicit notes or sections for Linux/macOS users where platform-specific steps differ.
- List installation and extraction instructions for all major platforms, not just Windows.
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 migration script and example, with no mention of Bash, shell, or cross-platform alternatives. This assumes users are on Windows or have PowerShell installed, which may not be the case for Linux/macOS users.
Recommendations
- Provide a Bash or shell script alternative for Linux/macOS users.
- Clarify whether the PowerShell script is compatible with PowerShell Core on Linux/macOS, and provide installation instructions if so.
- Explicitly mention cross-platform support or limitations for the migration script.
- Include Linux/macOS command-line examples alongside PowerShell.
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_first
missing_linux_example
windows_tools
Summary
The documentation consistently uses PowerShell syntax for all CLI examples, references .ps1 scripts (Windows PowerShell), and does not provide Linux/macOS shell equivalents or guidance. Script tooling is Windows-centric, and there is no mention of Bash, shell, or cross-platform alternatives. This creates friction for Linux/macOS users who may not use PowerShell or .ps1 scripts.
Recommendations
- Provide CLI examples using Bash/sh syntax alongside PowerShell, especially for az CLI commands.
- Offer Linux/macOS-compatible versions of deployment scripts (e.g., bulk_deployment.sh) and document their usage.
- Clarify whether .ps1 scripts can be run with PowerShell Core on Linux/macOS, or provide native shell alternatives.
- Explicitly state cross-platform compatibility for all commands and scripts.
- List Linux/macOS instructions and examples before or alongside Windows/PowerShell ones, not after.
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page presents Windows agent installation details before Linux, with more granular information about Windows-specific tools, services, accounts, and troubleshooting. Windows paths, service names, and security group details are more extensively described, while Linux coverage is briefer and lacks equivalent detail (e.g., no mention of Linux user/group management or troubleshooting tips). Windows-centric terminology and patterns (MSI, Download Center, Group Policy) are used, and Windows examples are consistently listed first.
Recommendations
- Present Linux and Windows installation details in parallel, or alternate which OS is described first in each section.
- Expand Linux documentation to match Windows detail, including user/group management, service configuration, and troubleshooting tips.
- Include Linux-specific commands and configuration patterns (e.g., systemd unit files, SELinux/AppArmor considerations, package manager commands).
- Provide parity in troubleshooting guidance, log file locations, and artifact cleanup steps.
- Avoid Windows-centric terminology (e.g., 'Group Policy') without Linux equivalents or explanations.
Azure Arc
Quickstart - Deploy Azure Arc-enabled data services - directly connected mode - Azure portal
...ttps://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-complete-managed-instance-directly-connected.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific file paths (e.g., C:<current path>\.kube\config), using Azure portal and CLI examples that implicitly assume Windows environments, and omitting explicit Linux/macOS instructions or examples. No Linux/macOS-specific guidance is provided for steps such as accessing the kubeconfig file, installing client tools, or using the Azure CLI, which may behave differently on non-Windows platforms.
Recommendations
- Include Linux/macOS-specific instructions and examples, such as typical file paths (e.g., ~/.kube/config) and command syntax differences.
- Add screenshots or terminal outputs from Linux/macOS environments alongside Windows examples.
- Explicitly state that the instructions apply to all platforms, and note any platform-specific differences in tool installation or usage.
- Provide guidance on installing Azure Data Studio, Azure CLI, and Kubernetes CLI on Linux/macOS.
- Avoid using Windows-only file path formats in example outputs, or provide both Windows and Linux/macOS variants.
Azure Arc
Resize persistent volume claim (PVC) for Azure Arc-enabled data services volume
...icles/azure-arc/data/resize-persistent-volume-claim.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides shell command examples for Kubernetes operations, but the PVC patching step uses a variable assignment syntax ($newsize='...') that is specific to PowerShell or Windows command line environments. There are no equivalent examples for Linux/macOS shells (e.g., Bash), and the Windows/PowerShell syntax is presented exclusively and first, which may confuse or block Linux/macOS users.
Recommendations
- Provide equivalent Bash/Linux/macOS command examples for variable assignment and kubectl patch usage.
- Clarify which shell environment each example is intended for, and present both Windows/PowerShell and Linux/Bash examples side-by-side.
- Add a note explaining the differences in shell syntax for variable assignment and command execution.
- Consider using shell-agnostic kubectl patch commands (e.g., inline JSON patching) where possible.
Azure Arc
Configure "BYOM" Endpoint Authentication for Edge RAG
...zure-arc/edge-rag/configure-endpoint-authentication.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page provides all command-line examples using PowerShell syntax and Windows-specific patterns (e.g., '.\kubectl.exe'), with no mention or examples for Linux/macOS shells. This creates friction for non-Windows users, who must adapt commands and may encounter issues with syntax and executable naming.
Recommendations
- Add equivalent bash/zsh examples for Linux/macOS users, using standard shell syntax.
- Use platform-neutral command formats (e.g., 'kubectl' instead of '.\kubectl.exe') where possible.
- Explicitly note any platform-specific differences in command usage.
- Provide guidance for both Windows and Linux/macOS environments in all steps.
Azure Arc
Configure DNS for Edge RAG Preview Enabled by Azure Arc
...s/blob/main/articles/azure-arc/edge-rag/prepare-dns.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides only Windows-specific instructions for updating the hosts file (using Notepad, referencing the Windows hosts file path), with no mention of Linux or macOS equivalents. This creates friction for non-Windows users who need to perform the same DNS configuration.
Recommendations
- Add instructions for editing the hosts file on Linux (e.g., using nano or vim to edit /etc/hosts with sudo).
- Include macOS-specific guidance (editing /etc/hosts with TextEdit or terminal editors).
- Present cross-platform steps in parallel or clearly labeled sections (e.g., 'Windows', 'Linux', 'macOS').
- Avoid referencing Windows tools (Notepad, Administrator privileges) exclusively; mention alternatives for other platforms.
Azure Arc
Connect hybrid machines to Azure at scale
...rticles/azure-arc/servers/onboard-service-principal.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides both Windows and Linux options for connecting hybrid machines to Azure Arc, but exhibits a Windows-first bias in several areas. Windows tools (PowerShell) are emphasized, examples and notes often mention Windows before Linux, and PowerShell-specific instructions are detailed. Linux instructions are present but sometimes less prominent, and Linux-specific automation or troubleshooting is not covered in equal depth.
Recommendations
- Alternate the order of Windows and Linux instructions/examples throughout the documentation to avoid Windows-first presentation.
- Provide Linux-specific automation and troubleshooting guidance, including common errors and solutions for Linux environments.
- Expand on Linux command-line usage, such as using Bash scripts or Ansible for at-scale onboarding, not just referencing .sh scripts.
- Ensure parity in example outputs and screenshots for both Windows and Linux onboarding processes.
- Include references to Linux-native tools and package managers (e.g., apt, yum) where appropriate, not just PowerShell or Windows tools.
Azure Arc
Connected Machine agent prerequisites
.../blob/main/articles/azure-arc/servers/prerequisites.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates several Windows biases: Windows-specific examples (PowerShell) are provided for critical tasks like agent installation and resource provider registration, with Linux equivalents either missing or shown after Windows. Windows tools (e.g., Local Group Policy Editor) are described in detail, while Linux configuration steps are not covered. The onboarding script modification example is only given for Windows, and the permissions section references Windows-specific accounts and procedures. Linux users may need to infer or seek external guidance for equivalent steps.
Recommendations
- Provide Linux-specific command examples for onboarding limited support servers, including explicit instructions for specifying agent versions.
- Include Linux equivalents for Windows tools and configuration steps (e.g., how to check service permissions or configure systemd for the agent).
- Present CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Add troubleshooting and configuration guidance for Linux environments, matching the detail given for Windows.
- Ensure all critical procedures have both Windows and Linux instructions.
Azure Arc
Troubleshoot SSH access to Azure Arc-enabled servers
...ain/articles/azure-arc/servers/ssh-arc-troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page exhibits a notable Windows bias, with troubleshooting steps and examples heavily focused on Azure PowerShell modules and commands. Windows-specific error messages and PowerShell-centric instructions are prevalent, while Linux/macOS equivalents are either missing or mentioned secondarily. The use of PowerShell modules (Az.Ssh, Az.Ssh.ArcProxy) and references to Windows error codes (WinError) further reinforce this bias. Although some Linux-related errors and paths are referenced, actionable Linux/macOS guidance is limited.
Recommendations
- Provide equivalent Linux/macOS troubleshooting steps and examples alongside PowerShell instructions, including bash and shell commands.
- Include installation and update instructions for Az.Ssh and Az.Ssh.ArcProxy modules on Linux/macOS (e.g., using pip, apt, or manual download).
- Offer clear guidance for configuring PATH and environment variables on Linux/macOS, not just Windows.
- Present CLI and shell examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Expand on Linux-specific error messages and resolutions, such as file permissions and executable flags.
Azure Arc
Troubleshoot Azure Arc-enabled servers VM extension issues
...ticles/azure-arc/servers/troubleshoot-vm-extensions.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation demonstrates a moderate Windows bias. The only explicit command-line example for extension removal uses Azure PowerShell, with no Linux shell or CLI equivalent shown. In several sections, Windows file paths and procedures are listed before Linux equivalents. However, Linux troubleshooting steps and log locations are generally included, and the CLI command for extension deletion is mentioned later.
Recommendations
- Provide Linux shell (bash) or Azure CLI examples alongside PowerShell commands, especially for extension management tasks.
- Alternate the order of Windows and Linux instructions or present them in parallel to avoid 'Windows first' bias.
- Explicitly mention that both PowerShell and CLI commands are cross-platform where applicable.
- Include screenshots or examples from Linux environments in addition to Windows.
Azure Arc
Troubleshoot Azure Arc-enabled servers in disconnected scenarios
...rticles/azure-arc/servers/troubleshoot-connectivity.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exhibits a Windows bias by exclusively mentioning Windows-specific tools (Windows Admin Center, Configuration Manager) as local management options for disconnected servers. There are no references to equivalent Linux/macOS tools or management patterns, nor are Linux examples provided for troubleshooting or contingency actions. Windows tools are presented as the default or only option, which may leave Linux/macOS users without clear guidance.
Recommendations
- Include Linux/macOS management options, such as Cockpit, Ansible, or native command-line tools for local server management.
- Add troubleshooting examples and contingency steps relevant to Linux environments.
- Present Windows and Linux/macOS options side-by-side, or clarify which instructions apply to which platforms.
- Explicitly mention that Configuration Manager and Windows Admin Center are Windows-only, and suggest alternatives for other operating systems.
Azure Arc
Support matrix for Azure Arc-enabled System Center Virtual Machine Manager
...pport-matrix-for-system-center-virtual-machine-manager.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation page exhibits a Windows bias by focusing primarily on Windows Server and SCVMM environments, referencing Windows tools (WinRM, Windows Management Framework), and providing detailed requirements and recommendations for Windows systems. Linux is mentioned only as an alternative for running the helper script, with a note about performance issues, and Linux-specific requirements are listed without examples or guidance. No Linux/macOS-specific deployment examples, troubleshooting, or parity guidance are provided.
Recommendations
- Provide step-by-step Linux/macOS deployment instructions for the Resource Bridge and Arc agent installation, including troubleshooting tips.
- Include Linux/macOS CLI examples and clarify any differences in workflow or performance.
- List Linux/macOS equivalents for Windows tools (e.g., alternatives to WinRM, PowerShell, Windows Management Framework).
- Address performance issues on Linux with recommendations or workarounds.
- Ensure that all requirements and steps are equally documented for Linux/macOS environments, not just Windows.
Azure Arc
Deliver ESUs for VMware VMs through Arc
...r-extended-security-updates-for-vmware-vms-through-arc.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is focused exclusively on Windows Server 2012/2012 R2 VMs and their ESU management through Azure Arc. All examples, screenshots, and instructions pertain to Windows environments, with no mention of Linux VM support, Linux patching tools, or cross-platform considerations. Windows-specific tools (WSUS, Microsoft Updates, Configuration Manager) are referenced, and Linux alternatives are absent.
Recommendations
- Clarify early in the document that ESUs are only available for Windows Server 2012/2012 R2, if that is the case, and explicitly state that Linux VMs are not in scope.
- If Azure Arc supports similar lifecycle management or patching for Linux VMs, provide links or references to those workflows.
- Mention Linux-compatible patch management solutions (e.g., Azure Update Manager for Linux, third-party Linux patching tools) where patching solutions are discussed.
- If any steps or features are applicable to Linux VMs, include parallel examples or notes.
- Add a section on cross-platform support and limitations to help administrators managing mixed environments.
Azure Portal
Create an Azure portal dashboard by using a Bicep file
.../blob/main/articles/azure-portal/quick-create-bicep.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits Windows bias by exclusively using a Windows VM example (SimpleWinVM), referencing Windows-specific username/password requirements, and linking only to Windows VM documentation. There are no Linux VM deployment examples, nor any mention of Linux-specific requirements or alternatives. The deployment scripts use Azure CLI and PowerShell, which are cross-platform, but the VM created is Windows-only, and all guidance is tailored to Windows environments.
Recommendations
- Add a parallel example for deploying a Linux VM, including links to Linux username/password requirements and best practices.
- Reference both Windows and Linux VM documentation when discussing prerequisites and password requirements.
- Use a more neutral VM name (e.g., SimpleVM) and provide parameters or instructions for selecting the OS type.
- Clarify that the Bicep file and deployment scripts work for both Windows and Linux VMs, or provide separate Bicep files/examples for each.
- Ensure that dashboard examples can visualize both Windows and Linux VM metrics.
Azure Portal
Create an Azure portal dashboard by using an Azure Resource Manager template
...ob/main/articles/azure-portal/quick-create-template.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits a notable Windows bias. All command-line examples for creating the required VM use PowerShell, with explicit instructions to select PowerShell in the Azure Cloud Shell. The resource group and VM naming conventions (e.g., 'SimpleWinVmResourceGroup', 'myVM1') and linked requirements reference Windows VM documentation. There are no equivalent Bash or Azure CLI examples for Linux/macOS users, nor any mention of Linux VM creation or requirements. The instructions and screenshots prioritize Windows-centric tools and workflows.
Recommendations
- Provide parallel instructions and command examples using Bash/Azure CLI in Cloud Shell for Linux/macOS users.
- Include links to Linux VM documentation and requirements alongside Windows references.
- Offer guidance for creating a Linux VM (e.g., using Ubuntu) with appropriate naming conventions.
- Alternate or combine screenshots to show both PowerShell and Bash options in Cloud Shell.
- Clarify that Cloud Shell supports both Bash and PowerShell, and users can choose based on their environment.
Azure Portal
Create an Azure portal dashboard with Azure CLI
.../azure-portal/quickstart-portal-dashboard-azure-cli.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing a Windows VM creation example (using the 'win2016datacenter' image) and referencing Windows-specific username/password requirements. There are no Linux VM examples or references to Linux-specific requirements, which may hinder Linux users from following the quickstart without additional research.
Recommendations
- Include a Linux VM creation example alongside the Windows example, such as using '--image UbuntuLTS' and appropriate authentication options.
- Reference Linux-specific username and password requirements, or link to the relevant documentation for Linux VMs.
- Clarify that the dashboard template and Azure CLI commands work equally well for Linux VMs.
- Present Windows and Linux examples in parallel, or alternate which is shown first to avoid implicit prioritization.
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
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Examples and instructions are frequently provided for Azure PowerShell and Azure CLI, with PowerShell examples given equal prominence to CLI. Windows-specific tools and patterns (PowerShell cmdlets, references to Connect-AzAccount, etc.) are mentioned throughout, often before or alongside cross-platform CLI commands. Linux/macOS users are referenced mainly in the context of Docker and Podman, but there are few explicit Linux/macOS shell examples (e.g., bash, zsh), and PowerShell is not available natively on most Linux/macOS systems. The page does mention Podman for RHEL, but only as an alternative to Docker and with minimal guidance. There are no examples using native Linux authentication tools or workflows outside of Docker/Podman. The 'Next steps' section also lists PowerShell as a primary path.
Recommendations
- Add explicit bash/zsh shell examples for Linux/macOS users, especially for authentication and scripting scenarios.
- Provide guidance for Linux/macOS users on installing and using Azure CLI, and clarify that PowerShell is optional and not required for most workflows.
- Reorder examples so that cross-platform CLI (az) and Docker/Podman commands are shown before PowerShell, or provide tabs for 'Windows', 'Linux/macOS', and 'Cloud Shell' usage.
- Include troubleshooting tips specific to Linux/macOS environments (e.g., Docker daemon issues, permissions, environment variables).
- Expand on Podman usage for Linux, including authentication flows and registry access, not just as a Docker replacement.
- Clarify which commands are cross-platform and which are Windows/PowerShell-specific.
Container Registry
Quickstart - Create Registry - Bicep
...ainer-registry/container-registry-get-started-bicep.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying the Bicep file, but PowerShell is featured as a primary option and is given its own tab. There is no mention of Bash or Linux-specific shell usage, nor are there any Linux/macOS-specific instructions or screenshots. The use of Visual Studio Code is suggested, but no alternatives for Linux users are discussed. The cleanup instructions focus on the Azure portal, with no CLI/Bash examples for resource deletion.
Recommendations
- Add explicit Bash/Linux shell examples for deploying the Bicep file using Azure CLI.
- Include instructions or screenshots relevant to Linux/macOS environments, such as using the terminal or alternative editors.
- Provide parity in cleanup instructions by showing how to delete resources using Azure CLI/Bash.
- Avoid presenting PowerShell as the default or primary option; ensure CLI/Bash instructions are equally prominent.
- Mention cross-platform tools and workflows where appropriate.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides examples exclusively for Azure CLI and Azure PowerShell, with no explicit Linux/macOS shell examples or instructions. While Azure CLI is cross-platform, PowerShell is traditionally associated with Windows, and its usage is emphasized throughout. There are no Linux-specific tools, shell commands, or platform notes, and Windows-centric images (e.g., Windows Server Core) are highlighted without Linux equivalents. The ordering of examples sometimes places PowerShell first or equally, which may subtly prioritize Windows users.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS and provide example shell environments (e.g., bash, zsh) for clarity.
- Add Linux/macOS-specific notes or troubleshooting tips where platform differences may affect usage (e.g., authentication, file paths, environment variables).
- Include Linux container image examples (e.g., Ubuntu, Alpine) alongside Windows images to demonstrate parity.
- Clarify that PowerShell Core is available cross-platform, or de-emphasize PowerShell in favor of CLI for platform-neutral documentation.
- Where possible, add sample commands using native Linux tools (e.g., curl, wget) for related tasks, or link to such resources.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. It repeatedly references PowerShell and its module (AIShell), links to PowerShell-centric resources, and does not mention or provide examples for Linux/macOS shells (e.g., Bash, Zsh). Installation instructions and tooling are described in terms of PowerShell, with no guidance for Linux users or alternative shell environments. All examples and use cases focus on Azure CLI and PowerShell, with PowerShell consistently mentioned first and exclusively as the extension mechanism.
Recommendations
- Add explicit instructions and examples for installing and using AI Shell on Linux/macOS terminals (e.g., Bash, Zsh, fish).
- Provide parity in examples, showing both PowerShell and Bash command generation and troubleshooting.
- Reference and link to Linux/macOS-specific documentation or community resources.
- Clarify whether the AIShell module or AI Shell itself is cross-platform, and if not, provide alternatives or workarounds for non-Windows users.
- Avoid listing PowerShell first in every example; alternate ordering or provide parallel examples.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides example prompts for Azure Copilot, including scenarios for both Azure CLI and PowerShell. However, PowerShell is given its own dedicated section with multiple examples, while Linux/macOS-native tools (such as Bash or shell scripting) are not mentioned. The CLI examples do not specify cross-platform usage or highlight Linux/macOS compatibility. PowerShell, a Windows-centric tool, is featured equally alongside Azure CLI, which is cross-platform, but there is no parity for Linux shell scripting. No explicit Linux/macOS examples or references are present, and Windows tools (PowerShell) are highlighted.
Recommendations
- Add example prompts for Bash or shell scripting to reflect Linux/macOS usage.
- Clarify that Azure CLI is cross-platform and provide prompts/examples for both Windows (cmd/PowerShell) and Linux/macOS (Bash/zsh).
- Include references to Linux-native tools or workflows where relevant.
- Ensure that PowerShell examples are balanced with Linux/macOS equivalents, such as Bash scripts.
- Consider reordering examples so that cross-platform tools (Azure CLI) are presented before Windows-specific tools (PowerShell).
Lighthouse
Onboard all subscriptions in a management group
...articles/lighthouse/how-to/onboard-management-group.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation provides only a PowerShell example for assigning the policy at the management group level, without mentioning or providing equivalent Azure CLI, Bash, or REST API examples. This creates friction for Linux/macOS users who may not use PowerShell as their primary automation tool. The example is labeled as 'azurepowershell-interactive', reinforcing a Windows-centric approach.
Recommendations
- Add Azure CLI and/or REST API examples for policy assignment, ensuring cross-platform compatibility.
- Explicitly mention that PowerShell is available on Linux/macOS, but provide alternatives for users who prefer native tools.
- Present examples for multiple platforms side-by-side or in parallel, rather than only PowerShell.
- Clarify any platform-specific requirements or limitations for each method.
Copilot
Optimization agent capabilities in Agents (preview) in Azure Copilot
...-docs/blob/main/articles/copilot/optimization-agent.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is explicitly mentioned in sample prompts and as a script generation target, while Linux/macOS equivalents (such as Bash or shell scripts) are not referenced. Azure CLI is mentioned, but only after PowerShell, and there are no explicit Linux/macOS examples or guidance. This may create friction for non-Windows users who rely on Bash or other shell environments.
Recommendations
- Include explicit Bash or shell script examples alongside PowerShell, especially in sample prompts and script generation sections.
- Clarify that Azure CLI is cross-platform and provide usage examples for Linux/macOS terminals.
- Avoid listing PowerShell before CLI unless there is a technical reason; consider presenting both equally.
- Add a note or section for Linux/macOS users on how to run generated scripts.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is referenced as the primary example for creating registration definitions, with no equivalent Azure CLI or REST API example provided inline. Windows-centric tools (PowerShell cmdlets) are mentioned first and exclusively in the main workflow, while Linux-friendly alternatives (Azure CLI, REST API) are only referenced in the 'Next steps' section and not shown in context. This may create friction for Linux/macOS users who prefer CLI or scripting over PowerShell.
Recommendations
- Provide Azure CLI examples alongside PowerShell for key tasks such as creating registration definitions and assignments.
- Explicitly mention REST API options for automation and cross-platform parity.
- Ensure that CLI and PowerShell examples are presented together, or alternate which is shown first.
- Add a note clarifying that all operations can be performed using CLI, PowerShell, or REST API, with links to relevant documentation.
Lighthouse
Monitor delegated resources at scale
...ob/main/articles/lighthouse/how-to/monitor-at-scale.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a notable Windows bias, particularly in the section on registering resource providers, where only Azure PowerShell commands are provided. There are no CLI or Bash examples, and PowerShell is referenced as the primary automation tool. This may create friction for Linux/macOS users who prefer Azure CLI or Bash scripting. Additionally, Windows-centric tools and patterns are mentioned before any cross-platform alternatives.
Recommendations
- Provide equivalent Azure CLI commands for resource provider registration and service principal creation.
- Include Bash scripting examples alongside PowerShell for automation tasks.
- Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI.
- Reorder examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
- Add notes clarifying tool compatibility across operating systems.
Lighthouse
Monitor delegation changes in your managing tenant
...ticles/lighthouse/how-to/monitor-delegation-changes.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is the primary scripting language used for querying delegation changes, with a detailed PowerShell script provided and no equivalent Bash or cross-platform shell example. While Azure CLI is mentioned for role assignment, all advanced querying and reporting is shown only in PowerShell, which is most commonly used on Windows. There is no guidance or sample for Linux/macOS users who may prefer Bash, Python, or other cross-platform tools.
Recommendations
- Provide equivalent Bash or Python scripts for querying the Tenant Activity Log using REST API and Azure CLI, suitable for Linux/macOS environments.
- Explicitly mention that PowerShell Core is available cross-platform, and clarify any Windows-specific dependencies.
- Show Azure CLI examples for querying and reporting, not just for role assignment.
- Reorder examples so that cross-platform tools (Azure CLI, Bash, Python) are presented before or alongside PowerShell.
- Add notes or links to cross-platform scripting resources for Azure.
Lighthouse
Deploy Azure Policy to delegated subscriptions at scale
...lob/main/articles/lighthouse/how-to/policy-at-scale.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively uses PowerShell commands and Azure PowerShell modules for all examples, with no mention of Bash, Azure CLI, or Linux/macOS-specific workflows. All code samples and deployment instructions assume the use of PowerShell, which is traditionally a Windows-centric tool, although it is available on Linux/macOS. There are no alternative examples or guidance for users who prefer Bash or Azure CLI, and Windows/PowerShell patterns are presented first and exclusively.
Recommendations
- Add equivalent examples using Azure CLI (az) commands for querying, deploying, validating, and cleaning up policies.
- Include Bash shell script samples for Linux/macOS users.
- Explicitly mention cross-platform compatibility of PowerShell, and provide installation/setup links for PowerShell on Linux/macOS.
- Where possible, note any differences or limitations when running these commands on Linux/macOS.
- Present Azure CLI and Bash examples alongside PowerShell, or at least link to relevant cross-platform documentation.
Azure Arc
Customer intent: "As a system administrator, I want to configure Linux with Ubuntu for a cluster setup, so that I can ensure adequate file monitoring capabilities are in place."
...e-arc/container-storage/includes/single-node-ubuntu.md
Low Priority
View Details →
Detected Bias Types
none
Summary
The documentation page exclusively provides instructions for preparing Linux with Ubuntu, including relevant shell commands. There is no evidence of Windows bias: no Windows or PowerShell examples, no mention of Windows tools or patterns, and no prioritization of Windows content.
Recommendations
No changes needed regarding Linux parity. If Windows support is relevant, consider adding equivalent instructions for Windows environments.
Azure Arc
Azure Arc-enabled data services - Automated validation testing
...ticles/azure-arc/data/automated-integration-testing.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation displays mild Windows bias, primarily in the order and emphasis of tooling and examples. Windows-specific issues (CRLF line endings) are highlighted with screenshots of VSCode on Windows, and Azure CLI examples are shown in PowerShell terminals. The process for generating environment files is described as identical across OSes, but troubleshooting and visuals focus on Windows. There is no explicit Linux/macOS example or troubleshooting, and Windows tools (VSCode, PowerShell) are mentioned before alternatives.
Recommendations
- Add explicit Linux/macOS troubleshooting steps for line endings (e.g., using 'dos2unix' or 'sed').
- Include screenshots or terminal examples from Linux/macOS environments alongside Windows.
- Clarify that Azure CLI and kubectl commands are cross-platform, and show examples in bash/zsh as well as PowerShell.
- Mention alternative editors for Linux/macOS when discussing line ending conversions.
- Ensure that any OS-specific issues (like CRLF/LF) are explained for all platforms, not just Windows.
Azure Arc
Connect to AD-integrated SQL Managed Instance enabled by Azure Arc
.../data/connect-active-directory-sql-managed-instance.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows-based tools (SSMS, ADS) are mentioned and illustrated, and the Windows connection example is presented before the Linux/Mac OS example. The Linux section is present and functional, but lacks parity in graphical tool instructions and screenshots.
Recommendations
- Add screenshots or step-by-step instructions for connecting from Azure Data Studio (ADS) on Linux/macOS.
- Clarify that ADS is cross-platform and provide explicit Linux/macOS usage notes.
- Present Linux/Mac OS examples before or alongside Windows examples to avoid ordering bias.
- Mention alternative Linux-native SQL clients if relevant.
- Ensure parity in troubleshooting steps for both platforms.
Azure Arc
Encrypt a database with transparent data encryption manually in SQL Managed Instance enabled by Azure Arc
...data/configure-transparent-data-encryption-manually.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides both Windows and Linux examples for key operations, but Windows examples are consistently shown first in each step. Windows-specific tools and patterns (e.g., 'type' command, Windows path syntax) are used, and there are multiple notes about Windows-specific issues (e.g., kubectl cp path problems). There is a slight emphasis on Windows workflows, but Linux parity is maintained with equivalent commands and examples.
Recommendations
- Alternate the order of Windows and Linux examples, or present Linux examples first in some sections.
- Add more explicit notes for Linux/macOS users where relevant, not just Windows-specific caveats.
- Where possible, use cross-platform commands or highlight platform-agnostic approaches.
- Consider grouping platform-specific instructions together, rather than interleaving them, to reduce perceived bias.
- Clarify that both Windows and Linux/macOS are fully supported and tested for these operations.
Azure Arc
Turn on transparent data encryption in SQL Managed Instance enabled by Azure Arc (preview)
...igure-transparent-data-encryption-sql-managed-instance.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_path_notes
Summary
The documentation provides both Windows and Linux examples for file operations (copying certificates and keys), but Windows examples are consistently shown first. There are explicit notes about Windows path issues, and Windows-specific commands (e.g., 'type' for file concatenation) are included. However, Linux parity is maintained with equivalent examples and instructions for both platforms.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Add a brief statement at the start of relevant sections clarifying that both Windows and Linux are equally supported.
- Where possible, use platform-neutral commands or highlight cross-platform tools (e.g., PowerShell Core, WSL) for Windows users.
- Ensure all notes about platform-specific issues (such as path handling) are balanced with Linux/macOS caveats if any exist.
Azure Arc
Connectivity modes and requirements
...docs/blob/main/articles/azure-arc/data/connectivity.md
Low Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation generally avoids explicit Windows-only tools, but there is a subtle bias in listing Azure CLI and Azure portal as primary management options, which are more familiar to Windows users. Linux-native tools (kubectl, Helm, oc) are mentioned, but often as secondary options or grouped together. No explicit Linux/Powershell examples are given, and there is no mention of Linux-specific patterns or shell commands. The documentation does not provide platform-specific guidance or parity in examples, which may create friction for Linux/macOS users.
Recommendations
- Provide explicit Linux/macOS command-line examples alongside Azure CLI and portal instructions.
- Clarify that Azure CLI, Azure Data Studio, and Kubernetes tools are cross-platform and provide installation links for Linux/macOS.
- List Linux-native tools (kubectl, Helm, oc) first or equally when describing provisioning and management options.
- Include examples or workflows using bash/zsh and Linux package managers where relevant.
- Add a section on platform compatibility for all mentioned tools.
Azure Arc
Prerequisites | Direct connect mode
...rc/data/create-data-controller-direct-prerequisites.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for connecting a Kubernetes cluster to Azure Arc, but lists PowerShell as a primary alternative to CLI, with no mention of Linux/macOS shell equivalents (e.g., Bash). The PowerShell example is given equal prominence to CLI, which may create friction for Linux/macOS users unfamiliar with PowerShell. There are no Windows-only tools, but the presence and parity of PowerShell examples suggest a mild Windows bias.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily for Windows users.
- Consider listing CLI (Bash/shell) examples first, as they are cross-platform.
- Add explicit notes or examples for Linux/macOS users, confirming that all steps can be performed in Bash or other shells.
- If PowerShell is not required for Linux/macOS, de-emphasize its use or move it to a separate section for Windows users.
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
windows_tools
missing_linux_example
Summary
The documentation page demonstrates mild Windows bias by prioritizing Windows-centric tools (SQL Server Management Studio) and mentioning them before Linux alternatives. While Azure Data Studio and SQLCMD are cross-platform, the examples and instructions reference Windows tools first and do not provide explicit Linux/macOS-specific guidance (e.g., package installation, command-line nuances, or alternative client tools). There are no PowerShell-only instructions, but the lack of Linux/macOS-specific connection examples and troubleshooting steps may create friction for non-Windows users.
Recommendations
- Explicitly mention and provide examples for connecting from Linux/macOS clients, including installation instructions for SQLCMD and Azure Data Studio on those platforms.
- List cross-platform tools (Azure Data Studio, SQLCMD) before Windows-only tools (SQL Server Management Studio) to avoid Windows-first bias.
- Include troubleshooting steps or notes relevant to Linux/macOS environments, such as firewall configuration or network tool usage.
- Add examples using native Linux/macOS tools (e.g., isql, DBeaver, or unixODBC) where appropriate.
Azure Arc
Deploy a new SQL Managed Instance enabled by Azure Arc using Kubernetes tools
...ate-sql-managed-instance-using-kubernetes-native-tools.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation displays mild Windows bias by presenting PowerShell as the first CLI example for base64 encoding credentials, followed by Linux/macOS. Additionally, the example file path for 'kubectl create' uses Windows-style paths (C:\arc-data-services\sqlmi.yaml) without showing a Linux/macOS equivalent. However, most instructions are cross-platform and focus on Kubernetes-native tools.
Recommendations
- Present Linux/macOS and Windows CLI examples side-by-side, or alternate which is shown first.
- Include Linux/macOS file path examples (e.g., /home/user/arc-data-services/sqlmi.yaml) alongside Windows paths.
- Clarify that all commands work on any OS with kubectl installed, and provide explicit notes where platform differences exist.
- Consider mentioning Linux-native editors (e.g., nano, vim) in addition to VS Code.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits mild Windows bias. Installation links for tools like kubectl and curl list Windows first, and explanations reference Windows-specific behaviors (e.g., using cmd.exe instead of PowerShell, PowerShell's curl alias). Linux installation instructions are less detailed or are mentioned second. There is no explicit Linux command-line example for checking tool versions or installing tools, and Windows-specific caveats are highlighted without Linux/macOS equivalents.
Recommendations
- Present installation options for all platforms (Windows, Linux, macOS) in parallel or alphabetical order, rather than listing Windows first.
- Include Linux/macOS-specific notes and caveats where relevant, not just Windows/PowerShell ones.
- Provide explicit Linux/macOS command-line examples for checking versions and installing tools (e.g., 'az --version', 'curl --version', installation via apt/yum/brew).
- Clarify that PowerShell's curl alias is a Windows-specific issue and provide Linux/macOS alternatives or warnings if needed.
- Ensure all critical instructions (such as running curl commands) are equally clear for Linux/macOS users.
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
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows instructions and examples are consistently presented before Linux equivalents. There is a minor bias in ordering, but Linux users are given full parity in instructions and tooling.
Recommendations
- Alternate the order of Windows and Linux instructions in sections, or present them side-by-side to avoid implicit prioritization.
- Explicitly mention macOS compatibility if the Bash script works on macOS, or clarify any limitations.
- Ensure screenshots and UI references do not assume a Windows environment unless necessary.
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 page is generally cross-platform, with most examples using OpenSSL, Azure CLI, and kubectl, which are available on Linux, macOS, and Windows. However, in the section on base64 encoding, the Linux command is presented first, but Windows users are directed to use certutil, a Windows-specific tool, with additional manual steps and Windows command-line syntax. No PowerShell examples are given, but the only OS-specific tool mentioned is for Windows, and it is described after the Linux method.
Recommendations
- Provide PowerShell examples for base64 encoding on Windows, as PowerShell is available on both Windows and Linux.
- Mention cross-platform alternatives to certutil, such as using OpenSSL or PowerShell's [Convert]::ToBase64String(), to avoid reliance on Windows-only tools.
- Clarify that the Azure CLI and kubectl commands work identically on Linux, macOS, and Windows.
- Consider listing both Linux and Windows methods side-by-side for encoding, rather than presenting Linux first and Windows as an afterthought.
Azure Arc
Get logs to troubleshoot Azure Arc-enabled data services
...in/articles/azure-arc/data/troubleshooting-get-logs.md
Low Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides CLI commands that are cross-platform, but the only explicit example of a target folder uses a Windows-style path (C:\temp\logs), and there are no Linux/macOS path examples. This may cause confusion for non-Windows users and suggests a subtle Windows-first bias.
Recommendations
- Include Linux/macOS path examples (e.g., /tmp/logs) alongside Windows paths when showing command usage.
- Add a note clarifying that the az CLI and arcdata extension work on Linux/macOS as well as Windows.
- Consider alternating the order of examples or providing OS-specific tabs for commands where file paths differ.
Azure Arc
Upload usage data, metrics, and logs to Azure
...e-arc/data/upload-metrics-and-logs-to-azure-monitor.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows and Linux/macOS examples for environment variable setting and role assignment, but Windows examples (including PowerShell) are consistently presented first. PowerShell-specific instructions are included as a separate tab, which may reinforce a Windows-centric approach. There is no evidence of missing Linux examples or exclusive use of Windows tools; all commands use Azure CLI, which is cross-platform.
Recommendations
- Alternate the order of example tabs so Linux/macOS is sometimes shown first.
- Add explicit notes confirming full parity and support for Linux/macOS environments.
- Consider merging PowerShell and Windows tabs if the commands are identical, or clarify when PowerShell is required.
- Reference Linux/macOS documentation in related content, not just PowerShell.
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides environment variable examples for Windows (cmd), PowerShell, and Linux/macOS, but consistently lists Windows examples first in each section. All major CLI instructions use Azure CLI, which is cross-platform, and Linux/macOS instructions are present and correct. There are no sections that are Windows-only, nor are there Windows-specific tools or patterns used exclusively.
Recommendations
- Rotate the order of example tabs so that Linux/macOS is shown first in some sections, or randomize the order to avoid implicit prioritization.
- Explicitly state that all CLI commands work on Linux/macOS as well as Windows.
- Consider adding more Linux/macOS-specific automation examples (e.g., cron job setup) alongside Windows Task Scheduler.
- Where scripting is discussed, provide equal detail for both Linux/macOS and Windows approaches.
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides examples for PowerShell, macOS & Linux, and Windows in several sections, but PowerShell (Windows-centric) examples are consistently presented first. Some commands and scripting guidance are PowerShell-heavy, and Windows tools like Task Scheduler are mentioned alongside Linux equivalents. However, Linux/macOS examples are present for most critical steps, and automation is illustrated with a Linux shell script. There are minor gaps, such as the lack of a full Windows batch script example for automation, and PowerShell is used as the default for environment variable manipulation.
Recommendations
- Alternate the order of examples so Linux/macOS commands are shown first in some sections.
- Provide full Windows batch (.bat/.cmd) script examples for automation, not just mention Task Scheduler.
- Include more explicit Linux/macOS tool recommendations (e.g., cron) before or alongside Windows tools.
- Balance PowerShell and Bash usage for environment variable manipulation and scripting.
- Ensure all critical steps have both Windows and Linux/macOS examples, especially for automation.
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides automation examples primarily for Linux/macOS (shell script), but when mentioning script file types, it lists Windows formats (.cmd, .bat, .ps1) before Linux/Mac (.sh). It also references Windows Task Scheduler as a job scheduler alongside cron, and does not provide explicit PowerShell or Windows batch script examples, but implies their use. The overall flow and examples are cross-platform, but subtle Windows-first ordering and tool mentions are present.
Recommendations
- List Linux/Mac script file types (.sh) before Windows types (.cmd, .bat, .ps1) to avoid Windows-first ordering.
- Provide explicit Linux/macOS automation examples (e.g., cron job setup) before or alongside Windows equivalents.
- Include a PowerShell or Windows batch script example if Windows automation is mentioned, and ensure Linux/macOS examples are equally detailed.
- Reference Linux tools (cron, systemd timers) before Windows Task Scheduler when discussing job scheduling.
- Clarify that all az CLI commands work identically on Linux, macOS, and Windows.
Azure Arc
Azure Arc-enabled data services validation
...lob/main/articles/azure-arc/data/validation-program.md
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page demonstrates mild Windows bias by referencing Windows-centric solutions (e.g., Azure Stack HCI, AKS-HCI) and listing Windows-based partner solutions (DataON, Dell, Hitachi with AKS-HCI, Lenovo ThinkAgile MX) before Linux-focused ones. The prerequisites mention Azure Data Studio and azdata CLI, which are cross-platform, but do not provide explicit Linux/macOS installation or usage guidance. No PowerShell-specific examples or commands are present, and Linux distributions (Red Hat OpenShift, Kublr, Wind River, VMware) are included, but Windows-based solutions are often listed first.
Recommendations
- Add explicit Linux/macOS installation instructions for tools like azdata and Azure Data Studio.
- Ensure partner solutions are grouped or ordered to avoid Windows-first perception (e.g., alternate listing order or group by OS type).
- Include examples or notes for Linux/macOS users where platform-specific steps may differ (e.g., Kubernetes config file location, CLI usage).
- Highlight Linux-native Kubernetes distributions and their validation status more prominently.
Azure Arc
Upload billing data to Azure and view it in the Azure portal
.../articles/azure-arc/data/view-billing-data-in-azure.md
Low Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Excel as the default tool for opening CSV files and omitting any mention of Linux/macOS alternatives. There are no command-line examples or instructions for Linux/macOS users, nor are cross-platform tools suggested for viewing or processing billing data. The workflow assumes GUI-based interaction with the Azure portal, which is accessible from any OS, but the file handling instructions are Windows-centric.
Recommendations
- Mention cross-platform tools for opening CSV files, such as LibreOffice Calc, Numbers (macOS), or command-line utilities like 'cat', 'less', or 'csvkit'.
- Provide examples or references for automating billing data uploads using Linux/macOS shell scripts (e.g., bash, curl, az CLI).
- Clarify that the Azure portal and storage account access are OS-agnostic and can be performed from any modern browser.
- Include a note or section for Linux/macOS users with relevant tips or alternative workflows.
Azure Arc
Configure Authentication for Edge RAG Preview Enabled by Azure Arc
.../articles/azure-arc/edge-rag/prepare-authentication.md
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows Notepad as the suggested tool for storing IDs, and by omitting any mention of Linux/macOS equivalents or cross-platform alternatives. All examples and screenshots are based on the Azure Portal GUI, which is platform-agnostic, but there are no CLI or Powershell examples (which could introduce further bias if present). The reference to Windows Notepad is minor but does signal a default assumption of Windows usage.
Recommendations
- Replace 'Windows Notepad' with 'a text editor of your choice (e.g., Notepad, TextEdit, gedit, nano, etc.)' to be inclusive of all platforms.
- Add a note that the Azure Portal is accessible from any OS with a web browser.
- If CLI instructions are added in future, ensure both Azure CLI (cross-platform) and Powershell (Windows/macOS/Linux) examples are provided.
- Avoid referencing platform-specific tools unless alternatives are listed.
Azure Arc
Requirements for Edge RAG Preview, Enabled by Azure Arc
.../blob/main/articles/azure-arc/edge-rag/requirements.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits mild Windows bias. Windows Server is mentioned first in NFS setup guides, and a Windows machine is suggested as a management host, with references to Windows-specific documentation. Linux is supported and required for VM OS, but Linux examples and guides are less prominent or secondary. There is no explicit PowerShell usage or exclusive Windows-only steps, but Windows tools and patterns are referenced before or alongside Linux equivalents.
Recommendations
- List Linux setup guides before or alongside Windows Server guides for NFS.
- Provide explicit Linux management host instructions and examples, not just Windows.
- Clarify that management tools (Azure CLI, kubectl, Helm) can be installed and used on Linux/macOS, and link to cross-platform installation guides.
- Avoid suggesting Windows as the default or preferred management host; present Linux/macOS as equal options.
- Ensure all referenced configuration and setup articles include Linux/macOS instructions where applicable.
Azure Arc
Customer intent: "As a cloud administrator, I want to understand how to get the region segment of regional endpoints , so that I can configure Azure services in specific regions without errors."
...ob/main/articles/azure-arc/includes/arc-region-note.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for listing regions, but the PowerShell example is shown immediately after the CLI example and uses Windows-centric tooling. There is no explicit Linux shell example (e.g., Bash), and PowerShell is primarily a Windows tool, though it is now cross-platform. The ordering and inclusion of PowerShell may subtly favor Windows users.
Recommendations
- Add a Bash example for listing regions, such as using 'az account list-locations --output table' in a Linux shell context.
- Clarify that Azure CLI works on all platforms and is the recommended cross-platform tool.
- If PowerShell is included, note its cross-platform availability or provide equivalent Bash commands.
- Consider listing examples in the order: Azure CLI (cross-platform), Bash (Linux/macOS), then PowerShell (Windows).
Azure Arc
Simplify network configuration requirements with Azure Arc gateway (preview)
...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 major tasks, but consistently lists Azure PowerShell examples immediately after Azure CLI, and sometimes with more detail. There is a slight Windows bias in the ordering and inclusion of PowerShell, which is a Windows-centric tool, but Linux/macOS users are not blocked from completing any tasks since Azure CLI is cross-platform and all required steps are covered. No Linux-specific tools or patterns (e.g., bash scripts, Linux package managers) are mentioned, but the use of environment variables and CLI commands is compatible with Linux/macOS.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and suitable for Linux/macOS.
- Add Linux/macOS-specific notes or examples where environment variable syntax differs (e.g., export vs. set).
- Consider listing Azure CLI examples first, and clarify that PowerShell is primarily for Windows users.
- Include troubleshooting tips for Linux/macOS environments (e.g., proxy configuration nuances, certificate stores).
Azure Arc
Troubleshoot extension issues for Azure Arc-enabled Kubernetes clusters
...les/azure-arc/kubernetes/extensions-troubleshooting.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
Summary
The documentation demonstrates mild Windows bias by referencing Azure CLI commands and Azure-specific features (such as AKS-ExtensionManager and Azure Policy Gatekeeper) that are primarily managed from Windows environments or with Windows-centric tooling. However, most troubleshooting steps use cross-platform Kubernetes tools (kubectl, helm, jq, bash), and Linux-specific issues (Oracle Linux/RHEL) are addressed. There are no PowerShell-only examples, and Linux/macOS users can follow all procedures.
Recommendations
- Explicitly note that Azure CLI is cross-platform and provide installation links for Linux/macOS.
- Where Azure Policy Gatekeeper or AKS-ExtensionManager is referenced, clarify how Linux/macOS users can manage these features (e.g., via Azure CLI, portal, or REST API).
- Add examples or notes for using Azure CLI on Linux/macOS, especially for commands that may behave differently or require different authentication.
- Ensure that any references to Windows-specific tools or patterns are accompanied by Linux/macOS equivalents or clarifications.
- Continue to provide Linux troubleshooting steps as done for Oracle Linux/RHEL.
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
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell is a Windows-centric tool and is presented as an equal alternative to Azure CLI. In several places, instructions for creating a Kubernetes cluster mention Docker for Windows before Docker for Mac, and PowerShell environment variable examples are given for proxy configuration. There is no explicit Linux shell example for Azure CLI environment variables (e.g., bash vs. PowerShell), and the documentation assumes familiarity with Windows/PowerShell patterns. However, the Azure CLI examples are cross-platform and the instructions do mention Docker for Mac and Linux-compatible tools like KIND and Cluster API.
Recommendations
- Add explicit Linux/macOS shell examples (e.g., bash) for environment variable setup and other commands where PowerShell syntax is shown.
- When listing options for creating clusters, mention Linux-native options (e.g., KIND, Minikube) first, or provide parity in order.
- Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
- Where PowerShell is shown for proxy configuration, also show the equivalent bash export commands.
- Consider adding a table or section summarizing platform-specific steps for Windows, Linux, and macOS.
- Avoid referring to Docker for Windows before Docker for Mac or Linux unless there is a technical reason.
Azure Arc
Azure Arc resource bridge security overview
...rticles/azure-arc/resource-bridge/security-overview.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation mentions retrieving Azure activity logs using PowerShell and Azure CLI, listing PowerShell first. This subtly prioritizes Windows tooling and patterns, though Azure CLI is cross-platform. No explicit Linux/macOS examples or tools are provided, and PowerShell is referenced without noting its availability on Linux/macOS.
Recommendations
- Explicitly state that both PowerShell and Azure CLI are available on Linux/macOS, and provide example commands for each platform.
- When listing tools, alternate the order or clarify cross-platform support to avoid implying Windows-first usage.
- Include Linux/macOS-specific guidance or screenshots where relevant, especially for command-line tasks.
- Add a note or section highlighting parity and any platform-specific considerations.
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
missing_linux_example
Summary
The documentation page for Azure Arc resource bridge system requirements shows mild Windows bias. Azure CLI installation links and references default to Windows, and there are no explicit examples or instructions for Linux/macOS users regarding CLI installation, command usage, or file paths. All CLI examples and management machine requirements assume a Windows environment, with no mention of Linux or macOS equivalents.
Recommendations
- Include explicit instructions and links for installing Azure CLI on Linux and macOS, not just Windows.
- Provide examples of CLI usage and file paths for Linux/macOS environments.
- Clarify that the management machine can be Linux, macOS, or Windows, and list any OS-specific requirements or caveats.
- When referencing CLI commands, note any differences in syntax or behavior across platforms.
- Ensure parity in troubleshooting and maintenance instructions for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page demonstrates a mild Windows bias by mentioning Windows-specific management tools (System Center Virtual Machine Manager, VMware vSphere) and referencing Windows and Linux together, but listing Windows tools first and providing more detail about Windows-centric environments. There are no explicit PowerShell-only examples or missing Linux examples, but the focus on Windows management platforms and tools is more prominent than Linux equivalents.
Recommendations
- Add explicit references to Linux-native management tools or platforms where relevant (e.g., mention integration with Ansible, Cockpit, or other Linux VM management solutions).
- Ensure examples and scenarios highlight Linux environments equally, including lifecycle operations and automation.
- When listing supported environments, alternate or balance the order of Windows and Linux mentions.
- Provide links to documentation or guides specifically for Linux VM management under Azure Arc.
Azure Arc
Archive for What's new with Azure Connected Machine agent
...icles/azure-arc/servers/agent-release-notes-archive.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation consistently lists Windows download links before Linux, and Windows-specific tools (PowerShell, MSI installer, Windows Event Logs, Windows cert store) are mentioned prominently. Some features and enhancements are described with a Windows focus (e.g., GUI installer, Windows-specific logging, dependency upgrades for PowerShell/.NET). Linux features are present and called out, but Windows terminology and tools are often referenced first or exclusively, and PowerShell upgrades are highlighted as major changes.
Recommendations
- Alternate the order of Windows and Linux download links or present them together to avoid Windows-first perception.
- Ensure Linux equivalents are mentioned alongside Windows tools (e.g., if referencing Windows Event Logs, also mention Linux journalctl).
- Highlight Linux-specific enhancements and tools with equal prominence as Windows features.
- Avoid referencing Windows tools (PowerShell, MSI, cert store) without noting Linux equivalents or alternatives.
- Where possible, provide parity in example commands, troubleshooting steps, and tool references for both platforms.
Azure Arc
CLI reference for `azcmagent check`
...lob/main/articles/azure-arc/servers/azcmagent-check.md
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page for `azcmagent check` shows mild Windows bias. The only extended use case explicitly mentioned is 'Windows Server Pay-as-you-go', and the link provided is to Windows-specific documentation. No Linux/macOS-specific examples, flags, or use cases are discussed, and the only extension example is for SQL Server (primarily a Windows workload). However, the command syntax and examples themselves are cross-platform and do not use Windows-only tools or shell syntax.
Recommendations
- Add examples or references for Linux/macOS-specific use cases, such as connectivity checks for Linux-based Arc workloads or extensions.
- Include links to Linux/macOS documentation where relevant, not just Windows Server.
- Mention that the command works identically on Linux/macOS, and clarify any platform-specific behaviors if they exist.
- Provide extension examples for workloads commonly found on Linux (e.g., PostgreSQL, custom scripts).
Azure Arc
CLI reference for `azcmagent connect`
...b/main/articles/azure-arc/servers/azcmagent-connect.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page exhibits mild Windows bias by mentioning Windows-specific authentication methods first and referencing Windows-only interactive browser login as the default. Additionally, the only explicit tool for obtaining an access token is PowerShell's Get-AzAccessToken, with no Linux/macOS equivalent shown. However, most examples and instructions are cross-platform, and Linux authentication flows are described.
Recommendations
- Present authentication options in a platform-neutral order or explicitly call out Linux/macOS flows first where appropriate.
- Add Linux/macOS equivalents for obtaining access tokens (e.g., using Azure CLI: 'az account get-access-token').
- Clarify which examples and flags are valid for Linux/macOS, and provide explicit Linux/macOS command snippets where platform differences exist.
- Where a method is Windows-only, immediately follow with the Linux/macOS alternative in the same section.
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation lists the Windows installation path and PATH update instructions before the Linux equivalent, but otherwise provides parity in information and examples for both platforms. No PowerShell-heavy content or exclusive Windows tools are present.
Recommendations
- Present installation paths for Windows and Linux in parallel or alternate which is listed first.
- Explicitly mention if any commands or flags differ on Linux/macOS, or confirm full parity.
- Add troubleshooting notes for Linux/macOS environments if relevant (e.g., PATH issues, permissions).
Azure Arc
Enable VM extensions to Arc-enabled servers from the Azure portal
...icles/azure-arc/servers/manage-vm-extensions-portal.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation generally presents a neutral, portal-centric workflow applicable to both Linux and Windows Arc-enabled servers. However, in the extension configuration example, only Windows-specific details (proxy for Azure Monitor agent for Windows) are mentioned, with no equivalent Linux example. Windows is referenced first in the extension configuration context, which may subtly prioritize Windows scenarios.
Recommendations
- Include configuration examples for both Windows and Linux extensions, such as proxy settings for the Azure Monitor agent on Linux.
- When mentioning extension-specific configuration, provide parity by referencing Linux scenarios alongside Windows.
- Ensure that screenshots and step-by-step instructions explicitly note any OS-specific differences or requirements.
- Review the ordering of OS mentions to avoid consistently listing Windows before Linux.
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 VM extensions before Linux extensions, listing a larger number of Windows-specific extensions and providing more detailed links for Windows scenarios. However, Linux extensions are also covered in a dedicated section with parity for core functionality. No examples or instructions are shown that are exclusive to Windows, and both OSes are referenced in deployment methods (CLI, PowerShell, portal, ARM templates). There is no evidence of missing Linux examples or exclusive use of Windows tools.
Recommendations
- Present Windows and Linux extension tables side-by-side or alternate their order to avoid Windows-first perception.
- Ensure that the number and detail of Linux extension entries matches those for Windows where possible.
- Add explicit cross-references between Windows and Linux extension documentation for users managing both platforms.
- Include a brief statement at the start clarifying that all extension management features are available for both Windows and Linux, to reinforce parity.
Azure Arc
Connect hybrid machines to Azure using a deployment script
...blob/main/articles/azure-arc/servers/onboard-portal.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page presents Windows installation and validation steps before Linux, with detailed usage of Windows-specific tools (msiexec, PowerShell) and command-line examples. PowerShell is emphasized for scripted onboarding, and Windows installer options are explained in depth. Linux instructions are provided and reasonably complete, but appear after Windows, and some sections (e.g., troubleshooting logs, installer options) are more detailed for Windows.
Recommendations
- Present Linux and Windows instructions in parallel sections, or alternate which OS is described first.
- Provide equally detailed Linux troubleshooting guidance, including log locations and common errors.
- Include Linux equivalents for Windows installer options and environment variable configuration (e.g., using export or systemd for proxy settings).
- Offer Bash script examples for Linux onboarding, matching the PowerShell detail for Windows.
- Reference Linux package manager commands (apt, yum, zypper) for manual installation, similar to msiexec for Windows.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, ensuring that both Linux/macOS and Windows users are supported. However, PowerShell examples are consistently presented alongside Bash, and in some sections, PowerShell appears before Bash, which may subtly prioritize Windows users. There are no examples or references to Windows-only tools, and all instructions are based on the cross-platform Azure CLI. No Linux-specific tools or patterns are omitted, but the documentation does not mention macOS or Linux environments explicitly, nor does it provide troubleshooting or environment setup guidance for those platforms.
Recommendations
- Ensure Bash examples are consistently presented before PowerShell to signal Linux/macOS parity.
- Explicitly mention that all CLI commands work on Linux, macOS, and Windows, and provide links to Azure CLI installation guides for each OS.
- Add a brief note or section on environment setup for Linux/macOS users, including common troubleshooting tips.
- Consider including sample outputs or screenshots from Linux/macOS terminals in addition to Windows/PowerShell where applicable.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring parity for Linux/macOS and Windows users. However, there are subtle signs of Windows bias: PowerShell examples are always present and sometimes shown first in certain sections (e.g., the order of tabs), and some commands (like base64 encoding) are shown in PowerShell but not in Bash. Additionally, the use of Azure Portal and ARMClient for status checks may be more familiar to Windows users. There are no sections that are Windows-only, and Linux/macOS users can complete all tasks, but minor friction exists.
Recommendations
- Ensure Bash (Linux/macOS) examples are always shown first or equally prioritized in tab order and narrative.
- Where PowerShell-specific commands are given (e.g., base64 encoding), always provide the Bash/Linux equivalent.
- Clarify that Azure CLI commands work identically on Linux/macOS and Windows, and note any OS-specific nuances.
- Where tools like ARMClient are used in PowerShell, suggest equivalent curl or REST API usage for Bash users.
- Add explicit notes or links for Linux/macOS users regarding file encoding (UTF-8/BOM) and editors.
Azure Arc
Use Azure Private Link to Connect Servers to Azure Arc by Using a Private Endpoint
...in/articles/azure-arc/servers/private-link-security.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation generally maintains OS parity, but there are several instances of Windows bias. Windows examples and terminology (such as Windows Admin Center, C:\Windows\System32\drivers\etc\hosts) are presented before Linux equivalents, and screenshots are Windows-centric. Windows-specific tools and patterns (Windows Admin Center, Windows agent download link) are mentioned, while Linux alternatives are referenced but less emphasized. Some sections, like troubleshooting and agent installation, mention Linux but provide less detail or fewer direct links for Linux users.
Recommendations
- Present Linux and Windows examples side-by-side or alternate which comes first.
- Include equivalent Linux screenshots and clarify steps for Linux users where only Windows UI is shown.
- Provide direct links and package manager instructions for Linux agent installation (e.g., apt, yum, zypper).
- Expand troubleshooting examples to include Linux-specific commands and scenarios.
- Mention Linux tools (such as SSH) with parity to Windows Admin Center, even if not supported, to clarify limitations for both platforms.
Azure Arc
Plan and Deploy Azure Arc-Enabled Servers
...articles/azure-arc/servers/plan-at-scale-deployment.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates mild Windows bias by mentioning Azure PowerShell and the Azure portal as primary onboarding methods, listing Windows alongside Linux but often referencing Windows tools first. There is a lack of explicit Linux/macOS command-line examples, and automation tooling is described in generic terms without highlighting Linux-native alternatives. The onboarding and management phases reference Windows and Linux together, but Windows-centric tools (PowerShell, Azure portal) are named before Linux equivalents, and no Bash or shell scripting examples are provided.
Recommendations
- Provide explicit Linux/macOS command-line examples (e.g., Bash scripts) alongside PowerShell and portal instructions.
- Mention Linux-native automation tools (such as Ansible, shell scripts) in the automation and deployment sections.
- Ensure that Linux examples are presented with equal prominence and detail as Windows examples.
- Clarify which steps or tools are cross-platform and which are Windows-specific.
- Add troubleshooting and management guidance for Linux/macOS environments.
Azure Arc
How to prepare to deliver Extended Security Updates for Windows Server 2012 through Azure Arc
...azure-arc/servers/prepare-extended-security-updates.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on Windows Server 2012/2012 R2, with all examples, tools, and procedures tailored exclusively to Windows environments. Windows-specific management tools (Configuration Manager, Group Policy, SCVMM) are mentioned, and there are no Linux/macOS onboarding or management examples. The documentation does not address how to use Azure Arc for ESUs with Linux servers, nor does it clarify whether Linux systems are supported or excluded.
Recommendations
- Explicitly state that the ESU process is Windows-only if Linux/macOS are not supported, to avoid confusion.
- If Linux/macOS onboarding to Azure Arc is possible, provide parallel examples and instructions for those platforms.
- Mention Linux-compatible management tools (e.g., Ansible, SSH, Linux-native agents) for onboarding to Azure Arc, if applicable.
- Clarify whether any Azure Arc features or ESU delivery mechanisms are relevant to non-Windows servers.
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation presents the Windows example before the Linux example in the section on blocking/allowing Run commands locally. Both platforms are covered with equivalent Azure CLI commands, and no Windows-specific tools or patterns are used elsewhere. There is a minor ordering bias favoring Windows.
Recommendations
- Alternate the order of examples, or present both Windows and Linux examples side-by-side.
- Explicitly state that the instructions apply equally to both platforms where possible.
- Consider including macOS if relevant, or clarify platform applicability.
Azure Arc
Quickstart - Connect a machine to Arc-enabled servers (Windows or Linux install script)
...n/articles/azure-arc/servers/quick-enable-hybrid-vm.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents Windows instructions before Linux in the agent installation section and specifies PowerShell for Windows without mentioning equivalent Linux shell requirements. However, both platforms are covered with clear, separate instructions and examples.
Recommendations
- Alternate the order of Windows and Linux instructions in sections to avoid implicit prioritization.
- Explicitly mention the required shell environment for Linux (e.g., Bash) as is done for PowerShell on Windows.
- Provide parity in detail for both platforms, such as troubleshooting steps or verification commands specific to Linux.
- Where possible, present combined instructions or highlight cross-platform similarities to reinforce equal support.
Azure Arc
Migrate Azure Arc-enabled server to Azure
...rticles/azure-arc/servers/scenario-migrate-to-azure.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation demonstrates a mild Windows bias by consistently mentioning Azure PowerShell and Windows-centric tools first when listing options for managing Azure Arc-enabled servers, such as inventorying and removing VM extensions and reviewing access rights. While Azure CLI and Linux agent links are included, PowerShell is presented as the primary example, and exporting results to CSV (a Windows-centric pattern) is referenced. Linux parity is present but less emphasized.
Recommendations
- Alternate the order of examples, sometimes listing Azure CLI before PowerShell.
- Provide explicit Linux shell (bash) command examples where relevant, especially for exporting data.
- Include notes or sections specifically addressing Linux/macOS workflows and considerations.
- Clarify that both Windows and Linux are supported throughout, and avoid defaulting to Windows-centric terminology (e.g., CSV export via PowerShell).
Azure Arc
Extensions security for Azure Arc-enabled servers
...main/articles/azure-arc/servers/security-extensions.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally maintains parity between Windows and Linux, providing examples for both platforms in most critical sections. However, there is a notable pattern of presenting Windows examples first, using PowerShell for Windows commands, and referencing Windows-specific tools and scenarios (e.g., elevated command console, Windows Server 2012 ESU). Some sections, such as the allowlist value 'Allow/None', reference Windows-specific use cases without mentioning Linux equivalents. The listing of extension management options includes Azure PowerShell before Azure CLI, which is more cross-platform.
Recommendations
- Alternate the order of Windows and Linux examples to avoid implicit prioritization.
- Where Windows-specific scenarios are mentioned (e.g., ESU), clarify the Linux equivalent or explicitly state if not applicable.
- Use cross-platform tools (e.g., Azure CLI) as the primary example when possible, or present both CLI and PowerShell examples side-by-side.
- Ensure that all feature descriptions and recommendations are equally applicable to Linux, or note any platform-specific limitations.
- Explicitly mention macOS where relevant, or clarify if only Windows and Linux are supported.
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
powershell_heavy
Summary
The documentation page presents troubleshooting steps for both Windows and Linux, but Windows examples and tools are consistently mentioned first. Windows-specific tools and paths (e.g., PowerShell syntax, Windows environment variables, %TEMP%, %ProgramData%) are referenced before their Linux equivalents. PowerShell-style commands are used for Windows, while Linux commands use bash. Some troubleshooting steps and log file locations are described with Windows paths first, and Windows error codes are listed before Linux ones. The overall structure and examples prioritize Windows, which may create friction for Linux users.
Recommendations
- Alternate the order of Windows and Linux examples so Linux is shown first in some sections.
- Provide Linux-specific troubleshooting steps and file paths before or alongside Windows equivalents.
- Use neutral language when referring to tools and commands, e.g., 'run the command as administrator/root' instead of 'run as administrator'.
- Ensure Linux error codes and log locations are given equal prominence and detail.
- Add explicit notes or sections for macOS if supported.
- Where PowerShell is referenced, provide equivalent bash or shell commands for Linux users.
Azure Arc
Overview of Azure Connected Machine agent to manage Windows and Linux machines
...center-virtual-machine-manager/agent-overview-scvmm.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides a reasonably balanced overview of the Azure Connected Machine agent for both Windows and Linux. However, in the 'Agent resources' section, Windows installation details are presented before Linux, and the Windows section is somewhat more detailed (e.g., security groups, service accounts, Group Policy notes) than the Linux equivalent. There are no PowerShell-heavy examples, Windows-only tools, or missing Linux examples, but the ordering and depth of Windows content may subtly signal Windows as the primary platform.
Recommendations
- Present Windows and Linux installation details in parallel or alternate the order in different sections to avoid implicit prioritization.
- Ensure Linux installation details include equivalent information to Windows (e.g., security groups, service accounts, troubleshooting tips) if applicable.
- Add explicit notes where platform-specific differences exist, so Linux users are aware of what does and does not apply.
- Consider a summary table comparing Windows and Linux agent behaviors and resources for quick reference.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all commands, but the PowerShell tab is present and fully populated, which is a Windows-centric shell. The Bash tab appears first, but the PowerShell examples are given equal prominence and detail. There is no explicit mention of Linux-specific tools, nor are there any examples for macOS Terminal or Linux-specific patterns beyond Bash. No Windows-only tools are referenced, and the Azure CLI commands are cross-platform. However, the presence of PowerShell examples may signal a slight Windows bias, especially since PowerShell is not the default shell on most Linux/macOS systems.
Recommendations
- Clarify that Bash examples are suitable for Linux and macOS users, and PowerShell is for Windows users.
- Consider adding a note about PowerShell Core availability on Linux/macOS, if relevant.
- If possible, provide explicit Linux/macOS terminal instructions or troubleshooting notes for common issues (e.g., file path differences, environment variable syntax).
- Ensure that all examples work as shown in native Linux/macOS environments, not just WSL or PowerShell Core.
- Add a brief section on shell selection for cross-platform users.
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 all commands, ensuring parity between Linux/macOS and Windows users. However, in each section, Bash examples are shown before PowerShell, which is the opposite of Windows bias ('windows_first'). There is no evidence of Windows bias such as exclusive use of Windows tools, missing Linux examples, or PowerShell-heavy content.
Recommendations
- No changes needed for Linux parity; both Bash and PowerShell examples are provided.
- Continue to maintain equal coverage for both platforms in future updates.
- Consider explicitly stating that commands work on Linux, macOS, and Windows to reassure users.
Azure Arc
Disaster recovery - SQL Managed Instance enabled by Azure Arc - portal
...-arc/data/managed-instance-disaster-recovery-portal.md
Low Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes disaster recovery configuration using the Azure portal, which is a web-based interface and not inherently Windows-specific. However, there is a subtle Windows bias in that the portal workflow is often associated with Windows environments, and there are no examples or mentions of Linux/macOS-specific tools or workflows. Additionally, the documentation does not provide parity for Linux users in terms of command-line or automation options within this page, though it does link to a CLI-based guide in 'Related content'.
Recommendations
- Explicitly state that the Azure portal is accessible from any OS with a supported browser, including Linux and macOS.
- Add a brief note or section highlighting cross-platform access, reassuring non-Windows users.
- Consider including CLI or automation examples directly in this page, or more prominently reference the CLI guide for users who prefer or require non-GUI workflows.
- Where screenshots or instructions reference OS-specific behaviors (e.g., file dialogs, browser compatibility), clarify cross-platform support.
Azure Arc
CLI reference for `azcmagent extension`
...main/articles/azure-arc/servers/azcmagent-extension.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
Summary
The documentation demonstrates mild Windows bias by listing Windows service management commands (Stop-Service/Start-Service) before their Linux equivalents (systemctl stop/start), and by referencing a Windows-specific extension ('AzureMonitorWindowsAgent') in examples. However, Linux equivalents are present and the core CLI commands are platform-agnostic.
Recommendations
- Alternate the order of Windows and Linux commands when describing service management, or present them side-by-side.
- Include examples using Linux-specific extensions (e.g., 'AzureMonitorLinuxAgent') to balance platform representation.
- Explicitly state that all CLI commands work identically on Linux/macOS and Windows.
- Add a note clarifying service names and management commands for both platforms.
Azure Arc
CLI reference for `azcmagent disconnect`
...ain/articles/azure-arc/servers/azcmagent-disconnect.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation shows minor Windows bias by mentioning Windows-specific authentication methods first and referencing a Windows-only interactive browser login. Additionally, the only tool explicitly referenced for obtaining an access token is the Windows PowerShell cmdlet 'Get-AzAccessToken', with no Linux/macOS alternatives provided.
Recommendations
- List authentication options in a neutral order or alternate which OS is mentioned first.
- Provide Linux/macOS equivalents for obtaining access tokens, such as using 'az account get-access-token' with Azure CLI.
- Clarify which authentication methods are available on Linux/macOS and provide explicit instructions or examples for those platforms.
- Where a method is Windows-only, immediately follow with Linux/macOS alternatives to ensure parity.
Azure Arc
Deliver Extended Security Updates for Windows Server 2012
...azure-arc/servers/deliver-extended-security-updates.md
Low Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is exclusively focused on Windows Server 2012 and its management via Azure Arc, with all examples, screenshots, and patching solutions referencing Windows-specific tools and workflows. There are no Linux or macOS examples, nor any mention of how similar ESU workflows would apply to non-Windows operating systems. Windows tools (WSUS, Configuration Manager) are referenced without Linux equivalents, and all instructions assume a Windows environment.
Recommendations
- Clarify early in the documentation that the ESU feature is only applicable to Windows Server 2012, and explicitly state that Linux/macOS servers are not eligible for this workflow.
- If Azure Arc supports similar lifecycle management or patching for Linux servers, provide links or references to those workflows for parity.
- When discussing patching solutions, mention third-party or Azure-native solutions that support Linux, or clarify their applicability.
- Add a note or section for cross-platform administrators explaining how ESU and patching differ for Linux servers managed by Azure Arc.
Azure Arc
How to deploy and configure Azure Monitor Agent using Azure Policy
...b/main/articles/azure-arc/servers/deploy-ama-policy.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation presents both Windows and Linux options for policy templates, but lists the Windows template first. No PowerShell or Windows-specific tools are used, and parity is maintained in instructions. The bias is minor and limited to ordering.
Recommendations
- List Windows and Linux options in alphabetical order or explicitly state that both are equally supported.
- Consider alternating the order of OS examples in related documentation to avoid implicit prioritization.
- Add a note clarifying that both Windows and Linux machines are supported equally.
Azure Portal
Use Azure Copilot with the Azure mobile app
...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation mentions generating CLI and PowerShell scripts as a key scenario, listing PowerShell before CLI. There are no explicit Linux/macOS examples, nor is Bash or other Linux shell scripting mentioned. The documentation does not clarify that CLI commands are cross-platform, nor does it provide parity in examples or terminology for Linux/macOS users.
Recommendations
- Explicitly mention Bash or shell scripting alongside PowerShell when discussing code generation.
- Clarify that Azure CLI is cross-platform and provide examples or notes for Linux/macOS users.
- Add sample prompts or screenshots showing Bash/CLI usage, not just PowerShell.
- Avoid listing PowerShell before CLI unless contextually appropriate; consider alphabetical or platform-neutral ordering.
Azure Arc
Create a Basic Solution with Workload Orchestration
...on/quickstart-solution-without-common-configuration.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently presented after Bash examples, and there is no evidence of exclusive use of Windows tools or missing Linux examples. No Windows-specific tools or patterns are mentioned, and all instructions are cross-platform via the Azure CLI.
Recommendations
- Maintain the current parity between Bash and PowerShell examples.
- Consider alternating the order of Bash and PowerShell tabs in different sections to avoid implicit prioritization.
- Explicitly state that all commands work on Linux, macOS, and Windows to reassure non-Windows users.
- If possible, add a short section on running Azure CLI commands in macOS Terminal to further emphasize cross-platform support.
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, but PowerShell examples are consistently shown immediately after Bash, and sometimes with more detailed variable assignment. There is no explicit Windows-only tooling, but the presence of PowerShell throughout and its parity with Bash may signal a slight Windows bias. No Linux-specific tools or troubleshooting are mentioned, and Bash examples are not always prioritized or expanded upon. However, all commands are cross-platform (Azure CLI), and Linux/macOS users can follow the Bash instructions without issue.
Recommendations
- Explicitly state that Bash instructions are suitable for Linux/macOS and PowerShell for Windows.
- Consider showing Bash examples first, or grouping all Bash instructions before PowerShell to signal Linux parity.
- Add troubleshooting notes for common Linux/macOS issues (e.g., file permissions, line endings, environment variables).
- Mention that Azure CLI is cross-platform and provide links to installation guides for Linux/macOS.
- If relevant, include Zsh or other Linux shell variants for advanced users.
Azure Arc
Create a Basic Solution with Common Configurations with Workload Orchestration
...ation/quickstart-solution-with-common-configuration.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, but PowerShell examples are always shown immediately after Bash, and sometimes include extra variable assignments (e.g., $childName) that are not present in Bash. There is no evidence of exclusive Windows tools or patterns, nor are Linux examples missing. However, the presence of PowerShell tabs throughout and the order of presentation may subtly signal a Windows-centric approach.
Recommendations
- Randomize or alternate the order of Bash and PowerShell examples to avoid implicit prioritization.
- Explicitly state that both Bash and PowerShell are supported equally, and clarify that Bash examples work on Linux/macOS and Windows (via WSL or Git Bash).
- Add a short section on running Bash commands on Windows (e.g., via WSL or Git Bash) for parity.
- Ensure variable naming and usage is consistent between Bash and PowerShell examples, unless platform differences require otherwise.
- Consider adding a 'macOS' label or note to Bash examples to reinforce cross-platform support.
Azure Arc
Service Groups for Workload Orchestration
...cles/azure-arc/workload-orchestration/service-group.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all command-line tasks, but PowerShell examples are consistently shown after Bash. However, the PowerShell examples are more verbose and sometimes include additional context or variable handling that is not present in the Bash examples. There is no evidence of exclusive use of Windows tools or missing Linux examples, as all commands use the cross-platform Azure CLI ('az'), and Bash is always present. The documentation does not mention Windows-specific tools or patterns, nor does it omit Linux/macOS equivalents.
Recommendations
- Ensure that Bash and PowerShell examples are equally detailed and provide the same context, especially for variable handling and file manipulation.
- Consider explicitly mentioning that all examples work on Linux, macOS, and Windows (with Azure CLI installed), to reassure non-Windows users.
- If possible, add a short section clarifying any platform-specific nuances (e.g., file path formats, environment variable syntax) for users on Linux/macOS vs. Windows.
- Maintain parity in example order; alternating which shell is shown first or grouping examples together may help reduce perceived bias.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all CLI steps, but consistently lists Bash first and PowerShell second. There is no exclusive use of Windows tools or patterns, and Linux/macOS users are not blocked from completing any tasks. However, the presence of PowerShell examples throughout and the explicit PowerShell tab may signal a slight Windows bias, especially since PowerShell is less commonly used on Linux/macOS compared to Bash.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows, possibly in a note at the top.
- Consider adding a short section on running PowerShell on Linux/macOS, or explicitly recommend Bash for non-Windows platforms.
- Ensure that any platform-specific nuances (e.g., file path separators, quoting) are called out in notes.
- If possible, add a generic 'az CLI' tab for commands that are identical across platforms, reducing duplication and emphasizing cross-platform parity.
Azure Arc
Multiple Solutions with a Single Shared Dependency at Different Levels
...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all major steps, but PowerShell examples are always present and sometimes shown first in tab order. There is a slight Windows bias in the ordering and presentation, as PowerShell is a Windows-centric shell, and its inclusion may suggest prioritization of Windows environments. However, all commands use the Azure CLI and Helm, which are cross-platform, and Bash examples are provided for every step, ensuring Linux/macOS users can follow along without missing functionality.
Recommendations
- Ensure Bash examples are always listed first in tab order, as Bash is the default shell for most Linux/macOS users.
- Explicitly state that all commands work on Linux/macOS and Windows, and that PowerShell is optional for Windows users.
- Consider adding a note clarifying that the Azure CLI and Helm commands are cross-platform and can be run in any supported shell.
- If possible, provide additional context or troubleshooting tips for Linux/macOS users (e.g., file path differences, shell quoting).
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
windows_first
powershell_heavy
Summary
The documentation consistently presents both Bash and PowerShell examples for all command-line steps. However, in every section, Bash examples are shown first, followed by PowerShell. The PowerShell examples use Windows-specific syntax (backticks for line continuation, .\ for file paths), which is only relevant for Windows users. There are no Linux/macOS-specific troubleshooting notes, nor are there any examples for native Linux shells beyond Bash. No Windows-only tools are used, and the Azure CLI is cross-platform, but the PowerShell examples reinforce a Windows-centric workflow.
Recommendations
- Add explicit notes clarifying that PowerShell examples are for Windows users, and Bash for Linux/macOS.
- Consider including examples for other popular Linux shells if relevant (e.g., zsh, fish), or clarify Bash is recommended.
- Add troubleshooting notes for Linux/macOS users (e.g., file permissions, path issues).
- Where possible, use syntax and file paths that are compatible across platforms, or highlight differences.
- If PowerShell is required on Linux/macOS, mention installation steps or alternatives.
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 lists Azure REST API, CLI, and PowerShell as programmatic options, but consistently mentions PowerShell before CLI, and links to PowerShell deployment instructions before CLI equivalents. Example deployment methods always list PowerShell before CLI, and the 'Next steps' section links to PowerShell before CLI. There are no explicit Linux/macOS examples, and no mention of platform-specific considerations, but the CLI is referenced and linked, which is cross-platform.
Recommendations
- Alternate the order of PowerShell and CLI references, or list CLI first to reflect its cross-platform nature.
- Explicitly mention that Azure CLI works on Linux/macOS and provide example commands for both CLI and PowerShell where appropriate.
- Add notes or examples for Linux/macOS users, especially for deployment steps.
- Ensure that links to CLI and PowerShell quickstarts are presented with equal prominence.
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
windows_first
powershell_heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatic access, but PowerShell is mentioned first in tips and links. PowerShell is a Windows-centric tool, and its prominence may signal a Windows-first bias. However, Azure CLI is cross-platform and included in all relevant sections, so Linux/macOS users are not blocked from completing any tasks.
Recommendations
- Alternate the order of PowerShell and CLI references, or mention CLI first to reflect its cross-platform nature.
- Explicitly state that Azure CLI works on Linux/macOS and provide installation links for those platforms.
- Add a brief note clarifying that PowerShell Core is available cross-platform, but CLI is generally preferred for Linux/macOS.
- Include screenshots or examples from non-Windows environments if possible.
Container Registry
Access Registry Images from ACI
...cles/container-registry/container-registry-auth-aci.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell script links, but the main example uses Azure CLI, which is cross-platform. However, the mention of Azure PowerShell and the explicit linking to PowerShell samples introduces a Windows bias. The note about 'export MSYS_NO_PATHCONV=1' is relevant for bash on Windows, but does not clarify Linux/macOS usage. There is no explicit Linux/macOS example or guidance, and the documentation does not mention platform-specific differences or provide parity for Linux users beyond the CLI example.
Recommendations
- Add explicit Linux/macOS usage notes, including any environment variables or differences in command execution.
- Provide sample scripts or links for bash/zsh on Linux/macOS, not just Azure CLI and PowerShell.
- Clarify that Azure CLI is cross-platform and provide examples of running it on Linux/macOS.
- If mentioning PowerShell, also mention bash/zsh or other common Linux shells to ensure parity.
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, but the PowerShell example is given equal prominence and detail as the CLI example. There is no explicit Linux/macOS bias, but the presence of PowerShell examples (which are primarily used on Windows) and the mention of Azure PowerShell as a main tool may suggest a slight Windows bias. However, the Azure CLI example is cross-platform and shown first, and there are no Windows-only tools or patterns. No Linux-specific examples or tools are missing, but parity could be improved by clarifying cross-platform usage and mentioning Linux/macOS environments explicitly.
Recommendations
- Explicitly state that Azure CLI is cross-platform and works on Linux/macOS/Windows.
- Add a note that Azure PowerShell is available on Linux/macOS, but is most commonly used on Windows.
- Include a brief example of using Azure CLI in a Linux/macOS shell (e.g., bash) to reinforce parity.
- Ensure that all steps and tools mentioned are clearly marked as cross-platform where applicable.
Container Registry
Managed Identity Authentication for ACR
...https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-authentication-managed-identity.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides parallel examples for both Azure CLI and Azure PowerShell throughout, but PowerShell is a Windows-centric tool and is featured as a first-class option alongside the CLI. The introductory sections mention Azure PowerShell before Azure CLI, and PowerShell is presented as an equal alternative even for Linux scenarios (e.g., installing PowerShell on Ubuntu). There are no examples or guidance for native Linux shell scripting or automation beyond Bash/CLI, and no mention of Linux-specific tools or patterns. However, all resource creation and authentication examples use Ubuntu VMs and Bash commands, and Docker installation instructions are Linux-focused.
Recommendations
- Make Azure CLI the primary example and reference, as it is cross-platform and native to Linux/macOS.
- Move Azure PowerShell examples to a secondary section or appendix, clarifying its Windows origins and optional use on Linux.
- Add native Bash scripting examples for automation tasks, rather than relying on PowerShell for Linux users.
- Explicitly mention that PowerShell is not required for Linux users unless they prefer it.
- Highlight Linux-native tools and patterns for authentication and automation where applicable.
Container Registry
Quickstart - Create Registry in Portal
...iner-registry/container-registry-get-started-portal.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for signing in to the registry, but PowerShell is given equal prominence to CLI, which is a Windows-centric tool. There are no Linux/macOS-specific shell examples (e.g., Bash), and PowerShell is presented as a primary option alongside CLI, potentially creating friction for Linux/macOS users who are less likely to use PowerShell. However, Docker installation links are provided for all platforms, and the main workflow is portal- and Docker-based, which is cross-platform.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows.
- Present Azure CLI instructions before PowerShell, or mark CLI as the default/recommended path for non-Windows users.
- Add explicit Bash shell examples for Linux/macOS users where relevant.
- Add a note clarifying platform suitability for each tool (e.g., 'Azure PowerShell is recommended for Windows users; Azure CLI is recommended for Linux/macOS').
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
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication and image deletion, but PowerShell is presented as a recommended method and receives equal prominence as Azure CLI. There are references to Windows-specific tools (Visual Studio Code with Docker extension) and patterns (Control+C for stopping containers, which is universal but often associated with Windows). However, Linux and macOS users are acknowledged in the prerequisites, and all Docker CLI commands are cross-platform. No Linux-specific commands or package manager examples (e.g., apt, yum) are provided, and PowerShell is mentioned before any Linux shell equivalents. There are no Linux/macOS-specific troubleshooting or usage notes.
Recommendations
- Add explicit bash or shell examples for authentication and image deletion, especially for Linux/macOS users.
- Include Linux/macOS-specific notes or troubleshooting tips (e.g., permissions, common issues with Docker on Linux).
- Balance the prominence of PowerShell by providing equivalent bash commands in tabbed sections.
- Mention Linux GUI tools (e.g., GNOME Terminal, Docker Desktop for Linux) alongside Visual Studio Code.
- Clarify that all Docker CLI commands work identically on Linux/macOS, and provide links to Linux/macOS documentation where appropriate.
Container Registry
Error Reference for Registry Health Checks
...-registry/container-registry-health-error-reference.md
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits mild Windows bias in several places. References to 'system variables' and 'system environment variables' are Windows-centric, and the Notary error section describes Windows installation paths and .exe files before mentioning Linux/macOS alternatives. There are no explicit Linux/macOS command examples or environment variable instructions, and Windows terminology appears first or exclusively in some solution steps.
Recommendations
- Include explicit instructions for adding CLI tools (Docker, Helm, Notary) to the PATH on Linux/macOS (e.g., modifying ~/.bashrc or ~/.zshrc).
- When mentioning installation paths, provide Linux/macOS equivalents alongside Windows paths.
- Avoid using Windows-specific terminology like 'system variables' without also mentioning the cross-platform equivalent ('PATH environment variable').
- Ensure examples and troubleshooting steps are provided for both Windows and Linux/macOS users, ideally with parity in detail and order.
- Where file extensions are mentioned (.exe), clarify the Linux/macOS binary naming conventions.
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 page demonstrates a mild Windows bias: environment variable setting uses the Windows 'set' command without showing the Linux/macOS equivalent, and the order of Kubernetes cluster creation examples lists Azure CLI (cross-platform) first, but then Azure PowerShell (Windows-only) before Azure Portal. Most commands use Azure CLI or Helm, which are cross-platform, but the initial environment variable setup and lack of explicit Linux/macOS instructions may cause friction for non-Windows users.
Recommendations
- Provide both Windows and Linux/macOS syntax when setting environment variables (e.g., 'set' for Windows, 'export' for Linux/macOS).
- Explicitly mention that Azure CLI and Helm commands work on Linux/macOS as well as Windows.
- Where PowerShell is referenced, clarify that it is Windows-specific and offer Bash alternatives.
- Consider listing Linux/macOS examples or alternatives alongside or before Windows-specific instructions.
Container Registry
Manage OCI Artifacts and Supply Chain Artifacts with ORAS
...ntainer-registry/container-registry-manage-artifact.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Linux/macOS and Windows examples for key ORAS commands, but Windows examples (using .cmd syntax and .\oras.exe) are consistently shown after Linux/macOS examples. There is a slight bias toward Windows in the authentication section, where Docker Desktop credential store is referenced, and Windows-specific command syntax is included throughout. However, Linux/macOS users are given clear instructions and examples for all major tasks, and Azure CLI commands are cross-platform.
Recommendations
- Present Linux/macOS and Windows examples side-by-side or in tabs to avoid implicit prioritization.
- Explicitly mention Linux credential store alternatives when referencing Docker Desktop.
- Ensure all command examples are provided for both platforms, including any Azure CLI or Docker commands.
- Add a note clarifying that all CLI commands work on Linux, macOS, and Windows, and highlight any platform-specific caveats.
- Consider using platform-agnostic command blocks where possible, and only split out platform-specific syntax when necessary.
Container Registry
Azure Container Registry custom roles
...ainer-registry/container-registry-rbac-custom-roles.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for listing permissions, but PowerShell (a Windows-centric tool) is mentioned alongside CLI rather than as a secondary option. In several places, Azure PowerShell is listed before or equally with Azure CLI, and no Linux/macOS-specific shell examples (e.g., Bash) are given. There is no explicit mention of Linux/macOS compatibility or guidance for users on those platforms, and no examples using native Linux tools.
Recommendations
- Ensure Azure CLI examples are presented first, as CLI is cross-platform and preferred for Linux/macOS users.
- Explicitly state that Azure CLI works on Linux/macOS and provide Bash shell usage examples where relevant.
- Add notes clarifying that Azure PowerShell is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
- Avoid listing PowerShell and CLI together without clarifying platform parity; prioritize CLI for cross-platform documentation.
- Include troubleshooting or environment setup notes for Linux/macOS users where differences may exist.
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
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations, but PowerShell is mentioned alongside CLI in multiple places and given its own dedicated example section. There is no mention of Linux/macOS-specific tools or shell environments, and examples do not clarify cross-platform usage. The ordering of examples sometimes places PowerShell before or alongside CLI, which may subtly prioritize Windows workflows. No Linux-specific commands (e.g., Bash scripts) or guidance are provided, and there is no explicit assurance that all CLI commands work identically on Linux/macOS.
Recommendations
- Add explicit Linux/macOS usage notes for Azure CLI commands, confirming cross-platform compatibility.
- Include Bash shell examples or clarify that CLI commands are intended for Bash/Unix shells as well as PowerShell.
- If PowerShell is mentioned, also mention Bash or other common Linux shells to balance platform representation.
- Consider adding a table or section comparing usage across Windows, Linux, and macOS environments.
- Clarify that Azure CLI is cross-platform and provide installation/use links for Linux/macOS.
Container Registry
Customer intent: "As a security analyst, I want to view vulnerability assessment results for container images, so that I can ensure all security issues are identified and resolved in our container registry."
...ontainer-registry/includes/azure-container-registry.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but PowerShell (a Windows-centric tool) is given equal prominence and is listed immediately after CLI. There is no explicit mention of Linux/macOS compatibility for PowerShell commands, nor any Linux/macOS-specific guidance. The CLI example is cross-platform, but the PowerShell tab may cause confusion or friction for non-Windows users.
Recommendations
- Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Add a note indicating that Azure PowerShell is primarily for Windows, with instructions for Linux/macOS users to use CLI.
- Consider listing CLI examples before PowerShell to emphasize cross-platform support.
- If PowerShell Core is supported on Linux/macOS, explicitly mention this and provide installation guidance.
Container Registry
Quickstart: Deploying the Connected Registry Arc Extension
...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but the PowerShell example is given equal prominence and is not separated by platform context. There is no explicit mention of Linux/macOS prerequisites or environment setup, and Windows/PowerShell is presented as a first-class option, potentially creating friction for Linux/macOS users. However, all critical tasks can be completed using Bash, and the Azure CLI commands are cross-platform.
Recommendations
- Clearly indicate which example is for Windows/PowerShell and which is for Linux/macOS/Bash, using platform tabs or headings.
- Provide explicit guidance for Linux/macOS users in the prerequisites (e.g., mention that Azure CLI and kubectl work on Linux/macOS).
- List Bash/Linux examples first, as Azure CLI is natively cross-platform.
- Remove unnecessary PowerShell-specific syntax or provide equivalent Bash commands for all steps.
- Add troubleshooting notes for common Linux/macOS issues (e.g., file permissions, line endings).
Container Registry
Quickstart- Manage Container Registry Content with Azure Client Libraries
...cles/container-registry/quickstart-client-libraries.md
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page demonstrates mild Windows bias in the 'Prerequisites' section, where Windows-centric tools (Azure PowerShell and Azure Portal) are mentioned before the Azure CLI, and the only example provided for registry creation uses Azure CLI (which is cross-platform, but the ordering suggests a Windows-first mindset). There are no PowerShell-heavy examples, and the rest of the documentation is organized by programming language and uses cross-platform tools and environment variables. No critical Linux/macOS gaps are present.
Recommendations
- List Azure CLI before Azure PowerShell and Portal in the prerequisites section, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that Azure CLI works on Linux/macOS and provide links to installation instructions for those platforms.
- Consider providing a Bash shell example for registry creation alongside the CLI command, or clarify that the CLI command works in Bash and other shells.
- If mentioning Azure PowerShell, also mention Bash or other Linux-native tools for parity.
- Ensure that all environment variable instructions and code samples are clear for both Windows and Linux/macOS users (e.g., variable naming conventions, export/set commands).
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation page demonstrates mild Windows bias. While the main content is platform-neutral, the 'Write and optimize code' section lists 'Generate PowerShell scripts' as a primary capability, and PowerShell is a Windows-centric tool (though available on Linux). Additionally, PowerShell is mentioned before Linux-native equivalents like Azure CLI, and no explicit Linux shell or Bash examples are referenced. The troubleshooting examples mention Power BI (Windows-focused) but do not mention Linux or macOS tools.
Recommendations
- Include explicit examples and references for Linux/macOS users, such as Bash scripts or Linux shell commands.
- Mention Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
- Add troubleshooting scenarios involving Linux/macOS tools (e.g., connecting from Linux clients, using Linux-based monitoring tools).
- Clarify that PowerShell is cross-platform, and provide links to Linux/macOS installation guides where relevant.
- Ensure parity in code generation examples by including Bash, zsh, or other Linux-native shells.
Lighthouse
Onboard a customer to Azure Lighthouse
...ob/main/articles/lighthouse/how-to/onboard-customer.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
minor_windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment and verification tasks, but PowerShell examples are always presented after CLI and before any mention of Linux-specific shell usage. There is no explicit mention of Linux/macOS shell environments (e.g., Bash), nor are there examples using native Linux tools or patterns. The documentation refers to 'Azure PowerShell' and 'Azure CLI' as cross-platform, but does not clarify that both are available on Linux/macOS. There is a slight Windows bias in the ordering and in the lack of explicit Linux/macOS context, but all tasks can be completed on Linux/macOS using Azure CLI or PowerShell Core.
Recommendations
- Explicitly state that Azure CLI and Azure PowerShell Core are available and supported on Linux/macOS, not just Windows.
- Add Bash shell examples for common tasks, or clarify that Azure CLI commands are intended for Bash/Unix shells as well as PowerShell.
- Where PowerShell is mentioned, clarify that PowerShell Core is cross-platform and available on Linux/macOS.
- Include a note or section for Linux/macOS users, confirming parity and listing any platform-specific considerations.
- Consider alternating the order of CLI and PowerShell examples, or grouping them together as 'cross-platform'.
Lighthouse
Cross-tenant management experiences
...hthouse/concepts/cross-tenant-management-experience.md
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page references both Azure PowerShell and Azure CLI for cross-tenant management, listing PowerShell first and providing a more detailed example for PowerShell. While Linux is mentioned in the context of Azure Arc, there are no explicit Linux/macOS-specific examples or tool recommendations. The documentation focuses on Azure portal, PowerShell, and CLI, which are available cross-platform, but the ordering and emphasis slightly favor Windows tools.
Recommendations
- Provide explicit examples for Linux/macOS users, such as bash shell commands or instructions for using Azure CLI on Linux.
- Ensure parity in example detail between PowerShell and CLI, and consider listing CLI first or equally.
- Mention that Azure CLI is cross-platform and highlight any Linux/macOS-specific considerations.
- Include notes or links for installing and using Azure CLI and PowerShell on Linux/macOS.
- Where management tools are referenced, clarify their availability and usage on non-Windows platforms.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents PowerShell instructions before Azure CLI examples in the 'Service providers' section, and references PowerShell-specific commands. While Azure CLI is covered, there are no explicit Linux/macOS-specific notes or examples, and the PowerShell example may implicitly favor Windows users. No Linux-only tools or shell examples are provided.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to avoid implicit Windows-first bias.
- Add explicit notes confirming that Azure CLI commands work on Linux/macOS and provide any necessary platform-specific instructions.
- Include bash or shell script examples for common Linux workflows where appropriate.
- Clarify that Cloud Shell is cross-platform and highlight its use for both Windows and Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation lists Azure PowerShell as a primary method for viewing quota usage, alongside Azure CLI and REST API. PowerShell is a Windows-centric tool, and its mention before Linux-native alternatives (CLI, REST) suggests a mild Windows-first bias. There are no explicit Linux/macOS examples or instructions, and no mention of platform-specific considerations for non-Windows users.
Recommendations
- Provide explicit Linux/macOS examples for quota viewing and management using Azure CLI.
- List Azure CLI before PowerShell when presenting cross-platform options.
- Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Add notes or links for installing and using Azure CLI on Linux/macOS.
- Consider including screenshots or terminal examples from Linux/macOS environments.
Quotas
Increase Azure Storage account quotas
...main/articles/quotas/storage-account-quota-requests.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation lists Azure PowerShell as the first tool for viewing storage account quota usage, followed by Azure CLI and REST API. This ordering subtly prioritizes Windows-centric tooling (PowerShell) over cross-platform options (CLI, REST). No explicit Linux/macOS examples or guidance are provided, and PowerShell is mentioned before CLI, which is more common on Linux/macOS.
Recommendations
- List Azure CLI before Azure PowerShell when presenting tool options, as CLI is cross-platform and widely used on Linux/macOS.
- Provide explicit example commands for both Azure CLI and PowerShell, ensuring parity and clarity for users on all platforms.
- Add a note clarifying that all listed tools (CLI, REST API, PowerShell) are available on Windows, Linux, and macOS, with links to installation guides for each platform.
- Consider including screenshots or terminal snippets for CLI usage, not just portal images.