756
Pages Scanned
238
Pages Flagged
756
Changed Pages
31.5%
% Pages Flagged
Scan Information
Started At: 2026-01-09 00:34:32
Finished At: 2026-01-09 21:30:35
Status: completed
Target Repo: Azure Management
Current Phase: done
Files Queued: 756
Files Completed: 756
Problematic Pages
238 issues found
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/active-directory-prerequisites.md
...icles/azure-arc/data/active-directory-prerequisites.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a strong Windows bias. All examples and instructions for managing Active Directory objects (OUs, users, permissions) are given using Windows GUI tools (Active Directory Users and Computers) and Windows PowerShell. There are no examples or guidance for performing these tasks from Linux environments, nor is there mention of cross-platform tools or alternatives. The prerequisite steps assume a Windows-based domain controller and link to a Windows Server-specific guide for setting up AD.
Recommendations
- Include instructions and examples for managing Active Directory objects using cross-platform tools such as ldapadd, ldapmodify, or samba-tool, which can be run from Linux.
- Mention and provide guidance for using remote management tools (e.g., RSAT from Windows, or LDAP tools from Linux) to interact with Active Directory.
- Add Linux shell command equivalents for PowerShell examples, where possible.
- Clarify whether a Windows Server domain controller is strictly required, or if Samba-based AD DCs are supported.
- Provide links to documentation for setting up and managing Active Directory from Linux environments.
Create Pull Request
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/configure-transparent-data-encryption-sql-managed-instance.md
...igure-transparent-data-encryption-sql-managed-instance.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_path_examples
windows_note_highlight
Summary
The documentation provides both Windows and Linux examples for file operations (copying certificates and keys), but Windows instructions and examples are consistently presented before Linux ones. Windows-specific issues (such as absolute path problems) are highlighted in notes, and Windows path syntax is used in examples. There are no PowerShell-only or Windows-only tools, but the ordering and emphasis show a subtle Windows bias.
Recommendations
- Alternate the order of Windows and Linux instructions/examples, or present Linux first to match the prevalence of Linux in container/Kubernetes environments.
- Use neutral path variables in examples (e.g., $HOME/sqlcerts/servercert.crt) before showing OS-specific syntax.
- Add notes for Linux-specific issues if any, to balance the attention given to Windows.
- Consider grouping OS-specific instructions in expandable sections, or clarify that Linux is the default/preferred environment for Kubernetes workloads.
- Review all examples to ensure parity in detail and clarity between Windows and Linux instructions.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/connect-managed-instance.md
...in/articles/azure-arc/data/connect-managed-instance.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools (SQL Server Management Studio), mentioning Windows tools before Linux alternatives, and lacking explicit Linux client examples or instructions. While Azure Data Studio and sqlcmd are cross-platform, the documentation does not provide Linux-specific connection instructions or highlight Linux-native SQL clients. The network configuration guidance is focused on Azure VM scenarios, which are often Windows-based, and does not address Linux VM nuances.
Recommendations
- Include explicit examples for connecting from Linux environments, such as using Linux-native SQL clients (e.g., DBeaver, SquirrelSQL) or command-line tools.
- Provide step-by-step instructions for configuring firewall rules and network access on Linux VMs, including relevant iptables or firewalld commands.
- Present connection instructions for both Windows and Linux platforms in parallel, ensuring parity and clarity for users of either OS.
- Mention Linux package installation steps for sqlcmd and Azure Data Studio, and clarify any OS-specific prerequisites.
- Add troubleshooting tips for common Linux connectivity issues (e.g., SELinux, ufw, etc.).
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/install-client-tools.md
...b/main/articles/azure-arc/data/install-client-tools.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits mild Windows bias. Windows installation links are listed before Linux/macOS in some tool rows (e.g., kubectl, curl), and there are specific notes about using cmd.exe instead of PowerShell for curl on Windows 10. The footnote about curl in PowerShell is Windows-specific, and there are no equivalent Linux shell notes. Linux installation instructions are sometimes less explicit (e.g., 'install curl package' vs. a direct link). No Linux-specific troubleshooting or usage notes are provided.
Recommendations
- Present installation links for all platforms in parallel order (e.g., Linux, macOS, Windows) or alphabetically to avoid Windows-first bias.
- Provide explicit Linux installation instructions or direct links, not just 'install curl package'.
- Include Linux shell usage notes where Windows/PowerShell notes are given (e.g., clarify curl behavior in bash/zsh).
- Add troubleshooting tips for Linux environments if Windows-specific ones are included.
- Ensure examples and footnotes cover both Windows and Linux usage patterns equally.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/prepare-dns.md
...s/blob/main/articles/azure-arc/edge-rag/prepare-dns.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates Windows bias by exclusively providing instructions for editing the hosts file using Windows-specific tools (Notepad, Administrator privileges, C:\Windows\System32\drivers\etc\hosts), without mentioning Linux or macOS equivalents. There are no examples or guidance for users on non-Windows platforms, and Windows patterns/tools are presented as the default.
Recommendations
- Add instructions for editing the hosts file on Linux (e.g., using sudo and editing /etc/hosts with nano or vi).
- Include macOS-specific guidance for updating /etc/hosts.
- Present platform-specific instructions in parallel sections or a table, rather than only Windows steps.
- Avoid assuming Windows as the default environment; clarify that steps may differ by OS.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/arc-gateway-simplify-networking.md
...zure-arc/kubernetes/arc-gateway-simplify-networking.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell is given equal prominence and detail, despite being primarily a Windows tool. There are no explicit Linux shell script examples (e.g., bash), and environment variable examples for proxy configuration use both Windows (PowerShell `$Env:`) and Linux (`export`) syntax, but the PowerShell examples are presented first in some sections. There is no mention of Linux-specific tools or patterns beyond Azure CLI, and no troubleshooting or operational guidance for Linux environments.
Recommendations
- Add explicit bash/Linux shell script examples for key operations, especially for proxy configuration and environment setup.
- Ensure that Linux environment variable examples (using `export`) are presented before or alongside PowerShell examples, not after.
- Include troubleshooting steps or operational notes specific to Linux environments (e.g., SELinux, systemd, log locations).
- Clarify that Azure CLI is cross-platform and recommend it as the default for Linux users.
- Avoid presenting PowerShell as the primary or default method for cross-platform tasks; make it clear when PowerShell is Windows-specific.
- Add notes or links to Linux-specific documentation where relevant.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/agent-release-notes.md
...main/articles/azure-arc/servers/agent-release-notes.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits several signs of Windows bias. Windows is consistently mentioned first in download links and feature tables. Troubleshooting and installation instructions focus on Windows-specific tools and patterns (e.g., 'msiexec', PowerShell, Command Prompt), with no equivalent Linux guidance provided. Known issues and fixes often detail Windows installer behaviors without Linux parallels. While Linux releases and features are included, examples and instructions are disproportionately Windows-centric.
Recommendations
- Alternate the order of Windows and Linux references in download links and feature tables, or present them together to avoid implicit prioritization.
- Provide Linux-specific troubleshooting and installation instructions (e.g., using 'rpm', 'dpkg', 'systemctl', or shell commands) alongside Windows examples.
- Include Linux equivalents for all Windows-only notes, especially in sections like 'Known Issues' and installation guidance.
- Ensure parity in the level of detail for both platforms when describing fixes, features, and configuration steps.
- Add explicit Linux command-line examples and clarify any platform-specific requirements or behaviors.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/resource-graph-samples.md
...blob/main/articles/azure-arc/resource-graph-samples.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page mentions Azure PowerShell before Azure CLI when describing how to run queries, which may suggest a Windows-first bias. There is no mention of Linux-specific tools, shell environments, or examples (such as Bash), nor are there instructions tailored for Linux users. The page does not provide parity in examples or guidance for Linux users, focusing instead on Windows-centric tools and patterns.
Recommendations
- List Azure CLI before Azure PowerShell when describing cross-platform usage, as CLI is natively supported on both Windows and Linux.
- Include explicit examples for running queries in Bash or other Linux shells, demonstrating cross-platform compatibility.
- Mention that Azure CLI and Resource Graph Explorer are available on Linux and macOS, not just Windows.
- Add a section or note highlighting Linux usage patterns and any relevant differences or considerations for Linux users.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/cloud-native/identity-access.md
...cles/azure-arc/servers/cloud-native/identity-access.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows-first perspective, referencing Windows-centric identity management concepts (Active Directory, Group Policy, LAPS) and tools before mentioning Linux equivalents. Windows access patterns (Remote Desktop) are described in detail, while Linux access (SSH) is mentioned only briefly and without example. Windows tools like LAPS are discussed exclusively, with no mention of Linux alternatives for local account management. There are no Linux-specific examples or guidance for hybrid identity scenarios.
Recommendations
- Provide Linux-specific examples for identity and access management, such as using SSH with Microsoft Entra ID, and managing local Linux accounts.
- Mention Linux-native tools or solutions for local account rotation and management, such as sssd, sudoers, or third-party password rotation tools.
- Ensure parity in describing access patterns: give equal detail to SSH access for Linux as is given to Remote Desktop for Windows.
- Include hybrid identity scenarios involving Linux servers, such as integrating Linux PAM with Microsoft Entra ID or Azure Arc.
- Avoid assuming AD or Windows-centric management as the default; explicitly address both Windows and Linux environments throughout.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/manage-agent.md
...s/blob/main/articles/azure-arc/servers/manage-agent.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions and tooling (such as PowerShell, Group Policy, Microsoft Update, WSUS, Configuration Manager) are often described in greater detail, with more context and step-by-step guidance than their Linux equivalents. Windows examples frequently appear before Linux ones, and Windows-specific tooling is referenced extensively, while Linux instructions rely on standard package managers with less narrative. Some advanced configuration scenarios (e.g., update infrastructure, proxy environment variables) provide richer Windows guidance, including PowerShell scripts and GUI walkthroughs, compared to more basic Linux command-line instructions.
Recommendations
- Provide parity in narrative detail for Linux instructions, including step-by-step guides for common Linux administration scenarios (e.g., using configuration management tools like Ansible, Puppet, or Chef for agent lifecycle management).
- Include Linux-first or at least parallel examples when describing agent installation, upgrade, and removal, rather than listing Windows first.
- Expand Linux proxy configuration guidance to match the depth of Windows coverage, including troubleshooting, service management, and environment variable persistence across distributions.
- Reference Linux equivalents to Windows tools (e.g., systemd for service management, cron for scheduled upgrades, or package manager hooks for automation).
- Offer more advanced Linux automation examples (e.g., shell scripts for bulk operations, integration with enterprise Linux management solutions).
- Ensure that all tables and lists present Windows and Linux options with equal prominence and detail.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/manage-vm-extensions-cli.md
...articles/azure-arc/servers/manage-vm-extensions-cli.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias in several ways: most command examples for VM extensions use Windows-specific tools (e.g., 'powershell.exe' in Custom Script Extension settings), extension types and names are often Windows-centric (e.g., 'IaaSAntimalware', 'DatadogWindowsAgent'), and Linux equivalents are either missing or mentioned secondarily (e.g., 'KeyVaultForLinux or KeyVaultForWindows'). There are no explicit Linux shell script examples, and the extension configuration examples do not show Linux usage patterns.
Recommendations
- Provide parallel Linux examples for all extension commands, especially for Custom Script Extension (e.g., using bash/sh instead of powershell.exe).
- Include Linux-specific extension types and settings (e.g., 'DependencyAgentLinux', 'DatadogLinuxAgent') in examples.
- When listing extension types or names, mention Linux and Windows options equally and explicitly.
- Add sample extension settings using Linux shell commands (e.g., 'commandToExecute': 'bash -c "ps aux | awk ..."').
- Clarify which extensions are cross-platform and which are OS-specific, and provide guidance for both.
- Avoid using Windows tools (like powershell.exe) as the default in examples; alternate or pair with Linux equivalents.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/overview.md
...-docs/blob/main/articles/azure-arc/servers/overview.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page describes Azure Arc-enabled servers as supporting both Windows and Linux, but several sections and linked resources prioritize Windows terminology, tools, and examples. PowerShell and Windows registry are mentioned explicitly, while Linux equivalents (such as shell scripting or Linux configuration files) are not. Some links and tabs default to Windows, and there is a lack of Linux-specific guidance or examples, especially in automation and configuration sections.
Recommendations
- Provide equal coverage and examples for Linux, such as shell scripting and Linux-specific configuration management.
- Ensure that documentation links and tabs offer both Windows and Linux options, and avoid defaulting to Windows.
- Mention Linux tools and patterns (e.g., systemd, cron, package managers) alongside Windows tools like PowerShell and registry.
- Add Linux-specific scenarios and walkthroughs, especially for automation, monitoring, and configuration.
- Review terminology to avoid Windows-centric language and ensure parity in describing supported features for both OS types.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/security-extensions.md
...main/articles/azure-arc/servers/security-extensions.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally presents Windows examples and terminology before Linux equivalents, especially in command examples and best practices. PowerShell is used for Windows instructions, while Linux examples use Bash, but Windows commands are often listed first. Windows-specific tools and scenarios (e.g., Active Directory domain controllers, Windows Server 2012 ESU) are mentioned, sometimes without equivalent Linux context. However, Linux examples are present and reasonably complete.
Recommendations
- Alternate the order of Windows and Linux examples to avoid consistently listing Windows first.
- Provide Linux-specific context for scenarios that currently only mention Windows (e.g., mention Linux equivalents for domain controllers or ESU scenarios if applicable).
- Ensure that any Windows-specific tool or pattern is matched with a Linux equivalent, or explicitly state when a feature is Windows-only.
- Where PowerShell is used for Windows, consider providing Bash examples for Linux in parallel, and clarify any differences in command usage or required privileges.
- Review terminology to ensure equal emphasis on both platforms throughout the documentation.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/ssh-arc-overview.md
...ob/main/articles/azure-arc/servers/ssh-arc-overview.md
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Windows and Linux instructions, but there is a noticeable Windows bias. Windows-specific tools (PowerShell, OpenSSH for Windows) are mentioned frequently and sometimes before Linux equivalents. PowerShell examples are given for most operations, and there are explicit references to Windows features and installation steps. Linux instructions are present but less detailed, and some examples (such as checking SSH status) are more thorough for Windows. The 'Next steps' section highlights Windows OpenSSH documentation but omits similar Linux resources.
Recommendations
- Ensure Linux instructions are as detailed as Windows instructions, including troubleshooting and configuration steps.
- Provide Linux-first examples or alternate between Windows and Linux to avoid prioritizing one platform.
- Include links to Linux OpenSSH documentation and troubleshooting guides in the 'Next steps' section.
- Balance the use of PowerShell and Bash examples throughout the documentation.
- Add explicit guidance for common Linux distributions (e.g., Ubuntu, CentOS) where package names or commands may differ.
- Where Windows-specific notes are given (e.g., OpenSSH installed by default), provide equivalent Linux notes (e.g., which distros have OpenSSH pre-installed).
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/private-link-security.md
...in/articles/azure-arc/servers/private-link-security.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias. Windows terminology and tooling (e.g., Windows Admin Center, Windows agent, C:\Windows\System32\drivers\etc\hosts) are mentioned first or exclusively in several places. Powershell and Windows-centric instructions are given before Linux equivalents, and some examples (such as editing the Hosts file) provide more detail for Windows than Linux. References to Windows tools (Windows Admin Center) are present, while Linux alternatives (such as SSH) are mentioned only briefly and with less guidance. There is a lack of parity in example commands and troubleshooting steps for Linux users.
Recommendations
- Ensure Linux instructions are given equal prominence and detail as Windows instructions, especially in configuration and troubleshooting sections.
- Provide example commands for Linux environments (e.g., using dig or host for DNS troubleshooting, systemctl for agent management).
- Mention Linux tools and workflows (such as Cockpit for remote management) alongside Windows Admin Center, or clarify parity and limitations.
- When listing agent download links, provide direct Linux package manager commands (e.g., apt, yum, zypper) for installing the agent.
- In sections where Windows is mentioned first (e.g., Hosts file editing), alternate the order or provide parallel step-by-step instructions for both OSes.
- Expand troubleshooting guidance to include Linux-specific scenarios, such as SELinux, iptables, or systemd service status.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/resource-graph-samples.md
...n/articles/azure-arc/servers/resource-graph-samples.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page references Azure PowerShell and Azure CLI as methods to run queries, but lists Azure PowerShell first, which may suggest a Windows-first approach. There are no explicit examples or instructions for running queries on Linux systems, nor is there mention of Linux-specific tools or shell environments. The absence of Linux command-line examples or references to Bash or other Linux shells indicates a bias towards Windows usage patterns.
Recommendations
- List Azure CLI before Azure PowerShell, as CLI is cross-platform and more commonly used on Linux.
- Provide explicit examples of running queries using Azure CLI in Bash or other Linux shells.
- Mention that both Azure CLI and PowerShell are available on Linux, and provide installation or usage notes for Linux users.
- Include sample queries or instructions tailored for Linux environments, such as using Bash scripts or integrating with Linux automation tools.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/troubleshoot-vm-extensions.md
...ticles/azure-arc/servers/troubleshoot-vm-extensions.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation shows a moderate Windows bias: PowerShell is the only CLI example given for extension removal, and Windows paths and tools are consistently listed before Linux equivalents. Windows-specific tools and patterns (PowerShell, C: drive paths) are mentioned more prominently, while Linux commands and tooling are not demonstrated or are listed second.
Recommendations
- Provide equivalent CLI examples for Linux, such as Azure CLI or shell commands, alongside PowerShell examples.
- Alternate the order of Windows and Linux instructions to avoid always listing Windows first.
- Include Linux-specific troubleshooting steps and commands where relevant (e.g., systemctl for service management, journalctl for logs).
- Explicitly mention that both Windows and Linux are supported and ensure parity in examples and guidance.
- Where file paths or logs are referenced, present both Windows and Linux locations together, or in parallel columns.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/switch-to-the-new-version-scvmm.md
...ual-machine-manager/switch-to-the-new-version-scvmm.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page focuses exclusively on System Center Virtual Machine Manager (SCVMM), a Windows-centric virtualization management tool. All instructions, references, and linked guides pertain to Windows environments, with no mention of Linux equivalents, Linux-based management tools, or cross-platform considerations. Examples and agent management instructions are specific to Windows, and the documentation assumes the user is operating in a Windows ecosystem.
Recommendations
- Include information about Linux-based virtualization management options, if supported by Azure Arc.
- Provide equivalent instructions or guidance for managing Linux VMs, including agent installation/uninstallation and onboarding steps.
- Add notes or links clarifying platform support and limitations, especially for users managing non-Windows environments.
- Where possible, offer cross-platform examples or highlight differences in process for Linux versus Windows VMs.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/enable-guest-management-at-scale.md
...arc/vmware-vsphere/enable-guest-management-at-scale.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by providing PowerShell-based automation scripts and examples, referencing Windows-specific tools such as Task Scheduler, and omitting equivalent Linux automation examples (e.g., Bash scripts, cron usage). Windows terminology and patterns (local administrator group, Task Scheduler) are mentioned before or instead of Linux equivalents, and Linux-specific instructions are minimal and relegated to notes.
Recommendations
- Provide Linux/Bash script examples for Arc agent installation and automation, including how to run the helper script from a Linux shell.
- Include instructions for scheduling automated agent installation on Linux using cron, with sample crontab entries.
- Mention Linux equivalents for administrative privileges (e.g., sudo/root) alongside Windows local administrator group references.
- Ensure parity in troubleshooting and prerequisites for both Windows and Linux VMs.
- Where PowerShell is referenced, also provide Bash or shell script alternatives for Linux users.
- Clarify which steps or scripts are cross-platform and which are Windows-specific, and offer alternatives where needed.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/support-matrix-for-system-center-virtual-machine-manager.md
...pport-matrix-for-system-center-virtual-machine-manager.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The documentation page exhibits a clear Windows bias. It consistently references Windows Server, SCVMM (a Windows-only product), and Windows-specific tools and patterns (e.g., WinRM, Windows Management Framework, PowerShell/OpenSSH for Windows). Windows operating systems are listed first and in detail, while Linux support is mentioned only as an alternative with less detail and no concrete examples. The workstation section notes Linux is supported but with performance caveats, and there are no Linux-specific configuration or troubleshooting examples. Windows tools and ports (WinRM, Windows Admin Center) are referenced exclusively or before Linux equivalents.
Recommendations
- Provide Linux-specific deployment and configuration examples, especially for agent installation and network setup.
- Include troubleshooting steps and performance optimization tips for Linux workstations.
- List supported Linux operating systems with the same level of detail as Windows, including version numbers and requirements.
- Mention Linux tools (e.g., SSH, systemctl) where relevant, and provide parity in instructions for both platforms.
- Avoid language that discourages Linux usage (e.g., 'deployment takes a bit longer and you might experience performance issues') without offering solutions or context.
- Where Windows tools (e.g., WinRM, Windows Management Framework) are referenced, provide Linux equivalents or alternatives.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/remove-scvmm-from-azure-arc.md
...virtual-machine-manager/remove-scvmm-from-azure-arc.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-specific instructions and tools. The deboarding script is only available for Windows/PowerShell, with no Linux equivalent or instructions. Windows uninstall steps are described first and in greater detail, while Linux instructions are brief and lack parity in tooling. The use of PowerShell and Windows-centric management patterns is prevalent, and Linux users are left with manual, less integrated steps.
Recommendations
- Provide a Linux-compatible deboarding script or manual CLI instructions for Linux environments.
- Offer Linux examples and tooling alongside Windows instructions, not just as an afterthought.
- Ensure parity in detail and guidance for both Windows and Linux uninstall steps.
- Mention cross-platform alternatives to PowerShell where possible, such as Bash scripts or Azure CLI.
- Explicitly state platform limitations and offer workarounds for Linux users.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/clean-up-script.md
...es/azure-arc/workload-orchestration/clean-up-script.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation exclusively provides a PowerShell script for resource clean-up, with all usage examples and instructions tailored to Windows environments. There is no mention of Linux-compatible alternatives (such as Bash scripts or Azure CLI commands), nor are Linux usage patterns or cross-platform considerations addressed. This creates a Windows-centric bias and may hinder users working on Linux or macOS systems.
Recommendations
- Provide equivalent clean-up instructions using Bash scripts or Azure CLI commands that work natively on Linux/macOS.
- Include explicit examples for running the clean-up process on Linux (e.g., using 'az group delete' or a Bash script).
- Clarify cross-platform compatibility of the provided script, or offer a platform-neutral version.
- List Linux/macOS instructions alongside Windows/PowerShell instructions, ensuring parity and accessibility for all users.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/how-to-stage.md
...icles/azure-arc/workload-orchestration/how-to-stage.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Bash and PowerShell examples for all major steps, but PowerShell is given equal prominence and detail, which may reflect a Windows-centric approach. Some commands and instructions (such as file encoding notes and base64 encoding) include Windows-specific details or tools (e.g., PowerShell's ConvertTo-Json, Out-File, [Convert]::ToBase64String), and the use of PowerShell tabs throughout signals parity but also a strong Windows orientation. The troubleshooting and portal instructions reference the Azure portal, which is cross-platform, but the CLI examples and scripting guidance are heavily focused on Windows and PowerShell, with no mention of Linux-specific nuances (such as file permissions, shell differences, or alternative editors). There is no explicit Linux bias, but the documentation does not address Linux-specific issues or provide guidance for Linux users beyond Bash commands.
Recommendations
- Add explicit notes about Linux-specific considerations, such as file permissions, common editors (vim, nano), and troubleshooting steps for Linux environments.
- Include examples for common Linux shell environments beyond Bash, such as Zsh, where relevant.
- Where file encoding is discussed, mention Linux tools (iconv, dos2unix) for converting between UTF-8 and UTF-8 with BOM.
- In base64 encoding sections, reference Linux commands (base64) and clarify differences in output between Linux and Windows.
- Review all steps for any implicit Windows assumptions (such as file paths, environment variables, or command syntax) and clarify for Linux users.
- Consider adding a 'Linux troubleshooting' section for common issues encountered on Linux systems.
- Ensure that PowerShell examples do not assume Windows-only environments, and clarify cross-platform support for PowerShell Core on Linux.
Azure Portal
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/mobile-app/microsoft-copilot-in-azure.md
.../azure-portal/mobile-app/microsoft-copilot-in-azure.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page mentions generating both CLI and PowerShell scripts as a key capability of Azure Copilot, but lists PowerShell before CLI and does not specify or provide examples for Linux shells (such as Bash). There is no mention of Linux-specific tools or patterns, nor are Linux/Bash examples provided. The focus on PowerShell and the ordering implies a Windows-first perspective.
Recommendations
- Explicitly mention Bash and Linux shell script generation as a capability alongside PowerShell and CLI.
- Provide example prompts or outputs for both PowerShell and Bash/Linux CLI to demonstrate parity.
- Clarify that Azure Copilot can generate scripts for multiple platforms, including Linux, and link to documentation on using Azure CLI and Bash on Linux.
- Avoid listing PowerShell before CLI or Linux tools unless there is a technical reason; consider alphabetical or platform-neutral ordering.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-rbac-built-in-roles-overview.md
...try/container-registry-rbac-built-in-roles-overview.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation lists Azure PowerShell as a primary method for performing role assignments, alongside Azure CLI and Portal, but does not provide any Linux-specific examples or mention Linux-native tools. PowerShell is a Windows-centric tool, and its inclusion without Linux parity can be seen as a Windows bias. The documentation does not provide command-line examples, but the ordering and tool selection suggest a Windows-first approach. There are no explicit Linux shell examples (e.g., Bash), nor are Linux-specific workflows or considerations mentioned.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide Bash/Linux shell examples for common role assignment tasks.
- If PowerShell is referenced, clarify that PowerShell Core is available on Linux and macOS, or provide equivalent Bash commands.
- Where tools are listed, alternate the order or explicitly state platform compatibility to avoid Windows-first perception.
- Add a section or note for Linux users, highlighting any platform-specific considerations or best practices.
- Ensure that all example commands (if added) are provided for both Windows (PowerShell) and Linux (Bash/CLI) environments.
Lighthouse
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/concepts/architecture.md
...blob/main/articles/lighthouse/concepts/architecture.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell for resource creation and management, with no explicit examples or instructions for Linux users or alternative tools. PowerShell commands are mentioned before Azure CLI, and there are no bash or Linux-specific examples, which may disadvantage users on non-Windows platforms.
Recommendations
- Provide equivalent Azure CLI examples alongside PowerShell instructions, especially for resource creation and onboarding steps.
- Include explicit references to cross-platform tools (e.g., bash, Azure CLI) in relevant sections, not just in 'Next steps'.
- Add sample commands for Linux/macOS environments where appropriate.
- Clarify that both PowerShell and CLI are supported and provide links to both sets of documentation in all relevant contexts.
- Avoid assuming PowerShell as the default tool for resource management; present CLI and PowerShell options in parallel.
Quotas
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/quotas/networking-quota-requests.md
...blob/main/articles/quotas/networking-quota-requests.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell as a primary method for viewing network quota usage, and by mentioning Azure PowerShell before Linux-friendly alternatives (Azure CLI and REST API). The page does not provide Linux-specific examples or guidance, and the ordering of tools subtly prioritizes Windows-centric workflows.
Recommendations
- Provide explicit Linux examples and workflows, such as showing Azure CLI commands with sample output.
- List cross-platform tools (Azure CLI, REST API) before Windows-specific tools (Azure PowerShell) to avoid implicit prioritization.
- Clarify that Azure CLI is available on Windows, macOS, and Linux, and provide installation or usage links for Linux users.
- Add screenshots or instructions demonstrating quota requests from Linux environments, if applicable.
- Ensure parity in troubleshooting and support instructions for both Windows and Linux users.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/choose-service.md
...nt-docs/blob/main/articles/azure-arc/choose-service.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and scenarios (e.g., SCVMM, Extended Security Updates for Windows Server, Azure VMware Solution onboarding with Windows tabs) are mentioned more frequently and in greater detail than Linux equivalents. PowerShell is referenced as a primary automation tool, while Linux-specific management tools and examples are absent. The onboarding and management guidance often defaults to Windows-centric workflows, and examples or references for Linux are either missing or less prominent.
Recommendations
- Add explicit Linux onboarding examples and workflows alongside Windows instructions, including links to Linux-specific documentation.
- Ensure automation examples include Bash, shell scripts, or Linux-native tools in addition to PowerShell.
- Highlight Linux management scenarios (e.g., patching, monitoring, security) with equal detail as Windows, including supported Linux distributions.
- Mention Linux equivalents for Windows-specific tools (e.g., alternatives to SCVMM for Linux VM management).
- Balance references to Windows and Linux in tables, feature lists, and recommendations, making it clear that both platforms are first-class citizens.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/container-storage/includes/multi-node-edge-essentials.md
...ntainer-storage/includes/multi-node-edge-essentials.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell-based examples (Invoke-AksEdgeNodeCommand) for configuring Linux nodes. It relies on a Windows-centric orchestration tool rather than showing native Linux commands or scripts, and does not provide direct Linux shell equivalents for the described tasks.
Recommendations
- Include native Linux shell command examples (bash) for each configuration step, so users managing Linux clusters directly can follow along without requiring Windows or PowerShell.
- Clarify whether Invoke-AksEdgeNodeCommand is mandatory, or if these steps can be performed directly on Linux nodes using standard tools (e.g., echo, tee, apt, systemctl).
- Add a section or sidebar specifically for Linux-only environments, detailing how to perform these tasks without any Windows or PowerShell dependencies.
- Ensure parity in documentation by presenting Linux-native instructions first or alongside any Windows/PowerShell-based orchestration methods.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/container-storage/includes/single-node-edge-essentials.md
...tainer-storage/includes/single-node-edge-essentials.md
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page, while focused on Linux preparation, demonstrates Windows bias by using Windows-centric tools (Invoke-AksEdgeNodeCommand) for Linux configuration, referencing Notepad as the default text editor, and relying on PowerShell-style cmdlets for Linux node management. Linux-native approaches (e.g., direct use of SSH, nano/vim for editing, bash commands) are missing or not prioritized.
Recommendations
- Provide Linux-native command examples for configuration tasks, such as using SSH and bash directly instead of Windows PowerShell cmdlets.
- Suggest Linux text editors (e.g., nano, vim, gedit) alongside or before Notepad for editing configuration files.
- Include instructions for running sysctl and editing config files directly on Linux, rather than through Windows-based tools.
- Clarify when Windows tools are required and offer Linux alternatives for all steps.
- Ensure that all examples and workflows can be completed entirely from a Linux environment without reliance on Windows or PowerShell.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/backup-controller-database.md
.../articles/azure-arc/data/backup-controller-database.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by providing only PowerShell examples for connecting to the SQL Server pod and running T-SQL commands, without offering equivalent Linux shell (bash) examples. The use of PowerShell syntax (e.g., command blocks labeled as 'powershell') and lack of Linux-specific instructions may hinder Linux users, especially since Kubernetes and container environments are commonly managed from Linux systems.
Recommendations
- Add Linux/bash equivalents for all PowerShell command examples, especially for connecting to the SQL Server pod and running sqlcmd.
- Label command blocks appropriately (e.g., 'bash' or 'console') rather than 'powershell' when the commands are cross-platform.
- Explicitly mention that the commands can be run from both Windows and Linux environments, and provide any necessary notes about differences (e.g., path separators, shell quoting).
- Include guidance for installing and using sqlcmd on Linux, if not already present.
- Review the documentation for other places where Windows tools or patterns are assumed, and ensure Linux parity.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/connect-active-directory-sql-managed-instance.md
.../data/connect-active-directory-sql-managed-instance.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits mild Windows bias. Windows-based tools (SSMS, ADS) are mentioned and visually highlighted, while Linux/Mac OS connection instructions are limited to command-line sqlcmd and kinit. The Windows connection example appears before the Linux/Mac OS section, and graphical connection steps are not provided for Linux clients. There is no mention of Linux-native graphical tools or parity in screenshots/examples.
Recommendations
- Include graphical connection instructions and screenshots for Azure Data Studio on Linux/Mac OS.
- Mention and provide examples for Linux-native SQL clients (e.g., DBeaver, SquirrelSQL) where appropriate.
- Present Linux/Mac OS connection examples before or alongside Windows examples to avoid ordering bias.
- Clarify tool availability across platforms (e.g., Azure Data Studio is cross-platform, SSMS is Windows-only).
- Add troubleshooting tips specific to Linux environments (e.g., Kerberos configuration, DNS setup).
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/automated-integration-testing.md
...ticles/azure-arc/data/automated-integration-testing.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias in several areas: screenshots and instructions for tasks like converting line endings and generating SAS tokens are shown using Windows tools (VSCode on Windows, Azure Portal), and PowerShell terminals are depicted in images. There is explicit mention of handling Windows-specific issues (CRLF vs LF), but no equivalent guidance for Linux or macOS users. CLI examples are generic (bash), but visual aids and step-by-step instructions favor Windows environments, and Linux alternatives (e.g., using 'dos2unix' for line endings, or Linux-native SAS generation) are missing.
Recommendations
- Include screenshots and instructions for Linux and macOS environments alongside Windows examples, especially for tasks like line ending conversion and SAS token generation.
- Mention and demonstrate Linux-native tools (e.g., 'dos2unix' for line ending conversion) and provide command-line alternatives to GUI-based steps.
- Ensure that all CLI examples are explicitly cross-platform, and clarify any OS-specific caveats for both Windows and Linux/macOS users.
- Add troubleshooting tips for Linux/macOS users where Windows-specific issues are discussed (e.g., clarify that CRLF is not an issue on Linux, but other encoding issues may arise).
- Balance the order of presentation so that Linux and Windows instructions/examples are given equal prominence, or group them by OS.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/configure-transparent-data-encryption-manually.md
...data/configure-transparent-data-encryption-manually.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows command examples are consistently presented before Linux equivalents in each tabbed section, and Windows-specific tools and patterns (such as the use of 'type' for file output and Windows path syntax) are highlighted. There is also a note specifically addressing Windows issues with 'kubectl cp', but no equivalent troubleshooting for Linux. The overall structure and example ordering subtly prioritize Windows users, even though Linux examples are present.
Recommendations
- Alternate the order of Windows and Linux examples in tabbed sections, or present Linux examples first in some cases.
- Provide troubleshooting notes for both Windows and Linux users, not just Windows.
- Where possible, use platform-neutral commands or highlight cross-platform alternatives (e.g., use 'cat' for both Windows and Linux via WSL or Git Bash).
- Explicitly state that both Windows and Linux are supported and encourage parity in example coverage.
- Consider adding a summary table comparing Windows and Linux workflows for key steps.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-complete-managed-instance-directly-connected.md
...ttps://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-complete-managed-instance-directly-connected.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing Windows file paths in command outputs, omitting Linux-specific instructions or outputs, and implicitly assuming a Windows environment for the user. No Linux/macOS-specific examples, outputs, or troubleshooting notes are provided, despite the cross-platform nature of the tools involved.
Recommendations
- Provide example outputs for both Windows and Linux/macOS environments, especially where file paths or environment-specific details differ (e.g., ~/.kube/config vs C:\...\.kube\config).
- Explicitly mention that the Azure CLI, kubectl, and Azure Data Studio are cross-platform, and provide installation or usage notes for Linux/macOS users.
- Include Linux/macOS-specific troubleshooting tips or notes where relevant.
- Where file paths or commands differ by OS, present both variants side by side or in tabs.
- Avoid using Windows-centric terminology or outputs as the default; strive for parity in representation.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-data-controller-direct-prerequisites.md
...rc/data/create-data-controller-direct-prerequisites.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for connecting a Kubernetes cluster to Azure Arc, but the PowerShell example is given equal prominence to the CLI example, despite PowerShell being primarily a Windows tool. There are no Linux-specific shell examples (e.g., Bash), nor are Linux patterns (such as using native package managers or shell scripts) discussed. The installation instructions for Azure CLI and Helm are platform-agnostic, but there is no explicit mention of Linux or macOS usage, nor are there troubleshooting notes for non-Windows environments.
Recommendations
- Add explicit Bash/Linux shell examples alongside Azure CLI and PowerShell, especially for steps like installing Azure CLI, Helm, and running connection commands.
- Clarify that PowerShell is primarily for Windows users and provide equivalent instructions for Linux/macOS users.
- Include troubleshooting notes or links for common Linux/macOS issues (e.g., permissions, package manager commands).
- Mention platform-specific prerequisites, such as required dependencies or environment setup for Linux/macOS.
- Ensure that examples and instructions are presented in a platform-neutral order, or provide tabs for Windows, Linux, and macOS.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/deploy-active-directory-sql-managed-instance.md
...c/data/deploy-active-directory-sql-managed-instance.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation page demonstrates a moderate Windows bias. Key Active Directory setup steps (such as creating accounts, DNS records, and SPNs) are described using Windows-centric tools and workflows, notably 'Active Directory Users and Computers' and the 'setspn' command, both of which are native to Windows environments. The Windows PowerShell script for keytab generation is mentioned before the Linux shell script, and the overall workflow assumes access to Windows domain controllers and tools. While Linux alternatives for keytab generation are provided, the initial instructions and examples prioritize Windows methods and tools.
Recommendations
- Provide explicit Linux-based instructions for Active Directory account creation and SPN registration, such as using 'adutil' or 'ldapadd' for account management and SPN registration.
- Include examples of using Samba tools (e.g., 'samba-tool') for managing Active Directory objects from Linux.
- Reorder tool and script references so that Linux and Windows options are presented equally, or Linux-first when targeting cross-platform audiences.
- Add guidance for environments where domain controllers are running on Samba/Unix, not just Windows Server.
- Clarify which steps require Windows-only tools and offer alternatives or workarounds for Linux administrators.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/deploy-system-managed-keytab-active-directory-connector.md
...eploy-system-managed-keytab-active-directory-connector.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates Windows bias by referencing Windows-specific tools (e.g., 'netdom query fsmo' for identifying the Primary Domain Controller) without providing Linux or cross-platform alternatives. Windows terminology and patterns (such as NetBIOS and AD account naming conventions) are used exclusively or explained first. There are no examples or guidance for performing equivalent tasks from Linux or non-Windows environments, despite the cross-platform nature of Kubernetes and Azure Arc.
Recommendations
- Provide Linux and cross-platform alternatives for domain controller discovery (e.g., using 'ldapsearch', 'samba-tool', or PowerShell Core on Linux).
- Include examples of how to interact with Active Directory from Linux environments, such as using 'realm', 'adcli', or 'ldapsearch' for querying domain information.
- Add notes or sections clarifying how users on Linux or macOS can perform prerequisite steps, especially for Active Directory tasks.
- Avoid referencing Windows tools exclusively; when mentioning a Windows command, also provide the equivalent for Linux or indicate if a cross-platform tool is available.
- Ensure terminology and instructions are inclusive of non-Windows environments, especially in cross-platform scenarios like Kubernetes deployments.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/deploy-active-directory-sql-managed-instance-cli.md
...ta/deploy-active-directory-sql-managed-instance-cli.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through its exclusive focus on Active Directory (AD) integration, which is a Windows-centric authentication technology. All examples and instructions assume the use of AD, with no mention of Linux-native identity solutions (such as LDAP, Kerberos, or FreeIPA). There are no examples or guidance for deploying SQL Managed Instance with non-Windows identity providers, nor is there discussion of Linux-specific tooling or patterns. The documentation also references AD setup and organizational unit (OU) configuration without Linux alternatives, reinforcing a Windows-first approach.
Recommendations
- Add examples and guidance for integrating SQL Managed Instance with Linux-native identity providers (e.g., LDAP, Kerberos, FreeIPA) where supported.
- Include documentation on how to perform similar deployments in environments that do not use Active Directory, or clarify AD requirements and alternatives.
- Provide parity in prerequisites and setup instructions for Linux-based identity management tools.
- Explicitly state platform requirements and limitations, and offer links to Linux-focused documentation if available.
- Consider adding troubleshooting or configuration notes for common Linux scenarios (e.g., keytab management, DNS setup on Linux, etc.).
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/deploy-customer-managed-keytab-active-directory-connector.md
...loy-customer-managed-keytab-active-directory-connector.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits Windows bias by focusing exclusively on Active Directory (a Windows-centric technology) and referencing Windows-specific concepts such as NetBIOS names and pre-Windows 2000 naming conventions. There are no examples or guidance for Linux-based directory services, nor is there mention of Linux tools or patterns for AD integration. The documentation assumes familiarity with Windows domain environments and omits Linux equivalents or alternatives.
Recommendations
- Include examples or guidance for integrating with Linux-based directory services (e.g., LDAP, FreeIPA) where possible.
- Provide context or alternatives for users who may not have a Windows AD environment, such as how to adapt the connector for non-Windows domains.
- Add notes on how Linux administrators can obtain required AD information (domain name, DNS servers, NetBIOS name) using Linux tools (e.g., ldapsearch, dig).
- Clarify whether the connector supports non-Windows directory services, and if not, explicitly state the Windows-only limitation.
- Balance terminology by explaining Windows-specific concepts (NetBIOS, pre-Windows 2000) for users from Linux backgrounds.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/managed-instance-features.md
...n/articles/azure-arc/data/managed-instance-features.md
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_authentication
windows_first
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (SSMS, SQL Server Data Tools, SQL Server Profiler, SQL Server PowerShell) are listed prominently in the 'Tools' section, with no mention of Linux-native alternatives or cross-platform equivalents. PowerShell scripting support is highlighted in the manageability features, and Windows Authentication is listed as a supported security feature, while Linux authentication mechanisms are not discussed. The overall tooling and examples focus on traditional Windows-centric patterns and utilities, with little to no reference to Linux or open-source alternatives.
Recommendations
- Include examples and references for Linux-native tools (e.g., sqlcmd, Azure Data Studio on Linux, or other CLI utilities).
- Mention and provide guidance for authentication mechanisms commonly used on Linux (e.g., Kerberos, certificate-based, or local accounts).
- Add parity for scripting support by referencing Bash, shell scripting, or Python-based automation alongside PowerShell.
- Clarify cross-platform compatibility for each tool, indicating which are available on Linux/macOS and how to install/use them.
- Provide links or documentation for managing SQL Managed Instance enabled by Azure Arc from Linux environments.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/privacy-data-collection-and-reporting.md
...zure-arc/data/privacy-data-collection-and-reporting.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias primarily through the use of Windows-centric terminology, examples, and data. SQL Server examples and JSON payloads reference Windows as the operating system (osType: 'Windows'), and the model is 'Hyper-V', a Windows virtualization technology. There are no explicit Linux or cross-platform examples, nor is there mention of Linux-specific tools or patterns. Windows tools and concepts (such as Hyper-V and SQL Server patch levels) are referenced, while Linux equivalents are absent. No PowerShell commands are present, but the overall framing and examples are Windows-centric.
Recommendations
- Add Linux-specific examples, such as inventory and billing data for SQL Server running on Linux hosts.
- Include references to Linux virtualization technologies (e.g., KVM, VMware) in addition to Hyper-V.
- Provide sample JSON payloads with osType set to 'Linux' and appropriate Linux host details.
- Mention Linux administrative tools and patterns where relevant (e.g., systemd, journalctl, Linux file paths).
- Ensure that any references to operating system or environment are presented in a cross-platform manner, not assuming Windows as the default.
- If discussing diagnostic data, include Linux log collection and export methods alongside any Windows approaches.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/resize-persistent-volume-claim.md
...icles/azure-arc/data/resize-persistent-volume-claim.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily through the use of PowerShell-style variable assignment (e.g., $newsize=...) in command examples, which is not compatible with Linux/macOS shells. There is no mention of Linux shell equivalents or alternative syntax, and the examples assume a Windows/PowerShell environment for patching PVCs. No Linux-specific instructions or parity guidance is provided.
Recommendations
- Provide Linux/macOS shell equivalents for variable assignment and kubectl patch commands (e.g., using export or direct inline JSON patching).
- Explicitly mention compatibility or differences between Windows (PowerShell) and Linux/macOS (bash/zsh) environments.
- Add examples using bash syntax, such as: newsize='{"spec":{"resources":{"requests":{"storage":"50Gi"}}}}'; kubectl patch pvc ... --patch "$newsize"
- Clarify that the $newsize variable assignment is PowerShell-specific and provide a bash alternative.
- Consider reordering examples or providing both Windows and Linux/macOS instructions side-by-side for each step.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/rotate-customer-managed-keytab.md
...icles/azure-arc/data/rotate-customer-managed-keytab.md
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates 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) without offering equivalent Linux/CLI instructions. While a bash script is mentioned, the process for password rotation is only described for Windows environments, and Linux domain controller scenarios are not addressed.
Recommendations
- Add instructions for rotating the Active Directory user password using Linux-based domain controller tools (e.g., samba-tool, ldapmodify) and CLI commands.
- Provide screenshots or command-line examples for Linux environments, not just Windows GUI tools.
- Ensure parity in troubleshooting steps by mentioning Linux equivalents for any referenced Windows logs or utilities.
- Clarify which steps/scripts are applicable for Linux-based AD environments and provide guidance for those scenarios.
- List both bash and PowerShell scripts together, and avoid presenting Windows tools/scripts first unless there is a technical reason.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/upload-metrics-and-logs-to-azure-monitor.md
...e-arc/data/upload-metrics-and-logs-to-azure-monitor.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a mild Windows bias. Windows and PowerShell examples are presented as primary or separate tabs, often before Linux/macOS equivalents. Windows-specific notes (such as quoting conventions) are highlighted, and references to PowerShell documentation are included in related content. While Linux/macOS examples are present, Windows environments and tools are given prominence.
Recommendations
- Present Linux/macOS and Windows examples side-by-side or in a neutral order, rather than listing Windows first.
- Include Bash and Linux shell examples wherever PowerShell or Windows command prompt examples are given.
- Add Linux-specific notes or troubleshooting tips, not just Windows-specific ones (e.g., quoting conventions, environment variable persistence).
- Reference Linux and Bash documentation in the 'Related content' section, not only PowerShell.
- Clarify that Azure CLI and az commands are cross-platform, and avoid implying a Windows-first workflow.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/upload-metrics.md
...cs/blob/main/articles/azure-arc/data/upload-metrics.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides examples for PowerShell and Windows, often listing PowerShell first and referencing Windows-specific tools and environment variable syntax. While Linux/macOS examples are present, some sections (such as role assignment and managed identity retrieval) omit direct Windows command examples, marking them as 'N/A'. Automation guidance mentions Windows Task Scheduler alongside cron, but scripting examples and automation are Linux shell-centric. This creates a subtle bias toward Windows and PowerShell, with Linux parity not fully achieved in all sections.
Recommendations
- Provide explicit Windows command examples (e.g., using batch files or Windows CLI syntax) where currently marked 'N/A', especially for role assignment and managed identity retrieval.
- Ensure Linux/macOS examples are given equal prominence and order as Windows/PowerShell examples, rather than listing PowerShell first.
- Expand automation examples to include Windows batch (.bat/.cmd) and PowerShell scripts, with step-by-step instructions for scheduling via Windows Task Scheduler.
- Reference cross-platform tools and patterns (e.g., using az CLI in both Windows and Linux environments) and avoid assuming PowerShell as the default for Windows.
- Where environment variables are set, clarify differences and provide examples for all platforms, including Windows Command Prompt, PowerShell, and Linux shells.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/upload-logs.md
...-docs/blob/main/articles/azure-arc/data/upload-logs.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
linux_parity_good
Summary
The documentation provides environment variable examples for Windows (CMD), PowerShell, and Linux/macOS, with Windows examples consistently listed first. Windows-specific tools (Task Scheduler, .cmd/.bat scripts) are mentioned alongside Linux equivalents (cron, .sh scripts), but not in a way that excludes Linux. The use of Azure CLI and kubectl is cross-platform, and Linux automation is well represented. Overall, the page demonstrates mild 'Windows-first' ordering and includes PowerShell examples, but Linux parity is strong and no major Linux omissions are present.
Recommendations
- Alternate the order of platform examples so Linux/macOS is sometimes listed first, or present all platforms in parallel tabs without implied priority.
- Explicitly mention that Azure CLI and kubectl commands work on all platforms at the start of relevant sections.
- Provide more detailed Linux automation examples (e.g., sample cron job setup) to match the detail given for Windows Task Scheduler.
- Consider grouping automation tool recommendations by platform (e.g., 'On Linux, use cron; on Windows, use Task Scheduler') for clarity.
- Ensure parity in script examples by showing full sample scripts for both Linux (.sh) and Windows (.bat/.ps1) where possible.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/configure-driver-machine.md
...rticles/azure-arc/edge-rag/configure-driver-machine.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation is heavily biased towards Windows, providing only a Windows-focused setup script using PowerShell and referencing Windows-specific installation paths and tools. There are no examples or instructions for Linux or cross-platform environments, and Windows tools and patterns are mentioned exclusively and first.
Recommendations
- Add equivalent setup instructions and sample scripts for Linux (e.g., Bash shell) and macOS environments.
- Include download and installation commands for Azure CLI, kubectl, and Helm for Linux (using apt, yum, curl, etc.) and macOS (using Homebrew, curl, etc.).
- Present cross-platform guidance, such as using environment variables and PATH modifications in a way that applies to all major operating systems.
- Clearly indicate which steps are OS-specific and provide parity in documentation structure and detail for Linux/macOS users.
- Consider providing a table or section comparing Windows and Linux/macOS setup steps for clarity.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/enable-gpu-aks.md
...lob/main/articles/azure-arc/edge-rag/enable-gpu-aks.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exclusively provides a PowerShell script for enabling GPU on AKS via Azure Arc, relying on Windows-specific tools (e.g., Get-PnpDevice, pnputil, Restart-Service). There are no Linux shell or cross-platform examples, and the workflow assumes a Windows environment throughout. Linux equivalents (such as lspci, modprobe, or driver installation via apt/yum) are not mentioned or provided.
Recommendations
- Add equivalent Linux shell script or command-line instructions for GPU enablement and driver installation.
- Document Linux-specific tools and patterns (e.g., lspci, nvidia-smi, modprobe) for GPU detection and configuration.
- Clarify platform requirements and provide guidance for both Windows and Linux hosts.
- Include notes or links to Linux documentation for Azure Arc and AKS GPU enablement.
- Present Windows and Linux instructions side-by-side or in separate sections to ensure parity.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/configure-endpoint-authentication.md
...zure-arc/edge-rag/configure-endpoint-authentication.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell-based command examples, referencing Windows-specific tools (e.g., '.\kubectl.exe'), and omitting equivalent Linux shell commands. There are no bash or Linux-native instructions, and the use of Windows paths and PowerShell syntax appears throughout, making it less accessible for Linux users.
Recommendations
- Provide parallel bash/Linux shell examples for all PowerShell commands.
- Use platform-neutral command syntax for kubectl (e.g., 'kubectl' instead of '.\kubectl.exe').
- Explicitly mention both Windows and Linux environments in setup instructions.
- Add notes or tabs to switch between Windows and Linux command examples.
- Avoid PowerShell-specific constructs (e.g., [System.Text.Encoding]::UTF8.GetString) in favor of cross-platform alternatives (e.g., base64 decoding with 'base64 --decode' in bash).
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/deploy.md
...t-docs/blob/main/articles/azure-arc/edge-rag/deploy.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation for deploying the Edge RAG extension demonstrates a Windows bias by providing only PowerShell-based Azure CLI examples, with no equivalent Bash or Linux shell commands. The parameter setting and deployment steps use Windows-centric scripting syntax and conventions, and there is no mention of Linux or cross-platform usage. This may hinder accessibility for users on Linux or macOS systems.
Recommendations
- Provide Bash (Linux/macOS) equivalents for all Azure CLI command examples, using standard shell variable syntax (e.g., export VARIABLE=value).
- Explicitly state that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
- Add notes or tabs for Linux/macOS users, showing how to set environment variables and run commands in their native shells.
- Avoid using PowerShell-specific syntax (e.g., $variable) in generic Azure CLI documentation, or supplement with Bash alternatives.
- Include screenshots or instructions for Linux environments where relevant.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/prepare-authentication.md
.../articles/azure-arc/edge-rag/prepare-authentication.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools (e.g., Windows Notepad) and only mentioning them for storing credentials. There are no examples or suggestions for Linux equivalents (such as gedit, nano, or text editors). The workflow is described entirely in terms of the Azure Portal GUI, which is platform-agnostic, but the only explicit tool recommendation is Windows-based. No command-line examples (PowerShell, Bash, Azure CLI) are provided, but the mention of 'Windows Notepad' and lack of Linux alternatives or parity is a clear bias.
Recommendations
- When suggesting tools for storing credentials, mention both Windows and Linux options (e.g., 'Paste the values to a text editor such as Windows Notepad, gedit, nano, or your preferred editor').
- Provide examples for command-line workflows using Azure CLI or Bash, which are cross-platform, in addition to GUI instructions.
- Avoid referencing platform-specific tools unless alternatives for other platforms are also provided.
- Consider including a note that all steps can be performed on any OS via the Azure Portal, and clarify that the instructions are not Windows-specific.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/prepare-aks-cluster.md
...ain/articles/azure-arc/edge-rag/prepare-aks-cluster.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. All command-line examples are given in PowerShell syntax, and instructions for cluster management and GPU enablement reference Windows-specific tools and workflows (e.g., Hyper-V, PowerShell commands, Windows management host setup). There are no Linux shell (bash) equivalents, nor are Linux-specific instructions or tools mentioned. The guidance for setting up a driver machine explicitly references Windows, with no mention of Linux or macOS alternatives.
Recommendations
- Provide equivalent bash shell commands for all PowerShell examples, ensuring Linux users can follow along.
- Include instructions for setting up a Linux (and optionally macOS) management host, listing required tools and installation steps.
- Mention Linux-compatible methods for checking GPU status and restarting services, avoiding exclusive reliance on Windows/Hyper-V tooling.
- Ensure all references to scripts or sample files are cross-platform, or clearly indicate platform-specific differences.
- Where possible, use platform-neutral Azure CLI commands and avoid embedding them in PowerShell variable assignment blocks.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/prepare-contributor-permission.md
...s/azure-arc/edge-rag/prepare-contributor-permission.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page provides only PowerShell-based CLI examples for verifying contributor permissions, which are typically associated with Windows environments. There are no equivalent Linux shell (bash) examples or explicit instructions for non-Windows users, and the use of PowerShell syntax may discourage or confuse Linux users.
Recommendations
- Add equivalent bash examples for the Azure CLI commands, demonstrating usage in a Linux or macOS terminal.
- Clarify that the 'az' CLI is cross-platform and can be used in both PowerShell and bash environments.
- Include a note or section specifically addressing Linux/macOS users, with instructions or screenshots relevant to those platforms.
- Avoid presenting PowerShell syntax exclusively; provide parallel examples for both PowerShell and bash where applicable.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/requirements.md
.../blob/main/articles/azure-arc/edge-rag/requirements.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits mild Windows bias. Windows Server is mentioned first in the NFS setup guides, and the link to the Windows guide precedes the Linux equivalent. There is a reference to 'Resource limits, VM sizes, and regions for AKS on Windows Server' without a Linux counterpart. The 'Windows machine (optional)' section suggests using a Windows machine for management, but does not provide equal guidance for Linux management hosts. No explicit Linux command-line examples or Linux management patterns are provided.
Recommendations
- Present Linux and Windows setup guides in parallel, or list Linux first when both are supported.
- Add explicit instructions for using a Linux machine as a management host, including installation steps for Azure CLI, kubectl, and Helm.
- Include links to Linux-specific AKS resource limits and VM size documentation, if available.
- Provide Linux command-line examples for common management tasks, not just generic tool mentions.
- Clarify that both Windows and Linux management hosts are supported, and outline any differences in setup or usage.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/uninstall-extension.md
...ain/articles/azure-arc/edge-rag/uninstall-extension.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing all command-line examples in PowerShell syntax, referencing PowerShell variables and patterns, and omitting Linux shell equivalents. The instructions assume the use of PowerShell even for cross-platform tools like Azure CLI and kubectl, and do not provide bash or Linux-specific guidance. There is no mention of Linux terminal usage or alternative shell environments, which may hinder Linux users.
Recommendations
- Provide equivalent bash/Linux shell examples alongside PowerShell commands, using standard shell variable syntax and conventions.
- Explicitly state that Azure CLI and kubectl are cross-platform and can be used from Linux/macOS terminals.
- Add a tabbed section for 'Linux/macOS Terminal' to mirror the 'Azure PowerShell' tab, with commands formatted for bash.
- Avoid using PowerShell-specific variable syntax ($var) in generic CLI examples; use environment variables or inline values for cross-platform clarity.
- Mention installation and usage notes for kubectl and Azure CLI on Linux/macOS where relevant.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/prepare-networking-observability.md
...azure-arc/edge-rag/prepare-networking-observability.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell command examples for installing and configuring MetalLB and observability modules. There are no bash or Linux shell equivalents, and the instructions assume use of PowerShell, which is native to Windows. Additionally, the order and phrasing imply a Windows-first approach, with no mention of Linux-specific tools or patterns.
Recommendations
- Provide equivalent bash or shell command examples for Linux users alongside PowerShell commands.
- Explicitly state platform requirements and offer guidance for both Windows and Linux environments.
- Include notes or sections for Linux-specific tools, such as using native Linux shells or package managers.
- Ensure that all steps are tested and documented for both Windows and Linux platforms to improve parity.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/includes/azure-arc-enabled-servers.md
...ticles/azure-arc/includes/azure-arc-enabled-servers.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal for each query, but does not include any Linux-specific shell examples (e.g., Bash, shell scripting) or mention Linux-native tools. The PowerShell examples are given equal prominence to Azure CLI, but PowerShell is primarily a Windows-centric tool, and there is no explicit guidance for Linux users beyond the Azure CLI. There is also a lack of discussion about Linux-specific patterns, troubleshooting, or considerations, and no mention of Linux package managers or command-line utilities that might be relevant for managing Arc-enabled servers running Linux.
Recommendations
- Add explicit Bash/shell examples for each query, demonstrating how Linux users can run these queries using Azure CLI in a Linux shell environment.
- Include notes or sections on Linux-specific troubleshooting, patterns, or considerations when managing Arc-enabled servers.
- Mention Linux-native tools (such as curl, jq, or package managers) where relevant, especially when discussing agent versions or installed extensions.
- Clarify that Azure CLI is cross-platform and provide guidance for both Windows and Linux users on installation and usage.
- Consider reordering examples so that Azure CLI (the most cross-platform option) appears before PowerShell, or explicitly label PowerShell as Windows-focused.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/azure-rbac.md
.../blob/main/articles/azure-arc/kubernetes/azure-rbac.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. While most command-line examples use Azure CLI and kubectl (cross-platform tools), installation instructions and tool references often mention Windows or Mac before Linux, and some steps (such as Azure kubelogin installation) provide more detailed instructions for Windows/Mac than for Linux. The page references Azure portal (a web interface, often used on Windows) for role assignment and access control, and does not provide parity for Linux-native tools or workflows (e.g., no mention of Linux desktop environments or alternatives to Azure portal). There are no PowerShell examples, but the overall flow assumes familiarity with Windows-centric patterns and tools.
Recommendations
- Provide Linux-first instructions or ensure Linux is mentioned before Windows/Mac in installation steps.
- Include parity for Linux desktop environments when referencing Azure portal workflows (e.g., mention browser-agnostic access).
- Offer explicit Linux command-line alternatives for all steps that reference Azure portal or GUI workflows.
- Expand installation instructions for Azure kubelogin and other tools to include package manager options for Linux (e.g., apt, yum, snap).
- Review all examples to ensure that Linux users are not required to adapt Windows-centric instructions.
- Where possible, add notes about cross-platform compatibility for Azure CLI and kubectl, and clarify any OS-specific caveats.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/includes/azure-arc.md
...ocs/blob/main/articles/azure-arc/includes/azure-arc.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and its inclusion as a primary example may signal a Windows bias. There are no explicit Linux shell (bash) or scripting examples, nor is there mention of Linux-specific tools or usage patterns. The ordering of examples (CLI, PowerShell, Portal) places PowerShell before any Linux-specific alternatives, and no Linux-native commands or instructions are provided.
Recommendations
- Add explicit bash shell examples for running Azure CLI commands on Linux.
- Include notes or sections highlighting Linux usage, such as scripting with bash or zsh.
- Clarify that Azure CLI is fully supported on Linux and provide installation/usage links.
- Consider reordering examples to present cross-platform (CLI/bash) options before PowerShell.
- If PowerShell is mentioned, note that it is available on Linux but provide parity with bash examples.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/cluster-connect.md
.../main/articles/azure-arc/kubernetes/cluster-connect.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, but PowerShell is a Windows-centric shell, and there are no explicit Bash or Linux shell examples. The environment variable setup and token extraction steps use PowerShell syntax in the PowerShell tab, which is not portable to Linux/macOS. The documentation does not mention Linux-specific tools or patterns, nor does it provide parity for Linux users in the PowerShell sections. The use of PowerShell is presented as an alternative to Azure CLI, but not as a cross-platform shell, and there is no explicit guidance for Linux or macOS users.
Recommendations
- Add explicit Bash/Linux shell examples alongside PowerShell, especially for environment variable setup and token extraction.
- Clarify that Azure CLI commands work on Linux/macOS and provide any necessary platform-specific notes.
- For steps that use PowerShell-specific syntax (e.g., token extraction), provide equivalent Bash commands.
- Include a 'Linux/macOS' tab or section for users who do not use PowerShell.
- Avoid implying PowerShell is the default or only alternative to Azure CLI; mention Bash as the primary shell for Linux/macOS.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/diagnose-connection-issues.md
...les/azure-arc/kubernetes/diagnose-connection-issues.md
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_example_in_linux_section
windows_first
Summary
The documentation provides both Linux and Windows examples for DNS troubleshooting in Kubernetes pods, but Windows-specific tools (PowerShell, Resolve-DnsName) and instructions are given special sections and detailed walkthroughs. The Windows example is included directly after the Linux example, and Windows tools (PowerShell, Resolve-DnsName) are highlighted, including references to Windows-specific images and commands. The documentation also links to Windows command documentation (nslookup) even in Linux contexts. There is a slight tendency to provide Windows instructions with equal or greater detail than Linux, and to mention Windows tools and patterns explicitly.
Recommendations
- Ensure Linux and Windows troubleshooting examples are given equal prominence and detail, possibly by separating them into clearly labeled sections.
- Provide Linux-first examples where appropriate, as most Kubernetes clusters run on Linux nodes.
- Avoid referencing Windows command documentation (e.g., nslookup) in Linux contexts; link to Linux equivalents (e.g., man pages) instead.
- Clarify when instructions are platform-specific and avoid mixing Windows commands in Linux-focused sections.
- Consider adding more Linux-native troubleshooting tools (e.g., dig, systemd-resolve) alongside nslookup and host.
- Explicitly state platform requirements for each example to avoid confusion.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/includes/network-requirements-azure-cloud.md
...ubernetes/includes/network-requirements-azure-cloud.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page shows a Windows bias in several ways: Windows-related endpoints (e.g., login.windows.net, sts.windows.net, servicebus.windows.net) are listed prominently and repeatedly, sometimes before their Azure equivalents. There is no mention of Linux-specific tooling or examples, and no Linux firewall or proxy configuration guidance is provided. The only explicit Linux reference is the 'linuxgeneva-microsoft.azurecr.io' endpoint, but no Linux-centric instructions or examples are given.
Recommendations
- Add Linux-specific examples for configuring outbound network access (e.g., using iptables, firewalld, or ufw).
- Include Linux command-line examples for translating wildcards or querying endpoints (e.g., using curl or wget).
- Ensure endpoint lists do not prioritize Windows-named endpoints over Azure or platform-neutral ones.
- Provide guidance for both Windows and Linux administrators, including references to common Linux tools and patterns.
- Clarify that the instructions apply equally to Linux and Windows environments, or explicitly call out differences where relevant.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/quickstart-connect-cluster.md
...les/azure-arc/kubernetes/quickstart-connect-cluster.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides parallel Azure CLI and Azure PowerShell instructions throughout, but PowerShell is a Windows-centric tool and is featured equally alongside the cross-platform Azure CLI. In several places, environment variable examples are given in PowerShell syntax before or instead of Bash/Linux equivalents. When discussing creating Kubernetes clusters, Docker for Mac and Docker for Windows are mentioned, but Linux-native options (e.g., Minikube, MicroK8s) are not. There is a lack of explicit Linux/Bash command examples for common deployment and environment setup tasks, which may disadvantage Linux users.
Recommendations
- Prioritize Azure CLI (which is cross-platform) in examples and structure, placing it before PowerShell sections.
- For environment variable setup, provide Bash/Linux export examples before or alongside PowerShell examples.
- Explicitly mention and provide links to Linux-native Kubernetes cluster creation tools (e.g., Minikube, MicroK8s) in the prerequisites.
- Wherever PowerShell is used, ensure a Bash/Linux equivalent is shown, especially for common setup steps (e.g., setting environment variables for proxies).
- Clarify that PowerShell is optional and primarily for Windows users, while Azure CLI and Bash commands are recommended for Linux/macOS.
- Audit for any other Windows-specific terminology or tools and ensure Linux alternatives are equally represented.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/system-requirements.md
...n/articles/azure-arc/kubernetes/system-requirements.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page demonstrates a Windows bias by consistently presenting Azure PowerShell instructions alongside Azure CLI, referencing PowerShell modules and patterns, and listing PowerShell examples before CLI equivalents. There is no mention of Linux-specific shell environments (e.g., bash), nor are there examples tailored for Linux users. The documentation assumes familiarity with Windows tools and workflows, potentially disadvantaging Linux-first users.
Recommendations
- Explicitly mention that Azure CLI and PowerShell are cross-platform, and clarify which instructions apply to Linux, macOS, and Windows.
- Provide bash shell examples for Linux users, especially for installation and resource provider registration steps.
- Include notes or sections on using Azure CLI from Linux/macOS, including prerequisites and troubleshooting tips.
- Avoid listing PowerShell instructions before CLI or alternate shell instructions; alternate between them or group by platform.
- Reference Linux-native tools and workflows where appropriate, such as using package managers (apt, yum, brew) for CLI installation.
- Clarify that Helm and Azure CLI can be installed and used on Linux, and provide explicit instructions for doing so.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/resource-graph-samples.md
...rticles/azure-arc/kubernetes/resource-graph-samples.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation references Azure PowerShell before Azure CLI when listing query execution options, which may suggest a Windows-first approach. There is a custom metadata tag 'devx-track-azurepowershell' listed before 'devx-track-azurecli', and no explicit Linux-specific instructions or examples are provided. The page does not mention running queries from Linux shells or provide bash examples, focusing instead on PowerShell and generic Azure CLI usage.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide Linux/bash shell examples for running queries.
- List Azure CLI before Azure PowerShell when describing query execution options to avoid Windows-first ordering.
- Add instructions or examples for running queries from Linux environments, such as bash or zsh.
- Clarify that Resource Graph Explorer is accessible via browser on any OS, not just Windows.
- Consider adding a 'devx-track-linux' metadata tag to highlight Linux parity.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/tutorial-gitops-flux2-ci-cd.md
...es/azure-arc/kubernetes/tutorial-gitops-flux2-ci-cd.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows/Azure-centric bias by prioritizing Azure DevOps (a Microsoft tool) and Azure CLI throughout the tutorial. The Azure DevOps workflow is described first and in much greater detail than the GitHub workflow, with step-by-step instructions and screenshots for Azure DevOps UI. There are no explicit Linux-specific examples or references to Linux-native CI/CD tools (e.g., Jenkins, GitLab CI, or shell scripting). The use of Azure CLI and Azure DevOps terminology assumes a Windows/Azure environment, and there is no mention of alternative Linux command-line tools or workflows.
Recommendations
- Provide equal detail and step-by-step instructions for the GitHub workflow, including screenshots and UI navigation.
- Include examples or references for Linux-native CI/CD tools such as Jenkins, GitLab CI, or shell scripting, especially for users who may not use Azure DevOps.
- Mention and demonstrate usage of Linux package managers (e.g., apt, yum) for installing required tools, in addition to Azure CLI.
- Add troubleshooting steps or notes for common Linux environments (e.g., Ubuntu, CentOS) when connecting to Azure services.
- Clarify that the tutorial is cross-platform and provide explicit instructions for both Windows and Linux users where relevant (e.g., file paths, environment setup).
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/overview.md
...nagement-docs/blob/main/articles/azure-arc/overview.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page for Azure Arc overview demonstrates a moderate Windows bias. It repeatedly references Windows-centric management tools (such as System Center Virtual Machine Manager and VMware vCenter) and features, often listing them before or instead of Linux equivalents. There is a lack of explicit Linux tooling or examples, and the documentation does not provide parity in describing Linux-specific management scenarios or tools. While Linux is mentioned as a supported platform, there are no concrete examples or references to Linux-native management solutions, and the focus remains on Windows-oriented infrastructure.
Recommendations
- Add explicit examples and references for managing Linux servers and VMs, including common Linux management tools (e.g., Ansible, SSH, systemd).
- Provide Linux-specific scenarios and workflows alongside Windows/SCVMM/VMware examples, ensuring equal visibility.
- Include links to documentation or guides for integrating Azure Arc with Linux-native automation and monitoring solutions.
- Ensure that lists and feature descriptions mention Linux and Windows platforms equally, and avoid listing Windows tools first unless contextually justified.
- Highlight cross-platform CLI usage (e.g., Azure CLI on Linux) and provide sample commands for both Windows and Linux environments.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/network-requirements-consolidated.md
...rticles/azure-arc/network-requirements-consolidated.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and platforms (e.g., VMware vSphere, System Center Virtual Machine Manager, Azure Stack HCI, SQL Server) without mentioning Linux equivalents or providing Linux-specific examples. The structure and examples prioritize Windows environments and management tools, while Linux scenarios and tools are absent or not addressed explicitly.
Recommendations
- Include Linux-specific examples and endpoints, such as those relevant to common Linux server distributions or management tools.
- Add guidance for configuring network requirements on Linux systems, including firewall rules and package dependencies.
- Reference Linux-native management solutions (e.g., Ansible, SSH, iptables) alongside Windows tools.
- Ensure parity in documentation by listing Linux scenarios and requirements before or alongside Windows-specific ones.
- Provide sample commands for both PowerShell (Windows) and Bash (Linux) where applicable.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/resource-bridge/maintenance.md
...main/articles/azure-arc/resource-bridge/maintenance.md
High Priority
View Details →
Detected Bias Types
missing_linux_example
windows_tools
windows_first
Summary
The documentation page for Azure Arc resource bridge maintenance operations demonstrates a bias towards Windows environments. It references Windows-centric infrastructure (such as SCVMM and vCenter), provides links to credential update guides for Windows-based platforms, and omits explicit Linux-based examples or guidance. The command-line instructions rely on the Azure CLI, which is cross-platform, but there is no mention of Linux-specific considerations, troubleshooting, or examples. The documentation assumes familiarity with Windows tools and patterns, and does not address Linux appliance VM management or credential update scenarios.
Recommendations
- Add explicit examples and guidance for managing Arc resource bridge on Linux-based appliance VMs, including credential updates and troubleshooting.
- Include links to Linux-specific documentation or sections, such as updating credentials for Linux-based infrastructure or managing Linux VMs via Arc resource bridge.
- Ensure parity in examples by providing both Windows and Linux scenarios where applicable, especially in sections discussing credential management and proxy settings.
- Mention any differences or considerations for Linux users when using the Azure CLI commands (e.g., file paths, permissions, environment variables).
- Clarify whether the appliance VM can be Linux-based and, if so, provide maintenance instructions relevant to Linux environments.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/resource-bridge/includes/network-requirements.md
...e-arc/resource-bridge/includes/network-requirements.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific services (e.g., time.windows.com, login.windows.net, sts.windows.net, servicebus.windows.net) and mentioning Windows NTP as the default for Hyper-V without discussing Linux alternatives. Windows endpoints are listed before Linux ones in several cases, and there is a lack of Linux-specific examples or parity in tool references (e.g., no mention of chrony/ntpd for NTP, or Linux management tools). The only explicit Linux reference is for package downloads, but no Linux-specific configuration guidance is provided.
Recommendations
- Add Linux NTP server examples (e.g., pool.ntp.org) and describe how to configure time sync for Linux-based management machines and appliance VMs.
- Include Linux management tools and patterns (e.g., SSH, systemd, chrony) where appropriate, and provide guidance for both Windows and Linux environments.
- Ensure that Linux endpoints and configuration steps are presented alongside Windows ones, not only as an afterthought.
- Clarify which instructions or endpoints apply to both Windows and Linux, and provide explicit examples for each platform.
- Review the order of endpoint listings to avoid consistently listing Windows endpoints first, and balance the presentation between platforms.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/resource-bridge/troubleshoot-resource-bridge.md
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page exhibits a Windows bias in several areas: troubleshooting steps and command-line examples often reference Windows-specific tools (such as PowerShell and RDP), and instructions for network and DNS troubleshooting default to Windows commands (e.g., nslookup, ping, Resolve-DnsName) without providing Linux equivalents. PowerShell is used for HTTP2 troubleshooting, and remote PowerShell/RDP are discussed as access methods, with no mention of SSH or Linux-native alternatives. The order of presentation typically places Windows tools and patterns before Linux ones, and some troubleshooting steps (such as downgrading Azure CLI via pip) are mentioned but lack parity in guidance for Linux package managers. There are also cases where Linux-specific errors (e.g., GLIBC version issues) are mentioned, but solutions are less detailed compared to Windows troubleshooting.
Recommendations
- Provide Linux equivalents for all command-line examples (e.g., show how to use curl, wget, dig, host, and SSH for troubleshooting).
- When discussing remote access, mention SSH and Linux console sessions alongside RDP and PowerShell.
- For DNS troubleshooting, include Linux commands such as 'dig', 'host', and 'systemd-resolve' in addition to 'nslookup' and 'Resolve-DnsName'.
- For HTTP2 troubleshooting, offer curl or wget examples with appropriate flags for Linux, not just PowerShell.
- When referencing CLI installation or downgrade, include instructions for Linux package managers (apt, yum, zypper) and not just pip.
- Ensure troubleshooting steps for Linux-specific errors (such as GLIBC version issues) are as detailed as those for Windows.
- Review the order of presentation so that Linux and Windows tools are given equal prominence, or group examples by OS.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/resource-bridge/security-overview.md
...rticles/azure-arc/resource-bridge/security-overview.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily in the 'Security audit logs' section, where PowerShell is mentioned as a method to retrieve activity log entries, but no Linux-specific tools or examples (such as Bash, Azure CLI on Linux, or REST API usage) are provided. The mention of PowerShell before Azure CLI also suggests a Windows-first approach. No Linux-specific commands, tools, or patterns are referenced throughout the page.
Recommendations
- Provide explicit examples for retrieving activity logs using Azure CLI on Linux (e.g., Bash commands).
- Mention REST API methods for log retrieval, which are platform-agnostic.
- Ensure that any command-line instructions are presented for both Windows (PowerShell) and Linux (Bash/Azure CLI) environments.
- Where possible, avoid listing Windows tools before Linux equivalents, or present them side-by-side.
- Add notes clarifying cross-platform compatibility for all tools and commands referenced.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/agent-overview.md
...blob/main/articles/azure-arc/servers/agent-overview.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
windows_heavy_detail
Summary
The documentation presents Windows agent installation details before Linux, provides more granular information about Windows-specific tools (MSI installer, service accounts, security groups, Group Policy), and includes detailed Windows folder/service/account/environment/log tables. Linux coverage is present but less detailed, with fewer references to Linux-specific system administration patterns or troubleshooting. Windows tools and concepts (MSI, Group Policy, NT SERVICE accounts) are described, while Linux equivalents (systemd, package managers, user/group management) are less emphasized.
Recommendations
- Present Linux and Windows installation details in parallel or alternate order to avoid Windows-first bias.
- Expand Linux sections to include equivalent details: describe Linux service accounts, security groups, and package management patterns.
- Provide Linux-specific troubleshooting tips (e.g., SELinux/AppArmor, systemd journal logs, permissions issues) similar to the Group Policy advice for Windows.
- Reference Linux system administration tools (e.g., systemctl, journalctl, usermod/groupmod) where appropriate.
- Ensure parity in log file descriptions, uninstall artifacts, and environment variable configuration between platforms.
- Include links to Linux package repository documentation and best practices for agent upgrades/removal.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/agent-release-notes-archive.md
...icles/azure-arc/servers/agent-release-notes-archive.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page for Azure Connected Machine agent release notes shows evidence of Windows bias. Windows download links are always listed first, and Windows-specific tools (PowerShell, MSI installer, Windows Event Logs, WMI, Windows Admin Center, etc.) are frequently mentioned, sometimes with detailed enhancements or fixes. PowerShell upgrades and telemetry are called out in multiple releases. Windows features and troubleshooting steps are often described in more detail than their Linux equivalents, and some features (e.g., GUI installer, MSI certificate handling) are exclusive to Windows. Linux-specific changes are present, but Linux examples, troubleshooting, and tool references are less frequent and sometimes missing.
Recommendations
- Alternate the order of Windows and Linux download links, or list them together without prioritization.
- Ensure Linux-specific tools (systemd, journalctl, package managers, etc.) are mentioned with equal detail and prominence as Windows tools.
- Provide Linux command-line examples and troubleshooting steps wherever Windows/PowerShell examples are given.
- Include references to Linux equivalents for Windows features (e.g., mention Linux logging and system metadata collection alongside Windows Event Logs and WMI).
- Expand documentation for Linux installation, upgrade, and error handling processes to match the depth provided for Windows.
- Add parity for GUI installer features by referencing or providing Linux installation scripts or graphical tools if available.
- Review and update documentation to ensure Linux-only features and fixes are highlighted as clearly as Windows-only ones.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/arc-gateway-endpoints.md
...in/articles/azure-arc/servers/arc-gateway-endpoints.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page lists a large number of endpoints related to Azure Arc gateway, with a noticeable emphasis on Windows-specific services and domains (e.g., windowsupdate.com, powershellgallery.com, windows.net, winatp-gw-*). There are no Linux-specific endpoints or examples, and the documentation does not mention Linux tools or patterns. The presence of Windows-oriented endpoints and the lack of Linux parity in the examples and explanations suggest a Windows bias.
Recommendations
- Include Linux-specific endpoints if applicable, such as those used by Linux Arc agents or related services.
- Add examples or notes about how Linux systems interact with the Arc gateway and which endpoints are relevant for Linux environments.
- Mention Linux tools or commands (e.g., curl, iptables, firewalld) for managing endpoint access alongside any Windows-specific tools.
- Clarify whether the endpoint list is universal for all OS types or if there are differences for Linux and Windows hosts.
- Provide guidance for both Windows and Linux administrators to ensure parity in documentation.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/azcmagent-check.md
...lob/main/articles/azure-arc/servers/azcmagent-check.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page for `azcmagent check` shows evidence of Windows bias. The only extended use case mentioned is 'Windows Server Pay-as-you-go', with no Linux equivalents or examples. There are no Linux-specific scenarios or flags referenced, and the documentation does not provide parity in examples or guidance for Linux users.
Recommendations
- Add examples relevant to Linux environments, such as connectivity checks for Linux-based extensions or services.
- Include references to Linux-specific use cases (e.g., Linux server pay-as-you-go, Linux Arc-enabled extensions).
- Ensure that documentation mentions both Windows and Linux platforms when describing supported scenarios and flags.
- Provide parity in guidance and troubleshooting steps for both Windows and Linux users.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/azcmagent-extension.md
...main/articles/azure-arc/servers/azcmagent-extension.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates Windows bias by listing Windows service management commands (Stop-Service/Start-Service) before their Linux equivalents (systemctl stop/start), and by referencing a Windows-specific extension ('AzureMonitorWindowsAgent') in the example for removing an extension. There are no Linux-specific extension examples, and the service management instructions prioritize Windows terminology and tools.
Recommendations
- Present Linux and Windows service management commands side-by-side, or alternate which platform is listed first.
- Include examples for removing Linux-specific extensions (e.g., 'AzureMonitorLinuxAgent').
- Clarify platform applicability for each command and example, ensuring parity in instructions and examples for both Windows and Linux.
- Consider a table or section explicitly mapping service management commands for both platforms.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/arc-gateway.md
...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation displays a moderate Windows bias. Windows and PowerShell examples are consistently presented alongside CLI and portal instructions, sometimes with more detail. Windows-specific tools and scenarios (e.g., Windows Admin Center, Windows Update, Defender) are mentioned explicitly, while Linux equivalents are less visible or omitted. The onboarding and monitoring sections reference Windows paths and tools first or exclusively, and Linux instructions are sometimes secondary or less detailed.
Recommendations
- Ensure Linux examples are provided for every CLI/PowerShell/portal workflow, with equal detail and clarity.
- When listing scenarios or prerequisites (e.g., Windows Update, Defender), include Linux equivalents (e.g., Linux package update mechanisms, Linux security solutions) or clarify if not applicable.
- In monitoring/logging sections, present Linux instructions and file paths with the same prominence and detail as Windows.
- Avoid listing Windows tools or scenarios (e.g., Windows Admin Center) first unless they are universally applicable; consider grouping by OS or providing parallel lists.
- Where PowerShell is used, offer Bash or shell script alternatives for Linux users.
- Explicitly state platform support and differences for all steps, especially where commands, file paths, or prerequisites diverge.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/billing-extended-security-updates.md
...azure-arc/servers/billing-extended-security-updates.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is exclusively focused on Windows Server 2012 ESUs enabled by Azure Arc, with no mention of Linux systems, Linux equivalents, or cross-platform scenarios. All examples, terminology, and referenced tools are Windows-centric, and there are no instructions or guidance for Linux environments, even though Azure Arc supports both Windows and Linux servers. The documentation assumes the reader is managing Windows workloads, omitting Linux parity in billing, licensing, and operational patterns.
Recommendations
- Include a section clarifying how ESU billing and license management applies (or does not apply) to Linux servers managed through Azure Arc.
- Add examples or notes for Linux server scenarios, even if only to state that ESUs are not relevant, to help cross-platform administrators understand the scope.
- Reference Azure Arc capabilities for Linux servers and link to relevant documentation for Linux management and billing.
- Avoid language that assumes all Azure Arc-enabled servers are Windows; specify when statements are Windows-specific.
- If there are any billing or licensing features unique to Linux servers, document those for parity.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/cloud-native/inventory-resource.md
...s/azure-arc/servers/cloud-native/inventory-resource.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Windows-centric tools and concepts (Active Directory, SCCM, Group Policy Objects) as primary analogies for Azure resource organization. Examples and comparisons are consistently drawn from Windows environments, with no mention of Linux equivalents (such as LDAP, Ansible, or Linux tagging/grouping mechanisms). The only OS-specific example in Azure Resource Graph queries is for 'Windows Server 2012', with no Linux server example provided. There are no Linux-specific tools, patterns, or terminology referenced, and no PowerShell or Bash examples are given, but the overall framing assumes familiarity with Windows administration.
Recommendations
- Include analogies and comparisons to Linux server management concepts (e.g., LDAP, systemd units, Ansible inventory, etc.) alongside Windows/AD references.
- Provide examples of Azure Resource Graph queries for Linux servers (e.g., finding all Ubuntu servers, or servers with specific Linux packages installed).
- Mention Linux-native tagging and grouping patterns, such as using system attributes, configuration management tools, or inventory files.
- Reference Linux configuration management and inventory tools (e.g., Chef, Puppet, Ansible) when discussing change tracking and inventory.
- Ensure that examples and analogies are balanced between Windows and Linux, or presented in a platform-neutral way.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/cloud-native/next-steps.md
.../articles/azure-arc/servers/cloud-native/next-steps.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric onboarding methods (Windows Admin Center, Configuration Manager, GPOs, WSUS) and omitting equivalent Linux examples or tools. Windows tools and management patterns are mentioned exclusively or before any Linux alternatives, and there are no explicit Linux onboarding or configuration examples provided.
Recommendations
- Add onboarding instructions and examples for Linux servers, such as using shell scripts, cloud-init, or Ansible.
- Mention Linux-native configuration management tools (e.g., Chef, Puppet, Ansible) alongside Windows GPOs.
- Provide examples of patch management for Linux (e.g., using Azure Update Manager with Linux, or integration with apt/yum/zypper).
- Include references to Linux command-line tools and automation patterns (e.g., Bash, systemd, cron) in automation sections.
- Ensure that documentation covers both Windows and Linux server management scenarios equally, with parallel examples and guidance.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/cloud-native/monitor-alerts.md
...icles/azure-arc/servers/cloud-native/monitor-alerts.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (System Center Operations Manager), mentioning Windows Event logs before Linux syslog, and lacking concrete Linux-specific examples or command-line instructions. The examples and terminology are more familiar to Windows administrators, with little detail on Linux workflows or equivalents.
Recommendations
- Provide explicit Linux examples for agent deployment, data collection, and log sources (e.g., show how to configure syslog collection, reference Linux package managers for agent installation).
- Mention Linux tools and patterns alongside Windows ones, such as referencing open-source monitoring tools commonly used on Linux.
- Balance the order of examples: mention Linux syslog before or alongside Windows Event logs.
- Include sample commands or configuration snippets for both Windows (PowerShell) and Linux (Bash/CLI) environments.
- Add troubleshooting and visualization guidance tailored to Linux administrators.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/azure-monitor-agent-deployment.md
...es/azure-arc/servers/azure-monitor-agent-deployment.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned repeatedly as a primary automation and management tool, with no equivalent emphasis on Bash or Linux-native scripting. Examples and references to deployment methods (Azure portal, PowerShell, Azure CLI, ARM templates) are listed in an order that prioritizes Windows-centric tools. There are no explicit Linux/Bash command examples or references to Linux-specific tooling, and the documentation does not provide parity in guidance for Linux administrators.
Recommendations
- Include explicit Bash and Linux-native command examples alongside PowerShell, especially for deployment and automation scenarios.
- When listing deployment options, alternate or balance the order so that Linux tools (e.g., Bash, shell scripts) are mentioned equally or first in some cases.
- Add references to Linux package managers (such as apt, yum, or zypper) if relevant for agent installation.
- Clarify which instructions or scripts apply to Windows, Linux, or both, and provide OS-specific guidance where necessary.
- Highlight Linux automation options (e.g., cron jobs, Ansible, shell scripts) in the Azure Automation section, not just PowerShell and Python.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/cloud-native/governance-policy.md
...es/azure-arc/servers/cloud-native/governance-policy.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows-centric tools (Group Policy, Active Directory, RSoP, gpresult), providing examples and built-in policies only for Windows scenarios (e.g., password complexity, Windows Firewall), and omitting explicit Linux examples or equivalent Linux tools. The discussion of policy enforcement and auditing is framed almost exclusively in terms of Windows server management, with no mention of Linux-specific settings, compliance scenarios, or how Azure Policy applies to Linux servers.
Recommendations
- Add explicit examples of Azure Policy auditing and enforcement for Linux servers, such as checking SSH configuration, file permissions, or Linux firewall (iptables/nftables) rules.
- Reference Linux equivalents to Windows tools (e.g., mention how compliance can be checked via tools like auditd, or configuration managed via Ansible/Puppet/Chef alongside DSC).
- Include built-in policy examples for Linux, such as enforcing password policies in /etc/login.defs, ensuring SELinux/AppArmor is enabled, or auditing systemd service status.
- Balance the discussion by describing how Azure Policy interacts with both Windows and Linux servers, including differences in agent behavior, supported settings, and reporting.
- Provide parity in documentation structure, ensuring that Linux scenarios are described with the same depth and clarity as Windows scenarios.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/cloud-native/licensing-cost-management.md
...-arc/servers/cloud-native/licensing-cost-management.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page focuses exclusively on Windows Server and SQL Server licensing options with Azure Arc, providing detailed examples and workflows for Windows environments. There is no mention of Linux server licensing, cost management, or patching scenarios. All tools and processes referenced (e.g., Azure Update Manager, ESUs, product keys) are specific to Windows, and the narrative assumes a Windows-centric environment throughout.
Recommendations
- Add equivalent examples and guidance for Linux servers managed by Azure Arc, including licensing, cost management, and patching workflows.
- Explicitly state whether Linux servers are supported for pay-as-you-go licensing or ESUs, and describe any differences in management or billing.
- Include references to Linux-native tools (such as package managers, update mechanisms, or compliance tools) and how they integrate with Azure Arc.
- Provide cross-platform comparison tables or sections to clarify feature parity and highlight any Windows-specific limitations.
- Ensure that introductory and summary sections acknowledge both Windows and Linux server scenarios to avoid implicit Windows-first bias.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/cloud-native/overview.md
...in/articles/azure-arc/servers/cloud-native/overview.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits a Windows bias by referencing traditional Windows management tools (Active Directory Group Policy, SCCM, MECM, PowerShell remoting, WSUS) as the primary legacy equivalents for Azure Arc features. These tools are mentioned exclusively or before any Linux alternatives, and there are no explicit examples or references to common Linux management tools or patterns (such as Ansible, Chef, Puppet, or native Linux patching/configuration mechanisms). The scripting and patching sections do not provide Linux-specific context or examples, and the licensing section focuses solely on Windows Server and SQL Server, omitting Linux licensing considerations.
Recommendations
- Include references to common Linux management tools (e.g., Ansible, Chef, Puppet, cron, yum/apt) when discussing legacy server management, alongside Windows tools.
- Provide examples or scenarios for both Windows and Linux servers when describing Azure Arc features (e.g., show how Run Command can execute Bash scripts as well as PowerShell scripts).
- Mention Linux-specific patching and configuration workflows (such as package managers, systemd, or configuration files) when discussing Azure Update Manager and Machine Configuration.
- Add a note about licensing implications for Linux servers, even if Azure Arc does not directly manage Linux licensing, to clarify parity.
- Balance introductory analogies (such as Active Directory/System Center) with Linux equivalents (e.g., LDAP, local configuration management) to make the documentation more inclusive.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/cloud-native/patch-management.md
...les/azure-arc/servers/cloud-native/patch-management.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (WSUS, SCCM) first and in detail, describing features in terms of their Windows equivalents, and providing examples and analogies rooted in Windows administration. Hotpatching is discussed only for Windows Server, and there are no concrete Linux command or workflow examples. Linux support is mentioned, but with less detail and no practical examples, making the documentation less accessible for Linux administrators.
Recommendations
- Provide equivalent Linux examples for patch management workflows, such as using apt, yum, or zypper commands, and how Azure Update Manager interacts with these.
- Include analogies or references to common Linux patch management tools (e.g., Landscape, Spacewalk, dnf-automatic, unattended-upgrades) alongside Windows tools.
- Add step-by-step Linux-specific scenarios (e.g., patching Ubuntu or RHEL servers) with sample commands and expected outcomes.
- Clarify hotpatching support for Linux, or explicitly state its absence, and discuss any analogous Linux features if available.
- Balance the order and emphasis of Windows and Linux content, ensuring Linux is not always secondary or an afterthought.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/deliver-extended-security-updates.md
...azure-arc/servers/deliver-extended-security-updates.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows Server 2012 and its management within Azure Arc, with all examples, screenshots, and scenarios exclusively referencing Windows environments. There are no Linux equivalents or cross-platform considerations mentioned, and all patching solutions and license management steps are tailored to Windows-specific tools and workflows.
Recommendations
- Explicitly state whether the ESU delivery process is Windows-only, or clarify if Linux servers onboarded to Azure Arc are supported or excluded.
- If Linux support exists, provide parallel instructions and examples for managing ESUs or similar security updates on Linux Arc-enabled servers.
- Mention Linux-compatible patch management solutions (e.g., apt, yum, Azure Update Management for Linux) alongside Windows tools like WSUS and Configuration Manager.
- Include screenshots or CLI examples (such as Bash or Azure CLI) relevant to Linux environments where applicable.
- Add a section comparing Windows and Linux server update/ESU workflows in Azure Arc to help administrators understand platform differences.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/deployment-options.md
.../main/articles/azure-arc/servers/deployment-options.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page lists deployment options for both Linux and Windows, but several onboarding methods and tools are Windows-specific (e.g., Windows Admin Center, Group Policy, Configuration Manager, Windows Server setup). PowerShell is highlighted as a cross-platform method, but there is no mention of Linux-native automation tools (like shell scripts or cloud-init) in the same detail. Windows-specific tools and workflows are described in dedicated sections, while Linux equivalents are absent or not given equal prominence.
Recommendations
- Add Linux-specific onboarding examples, such as using Bash scripts, cloud-init, or native Linux automation tools.
- Provide parity for Windows-only methods by listing Linux equivalents where possible (e.g., for Group Policy, suggest Ansible or Puppet for Linux).
- Ensure that PowerShell is not presented as the primary or only automation method for Linux; mention and link to Linux-native alternatives.
- Balance the order and prominence of Windows and Linux tools/methods in tables and documentation structure.
- Include step-by-step Linux onboarding guides alongside Windows guides for each method.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/manage-automatic-vm-extension-upgrade.md
...e-arc/servers/manage-automatic-vm-extension-upgrade.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page generally presents Windows and Linux as equally supported for Azure Arc-enabled server extension upgrades. However, there are subtle signs of Windows bias: PowerShell is given its own dedicated example section, while Linux-specific shell examples (e.g., bash scripts) are not provided. The order of tools often lists Windows-centric options (Azure portal, PowerShell) before Linux-friendly ones (CLI), and some extension examples and supported extensions are Windows-only. There is no explicit Linux shell scripting or troubleshooting guidance, and the use of PowerShell is emphasized more than Linux-native tools.
Recommendations
- Add explicit Linux shell (bash/zsh) scripting examples alongside PowerShell, especially for common management tasks.
- Ensure CLI examples use Linux shell syntax (e.g., with environment variables, piping, etc.) where relevant.
- List CLI and Linux-friendly tools before or alongside PowerShell in tool recommendations and example sections.
- Include troubleshooting steps or tips specific to Linux environments (e.g., log file locations, permissions).
- Clarify extension support for Linux and Windows, and provide parity in extension feature documentation.
- Where Windows-only extensions are mentioned, highlight Linux equivalents or alternatives if available.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/cloud-native/scripting-task-automation.md
...-arc/servers/cloud-native/scripting-task-automation.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by frequently referencing Windows tools and patterns (such as RDP, PowerShell, SCCM, and Windows Task Scheduler) before or instead of their Linux equivalents. PowerShell is emphasized as the primary scripting language, and examples or scenarios are described in Windows-centric terms. Linux tools and workflows are mentioned less frequently, and there are no concrete Linux-specific scripting examples or references to common Linux automation tools (e.g., Bash, cron, Ansible).
Recommendations
- Provide parallel Linux examples for all automation scenarios, using Bash or Python scripts and referencing common Linux tools (e.g., cron for scheduling, systemd for service management).
- When introducing automation concepts, mention Linux and Windows approaches together, rather than defaulting to Windows-first patterns (e.g., 'In a traditional environment, you might use RDP and PowerShell for Windows, or SSH and Bash scripts for Linux').
- Include Linux-native automation tools (e.g., Ansible, shell scripts, cron jobs) in the discussion alongside Windows tools like SCCM and Task Scheduler.
- Show example commands for both PowerShell and Bash/Python when demonstrating Run Command or Azure Automation usage.
- Highlight Linux authentication and management features (such as Entra ID for SSH, sudo usage, etc.) with equal prominence to Windows features.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/includes/network-requirements.md
...les/azure-arc/servers/includes/network-requirements.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
windows_admin_center_emphasis
windows_tls_details
linux_example_missing
Summary
The documentation page exhibits a moderate Windows bias. Windows-related endpoints (e.g., download.microsoft.com, Windows Admin Center) are listed before Linux equivalents (e.g., packages.microsoft.com), and Windows-specific tools and scenarios (Windows Admin Center, Windows Server versions) are mentioned more prominently and in greater detail. TLS configuration guidance is more detailed for Windows, with Linux relegated to a brief note about OpenSSL. There are no Linux-specific configuration examples, troubleshooting links, or tool mentions beyond the basic package source.
Recommendations
- Present Linux and Windows endpoints/examples in parallel, rather than listing Windows first.
- Include Linux-specific troubleshooting guidance and links (e.g., OpenSSL configuration, common Linux firewall/proxy tools).
- Add parity for Linux management tools (e.g., mention Cockpit, Ansible, or other Linux equivalents to Windows Admin Center where relevant).
- Expand TLS configuration instructions for Linux, including example OpenSSL settings and common pitfalls.
- Where Windows-specific features (e.g., hotpatching, Windows Admin Center) are mentioned, clarify Linux alternatives or note their absence.
- Ensure that all tables and lists present Linux and Windows options with equal prominence and detail.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/license-extended-security-updates.md
...azure-arc/servers/license-extended-security-updates.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows Server 2012 environments, with all examples, scenarios, and licensing models centered around Windows Server. There are no examples or guidance for Linux servers or non-Windows workloads, and all operational details (such as Azure Arc onboarding and license linking) are described exclusively for Windows. Windows-specific licensing terms and tools are mentioned throughout, with no Linux parity or alternatives discussed.
Recommendations
- Add equivalent guidance and examples for Linux servers, such as how to manage ESU-like updates or licensing for Linux workloads through Azure Arc.
- Include scenario-based examples for mixed environments (Windows and Linux), showing how Azure Arc can be used for both.
- Clarify whether any of the described licensing or management operations apply to Linux servers, and if not, explicitly state the scope.
- Reference Linux tools, patterns, or best practices where relevant, and provide links to Linux-specific documentation for Azure Arc.
- Ensure that onboarding instructions and next steps include Linux server options and documentation.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/manage-vm-extensions-portal.md
...icles/azure-arc/servers/manage-vm-extensions-portal.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates subtle Windows bias. While it claims to cover both Linux and Windows hybrid machines, the only specific example provided is for deploying the Azure Monitor agent for Windows using a proxy. No Linux-specific extension configuration or examples are given. Additionally, the mention of Azure PowerShell (a Windows-centric tool) appears before Azure CLI in both the notes and related content, and no Linux command-line tools or patterns are referenced.
Recommendations
- Add explicit examples for deploying and configuring extensions on Linux machines, including any Linux-specific configuration fields or requirements.
- When listing command-line tools, mention Azure CLI before Azure PowerShell, as CLI is cross-platform and more commonly used on Linux.
- Include screenshots or configuration walkthroughs for Linux extensions (e.g., the Azure Monitor agent for Linux), not just Windows.
- Clarify any differences in extension support, configuration, or troubleshooting between Linux and Windows Arc-enabled servers.
- Review and balance references to Windows-specific tools and patterns with equivalent Linux approaches where applicable.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/modernize-server-management.md
...icles/azure-arc/servers/modernize-server-management.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows-first bias in several areas. Windows licensing and onboarding methods (Scheduled Task, Configuration Manager) are mentioned before Linux equivalents, and Windows-specific tools (SCVMM, SCOM, Windows Server Software Assurance) are referenced without Linux alternatives. Examples and onboarding instructions are tailored to Windows environments, with no explicit Linux onboarding or management workflow guidance. Although Linux support is acknowledged, practical Linux examples and parity in tooling are missing.
Recommendations
- Provide onboarding instructions for Linux servers, including agent installation via native Linux tools (systemd, cron, shell scripts) and package managers.
- Include Linux-specific examples and workflows for each core functionality (patching, configuration, reporting, security, scripting, software distribution).
- Mention Linux equivalents or alternatives to Windows tools (e.g., alternatives to Scheduled Task, Configuration Manager, SCVMM, SCOM) and clarify how Azure Arc integrates with common Linux management solutions.
- Ensure that examples and guidance are presented for both Windows and Linux environments, ideally side-by-side, to demonstrate parity.
- Highlight any limitations or differences in feature support between Windows and Linux, and provide guidance for Linux administrators transitioning from SCCM.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/onboard-portal.md
...blob/main/articles/azure-arc/servers/onboard-portal.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows installation instructions and examples are presented before Linux, with detailed steps using Windows Installer (msiexec.exe) and PowerShell commands. Windows-specific tools and patterns (such as .msi installers, PowerShell, and Windows environment variables) are described in depth, while Linux instructions are comparatively concise and lack equivalent troubleshooting and validation detail. The scripted method for onboarding is described for both platforms, but Windows examples (PowerShell, msiexec) are more prominent and detailed.
Recommendations
- Present Linux and Windows instructions in parallel or alternate their order to avoid implicit prioritization.
- Provide equally detailed Linux troubleshooting and validation steps, including log file locations and common error resolutions.
- Include Linux-specific command-line options and environment variable configuration examples (e.g., using export, systemd service management).
- Ensure that Linux tools and patterns (such as package managers, shell scripting, and systemctl) are explained with the same depth as Windows tools.
- Add references to Linux documentation for agent management and configuration, similar to the Windows msiexec documentation links.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/manage-vm-extensions-template.md
...les/azure-arc/servers/manage-vm-extensions-template.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias primarily through exclusive use of PowerShell for deployment commands, with no mention or examples of Azure CLI or Bash equivalents for Linux users. All command-line instructions use PowerShell syntax and Windows-style file paths, and the deployment workflow assumes the use of Windows tools. While ARM template examples are provided for both Linux and Windows extensions, the operational steps and instructions are Windows-centric, potentially making it less accessible for Linux administrators.
Recommendations
- Provide equivalent Azure CLI and Bash examples for deploying ARM templates, especially for Linux users.
- Include Linux-style file paths in examples, or clarify that paths should be adapted for Linux environments.
- Explicitly mention and demonstrate how Linux users can perform deployments using native tools (e.g., Azure CLI on Bash).
- Reorganize deployment instructions to present both Windows and Linux workflows in parallel, rather than focusing on Windows/PowerShell first.
- Add notes or sections highlighting any OS-specific considerations for deployment commands and tools.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/managed-identity-authentication.md
...s/azure-arc/servers/managed-identity-authentication.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows and PowerShell examples are presented first and in greater detail, with explicit references to PowerShell for access policy assignment and token acquisition. Windows-specific tools and group memberships are mentioned before their Linux equivalents, and links to Windows instructions often precede or are more prominent than Linux ones. While Linux/Bash examples are present, they are less detailed and sometimes require additional steps (e.g., needing an SSH client). Some instructions and references (such as access policy assignment) are PowerShell-centric, with CLI alternatives mentioned only in 'Next steps'.
Recommendations
- Present Linux and Windows examples side-by-side or alternate which comes first to avoid implicit prioritization.
- Provide equally detailed Bash/Linux examples for all PowerShell/Windows instructions, including access policy assignment and token acquisition.
- Include direct references and links to Linux/CLI instructions wherever Windows/PowerShell links are given.
- Mention Linux group memberships and prerequisites before or alongside Windows equivalents.
- Add screenshots or output examples for Linux/Bash commands, matching the detail given for PowerShell.
- Where PowerShell is used for resource management, provide Azure CLI or Bash alternatives in the main content, not just in 'Next steps'.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/migrate-legacy-agents.md
...in/articles/azure-arc/servers/migrate-legacy-agents.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by mentioning Windows-specific tools (Windows Admin Center, Windows Server Graphical Installer) and deployment methods before Linux equivalents. PowerShell is referenced as a primary scripting option, while Bash is mentioned only in passing and no Linux-specific deployment tools (e.g., cloud-init, systemd, shell scripts) are highlighted. There are no explicit Linux examples or guidance for Linux environments, and standalone agent installation is only described for Windows clients.
Recommendations
- Add explicit Linux deployment examples, such as using shell scripts, cloud-init, or systemd for agent installation and configuration.
- Mention Linux-native tools (e.g., Ansible, Chef, Puppet) with equal prominence to Windows tools for at-scale deployment.
- Provide standalone Azure Monitor Agent installation instructions for Linux client machines, not just Windows.
- Ensure that scripting examples (e.g., PowerShell, Bash) are presented in parallel, with full examples for both platforms.
- List deployment options for Windows and Linux together, or alternate the order to avoid Windows-first presentation.
- Reference Linux-specific documentation links where appropriate, similar to the Windows client installer link.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/onboard-configuration-manager-custom-task.md
...c/servers/onboard-configuration-manager-custom-task.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a clear Windows bias: all examples and instructions are tailored exclusively for Windows environments, specifically using Microsoft Configuration Manager and Windows Installer (.msi) packages. The agent download, application creation, and task sequence steps are Windows-centric, with no mention of Linux equivalents or cross-platform considerations. PowerShell is the only scripting language referenced, and there are no examples or guidance for onboarding Linux servers or using Linux-native tools.
Recommendations
- Add equivalent instructions for onboarding Linux machines at scale, including agent download and installation steps for Linux (e.g., .deb, .rpm packages).
- Provide sample task sequences or automation scripts using Linux-native tools (such as shell scripts, Ansible, or cloud-init) and demonstrate how to connect Linux servers to Azure Arc.
- Include examples using Bash or other Linux scripting languages alongside PowerShell.
- Clarify which steps are Windows-specific and offer parallel guidance for Linux environments.
- Reference cross-platform management tools or workflows where applicable, not just Configuration Manager.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/onboard-service-principal.md
...rticles/azure-arc/servers/onboard-service-principal.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows and PowerShell are mentioned first or more prominently in several places, such as the creation of service principals and installation scripts. PowerShell examples are provided in detail, while Linux-specific command-line examples are less emphasized or absent. The troubleshooting and agent installation sections also focus on Windows tools and patterns, with limited Linux-specific troubleshooting or automation guidance.
Recommendations
- Ensure Linux examples (e.g., Bash, shell scripting) are provided alongside or before Windows/PowerShell examples.
- Balance the order of presentation so that Linux and Windows instructions alternate or are grouped together, rather than Windows-first.
- Include Linux-specific troubleshooting steps and notes, especially for common issues encountered during onboarding.
- Provide parity in automation guidance, such as sample scripts for Linux environments (e.g., Bash, Ansible) where PowerShell scripts are shown for Windows.
- Explicitly mention cross-platform compatibility for tools like Azure CLI and azcmagent, and clarify any OS-specific limitations.
- Add links to Linux admin guides or best practices for Azure Arc onboarding, similar to those provided for Windows.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/plan-at-scale-deployment.md
...articles/azure-arc/servers/plan-at-scale-deployment.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows and PowerShell are mentioned before Linux in several places, such as when creating a service principal ('using Azure PowerShell or from the Azure portal') and in onboarding scripts. There is a lack of explicit Linux command-line or automation tool examples (e.g., Bash, SSH, Ansible), and no Linux-specific tooling or patterns are highlighted. Most examples and instructions are either generic or Windows/PowerShell-centric, with Linux only referenced as an afterthought or in combined links.
Recommendations
- Provide explicit Linux command-line examples (e.g., Bash scripts, CLI commands) alongside PowerShell and portal instructions.
- Mention Linux automation tools (e.g., Ansible, Chef, Puppet) as options for deploying the Connected Machine agent.
- Ensure that Linux is referenced equally or first in lists and examples, not only as a secondary option.
- Include troubleshooting and management instructions specific to Linux environments (e.g., systemd service management, log file locations).
- Highlight Linux-specific considerations (e.g., package managers, SELinux/AppArmor, root permissions) where relevant.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/prerequisites.md
.../blob/main/articles/azure-arc/servers/prerequisites.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates several forms of Windows bias. Windows-specific tools (such as PowerShell and Group Policy Editor) are mentioned and explained in detail, while Linux equivalents are either omitted or referenced only briefly. Script examples for agent installation adjustments are provided only for Windows (PowerShell), with no corresponding Linux command-line example. Windows configuration steps (e.g., user rights assignment) are described with screenshots and step-by-step instructions, whereas Linux system requirements are listed without further guidance. In sections where both platforms are relevant, Windows instructions and tools are presented first or exclusively.
Recommendations
- Provide Linux-specific onboarding script examples, especially for limited support scenarios, such as showing how to install a specific agent version using package managers (e.g., apt, yum, zypper).
- Include Linux equivalents for configuration tasks, such as managing service permissions or troubleshooting agent startup (e.g., systemd service configuration, checking logs).
- Balance the order of presentation so that Linux instructions and examples are given equal prominence and detail as Windows.
- Add screenshots or step-by-step instructions for common Linux administrative tasks relevant to the agent (e.g., verifying required packages, checking service status).
- Explicitly mention Linux tools and patterns (e.g., sudo, systemctl, package repositories) where appropriate, not just in passing.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/onboard-update-management-machines.md
...zure-arc/servers/onboard-update-management-machines.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation describes onboarding both Windows and Linux machines to Azure Arc via Automation Update Management, but operational details and examples are Windows-centric. Runbook names and references (e.g., Add-UMMachinesToArc, Add-UMMachinesToArcWindowsChild) use PowerShell-style naming conventions, and instructions for monitoring and troubleshooting refer to Azure PowerShell and Windows-first workflows. There are no explicit Linux command-line examples or references to Linux-native tools, and the documentation does not provide parity in Linux-specific guidance.
Recommendations
- Include explicit Linux command-line examples (e.g., Bash, shell scripts) for onboarding and verification steps.
- Reference Linux-native tools (such as CLI commands, systemd, journalctl) alongside or before Windows equivalents.
- Provide screenshots or walkthroughs from Linux environments in addition to Windows/Azure portal views.
- Clarify that runbooks and automation workflows support both PowerShell and Bash, and provide sample scripts for each.
- Ensure troubleshooting and verification steps include Linux-specific guidance (e.g., checking agent status via systemctl, reviewing logs in /var/log).
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/plan-evaluate-on-azure-virtual-machine.md
...-arc/servers/plan-evaluate-on-azure-virtual-machine.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a mild Windows bias. Windows examples and tools (PowerShell, WindowsAzureGuestAgent, New-NetFirewallRule) are consistently presented first, with more detailed and explicit instructions. Linux equivalents are provided, but sometimes with less detail or with references to external documentation. Windows-specific tooling (PowerShell, Windows firewall) is mentioned before Linux alternatives, and some Linux instructions are less direct (e.g., 'consult your distribution's documentation').
Recommendations
- Alternate the order of Windows and Linux instructions throughout the documentation to avoid consistently prioritizing Windows.
- Provide equally detailed, step-by-step Linux instructions for all major distributions (not just Ubuntu, Red Hat, SUSE), or link to official docs for each.
- Include direct Linux command examples for all steps where Windows PowerShell is used, rather than referring users to external documentation.
- Where Windows tools are mentioned (e.g., PowerShell, Windows firewall), ensure Linux equivalents (e.g., iptables, nftables, firewalld) are described with similar clarity and completeness.
- Add troubleshooting tips and verification steps for Linux users, matching those provided for Windows.
- Review and update links to ensure Linux VM deployment templates are correct (the Ubuntu link currently points to a Windows template).
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/prepare-extended-security-updates.md
...azure-arc/servers/prepare-extended-security-updates.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows Server 2012/2012 R2, with all examples, deployment options, and tooling references tailored to Windows environments. There are no Linux-specific instructions, examples, or mentions of Linux equivalents for onboarding, patching, or managing servers with Azure Arc. Windows tools and patterns (Group Policy, Configuration Manager, SCVMM, VDI, MAK keys) are referenced exclusively, and no parity is provided for Linux systems.
Recommendations
- Add explicit statements clarifying whether Linux servers are supported or not for ESU delivery via Azure Arc.
- If Linux onboarding is possible, provide equivalent Linux examples (e.g., shell scripts, Linux agent installation, Linux patching workflows).
- Include Linux-centric deployment options (such as Ansible, SSH, or Linux-native automation tools) alongside Windows tools like Group Policy and Configuration Manager.
- Mention Linux-specific networking and certificate installation steps if applicable.
- Ensure documentation structure does not assume Windows-first by default; provide parallel guidance for Linux where relevant.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/run-command-rest.md
...ob/main/articles/azure-arc/servers/run-command-rest.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All example scenarios, scripts, and references are exclusively for Windows Server (specifically Windows Server 2012/R2) and use PowerShell cmdlets (e.g., New-NetFirewallRule). There are no examples or guidance for Linux servers, nor are Linux shell scripts or tools mentioned. Even instructions for generating SAS tokens reference PowerShell tools (New-AzStorageBlobSASToken) without Linux alternatives.
Recommendations
- Add parallel example scenarios for Linux Arc-enabled servers, including sample shell scripts (e.g., using iptables or ufw for firewall rules).
- Explicitly mention Linux support and provide guidance for Linux-specific Run command usage.
- Include instructions for generating SAS tokens using Azure CLI or REST API, which are cross-platform.
- Clarify in the prerequisites or introduction which OS platforms are supported and ensure both Windows and Linux are covered.
- Balance references to PowerShell with equivalent Bash or shell script examples and tools.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/quick-enable-hybrid-vm.md
...n/articles/azure-arc/servers/quick-enable-hybrid-vm.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. In the installation section, Windows instructions (using PowerShell) are presented before Linux instructions, and the Windows steps are more detailed (e.g., specifying 'elevated 64-bit PowerShell'). The Linux section is shorter and less detailed. The script generation and portal steps are OS-neutral, but the overall pattern prioritizes Windows terminology and tools.
Recommendations
- Alternate the order of Windows and Linux instructions in each section, or present them in parallel tabs to avoid implicit prioritization.
- Provide equally detailed steps for Linux, including information about required permissions, shell environment, and any prerequisites (e.g., bash version, package manager).
- Where PowerShell is referenced for Windows, mention the equivalent shell (e.g., Bash) for Linux in the same level of detail.
- Avoid using Windows-specific terminology (e.g., 'elevated PowerShell') without providing the Linux equivalent (e.g., 'run as root or with sudo').
- Consider including screenshots or command-line examples for both platforms to ensure parity.
- Where possible, use cross-platform language and tools, or clearly indicate when a step is OS-specific.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/run-command-cli.md
...lob/main/articles/azure-arc/servers/run-command-cli.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell script examples (e.g., 'Write-Host Hello World!') and omitting any Linux shell script (bash/sh) examples. The only script shown uses a Windows-centric command, and there is no mention of Linux tools or patterns. This may lead Linux users to feel unsupported or unclear about how to use the feature with bash scripts.
Recommendations
- Add equivalent Linux shell script examples (e.g., 'echo Hello World!') alongside PowerShell examples.
- Explicitly state that both Windows and Linux Arc-enabled servers are supported, and clarify any platform-specific considerations.
- Where possible, provide side-by-side examples for common tasks (e.g., one PowerShell, one bash) to ensure parity.
- Mention any differences in script execution environments or output handling between Windows and Linux.
- Avoid using only Windows-centric commands in introductory examples; alternate or combine with Linux equivalents.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/scenario-migrate-to-azure.md
...rticles/azure-arc/servers/scenario-migrate-to-azure.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a Windows bias by prioritizing Azure PowerShell examples and references, mentioning PowerShell before Azure CLI, and providing detailed PowerShell instructions without equivalent Linux shell examples. While Linux is mentioned in the context of the Azure Guest Agent, there are no explicit Linux command-line examples or references to Linux-native tools, and PowerShell is presented as the primary method for inventorying and managing resources.
Recommendations
- Provide Linux shell (bash) command examples alongside PowerShell, especially for inventorying extensions and managing role assignments.
- Explicitly mention and demonstrate how to perform key steps (such as uninstalling the Connected Machine agent and managing VM extensions) on Linux systems, including relevant commands.
- Ensure that references to Azure CLI are given equal prominence and detail as PowerShell, and consider listing CLI examples before or alongside PowerShell to avoid Windows-first ordering.
- Include troubleshooting and migration guidance specific to Linux environments, such as handling Linux-specific agents and extensions.
- Add links to Linux documentation and best practices where Windows documentation is referenced.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/run-command.md
...cs/blob/main/articles/azure-arc/servers/run-command.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page mentions support for both Windows and Linux, but the examples and next steps prioritize PowerShell and Azure CLI (which often have Windows-centric usage patterns). There are no explicit Linux shell (bash) examples, and the documentation refers to PowerShell before CLI and REST, suggesting a Windows-first perspective. There is no mention of Linux-specific tools, shell scripts, or usage patterns, and no examples tailored for Linux administrators.
Recommendations
- Add explicit Linux shell (bash) examples for using Run command, including sample scripts and command invocations.
- Ensure parity in documentation by providing both Windows (PowerShell) and Linux (bash/sh) script examples in all relevant sections.
- Mention Linux-specific administrative tasks (e.g., apt/yum updates, iptables configuration) alongside Windows tasks.
- Reorder examples and references so that Windows and Linux are treated equally, or alternate which is mentioned first.
- Clarify any differences in usage or limitations between Windows and Linux environments.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/security-machine-configuration.md
...es/azure-arc/servers/security-machine-configuration.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by emphasizing PowerShell Desired State Configuration as the foundation for Azure Machine Configuration, mentioning Windows Admin Center (WAC) as a primary remote management tool, and providing detailed descriptions of Windows-specific workflows and roles. Linux is referenced mainly in the context of SSH access, but there are no Linux-specific configuration or management examples, and Windows tools/patterns are described first and in more detail.
Recommendations
- Include Linux-specific examples for configuration management, such as using native Linux tools (e.g., Ansible, Chef, or native shell scripts) alongside PowerShell DSC.
- Provide parity in remote management tooling by mentioning or recommending Linux equivalents to Windows Admin Center, such as Cockpit or Webmin, and describe how they can be integrated with Azure Arc.
- Present examples and workflows for both Windows and Linux systems side-by-side, ensuring that Linux instructions are not omitted or relegated to secondary status.
- Clarify role assignments and access patterns for Linux systems, including details on how RBAC and Entra ID integration work for Linux beyond SSH.
- Add troubleshooting and best practices sections for Linux environments, similar to those provided for Windows.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/security-onboarding.md
...main/articles/azure-arc/servers/security-onboarding.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several areas: Windows-specific tools and patterns (Group Policy, Microsoft Update, WSUS) are mentioned before or in more detail than their Linux equivalents; PowerShell is referenced for extension management and onboarding, but Linux command-line examples are absent; onboarding guidance links to Windows/PowerShell-specific instructions without Linux parity; and automation tooling examples prioritize Microsoft Configuration Manager and Group Policy over Linux-first tools like Ansible.
Recommendations
- Provide Linux-specific onboarding examples and guidance, including shell script and configuration file encryption best practices.
- Include Linux command-line examples (bash, shell, etc.) alongside PowerShell for extension management and onboarding.
- Reference Linux-native automation tools (e.g., Chef, Puppet, SaltStack) equally with Windows tools.
- Ensure links to onboarding guidance include Linux-focused documentation, not just Group Policy/PowerShell.
- Present update management instructions for Linux (apt, yum, etc.) before or alongside Windows update mechanisms.
- Clarify disk encryption recommendations with Linux-first examples (e.g., dm-crypt, LUKS) and provide parity with BitLocker.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/security-identity-authorization.md
...s/azure-arc/servers/security-identity-authorization.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page demonstrates mild Windows bias. File paths and group names are consistently listed with Windows examples first (e.g., 'C:\ProgramData\...' before '/var/opt/...'), and Windows-specific terminology (such as 'administrators', 'Hybrid agent extension applications') is mentioned before Linux equivalents. The documentation references Windows tools and patterns (e.g., access control lists, directory structure) and omits explicit Linux command-line or shell examples, focusing more on Windows conventions.
Recommendations
- Alternate the order of Windows and Linux examples so that Linux is sometimes presented first.
- Provide explicit Linux shell command examples (e.g., chmod, chown) for managing access to certificate and token directories.
- Clarify group and user mappings for Linux (e.g., explain 'himds' and how to add users to this group on Linux).
- Include Linux-specific troubleshooting steps and patterns where relevant.
- Ensure parity in screenshots and video content, showing both Windows and Linux environments.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/security-overview.md
...b/main/articles/azure-arc/servers/security-overview.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias in several ways: it references PowerShell Desired State Configuration as the basis for guest configuration policies without mentioning Linux equivalents, describes Windows service accounts in detail before Linux, and provides extension allowlist examples only for Windows agents. There are no explicit Linux command examples or references to Linux-native configuration tools or patterns.
Recommendations
- Provide Linux-specific examples for extension allowlists and agent configuration, including azcmagent commands relevant to Linux environments.
- Mention Linux equivalents to PowerShell Desired State Configuration, such as Ansible, Chef, or native shell scripts, for guest configuration policies.
- Describe Linux service/daemon accounts with equal detail and order as Windows service accounts.
- Include references to Linux security best practices (e.g., SELinux, AppArmor, systemd hardening) alongside Windows recommendations.
- Ensure all examples and recommendations are presented for both Windows and Linux, or clarify when a feature is Windows-only.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/ssh-arc-troubleshoot.md
...ain/articles/azure-arc/servers/ssh-arc-troubleshoot.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits a Windows bias by prioritizing PowerShell-based troubleshooting steps and examples, referencing Windows-specific error codes (e.g., WinError), and focusing on Azure PowerShell modules and commands. Linux equivalents (such as bash or shell commands) are either missing or mentioned only in error messages, with no corresponding troubleshooting steps or examples. The guidance assumes the use of PowerShell and Windows tools, with little attention to Linux-native workflows or commands.
Recommendations
- Provide Linux-specific troubleshooting steps and examples alongside PowerShell instructions, such as using bash or shell commands for module installation and updates.
- Include guidance for managing PATH and SSH client binaries on Linux systems, with explicit examples for common distributions.
- Offer parity in error resolution steps for both Windows and Linux, including installation and permission troubleshooting using Linux-native tools (e.g., apt, yum, chmod).
- Reference Linux package managers and environment variables where appropriate, not just PowerShell Gallery and Windows PATH.
- Ensure that CLI examples are not limited to Azure CLI and PowerShell, but also include relevant Linux shell commands where applicable.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/troubleshoot-connectivity.md
...rticles/azure-arc/servers/troubleshoot-connectivity.md
High Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates Windows bias by exclusively mentioning Windows-specific tools (Windows Admin Center, Configuration Manager) as local management options for disconnected servers, without referencing equivalent Linux tools or approaches. No Linux-specific examples or management strategies are provided, and Windows tools are presented first and solely, implying a Windows-centric perspective.
Recommendations
- Include Linux management tool options such as Cockpit, Webmin, or command-line utilities for local server management in disconnected scenarios.
- Provide examples or guidance for troubleshooting and managing disconnected Arc-enabled servers on Linux, including relevant commands and best practices.
- Ensure parity in documentation by listing both Windows and Linux tools and approaches, ideally presenting them side-by-side or in separate subsections.
- Clarify that Azure Arc-enabled servers support both Windows and Linux, and tailor troubleshooting steps to both platforms.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/troubleshoot-agent-onboard.md
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows examples and tools are presented before Linux equivalents in several sections (e.g., verbose logging commands, log file locations). Windows-specific tools and terminology (such as PowerShell, elevated command prompt, %ProgramData%, %TEMP%) are mentioned explicitly, while Linux equivalents are sometimes only referenced after or less prominently. The error and exit code tables often list Windows paths first, and PowerShell requirements are called out in error codes. However, Linux examples and troubleshooting steps are generally present and reasonably complete.
Recommendations
- Present Windows and Linux examples side-by-side or alternate their order to avoid implicit prioritization.
- Explicitly mention Linux equivalents for all Windows-specific tools, paths, and terminology (e.g., clarify that %TEMP% on Windows corresponds to /tmp on Linux).
- Include Linux-specific troubleshooting steps and log file locations with equal prominence.
- Avoid using Windows-centric language (such as 'elevated command prompt') without also referencing Linux equivalents (such as 'sudo' or 'root').
- Where PowerShell is referenced, clarify if Bash or other shells are supported and provide examples.
- Ensure that error codes and remediation steps are equally detailed for both platforms.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/troubleshoot-networking.md
.../articles/azure-arc/servers/troubleshoot-networking.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation page focuses exclusively on troubleshooting TLS configuration issues for Windows, providing only Windows-specific instructions and examples (PowerShell commands, Group Policy, Registry edits). There is no mention of Linux equivalents, nor are any Linux troubleshooting steps or commands provided. The use of Windows tools and patterns is pervasive, and Linux users are left without guidance.
Recommendations
- Add a dedicated section for Linux TLS configuration troubleshooting, including relevant commands (e.g., using openssl, update-crypto-policy, or editing /etc/ssl/openssl.cnf).
- Provide Linux-specific examples for checking and enabling cipher suites, such as using 'openssl ciphers' or inspecting system-wide TLS settings.
- Clarify which steps apply only to Windows and ensure Linux parity by listing corresponding Linux procedures.
- Reference Linux documentation or official guides for managing TLS cipher suites on common distributions (Ubuntu, RHEL, etc.).
- Consider presenting Windows and Linux instructions side-by-side or in parallel sections for easier cross-platform comparison.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/tutorial-enable-vm-insights.md
...icles/azure-arc/servers/tutorial-enable-vm-insights.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates Windows bias by providing explicit instructions and examples for Windows event logs (e.g., referencing the 'Event' table for Windows event log entries) while omitting equivalent details for Linux systems (such as syslog or Linux-specific event tables). The mention of event logs and Log Analytics queries is Windows-centric, and there are no Linux-specific examples or references to Linux logging mechanisms. Additionally, Windows terminology and tools (event log) are mentioned before or instead of Linux equivalents.
Recommendations
- Include explicit examples and instructions for Linux machines, such as how to view syslog or other Linux event tables in Log Analytics.
- Mention Linux-specific logging mechanisms (e.g., syslog, journald) alongside Windows event logs when discussing collected data.
- Provide sample queries for both Windows and Linux event data in Log Analytics.
- Clarify which tables and data types are available for Linux machines and how to interpret them.
- Ensure parity in screenshots and walkthroughs by showing both Windows and Linux machine perspectives.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/troubleshoot-extended-security-updates.md
...-arc/servers/troubleshoot-extended-security-updates.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation is heavily focused on Windows Server 2012 and 2012 R2, with all troubleshooting steps, examples, and commands tailored exclusively for Windows environments. There are no Linux equivalents or cross-platform guidance, and Windows-specific tools and patterns (e.g., certutil, PowerShell, Windows file paths) are used throughout. The documentation assumes the reader is working with Windows servers, with no mention of Linux scenarios or how similar troubleshooting might apply to non-Windows Arc-enabled machines.
Recommendations
- Add explicit statements clarifying that the guidance is only applicable to Windows Server 2012/2012 R2, and provide links or references for troubleshooting ESU delivery on Linux or other platforms if relevant.
- Where possible, include Linux equivalents for Azure Arc-enabled servers, such as how to check agent status, manage certificates, or troubleshoot connectivity and enrollment issues on Linux.
- If certain steps (e.g., certificate installation, agent updates) have Linux alternatives, provide corresponding commands (e.g., using openssl, update-ca-certificates, systemctl) and file paths.
- Ensure parity in troubleshooting steps for both Windows and Linux Arc-enabled servers, or clearly state platform limitations.
- Avoid assuming PowerShell or Windows command prompt as the only available shell; mention Bash or other shells where appropriate.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/agent-overview-scvmm.md
...center-virtual-machine-manager/agent-overview-scvmm.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
windows_heavy_detail
Summary
The documentation provides detailed, step-by-step information for both Windows and Linux agent installation and configuration. However, Windows installation details are presented first and in greater depth, including specifics about MSI packages, Windows services, security groups, and Group Policy adjustments. Windows-specific tools and patterns (MSI, NT SERVICE accounts, Group Policy) are described before their Linux equivalents, and troubleshooting/logging paths are Windows-first. Linux instructions are present and reasonably detailed, but some advanced configuration and troubleshooting guidance (e.g., security groups, service accounts) are more thoroughly covered for Windows.
Recommendations
- Alternate the order of Windows and Linux sections, or present them in parallel tables to avoid Windows-first bias.
- Ensure Linux installation details include equivalent information on service accounts, security groups, and permissions, if applicable.
- Provide Linux-specific troubleshooting tips, such as SELinux/AppArmor considerations, systemd unit file locations, and log rotation.
- Mention Linux package management commands (e.g., apt, yum, zypper) for agent installation and removal.
- If Group Policy is discussed for Windows, mention Linux equivalents (e.g., PAM, sudoers, systemd service permissions) where relevant.
- Include parity in advanced configuration examples, such as environment variable management and post-uninstall cleanup steps.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/built-in-roles.md
...ystem-center-virtual-machine-manager/built-in-roles.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation is focused exclusively on Azure Arc-enabled SCVMM, a Windows-centric technology (System Center Virtual Machine Manager). All role definitions and actions pertain to SCVMM resources, which are only available on Windows. There are no references to Linux equivalents, Linux management tools, or cross-platform scenarios. The documentation does not mention or provide examples for Linux-based environments, nor does it clarify the lack of Linux support.
Recommendations
- Explicitly state in the introduction that Azure Arc-enabled SCVMM is a Windows-only solution and not applicable to Linux environments.
- Provide links or references to Azure Arc documentation for Linux-based management (e.g., Azure Arc for Linux servers, Azure Arc for Kubernetes) to guide Linux users.
- Add a comparison table or section outlining Azure Arc features for both Windows (SCVMM) and Linux, clarifying where each applies.
- If possible, mention alternative Azure Arc built-in roles or management approaches for Linux workloads.
- Ensure that related documentation pages (e.g., 'Next steps') include Linux-relevant links and guidance for parity.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/create-virtual-machine.md
...nter-virtual-machine-manager/create-virtual-machine.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation is heavily focused on System Center Virtual Machine Manager (SCVMM), a Windows-only tool, and does not mention or provide examples for Linux-based virtualization platforms or management tools. All instructions and terminology are centered around Windows technologies, with no parity for Linux environments or tools. There are no Linux CLI, shell, or platform-specific examples, and the prerequisites and workflow assume a Windows-centric infrastructure.
Recommendations
- Include references or examples for Linux-based virtualization management tools (e.g., KVM, libvirt, oVirt) where applicable.
- Provide equivalent instructions or workflows for creating virtual machines on Linux platforms using Azure Arc, if supported.
- Add CLI or shell examples (bash, Azure CLI) that demonstrate VM creation from Linux environments.
- Clarify in the introduction that the guide is specific to SCVMM and Windows environments, and link to Linux-focused documentation if available.
- Ensure parity in terminology and screenshots by including Linux platform equivalents or noting differences.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/deliver-esus-for-system-center-virtual-machine-manager-vms.md
...ver-esus-for-system-center-virtual-machine-manager-vms.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows Server 2012/2012 R2 VMs managed by SCVMM, with all examples, terminology, and tooling centered around Windows environments. There are no Linux equivalents or examples provided, and all patching solutions and management tools referenced are Microsoft/Windows-centric (e.g., Windows Server Update Services, Microsoft Endpoint Configuration Manager). The documentation does not mention Linux VMs, Linux patching tools, or how ESUs might apply in a mixed environment.
Recommendations
- Explicitly state whether Linux VMs are supported or not in this scenario. If not, clarify the scope is Windows-only.
- If Linux VMs can be managed via Azure Arc in similar ways, provide parallel examples and instructions for Linux environments.
- Reference Linux patch management solutions (e.g., Azure Update Manager for Linux, native Linux tools like apt/yum/dnf, or third-party solutions) where appropriate.
- Include a section comparing Windows and Linux management patterns in Azure Arc-enabled SCVMM environments.
- Ensure terminology and screenshots do not assume a Windows-only audience if Linux is supported.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/enable-guest-management-at-scale.md
...al-machine-manager/enable-guest-management-at-scale.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation demonstrates a Windows bias by prioritizing Windows VM scenarios, listing Windows versions and tools first, and referencing Windows-specific management patterns (e.g., PowerShell scripts, Group Policy, Configuration Manager) before Linux equivalents. Linux support is mentioned as an exception or alternative, and Linux-specific instructions/examples are less detailed and less prominent.
Recommendations
- Present Linux and Windows instructions/examples side-by-side, or in parallel tabs, rather than listing Windows first and Linux as an exception.
- Expand Linux-specific guidance, including troubleshooting, prerequisites, and automation patterns (e.g., systemd, cloud-init, Ansible) to match the detail given for Windows.
- Include Linux management tools and automation approaches (e.g., Puppet, Chef, SaltStack) alongside Windows tools like Group Policy and Configuration Manager.
- Ensure parity in example scripts, showing both PowerShell and Bash/CLI commands with equal prominence.
- Clarify supported Linux distributions and versions in the prerequisites section, not just link out.
- Add screenshots or walkthroughs for Linux flows in the Azure portal, if supported.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/overview.md
...-arc/system-center-virtual-machine-manager/overview.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page for Azure Arc-enabled System Center Virtual Machine Manager demonstrates a Windows bias. The content centers on SCVMM, a Windows-only management tool, and repeatedly references Windows Server management, Windows registry, and PowerShell as primary automation and configuration mechanisms. Examples and links for configuration and automation tasks (such as Azure Automation runbooks and Update Manager) mention Windows and PowerShell first, with Linux support referenced only as an add-on or secondary. There are no explicit Linux or cross-platform CLI examples, and Windows-centric tools and patterns are mentioned more frequently and in greater detail than their Linux equivalents.
Recommendations
- Provide explicit Linux examples and scenarios alongside Windows, especially for automation, monitoring, and configuration tasks.
- Include CLI and scripting examples using Bash, Azure CLI, and Python for Linux environments, not just PowerShell.
- Highlight Linux support equally in feature lists and supported scenarios, rather than as a secondary note.
- Reference Linux-specific management tools and patterns (e.g., systemd, Linux daemons, package managers) where relevant.
- Ensure documentation links and tabs offer parity between Windows and Linux instructions, particularly for onboarding, agent installation, and VM lifecycle management.
- Clarify which features are cross-platform and which are Windows-only, to help users plan hybrid deployments.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/troubleshoot-scvmm.md
...m-center-virtual-machine-manager/troubleshoot-scvmm.md
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation is heavily focused on troubleshooting errors specific to SCVMM (System Center Virtual Machine Manager), a Windows-only tool. All error examples reference PowerShell sessions (PSSession), SCVMM server commands, and Windows-specific permissions and networking concepts. There are no Linux equivalents, examples, or troubleshooting steps provided, and Windows tools and patterns are mentioned exclusively and first.
Recommendations
- Include troubleshooting steps for Linux-based resource bridge deployments, if supported.
- Provide examples using Linux command-line tools (e.g., Bash, SSH) alongside PowerShell where applicable.
- Clarify in the introduction whether the guide is only relevant for Windows/SCVMM environments, and link to Linux-specific documentation if available.
- Add parity for error handling and troubleshooting for Linux-based management platforms (e.g., OpenStack, KVM) if Azure Arc supports them.
- Ensure future documentation covers both Windows and Linux scenarios, or clearly states platform limitations.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/disaster-recovery.md
...em-center-virtual-machine-manager/disaster-recovery.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation exclusively provides recovery instructions for Windows environments, specifically referencing a PowerShell script and Windows-centric workflow. There are no examples, scripts, or guidance for performing the same recovery from a Linux or cross-platform environment. The use of PowerShell and the absence of Linux shell or cross-platform alternatives indicate a strong Windows bias.
Recommendations
- Add equivalent recovery instructions for Linux environments, including Bash shell examples.
- Provide a cross-platform recovery script (e.g., written in Python or Bash) or clarify if the existing script can run on Linux with PowerShell Core.
- Explicitly mention Linux prerequisites and steps, such as using SSH and Linux command-line tools.
- Ensure that both Windows and Linux recovery paths are presented in parallel, or at least reference Linux options if Windows is described first.
- Include troubleshooting steps and support channels relevant to Linux users.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/enable-virtual-hardware-scvmm.md
...rtual-machine-manager/enable-virtual-hardware-scvmm.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation is heavily focused on SCVMM (System Center Virtual Machine Manager), a Windows-centric virtualization management tool. All examples, instructions, and screenshots are based on Windows tools and interfaces, with no mention of Linux equivalents or cross-platform alternatives. There are no Linux-specific instructions, examples, or references to Linux-based management tools or workflows.
Recommendations
- Include information on managing Arc-enabled VMs that are hosted on Linux-based hypervisors or environments, if supported.
- Provide Linux CLI or script examples (e.g., Bash, Azure CLI on Linux) for VM CRUD and power cycle operations.
- Mention whether the described process is exclusive to Windows/SCVMM or if similar functionality exists for Linux-based management platforms.
- Add a section clarifying platform limitations and, if possible, link to Linux-specific documentation for Azure Arc-enabled servers.
- Ensure parity in screenshots and UI walkthroughs by including Linux management interfaces or command-line alternatives where applicable.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/quickstart-connect-system-center-virtual-machine-manager-to-arc.md
...t-connect-system-center-virtual-machine-manager-to-arc.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-specific instructions, tools, and troubleshooting steps. Windows prerequisites and PowerShell commands are presented first and in greater detail, while Linux instructions are less prominent and lack troubleshooting depth. Windows tools (e.g., PowerShell, WinRM, tar.exe) are discussed exclusively, and performance warnings are given for Linux without offering mitigation strategies.
Recommendations
- Present Linux and Windows instructions in parallel, giving equal prominence to both platforms.
- Provide Linux-specific troubleshooting and retry examples, matching the detail given for Windows.
- Include Linux equivalents for Windows tools (e.g., clarify how to install tar and SSH on Linux, mention Linux alternatives to WinRM if relevant).
- Avoid language that discourages Linux usage (e.g., performance warnings) unless accompanied by actionable advice or mitigation steps.
- List prerequisites for both platforms explicitly and equally, including package installation steps for Linux.
- Ensure screenshots and UI instructions are platform-neutral or provide Linux-specific alternatives where appropriate.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/upgrade-azure-arc-resource-bridge.md
...l-machine-manager/upgrade-azure-arc-resource-bridge.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily oriented towards Windows environments, specifically SCVMM (System Center Virtual Machine Manager), and provides upgrade instructions and examples that assume the user is operating from a Windows server or workstation. All CLI commands are shown in the context of SCVMM and reference Windows-specific concepts (VHDX, library share, SCVMM server). There are no Linux-specific instructions, examples, or parity notes, and Linux tools or workflows are not mentioned.
Recommendations
- Add explicit instructions and examples for performing the upgrade from a Linux workstation, including any differences in file paths, CLI usage, and prerequisites.
- Clarify whether the az arcappliance CLI extension and upgrade workflow are supported on Linux, and provide troubleshooting or caveats if there are limitations.
- Mention Linux equivalents for concepts like 'library share' and VHDX handling, or note if these steps must be performed on Windows only.
- Include a parity table or section that lists differences and supported scenarios for both Windows and Linux environments.
- If SCVMM is strictly Windows-only, clarify this early in the documentation and provide guidance for users managing Arc resource bridges in non-SCVMM (potentially Linux-based) environments.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/azure-arc-agent.md
...n/articles/azure-arc/vmware-vsphere/azure-arc-agent.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a Windows-first bias by presenting Windows installation details before Linux, using Windows-specific tools (MSI, Download Center), and referencing Windows paths and services extensively. Windows terminology (e.g., 'NT SERVICE', 'Group Policy', '%ProgramFiles%') is used without Linux equivalents or explanations. Linux instructions are present but less detailed, and troubleshooting/logging examples are Windows-centric. No PowerShell commands are shown, but the overall pattern prioritizes Windows concepts and tools.
Recommendations
- Present Windows and Linux installation instructions in parallel or alternate order to avoid Windows-first impression.
- Provide Linux-specific troubleshooting steps and examples, including common Linux commands for agent management (e.g., systemctl, journalctl).
- Reference Linux package managers and repositories with equal prominence to Windows Installer/MSI.
- Include Linux equivalents for Windows concepts (e.g., explain Linux service accounts, systemd units, and security groups).
- Ensure all directory and environment variable examples are shown for both platforms, not just Windows.
- Add more detail to Linux agent management, including uninstall steps, permissions, and integration with Linux security policies.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/whats-new.md
...arc/system-center-virtual-machine-manager/whats-new.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page for Azure Arc-enabled SCVMM demonstrates a Windows bias by prioritizing Windows-centric tools and features. Windows Server management, PowerShell-based VM management, and Windows-specific capabilities (such as Software Assurance benefits and Extended Security Updates for Windows Server) are highlighted before or in greater detail than Linux equivalents. While some cross-platform tools (Ansible, Terraform, Python/Java/Go SDKs) are mentioned, Windows tools and patterns (PowerShell, Group Policy, System Center Configuration Manager) appear first and are more prominent. There are no explicit Linux management examples or references to Linux-specific tooling.
Recommendations
- Include explicit examples and documentation for managing Linux VMs in SCVMM environments, such as using Ansible or Azure CLI for Linux.
- Provide parity in feature descriptions for Linux VMs, such as cost-benefits, update management, and monitoring capabilities.
- Add Linux-first or cross-platform examples alongside Windows/PowerShell instructions.
- Mention Linux-compatible agent installation methods and highlight any differences or requirements for Linux VMs.
- Ensure that cross-platform tools (e.g., Terraform, Ansible, SDKs) are given equal prominence and example coverage as Windows tools.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/deliver-extended-security-updates-for-vmware-vms-through-arc.md
...r-extended-security-updates-for-vmware-vms-through-arc.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Windows Server 2012/2012 R2 VMs, with all examples, terminology, and tools centered around Windows environments. There are no Linux VM examples, nor are Linux patching or management tools mentioned. The patching solutions listed are all Microsoft/Windows-centric, and the eligibility and workflow are described only for Windows VMs.
Recommendations
- Add explicit mention of Linux VM support (if available) and clarify whether ESUs or similar mechanisms exist for Linux VMs managed via Arc.
- Provide examples and workflows for managing updates and compliance for Linux VMs in VMware environments through Azure Arc.
- Include Linux patch management solutions (e.g., Azure Update Manager for Linux, third-party Linux update tools) alongside Windows options.
- Ensure that screenshots and UI descriptions reflect both Windows and Linux VM scenarios, or clarify the scope if the feature is Windows-only.
- If the feature is Windows-only, state this clearly at the beginning to avoid confusion for Linux administrators.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/overview.md
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by frequently referencing Windows-specific management features, tools, and benefits before or instead of their Linux equivalents. Windows Server management, Extended Security Updates for Windows Server and SQL Server, and PowerShell are highlighted, while Linux-specific guidance and examples are less prominent or missing. Where both Windows and Linux are mentioned, Windows is often listed first or given more detail, and some links and tabs default to Windows content.
Recommendations
- Ensure parity by providing Linux-specific examples and guidance alongside Windows, especially for automation, agent installation, and management tasks.
- When referencing tools like PowerShell, also mention Bash, shell scripts, or Linux-native automation tools where applicable.
- Balance the order of presentation: alternate or randomize listing Windows and Linux, or explicitly state support for both at the outset.
- Include links and tabs for Linux documentation wherever Windows links are provided (e.g., not just /tabs=windows).
- Highlight Linux-specific benefits or scenarios, such as Linux VM management, security, and update management, to match the detail given to Windows.
- Add Linux-focused use cases and callouts in the 'Supported scenarios' and 'Next steps' sections.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page exhibits Windows bias by prioritizing Windows and PowerShell instructions, especially for running the deboarding script. Only Windows/PowerShell examples are provided for script execution, with no equivalent Linux instructions or shell script alternatives. The guidance for uninstalling the agent is split between Windows and Linux, but the script-based removal process is exclusively documented for Windows users, and Windows tools (Control Panel, PowerShell) are mentioned first and in more detail.
Recommendations
- Provide explicit instructions for running the deboarding script on Linux and macOS, including prerequisites and example commands (e.g., using Bash, sh, or Azure CLI).
- Offer a cross-platform version of the deboarding script (e.g., a Bash or Python script) or clarify if the PowerShell script can be run on PowerShell Core on Linux/macOS.
- Present Windows and Linux instructions in parallel or side-by-side, rather than Windows-first.
- Mention Linux equivalents for Windows tools (e.g., uninstalling via package manager vs. Control Panel) in all relevant steps.
- Add notes about script compatibility and requirements for non-Windows platforms.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/support-matrix-for-arc-enabled-vmware-vsphere.md
...phere/support-matrix-for-arc-enabled-vmware-vsphere.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates Windows bias by listing Windows requirements and tools (such as .NET Framework and PowerShell) before Linux equivalents, mentioning Windows-specific URLs and tools (Windows Admin Center, Windows Management Framework), and omitting Linux command examples or detailed Linux tooling. Linux requirements are mentioned briefly and generically, with no parity in example depth or tool specificity.
Recommendations
- Present Windows and Linux requirements in parallel, rather than listing Windows first.
- Include Linux-specific examples and tooling (e.g., bash scripts, systemd service management) where Windows PowerShell is referenced.
- Provide explicit Linux command-line examples for agent installation and management, similar to the Windows instructions.
- Mention Linux management tools (such as Cockpit or Ansible) if relevant, alongside Windows Admin Center.
- Clarify any differences in network requirements or agent behavior between Windows and Linux guests.
- Ensure all URLs and download instructions are equally detailed for both platforms.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/bulk-deployment.md
...es/azure-arc/workload-orchestration/bulk-deployment.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively providing CLI examples in PowerShell syntax, referencing only PowerShell scripts (e.g., bulk_deployment.ps1, workflow-delete.ps1), and omitting Linux/bash equivalents. All command-line instructions and automation scripts are presented in a Windows-centric manner, with no mention of Linux shell usage or cross-platform script alternatives. This may hinder accessibility and usability for Linux users.
Recommendations
- Provide bash shell examples alongside PowerShell for all CLI commands, using appropriate syntax and file path conventions.
- Offer Linux-compatible scripts (e.g., bulk_deployment.sh, workflow-delete.sh) and document their usage.
- Explicitly state cross-platform compatibility for the Azure CLI commands and clarify any OS-specific requirements.
- Include notes or sections highlighting differences in file handling, permissions, and environment setup between Windows and Linux.
- Ensure that examples and instructions do not assume a Windows environment by default; present Linux options equally or first where appropriate.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/quick-start-connect-vcenter-to-arc-using-script.md
...ere/quick-start-connect-vcenter-to-arc-using-script.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page presents both Windows (PowerShell) and Linux (Bash) script options for onboarding, but Windows/PowerShell instructions and notes are consistently listed before Linux/Bash equivalents. There are multiple Windows-specific notes and troubleshooting steps (e.g., PowerShell ISE caveat, Set-ExecutionPolicy), and PowerShell commands are shown with more detail and emphasis. Windows terminology and tooling (PowerShell, Set-ExecutionPolicy) are referenced more frequently and with more guidance than Linux equivalents.
Recommendations
- Alternate the order of Windows and Linux instructions so that Linux is sometimes presented first, or present both together in parallel.
- Provide equivalent troubleshooting notes for Linux environments (e.g., permissions, shell compatibility).
- Add more detailed Linux-specific guidance, such as handling script permissions (chmod +x), shell requirements, and common issues.
- Ensure parity in examples and explanations for both platforms, including error handling and recovery steps.
- Avoid Windows-centric terminology when describing cross-platform steps (e.g., refer to 'terminal' or 'shell' generically where possible).
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/recover-from-resource-bridge-deletion.md
...mware-vsphere/recover-from-resource-bridge-deletion.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell script examples and instructions, with no mention of Bash, shell, or Linux-native tooling. All scripting and automation steps are shown using PowerShell syntax, and there is no guidance for users operating from Linux or macOS environments. The onboarding and recovery process is described in terms of Windows-centric tools and workflows, with no parity for Linux users.
Recommendations
- Provide equivalent Bash or shell script examples for onboarding and recovery operations, ensuring Linux users can follow the same workflow.
- Explicitly mention platform requirements and offer guidance for both Windows and Linux/macOS users.
- Document any prerequisites or dependencies for running scripts on Linux, such as using Azure CLI or PowerShell Core on Linux.
- Include troubleshooting steps and script editing instructions relevant to Linux environments (e.g., using nano, vim, or other editors).
- Clarify whether the onboarding script can be run cross-platform, and if not, provide alternative methods or scripts for Linux users.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/whats-new.md
...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific features (such as customizing guest OS settings for Windows VMs and Windows Server Management) are highlighted, and Windows tools (System Center Configuration Manager, Group Policy, PowerShell) are mentioned explicitly, often before or without Linux equivalents. Linux support is referenced (e.g., Arc agent installation via SSH), but examples and tooling for Linux are less detailed or absent. Windows-centric management and billing features are described in more depth than Linux ones.
Recommendations
- Provide equivalent Linux examples and tooling references (e.g., mention Linux configuration management tools like Puppet, Chef, or native Linux scripting for at-scale agent installation).
- Ensure parity in feature descriptions for both Windows and Linux VMs (e.g., detail guest OS customization for Linux VMs if supported).
- List cross-platform or Linux-first tools alongside Windows tools, and avoid listing Windows tools first unless justified by usage statistics.
- Add explicit Linux management scenarios and billing features where applicable.
- Include links to Linux-specific documentation and guides for Arc agent installation, VM management, and lifecycle operations.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/migration-script.md
...s/azure-arc/workload-orchestration/migration-script.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page provides only a PowerShell migration script example, assumes the use of PowerShell (a Windows-centric tool), and does not mention or provide equivalent instructions for Linux or cross-platform environments. There is no Bash or shell script alternative, nor guidance for running the migration on Linux or macOS.
Recommendations
- Provide a Bash or shell script alternative for Linux/macOS users.
- Explicitly mention how Linux and macOS users can perform the migration, including any prerequisites or platform-specific steps.
- Clarify whether the PowerShell script can be run using PowerShell Core on Linux/macOS, and provide instructions if so.
- Ensure examples and instructions are presented for both Windows and Linux environments, or indicate platform compatibility up front.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/diagnose-problems.md
.../azure-arc/workload-orchestration/diagnose-problems.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples are given in PowerShell syntax, with no Bash or Linux shell equivalents. File paths in configuration examples use Windows-style paths (e.g., C:\Users\...), and script execution instructions reference PowerShell scripts (.ps1) exclusively. There is no mention of Linux tools, nor are Linux/Bash alternatives provided for any step, despite the cross-platform nature of Kubernetes and Azure Arc. This may hinder usability for Linux users and does not reflect best practices for cross-platform documentation.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell commands and scripts, using az CLI and kubectl where appropriate.
- Include Linux-style file paths in configuration examples, or clarify that paths should be adapted to the user's OS.
- Explicitly mention that the instructions apply to both Windows and Linux environments, and note any OS-specific differences.
- Offer downloadable Bash scripts (.sh) alongside PowerShell scripts (.ps1) for onboarding and automation tasks.
- Add a section or callouts for Linux users, highlighting any prerequisites or steps unique to Linux environments.
- Ensure screenshots and UI instructions are OS-neutral or provide examples for both Windows and Linux where relevant.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/initial-setup-environment.md
...rc/workload-orchestration/initial-setup-environment.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation exhibits Windows bias in several areas. Windows-specific tools (winget) are used for installing kubectl, and file path examples consistently use Windows-style paths (e.g., C:\path\to\archive.zip) in both Bash and PowerShell tabs. The extraction command for ZIP files uses Expand-Archive, which is a Windows PowerShell cmdlet, even in the Bash tab, with no Linux-native alternatives (e.g., unzip) provided. There are no Linux-specific installation instructions or examples for common tasks such as extracting files or installing kubectl, and the documentation assumes a Windows environment by default.
Recommendations
- Provide Linux-specific examples for installing kubectl (e.g., using apt, yum, or curl).
- Include Linux-native commands for extracting ZIP files (e.g., unzip, tar) in the Bash tab.
- Use generic or platform-neutral file path examples (e.g., /home/user/archive.zip) in Bash sections.
- Clearly indicate when commands or instructions are platform-specific, and offer alternatives for both Windows and Linux.
- Add a dedicated section or tab for Linux/macOS users where appropriate, especially for setup and prerequisite steps.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/onboarding-scripts.md
...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation is heavily biased towards Windows environments. All onboarding scripts and examples are provided exclusively for PowerShell, with no mention of Bash, shell scripts, or Linux equivalents. Prerequisites use Windows-specific tools like 'winget' for installing Azure CLI and kubectl, and all usage instructions assume a PowerShell terminal. There is no guidance for Linux or macOS users, nor alternative commands or scripts for non-Windows platforms.
Recommendations
- Provide equivalent Bash/shell script examples for Linux and macOS users alongside PowerShell instructions.
- Replace or supplement 'winget' installation commands with platform-agnostic alternatives (e.g., apt, yum, brew, direct download links) for Azure CLI and kubectl.
- Explicitly state platform requirements and offer cross-platform onboarding scripts, or document how to run the scripts on Linux/macOS (e.g., via pwsh, or provide .sh versions).
- Add a section or callouts for Linux/macOS users, including troubleshooting tips and environment setup steps.
- Ensure all CLI commands (e.g., az workload-orchestration) are shown in both PowerShell and Bash syntax where applicable.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/release-notes.md
...cles/azure-arc/workload-orchestration/release-notes.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page for Workload Orchestration release notes demonstrates Windows bias in several ways. CLI examples for configuration management use PowerShell syntax (backticks and variable notation), which is specific to Windows and not compatible with Linux/macOS shells. There are no Bash or Linux shell equivalents provided for these examples, and the only explicit CLI code blocks outside of Azure CLI commands are in PowerShell format. Additionally, instructions for installing and updating the Azure CLI extension are given in Bash syntax, but the configuration management examples revert to PowerShell, suggesting a Windows-first approach.
Recommendations
- Provide equivalent Bash examples for all CLI commands currently shown only in PowerShell.
- Use cross-platform variable notation and line continuation (e.g., $VAR and \ for Bash, $var and ` for PowerShell) or explicitly show both formats.
- Add a note clarifying that CLI commands work on Linux/macOS and Windows, and specify any platform-specific differences.
- Where possible, use neutral syntax in documentation examples, or alternate between Windows and Linux examples to ensure parity.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/troubleshooting.md
...es/azure-arc/workload-orchestration/troubleshooting.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits a strong Windows bias, particularly in the troubleshooting sections for workload orchestration. Most command-line examples are provided exclusively in PowerShell, with no equivalent Bash or Linux shell commands for key troubleshooting steps. Windows-centric tools and patterns (such as PowerShell-specific syntax, file encoding notes about 'UTF-8 with BOM', and use of ConvertTo-Json/Out-File) are used throughout, while Linux alternatives are missing or only appear later in the document. Only in the 'Troubleshoot service groups' section are Bash examples provided alongside PowerShell, but the rest of the page lacks Linux parity.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell commands, especially in troubleshooting steps for staging, authentication, and registry management.
- Include notes about file encoding and manipulation that are relevant for Linux users (e.g., using iconv or sed for encoding changes, jq for JSON creation).
- Avoid Windows-specific syntax (such as PowerShell variable notation and cmdlets) in generic troubleshooting steps, or provide cross-platform alternatives.
- Ensure that both Windows and Linux users are equally supported in all troubleshooting scenarios, with clear instructions for each platform.
- Add explicit guidance for running Azure CLI and kubectl commands on Linux, including any differences in output or required environment setup.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/tutorial-service-group-scenario-2.md
...oad-orchestration/tutorial-service-group-scenario-2.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Bash and PowerShell examples for all commands, ensuring that both Linux and Windows users are supported. However, the presence of PowerShell examples throughout, and the explicit inclusion of PowerShell tabs, reflects a bias toward Windows environments. There is also a subtle Windows-first bias, as PowerShell is a Windows-native shell and its inclusion may suggest prioritization of Windows users. Additionally, references to the Azure portal (a web GUI often used by Windows users) and the use of az CLI (which is cross-platform but often associated with Windows/PowerShell usage) reinforce this bias. No Linux-specific tools (e.g., native Linux utilities, shell scripts, or package managers) are mentioned, and there are no examples using Linux-only patterns.
Recommendations
- Add explicit notes clarifying that all Bash examples are fully supported on Linux and macOS, and that az CLI is cross-platform.
- Include troubleshooting steps or tips specific to Linux environments (e.g., permissions, file paths, environment variables).
- Mention Linux-native tools or alternatives where appropriate (e.g., kubectl, jq, grep) and provide examples.
- Ensure that Bash examples use idiomatic Linux shell scripting practices (e.g., use of export, sourcing files, etc.).
- Consider adding a Linux-first section or explicitly stating Linux compatibility at the beginning of the documentation.
- If PowerShell is included, clarify that it is available cross-platform (Windows, Linux, macOS) via PowerShell Core.
Azure Portal
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/quick-create-bicep.md
.../blob/main/articles/azure-portal/quick-create-bicep.md
High 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. There are no examples or guidance for deploying a Linux VM, nor are Linux username/password requirements mentioned. The deployment scripts are generic (Azure CLI and PowerShell), but the resource and supporting information are Windows-centric.
Recommendations
- Provide parallel examples for deploying a Linux VM (e.g., 'SimpleLinuxVM') alongside the Windows VM, including relevant ARM templates and Bicep parameters.
- Reference Linux VM documentation for username and password requirements, and link to Linux security best practices.
- Clarify that the dashboard can visualize both Windows and Linux VMs, and offer sample dashboards for each.
- Ensure that both Windows and Linux options are presented equally in prerequisites and deployment steps.
Azure Portal
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/supportability/how-to-create-azure-support-request.md
.../supportability/how-to-create-azure-support-request.md
High Priority
View Details →
Detected Bias Types
windows_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways. The advanced diagnostic information and memory dump collection sections focus exclusively on Windows VM logs and Windows-specific memory dump formats, with no mention of Linux VM equivalents. The examples and references for diagnostic data collection and troubleshooting are centered on Windows tools and patterns, and there are no Linux-specific instructions, examples, or links provided for support scenarios involving Linux VMs.
Recommendations
- Add explicit instructions and references for collecting diagnostic logs and memory dumps from Linux VMs, including links to relevant documentation.
- Include examples and troubleshooting steps for Linux-based environments alongside Windows examples, ensuring parity in guidance.
- Reference Linux tools (such as syslog, dmesg, journalctl, etc.) and provide guidance for uploading Linux log files when creating support requests.
- Clarify which steps or data collection procedures differ for Linux VMs and provide links to Azure documentation for Linux VM support.
- Review all sections for OS-specific terminology and ensure that Linux is mentioned wherever Windows is referenced, especially in advanced diagnostic and memory dump collection contexts.
Azure Portal
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/quick-create-template.md
...ob/main/articles/azure-portal/quick-create-template.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits a strong Windows bias. All command-line examples for creating the prerequisite VM use PowerShell, with no mention of Bash or Azure CLI alternatives. The resource group and VM names (SimpleWinVmResourceGroup, myVM1) and referenced documentation (Windows username/password requirements) reinforce a Windows-centric approach. There are no Linux VM creation examples, nor is there guidance for users who prefer Bash or Linux tools in Cloud Shell. The documentation mentions Azure CLI as a deployment option, but does not provide CLI examples or parity in the quickstart steps.
Recommendations
- Add equivalent Azure CLI and Bash examples for VM and resource group creation, especially for users accessing Cloud Shell from Linux or macOS.
- Include instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM example, with appropriate username/password requirements links.
- Use more neutral resource group and VM names (e.g., 'SimpleVmResourceGroup', 'myVM1') to avoid implying Windows-only usage.
- Present both PowerShell and CLI/Bash options side-by-side, or allow users to select their preferred shell in the documentation.
- Reference both Windows and Linux documentation for username/password requirements when creating VMs.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-authentication.md
...ontainer-registry/container-registry-authentication.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by consistently presenting Azure PowerShell examples alongside or immediately after Azure CLI examples, with no equivalent Linux shell or Bash scripting examples. Windows-specific tools and patterns (PowerShell, Azure portal UI) are mentioned and illustrated, while Linux-native workflows (e.g., Bash scripting, Linux authentication patterns) are largely absent or relegated to brief notes. The use of PowerShell is emphasized throughout, and Linux alternatives (such as podman) are only mentioned in a single section, with no comprehensive Linux-focused guidance or examples.
Recommendations
- Add explicit Bash and Linux shell examples for all authentication flows, especially for service principal and admin account scenarios.
- Present Linux-native workflows (e.g., Bash scripts using az CLI, environment variable management, podman usage) alongside or before PowerShell examples to ensure parity.
- Include guidance for Linux users on installing and configuring the Azure CLI, Docker, and podman, with troubleshooting steps relevant to Linux environments.
- Expand the section on alternative container tools to cover common Linux distributions and their package managers (e.g., apt, yum, dnf) for installing podman and Docker.
- Ensure that all command examples are provided in both PowerShell and Bash syntax, and clarify OS-specific differences where relevant.
- Mention and link to Linux-specific documentation or community resources for Azure authentication and container registry usage.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-auth-aci.md
...cles/container-registry/container-registry-auth-aci.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell script links, but PowerShell (a Windows-centric tool) is mentioned alongside CLI without explicit Linux shell examples. The note about 'export MSYS_NO_PATHCONV=1' references bash on Windows (MSYS), which may confuse Linux users. There are no explicit Linux shell script examples or references to Linux-native tools, and PowerShell is given parity with CLI rather than being secondary.
Recommendations
- Add explicit Linux shell (bash) script examples and links, not just Azure CLI and PowerShell.
- Clarify the note about MSYS_NO_PATHCONV to distinguish between Windows bash environments and native Linux shells.
- Mention Linux-native tools and patterns where relevant, and ensure examples are tested and presented for Linux users.
- If PowerShell is referenced, clarify its cross-platform availability, but avoid implying it is the default or primary choice for Linux users.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-auth-service-principal.md
...-registry/container-registry-auth-service-principal.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation references both Azure CLI and Azure PowerShell sample scripts, but lists Azure PowerShell (a Windows-centric tool) alongside Azure CLI without providing parity for Linux-native scripting (e.g., Bash, shell scripts). There is a lack of explicit Linux or Bash examples for creating service principals or managing credentials, and the mention of PowerShell scripts may imply a Windows-first approach. The only explicit command-line example is for 'docker login', which is cross-platform, but the sample script links and references favor Windows/PowerShell tools. There are no explicit Linux-specific instructions or examples, nor is there mention of Linux tools or patterns for certificate management beyond a brief mention of 'openssl'.
Recommendations
- Provide explicit Bash/shell script examples for common tasks (e.g., creating service principals, managing credentials) alongside PowerShell examples.
- List Azure CLI (cross-platform) examples before PowerShell to avoid Windows-first ordering.
- Include instructions or tips for Linux users, such as using Bash environment variables, file permissions, and certificate management with Linux tools.
- Add links to Linux-focused sample scripts or repositories, if available.
- Clarify that Azure CLI commands work on both Windows and Linux, and highlight any platform-specific considerations.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-get-started-bicep.md
...ainer-registry/container-registry-get-started-bicep.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell and Visual Studio Code as primary tools, listing PowerShell deployment instructions before CLI, and omitting explicit Linux/macOS terminal examples or shell commands. The use of Windows-centric shortcuts (e.g., ctrl+`) and lack of mention of Linux editors or shells further reinforces this bias.
Recommendations
- Add explicit Linux/macOS shell examples (e.g., bash) alongside PowerShell and Azure CLI instructions.
- Mention common Linux editors (e.g., Vim, Nano) in addition to Visual Studio Code.
- Include Linux/macOS-specific instructions for changing directories and running commands.
- Clarify that Azure CLI commands work cross-platform and provide terminal usage examples for Linux/macOS.
- Avoid Windows-specific keyboard shortcuts or provide alternatives for other platforms.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-get-started-docker-cli.md
...-registry/container-registry-get-started-docker-cli.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page exhibits mild Windows bias. Azure PowerShell examples are provided alongside Azure CLI, and PowerShell is called out as a recommended method for authentication and image removal. Windows tools such as Visual Studio Code and its Docker extension are mentioned as productivity aids. In several places, Windows-specific patterns (e.g., Control+C for stopping containers) are referenced without Linux alternatives. The order of presentation often places Windows/PowerShell options before or alongside Linux/CLI equivalents, but Linux-specific examples or notes are generally missing.
Recommendations
- Add explicit Linux shell examples (e.g., bash) for authentication and image removal, especially where PowerShell is featured.
- Include Linux-specific notes for common operations, such as stopping containers (e.g., mention that Control+C works in most terminals, but clarify for Linux users).
- Mention Linux-native tools or workflows where Windows tools (e.g., Visual Studio Code) are recommended.
- Ensure that Azure CLI (cross-platform) is presented as the primary method, with PowerShell as an alternative, and clarify platform applicability.
- Where tabs are used for CLI/PowerShell, add a Bash/Linux tab if there are platform-specific nuances.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-health-error-reference.md
...-registry/container-registry-health-error-reference.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits a mild Windows bias, primarily in the Notary error section, where Windows-specific instructions (using notary.exe and placing it in a Windows path) are given first and in more detail than Linux/macOS equivalents. Other sections mention adding paths to 'system variables' without clarifying cross-platform differences, and do not provide explicit Linux or macOS examples for environment variable configuration or tool installation.
Recommendations
- Provide explicit Linux/macOS instructions alongside Windows ones, especially for tool installation and environment variable configuration (e.g., mention modifying $PATH in bash/zsh).
- When referencing file paths or executables, include Linux/macOS equivalents (e.g., where to place binaries, how to rename them, and typical locations).
- Avoid using Windows terminology like 'system variables' or '.exe' exclusively; clarify cross-platform differences.
- Ensure that examples and troubleshooting steps are presented for all major platforms (Windows, Linux, macOS) in parallel, not just Windows-first.
- Where possible, link to platform-specific installation guides for Docker, Helm, Notary, etc.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-import-images.md
...container-registry/container-registry-import-images.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows environments by providing examples exclusively for Azure CLI and Azure PowerShell, with no explicit Linux shell (bash/zsh) or cross-platform command-line examples. PowerShell is a Windows-native tool, and its usage is presented equally alongside Azure CLI, but there are no Linux-specific instructions, nor are Linux tools or shell patterns mentioned. The only OS-specific image example is for Windows Server Core, with no Linux image import example. There is no mention of running commands in Linux terminals, nor are Linux authentication or credential patterns discussed.
Recommendations
- Add explicit Linux shell (bash/zsh) examples for all CLI commands, demonstrating usage in a typical Linux terminal.
- Include instructions or notes on installing and running Azure CLI on Linux, and clarify that all CLI commands work cross-platform.
- Provide an example of importing a Linux-based image (e.g., Ubuntu, Alpine) from Microsoft Container Registry, not just Windows Server Core.
- Mention Linux authentication patterns (such as using environment variables for credentials, or using managed identities on Linux VMs).
- Clarify that Azure PowerShell can be run on Linux, but provide bash alternatives where possible.
- Ensure parity in troubleshooting and prerequisites sections, referencing Linux-specific issues or steps where relevant.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-get-started-portal.md
...iner-registry/container-registry-get-started-portal.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides sign-in instructions for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. There are no explicit Linux shell examples (e.g., Bash) for registry sign-in, and PowerShell instructions are given equal prominence to CLI, despite CLI being cross-platform. The documentation references Docker installation for Mac, Windows, and Linux, but operational examples (e.g., registry sign-in) omit Linux-specific command-line patterns. There is a subtle Windows bias in tool selection and example prioritization.
Recommendations
- Add explicit Bash/Linux shell examples for Azure CLI usage, clarifying that CLI commands work natively on Linux and MacOS.
- Clarify that Azure PowerShell is available cross-platform, but highlight Bash/CLI as the default for Linux users.
- Consider providing a Linux-first example order, or at least alternate between Windows and Linux examples.
- Add notes or tabs for Linux-specific workflows, such as using Bash scripts for automation.
- Ensure parity in troubleshooting and environment setup instructions for Linux users.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-helm-repos.md
...es/container-registry/container-registry-helm-repos.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation exhibits Windows bias by listing Windows-centric tools and patterns before Linux equivalents, using Windows-style commands (e.g., 'set' for environment variables), and referencing Azure PowerShell alongside Azure CLI for cluster creation. There are missing Linux-specific examples for common tasks such as setting environment variables and authentication, and no explicit mention of Linux shell alternatives (e.g., 'export' instead of 'set').
Recommendations
- Provide Linux/macOS shell equivalents for all command-line examples, especially for environment variable setting (e.g., use 'export ACR_NAME=...' alongside 'set').
- List Azure CLI and Linux shell commands before or alongside Windows/PowerShell commands when presenting options.
- Explicitly mention that all commands are cross-platform, and clarify any platform-specific differences.
- Add notes or tabs for Linux/macOS and Windows/PowerShell command variants where appropriate.
- Ensure that authentication and scripting examples use syntax compatible with bash/zsh and PowerShell, or provide both.
- Review all examples for Windows-specific assumptions and update them for platform neutrality.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-manage-artifact.md
...ntainer-registry/container-registry-manage-artifact.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Linux/macOS and Windows examples for ORAS commands, but Windows examples are consistently presented after Linux/macOS, and use Windows-specific syntax (cmd.exe, .\oras.exe, caret line continuation). There is a notable emphasis on Docker Desktop credential store, which is primarily a Windows/Mac tool, and no mention of Linux-native credential management. The authentication section references Microsoft Entra and Azure CLI, which are cross-platform, but the Docker credential store reference is Windows-centric. There are no missing Linux examples, but Windows-specific tools and patterns are mentioned.
Recommendations
- Present Linux and Windows examples in parallel, or alternate which is shown first to avoid implicit prioritization.
- Explicitly mention Linux-native credential management options (e.g., Docker credential helpers for Linux, or ORAS config file usage).
- Clarify that Docker Desktop credential store is available on Windows and Mac, and provide equivalent instructions for Linux users (e.g., using docker-credential-pass or other Linux credential helpers).
- Where possible, use platform-agnostic commands, or provide clear guidance for each platform, including Linux-specific nuances.
- Review references to Windows tools (e.g., .\oras.exe) and ensure Linux equivalents are equally described and visible.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-skus.md
...articles/container-registry/container-registry-skus.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page presents both Azure CLI and Azure PowerShell examples for managing Azure Container Registry SKUs, but PowerShell is given equal prominence to CLI, and is mentioned before Linux-native alternatives (e.g., Bash scripting). There are no explicit Linux shell (bash) or macOS Terminal examples, and the only command-line tools referenced are Azure CLI and PowerShell, both of which are commonly associated with Windows environments. No Linux-specific tools or usage patterns are discussed, and PowerShell is referenced in multiple places, reinforcing a Windows-centric approach.
Recommendations
- Add explicit bash shell examples for all CLI commands, showing usage in Linux/macOS environments.
- Clarify that Azure CLI is cross-platform and provide installation/use instructions for Linux and macOS.
- Include notes or examples for common Linux container tools (e.g., Podman, containerd) where relevant.
- Avoid presenting PowerShell examples before or alongside CLI unless parity is maintained for Linux/macOS users.
- Reference Linux-native scripting and automation patterns where appropriate.
Copilot
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/copilot/ai-shell-overview.md
...t-docs/blob/main/articles/copilot/ai-shell-overview.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows/Powershell bias by emphasizing PowerShell usage, requiring the installation of a PowerShell module (AIShell), and referencing PowerShell-specific documentation and repositories. There are no explicit Linux or Bash examples, and the installation instructions point to PowerShell-centric resources, which may alienate Linux or macOS users who prefer Bash or other shells.
Recommendations
- Provide explicit examples for Bash or other common Linux shells alongside PowerShell examples.
- Include installation instructions and requirements for Linux/macOS environments, not just PowerShell.
- Reference documentation and repositories that are not exclusively PowerShell-focused, or clarify cross-platform compatibility.
- Mention and demonstrate the use of AI Shell in non-Windows terminals (e.g., bash, zsh, fish) to ensure Linux users feel equally supported.
- Clarify whether the AIShell module is required for all platforms or only for PowerShell users, and provide alternatives if available.
Copilot
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/copilot/example-prompts.md
...ent-docs/blob/main/articles/copilot/example-prompts.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides dedicated sections and example prompts for both Azure CLI and PowerShell, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, despite CLI being cross-platform. There are multiple PowerShell-specific examples, and no Bash or Linux shell scripting examples are provided. The documentation mentions creating and SSH-ing into Linux VMs, but does not provide Linux-specific command-line or scripting examples. Windows tools (PowerShell) are featured, but Linux equivalents (Bash, shell scripts) are missing.
Recommendations
- Add example prompts for Bash or Linux shell scripting to match PowerShell coverage.
- Include references to Linux-native tools (e.g., Bash, SSH, scp) in scenarios where PowerShell is mentioned.
- Ensure that CLI examples clarify cross-platform compatibility and, where relevant, provide both Windows and Linux command-line patterns.
- Consider adding a table or section that explicitly compares PowerShell and Bash usage for common Azure tasks.
- Review prompt examples to ensure Linux users see their workflows represented equally alongside Windows/PowerShell.
Copilot
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/copilot/improve-storage-accounts.md
...blob/main/articles/copilot/improve-storage-accounts.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily through its focus on Azure File Sync, which is a Windows-only tool, and the absence of Linux-specific migration or troubleshooting examples. Migration scenarios mention SMB (Windows) and NFS (Linux/UNIX), but do not provide parity in examples or troubleshooting for Linux environments. There are no references to Linux-native tools, commands, or issues, and troubleshooting is centered on Windows-centric error codes and patterns.
Recommendations
- Include Linux-specific migration scenarios and troubleshooting examples, such as issues with NFS mounts, permissions, or SELinux/AppArmor.
- Provide sample prompts and screenshots for Linux environments, e.g., migrating data from Linux servers or handling Linux file system errors.
- Mention Linux-native tools (rsync, scp, azcopy on Linux, etc.) alongside Windows tools like Azure File Sync.
- Balance coverage by adding sections or examples for Linux administrators, ensuring that both Windows and Linux use cases are equally represented.
- Reference common Linux error codes or troubleshooting steps when discussing migration and sync issues.
Copilot
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/copilot/optimization-agent.md
...-docs/blob/main/articles/copilot/optimization-agent.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by explicitly mentioning PowerShell script generation before Azure CLI, using a sample prompt that requests a PowerShell script, and lacking any Linux-specific examples or references. There is no mention of Bash, Linux shell environments, or cross-platform script compatibility. The language and examples assume familiarity with Windows tooling and do not provide parity for Linux users.
Recommendations
- Provide explicit examples of both PowerShell and Bash/Azure CLI scripts for optimization tasks.
- Mention Linux environments and clarify that Azure CLI is cross-platform, including usage notes for Bash or other shells.
- Balance sample prompts to include requests for Bash scripts or Linux-compatible automation.
- Add a section highlighting cross-platform support and any differences in script execution between Windows and Linux environments.
- Ensure that references to scripting tools do not default to Windows-first (e.g., list Azure CLI before PowerShell or present both together).
Lighthouse
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/monitor-delegation-changes.md
...ticles/lighthouse/how-to/monitor-delegation-changes.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell scripts for querying delegation changes, with no equivalent Bash or Linux shell examples. PowerShell is presented first in all code sections, and the main sample script is exclusively PowerShell-based. Although Azure CLI commands are briefly mentioned for role assignment, all advanced scripting and automation guidance is Windows-centric, with no Linux-native alternatives or cross-platform scripting shown.
Recommendations
- Provide equivalent Bash or shell script examples for querying the Tenant Activity Log using REST API calls, leveraging curl/jq or Azure CLI.
- Present Azure CLI examples before or alongside PowerShell, especially for common tasks like role assignment and log querying.
- Explicitly mention cross-platform compatibility for all scripts and tools, and clarify when a script is Windows-only.
- Offer downloadable sample scripts for Linux/macOS environments, or link to GitHub repositories with both PowerShell and Bash versions.
- Add guidance for running these tasks in Linux-based Azure Cloud Shell, including any differences in authentication or environment setup.
Lighthouse
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/onboard-management-group.md
...articles/lighthouse/how-to/onboard-management-group.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides only a PowerShell example for assigning the policy, with no equivalent examples for Linux/macOS users (such as Azure CLI or Bash). The use of PowerShell is presented as the default method, which may disadvantage users on non-Windows platforms. There is no mention of cross-platform alternatives or parity in tooling.
Recommendations
- Add Azure CLI and/or Bash examples for assigning the policy, alongside the PowerShell example.
- Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
- Where possible, use cross-platform tools or scripts in examples, or provide parallel instructions for both PowerShell and CLI.
- Clarify that PowerShell is not required and that users can choose their preferred platform/tooling.
Lighthouse
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/monitor-at-scale.md
...ob/main/articles/lighthouse/how-to/monitor-at-scale.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for resource provider registration, referencing PowerShell as the sole automation tool, and omitting equivalent instructions for Linux users (such as Azure CLI or Bash). Windows-centric tools and patterns are mentioned exclusively or before cross-platform alternatives, and there are no Linux-specific or cross-platform code samples for key tasks.
Recommendations
- Provide Azure CLI and Bash script examples alongside PowerShell commands for resource provider registration and workspace creation.
- Explicitly mention that automation tasks can be performed on Linux/macOS using Azure CLI, not just PowerShell.
- Add links to cross-platform documentation and tools where available.
- Ensure that references to management tools (e.g., automation accounts, scripting) include both Windows and Linux options.
- Review all code samples and ensure parity between Windows and Linux environments for all major tasks.
Lighthouse
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/onboard-customer.md
...ob/main/articles/lighthouse/how-to/onboard-customer.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides onboarding instructions for Azure Lighthouse using the Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, PowerShell examples and references are prominent and presented alongside CLI, but there is no mention of Linux-specific patterns, shell scripting, or alternative Linux-native tools. The documentation refers to 'PowerShell' and 'Azure PowerShell' throughout, and troubleshooting steps do not include Linux-specific guidance or command-line alternatives beyond Azure CLI. The order of presentation often lists Azure PowerShell before Azure CLI, and there are no explicit Linux shell (bash/zsh) examples or references to Linux package managers or environments.
Recommendations
- Add explicit Linux shell (bash/zsh) examples for template deployment, such as using curl, wget, jq, or scripting with az CLI.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide installation instructions for Linux environments.
- Include troubleshooting steps relevant to Linux environments, such as checking az CLI installation, permissions, and environment variables.
- When listing command-line options, present Azure CLI before PowerShell to avoid implicit Windows-first ordering.
- Reference Linux-native automation tools (e.g., cron jobs, shell scripts) for ongoing management and onboarding automation.
- Add notes or links about using Azure Cloud Shell, which is accessible from any OS and supports both bash and PowerShell.
Quotas
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/quotas/storage-account-quota-requests.md
...main/articles/quotas/storage-account-quota-requests.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page exhibits a Windows bias by listing Azure PowerShell as the first tool for quota management, referencing PowerShell-specific modules, and using terminology familiar to Windows users. Although Azure CLI and REST API are mentioned, the ordering and emphasis favor Windows-centric tools. There are no explicit Linux shell examples or guidance for Linux users, and no mention of platform-specific considerations.
Recommendations
- List Azure CLI before Azure PowerShell when presenting cross-platform tools, as CLI is natively cross-platform.
- Provide explicit Linux shell examples (e.g., Bash) for Azure CLI commands.
- Clarify that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and link to installation guides for each platform.
- Avoid using Windows-centric terminology or ordering unless justified by usage statistics.
- Include screenshots or instructions that reflect Linux/macOS environments where relevant.
Lighthouse
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/policy-at-scale.md
...lob/main/articles/lighthouse/how-to/policy-at-scale.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation exclusively uses PowerShell for all examples and instructions, which is primarily associated with Windows environments. There are no equivalent examples using Azure CLI, Bash, or other cross-platform tools commonly used on Linux or macOS. The use of PowerShell cmdlets (e.g., Get-AzSubscription, New-AzSubscriptionDeployment) and the lack of mention of Linux-native workflows or tools indicate a strong Windows bias. This may hinder accessibility for users who primarily work in Linux or macOS environments.
Recommendations
- Provide equivalent examples using Azure CLI, which is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell Core is available on Linux and macOS, if PowerShell usage is required.
- Include Bash script examples for querying and deploying policies, or reference how to adapt the workflow for Bash/CLI users.
- Add a section comparing PowerShell and Azure CLI approaches, highlighting platform compatibility.
- Ensure that tool recommendations and instructions are not exclusively focused on Windows environments.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/connectivity.md
...docs/blob/main/articles/azure-arc/data/connectivity.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page presents examples and tooling in a platform-neutral way for most operations, referencing Azure Data Studio, CLI, and Kubernetes-native tools. However, there is a subtle Windows bias in the authentication section, where Active Directory (AD) and Active Directory Federation Services (ADFS) are mentioned as alternatives to Microsoft Entra ID, without mentioning Linux-native authentication options (such as LDAP or Kerberos). Additionally, the documentation does not provide explicit Linux command-line examples or reference Linux-specific tools, which may leave Linux administrators without clear guidance.
Recommendations
- Add explicit Linux authentication options (e.g., LDAP, Kerberos) alongside Active Directory/ADFS in the authentication section.
- Provide Linux-specific command-line examples for provisioning, configuration, and management tasks (e.g., using bash, curl, kubectl on Linux).
- Reference Linux-native tools and patterns where appropriate, such as systemd, cron, or Linux file paths for backup/restore operations.
- Ensure that any mention of Windows-centric technologies (Active Directory, ADFS) is balanced with Linux equivalents or alternatives.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/managed-instance-disaster-recovery-portal.md
...-arc/data/managed-instance-disaster-recovery-portal.md
Medium 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 implicitly assumes a GUI workflow common to Windows users. There are no examples or mentions of Linux-specific tools, CLI commands, or cross-platform alternatives within the main content. The only reference to CLI-based configuration is in the 'Related content' section, which is listed after the portal instructions, suggesting a secondary priority. There is no mention of Linux shell commands, nor is there guidance for users who may prefer or require non-GUI workflows.
Recommendations
- Include explicit references to cross-platform CLI workflows (e.g., Azure CLI, az commands) within the main documentation, not just as related links.
- Provide example commands for disaster recovery configuration using Azure CLI or PowerShell, and clarify which are available on Linux, macOS, and Windows.
- Add notes or sections highlighting how Linux users can perform equivalent actions, including screenshots or terminal output where appropriate.
- Ensure that non-Windows workflows are presented with equal prominence and detail as portal-based instructions.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/view-billing-data-in-azure.md
.../articles/azure-arc/data/view-billing-data-in-azure.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page demonstrates bias towards Windows environments by exclusively referencing Windows-centric tools (such as Excel for viewing CSV files) and omitting any examples or guidance for Linux users. There are no instructions for using Linux-native tools to view or process billing data, nor are there any command-line examples for Linux or cross-platform usage.
Recommendations
- Include examples of how to view and process downloaded CSV files using Linux tools such as LibreOffice Calc, csvkit, or command-line utilities like awk, grep, and cut.
- Provide instructions for automating billing data uploads using Bash scripts or Linux shell commands, in addition to any PowerShell or Windows-based automation.
- Mention cross-platform editors (e.g., VS Code) and clarify that the download location may vary depending on the operating system.
- Add explicit notes or sections for Linux users, ensuring parity in guidance and examples.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/azcmagent-connect.md
...b/main/articles/azure-arc/servers/azcmagent-connect.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
Summary
The documentation displays a mild Windows bias by describing the interactive browser login as 'Windows only' and listing it first among authentication options. It references a PowerShell cmdlet (Get-AzAccessToken) for obtaining an access token, without mentioning a Linux/CLI equivalent. However, most examples and instructions are cross-platform, and Linux is explicitly mentioned in several places.
Recommendations
- For the interactive browser login, clarify whether this method is available on Linux with a desktop environment (e.g., GNOME/KDE) and provide instructions or caveats for Linux users.
- When referencing tools for obtaining access tokens, provide both PowerShell (Get-AzAccessToken) and Azure CLI (az account get-access-token) examples, or mention that both are supported.
- Consider reordering authentication options so that cross-platform or Linux-default methods (like device code login) are listed first, or group them by platform applicability.
- Explicitly state in each authentication option which platforms are supported, and provide Linux-specific notes or examples where behavior differs.
- Ensure that all sample commands and flags are shown in a cross-platform way, and avoid implying that Windows is the primary or default environment.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/includes/esu-network-requirements.md
...azure-arc/servers/includes/esu-network-requirements.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation focuses exclusively on Windows Server 2012 and SQL Server 2012, with all examples and endpoint descriptions tailored to Windows environments. There are no references to Linux servers, Linux-specific endpoints, or instructions for Linux-based Azure Arc-enabled servers. This creates a Windows-first bias and omits guidance for Linux users.
Recommendations
- Include information about required endpoints for Linux-based Azure Arc-enabled servers, if applicable.
- Add examples or notes for Linux package downloads and update mechanisms (e.g., mention if endpoints are also used for Linux extension packages).
- Clarify whether the endpoints listed are relevant for Linux servers, and specify any differences.
- Provide parity in documentation by listing both Windows and Linux scenarios, or explicitly state if Linux is not supported in this context.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/set-up-and-manage-self-service-access-scvmm.md
...manager/set-up-and-manage-self-service-access-scvmm.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is focused exclusively on SCVMM (System Center Virtual Machine Manager), a Windows-centric virtualization management tool. All examples and instructions assume the use of Windows-based management interfaces (Azure Portal, SCVMM), with no mention of Linux tools, CLI, or cross-platform alternatives. There are no Linux-specific instructions or parity examples for managing access or resources.
Recommendations
- Include equivalent instructions for managing access using Azure CLI and/or PowerShell Core, which are cross-platform.
- Clarify whether SCVMM resources can be managed from Linux environments, and if so, provide examples.
- Mention any limitations or requirements for Linux administrators, such as needing to use the Azure Portal or specific tools.
- Provide guidance for Linux users on how to interact with Azure Arc-enabled SCVMM resources, if possible.
- Add references to cross-platform documentation or tools where appropriate.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/create-virtual-machine.md
...les/azure-arc/vmware-vsphere/create-virtual-machine.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page primarily describes VM creation via the Azure portal, with administrator account setup focused on username/password authentication (typical for Windows). Linux-specific options, such as SSH key authentication, are mentioned only as an alternative and not illustrated with examples or screenshots. There are no Linux-specific configuration steps, patterns, or troubleshooting tips, and Windows-centric patterns (username/password) are presented first and in more detail.
Recommendations
- Provide explicit Linux VM creation examples, including screenshots illustrating SSH key authentication setup.
- Include guidance on Linux-specific configuration options (e.g., cloud-init, OS customization, package installation).
- Mention Linux guest customization and management patterns (e.g., using Azure Arc agent on Linux, troubleshooting Linux connectivity).
- Ensure parity in documentation structure, presenting Linux and Windows options side-by-side where relevant.
- Add references to Linux CLI tools and automation patterns (e.g., Bash scripts, Linux-based Infrastructure-as-Code).
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-rbac-custom-roles.md
...ainer-registry/container-registry-rbac-custom-roles.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page presents both Azure CLI and Azure PowerShell examples for listing permissions, but PowerShell (a Windows-centric tool) is mentioned alongside CLI rather than as a secondary option. In several places, Azure PowerShell is referenced equally with Azure CLI for creating and assigning custom roles, which may suggest a slight Windows bias by not prioritizing cross-platform tools. No explicit Linux-only examples or Linux-specific tools are provided, and PowerShell is traditionally associated with Windows environments.
Recommendations
- Prioritize Azure CLI examples and instructions, as CLI is natively cross-platform and widely used on Linux and macOS.
- Clearly indicate that Azure PowerShell is available cross-platform, but note its historical association with Windows to avoid confusion.
- Add explicit Linux usage notes or examples, such as running Azure CLI commands in Bash or Zsh.
- If referencing PowerShell, provide context for Linux/macOS users (e.g., how to install and use PowerShell Core on non-Windows systems).
- Consider including screenshots or terminal outputs from Linux environments to demonstrate parity.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/azure-firewall-explicit-proxy.md
...in/articles/azure-arc/azure-firewall-explicit-proxy.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides instructions and examples for configuring Azure Arc resources with Azure Firewall Explicit Proxy, but it implicitly favors Windows environments. The onboarding and proxy configuration steps reference the Azure Connected Machine agent CLI without specifying OS-specific commands or clarifying Linux support. The Private Link integration section links to proxy bypass instructions specifically for Windows, with no mention of Linux equivalents. There are no explicit PowerShell examples, but the lack of Linux-specific guidance and the use of Windows-centric links and terminology indicate a Windows-first bias and missing Linux parity.
Recommendations
- Add explicit instructions and examples for Linux environments, including onboarding, proxy configuration, and troubleshooting steps using Linux shell commands.
- Clarify whether the Azure Connected Machine agent CLI commands are OS-agnostic, and provide Linux-specific syntax or notes if necessary.
- Include links and documentation for proxy bypass features for Linux, not just Windows.
- Ensure that all referenced features and troubleshooting steps are demonstrated for both Windows and Linux platforms, with clear parity in guidance.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/container-storage/howto-configure-onelake-identity.md
.../container-storage/howto-configure-onelake-identity.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Power BI web links and portals, which are typically accessed via web browsers on Windows systems. There are no Linux-specific examples, CLI commands, or alternative instructions for Linux users. The configuration steps rely on graphical interfaces and do not mention command-line or automation options that are common in Linux environments.
Recommendations
- Provide equivalent instructions using Azure CLI or REST API, which are platform-agnostic and can be used on Linux.
- Include examples of configuring OneLake Identity and subvolumes using command-line tools available on Linux.
- Mention any Linux-specific considerations or prerequisites for Azure Arc and Container Storage.
- Add screenshots or walkthroughs for Linux environments where applicable.
- Clarify that the portal-based steps are accessible from any OS and offer alternatives for users who prefer not to use a GUI.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-sql-managed-instance-using-kubernetes-native-tools.md
...ate-sql-managed-instance-using-kubernetes-native-tools.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page demonstrates mild Windows bias by presenting PowerShell as the first example for base64 encoding credentials, followed by Linux/macOS. Additionally, file path examples use Windows-style paths (e.g., C:\arc-data-services\sqlmi.yaml) without showing Linux equivalents. The text editor recommendation (VS Code) is cross-platform, and most Kubernetes commands are platform-neutral, but the ordering and examples subtly favor Windows users.
Recommendations
- Present Linux/macOS and Windows examples side-by-side or alternate which comes first.
- Include Linux file path examples (e.g., /home/user/arc-data-services/sqlmi.yaml) alongside Windows paths.
- Explicitly state that all commands work on Linux/macOS and Windows, and highlight any platform-specific differences.
- Consider adding a table or section summarizing commands for each major platform.
- Where PowerShell is used, also mention Bash or other common Linux shells for parity.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/delete-azure-resources.md
...main/articles/azure-arc/data/delete-azure-resources.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (a web UI often associated with Windows workflows) for resource deletion steps and by not providing any Linux-specific examples or commands for managing Kubernetes resources directly. All CLI examples use the Azure CLI, which is cross-platform, but there are no examples of using Linux-native tools (e.g., kubectl) for resource deletion, nor is there any mention of Linux shell commands or patterns. The documentation does not reference PowerShell, but the absence of Linux-specific guidance or parity in examples indicates a bias toward Windows-centric management patterns.
Recommendations
- Add examples for deleting resources using kubectl commands, especially for Kubernetes clusters running on Linux.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample shell commands for Linux users.
- Include guidance for managing resources via Linux terminal, such as using bash scripts or native Linux tools.
- Balance instructions by providing both portal (GUI) and command-line (CLI) options for all major operations, and clarify platform compatibility.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/migrate-to-managed-instance.md
...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation consistently presents Windows-centric examples and file paths (e.g., C:\Backupfiles\test.bak) when demonstrating backup and restore operations. There are no equivalent Linux examples or file paths (e.g., /home/user/test.bak) provided, and Windows patterns/tools are mentioned first or exclusively. This may make it less accessible for users working on Linux environments.
Recommendations
- Provide Linux-specific examples alongside Windows ones, such as using /home/user/test.bak for backup file paths.
- Explicitly mention that the backup and restore steps can be performed on both Windows and Linux, and clarify any platform-specific differences.
- Include screenshots or instructions for Azure Data Studio and Azure Storage Explorer usage on Linux, if available.
- Add notes or sections that address common Linux tools or commands for file manipulation and backup management.
- Ensure that references to file paths, commands, and tooling are not exclusively Windows-centric and offer parity for Linux users.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/rotate-user-tls-certificate.md
...articles/azure-arc/data/rotate-user-tls-certificate.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation provides both Linux and Windows instructions for base64 encoding, but Windows-specific tools (certutil, findstr) are mentioned separately and in detail, while the Linux example is presented first and more simply. The Windows tool usage is explained with extra steps (removing headers), which may indicate a slight Windows bias in tool coverage and troubleshooting. However, the main certificate generation and Kubernetes steps use cross-platform tools (OpenSSL, Azure CLI, kubectl), and Linux is referenced first in the base64 section.
Recommendations
- Provide equivalent Linux troubleshooting steps for base64 encoding (e.g., how to remove headers if needed), to match the detail given for Windows.
- Mention cross-platform alternatives for base64 encoding/decoding (e.g., Python, OpenSSL) for both OSes.
- Clarify that all CLI and YAML steps are OS-agnostic unless otherwise noted.
- Consider grouping OS-specific instructions together, or using tabs to separate Windows and Linux workflows for encoding/decoding.
- Ensure that any Windows-specific tool (certutil, findstr) is matched with a Linux equivalent (e.g., grep, sed) and provide example commands.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/troubleshooting-get-logs.md
...in/articles/azure-arc/data/troubleshooting-get-logs.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides a CLI example that uses a Windows-style file path (C:\temp\logs) as the only explicit example for the --target-folder parameter. There are no Linux or cross-platform path examples, and no mention of Linux-specific considerations. This may lead Linux users to feel the documentation is Windows-centric and less relevant to their environment.
Recommendations
- Include Linux-style file path examples (e.g., /tmp/logs) alongside Windows examples when demonstrating CLI parameters that accept file paths.
- Explicitly state that the az CLI and arcdata extension work on both Windows and Linux, and provide guidance for both platforms where relevant.
- Add a note or section on cross-platform usage, including any differences in file system paths, permissions, or environment setup.
- Ensure that all examples and instructions are platform-neutral or provide parallel examples for both Windows and Linux.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/validation-program.md
...lob/main/articles/azure-arc/data/validation-program.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page demonstrates mild Windows bias by prominently featuring Windows-centric partner solutions (such as DataON AZS-6224 for Azure Stack HCI, Hitachi UCP with Microsoft AKS-HCI, Lenovo ThinkAgile MX1020/MX3520) and referencing tools and patterns commonly associated with Windows environments (e.g., Azure Data Studio, Azure Data CLI). Windows-based Kubernetes distributions (AKS-HCI, Azure Stack HCI) are mentioned before Linux-based equivalents (Red Hat OpenShift, VMware Tanzu, etc.), and some partner solutions are described with a clear Windows orientation. However, the page does include Linux-oriented solutions and tools (kubectl, OpenShift, Kublr, Wind River, etc.), and does not provide command-line examples that are exclusive to Windows or PowerShell.
Recommendations
- Ensure equal prominence and ordering of Linux-based solutions alongside Windows-based ones in partner tables and descriptions.
- Include explicit Linux command-line examples (e.g., bash, kubectl usage on Linux) where platform-specific instructions are relevant.
- Reference Linux-native tools (such as Linux package managers for azdata installation) in the prerequisites section.
- Clarify platform compatibility for all tools (e.g., Azure Data Studio, azdata) and provide installation instructions for both Windows and Linux.
- Avoid listing Windows-centric solutions (e.g., AKS-HCI, Azure Stack HCI) before Linux equivalents unless there is a technical reason.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/upload-usage-data.md
...blob/main/articles/azure-arc/data/upload-usage-data.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
linux_first
Summary
The documentation provides automation examples using Linux shell scripting and mentions Linux/Mac script extensions before Windows equivalents. It references both Linux (cron) and Windows (Task Scheduler) job schedulers, but Linux tools and patterns are presented first and in more detail. There are no PowerShell or Windows-specific command examples, nor is there exclusive use of Windows tools.
Recommendations
- Add explicit PowerShell or Windows batch script examples for automating uploads, similar to the Linux shell script provided.
- Provide step-by-step instructions for setting up scheduled uploads using Windows Task Scheduler, including sample .bat or .ps1 scripts.
- Ensure that references to both Linux and Windows automation tools are balanced and that examples for both platforms are equally detailed.
- Mention cross-platform scripting options, such as Python, for users who may want a unified approach.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/observability.md
...blob/main/articles/azure-arc/edge-rag/observability.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (a graphical interface most commonly used on Windows) and Azure Managed Grafana for metric visualization, without providing any Linux-specific or cross-platform command-line examples. There are no instructions for accessing metrics via Linux-native tools (such as kubectl, curl, or Prometheus CLI), nor are there any PowerShell or Windows tool references, but the workflow is centered on Azure portal navigation and GUI screenshots, which are typically more accessible to Windows users. Linux CLI options (e.g., Azure CLI, kubectl) are mentioned only in links, not in the main workflow or examples.
Recommendations
- Add explicit Linux command-line examples for viewing Edge RAG metrics, such as using Azure CLI, kubectl, or Prometheus queries.
- Provide step-by-step instructions for monitoring metrics using Linux-native tools and terminal workflows.
- Include screenshots or terminal output examples from Linux environments.
- Ensure parity by presenting both GUI (portal) and CLI methods side-by-side, or in separate tabs, for each workflow.
- Reference cross-platform tools and clarify that Azure CLI and Grafana are available on Linux, macOS, and Windows.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/quickstart-edge-rag.md
...ain/articles/azure-arc/edge-rag/quickstart-edge-rag.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation demonstrates Windows bias by providing host file editing instructions exclusively for Windows (using Notepad and the C:\windows\System32\drivers\etc\hosts path), without mentioning Linux or macOS equivalents. Additionally, the instructions for opening Azure Cloud Shell mention switching to PowerShell, which is more relevant for Windows users, and variable assignment syntax (e.g., $var = ...) is PowerShell-style, which may not be familiar to Linux/bash users.
Recommendations
- Include instructions for editing the hosts file on Linux (e.g., using sudo nano /etc/hosts) and macOS.
- Provide both PowerShell and bash syntax for variable assignment and command examples, or clarify which shell is being used.
- When referencing Azure Cloud Shell, mention both Bash and PowerShell options, and provide guidance for users on Linux/macOS.
- Ensure that all steps involving local file paths or tools have cross-platform equivalents or notes.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/includes/arc-region-note.md
...ob/main/articles/azure-arc/includes/arc-region-note.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for listing regions, but the PowerShell example is given immediately after the CLI example, and no explicit Linux shell (bash/zsh) or cross-platform command-line examples are provided. The presence of Azure PowerShell, which is most commonly used on Windows, may signal a slight Windows bias, especially since there is no mention of Linux-specific tools or shell usage.
Recommendations
- Add explicit bash/zsh examples for Linux users, such as using jq or grep with az CLI output.
- Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Consider listing the Azure CLI example first, as it is more universally available.
- Mention that PowerShell Core is available on Linux, if retaining the PowerShell example.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/private-link.md
...lob/main/articles/azure-arc/kubernetes/private-link.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates Windows bias by exclusively referencing the Azure portal (GUI) and Azure CLI for configuration steps, without providing any Linux-specific or cross-platform command-line examples (e.g., Bash, PowerShell, or Linux-native tools). There are no references to Linux-specific patterns, tools, or considerations, and all example commands are generic Azure CLI, which is available on both platforms but lacks explicit Linux context. The troubleshooting section uses 'nslookup' (available on both platforms), but does not mention Linux-specific DNS tools or troubleshooting steps. No PowerShell-specific examples are present, but the overall flow assumes familiarity with Azure portal and Azure CLI, which are more commonly used in Windows environments.
Recommendations
- Include explicit Linux/Bash shell examples for Azure CLI commands, showing usage in a Linux terminal.
- Add instructions for configuring DNS forwarding and firewall rules using Linux-native tools (e.g., iptables, firewalld, systemd-resolved).
- Provide guidance for users managing Kubernetes clusters on Linux, such as using kubeadm, kubectl, or Linux-based DNS servers (e.g., BIND, dnsmasq).
- Mention cross-platform compatibility of Azure CLI and clarify any OS-specific prerequisites or differences.
- Add troubleshooting steps using Linux tools (e.g., dig, systemctl status) alongside nslookup.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/multicloud-connector/add-public-cloud.md
...les/azure-arc/multicloud-connector/add-public-cloud.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page presents instructions for connecting AWS and GCP to Azure via the multicloud connector, but all example workflows for uploading templates and configuring access are described using graphical portals (Azure portal, AWS CloudFormation console, GCP Console/Cloud Shell). There are no explicit examples or command-line instructions for Linux users (e.g., using AWS CLI, gcloud CLI, or Terraform from a Linux shell). The only mention of running Terraform locally refers to Azure Cloud Shell, which is typically a Bash environment, but this is not highlighted or explained for Linux parity. There is no mention of Powershell, but the overall approach assumes users are comfortable with web portals and does not provide parity for Linux command-line workflows.
Recommendations
- Add explicit Linux CLI instructions for uploading CloudFormation templates to AWS (using aws CLI) and running Terraform for GCP (using gcloud CLI and terraform CLI).
- Provide example commands for each major step (e.g., creating stacks, uploading templates, assigning IAM roles) using CLI tools on Linux.
- Clarify that Azure Cloud Shell is Bash-based and suitable for Linux users, and provide equivalent instructions for running commands locally on Linux.
- Include troubleshooting tips for common Linux environments (e.g., Ubuntu, CentOS) when running Terraform or gcloud CLI.
- Ensure parity by listing both portal and CLI workflows side-by-side, so users can choose their preferred method regardless of OS.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/resource-bridge/system-requirements.md
...icles/azure-arc/resource-bridge/system-requirements.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page for Azure Arc resource bridge system requirements shows evidence of Windows bias. The management machine requirements and Azure CLI installation instructions link specifically to the Windows version first, with no mention of Linux or macOS equivalents. There are no examples or instructions for installing or running Azure CLI or the arcappliance extension on Linux or macOS, nor are there references to Linux-specific patterns or tools. All CLI examples and references assume a Windows environment.
Recommendations
- Add explicit instructions and links for installing Azure CLI and the arcappliance extension on Linux and macOS management machines.
- Include examples of CLI commands being run on Linux/macOS, including any differences in file paths, permissions, or environment setup.
- Ensure that references to management machine requirements mention Linux and macOS as supported platforms, and clarify any platform-specific requirements or limitations.
- Where CLI commands are shown, provide cross-platform notes or tabs (e.g., Windows, Linux, macOS) to demonstrate parity and highlight any differences.
- Review all links and references to ensure they do not default to Windows unless Windows is the only supported platform (which should be explicitly stated if true).
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/api-extended-security-updates.md
...les/azure-arc/servers/api-extended-security-updates.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is heavily focused on Windows Server 2012 and 2012 R2, with all examples and API payloads referencing Windows-specific targets. There are no examples or guidance for Linux systems, nor any mention of Linux equivalents, tools, or patterns. The only OS referenced for license management is Windows Server, and the customer intent is explicitly for Windows. No Linux scenarios or cross-platform considerations are discussed.
Recommendations
- Add examples for managing ESU licenses for Linux servers, if supported by Azure Arc.
- Include Linux-specific API payloads or CLI commands, such as targeting Linux distributions in the 'target' parameter.
- Clarify in the introduction whether Linux systems are supported or not, and if not, explicitly state the Windows-only scope.
- If Linux is not supported, provide links or references to documentation for Linux lifecycle management in Azure Arc.
- Ensure parity in documentation structure and examples for both Windows and Linux where applicable.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/azcmagent-disconnect.md
...ain/articles/azure-arc/servers/azcmagent-disconnect.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation exhibits mild Windows bias by describing the interactive browser login as 'Windows only' and listing it first among authentication options. Additionally, the only explicit method given for obtaining an access token is via the Windows PowerShell cmdlet `Get-AzAccessToken`, with no mention of Linux alternatives (e.g., Azure CLI). Linux is mentioned as a default for device code login, but examples and tooling references favor Windows.
Recommendations
- Provide Linux-specific instructions and examples where appropriate, such as how to obtain an access token using Azure CLI (`az account get-access-token`) on Linux.
- Reorder authentication options to present cross-platform methods (device code, service principal, Azure CLI) before platform-specific ones.
- Clarify that most authentication methods (except interactive browser login) are available on both Windows and Linux, and explicitly state Linux compatibility.
- Add explicit Linux command-line examples (e.g., bash) alongside any PowerShell examples.
- Where a method is Windows-only, suggest the equivalent Linux workflow or tool.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/manage-vm-extensions.md
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page presents Windows VM extensions before Linux equivalents, with a much longer and more detailed Windows extension table. Windows-specific tools (e.g., Windows Admin Center, OpenSSH for Windows) are highlighted, and Windows extensions are listed first, suggesting a prioritization of Windows scenarios. Linux extensions are covered, but with less detail and fewer examples. The ordering and emphasis may lead Linux users to perceive the documentation as Windows-centric.
Recommendations
- Present Windows and Linux extension tables side-by-side or alternate their order in different sections to avoid implicit prioritization.
- Ensure parity in the level of detail and number of examples for Linux extensions, matching those provided for Windows.
- Highlight Linux-specific management tools or patterns where relevant, similar to the coverage of Windows Admin Center.
- Include explicit cross-platform usage scenarios and call out differences or similarities in extension management for both OS types.
- Add more Linux-focused extension examples and links to Linux-specific documentation, especially for commonly used extensions.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/organize-inventory-servers.md
...ticles/azure-arc/servers/organize-inventory-servers.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page discusses organizing and inventorying servers with Azure Arc, mentioning support for both Windows and Linux platforms. However, examples and tooling references (Azure CLI, Azure PowerShell, ARM templates) are presented in a generic way, with no explicit Linux-specific examples or Linux-native tools mentioned. The documentation implicitly prioritizes Windows-centric management patterns and does not provide parity in examples or guidance for Linux users.
Recommendations
- Include explicit Linux examples alongside Windows examples, such as using Bash scripts or Linux command-line tools for tagging and querying resources.
- Reference Linux-native tools (e.g., shell scripts, cron jobs) for automating tagging and reporting, in addition to Azure CLI and PowerShell.
- Provide sample workflows or code snippets for Linux environments, such as onboarding Linux servers to Azure Arc using Bash.
- Clarify cross-platform support in each section and ensure that instructions are not implicitly Windows-centric.
- Add links to Linux-specific documentation or guides for Azure Arc management.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/run-command-security.md
...ain/articles/azure-arc/servers/run-command-security.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents Windows examples before Linux ones and references the Windows extension handler first. The metadata and custom tags emphasize Azure PowerShell, suggesting a Windows-centric approach. While both Windows and Linux examples are provided, the ordering and emphasis favor Windows.
Recommendations
- Present Linux and Windows examples in parallel or alternate the order to avoid implicit prioritization.
- Include Azure CLI examples for both platforms and avoid referencing PowerShell unless necessary for platform-specific tasks.
- Ensure metadata and custom tags reflect equal support for Azure CLI and Linux tools.
- Explicitly mention that all features and instructions apply equally to Linux and Windows, unless there are platform-specific differences.
- Provide links to Linux-specific documentation and troubleshooting resources alongside Windows ones.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/security-data-privacy.md
...in/articles/azure-arc/servers/security-data-privacy.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation generally presents Windows and Linux log locations side-by-side, maintaining parity. However, there is evidence of Windows bias: the link for retaining activity logs directs users to a page with PowerShell tabs, and the reference to PowerShell appears before any mention of Linux alternatives. Additionally, in the 'Azure Activity log' section, the example for sending activity log data references PowerShell specifically, without mentioning Linux CLI or Bash alternatives.
Recommendations
- Provide explicit Linux/Bash/Azure CLI examples alongside PowerShell commands for activity log retention and other operational tasks.
- Ensure that references to tools or commands are presented in a cross-platform manner, listing both Windows and Linux options together or in alternating order.
- Add tabs or sections for both PowerShell and Bash/Azure CLI in linked documentation, making it clear that both platforms are supported.
- Review linked pages to ensure Linux parity in examples and instructions, not just in log file locations.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/administer-arc-scvmm.md
...center-virtual-machine-manager/administer-arc-scvmm.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page focuses on Azure Arc-enabled System Center Virtual Machine Manager (SCVMM), a Windows-centric technology, and provides instructions and examples that assume a Windows environment. All operational examples use Azure CLI, but there is no mention of Linux-specific considerations, nor are there examples or guidance for Linux administrators (e.g., using bash, SSH from Linux, or Linux file paths). The instructions for credential updates, log collection, and resource management do not clarify cross-platform compatibility or provide Linux-oriented usage patterns.
Recommendations
- Explicitly state that all Azure CLI commands are cross-platform and provide examples for both Windows (PowerShell/CMD) and Linux (bash).
- Include Linux-specific instructions for SSH access, file path conventions, and environment setup where relevant (e.g., storing kubeconfig files, log output directories).
- Mention any platform-specific prerequisites or differences (such as installing Azure CLI or the connectedscvmm extension on Linux).
- Add screenshots or terminal output examples from Linux environments alongside existing Windows-centric images.
- Clarify whether SCVMM management operations can be performed from Linux workstations and, if not, explain the limitations.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/enable-scvmm-inventory-resources.md
...al-machine-manager/enable-scvmm-inventory-resources.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is focused exclusively on SCVMM (System Center Virtual Machine Manager), a Windows-centric management tool, with no mention of Linux equivalents or cross-platform alternatives. All examples and instructions assume the use of SCVMM and its inventory, which are only available on Windows. There are no references to Linux-based virtualization management tools (such as oVirt, KVM, or libvirt), nor are there examples for managing Linux VMs or resources.
Recommendations
- Add guidance or references for managing Linux-based virtualization environments (e.g., oVirt, KVM, libvirt) with Azure Arc, if supported.
- Include examples or links for enabling inventory resources from Linux virtualization platforms in Azure Arc.
- Clarify in the introduction that the instructions are specific to SCVMM/Windows environments, and provide parity documentation for Linux users if available.
- If Azure Arc supports Linux VM management, provide step-by-step instructions or links for those scenarios.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/terraform-vm-management.md
...ter-virtual-machine-manager/terraform-vm-management.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page focuses exclusively on SCVMM VM management using Terraform, but all examples and variable defaults assume Windows-centric patterns (e.g., 'Administrator' username, domain/workgroup settings, and SCVMM itself is a Windows-only technology). There are no Linux-specific examples, guidance, or mention of Linux VM management, and all operational steps and prerequisites are generic or implicitly Windows-oriented.
Recommendations
- Add explicit examples for managing Linux VMs via SCVMM (if supported), including Linux-specific variables (e.g., 'root' or other Linux usernames, SSH keys, etc.).
- Clarify whether SCVMM supports Linux VM lifecycle management and, if so, provide sample Terraform configurations for Linux VMs.
- Include notes or sections on differences in provisioning Windows vs. Linux VMs with SCVMM and Terraform.
- If Linux management is not supported, state this clearly to avoid confusion for cross-platform users.
- Where possible, avoid hardcoding Windows-centric values (like 'Administrator', domain/workgroup) in sample files, or provide alternatives for Linux.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/administer-arc-vmware.md
...cles/azure-arc/vmware-vsphere/administer-arc-vmware.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure CLI and Azure Portal for all administrative tasks, without providing Linux-specific instructions or examples. There are no mentions of Linux tools, shell commands, or platform-specific considerations (e.g., file paths, SSH usage from Linux, or Linux-based automation). The instructions and screenshots assume a Windows-centric workflow, and do not address Linux environments or provide parity for Linux administrators.
Recommendations
- Add explicit instructions and examples for Linux environments, including shell commands (bash), file path conventions, and SSH usage from Linux workstations.
- Include screenshots or descriptions for Linux desktop environments when referencing Azure Portal or CLI usage.
- Mention cross-platform compatibility of Azure CLI and clarify any differences in usage or prerequisites for Linux users.
- Provide troubleshooting steps and log collection instructions that consider Linux-specific scenarios (e.g., permissions, directory structures).
- Ensure that references to configuration files (e.g., kubeconfig) include Linux path examples and security best practices for Linux systems.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/create-custom-roles.md
...ticles/azure-arc/vmware-vsphere/create-custom-roles.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation focuses exclusively on the Azure portal UI and mentions Azure PowerShell and Azure CLI only in passing, without providing any command-line examples. While both Azure PowerShell and Azure CLI are cross-platform, the order of mention (PowerShell before CLI) and the lack of explicit Linux or Bash examples may subtly prioritize Windows workflows. There are no Linux- or Bash-specific instructions, screenshots, or references, and no mention of Linux-native tools or environments.
Recommendations
- Provide explicit Azure CLI (bash/shell) examples for creating and managing custom roles, alongside or before PowerShell examples.
- Include Linux/Bash command-line snippets and screenshots where relevant, especially for users who prefer or require non-Windows environments.
- When listing management options (Azure portal, PowerShell, CLI, REST API), alternate the order or explicitly state that both CLI and PowerShell are cross-platform.
- Add a section or links specifically addressing Linux/macOS users, clarifying that all operations can be performed from these platforms using Azure CLI.
- Ensure that references to command-line management (e.g., 'To manage custom roles using Azure PowerShell, Azure CLI...') are accompanied by direct links to both Windows and Linux usage guides.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/quick-start-create-a-vm.md
...es/azure-arc/vmware-vsphere/quick-start-create-a-vm.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively using Windows-centric examples, such as 'Administrator' as the default username, and VM templates named with 'win22'. There are no Linux-specific examples, usernames, templates, or instructions provided, and no mention of Linux tools or patterns. This may make it less accessible or relatable for users intending to deploy Linux VMs or manage Linux environments.
Recommendations
- Add Linux-specific examples alongside Windows ones, such as using 'ubuntu' or 'centos' templates and 'adminuser' or 'root' usernames.
- Provide sample variable values and template IDs for common Linux distributions.
- Include instructions or notes on Linux guest agent installation and configuration.
- Explicitly mention that both Windows and Linux VMs are supported, and link to relevant Linux documentation.
- Ensure parity in best practices and troubleshooting guidance for Linux VMs.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/external-validation.md
...zure-arc/workload-orchestration/external-validation.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring cross-platform coverage. However, PowerShell examples are always presented immediately after Bash, and in some cases, the PowerShell example is slightly more detailed (e.g., variable assignment syntax). There is a subtle 'windows_first' bias in the ordering and presentation, as PowerShell is always included and never omitted, while no Linux-specific tools or patterns (such as shell scripting, environment variables, or automation via cron) are mentioned. The Azure portal instructions are platform-neutral, but the CLI examples could better highlight Linux parity.
Recommendations
- Explicitly state that Bash examples are suitable for Linux/macOS environments and PowerShell for Windows, to help users choose the right example.
- Consider including a note about running Azure CLI in WSL (Windows Subsystem for Linux) for Windows users who prefer Bash.
- Add references or tips for Linux automation (e.g., using cron jobs for periodic validation checks) to balance the PowerShell/Windows automation bias.
- Ensure that any advanced scripting or troubleshooting examples are provided for both Bash and PowerShell, not just PowerShell.
- If possible, include troubleshooting steps or environment setup instructions specific to Linux (e.g., installing Azure CLI on Ubuntu, handling permissions, etc.).
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/initial-setup-configuration.md
.../workload-orchestration/initial-setup-configuration.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for workload orchestration setup, but the PowerShell tab is given equal prominence and detail as Bash, which is uncommon for Linux-focused workflows. The PowerShell examples use Windows-centric variable syntax and patterns, and there is no mention of Linux-specific tools or shell environments beyond Bash. The documentation does not reference Linux-native tools (e.g., native Linux CLI, shell scripting best practices) and does not clarify which environments (Windows, Linux, WSL) are recommended for each approach. The use of PowerShell may imply a Windows bias, especially for Azure Arc scenarios that often target Linux/Kubernetes clusters.
Recommendations
- Clarify the intended environment for each example (e.g., Windows, Linux, WSL, macOS) and recommend the best shell for Linux users.
- Provide Linux-native CLI examples (e.g., Bash, sh) as the primary or default tab, with PowerShell as a secondary option.
- Add notes on how to run these commands in Linux environments, including installation of the Azure CLI and prerequisites for Linux users.
- Include troubleshooting tips for Linux users, such as file permissions, environment variables, and differences in shell syntax.
- Mention Linux tools or patterns where relevant (e.g., jq for JSON manipulation, curl/wget for downloads) to improve Linux parity.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/quickstart-solution-multiple-shared-adapter-dependency.md
...quickstart-solution-multiple-shared-adapter-dependency.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation consistently presents both Bash and PowerShell examples for every CLI step, but PowerShell is always given equal prominence and detail as Bash, rather than being secondary or omitted. In some places, PowerShell syntax is shown first (e.g., variable assignment in the 'Define the variables for solution templating' section), and PowerShell-specific instructions are present throughout. There is no explicit Linux bias, and Windows/PowerShell is treated as a first-class citizen, which may be appropriate for Azure CLI documentation but does reflect a parity bias toward Windows environments. However, there are no examples that are exclusive to Windows or PowerShell, and Linux equivalents (Bash) are always present. There is no use of Windows-only tools, and all commands are cross-platform (Azure CLI, kubectl).
Recommendations
- Ensure Bash (Linux) examples are always listed first, as Bash is the default shell on most cross-platform environments.
- Add explicit notes clarifying that all CLI commands work identically on Linux, macOS, and Windows, and that Bash syntax is preferred for cross-platform scripting.
- Consider providing a single canonical Bash example for each step, with PowerShell as an optional tab for Windows users, rather than giving both equal weight.
- Review variable naming and assignment conventions to ensure Bash/Linux idioms are primary (e.g., use $VAR=VALUE rather than $VAR = VALUE).
- If any step is Windows-specific (e.g., file paths, environment setup), provide Linux/macOS equivalents or highlight differences.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/quickstart-solution-shared-adapter-dependency.md
...ation/quickstart-solution-shared-adapter-dependency.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every CLI command, but PowerShell is always presented as a first-class citizen alongside Bash, rather than as a secondary or alternative option. There is a slight Windows bias in the ordering and parity of examples: PowerShell examples are always present, and in some cases, Windows-specific syntax (e.g., variable assignment, backtick line continuation) is shown. There are no Linux-specific tools, troubleshooting steps, or environment setup instructions; the focus is on the Azure CLI, which is cross-platform, but the documentation does not address Linux-specific nuances or alternative shell environments (e.g., zsh, fish). No explicit Windows-only tools are mentioned, but the consistent inclusion and parity of PowerShell examples elevates Windows usage to equal status with Bash, which is less common in Linux-focused documentation.
Recommendations
- Add explicit notes clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, and mention that Azure CLI works on all platforms.
- Consider providing examples for other popular Linux shells (e.g., zsh) or at least note that Bash commands work in most Linux environments.
- If PowerShell is included, clarify its cross-platform availability (PowerShell Core) and note any differences for Windows vs. Linux users.
- Add troubleshooting tips or environment setup instructions for Linux users (e.g., installing Azure CLI on Ubuntu, handling file permissions, using sudo).
- If possible, provide a default example in Bash (Linux-first), with PowerShell as an alternative, to reflect the majority of cloud-native and orchestration users who use Linux.
- Ensure that any file paths, environment variables, or command syntax are compatible with Linux conventions, and call out any Windows-specific differences.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/service-group.md
...cles/azure-arc/workload-orchestration/service-group.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation consistently presents PowerShell examples alongside Bash, but PowerShell examples are always listed second and are often more detailed, including Windows-specific scripting constructs (e.g., Set-Content, ConvertFrom-JSON, Select-Object). There is a slight 'Windows-first' bias in the sense that PowerShell is given parity and sometimes more detail, even though the core commands are cross-platform (az CLI). No explicit Windows-only tools are used, and Linux/Bash examples are present for every scenario. However, the PowerShell examples sometimes use constructs that are only available on Windows or require PowerShell Core on Linux, which may not be as familiar to Linux users.
Recommendations
- Ensure Bash examples are as detailed as PowerShell examples, especially for JSON manipulation and file handling.
- Add explicit notes clarifying that PowerShell examples require PowerShell Core on Linux/macOS, or provide alternative Bash-native approaches for complex scripting (e.g., JSON editing).
- Consider listing Bash examples first to reflect the default shell on most Linux systems.
- Where PowerShell-specific constructs are used (e.g., ConvertFrom-JSON, Set-Content), provide Bash equivalents using jq or standard shell utilities.
- Review whether any steps assume Windows file paths or scripting conventions, and clarify cross-platform compatibility.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/tutorial-service-group-scenario-1.md
...oad-orchestration/tutorial-service-group-scenario-1.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, ensuring parity between Linux and Windows users. However, PowerShell is given equal prominence to Bash, which is a Windows-centric shell, and the use of PowerShell-specific syntax (backticks, variable assignment) may suggest a slight Windows bias. There are no Linux-specific tools or patterns highlighted, and the Azure CLI is used throughout, which is cross-platform. No Windows-only tools or patterns are mentioned, and Linux examples are not missing.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows, possibly in a note at the top of the command sections.
- Consider providing additional Linux-native troubleshooting or validation steps (e.g., using kubectl, journalctl, or Linux file system commands) where appropriate.
- Ensure that any references to file paths, environment variables, or shell behaviors are clearly distinguished between Windows and Linux/macOS conventions.
- If possible, add a short section on how to install and use Azure CLI and Helm on Linux, for users who may be new to these tools.
- Review variable naming and scripting conventions to ensure they are idiomatic for each platform (e.g., avoid Windows-style variable names in Bash).
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/tutorial-service-group-scenario-3.md
...oad-orchestration/tutorial-service-group-scenario-3.md
Medium 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 throughout, and in some cases, the PowerShell tab appears before Bash. There is a strong focus on PowerShell scripting, which is primarily used on Windows. No Linux-specific tools, patterns, or troubleshooting steps are mentioned, and the only shell options are Bash and PowerShell, with no mention of native Linux shells or workflows beyond Bash. There are no examples using Linux-only utilities or approaches, and the validation steps rely on Helm and az CLI, which are cross-platform, but the scripting style and tab structure may subtly favor Windows users.
Recommendations
- Ensure Bash examples are always listed before PowerShell to avoid implicit Windows-first bias.
- Add explicit notes about Linux compatibility for all CLI commands and scripts.
- Include troubleshooting steps or tips specific to Linux environments (e.g., file permissions, environment variables, common shell issues).
- Mention alternative Linux shells (e.g., Zsh) or workflows where appropriate.
- Clarify that PowerShell examples are for users who prefer PowerShell, but Bash is the default for Linux.
- Consider adding a section on validating deployments using native Linux tools (e.g., kubectl, grep, awk) in addition to Helm.
- Review tab ordering and ensure Linux/Bash is the default or first tab shown.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/tutorial-service-group-scenario-4.md
...oad-orchestration/tutorial-service-group-scenario-4.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all steps, but PowerShell examples are always present and given equal prominence to Bash. There is a slight Windows bias in that PowerShell is included as a primary scripting option, even for Kubernetes and Helm operations that are typically performed in Bash or Linux shells. Additionally, the PowerShell examples use Windows-style paths and conventions (e.g., .\file.yaml), and there is no mention of Linux-specific tools or troubleshooting patterns. The Azure CLI is cross-platform, but the inclusion of PowerShell throughout may suggest a Windows-centric workflow.
Recommendations
- Consider making Bash the default or first example in each tab, as Bash is the primary shell in most Kubernetes/Linux environments.
- Add explicit notes clarifying that all commands work on Linux, macOS, and Windows, and that Bash is recommended for Linux/macOS users.
- Where PowerShell is used for Helm or Kubernetes commands, clarify that Bash is more common in Linux environments and provide troubleshooting tips for Linux users.
- Include Linux-specific validation or troubleshooting steps, such as using kubectl, journalctl, or other Linux-native tools.
- Ensure file path examples use forward slashes (/) in Bash and clarify path differences between platforms.
Azure Portal
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/azure-portal-dashboards-create-programmatically.md
...tal/azure-portal-dashboards-create-programmatically.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page demonstrates mild Windows bias. In the 'Overview' and deployment sections, Azure PowerShell is mentioned before Azure CLI, and PowerShell is listed as a primary method for deployment alongside REST API and CLI. There are no explicit Linux shell examples, and PowerShell is referenced in both the main text and in links, suggesting a preference for Windows tooling. However, Azure CLI is also mentioned, and the JSON templates themselves are platform-neutral. The dashboard examples do include links to both Linux and Windows VM creation guides, with Linux listed first.
Recommendations
- Ensure Azure CLI is mentioned before or alongside PowerShell in all lists and instructions, as CLI is cross-platform.
- Add explicit Bash or shell script examples for deploying templates, to demonstrate Linux parity.
- Clarify that both Azure CLI and PowerShell are available on all platforms, and provide links to installation guides for Linux users.
- Avoid listing Windows-specific tools (PowerShell) before cross-platform tools (CLI) unless contextually justified.
- Consider including a section or callout for Linux/macOS users, highlighting any platform-specific considerations.
Azure Portal
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/get-subscription-tenant-id.md
...in/articles/azure-portal/get-subscription-tenant-id.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page presents both Azure PowerShell and Azure CLI options for programmatic access, but PowerShell is consistently mentioned first and sometimes exclusively (e.g., 'Get-AzSubscription' is referenced before 'az account list'). This ordering and emphasis may subtly favor Windows users, as PowerShell is traditionally associated with Windows environments, while Azure CLI is cross-platform and more commonly used on Linux/macOS. There are no explicit Linux examples or references to Linux-specific tools or workflows.
Recommendations
- Alternate the order of PowerShell and Azure CLI references, or list Azure CLI first to reflect its cross-platform nature.
- Explicitly mention that Azure CLI works natively on Linux and macOS, and provide example commands for these platforms.
- Include screenshots or instructions showing use of Azure CLI in a Linux terminal.
- Add a note clarifying that both PowerShell and CLI are available on all major platforms, and link to installation guides for Linux/macOS.
- Where possible, provide parity in examples and tips for both Windows (PowerShell) and Linux/macOS (CLI).
Azure Portal
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/quickstart-portal-dashboard-azure-cli.md
.../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 Windows bias by providing only a Windows VM creation example (using the 'win2016datacenter' image) and referencing Windows-specific username and password requirements. No Linux VM creation example or Linux-specific guidance is provided, despite Azure CLI supporting both platforms equally. The documentation implicitly prioritizes Windows by omitting Linux alternatives.
Recommendations
- Add a Linux VM creation example alongside the Windows example, using a popular image such as 'UbuntuLTS'.
- Include links to Linux-specific username and password requirements, similar to the Windows references.
- Clarify that Azure CLI commands work for both Windows and Linux VMs, and provide guidance for customizing the dashboard template for Linux VMs.
- Ensure that dashboard template customization instructions mention both Windows and Linux VM resource types and monitoring options.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/authenticate-aks-cross-tenant.md
...es/container-registry/authenticate-aks-cross-tenant.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (web UI) and omitting command-line examples. There are no examples using cross-platform tools such as Azure CLI, Bash, or PowerShell, nor are there any Linux-specific instructions. The workflow assumes use of the graphical portal, which is more common on Windows, and does not provide parity for users who prefer or require command-line automation, typical in Linux environments.
Recommendations
- Add Azure CLI command examples for all steps, especially for app registration, service principal creation, and role assignment.
- Include Bash script snippets for updating AKS credentials and provisioning service principals.
- Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide platform-agnostic instructions.
- Where the Azure portal is referenced, provide equivalent CLI commands as alternatives.
- If PowerShell is used, ensure Bash or Azure CLI equivalents are always provided.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/buffer-gate-public-content.md
...icles/container-registry/buffer-gate-public-content.md
Medium 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. There are no explicit Linux shell (bash) or native Linux tool examples, nor is there mention of Linux-specific workflows or patterns. The documentation refers to Azure PowerShell as a primary tool, which is more commonly used in Windows environments, and does not offer parity for Linux users beyond the Azure CLI. The order of presentation (CLI first, then PowerShell) is neutral, but the lack of bash or Linux-native examples may disadvantage Linux users.
Recommendations
- Add explicit bash shell examples for image import using Azure CLI, demonstrating usage in native Linux environments.
- Clarify that Azure CLI commands can be run directly in Linux/macOS terminals, not just in Azure Cloud Shell.
- Include references to Linux-native authentication patterns (e.g., using environment variables, .docker/config.json) when discussing Docker Hub authentication.
- Mention Linux package managers or tools (e.g., apt, yum) for installing Azure CLI and Docker, to assist Linux users.
- Consider adding a section or tab for 'Linux/Bash' alongside 'Azure CLI' and 'Azure PowerShell' to ensure parity in examples and workflows.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-auth-kubernetes.md
...ntainer-registry/container-registry-auth-kubernetes.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation provides command-line examples using Azure CLI and kubectl, which are cross-platform tools. However, the only credential reset example uses the Azure CLI, which is most commonly installed and used on Windows, and there is no mention of Linux-specific patterns or alternatives (such as using bash scripting, environment variables, or Linux-native credential management). There are no PowerShell-specific commands, but the documentation does not explicitly address Linux usage or provide Linux-centric examples, which may lead to implicit Windows bias.
Recommendations
- Explicitly mention that Azure CLI and kubectl are cross-platform and provide installation instructions or links for Linux users.
- Include Linux-specific tips, such as using environment variables to securely handle credentials, or using bash scripting for automation.
- Add examples of credential management on Linux, such as using keyring or secret management tools.
- Ensure that references to Azure CLI do not imply Windows-only usage, and clarify that commands work on Linux/macOS as well.
- Consider adding a note or section for Linux users, highlighting any differences or best practices.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-authentication-managed-identity.md
...https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-authentication-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides parallel Azure CLI and Azure PowerShell instructions for all steps, but PowerShell is a Windows-centric tool and is presented as an equal alternative throughout. There are no explicit Linux shell examples for Azure resource management (e.g., Bash scripts using REST API or SDKs), and PowerShell installation is described for Ubuntu, which is uncommon for Linux users who typically prefer Bash. The documentation does mention Docker installation for Linux, macOS, and Windows, but all resource management examples are either Azure CLI or PowerShell, with PowerShell given equal prominence despite its Windows origins.
Recommendations
- Provide Bash script examples for Azure resource management tasks, especially for Linux users who may not use PowerShell.
- Clarify that Azure CLI is the recommended tool for Linux environments, and mention that PowerShell is optional.
- Reorder sections so that Azure CLI instructions appear before PowerShell, emphasizing CLI as the default for cross-platform usage.
- Add explicit notes about the typical usage patterns on Linux (e.g., Bash + Azure CLI) and avoid suggesting PowerShell installation on Linux unless necessary.
- Where possible, include SDK or REST API examples for advanced users who may prefer direct scripting over CLI/PowerShell.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-troubleshoot-access.md
...ner-registry/container-registry-troubleshoot-access.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page does not provide explicit Windows-only examples or tools, but it exhibits subtle Windows bias by omitting platform-specific troubleshooting steps and examples for Linux. Generic instructions (e.g., configuring Docker behind a proxy, restarting the Docker daemon) do not specify how to perform these actions on Linux, and there are no Linux shell command examples (such as systemctl for restarting Docker). The mention of tools like 'nslookup' (commonly available on both platforms) is paired with 'dig', but there is no explicit parity in example commands or troubleshooting steps for Linux users. The documentation assumes familiarity with Azure CLI and Docker, which are cross-platform, but lacks Linux-specific guidance where platform differences exist.
Recommendations
- Add explicit Linux command examples for common troubleshooting steps, such as restarting the Docker daemon (e.g., 'sudo systemctl restart docker').
- Include Linux-specific instructions for configuring Docker behind a proxy, referencing relevant documentation for systemd-based systems.
- Where network utilities are mentioned, provide example commands for both Windows (e.g., 'nslookup') and Linux (e.g., 'dig', 'host').
- Clarify any platform-specific differences in Azure CLI usage or environment setup, especially for networking and firewall configuration.
- Ensure that troubleshooting steps and examples are presented for both Windows and Linux environments, or explicitly state when instructions apply equally to both.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-tutorial-github-verify-notation-trusted-signing.md
...gistry-tutorial-github-verify-notation-trusted-signing.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Linux (bash) and Windows (PowerShell) examples for all relevant CLI commands, but the Windows/PowerShell examples are always presented immediately after the Linux ones, and sometimes with additional context (e.g., directory creation). There is a slight tendency to elaborate more on Windows-specific steps (such as using New-Item in PowerShell), and Windows examples are consistently present, which may suggest a mild Windows bias. However, Linux parity is generally maintained, and no steps are missing for Linux users.
Recommendations
- Ensure that Linux and Windows examples are equally detailed, especially for tasks like directory creation.
- Consider alternating the order of examples (sometimes presenting Windows first, sometimes Linux) to avoid implicit prioritization.
- Add a short note at the beginning clarifying that all steps are equally supported on Linux and Windows, and that users should follow the tab appropriate for their environment.
- If possible, provide cross-platform commands (e.g., using Python or Node.js scripts) for tasks like downloading files, to further reduce platform-specific bias.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/includes/azure-container-registry.md
...ontainer-registry/includes/azure-container-registry.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but PowerShell is given its own dedicated tab, which can be interpreted as a Windows-centric approach. There is no explicit mention of Linux-specific tools or shell environments, nor are there examples tailored for Bash or Linux users. The Azure CLI example is cross-platform, but the PowerShell example may imply a preference for Windows users. No Linux-specific instructions or troubleshooting are provided.
Recommendations
- Add explicit Bash/Linux shell examples, showing how to run the Azure CLI command in a typical Linux terminal.
- Clarify that Azure CLI is fully supported on Linux and macOS, and provide any necessary platform-specific notes (e.g., authentication, environment setup).
- If PowerShell is mentioned, also mention PowerShell Core (pwsh), which is cross-platform, and clarify usage on Linux/macOS.
- Consider adding a 'Linux' or 'macOS' tab alongside 'Azure CLI' and 'Azure PowerShell' to reinforce parity.
- Include troubleshooting or environment setup notes for Linux users if any differences exist.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/quickstart-client-libraries.md
...cles/container-registry/quickstart-client-libraries.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page demonstrates mild Windows bias in the 'Prerequisites' section, where Azure PowerShell is listed as a primary tool for creating a container registry, alongside the Azure portal and Azure CLI. PowerShell is a Windows-centric tool, and its mention before Linux-native alternatives (such as Bash or shell scripting) may suggest a Windows-first approach. However, the main code samples for all languages use cross-platform tools (Azure CLI, SDKs) and environment variables, and do not rely on Windows-specific patterns or tooling. No PowerShell-heavy examples or missing Linux equivalents are present.
Recommendations
- In the 'Prerequisites' section, list Azure CLI before Azure PowerShell, as CLI is cross-platform and more commonly used on Linux.
- Explicitly mention that Azure CLI commands work on both Windows and Linux/macOS, and provide links to installation instructions for multiple platforms.
- If referencing PowerShell, clarify its cross-platform availability or provide Bash equivalents where appropriate.
- Ensure that any future examples or instructions do not assume a Windows environment (e.g., avoid referencing Windows-only paths, tools, or environment variables).
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/quickstart-connected-registry-arc-cli.md
...iner-registry/quickstart-connected-registry-arc-cli.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but the PowerShell example is presented after Bash and uses Unix-style command substitution (suggesting WSL or PowerShell Core on Linux/Mac). There is no exclusive use of Windows tools, nor are Windows-specific patterns or tools mentioned before Linux equivalents. The Azure CLI is used throughout, which is cross-platform, and kubectl commands are shown in Bash. However, the presence of a PowerShell example and its explicit labeling may suggest a slight Windows bias, especially since no explicit Linux-only or MacOS-only instructions are given, and the PowerShell example is not clearly marked as Windows-only.
Recommendations
- Clarify which shell examples are for which platforms (e.g., label PowerShell as 'Windows PowerShell' and Bash as 'Linux/macOS Bash').
- Provide explicit instructions for running PowerShell commands on Windows (e.g., using Windows PowerShell vs. PowerShell Core on Linux/macOS).
- Add a note about running Azure CLI and kubectl on Windows, including any differences in authentication, file paths, or command syntax.
- Ensure parity by including troubleshooting or setup notes for Linux and macOS users, such as permissions, environment variables, or file system differences.
- If possible, provide a cross-platform script or highlight any platform-specific caveats for the commands shown.
Copilot
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/copilot/capabilities.md
...gement-docs/blob/main/articles/copilot/capabilities.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page exhibits mild Windows bias by listing PowerShell script generation before Linux-oriented equivalents and referencing Windows-centric tools (PowerShell) in the 'Write and optimize code' section. While Azure CLI and Terraform/Bicep are mentioned, PowerShell is given equal or greater prominence, and there are no explicit Linux shell (bash) or Linux-specific troubleshooting examples. No Linux-first examples or tools are highlighted, and the troubleshooting scenarios reference Windows-centric products (Power BI) without Linux alternatives.
Recommendations
- Add explicit Linux/bash shell script generation examples alongside PowerShell.
- Ensure Linux tools (e.g., bash, SSH, Linux VM management) are mentioned with parity to Windows/PowerShell.
- Provide troubleshooting examples relevant to Linux environments (e.g., issues with Linux VMs, SSH connectivity, Linux containers).
- When listing script generation capabilities, alternate or randomize the order of Windows and Linux tools, or group them together to avoid implicit prioritization.
- Reference Linux-native tools and workflows (e.g., systemd, journalctl, Linux package management) where appropriate.
Lighthouse
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/concepts/cross-tenant-management-experience.md
...hthouse/concepts/cross-tenant-management-experience.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page demonstrates mild Windows bias, primarily in the 'APIs and management tool support' section, where Azure PowerShell is mentioned before Azure CLI, and the PowerShell example is more detailed. There are no Linux-specific examples or tools referenced, and the documentation does not mention Linux shell equivalents (e.g., Bash) or provide parity in command-line examples. However, the page does mention managing both Windows and Linux machines with Azure Arc, which helps mitigate bias.
Recommendations
- Provide Linux/Bash shell examples alongside PowerShell examples, especially for common management tasks.
- Mention Azure CLI before or alongside Azure PowerShell to avoid 'Windows first' ordering.
- Include references to Linux-native tools or workflows where relevant (e.g., Bash scripts, SSH, cloud-init).
- Clarify that Azure CLI is cross-platform and suitable for Linux users.
- Add explicit examples or links for managing Linux resources, not just mentioning their existence.
Lighthouse
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/remove-delegation.md
...b/main/articles/lighthouse/how-to/remove-delegation.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents PowerShell instructions before Azure CLI examples for removing delegations, which may suggest a Windows-first approach. PowerShell is a Windows-centric tool, and its prominence can indicate bias, especially if not balanced with Linux-friendly alternatives. However, Azure CLI instructions are also provided, and no exclusive Windows tools or patterns are mentioned. Portal instructions are platform-neutral.
Recommendations
- Present Azure CLI examples before PowerShell examples to prioritize cross-platform tools.
- Explicitly mention that Azure CLI works natively on Linux and macOS, while PowerShell may require additional setup.
- Add Bash script examples where appropriate to further support Linux users.
- Clarify that all portal instructions are platform-agnostic and accessible from any OS.
- Review other documentation pages for similar ordering or tool selection biases.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/deploy-overview.md
...ob/main/articles/azure-arc/edge-rag/deploy-overview.md
Low Priority
View Details →
Detected Bias Types
missing_linux_example
Summary
The documentation page describes the deployment of Edge RAG with Azure Arc in a platform-neutral way, focusing on Azure resources and Kubernetes clusters. However, it lacks explicit examples or instructions for Linux environments, such as Linux CLI commands, Linux-specific tooling, or references to Linux management patterns. There are no Windows-specific tools or PowerShell examples, but the absence of Linux examples may hinder Linux users.
Recommendations
- Add explicit Linux CLI examples for key deployment steps, such as using kubectl, az CLI, and NFS configuration.
- Include references to Linux management hosts and clarify that the 'driver machine' can be Linux-based.
- Provide sample configuration files or scripts for Linux environments.
- Mention Linux-compatible monitoring and evaluation tools where relevant.
- Ensure parity in documentation by listing both Windows and Linux options for management and deployment tasks.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/azcmagent-genkey.md
...ob/main/articles/azure-arc/servers/azcmagent-genkey.md
Low Priority
View Details →
Detected Bias Types
missing_linux_example
Summary
The documentation provides a generic CLI example without specifying platform-specific usage. However, it does not include any examples or notes for Linux environments, nor does it mention platform differences or provide Linux-specific guidance. There is no explicit Windows bias (such as Powershell examples or Windows tools), but the lack of Linux-specific content may leave Linux users uncertain about compatibility or usage nuances.
Recommendations
- Add explicit examples for both Windows (CMD/Powershell) and Linux (Bash) shells to demonstrate cross-platform usage.
- Include a note clarifying that the command works identically on both Windows and Linux, or highlight any platform-specific considerations.
- Mention prerequisites or environment setup steps for Linux users, such as package installation or permissions.
- If relevant, provide troubleshooting tips for common issues encountered on Linux systems.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/scenario-onboard-azure-sentinel.md
...s/azure-arc/servers/scenario-onboard-azure-sentinel.md
Low Priority
View Details →
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any platform-specific examples or instructions, but it also does not mention Linux tools, commands, or patterns. There are no explicit Windows or PowerShell examples, but the lack of Linux-specific guidance or parity (such as shell commands, Linux agent installation notes, or troubleshooting tips) may leave Linux users underserved.
Recommendations
- Add explicit instructions or examples for onboarding Linux-based Arc-enabled servers, including relevant shell commands and troubleshooting steps.
- Clarify whether the Azure Monitor Agent installation steps differ for Windows and Linux, and provide links or sections for both.
- Include references to Linux log paths, agent configuration files, or common Linux security event sources to help Linux administrators integrate their systems effectively.
- Ensure that any screenshots or UI references are not Windows-centric, or provide Linux equivalents where appropriate.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/rbac-guide.md
...rticles/azure-arc/workload-orchestration/rbac-guide.md
Low Priority
View Details →
Detected Bias Types
missing_linux_example
Summary
The documentation page focuses exclusively on Azure RBAC concepts and role definitions without providing any platform-specific command-line examples. However, it references 'CLI access' and 'Azure portal access' user scenarios but does not specify or demonstrate how to perform RBAC tasks using CLI tools on either Windows (e.g., PowerShell) or Linux (e.g., Azure CLI in Bash). There is no explicit Windows bias in terms of tools or examples, but the lack of any Linux-specific examples or parity guidance constitutes a 'missing_linux_example' bias.
Recommendations
- Add explicit examples for performing RBAC operations using Azure CLI in Bash, suitable for Linux environments.
- If PowerShell examples are added in future revisions, ensure equivalent Bash/Azure CLI examples are provided.
- Clarify that RBAC operations can be performed cross-platform and provide guidance for both Windows and Linux users.
- Include troubleshooting notes or environment setup instructions for Linux users where relevant.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/azcmagent-config.md
...ob/main/articles/azure-arc/servers/azcmagent-config.md
Low Priority
View Details →
Detected Bias Types
missing_linux_example
Summary
The documentation provides command-line examples for azcmagent config but does not show any platform-specific commands, shell syntax, or usage patterns. However, all examples use generic CLI syntax and do not mention or demonstrate Linux-specific shell usage (e.g., Bash, environment variables, piping, or file redirection), nor do they clarify platform differences. There is a subtle bias in that the extension allowlist example references 'AzureMonitorWindowsAgent', which is Windows-specific, without mentioning a Linux equivalent.
Recommendations
- Add Linux-specific examples, such as using azcmagent config commands in Bash scripts, with environment variables, or showing output redirection.
- Include extension allowlist examples for Linux agents (e.g., 'Microsoft.Azure.Monitor/AzureMonitorLinuxAgent').
- Explicitly state platform compatibility and note any differences in usage or available configuration properties between Windows and Linux.
- Where possible, balance examples to show both Windows and Linux agent scenarios.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/azcmagent.md
...docs/blob/main/articles/azure-arc/servers/azcmagent.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation page presents installation path information for Windows before Linux, and provides more detail about Windows-specific behavior (PATH variable update, console restart) than for Linux. No explicit Linux examples or troubleshooting notes are given, and Windows is mentioned first in the installation section.
Recommendations
- Present Windows and Linux installation paths in parallel, or alternate which is mentioned first.
- Provide Linux-specific details, such as whether the installation path is added to $PATH, and any required steps to make the CLI available (e.g., symlinking, shell configuration).
- Include troubleshooting notes for Linux users similar to those given for Windows (e.g., if a shell restart is needed).
- Add Linux-specific examples or notes where appropriate, such as permissions or file system differences.