756
Pages Scanned
198
Pages Flagged
756
Changed Pages
26.2%
% Pages Flagged
Scan Information
Started At: 2026-01-13 00:00:08
Finished At: 2026-01-13 05:14:07
Status: completed
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 756
Files Completed: 756
Problematic Pages
202 issues found
Azure Arc
Troubleshoot Azure Arc-enabled servers networking issues
.../articles/azure-arc/servers/troubleshoot-networking.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation focuses exclusively on troubleshooting TLS configuration issues for Windows servers. All examples, commands, and procedures use Windows-specific tools (PowerShell, Group Policy, Registry Editor), with no mention of Linux or macOS equivalents. There are no instructions or guidance for Linux-based Arc-enabled servers, leaving Linux users without actionable steps for similar networking issues.
Recommendations
- Add a dedicated section for troubleshooting TLS/cipher suite issues on Linux servers, including relevant commands (e.g., using openssl, update-crypto-policy, or editing configuration files like /etc/ssl/openssl.cnf).
- Provide cross-platform parity by including both Windows and Linux/macOS examples for checking and enabling cipher suites.
- Clarify which troubleshooting steps apply only to Windows and direct Linux/macOS users to appropriate resources or documentation.
- List Linux troubleshooting steps before or alongside Windows steps to avoid implicit prioritization.
Create Pull Request
Azure Arc
Recover from accidental deletion of resource bridge VM
...em-center-virtual-machine-manager/disaster-recovery.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation provides recovery instructions exclusively for Windows, using a downloadable PowerShell script. There are no examples, scripts, or guidance for Linux or macOS users, nor any mention of equivalent Linux tooling or steps. The section is explicitly titled 'Recover Arc resource bridge from a Windows machine', and no alternatives are offered.
Recommendations
- Provide equivalent recovery instructions for Linux/macOS, including a Bash or Python script.
- Clarify whether the recovery process is possible from non-Windows platforms, and if not, explain the limitation.
- If the PowerShell script is required, document how to run it on Linux/macOS (e.g., via PowerShell Core), or provide a cross-platform version.
- Add Linux/macOS-specific prerequisites and troubleshooting steps.
Azure Arc
Switch to the new version of Arc-enabled SCVMM
...ual-machine-manager/switch-to-the-new-version-scvmm.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily oriented towards Windows environments, referencing System Center Virtual Machine Manager (SCVMM), which is a Windows-only tool. All examples and instructions assume the use of Windows-based management servers and agents. References to agent management link only to Windows-specific instructions, with no mention of Linux or macOS equivalents or scenarios. There is no guidance for users managing Linux VMs or using non-Windows platforms.
Recommendations
- Clarify that SCVMM is a Windows-only tool and explicitly state platform limitations at the beginning.
- If Azure Arc supports Linux VMs or management from Linux/macOS, provide parallel instructions and examples for those platforms.
- Include links or references to Linux agent management documentation where applicable.
- Add notes or sections for users who may be managing mixed environments, outlining any differences or additional steps for Linux VMs.
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_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias by exclusively referencing Windows-specific tools (Active Directory Users and Computers MMC, PowerShell), providing only Windows-based examples and screenshots, and omitting any guidance for Linux or cross-platform environments. There are no instructions for performing equivalent tasks on Linux (e.g., using Samba, ldap-utils, or cross-platform AD management tools), nor is there mention of how to interact with AD from non-Windows systems.
Recommendations
- Add instructions and examples for managing Active Directory objects from Linux systems, such as using ldapadd, ldapmodify, or Samba tools.
- Include cross-platform PowerShell (PowerShell Core) examples and clarify any differences when running on Linux/macOS.
- Reference Azure Active Directory and hybrid scenarios where AD management may be performed from cloud or Linux-based environments.
- Provide links or guidance for setting up and managing AD from Linux, including open-source tools and best practices.
- Reorder examples so that cross-platform or Linux methods are presented alongside or before Windows-specific instructions.
Azure Arc
Configure Machine to Manage Arc-Enabled Kubernetes Cluster
...rticles/azure-arc/edge-rag/configure-driver-machine.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily biased towards Windows, providing only a PowerShell script and instructions for configuring a Windows machine. All examples, download links, and environment variable manipulations are Windows-specific, with no mention of Linux or macOS equivalents. Linux users are left without guidance or scripts to perform the same setup.
Recommendations
- Provide equivalent setup instructions and sample scripts for Linux/macOS, using Bash or shell scripting.
- Include download links for kubectl, Helm, and Azure CLI for Linux/macOS.
- Document environment variable and PATH updates for Linux/macOS (e.g., modifying ~/.bashrc or ~/.profile).
- Clearly state cross-platform requirements and offer parity in step-by-step instructions.
- Add a section or note indicating how Linux/macOS users can adapt the process.
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 provides only a Windows PowerShell script for enabling GPU on AKS via Azure Arc, relying heavily on Windows-specific cmdlets and tools (e.g., Get-PnpDevice, pnputil, Restart-Service). No Linux or cross-platform alternatives are mentioned, and the instructions assume a Windows environment throughout.
Recommendations
- Add equivalent instructions and sample scripts for Linux hosts, using bash and Linux-native tools (e.g., lspci, lsmod, modprobe, systemctl).
- Clarify OS requirements and explicitly state if the procedure is Windows-only, or provide guidance for Linux/macOS users.
- If Azure Arc supports Linux nodes, document the GPU enablement workflow for those platforms.
- Present examples for both Windows and Linux side-by-side, or indicate which steps are OS-specific.
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 options via Azure Arc, with all examples and scenarios centered on Windows environments. There is no mention of Linux licensing, Linux server management, or equivalent Linux tools. Windows-specific tools and patterns (e.g., Azure Update Manager, ESUs for Windows Server) are referenced throughout, and Windows scenarios are presented first and exclusively.
Recommendations
- Add sections or examples describing how Azure Arc licensing and cost management applies to Linux servers, including any differences or limitations.
- Include Linux-specific licensing scenarios, such as integration with RHEL, SUSE, or other commercial Linux distributions, and how pay-as-you-go or subscription models work for those platforms.
- Mention Linux-compatible update and patch management tools available via Azure Arc, and clarify whether similar centralized billing and compliance features exist for Linux workloads.
- Ensure that examples and guidance are balanced between Windows and Linux, or explicitly state if features are Windows-only.
Azure Arc
Customer intent: "As a system administrator managing Azure Arc-enabled servers, I want to understand the required endpoints for Extended Security Updates so that I can ensure proper connectivity and compliance during installation and updates."
...azure-arc/servers/includes/esu-network-requirements.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is focused exclusively on Windows Server 2012 and SQL Server 2012, with all endpoint descriptions referencing Windows installation packages and Extended Security Updates for Windows products. There are no examples, instructions, or endpoint references for Linux or macOS systems, nor any mention of Linux equivalents or considerations. The documentation implicitly assumes a Windows environment and does not address cross-platform scenarios.
Recommendations
- Clarify whether Extended Security Updates via Azure Arc are available for Linux servers, and if so, include relevant endpoints and instructions.
- If Linux is not supported, explicitly state this to avoid confusion for non-Windows users.
- If Linux support is planned, provide parity in documentation with Linux-specific examples, endpoints, and installation/update instructions.
- Consider adding a section or note about cross-platform applicability, including any limitations or differences for Linux/macOS users.
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
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily biased toward Windows environments. All examples, instructions, and screenshots are based on Windows tools (Configuration Manager, .msi installers, PowerShell scripts). There is no mention of Linux/macOS equivalents, nor guidance for deploying the Connected Machine Agent at scale on non-Windows platforms. The use of PowerShell and .msi files further excludes Linux users, and the workflow is entirely centered on Windows-specific deployment patterns.
Recommendations
- Add a dedicated section for Linux/macOS onboarding at scale, including supported automation tools (e.g., Ansible, shell scripts, Linux package managers).
- Provide examples for downloading and installing the Connected Machine Agent on Linux (e.g., using .deb/.rpm packages, wget/curl commands).
- Include sample task automation scripts for Linux (e.g., Bash, Python) and show how to connect to Azure Arc from Linux using azcmagent.
- Clarify whether Configuration Manager supports Linux/macOS endpoints for this scenario, or recommend alternative management solutions for non-Windows platforms.
- Present both Windows and Linux workflows side-by-side or in parallel sections to ensure parity.
Azure Arc
REST API Requests for the Run Command on Azure Arc-enabled Servers (Preview)
...ob/main/articles/azure-arc/servers/run-command-rest.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page is heavily biased towards Windows. All example scenarios, scripts, and references are specific to Windows Server (e.g., Windows Server 2012/R2, PowerShell cmdlets like New-NetFirewallRule). There are no examples or guidance for Linux or macOS servers, nor are Linux shell scripts or tools mentioned. Even instructions for generating SAS tokens reference PowerShell tools (New-AzStorageBlobSASToken) exclusively.
Recommendations
- Add example scenarios for Linux Arc-enabled servers, including REST API payloads with bash or shell scripts (e.g., using iptables or ufw for firewall rules).
- Explicitly mention Linux support in the introduction and prerequisites, clarifying any OS-specific limitations.
- Provide Linux/macOS equivalents for SAS token generation (e.g., using Azure CLI az storage blob generate-sas).
- Alternate examples between Windows and Linux, or present both side-by-side.
- Reference Linux documentation and tools in the 'Related content' section.
Azure Arc
How to troubleshoot delivery of Extended Security Updates for Windows Server 2012 through Azure Arc
...-arc/servers/troubleshoot-extended-security-updates.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation is exclusively focused on troubleshooting Extended Security Updates for Windows Server 2012 through Azure Arc, with all examples, commands, and instructions tailored to Windows environments. Only Windows Server operating systems are mentioned as eligible, and all troubleshooting steps (such as certificate installation and error resolution) use Windows-specific tools (certutil, PowerShell). No Linux or macOS equivalents, examples, or considerations are provided, and Windows terminology and tools are used throughout.
Recommendations
- Explicitly state that the process and troubleshooting steps are only applicable to Windows Server 2012/2012 R2, and clarify if Linux/macOS are not supported.
- If Linux or macOS Arc-enabled servers could be relevant, provide troubleshooting steps, eligibility criteria, and examples for those platforms.
- Where possible, mention cross-platform alternatives or note the absence of Linux/macOS support for ESU delivery.
- Add a section addressing common questions for non-Windows users (e.g., 'Can I use ESU with Linux Arc-enabled servers?').
Azure Arc
Azure built-in roles for Azure Arc-enabled SCVMM
...ystem-center-virtual-machine-manager/built-in-roles.md
High Priority
View Details →
Detected Bias Types
windows_tools
Summary
The documentation is focused on Azure Arc-enabled SCVMM, which is inherently a Windows-centric technology (System Center Virtual Machine Manager). All role definitions and permissions revolve around SCVMM resources and actions, which are only available on Windows. There are no examples, instructions, or references to Linux or macOS tools, nor is there any mention of how these roles or resources could be managed or accessed from non-Windows platforms.
Recommendations
- Explicitly state the Windows-only nature of SCVMM and its management tools at the top of the documentation.
- If any Azure Arc management tasks can be performed from Linux/macOS (e.g., via Azure CLI, REST API), provide examples or links.
- Clarify which aspects (if any) of Azure Arc-enabled SCVMM can be accessed or managed cross-platform.
- Add a section for Linux/macOS users explaining limitations and possible alternatives for managing virtual machines in hybrid environments.
Azure Arc
Enable SCVMM inventory resources in Azure Arc center
...al-machine-manager/enable-scvmm-inventory-resources.md
High 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-only management tool, and provides instructions only for enabling SCVMM resources in Azure via the Azure portal. There are no references to Linux or cross-platform alternatives, and all examples and screenshots are based on Windows-centric tools and workflows.
Recommendations
- Clarify early in the documentation that SCVMM is a Windows-only tool, and that these instructions are specific to environments using SCVMM.
- Provide links or references to equivalent workflows for Linux-based virtualization platforms (such as VMware vSphere, KVM, or Hyper-V on Linux) if supported by Azure Arc.
- If Azure Arc supports onboarding Linux VMs or resources, include a 'Linux and cross-platform resources' section with relevant instructions or links.
- Consider adding a comparison table showing supported platforms and management tools, highlighting where Linux users should look for guidance.
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-only virtualization management tool. All operational steps, terminology, and screenshots are based on Windows tools and Azure portal integration with SCVMM. There are no Linux or macOS equivalents, nor are alternative management patterns for non-Windows environments discussed.
Recommendations
- Clarify in the prerequisites and introduction that SCVMM is a Windows-only tool and that the instructions are not applicable to Linux-based virtualization platforms.
- Provide links or references to equivalent Azure Arc onboarding and VM management documentation for Linux-based hypervisors (e.g., KVM, VMware on Linux).
- If possible, include a comparison table or section outlining how similar CRUD and power cycle operations can be performed on Linux-managed VMs using Azure Arc.
- Explicitly state the platform limitations to help Linux/macOS users quickly determine applicability.
Azure Arc
Troubleshoot SCVMM-specific Azure Arc resource bridge deployment errors
...m-center-virtual-machine-manager/troubleshoot-scvmm.md
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation is heavily focused on troubleshooting errors specific to SCVMM (System Center Virtual Machine Manager), a Windows-only tool. All error codes and troubleshooting steps reference Windows technologies (e.g., PSSession, SCVMMServer), with no mention of Linux or macOS equivalents, nor any cross-platform guidance. There are no Linux/macOS examples or alternative instructions.
Recommendations
- Clarify early in the documentation that SCVMM is a Windows-only technology, and that the troubleshooting steps are relevant only for Windows environments.
- If Azure Arc resource bridge supports Linux-based resource managers, provide equivalent troubleshooting steps for those platforms.
- Where possible, include cross-platform notes or links to Linux/macOS troubleshooting guides for Azure Arc resource bridge.
- Explicitly state platform requirements and limitations to avoid confusion for non-Windows users.
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
windows_tools
missing_linux_example
Summary
The documentation is heavily oriented towards Windows environments, specifically SCVMM (System Center Virtual Machine Manager), and assumes the use of Windows servers and workstations. All examples and instructions reference Windows tools and patterns (e.g., VHDX, SCVMM server, Azure Portal), with no mention of Linux or macOS equivalents, nor guidance for users operating outside of Windows. There are no Linux/macOS-specific instructions or troubleshooting steps.
Recommendations
- Clarify platform requirements early in the document, explicitly stating if the upgrade process is only supported on Windows/SCVMM environments.
- If possible, provide instructions or notes for Linux/macOS users, such as how to use the Azure CLI and manage configuration files on those platforms.
- Include examples of commands run from Linux/macOS terminals, or specify any limitations for non-Windows users.
- Mention alternative virtualization formats (e.g., VHD, VMDK) or tools if supported, or clarify that only VHDX/SCVMM is supported.
- Add troubleshooting and prerequisite sections relevant to Linux/macOS environments if applicable.
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
powershell_heavy
windows_first
windows_tools
Summary
The documentation shows a notable Windows bias in the deboarding script section, where only Windows/PowerShell instructions are provided for running the cleanup script. The script is described as a PowerShell script, and all usage examples and troubleshooting notes are Windows/PowerShell-centric. There is no mention of how to run the script on Linux or macOS, nor are alternative instructions or parity examples given for non-Windows platforms. The agent uninstall instructions are well-balanced between Windows and Linux, but the critical deboarding step is Windows-only.
Recommendations
- Provide instructions for running the deboarding script on Linux/macOS, including prerequisites (e.g., PowerShell Core, Azure CLI) and any platform-specific steps.
- If the script is Windows-only, offer an equivalent Bash or cross-platform script, or document manual cleanup steps for Linux/macOS users.
- Clearly state platform requirements and limitations for the deboarding script at the start of the section.
- Add troubleshooting notes for Linux/macOS environments, similar to the PowerShell ISE note for Windows.
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
windows_tools
missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. All command-line examples and automation scripts are provided exclusively in PowerShell, with no Bash, shell, or Linux/macOS equivalents. File paths in JSON templates use Windows-style backslashes and drive letters (e.g., C:\, E:\), and script instructions reference PowerShell scripts (.ps1) only. There is no mention of how to perform these tasks on Linux or macOS, nor are alternative shell commands or cross-platform notes provided.
Recommendations
- Provide Bash or shell script equivalents for all PowerShell commands and scripts, especially for az CLI usage.
- Use platform-agnostic file path examples or show both Windows and Linux/macOS path formats.
- Explicitly note any platform requirements or limitations for provided scripts, and offer guidance for Linux/macOS users.
- Include instructions for running automation tasks on Linux/macOS, such as using shell scripts (.sh) or direct az CLI commands.
- Add cross-platform compatibility notes for JSON templates and configuration files.
Azure Arc
Onboarding Scripts for Workload Orchestration
...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily biased towards Windows, with all onboarding scripts and examples provided only in PowerShell (.ps1) format. Prerequisites use Windows-specific tools (winget), and there are no Bash, shell, or Linux/macOS equivalents or instructions. All example commands and instructions assume a Windows environment, making it difficult for Linux/macOS users to follow or execute the onboarding process without significant adaptation.
Recommendations
- Provide equivalent Bash/shell scripts for infra and cm onboarding, or document how to run the PowerShell scripts on Linux/macOS (e.g., via pwsh).
- Include Linux/macOS installation instructions for prerequisites (e.g., use apt, yum, brew for Azure CLI and kubectl, instead of winget).
- Offer examples and command syntax for both Windows (PowerShell) and Linux/macOS (Bash) side-by-side.
- Explicitly state cross-platform requirements and limitations, and link to guidance for running PowerShell scripts on non-Windows platforms.
- Clarify whether the scripts are compatible with PowerShell Core (pwsh) on Linux/macOS, and provide troubleshooting tips for non-Windows environments.
Azure Arc
Troubleshooting for Workload Orchestration
...es/azure-arc/workload-orchestration/troubleshooting.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The troubleshooting documentation for workload orchestration is heavily biased toward Windows and PowerShell usage. Most command-line examples (especially in critical troubleshooting sections) use PowerShell syntax and Windows-specific patterns, with little to no equivalent Bash or Linux shell examples. Windows tools and conventions (such as PowerShell variables, ConvertTo-Json, Out-File, and [Convert]::ToBase64String) are used exclusively, and Linux alternatives are not mentioned. Only in the 'service groups' section are Bash examples provided, and even there, PowerShell is shown first in some places. This creates friction for Linux/macOS users attempting to follow the troubleshooting steps.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell commands, especially in troubleshooting steps.
- Replace or supplement Windows-specific tools (e.g., ConvertTo-Json, Out-File) with cross-platform alternatives (e.g., jq, echo, cat, base64).
- Ensure variable syntax is compatible with Bash (e.g., $var vs. ${var}).
- Clearly indicate which commands are platform-specific and offer alternatives or notes for Linux/macOS users.
- Where possible, use platform-neutral Azure CLI commands and avoid PowerShell-only constructs.
- Present Bash/Linux examples before or alongside PowerShell examples to avoid implicit prioritization.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides Azure CLI deployment instructions exclusively using PowerShell syntax and variable assignment, which is native to Windows. There are no Bash or Linux/macOS shell examples, and the CLI section assumes a Windows environment. This creates friction for Linux/macOS users, who must adapt the instructions to their shell. The Azure portal instructions are platform-neutral, but the CLI section is Windows-centric.
Recommendations
- Provide equivalent Bash examples for Azure CLI commands, including variable assignment and command execution.
- Explicitly note that PowerShell syntax is shown and provide guidance for Linux/macOS users.
- Consider presenting Bash and PowerShell examples side-by-side or in tabs.
- Avoid using Windows-specific variable assignment (e.g., $var) in CLI documentation unless clearly marked as PowerShell-only.
Azure Arc
Data collection and reporting | Azure Arc-enabled data services
...zure-arc/data/privacy-data-collection-and-reporting.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is generally cross-platform and references Azure Arc-enabled data services, which run on Kubernetes and are managed via Azure CLI and Azure Data Studio (both cross-platform). However, there is evidence of Windows bias in the 'Arc-enabled SQL Server' billing data JSON example, where 'osType' is set to 'Windows', 'manufacturer' is 'Microsoft', and 'model' is 'Hyper-V'. There are no explicit Linux/macOS examples or references to Linux-specific environments, and the only OS-specific example is Windows. Additionally, SQL Server is a product historically associated with Windows, and no parity is shown for Linux deployments or examples, even though SQL Server is available on Linux. The order of presentation also puts Windows-centric examples first.
Recommendations
- Add explicit Linux/macOS examples in the billing data section, e.g., show 'osType': 'Linux', 'manufacturer': 'Dell', 'model': 'PowerEdge', etc.
- Clarify that SQL Server can run on Linux and provide example JSON payloads for Linux-based deployments.
- Where OS-specific properties are shown, provide a table or section describing possible values for both Windows and Linux environments.
- Ensure that any references to tools (Azure CLI, Azure Data Studio) highlight their cross-platform nature and provide links to installation instructions for Linux/macOS.
- If PowerShell or Windows tools are referenced elsewhere, add Bash or Linux shell equivalents.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing all CLI examples in PowerShell syntax, referencing PowerShell explicitly, and omitting Linux/macOS shell equivalents. The instructions assume use of PowerShell, even for commands that are cross-platform (e.g., az, kubectl), and do not offer bash/zsh examples or mention Linux-specific considerations.
Recommendations
- Add a Bash/zsh/Linux/macOS tab alongside the Azure PowerShell tab, showing equivalent commands in standard shell syntax.
- Clarify that az and kubectl commands are cross-platform and provide examples for both Windows (PowerShell) and Linux/macOS (bash).
- Avoid using PowerShell variable syntax ($var) in generic CLI examples; use environment variables or inline arguments for broader compatibility.
- Explicitly mention that the instructions apply to Linux/macOS as well, and note any OS-specific steps if relevant.
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 mentions Windows service management commands ('Stop-Service ExtensionService', 'Start-Service ExtensionService') before their Linux equivalents ('systemctl stop extd', 'systemctl start extd'). The extension removal example uses a Windows-specific extension ('AzureMonitorWindowsAgent'), and there are no Linux/macOS-specific examples or extension names. The documentation does not provide Linux/macOS-specific usage patterns or troubleshooting tips.
Recommendations
- Present Linux and Windows service management commands side-by-side, or alternate which platform is listed first.
- Include examples using Linux/macOS-specific extensions (e.g., 'AzureMonitorLinuxAgent').
- Add notes or examples relevant to Linux/macOS users, such as common extension names or troubleshooting steps.
- Clarify any platform-specific differences in extension management, if applicable.
Azure Arc
Simplify Network Configuration Requirements with Azure Arc Gateway
...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools and PowerShell commands are consistently presented alongside Azure CLI, and in some cases, Windows-specific instructions (such as log file locations) are described before or in more detail than their Linux equivalents. Some scenarios (e.g., Windows Admin Center, Windows OS Update Extension) are highlighted without Linux alternatives or parity notes. The onboarding and management instructions do include Azure CLI examples, which are cross-platform, but PowerShell is given equal prominence, and Windows-specific patterns (like referencing Windows installation packages and prerequisites) are more detailed than Linux ones.
Recommendations
- Ensure Linux examples and instructions are presented with equal detail and prominence as Windows ones, including log file locations, onboarding steps, and troubleshooting.
- Where PowerShell is used, clarify that Azure CLI commands are cross-platform and provide explicit Bash/Linux shell examples where appropriate.
- For scenarios listed as 'Windows only' (e.g., Windows Admin Center, Windows OS Update Extension), add notes about Linux alternatives or clarify Linux support status.
- Review all endpoint and prerequisite lists to ensure Linux-specific requirements are fully documented and not overshadowed by Windows-centric notes.
- Consider presenting CLI (cross-platform) examples before PowerShell (Windows-only) in each tabbed section.
Azure Arc
How to evaluate Azure Arc-enabled servers with an Azure virtual machine
...-arc/servers/plan-evaluate-on-azure-virtual-machine.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows examples and PowerShell commands are consistently presented before Linux equivalents. Windows-specific tools (PowerShell, WindowsAzureGuestAgent, New-NetFirewallRule) are described in detail, while Linux instructions sometimes refer users to external documentation or provide less guidance. The VM creation links for Linux are inconsistent, and some Linux steps (e.g., firewall configuration) require users to consult their own distribution's documentation, whereas Windows steps are fully detailed.
Recommendations
- Present Linux and Windows examples side-by-side or alternate which comes first.
- Provide direct, detailed Linux command examples for all major distributions (Ubuntu, Red Hat, SUSE) rather than referring users to external documentation.
- Ensure VM creation links for Linux point to the correct template (the Ubuntu link currently points to the Windows template).
- Offer parity in troubleshooting and error messages for both platforms.
- Include more context and explanation for Linux-specific steps, matching the detail given to Windows instructions.
Azure Arc
Troubleshoot Azure Arc-enabled servers in disconnected scenarios
...rticles/azure-arc/servers/troubleshoot-connectivity.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates Windows bias by exclusively mentioning Windows-specific tools (Windows Admin Center, Configuration Manager) as local management options for disconnected servers. There are no references to Linux/macOS equivalents or examples, and Windows tools are presented first and solely, which may leave Linux users without clear guidance for managing Arc-enabled servers in disconnected scenarios.
Recommendations
- Include Linux/macOS management tool options (e.g., Cockpit, Ansible, SSH, systemd) alongside Windows Admin Center and Configuration Manager.
- Provide examples or guidance for Linux users on how to monitor, manage, and troubleshoot Arc-enabled servers when disconnected.
- Add parity in recommendations for local troubleshooting and configuration steps for both Windows and Linux platforms.
- Explicitly state which steps or tools are platform-specific and offer alternatives for other operating systems.
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
windows_tools
Summary
The documentation page demonstrates moderate Windows bias. PowerShell is the only CLI example shown for extension removal, with no equivalent Linux shell command provided. Windows file paths and troubleshooting steps are consistently listed before Linux equivalents, and Windows-specific tools (PowerShell) are referenced without parity for Linux users. While Linux information is present, it is secondary and less actionable.
Recommendations
- Provide Linux shell (bash) command examples alongside PowerShell, such as using the Azure CLI for extension removal.
- Alternate the order of Windows and Linux instructions or present them in parallel to avoid Windows-first bias.
- Reference Linux-native tools and troubleshooting patterns (e.g., systemctl, journalctl) where appropriate.
- Ensure all actionable steps (such as extension removal) have clear instructions for both platforms.
Azure Arc
Remove your SCVMM environment from Azure Arc
...virtual-machine-manager/remove-scvmm-from-azure-arc.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation exhibits a notable Windows bias. Windows examples and tools (e.g., PowerShell scripts, Control Panel instructions) are presented first and in greater detail. The deboarding script is only available as a Windows PowerShell script, with no Linux or cross-platform alternative. Manual steps and UI flows are described in a way that assumes a Windows-centric SCVMM environment, and Linux users are left without equivalent automation or scripting guidance.
Recommendations
- Provide a cross-platform (e.g., Bash or Python) version of the deboarding script, or at least document manual CLI steps for Linux environments.
- Present Linux and Windows instructions with equal prominence, possibly using side-by-side tabs or sections.
- Include Linux-specific automation examples for agent removal and resource cleanup, not just manual commands.
- Clarify any platform limitations up front, and offer workarounds or alternatives for non-Windows users.
- Where PowerShell is used, note if it can be run on PowerShell Core on Linux/macOS, or provide equivalent Bash/CLI commands.
Azure Arc
Perform disaster recovery operations
...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation exclusively provides PowerShell script examples and instructions, with no mention of Linux/macOS shell equivalents or cross-platform onboarding scripts. All command-line steps assume a Windows environment and tooling, creating friction for users on Linux or macOS.
Recommendations
- Provide equivalent Bash or shell script examples for Linux/macOS users.
- Clarify whether the onboarding script can be run on Linux/macOS, and provide instructions if so.
- Explicitly mention platform requirements and alternatives for non-Windows users.
- If the onboarding script is Windows-only, offer a containerized or cross-platform version.
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
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation for preparing Linux with AKS Edge Essentials exclusively uses PowerShell commands (Invoke-AksEdgeNodeCommand) to configure Linux nodes, rather than providing native Linux shell commands. This assumes users are operating from a Windows environment or using Windows-based management tools, and does not show direct Linux CLI equivalents. No bash or shell examples are given, which may hinder Linux/macOS users who manage clusters directly from Linux terminals.
Recommendations
- Provide native Linux shell (bash) command examples for each step, so users can run them directly on Linux nodes.
- Clarify whether Invoke-AksEdgeNodeCommand is required, or if manual SSH and shell commands are supported.
- Add a section describing how to perform these tasks from a Linux or macOS management workstation.
- Ensure parity by listing both PowerShell and bash examples side-by-side.
Azure Arc
Choosing the right Azure Arc service for machines
...nt-docs/blob/main/articles/azure-arc/choose-service.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (SCVMM, Azure VMware Solution, Extended Security Updates for Windows Server) are mentioned more frequently and in greater detail than Linux equivalents. Windows scenarios (e.g., onboarding Windows Server, SQL Server, PowerShell automation) are highlighted, and links often default to Windows tabs or documentation. While Linux is mentioned as supported, concrete Linux-specific examples, tooling, or onboarding steps are missing, and Windows-centric patterns (e.g., PowerShell, SCVMM) are referenced before or instead of Linux alternatives.
Recommendations
- Add explicit Linux onboarding examples and workflows, including links to Linux-specific documentation and troubleshooting.
- Provide parity in automation examples by including Bash, shell scripts, and Linux-native tools alongside PowerShell.
- Highlight Linux management scenarios (e.g., patching, monitoring, security) with concrete examples and guidance.
- Balance references to Windows tools (SCVMM, PowerShell) with Linux equivalents (e.g., Ansible, shell scripts, Linux package managers).
- Ensure links and tabs do not default to Windows-only content; provide equal visibility for Linux instructions.
Azure Arc
Customer intent: As a system administrator, I want to configure a single-node Kubernetes cluster with adequate resources and storage provisions, so that I can deploy and manage applications effectively using Azure IoT Operations and Azure Container Storage.
...tainer-storage/includes/single-node-edge-essentials.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is focused on preparing Linux nodes for AKS Edge Essentials, but it uses Windows-centric tools and patterns, specifically the Invoke-AksEdgeNodeCommand PowerShell cmdlet for Linux configuration. There are no direct Linux shell command examples for critical sysctl configuration steps, and the use of Notepad as the suggested editor further reflects Windows bias.
Recommendations
- Provide Linux-native shell command equivalents for sysctl configuration (e.g., using sudo sysctl directly on the Linux host).
- Suggest Linux text editors (e.g., nano, vim) alongside Notepad for editing configuration files.
- Clarify whether the PowerShell cmdlets must be run from a Windows host or if Linux users can perform these steps natively.
- Add explicit instructions for Linux users to perform all steps without requiring Windows tools.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page demonstrates a moderate Windows bias. It prioritizes Windows-centric tools (SQL Server Management Studio, Azure Data Studio) and patterns, mentioning them before Linux alternatives. Examples and instructions for connecting to SQL Managed Instance focus on Windows tools and workflows, with only brief mentions of Linux. The documentation does not provide Linux-specific client recommendations or detailed Linux connection steps, and the VM networking section assumes Azure CLI usage, which is cross-platform but often associated with Windows environments.
Recommendations
- Include explicit Linux/macOS client tool recommendations (e.g., DBeaver, SquirrelSQL, or native sqlcmd usage on Linux).
- Provide step-by-step connection examples for Linux/macOS, including screenshots or terminal commands.
- Clarify that Azure Data Studio and SQLCMD are cross-platform, and provide installation instructions for Linux/macOS.
- Add troubleshooting notes for common Linux/macOS connectivity issues (e.g., firewall, SELinux, network configuration).
- Present examples in parallel (Windows and Linux/macOS side-by-side) rather than Windows-first.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits Windows bias by providing SQL Server connection examples using Powershell syntax and commands, without offering equivalent Linux/macOS shell examples. The use of Powershell code blocks for kubectl exec and sqlcmd commands may confuse Linux users, and there are no bash or Linux-native examples for connecting to SQL Server or decoding secrets. The documentation implicitly assumes a Windows environment for command execution, which may create friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS shell (bash) examples alongside Powershell, especially for kubectl exec and sqlcmd commands.
- Use generic 'console' or 'bash' code blocks for commands that are cross-platform, and clarify any OS-specific differences.
- Include instructions for decoding base64 secrets using Linux/macOS tools (e.g., 'echo ... | base64 -d').
- Explicitly state that all commands can be run from Linux/macOS terminals, and note any prerequisites or differences.
- Avoid using Powershell code blocks for commands that are not Windows-specific.
Azure Arc
Quickstart - Deploy Azure Arc-enabled data services - directly connected mode - Azure portal
...ttps://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-complete-managed-instance-directly-connected.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows environments by showing Windows-style file paths in command outputs (e.g., C:<current path>\.kube\config) and omitting explicit Linux/macOS examples or notes. All instructions and outputs assume Windows conventions, with no mention of Linux/macOS equivalents or differences, such as file path formats or prerequisites for non-Windows systems.
Recommendations
- Include Linux/macOS-specific notes where file paths or command outputs differ (e.g., ~/.kube/config for Linux/macOS).
- Add explicit examples or screenshots for Linux/macOS environments alongside Windows ones.
- Mention any OS-specific prerequisites or installation steps for client tools.
- Clarify that Azure CLI and kubectl commands are cross-platform, and provide guidance for users on different operating systems.
Azure Arc
Deploy Active Directory-integrated SQL Managed Instance enabled by Azure Arc
...c/data/deploy-active-directory-sql-managed-instance.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation page exhibits moderate Windows bias. Windows-specific tools (Active Directory Users and Computers, setspn, ktpass, PowerShell scripts) are mentioned and demonstrated before or alongside Linux alternatives. The process of creating AD accounts and SPNs is described using Windows GUI and CLI tools, with Linux tools (adutil, ktutil, shell scripts) referenced but not given equal prominence or detailed walkthroughs. Windows examples and scripts are often listed first, and some steps (such as account creation) are described only using Windows methods.
Recommendations
- Provide step-by-step instructions for creating Active Directory accounts and SPNs using Linux-based tools (e.g., adutil, samba-tool, ldapadd) and CLI workflows.
- Ensure Linux tools (adutil, ktutil) are described with equal detail and prominence as Windows tools (ktpass, setspn).
- Present Linux examples and scripts before or alongside Windows examples, not after.
- Include guidance for managing Active Directory from Linux environments, such as using Kerberos and LDAP utilities.
- Clarify which steps require Windows-only tools and offer Linux alternatives wherever possible.
Azure Arc
Deploy Active Directory integrated SQL Managed Instance enabled by Azure Arc using Azure CLI
...ta/deploy-active-directory-sql-managed-instance-cli.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is focused on deploying Active Directory integrated SQL Managed Instance using Azure Arc and Azure CLI. While the instructions are platform-neutral in terms of CLI usage, there is a notable bias towards Windows environments: Active Directory (AD) is a Windows-centric technology, and all examples and terminology assume the use of AD, with no mention of Linux-native identity solutions or integration patterns. The documentation does not provide guidance for Linux-based directory services or alternatives, and references to AD setup and prerequisites implicitly target Windows administrators. However, the actual CLI commands are cross-platform and do not use Windows-only tools like PowerShell.
Recommendations
- Explicitly state that the instructions are applicable to any OS that supports Azure CLI, including Linux and macOS.
- Provide guidance or references for integrating with Linux-based directory services (e.g., LDAP, FreeIPA) if supported, or clarify AD is required.
- Add notes or examples for Linux/macOS users, such as shell command syntax for related tasks (e.g., managing keytab files, DNS configuration).
- Clarify any OS-specific requirements for prerequisites, such as AD connector setup, and provide links to Linux-compatible instructions if available.
Azure Arc
Tutorial – Deploy Active Directory connector in system-managed keytab mode
...eploy-system-managed-keytab-active-directory-connector.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation contains a notable Windows bias in the section describing how to identify the Primary Domain Controller (PDC). It only provides a Windows-specific command (`netdom query fsmo`) and does not offer an equivalent method for Linux/macOS users. No PowerShell scripts or Windows-first ordering is present elsewhere, but the lack of cross-platform instructions for this critical step may hinder non-Windows administrators.
Recommendations
- Provide Linux/macOS alternatives for identifying the Primary Domain Controller, such as using `ldapsearch`, `samba-tool`, or other cross-platform tools.
- Add a note or section explaining how to obtain the required Active Directory information from non-Windows environments.
- Wherever Windows-specific tools are mentioned, ensure parity by including equivalent Linux/macOS commands or references.
- Consider linking to external resources or official documentation for cross-platform AD administration.
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_authentication
windows_first
Summary
The documentation page demonstrates moderate Windows bias. Windows-specific tools (SSMS, SSDT, SQL Server Profiler, SQL Server PowerShell) are listed prominently, and PowerShell scripting is called out as a manageability feature. Windows Authentication is explicitly listed as a supported security feature, while Linux/macOS equivalents (e.g., Kerberos, local authentication) are not mentioned. There are no Linux/macOS-specific management tools or examples, and Windows-centric patterns (PowerShell, SSMS) are referenced before cross-platform alternatives like Azure Data Studio.
Recommendations
- Add explicit mention and examples of Linux/macOS management workflows, such as using Azure Data Studio, Azure CLI, or REST APIs.
- Clarify authentication options for non-Windows environments (e.g., Kerberos, certificate-based, or local authentication).
- Include Linux/macOS equivalents for PowerShell scripting, such as Bash scripts or cross-platform automation tools.
- Reorder tool lists to present cross-platform options (Azure Data Studio, Azure CLI) before Windows-only tools.
- Note any limitations or differences for Linux/macOS users in relevant sections.
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 a Windows bias by providing backup and file path examples using Windows conventions (e.g., C:\Backupfiles\test.bak) and omitting equivalent Linux/macOS examples (e.g., /home/user/test.bak). The instructions and examples for copying files into pods and backing up databases are shown only with Windows paths and do not mention Linux or macOS workflows, potentially causing confusion or friction for non-Windows users.
Recommendations
- Include Linux/macOS file path examples alongside Windows examples (e.g., /home/user/test.bak).
- Explicitly state that the backup file can be created on any OS and provide sample commands for Linux/macOS environments.
- Show kubectl cp examples using Linux/macOS source paths.
- Clarify that Azure Data Studio and Azure Storage Explorer are cross-platform, and provide installation instructions for Linux/macOS.
- Add notes or tables summarizing OS-specific steps or differences.
Azure Arc
Resize persistent volume claim (PVC) for Azure Arc-enabled data services volume
...icles/azure-arc/data/resize-persistent-volume-claim.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation provides shell command examples using a variable assignment syntax ($newsize='...') that is specific to PowerShell or Windows Command Prompt, without offering equivalent Linux/macOS shell (bash) examples. This may confuse or hinder Linux/macOS users, as the variable assignment and quoting are not compatible with bash/zsh.
Recommendations
- Provide both PowerShell/Windows and bash/Linux/macOS command examples for variable assignment and kubectl patch usage.
- Clearly label which example is for Windows/PowerShell and which is for Linux/macOS.
- Consider using cross-platform compatible commands (e.g., using environment variables and quoting that work in both shells) or explain the differences.
- Add a note clarifying that the provided variable assignment is for PowerShell, and provide the bash equivalent, such as: newsize='{"spec":{"resources":{"requests":{"storage":"50Gi"}}}}' and kubectl patch pvc ... --patch "$newsize"
Medium Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (ktpass.exe), providing PowerShell scripts, and describing password changes using Windows GUI tools (Server Manager, Active Directory Users and Computers). While a bash script is provided for Linux, the instructions and examples for password rotation are exclusively Windows-centric, with no Linux or cross-platform alternatives for Active Directory password management. The order of presentation also places Windows tools and workflows first.
Recommendations
- Add instructions for changing Active Directory passwords using cross-platform tools (e.g., samba-tool, ldapmodify) or via command line on Linux.
- Include screenshots or examples for Linux-based AD management (e.g., using RSAT on Linux, or CLI tools).
- Present bash and PowerShell scripts in parallel, with equal prominence.
- Clarify which steps are platform-specific and provide alternatives for Linux/macOS users.
- Mention any prerequisites or limitations for Linux users (e.g., access to AD via LDAP, required packages).
Azure Arc
Configure "BYOM" Endpoint Authentication for Edge RAG
...zure-arc/edge-rag/configure-endpoint-authentication.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exclusively uses PowerShell syntax and Windows-specific patterns (e.g., '.\kubectl.exe'), with no Bash or Linux/macOS shell examples. All code snippets assume a Windows environment, and there is no mention of Linux/macOS equivalents or cross-platform usage. This creates friction for non-Windows users attempting to follow the instructions.
Recommendations
- Provide equivalent Bash shell examples for Linux/macOS users, using standard kubectl commands and shell utilities (e.g., base64, echo).
- Avoid using Windows-specific executable extensions (e.g., 'kubectl.exe'); use 'kubectl' for cross-platform compatibility.
- Add notes or sections clarifying platform differences and how to adapt commands for Linux/macOS.
- Present Linux/macOS examples alongside Windows examples, or use a tabbed format to allow users to select their OS.
Azure Arc
Configure DNS for Edge RAG Preview Enabled by Azure Arc
...s/blob/main/articles/azure-arc/edge-rag/prepare-dns.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides only Windows-specific instructions for updating the hosts file (using Notepad, Administrator privileges, and referencing the Windows file path). There are no examples or guidance for Linux or macOS users, and Windows tools/patterns are mentioned exclusively and first.
Recommendations
- Add instructions for Linux and macOS users, including the appropriate hosts file path (e.g., /etc/hosts) and required permissions (e.g., using sudo and a text editor like nano or vim).
- Present platform-specific instructions in parallel or clearly labeled sections (e.g., 'Windows', 'Linux', 'macOS') to ensure parity.
- Avoid assuming Windows as the default environment; mention cross-platform considerations where relevant.
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
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page displays a notable Windows bias. All command-line examples are written in PowerShell syntax, including variable assignment and command chaining, which are not directly usable on Linux/macOS shells. Windows-specific tools and patterns (e.g., Restart-Service, Start-Sleep) are referenced without Linux equivalents. Instructions for configuring a management machine explicitly link to a Windows setup script, with no mention of Linux/macOS alternatives. There are no bash or cross-platform CLI examples, and Windows approaches are presented first and exclusively.
Recommendations
- Provide equivalent bash shell examples for all PowerShell commands, especially for az CLI usage and node pool creation.
- Document Linux/macOS setup steps for the management host, including installation of Azure CLI, kubectl, Helm, and required extensions.
- Reference Linux/macOS tools and commands for GPU driver installation and service management (e.g., systemctl instead of Restart-Service).
- Clearly indicate which steps are OS-specific and offer parity for Linux/macOS users.
- Reorder examples or provide parallel instructions to avoid Windows-first presentation.
Azure Arc
Verify Contributor Role for Edge RAG Preview Enabled by Azure Arc
...s/azure-arc/edge-rag/prepare-contributor-permission.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation provides only PowerShell-based Azure CLI examples and does not mention or show Linux/macOS shell equivalents. Windows/PowerShell command patterns are presented exclusively, with no reference to Bash or cross-platform usage.
Recommendations
- Include Bash/zsh shell examples for the Azure CLI commands, as 'az' is cross-platform.
- Clarify that the commands work on Linux/macOS terminals as well, not just PowerShell.
- Add a note or section on running these commands from a Linux/macOS environment.
- Avoid using PowerShell-specific formatting for cross-platform CLI commands.
Azure Arc
Install Networking and Observability Components for Edge RAG Preview Enabled by Azure Arc
...azure-arc/edge-rag/prepare-networking-observability.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides only PowerShell-based examples and scripts, assuming the user is on Windows or using PowerShell Core. There are no bash, shell, or Linux-native command examples, and all variable assignments and scripting patterns are Windows-centric. This creates friction for Linux/macOS users, who must translate or adapt the instructions themselves.
Recommendations
- Provide equivalent bash/shell command examples for all PowerShell scripts, especially for az CLI and kubectl/helm usage.
- Clearly indicate which steps are OS-agnostic and which require adaptation.
- Mention that az CLI, kubectl, and helm are cross-platform, and show how to set variables and run commands in both Windows (PowerShell) and Linux/macOS (bash).
- If PowerShell Core is required on Linux/macOS, explicitly state this and provide installation guidance.
Azure Arc
Quickstart: Install Edge RAG on Azure Kubernetes Service
...ain/articles/azure-arc/edge-rag/quickstart-edge-rag.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates Windows bias primarily in the 'Connect to the developer portal' section, where instructions are given exclusively for editing the Windows hosts file using Notepad and navigating to C:\windows\System32\drivers\etc. There are no equivalent instructions for Linux or macOS users, such as using sudo and a text editor to edit /etc/hosts. Additionally, the use of backticks (`) for line continuation in Azure CLI examples is a PowerShell/Windows convention, which may confuse Linux/macOS users who expect backslashes (\) or no continuation. The document also suggests switching to PowerShell in Azure Cloud Shell, further reinforcing a Windows-first approach.
Recommendations
- Provide explicit instructions for editing the hosts file on Linux (e.g., 'sudo nano /etc/hosts') and macOS (e.g., 'sudo open -e /etc/hosts' or 'sudo nano /etc/hosts').
- Clarify line continuation syntax for Azure CLI commands: show both Windows (backtick) and Linux/macOS (backslash or multi-line without continuation) examples.
- Avoid suggesting PowerShell as the default shell in Azure Cloud Shell; mention Bash as an alternative and provide command compatibility notes.
- Where file paths are referenced, include both Windows and Unix-style paths.
- Add a note or section for cross-platform differences, especially for steps that involve local machine configuration.
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
missing_linux_example
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 without clarifying platform applicability. There is no explicit mention of Linux/macOS usage, nor are Linux-specific shell examples (e.g., Bash) provided. The presence of PowerShell (commonly associated with Windows) may create friction for Linux users unfamiliar with it.
Recommendations
- Clarify that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for Linux/macOS users.
- Add a Bash shell example using Azure CLI to reinforce Linux parity.
- Explicitly state platform compatibility for each command.
- Consider listing Azure CLI examples first, as it is cross-platform.
Azure Arc
Simplify network configuration requirements with Azure Arc gateway (preview)
...zure-arc/kubernetes/arc-gateway-simplify-networking.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 tasks, but consistently lists PowerShell examples immediately after CLI, and uses Windows-style environment variable syntax in PowerShell sections. There are no explicit Linux/macOS command-line examples (e.g., bash, zsh), and no mention of platform-specific differences or considerations. The CLI examples are cross-platform, but PowerShell is Windows-centric, and its inclusion without Linux/macOS shell equivalents may create friction for non-Windows users.
Recommendations
- Add explicit bash/zsh examples for environment variable configuration and commands, especially in sections where PowerShell syntax is shown.
- Clarify that Azure CLI commands work on Linux/macOS and Windows, and note any platform-specific prerequisites or differences.
- Where environment variables are set, show both export (bash/zsh) and set (PowerShell) syntax side-by-side.
- Consider listing CLI (cross-platform) examples before PowerShell (Windows-centric) examples, or grouping them in tabs labeled by OS.
- Explicitly mention that PowerShell Core is available on Linux/macOS, or provide links to installation instructions if recommending PowerShell usage on those platforms.
Azure Arc
Use cluster connect to securely connect to Azure Arc-enabled Kubernetes clusters.
.../main/articles/azure-arc/kubernetes/cluster-connect.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for most steps, but PowerShell is featured as a first-class option throughout, and several code blocks use PowerShell-specific syntax (e.g., $VARIABLE assignment, [System.Text.Encoding] calls) that are not portable to Linux/macOS shells. There is no explicit mention or example of Bash, zsh, or other Linux/macOS shell environments, nor are Linux-specific instructions or troubleshooting tips provided. The use of PowerShell for environment variable assignment and token extraction is Windows-centric, and the CLI examples do not clarify cross-platform compatibility. The documentation assumes users are familiar with PowerShell, which is not standard on Linux/macOS.
Recommendations
- Add explicit Bash/zsh examples for all steps involving environment variables and token extraction, using POSIX-compliant syntax.
- Clarify that Azure CLI commands are cross-platform and provide shell-agnostic instructions where possible.
- Reorder examples so that Bash/Linux/macOS instructions are shown first or side-by-side with PowerShell, rather than PowerShell being a primary option.
- Include troubleshooting notes for Linux/macOS users, such as handling base64 decoding and file creation.
- Avoid using PowerShell-specific constructs (e.g., $VARIABLE assignment, [System.Text.Encoding]) without providing equivalent Bash alternatives.
Azure Arc
Quickstart: Connect an existing Kubernetes cluster to Azure Arc
...les/azure-arc/kubernetes/quickstart-connect-cluster.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides parallel instructions for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. In several places, Docker for Windows is mentioned alongside Docker for Mac, but Linux-specific instructions are not highlighted or are omitted. The use of PowerShell examples and environment variable syntax is Windows-specific, and Windows tooling (PowerShell) is presented as an equal alternative to Azure CLI, which is cross-platform. There are no explicit Linux shell examples for Azure CLI usage, and the order of presenting Windows tools (PowerShell) before Linux alternatives (bash) in proxy configuration sections may create friction for Linux/macOS users.
Recommendations
- Add explicit Linux shell (bash) examples for Azure CLI usage, especially for environment variable configuration and proxy settings.
- Include instructions or links for setting up Kubernetes clusters on Linux (e.g., minikube, kubeadm) in the prerequisites section.
- Clarify that Azure CLI commands can be run on Linux/macOS, and provide example shell commands where appropriate.
- When mentioning Docker for Windows/Mac, also mention Docker for Linux or other Linux-native Kubernetes solutions.
- Consider moving PowerShell sections after CLI/bash sections, or clarify platform applicability at the start of each section.
Azure Arc
Tutorial: Implement CI/CD with GitOps (Flux v2)
...es/azure-arc/kubernetes/tutorial-gitops-flux2-ci-cd.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
Summary
The documentation is Azure-centric and presents Azure DevOps (a Microsoft/Windows ecosystem tool) as the primary CI/CD orchestrator, with detailed, step-by-step instructions for Azure DevOps before introducing GitHub. Azure DevOps workflows, permissions, and terminology are described in depth, while GitHub instructions are briefer and appear later. There is a strong focus on Azure CLI and Azure portal, both of which are cross-platform, but the overall flow and examples are tailored to users familiar with Microsoft tools and patterns. No explicit PowerShell-only or Windows-only commands are present, and all CLI examples use az, kubectl, and helm, which are available on Linux/macOS. However, the documentation assumes Azure DevOps as the default and provides more guidance for it, which may create friction for Linux/macOS users who prefer open-source or non-Microsoft CI/CD solutions.
Recommendations
- Present GitHub and Azure DevOps workflows in parallel, giving equal detail and prominence to both.
- Add explicit notes about cross-platform compatibility of all CLI tools used (az, kubectl, helm).
- Include references or examples for other popular CI/CD orchestrators (e.g., Jenkins, GitLab CI) to broaden applicability.
- Clarify that Azure DevOps is not required and that all steps can be completed on Linux/macOS.
- Provide troubleshooting tips for Linux/macOS users (e.g., file path differences, CLI installation instructions).
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page demonstrates a moderate Windows bias by repeatedly referencing Windows-centric management tools (VMware vCenter, System Center Virtual Machine Manager) and listing them before Linux-native alternatives. While Linux is mentioned as a supported platform for servers and VMs, there are no explicit Linux tooling examples or references to Linux-native management solutions. The focus on Windows-based virtualization and management tools may create friction for Linux/macOS users seeking parity.
Recommendations
- Include explicit examples and references for managing Linux servers and VMs, such as integration with Linux-native hypervisors (e.g., KVM, libvirt) or management tools.
- Balance the order of tool mentions by listing Linux and Windows options together, or alternating which is mentioned first.
- Add links to documentation or guides specifically for Linux users, covering onboarding, management, and troubleshooting.
- Clarify that Azure Arc supports Linux environments equally and provide scenarios or case studies relevant to Linux-heavy infrastructures.
Azure Arc
CLI reference for `azcmagent check`
...lob/main/articles/azure-arc/servers/azcmagent-check.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page references a Windows-specific use case ('Windows Server Pay-as-you-go') in the flag descriptions and links to Windows documentation. No Linux/macOS-specific examples, flags, or use cases are mentioned, and the only extended use case described is Windows-centric. All examples and usage patterns are generic, but the only explicit OS reference is to Windows, with no Linux parity or equivalent scenarios discussed.
Recommendations
- Add Linux/macOS-specific examples or use cases, such as connectivity checks relevant to Linux workloads or extensions.
- Include references to Linux documentation or equivalent extended use cases (e.g., Linux server pay-as-you-go, Linux Arc extensions).
- Balance OS-specific references by mentioning both Windows and Linux where applicable, especially in flag descriptions and sample values.
- Clarify that the tool and examples apply equally to Linux/macOS, or note any differences in usage or output.
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The endpoint list documentation displays a notable Windows bias, with many endpoints referencing Windows-specific services (e.g., windowsupdate.com, powershellgallery.com, windows.net) and Microsoft services that are primarily relevant to Windows environments. The list includes endpoints for Windows Update, Windows ATP, and other Windows-centric tools before mentioning Linux-specific endpoints (e.g., linuxgeneva-microsoft.azurecr.io). There are no explicit Linux/macOS examples, nor is there guidance for Linux users regarding endpoint relevance.
Recommendations
- Clearly indicate which endpoints are required for Linux, Windows, and macOS environments, possibly with separate tables or annotations.
- Add notes or sections highlighting Linux/macOS-specific endpoints and considerations.
- Provide guidance or examples for Linux/macOS users on how to validate or configure endpoint access.
- Review endpoint descriptions to ensure parity and clarity for non-Windows platforms.
Azure Arc
Troubleshoot Azure Arc resource bridge issues
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and patterns (PowerShell, RDP, Windows paths, and references to time.windows.com) are mentioned before or instead of Linux/macOS equivalents. Troubleshooting steps and example commands often use Windows-centric terminology and workflows (e.g., 'Remote PowerShell', 'RDP', Windows file paths), and some diagnostic instructions (such as PowerShell cmdlets for DNS resolution and HTTP/2 troubleshooting) are provided only for Windows. Linux-specific troubleshooting is limited, and parity in examples (e.g., using Linux CLI tools for network, DNS, or HTTP/2 validation) is missing. However, the core deployment and troubleshooting commands use Azure CLI, which is cross-platform, and there are some references to Linux (e.g., glibc errors), so Linux users can generally complete the tasks with some friction.
Recommendations
- Provide Linux/macOS equivalents for all PowerShell and Windows-specific commands (e.g., use curl, wget, dig, nslookup, or openssl for network and DNS troubleshooting).
- Include Linux/macOS instructions for remote access (e.g., SSH, console session) where RDP is mentioned.
- Add Linux file path examples and clarify cross-platform differences in file locations (e.g., SSH folder).
- When referencing time synchronization, mention NTP and Linux time sources, not just time.windows.com.
- Ensure troubleshooting steps for HTTP/2, DNS, and proxy issues include Linux/macOS workflows and tools.
- Where Windows tools are referenced first, present Linux/macOS alternatives in parallel or before Windows examples.
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific issues, tools, and troubleshooting steps (such as PowerShell, msiexec, and GUI instructions) are described in detail, often without Linux equivalents or with Linux information presented second. Troubleshooting and installer guidance is Windows-centric, and Windows download links are consistently listed before Linux. Some bug fixes and features are marked as Windows-only, while Linux-specific guidance is sparse or missing.
Recommendations
- Provide equivalent Linux troubleshooting steps, such as command-line installation and service management instructions (e.g., systemctl, rpm, deb).
- Include Linux-first or side-by-side examples for installation, configuration, and known issues.
- Add Linux-specific guidance for common problems, such as permission issues, service failures, or package management errors.
- Ensure parity in bug fix and feature descriptions, clarifying when a fix or feature applies to both platforms or only one.
- Alternate the order of Windows and Linux download links or present them together to avoid implicit prioritization.
Azure Arc
Identity and access management with Azure Arc-enabled servers
...cles/azure-arc/servers/cloud-native/identity-access.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric identity concepts (Active Directory, Group Policy, LAPS) are discussed first and in detail, while Linux equivalents are only briefly mentioned. Remote Desktop for Windows is described before SSH for Linux, and Windows management tools are referenced without Linux alternatives. There are no concrete Linux command examples or guidance for Linux-specific scenarios, making it harder for Linux users to follow or adapt the instructions.
Recommendations
- Provide Linux-specific examples and workflows, such as how to use Azure Arc and Microsoft Entra ID for Linux server management.
- Include Linux command-line examples (e.g., using SSH, Azure CLI on Linux, configuring managed identities on Linux).
- Mention Linux-native identity management tools and patterns (such as SSSD, PAM, or local sudoers management) where relevant.
- Balance the order of presentation: introduce Linux and Windows scenarios together, rather than focusing on Windows first.
- Add troubleshooting or best practices sections for Linux environments.
Azure Arc
Deploy Azure Monitor agent on Arc-enabled servers
...es/azure-arc/servers/azure-monitor-agent-deployment.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation references PowerShell as a primary automation tool and lists it before alternatives like Azure CLI or ARM templates. There is no explicit mention of Linux-specific commands, tools, or examples (e.g., Bash, shell scripts), nor any guidance for Linux users on how to perform equivalent tasks. The documentation assumes familiarity with Windows-centric tooling and patterns, which may create friction for Linux/macOS users.
Recommendations
- Add explicit examples for Linux environments, such as Bash or shell script equivalents for agent deployment.
- Clarify which tools and methods are cross-platform (e.g., Azure CLI, ARM templates) and provide OS-specific guidance where necessary.
- When listing automation options, alternate or balance the order (e.g., mention Bash and PowerShell together, or Azure CLI before PowerShell in some sections).
- Include notes or links to Linux/macOS documentation for agent installation and management.
- Highlight any OS-specific requirements or differences in the deployment process.
Azure Arc
Cloud-native governance and policy with Azure Arc-enabled servers
...es/azure-arc/servers/cloud-native/governance-policy.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows-centric tools (Active Directory Group Policy, RSoP, gpresult, Windows Firewall, Windows security baselines) and providing examples and scenarios exclusively for Windows servers. There are no explicit examples, policy mappings, or references for Linux servers, nor is there mention of how Azure Policy or machine configuration applies to Linux or macOS environments. The language and examples assume a Windows-first audience, leaving Linux users without clear guidance on parity or implementation.
Recommendations
- Add explicit examples of Azure Policy and machine configuration for Linux servers, such as auditing and enforcing Linux-specific settings (e.g., SSH configuration, firewall rules, systemd services).
- Reference Linux equivalents to Windows tools (e.g., mention how compliance can be checked on Linux, such as using auditd, systemctl, or custom scripts).
- Include links to documentation about Azure Policy support for Linux, and clarify which built-in policies are available for Linux.
- Discuss differences and limitations in policy enforcement between Windows and Linux, and provide guidance for hybrid environments with both OS types.
- Avoid assuming all servers are Windows; use inclusive language and examples for cross-platform scenarios.
Azure Arc
Cloud-native inventory and resource organization with Azure Arc-enabled servers
...s/azure-arc/servers/cloud-native/inventory-resource.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page uses Windows-centric terminology and examples throughout, such as references to Active Directory (AD), Group Policy Objects (GPOs), System Center Configuration Manager (SCCM), and Windows Server versions. There are no Linux/macOS-specific organizational analogies or examples, and inventory queries reference Windows Server explicitly. The documentation assumes familiarity with Windows management paradigms and does not mention Linux-native equivalents or provide Linux-specific examples.
Recommendations
- Add analogies and examples relevant to Linux environments, such as referencing LDAP, systemd units, or Ansible inventory/grouping.
- Include sample queries or scenarios for Linux servers (e.g., finding all Ubuntu servers, grouping by Linux distribution).
- Mention Linux-native management tools or patterns (e.g., Puppet, Chef, SaltStack) alongside SCCM and AD.
- Provide examples of tags or resource groups that might be used in Linux-centric organizations.
- Explicitly state that Azure Arc supports Linux servers and highlight any differences or considerations for Linux resource organization.
Azure Arc
Next steps for cloud-native server management with Azure Arc-enabled servers
.../articles/azure-arc/servers/cloud-native/next-steps.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and workflows (Windows Admin Center, Configuration Manager, WSUS, GPOs) are mentioned exclusively or before any Linux equivalents. There are no explicit Linux onboarding or management examples, and Linux-native tools or patterns are not referenced. This may create friction for Linux users seeking parity in onboarding and management guidance.
Recommendations
- Include explicit onboarding instructions and examples for Linux servers, such as using shell scripts, cloud-init, or Ansible.
- Mention Linux-native management tools (e.g., cron for automation, Linux patching workflows) alongside Windows tools.
- Provide parity in examples: if Windows Admin Center is referenced, also reference SSH, Linux CLI, or other Linux-friendly onboarding methods.
- Clarify which Azure Arc features and workflows are OS-agnostic, and highlight any differences or limitations for Linux.
- Add links to Linux-specific documentation or community resources.
Azure Arc
Cloud-native server management with Azure Arc-enabled servers
...in/articles/azure-arc/servers/cloud-native/overview.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. It references Windows-centric management tools (Active Directory Group Policy, SCCM, MECM, PowerShell remoting, WSUS) as the primary legacy equivalents, and describes Azure Arc as an evolution of these Windows tools. Windows concepts and terminology (Active Directory, System Center, Intune, ESUs for Windows Server) are mentioned first or exclusively, while Linux equivalents (such as Ansible, Chef, or Linux-native patching tools) are absent. There are no explicit Linux command-line or tool examples, and the narrative assumes familiarity with Windows administration patterns.
Recommendations
- Include references to common Linux management tools (e.g., Ansible, Chef, Puppet, cron, yum/apt patching) as legacy equivalents alongside Windows tools.
- Provide examples or scenarios for Linux server management, such as how Azure Arc replaces or augments SSH, shell scripting, or Linux configuration management.
- Balance terminology by mentioning Linux-native concepts (e.g., sudoers, systemd, SELinux policies) where relevant.
- Add explicit Linux command-line examples or workflows in relevant sections.
- Clarify that Azure Arc supports both Windows and Linux equally, and highlight any Linux-specific features or considerations.
Azure Arc
Cloud-native scripting and task automation with Azure Arc-enabled servers
...-arc/servers/cloud-native/scripting-task-automation.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools and patterns (RDP, PowerShell, SCCM, Task Scheduler) are mentioned first and more frequently than their Linux equivalents. Examples and analogies are often Windows-oriented, and Linux-specific workflows (e.g., Bash scripting, cron jobs) are not described or exemplified. While SSH and Python are mentioned, there are no explicit Linux command or scripting examples, and Linux automation patterns are not discussed in detail.
Recommendations
- Add explicit Linux/Bash scripting examples alongside PowerShell examples.
- Mention Linux-native automation tools (e.g., cron, Ansible) as analogies to Azure Automation and Logic Apps.
- Provide sample workflows for Linux server management (e.g., using Bash scripts with Run Command, automating package updates).
- Ensure examples and analogies are balanced between Windows and Linux, or presented in parallel.
- Clarify that Azure Run Command supports both Windows and Linux, and show how commands/scripts differ between platforms.
Azure Arc
Cloud-native patch management with Azure Arc-enabled servers
...les/azure-arc/servers/cloud-native/patch-management.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools (WSUS, SCCM) are referenced first and exclusively as traditional patch management solutions, with no mention of Linux equivalents (e.g., apt, yum, dnf, Landscape, Spacewalk). Hotpatching is described only for Windows Server, with no Linux hotpatching discussion. Examples and analogies throughout the page use Windows-centric terminology and patterns, and there are no concrete Linux workflow examples or scripts. Linux support is acknowledged, but details are sparse and secondary.
Recommendations
- Include references to traditional Linux patch management tools (e.g., apt, yum, dnf, Landscape, Spacewalk) alongside WSUS/SCCM in introductory sections.
- Provide concrete Linux patching workflow examples, such as using Azure Update Manager to patch Ubuntu or RHEL servers, with sample commands or scripts.
- Clarify whether features like hotpatching or granular patch sequencing are available for Linux, and if not, explicitly state limitations.
- Balance analogies and examples so that Linux scenarios are presented with equal detail and prominence as Windows scenarios.
- Add a table or section comparing Windows and Linux feature parity for Azure Update Manager.
Azure Arc
Azure Connected Machine Agent Deployment Options
.../main/articles/azure-arc/servers/deployment-options.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page lists deployment options for both Linux and Windows, but Windows-specific tools and methods (Windows Admin Center, Group Policy, Configuration Manager, PowerShell) are given dedicated sections and examples, while Linux-specific automation tools (e.g., shell scripts, cloud-init) are not mentioned. PowerShell is referenced as a cross-platform method, but Windows-centric management patterns and tools are described in detail, with no Linux equivalents (like Ansible, shell scripting, or Linux-native automation frameworks) highlighted in the same way.
Recommendations
- Add Linux-specific onboarding examples and highlight Linux-native automation tools (e.g., shell scripts, cloud-init, systemd units) alongside Windows tools.
- Provide parity for Linux in sections that currently only mention Windows tools (e.g., Group Policy, Configuration Manager) by referencing Linux equivalents or stating their absence.
- Ensure that cross-platform methods (like PowerShell) clarify Linux compatibility and provide Linux-specific usage notes or examples.
- Consider listing Linux and Windows methods together, or alternating which platform is described first, to avoid implicit prioritization.
Azure Arc
Customer intent: "As a network administrator, I want to configure secure outbound connectivity for the Azure Connected Machine agent so that I can ensure proper communication with Azure Arc while adhering to my organization's security policies."
...les/azure-arc/servers/includes/network-requirements.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
windows_heavy
minor_missing_linux_example
Summary
The documentation generally covers both Windows and Linux, but there is a noticeable Windows bias. Windows-specific tools (e.g., Windows Admin Center) and endpoints are mentioned more frequently and sometimes before Linux equivalents. Examples and troubleshooting links are Windows-focused, and cryptographic protocol configuration details are more explicit for Windows than Linux. Linux is referenced, but with less detail and fewer actionable instructions.
Recommendations
- Provide Linux-specific troubleshooting and configuration guidance, especially for TLS/cipher suite setup (e.g., OpenSSL configuration examples).
- Include Linux-first or side-by-side examples for agent installation, configuration, and endpoint usage.
- Mention Linux management tools (such as Cockpit or Ansible) where Windows Admin Center is referenced.
- Balance references to Windows and Linux endpoints and tools in tables and lists.
- Add explicit instructions or links for Linux users in sections that currently reference only Windows issues.
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides both Windows and Linux instructions for all major tasks (install, upgrade, uninstall, proxy config), but Windows examples and tooling (PowerShell, Group Policy, WSUS, Configuration Manager, Control Panel, MSI installer) are often presented first and in greater detail. Windows-specific tools and patterns are described extensively, while Linux instructions are more concise and generic. PowerShell examples are given for Windows, but there are no equivalent Bash scripting examples for Linux. The upgrade section especially emphasizes Windows update infrastructure before Linux package managers.
Recommendations
- Present Linux and Windows instructions in parallel, or alternate which OS is shown first in each section.
- Provide Linux scripting examples (e.g., Bash scripts for automation) similar to the PowerShell examples for Windows.
- Expand Linux sections to include more detail on automation, logging, and troubleshooting, matching the depth of Windows content.
- Include references to Linux configuration management tools (e.g., Ansible, systemd) where appropriate.
- Ensure parity in troubleshooting and advanced configuration guidance for Linux users.
Azure Arc
How to migrate from legacy Log Analytics agents in non-Azure environments with Azure Arc
...in/articles/azure-arc/servers/migrate-legacy-agents.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and deployment methods (Windows Admin Center, Windows Server Graphical Installer) are mentioned explicitly, while equivalent Linux tools or graphical installers are not referenced. Windows deployment options are listed before Linux alternatives, and the only standalone agent installation example is for Windows clients, with no mention of Linux client equivalents. Although Bash and Ansible are referenced, concrete Linux-centric examples or instructions are missing.
Recommendations
- Add explicit Linux deployment examples, such as using Bash scripts, Ansible playbooks, or Linux package managers (e.g., apt, yum) for agent installation.
- Include graphical or interactive deployment options for Linux (if available), or clarify that such options do not exist.
- Provide standalone Azure Monitor Agent installation guidance for Linux client machines, or state if unsupported.
- Ensure that deployment instructions and examples are presented in a platform-neutral order or grouped by OS for clarity.
- Reference Linux-specific management tools (e.g., Cockpit) if relevant, or clarify their absence.
Azure Arc
Connect hybrid machines to Azure using a deployment script
...blob/main/articles/azure-arc/servers/onboard-portal.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page presents Windows installation and validation steps before Linux, provides more detailed instructions for Windows (including explicit use of PowerShell and Windows Installer tools), and references Windows-specific tools and command-line options. PowerShell is highlighted as the required shell for the scripted method on Windows, while the Linux section is somewhat shorter and less detailed. The Windows section includes more troubleshooting and log location details, and references to Msiexec and environment variable management are Windows-centric.
Recommendations
- Present Windows and Linux instructions in parallel or alternate the order to avoid Windows-first bias.
- Expand Linux instructions to match the detail level of Windows, including troubleshooting, log locations, and command-line options.
- Include equivalent Linux commands and tools where Windows-specific ones are mentioned (e.g., environment variable management, installer options).
- Provide parity in examples for proxy setup, agent configuration, and script execution.
- Clarify any differences in script capabilities or limitations between platforms.
Azure Arc
Enable VM Extensions Using the Azure CLI (Windows and Linux)
...articles/azure-arc/servers/manage-vm-extensions-cli.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Most example commands for enabling and updating VM extensions use PowerShell-specific syntax (e.g., powershell.exe and PowerShell cmdlets in the Custom Script Extension), and extension types and settings are frequently Windows-centric (e.g., IaaSAntimalware, DatadogWindowsAgent, DependencyAgentWindows). There is a lack of Linux-specific examples, such as Bash scripts or Linux extension types, and Windows tools/patterns are referenced more prominently and exclusively in examples.
Recommendations
- Provide parallel Linux examples for Custom Script Extension, using Bash or shell commands instead of PowerShell.
- Include extension examples for Linux-specific extensions (e.g., DependencyAgentLinux, DatadogLinuxAgent, KeyVaultForLinux).
- Alternate the order of examples so that Linux and Windows are equally represented and neither is always shown first.
- Explicitly mention differences in extension types and settings between Windows and Linux, and link to relevant Linux documentation.
- Add notes or tips for Linux/macOS users regarding command syntax, file paths, and shell differences.
Azure Arc
Enable VM Extensions Using Azure Resource Manager Template
...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation exhibits a notable Windows bias by exclusively providing PowerShell deployment commands, referencing Windows file paths in examples, and omitting equivalent Azure CLI or Bash instructions for Linux/macOS users. While ARM template samples are provided for both Linux and Windows VM extensions, the deployment workflow is centered around PowerShell, which is native to Windows. This creates friction for Linux/macOS users who may prefer or require Azure CLI or Bash-based deployment methods.
Recommendations
- Add Azure CLI and/or Bash examples for deploying ARM templates, especially for Linux/macOS users.
- Present deployment commands for both PowerShell and Azure CLI, ideally side-by-side.
- Use platform-neutral file path examples (e.g., /home/user/Templates or relative paths) alongside Windows paths.
- Explicitly mention cross-platform options and clarify that PowerShell Core is available on Linux/macOS, but Azure CLI is often preferred.
- In the 'Related content' section, surface links to Azure CLI documentation more prominently.
Azure Arc
How to modernize server management from Configuration Manager to Azure Arc
...icles/azure-arc/servers/modernize-server-management.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates mild Windows bias by referencing Windows-specific licensing and onboarding patterns (Scheduled Task, Windows Server Software Assurance) before Linux equivalents, and by lacking explicit Linux onboarding examples. While the page states that Azure Arc supports Linux and lists supported distributions, practical guidance and examples are Windows-centric, with no step-by-step instructions or tooling recommendations for Linux users. Windows tools and terminology (SCCM, SCVMM, SCOM, Scheduled Task) are mentioned exclusively or first, and Linux onboarding and management scenarios are not illustrated.
Recommendations
- Add explicit onboarding instructions for Linux servers, including example commands for agent installation (e.g., using systemd, cron, or shell scripts).
- Provide Linux-specific examples for common management tasks (patching, configuration, reporting, security, scripting).
- Mention Linux equivalents to Windows tools (e.g., cron instead of Scheduled Task) and clarify cross-platform steps.
- Include screenshots or walkthroughs for Linux environments in addition to Windows.
- Ensure that references to licensing and onboarding cover both Windows and Linux scenarios equally.
Azure Arc
Connect hybrid machines to Azure at scale
...rticles/azure-arc/servers/onboard-service-principal.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides both Windows and Linux options for connecting hybrid machines to Azure Arc, but there is a noticeable Windows bias. Windows tools (PowerShell, Windows-specific CLI install links) are often mentioned first, and PowerShell examples are given in detail, while Linux-specific command-line examples are less emphasized. The troubleshooting section and some notes are Windows-centric, and the agent installation script section explicitly calls out Windows PowerShell limitations without similar Linux caveats. There is a lack of parity in example depth and troubleshooting for Linux users.
Recommendations
- Present Linux and Windows options in parallel, rather than listing Windows first.
- Provide equally detailed Linux shell (bash) examples alongside PowerShell examples, including troubleshooting steps.
- Add Linux-specific notes and caveats where relevant, similar to the Windows PowerShell note.
- Ensure that all tool references (CLI, portal, scripts) are equally accessible and explained for Linux users.
- Include screenshots or walkthroughs for Linux onboarding, not just Windows/portal.
Azure Arc
How to organize and inventory servers using hierarchies, tagging, and reporting
...ticles/azure-arc/servers/organize-inventory-servers.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation describes organizational and inventory features for Azure Arc-enabled servers, emphasizing platform-agnostic support. However, practical examples and tooling references (e.g., Azure CLI, PowerShell, ARM templates) are presented generically or with a subtle Windows-first bias. There are no explicit Linux/macOS command-line examples, nor are Linux-specific patterns or tools mentioned. The absence of Linux/macOS examples and the implicit prioritization of Windows-centric tools may create friction for non-Windows users.
Recommendations
- Include explicit Linux/macOS command-line examples for tagging and querying resources (e.g., bash, shell scripts).
- Mention Linux-native tools or patterns where relevant, such as using Azure CLI from bash or integrating with Linux configuration management tools.
- Ensure that references to Azure PowerShell are balanced with Azure CLI examples, noting CLI's cross-platform nature.
- Add a section or callout highlighting Linux-specific considerations or best practices for Arc-enabled server management.
Azure Arc
Connected Machine agent prerequisites
.../blob/main/articles/azure-arc/servers/prerequisites.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific instructions, examples, and tooling (e.g., PowerShell scripts, Group Policy Editor) are presented in detail, while Linux equivalents are either omitted or given less prominence. Windows onboarding scripts are explained with explicit commands and troubleshooting, whereas Linux onboarding is described as straightforward with no example commands or troubleshooting guidance. Windows tools (gpedit.msc, Group Policy) are referenced without Linux analogs. In sections where both platforms are relevant, Windows instructions are often given first or exclusively.
Recommendations
- Provide Linux onboarding script examples, including how to specify agent versions for limited support OSes.
- Include troubleshooting steps for Linux installations, similar to the Windows Group Policy guidance.
- Add parity for system configuration checks on Linux (e.g., how to verify required services and permissions).
- Balance the order of presentation so Linux instructions/examples are given equal prominence to Windows.
- Reference Linux tools and configuration files where relevant (e.g., systemd service management, sudoers for permissions).
Azure Arc
Connect machines from Azure Automation Update Management
...zure-arc/servers/onboard-update-management-machines.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation describes onboarding both Windows and Linux machines to Azure Arc via Automation Update Management, but operational details and examples (e.g., runbook job status retrieval) reference Azure PowerShell and Windows-centric tools first or exclusively. There are no explicit Linux command-line examples or references to Linux-native tooling, and the runbook naming conventions (Add-UMMachinesToArcWindowsChild, Add-UMMachinesToArcLinuxChild) are mentioned, but no Linux-specific steps or screenshots are provided. The verification and troubleshooting steps are portal-centric, with no Linux CLI parity.
Recommendations
- Include Linux command-line examples for verifying agent installation and connection (e.g., using Bash, systemctl, journalctl).
- Reference Linux-native tools (such as shell scripts or CLI commands) alongside PowerShell for runbook job status retrieval.
- Provide screenshots or walkthroughs for Linux environments, not just portal-based verification.
- Explicitly mention any Linux-specific considerations or troubleshooting steps.
- Ensure that Linux onboarding steps are described with equal detail as Windows steps.
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
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on Windows Server 2012/2012 R2, as the ESU program and Azure Arc onboarding are described exclusively for Windows environments. All examples, tools, and deployment options (e.g., Group Policy, Configuration Manager, SCVMM) are Windows-centric, with no mention of Linux or macOS equivalents or scenarios. There are no Linux-specific onboarding instructions, examples, or troubleshooting notes, and Windows tools and patterns are referenced without alternatives.
Recommendations
- Explicitly state that the ESU program described is only for Windows Server 2012/2012 R2, and clarify if Linux/macOS servers are out of scope.
- If Azure Arc onboarding is supported for Linux servers (even if not for ESUs), provide parallel examples or links for Linux onboarding and management.
- Where Windows tools (e.g., Group Policy, Configuration Manager) are mentioned, note their Windows specificity and suggest Linux alternatives for general Azure Arc onboarding if available.
- Add a section or note addressing Linux/macOS users, clarifying what is and isn't supported, and linking to relevant Linux documentation if applicable.
- For certificate installation and agent deployment, provide Linux command-line examples or reference Linux documentation if those scenarios are supported.
Azure Arc
Azure CLI Requests for the Run Command on Azure Arc-enabled Servers (Preview)
...lob/main/articles/azure-arc/servers/run-command-cli.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page provides only PowerShell/Windows-style script examples (e.g., 'Write-Host Hello World!') when demonstrating Azure CLI usage, without any Linux shell (bash/sh) script examples. This may confuse or exclude Linux/macOS users, as it is unclear how to use the feature with bash scripts. The terminology and scripting patterns are Windows-centric.
Recommendations
- Provide parallel Linux/bash shell script examples (e.g., --script "echo Hello World!") alongside PowerShell examples.
- Explicitly state that both PowerShell and bash scripts are supported, if applicable, and clarify any OS-specific behaviors.
- Add a section or table showing example scripts for both Windows and Linux Arc-enabled servers.
- Avoid using only Windows scripting constructs (like Write-Host) in generic CLI documentation.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a notable Windows bias. Azure Machine Configuration is described as PowerShell DSC-based, with no mention of Linux-native configuration tools or examples. Windows Admin Center (WAC) is highlighted as a primary remote management tool, with a dedicated section and detailed explanation, while Linux management is only briefly mentioned in the context of SSH. Examples and tooling references (PowerShell, WAC) are Windows-centric, and there are no Linux-specific configuration or remote access examples (e.g., using Ansible, SSH command-line, or Linux admin tools). Windows scenarios and tools are described in greater detail and appear before Linux equivalents.
Recommendations
- Add Linux-native configuration examples, such as using Ansible, Chef, or native SSH commands.
- Provide parity in remote management tooling by mentioning Linux equivalents to Windows Admin Center, or clarify how Linux servers are managed interactively.
- Include Linux-specific RBAC role assignment and authentication flows, with step-by-step examples.
- Balance the order and detail of Windows and Linux sections to ensure equal visibility and guidance.
- Explicitly state PowerShell DSC limitations or alternatives for Linux environments.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-specific concepts (such as NT SERVICE accounts, Local System, Network Service) before their Linux equivalents, and describes guest configuration policies as being written in PowerShell Desired State Configuration without mentioning Linux alternatives. The example extension allowlist references only Windows agents, and there are no explicit Linux/macOS command or extension examples. The documentation also uses Windows terminology and patterns first, with Linux details as secondary notes.
Recommendations
- Provide explicit Linux/macOS examples alongside Windows ones, especially for extension allowlists and agent configuration.
- Mention Linux equivalents for guest configuration policies, such as Ansible or native Linux configuration management tools, if supported.
- Include Linux/macOS agent extension IDs in allowlist examples.
- Clarify whether PowerShell Desired State Configuration is required on Linux, or if there are alternative mechanisms.
- Balance terminology by listing Linux service accounts and patterns before or alongside Windows ones.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools and patterns (Group Policy, WSUS, Microsoft Update) are mentioned before or in more detail than their Linux equivalents. PowerShell is referenced for extension management and onboarding, with no equivalent Linux shell examples. Some onboarding methods are described as Windows-only, and links to Windows-specific guidance are provided, while Linux automation tools (e.g., Ansible) are only briefly mentioned. Linux update mechanisms are covered, but with less detail and fewer actionable examples.
Recommendations
- Provide Linux shell (bash) examples alongside PowerShell for onboarding and extension management tasks.
- Include links to Linux-specific onboarding and automation guidance, similar to the Group Policy onboarding link for Windows.
- Expand coverage of Linux automation tools (e.g., Ansible, Chef, Puppet) with concrete examples for protecting secrets and orchestrating onboarding.
- Present update management instructions for Linux (e.g., using apt/yum/zypper) with step-by-step guidance, not just a brief mention.
- Ensure that Linux tools and patterns are described with equal detail and prominence as Windows tools.
- Where features are Windows-only (e.g., interactive logon via local browser), clearly state Linux alternatives or workarounds.
Azure Arc
Troubleshoot SSH access to Azure Arc-enabled servers
...ain/articles/azure-arc/servers/ssh-arc-troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page demonstrates a notable Windows bias. Troubleshooting steps and examples frequently reference Azure PowerShell modules (Az.Ssh, Az.Ssh.ArcProxy) and provide PowerShell commands for module management and error resolution. The guidance for resolving client-side issues is centered around PowerShell and Windows-specific error messages, with Linux equivalents mentioned less prominently or only as error output. Examples for enabling SSH on the server are given for both Azure CLI and PowerShell, but PowerShell is emphasized throughout the document. There is limited coverage of Linux/macOS workflows, and no explicit Linux/macOS installation or troubleshooting steps for the Azure CLI or SSH client tools are provided.
Recommendations
- Add explicit Linux/macOS troubleshooting steps, including installation and path configuration for SSH clients and Azure CLI.
- Provide Linux/macOS-specific error messages and their resolutions alongside Windows/PowerShell examples.
- Include Bash or shell command alternatives for PowerShell module management and SSH connectivity.
- Ensure examples and instructions for Azure CLI are shown before or alongside PowerShell, not after.
- Clarify which steps are platform-agnostic and which are platform-specific, and provide parity for both.
Azure Arc
Tutorial - Monitor a hybrid machine with Azure Monitor VM insights
...icles/azure-arc/servers/tutorial-enable-vm-insights.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides a general tutorial for enabling VM insights on hybrid machines, claiming support for both Linux and Windows. However, when discussing log events, it only references the Windows event log and does not provide equivalent Linux log examples (e.g., syslog). The Event table is described as containing Windows event log data, with no mention of Linux log sources or queries. There are no Linux-specific screenshots, examples, or instructions, and Windows terminology (event log) is used exclusively in the data viewing section.
Recommendations
- Add explicit examples and screenshots for Linux machines, showing how Linux logs (such as syslog or journald) are collected and queried.
- Clarify what tables and data are available for Linux machines in Log Analytics, and provide sample queries.
- Use neutral terminology when describing log events (e.g., 'system logs') and mention both Windows and Linux sources.
- Ensure parity in instructions and visuals for both platforms throughout the tutorial.
Azure Arc
Overview of the Azure Arc-enabled System Center Virtual Machine Manager
...-arc/system-center-virtual-machine-manager/overview.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. It focuses on System Center Virtual Machine Manager (SCVMM), a Windows-only tool, and repeatedly references Windows-specific management features (e.g., Windows Server management, Windows registry, Windows services). PowerShell is mentioned as a primary automation tool, and Windows-centric update and configuration scenarios are highlighted before Linux equivalents. Linux support is mentioned but not detailed, and examples or guidance for Linux users are minimal or absent.
Recommendations
- Add explicit examples and guidance for Linux VM management, including onboarding, configuration, and monitoring steps.
- Provide parity in automation examples (e.g., Bash, Python scripts for Linux alongside PowerShell for Windows).
- Highlight Linux-specific features and scenarios where applicable, such as Linux daemon management, package updates, and security hardening.
- Clarify which features are Windows-only and which are cross-platform, to help Linux/macOS users understand applicability.
- Include links to Linux-focused documentation and best practices for hybrid management.
Azure Arc
Create custom roles with Azure Arc-enabled SCVMM
...-center-virtual-machine-manager/create-custom-roles.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation focuses on Azure Arc-enabled SCVMM, a Windows-centric virtualization manager, and describes custom role creation exclusively through the Azure portal. While it mentions Azure PowerShell and Azure CLI as alternatives, the main instructions and screenshots are portal-based, which is platform-neutral but implicitly Windows-oriented due to SCVMM's Windows-only nature. There are no Linux/macOS-specific examples or guidance, and the documentation does not address cross-platform considerations for CLI or scripting.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide CLI examples for custom role creation.
- Clarify any platform requirements for SCVMM and role management, especially for users on Linux/macOS.
- Add a section comparing Azure PowerShell and Azure CLI usage for custom roles, highlighting Linux/macOS compatibility.
- Include links or references to Linux/macOS setup guides for Azure CLI.
- State limitations for non-Windows users, if any, and suggest workarounds.
Azure Arc
Deliver ESUs for SCVMM VMs through Arc
...ver-esus-for-system-center-virtual-machine-manager-vms.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on Windows Server 2012/2012 R2 VMs managed by SCVMM, with all examples, terminology, and processes centered around Windows environments. Windows-specific tools (SCVMM, WSUS, Microsoft Endpoint Configuration Manager) are mentioned exclusively or before alternatives, and there are no Linux/macOS examples or guidance for non-Windows VMs. The documentation does not address how Linux or macOS VMs could participate in ESU delivery or management through Arc in this scenario.
Recommendations
- Clarify early in the documentation that the process is specific to Windows Server 2012/2012 R2 and SCVMM-managed VMs, and explicitly state that Linux/macOS VMs are not supported for ESU delivery in this workflow.
- If Azure Arc supports similar patching or management workflows for Linux/macOS VMs, provide links or references to those workflows for parity.
- When listing patch management solutions, mention Linux-compatible options (e.g., Ansible, Chef, native Linux update tools) and clarify their applicability.
- Consider adding a section or FAQ addressing Linux/macOS scenarios, even if only to state their exclusion and suggest alternatives.
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation exhibits a moderate Windows bias: Windows operating systems and tools are mentioned first and more prominently, especially in the Azure portal section, which is only available for Windows VMs. Windows-specific tools like PowerShell and Group Policy are referenced before Linux equivalents. However, Linux support is present via scripts and Ansible, and Linux instructions are included in the manual installation section.
Recommendations
- Explicitly state Linux support and parity in the introduction and relevant sections.
- Provide Linux examples and instructions alongside Windows, not after or as exceptions.
- List Linux automation tools (e.g., Ansible, shell scripts) before or alongside Windows tools (e.g., PowerShell, Group Policy) in out-of-band methods.
- Clarify which features are Windows-only and offer alternative workflows for Linux users.
- Add screenshots and walkthroughs for Linux VM onboarding where possible.
Azure Arc
Quickstart for Azure Arc-enabled System Center Virtual Machine Manager (SCVMM)
...t-connect-system-center-virtual-machine-manager-to-arc.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, WinRM, tar.exe, archiveint.dll) are discussed in detail, and Windows instructions are presented before Linux equivalents. Prerequisites and troubleshooting focus on Windows environments, with Linux guidance being less detailed and sometimes described as slower or less performant. Some steps, such as copying tar.exe and archiveint.dll, are only relevant to Windows, and there is no mention of Linux alternatives or troubleshooting steps for Linux users.
Recommendations
- Provide Linux-first or side-by-side examples for all steps, including troubleshooting and prerequisites.
- Offer detailed Linux prerequisites (e.g., required packages, permissions, dependencies) and troubleshooting guidance.
- Avoid language that discourages Linux usage (e.g., 'deployment takes a bit longer'), or provide actionable advice to mitigate performance issues.
- List Linux tools and commands where Windows tools are mentioned (e.g., alternatives to WinRM, tar.exe, archiveint.dll).
- Ensure parity in script functionality and documentation for both PowerShell and Bash versions.
Azure Arc
Support matrix for Azure Arc-enabled System Center Virtual Machine Manager
...pport-matrix-for-system-center-virtual-machine-manager.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. Windows Server and SCVMM (a Windows-only product) are naturally central, but the page repeatedly references Windows-specific tools and patterns (e.g., WinRM, Windows Management Framework, PowerShell/Win32-OpenSSH), and provides more detail for Windows environments. Linux is mentioned only in passing, with minimal guidance and no concrete examples or parity in troubleshooting or deployment steps. The only Linux-specific note is that deployments from Linux workstations may be slower, but no Linux-specific instructions or optimizations are provided.
Recommendations
- Provide explicit Linux workstation deployment instructions, including any required dependencies, troubleshooting steps, and performance tips.
- Where Windows-specific tools (e.g., WinRM, Windows Management Framework) are mentioned, clarify their Linux equivalents or note if not applicable.
- Include Linux examples or callouts wherever scripts or commands are referenced, especially for onboarding and agent installation.
- Balance the order of presentation so that Linux and Windows requirements/examples are given equal prominence.
- Clarify any limitations or differences for Linux users up front, and link to relevant Linux documentation where possible.
Azure Arc
Deliver ESUs for VMware VMs through Arc
...r-extended-security-updates-for-vmware-vms-through-arc.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is exclusively focused on managing Extended Security Updates (ESUs) for Windows Server 2012/2012 R2 VMs via Azure Arc on VMware vSphere. All examples, screenshots, and instructions pertain to Windows Server environments, with no mention of Linux VMs, Linux patching tools, or cross-platform considerations. Windows-centric patching solutions (WSUS, Microsoft Updates, Configuration Manager) are referenced, while Linux equivalents are absent.
Recommendations
- Clarify early in the document that the ESU process described is Windows-specific, and note whether Linux VMs are supported or not.
- If Azure Arc supports similar update management for Linux VMs, add parallel instructions and examples for Linux environments.
- Reference Linux patch management solutions (e.g., Azure Update Manager for Linux, third-party Linux patching tools) where appropriate.
- Include a section or note about ESU applicability to non-Windows operating systems, if relevant.
- Ensure screenshots and UI descriptions indicate OS scope (e.g., 'Windows Server VMs only').
Azure Arc
What's new in Azure Arc-enabled SCVMM
...arc/system-center-virtual-machine-manager/whats-new.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation page for Azure Arc-enabled SCVMM exhibits a moderate Windows bias. Windows-centric tools (SCVMM, PowerShell, Windows Server Management, Group Policy, System Center Configuration Manager) are mentioned exclusively or before Linux alternatives. Examples and features are often described in terms of Windows tooling, with Linux-native approaches (e.g., Ansible) only occasionally referenced and never prioritized. There are no explicit Linux/macOS examples or instructions, and the documentation assumes familiarity with Windows environments.
Recommendations
- Add explicit Linux/macOS examples for agent installation and VM management, such as shell scripts, systemd unit files, or Linux-native automation tools.
- Include parity in documentation for Linux-based VM management, e.g., using Azure CLI, REST API, or SDKs on Linux.
- Mention Linux equivalents alongside Windows tools (e.g., contrast Group Policy with Linux configuration management tools).
- Provide guidance for integrating SCVMM with Linux VMs or hybrid environments, if supported.
- Ensure that cross-platform automation tools (like Ansible) are given equal prominence and detailed examples.
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page presents Windows agent installation details before Linux, with more granular information about Windows-specific tools, services, accounts, and troubleshooting paths. Windows terminology (MSI, Group Policy, NT SERVICE accounts) is emphasized, and Windows examples (directory paths, service names) are listed first. Linux instructions are present and reasonably detailed, but the overall structure and depth favor Windows, which may create friction for Linux users seeking parity.
Recommendations
- Present Linux and Windows agent installation details in parallel sections or alternate which OS is described first.
- Provide equivalent depth for Linux, including details on service accounts, security groups, and troubleshooting steps.
- Include Linux-specific tips for permissions, service management (systemd), and log file analysis.
- Avoid Windows-centric terminology (e.g., MSI, Group Policy) without Linux equivalents or explanations.
- Ensure all examples (paths, commands) are shown for both platforms, and highlight differences clearly.
Azure Arc
Install Arc agent at scale for your VMware VMs
...arc/vmware-vsphere/enable-guest-management-at-scale.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. The primary automation script is a PowerShell script, with instructions and examples focused on Windows environments (PowerShell terminal, Windows Task Scheduler for cron jobs). There is no equivalent Linux shell script or example for running at scale on Linux/macOS, nor are Linux scheduling tools (like cron) mentioned. Out-of-band methods reference Ansible (Linux-friendly), but most step-by-step guidance and examples are Windows-centric, with Linux-specific instructions limited to a sudo configuration note.
Recommendations
- Provide a Bash or Python script equivalent for Linux/macOS users, with usage instructions.
- Include examples for running the automation script on Linux (e.g., using cron, shell commands).
- Mention Linux-native scheduling tools (cron, systemd timers) alongside Windows Task Scheduler.
- Ensure all automation steps and prerequisites are covered for both Windows and Linux environments.
- Present examples for both platforms in parallel, or clearly indicate platform-specific instructions.
Azure Arc
Clean-Up Script for Workload Orchestration
...es/azure-arc/workload-orchestration/clean-up-script.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively provides instructions and examples for running a PowerShell script (RGCleanScript.ps1) to clean up Azure resources. All usage examples are in PowerShell syntax, and there is no mention of Linux/macOS-compatible alternatives (such as Bash scripts or cross-platform instructions). The documentation assumes the user is on Windows or has PowerShell available, which may not be the case for many Linux/macOS users.
Recommendations
- Provide equivalent Bash or shell script examples for Linux/macOS users.
- Clarify whether the PowerShell script can be run using PowerShell Core (pwsh) on Linux/macOS, and provide instructions for doing so.
- Offer guidance on installing PowerShell on non-Windows platforms if the script is not available in another format.
- Consider providing a cross-platform script (e.g., written in Python or Bash) or instructions for using Azure CLI directly for resource cleanup.
- Explicitly state platform compatibility and any prerequisites for non-Windows environments.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific management features (e.g., Windows Server management, Extended Security Updates for Windows Server and SQL Server) are highlighted, and Windows tools (PowerShell, Windows registry, Windows-specific tabs/links) are mentioned before or more prominently than their Linux equivalents. While Linux is referenced in some scenarios (e.g., Azure Update Manager, VM extensions), examples and links often default to Windows, and Linux-specific instructions or parity are less visible or absent.
Recommendations
- Provide explicit Linux/macOS examples and instructions alongside Windows ones, especially for agent installation, automation, and VM extension management.
- Ensure links and tabs (e.g., for Azure Automation, VM extensions) include Linux-focused content and are not Windows-default.
- Highlight Linux management features and benefits equally with Windows, including security, update, and monitoring scenarios.
- Include CLI/bash examples and Linux-native automation tools (e.g., shell scripts) where PowerShell is referenced.
- Clarify any limitations or differences for Linux/macOS users in supported scenarios and next steps.
Medium Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, .NET Framework) are explicitly listed as requirements, while Linux requirements are more generic. Windows tools are mentioned first and with download links, whereas Linux requirements lack similar guidance. No Linux-specific examples or troubleshooting are provided, and Windows-centric URLs (e.g., *.servicebus.windows.net for Windows Admin Center) are highlighted.
Recommendations
- Provide Linux-specific installation instructions and troubleshooting steps, equivalent to the Windows guidance.
- Include download links or package manager commands for Linux prerequisites (e.g., systemd, wget).
- Offer example commands for both Windows (PowerShell) and Linux (bash/shell) when referencing onboarding scripts or agent installation.
- Balance the order of presentation so Linux requirements/examples are not always listed after Windows.
- Clarify which URLs are relevant for Linux scenarios (e.g., SSH) versus Windows Admin Center.
Azure Arc
Bulk Review, Publish, and Deploy with Workload Orchestration
...es/azure-arc/workload-orchestration/bulk-deployment.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation consistently uses PowerShell syntax for CLI commands and references PowerShell scripts (.ps1) for automation, without providing Bash or shell script equivalents. There is no mention of Linux/macOS-specific instructions, and all examples and automation scripts are Windows-centric, creating friction for users on non-Windows platforms.
Recommendations
- Provide CLI command examples in Bash syntax alongside PowerShell, especially for az CLI commands.
- Offer equivalent shell scripts (e.g., bulk_deployment.sh) for Linux/macOS users, or document how to run the provided .ps1 scripts using cross-platform tools like PowerShell Core.
- Explicitly state platform compatibility for scripts and commands, and provide troubleshooting or installation guidance for Linux/macOS environments.
- Ensure documentation sections do not assume Windows-first usage; alternate examples should be shown for Linux/macOS where relevant.
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation exhibits Windows bias primarily in the file extraction step, where only Windows-specific tools (Expand-Archive, winget) are referenced and no Linux/macOS alternatives (such as unzip, tar, or Homebrew) are provided. The examples for extracting ZIP files and installing kubectl use Windows-centric commands and tools, which may not work on Linux/macOS. Additionally, the Bash tab for extracting ZIP files incorrectly uses Expand-Archive (a PowerShell/Windows command), further confusing Linux/macOS users. The ordering of examples sometimes places Windows tools first or exclusively.
Recommendations
- Add Linux/macOS-specific instructions for extracting ZIP files (e.g., 'unzip archive.zip -d /path/to/folder').
- Provide alternative installation methods for kubectl for Linux/macOS (e.g., curl, apt, yum, Homebrew).
- Ensure Bash examples use cross-platform commands and avoid Windows-only tools.
- Clearly separate Windows/PowerShell and Linux/macOS instructions, and provide parity in all steps.
- Review and correct any Bash tabs that use Windows-only commands.
Azure Arc
Migrate Existing Target Resources to General Availability
...s/azure-arc/workload-orchestration/migration-script.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation provides only a PowerShell migration script example, assumes use of PowerShell, and does not mention or provide equivalent instructions for Linux/macOS users (e.g., Bash or cross-platform scripting). The migration process appears Windows-centric, creating friction for non-Windows users.
Recommendations
- Provide a Bash or shell script alternative for Linux/macOS users.
- Clarify whether the PowerShell script can be run with PowerShell Core on Linux/macOS, and provide instructions for doing so if possible.
- Explicitly mention cross-platform compatibility or limitations of the migration script.
- Include Linux/macOS command-line examples and usage notes alongside Windows/PowerShell instructions.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page predominantly provides CLI examples using PowerShell syntax, especially in the May 2025 release section, without offering equivalent Bash or Linux/macOS shell examples. While most CLI instructions use the Azure CLI (which is cross-platform), the explicit use of PowerShell syntax (backticks for line continuation, $variable notation) is Windows-centric and may confuse Linux/macOS users. No Linux/macOS-specific instructions or examples are provided, and Windows-style examples are presented first and exclusively where scripting is shown.
Recommendations
- Provide Bash/Linux/macOS shell examples alongside PowerShell examples for all CLI commands, especially where line continuation or variable usage is shown.
- Add a note clarifying that Azure CLI is cross-platform and provide guidance for Linux/macOS users on adapting examples (e.g., using \ for line continuation, $VAR for variables).
- Where possible, alternate the order of examples so Linux/macOS instructions are not always secondary or missing.
- Explicitly mention platform compatibility for all CLI commands and extensions.
Azure Portal
Create an Azure portal dashboard by using a Bicep file
.../blob/main/articles/azure-portal/quick-create-bicep.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows by exclusively deploying a Windows VM ('SimpleWinVM'), referencing Windows-specific username/password requirements, and linking only to Windows VM documentation. The examples and scripts use Azure CLI and PowerShell, which are cross-platform, but the VM deployment and supporting links are Windows-centric. There are no examples or notes for deploying a Linux VM, nor are Linux username/password requirements or Linux VM documentation referenced.
Recommendations
- Provide an alternative example that deploys a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
- Include links to Linux VM documentation for username and password requirements.
- Clarify that the Azure CLI and PowerShell examples work on Linux/macOS, and show any OS-specific differences if relevant.
- Use a more neutral VM name (e.g., 'SimpleVM') and parameterize the OS type in the Bicep/ARM template.
- Add a note explaining how Linux users can adapt the example for their preferred OS.
Azure Portal
Create an Azure portal dashboard with Azure CLI
.../azure-portal/quickstart-portal-dashboard-azure-cli.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing a VM creation example using a Windows image ('win2016datacenter') and referencing Windows-specific username/password requirements. There are no examples or guidance for creating Linux VMs, nor are Linux-specific requirements or considerations mentioned. All CLI commands themselves are cross-platform, but the resource examples and supporting notes focus solely on Windows.
Recommendations
- Add a parallel example for creating a Linux VM (e.g., using '--image UbuntuLTS'), including Linux-specific username and password requirements.
- Reference both Windows and Linux VM documentation for further information.
- Clarify that the dashboard template and Azure CLI commands work with both Windows and Linux VMs.
- Consider alternating or balancing examples so that Linux users see their platform represented equally.
Azure Portal
Create an Azure portal dashboard by using an Azure Resource Manager template
...ob/main/articles/azure-portal/quick-create-template.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a notable Windows bias. The only example for creating the required VM uses Azure PowerShell commands, with explicit instructions to select PowerShell in Cloud Shell. The resource group and VM naming conventions (e.g., 'SimpleWinVmResourceGroup', 'myVM1') and referenced documentation (Windows username/password requirements) further reinforce a Windows-centric approach. No Bash/Azure CLI examples are provided for Linux/macOS users, and the VM creation steps are tailored to Windows environments.
Recommendations
- Provide equivalent Azure CLI (Bash) commands for VM and resource group creation, suitable for Linux/macOS users.
- Mention that Cloud Shell supports both PowerShell and Bash, and offer users a choice.
- Reference Linux VM documentation and requirements alongside Windows, especially for username/password guidance.
- Use more neutral resource group and VM names (e.g., 'SimpleVmResourceGroup') to avoid implying Windows-only scenarios.
- Ensure all critical steps (e.g., VM creation) have cross-platform instructions.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell throughout, but PowerShell is a Windows-centric tool and is featured equally alongside CLI. There is a notable Windows bias in the 'Import from Microsoft Container Registry' section, where the only example given is for a Windows Server Core image. There are no explicit Linux/macOS examples (e.g., importing Ubuntu or Alpine images), nor is there mention of Linux-specific patterns or tools. The documentation does not mention platform-specific issues or considerations for Linux/macOS users, and Windows images are highlighted before any Linux equivalents.
Recommendations
- Add examples importing popular Linux images (e.g., Ubuntu, Alpine, nginx) from public registries and Microsoft Container Registry.
- Explicitly state that Azure CLI and PowerShell are cross-platform, but clarify installation and usage differences for Linux/macOS users.
- Include troubleshooting notes or caveats for Linux/macOS environments if any exist.
- Balance examples by alternating between Windows and Linux image imports, or provide both in each relevant section.
- Mention that Azure CLI is natively available on Linux/macOS and provide links to installation guides for those platforms.
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Examples and instructions are frequently given for Azure PowerShell and Azure CLI, with PowerShell examples present throughout. Windows-centric tools and patterns (PowerShell, Azure portal UI) are mentioned before or alongside CLI examples, but Linux/macOS-specific workflows are not explicitly covered. While Docker is referenced as the default container tool, Linux alternatives like Podman are only briefly mentioned near the end, and there are no explicit bash or Linux shell examples. There are no direct instructions for Linux/macOS users on installing prerequisites, handling authentication, or troubleshooting common platform-specific issues.
Recommendations
- Add explicit Linux/macOS shell examples (bash/zsh) for authentication workflows alongside PowerShell.
- Provide installation and troubleshooting guidance for Azure CLI and Docker/Podman on Linux/macOS.
- Include Linux/macOS-specific notes for environment setup, such as file paths, permissions, and common errors.
- Present CLI (cross-platform) examples before PowerShell/Windows-specific ones.
- Expand the section on alternative container tools to include more details and examples for Podman and other Linux-native tools.
- Clarify that all authentication methods work on Linux/macOS, and highlight any platform-specific caveats.
Container Registry
Quickstart - Create Registry - Bicep
...ainer-registry/container-registry-get-started-bicep.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying the Bicep file, but PowerShell is featured as a primary option and is mentioned before Linux alternatives. The instructions reference opening PowerShell or Azure CLI, but do not explicitly mention Bash or Linux/macOS terminals. There are no Linux-specific examples or guidance for users on non-Windows platforms, and the use of Visual Studio Code is suggested without alternatives for Linux/macOS users.
Recommendations
- Explicitly mention Bash or Linux/macOS terminal as an option for running Azure CLI commands.
- Provide Linux/macOS-specific instructions or examples, such as using Bash with Azure CLI.
- Reorder examples so that Azure CLI (cross-platform) is shown before PowerShell.
- Clarify that Visual Studio Code is available on Linux/macOS, or suggest alternative editors for those platforms.
- Add a note or section for Linux/macOS users to ensure parity and inclusivity.
Container Registry
Error Reference for Registry Health Checks
...-registry/container-registry-health-error-reference.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation occasionally references Windows-specific tools and paths (e.g., notary.exe, C:\ProgramFiles\Docker\Docker\resources\bin) and mentions adding executables to 'system variables' without clarifying Linux/macOS equivalents. Windows instructions are sometimes given before Linux/macOS, and there are missing explicit examples for Linux/macOS users regarding environment variable configuration and binary placement.
Recommendations
- For each mention of adding executables to 'system variables', provide explicit Linux/macOS instructions (e.g., updating $PATH in ~/.bashrc or ~/.zshrc).
- When referencing binary installation paths (e.g., Notary), include typical Linux/macOS locations (such as /usr/local/bin) alongside Windows paths.
- Ensure that download and installation instructions for tools like Notary are equally detailed for Linux/macOS, not just referencing Windows .exe files and paths.
- Present cross-platform instructions in parallel, or clarify OS-specific steps, rather than defaulting to Windows-first.
- Where possible, provide command-line examples for both Windows (PowerShell/CMD) and Linux/macOS (bash/zsh).
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_tools
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but PowerShell is a Windows-centric tool and is presented as a primary tab. There is no explicit mention of Linux/macOS-specific instructions or shell environments, and PowerShell is listed before the portal options. No Linux shell (bash, zsh) or cross-platform scripting alternatives are discussed.
Recommendations
- Clarify that Azure CLI works natively on Linux/macOS and provide explicit bash/zsh example usage.
- Add notes or examples for running Azure CLI queries in Linux/macOS terminals, including any OS-specific considerations (e.g., quoting, line breaks).
- If PowerShell is shown, clarify its cross-platform availability, but avoid implying it is required for Linux/macOS users.
- Consider listing Azure CLI before PowerShell, as CLI is the most cross-platform tool.
- Add troubleshooting or environment setup notes for Linux/macOS users if needed.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. It repeatedly references PowerShell and its module (AIShell), links to PowerShell-specific documentation, and provides no explicit examples or instructions for Linux or macOS users. The installation section only mentions the PowerShell module, and all external links point to PowerShell resources. There are no Bash or Linux-native command examples, nor any mention of platform-specific differences or requirements for non-Windows environments.
Recommendations
- Include explicit instructions and examples for Linux/macOS users, such as Bash shell usage.
- Clarify whether AI Shell can be used outside PowerShell (e.g., in Bash, zsh, etc.), and provide installation steps for those environments.
- Add links to cross-platform or Linux/macOS-specific documentation.
- Ensure command examples alternate between Azure CLI (cross-platform) and PowerShell, or show both side-by-side.
- Mention any platform-specific requirements or limitations.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is referenced as the primary example for creating registration definitions, with no equivalent Azure CLI or REST API example shown inline. Windows tooling (PowerShell cmdlets) is mentioned before Linux-friendly alternatives, and there are no explicit Linux/macOS instructions or examples for onboarding or resource management tasks.
Recommendations
- Add explicit Azure CLI examples for creating registration definitions and assignments alongside PowerShell examples.
- Reference REST API methods for resource creation and management to ensure cross-platform accessibility.
- Ensure that CLI and API instructions are presented before or alongside PowerShell examples, not after.
- Include notes or links for Linux/macOS users on how to install and use Azure CLI for these tasks.
Lighthouse
Monitor delegated resources at scale
...ob/main/articles/lighthouse/how-to/monitor-at-scale.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a notable Windows bias, particularly in the section on registering resource providers in the managing tenant, where only Azure PowerShell commands are provided. There is no mention of equivalent Azure CLI or Bash examples, nor are Linux/macOS automation patterns discussed. Windows tools and PowerShell are referenced exclusively and before any cross-platform alternatives, which may create friction for Linux/macOS users.
Recommendations
- Provide Azure CLI examples alongside PowerShell for resource provider registration and service principal creation.
- Explicitly mention that Azure CLI and Bash can be used for automation tasks, and link to relevant documentation.
- Reorder examples or provide both Windows and Linux/macOS instructions in parallel, ensuring parity.
- Clarify which steps are platform-agnostic and which require specific OS tools, offering alternatives where possible.
Copilot
Optimization agent capabilities in Agents (preview) in Azure Copilot
...-docs/blob/main/articles/copilot/optimization-agent.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page shows a moderate Windows bias. PowerShell is explicitly mentioned in sample prompts before Azure CLI, and the example prompt specifically asks for a PowerShell script, with CLI mentioned only generically. No Linux/macOS-specific instructions, examples, or considerations are provided, and there is no mention of Bash or shell scripting. The documentation assumes familiarity with PowerShell, which is primarily a Windows tool, and does not provide parity for Linux/macOS users.
Recommendations
- Add explicit Bash or shell script examples alongside PowerShell and Azure CLI.
- When listing script generation options, mention Azure CLI and Bash equally with PowerShell.
- Provide sample prompts that request Bash or CLI scripts, not just PowerShell.
- Clarify that Azure CLI works cross-platform and provide guidance for Linux/macOS users.
- Consider the order of examples: alternate or randomize PowerShell and CLI/Bash to avoid Windows-first bias.
Lighthouse
Monitor delegation changes in your managing tenant
...ticles/lighthouse/how-to/monitor-delegation-changes.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is the primary scripting language shown for querying delegation changes, with a lengthy, complex PowerShell script provided and no equivalent Bash or cross-platform shell example. While Azure CLI is mentioned for role assignment, all advanced querying and reporting examples are PowerShell-only. There is no guidance for Linux/macOS users on how to perform these tasks outside of PowerShell, nor are alternative tools or scripts referenced.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for querying the Tenant Activity Log and reporting delegation changes, ensuring Linux/macOS users can follow along without PowerShell.
- Explicitly note cross-platform options and clarify which commands/tools work on all platforms.
- Reference REST API usage directly with curl or other cross-platform tools, not just via PowerShell.
- Consider reordering examples so that Azure CLI or platform-neutral approaches are presented first or alongside PowerShell.
Lighthouse
Deploy Azure Policy to delegated subscriptions at scale
...lob/main/articles/lighthouse/how-to/policy-at-scale.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively uses PowerShell commands and Azure PowerShell modules for all examples and instructions, without mentioning or providing alternatives for Linux/macOS users (such as Azure CLI or Bash). Windows-centric tools and patterns are referenced throughout, and no Linux/macOS shell or cross-platform instructions are given. This creates friction for users on non-Windows platforms.
Recommendations
- Provide equivalent Azure CLI (az) examples alongside PowerShell commands for all major steps.
- Explicitly mention that Azure PowerShell is available cross-platform, but clarify installation and usage differences for Linux/macOS.
- Include Bash shell script examples where appropriate, especially for loops and resource queries.
- Add a section on platform prerequisites, clarifying support for Linux/macOS and how to set up the required tools.
- Reorder examples or alternate between Windows and Linux/macOS instructions to avoid Windows-first bias.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation lists Azure PowerShell as a primary method for viewing quota usage, with Azure CLI mentioned but not prioritized. No explicit Linux/macOS examples or screenshots are provided, and PowerShell is a Windows-centric tool. The ordering and emphasis may create friction for Linux/macOS users.
Recommendations
- Provide explicit Linux/macOS examples using Azure CLI, including command-line usage and sample outputs.
- List Azure CLI before Azure PowerShell when presenting cross-platform options.
- Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Include screenshots or instructions relevant to Linux/macOS environments where appropriate.
Lighthouse
Onboard all subscriptions in a management group
...articles/lighthouse/how-to/onboard-management-group.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
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/macOS instructions. This creates friction for users on non-Windows platforms, as PowerShell is not the default or preferred tool for many Linux/macOS administrators. The documentation also introduces the PowerShell example before mentioning any alternatives, and does not clarify cross-platform options.
Recommendations
- Add equivalent Azure CLI (az) commands for policy assignment, which are natively supported on Linux/macOS.
- Explicitly state that PowerShell is cross-platform, or link to instructions for installing PowerShell on Linux/macOS if PowerShell must be used.
- Present CLI and PowerShell examples side-by-side, or indicate which tools are available for each platform.
- Include Bash script examples where appropriate, especially for tasks like file editing or deployment.
Azure Arc
Turn on transparent data encryption in SQL Managed Instance enabled by Azure Arc (preview)
...igure-transparent-data-encryption-sql-managed-instance.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_path_notes
Summary
The documentation provides both Windows and Linux examples for file operations (copying certificates/keys), but Windows instructions and caveats are often presented first. There are specific notes about Windows path issues and workarounds, but Linux examples are present and equally detailed. No PowerShell-specific or Windows-only tools are used, and all core tasks can be completed on Linux/macOS. The overall bias is minor, mostly in ordering and emphasis.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Add explicit macOS notes/examples where relevant, as macOS users may have unique path or shell considerations.
- Clarify that all steps are equally supported on Linux/macOS, and avoid language that implies Windows is the default or primary platform.
- Group platform-specific caveats together at the end or in a dedicated section, rather than interspersing them in the main flow.
Low 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. There is a slight emphasis on Windows scripting patterns (SET, .cmd/.bat/.ps1) and Windows tools (Task Scheduler) are mentioned before Linux equivalents (cron). However, Linux/macOS examples are present and functional throughout, and the main CLI commands are cross-platform.
Recommendations
- Alternate the order of example tabs so Linux/macOS is shown first in some sections.
- Explicitly mention Linux/macOS tools (cron, systemd timers) before or alongside Windows Task Scheduler.
- Provide more detailed Linux/macOS automation examples (e.g., sample cron job entry).
- Ensure parity in scripting guidance (e.g., show full .sh script example, not just snippets).
Azure Arc
Built-in policy definitions for Azure Arc-enabled Kubernetes
...main/articles/azure-arc/kubernetes/policy-reference.md
Low Priority
View Details →
Detected Bias Types
none
Summary
The documentation page does not exhibit any Windows bias. It serves as an index of Azure Policy definitions for Azure Arc-enabled Kubernetes and does not contain any OS-specific instructions, examples, or tool references.
Recommendations
No changes needed. The documentation is platform-neutral and accessible to users on Windows, Linux, and macOS.
Azure Arc
Programmatically deploy and manage Azure Arc Extended Security Updates licenses
...les/azure-arc/servers/api-extended-security-updates.md
Low Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is focused exclusively on managing Extended Security Updates licenses for Windows Server 2012, with all examples and API payloads referencing Windows-specific targets. There are no Linux or macOS examples, nor any mention of how Linux users might interact with these APIs or manage similar scenarios. The Azure CLI example is generic and cross-platform, but all usage is Windows-centric.
Recommendations
- Clarify in the introduction that this documentation is specific to Windows Server scenarios.
- If Azure Arc supports similar license management for Linux servers, add equivalent examples and API payloads for Linux.
- Explicitly state platform limitations or scope (e.g., 'These APIs are only for Windows Server ESU management').
- Provide links or references to Linux/macOS documentation for Azure Arc license management, if available.
Azure Arc
License provisioning guidelines for Extended Security Updates for Windows Server 2012
...azure-arc/servers/license-extended-security-updates.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on Windows Server environments, with all examples, scenarios, and licensing models centered around Windows Server 2012 and its variants. There is no mention of Linux or macOS systems, nor any guidance for provisioning ESUs for non-Windows platforms. The tools and patterns referenced (Azure Arc, Azure portal, Windows licensing models) are all Windows-specific, and there are no Linux equivalents or cross-platform considerations discussed.
Recommendations
- Explicitly state that the ESU licensing guidance is only applicable to Windows Server environments, and clarify if Linux/macOS systems are not supported.
- If Azure Arc supports onboarding Linux servers, add a section explaining how ESU licensing differs (or is not applicable) for Linux workloads.
- Provide examples or notes for mixed environments, such as how to manage licensing when both Windows and Linux servers are present in the same Azure Arc deployment.
- Add a table or FAQ clarifying platform support and any limitations for non-Windows operating systems.
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation lists the Windows installation path and PATH update process before the Linux equivalent, but otherwise provides parity in describing both platforms. No examples or instructions are exclusive to Windows, and Linux paths are given where relevant.
Recommendations
- Present installation paths for Windows and Linux in parallel or alternate order to avoid Windows-first bias.
- Explicitly mention if any commands or flags behave differently on Linux/macOS.
- Include troubleshooting notes for both platforms if applicable.
Azure Arc
Run command on Azure Arc-enabled servers (Preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation mentions both Windows and Linux support, but Windows-centric tools (PowerShell) are emphasized alongside Azure CLI and REST API. PowerShell is listed before REST API, and there are no explicit Linux-specific examples or references to Linux shell scripting. The documentation avoids outright exclusion but subtly prioritizes Windows patterns.
Recommendations
- Explicitly mention Bash or shell scripting alongside PowerShell when discussing script execution.
- Provide Linux-specific examples or references in the overview, not just in linked pages.
- Alternate the order of tool mentions (e.g., sometimes list Azure CLI, Bash, PowerShell, REST API) to avoid Windows-first perception.
- Include a note or example highlighting that both Windows batch/PowerShell and Linux shell scripts are supported.
Azure Arc
Migrate Azure Arc-enabled server to Azure
...rticles/azure-arc/servers/scenario-migrate-to-azure.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page demonstrates a mild Windows bias by consistently mentioning Azure PowerShell and Windows-centric tools/examples before their Azure CLI or Linux equivalents. PowerShell commands are highlighted for inventorying extensions and reviewing access rights, with CLI alternatives mentioned but less emphasized. The instructions for installing the Azure Guest Agent reference both Windows and Linux, but the Windows agent is listed first.
Recommendations
- Present Azure CLI and Linux-native commands/examples before or alongside PowerShell/Windows instructions.
- Explicitly include Linux/macOS shell commands for tasks like exporting role assignments, uninstalling agents, and managing extensions.
- Ensure parity in troubleshooting and agent management guidance for Linux systems.
- Alternate the order of Windows and Linux references in agent installation and extension management sections.
Azure Arc
Azure Arc-enabled servers Overview
...-docs/blob/main/articles/azure-arc/servers/overview.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation describes Azure Arc-enabled servers as supporting both Windows and Linux, but several sections show subtle Windows bias. Windows is consistently mentioned first when listing supported OSes and tools. The configuration section emphasizes PowerShell and Windows registry, with Linux daemons only mentioned secondarily. References to automation and runbooks link to Windows-specific tabs by default. Windows tools and patterns (e.g., registry, PowerShell) are highlighted before Linux equivalents, and Linux-specific examples or tooling are not described in detail.
Recommendations
- Alternate the order of Windows and Linux mentions to avoid implicit prioritization.
- Provide equal coverage and examples for Linux, including shell scripts and Linux-specific configuration management.
- Ensure links to documentation (e.g., Azure Automation runbook worker install) default to a neutral or Linux tab, or clearly show both OS options.
- Expand on Linux-specific operational details, such as managing daemons, file systems, and package updates.
- Include explicit Linux command-line examples alongside PowerShell examples where relevant.
Azure Arc
Plan and Deploy Azure Arc-Enabled Servers
...articles/azure-arc/servers/plan-at-scale-deployment.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates mild Windows bias. While it mentions Linux and Windows support and links to onboarding instructions for both, Windows tools and patterns (such as Azure PowerShell and Azure portal) are referenced first or exclusively in key automation and service principal creation steps. There are no explicit Linux shell or CLI examples, and Windows-centric terminology (administrator, PowerShell) is used more frequently than Linux equivalents (root, bash, shell).
Recommendations
- Provide explicit Linux shell (bash) and Azure CLI examples alongside PowerShell and portal instructions.
- When listing onboarding resources, alternate or parallelize Linux and Windows instructions/examples.
- Reference Linux-specific roles and terminology (e.g., 'root') equally with Windows terms ('administrator').
- Include automation patterns and tools commonly used on Linux (e.g., Ansible, shell scripts) in deployment steps.
- Ensure that service principal creation and agent deployment instructions include both PowerShell and CLI/bash options, with equal prominence.
Azure Arc
Solution with Multiple Shared Dependencies at Different Hierarchy Levels
...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation consistently presents both Bash and PowerShell examples for all command-line steps, but PowerShell examples always follow Bash and are present for every operation. There are no Windows-only tools or commands, and the workflow is cross-platform via the Azure CLI and Helm. However, the presence of PowerShell examples throughout and their explicit inclusion may create a slight perception of Windows bias, especially since PowerShell is primarily associated with Windows, even though it is available on Linux/macOS. There are no missing Linux/macOS examples, and no Windows-only tools are referenced.
Recommendations
- Clarify that PowerShell examples are compatible with PowerShell Core on Linux/macOS, not just Windows.
- Consider including a short note at the top explaining that all commands work on Linux/macOS and Windows, and that PowerShell examples are for users who prefer that shell, regardless of OS.
- If possible, add explicit examples for macOS (e.g., file path differences) or mention any OS-specific caveats.
- Ensure that Bash examples are shown first to reinforce Linux parity, or alternate the order in some sections.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias in its command examples and environment variable usage. The initial example for setting environment variables uses the Windows 'set' command, with no Linux/macOS equivalent ('export') provided. While most commands are cross-platform (Helm and Azure CLI), the absence of explicit Linux/macOS instructions for environment variables and authentication may cause confusion for non-Windows users. No PowerShell-specific commands or Windows-only tools are present, but the ordering and omission of Linux/macOS alternatives indicate a minor bias.
Recommendations
- Provide both Windows ('set VAR=val') and Linux/macOS ('export VAR=val') examples when setting environment variables.
- Clarify that Azure CLI and Helm commands are cross-platform, and explicitly mention any OS-specific differences where relevant.
- Add notes or tabs for platform-specific instructions, especially in authentication and environment setup sections.
- Ensure all command snippets are tested and presented for both Windows and Linux/macOS shells.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides step-by-step instructions for removing delegations using the Azure portal, PowerShell, and Azure CLI. The PowerShell example is presented before the Azure CLI example, and PowerShell is typically associated with Windows environments. There are no explicit Linux/macOS-only instructions or examples, and the documentation does not mention platform-specific considerations for running these commands. However, both Azure CLI and PowerShell Core are cross-platform, and the examples given can be executed on Linux/macOS with appropriate installations.
Recommendations
- Explicitly mention that both Azure CLI and PowerShell Core are available on Linux and macOS, and provide installation links.
- Alternate the order of examples, sometimes showing Azure CLI before PowerShell to avoid implicit Windows-first bias.
- Add a brief note clarifying that all command-line examples work on Linux/macOS as well as Windows.
- If there are platform-specific caveats (e.g., authentication, environment setup), include those details.
Azure Arc
Azure Arc-enabled data services - Automated validation testing
...ticles/azure-arc/data/automated-integration-testing.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation demonstrates mild Windows bias. While the core instructions use cross-platform tools (kubectl, git, Azure CLI), several examples and tips reference Windows-specific scenarios first or exclusively. For instance, line ending conversion is explained for Windows users, and screenshots of PowerShell terminals are shown. Azure CLI usage is demonstrated in PowerShell, and instructions for obtaining certain values (like CUSTOM_LOCATION_OID) show Windows terminals and mention Windows-specific issues before Linux/macOS equivalents.
Recommendations
- Provide explicit Linux/macOS examples and screenshots alongside Windows/PowerShell ones, especially for Azure CLI commands.
- Include instructions or tips for converting line endings on Linux/macOS (e.g., using dos2unix), not just VSCode on Windows.
- When referencing terminal commands, clarify that they work on all platforms and show at least one example in a bash/zsh terminal.
- Avoid assuming the user is on Windows when discussing file editing or command execution; mention cross-platform alternatives.
- Balance screenshots between Windows and Linux/macOS environments.
Azure Arc
Encrypt a database with transparent data encryption manually in SQL Managed Instance enabled by Azure Arc
...data/configure-transparent-data-encryption-manually.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides both Windows and Linux examples for file operations, but Windows examples are consistently presented before Linux ones. Windows-specific tools and patterns (such as 'type' for file output and Windows path syntax) are used, and troubleshooting notes focus on Windows issues. There is a slight emphasis on Windows workflows, with Linux examples present but secondary.
Recommendations
- Alternate the order of Windows and Linux examples, or present Linux examples first in some sections.
- Add troubleshooting notes for Linux/macOS users, not just Windows.
- Where possible, use cross-platform commands or clarify platform-specific differences.
- Include macOS-specific notes/examples if relevant.
- Consider grouping platform-specific instructions together, or using tabs that default to the user's detected OS.
Azure Arc
Connectivity modes and requirements
...docs/blob/main/articles/azure-arc/data/connectivity.md
Low Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page generally avoids explicit Windows bias in tooling, but there is a subtle 'windows_first' bias in the order of examples and tool mentions. Azure CLI, Azure Data Studio, and Azure portal are referenced before Linux-native tools (kubectl, Helm, oc), and there are no explicit Linux/macOS-specific examples or guidance. The documentation does not mention PowerShell or Windows-only tools, but it could better highlight Linux/macOS parity and usage patterns.
Recommendations
- Provide explicit Linux/macOS examples for provisioning, configuration, and management tasks (e.g., using bash, kubectl, Helm).
- Clarify that Azure Data Studio and Azure CLI are cross-platform, and provide installation/use instructions for Linux/macOS.
- When listing tools, alternate or balance the order (e.g., mention kubectl/Helm before Azure CLI/Azure Data Studio in some sections).
- Add a section or note confirming full support for Linux/macOS environments and referencing relevant documentation.
- Include troubleshooting or networking guidance specific to Linux/macOS (e.g., proxy configuration, firewall rules).
Azure Arc
Connect to AD-integrated SQL Managed Instance enabled by Azure Arc
.../data/connect-active-directory-sql-managed-instance.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation shows a mild Windows bias: Windows tools (SSMS, ADS) are mentioned and illustrated, and Windows terminology (NetBIOS, domain joined Windows-based client) is used first. Linux instructions are present and reasonably clear, but Windows examples and tools are described before Linux equivalents, and screenshots are Windows-centric.
Recommendations
- Add screenshots or explicit instructions for connecting via Azure Data Studio (ADS) on Linux/macOS.
- Clarify that ADS is cross-platform and provide Linux/macOS installation links.
- Present Linux/Mac OS connection instructions before or alongside Windows instructions, not after.
- Include troubleshooting tips for Kerberos setup on Linux/macOS.
- Mention alternative Linux SQL clients (e.g., DBeaver) if applicable.
Azure Arc
Deploy a new SQL Managed Instance enabled by Azure Arc using Kubernetes tools
...ate-sql-managed-instance-using-kubernetes-native-tools.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
minor_windows_path_example
Summary
The documentation generally maintains cross-platform parity, but there are minor signs of Windows bias. PowerShell is shown first for base64 encoding, and a Windows-style file path (C:\arc-data-services\sqlmi.yaml) is used in the kubectl example. Linux/macOS equivalents are present, but Windows examples and tools are mentioned before Linux ones.
Recommendations
- Present Linux/macOS and Windows examples side-by-side or alternate which is shown first.
- Use platform-neutral file paths in examples (e.g., ./arc-data-services/sqlmi.yaml).
- Explicitly mention that all commands work on Linux/macOS and Windows, and provide clear instructions for both.
- Consider adding a table or section summarizing platform-specific steps or differences.
Azure Arc
Prerequisites | Direct connect mode
...rc/data/create-data-controller-direct-prerequisites.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for connecting a Kubernetes cluster to Azure Arc, but the PowerShell example is given equal prominence and is not marked as Windows-specific. There are no Linux/macOS-specific instructions or clarifications, and the ordering of examples does not explicitly prioritize Linux-friendly tools. The rest of the documentation uses cross-platform tools (Azure CLI, Helm, kubectl), but the inclusion of PowerShell may cause confusion for Linux/macOS users.
Recommendations
- Clearly indicate that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- Provide explicit instructions or notes for Linux/macOS users, such as installation steps for Azure CLI and Helm on those platforms.
- List Azure CLI examples first, and clarify that CLI is cross-platform.
- Consider removing or de-emphasizing PowerShell examples unless there is a specific Windows-only workflow.
- Add a table or section comparing tool availability and usage across platforms.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page shows mild Windows bias: Windows installation links are listed first for some tools, PowerShell/cmd.exe are mentioned specifically, and there are notes about Windows-specific behaviors (e.g., curl alias in PowerShell). Linux installation instructions are present but less emphasized, and Linux/macOS users may need to infer steps or look elsewhere for parity.
Recommendations
- Present installation links for all platforms in parallel (Windows, Linux, macOS) rather than listing Windows first.
- Add explicit Linux/macOS installation instructions for all tools, not just links.
- Include notes about Linux/macOS command-line behaviors where Windows-specific notes are given (e.g., curl usage).
- Avoid mentioning Windows tools (cmd.exe, PowerShell) without equivalent Linux/macOS context.
- Provide example commands for Linux/macOS where Windows-specific commands are shown.
Azure Arc
Disaster recovery - SQL Managed Instance enabled by Azure Arc - portal
...-arc/data/managed-instance-disaster-recovery-portal.md
Low Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes disaster recovery configuration using the Azure portal UI, which is platform-agnostic but typically associated with Windows environments. There are no command-line examples (PowerShell, Bash, CLI) provided in this page, and no mention of Linux-specific tools or workflows. The only alternative mentioned is a link to a separate CLI documentation page, but this page itself does not provide Linux parity or examples.
Recommendations
- Include direct CLI examples (az CLI, Bash) within this page or side-by-side with portal instructions.
- Explicitly state that the portal is accessible from any OS/browser to clarify platform neutrality.
- Add a section comparing portal and CLI workflows, highlighting cross-platform options.
- Reference Linux/macOS compatibility for Azure Arc and SQL Managed Instance management.
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_example
linux_first
Summary
The documentation provides both Linux and Windows instructions for base64 encoding, with Linux (base64) shown first and Windows (certutil) as an alternative. The Windows example includes an extra step for removing headers using findstr, which is not needed for Linux. No PowerShell-heavy or Windows-first patterns are present elsewhere; all other examples use cross-platform tools (openssl, kubectl, Azure CLI) and generic YAML. The overall bias is low, as Linux is prioritized and Windows is included for parity.
Recommendations
- Add explicit macOS instructions for base64 encoding if differences exist.
- Clarify that certutil and findstr are Windows-only, and provide equivalent Linux/macOS commands for header removal if needed.
- Consider grouping OS-specific instructions in a clearer way (e.g., tabs or subheadings) to reduce confusion.
- Verify that all CLI commands (openssl, kubectl, Azure CLI) work identically on Windows, Linux, and macOS, and note any platform-specific caveats.
Azure Arc
Get logs to troubleshoot Azure Arc-enabled data services
...in/articles/azure-arc/data/troubleshooting-get-logs.md
Low Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides CLI-based instructions that are generally cross-platform, but the only explicit example of a target folder uses a Windows-style path (C:\temp\logs), with no equivalent Linux/macOS example. This may cause confusion for non-Windows users and suggests a subtle Windows-first bias.
Recommendations
- Include Linux/macOS path examples (e.g., /tmp/logs) alongside Windows examples when specifying file system locations.
- Explicitly state that the az CLI and arcdata extension are cross-platform and provide any OS-specific notes if needed.
- When showing example commands or outputs, alternate or show both Windows and Linux/macOS conventions where relevant.
Azure Arc
Upload usage data, metrics, and logs to Azure
...e-arc/data/upload-metrics-and-logs-to-azure-monitor.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows and Linux/macOS examples for environment variable setup and role assignment, but Windows examples are consistently presented first, and there is a dedicated PowerShell tab. There is a minor emphasis on Windows conventions (e.g., quoting in CLI commands), but Linux/macOS users are not missing any critical information or steps.
Recommendations
- Alternate the order of platform-specific tabs so Linux/macOS examples are sometimes shown first.
- Explicitly state that all Azure CLI commands work identically on Linux/macOS and Windows, reducing perceived Windows primacy.
- Ensure that any PowerShell-specific instructions are matched with bash/zsh equivalents where relevant.
- Consider grouping cross-platform CLI commands together, only splitting out platform-specific details (like environment variable syntax) when necessary.
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides examples for PowerShell, macOS/Linux, and Windows, but PowerShell (Windows-centric) is consistently listed first in code tabs. Windows-specific tools and patterns (PowerShell, Windows Task Scheduler) are mentioned before Linux equivalents (cron). Some sections lack parity in detail for Linux/macOS automation, and the overall structure subtly prioritizes Windows workflows.
Recommendations
- List Linux/macOS examples before or alongside PowerShell/Windows examples to avoid implicit prioritization.
- Expand Linux/macOS automation guidance, e.g., provide full cron job setup instructions, not just mention cron.
- Include more bash/zsh script examples and highlight cross-platform CLI usage.
- When mentioning automation tools, give equal detail for Linux (cron, systemd timers) and Windows (Task Scheduler).
- Consider a 'cross-platform' tab for CLI commands that work identically on all OSes.
- Review all sections for parity in troubleshooting and advanced usage instructions for Linux/macOS.
Azure Arc
Azure Arc-enabled data services validation
...lob/main/articles/azure-arc/data/validation-program.md
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page shows mild Windows bias. Several partner solutions are Windows-centric (e.g., DataON AZS-6224 for Azure Stack HCI, Hitachi UCP with Microsoft AKS-HCI, Lenovo ThinkAgile MX1020/MX3520), and the prerequisites list Azure Data Studio (primarily a Windows application) and Azure Data CLI, but does not mention Linux-native alternatives or provide explicit parity guidance. The ordering of partner solutions also places Windows-focused vendors before Linux-centric ones (e.g., Red Hat/OpenShift, Wind River). However, the validation process itself is Kubernetes-based and thus cross-platform, and Linux solutions (Red Hat, Wind River, Kublr) are included.
Recommendations
- Explicitly mention Linux/macOS support for Azure Data Studio and Azure Data CLI, including installation instructions or links for those platforms.
- Add examples or notes for Linux users in the prerequisites section (e.g., how to generate and use kubeconfig files on Linux).
- Balance the ordering of partner solutions so Linux-focused vendors are not consistently listed after Windows-centric ones.
- Highlight any platform-specific considerations for the validation process, especially where tools or workflows differ.
- If any steps require Windows-only tools, provide Linux/macOS alternatives or workarounds.
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides automation examples using Linux shell scripting and mentions both Linux and Windows script file extensions. However, when discussing automation, Windows tools (Task Scheduler) are mentioned before Linux equivalents (cron), and Windows script extensions (.cmd, .bat, .ps1) are listed before Linux/Mac (.sh). No PowerShell-specific examples are given, and the main CLI commands are cross-platform. There is a slight tendency to mention Windows patterns first, but Linux parity is generally maintained.
Recommendations
- List Linux/Mac script extensions (.sh) before Windows ones (.cmd, .bat, .ps1) to avoid subtle ordering bias.
- Mention Linux automation tools (cron) before Windows Task Scheduler, or present them together without prioritization.
- Provide explicit PowerShell and Bash script examples if platform-specific scripting is discussed.
- Clarify that all az CLI commands work identically on Linux, macOS, and Windows.
Azure Arc
Configure Authentication for Edge RAG Preview Enabled by Azure Arc
.../articles/azure-arc/edge-rag/prepare-authentication.md
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates mild Windows bias by referencing Windows Notepad as the example tool for storing IDs, and by not mentioning or providing alternatives for Linux/macOS users. All instructions are portal-based and do not reference platform-specific CLI tools, but the only explicit tool mentioned is Windows Notepad. There are no PowerShell examples, but the lack of parity in tool recommendations and examples may create minor friction for non-Windows users.
Recommendations
- Replace 'Windows Notepad' with a platform-neutral suggestion such as 'a text editor (e.g., Notepad, TextEdit, gedit, nano)'.
- Where possible, provide CLI alternatives using Azure CLI or Microsoft Graph for users who prefer command-line workflows on Linux/macOS.
- Explicitly mention that the Azure portal is accessible from any OS and that steps are not Windows-specific.
- Add screenshots or notes indicating cross-platform compatibility.
Azure Arc
Requirements for Edge RAG Preview, Enabled by Azure Arc
.../blob/main/articles/azure-arc/edge-rag/requirements.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates mild Windows bias by listing Windows Server NFS setup guides before Linux equivalents, referencing Windows-specific VM sizes and links, and mentioning a Windows machine as a recommended management host. While Linux is the required OS for VMs and Linux NFS setup is linked, Windows examples and tools are often referenced first or exclusively, and Linux management workflows are not described in detail.
Recommendations
- Present Linux and Windows setup guides side-by-side or list Linux first, given the VM OS requirement.
- Add explicit instructions or links for managing Azure Arc-enabled Kubernetes clusters from Linux/macOS hosts (e.g., installing Azure CLI, kubectl, Helm on Linux).
- Reference Linux VM sizes and hardware recommendations where appropriate, not just Windows-centric SKUs.
- Clarify that a Windows machine is optional and provide parity for Linux/macOS management hosts.
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
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for each query, with PowerShell examples present throughout. The PowerShell examples may be perceived as Windows-centric, and in each section, Azure CLI is shown before PowerShell, but there is no explicit mention of Linux/macOS-specific instructions, nor any discussion of platform differences or requirements for running the CLI or PowerShell commands on non-Windows systems.
Recommendations
- Add explicit notes confirming Azure CLI and Azure PowerShell are cross-platform, and provide installation/usage links for Linux/macOS.
- Include troubleshooting tips for running Azure PowerShell on Linux/macOS (e.g., .NET dependencies, shell integration).
- Consider adding bash or shell script examples where relevant, especially for automation scenarios.
- If there are any platform-specific caveats (e.g., authentication, environment variables), document them.
- Clarify that the Azure Portal is accessible from any OS with a browser.
Azure Arc
Azure RBAC on Azure Arc-enabled Kubernetes clusters
.../blob/main/articles/azure-arc/kubernetes/azure-rbac.md
Low 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 is used throughout, which is cross-platform, but references to the Azure portal and Microsoft Entra ID are inherently Windows-centric. Installation instructions for Azure kubelogin mention Windows and Mac before Linux, and some steps (e.g., SSH into master nodes, editing files with 'vi') assume Linux/Unix environments but do not provide explicit parity for Windows users. Conversely, there are no PowerShell-specific examples, but Windows is often mentioned first, and portal-based instructions are Windows-centric. Linux-specific instructions (e.g., kubelogin install) are present but appear after Windows/Mac. There are no explicit Linux-only gaps, but the ordering and tool references favor Windows.
Recommendations
- Provide Linux and macOS instructions/examples before or alongside Windows instructions, not after.
- Explicitly mention cross-platform compatibility for Azure CLI and kubectl commands.
- Add PowerShell examples where relevant, or clarify that commands work in Bash, PowerShell, and other shells.
- For portal-based steps, clarify that the Azure portal is web-based and accessible from any OS.
- For file editing and SSH steps, provide guidance for Windows users (e.g., using PuTTY, Windows Terminal, or WSL).
- Ensure that installation instructions for tools like kubelogin are equally detailed for all platforms.
Azure Arc
Diagnose connection issues for Azure Arc-enabled Kubernetes clusters
...les/azure-arc/kubernetes/diagnose-connection-issues.md
Low Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_examples_present
windows_node_pool_example
Summary
The documentation provides both Linux and Windows examples for DNS troubleshooting in Kubernetes pods, including PowerShell commands and Windows node pool instructions. While most of the guide is platform-neutral and uses cross-platform tools (kubectl, Azure CLI), the DNS troubleshooting section includes explicit Windows-specific steps and tools (Resolve-DnsName, Windows container images, PowerShell), which may create friction for Linux/macOS users. However, Linux examples are present and generally shown first.
Recommendations
- Ensure that Linux/macOS troubleshooting steps are always presented before or alongside Windows-specific instructions.
- Clarify which steps are platform-specific and provide equivalent Linux/macOS commands where possible.
- Add explicit notes or tables summarizing platform differences for DNS troubleshooting.
- Consider providing macOS-specific DNS troubleshooting examples (e.g., using 'dig' or 'nslookup' on macOS).
- For Windows node pool examples, explain when and why a user would need to use them, and provide guidance for clusters without Windows nodes.
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound network access for Azure Arc agents in the Azure Government cloud, so that they can connect to necessary endpoints for proper functionality and management of connected clusters."
...etes/includes/network-requirements-azure-government.md
Low Priority
View Details →
Detected Bias Types
windows_tools
Summary
The documentation lists 'sts.windows.net' as a required endpoint for certain scenarios. The inclusion of 'windows.net' suggests a Windows-centric service, and there is no mention of Linux-specific endpoints or tools. However, the page does not provide any OS-specific command-line examples, configuration steps, or instructions—so the bias is limited to endpoint naming and implied service orientation.
Recommendations
- Clarify whether 'sts.windows.net' is required for all platforms or only for Windows-based clusters.
- Add explicit notes or examples for Linux/macOS users if any steps or endpoints differ.
- Ensure parity in endpoint documentation by mentioning any Linux/macOS-specific endpoints or considerations if they exist.
- If platform-specific configuration is needed (e.g., firewall rules, proxy settings), provide examples for both Windows (PowerShell, Windows Firewall) and Linux (iptables, ufw, etc.).
Azure Arc
Azure Resource Graph sample queries for Azure Arc-enabled Kubernetes
...rticles/azure-arc/kubernetes/resource-graph-samples.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation references Azure PowerShell before Azure CLI when describing how to run queries, and the metadata includes a 'devx-track-azurepowershell' tag. This ordering and emphasis may subtly prioritize Windows-centric tools and workflows, even though Azure CLI is cross-platform. No explicit Linux/macOS examples or guidance are provided, but workarounds exist since Azure CLI and the portal are available on all platforms.
Recommendations
- List Azure CLI before Azure PowerShell when describing cross-platform workflows.
- Explicitly mention that Azure CLI and Resource Graph Explorer are available on Linux and macOS.
- Add example commands for both Azure CLI and PowerShell, or clarify that queries are platform-agnostic.
- Include a note on platform compatibility for all tools mentioned.
Azure Arc
Azure Arc-enabled Kubernetes system requirements
...n/articles/azure-arc/kubernetes/system-requirements.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for management and resource provider registration, but PowerShell examples are consistently presented first. PowerShell is a Windows-centric tool, and its prominence may signal a Windows-first bias. There are no explicit Linux/macOS examples (e.g., bash, zsh), nor is there mention of Linux-specific installation or usage patterns for Azure CLI. However, the CLI instructions are cross-platform, and no critical steps are Windows-only.
Recommendations
- Alternate the order of CLI and PowerShell examples, or present CLI (cross-platform) instructions first.
- Explicitly mention that Azure CLI is available and supported on Linux and macOS, and provide links to installation instructions for those platforms.
- Add notes or examples for common Linux/macOS shell environments (bash/zsh) where appropriate.
- Clarify that PowerShell Core is available cross-platform, if relevant, or provide bash equivalents for resource provider registration.
- Ensure parity in troubleshooting and tool installation guidance for Linux/macOS users.
Azure Arc
Azure Arc resource bridge system requirements
...icles/azure-arc/resource-bridge/system-requirements.md
Low Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias by linking Azure CLI installation instructions specifically for Windows in the management machine requirements, and by not providing explicit Linux/macOS examples or installation guidance. All CLI commands are generic, but the only installation link is for Windows, and there is no mention of Linux/macOS management machine requirements or parity.
Recommendations
- Add explicit instructions and links for installing Azure CLI on Linux and macOS in the management machine requirements section.
- Clarify that the management machine can be Windows, Linux, or macOS, and provide any OS-specific considerations (e.g., file paths, permissions).
- Include example CLI commands or configuration file locations for Linux/macOS environments.
- Ensure that all referenced CLI commands and extensions are confirmed to work cross-platform, and note any differences if present.
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge."
...e-arc/resource-bridge/includes/network-requirements.md
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page displays mild Windows bias. Windows-specific services and tools (e.g., time.windows.com, login.windows.net, sts.windows.net, servicebus.windows.net) are referenced, and Windows NTP is mentioned explicitly, while Linux equivalents (e.g., ntp.org, chrony) are not. The Azure CLI installer download is described generically, but no explicit Linux installation instructions or references are provided. The order of presentation often lists Windows endpoints before Linux-specific ones, and some notes (e.g., NTP) are written from a Windows-centric perspective. There are no Linux-specific configuration examples, and Linux time sync is not discussed.
Recommendations
- Include Linux/macOS equivalents for time synchronization (e.g., ntp.org, chrony) and clarify if time.windows.com is required for Linux VMs.
- Add explicit Linux/macOS installation instructions for Azure CLI and other tools where relevant.
- Balance the presentation order of endpoints and examples so that Linux and Windows are treated equally.
- Clarify which endpoints/services are required for Linux, Windows, or both, and provide guidance for each platform.
- Add notes or examples for Linux-specific log collection, package management, and time sync.
Azure Arc
Azure Arc resource bridge security overview
...rticles/azure-arc/resource-bridge/security-overview.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation mentions retrieving activity log entries with PowerShell and Azure CLI, listing PowerShell first and referencing it as a primary tool. There are no explicit Linux/macOS examples or references to platform-specific tools, but the mention of PowerShell before Azure CLI suggests a subtle Windows-first bias. No critical steps are Windows-only, and Azure CLI is cross-platform, so Linux/macOS users are not blocked but may feel secondary.
Recommendations
- List Azure CLI before PowerShell when describing cross-platform operations, as Azure CLI is natively supported on Linux/macOS.
- Explicitly mention that Azure CLI commands work on Linux/macOS and provide example commands for both platforms where appropriate.
- Avoid implying PowerShell is the default or primary tool unless necessary for a specific scenario.
- Add a note clarifying platform compatibility for all tools mentioned.
Azure Arc
Archive for What's new with Azure Connected Machine agent
...icles/azure-arc/servers/agent-release-notes-archive.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation consistently lists Windows download links before Linux, references Windows-specific tools (PowerShell, MSI installer, Windows Event Logs, WMI, Win32 API), and highlights Windows features and fixes in detail. PowerShell upgrades and telemetry are frequently mentioned, and Windows installer improvements are called out. While Linux features and fixes are present, Windows patterns and terminology are more prominent and often appear first. There are no critical sections that are Windows-only, but the overall framing and example order favor Windows.
Recommendations
- Alternate the order of Windows and Linux download links or present them together to avoid Windows-first perception.
- Ensure Linux-specific tools (e.g., systemd, journalctl, shell commands) are mentioned with equal prominence and detail as Windows tools.
- Highlight Linux features and fixes in summary sections, not just as bracketed notes.
- Include Linux/macOS equivalents for Windows-specific terminology (e.g., mention .deb/.rpm installers alongside MSI, systemd/journalctl alongside Event Logs).
- Balance PowerShell mentions with Bash/shell scripting references for Linux users.
- Add explicit parity notes when a feature or fix applies to both platforms, or clarify when it is platform-specific.
Azure Arc
Overview of the Azure Connected Machine agent
...blob/main/articles/azure-arc/servers/agent-overview.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides detailed, separate sections for Windows and Linux agent installation, but the Windows section appears first and is more verbose, including tips about Group Policy and Windows-specific service accounts. Windows tools and patterns (MSI installer, Group Policy, NT SERVICE accounts) are described in detail, while Linux equivalents (systemd, package managers) are covered but with less depth. The overall structure and example order favor Windows, and troubleshooting/logging paths are described with Windows locations first.
Recommendations
- Reorder sections so Linux and Windows installation details are presented in parallel or alternate order, or begin with Linux to balance representation.
- Provide equally detailed tips for Linux, such as SELinux/AppArmor considerations, systemd unit permissions, and package manager troubleshooting.
- Include Linux-specific troubleshooting advice (e.g., dealing with systemd failures, log rotation, permissions).
- Ensure examples and tables list Linux and Windows paths side-by-side, rather than Windows first.
- Add parity for advanced configuration topics, such as customizing service accounts or security groups on Linux.
- Explicitly mention macOS support or lack thereof, if relevant.
Azure Arc
CLI reference for `azcmagent connect`
...b/main/articles/azure-arc/servers/azcmagent-connect.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page exhibits mild Windows bias by listing the 'Interactive browser login (Windows only)' authentication method first and referencing PowerShell's Get-AzAccessToken as the primary example for obtaining access tokens, while not providing equivalent Linux/macOS command examples (such as Azure CLI). However, the majority of examples and instructions are cross-platform and mention Linux explicitly where relevant.
Recommendations
- Reorder authentication options so that cross-platform or Linux-default methods (e.g., device code login) appear first.
- Provide explicit Linux/macOS equivalents for PowerShell commands, such as showing how to obtain an access token using Azure CLI (e.g., 'az account get-access-token').
- Clarify that most examples are OS-agnostic unless otherwise stated, and add notes where behavior differs by platform.
- Add a Linux/macOS-specific example for interactive login, if supported, or clarify its availability.
Azure Arc
Automatic extension upgrade for Azure Arc-enabled servers
...e-arc/servers/manage-automatic-vm-extension-upgrade.md
Low Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation provides parity between Windows and Linux in most conceptual sections and explicitly states that Azure Arc-enabled servers can be Windows or Linux. However, there is a mild Windows bias in tooling references: Azure PowerShell is given its own section and detailed examples, while Linux users are directed to Azure CLI (which is cross-platform) but not to native Linux tools or shell scripts. The PowerShell section is more prominent and detailed, and Windows-only extensions are listed before Linux equivalents. The documentation mentions Windows tools (PowerShell) and provides installation guidance for the PowerShell module, but does not offer similar guidance for Linux-specific environments or scripting. The order of examples and extension lists tends to favor Windows-first presentation.
Recommendations
- Add explicit bash/zsh shell script examples for common extension management tasks, especially for Linux users who may not use Azure CLI or PowerShell.
- Provide installation and usage guidance for Azure CLI on Linux in the same detail as PowerShell on Windows.
- When listing extensions, group or order them by platform support (Windows-only, Linux-only, cross-platform) to clarify applicability.
- Ensure that Linux-specific troubleshooting or management patterns are mentioned where relevant.
- Consider adding a section on using automation tools common in Linux environments (e.g., Ansible, shell scripts) for extension management.
Azure Arc
CLI reference for `azcmagent disconnect`
...ain/articles/azure-arc/servers/azcmagent-disconnect.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation shows mild Windows bias by describing the interactive browser login as 'Windows only' and listing it first among authentication options. It also references the PowerShell cmdlet Get-AzAccessToken as an example for obtaining an access token, without mentioning Linux/macOS alternatives. However, Linux authentication flows (device code, Azure CLI) are described and supported, and examples are generally cross-platform.
Recommendations
- Explicitly mention Linux/macOS equivalents for obtaining access tokens (e.g., Azure CLI: 'az account get-access-token').
- Clarify that device code login is the default for Linux and Windows Server Core, and consider listing it first or in parallel with Windows options.
- Provide example commands for both Windows (PowerShell) and Linux/macOS (bash) where relevant.
- Add a note that all examples are cross-platform unless otherwise stated, and specify OS requirements for each authentication method.
Azure Arc
Billing service for Extended Security Updates for Windows Server 2012 through Azure Arc
...azure-arc/servers/billing-extended-security-updates.md
Low Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is exclusively focused on Windows Server 2012 ESUs enabled by Azure Arc, with no mention of Linux or macOS systems, examples, or billing scenarios. All terminology, examples, and scenarios are Windows-centric, and there are no references to Linux equivalents or cross-platform considerations.
Recommendations
- Clarify early in the documentation that the service is Windows-only, if applicable, to set expectations for cross-platform users.
- If Azure Arc ESU billing or management has any relevance for Linux servers (e.g., for hybrid environments or billing parity), add explicit sections or notes addressing Linux/macOS scenarios.
- Provide guidance or links for users managing non-Windows servers with Azure Arc, even if only to state that ESUs are not applicable.
- Consider including a comparison table or FAQ that addresses differences between Windows and Linux server management under Azure Arc, especially regarding billing and licensing.
Azure Arc
Deliver Extended Security Updates for Windows Server 2012
...azure-arc/servers/deliver-extended-security-updates.md
Low Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is exclusively focused on Windows Server 2012 and its management via Azure Arc, with all examples, screenshots, and instructions tailored to Windows environments. Windows-specific tools (WSUS, Configuration Manager) are mentioned, and there are no Linux or macOS equivalents, nor any guidance for non-Windows systems. The content assumes the reader is working with Windows Server and does not address Linux or cross-platform scenarios.
Recommendations
- Clarify early in the documentation that the process is only applicable to Windows Server 2012 and not to Linux or macOS systems.
- If Azure Arc supports similar extended update scenarios for Linux, provide parallel documentation or links.
- When mentioning patching solutions, briefly note Linux equivalents (e.g., Azure Update Manager for Linux, third-party Linux patching tools) or state that the described ESU process is Windows-only.
- Add a section or note for cross-platform administrators explaining the scope and limitations regarding non-Windows servers.
Azure Arc
Enable VM extensions to Arc-enabled servers from the Azure portal
...icles/azure-arc/servers/manage-vm-extensions-portal.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation generally presents a platform-neutral workflow for managing VM extensions via the Azure portal, which applies equally to Linux and Windows servers. However, in the example configuration step, only a Windows-specific scenario (deploying the Azure Monitor agent for Windows with a proxy) is mentioned, with no equivalent Linux example or clarification. This subtly prioritizes Windows use cases and may leave Linux users uncertain about their own configuration requirements.
Recommendations
- Include example configuration scenarios for both Windows and Linux extensions, or clarify when steps are platform-specific.
- When mentioning extension configuration, provide at least one Linux-specific example (e.g., deploying the Azure Monitor agent for Linux, or configuring a Linux extension with a proxy).
- Explicitly state that the portal workflow applies equally to Linux and Windows, and highlight any differences if they exist.
- Ensure screenshots and illustrations alternate or include both Linux and Windows perspectives where relevant.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation presents Windows VM extensions before Linux equivalents, listing a larger number of Windows-specific extensions and providing more detailed links for Windows. However, Linux extensions are also covered in a dedicated section with parity for core functionality. No examples, commands, or tools are shown exclusively for Windows, and both platforms are mentioned in all major deployment methods.
Recommendations
- Alternate the order of Windows and Linux sections or present them side-by-side to avoid implicit prioritization.
- Ensure that extension lists for both platforms are equally comprehensive and detailed.
- Add explicit examples or links for Linux where Windows-specific links are provided.
- Consider a summary table showing extension parity across platforms.
Azure Arc
Authenticate against Azure resources with Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation presents Windows/Powershell examples and tools before Linux equivalents in several sections. PowerShell is referenced multiple times as the primary method for access policy assignment and token retrieval, with Windows-specific instructions and screenshots shown first. Linux/Bash examples are provided, but often after Windows instructions, and some links and guidance (e.g., assigning access policies) default to PowerShell before mentioning Azure CLI.
Recommendations
- Alternate the order of Windows and Linux examples so that neither platform is consistently prioritized.
- Provide Azure CLI examples alongside PowerShell for resource assignment and management tasks, as CLI is cross-platform.
- Ensure screenshots and sample outputs are provided for both Windows and Linux, not just PowerShell.
- Explicitly mention that all steps can be performed on Linux/macOS, and link to platform-neutral or Linux-first tutorials where available.
- Where possible, use platform-neutral language and tools (e.g., Azure CLI, REST API) in introductory and summary sections.
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 Run commands locally. Both platforms are covered with equivalent Azure CLI commands, but Windows is shown first, which may subtly prioritize Windows users.
Recommendations
- Alternate the order of examples so that Linux is sometimes presented first.
- Explicitly state that the instructions apply equally to both Windows and Linux, and clarify any differences.
- Consider grouping platform-specific instructions together under clear headings, or provide a combined example for both platforms.
Azure Arc
Use Azure Private Link to Connect Servers to Azure Arc by Using a Private Endpoint
...in/articles/azure-arc/servers/private-link-security.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation generally maintains parity between Windows and Linux, especially in agent installation and DNS configuration. However, there are several instances of Windows bias: Windows examples and instructions are often presented first (e.g., Hosts file editing), Windows-specific tools and terminology (e.g., Windows Admin Center, C:\Windows\System32\drivers\etc\hosts) are mentioned before Linux equivalents, and screenshots and portal instructions use Windows-centric UI language. There is also a lack of explicit Linux command-line examples or references to Linux-specific troubleshooting tools.
Recommendations
- Alternate the order of Windows and Linux instructions/examples, or present them side-by-side.
- Include explicit Linux command-line examples for troubleshooting (e.g., dig, host) alongside nslookup.
- Mention Linux-specific management tools (e.g., Cockpit, SSH) where Windows Admin Center is referenced.
- Provide more detailed Linux agent installation steps, including package manager commands for common distributions.
- Ensure screenshots and UI instructions clarify that the process is identical for Linux servers 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
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents Windows instructions before Linux in the agent installation section and specifies the use of PowerShell for Windows, which may signal a slight Windows bias. However, Linux instructions are present and clear, and both platforms are supported throughout the guide.
Recommendations
- Present Windows and Linux installation instructions in parallel or alternate which is shown first.
- Include explicit mention of Linux shell requirements (e.g., bash, sudo) for parity with the Windows PowerShell note.
- Where possible, provide cross-platform script invocation examples together, emphasizing equal support.
- Add troubleshooting tips for both platforms, not just Windows (e.g., common Linux errors, log locations).
Azure Arc
Extensions security for Azure Arc-enabled servers
...main/articles/azure-arc/servers/security-extensions.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally maintains parity between Windows and Linux, but there is a consistent pattern of presenting Windows examples and instructions before Linux equivalents. PowerShell is used for Windows examples, while Bash is used for Linux, but Windows commands are often shown first. There are references to Windows-specific tools and scenarios (e.g., elevated command console, Windows Server 2012 ESU) before Linux ones. However, Linux examples are present for all major configuration steps, and there are no critical omissions for Linux users.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Explicitly state that all features and controls apply equally to Linux and Windows, and highlight any differences.
- Where Windows-specific scenarios (e.g., ESU) are mentioned, provide Linux context or clarify that the scenario is Windows-only.
- Ensure that references to management tools (PowerShell, Bash) are balanced and that CLI examples are shown for both platforms.
- Add a summary table or section that lists all commands for both platforms together for quick reference.
Azure Arc
Overview of Azure Connected Machine agent to manage Windows and Linux machines
...center-virtual-machine-manager/agent-overview-scvmm.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides a balanced overview of both Windows and Linux agent installation, configuration, and resource management. However, the Windows installation details are presented before the Linux section, which may subtly prioritize Windows. Both platforms receive equivalent technical depth and coverage, with directories, services/daemons, environment variables, and logs described for each. No Windows-only tools, examples, or patterns are present, and Linux-specific details are included where appropriate.
Recommendations
- Present Windows and Linux installation details in parallel sections or alternate the order in different documentation pages to avoid implicit prioritization.
- Explicitly state that both platforms are equally supported at the beginning of the installation section.
- Where possible, use platform-neutral terminology and examples, or provide side-by-side comparisons.
- Ensure that any referenced scripts, troubleshooting steps, or advanced configuration are equally available for both platforms.
Azure Arc
SSH access to Azure Arc-enabled servers
...ob/main/articles/azure-arc/servers/ssh-arc-overview.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux instructions, but Windows-specific tools (PowerShell, Windows OpenSSH) are frequently mentioned first or in greater detail. PowerShell examples are given for most Azure CLI commands, and Windows OpenSSH installation is referenced with a dedicated link and tip. Linux instructions are present but often secondary, and some sections (like prerequisites and next steps) highlight Windows tools before Linux equivalents.
Recommendations
- Alternate the order of Windows and Linux instructions/examples so Linux is not always second.
- Provide Linux/macOS-specific command examples (e.g., bash, zsh) for Azure CLI usage, not just PowerShell adaptations.
- Include direct links to Linux OpenSSH documentation in 'Next steps', not just Windows.
- Where PowerShell is referenced, also provide equivalent bash/zsh syntax for Linux/macOS users.
- Clarify that Azure CLI commands work natively on Linux/macOS shells, and highlight any differences in quoting or syntax.
- Add troubleshooting links for Linux SSH/OpenSSH issues, not just Windows.
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
minor_path_bias
Summary
The documentation generally provides parity between Windows and Linux, but there are subtle signs of Windows bias. Windows examples and paths are presented first in several sections, and Windows-specific tools (PowerShell, Windows environment variables) are referenced without equivalent Linux context. Some error codes reference Windows tools (PowerShell version requirements, %TEMP% paths) before or more prominently than Linux equivalents. However, Linux examples and paths are present and reasonably complete.
Recommendations
- Alternate the order of Windows and Linux examples so Linux is shown first in some sections.
- When referencing Windows-specific paths (e.g., %TEMP%, %ProgramData%), always provide the Linux equivalent alongside.
- For error codes mentioning PowerShell, clarify if/when Linux users are affected (e.g., PowerShell Core on Linux) or provide Linux-specific troubleshooting.
- Ensure troubleshooting steps and log file locations are always presented for both platforms in parallel.
- Explicitly mention Linux tools or commands where Windows tools (like PowerShell) are referenced.
- Consider a summary table or section that highlights platform-specific differences for quick reference.
Azure Arc
Connect VMware vCenter Server to Azure Arc by using the helper script
...ere/quick-start-connect-vcenter-to-arc-using-script.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) instructions for running the onboarding script, but Windows/PowerShell examples and notes are presented first and in greater detail. Windows-specific troubleshooting and caveats (e.g., PowerShell ISE warning) are included, while Linux instructions are more succinct. The download step lists 'PowerShell or Bash script' but does not elaborate on Linux-specific requirements or troubleshooting. The retry commands section also lists Windows first.
Recommendations
- Alternate the order of Windows and Linux instructions in each section, or present them side-by-side.
- Add Linux-specific troubleshooting notes or caveats, similar to the PowerShell ISE warning for Windows.
- Ensure parity in detail and clarity between Windows and Linux instructions.
- Explicitly mention macOS support if applicable, or clarify its status.
- Provide a summary table comparing Windows and Linux requirements, commands, and known issues.
Azure Arc
What's new in Azure Arc-enabled VMware vSphere
...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page shows a mild Windows bias, with Windows-specific features and tools (e.g., Windows VM customization, Windows Server Management, Extended Security Updates for Windows Server/SQL Server) mentioned explicitly and sometimes before Linux equivalents. While Linux support is referenced (e.g., Arc agent installation via SSH), examples and tooling for Linux are less detailed or not highlighted equally. Windows management tools (Group Policy, System Center Configuration Manager, PowerShell) are listed before Linux alternatives (Ansible), and some sections focus exclusively on Windows benefits.
Recommendations
- Ensure Linux-specific features and management tools are described with equal detail and prominence as Windows ones.
- Provide explicit Linux/macOS examples and workflows where Windows examples are given (e.g., guest OS customization, agent installation).
- List cross-platform tools (e.g., Ansible, Azure CLI) before or alongside Windows-only tools (e.g., PowerShell, Group Policy).
- Clarify which features are Windows-only and which are available for Linux, and provide links to Linux documentation where relevant.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents both Bash and PowerShell examples for all commands, but PowerShell examples are shown after Bash, and the PowerShell tab is present throughout. There are no Windows-specific tools or patterns, and Linux examples are not missing. However, the presence of PowerShell examples may suggest a slight Windows bias, as PowerShell is primarily used on Windows (though it is available cross-platform). The Bash examples are fully functional for Linux/macOS users.
Recommendations
- Clarify that PowerShell examples are for users who prefer PowerShell, which is available cross-platform, and not exclusively for Windows.
- Consider adding a note that Bash examples are suitable for Linux/macOS, and PowerShell examples are suitable for Windows and PowerShell Core users.
- Ensure that any future examples or troubleshooting steps include Linux/macOS-specific considerations if differences arise.
- If possible, provide a generic CLI example (without shell-specific syntax) for maximum cross-platform clarity.
Azure Arc
Create a Solution with Multiple Dependencies with Workload Orchestration
...quickstart-solution-multiple-shared-adapter-dependency.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every CLI operation, but PowerShell examples are consistently presented immediately after Bash and use Windows-style variable syntax. There is no evidence of Windows-only tools or commands, nor are Linux examples missing. However, PowerShell is given equal prominence throughout, which may suggest a slight Windows bias in prioritization and example parity.
Recommendations
- Consider listing Bash examples before PowerShell, as Bash is the default shell on most Linux and macOS systems.
- Add a short note clarifying that Bash examples are intended for Linux/macOS and PowerShell for Windows, to help users quickly identify which section is relevant.
- If possible, provide guidance for using the Azure CLI in other shells (e.g., zsh, fish) or clarify any platform-specific differences.
- Ensure that any file paths, environment variables, or CLI flags are cross-platform compatible and note any differences.
- If the documentation is intended for a cross-platform audience, consider leading with Bash examples or grouping examples by OS rather than shell.
Azure Portal
Get subscription and tenant IDs in the Azure portal
...in/articles/azure-portal/get-subscription-tenant-id.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation mentions both Azure PowerShell and Azure CLI for programmatic access, but PowerShell is consistently listed first, and links to PowerShell examples are provided before CLI equivalents. This ordering subtly prioritizes Windows-centric tools and patterns, which may create friction for Linux/macOS users who typically use Azure CLI. However, CLI options are present and linked, so Linux parity is not critically impacted.
Recommendations
- Alternate the order of PowerShell and CLI references, or list CLI first in sections targeting cross-platform users.
- Explicitly state that both Azure CLI and PowerShell are cross-platform, and clarify which commands are best suited for Linux/macOS.
- Provide example commands for both Azure CLI and PowerShell side-by-side where programmatic access is discussed.
- Add a note highlighting that Azure CLI is natively supported on Linux/macOS.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
minor_windows_tools
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring Linux and Windows parity in command-line instructions. However, PowerShell examples are consistently presented after Bash, and some PowerShell-specific details (such as base64 encoding and carriage return removal) are included. There are minor references to Windows tools (e.g., Out-File, [Convert]::ToBase64String) in PowerShell sections, but no critical steps are Windows-only. The workflow is fundamentally cross-platform, with no missing Linux examples or exclusive use of Windows tools.
Recommendations
- Continue providing both Bash and PowerShell tabs for all command-line instructions.
- Consider explicitly mentioning macOS compatibility where relevant (e.g., file encoding, carriage return handling).
- Add a short note at the top clarifying that Bash examples work on Linux and macOS, and PowerShell examples work on Windows (and PowerShell Core on Linux/macOS).
- Where file encoding is discussed, provide platform-agnostic instructions or reference common Linux/macOS editors (e.g., 'Use VS Code, nano, or vi to change encoding').
- Ensure that any troubleshooting or advanced sections also include Bash/Linux instructions if PowerShell/Windows-specific tools are mentioned.
Azure Arc
Create a Solution with Shared Adapter Dependency with Workload Orchestration
...ation/quickstart-solution-shared-adapter-dependency.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every command and variable definition, but PowerShell is always presented as a first-class citizen alongside Bash. There is no evidence of exclusive Windows tools or missing Linux examples, but the structure sometimes lists PowerShell examples immediately after Bash, and variable naming conventions are adapted for PowerShell. There are no sections that are Windows-only, and all CLI commands are cross-platform (Azure CLI).
Recommendations
- Consider listing Bash examples first in each section, as Bash is the default shell on most Linux/macOS systems.
- Explicitly state that all commands work on Linux/macOS and Windows, and clarify any platform-specific caveats.
- Add a note at the top clarifying that PowerShell examples are for Windows users, while Bash is for Linux/macOS (and Windows WSL).
- If possible, provide a single unified example when the commands are identical for both shells, to reduce duplication and emphasize parity.
Azure Arc
Create a Basic Solution with Common Configurations with Workload Orchestration
...ation/quickstart-solution-with-common-configuration.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell examples are always presented immediately after Bash, and sometimes include additional variable assignments (e.g., $childName) not present in Bash. There is no evidence of exclusive Windows tools or patterns, nor are Linux examples missing. However, the consistent pairing and sometimes more detailed PowerShell instructions suggest a mild Windows bias.
Recommendations
- Ensure Bash and PowerShell examples are equally detailed and parallel in content.
- Consider alternating which example appears first, or explicitly state that both platforms are equally supported.
- Add a short note at the top clarifying that all commands work on Linux, macOS, and Windows (with Bash or PowerShell).
- Review variable naming and assignment to ensure parity between Bash and PowerShell sections.
Azure Arc
Create a Basic Solution with Workload Orchestration
...on/quickstart-solution-without-common-configuration.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, but consistently lists Bash examples before PowerShell. However, the variable naming conventions and some example details (e.g., $childName in PowerShell, contextId formatting) are slightly more tailored to Windows/PowerShell users. There is no mention of Linux/macOS-specific tools, nor any platform-specific troubleshooting or notes. No critical Linux/macOS functionality is missing, but the parity is not perfect.
Recommendations
- Explicitly state that both Bash and PowerShell examples are supported on all platforms, and clarify any platform-specific nuances.
- Add a short section on running the Azure CLI in Linux/macOS environments, including common shell setup tips.
- Ensure variable naming and example values are equally clear for Bash and PowerShell users.
- Consider alternating the order of Bash and PowerShell tabs, or provide a neutral CLI example first.
- Add troubleshooting notes for Linux/macOS users if there are known issues (e.g., file permissions, path formats).
Azure Arc
Service Groups for Workload Orchestration
...cles/azure-arc/workload-orchestration/service-group.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, but PowerShell examples are consistently shown after Bash. However, the PowerShell examples are often more verbose and include additional scripting logic (such as object manipulation and JSON handling) that is specific to Windows/PowerShell environments. There is a slight 'windows_first' bias in the ordering of sections and the inclusion of PowerShell-specific scripting patterns, but Linux users are not blocked from completing any tasks, as Bash examples are present throughout.
Recommendations
- Ensure Bash and PowerShell examples are equally detailed and cover the same scripting logic, especially for JSON manipulation and file creation.
- Consider providing cross-platform scripting notes for steps that require more complex logic (e.g., JSON file creation, string manipulation), as Bash and PowerShell syntax differ.
- Explicitly mention that Bash examples are suitable for Linux/macOS and that PowerShell examples are for Windows, to guide users to the correct section.
- Where possible, provide generic az CLI commands that work identically across platforms, minimizing the need for platform-specific scripting.
- If PowerShell examples include advanced scripting, provide equivalent Bash scripting for parity.
Low 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 always presented as the second tab, and the examples are nearly identical except for syntax. There is no exclusive use of Windows tools, nor are Windows-specific patterns or tools prioritized. However, the presence of PowerShell examples throughout and their parity with Bash may signal a slight Windows bias, especially since PowerShell is primarily a Windows shell (though it is available cross-platform). No Linux/macOS examples are missing, and all steps can be completed on Linux/macOS using Bash.
Recommendations
- Consider listing Bash examples first to reflect the prevalence of Linux/macOS in cloud and orchestration scenarios.
- Clarify in the introduction that all commands work on Linux/macOS and Windows, and that PowerShell is available cross-platform.
- Add a note about PowerShell Core compatibility for Linux/macOS users who may prefer PowerShell.
- If possible, include a generic 'CLI' tab for commands that are identical in both Bash and PowerShell, reducing duplication and emphasizing cross-platform parity.
Azure Arc
Multiple Solutions with a Single Shared Dependency at Different Levels
...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all steps, but PowerShell is given equal prominence to Bash, and in some sections, PowerShell examples are shown immediately after Bash. There are no Linux/macOS-specific tools or patterns mentioned, and no Windows-only tools are used. However, the presence of PowerShell examples throughout may suggest a slight Windows bias, especially since PowerShell is primarily used on Windows, though it is available cross-platform. Bash is shown first in every case, which helps reduce bias.
Recommendations
- Clarify that PowerShell examples are intended for cross-platform use (Windows, Linux, macOS), or explicitly mention that Bash is recommended for Linux/macOS users.
- Add a note at the start of each code section indicating which shell is recommended for which OS.
- Consider including explicit Linux/macOS validation steps (e.g., using native Linux tools for file manipulation or environment setup, if relevant).
- If PowerShell is not required for Linux/macOS, consider omitting it or moving it to a separate section for Windows users.
Azure Portal
Use Azure Copilot with the Azure mobile app
...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell alongside CLI. PowerShell is a Windows-centric tool, and its mention before Bash or Linux shell scripting may suggest a Windows-first perspective. There are no explicit Linux/macOS examples or references to Bash, zsh, or other Unix shells, nor is there mention of platform-specific differences in script generation.
Recommendations
- Explicitly mention Bash or Linux shell scripting alongside PowerShell and CLI.
- Clarify that Azure Copilot can generate scripts for multiple platforms, including Linux/macOS.
- Provide examples or guidance for Linux/macOS users, such as how to use generated CLI scripts in their environment.
- Add a note about platform-specific limitations or differences in script generation.
Container Registry
Cross-Tenant Authentication from AKS to ACR
...es/container-registry/authenticate-aks-cross-tenant.md
Low Priority
View Details →
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any OS-specific command-line examples, but it also does not mention or show any Windows-specific tools, PowerShell commands, or patterns. All steps are described using the Azure portal or generic Azure CLI references, without explicit examples for either Windows or Linux/macOS environments. However, there is a minor bias in that no Linux/macOS-specific guidance or examples are provided, which could help users who prefer or require CLI-based workflows.
Recommendations
- Add Azure CLI command-line examples for each step, ensuring they are cross-platform and work on Linux/macOS as well as Windows.
- Explicitly mention that the Azure CLI commands are supported on all major platforms.
- Where portal steps are described, offer equivalent CLI commands as an alternative for users who prefer not to use the Azure portal.
- If any step requires a tool or method that behaves differently on Linux/macOS, note the differences or provide platform-specific guidance.
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images into Azure Container Registry, but the PowerShell example is given equal prominence and detail as the CLI example, and PowerShell is a Windows-centric tool. There are no Linux/macOS-specific shell examples (e.g., Bash scripts), nor is there mention of Linux-native tools or workflows. The ordering of examples (CLI first, then PowerShell) is neutral, but the inclusion of PowerShell as a primary method may suggest a slight Windows bias. However, the Azure CLI example is cross-platform and suitable for Linux/macOS users.
Recommendations
- Add explicit Bash/shell script examples for Linux/macOS users, especially for common tasks like image import.
- Clarify that Azure CLI commands work on Linux/macOS and Windows equally, and provide platform-specific notes if needed.
- If PowerShell is mentioned, also mention Bash or other Linux-native scripting options for parity.
- Consider including a section or note highlighting Linux/macOS workflows and tools for managing Azure Container Registry.
Container Registry
Access Registry Images from ACI
...cles/container-registry/container-registry-auth-aci.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell sample scripts, but references to PowerShell (a Windows-centric tool) are given equal prominence to Azure CLI, and there is no explicit mention of Linux/macOS shell environments or examples. The only environment-specific note is about setting MSYS_NO_PATHCONV for 'on-perm bash', which is vague and does not directly address Linux/macOS users. The ordering of examples and links does not prioritize Linux-native tools or workflows.
Recommendations
- Explicitly mention Linux/macOS compatibility and provide clear bash/zsh examples.
- Clarify the 'on-perm bash' note to directly reference Linux/macOS environments.
- Add troubleshooting notes for common Linux/macOS issues (e.g., file permissions, environment variables).
- Ensure that Azure CLI examples are shown before PowerShell, and highlight that CLI works cross-platform.
- Include links to Linux/macOS-specific documentation or guides where relevant.
Container Registry
Push & Pull Container Image using Azure Container Registry
...-registry/container-registry-get-started-docker-cli.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page exhibits mild Windows bias. Azure PowerShell examples are given equal prominence to Azure CLI, and Windows-centric tools like Visual Studio Code are recommended. The instructions for stopping containers use 'Control+C', which is universal but often associated with Windows. However, Docker CLI commands are cross-platform, and Linux/macOS installation links are provided. No Linux-specific examples or troubleshooting are present, and PowerShell is mentioned before any Linux shell alternatives.
Recommendations
- Add explicit Bash or shell examples for Linux/macOS users alongside PowerShell, especially in authentication and image removal sections.
- Include Linux/macOS-specific tips (e.g., stopping containers, file permissions, troubleshooting common issues).
- Balance tool recommendations by mentioning Linux-native editors (e.g., VS Code on Linux, Vim, etc.) and alternatives to PowerShell.
- Where PowerShell is mentioned, clarify that Bash or other shells can be used on Linux/macOS and provide equivalent commands if needed.
Container Registry
Quickstart - Create Registry in Portal
...iner-registry/container-registry-get-started-portal.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for signing in to the registry, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and examples for both are shown in parallel tabs. There is no explicit Linux/macOS bias, but PowerShell is not natively available on most Linux/macOS systems. The overall flow is platform-neutral, with Docker instructions and portal steps applicable to all OSes. However, the inclusion of PowerShell as a primary method may create friction for Linux/macOS users, who are more likely to use Azure CLI.
Recommendations
- Make Azure CLI the default or primary example, as it is cross-platform and preferred on Linux/macOS.
- Clearly indicate that PowerShell is optional and primarily for Windows users.
- Add a note clarifying that Azure CLI is recommended for Linux/macOS, and PowerShell for Windows.
- Consider moving CLI examples before PowerShell examples, or providing CLI-only instructions unless PowerShell is required.
- Ensure that all steps can be completed using CLI commands on Linux/macOS, and highlight any differences if they exist.
Container Registry
Manage OCI Artifacts and Supply Chain Artifacts with ORAS
...ntainer-registry/container-registry-manage-artifact.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Linux/macOS and Windows examples for key ORAS CLI commands, but Windows examples (using .cmd syntax) are consistently shown after Linux/macOS examples. There is a notable mention of Docker Desktop credential store, which is primarily a Windows tool, and some authentication instructions reference Windows-specific patterns. However, Linux/macOS users are generally able to follow all steps, and most commands are shown in bash syntax first.
Recommendations
- Ensure that Linux/macOS and Windows instructions are presented with equal prominence, possibly side-by-side or in tabs.
- Clarify Docker credential store usage for Linux (e.g., mention pass, secretservice, or other Linux-native credential helpers).
- Where Windows-specific instructions are given, provide equivalent Linux/macOS instructions if any differences exist.
- Review authentication sections to ensure Linux/macOS users are not left out when Docker Desktop is referenced.
- Consider using platform-agnostic command blocks or explicitly note platform differences.
Container Registry
Azure Container Registry custom roles
...ainer-registry/container-registry-rbac-custom-roles.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for listing permissions, but PowerShell is mentioned and shown alongside CLI, which can signal a Windows-centric approach. In the 'Creating or updating a custom role' and 'Assigning a custom role' sections, Azure PowerShell is listed as a primary tool, and the order of tools sometimes places PowerShell before or alongside CLI, which may subtly prioritize Windows workflows. No Linux-specific tools or shell examples are provided, and there is no explicit mention of Linux/macOS compatibility or parity.
Recommendations
- Ensure Azure CLI examples are shown first, as it is cross-platform and preferred on Linux/macOS.
- Explicitly mention that Azure CLI and Azure PowerShell are both available on Windows, Linux, and macOS.
- Add Bash or shell script examples where appropriate to demonstrate Linux workflows.
- Avoid listing PowerShell before CLI unless there is a technical reason.
- Clarify that all shown commands work on Linux/macOS unless otherwise noted.
Container Registry
Azure Container Registry SKU Features and Limits
...articles/container-registry/container-registry-skus.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations (showing usage, changing SKUs), but PowerShell is mentioned explicitly and examples are given alongside CLI. The PowerShell references and examples may be more familiar to Windows users, and PowerShell is a Windows-centric tool, though it is now cross-platform. There are no explicit Linux/macOS shell examples (e.g., Bash), and CLI examples are not shown as the primary or sole method. The order of presentation sometimes puts PowerShell before or alongside CLI, rather than CLI first (which is more universal).
Recommendations
- Present Azure CLI examples first, as CLI is cross-platform and more widely used outside Windows.
- Add explicit Bash/shell examples where relevant, especially for Linux/macOS users.
- Clarify that PowerShell is available cross-platform, but note that CLI is often preferred for Linux/macOS.
- Consider separating Windows-specific tooling (PowerShell) into a distinct section, or mark it as optional for Windows users.
- Ensure that all examples and instructions can be completed using CLI alone, without requiring PowerShell.
Container Registry
Quickstart- Manage Container Registry Content with Azure Client Libraries
...cles/container-registry/quickstart-client-libraries.md
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page shows mild Windows bias in the prerequisites section, where Azure PowerShell and Azure Portal are mentioned as options to create a registry before the Azure CLI. The package installation examples for each language use cross-platform tools (npm, pip, go get, etc.), and the code samples themselves are platform-neutral. However, the only explicit shell example shown is PowerShell for .NET package installation, and Azure PowerShell is mentioned before Azure CLI in the registry creation instructions. No Linux/macOS-specific instructions or examples are missing, but Windows tools are referenced first.
Recommendations
- List Azure CLI before Azure PowerShell and Portal in the prerequisites, as CLI is cross-platform.
- Provide Bash or shell examples alongside PowerShell for .NET package installation.
- Clarify that all client libraries and CLI commands work on Linux/macOS as well as Windows.
- Add explicit notes or links for Linux/macOS users where relevant, especially in setup sections.
Container Registry
Quickstart: Deploying the Connected Registry Arc Extension
...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but the PowerShell example is given equal prominence and uses Windows-specific syntax (echo, tr -d '\r'), which is not portable to Linux/macOS. The Bash example is listed first, but the presence of a dedicated PowerShell tab and Windows-centric command patterns may create friction for Linux/macOS users. No Linux-specific tools or patterns are missing, and all CLI commands are cross-platform, but the PowerShell example could be confusing for non-Windows users.
Recommendations
- Clearly indicate which example is for Windows and which is for Linux/macOS, using tabbed sections labeled 'Windows (PowerShell)' and 'Linux/macOS (Bash)'.
- Add a note clarifying that the PowerShell example is intended for Windows users, and the Bash example for Linux/macOS.
- Consider providing a macOS-specific example if there are any platform-specific nuances.
- Review the PowerShell example to ensure it does not introduce unnecessary complexity for Linux/macOS users (e.g., avoid using 'tr -d "\r"' unless needed).
- Ensure that the Bash example is complete and works as expected on both Linux and macOS.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page lists both Azure CLI and PowerShell script generation as Copilot capabilities, but PowerShell is mentioned directly after CLI and before other Linux-native tools. No Linux/macOS-specific tools or shell examples (e.g., Bash) are referenced, and PowerShell (a Windows-centric tool, though cross-platform) is highlighted as a primary scripting option. There are no explicit Linux/macOS examples, nor are Linux-specific patterns or tools (such as Bash, zsh, or Linux package managers) mentioned. The ordering and emphasis suggest a mild Windows-first bias.
Recommendations
- Include explicit examples or references for Linux/macOS users, such as Bash shell scripts or zsh.
- Mention that Azure CLI and PowerShell are both cross-platform, and clarify usage on Linux/macOS.
- Add links or examples for Linux-native tools and workflows where relevant.
- Ensure that script generation capabilities highlight parity between PowerShell and Bash, and show examples for both.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides example prompts for both Azure CLI and PowerShell, but PowerShell is listed as a primary scenario alongside CLI, despite PowerShell being predominantly a Windows tool. There is no explicit mention of Linux/macOS equivalents for PowerShell scenarios, and CLI examples do not clarify cross-platform compatibility. The order of presentation (CLI then PowerShell) is reasonable, but the inclusion of PowerShell-specific prompts without Bash or Linux shell alternatives suggests a mild Windows bias.
Recommendations
- Add example prompts for Bash or Linux shell scripting, especially for resource management tasks.
- Clarify in the Azure CLI section that CLI is cross-platform and works on Linux/macOS.
- For PowerShell scenarios, mention that Azure PowerShell is available on Linux/macOS, or provide equivalent Bash/CLI examples.
- Consider balancing the number of PowerShell and CLI examples, or grouping them under a 'Scripting' heading with platform notes.
Lighthouse
Cross-tenant management experiences
...hthouse/concepts/cross-tenant-management-experience.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page demonstrates mild Windows bias by mentioning Azure PowerShell before Azure CLI in the APIs and management tool support section, and by providing a PowerShell-specific example (Get-AzSubscription) with more detail than the equivalent Azure CLI command. No Linux/macOS-specific tools or examples are given, but Azure CLI is referenced and supported. No critical tasks are Windows-only, and most examples are cross-platform or generic.
Recommendations
- Present Azure CLI and PowerShell examples side-by-side, or alternate which is shown first.
- Provide explicit Linux/macOS usage notes or examples where relevant, especially for command-line tasks.
- Clarify that Azure CLI is fully supported on Linux/macOS and link to installation guides for non-Windows platforms.
- Avoid giving more detail or emphasis to PowerShell commands than to CLI equivalents.
Lighthouse
Onboard a customer to Azure Lighthouse
...ob/main/articles/lighthouse/how-to/onboard-customer.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment and confirmation steps, but PowerShell examples are given equal prominence and detail as CLI, and are not separated by platform. There is a subtle Windows bias in that PowerShell is presented as a primary automation tool alongside CLI, and the documentation does not explicitly mention Linux/macOS compatibility for PowerShell commands. The order of presentation sometimes puts Azure portal (Windows-centric), CLI, and PowerShell together, but does not prioritize Linux-native tools or clarify cross-platform usage. No Linux-specific examples, troubleshooting, or notes are provided.
Recommendations
- Explicitly state that Azure CLI and Azure PowerShell are cross-platform, and clarify any platform-specific requirements (e.g., installation steps for macOS/Linux).
- Add Linux/macOS-specific notes or troubleshooting tips, especially for PowerShell usage (e.g., installation via Homebrew, required modules).
- Consider showing Azure CLI examples first, as CLI is natively cross-platform, and clarify that PowerShell Core is available on Linux/macOS.
- Include links to official installation guides for Azure CLI and PowerShell on Linux/macOS.
- If relevant, mention alternative Linux-native tools or scripting options for automation.
Quotas
Increase Azure Storage account quotas
...main/articles/quotas/storage-account-quota-requests.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation lists Azure PowerShell as the first tool for viewing quota usage, and refers to it by name before mentioning the Azure CLI and REST API. PowerShell is primarily a Windows-centric tool, and its prominent placement may suggest a Windows bias. There are no explicit Linux/macOS examples or screenshots, and the documentation does not clarify cross-platform usage for CLI or REST API. The portal instructions are platform-neutral, but the tools section leans toward Windows.
Recommendations
- List Azure CLI before Azure PowerShell, as CLI is cross-platform and widely used on Linux/macOS.
- Provide explicit examples for both Azure CLI and PowerShell, showing usage on Linux/macOS and Windows.
- Clarify that all tools (CLI, REST API, PowerShell) are available on multiple platforms, and link to installation guides for Linux/macOS.
- Add screenshots or notes indicating that the Azure portal is accessible from any OS.
- Avoid referring to PowerShell as the default or primary tool unless justified by usage statistics.