756
Pages Scanned
235
Pages Flagged
756
Changed Pages
31.1%
% Pages Flagged
Scan Information
Started At: 2026-01-10 00:00:07
Finished At: 2026-01-10 20:21:56
Status: completed
Target Repo: Azure Management
Current Phase: done
Files Queued: 756
Files Completed: 756
Problematic Pages
235 issues found
Azure Arc
Prerequisites | Direct connect mode
...rc/data/create-data-controller-direct-prerequisites.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for connecting a Kubernetes cluster to Azure Arc, but the PowerShell example is given equal prominence despite being primarily a Windows tool. There are no explicit Linux shell (bash) examples or instructions, and the installation instructions for Azure CLI do not mention platform-specific steps for Linux. The documentation assumes familiarity with PowerShell and does not offer parity for Linux users, such as bash or shell script equivalents.
Recommendations
- Add explicit bash/shell examples for Linux users alongside PowerShell examples.
- Clarify installation steps for Azure CLI and Helm on Linux, including package manager commands (e.g., apt, yum).
- Where PowerShell is mentioned, also provide equivalent bash commands or scripts, and indicate which platforms each example applies to.
- Consider listing Linux-native instructions first or in parallel with Windows/PowerShell instructions to avoid Windows-first bias.
- Add troubleshooting notes relevant to Linux environments (e.g., permissions, environment variables).
Create Pull Request
Azure Arc
Configure "BYOM" Endpoint Authentication for Edge RAG
...zure-arc/edge-rag/configure-endpoint-authentication.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 by exclusively providing PowerShell examples and using Windows-specific tools (e.g., .\kubectl.exe). There are no bash or Linux shell equivalents, and the command syntax assumes a Windows environment. This may hinder Linux users from following the instructions effectively.
Recommendations
- Provide equivalent bash/Linux shell commands alongside PowerShell examples.
- Use cross-platform command syntax (e.g., 'kubectl' instead of '.\kubectl.exe') where possible.
- Explicitly mention platform differences and offer guidance for both Windows and Linux users.
- Add notes or tabs to switch between Windows and Linux instructions.
Azure Arc
Simplify Network Configuration Requirements with Azure Arc Gateway
...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits Windows bias in several ways: PowerShell examples are provided for every operation, sometimes before or alongside CLI examples, and Windows-specific tools and patterns (such as referencing PowerShell and Windows Admin Center) are mentioned. Linux-specific instructions are less detailed or absent in some sections, and Windows scenarios are listed first in several places. The documentation also references Windows installation packages and prerequisites for Windows Update and Defender, but does not provide equivalent detail for Linux. While some Linux paths and commands are mentioned (e.g., log file locations), overall, the documentation assumes familiarity with Windows tools and environments.
Recommendations
- Ensure Linux examples are provided for every CLI/PowerShell operation, including bash script syntax and Linux command-line usage.
- List Linux and Windows instructions in parallel, or alternate which is presented first to avoid 'Windows-first' ordering.
- Provide equivalent detail for Linux prerequisites and installation packages, such as referencing Linux package managers and update mechanisms.
- Expand Linux-specific troubleshooting and log access instructions, matching the detail given for Windows.
- Include references to Linux administration tools (e.g., Cockpit, systemd) where appropriate, alongside Windows Admin Center.
- Review scenario lists to ensure Linux scenarios are equally represented and not overshadowed by Windows-centric features.
Azure Arc
Deliver Extended Security Updates for Windows Server 2012
...azure-arc/servers/deliver-extended-security-updates.md
High 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 workflows tailored to Windows environments. There is no mention of Linux servers, Linux equivalents, or cross-platform considerations. Windows-specific tools (WSUS, Microsoft Endpoint Configuration Manager) are referenced, and no Linux patching solutions or examples are provided.
Recommendations
- Explicitly state whether Linux servers are supported or not in the ESU workflow, and clarify any platform limitations.
- If Linux servers can be Arc-enabled and managed, provide parallel instructions or examples for Linux systems, including how to manage security updates and licenses.
- Reference Linux-compatible patch management solutions (e.g., Azure Update Manager for Linux, third-party Linux patching tools) alongside Windows tools.
- Include screenshots or CLI examples (e.g., Bash, Azure CLI) relevant to Linux environments, if applicable.
- Add a section comparing Windows and Linux ESU delivery, or clarify that ESUs are only applicable to Windows Server if that is the case.
Azure Arc
CLI reference for `azcmagent check`
...lob/main/articles/azure-arc/servers/azcmagent-check.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific features (such as 'Windows Server Pay-as-you-go') in the flag descriptions, and linking to Windows documentation. There are no Linux-specific examples, nor is there mention of Linux equivalents or considerations. The examples and usage patterns are generic, but the only extended use case highlighted is Windows-centric.
Recommendations
- Add Linux-specific use cases or flags, such as checks for Linux extensions or scenarios (e.g., SQL Server on Linux, Linux server onboarding).
- Include links to Linux documentation or parity features (e.g., Linux server pay-as-you-go, if available).
- Balance the 'include-all' flag description by mentioning both Windows and Linux extended use cases, or clarify if only Windows is supported.
- Provide example commands relevant to Linux environments, such as those involving Linux-specific extensions or configurations.
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
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows Server 2012 environments, with all examples, scenarios, and licensing guidance tailored exclusively to Windows Server. There are no examples or guidance for Linux servers, nor are Linux tools or patterns mentioned. The page assumes the reader is managing Windows Server infrastructure and does not address cross-platform or Linux-specific needs.
Recommendations
- Include examples and guidance for provisioning ESU licenses for Linux servers, if supported by Azure Arc.
- Mention Linux equivalents or clarify if ESU licensing is not applicable to Linux, to avoid confusion for cross-platform administrators.
- Add references to Linux management tools and patterns where relevant, such as Azure Arc onboarding for Linux VMs.
- Ensure that scenario-based examples include at least one Linux-based environment to demonstrate parity.
- Clarify in the introduction whether the guidance is Windows-only or applicable to other platforms.
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page lists a large number of endpoints, many of which are explicitly Windows-centric (e.g., windowsupdate.com, powershellgallery.com, windows.net, wustat.windows.com, etc.), and references to Microsoft and Windows services dominate the list. There are no examples or mentions of Linux-specific endpoints, tools, or patterns, nor is there guidance for Linux administrators. The page implicitly prioritizes Windows environments and tools, with no parity for Linux users.
Recommendations
- Add a section clarifying which endpoints are relevant for Linux-based Arc-enabled servers, and which are Windows-specific.
- Include examples or notes for Linux administrators, such as how to verify endpoint access using Linux tools (e.g., curl, iptables, firewalld).
- Explicitly mention any Linux-specific endpoints if applicable, or state that all listed endpoints are required regardless of OS.
- Balance references to Windows services with equivalent Linux or cross-platform services where possible.
- Provide guidance for both Windows and Linux environments in any configuration or troubleshooting instructions.
Azure Arc
Cloud-native scripting and task automation with Azure Arc-enabled servers
...-arc/servers/cloud-native/scripting-task-automation.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows tools (RDP, PowerShell, SCCM, Windows Task Scheduler) before or more prominently than their Linux equivalents. PowerShell is discussed as the primary scripting language, with Linux alternatives (SSH, Python) mentioned later or in passing. Examples and scenarios are generally Windows-centric, and there is a lack of explicit Linux shell (bash) or Linux-specific automation examples.
Recommendations
- Provide parallel Linux examples for each Windows-centric scenario, such as using bash scripts with Run Command.
- Mention Linux tools (e.g., cron, Ansible, shell scripting) alongside Windows tools like Task Scheduler and SCCM.
- Include sample scripts or walkthroughs for Linux automation tasks, not just PowerShell.
- Ensure that references to scripting and automation are balanced between PowerShell and bash/Python, and clarify cross-platform support.
- Highlight Linux authentication and management features (e.g., Entra authentication for SSH) with practical examples.
Azure Arc
How to evaluate Azure Arc-enabled servers with an Azure virtual machine
...-arc/servers/plan-evaluate-on-azure-virtual-machine.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally presents Windows examples and tooling before Linux equivalents, with PowerShell commands featured prominently and detailed Windows-specific instructions. Linux instructions are present and reasonably complete, but often follow Windows steps or are less detailed regarding distribution-specific nuances. Windows tools (PowerShell, Windows Firewall) are mentioned by name and with explicit commands, while Linux firewall guidance is more generic and less distribution-specific.
Recommendations
- Alternate the order of Windows and Linux instructions so that neither is consistently presented first.
- Provide equally detailed, distribution-specific Linux examples for common distributions (e.g., Ubuntu, RHEL, SLES) alongside Windows instructions.
- Include Bash and Linux-native command examples wherever PowerShell is used, and avoid assuming PowerShell as the default scripting language.
- Reference Linux tools (e.g., iptables, nftables, firewalld, UFW) with the same specificity as Windows tools.
- Add troubleshooting and verification steps for both Windows and Linux environments with parity in detail and clarity.
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_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All examples, instructions, and screenshots are centered around Windows environments, specifically using Microsoft Configuration Manager and Windows Installer (.msi) packages. The only agent download referenced is the Windows .msi, and the task sequence relies exclusively on PowerShell scripting and Windows paths. There is no mention of Linux equivalents, Linux agent packages, or cross-platform deployment strategies. Linux onboarding scenarios and tools are entirely absent.
Recommendations
- Add parallel instructions and examples for onboarding Linux machines, including references to the Linux agent package (.deb/.rpm) and its download location.
- Provide sample task sequences or automation scripts for Linux environments, such as using Bash scripts or native Linux configuration management tools (e.g., Ansible, shell scripts).
- Include screenshots and walkthroughs for Linux deployment workflows, possibly using Configuration Manager's Linux support or other cross-platform tools.
- Mention differences in agent installation and onboarding between Windows and Linux, and link to Linux-specific documentation where appropriate.
- Ensure that PowerShell examples are complemented by Bash or shell script equivalents for Linux users.
Azure Arc
Migrate Azure Arc-enabled server to Azure
...rticles/azure-arc/servers/scenario-migrate-to-azure.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows by predominantly featuring Azure PowerShell commands and examples, referencing Windows tools and patterns first, and omitting explicit Linux command-line examples (such as Bash or shell scripts). While there are occasional mentions of Linux (e.g., the Linux Guest Agent), actionable steps and code samples are almost exclusively Windows/PowerShell-centric, leaving Linux users with less direct guidance.
Recommendations
- Provide equivalent Linux command-line examples (e.g., Bash, Azure CLI) alongside PowerShell commands for all steps.
- Explicitly mention and link to Linux-specific documentation and tools where available, especially for agent installation and extension management.
- Ensure that instructions for exporting data (such as role assignments) include Linux-friendly methods (e.g., using jq or awk with Azure CLI output).
- When listing tools or commands, present both Windows and Linux options together, or alternate which is mentioned first.
- Add troubleshooting steps and references specific to common Linux migration issues.
Azure Arc
Troubleshoot Azure Arc-enabled servers in disconnected scenarios
...rticles/azure-arc/servers/troubleshoot-connectivity.md
High Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates Windows bias by mentioning Windows-specific tools (Windows Admin Center, Configuration Manager) as contingency options for disconnected servers, without referencing equivalent Linux management tools or approaches. No Linux-specific examples or alternatives are provided, and Windows tools are listed first and exclusively in the local management context.
Recommendations
- Include Linux management tools (e.g., Cockpit, Ansible, SSH, systemd utilities) as contingency options for disconnected servers.
- Provide examples or guidance for managing disconnected Linux Arc-enabled servers, such as using local CLI tools or scripts.
- Ensure parity by listing both Windows and Linux options when discussing local management, and avoid presenting Windows tools exclusively or first.
- Add troubleshooting steps or considerations specific to Linux environments, such as log locations, service management commands, or package update procedures.
Azure Arc
Connect hybrid machines to Azure at scale
...rticles/azure-arc/servers/onboard-service-principal.md
High 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 and PowerShell are mentioned first or more prominently in several places, such as the installation script download instructions and the troubleshooting note. PowerShell examples are provided in detail, while Linux-specific command-line or automation examples are less emphasized or missing. Windows tools and patterns (e.g., PowerShell, Local Administrators group) are referenced more explicitly, and Linux equivalents are not always given equal detail or placement.
Recommendations
- Ensure Linux examples (e.g., shell commands, automation scripts) are presented alongside or before Windows/PowerShell examples.
- Provide explicit Linux troubleshooting notes and guidance, not just Windows/PowerShell-specific notes.
- When referencing administrator permissions, equally describe Linux (root/sudo) and Windows (Local Administrators group) requirements.
- Clarify that both .ps1 (Windows) and .sh (Linux) scripts are generated and provide sample content or usage for both.
- Balance the mention of Windows and Linux tools throughout the documentation, including in prerequisites, examples, and troubleshooting.
- Consider adding a dedicated Linux section or callouts where Linux-specific steps or considerations differ.
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 page exclusively covers troubleshooting TLS configuration issues for Windows, providing only Windows-specific instructions and examples (PowerShell commands, Group Policy, Registry edits). There are no Linux equivalents or guidance for Linux-based Azure Arc-enabled servers, and Windows tools and patterns are mentioned throughout without parity for other platforms.
Recommendations
- Add a dedicated section for troubleshooting TLS/cipher suite issues on Linux, including relevant commands (e.g., using openssl, update-crypto-policy, or editing configuration files such as /etc/ssl/openssl.cnf).
- Provide Linux-specific examples for checking enabled cipher suites (e.g., openssl ciphers, nmap --script ssl-enum-ciphers).
- Include instructions for enabling/disabling cipher suites on common Linux distributions (Ubuntu, RHEL, etc.), referencing appropriate configuration files and commands.
- Clearly indicate which sections apply only to Windows and provide cross-references to Linux troubleshooting guidance.
- Ensure parity in troubleshooting steps and tools for both Windows and Linux environments.
Azure Arc
Upgrade the Azure Arc resource bridge
...l-machine-manager/upgrade-azure-arc-resource-bridge.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily oriented toward Windows environments, specifically SCVMM (System Center Virtual Machine Manager), which is a Windows-only tool. All examples and instructions assume the use of Windows servers and workstations, with no mention of Linux equivalents or cross-platform considerations. The upgrade commands are shown for Azure CLI, but the context and prerequisites (such as VHDX format, SCVMM, and file paths) are Windows-centric. There are no Linux-specific instructions, examples, or troubleshooting steps.
Recommendations
- Clarify whether the resource bridge upgrade process is supported or possible on Linux environments, and explicitly state platform limitations.
- If Linux is supported, provide equivalent instructions for Linux users, including file format considerations (e.g., VHDX vs. VMDK), and example commands for Linux shells.
- Mention any cross-platform tools or approaches, such as running Azure CLI on Linux, and update prerequisites to include Linux-specific requirements if applicable.
- Add troubleshooting steps and examples relevant to Linux environments, or explicitly state that the process is Windows-only if that is the case.
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits a Windows-first bias in several areas: Windows installation details are presented before Linux, with more granular information about Windows-specific artifacts (services, accounts, security groups, environment variables, logs). Windows tools and patterns (MSI installer, Group Policy, NT SERVICE accounts) are described in detail, while Linux equivalents are less emphasized or generalized. There are references to Windows paths and conventions before Linux ones, and troubleshooting/logging examples are more extensive for Windows. Linux instructions are present but less detailed, and there are no Linux-specific troubleshooting or configuration examples (e.g., systemd unit files, SELinux/AppArmor notes).
Recommendations
- Present Windows and Linux installation details in parallel, or alternate order between sections to avoid Windows-first presentation.
- Expand Linux installation details to match Windows granularity: include information about systemd unit files, Linux user/group accounts, permissions, and security context (SELinux/AppArmor).
- Provide Linux-specific troubleshooting steps and log file locations, matching the depth given for Windows.
- Mention Linux package management commands (rpm, deb, apt, yum, zypper) and provide direct examples for installation, upgrade, and removal.
- Discuss Linux environment variable configuration (e.g., /etc/environment, systemd drop-ins) in more detail.
- Include notes about Linux security practices (e.g., sudo usage, file permissions, systemd service isolation).
- Ensure parity in extension management examples: if Windows uses Group Policy, mention Linux equivalents (e.g., configuration management tools like Ansible, Puppet, or native OS mechanisms).
Azure Arc
Clean-Up Script for Workload Orchestration
...es/azure-arc/workload-orchestration/clean-up-script.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page exclusively provides PowerShell script examples and instructions for running the clean-up script, which is a Windows-centric approach. There are no Bash, shell, or Linux-specific instructions or examples, nor is there mention of how Linux or macOS users should execute the script or if an equivalent exists. This creates a bias toward Windows users and may exclude or confuse users on other platforms.
Recommendations
- Provide equivalent instructions for running the clean-up script on Linux and macOS, including how to use PowerShell Core (pwsh) on those platforms.
- Include Bash or shell script alternatives if available, or clarify if the PowerShell script is cross-platform.
- Explicitly state platform compatibility for the script and give installation guidance for PowerShell on non-Windows systems.
- Add example commands for Linux/macOS users, such as using 'pwsh' instead of 'powershell.exe', and note any differences in usage or prerequisites.
Azure Portal
Use Azure Copilot with the Azure mobile app
.../azure-portal/mobile-app/microsoft-copilot-in-azure.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation mentions generating both CLI and PowerShell scripts, but lists PowerShell before CLI, which may suggest a Windows-first approach. There are no explicit Linux-specific examples, tools, or references, and PowerShell (traditionally a Windows tool) is highlighted without equal emphasis on Bash or other Linux-native shells. No Linux command-line examples or patterns are provided.
Recommendations
- List CLI (az CLI) before PowerShell when mentioning script generation, or present them together to avoid perceived prioritization.
- Explicitly mention Bash and Linux shell script generation capabilities if supported by Azure Copilot.
- Provide examples or references for Linux users, such as how to use generated scripts in Bash or other Linux environments.
- Clarify that PowerShell is cross-platform, or provide links to documentation for using PowerShell on Linux and macOS.
- Ensure parity in documentation by including Linux-specific scenarios or tips for mobile users who manage Azure resources from Linux devices.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently presenting Azure PowerShell examples alongside Azure CLI, referencing Windows-specific images (e.g., Windows Server Core), and omitting explicit Linux shell examples (such as Bash or sh). Windows tools and patterns (PowerShell cmdlets, Windows image import) are mentioned or shown before or alongside their Linux equivalents, but Linux-native usage patterns are not covered. There is no mention of Linux-specific shell environments, nor are there examples using Bash, zsh, or other common Linux shells.
Recommendations
- Add explicit Bash or Linux shell examples for all Azure CLI commands, showing usage in a typical Linux terminal.
- Include notes or sections on running Azure CLI commands in Linux environments, including installation and authentication steps specific to Linux.
- Provide parity in image examples by including imports of popular Linux-based images (e.g., Ubuntu, Alpine) alongside Windows images.
- Clarify that Azure CLI commands are cross-platform and demonstrate their use in both Windows and Linux environments.
- Avoid referencing only Windows-specific images (such as Windows Server Core) and balance with Linux container images.
- If PowerShell is shown, also show equivalent Bash scripts for Linux users, especially for authentication and token retrieval steps.
Azure Arc
Choosing the right Azure Arc service for machines
...nt-docs/blob/main/articles/azure-arc/choose-service.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-specific features (such as Extended Security Updates for Windows Server and SQL Server) are highlighted, Windows management tools (SCVMM, PowerShell) are mentioned more frequently and sometimes before Linux equivalents, and onboarding instructions for Azure VMware Solution link to Windows-specific tabs. While Linux is referenced as supported, concrete Linux-specific examples, tools, or onboarding instructions are missing or less emphasized. Automation examples mention PowerShell before Python, and there is a lack of parity in Linux-specific operational guidance.
Recommendations
- Provide explicit Linux onboarding instructions and examples alongside Windows, including links to Linux-specific documentation where available.
- Include Linux-specific management tools and patterns (e.g., systemd, shell scripts) in automation and configuration sections, not just PowerShell.
- Balance feature tables and capability lists by highlighting Linux-specific features and scenarios, such as kernel-level monitoring, SELinux/AppArmor integration, or Linux patching nuances.
- Ensure that documentation links (such as onboarding guides) offer both Windows and Linux tabs or instructions, not defaulting to Windows.
- Add concrete Linux use cases and operational examples (e.g., onboarding Ubuntu or RHEL servers, using Linux CLI tools) to demonstrate parity.
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
windows_first
Summary
The documentation page for preparing Linux with AKS Edge Essentials demonstrates a Windows bias by exclusively using PowerShell-based Invoke-AksEdgeNodeCommand for all Linux configuration examples. This approach assumes users are operating from a Windows environment or using Windows-native tools to manage Linux nodes, rather than providing direct Linux shell commands or instructions for Linux-native management. No Linux shell (bash) equivalents are provided, and Windows-centric tooling is presented as the default method.
Recommendations
- Provide direct Linux shell (bash) command examples for each step, allowing users to execute commands natively on Linux nodes.
- Include instructions for running these commands via SSH or local terminal on Linux, not just through Windows-based orchestration tools.
- Clarify when Windows tools are optional or required, and offer Linux-native alternatives where possible.
- Reorder examples to present Linux-native methods first, or side-by-side with Windows/PowerShell approaches, to avoid implying Windows is the primary or only supported management platform.
Azure Arc
Azure Arc-enabled data services - Automated validation testing
...ticles/azure-arc/data/automated-integration-testing.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page demonstrates mild Windows bias. While the majority of instructions and examples use cross-platform tools (kubectl, git, bash), there are several instances where Windows-specific concerns are addressed before Linux equivalents, such as the handling of CRLF vs LF line endings and screenshots from VSCode on Windows. Additionally, Azure CLI usage is shown in PowerShell terminals, and references to Azure Portal are more prominent than Linux-native alternatives. There is little explicit mention of Linux-specific workflows, and no Linux-only examples or troubleshooting tips are provided.
Recommendations
- Add explicit Linux terminal screenshots and instructions alongside Windows/PowerShell examples.
- Provide guidance for Linux users on editing files, such as using 'dos2unix' to convert CRLF to LF, and mention common Linux editors (vim, nano) for configuration.
- Include troubleshooting tips for Linux environments (e.g., file permissions, SELinux/AppArmor issues on OpenShift).
- Balance Azure Portal instructions with CLI-only alternatives, especially for users who prefer not to use a GUI.
- Clarify that all CLI commands are cross-platform and provide notes for any platform-specific differences.
- Ensure that any mention of Windows-specific issues (like CRLF) is matched with Linux-specific advice where relevant.
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
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page, while focused on Linux preparation, frequently uses Windows-centric tools and patterns. Notably, it instructs users to open configuration files in Notepad (a Windows application), and uses the Invoke-AksEdgeNodeCommand cmdlet, which is a PowerShell/Windows-specific command, to run Linux commands on nodes. There is an implicit assumption that the user is operating from a Windows environment, even when managing Linux clusters. Linux-native alternatives (e.g., using nano/vim for editing, direct SSH for command execution) are not mentioned.
Recommendations
- Provide Linux-native instructions for editing configuration files (e.g., using nano, vim, or other Linux text editors).
- Include direct Linux shell commands for checking and setting sysctl parameters, rather than relying solely on Windows/PowerShell cmdlets.
- Clarify whether the workflow assumes a Windows management workstation, and if so, provide parallel instructions for Linux-based management.
- Ensure that examples and tooling are presented in a platform-neutral way, or offer both Windows and Linux alternatives side-by-side.
Azure Arc
Deploy Azure Arc-enabled data services in Active Directory authentication - prerequisites
...icles/azure-arc/data/active-directory-prerequisites.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a clear Windows bias. All examples and instructions for managing Active Directory objects (OU creation, user creation, permissions) are provided using Windows GUI tools (Active Directory Users and Computers) and PowerShell cmdlets. There are no equivalent instructions or examples for performing these tasks from Linux environments or using cross-platform tools. The prerequisite steps assume the presence of a Windows domain controller and reference a Windows-specific guide for domain controller setup.
Recommendations
- Provide equivalent instructions for managing Active Directory objects using cross-platform tools such as ldapadd, ldapmodify, or samba-tool, which can be used from Linux environments.
- Include examples for creating OUs and users via LDAP commands or scripts that work on Linux.
- Reference documentation or guides for setting up Active Directory-compatible services (e.g., Samba AD DC) on Linux, in addition to Windows Server.
- Clearly indicate which steps require Windows-only tools and suggest alternatives for Linux administrators.
- Ensure parity in screenshots and step-by-step instructions for both Windows and Linux environments where possible.
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily through the use of PowerShell syntax in all SQL Server connectivity examples, with no mention of Linux shell alternatives. The examples for connecting to the SQL Server pod use PowerShell command blocks, which may not be directly usable on Linux or macOS systems. There are no bash or shell script equivalents provided, and the documentation does not acknowledge Linux-specific tools or workflows, despite the Kubernetes context being cross-platform.
Recommendations
- Provide Linux/bash shell equivalents for all PowerShell examples, especially for connecting to the SQL Server pod using sqlcmd.
- Use generic shell command blocks (e.g., 'sh' or 'console') instead of 'powershell' when the command is not Windows-specific.
- Explicitly mention that the commands can be run from Linux, macOS, or Windows, and clarify any platform-specific prerequisites.
- Include notes or sections for Linux users, highlighting any differences in environment setup, tools, or command syntax.
- Review all command examples to ensure they are cross-platform, or provide platform-specific instructions where necessary.
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
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
windows_path_examples
Summary
The documentation demonstrates a mild Windows bias: Windows examples and tabs are consistently listed before Linux, and Windows-specific command patterns (such as using 'type' and backslash paths) are shown. There are multiple notes about Windows-specific issues (e.g., kubectl cp failing with absolute Windows paths), but Linux equivalents are present and complete. No PowerShell-specific commands are used, and Linux instructions are provided for every step.
Recommendations
- Alternate the order of Windows and Linux tabs/examples, or list Linux first to avoid implicit prioritization.
- Provide a brief explanation of differences between Windows and Linux command patterns at the start, rather than repeating notes.
- Use platform-neutral variable names and paths in generic instructions before showing platform-specific examples.
- Consider including macOS examples if relevant, or clarify that Linux instructions apply to macOS.
- Ensure that troubleshooting notes are provided for both 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
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools (SSMS, ADS) are mentioned and visually highlighted, while Linux/Mac instructions are less detailed and lack graphical examples. The narrative and examples often mention Windows first or exclusively, and do not provide parity in tooling or troubleshooting for Linux users. There is no mention of Linux-specific SQL client alternatives or troubleshooting steps, and the documentation assumes familiarity with Windows-centric patterns.
Recommendations
- Provide graphical walkthroughs or screenshots for Linux/Mac clients using Azure Data Studio or alternative tools.
- Include troubleshooting steps and environment setup for Linux/Mac, such as Kerberos configuration and common issues.
- Mention and provide examples for Linux-native SQL clients (e.g., DBeaver, SquirrelSQL) alongside sqlcmd.
- Ensure that Linux/Mac instructions are as detailed and prominent as Windows instructions, including step-by-step connection guides.
- Avoid listing Windows tools and examples before Linux equivalents; present both platforms in parallel where possible.
Azure Arc
Turn on transparent data encryption in SQL Managed Instance enabled by Azure Arc (preview)
...igure-transparent-data-encryption-sql-managed-instance.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_path_examples
windows_notes
Summary
The documentation provides both Windows and Linux examples for file operations (copying certificates/keys), but Windows instructions and notes are often presented first or given special attention. Windows-specific issues (such as absolute path problems with kubectl cp) are called out in notes, and Windows path syntax (e.g., $HOME\sqlcerts\servercert.crt) is used in examples. Linux equivalents are present and correct, but Windows is prioritized in ordering and troubleshooting.
Recommendations
- Alternate the order of Windows and Linux instructions so neither is consistently prioritized.
- Add troubleshooting notes for Linux where relevant, not only for Windows.
- Use neutral or cross-platform environment variable syntax (e.g., $HOME/sqlcerts/servercert.crt) in generic examples, or clarify both syntaxes.
- Consider a summary table or section highlighting cross-platform differences and best practices.
- Ensure parity in troubleshooting and caveats for both platforms, not just Windows.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools (SQL Server Management Studio, Azure Data Studio) and patterns. While it mentions connecting via sqlcmd on Linux or Windows, the examples and tool recommendations are Windows-first, and there are no Linux-specific client examples (e.g., DBeaver, SquirrelSQL, or command-line tools like isql). The instructions for network configuration focus on Azure CLI and NSG, which are cross-platform, but the client connection guidance lacks parity for Linux users.
Recommendations
- Include explicit examples of connecting from popular Linux SQL clients (e.g., DBeaver, SquirrelSQL, isql).
- Provide step-by-step instructions for Linux environments, such as using native Linux command-line tools and GUI clients.
- List Linux tools alongside Windows tools when suggesting SQL client options, rather than mentioning Windows tools first.
- Clarify any OS-specific requirements or differences in connection steps.
- Add screenshots or terminal output examples from Linux environments to improve parity.
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
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows environments by referencing Windows file paths in command outputs (e.g., C:<current path>\.kube\config), using Azure portal and Azure CLI exclusively (which are cross-platform but often used in Windows-centric workflows), and omitting Linux-specific instructions or examples (such as Linux file paths, shell commands, or package installation steps). There are no examples or notes for Linux users regarding differences in command outputs, file locations, or tool installation, and no mention of Linux-native tools or patterns.
Recommendations
- Include Linux-specific examples and notes, such as showing Linux file paths (e.g., ~/.kube/config) alongside Windows paths.
- Add instructions for installing required tools (Azure CLI, kubectl, Azure Data Studio) on Linux distributions.
- Mention platform differences in command outputs, especially where file paths or environment variables differ.
- Provide alternative instructions for users who prefer command-line workflows over the Azure portal, including bash scripts or Linux shell commands.
- Explicitly state that the instructions apply to both Windows and Linux, and highlight any steps that differ between platforms.
Azure Arc
Deploy Active Directory-integrated SQL Managed Instance enabled by Azure Arc
...c/data/deploy-active-directory-sql-managed-instance.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and patterns (such as Active Directory Users and Computers, setspn, and ktpass) are mentioned prominently and sometimes before their Linux equivalents. The process for creating accounts and SPNs is described using Windows-centric tools and terminology, and Windows PowerShell scripts are provided alongside Linux shell scripts. While Linux tools (adutil, ktutil, bash scripts) are mentioned, the overall flow and examples tend to assume familiarity with Windows administration practices.
Recommendations
- Present Linux and Windows tools/examples in parallel, rather than listing Windows tools first.
- Provide explicit step-by-step instructions for Linux environments (e.g., using adutil or ktutil for SPN and keytab management), not just mention the tools.
- Include screenshots or CLI examples for Linux equivalents of Windows GUI steps (such as creating accounts and DNS records).
- Clarify which steps are OS-agnostic and which require OS-specific tooling, and provide guidance for both.
- Consider a tabbed or side-by-side format for all OS-specific instructions to ensure parity and reduce implicit prioritization of Windows.
Azure Arc
Tutorial – Deploy Active Directory connector in system-managed keytab mode
...eploy-system-managed-keytab-active-directory-connector.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tools (such as 'netdom query fsmo' for identifying the primary domain controller) without providing Linux or cross-platform alternatives. The instructions and examples assume familiarity with Windows Active Directory concepts and tools, and do not mention equivalent Linux commands or approaches for interacting with AD. The only example command-line usage shown is for kubectl, which is cross-platform, but the AD-specific discovery step is Windows-only.
Recommendations
- Provide Linux or cross-platform alternatives for Active Directory domain controller discovery, such as using 'ldapsearch' or other open-source tools.
- Include example commands for querying AD from Linux environments, or reference third-party utilities that can be used outside of Windows.
- Clarify that the AD connector can be managed from non-Windows environments and provide guidance for users who do not have access to Windows machines.
- Where Windows tools are mentioned, add equivalent Linux instructions or note their absence and suggest workarounds.
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
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively referencing Active Directory (a Windows-centric identity solution) and using Windows-style DNS names (e.g., .local). There are no Linux-specific authentication examples, nor is there mention of Linux-native identity solutions (such as LDAP or Kerberos outside of AD). The prerequisites and examples assume familiarity with Windows AD concepts and do not provide parity for Linux-based directory services or authentication patterns.
Recommendations
- Include examples or references for integrating with Linux-based directory services (e.g., OpenLDAP, FreeIPA) where supported.
- Clarify whether non-Windows AD environments are supported, and if so, provide guidance for those scenarios.
- Add notes or sections explaining how Linux administrators can map AD concepts to their environments, or what alternatives exist.
- Use more neutral terminology and examples (e.g., avoid .local DNS names, clarify cross-platform compatibility).
- Explicitly state platform requirements and limitations regarding Active Directory and authentication mechanisms.
Azure Arc
Tutorial – Deploy Active Directory (AD) Connector in customer-managed keytab mode
...loy-customer-managed-keytab-active-directory-connector.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Active Directory concepts and terminology (e.g., NetBIOS, domain controllers, AD DNS servers) that are native to Windows environments. There are no examples or guidance for Linux-based directory services or integration patterns, and Windows-centric terms are used without Linux equivalents or alternatives. The tutorial assumes familiarity with Windows AD tools and does not provide parity for Linux administrators who may use Samba or other non-Windows directory services.
Recommendations
- Include examples or notes for integrating with Linux-based directory services such as Samba/FreeIPA where possible.
- Clarify whether the AD Connector supports non-Windows AD implementations and provide guidance for those scenarios.
- Add references or links to documentation for setting up Active Directory-like environments on Linux.
- Where Windows-specific terminology is used (e.g., NetBIOS, domain controllers), provide Linux equivalents or explain their relevance in cross-platform scenarios.
- Ensure that instructions and examples are not exclusively tailored to Windows administrators, and consider the needs of Linux-first environments.
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias. Installation instructions and tool references often list Windows first or exclusively, such as for kubectl and curl. There are specific notes about using cmd.exe instead of PowerShell on Windows, and PowerShell's curl alias is mentioned, but no equivalent Linux shell notes are given. Linux installation instructions are sometimes less explicit or missing, and there are no Linux-specific usage examples or troubleshooting notes.
Recommendations
- Ensure installation instructions for all tools are equally detailed for Linux, macOS, and Windows.
- Provide Linux shell equivalents where Windows-specific notes are given (e.g., mention bash/zsh usage for curl and kubectl).
- Add troubleshooting notes for Linux environments, similar to the PowerShell/cmd.exe note for Windows.
- List platforms in a neutral order (e.g., alphabetical or grouped together) rather than Windows first.
- Include Linux-specific examples or references where appropriate, such as package manager commands (apt, yum, etc.) for installing tools.
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by emphasizing Windows-centric tools (e.g., SQL Server Management Studio, SQL Server PowerShell, SQL Server Profiler), explicitly listing PowerShell scripting support, and referencing Windows Authentication as a supported feature. There is little to no mention of Linux-native tools, patterns, or authentication mechanisms, and no Linux-specific examples or guidance are provided.
Recommendations
- Include examples and references for Linux-native management tools (e.g., sqlcmd, Azure Data Studio on Linux, or command-line utilities available on Linux).
- Mention and provide guidance for Linux authentication methods (such as Kerberos or local authentication) where relevant.
- Balance the listing of tools by including cross-platform or Linux-preferred options alongside Windows tools.
- Add explicit notes or examples for managing SQL Managed Instance enabled by Azure Arc from Linux environments, including scripting and automation scenarios.
- When listing features such as scripting support, clarify whether Bash, shell scripts, or other Linux scripting environments are supported in addition to PowerShell.
Azure Arc
Data collection and reporting | Azure Arc-enabled data services
...zure-arc/data/privacy-data-collection-and-reporting.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits Windows bias primarily in the examples and terminology used. For instance, billing data examples for Arc-enabled SQL Server include 'osType': 'Windows', 'manufacturer': 'Microsoft', and 'model': 'Hyper-V', with no Linux or non-Microsoft virtualization examples. There are no explicit Linux or cross-platform examples for inventory, billing, or diagnostics. Windows-centric terms and tools (such as SQL Server, Hyper-V, and Windows OS) are referenced, while Linux equivalents (e.g., KVM, Linux OS, or Linux-based SQL deployments) are absent. No PowerShell examples are present, but the overall framing and examples are Windows-first and lack Linux parity.
Recommendations
- Add explicit Linux-based examples for inventory, billing, and diagnostics data, including sample JSON payloads with 'osType': 'Linux', and Linux-specific virtualization (e.g., KVM, VMware).
- Mention Linux deployment scenarios and tools (such as Linux distributions, Linux-based SQL Server, or container runtimes) alongside Windows examples.
- Ensure that any references to OS, manufacturer, or model in examples include both Windows and Linux variants.
- Clarify that Azure Arc-enabled data services support both Windows and Linux environments, and provide guidance for Linux administrators.
- Where relevant, include cross-platform CLI commands and avoid exclusive use of Windows terminology.
Azure Arc
Save costs with reserved capacity
.../articles/azure-arc/data/reserved-capacity-overview.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
Summary
The documentation page demonstrates a Windows bias by referencing the Azure portal and PowerShell as primary management tools, with no explicit Linux-specific examples or instructions. The mention of Azure CLI is brief and secondary, and there are no Linux shell or cross-platform command-line examples. The workflow and terminology (e.g., EA portal, Azure portal navigation) are oriented toward Windows-centric environments, and there is no guidance for Linux users or parity in example commands.
Recommendations
- Include explicit Linux and cross-platform examples using Azure CLI and Bash, especially for reservation management and scope updates.
- Provide step-by-step instructions for managing reservations via Azure CLI, with sample commands for Linux/macOS users.
- Clarify that all management operations can be performed from Linux environments and highlight any differences or prerequisites.
- Add references to Linux-compatible tools and workflows alongside PowerShell and Azure portal instructions.
- Ensure that examples and tool mentions are presented in a platform-neutral order (e.g., 'Azure portal, Azure CLI, PowerShell, or API') rather than Windows-first.
Azure Arc
Resize persistent volume claim (PVC) for Azure Arc-enabled data services volume
...icles/azure-arc/data/resize-persistent-volume-claim.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page demonstrates Windows bias primarily through its use of PowerShell-style variable assignment ($newsize=...) in the PVC patching example, which is not directly compatible with Linux/macOS shells. The variable assignment and quoting style are specific to PowerShell, and no Linux/bash equivalent is provided. Additionally, the documentation does not mention Linux-specific tools or shell patterns, and the only scripting example uses Windows conventions.
Recommendations
- Provide equivalent bash/Linux shell examples for variable assignment and kubectl patch commands, e.g., using export and single quotes.
- Clearly indicate which commands are for PowerShell and which are for bash, or provide both side-by-side.
- Avoid using Windows-specific syntax in generic Kubernetes documentation unless explicitly targeting Windows users.
- Mention Linux tools or patterns where relevant, such as using 'export' or direct command-line patching without variables.
- Add a note about shell compatibility and provide guidance for users on Linux/macOS.
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation demonstrates Windows bias by referencing Windows-specific tools (ktpass.exe), providing a PowerShell script, and detailing password reset steps using Windows GUI tools (Server Manager, Active Directory Users and Computers) without mentioning Linux alternatives. The Linux bash script is mentioned, but Windows tools and workflows are described first and in more detail, while Linux domain controller management is omitted.
Recommendations
- Add instructions for resetting the Active Directory user password using Linux tools (e.g., samba-tool, ldapmodify) for environments where the domain controller is Samba-based or managed from Linux.
- Provide parity in example scripts and workflows, ensuring bash/Linux instructions are as detailed as PowerShell/Windows ones.
- Mention Linux equivalents for Active Directory management, such as using RSAT on Linux, or direct LDAP commands.
- Reorder sections to present Linux and Windows options equally, or clarify which environments each applies to.
- Include troubleshooting steps for Linux-based domain controllers and clarify any differences in keytab rotation processes.
High Priority
View Details →
Detected Bias Types
windows_first
azure_heavy
missing_linux_example
Summary
The documentation page demonstrates a bias towards Azure and Windows-centric environments. Storage class examples and recommendations are almost exclusively focused on Azure Kubernetes Service (AKS), with detailed coverage of Azure-specific storage classes and tools. There is minimal mention of Linux-native storage solutions or patterns, and no explicit Linux or open-source example is provided. The documentation also presents Azure/Windows options before AWS and GCP, and does not offer parity in terms of Linux command-line or storage configuration examples.
Recommendations
- Include examples of configuring storage classes using Linux-native tools and environments, such as NFS, Ceph, or local SSDs on Linux nodes.
- Provide sample YAML manifests for storage classes and persistent volumes that are not Azure-specific, demonstrating usage on generic Kubernetes clusters (including on-premises Linux clusters).
- Add explicit Linux command-line examples (e.g., using bash, sed, jq) for configuration tasks, not just Azure CLI.
- Balance the order of cloud provider recommendations, and include open-source solutions (e.g., Longhorn, Rook/Ceph) as first-class options.
- Reference Linux documentation and best practices for storage configuration alongside Azure/Windows resources.
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides examples for PowerShell and Windows, often listing PowerShell first and sometimes omitting explicit Linux/macOS instructions or relegating them to secondary tabs. Windows-specific tools and patterns (e.g., Task Scheduler, .cmd/.bat scripts) are mentioned before or alongside Linux equivalents, but Linux automation (cron, shell scripts) is only briefly covered. Some sections (e.g., role assignment, managed identity retrieval) have 'N/A' for Windows, but PowerShell is used as the primary scripting example, and Windows environment variable syntax is shown. Linux-specific guidance is less detailed, and Linux-first patterns are not emphasized.
Recommendations
- Provide Linux/macOS examples with equal prominence and detail as Windows/PowerShell examples, including shell scripting and automation patterns.
- List Linux/macOS instructions before or alongside Windows/PowerShell instructions to avoid Windows-first bias.
- Expand Linux automation guidance (e.g., cron usage, systemd timers) and provide sample scripts for Linux environments.
- Include troubleshooting and environment setup steps specific to Linux, such as permissions, package dependencies, and common issues.
- When mentioning Windows tools (e.g., Task Scheduler), also mention Linux equivalents (cron, systemd) with equal detail.
- Avoid using PowerShell as the default scripting language; provide Bash/sh examples where appropriate.
- Ensure all steps (e.g., managed identity retrieval, role assignment) have clear, working Linux/macOS instructions, not just 'N/A' for Windows.
Azure Arc
Upload usage data, metrics, and logs to Azure
...e-arc/data/upload-metrics-and-logs-to-azure-monitor.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides examples for Windows, macOS/Linux, and PowerShell, but Windows examples and notes are presented first in each section. There are specific notes about Windows quoting conventions and environment variable setting, and PowerShell is given its own tab, reinforcing a Windows-centric approach. References to related content include a PowerShell-specific link for service principals. There is no evidence of missing Linux examples, but the ordering and emphasis favor Windows users.
Recommendations
- Present Linux/macOS examples before or alongside Windows examples, rather than always listing Windows first.
- Include Bash scripting examples or references where PowerShell is mentioned, to improve parity for Linux users.
- Add links to Linux-specific documentation for service principal management, not just PowerShell.
- Clarify that Azure CLI commands are cross-platform and highlight any platform-specific differences equally.
- Review related content links to ensure parity between Windows/PowerShell and Linux/Bash resources.
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
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation is heavily biased toward Windows, providing only a Windows/Powershell script and instructions. All examples, folder paths, and installation steps use Windows conventions and tools (e.g., .msi installers, C:\ paths, PowerShell scripting). There is no mention of Linux or cross-platform alternatives, nor are equivalent Linux shell commands or installation instructions provided.
Recommendations
- Add equivalent Linux setup instructions, including a Bash shell script for Ubuntu/CentOS.
- Include Linux-specific download and installation commands for Azure CLI, kubectl, and Helm.
- Present both Windows and Linux examples side-by-side, or clearly indicate platform-specific sections.
- Reference Linux file paths and environment variable management (e.g., ~/.bashrc, /usr/local/bin).
- Mention cross-platform compatibility of Azure CLI, kubectl, and Helm, and link to official installation guides for both Windows and Linux.
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 page provides only a Windows PowerShell script for enabling GPU on AKS enabled by Azure Arc. It exclusively uses Windows-specific tools (e.g., Get-PnpDevice, pnputil, Restart-Service) and patterns, with no mention or example for Linux hosts. There is no guidance for Linux users, and Windows tooling is presented as the default and only option.
Recommendations
- Add equivalent Linux instructions and sample scripts (e.g., using lspci, lsmod, modprobe, systemctl, etc.) for GPU enablement.
- Explicitly state platform requirements and clarify if the procedure is Windows-only, or provide parity for Linux-based Azure Arc hosts.
- Include a section comparing Windows and Linux approaches, highlighting differences and prerequisites for each.
- Ensure related content links include Linux-specific documentation if available.
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 instructions reference Windows-specific tools and services (e.g., Hyper-V, PowerShell cmdlets). There are no Linux shell (bash) equivalents provided, nor are Linux management scenarios discussed. The guidance for setting up a management machine only links to Windows setup scripts, omitting Linux or macOS alternatives.
Recommendations
- Provide equivalent bash shell commands for all PowerShell examples, especially for az CLI usage and node pool creation.
- Include instructions for managing AKS Arc clusters from Linux and macOS machines, with links to relevant setup guides.
- Mention Linux virtualization technologies (such as KVM) where Hyper-V is referenced, or clarify platform requirements.
- Ensure that references to scripts or configuration guides include both Windows and Linux versions.
- Add notes or sections highlighting cross-platform support and any platform-specific caveats.
Azure Arc
Configure DNS for Edge RAG Preview Enabled by Azure Arc
...s/blob/main/articles/azure-arc/edge-rag/prepare-dns.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates Windows bias by exclusively providing instructions for editing the hosts file using Windows-specific paths and tools (Notepad, C:\Windows\System32\drivers\etc\hosts), without mentioning Linux or macOS equivalents. No examples or guidance are given for non-Windows platforms, despite their prevalence in cloud and edge environments.
Recommendations
- Add instructions for editing the hosts file on Linux (e.g., /etc/hosts) and macOS.
- Include examples using common Linux text editors (e.g., nano, vim) and note the need for sudo/root privileges.
- Present platform-specific instructions in parallel or as tabs, ensuring equal visibility for Windows, Linux, and macOS.
- Avoid assuming Windows as the default environment; clarify that steps may differ by OS.
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias in its Azure CLI section by exclusively providing PowerShell-based examples and variable assignments, which are specific to Windows environments. There are no bash or Linux shell equivalents, and the use of PowerShell syntax may confuse or exclude Linux/macOS users. The ordering and example structure implicitly prioritize Windows users, with no mention of cross-platform compatibility or alternative shell instructions.
Recommendations
- Provide equivalent Azure CLI examples using bash syntax, including variable assignments and command execution, to support Linux/macOS users.
- Explicitly state that the Azure CLI commands can be run on any platform, and clarify any platform-specific differences.
- Add a tabbed section for 'Bash (Linux/macOS)' alongside 'PowerShell (Windows)' in the CLI instructions.
- Avoid using PowerShell-specific syntax (e.g., `$variable = value`) as the sole example; include bash-style variable assignment (e.g., `variable=value`).
- Mention prerequisites or installation steps for Azure CLI on Linux/macOS, if relevant.
Azure Arc
Configure Authentication for Edge RAG Preview Enabled by Azure Arc
.../articles/azure-arc/edge-rag/prepare-authentication.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools (e.g., Windows Notepad) as the default for storing configuration values, and by exclusively using Azure Portal GUI instructions without mentioning command-line alternatives (such as Azure CLI or PowerShell for Windows, Bash for Linux). There are no examples or guidance for Linux users, nor are cross-platform tools or workflows discussed.
Recommendations
- Replace references to Windows-only tools (e.g., Notepad) with cross-platform alternatives (e.g., 'a text editor of your choice, such as Notepad, nano, or vim').
- Provide command-line instructions using Azure CLI, which works on both Windows and Linux, alongside GUI steps.
- Explicitly mention that the steps can be performed on any OS and highlight platform-agnostic tools.
- Include screenshots or examples for Linux environments where relevant.
- Add a note or section for Linux/macOS users to clarify any differences in workflow or tool usage.
Azure Arc
Verify Contributor Role for Edge RAG Preview Enabled by Azure Arc
...s/azure-arc/edge-rag/prepare-contributor-permission.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page provides command examples using PowerShell syntax and references the 'az' CLI commands in a way that suggests Windows usage, without mentioning or providing Linux/macOS shell equivalents. There is no explicit guidance or examples for Linux users, such as bash/zsh syntax or platform-specific considerations, which may make the instructions less accessible to non-Windows users.
Recommendations
- Include Linux/macOS shell examples (e.g., bash/zsh) alongside PowerShell commands.
- Clarify that the 'az' CLI is cross-platform and provide instructions for installing and running it on Linux/macOS.
- Avoid assuming PowerShell as the default shell; use generic CLI syntax or provide both PowerShell and bash examples.
- Mention any platform-specific prerequisites or differences in command usage, if applicable.
Azure Arc
Install Networking and Observability Components for Edge RAG Preview Enabled by Azure Arc
...azure-arc/edge-rag/prepare-networking-observability.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page exclusively provides PowerShell-based examples and commands, assuming the user is on Windows or using PowerShell. There are no Bash, Linux shell, or cross-platform CLI examples. Windows-centric tools and patterns (e.g., PowerShell variables, 'start-sleep') are used throughout, and no Linux alternatives or instructions are mentioned.
Recommendations
- Provide equivalent Bash/Linux shell command examples alongside PowerShell, especially for az CLI and kubectl/helm operations.
- Clarify platform requirements and note that commands can be run from Linux/macOS terminals as well, adjusting syntax as needed.
- Avoid using PowerShell-specific constructs (e.g., $variables, start-sleep) without offering cross-platform alternatives.
- Explicitly mention that Azure CLI, kubectl, and helm are cross-platform, and show how to use them from Linux/macOS.
- Add a section or note for Linux users, including installation prerequisites and environment setup.
Azure Arc
Use cluster connect to securely connect to Azure Arc-enabled Kubernetes clusters.
.../main/articles/azure-arc/kubernetes/cluster-connect.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for most steps, but the PowerShell examples are given equal prominence as CLI, and in some cases, PowerShell-specific syntax is used (e.g., variable assignment, base64 decoding). There are no explicit Linux shell examples (e.g., bash, zsh), and the use of PowerShell for environment variable handling and token extraction may not be directly applicable to Linux/macOS users. The documentation does not mention Linux-specific tools or patterns, and the shell commands (kubectl, echo, etc.) are shown in a way that may be ambiguous for non-Windows users.
Recommendations
- Add explicit bash/zsh examples for all steps involving environment variables, token extraction, and file manipulation, especially for Linux/macOS users.
- Clarify which commands are cross-platform (e.g., kubectl, az CLI) and provide OS-specific notes where syntax differs.
- For variable assignment and token extraction, show both PowerShell and bash syntax side-by-side, or use tabs for 'Linux/macOS (bash)' and 'Windows (PowerShell)'.
- Avoid using PowerShell-specific syntax (e.g., $TOKEN = ...) without providing the bash equivalent.
- Mention that Azure CLI and kubectl are cross-platform and provide installation instructions for Linux/macOS as well as Windows.
Azure Arc
Requirements for Edge RAG Preview, Enabled by Azure Arc
.../blob/main/articles/azure-arc/edge-rag/requirements.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates mild Windows bias by listing Windows Server NFS setup guides before Linux equivalents, referencing Windows VM sizes and links, and mentioning a Windows machine as a management host. There is a lack of parity in example depth and ordering, with Windows resources and links often appearing first or exclusively. Linux management scenarios and tools are not described in detail, and some references (e.g., VM sizes) are Windows-centric.
Recommendations
- Present Linux and Windows setup guides in parallel, or list Linux first when the default OS is Linux.
- Add explicit instructions and examples for managing Azure Arc-enabled Kubernetes clusters from Linux hosts, including installation of Azure CLI, kubectl, and Helm on Linux.
- Include Linux VM sizing references and links, not just Windows Server VM sizes.
- Ensure that all tooling and configuration steps (e.g., driver machine setup) have Linux-specific guidance and troubleshooting.
- Review all links and examples to ensure Linux parity and avoid Windows-first ordering.
High 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 Azure CLI usage with PowerShell variables, and omitting equivalent Linux shell (bash) examples. The instructions assume the use of PowerShell, which is native to Windows, and do not mention or demonstrate how to perform the same actions on Linux or macOS systems. Additionally, the use of PowerShell syntax for kubectl commands is atypical for Linux environments.
Recommendations
- Add bash shell examples alongside PowerShell examples for all command-line instructions.
- Explicitly mention that the steps can be performed on Linux/macOS and provide any necessary adjustments (e.g., environment variable syntax differences).
- Use generic CLI syntax (e.g., az, kubectl) without PowerShell-specific variable assignment when possible.
- Clarify that Azure CLI and kubectl are cross-platform tools and provide installation or usage notes for Linux/macOS users.
- Consider reordering examples to present bash/Linux instructions first or in parallel tabs.
Azure Arc
Customer intent: As a cloud administrator, I want to list all Azure Arc-enabled Kubernetes resources, so that I can monitor and manage the connected clusters and their configurations effectively.
...les/azure-arc/includes/azure-arc-enabled-kubernetes.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides command-line examples only for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. There are no explicit Linux shell (bash, zsh) or scripting examples, nor is there mention of Linux-specific patterns or tools. The PowerShell tab is always present and listed before the portal tab, which may reinforce a Windows-first perspective. No Linux-specific guidance or troubleshooting is included.
Recommendations
- Add bash/zsh shell examples for each scenario, using Azure CLI commands as they would be run on Linux.
- Explicitly state that Azure CLI commands work cross-platform and provide any necessary Linux-specific notes (e.g., quoting, environment variables).
- Include troubleshooting or usage notes for Linux environments, such as package installation or authentication differences.
- Consider reordering tabs so that Azure CLI (cross-platform) is listed before PowerShell, or clarify the cross-platform nature of CLI.
- If PowerShell is included, mention PowerShell Core and its availability on Linux, or provide bash equivalents.
Azure Arc
Customer intent: "As a cloud administrator, I want to retrieve the list of enabled resource types for Azure Arc-enabled custom locations, so that I can manage and utilize those resources effectively in our hybrid cloud environment."
...ocs/blob/main/articles/azure-arc/includes/azure-arc.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is historically Windows-centric, though now available on Linux) and the absence of explicit Linux shell (bash) or scripting examples, as well as no mention of Linux-native tools or patterns, suggests a Windows bias. Azure PowerShell is presented as a primary method alongside Azure CLI, and there are no examples using bash, shell scripts, or Linux-specific instructions.
Recommendations
- Add explicit bash/shell examples for running Azure CLI commands on Linux, including environment setup and output parsing.
- Clarify that Azure CLI is cross-platform and provide usage notes for both Windows and Linux environments.
- If Azure PowerShell is recommended, note its availability on Linux and provide installation/usage guidance for Linux users.
- Consider including Linux-native scripting patterns (e.g., using jq for JSON output parsing) to improve parity.
- Review the ordering and prominence of examples to ensure Linux and Windows users are equally supported.
Azure Arc
Simplify network configuration requirements with Azure Arc gateway (preview)
...zure-arc/kubernetes/arc-gateway-simplify-networking.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation consistently presents both Azure CLI and Azure PowerShell examples for all major workflows. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some sections, PowerShell is mentioned before Linux-native patterns. There are no explicit Linux shell script examples, nor any references to Linux-specific tools or package managers. Environment variable examples for proxy configuration are shown for both CLI (Linux-style) and PowerShell (Windows-style), but there is no mention of Linux-specific nuances (such as systemd proxy configuration, bash scripting, or troubleshooting on Linux). The documentation does not reference Linux package managers or provide troubleshooting steps for Linux environments.
Recommendations
- Add explicit Linux shell script examples for key workflows (e.g., using bash, curl, or kubectl in Linux environments).
- Include troubleshooting steps or notes for common Linux proxy configuration issues (such as systemd, environment variables in bash, etc.).
- Reference Linux package managers (e.g., apt, yum) for installing Azure CLI, and clarify prerequisites for Linux environments.
- Consider reordering examples to present Azure CLI (cross-platform, Linux-native) before PowerShell, or clearly indicate CLI as the recommended/default for Linux.
- Add notes on file permissions, SELinux/AppArmor, or other Linux-specific security considerations when onboarding clusters.
Azure Arc
Quickstart: Connect an existing Kubernetes cluster to Azure Arc
...les/azure-arc/kubernetes/quickstart-connect-cluster.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Examples and instructions are consistently provided for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. Where cluster creation is discussed, Docker for Windows is mentioned explicitly and equally with Mac, but Linux is not mentioned, despite being a common platform for Kubernetes. Proxy environment variable examples are given for Bash (cross-platform) and PowerShell (Windows), but no Linux-specific shell or tool examples are provided. There is no mention of Linux-native alternatives to PowerShell, nor are Linux-specific instructions or troubleshooting steps highlighted. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users in terms of example commands or environment setup.
Recommendations
- Add explicit instructions and examples for Linux users, such as using Bash or other Linux shells for environment variable configuration.
- Include references to Docker for Linux when discussing cluster creation options, not just Docker for Mac and Windows.
- Provide troubleshooting steps and environment setup examples for Linux environments, including common Linux package managers and shell usage.
- Mention Linux-native alternatives to PowerShell where appropriate, or clarify that Azure CLI is fully supported on Linux.
- Ensure that all examples and instructions are platform-neutral or include platform-specific tabs for Windows, Mac, and Linux where differences exist.
Azure Arc
Diagnose connection issues for Azure Arc-enabled Kubernetes clusters
...les/azure-arc/kubernetes/diagnose-connection-issues.md
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation provides both Linux and Windows examples for DNS troubleshooting, but the Windows-specific steps (using PowerShell and the Resolve-DnsName cmdlet) are given in detail, including instructions for running a Windows test pod and executing PowerShell commands. The Linux example is more generic, while the Windows example is more elaborate and uses Windows-specific tools. The documentation also references Windows command documentation for nslookup, even though the example uses a Debian pod. Overall, Windows tools and patterns are mentioned explicitly and in detail, sometimes before or in more depth than their Linux equivalents.
Recommendations
- Provide equally detailed Linux troubleshooting steps, such as using dig or other Linux-native DNS tools, and include example outputs.
- Reference Linux documentation for commands like nslookup and host, not just Windows command documentation.
- Ensure that Linux steps are presented with the same level of detail and clarity as Windows steps, including pod creation, command execution, and expected output.
- Consider presenting Linux examples first, or in parallel with Windows examples, to avoid Windows-first bias.
- Clarify when steps are OS-specific and provide clear guidance for both Linux and Windows environments.
Azure Arc
Troubleshoot extension issues for Azure Arc-enabled Kubernetes clusters
...les/azure-arc/kubernetes/extensions-troubleshooting.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Azure CLI commands are shown throughout, which are cross-platform, but some troubleshooting steps (such as enabling AKS feature flags and force-deleting extensions) are more familiar to Windows/Azure users. There is a lack of explicit Linux shell or distribution-specific examples, and no mention of Linux-specific troubleshooting tools or patterns (e.g., systemd, journalctl, bash scripting). The only OS-specific troubleshooting is for Oracle Linux, but even there, the solution is generic. No PowerShell-specific commands are present, but the overall flow assumes Azure CLI and Azure-centric workflows, which are more common in Windows environments. There are no examples using Linux-native tools like grep, sed, or direct shell scripting, and no mention of Linux package managers or service management.
Recommendations
- Add explicit Linux shell examples (e.g., bash, zsh) for common troubleshooting tasks.
- Include troubleshooting steps using Linux-native tools (e.g., journalctl, systemctl, grep, sed) where relevant.
- Provide parity for Linux distributions beyond Oracle Linux, such as Ubuntu, CentOS, or SUSE, especially for extension installation and troubleshooting.
- Mention Linux package managers or service management commands when discussing dependencies or required modules.
- Clarify that Azure CLI is cross-platform, and provide guidance for installing and using it on Linux systems.
- Where AKS or Azure-specific commands are shown, offer alternative approaches for clusters running on Linux outside Azure (e.g., on-premises, other clouds).
Azure Arc
Customer intent: As a network administrator, I want to configure outbound network access for Azure Arc agents in the Azure public cloud, so that they can connect to necessary endpoints for proper functionality and management of connected clusters.
...ubernetes/includes/network-requirements-azure-cloud.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits Windows bias by listing endpoints and authentication domains with Windows-centric naming (e.g., login.windows.net, sts.windows.net, servicebus.windows.net) before mentioning Linux-specific resources. There is reference to Windows tools and endpoints, but no explicit Linux command-line examples or Linux firewall/proxy configuration guidance. The only Linux-specific endpoint (linuxgeneva-microsoft.azurecr.io) is mentioned last, and there are no examples or instructions tailored for Linux environments.
Recommendations
- Provide Linux-specific examples for configuring outbound network access, such as iptables, firewalld, or ufw commands.
- Include sample Linux shell commands for endpoint testing (e.g., curl, wget, nc) alongside any REST or PowerShell examples.
- Ensure that Linux endpoints and tools are mentioned with equal prominence and ordering as Windows equivalents.
- Add guidance for configuring proxies and firewalls on common Linux distributions.
- Clarify that the endpoints are platform-agnostic and provide explicit instructions for both Windows and Linux environments.
Azure Arc
Azure Resource Graph sample queries for Azure Arc-enabled Kubernetes
...rticles/azure-arc/kubernetes/resource-graph-samples.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation references Azure PowerShell before Azure CLI when listing query execution options, which can suggest a Windows-first approach. The mention of Azure PowerShell (commonly associated with Windows environments) and the custom metadata 'devx-track-azurepowershell' reinforce this bias. There are no explicit Linux shell examples (e.g., Bash), nor are Linux-specific tools or instructions provided.
Recommendations
- List Azure CLI before Azure PowerShell when describing cross-platform query execution options, as CLI is natively supported on Linux and macOS.
- Include explicit Bash/Linux shell examples for running queries using Azure CLI.
- Add metadata tags that reflect Linux parity, such as 'devx-track-linux' or similar.
- Clarify that Azure CLI is cross-platform and provide installation/use instructions for Linux environments.
- Avoid implying PowerShell is the primary or default method unless justified by user data.
Azure Arc
Azure Arc-enabled Kubernetes system requirements
...n/articles/azure-arc/kubernetes/system-requirements.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell is featured prominently alongside Azure CLI in all management tool and resource provider registration examples, with PowerShell commands shown before or alongside CLI commands. The documentation references Azure PowerShell and its installation, which is primarily a Windows-centric tool, and does not mention Linux-native alternatives or shell environments (e.g., Bash, zsh) for command-line operations. There is no explicit mention of Linux-specific tooling or patterns, and the examples do not clarify cross-platform usage or provide parity for Linux users beyond Azure CLI.
Recommendations
- Explicitly state that Azure CLI is cross-platform and recommend it as the primary tool for Linux and macOS users.
- Provide Bash/zsh shell examples for Linux users where appropriate, especially for installation and resource provider registration steps.
- Clarify that Azure PowerShell is available on Linux and macOS, but is more commonly used on Windows, and link to installation instructions for non-Windows platforms.
- Add notes or sections highlighting Linux-native workflows and tools, ensuring Linux users are aware of best practices and supported environments.
- Review the ordering of examples to avoid listing Windows/PowerShell commands first by default; alternate or prioritize CLI/Bash examples for broader accessibility.
Azure Arc
Tutorial: Implement CI/CD with GitOps (Flux v2)
...es/azure-arc/kubernetes/tutorial-gitops-flux2-ci-cd.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows/Azure bias. Azure DevOps (a Microsoft/Windows-centric tool) is presented first and in greater detail than GitHub. The tutorial assumes Azure CLI and Azure DevOps familiarity, with step-by-step instructions focused on Azure DevOps workflows, service connections, and permissions. There are no explicit Linux-specific or cross-platform alternatives mentioned for key steps (e.g., service connections, environment variable management, or pipeline setup). The use of Azure CLI and Azure DevOps UI is emphasized, with no mention of Linux-native tools or patterns (such as shell scripts, open-source CI/CD tools like Jenkins, or Linux desktop workflows). While Kubernetes and Helm commands are platform-neutral, the overall flow and examples are tailored to Azure-centric, Windows-preferred environments.
Recommendations
- Provide Linux-specific or cross-platform alternatives for Azure DevOps steps, such as using open-source CI/CD tools (Jenkins, GitLab CI, ArgoCD) and shell scripting.
- Include examples of managing secrets, environment variables, and service connections using Linux-native tools (e.g., kubectl, bash scripts, or open-source secret managers).
- Balance the order and depth of Azure DevOps and GitHub sections, or add a third section for a fully open-source, non-Microsoft workflow.
- Explicitly mention that all CLI commands (Azure CLI, kubectl, Helm) work on Linux, macOS, and Windows, and provide installation instructions for each OS.
- Add troubleshooting tips for Linux users (e.g., file permissions, environment setup, CLI installation issues).
- Reference Linux desktop workflows and editors (VS Code, Vim, etc.) alongside Windows tools where relevant.
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric management tools (e.g., System Center Virtual Machine Manager, Azure Stack HCI, VMware vSphere) and features (ESU, Connected Machine agent) without mentioning Linux equivalents or providing Linux-specific examples. The structure and examples prioritize Windows environments and tools, with no explicit guidance for Linux-based scenarios or tools.
Recommendations
- Add explicit examples and requirements for Linux-based Azure Arc-enabled servers, including common Linux distributions and their network configuration patterns.
- Include references to Linux-native management tools (e.g., Ansible, SSH, systemd) where relevant, alongside Windows tools.
- Provide parity in documentation by listing Linux endpoints, ports, and protocols for Azure Arc features, especially for Connected Machine agent and Kubernetes scenarios.
- Ensure that instructions and examples are not exclusively tailored to Windows environments; offer cross-platform guidance wherever possible.
Azure Arc
Azure Arc resource bridge security overview
...rticles/azure-arc/resource-bridge/security-overview.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias in the 'Security audit logs' section, where PowerShell is mentioned explicitly as a method to retrieve activity log entries, but no Linux-specific examples (such as Bash or Azure CLI on Linux) are provided. The mention of PowerShell before Azure CLI also suggests a Windows-first approach. There are no references to Linux tools or patterns elsewhere in the document, and no explicit Linux usage examples are given.
Recommendations
- Provide explicit examples for retrieving activity logs using Azure CLI on Linux (e.g., Bash commands).
- Mention Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
- Include references to Linux environments and tools where relevant, ensuring parity in instructions and examples.
- Add a note clarifying that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
Azure Arc
Troubleshoot Azure Arc resource bridge issues
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation exhibits several forms of Windows bias. Windows tools and patterns (PowerShell, RDP, Windows paths, time.windows.com) are mentioned before or instead of Linux equivalents. Troubleshooting steps and example commands often reference Windows environments (e.g., PowerShell, Windows file paths, RDP) without providing Linux alternatives. Some error messages and solutions are Windows-centric, and Linux-specific troubleshooting is limited to a few cases (e.g., GLIBC version errors). There is a lack of parity in examples and guidance for Linux users, especially regarding log collection, proxy configuration, and network troubleshooting.
Recommendations
- Provide Linux-specific command examples alongside Windows/PowerShell examples (e.g., use curl, wget, or bash for network tests, and Linux file paths for CLI operations).
- Include troubleshooting steps for common Linux environments (Ubuntu, CentOS, RHEL, etc.), especially for proxy, DNS, and permissions issues.
- Mention Linux equivalents for Windows tools (e.g., SSH instead of RDP, journalctl/logs instead of Event Viewer, timedatectl/NTP instead of time.windows.com).
- Ensure error messages and solutions reference both Windows and Linux scenarios, including file system permissions and process concurrency.
- Add explicit guidance for Linux users in sections that currently only reference Windows or PowerShell (e.g., how to run Azure CLI commands, collect logs, or configure proxies on Linux).
- Balance references to Windows and Linux throughout the documentation, and avoid assuming the management machine is Windows by default.
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric management tools (e.g., System Center Virtual Machine Manager, VMware vCenter), mentioning them before or instead of Linux-native alternatives. There are no explicit Linux management tool examples or references to Linux-specific operational patterns. While Linux is mentioned as a supported OS, examples and tooling focus on Windows environments, and there is a lack of parity in Linux-specific guidance.
Recommendations
- Include examples and references to Linux-native management tools (e.g., libvirt, KVM, OpenStack) alongside Windows tools like SCVMM and VMware vCenter.
- Provide explicit Linux operational scenarios, such as managing Linux VMs using Azure Arc, and reference Linux-specific automation and configuration tools (e.g., Ansible, cloud-init).
- Ensure that examples and instructions are provided for both Windows and Linux environments, including CLI commands and scripts relevant to Linux users.
- Mention Linux-first or cross-platform patterns where applicable, and avoid listing Windows tools before Linux equivalents unless contextually necessary.
- Add links to Linux-focused documentation and best practices for hybrid management with Azure Arc.
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
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific services (e.g., time.windows.com, login.windows.net, sts.windows.net) and mentioning Windows NTP as the default for Hyper-V without discussing Linux alternatives. Windows-related endpoints and tools are listed before or more prominently than their Linux equivalents, and there is a lack of explicit Linux-focused examples or guidance, especially regarding time synchronization and management machine setup.
Recommendations
- Add explicit references to Linux equivalents for services such as NTP (e.g., pool.ntp.org) and authentication endpoints.
- Provide guidance for configuring outbound/inbound connectivity on Linux management machines, including relevant tools and commands.
- Ensure parity in examples and instructions for both Windows and Linux environments, especially for common administrative tasks.
- Clarify when a service or endpoint is Windows-specific and offer Linux alternatives where applicable.
- Include Linux-specific notes for VM deployment, time sync, and package management alongside Windows instructions.
Azure Arc
Azure Resource Graph sample queries for Azure Arc
...blob/main/articles/azure-arc/resource-graph-samples.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation mentions running queries through Azure PowerShell before Azure CLI, which may suggest a Windows-first approach. There is no explicit mention of Linux-specific tools or examples, nor any guidance for Linux users (e.g., bash shell usage, Linux-specific CLI instructions). The focus on PowerShell and lack of Linux parity in examples and instructions indicates a mild Windows bias.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux (bash).
- Include examples or instructions for running queries in a Linux environment, such as using bash or zsh.
- Clarify that Resource Graph Explorer is accessible via the Azure portal from any OS.
- Avoid listing PowerShell before CLI unless there is a technical reason; consider alternating or grouping by platform.
- Add a section or note for Linux users to ensure parity in guidance and examples.
Azure Arc
Archive for What's new with Azure Connected Machine agent
...icles/azure-arc/servers/agent-release-notes-archive.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation consistently lists Windows download links before Linux, highlights Windows-specific tools (e.g., PowerShell, MSI installer, Windows Event Logs), and frequently introduces or upgrades Windows technologies (PowerShell, .NET) before or without Linux equivalents. Windows features and fixes are often described in more detail, and Windows-only enhancements are called out, while Linux-specific examples, tools, or instructions are less prominent or sometimes missing.
Recommendations
- Alternate the order of Windows and Linux download links, or list both together to avoid implicit prioritization.
- Provide equivalent Linux command-line examples and highlight Linux-specific tools (e.g., systemd, journalctl) with the same detail as Windows tools.
- When mentioning upgrades to Windows technologies (e.g., PowerShell, .NET), also note Linux runtime upgrades or equivalents if applicable.
- Ensure Linux-specific enhancements and fixes are described with equal detail and visibility as Windows ones.
- Include explicit Linux troubleshooting steps and log locations where Windows Event Log is referenced.
- Add parity for GUI installer notes by referencing Linux installation scripts or package managers where relevant.
- Review for missing Linux examples in sections that discuss configuration, authentication, and agent management, and add them where absent.
Azure Arc
Overview of the Azure Connected Machine agent
...blob/main/articles/azure-arc/servers/agent-overview.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
windows_heavy_details
Summary
The documentation provides detailed, step-by-step information for both Windows and Linux installations of the Azure Connected Machine agent, but the Windows section is presented first and is more verbose, with additional details about Windows-specific services, security groups, environment variables, and troubleshooting. Windows tools and concepts (MSI installer, Group Policy, NT SERVICE accounts) are described in depth, while Linux equivalents are covered more briefly. Some operational notes (e.g., antivirus exclusions) are Windows-centric. Linux instructions are present but less detailed, and Linux system administration patterns (e.g., systemd, package managers) are mentioned but not explained as thoroughly as Windows concepts.
Recommendations
- Present Windows and Linux installation sections in parallel or alternate order, or begin with a general overview before OS-specific details.
- Expand Linux installation details to match Windows, including more information about service accounts, permissions, and troubleshooting steps.
- Provide Linux-specific operational notes, such as SELinux/AppArmor considerations, package manager commands, and antivirus recommendations for Linux.
- Include explicit Linux examples for any configuration or troubleshooting steps that are shown for Windows (e.g., how to grant service rights, manage log files, or handle post-uninstall artifacts).
- Balance the depth of explanation for system concepts (e.g., security groups, service accounts) between Windows and Linux.
- Where possible, use cross-platform terminology before introducing OS-specific tools or patterns.
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
High 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 is consistently mentioned first in download links and feature tables. Troubleshooting and installation guidance focus on Windows-specific tools (PowerShell, Command Prompt, msiexec), with no equivalent Linux instructions provided. Known issues and fixes are often described in terms of Windows installer behavior, while Linux-specific troubleshooting is absent. Some features and bug fixes are Windows-only, and Windows GUI improvements are highlighted without Linux parity.
Recommendations
- Alternate the order of Windows and Linux in download links and feature tables, or present them side-by-side.
- Provide Linux-specific troubleshooting steps and installer guidance (e.g., using rpm, dpkg, systemctl, or shell commands) where Windows tools are referenced.
- Include Linux equivalents for all Windows-only examples, especially for installation, configuration, and known issues.
- Highlight Linux-specific features and improvements with equal prominence to Windows updates.
- Ensure parity in documentation for GUI and CLI tools, mentioning Linux desktop environments or alternatives if relevant.
- Add explicit notes when a feature or fix is platform-specific, and clarify if/when Linux equivalents are planned.
Azure Arc
CLI reference for `azcmagent connect`
...b/main/articles/azure-arc/servers/azcmagent-connect.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation exhibits Windows bias in several ways. The authentication options section lists 'Interactive browser login (Windows only)' first and describes it as the default, while Linux is only mentioned as the default for device code login. The only explicit tooling reference for obtaining an access token is to the Windows PowerShell cmdlet 'Get-AzAccessToken', with no Linux equivalent (such as Azure CLI or REST API) mentioned. There are no Linux-specific examples or shell commands (e.g., using bash or Linux-specific environment variables), and the examples do not clarify cross-platform usage or differences.
Recommendations
- Add explicit Linux examples, such as using bash commands and environment variables.
- Mention Linux tools (e.g., Azure CLI, curl for REST API) for obtaining access tokens alongside PowerShell.
- Reorder authentication options so that cross-platform or Linux defaults (device code login) are listed first or equally.
- Clarify which examples and flags are platform-agnostic and note any platform-specific behaviors.
- Provide guidance for Linux users on certificate formats, file permissions, and common pitfalls.
Azure Arc
Cloud-native governance and policy with Azure Arc-enabled servers
...es/azure-arc/servers/cloud-native/governance-policy.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows-centric tools (Group Policy, Active Directory, RSoP, gpresult), providing examples and built-in policies only for Windows scenarios (e.g., password complexity, Windows Firewall), and mapping Azure Policy initiatives to Windows security baselines. There are no explicit Linux examples, nor are Linux-specific settings, tools, or compliance scenarios mentioned. The narrative assumes a Windows-centric hybrid environment and omits guidance for Linux server management with Azure Policy.
Recommendations
- Add explicit examples of Azure Policy auditing and enforcement for Linux servers, such as checking SSH configuration, enforcing file permissions, or auditing installed packages.
- Mention Linux equivalents to Windows tools (e.g., using OpenSSH, sudoers, or systemd for configuration management) and how Azure Policy can interact with these.
- Reference built-in Azure Policy definitions relevant to Linux (e.g., ensuring SELinux is enabled, auditing sudo access, or checking for specific services).
- Clarify how Desired State Configuration (DSC) and custom scripts can be used for Linux, including links to Linux DSC documentation and examples.
- Provide a comparison of Azure Policy and common Linux configuration management tools (e.g., Ansible, Chef, Puppet) to help Linux admins understand integration points.
- Ensure that introductory and summary sections mention both Windows and Linux server scenarios to set parity in audience targeting.
Azure Arc
Identity and access management with Azure Arc-enabled servers
...cles/azure-arc/servers/cloud-native/identity-access.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by focusing on traditional Active Directory and Group Policy patterns, mentioning Windows tools (such as LAPS) and management approaches first, and providing more detail for Windows scenarios. Linux access is only briefly mentioned (via SSH), and there are no Linux-specific examples or tools discussed. The page lacks parity in describing Linux identity management practices or hybrid scenarios involving Linux servers.
Recommendations
- Add explicit Linux management examples, such as how Microsoft Entra integrates with Linux servers (e.g., SSH authentication, sudo role mapping, PAM integration).
- Include Linux equivalents for tools and patterns mentioned (e.g., alternatives to LAPS for local account management on Linux, such as sssd or Ansible modules).
- Present both Windows and Linux scenarios side-by-side when discussing hybrid environments, rather than focusing on Windows first.
- Expand on how Azure Arc and Microsoft Entra can be used to manage Linux server identities, including role assignment and access control workflows.
- Reference Linux documentation and best practices for hybrid identity management, ensuring equal coverage.
Azure Arc
Cloud-native monitoring and alerts with Azure Arc-enabled servers
...icles/azure-arc/servers/cloud-native/monitor-alerts.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates subtle Windows bias by referencing Windows-centric tools (System Center Operations Manager, Windows Event logs) before mentioning Linux equivalents (syslog), and by omitting concrete Linux-specific examples or instructions. The examples and terminology lean toward Windows administration patterns, with no PowerShell commands but a general prioritization of Windows tools and workflows.
Recommendations
- Provide explicit Linux examples alongside Windows ones, such as showing how to collect syslog data or configure the Azure Monitor Agent on Linux systems.
- Mention Linux tools and workflows (e.g., journalctl, systemd, logrotate) in parallel with Windows Event logs.
- Include sample queries or configuration steps for both Windows and Linux environments.
- Balance references to legacy tools by mentioning Linux monitoring solutions (e.g., Nagios, Zabbix) alongside SCOM.
- Ensure that all instructions and examples are cross-platform, or clearly indicate platform-specific differences.
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 almost exclusively on Windows Server and SQL Server licensing via Azure Arc, with all examples, features, and workflows centered around Windows environments. There is no mention of Linux server licensing, Linux equivalents, or cross-platform scenarios. Windows-specific tools and patterns (e.g., product keys, ESUs, Azure Update Manager for Windows) are referenced, while Linux licensing and management are omitted.
Recommendations
- Add sections describing how Azure Arc licensing and cost management apply to Linux servers, including any differences or similarities in workflows.
- Provide Linux-specific examples and mention Linux-compatible tools for patching, compliance, and cost management.
- Clarify whether pay-as-you-go or ESU-like models exist for Linux distributions under Azure Arc, or explicitly state if they do not.
- Ensure that documentation addresses hybrid environments with both Windows and Linux servers, offering guidance for administrators managing both.
- Include links to Linux server management documentation within Azure Arc where relevant.
Azure Arc
Deploy Azure Monitor agent on Arc-enabled servers
...es/azure-arc/servers/azure-monitor-agent-deployment.md
High 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, mentioning support for both Windows and Linux. However, examples and tooling references (PowerShell, Azure CLI, ARM templates) are presented in a way that prioritizes Windows-centric tools and patterns. PowerShell is repeatedly mentioned as a primary automation method, with no explicit Linux shell (e.g., Bash) or Linux-native scripting examples. There are no concrete Linux-specific instructions or examples, and the documentation does not clarify differences or considerations for Linux environments.
Recommendations
- Add explicit Linux shell (e.g., Bash) examples for deploying the Azure Monitor agent, alongside PowerShell examples.
- Clarify which deployment methods and tools are recommended or supported for Linux, including any differences in usage or prerequisites.
- Include references to Linux-native automation tools (such as Ansible, shell scripts, or cloud-init) where appropriate.
- Ensure that instructions and examples for both Windows and Linux are presented in parallel, or clearly indicate OS-specific steps.
- Add troubleshooting or notes specific to Linux environments, if applicable.
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
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows Server 2012 and its Extended Security Updates (ESUs, via Azure Arc), with no mention of Linux systems, Linux equivalents, or cross-platform scenarios. All examples, terminology, and service descriptions are specific to Windows environments. There are no Linux-specific instructions, billing scenarios, or references to Linux management tools. The documentation assumes the reader is working exclusively with Windows Server workloads.
Recommendations
- Add explicit statements clarifying whether the ESU billing service is Windows-only or if similar mechanisms exist for Linux servers managed via Azure Arc.
- Include examples or notes for Linux server management via Azure Arc, even if ESUs are not applicable, to help cross-platform administrators understand the scope.
- Reference Azure Arc's capabilities for Linux servers and clarify any differences in billing, licensing, or management compared to Windows servers.
- If relevant, provide links to documentation about managing Linux servers with Azure Arc, including security update and billing practices.
- Avoid assuming all Azure Arc users are managing Windows workloads; acknowledge and address cross-platform scenarios where possible.
Azure Arc
Cloud-native inventory and resource organization with Azure Arc-enabled servers
...s/azure-arc/servers/cloud-native/inventory-resource.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page frequently references Windows-centric tools and concepts (Active Directory, SCCM, Group Policy Objects, OUs) as the primary analogy for Azure resource organization. Examples and comparisons are almost exclusively drawn from Windows environments, with no mention of Linux equivalents (such as LDAP, systemd, or Linux configuration management tools). There are no Linux-specific examples or analogies, and the only operating system mentioned in Azure Resource Graph queries is Windows Server. This creates a bias toward Windows administrators and may leave Linux users without clear guidance on mapping their organizational patterns to Azure.
Recommendations
- Include analogies and examples relevant to Linux environments, such as LDAP organizational units, systemd services, or Linux-native configuration management tools (e.g., Ansible, Chef, Puppet).
- Provide sample Azure Resource Graph queries for Linux servers (e.g., finding all Ubuntu servers or those with specific packages installed).
- Mention how tags and resource groups can be used to organize Linux servers, perhaps referencing common Linux server roles or deployment patterns.
- Describe how Azure Change Tracking and Inventory works for Linux servers, including what types of changes (e.g., package updates, service changes) are tracked.
- Balance references to Windows tools (AD, SCCM, GPOs) with Linux equivalents to ensure parity and inclusivity for cross-platform administrators.
Azure Arc
Next steps for cloud-native server management with Azure Arc-enabled servers
.../articles/azure-arc/servers/cloud-native/next-steps.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools (Windows Admin Center, Configuration Manager, WSUS, GPOs) and providing onboarding/deployment examples that are Windows-centric. There is a lack of explicit Linux onboarding or management examples, and Windows tools/patterns are mentioned before any Linux equivalents (if any). No Linux-specific management tools or onboarding workflows are described.
Recommendations
- Include explicit onboarding instructions and examples for Linux servers, such as using shell scripts, cloud-init, or Ansible for agent installation.
- Mention Linux-native management tools (e.g., cron for automation, Linux package managers for updates) alongside Windows tools like WSUS and GPOs.
- Provide parity in examples: for every Windows Admin Center or Configuration Manager reference, add equivalent Linux workflows (e.g., onboarding via SSH, using Azure CLI on Linux, or automation via shell scripts).
- Clarify that Azure Arc supports both Windows and Linux servers, and link to Linux-specific documentation where available.
- Add troubleshooting and health monitoring examples for Linux agents, not just generic or Windows-focused guidance.
Azure Arc
Cloud-native server management with Azure Arc-enabled servers
...in/articles/azure-arc/servers/cloud-native/overview.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (Active Directory Group Policy, SCCM, MECM, PowerShell remoting, WSUS) as the primary on-premises management paradigms being replaced by Azure Arc. These tools are mentioned before or instead of Linux equivalents. There are no explicit Linux management tool examples (e.g., Ansible, Chef, Puppet, cron, systemd, yum/apt update) or Linux-specific workflows. The scripting and patching sections do not clarify how Linux administrators would transition from their native tools to Azure Arc, and examples or terminology are Windows-heavy.
Recommendations
- Add references to common Linux management tools (e.g., Ansible, Chef, Puppet, cron, systemd, yum/apt, dpkg/rpm, SSH) alongside Windows tools when describing what Azure Arc replaces.
- Provide explicit Linux-focused examples and workflows in sections discussing policy, patching, scripting, and inventory (e.g., how Azure Policy can enforce Linux OS settings, how Update Manager replaces yum/apt update schedules, how Run Command can execute bash scripts).
- Balance the order of tool mentions so that Linux and Windows paradigms are presented equally (e.g., 'Active Directory Group Policy or Linux configuration management tools such as Puppet/Ansible').
- Include sample commands or links for both PowerShell and Bash/CLI usage in Azure Arc scenarios.
- Clarify how identity and access management applies to Linux servers (e.g., integration with sudoers, PAM, SSH key management) as well as Windows.
Azure Arc
Azure Connected Machine Agent Deployment Options
.../main/articles/azure-arc/servers/deployment-options.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page presents onboarding methods for both Linux and Windows, but several methods and examples are Windows-centric. Windows-specific tools (Windows Admin Center, Group Policy, Configuration Manager) are listed as dedicated options, while Linux equivalents (such as Cockpit, Ansible, or native Linux automation tools) are absent. PowerShell is mentioned as a cross-platform method, but the documentation does not clarify Linux shell alternatives or provide bash examples. Windows methods are described in more detail and appear before any Linux-specific guidance, indicating a Windows-first bias.
Recommendations
- Add Linux-specific onboarding examples, such as bash scripts or shell commands, alongside PowerShell examples.
- Include Linux-native automation tools (e.g., Cockpit, cloud-init, systemd) as onboarding options where appropriate.
- Ensure parity in documentation detail for Linux methods, matching the depth provided for Windows tools like Group Policy and Configuration Manager.
- Explicitly state which onboarding methods are best suited for Linux environments and provide links to Linux-focused guides.
- Reorder or balance the presentation of Windows and Linux methods to avoid a Windows-first impression.
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
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
windows_admin_center_emphasis
windows_tls_details
missing_linux_example
Summary
The documentation page displays a moderate Windows bias. Windows-specific tools (Windows Admin Center) and endpoints are mentioned explicitly and repeatedly, often before or with greater detail than Linux equivalents. Windows installation and configuration details (such as TLS cipher suites) are provided with more specificity, while Linux is referenced more generically (e.g., 'Linux distributions tend to rely on OpenSSL'). There are no Linux-specific troubleshooting links or configuration examples, and Windows endpoints (e.g., download.microsoft.com) and tools are listed first in tables and explanations.
Recommendations
- Provide Linux-specific troubleshooting and configuration guidance, similar to the detailed Windows TLS section.
- Include Linux-first or parity examples in tables, such as listing Linux endpoints before or alongside Windows endpoints.
- Mention Linux management tools or patterns (e.g., Cockpit, SSH, systemd) where Windows Admin Center is referenced.
- Add links to Linux documentation for TLS configuration and agent installation, not just generic OpenSSL references.
- Ensure that Linux and Windows instructions are equally detailed and accessible throughout the documentation.
Azure Arc
Automatic extension upgrade for Azure Arc-enabled servers
...e-arc/servers/manage-automatic-vm-extension-upgrade.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page generally maintains parity between Windows and Linux, but there are subtle signs of Windows bias. Windows is consistently mentioned first when referring to supported platforms. PowerShell is given its own dedicated section for managing extension upgrades, while Linux-specific shell examples (e.g., bash) are only referenced in passing under Azure CLI. The list of supported extensions includes several Windows-only extensions, with no Linux-only equivalents highlighted. The documentation references Windows tools (PowerShell) before mentioning cross-platform alternatives (CLI), and does not provide Linux-specific troubleshooting or management patterns.
Recommendations
- Alternate the order of platform mentions (e.g., 'Linux and Windows') to avoid implicit prioritization.
- Provide explicit Linux shell examples (e.g., bash, zsh) alongside PowerShell examples, especially in command sections.
- Highlight any Linux-only extensions or features if available, or clarify parity in extension support.
- Include troubleshooting steps or management patterns specific to Linux environments, such as log file locations or systemd integration.
- Ensure that CLI examples reference Linux usage explicitly, including environment-specific notes where relevant.
- Consider adding a table comparing extension support and management features between Windows and Linux.
Azure Arc
Cloud-native patch management with Azure Arc-enabled servers
...les/azure-arc/servers/cloud-native/patch-management.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits a Windows-first bias: Windows tools (WSUS, SCCM) are mentioned exclusively and before any Linux equivalents, and examples and analogies throughout the document are centered on Windows patterns. There are no concrete Linux-specific examples or workflows (e.g., using Linux-native patching tools or scripting), and the only Linux mention is generic, without practical demonstration. Hotpatching is described only for Windows, and pre/post event examples are Windows-centric (e.g., snapshot VM, stop/start services) without Linux-specific scenarios.
Recommendations
- Add Linux-native patch management tool references (e.g., apt, yum, dnf, zypper) alongside WSUS/SCCM in the introduction.
- Provide Linux-specific workflow examples for patch scheduling, compliance reporting, and automation (e.g., using shell scripts, cron jobs, or Ansible).
- Include Linux-focused pre/post event script examples (e.g., systemctl commands, package manager hooks).
- Clarify hotpatching support or alternatives for Linux, or explicitly state its absence.
- Ensure parity in feature explanations by describing how Linux admins can leverage Azure Update Manager with their existing tools and patterns.
- Balance examples and analogies so that both Windows and Linux administrators see relevant, actionable guidance.
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions and tooling (such as PowerShell, Group Policy, Microsoft Update, WSUS, and Configuration Manager) are often described in greater detail, with more context and step-by-step guidance than their Linux equivalents. Windows examples and explanations frequently appear before Linux ones, and some sections (like update infrastructure and proxy configuration) provide extensive Windows-specific tooling coverage, while Linux instructions are more generic and less detailed.
Recommendations
- Ensure Linux instructions are as detailed as Windows ones, including troubleshooting, automation, and integration with common Linux management tools (e.g., Ansible, systemd, cron).
- Provide parity in examples: where Windows uses PowerShell or Group Policy, offer equivalent Linux automation (e.g., shell scripts, configuration management).
- When listing upgrade or uninstall methods, alternate the order or present Windows and Linux together, rather than always leading with Windows.
- Expand Linux-specific guidance for enterprise scenarios, such as using package repositories with local mirrors, integrating with Linux update management tools, or handling agent upgrades in air-gapped environments.
- Include more Linux-focused troubleshooting and operational tips, matching the depth given to Windows (e.g., log file locations, service management commands, SELinux/AppArmor considerations).
Azure Arc
Enable VM extensions to Arc-enabled servers from the Azure portal
...icles/azure-arc/servers/manage-vm-extensions-portal.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates subtle Windows bias. While it claims to cover both Linux and Windows Arc-enabled servers, specific examples (such as proxy configuration for the Azure Monitor agent) mention Windows only, with no Linux equivalent. Additionally, references to command-line tools in notes and related content list Azure PowerShell before Azure CLI, and do not provide explicit Linux-centric examples or guidance. The screenshots and configuration steps do not clarify Linux-specific differences, if any.
Recommendations
- Include explicit examples and configuration details for Linux Arc-enabled servers, especially where Windows-specific instructions are given.
- When mentioning command-line tools, list Azure CLI before Azure PowerShell, or clarify parity between them for Linux users.
- Add screenshots or walkthroughs that show Linux-specific extension configuration, if applicable.
- Where extensions have OS-specific requirements or behaviors, call these out clearly in the main instructions.
- Ensure troubleshooting and related content links include Linux-focused resources and examples.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
windows_heavy_examples
Summary
The documentation page demonstrates a Windows bias by listing Windows extensions before Linux extensions, providing a longer and more detailed table for Windows-specific extensions, and referencing Windows-centric tools such as Windows Admin Center and PowerShell. The partner extensions table also lists Windows variants before Linux. The deployment methods mention Azure PowerShell (primarily a Windows tool) alongside Azure CLI, but do not highlight Linux-native management tools or shell examples. The overall structure and content favor Windows scenarios and tools, with Linux equivalents presented secondarily.
Recommendations
- Present Linux and Windows extension tables side-by-side or alternate their order to avoid implicit prioritization.
- Ensure parity in the number and detail of Linux extension examples, matching the coverage given to Windows.
- Include Linux-native management tool examples (e.g., Bash scripts, cloud-init) alongside PowerShell and CLI.
- Highlight cross-platform management approaches and clarify which tools are available on Linux.
- Add explicit Linux usage scenarios and troubleshooting sections to match Windows coverage.
- Avoid listing Windows-specific tools (e.g., Windows Admin Center) without mentioning Linux alternatives or clarifying platform limitations.
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
High 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, Windows Server Graphical Installer) and deployment methods before Linux equivalents. While Bash and Ansible are referenced, examples and detailed instructions are not provided for Linux. The standalone Azure Monitor Agent installation is only described for Windows client machines, with no mention of Linux client installation. PowerShell is listed before Bash, and Windows-centric management options (Group Policy, Windows Admin Center) are highlighted, while Linux-native approaches are less visible.
Recommendations
- Provide explicit Linux deployment examples and instructions alongside Windows methods, such as using shell scripts, systemd services, or Linux package managers.
- Include references to Linux-native management tools (e.g., systemctl, cron, configuration via Ansible or Puppet) where Windows tools like Group Policy or Admin Center are mentioned.
- Add a section for standalone Azure Monitor Agent installation on Linux client machines, if supported, or clarify parity and limitations.
- Ensure that PowerShell and Bash examples are presented together, or alternate their order to avoid Windows-first presentation.
- Highlight any differences or additional steps required for Linux environments in migration, agent configuration, and networking.
Azure Arc
Enable VM Extensions Using the Azure CLI (Windows and Linux)
...articles/azure-arc/servers/manage-vm-extensions-cli.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias in several ways: most command examples use PowerShell syntax or Windows-specific tools (e.g., 'powershell.exe'), extension examples are predominantly for Windows (Antimalware, DatadogWindowsAgent), and the Custom Script Extension examples only show PowerShell commands. Linux equivalents (e.g., Bash scripts, Linux-specific extensions) are not provided or are mentioned only generically. The extension names and settings in examples are Windows-centric, and Linux usage patterns are not illustrated.
Recommendations
- Provide Linux-specific examples for the Custom Script Extension, using Bash or shell commands (e.g., 'bash -c "ps aux | awk ..."').
- Include examples of enabling Linux-specific extensions (e.g., DependencyAgentLinux, KeyVaultForLinux with Linux settings).
- Balance extension examples by showing both Windows and Linux scenarios for each major operation (enable, update, remove).
- Clarify in each example which OS it targets, and offer parallel commands for both Windows and Linux where applicable.
- Avoid using Windows tools (e.g., 'powershell.exe') exclusively in generic examples; use cross-platform or Linux-native tools as well.
Azure Arc
Enable VM Extensions Using Azure Resource Manager Template
...les/azure-arc/servers/manage-vm-extensions-template.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation exhibits a Windows bias primarily through exclusive use of PowerShell for deployment commands, Windows-centric file path examples, and the absence of equivalent Linux/CLI deployment instructions. While ARM template samples are provided for both Linux and Windows, all operational guidance (how to actually deploy the templates) is shown only with PowerShell, which is a Windows-first tool. There are no bash, Azure CLI, or cross-platform examples for Linux users, and file path examples use Windows-style paths.
Recommendations
- Add Azure CLI examples for deploying ARM templates, demonstrating parity with PowerShell commands.
- Include bash shell examples for Linux users, especially for template deployment.
- Use platform-neutral file paths in examples, or provide both Windows and Linux path formats.
- Clearly indicate that PowerShell is available cross-platform, but also provide native Linux command alternatives.
- In 'Related content', elevate Azure CLI and bash options to equal prominence with PowerShell and portal instructions.
- Add notes or sections specifically addressing Linux deployment workflows, including troubleshooting and environment setup.
Azure Arc
Authenticate against Azure resources with Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a mild Windows bias. Windows and PowerShell are frequently mentioned first, and PowerShell is used as the primary example for access policy assignment and token retrieval. Windows-specific tools and groups (e.g., Administrators, PowerShell) are referenced before their Linux equivalents, and links to Windows instructions often precede Linux ones. While Linux examples are present, they are sometimes less detailed or referenced after Windows steps.
Recommendations
- Alternate the order of Windows and Linux instructions/examples to avoid consistently prioritizing Windows.
- Provide equally detailed Linux examples and screenshots for all major steps, including access policy assignment and token retrieval.
- Include references to Linux-native tools (e.g., Azure CLI, Bash scripts) alongside or before PowerShell, especially in 'Next steps' and prerequisite sections.
- Ensure that group membership requirements and terminology for Linux are explained as thoroughly as for Windows.
- Where possible, use generic cross-platform instructions first, then provide OS-specific details.
Azure Arc
How to modernize server management from Configuration Manager to Azure Arc
...icles/azure-arc/servers/modernize-server-management.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. While it acknowledges Linux support and parity improvements in Azure Arc, most examples, onboarding instructions, and tool references are Windows-centric. Windows licensing, Windows Server Software Assurance, and Windows-specific onboarding methods (Scheduled Task) are mentioned first or exclusively. There is a lack of explicit Linux onboarding guidance and Linux-specific examples for key management tasks.
Recommendations
- Add explicit onboarding instructions for Linux servers, including supported Linux distributions and recommended automation methods (e.g., systemd timers, cron jobs) for agent installation.
- Provide Linux-specific examples for core management tasks, such as patching, configuration, and reporting, including command-line snippets or references to Linux-native tools.
- Balance references to Windows licensing and tools with equivalent information for Linux environments (e.g., mention Linux support in pricing, clarify licensing implications for Linux servers).
- Include links to Linux documentation, troubleshooting guides, and best practices for Azure Arc management.
- Where Windows tools or patterns are mentioned (e.g., Scheduled Task), immediately follow with Linux equivalents to ensure parity and clarity for cross-platform administrators.
Azure Arc
Connect hybrid machines to Azure using a deployment script
...blob/main/articles/azure-arc/servers/onboard-portal.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page exhibits a moderate Windows bias. Windows installation instructions and examples are presented before Linux equivalents, with detailed steps using Windows Installer (msiexec.exe) and PowerShell commands. Windows-specific tools and patterns (such as .msi installers, PowerShell, and Windows environment variables) are described in depth, while Linux instructions are comparatively concise and less detailed. The scripted method for onboarding is described for both platforms, but Windows steps and troubleshooting are more prominent.
Recommendations
- Present Linux and Windows instructions in parallel or alternate the order to avoid Windows-first bias.
- Expand Linux installation instructions to include more troubleshooting steps, command-line options, and log file locations, matching the detail given for Windows.
- Include Linux equivalents for environment variable configuration and agent management (e.g., using export or systemctl commands for proxy and service management).
- Provide more examples using common Linux shells and package managers (e.g., apt, yum, systemctl), not just bash scripts.
- Ensure that references to tools and commands are balanced between platforms, and avoid assuming familiarity with Windows-specific tools.
Azure Arc
Plan and Deploy Azure Arc-Enabled Servers
...articles/azure-arc/servers/plan-at-scale-deployment.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and the Azure portal as primary methods for creating service principals, mentioning Windows and Linux together but often listing Windows first, and lacking explicit Linux command-line examples (e.g., Bash, shell scripts) for key deployment steps. The automation and onboarding examples do not provide parity for Linux-specific tools or workflows, and there is no mention of Linux-native automation frameworks (like Ansible or shell scripting) or package managers (such as apt, yum) for agent installation.
Recommendations
- Provide explicit Linux command-line examples (e.g., Bash scripts) alongside PowerShell and portal instructions for all deployment and management steps.
- Reference Linux-native automation tools (such as Ansible, Chef, or shell scripting) when discussing at-scale onboarding and automation.
- List Linux and Windows examples in parallel, ensuring Linux is not always mentioned second or as an afterthought.
- Include instructions for installing the Connected Machine agent using common Linux package managers (apt, yum, zypper) and systemd service management.
- Add troubleshooting and management guidance specific to Linux environments, including log file locations and diagnostic commands.
- Ensure that all sample scripts and onboarding resources have Linux equivalents and are clearly documented.
Azure Arc
Connect machines from Azure Automation Update Management
...zure-arc/servers/onboard-update-management-machines.md
High 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 the detailed operational examples and tool references (such as runbooks and PowerShell) are Windows-centric. The runbook naming and usage (Add-UMMachinesToArc, Add-UMMachinesToArcWindowsChild) and references to Azure PowerShell for status checks are presented before or without Linux equivalents. There are no explicit Linux command-line examples or references to Linux-native tools (e.g., Bash, shell scripts), and troubleshooting/verification steps do not mention Linux-specific guidance.
Recommendations
- Provide explicit Linux command-line examples (e.g., Bash, shell scripts) for onboarding and verification steps.
- Include references to Linux-native tools (such as CLI commands, log file locations, and troubleshooting steps specific to Linux).
- Balance the order of presentation so that Windows and Linux instructions/examples are given equal prominence.
- Add screenshots or walkthroughs showing the process on Linux systems, not just Windows.
- Clarify that both Add-UMMachinesToArcWindowsChild and Add-UMMachinesToArcLinuxChild runbooks are available and provide example outputs for each.
Azure Arc
Azure Arc-enabled servers Overview
...-docs/blob/main/articles/azure-arc/servers/overview.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation frequently references Windows-specific tools, concepts, and examples before or in greater detail than their Linux equivalents. PowerShell and Windows registry are mentioned explicitly, while Linux-specific configuration and automation patterns are less emphasized. Some links and tabs default to Windows, and Linux examples or instructions are missing or less prominent.
Recommendations
- Ensure examples and instructions are provided for both Windows and Linux platforms, with equal detail and visibility.
- When referencing automation tools (e.g., Azure Automation), include Linux-specific scripting examples (e.g., Bash, Python) alongside PowerShell.
- Mention Linux configuration management patterns (e.g., systemd, cron, package managers) when discussing configuration and monitoring.
- Avoid defaulting links or tabs to Windows; use neutral or parallel presentation (e.g., 'Windows | Linux' tabs).
- Explicitly state Linux support and provide direct links to Linux documentation where available.
- Include Linux-specific troubleshooting and operational guidance (e.g., handling Linux daemons, log files, permissions).
Azure Arc
Connected Machine agent prerequisites
.../blob/main/articles/azure-arc/servers/prerequisites.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and procedures (such as PowerShell scripts and Group Policy Editor) are described in detail, including explicit script examples and troubleshooting steps. Linux requirements are mentioned but lack equivalent depth or example commands. Windows instructions and tools (PowerShell, gpedit.msc) are given before or instead of Linux alternatives, and the onboarding script modification example is only for Windows. Linux onboarding is described as requiring 'no special considerations,' but no example is provided.
Recommendations
- Provide Linux onboarding script examples, including how to specify agent versions or handle limited support scenarios.
- Include troubleshooting steps for Linux environments, such as checking required permissions or service status.
- Offer Linux equivalents for Windows-specific tools (e.g., show how to check service permissions or agent status using systemd or relevant Linux commands).
- Balance the depth of Windows and Linux instructions, ensuring both platforms have clear, actionable guidance.
- Where possible, present Windows and Linux instructions side-by-side or in parallel sections to avoid implicit prioritization.
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
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows Server 2012/2012 R2, with all examples, deployment options, and tooling references tailored exclusively to Windows environments. There are no Linux-specific instructions, examples, or parity notes, and Windows-centric tools (Group Policy, Configuration Manager, SCVMM) are mentioned without Linux alternatives or guidance. The documentation assumes the reader is managing Windows servers and does not address scenarios for Linux hosts or mixed environments.
Recommendations
- Add explicit notes clarifying whether Linux servers can be onboarded to Azure Arc for ESU delivery, and if not, state this limitation.
- If Linux onboarding is supported, provide Linux-specific instructions and examples for agent installation, enrollment, and patch management.
- Include Linux equivalents for deployment automation (e.g., using Ansible, shell scripts, or cron jobs) alongside Windows tools like Group Policy and Configuration Manager.
- Reference Linux patching solutions (such as Azure Update Manager for Linux, or native Linux update mechanisms) where appropriate.
- Ensure networking and certificate installation instructions include Linux command-line examples (e.g., using curl, openssl, or package managers).
- Add a parity table or section comparing Windows and Linux onboarding and management workflows for Azure Arc-enabled servers.
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
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools and paths (e.g., Windows Admin Center, C:\Windows\System32\drivers\etc\hosts) are mentioned before their Linux equivalents, and Windows scenarios are often described first. Some examples and troubleshooting steps are Windows-centric, with Linux instructions sometimes provided but less detailed. There is a lack of parity in example scripts, troubleshooting commands, and tool references for Linux environments.
Recommendations
- Ensure Linux instructions are presented alongside Windows instructions, with equal detail and prominence.
- Provide example scripts and troubleshooting commands for both Windows (PowerShell, CMD) and Linux (bash, shell) environments.
- Mention Linux tools (e.g., SSH, systemd-resolved, firewalld) where appropriate, not just Windows Admin Center.
- When describing file paths or configuration steps, list both Windows and Linux locations together.
- Include screenshots and step-by-step guides for Linux environments in addition to Windows.
- Avoid presenting Windows scenarios or tools first unless there is a clear usage rationale; alternate or parallelize the order.
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
High Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation page exclusively provides examples using PowerShell syntax (e.g., 'Write-Host Hello World!'), which is specific to Windows environments. There are no examples for Linux shell scripts (e.g., Bash), and the scripting pattern assumes a Windows-first audience. This may make it less accessible or relevant for users managing Linux Arc-enabled servers.
Recommendations
- Include equivalent examples using Bash or other Linux shell scripts (e.g., 'echo Hello World!') to demonstrate parity.
- Explicitly mention that the Run Command supports both Windows and Linux servers, and clarify any differences in script syntax or supported features.
- Alternate or parallel example blocks for Windows (PowerShell) and Linux (Bash) to ensure both audiences are served.
- Add notes or links to Linux-specific documentation or troubleshooting guides.
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 demonstrates a strong Windows bias. All example scenarios and scripts 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 servers, such as using Bash scripts, iptables, or Linux authentication patterns. The documentation does not mention Linux support or provide parity in examples.
Recommendations
- Add equivalent Linux examples for each REST API operation, such as using Bash scripts to configure firewall rules (e.g., with iptables or ufw).
- Explicitly state which operating systems are supported and clarify any limitations or differences in usage between Windows and Linux Arc-enabled servers.
- Provide sample scripts and blob SAS token generation steps using Linux tools (e.g., Azure CLI on Linux, Bash).
- Include authentication and user patterns relevant to Linux (e.g., sudo usage, SSH keys, Linux user accounts).
- Ensure that documentation for related content (CLI, PowerShell) also includes Linux parity.
Azure Arc
Run command on Azure Arc-enabled servers (Preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by emphasizing PowerShell as a primary experience, listing it before Linux-friendly tools, and failing to provide explicit Linux-specific examples or guidance. The references to PowerShell and Azure CLI are prominent, but there is no mention of Bash, shell scripting, or Linux command patterns. The documentation does not illustrate Linux workflows or highlight Linux-specific considerations, despite claiming support for both Windows and Linux.
Recommendations
- Include explicit Linux command/script examples (e.g., Bash, shell scripts) alongside PowerShell examples.
- Mention Linux-native tools and scripting patterns when describing supported experiences.
- Provide guidance on Linux-specific use cases, such as package management (apt, yum), firewall configuration (iptables, firewalld), and log auditing (journalctl, syslog).
- Ensure that references to supported operating systems are accompanied by examples or documentation links for both Windows and Linux.
- Balance the order of presentation so that Linux and Windows are treated equally (e.g., alternate listing PowerShell and Bash examples).
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific tools and patterns (Group Policy, Microsoft Update, WSUS, BitLocker) are mentioned before or in more detail than their Linux equivalents. PowerShell is referenced as a primary automation method, with Linux alternatives (e.g., Ansible) mentioned but not elaborated. Some examples and guidance (such as onboarding via local web browser and Group Policy encryption steps) are Windows-only, with no Linux equivalents provided. Linux update mechanisms are briefly mentioned, but Windows update processes are described in greater detail.
Recommendations
- Provide Linux-specific onboarding examples and scripts, including credential protection methods for common Linux automation tools (e.g., Ansible, shell scripts).
- Balance the detail level for update management: elaborate on Linux update workflows and tools (e.g., package managers, unattended-upgrades) as much as Windows Update/WSUS.
- Include Linux equivalents for disk encryption (e.g., dm-crypt, LUKS) with configuration guidance, not just mention them.
- Offer PowerShell and CLI examples side-by-side with Linux shell commands where applicable.
- Reference Linux-first automation tools (e.g., Ansible, Chef, Puppet) with links to onboarding and update management guides.
- Clarify which features or steps are OS-specific and provide parity guidance for both Windows and Linux throughout the documentation.
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by emphasizing PowerShell Desired State Configuration as the foundation of Azure Machine Configuration, referencing Windows Admin Center (WAC) as a primary remote management tool, and providing detailed explanations and role assignments for Windows scenarios. Linux is mentioned (e.g., SSH access), but Linux-specific configuration examples, tools, and parity in management workflows are lacking. Windows tools and patterns are described in greater depth, and Windows scenarios are often presented first or exclusively.
Recommendations
- Provide Linux-specific configuration and compliance examples, such as using native Linux configuration management tools (e.g., Ansible, Chef, or native shell scripts) in addition to PowerShell DSC.
- Include parallel Linux-focused remote management workflows, such as using Cockpit or Webmin, to match the coverage given to Windows Admin Center.
- Offer explicit Linux command-line examples for all configuration and agent management steps, not just generic azcmagent commands.
- Balance the order of presentation so that Linux and Windows scenarios are introduced together or alternate, rather than Windows-first.
- Clarify any feature gaps or differences in experience between Windows and Linux, and provide guidance or workarounds for Linux users.
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell Desired State Configuration as the sole example for guest configuration policies, using Windows account types and SIDs before mentioning Linux equivalents, and providing extension allowlist examples that only reference Windows-specific extensions. There are no Linux-specific extension examples or mentions of Linux configuration tools, and the documentation generally describes Windows patterns and tools first.
Recommendations
- Include Linux-specific examples for extension allowlists, such as referencing Linux monitoring or security extensions.
- Mention Linux equivalents to PowerShell Desired State Configuration, such as Ansible, Chef, or native Linux configuration management tools, when discussing guest configuration policies.
- Provide sample azcmagent commands for Linux scenarios, including extension allowlists and disabling features relevant to Linux servers.
- Ensure that both Windows and Linux account/service names are described with equal prominence and detail.
- Add notes or sections highlighting differences in security controls or agent behavior between Windows and Linux environments.
Azure Arc
Troubleshoot SSH access to Azure Arc-enabled servers
...ain/articles/azure-arc/servers/ssh-arc-troubleshoot.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits a notable Windows bias. Troubleshooting steps and examples are heavily focused on Azure PowerShell modules and commands, with multiple references to PowerShell-specific tools (Az.Ssh, Az.Ssh.ArcProxy) and error messages. Solutions are often presented using PowerShell first or exclusively, with limited or no equivalent Linux shell or cross-platform instructions. There is a lack of parity in examples for Linux users, such as missing bash or shell commands for module management and troubleshooting.
Recommendations
- Provide equivalent Linux/bash commands for installing and updating SSH-related modules and troubleshooting steps.
- Include instructions for managing PATH and client binaries on Linux/macOS systems, not just Windows/PowerShell.
- Add troubleshooting examples using native Linux tools (e.g., apt, yum, ssh-keygen) alongside PowerShell.
- Ensure that error messages and their resolutions are presented for both Windows and Linux environments, with clear distinctions.
- Balance the order of examples so that Azure CLI and Linux-native approaches are presented before or alongside PowerShell/Windows-specific solutions.
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows examples and tools (such as PowerShell and Windows-specific paths) are presented first or in greater detail, and references to Windows concepts (like elevated command prompt, %TEMP%, %ProgramData%) appear before or more prominently than Linux equivalents. Some troubleshooting steps and error code explanations reference Windows tools or patterns (e.g., PowerShell version requirements, Windows log file locations) without always providing Linux alternatives or parity in detail. While Linux examples are present, they sometimes lack the same depth or are listed after Windows instructions.
Recommendations
- Present Linux and Windows examples in parallel or alternate their order to avoid always listing Windows first.
- Ensure Linux-specific troubleshooting steps and log file locations are equally detailed and visible.
- Where Windows tools or concepts (e.g., PowerShell, %TEMP%, elevated command prompt) are mentioned, provide the Linux equivalents (e.g., Bash, /tmp, sudo/root) in the same context.
- Add Linux-specific error code details and remediation steps where only Windows details are given (e.g., installation logs, platform-specific issues).
- Avoid referencing Windows-only tools or patterns (such as PowerShell version requirements) without noting Linux applicability or alternatives.
Azure Arc
SSH access to Azure Arc-enabled servers
...ob/main/articles/azure-arc/servers/ssh-arc-overview.md
High 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-specific tools, commands, and references (such as PowerShell and Windows OpenSSH) are frequently mentioned first or in greater detail. PowerShell examples are given for most operations, sometimes with more explanation than Linux equivalents. There is a tendency to reference Windows Server features and documentation, and the installation/validation steps for Windows are more verbose. Some Linux-specific details (e.g., systemd service management, SELinux) are missing or less emphasized.
Recommendations
- Ensure Linux examples are presented with equal detail and order as Windows examples, including service management (systemctl), package installation across major distros (apt, yum, zypper), and troubleshooting steps.
- Add explicit Linux command-line examples for all major steps, not just generic Azure CLI commands.
- Include references to Linux SSH server documentation and troubleshooting guides alongside Windows equivalents.
- Where PowerShell is used, provide equivalent bash/shell commands for Linux users.
- Mention Linux tools and patterns (e.g., journalctl for logs, systemctl for service status) in troubleshooting and validation sections.
- Balance 'Next steps' links to include Linux-focused resources, not just Windows OpenSSH.
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
powershell_heavy
windows_tools
Summary
The documentation is exclusively focused on troubleshooting Extended Security Updates for Windows Server 2012 via Azure Arc, with all examples, commands, and troubleshooting steps tailored to Windows environments. Only Windows Server is mentioned as eligible, and all command-line instructions use Windows-specific tools (certutil, PowerShell). There are no Linux equivalents, nor any mention of Linux scenarios, even though Azure Arc can manage both Windows and Linux servers.
Recommendations
- Explicitly state that the ESU process described is only applicable to Windows Server 2012 and 2012 R2, and clarify whether Linux servers are supported or not for ESU via Azure Arc.
- If Azure Arc troubleshooting is relevant for Linux servers in other contexts, provide parallel troubleshooting steps, examples, and commands for Linux (e.g., using openssl, update-ca-certificates, systemctl).
- Where possible, mention cross-platform Azure Arc capabilities and link to Linux-specific documentation for agent installation, connectivity, and certificate management.
- Ensure that resource provider and Azure Policy instructions clarify any differences or requirements for Linux servers managed by Azure Arc.
- Add a section or note on how Linux servers are handled in the context of ESU, even if only to state that they are not eligible, to avoid confusion and improve parity.
Azure Arc
Tutorial - Monitor a hybrid machine with Azure Monitor VM insights
...icles/azure-arc/servers/tutorial-enable-vm-insights.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates subtle Windows bias. While it claims to support both Linux and Windows VMs, the only explicit example of log/event collection references the Windows event log and the Event table, with no mention of Linux equivalents (such as syslog or Linux-specific tables). The workflow and screenshots are generic, but the event log example is Windows-centric, and there are no Linux-specific instructions or examples provided.
Recommendations
- Include explicit examples and screenshots for Linux machines, such as how to view syslog or Linux audit logs in Log Analytics.
- Mention the Linux-specific tables (e.g., Syslog, SyslogEvents) alongside the Windows Event table, and provide sample queries for both.
- Clarify any differences in data collection, troubleshooting, or agent installation steps for Linux versus Windows machines.
- Ensure that instructions and terminology are balanced, mentioning Linux tools and patterns wherever Windows tools are referenced.
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits a Windows bias by prioritizing Windows Server and Windows client OS in supported scenarios, listing Windows-specific tools (PowerShell, Group Policy, Configuration Manager) before Linux equivalents, and providing more detailed instructions and examples for Windows environments. Linux support is mentioned but often as an exception or after Windows, and Linux-specific automation methods are less emphasized.
Recommendations
- Provide Linux examples and instructions alongside Windows examples, not as exceptions or afterthoughts.
- List Linux automation tools (e.g., Ansible, shell scripting) before or equally with Windows tools in out-of-band methods.
- Include parity in supported OS lists, and clarify which features are available for Linux VMs.
- Offer detailed step-by-step Linux installation and troubleshooting guidance equal to Windows coverage.
- Add references to Linux-specific documentation and best practices for Arc agent installation and management.
Azure Arc
Overview of Azure Connected Machine agent to manage Windows and Linux machines
...center-virtual-machine-manager/agent-overview-scvmm.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
windows_heavy_detail
Summary
The documentation provides a reasonably balanced overview of both Windows and Linux support for the Azure Connected Machine agent. However, there is a noticeable Windows bias: Windows installation details are presented first and in greater depth, with more granular information about folders, services, accounts, security groups, environment variables, and logs. Windows-specific tools (MSI installer, Group Policy, NT SERVICE accounts) are described in detail, while Linux equivalents (systemd, package managers, service accounts) are covered more briefly. The Windows section includes troubleshooting tips and security group details that are missing or less emphasized for Linux.
Recommendations
- Present Windows and Linux installation details in parallel sections or tables, rather than Windows-first.
- Provide equal depth for Linux installation, including details on service accounts, security groups, and troubleshooting tips.
- Include Linux-specific configuration and management patterns (e.g., SELinux/AppArmor, systemd unit files, user/group management) where Windows Group Policy and NT SERVICE accounts are discussed.
- Add Linux-specific tips for troubleshooting and post-uninstall artifact cleanup.
- Ensure examples and instructions for both platforms are equally visible and accessible.
Azure Arc
Create custom roles with Azure Arc-enabled SCVMM
...-center-virtual-machine-manager/create-custom-roles.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Azure Arc-enabled SCVMM, a Windows-centric virtualization management tool. All examples and instructions are tailored to the Azure portal and SCVMM, with no mention of Linux-based equivalents or cross-platform scenarios. The prerequisites, steps, and next actions are all oriented toward Windows environments, and there are no examples or guidance for Linux users or tools.
Recommendations
- Include examples or references for creating custom roles with Azure Arc-enabled Linux servers or other non-Windows resource providers.
- Add parity guidance for managing custom roles via Azure CLI on Linux, including sample commands and screenshots from Linux terminals.
- Explicitly mention cross-platform support and limitations, clarifying which steps apply to Windows-only scenarios and which are universal.
- Provide links or references to documentation for Linux-based virtualization management (e.g., integration with KVM, Hyper-V on Linux, or other Azure Arc-supported platforms).
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
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows Server 2012/2012 R2 environments managed by SCVMM, with all examples, terminology, and tooling referencing Windows-specific technologies. There are no Linux examples, nor are Linux VMs or management tools mentioned. Patch management solutions listed are either Microsoft/Windows-centric or generically reference 'non-Microsoft' options without examples. The documentation assumes a Windows-only context and does not address Linux VM scenarios or parity.
Recommendations
- Explicitly state that the process is only applicable to Windows Server VMs, and clarify whether Linux VMs managed by SCVMM or Azure Arc are supported or excluded.
- If Azure Arc and SCVMM support Linux VMs, provide equivalent instructions or note any limitations for Linux environments.
- Include examples of patch management solutions commonly used for Linux (e.g., Red Hat Satellite, SUSE Manager, Canonical Landscape) and describe how ESU delivery or update compliance would work for Linux VMs, if applicable.
- Add a section comparing Windows and Linux VM management in Azure Arc-enabled SCVMM environments, including any differences in ESU delivery, licensing, or update mechanisms.
- If Linux is not supported, make this clear early in the documentation to avoid confusion for cross-platform administrators.
Azure Arc
Create a virtual machine on System Center Virtual Machine Manager using Azure Arc
...nter-virtual-machine-manager/create-virtual-machine.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation is heavily focused on System Center Virtual Machine Manager (SCVMM), a Windows-only tool, and does not mention or provide examples for Linux-based virtualization platforms or management tools. All instructions and terminology are specific to Windows environments, with no parity for Linux users or administrators. There are no CLI or scripting examples, and the only references to automation mention PowerShell and REST APIs in a generic way, without Linux equivalents.
Recommendations
- Add guidance or links for creating virtual machines using Linux-based management tools (e.g., libvirt, KVM, oVirt) in hybrid Azure Arc scenarios.
- Include CLI examples using Azure CLI or Bash, not just PowerShell, and clarify cross-platform compatibility.
- Explicitly state SCVMM is Windows-only and provide alternative documentation for Linux environments where possible.
- Mention and compare equivalent Linux patterns for VM management in hybrid cloud scenarios.
- Ensure references to automation (CLI, SDKs, IaC) include Linux-friendly options and examples.
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
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides recovery instructions exclusively for Windows, including a PowerShell script and Windows-centric steps. There are no Linux-specific instructions, examples, or parity for running the recovery process from a Linux machine. The use of PowerShell and the absence of Bash or cross-platform alternatives indicate a Windows bias.
Recommendations
- Add equivalent recovery instructions for Linux, including Bash or Python scripts.
- Provide examples for running the recovery process from a Linux machine, including prerequisites and environment setup.
- Ensure that any downloadable scripts are cross-platform or offer separate versions for Windows and Linux.
- Mention Linux tools and patterns (e.g., shell scripting, CLI usage) alongside Windows/PowerShell options.
- Clearly state platform requirements and offer guidance for both Windows and Linux users.
Azure Arc
Overview of the Azure Arc-enabled System Center Virtual Machine Manager
...-arc/system-center-virtual-machine-manager/overview.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page for Azure Arc-enabled System Center Virtual Machine Manager exhibits a Windows-centric bias. Windows tools and patterns (such as PowerShell, Windows Server management, Windows registry, and SQL Server) are mentioned first or exclusively, with Linux equivalents either mentioned later or omitted. Examples and guidance for Linux environments are minimal or absent, and automation references prioritize PowerShell over Linux-native tools.
Recommendations
- Provide Linux-specific examples and workflows alongside Windows ones, especially for automation, configuration, and monitoring tasks.
- Mention Linux tools and patterns (e.g., Bash, systemd, Linux file system, Linux daemons) with equal prominence to Windows tools.
- Include explicit Linux onboarding and management scenarios, such as connecting Linux VMs managed by SCVMM to Azure Arc.
- Expand documentation for automation to include Bash scripts and Linux-native configuration management tools (e.g., Ansible, Chef, Puppet).
- Ensure that references to VM extensions, update management, and monitoring cover both Windows and Linux in detail, with clear parity.
- Add Linux-focused troubleshooting and best practices sections.
Azure Arc
Quickstart for Azure Arc-enabled System Center Virtual Machine Manager (SCVMM)
...t-connect-system-center-virtual-machine-manager-to-arc.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows prerequisites, tools, and instructions. Windows-specific requirements (such as installing tar.exe and OpenSSH from Windows sources) are detailed, while Linux equivalents are not mentioned. PowerShell is the primary scripting language, with Bash provided as an alternative. Troubleshooting and retry commands are shown first for Windows/PowerShell, and Windows tools/patterns (e.g., Set-ExecutionPolicy, WinRM ports) are referenced exclusively or before Linux equivalents. Linux instructions are present but less detailed, and performance warnings for Linux are included without mitigation advice.
Recommendations
- Provide Linux-specific prerequisites and installation steps (e.g., how to ensure tar and SSH are installed on common Linux distributions).
- List Linux instructions and examples alongside or before Windows examples to ensure parity.
- Include troubleshooting and retry commands for Linux with equal detail and visibility.
- Avoid language that discourages Linux use (e.g., performance warnings) unless accompanied by actionable mitigation steps.
- Reference Linux tools and patterns (e.g., systemd, SELinux, iptables) where relevant, not just Windows tools like WinRM.
- Ensure all script parameters and behaviors are documented for both PowerShell and Bash scripts.
Azure Arc
Support matrix for Azure Arc-enabled System Center Virtual Machine Manager
...pport-matrix-for-system-center-virtual-machine-manager.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation page exhibits a strong Windows bias. Windows Server and SCVMM are the primary focus, with requirements, examples, and troubleshooting steps centered on Windows environments. Linux is mentioned only briefly, often as an afterthought, and Linux-specific instructions or examples are minimal or absent. Windows tools (WinRM, Windows Management Framework, OpenSSH for Windows) are referenced exclusively, and performance warnings are given for Linux workstations without offering guidance or parity for Linux users.
Recommendations
- Provide Linux-specific deployment instructions and troubleshooting steps, especially for the Resource Bridge and agent installation.
- Include Linux command-line examples (e.g., Bash, SSH, systemd service management) alongside or before Windows/Powershell examples.
- Offer guidance for optimizing performance when deploying from Linux workstations, rather than simply warning of slower performance.
- Reference Linux equivalents for Windows tools (e.g., SSH, systemd, firewall configuration), and clarify any differences in setup or requirements.
- Ensure that all requirements, especially networking and permissions, are explained for both Windows and Linux environments.
- Add explicit support matrices for Linux distributions and versions, not just Windows OS versions.
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
windows_first
Summary
The documentation page is heavily focused on troubleshooting errors specific to SCVMM (System Center Virtual Machine Manager), a Windows-only tool. All error examples reference Windows-centric technologies and PowerShell (e.g., PSSessionAccessDenied, Get-SCVMMServer), with no mention of Linux equivalents, troubleshooting steps, or tools. There are no examples or guidance for Linux environments, and Windows tools/patterns are presented exclusively and first.
Recommendations
- Add troubleshooting steps and examples for Linux-based resource bridge deployments, if supported.
- Include equivalent Linux commands or error scenarios alongside Windows/PowerShell examples.
- Clarify in the introduction whether the guide is Windows-only or provide links to Linux troubleshooting documentation.
- If SCVMM is inherently Windows-only, explicitly state this limitation and direct Linux users to relevant Azure Arc documentation.
- Ensure parity in documentation by referencing cross-platform tools and patterns where possible.
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
missing_linux_example
windows_first
Summary
The documentation is heavily focused on SCVMM (System Center Virtual Machine Manager), a Windows-centric virtualization management tool. All operational steps, terminology, and screenshots are specific to Windows environments, with no mention of Linux equivalents, Linux-based management tools, or cross-platform considerations. There are no examples or instructions for Linux VMs or management workflows.
Recommendations
- Add guidance for managing Linux-based VMs within SCVMM, if supported, or clarify limitations.
- Include examples or references for enabling VM CRUD and power cycle operations on Linux VMs managed by Azure Arc, if possible.
- Mention or link to equivalent workflows for non-Windows virtualization platforms (e.g., VMware, KVM) where Azure Arc integration is available.
- Explicitly state the Windows-only scope in the prerequisites or introduction, if Linux parity is not feasible.
- Provide a comparison table or section outlining differences in management capabilities between Windows and Linux VMs in SCVMM and 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
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-specific tools and instructions. The deboarding script is only available as a Windows PowerShell script, with no Linux equivalent or instructions for running it on Linux. Windows uninstall instructions are more detailed and appear before Linux instructions. The use of PowerShell and references to Windows tools (Control Panel, Programs and Features) further reinforce the bias. There is no mention of how Linux administrators could perform equivalent actions for SCVMM environments, nor are cross-platform alternatives provided.
Recommendations
- Provide a cross-platform deboarding script or document manual steps for Linux environments.
- Include Linux CLI examples (e.g., Bash, Azure CLI) alongside PowerShell instructions.
- Ensure uninstall instructions for Linux are as detailed as those for Windows, including file/folder cleanup.
- Clarify whether SCVMM environments can be managed or deboarded from Linux, and if not, state this explicitly.
- Present Windows and Linux instructions in parallel tabs or sections, rather than Windows-first ordering.
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 page exhibits Windows bias by exclusively referencing System Center Virtual Machine Manager (SCVMM), a Windows-only tool, and providing instructions and agent management links that are specific to Windows environments. There are no examples, instructions, or references for Linux-based management or Linux agents, and all operational steps assume a Windows-centric infrastructure.
Recommendations
- Include equivalent instructions or notes for environments that use Linux-based virtualization management tools (e.g., mention if/how Azure Arc supports Linux KVM, VMware, or other platforms).
- Provide agent management steps for Linux VMs, including links to Linux agent uninstall/disconnect documentation.
- Clarify whether the process applies only to Windows-based SCVMM or if there are alternatives for Linux users, and explicitly state platform limitations.
- Add cross-platform examples or a comparison table showing Windows and Linux management workflows where applicable.
Azure Arc
What's new in Azure Arc-enabled SCVMM
...arc/system-center-virtual-machine-manager/whats-new.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation for Azure Arc-enabled SCVMM demonstrates a Windows bias by prioritizing Windows-centric tools and management patterns (e.g., PowerShell, Windows Server Management, Group Policy, System Center Configuration Manager) and referencing Windows features before or instead of Linux equivalents. There is a lack of explicit Linux management examples, and Windows-specific tooling is mentioned more frequently and in greater detail than cross-platform or Linux-native options.
Recommendations
- Include Linux-specific management examples and workflows, such as using SSH, Linux configuration management tools (e.g., Puppet, Chef), or native Linux scripting.
- Provide parity in documentation for Linux VM management, including cost-benefit features and agent installation methods tailored for Linux environments.
- Highlight cross-platform tools (e.g., Ansible, Terraform, Azure CLI) with both Windows and Linux usage examples, ensuring equal visibility.
- Avoid listing Windows tools and patterns (e.g., PowerShell, Group Policy, SCCM) before cross-platform or Linux alternatives unless contextually necessary.
- Add explicit guidance for Linux administrators on integrating SCVMM VMs with Azure Arc, including troubleshooting and best practices for Linux-based environments.
Azure Arc
Create custom roles with Azure Arc-enabled VMware vSphere
...ticles/azure-arc/vmware-vsphere/create-custom-roles.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates Windows bias by prioritizing Azure portal (web UI) and mentioning Azure PowerShell before Azure CLI and REST API. There are no Linux-specific examples or screenshots, and the guidance does not address cross-platform command-line usage or tools. The examples and instructions are generic but implicitly favor Windows users by referencing PowerShell and the portal, both of which are more commonly used on Windows.
Recommendations
- Provide explicit Azure CLI examples for creating and managing custom roles, including command syntax and sample outputs.
- Include Linux-specific instructions or screenshots where relevant, such as using Azure CLI on Linux terminals.
- Mention Azure CLI before or alongside Azure PowerShell to signal parity and cross-platform support.
- Add a section comparing usage on Windows and Linux, highlighting any differences or considerations.
- Ensure that REST API and ARM/Bicep template examples are platform-neutral and include sample usage from Linux environments.
Azure Arc
Deliver ESUs for VMware VMs through Arc
...r-extended-security-updates-for-vmware-vms-through-arc.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows Server 2012/2012 R2 VMs, with all examples, terminology, and tools centered around Windows. There is no mention of Linux VM support, Linux patching tools, or Linux-specific ESU processes. All patching solutions referenced are Microsoft/Windows-centric, and screenshots and instructions only show Windows Server resources.
Recommendations
- Clarify in the introduction whether Linux VMs are supported or not for ESUs via Arc. If not, explicitly state this limitation.
- If Linux VM support is possible, add equivalent instructions and screenshots for Linux VMs, including how to enroll them and manage ESUs.
- Include references to Linux patch management solutions (such as Azure Update Manager for Linux, or third-party Linux patching tools) where appropriate.
- Add a section comparing Windows and Linux ESU delivery processes, or link to Linux-specific documentation if available.
- Ensure that terminology and examples do not assume all VMs are Windows; use more inclusive language where possible.
Azure Arc
Install Arc agent at scale for your VMware VMs
...arc/vmware-vsphere/enable-guest-management-at-scale.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and patterns. The main automation script is a PowerShell script, and instructions for running it reference Windows Task Scheduler, with no mention of Linux equivalents (e.g., cron). Examples and automation approaches are predominantly Windows-focused (PowerShell, Group Policy, Configuration Manager), with Linux methods (e.g., Ansible) mentioned last and without detailed examples. There are no Linux shell script examples or guidance for running the automation at scale on Linux systems.
Recommendations
- Provide equivalent Linux shell script (bash) examples for Arc agent installation at scale.
- Include instructions for scheduling automation on Linux systems (e.g., using cron) alongside Windows Task Scheduler.
- Offer parity in example detail for Linux automation tools (e.g., Ansible, shell scripts) as is given for PowerShell.
- List Linux methods and examples before or alongside Windows methods to avoid 'windows_first' ordering.
- Expand out-of-band methods with detailed Linux-centric approaches, not just a reference to Ansible.
Azure Arc
Connect VMware vCenter Server to Azure Arc by using the helper script
...ere/quick-start-connect-vcenter-to-arc-using-script.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows/PowerShell instructions are consistently presented before Linux/Bash equivalents, and there is more detailed guidance for Windows users (e.g., PowerShell execution policy, warnings about PowerShell ISE). The script download step lists PowerShell before Bash, and troubleshooting/retry commands are shown for Windows first. The documentation references Windows-specific tools and patterns (PowerShell, Set-ExecutionPolicy), while Linux instructions are more minimal and lack equivalent detail.
Recommendations
- Present Linux and Windows instructions in parallel or alternate the order to avoid always listing Windows first.
- Provide equally detailed guidance for Linux users, such as troubleshooting common shell issues, permissions, or environment requirements.
- Mention Linux-specific considerations (e.g., required Bash version, dependencies, or SELinux/AppArmor notes) where relevant.
- Avoid Windows-centric terminology (e.g., 'PowerShell window') when describing steps that apply to both platforms.
- Ensure screenshots and examples reflect both Windows and Linux environments where possible.
Azure Arc
Perform disaster recovery operations
...mware-vsphere/recover-from-resource-bridge-deletion.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell script examples and instructions, with no mention of Linux or cross-platform alternatives. The onboarding and recovery scripts are shown only in PowerShell, and there is no guidance for users operating from Linux or macOS environments. The workflow assumes the use of Windows-centric tools and patterns, such as PowerShell and .ps1 scripts, without addressing Linux shell equivalents or providing Bash examples.
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 or compatibility for the onboarding script, and provide installation guidance for non-Windows platforms if supported.
- If the onboarding script is only available as a PowerShell script, mention how Linux/macOS users can run it (e.g., via PowerShell Core on Linux) and provide instructions.
- Include screenshots or CLI instructions for both Windows and Linux environments where applicable.
- Review all steps for assumptions of Windows-only tools or workflows, and add Linux alternatives or notes where possible.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific management features (such as Windows Server management and Extended Security Updates for Windows Server and SQL Server) are highlighted, often before or instead of Linux equivalents. References to Azure Automation and runbooks emphasize PowerShell and Windows registry/files, with Linux daemons mentioned only as a secondary consideration. Examples and links for onboarding and management tasks frequently use Windows as the default or only tab, and Linux-specific instructions or examples are missing or less prominent.
Recommendations
- Ensure Linux management features (such as Linux VM lifecycle, Linux security updates, and Linux configuration management) are described with equal detail and prominence as Windows features.
- Provide explicit Linux examples and links (e.g., onboarding Linux VMs, using Bash scripts in Azure Automation, managing Linux daemons and files) alongside or before Windows examples.
- Include Linux-first or cross-platform tabs in referenced guides and quickstarts, not just Windows or PowerShell.
- Highlight Azure Arc benefits for Linux VMs (such as free ESUs for Linux, Linux-specific monitoring, and configuration scenarios) where applicable.
- Balance mentions of Windows tools (PowerShell, registry, Windows Server management) with Linux tools (Bash, systemd, Linux configuration management) in automation and monitoring sections.
Azure Arc
Remove your VMware vCenter environment from Azure Arc
...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing detailed, step-by-step instructions and examples for Windows environments first, especially in the deboarding script section where only PowerShell and Windows instructions are given. There is no equivalent Linux shell script or guidance for running the deboarding script on Linux or macOS. The use of Windows-specific tools (Control Panel, PowerShell, Set-ExecutionPolicy) is emphasized, while Linux instructions are limited to agent uninstallation commands and lack parity in automation/script usage.
Recommendations
- Provide equivalent instructions for running the deboarding script on Linux and macOS, including prerequisites, shell commands, and troubleshooting notes.
- If the deboarding script is Windows-only, clarify its platform limitations and offer a Linux-compatible alternative or manual steps.
- Present Windows and Linux instructions side-by-side or in parallel sections to avoid Windows-first ordering.
- Include Linux-specific tooling and patterns (e.g., bash, shell scripts, package managers) where appropriate.
- Ensure all automation steps (such as script execution) have Linux/macOS equivalents or alternatives.
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates Windows bias by listing Windows requirements and tools (such as .NET Framework and PowerShell) before Linux equivalents, mentioning Windows-specific URLs and tools (Windows Admin Center), and omitting concrete Linux usage examples or commands. Linux requirements are listed but not elaborated with the same detail or guidance as Windows, and no Linux-specific helper scripts or admin tools are referenced.
Recommendations
- Provide Linux-specific examples and instructions for onboarding, administration, and agent installation, including shell commands and scripts.
- List Linux requirements and tools with equal detail and prominence as Windows, possibly in parallel tables or sections.
- Reference Linux admin tools (e.g., Cockpit, SSH) where Windows Admin Center is mentioned, and clarify their use cases.
- Ensure helper scripts and onboarding guides are available and documented for Linux environments, not just Windows/PowerShell.
- Include troubleshooting and credential rotation guidance for Linux environments, not just Windows.
- Review and balance the order of presentation so Linux is not always listed after Windows.
Azure Arc
Bulk Review, Publish, and Deploy with Workload Orchestration
...es/azure-arc/workload-orchestration/bulk-deployment.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell-based CLI and script examples, referencing .ps1 scripts, and omitting any Linux shell (bash/sh) equivalents. All command-line instructions use PowerShell syntax, and there is no mention of Linux-specific tools, shell environments, or cross-platform script usage. The page assumes a Windows environment for automation and scripting, which may hinder Linux users from following the instructions seamlessly.
Recommendations
- Provide equivalent bash/sh examples for all CLI commands and scripts, using Linux-friendly syntax.
- Include instructions for running the Azure CLI commands in Linux/macOS terminals, highlighting any differences (e.g., file path formats, quoting).
- Offer a Linux shell script (e.g., bulk_deployment.sh) alongside the PowerShell script, with usage instructions.
- Clarify that the Azure CLI is cross-platform and specify any OS-specific prerequisites or considerations.
- Mention how to delete workflows using Linux shell commands or scripts, not just workflow-delete.ps1.
- Ensure that examples and tooling references are presented in a cross-platform manner, or at least alternate between Windows and Linux approaches.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring cross-platform coverage. However, there are signs of Windows bias: PowerShell examples are given equal prominence to Bash, which is uncommon for Linux-focused workflows; some PowerShell commands use Windows-specific patterns (e.g., Out-File, ConvertTo-Json, armclient); and PowerShell is presented as a first-class option throughout, which may over-emphasize Windows environments in a Kubernetes/edge context that is typically Linux-centric.
Recommendations
- Clarify the intended audience for PowerShell vs Bash (e.g., recommend Bash for Linux/macOS, PowerShell for Windows).
- Add explicit guidance for Linux users to use Bash and for Windows users to use PowerShell, including a note on cross-platform compatibility.
- Where PowerShell commands use Windows-specific tools (e.g., Out-File, armclient), provide Linux/macOS alternatives or clarify tool availability.
- Consider listing Bash examples before PowerShell to reflect the typical Linux-first workflow in Kubernetes and container orchestration contexts.
- Review and ensure that all steps (especially file encoding, JSON manipulation, and CLI usage) are equally covered for Linux environments, not just Windows/PowerShell.
- Add troubleshooting notes for common issues encountered on Linux/macOS (e.g., file encoding, permission errors) if not already present.
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates several Windows-centric biases. Windows tools such as 'winget' are used for installing kubectl, which is not available on Linux/macOS. File path examples and extraction commands use Windows-style paths and commands (e.g., Expand-Archive with C:\ paths) in both Bash and PowerShell tabs, and there are no Linux/macOS equivalents (e.g., unzip, tar, or homebrew). Bash examples are often just Windows commands run in Bash, not true Linux shell commands. PowerShell is given equal or greater prominence, and Linux-native installation and file manipulation patterns are missing.
Recommendations
- Add Linux/macOS-specific instructions for installing kubectl (e.g., using curl, apt, yum, or Homebrew).
- Provide Linux/macOS file extraction commands (e.g., unzip, tar) and use POSIX-style paths (/home/user/...).
- Ensure Bash tab examples use Linux-native commands and syntax, not Windows commands.
- Include explicit notes or tabs for macOS where relevant.
- Where Windows tools (e.g., winget, Expand-Archive) are mentioned, provide equivalent Linux/macOS alternatives.
- Review all file path and environment variable usage for cross-platform compatibility.
- Consider reordering examples so that Linux-native commands appear before or alongside Windows commands.
Azure Arc
What's new in Azure Arc-enabled VMware vSphere
...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page shows a moderate Windows bias. Windows-specific features (such as customizing Windows VM guest OS settings and Windows Server Management) are highlighted, and Windows tools (PowerShell, System Center Configuration Manager, Group Policy) are mentioned explicitly for agent installation at scale, while Linux equivalents are either absent or mentioned later. There is a lack of parity in examples and tooling for Linux, with only a brief mention of SSH-based Linux agent installation and Ansible playbook, but no details or Linux-first examples.
Recommendations
- Provide Linux-specific examples and tooling for agent installation at scale (e.g., shell scripts, cloud-init, Linux-native automation tools) alongside Windows tools.
- Ensure that Linux features (such as customizing Linux VM guest OS settings) are mentioned with equal prominence and detail as Windows features.
- Include Linux equivalents for Windows management features (e.g., cost benefits, update management) where applicable.
- Add parity in documentation for Linux-focused orchestration and configuration management tools (e.g., Chef, Puppet) if supported.
- Where Windows tools are listed, explicitly mention Linux alternatives in the same context and order.
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. All command-line examples use PowerShell syntax (with backticks for line continuation and Windows-style paths), and there are no bash, Linux shell, or cross-platform CLI examples. File paths in JSON templates and scripts use Windows drive letters and backslashes. Script automation is exclusively shown with PowerShell scripts (.ps1), with no mention of bash or shell alternatives. There is no guidance for Linux or macOS users, nor any mention of how to adapt the instructions for non-Windows environments.
Recommendations
- Provide equivalent bash or shell script examples for all PowerShell commands, using POSIX-compliant syntax and Linux-style paths.
- Show how to run Azure CLI commands in Linux/macOS terminals, including line continuation with '\' and environment variable usage.
- Include notes or sections for Linux/macOS users, highlighting any differences in file paths, script execution, or prerequisites.
- Offer downloadable script templates in both PowerShell (.ps1) and bash (.sh) formats.
- Avoid using Windows-only file paths in JSON templates; use relative paths or examples compatible with both platforms.
- Explicitly state cross-platform compatibility for all tools and extensions, and provide troubleshooting tips for Linux environments.
Azure Arc
Migrate Existing Target Resources to General Availability
...s/azure-arc/workload-orchestration/migration-script.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by providing only a PowerShell migration script example, referencing a .ps1 file (PowerShell script), and instructing users to run the script in PowerShell. There are no equivalent instructions or examples for Linux users (e.g., Bash scripts or cross-platform alternatives), nor is there mention of how to perform the migration on non-Windows systems.
Recommendations
- Provide a Bash or shell script alternative for Linux users, or clarify if the PowerShell script can be run using PowerShell Core on Linux/macOS.
- Include explicit instructions for running the migration on Linux and macOS, including installation steps for PowerShell Core if needed.
- Mention cross-platform compatibility of the migration script, if applicable, and test/document any platform-specific caveats.
- Ensure that examples and instructions for Linux are given equal prominence and detail as those for Windows.
Azure Arc
Onboarding Scripts for Workload Orchestration
...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias. All script examples use PowerShell (.ps1) and instruct users to open a PowerShell terminal, with no mention of Bash, Linux shell, or cross-platform alternatives. Prerequisites use 'winget', a Windows-only package manager, to install tools like Azure CLI and kubectl, without providing equivalent Linux/macOS instructions (e.g., apt, yum, brew). There are no Linux-specific onboarding script examples, nor any notes about running these scripts on non-Windows platforms.
Recommendations
- Provide equivalent onboarding script examples for Bash/shell environments, including .sh scripts if available.
- List Linux/macOS installation commands for prerequisites (e.g., use apt, yum, or brew for Azure CLI and kubectl).
- Clarify whether the onboarding scripts are cross-platform, and if not, provide guidance or alternatives for Linux/macOS users.
- Mention and document any required dependencies or compatibility notes for running the scripts on non-Windows systems.
- Consider using cross-platform scripting languages (e.g., Python) or provide containerized solutions for onboarding.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page predominantly features CLI examples using Powershell syntax (backticks for line continuation, variable notation), which is specific to Windows environments. There are no Bash or Linux shell equivalents provided, and the only explicit CLI examples for configuration management use Powershell. This suggests a bias towards Windows users, potentially making it less accessible for Linux users who use Bash or other shells.
Recommendations
- Provide equivalent Bash examples for all CLI commands, especially those currently shown only in Powershell.
- When presenting CLI instructions, use cross-platform syntax (e.g., avoid Powershell-specific line continuation and variable notation) or show both Windows and Linux variants.
- Explicitly mention that the Azure CLI is cross-platform and clarify any OS-specific instructions.
- Review all examples and ensure Linux users are equally supported, including troubleshooting and file path conventions.
Azure Arc
Troubleshooting for Workload Orchestration
...es/azure-arc/workload-orchestration/troubleshooting.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. Most troubleshooting steps and command examples are provided exclusively in PowerShell, with Windows-centric syntax and patterns (e.g., use of variables like $var, ConvertTo-Json, Out-File, [Convert]::ToBase64String). Linux/Bash equivalents are missing for nearly all steps except the service group queries, which are presented in both Bash and PowerShell. Windows tools and workflows (PowerShell, Windows file encoding notes) are mentioned without Linux alternatives, and Windows commands are presented first or exclusively in most sections.
Recommendations
- Provide Bash/Linux equivalents for all PowerShell commands, especially for az, kubectl, docker, and file manipulation steps.
- Include Linux-specific instructions for file encoding and editing (e.g., using iconv, nano, or vim instead of Windows Notepad encoding advice).
- Use cross-platform variable syntax in examples (e.g., $var for PowerShell, $var for Bash, and avoid Windows-only constructs like @{ } | ConvertTo-Json).
- Explicitly state platform requirements or differences where applicable, and ensure troubleshooting steps are accessible to Linux users.
- Review all command snippets to ensure they work on both Windows and Linux shells, or provide clear tabs/sections for each OS.
Azure Portal
Create an Azure portal dashboard by using a Bicep file
.../blob/main/articles/azure-portal/quick-create-bicep.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
This documentation page exhibits Windows bias in several ways: the example VM deployed is hard-coded as 'SimpleWinVM', with references to Windows-specific username and password requirements. The prerequisites and deployment instructions mention Azure PowerShell and Azure CLI, but the VM template and guidance are tailored for a Windows VM only, with no mention of Linux VM options or Linux-specific requirements. There are no examples or instructions for deploying a Linux VM or managing Linux credentials, and the documentation links for username/password requirements point to Windows VM documentation.
Recommendations
- Provide parallel examples for deploying a Linux VM (e.g., 'SimpleLinuxVM'), including Linux-specific username and password requirements.
- Include links to Linux VM documentation for credential requirements.
- Make it clear that the dashboard can visualize both Windows and Linux VMs, and provide sample Bicep/ARM templates for each.
- Ensure that CLI and PowerShell examples use variables and resource names that are not Windows-specific.
- Add a note or section explaining how to adapt the process for Linux VMs, including any differences in deployment parameters or dashboard configuration.
Azure Portal
How to create an Azure support request
.../supportability/how-to-create-azure-support-request.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page displays a Windows bias in several ways. The 'Advanced diagnostic information logs' and 'Memory dump collection' sections focus on Windows-specific logs and memory dump formats, referencing Windows VM logs and Windows kernel-mode dumps without mentioning Linux equivalents. The memory dump process is described exclusively in terms of Windows (Hyper-V, Windows memory), with no discussion of Linux VM diagnostics or dump collection. There are no examples or guidance for Linux users, and Windows terminology and tools are presented first and exclusively.
Recommendations
- Include information and examples for Linux VM diagnostics, such as collecting logs and memory dumps from Linux-based Azure VMs.
- Add references to Linux-specific troubleshooting guides and support data collection procedures.
- When listing diagnostic logs or support packages, explicitly mention both Windows and Linux options, and provide parity in instructions.
- Describe memory dump collection for Linux VMs, including any differences in process, impact, and data collected.
- Ensure that examples and terminology are platform-neutral or provide both Windows and Linux variants side-by-side.
Azure Portal
Create an Azure portal dashboard by using an Azure Resource Manager template
...ob/main/articles/azure-portal/quick-create-template.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All example commands for creating the required VM use PowerShell, with no Bash or Azure CLI equivalents shown. The resource group and VM names (SimpleWinVmResourceGroup, myVM1) and referenced documentation (Windows username/password requirements) further reinforce a Windows-centric approach. There are no instructions or examples for Linux users, nor are Linux VM creation patterns mentioned. The use of PowerShell in Cloud Shell is presented as the default, with no mention of Bash.
Recommendations
- Provide equivalent Azure CLI or Bash examples for VM and resource group creation, especially in Cloud Shell.
- Include instructions for creating a Linux VM, with appropriate references to Linux username/password requirements.
- Use more neutral resource group and VM names (e.g., 'SimpleVmResourceGroup', 'myVM1') or provide parallel examples for Windows and Linux.
- Explicitly mention that Cloud Shell supports both PowerShell and Bash, and show how to select Bash.
- Add links to Linux VM documentation and best practices alongside Windows references.
- Ensure that deployment and cleanup instructions are platform-agnostic or provide both Windows and Linux command examples.
Container Registry
Quickstart - Create Registry - Bicep
...ainer-registry/container-registry-get-started-bicep.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell and Visual Studio Code as primary tools, providing explicit PowerShell deployment instructions, and mentioning the integrated VS Code terminal shortcut (which is Windows-specific). There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific editors or terminal usage. The Azure CLI example is present, but it is not clearly contextualized for Linux users, and the PowerShell tab appears before CLI in the deployment section.
Recommendations
- Add explicit bash shell examples for deploying the Bicep file on Linux/macOS.
- Mention Linux-compatible editors (e.g., Vim, Nano, VS Code on Linux) in the 'Review the Bicep file' section.
- Clarify that Azure CLI commands work cross-platform and provide terminal instructions for Linux/macOS (e.g., using 'cd' and './').
- Avoid referencing Windows-specific shortcuts (e.g., ctrl+` for VS Code) without noting Linux/macOS equivalents.
- Ensure that CLI examples are presented before PowerShell, or at least in parallel, to avoid Windows-first ordering.
Container Registry
Service Principal Authentication for ACR
...-registry/container-registry-auth-service-principal.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation references both Azure CLI and Azure PowerShell sample scripts, but lists Azure PowerShell second and does not provide explicit Linux shell examples for service principal creation or management. The only command-line example shown is for 'docker login', which is cross-platform, but the links to sample scripts and the mention of PowerShell may suggest a slight Windows-first bias. There is no mention of Linux-specific tools or patterns, and no explicit Bash or shell script examples for service principal creation or credential management. The certificate section references 'openssl', which is cross-platform, but does not provide a full Linux workflow.
Recommendations
- Add explicit Bash and Linux shell examples for service principal creation, credential reset, and certificate management.
- List Azure CLI (cross-platform) examples before PowerShell, and clarify that CLI commands work on Linux, macOS, and Windows.
- Provide links to Linux-focused sample scripts or workflows, and mention Linux-specific considerations where relevant.
- Ensure parity in documentation by including both PowerShell and Bash examples side-by-side where possible.
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently presenting Azure PowerShell examples alongside or immediately after Azure CLI, referencing Windows-centric tools and patterns (PowerShell, Azure portal), and omitting explicit Linux shell examples (e.g., bash scripts, Linux-native workflows). While there is a brief mention of podman for RHEL, most authentication and management scenarios are described using Windows tools or interfaces first, with Linux alternatives only referenced as exceptions.
Recommendations
- Add explicit bash/Linux shell examples for all authentication scenarios, not just Azure CLI but also for service principal and admin account workflows.
- Present Linux-native workflows (e.g., bash, podman, environment variables) alongside or before Windows/PowerShell examples to ensure parity.
- Include instructions for using Azure CLI and Docker/podman on Linux, including installation and troubleshooting steps relevant to Linux environments.
- Reference Linux desktop environments and terminal usage where appropriate, not just the Azure portal or PowerShell.
- Ensure all examples using environment variables, file paths, or command syntax are cross-platform (e.g., avoid Windows-style paths or commands unless also providing Linux equivalents).
Container Registry
Push & Pull Container Image using Azure Container Registry
...-registry/container-registry-get-started-docker-cli.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided alongside Azure CLI, but there are no equivalent Linux shell examples (e.g., Bash, sh) for Azure-specific commands. Windows tools and patterns, such as Visual Studio Code and its Docker extension, are mentioned as recommended options. The order of presentation often puts Windows-centric tools (PowerShell, VS Code) before Linux alternatives, and there is no explicit mention of Linux-native Azure management tools or shell scripting.
Recommendations
- Add Bash or sh examples for Azure CLI commands to demonstrate usage on Linux systems.
- Explicitly mention Linux shell environments and provide guidance for using Azure CLI in Bash.
- Balance recommendations for development tools by including Linux-native editors (e.g., Vim, Emacs, GNOME Builder) and extensions.
- Clarify that Azure CLI works cross-platform and show examples of authentication and image management in Linux terminal environments.
- Include troubleshooting or tips specific to Linux users, such as dealing with Docker permissions or using service principals in shell scripts.
Container Registry
Quickstart - Create Registry in Portal
...iner-registry/container-registry-get-started-portal.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page presents both Azure CLI and Azure PowerShell options for signing in to the registry, but gives equal prominence to PowerShell, which is primarily a Windows-centric tool. There are no explicit Linux shell examples (e.g., Bash), and the PowerShell instructions may not be directly applicable to Linux users. The page references Docker installation for Mac, Windows, and Linux, but all command-line examples for Azure interactions are either Azure CLI (cross-platform) or PowerShell (Windows-first). There is no mention of Linux-specific patterns or tools, and PowerShell is given a dedicated section before any Linux shell alternatives.
Recommendations
- Add explicit Bash/Linux shell examples for Azure CLI usage, demonstrating commands in a Linux terminal context.
- Clarify that Azure CLI commands work equally well on Linux, macOS, and Windows, and provide sample outputs from a Linux shell.
- De-emphasize PowerShell as a primary option, or move it after CLI/Bash examples to avoid Windows-first ordering.
- Include notes or sections for Linux users, such as common troubleshooting steps, environment setup, or differences in authentication flows.
- Ensure parity in screenshots and instructions, e.g., showing Linux terminal screenshots alongside Windows/PowerShell ones.
Container Registry
Manage OCI Artifacts and Supply Chain Artifacts with ORAS
...ntainer-registry/container-registry-manage-artifact.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Linux/macOS and Windows examples for ORAS CLI usage, but Windows examples are consistently presented after Linux/macOS. Windows-specific command syntax (cmd.exe) is included, but there is no PowerShell-specific example. The documentation references Docker Desktop (a Windows-centric tool) for credential storage, and mentions WSL2 (Windows Subsystem for Linux), which is a Windows-specific compatibility layer. However, Linux and macOS are generally well-represented, and most commands are shown for bash first. There are no missing Linux examples, but Windows tooling and patterns are referenced, and Windows-specific instructions are provided throughout.
Recommendations
- Add PowerShell examples alongside cmd.exe for Windows users, as PowerShell is increasingly the default shell.
- Clarify Docker credential store usage for Linux (e.g., pass or secretservice) and macOS (keychain), not just Docker Desktop.
- Present Windows and Linux/macOS examples in parallel, rather than always listing Linux/macOS first.
- Reduce reliance on WSL2 references; provide native Linux instructions where possible.
- Explicitly mention Linux credential store alternatives and authentication flows, not just AD token and Docker Desktop.
- Where Windows-specific tools or patterns are mentioned, provide equivalent Linux/macOS alternatives and links.
Container Registry
Azure Container Registry Entra permissions and role assignments overview
...try/container-registry-rbac-built-in-roles-overview.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation references Azure PowerShell as a primary method for role assignment alongside Azure CLI and portal, but does not provide explicit Linux-specific examples or mention Linux-native tools. The order of listing ('Azure portal', 'Azure CLI', 'Azure PowerShell') may suggest a Windows-first approach, and there are no Bash or Linux shell examples or references to Linux package managers or automation tools. The documentation is neutral in most technical details, but the lack of Linux-specific guidance and examples may disadvantage Linux users.
Recommendations
- Add explicit examples for performing role assignments using Bash or Linux shell environments.
- Clarify that Azure CLI is cross-platform and provide sample commands for Linux terminals.
- Include references to Linux-native automation tools (e.g., shell scripts, Ansible) where appropriate.
- Balance the mention of Azure PowerShell with equivalent Linux-friendly instructions, or note platform compatibility.
- Consider reordering tool lists or explicitly stating platform parity to avoid perceived Windows-first bias.
Container Registry
Error Reference for Registry Health Checks
...-registry/container-registry-health-error-reference.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation exhibits mild Windows bias, particularly in the 'NOTARY_VERSION_ERROR' section, where Windows-specific instructions (e.g., using notary.exe, referencing C:\ProgramFiles\Docker\Docker\resources\bin) are given in detail, while Linux and macOS instructions are less explicit and appear after the Windows example. Several recommendations reference 'system variables' or 'system environment variables' without clarifying platform differences, and there are no explicit Linux or macOS command-line examples or file paths provided throughout the document.
Recommendations
- For every mention of adding a tool to 'system variables' or 'system environment variables', provide explicit instructions or links for both Windows (using System Properties or setx) and Linux/macOS (editing ~/.bashrc, ~/.zshrc, or /etc/environment).
- In the 'NOTARY_VERSION_ERROR' section, provide equally detailed instructions for Linux and macOS, including example file paths (e.g., /usr/local/bin/notary) and installation steps.
- Wherever a Windows path or .exe is mentioned, also mention the equivalent for Linux/macOS (e.g., binary name, typical install location).
- Add Linux/macOS-specific troubleshooting steps or notes where relevant, especially for Docker and Helm installation and path configuration.
- Consider including example commands for both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) where manual command execution is suggested.
Container Registry
Azure Container Registry SKU Features and Limits
...articles/container-registry/container-registry-skus.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page presents both Azure CLI and Azure PowerShell examples for managing Azure Container Registry SKUs, but it consistently lists PowerShell (a Windows-centric tool) alongside or immediately after CLI commands, without providing explicit Linux shell examples (e.g., Bash). There is no mention of Linux-specific tools or workflows, and the examples do not clarify cross-platform usage or differences. The documentation assumes familiarity with PowerShell, which may not be common for Linux users.
Recommendations
- Add explicit Bash/Linux shell examples for all CLI commands, clarifying cross-platform compatibility.
- Clearly indicate that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily Windows-focused.
- If PowerShell is mentioned, also mention Linux alternatives (e.g., Bash scripts, shell scripting) and provide equivalent examples.
- Consider listing Azure CLI (cross-platform) examples before PowerShell examples to avoid Windows-first perception.
- Include a section or note on platform compatibility for all tools and commands referenced.
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page includes several examples that reference Windows-specific tools and patterns, such as PowerShell and Azure PowerShell scripts, with no equivalent examples for Linux shell environments (e.g., Bash). PowerShell examples are presented alongside Azure CLI, but there is no parity for Linux-native scripting or command-line environments. The documentation mentions Windows-centric tools first (PowerShell) and does not provide Linux shell alternatives, which may disadvantage Linux users or those working in cross-platform environments.
Recommendations
- Add example prompts for Bash or Linux shell scripting, especially for resource management tasks currently shown only with PowerShell.
- Ensure parity between PowerShell and CLI examples by providing both Windows and Linux command-line alternatives for each scenario.
- Explicitly mention cross-platform compatibility for Azure CLI and clarify when PowerShell examples are Windows-specific.
- Consider reordering examples so that CLI (cross-platform) appears before PowerShell (Windows-centric) to reduce perceived Windows-first bias.
- Include prompts that demonstrate Linux administration tasks (e.g., using SSH, Bash scripts) in addition to Windows/PowerShell tasks.
Copilot
Manage and migrate storage accounts using Azure Copilot
...blob/main/articles/copilot/improve-storage-accounts.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits Windows bias primarily through its focus on Azure File Sync, a Windows-centric tool, and error codes that are relevant only to Windows environments. There are no Linux-specific troubleshooting examples, tools, or migration scenarios highlighted. While migration prompts mention SMB and NFS, the detailed troubleshooting and operational guidance centers on Windows technologies, with no parity for Linux equivalents (e.g., NFS troubleshooting, Linux-based sync agents). All examples and screenshots are generic or Windows-oriented, and there is no mention of Linux command-line tools, scripts, or platform-specific considerations.
Recommendations
- Add troubleshooting examples and guidance for Linux-based storage scenarios, such as NFS shares and Linux sync agents.
- Include sample prompts and screenshots for Linux environments, e.g., resolving NFS mount issues or permissions errors on Linux file shares.
- Reference Linux-native migration tools (such as rsync, azcopy for Linux, or third-party Linux migration solutions) alongside Windows tools.
- Provide parity in error code documentation for Linux-based storage solutions and common issues encountered in Linux environments.
- Ensure that migration, security, and resiliency sections explicitly address both Windows and Linux use cases, with examples for each.
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by focusing on PowerShell and its module (AIShell), referencing only PowerShell-specific installation and documentation links, and omitting explicit Linux shell (e.g., Bash) examples or instructions. The examples and instructions prioritize PowerShell and Windows-centric tools, with no mention of Linux equivalents or cross-platform usage patterns.
Recommendations
- Include explicit Bash or Linux shell examples alongside PowerShell examples to demonstrate parity.
- Reference installation instructions and system requirements for both Windows (PowerShell) and Linux/macOS (Bash, Zsh, etc.).
- Provide links to cross-platform documentation, not just PowerShell-specific resources.
- Clarify that AI Shell works in multiple terminal environments and describe any platform-specific differences.
- Mention how Linux users can install and use AI Shell, including any required dependencies or alternative modules.
Copilot
Optimization agent capabilities in Agents (preview) in Azure Copilot
...-docs/blob/main/articles/copilot/optimization-agent.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by explicitly mentioning PowerShell script generation for optimization tasks and listing PowerShell before Azure CLI. There are no examples or references to Linux-specific tools, shell environments, or script formats (e.g., Bash). All sample prompts and instructions focus on PowerShell and CLI, with PowerShell mentioned first and no Linux/Bash script examples provided.
Recommendations
- Include explicit examples of Bash scripts for Linux users alongside PowerShell and Azure CLI.
- Mention Linux shell environments (e.g., Bash, zsh) when discussing script generation and execution.
- Alternate the order of script type mentions (e.g., say 'Azure CLI or PowerShell' instead of always listing PowerShell first).
- Clarify that generated CLI scripts are cross-platform and provide guidance for running them on Linux/macOS.
- Add sample prompts requesting Bash scripts for optimization tasks.
- Reference Linux tools and patterns where relevant, and ensure parity in instructions for both Windows and Linux users.
Lighthouse
Cross-tenant management experiences
...hthouse/concepts/cross-tenant-management-experience.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates mild Windows bias, primarily in the order and emphasis of tooling. Azure PowerShell (a Windows-centric tool) is mentioned before Azure CLI, and the only explicit command example is for PowerShell. Windows Server is mentioned before Linux in hybrid management scenarios. There is no explicit Linux shell example, and Windows terminology/tools are referenced more frequently or earlier than their Linux equivalents.
Recommendations
- Present Azure CLI examples before or alongside Azure PowerShell examples, and include explicit Linux shell usage where relevant.
- When listing supported operating systems (e.g., for Azure Arc-enabled servers), mention Linux before or alongside Windows Server.
- Provide balanced examples for both Windows and Linux environments, especially in hybrid management scenarios.
- Avoid defaulting to Windows-centric terminology (e.g., PowerShell cmdlets) and ensure parity with Linux tools and workflows.
- Add explicit Linux shell command examples where management tasks are discussed.
Lighthouse
Monitor delegated resources at scale
...ob/main/articles/lighthouse/how-to/monitor-at-scale.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for key resource provider registration tasks, mentioning PowerShell as the sole automation method, and omitting equivalent Azure CLI or Bash examples that would be more familiar to Linux users. The instructions and code samples focus exclusively on Windows-centric tooling and scripting, with no mention of Linux-native alternatives or cross-platform approaches.
Recommendations
- Add Azure CLI examples alongside PowerShell for resource provider registration and other automation tasks.
- Explicitly mention that Azure CLI and Bash can be used on Linux and macOS, and provide sample commands.
- When listing automation options, present cross-platform tools (Azure CLI, REST API) before or alongside PowerShell.
- Include notes or links to documentation for Linux users, ensuring parity in guidance for both Windows and Linux environments.
- Review all code samples and ensure that for every PowerShell example, a CLI/Bash equivalent is provided.
Lighthouse
Onboard a customer to Azure Lighthouse
...ob/main/articles/lighthouse/how-to/onboard-customer.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a mild Windows bias. While Azure CLI is included (which is cross-platform), Azure PowerShell is given equal prominence and is featured in all example sections. There are no explicit Linux shell (bash) or automation examples, and no mention of Linux-specific tools or workflows. The instructions for command-line deployment and verification are presented as Azure CLI and PowerShell tabs, but PowerShell is a Windows-centric tool, and there is no parity for native Linux shell scripting or automation. Additionally, references to 'Cloud Shell' do not clarify that it is available on both Windows and Linux, and the documentation does not provide any bash or shell script equivalents.
Recommendations
- Add bash shell script examples for template deployment and verification, using Azure CLI commands, to demonstrate Linux-native workflows.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Explicitly mention that Cloud Shell is available on both Windows and Linux, and provide instructions for accessing it from Linux environments.
- Consider including automation examples using bash scripting for common onboarding tasks.
- Review references to PowerShell and ensure they are balanced with Linux-native alternatives where possible.
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell for resource creation and management tasks, with specific cmdlets mentioned and no equivalent Azure CLI or REST API examples provided inline. PowerShell is a Windows-centric tool, and its usage is described before mentioning Azure CLI in the 'Next steps' section. There are no Linux-specific examples or guidance, and the documentation does not address cross-platform usage patterns directly.
Recommendations
- Include Azure CLI examples alongside PowerShell examples for all resource creation and management tasks, especially for registration definition and assignment.
- Explicitly mention REST API options and provide sample requests for users who prefer platform-agnostic approaches.
- Ensure that references to management tools are balanced, listing Azure CLI before or alongside PowerShell where appropriate.
- Add notes or sections highlighting cross-platform compatibility and usage, including instructions for Linux and macOS users.
- Review and update onboarding instructions to show both PowerShell and CLI workflows in parallel.
Lighthouse
Monitor delegation changes in your managing tenant
...ticles/lighthouse/how-to/monitor-delegation-changes.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell scripts for querying delegation changes and referencing Windows-centric tools and patterns. While Azure CLI is mentioned for role assignment, all advanced scripting and automation examples are exclusively given in PowerShell, with no equivalent Bash or Linux shell scripts. There is no guidance for Linux users on how to perform the same monitoring tasks outside of PowerShell, and the PowerShell script is presented first and in greater detail.
Recommendations
- Provide equivalent Bash or shell script examples for querying delegation changes using REST API calls with curl or az CLI, suitable for Linux environments.
- Ensure that Azure CLI examples are as detailed and comprehensive as PowerShell examples, especially for advanced automation tasks.
- Explicitly mention cross-platform compatibility and provide instructions for both Windows and Linux users.
- Consider including sample scripts in Python or other cross-platform languages for automation.
- Reorder examples so that Azure CLI or platform-neutral solutions are presented before or alongside PowerShell scripts.
Lighthouse
Onboard all subscriptions in a management group
...articles/lighthouse/how-to/onboard-management-group.md
High 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, with no equivalent CLI (az), Bash, or Linux-native instructions. The use of PowerShell as the sole automation example assumes a Windows environment or familiarity with PowerShell, which may disadvantage Linux or cross-platform users. There is no mention of Azure CLI or other cross-platform tools, and the PowerShell example is presented as the primary (and only) method.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands, especially for policy assignment and deployment.
- Explicitly mention that PowerShell Core is cross-platform, or clarify if the script requires Windows PowerShell.
- Provide Bash or shell script examples where appropriate, or at least reference how Linux/macOS users can perform the same tasks.
- When listing automation options (e.g., Logic Apps, scripts), avoid assuming PowerShell is the default and present CLI or REST API alternatives.
- Consider a 'Choose your platform' section or table that shows how to perform key steps using PowerShell, Azure CLI, and REST API.
Lighthouse
Deploy Azure Policy to delegated subscriptions at scale
...lob/main/articles/lighthouse/how-to/policy-at-scale.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively uses PowerShell for all examples and instructions, which is primarily associated with Windows environments. There are no examples or guidance for using Azure CLI, Bash, or other Linux-native tools. The use of PowerShell cmdlets and patterns is pervasive, and there is no mention of Linux or cross-platform alternatives, which may hinder accessibility for users on Linux or macOS.
Recommendations
- Provide equivalent examples using Azure CLI commands, which are natively supported on Linux and macOS.
- Add notes or sections indicating how to perform these tasks in Bash or other shell environments.
- Clarify that PowerShell Core is cross-platform, but also explicitly support and document Linux-native workflows.
- Ensure that tool recommendations and examples do not assume a Windows-first environment; present cross-platform options side-by-side.
- Include troubleshooting or setup guidance for Linux users where necessary (e.g., installing Azure CLI, authentication differences).
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell as a primary method for viewing network quota usage, placing it before REST API and alongside Azure CLI. The explicit mention and linking of Azure PowerShell (a Windows-centric tool) without providing parity for Linux-native alternatives (such as Bash scripting or direct CLI examples) suggests a preference for Windows tools. There are no Linux-specific examples or references, and the ordering of tools implies Windows-first thinking.
Recommendations
- Provide explicit Linux/Bash examples for viewing and managing quotas using Azure CLI.
- Reorder the list of tools to mention Azure CLI before Azure PowerShell, reflecting cross-platform parity.
- Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux (Bash).
- Add notes or examples for Linux users, especially for command-line operations.
- Avoid listing Windows-centric tools (like PowerShell) before cross-platform alternatives unless contextually justified.
Medium Priority
View Details →
Detected Bias Types
missing_windows_example
linux_tools
Summary
The documentation exclusively provides Linux-based examples using the 'attr' command and shell syntax, with no mention of Windows equivalents, PowerShell commands, or Windows-specific tooling. This indicates a bias toward Linux environments and may leave Windows users without clear guidance.
Recommendations
- Add equivalent Windows examples using PowerShell or relevant Windows tools (e.g., using 'Get-Item', 'Set-ItemProperty', or third-party utilities for NTFS alternate data streams or extended attributes).
- Explicitly mention whether the described functionality is supported on Windows, and if so, how to achieve it.
- Include a section comparing Linux and Windows approaches to setting extended attributes for blob index and metadata tags.
- Clarify any platform limitations or prerequisites for both Linux and Windows users.
Azure Arc
Get logs to troubleshoot Azure Arc-enabled data services
...in/articles/azure-arc/data/troubleshooting-get-logs.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides a CLI example that uses a Windows-style path (C:\temp\logs) and does not include a Linux/macOS equivalent (such as /tmp/logs). There are no PowerShell-specific commands or Windows-only tools mentioned, but the example and directory pathing implicitly prioritize Windows users and omit Linux parity.
Recommendations
- Add a Linux/macOS example alongside the Windows example, e.g., --target-folder /tmp/logs.
- Explicitly mention that the CLI commands work on both Windows and Linux/macOS, and provide guidance for path formatting on each OS.
- Consider alternating the order of examples or presenting both OS options together to avoid implicit prioritization.
- If relevant, note any OS-specific considerations for file permissions or CLI usage.
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
Medium 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 given immediately after the CLI example, and no explicit Linux shell (bash) or cross-platform command is highlighted. The use of PowerShell may suggest a Windows-centric approach, especially since PowerShell is traditionally associated with Windows environments.
Recommendations
- Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for Linux users.
- Provide a bash shell example (e.g., using jq or grep) for parsing Azure CLI output on Linux.
- Clarify that PowerShell is available on Linux, but many Linux users may prefer bash or other native tools.
- Consider listing the CLI example first, or equally highlighting both CLI and PowerShell options.
Azure Arc
CLI reference for `azcmagent disconnect`
...ain/articles/azure-arc/servers/azcmagent-disconnect.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation demonstrates Windows bias by describing the interactive browser login as 'Windows only' and presenting it before Linux authentication methods. Additionally, the only method shown for obtaining an access token is via the Windows-centric PowerShell cmdlet 'Get-AzAccessToken', with no mention of Linux or cross-platform alternatives.
Recommendations
- Present authentication options in a neutral or cross-platform order, or explicitly alternate between Windows and Linux methods.
- For access token acquisition, include Linux-compatible methods such as using 'az account get-access-token' from Azure CLI.
- Clarify which authentication methods are available on Linux and provide equivalent Linux examples where applicable.
- Avoid labeling features as '(Windows only)' without also specifying Linux alternatives or behaviors.
- Where PowerShell is referenced, also mention Bash or other Linux shell equivalents for parity.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation generally presents Windows and Linux log locations side-by-side, maintaining parity. However, there is a subtle Windows bias in the 'Azure Activity log' section, where the link to retaining activity logs explicitly references PowerShell, a Windows-centric tool, without mentioning Linux alternatives (such as Azure CLI or REST API). Additionally, in all log location tables, Windows paths are listed before Linux paths, which may reinforce a Windows-first perspective.
Recommendations
- Provide Linux-specific instructions or examples alongside PowerShell references, such as using Azure CLI or Bash scripts for activity log retention.
- Alternate the order of OS examples in tables or documentation sections, sometimes listing Linux first to balance perspective.
- Explicitly state that both Windows and Linux are supported and provide parity in tooling and documentation.
- Where possible, link to documentation tabs or sections for both PowerShell and CLI, ensuring Linux users are equally served.
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 Windows bias by providing only a PowerShell example for extension removal, with no equivalent Linux CLI or shell command. Windows paths and tools are often listed before their Linux counterparts, and troubleshooting steps reference Windows-specific details first. Linux users may find the guidance less accessible due to missing parity in command examples and ordering.
Recommendations
- Provide Linux CLI (e.g., Bash, az CLI) examples alongside PowerShell commands for extension management tasks.
- Present Windows and Linux instructions in parallel or alternate the order to avoid consistently listing Windows first.
- Include Linux-specific troubleshooting commands and patterns (such as systemctl, journalctl, or relevant log inspection commands).
- Ensure all steps and examples are equally detailed for both platforms, especially for manual cleanup and log review.
- Consider a table or side-by-side format for Windows and Linux paths, commands, and procedures.
Azure Arc
Set up and manage self-service access to SCVMM resources
...manager/set-up-and-manage-self-service-access-scvmm.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is focused exclusively on SCVMM, a Windows-centric virtualization management tool, and all examples and instructions are tailored to Azure Portal UI and SCVMM resources. There is no mention of Linux-based management tools, Linux VMs, or cross-platform command-line alternatives (e.g., Azure CLI, Bash). The documentation implicitly assumes a Windows environment and audience.
Recommendations
- Include examples or guidance for managing Linux VMs within SCVMM, if supported.
- Provide Azure CLI or REST API examples for role assignment, which are cross-platform and usable from Linux/macOS.
- Explicitly mention whether the process applies to Linux-based SCVMM resources or clarify SCVMM's Windows-only scope.
- Add a section comparing SCVMM with other virtualization management platforms (e.g., VMware, Linux KVM) and how Azure Arc handles access control for those.
- Ensure parity by referencing Linux-friendly tools and workflows where possible, or state limitations clearly.
Azure Arc
Perform ongoing maintenance and administration for Azure Arc-enabled VMware vSphere
...cles/azure-arc/vmware-vsphere/administer-arc-vmware.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure CLI commands and Azure portal workflows, with no mention of Linux-specific tools, shell environments, or alternative command-line patterns (e.g., Bash, SSH command examples). All instructions assume use of the Azure CLI, which is cross-platform, but there is no explicit guidance or examples for Linux users, such as using Bash, handling file paths, or troubleshooting with Linux utilities. The portal navigation and screenshots also reflect a Windows-centric workflow, and there is no mention of Linux desktop environments or command-line nuances.
Recommendations
- Add explicit Linux/Bash command examples alongside Azure CLI instructions, including handling of file paths and environment variables.
- Clarify that Azure CLI is cross-platform and provide installation instructions for Linux users.
- Include troubleshooting tips relevant to Linux environments (e.g., using SSH from Bash, checking file permissions).
- Reference Linux desktop environments or CLI workflows when describing portal navigation or file management.
- Ensure screenshots and UI instructions are not Windows-specific, or provide equivalent guidance for Linux users.
Azure Arc
Multiple Solutions with a Single Shared Dependency at Different Levels
...oad-orchestration/tutorial-service-group-scenario-4.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, but PowerShell is given equal prominence and detail as Bash, which is uncommon for Linux-first environments. The structure and language of the examples, as well as the use of PowerShell-specific syntax and idioms, may indicate a bias toward Windows users. Additionally, the documentation refers to the Azure portal for validation, which is a web-based tool but often associated with Windows-centric workflows. There is no explicit mention of Linux-specific tools, troubleshooting, or environment setup, and no prioritization of Linux-native workflows.
Recommendations
- Ensure Bash examples are presented first in each section, as Bash is the default shell for most Linux environments.
- Add explicit notes about Linux prerequisites, such as package installation (e.g., Helm, Azure CLI) on popular Linux distributions.
- Include troubleshooting steps or environment setup guidance specific to Linux (e.g., permissions, file paths, shell differences).
- Clarify that PowerShell examples are intended for Windows users and Bash for Linux/macOS users.
- Consider adding a section on validating deployments using Linux-native tools (e.g., kubectl, journalctl) in addition to Helm.
- Review the language and structure to avoid assuming Windows as the default platform, and highlight Linux parity where possible.
Container Registry
Azure Container Registry custom roles
...ainer-registry/container-registry-rbac-custom-roles.md
Medium 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 after or as an alternative. In several places, Azure PowerShell is listed before or equally with Azure CLI, and no explicit Linux shell examples (e.g., Bash) or guidance for Linux users is provided. There is a slight preference for Windows tools and patterns, with no mention of Linux-specific considerations or parity.
Recommendations
- Ensure Azure CLI examples are presented first, as it is cross-platform and preferred for Linux users.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, while Azure PowerShell is primarily Windows-focused.
- Provide Bash shell usage examples or clarify that CLI commands are suitable for Linux terminals.
- Add notes or sections highlighting any differences or considerations for Linux users when creating or assigning roles.
- Avoid listing Azure PowerShell as the default or first option unless contextually appropriate for the majority of users.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page demonstrates a mild Windows bias by listing 'Generate PowerShell scripts' before Linux-oriented scripting options (such as Azure CLI and Terraform), and by referencing PowerShell specifically as a supported automation example. There are no explicit Linux shell (bash) or Linux tool examples, and Windows-centric tools (PowerShell) are mentioned by name, while Linux equivalents are not. No Linux-specific troubleshooting or usage patterns are described.
Recommendations
- Add explicit examples and references for Linux users, such as bash scripting and Linux command-line tools.
- Mention Linux shell script generation alongside PowerShell and Azure CLI, and provide parity in example coverage.
- Include troubleshooting scenarios and examples relevant to Linux environments, such as SSH, systemd, or Linux-specific error messages.
- Ensure that references to scripting and automation tools are balanced, listing Azure CLI, bash, and PowerShell together rather than prioritizing Windows-centric tools.
- Where possible, provide links to documentation or guides for both Windows and Linux workflows.
Quotas
Increase Azure Storage account quotas
...main/articles/quotas/storage-account-quota-requests.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation lists Azure PowerShell as the first tool for viewing storage account quota usage, followed by Azure CLI and REST API. PowerShell is primarily a Windows-centric tool, and its placement before the cross-platform Azure CLI may suggest a Windows-first or PowerShell-heavy bias. No explicit Linux examples or Linux-specific instructions are provided.
Recommendations
- List Azure CLI before Azure PowerShell, as CLI is cross-platform and widely used on Linux and macOS.
- Provide explicit examples for both Azure CLI and PowerShell, ensuring parity and clarity for Linux users.
- Mention that Azure CLI works natively on Linux and macOS, and provide installation links for those platforms.
- Avoid implying PowerShell is the default or preferred method unless justified by usage data.
- Consider adding a short section or note for Linux/macOS users, highlighting any platform-specific considerations.
Azure Arc
Configure OneLake Identity for Cloud subvolumes
.../container-storage/howto-configure-onelake-identity.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing Power BI web links and portals, which are typically associated with Microsoft/Windows environments. There are no Linux-specific examples, command-line instructions, or alternative tooling mentioned for Linux users. The configuration steps focus on GUI navigation and do not provide parity for Linux administrators who may prefer or require CLI or non-GUI workflows.
Recommendations
- Include CLI-based instructions (e.g., Azure CLI, Bash scripts) for configuring OneLake Identity and subvolumes.
- Provide examples of how to perform these tasks on Linux systems, such as using curl, az CLI, or kubectl commands.
- Mention Linux-compatible tools and workflows alongside or before Windows/portal-based instructions.
- Clarify whether the configuration steps are platform-agnostic or provide explicit guidance for both Windows and Linux environments.
Azure Arc
Connectivity modes and requirements
...docs/blob/main/articles/azure-arc/data/connectivity.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page generally avoids explicit Windows bias in terms of tools or examples, but there is a subtle 'windows_first' bias in the authentication section, where Active Directory (AD) is mentioned as the default enterprise authentication method, with ADFS as an alternative. There are no explicit Linux authentication examples (e.g., LDAP, Kerberos), nor is there mention of Linux-native RBAC or identity providers. Additionally, while Kubernetes-native tools are referenced for provisioning, there are no concrete Linux command-line examples (e.g., bash, Linux shell commands), and no mention of Linux-specific patterns for connectivity, monitoring, or backup.
Recommendations
- Add Linux-native authentication examples, such as integration with LDAP, Kerberos, or other Linux identity providers.
- Provide explicit Linux shell command examples for provisioning and management alongside Azure CLI and Kubernetes tools.
- Mention Linux RBAC and local user/group management as alternatives to Active Directory and Azure RBAC.
- Include references to Linux-native monitoring tools (e.g., Prometheus, syslog) in addition to Grafana/Kibana.
- Ensure parity in backup and restore examples by referencing Linux storage classes and backup utilities.
Azure Arc
Deploy a new SQL Managed Instance enabled by Azure Arc using Kubernetes tools
...ate-sql-managed-instance-using-kubernetes-native-tools.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page demonstrates mild Windows bias. In the section about base64 encoding credentials, PowerShell is presented first, followed by Linux/macOS. The example for creating the SQL managed instance uses a Windows-style file path (C:\arc-data-services\sqlmi.yaml) in the command. The recommended text editor is VS Code, which is cross-platform but often associated with Windows. However, most commands use kubectl, which is platform-agnostic, and Linux/macOS instructions are present.
Recommendations
- Present Linux/macOS and Windows examples side-by-side, or alternate which platform is shown first.
- Use platform-neutral file paths in examples (e.g., ./arc-data-services/sqlmi.yaml) or provide both Windows and Linux/macOS path examples.
- Explicitly mention that VS Code is available on Linux/macOS, or suggest other popular editors for those platforms.
- Where PowerShell is used, also provide equivalent bash or shell commands for Linux/macOS users.
- Review all examples and notes to ensure Linux parity and avoid implicit prioritization of Windows tools or conventions.
Azure Arc
Delete resources from Azure Arc-enabled data services
...main/articles/azure-arc/data/delete-azure-resources.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (a web UI commonly associated with Windows workflows) for resource deletion steps and omitting any Linux-specific examples or tools. All command-line instructions use the Azure CLI, which is cross-platform, but there are no examples of using native Linux tools or shell patterns (e.g., bash scripts, kubectl commands) for resource deletion. The documentation does not mention or prioritize Linux workflows, nor does it provide parity for Linux users in terms of examples or guidance.
Recommendations
- Add examples using native Linux tools such as kubectl for deleting resources from Kubernetes clusters.
- Include bash script examples for automating resource deletion on Linux.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any OS-specific considerations.
- Provide guidance for Linux users on managing resources without relying solely on the Azure portal.
- Ensure that documentation sections are balanced, offering both Windows/portal and Linux/CLI or kubectl workflows side by side.
Azure Arc
Disaster recovery - SQL Managed Instance enabled by Azure Arc - portal
...-arc/data/managed-instance-disaster-recovery-portal.md
Medium Priority
View Details →
Detected Bias Types
missing_linux_example
windows_first
Summary
The documentation exclusively describes disaster recovery configuration using the Azure portal UI, without mentioning or providing examples for Linux-specific tools, workflows, or command-line interfaces. There are no references to Linux environments or considerations, and the only alternative mentioned is a CLI guide, which is not included here. The documentation implicitly assumes a GUI-first (often Windows-centric) workflow, potentially disadvantaging Linux users who may prefer or require non-GUI methods.
Recommendations
- Include explicit references and links to Linux-friendly command-line workflows (such as Azure CLI or Bash scripts) alongside portal instructions.
- Add a section summarizing cross-platform options for disaster recovery configuration, clarifying that the portal is accessible from any OS but that CLI and automation options are available and supported on Linux.
- Where possible, provide parallel examples or notes for both portal (GUI) and CLI (cross-platform) usage within the same document.
- Clarify that the Azure portal is web-based and not limited to Windows, to avoid the perception of Windows bias.
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 page demonstrates Windows bias by consistently presenting Windows-centric examples and file paths (e.g., C:\Backupfiles\test.bak) without offering equivalent Linux examples or guidance. Instructions for backup and file manipulation assume a Windows environment, and tools like Azure Data Studio and SQL Server Management Studio are referenced without clarifying cross-platform usage or alternatives. Linux file paths and workflows are only mentioned in the context of restoring within the pod, not for initial backup or file handling.
Recommendations
- Provide parallel Linux examples for all file operations, such as backing up to /home/user/Backupfiles/test.bak and copying from Linux file systems.
- Clarify that Azure Data Studio is cross-platform and provide installation and usage instructions for Linux and macOS.
- When referencing file paths, show both Windows (C:\...) and Linux (/home/...) formats.
- Explicitly mention that SQL Server Management Studio is Windows-only and suggest Azure Data Studio or sqlcmd for Linux/macOS users.
- Include notes or sections for Linux users at each step where OS-specific commands or paths are relevant.
- Ensure that screenshots, if any, and UI instructions are not Windows-exclusive, or provide Linux/macOS equivalents.
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation provides both Linux and Windows methods for base64 encoding, but the Windows-specific tool (certutil) is mentioned separately and with more detailed instructions, including manual header removal and use of findstr. The Linux method is presented first and more succinctly. The rest of the documentation uses cross-platform tools (openssl, Azure CLI, kubectl) and does not show a strong overall Windows bias, but the Windows section is more elaborate and could be perceived as prioritized.
Recommendations
- Provide equally detailed instructions for Linux base64 decoding and header removal, such as using 'sed' or 'awk', to match the Windows guidance.
- Consider grouping the base64 encoding instructions together, clearly labeling them as 'Linux' and 'Windows' alternatives, to avoid implying priority.
- Add a note that both Linux and Windows users can use OpenSSL and Azure CLI, and clarify any platform-specific differences where relevant.
- If possible, provide PowerShell examples for certificate handling alongside bash equivalents, or vice versa, to ensure parity.
- Review future documentation for similar patterns where Windows tools are given more space or detail than Linux equivalents.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides environment variable examples for Windows (CMD), PowerShell, and Linux/macOS, but consistently lists Windows and PowerShell examples before Linux/macOS. This ordering may subtly reinforce a Windows-centric perspective. Additionally, the automation section mentions Windows Task Scheduler before Linux cron, and script file extensions for Windows (.cmd, .bat, .ps1) are listed alongside Linux/Mac (.sh), but Windows tools are mentioned first. All CLI commands are cross-platform (Azure CLI, kubectl), and Linux examples are present, but the overall structure and ordering favor Windows.
Recommendations
- Alternate the order of platform examples so that Linux/macOS is sometimes listed first.
- Provide equal emphasis to Linux automation tools (cron) before or alongside Windows Task Scheduler.
- Explicitly state that all CLI commands work on Linux, macOS, and Windows at the beginning of the page.
- Consider grouping platform-specific instructions together or using tabs that default to the user's OS if possible.
- Add more Linux-specific tips or troubleshooting notes where relevant.
Azure Arc
Azure Arc-enabled data services validation
...lob/main/articles/azure-arc/data/validation-program.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page shows mild Windows bias. Several partner solutions (DataON, Dell, Hitachi UCP with AKS-HCI, Lenovo ThinkAgile MX) are Windows-centric or reference Microsoft AKS-HCI, which is a Windows-focused Kubernetes distribution. In the prerequisites, Azure Data Studio is mentioned, which is historically Windows-first (though now cross-platform), and the Azure Data CLI ('azdata') is referenced without explicit mention of Linux installation or usage. There are no explicit Linux/Powershell command examples, but the partner list and tool references tend to prioritize or exclusively mention Windows-oriented solutions before Linux-native ones.
Recommendations
- Add explicit Linux installation and usage instructions for Azure Data CLI ('azdata') and Azure Data Studio, including links to Linux-specific documentation.
- Balance partner solution listings by highlighting Linux-native distributions (e.g., OpenShift, Kublr, Wind River) earlier or more prominently.
- Include examples or notes for both Windows and Linux environments when discussing prerequisites and tooling.
- Clarify cross-platform compatibility for all listed tools, especially where Windows-centric solutions (AKS-HCI, Azure Data Studio) are mentioned.
- Consider adding a table or section that summarizes Linux-native solutions and their validation status.
Azure Arc
Upload billing data to Azure and view it in the Azure portal
.../articles/azure-arc/data/view-billing-data-in-azure.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively referencing Windows-centric tools (Excel) for viewing downloaded billing data and omitting any Linux-specific instructions or examples. There are no references to Linux tools or command-line patterns for handling CSV files, nor are there examples using cross-platform or Linux-native utilities.
Recommendations
- Include examples of how to view and process downloaded CSV files using Linux tools such as LibreOffice Calc, csvkit, or command-line utilities like awk, grep, and cut.
- Mention cross-platform editors (e.g., VS Code) for opening CSV files.
- Provide sample shell commands for filtering and analyzing billing data on Linux.
- Clarify that the download location may differ on Linux systems and provide instructions for locating downloaded files.
- Ensure that any automation or scripting references include both PowerShell and Bash examples.
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation mentions both Linux and Windows automation tools for scheduling uploads (cron and Windows Task Scheduler), but Windows tools are listed first. Script file extensions for both platforms are referenced, but Linux shell scripting is given as the main example. There are no PowerShell or Windows CMD/BAT script examples, nor are there exclusive references to Windows-only commands or patterns. However, the mention of Windows Task Scheduler before Linux cron and the inclusion of Windows script extensions (.cmd, .bat, .ps1) alongside Linux (.sh) suggest a slight Windows-first bias.
Recommendations
- List Linux automation tools (cron) before Windows Task Scheduler to avoid Windows-first ordering.
- Provide explicit examples for Windows automation (e.g., a PowerShell or CMD script for scheduled uploads) to match the Linux shell script example.
- Clarify cross-platform instructions by separating Linux and Windows steps, ensuring parity in detail and examples.
- Consider referencing platform-agnostic orchestration tools (e.g., Ansible, Puppet, Chef) before platform-specific schedulers.
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows-first bias by exclusively referencing the Azure portal (a web UI typically accessed from Windows environments) and Azure Managed Grafana for metric visualization, without providing any Linux-native or command-line examples (such as Bash, kubectl, or Linux monitoring tools). There are no PowerShell-specific instructions, but the absence of Linux CLI or tool references means Linux users may not find direct guidance for their workflows.
Recommendations
- Add Linux CLI examples using tools like kubectl, az CLI, or Bash scripts to retrieve and visualize Edge RAG metrics.
- Include instructions for accessing metrics via Prometheus or Grafana running on Linux, not just Azure Managed Grafana.
- Provide parity by showing how to monitor Edge RAG metrics from a Linux terminal, including sample queries and commands.
- Mention Linux-native monitoring tools (e.g., top, htop, netdata) where appropriate, or clarify how Azure Monitor integrates with Linux environments.
- Ensure screenshots and walkthroughs are not exclusively tied to the Azure portal UI; consider adding text-based alternatives.
Azure Arc
Customer intent: "As a system administrator managing Azure Arc-enabled servers, I want to query and analyze the installation status of databases such as SQL Server, PostgreSQL, or MySQL, so that I can ensure compliance and optimize resource allocation."
...ticles/azure-arc/includes/azure-arc-enabled-servers.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal for each query. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows and is listed as a main example for each scenario. There are no Linux-specific shell (e.g., Bash) or scripting examples, nor is there mention of Linux-native tools or patterns. The documentation does not explicitly favor Windows-only tools, but the presence of PowerShell as a primary example and the lack of Linux shell examples indicate a subtle Windows bias.
Recommendations
- Add explicit Bash or shell script examples for each query to demonstrate Linux parity.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and highlight any OS-specific considerations.
- Consider including notes or examples for using the queries in Linux automation contexts (e.g., cron jobs, shell pipelines).
- If PowerShell is shown, also show equivalent Bash or shell scripting usage for cross-platform audiences.
- Mention any differences in agent installation, query output, or extension management between Windows and Linux Arc-enabled servers, if applicable.
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
missing_linux_example
Summary
The documentation page exhibits Windows bias primarily in the 'Connect to the developer portal' section, where instructions for editing the hosts file are provided exclusively for Windows (using Notepad and the C:\windows\System32\drivers\etc\hosts path). There are no equivalent instructions for Linux or macOS users, nor is there mention of alternative text editors or file paths. Throughout the rest of the document, command-line examples use Azure CLI and kubectl, which are cross-platform, and do not show a strong bias toward Windows or PowerShell. However, the explicit mention of 'Switch to PowerShell' in Azure Cloud Shell may suggest a slight preference for Windows environments.
Recommendations
- Add instructions for editing the hosts file on Linux (e.g., using sudo nano /etc/hosts) and macOS (e.g., using sudo vi /etc/hosts).
- Mention the default hosts file paths for Linux (/etc/hosts) and macOS (/etc/hosts) alongside the Windows path.
- Suggest cross-platform text editors (nano, vi, etc.) in addition to Notepad.
- Clarify that all CLI commands work on Linux, macOS, and Windows, and provide any OS-specific notes if necessary.
- If referencing Azure Cloud Shell, note that both Bash and PowerShell are available, and users can choose either based on their preference.
Azure Arc
Use private connectivity for Azure Arc-enabled Kubernetes clusters with private link (preview)
...lob/main/articles/azure-arc/kubernetes/private-link.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively using Azure Portal (GUI) and Azure CLI examples, with no mention of Linux-specific tools or command-line patterns outside of Azure CLI. There are no PowerShell examples, but the instructions and screenshots are focused on the Azure Portal, which is most commonly used on Windows. There is no reference to Linux-native tools (such as curl, dig, or Linux firewall configuration), nor are there examples of configuring DNS or firewall rules using Linux commands. The troubleshooting section uses nslookup, which is available on both Windows and Linux, but does not mention alternatives like dig or provide Linux-specific guidance.
Recommendations
- Add Linux-specific command-line examples for DNS configuration and troubleshooting (e.g., using dig, systemd-resolved, or BIND).
- Include instructions for configuring firewalls on Linux (e.g., using iptables, nftables, or ufw) alongside references to Azure NSG and Windows firewalls.
- Provide guidance for managing DNS forwarding and records on common Linux DNS servers (such as BIND or dnsmasq), not just generic 'consult your vendor' advice.
- Clarify that Azure CLI is cross-platform and provide installation instructions for Linux users.
- Include screenshots or walkthroughs for Linux environments where relevant, especially for on-premises steps.
Azure Arc
Add a public cloud with the multicloud connector in the Azure portal
...les/azure-arc/multicloud-connector/add-public-cloud.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page presents steps for connecting AWS and GCP to Azure using the Azure portal, with template-based onboarding. While the page is generally cloud-agnostic, there is subtle Windows bias: when describing how to run Terraform for GCP onboarding, it mentions Azure Cloud Shell and local execution but does not provide explicit Linux CLI examples or mention Linux-specific tools. Additionally, the order of instructions and examples tends to present Windows/Azure-centric workflows first (e.g., Azure portal, Azure Cloud Shell), with Linux alternatives only implied or omitted.
Recommendations
- Explicitly provide Linux CLI examples for running Terraform and interacting with GCP, including commands for common Linux shells (bash, zsh).
- Mention Linux-native tools (e.g., gcloud CLI on Linux, Linux Cloud Shell) alongside Azure Cloud Shell and Windows tools.
- Ensure parity by listing Linux and Windows options together when discussing where and how to execute onboarding steps.
- Add troubleshooting or FAQ sections for Linux-specific issues that may arise during onboarding.
- Clarify that all steps can be performed from Linux environments, not just Azure Cloud Shell or Windows.
Azure Arc
Azure Arc resource bridge system requirements
...icles/azure-arc/resource-bridge/system-requirements.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page for Azure Arc resource bridge system requirements exhibits Windows bias by referencing Azure CLI installation instructions specifically for Windows (with a direct link to the Windows install page), and by omitting explicit Linux or macOS management machine requirements or examples. There are no Linux-specific instructions, examples, or parity checks for CLI installation, usage, or environment setup, despite Azure CLI being cross-platform.
Recommendations
- Include explicit instructions and links for installing Azure CLI on Linux and macOS alongside Windows.
- Clarify that the management machine can be Windows, Linux, or macOS, and provide minimum requirements for each OS.
- Provide example deployment commands and file paths for Linux/macOS environments (e.g., default CLI directory locations, file permissions).
- Mention any OS-specific considerations (such as SSH client availability, firewall configuration, or package dependencies) for Linux and macOS.
- Ensure all CLI commands and configuration steps are validated and documented for Linux and macOS, not just Windows.
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 is heavily focused on Windows Server 2012 scenarios and does not provide any Linux-specific examples or mention Linux equivalents for license management. All examples, parameters, and instructions are tailored to Windows environments, with no guidance for Linux systems or workloads.
Recommendations
- Add explicit examples for Linux machines, such as provisioning and managing ESU licenses for Linux servers if supported.
- Clarify whether the APIs and Azure CLI commands can be used for Linux workloads, and if so, provide relevant parameter values and scenarios.
- Include Linux-specific notes or sections to address cross-platform usage, even if the feature is Windows-only, to inform users of platform limitations.
- If the feature is not available for Linux, state this clearly at the beginning of the documentation to avoid confusion.
Azure Arc
CLI reference for `azcmagent extension`
...main/articles/azure-arc/servers/azcmagent-extension.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
Summary
The documentation demonstrates a Windows-first 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 the example. Windows tools and patterns are mentioned first and more prominently, while Linux examples and extension names are less visible.
Recommendations
- Alternate the order of Windows and Linux commands when describing service management (e.g., list systemctl before Stop-Service in some places).
- Provide Linux-specific extension examples (e.g., use an extension name relevant to Linux in the remove example).
- Explicitly state cross-platform applicability in examples and usage notes.
- Include a table or section summarizing both Windows and Linux commands for common operations.
- Ensure that extension names and scenarios are balanced between Windows and Linux environments.
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
Medium 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 and examples tailored to Windows environments. There are no references to Linux servers, Linux-based Azure Arc scenarios, or Linux-specific endpoints, tools, or patterns. The documentation assumes the reader is managing Windows workloads, omitting Linux parity and guidance.
Recommendations
- Include equivalent guidance for Linux servers managed by Azure Arc, specifying required endpoints for Extended Security Updates (if applicable).
- Add examples and notes for Linux installation/update processes, including package sources, certificate handling, and extension management.
- Clarify whether Extended Security Updates via Azure Arc are available for Linux workloads, and if not, explicitly state this to avoid confusion.
- If Linux is not supported for ESU in this scenario, provide links or references to general Azure Arc Linux documentation for completeness.
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 page describes organizing and inventorying servers using Azure Arc, hierarchies, tagging, and reporting. While it mentions support for both Windows and Linux, all examples and tool references (Azure CLI, PowerShell, ARM templates) are generic or Windows-centric, with no Linux-specific examples, commands, or considerations. The documentation implicitly assumes Windows environments by referencing tools and patterns more common to Windows administrators, and does not provide parity for Linux users in terms of examples or operational guidance.
Recommendations
- Add explicit Linux-specific examples for tagging, querying, and reporting (e.g., using Bash with Azure CLI, Linux shell scripts, or integration with Linux-native tools).
- Include sample commands for both Windows (PowerShell) and Linux (Bash) when demonstrating Azure CLI or other tool usage.
- Highlight any differences or considerations for Linux servers when onboarding to Azure Arc, tagging, or reporting.
- Reference Linux-native management tools or patterns where appropriate, and provide guidance for integrating them with Azure Arc.
- Ensure that screenshots, diagrams, and sample outputs reflect both Windows and Linux environments.
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
Summary
The documentation generally presents Windows paths and group names before their Linux equivalents, and references Windows-specific concepts (e.g., 'local administrators', 'C:\ProgramData', 'Hybrid agent extension applications') prior to or more prominently than Linux ones. There are no Linux-specific command examples or tool references, and the structure tends to favor Windows terminology and patterns.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side for parity.
- Include Linux-specific command-line examples (e.g., using 'ls', 'chmod', 'chown') where relevant.
- Reference Linux group names and file paths with equal prominence to Windows equivalents.
- Add guidance for managing permissions and access control on Linux systems, not just referencing Windows ACLs.
- Ensure screenshots and walkthroughs include Linux scenarios where applicable.
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
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents Windows onboarding instructions before Linux, and provides explicit PowerShell usage for Windows, while Linux instructions are more generic. Windows-specific tooling (PowerShell) is mentioned by name, whereas Linux instructions do not specify shell or package manager details. Both platforms are covered, but Windows is given primacy and more detailed command context.
Recommendations
- Alternate the order of Windows and Linux instructions or present them in parallel to avoid implicit prioritization.
- Provide equally detailed Linux instructions, specifying the shell (e.g., Bash) and mentioning common package managers (apt, yum, zypper) where relevant.
- Include example output or troubleshooting steps for Linux similar to those for Windows.
- Explicitly mention that both Windows and Linux scripts are generated and clarify any differences in script usage or prerequisites.
- Where PowerShell is referenced for Windows, mention the equivalent shell (Bash) for Linux and provide parity in command specificity.
Azure Arc
Extensions security for Azure Arc-enabled servers
...main/articles/azure-arc/servers/security-extensions.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation generally maintains parity between Windows and Linux, but Windows examples and terminology are often presented first, and PowerShell commands are highlighted for Windows while Bash is used for Linux. In some sections, Windows tools and scenarios are described before their Linux equivalents, and links to PowerShell documentation precede CLI references. However, most examples are provided for both platforms, and Linux is not omitted.
Recommendations
- Alternate the order of Windows and Linux examples to avoid consistently prioritizing Windows.
- Present CLI and Bash examples before or alongside PowerShell examples, especially in cross-platform contexts.
- Ensure links to CLI and Linux documentation are given equal prominence as PowerShell and Windows links.
- Explicitly state platform parity in introductory sections to reinforce equal support.
- Where possible, use platform-neutral language and avoid referring to Windows-specific tools or scenarios before their Linux equivalents.
Azure Arc
Enable SCVMM inventory resources in Azure Arc center
...al-machine-manager/enable-scvmm-inventory-resources.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is focused exclusively on SCVMM (System Center Virtual Machine Manager), a Windows-centric management tool, and provides instructions only for managing SCVMM resources via the Azure portal. There are no references to Linux-based virtualization platforms, nor are there any examples or guidance for users managing Linux environments or using Linux tools.
Recommendations
- Include references or links to equivalent Azure Arc onboarding processes for Linux-based virtualization platforms (e.g., KVM, oVirt, Proxmox).
- Provide examples or documentation for managing Linux VMs and resources in Azure Arc, ensuring parity in instructions and screenshots.
- Clearly state the Windows/SCVMM scope in the introduction and suggest alternative documentation for Linux users.
- If possible, add a comparison table highlighting supported features and onboarding steps for both Windows (SCVMM) and Linux virtualization environments.
Azure Arc
Perform ongoing maintenance and administration for Azure Arc-enabled System Center Virtual Machine Manager
...center-virtual-machine-manager/administer-arc-scvmm.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Azure portal GUI steps and Azure CLI commands, without mentioning or providing examples for Linux-specific workflows, shell environments, or tools. There is no reference to PowerShell, but the absence of Linux command-line examples (e.g., bash, SSH usage details, Linux file paths) and the use of Windows-centric terminology (e.g., 'workstation', 'current CLI directory') suggest a Windows-first perspective. No Linux-specific troubleshooting, credential management, or log collection patterns are discussed.
Recommendations
- Add explicit Linux shell (bash) examples for all CLI commands, including notes on file path differences and environment setup.
- Clarify that Azure CLI commands work cross-platform and provide guidance for Linux users (e.g., installing Azure CLI on Linux, using SSH from Linux, storing kubeconfig in Linux home directories).
- Include screenshots or instructions for Linux desktop environments where GUI steps are referenced.
- Mention Linux-specific troubleshooting steps, such as using journalctl or systemd for log collection on the resource bridge VM.
- Ensure terminology is platform-neutral (e.g., use 'machine' or 'host' instead of 'workstation', specify both Windows and Linux locations for configuration files).
Azure Arc
Azure built-in roles for Azure Arc-enabled SCVMM
...ystem-center-virtual-machine-manager/built-in-roles.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is focused exclusively on Azure Arc-enabled SCVMM, which is a Windows-centric technology (System Center Virtual Machine Manager). All roles and permissions described are for managing SCVMM resources, with no mention of Linux equivalents, Linux-based management tools, or cross-platform scenarios. There are no examples, references, or guidance for Linux environments or tools. The documentation assumes a Windows infrastructure and does not address Linux users or administrators.
Recommendations
- Add context or guidance for users managing hybrid environments, including Linux hosts managed via Azure Arc.
- Include references or links to Azure Arc documentation for Linux servers and VMs, highlighting role definitions and permissions for Linux resources.
- Provide examples or scenarios where Linux resources are managed alongside SCVMM, and clarify role differences or similarities.
- Explicitly state the Windows-only scope of SCVMM and direct Linux users to relevant Azure Arc documentation.
- If possible, add a section comparing SCVMM roles with those available for Linux-based Azure Arc resources, to help users understand cross-platform role management.
Azure Arc
Terraform based SCVMM VM management
...ter-virtual-machine-manager/terraform-vm-management.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exhibits Windows bias primarily through its exclusive focus on SCVMM (a Windows-centric virtualization manager) and the use of Windows-specific conventions (e.g., 'Administrator' username, domain/workgroup references) in examples. There are no Linux-specific instructions, examples, or considerations, and all sample Terraform configurations assume Windows VM patterns. The documentation does not mention Linux VMs, Linux authentication, or Linux-specific provisioning steps, nor does it provide parity for Linux users in terms of examples or troubleshooting.
Recommendations
- Add explicit examples for managing Linux-based VMs via SCVMM, including sample variables.tf, tfvars, and main.tf files with Linux conventions (e.g., 'root' or other Linux usernames, SSH key authentication, Linux OS profile settings).
- Include notes or sections describing differences in provisioning Linux VMs versus Windows VMs, such as initialization scripts, agent installation, and credential management.
- Provide troubleshooting tips or best practices for Linux VM lifecycle management in SCVMM environments.
- Ensure that prerequisites and steps are inclusive of both Windows and Linux workstation environments (e.g., mention that Terraform can be installed and used on Linux, macOS, and Windows).
- Where domain or workgroup settings are referenced, clarify their applicability or alternatives for Linux VMs.
Azure Arc
Create a virtual machine on VMware vSphere using Azure Arc
...les/azure-arc/vmware-vsphere/create-virtual-machine.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page primarily describes VM creation via the Azure portal with generic steps, but in the 'Administrator account' section, it defaults to username/password authentication (typical for Windows) and only mentions Linux/SSH as an alternative. No Linux-specific examples, screenshots, or guidance are provided, and Windows patterns are implicitly prioritized.
Recommendations
- Provide explicit Linux VM creation examples, including screenshots showing SSH key authentication.
- Clarify Linux-specific steps, such as cloud-init support, SSH configuration, and post-deployment access.
- Mention Linux guest customization options in the 'Advanced' section, such as script injection or OS-specific settings.
- Balance authentication guidance by presenting SSH key as a primary method for Linux VMs, not just as an alternative.
- Include references to Linux management tools or patterns where relevant (e.g., package updates, monitoring agents).
Azure Arc
Create a virtual machine on VMware vCenter using Infrastructure as Code methods
...es/azure-arc/vmware-vsphere/quick-start-create-a-vm.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exhibits a Windows bias by exclusively using Windows-centric examples and patterns, such as 'Administrator' as the VM username, and VM templates named with 'win22'. There are no examples or references to Linux VM templates, Linux usernames, or Linux-specific provisioning steps. The documentation does not mention Linux tools, patterns, or provide Linux-focused sample values, making it less accessible for users intending to deploy Linux VMs.
Recommendations
- Add Linux VM template examples alongside Windows examples (e.g., use a template named 'contoso-template-ubuntu20' or similar).
- Provide sample variable values for Linux VMs, such as 'vm_username = "ubuntu"' or 'vm_username = "root"'.
- Include notes or sections that describe differences in provisioning Linux VMs, such as SSH key usage instead of passwords.
- Explicitly mention Linux compatibility and provide guidance for Linux-specific configuration (e.g., cloud-init, SSH setup).
- Ensure that both Windows and Linux scenarios are covered equally in code samples and explanations.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation consistently provides both Bash and PowerShell examples for all CLI commands, but PowerShell (Windows) examples are always presented immediately after Bash, and sometimes with slightly more detail. There is no evidence of exclusive Windows tools or patterns, but the presence of PowerShell examples throughout the page may signal a slight Windows bias, especially as Linux-specific shell environments (e.g., zsh, fish) are not mentioned, nor are native Linux tools beyond Bash. The Azure portal instructions are platform-neutral, but the CLI instructions focus only on Bash and PowerShell, omitting other Linux shells or macOS-specific considerations.
Recommendations
- Add explicit mention that Bash examples apply to Linux and macOS environments, and clarify any differences if present.
- Consider including examples for other popular Linux shells (e.g., zsh) or note that Bash commands are compatible.
- Ensure parity in detail and explanation between Bash and PowerShell sections.
- If platform-specific issues exist (e.g., file path formats, authentication differences), call them out in notes.
- Add a brief section on running Azure CLI commands on macOS and Linux, including installation and environment setup tips.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for setting up workload orchestration, but the PowerShell section is given equal prominence and detail as Bash, despite PowerShell being primarily a Windows tool. There is no explicit mention of Linux-specific tools, nor are Linux-native patterns (such as shell scripting, environment variables, or file system conventions) discussed. The documentation does not clarify which examples are recommended for Linux users, nor does it address differences in environment setup or command syntax between Windows and Linux platforms.
Recommendations
- Clearly indicate which examples are intended for Linux and which for Windows, and recommend Bash for Linux users and PowerShell for Windows users.
- Provide Linux-specific guidance, such as using native Linux tools (e.g., jq, sed, grep) for JSON manipulation or file operations.
- Add notes about environment differences (e.g., file paths, environment variable syntax) between Windows and Linux.
- Ensure that Bash examples are comprehensive and do not assume familiarity with PowerShell.
- Consider adding troubleshooting tips for common issues encountered on Linux (e.g., permissions, shell compatibility).
Azure Arc
Create a Solution with Multiple Dependencies with Workload Orchestration
...quickstart-solution-multiple-shared-adapter-dependency.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation consistently provides both Bash and PowerShell examples side-by-side for every CLI operation. However, PowerShell is given equal prominence to Bash, which may suggest a Windows-centric approach, especially since PowerShell is primarily a Windows shell (though it is available cross-platform). There are no Linux-specific tools, patterns, or troubleshooting steps mentioned, nor are there any examples using native Linux utilities or shell scripting beyond Bash. No Linux-only workflows or considerations are discussed, and PowerShell examples are always present, which can imply a bias toward Windows environments.
Recommendations
- Clarify that PowerShell examples are intended for cross-platform PowerShell (pwsh), not Windows-only PowerShell, if applicable.
- Add explicit notes or sections for Linux-specific considerations, such as file permissions, environment setup, or troubleshooting common Linux issues.
- Include examples using native Linux utilities or shell scripting (e.g., using grep, awk, sed for output parsing) where relevant.
- Provide guidance for users working in Linux-only environments, such as using Bash exclusively or integrating with Linux package managers.
- Consider adding troubleshooting steps for common Linux deployment issues (e.g., SELinux, systemd, networking differences).
- If PowerShell is not required for Linux users, clarify that Bash is the recommended shell for Linux and macOS.
Azure Arc
Create a Solution with Shared Adapter Dependency with Workload Orchestration
...ation/quickstart-solution-shared-adapter-dependency.md
Medium 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 is always presented as a first-class citizen alongside Bash, rather than as a secondary or alternative option. In some cases, PowerShell examples are given equal prominence, which can be interpreted as a Windows bias, especially since Linux users typically use Bash and Windows users use PowerShell. There are no Linux-specific tools, patterns, or troubleshooting steps mentioned, and no explicit references to Linux environments or considerations. The documentation does not mention WSL, Linux file paths, or shell differences, and does not address potential issues that may arise when running these commands on Linux versus Windows. All CLI commands are cross-platform (Azure CLI), but the parity in examples does not extend to Linux-specific guidance.
Recommendations
- Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and clarify any OS-specific considerations.
- Provide troubleshooting tips for common Linux-specific issues (e.g., file permissions, path formats, environment variable syntax differences).
- Include Linux-specific notes where relevant, such as differences in shell behavior, quoting, or file handling.
- Consider adding a dedicated Linux section for advanced users, or at least a note about compatibility with Linux distributions.
- Mention that Bash examples are suitable for Linux/macOS, and PowerShell for Windows, to guide users to the correct tab for their OS.
- If possible, add examples using native Linux tools (e.g., jq for JSON parsing, curl for REST calls) where appropriate.
Azure Arc
Service Groups for Workload Orchestration
...cles/azure-arc/workload-orchestration/service-group.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation consistently presents both Bash and PowerShell examples for all command-line instructions, but PowerShell examples are always listed after Bash. However, the PowerShell examples are detailed and use Windows-specific scripting constructs (e.g., backticks for line continuation, PowerShell variables, and cmdlets like ConvertFrom-JSON, Select-Object, Set-Content), which are only relevant for Windows users. There is no evidence of exclusive use of Windows tools or missing Linux examples, as Bash instructions are provided throughout. The documentation does not mention Windows-specific tools or patterns before their Linux equivalents, but the PowerShell examples are more elaborate in some places, which may encourage a Windows-centric workflow for advanced scenarios.
Recommendations
- Ensure that Bash and PowerShell examples are equally detailed and cover advanced scenarios in both shells.
- Consider alternating the order of Bash and PowerShell tabs in different sections to avoid implicit prioritization.
- Add a brief note clarifying that both Bash and PowerShell examples are supported equally on Azure CLI, and that users should choose based on their environment.
- Where PowerShell-specific constructs are used (e.g., ConvertFrom-JSON, Set-Content), provide equivalent Bash alternatives (e.g., jq, cat/echo) to ensure Linux users have parity for complex tasks.
- Review all examples to ensure that neither shell is given more advanced or complete coverage than the other.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, but PowerShell examples are consistently presented after Bash, and the PowerShell examples use Windows-specific scripting conventions. There is no evidence of exclusive use of Windows tools or missing Linux examples, but the presence of PowerShell tabs and scripts throughout the page indicates a bias toward Windows users and workflows.
Recommendations
- Ensure Bash examples are fully tested and use idiomatic Linux shell scripting.
- Consider providing cross-platform notes for users running Bash on Windows (e.g., WSL, Git Bash) and PowerShell on Linux.
- Explicitly mention that all commands are supported on both Linux and Windows, and clarify any platform-specific caveats.
- Add troubleshooting tips for common issues on Linux environments (e.g., file permissions, path separators).
- If possible, include a generic CLI tab for commands that are identical across platforms, reducing duplication and emphasizing parity.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, but consistently lists PowerShell examples after Bash. However, the PowerShell examples are written in a way that assumes familiarity with Windows conventions (e.g., backtick line continuations, Windows-style paths), and there is no mention of Linux-specific tools or troubleshooting. The overall structure and language subtly prioritize Windows/PowerShell usage, and there is no explicit guidance for Linux users regarding environment setup, shell differences, or potential issues.
Recommendations
- Add explicit notes about Linux environment setup, including prerequisites such as Bash shell, package managers, and file path conventions.
- Provide troubleshooting tips for common Linux issues (e.g., file permissions, path separators, environment variables).
- Ensure that Bash examples use Linux-style paths and conventions throughout, and clarify any differences in command syntax or output between Bash and PowerShell.
- Consider adding a 'Linux-specific considerations' section to highlight any nuances or best practices for Linux users.
- Where relevant, mention Linux-native tools or alternatives (e.g., using jq for JSON manipulation, grep for searching output) alongside Azure CLI commands.
Azure Portal
Programmatically create Azure Dashboards
...tal/azure-portal-dashboards-create-programmatically.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page exhibits mild Windows bias. In several sections, Azure PowerShell is mentioned before Azure CLI, and PowerShell is listed as a primary deployment method alongside REST API and CLI. There are no explicit Linux shell examples, and PowerShell is referenced with dedicated links and instructions, while Linux-specific tooling or shell commands are not present. However, the page does mention Azure CLI, which is cross-platform, and includes links to both Linux and Windows VM creation guides in dashboard content.
Recommendations
- Ensure Azure CLI is mentioned before or alongside PowerShell when listing deployment methods, as CLI is cross-platform.
- Provide explicit Bash or Linux shell examples for template deployment, not just PowerShell.
- Add links to Linux-specific documentation (e.g., deploying with Bash, using Linux tools) where appropriate.
- Clarify that Azure CLI works on Windows, Linux, and macOS, and encourage its use for cross-platform scenarios.
- Balance references to PowerShell and CLI in instructions and examples to avoid implying PowerShell is the default or preferred method.
Azure Portal
Get subscription and tenant IDs in the Azure portal
...in/articles/azure-portal/get-subscription-tenant-id.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides both Azure PowerShell and Azure CLI options for programmatic access, but PowerShell is consistently mentioned first and given prominence. PowerShell is a Windows-centric tool, and its prioritization may suggest a Windows bias. No explicit Linux-only tools or patterns are mentioned, and examples do not highlight Linux-specific usage or shell environments.
Recommendations
- Alternate the order of PowerShell and CLI mentions, or mention Azure CLI first, as it is cross-platform and widely used on Linux.
- Include explicit examples or screenshots showing usage in Linux terminals (e.g., bash), and clarify that Azure CLI works on Linux, macOS, and Windows.
- Add notes or tips for Linux/macOS users, such as how to install and use Azure CLI in those environments.
- Avoid implying that copying to clipboard or pasting is a Windows-only workflow; mention equivalent actions in Linux/macOS.
- Consider referencing Bash scripts or other Linux-native automation approaches where relevant.
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 bias toward Windows by exclusively providing a VM creation example using a Windows image ('win2016datacenter') and referencing Windows-specific username and password requirements. There are no Linux VM examples, nor are Linux-specific requirements or images mentioned. The documentation does not offer parity for users who may prefer or require Linux-based VMs.
Recommendations
- Include a Linux VM creation example alongside the Windows example, using a popular image such as 'UbuntuLTS'.
- Add a note or section describing Linux username and password requirements, linking to the relevant Azure documentation.
- Ensure that dashboard template customization instructions reference both Windows and Linux VM names and resource types.
- Where possible, present Windows and Linux options together, or alternate which is shown first to avoid implicit prioritization.
Container Registry
Cross-Tenant Authentication from AKS to ACR
...es/container-registry/authenticate-aks-cross-tenant.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (web UI) and Azure CLI for configuration steps, without providing any Linux-specific or cross-platform command-line examples. There are no PowerShell commands, but the lack of Linux shell examples (e.g., Bash scripts, kubectl commands for updating secrets) and the absence of explicit Linux tool references means users on Linux are not directly supported. The instructions implicitly assume a Windows-centric workflow by prioritizing GUI and Azure CLI, which are commonly used on Windows.
Recommendations
- Add explicit Linux/Bash shell examples for key steps, such as updating AKS service principal credentials and assigning roles.
- Include kubectl commands for managing image pull secrets, showing how to use the service principal credentials in a Kubernetes-native way.
- Clarify that Azure CLI is cross-platform, and provide sample commands for both Windows (PowerShell) and Linux (Bash).
- Mention any OS-specific prerequisites or differences in authentication workflows.
- Ensure parity by providing step-by-step instructions for both GUI (Azure portal) and CLI workflows, with clear notes for Linux users.
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for importing images to Azure Container Registry, but PowerShell is given equal prominence and is described in detail, which may indicate a Windows bias. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-native tools or workflows. The documentation references Azure Cloud Shell, which is cross-platform, but does not provide explicit Linux command-line examples or mention Linux-specific considerations. The order of presentation (CLI first, then PowerShell) is neutral, but the inclusion of PowerShell as a primary tab and lack of Linux/Bash examples suggests a subtle Windows bias.
Recommendations
- Add explicit Bash/Linux shell examples for image import and registry management, especially for users working on Linux or macOS.
- Include references to Linux-native tools and workflows where appropriate (e.g., scripting with Bash, using curl or wget for registry interactions).
- Clarify that Azure CLI commands are cross-platform and provide usage notes for Linux/macOS environments.
- Consider adding a 'Linux shell' or 'macOS terminal' tab alongside CLI and PowerShell to demonstrate parity.
- Mention any Linux-specific authentication or networking considerations when accessing Azure Container Registry.
Container Registry
Kubernetes Pull Secret for ACR Authentication
...ntainer-registry/container-registry-auth-kubernetes.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation provides an example for resetting a service principal password using the Azure CLI, which is available on both Windows and Linux, but does not mention or show Linux-specific patterns or alternatives (such as using bash scripting or Linux credential management). There are no PowerShell-specific examples, but the lack of explicit Linux examples or references (e.g., using bash, Linux credential stores, or Linux-specific troubleshooting) may make the documentation feel slightly Windows-centric, especially for users unfamiliar with Azure CLI on Linux.
Recommendations
- Add explicit notes confirming Azure CLI commands work on Linux, macOS, and Windows.
- Include example commands using bash scripting for Linux users where appropriate.
- Mention installation and usage of Azure CLI on Linux, with links to relevant documentation.
- Provide troubleshooting tips or patterns for Linux environments (e.g., file permissions, environment variables).
- Ensure parity in references to credential management tools or shell environments (e.g., mention bash/zsh alongside PowerShell if referenced).
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
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major steps, but PowerShell is a Windows-centric tool and is presented as an equal alternative to Azure CLI, which is more cross-platform. There are no explicit Windows-only examples, but the prominence of PowerShell may suggest a bias toward Windows users. However, all VM and Docker instructions use Ubuntu (Linux), and Linux-specific commands (apt, ssh) are shown. The documentation does not provide Linux shell alternatives for PowerShell commands, nor does it mention Linux-native tools (e.g., Bash scripts) for Azure resource management. The order of presentation is mostly Azure CLI first, but PowerShell is always present and emphasized.
Recommendations
- Clarify that PowerShell is available cross-platform, but Azure CLI is generally preferred for Linux users.
- Add Bash script equivalents for Azure resource management steps, especially for users who may not want to install PowerShell.
- Consider reducing the prominence of PowerShell in Linux-focused scenarios, or provide guidance on when to use CLI vs. PowerShell.
- Explicitly mention that all steps can be performed on Linux without requiring Windows tools.
- If possible, add a section comparing Azure CLI and PowerShell for Linux users, highlighting pros and cons.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias by using Windows-style environment variable setting (set ACR_NAME=<container-registry-name>) without providing the equivalent Linux/macOS syntax (export ACR_NAME=...), and by listing Azure PowerShell as an option before the Azure portal for creating AKS clusters. All command-line examples use generic 'console' or 'azurecli' blocks, which are mostly cross-platform, but the omission of Linux/macOS-specific instructions for environment variables and authentication may hinder parity.
Recommendations
- Provide both Windows (set VAR=...) and Linux/macOS (export VAR=...) syntax when instructing users to set environment variables.
- Explicitly state that all CLI commands are cross-platform and clarify any OS-specific differences.
- When listing options for creating resources (e.g., AKS clusters), alternate or balance the order between Windows (PowerShell) and Linux/macOS (CLI, portal) tools.
- Add a note or section highlighting any OS-specific prerequisites or considerations, especially for authentication and scripting.
- Review all examples to ensure Linux/macOS users are equally supported, especially in sections where Windows conventions are used.
Container Registry
Verify Container Images in GitHub Workflows with Notation and Trusted Signing
...gistry-tutorial-github-verify-notation-trusted-signing.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Linux (bash) and Windows (PowerShell) examples for all CLI commands, but Windows/PowerShell examples are always presented immediately after Linux, and sometimes with more explanation (e.g., directory creation). There is a slight Windows-first bias in the structure and detail of examples, and PowerShell is used as the exclusive Windows shell, with no mention of alternatives like Git Bash or WSL. No Linux example is missing, but Windows tools and patterns (PowerShell, Invoke-WebRequest, New-Item) are consistently highlighted.
Recommendations
- Alternate the order of Linux and Windows examples, or present them side-by-side to avoid implicit prioritization.
- Add brief notes about using Git Bash, WSL, or other shells on Windows for parity.
- Ensure explanations and comments are equally detailed for both platforms.
- Consider providing a generic cross-platform script example (e.g., using Node.js, Python, or a workflow step) where possible.
- Explicitly state that all steps are supported on both platforms and clarify any platform-specific caveats.
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
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but the PowerShell example is given equal prominence as the CLI example, which can be interpreted as a Windows bias since PowerShell is primarily a Windows tool (despite cross-platform support). There are no explicit Linux shell (bash) examples or notes about running the CLI on Linux, and the PowerShell example appears before the portal instructions, which may reinforce a Windows-centric workflow.
Recommendations
- Add explicit bash/Linux shell examples for the Azure CLI, showing usage in a typical Linux terminal.
- Clarify that the Azure CLI commands work identically on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
- Consider reordering the examples to present the Azure CLI (which is cross-platform) before PowerShell, or provide a clear note about PowerShell's cross-platform availability.
- Include a table or section summarizing command usage across different platforms (Windows, Linux, macOS) to reinforce parity.
- If PowerShell is included, mention PowerShell Core and its availability on Linux/macOS to reduce the perception of Windows-only tooling.
Container Registry
Quickstart- Manage Container Registry Content with Azure Client Libraries
...cles/container-registry/quickstart-client-libraries.md
Medium 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 Portal and Azure PowerShell) are mentioned before the cross-platform Azure CLI for creating a container registry. The installation example for .NET uses PowerShell syntax, which is Windows-specific, rather than a cross-platform shell. However, the main client library usage examples for all languages are platform-neutral, and Linux tools (Docker CLI) are referenced for pushing images. No explicit Linux examples or Linux-first instructions are present.
Recommendations
- List Azure CLI as the first option for creating a container registry, as it is cross-platform and widely used on Linux.
- Provide installation instructions for .NET using both PowerShell and Bash (e.g., 'dotnet add package ...' in Bash), or use a generic command line format.
- Explicitly mention Linux and macOS compatibility in the prerequisites and installation sections.
- Include links or references to Linux-specific documentation or troubleshooting guides.
- Ensure that any tool or command mentioned (e.g., PowerShell) is accompanied by its Linux/macOS equivalent where applicable.
Container Registry
Quickstart: Deploying the Connected Registry Arc Extension
...iner-registry/quickstart-connected-registry-arc-cli.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but the PowerShell example is given equal prominence and is not clearly marked as Windows-specific. The documentation does not exclusively use Windows tools or patterns, but it does present PowerShell as a primary option alongside Bash, which may suggest a slight Windows bias. There are no examples that use Linux-specific tools beyond Bash, and no explicit mention of Linux environments or parity considerations. The Azure CLI commands are cross-platform, but the inclusion of PowerShell examples without clear context may imply Windows-first thinking.
Recommendations
- Clearly label PowerShell examples as Windows-specific and Bash examples as Linux/macOS-specific.
- Provide guidance on which example to use based on the user's operating system.
- Consider including a note at the top of the page clarifying that Azure CLI commands work on Windows, Linux, and macOS, and that Bash examples are intended for Linux/macOS users.
- If PowerShell is included, ensure that Bash is presented first, or provide a parity check to confirm both environments are equally supported.
- Add troubleshooting or environment setup notes for Linux users where applicable.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides step-by-step instructions for removing delegations in Azure Lighthouse, with examples for both PowerShell and Azure CLI. However, the PowerShell example is presented before the Azure CLI example, and there is no mention of Linux-specific tools or shell environments. The use of PowerShell (which is traditionally associated with Windows) as the first example and lack of explicit Linux guidance may indicate a subtle Windows bias.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and commonly used on Linux.
- Explicitly mention that both PowerShell and Azure CLI are available on Linux, macOS, and Windows, and provide guidance for running commands in Bash or other Linux shells.
- Include screenshots or instructions for using the Azure portal on non-Windows platforms if relevant.
- Add notes or tips for Linux users, such as using Bash aliases or integrating with Linux automation tools.
- Ensure terminology and instructions do not assume a Windows environment (e.g., avoid references to Windows-specific shell behaviors or file paths).
Low Priority
View Details →
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide explicit examples or instructions tailored to either Windows or Linux environments. However, it lacks any mention of Linux-specific tools, commands, or patterns, and does not clarify whether the deployment steps (such as using the Azure CLI or configuring NFS) are cross-platform or require platform-specific considerations. This omission can disadvantage Linux users by not addressing their needs or potential issues.
Recommendations
- Add explicit instructions and examples for both Windows and Linux environments, especially for steps involving Azure CLI, NFS configuration, and driver machine setup.
- Clarify platform requirements and compatibility for the driver machine and management host (e.g., supported OS versions, prerequisites for Linux vs. Windows).
- Include troubleshooting tips for common Linux-specific issues (e.g., NFS permissions, firewall settings, CLI installation).
- Where relevant, provide both PowerShell and Bash command examples for deployment and configuration steps.
- Indicate whether the Azure portal and CLI instructions are identical for Linux and Windows, or note any differences.
Azure Arc
CLI reference for `azcmagent config`
...ob/main/articles/azure-arc/servers/azcmagent-config.md
Low Priority
View Details →
Detected Bias Types
missing_linux_example
Summary
The documentation provides command-line usage and examples for the azcmagent config tool, but all examples are generic and do not reference platform-specific shells, tools, or patterns. However, there is a lack of explicit Linux-specific examples, such as using bash or shell scripting, and no mention of Linux-specific configuration nuances or file paths. The only extension example references 'AzureMonitorWindowsAgent', which may suggest a Windows-centric scenario, but otherwise, the documentation is mostly neutral.
Recommendations
- Add explicit Linux shell examples (e.g., bash, sh) where relevant, such as showing command usage in a Linux terminal.
- Include examples or notes about Linux-specific configuration properties, file paths, or environment variables if they differ from Windows.
- Provide extension allowlist examples that include Linux agents (e.g., 'Microsoft.Azure.Monitor/AzureMonitorLinuxAgent') to balance platform representation.
- Clarify that the commands are cross-platform and note any platform-specific behaviors or requirements.
Azure Arc
CLI reference for `azcmagent genkey`
...ob/main/articles/azure-arc/servers/azcmagent-genkey.md
Low Priority
View Details →
Detected Bias Types
missing_linux_example
Summary
The documentation provides a generic CLI example without specifying platform-specific usage. However, it lacks any mention of Linux-specific considerations, shell environments, or examples, which may implicitly favor Windows users by omission.
Recommendations
- Add explicit examples for both Windows (PowerShell/CMD) and Linux (bash/sh) environments to demonstrate cross-platform usage.
- Mention any platform-specific prerequisites or behaviors, such as file permissions or path formats.
- Clarify that the command works identically on both Windows and Linux, or note any differences if they exist.
- Include troubleshooting tips for common issues on Linux systems (e.g., permission denied, missing dependencies).
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides installation path information for both Windows and Linux, but lists the Windows path first and includes additional detail about PATH variable updates for Windows only. There are no command usage examples specific to either platform, and no PowerShell-specific examples or Windows-only tools are mentioned. However, the ordering and extra detail for Windows installation may indicate a subtle Windows-first bias.
Recommendations
- List Linux installation path before Windows, or present both paths in parallel to avoid perceived prioritization.
- Include details about Linux PATH management (e.g., mention if /opt/azcmagent/bin is added to PATH or if users need to update their shell configuration).
- Provide platform-specific troubleshooting tips for both Windows and Linux, ensuring parity in guidance.
- If referencing Azure PowerShell, also reference equivalent Linux-native tools or shell usage where applicable.
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. While both platforms are covered with equivalent Azure CLI commands, the ordering prioritizes Windows, which may subtly reinforce a Windows-centric perspective.
Recommendations
- Alternate the order of examples so that Linux is presented first in some sections, or present both examples side-by-side to avoid implicit prioritization.
- Explicitly state that the instructions apply equally to both Windows and Linux, and clarify any platform-specific differences.
- Ensure parity in detail and explanation for both Windows and Linux examples throughout the documentation.