Azure Arc
465
Total Pages
253
Linux-Friendly Pages
212
Pages with Bias
45.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2334 issues found
Showing 2276-2300 of 2334 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides automation examples using Linux shell scripting and mentions both Linux and Windows script file extensions. However, when discussing automation, Windows tools (Task Scheduler) are mentioned before Linux equivalents (cron), and Windows script extensions (.cmd, .bat, .ps1) are listed before Linux/Mac (.sh). No PowerShell-specific examples are given, and the main CLI commands are cross-platform. There is a slight tendency to mention Windows patterns first, but Linux parity is generally maintained.
Recommendations
- List Linux/Mac script extensions (.sh) before Windows ones (.cmd, .bat, .ps1) to avoid subtle ordering bias.
- Mention Linux automation tools (cron) before Windows Task Scheduler, or present them together without prioritization.
- Provide explicit PowerShell and Bash script examples if platform-specific scripting is discussed.
- Clarify that all az CLI commands work identically on Linux, macOS, and Windows.
Create Pull Request
Azure Arc
Configure Authentication for Edge RAG Preview Enabled by Azure Arc
.../articles/azure-arc/edge-rag/prepare-authentication.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias by referencing Windows Notepad as the example tool for storing IDs, and by not mentioning or providing alternatives for Linux/macOS users. All instructions are portal-based and do not reference platform-specific CLI tools, but the only explicit tool mentioned is Windows Notepad. There are no PowerShell examples, but the lack of parity in tool recommendations and examples may create minor friction for non-Windows users.
Recommendations
- Replace 'Windows Notepad' with a platform-neutral suggestion such as 'a text editor (e.g., Notepad, TextEdit, gedit, nano)'.
- Where possible, provide CLI alternatives using Azure CLI or Microsoft Graph for users who prefer command-line workflows on Linux/macOS.
- Explicitly mention that the Azure portal is accessible from any OS and that steps are not Windows-specific.
- Add screenshots or notes indicating cross-platform compatibility.
Azure Arc
Requirements for Edge RAG Preview, Enabled by Azure Arc
.../blob/main/articles/azure-arc/edge-rag/requirements.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias by listing Windows Server NFS setup guides before Linux equivalents, referencing Windows-specific VM sizes and links, and mentioning a Windows machine as a recommended management host. While Linux is the required OS for VMs and Linux NFS setup is linked, Windows examples and tools are often referenced first or exclusively, and Linux management workflows are not described in detail.
Recommendations
- Present Linux and Windows setup guides side-by-side or list Linux first, given the VM OS requirement.
- Add explicit instructions or links for managing Azure Arc-enabled Kubernetes clusters from Linux/macOS hosts (e.g., installing Azure CLI, kubectl, Helm on Linux).
- Reference Linux VM sizes and hardware recommendations where appropriate, not just Windows-centric SKUs.
- Clarify that a Windows machine is optional and provide parity for Linux/macOS management hosts.
Azure Arc
Customer intent: As a cloud administrator, I want to list all Azure Arc-enabled Kubernetes resources, so that I can monitor and manage the connected clusters and their configurations effectively.
...les/azure-arc/includes/azure-arc-enabled-kubernetes.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for each query, with PowerShell examples present throughout. The PowerShell examples may be perceived as Windows-centric, and in each section, Azure CLI is shown before PowerShell, but there is no explicit mention of Linux/macOS-specific instructions, nor any discussion of platform differences or requirements for running the CLI or PowerShell commands on non-Windows systems.
Recommendations
- Add explicit notes confirming Azure CLI and Azure PowerShell are cross-platform, and provide installation/usage links for Linux/macOS.
- Include troubleshooting tips for running Azure PowerShell on Linux/macOS (e.g., .NET dependencies, shell integration).
- Consider adding bash or shell script examples where relevant, especially for automation scenarios.
- If there are any platform-specific caveats (e.g., authentication, environment variables), document them.
- Clarify that the Azure Portal is accessible from any OS with a browser.
Azure Arc
Azure RBAC on Azure Arc-enabled Kubernetes clusters
.../blob/main/articles/azure-arc/kubernetes/azure-rbac.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Azure CLI is used throughout, which is cross-platform, but references to the Azure portal and Microsoft Entra ID are inherently Windows-centric. Installation instructions for Azure kubelogin mention Windows and Mac before Linux, and some steps (e.g., SSH into master nodes, editing files with 'vi') assume Linux/Unix environments but do not provide explicit parity for Windows users. Conversely, there are no PowerShell-specific examples, but Windows is often mentioned first, and portal-based instructions are Windows-centric. Linux-specific instructions (e.g., kubelogin install) are present but appear after Windows/Mac. There are no explicit Linux-only gaps, but the ordering and tool references favor Windows.
Recommendations
- Provide Linux and macOS instructions/examples before or alongside Windows instructions, not after.
- Explicitly mention cross-platform compatibility for Azure CLI and kubectl commands.
- Add PowerShell examples where relevant, or clarify that commands work in Bash, PowerShell, and other shells.
- For portal-based steps, clarify that the Azure portal is web-based and accessible from any OS.
- For file editing and SSH steps, provide guidance for Windows users (e.g., using PuTTY, Windows Terminal, or WSL).
- Ensure that installation instructions for tools like kubelogin are equally detailed for all platforms.
Azure Arc
Diagnose connection issues for Azure Arc-enabled Kubernetes clusters
...les/azure-arc/kubernetes/diagnose-connection-issues.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows Examples Present
Windows Node Pool Example
Summary
The documentation provides both Linux and Windows examples for DNS troubleshooting in Kubernetes pods, including PowerShell commands and Windows node pool instructions. While most of the guide is platform-neutral and uses cross-platform tools (kubectl, Azure CLI), the DNS troubleshooting section includes explicit Windows-specific steps and tools (Resolve-DnsName, Windows container images, PowerShell), which may create friction for Linux/macOS users. However, Linux examples are present and generally shown first.
Recommendations
- Ensure that Linux/macOS troubleshooting steps are always presented before or alongside Windows-specific instructions.
- Clarify which steps are platform-specific and provide equivalent Linux/macOS commands where possible.
- Add explicit notes or tables summarizing platform differences for DNS troubleshooting.
- Consider providing macOS-specific DNS troubleshooting examples (e.g., using 'dig' or 'nslookup' on macOS).
- For Windows node pool examples, explain when and why a user would need to use them, and provide guidance for clusters without Windows nodes.
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound network access for Azure Arc agents in the Azure Government cloud, so that they can connect to necessary endpoints for proper functionality and management of connected clusters."
...etes/includes/network-requirements-azure-government.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Summary
The documentation lists 'sts.windows.net' as a required endpoint for certain scenarios. The inclusion of 'windows.net' suggests a Windows-centric service, and there is no mention of Linux-specific endpoints or tools. However, the page does not provide any OS-specific command-line examples, configuration steps, or instructions—so the bias is limited to endpoint naming and implied service orientation.
Recommendations
- Clarify whether 'sts.windows.net' is required for all platforms or only for Windows-based clusters.
- Add explicit notes or examples for Linux/macOS users if any steps or endpoints differ.
- Ensure parity in endpoint documentation by mentioning any Linux/macOS-specific endpoints or considerations if they exist.
- If platform-specific configuration is needed (e.g., firewall rules, proxy settings), provide examples for both Windows (PowerShell, Windows Firewall) and Linux (iptables, ufw, etc.).
Azure Arc
Azure Resource Graph sample queries for Azure Arc-enabled Kubernetes
...rticles/azure-arc/kubernetes/resource-graph-samples.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation references Azure PowerShell before Azure CLI when describing how to run queries, and the metadata includes a 'devx-track-azurepowershell' tag. This ordering and emphasis may subtly prioritize Windows-centric tools and workflows, even though Azure CLI is cross-platform. No explicit Linux/macOS examples or guidance are provided, but workarounds exist since Azure CLI and the portal are available on all platforms.
Recommendations
- List Azure CLI before Azure PowerShell when describing cross-platform workflows.
- Explicitly mention that Azure CLI and Resource Graph Explorer are available on Linux and macOS.
- Add example commands for both Azure CLI and PowerShell, or clarify that queries are platform-agnostic.
- Include a note on platform compatibility for all tools mentioned.
Azure Arc
Azure Arc-enabled Kubernetes system requirements
...n/articles/azure-arc/kubernetes/system-requirements.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for management and resource provider registration, but PowerShell examples are consistently presented first. PowerShell is a Windows-centric tool, and its prominence may signal a Windows-first bias. There are no explicit Linux/macOS examples (e.g., bash, zsh), nor is there mention of Linux-specific installation or usage patterns for Azure CLI. However, the CLI instructions are cross-platform, and no critical steps are Windows-only.
Recommendations
- Alternate the order of CLI and PowerShell examples, or present CLI (cross-platform) instructions first.
- Explicitly mention that Azure CLI is available and supported on Linux and macOS, and provide links to installation instructions for those platforms.
- Add notes or examples for common Linux/macOS shell environments (bash/zsh) where appropriate.
- Clarify that PowerShell Core is available cross-platform, if relevant, or provide bash equivalents for resource provider registration.
- Ensure parity in troubleshooting and tool installation guidance for Linux/macOS users.
Azure Arc
Azure Arc resource bridge system requirements
...icles/azure-arc/resource-bridge/system-requirements.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by linking Azure CLI installation instructions specifically for Windows in the management machine requirements, and by not providing explicit Linux/macOS examples or installation guidance. All CLI commands are generic, but the only installation link is for Windows, and there is no mention of Linux/macOS management machine requirements or parity.
Recommendations
- Add explicit instructions and links for installing Azure CLI on Linux and macOS in the management machine requirements section.
- Clarify that the management machine can be Windows, Linux, or macOS, and provide any OS-specific considerations (e.g., file paths, permissions).
- Include example CLI commands or configuration file locations for Linux/macOS environments.
- Ensure that all referenced CLI commands and extensions are confirmed to work cross-platform, and note any differences if present.
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge."
...e-arc/resource-bridge/includes/network-requirements.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page displays mild Windows bias. Windows-specific services and tools (e.g., time.windows.com, login.windows.net, sts.windows.net, servicebus.windows.net) are referenced, and Windows NTP is mentioned explicitly, while Linux equivalents (e.g., ntp.org, chrony) are not. The Azure CLI installer download is described generically, but no explicit Linux installation instructions or references are provided. The order of presentation often lists Windows endpoints before Linux-specific ones, and some notes (e.g., NTP) are written from a Windows-centric perspective. There are no Linux-specific configuration examples, and Linux time sync is not discussed.
Recommendations
- Include Linux/macOS equivalents for time synchronization (e.g., ntp.org, chrony) and clarify if time.windows.com is required for Linux VMs.
- Add explicit Linux/macOS installation instructions for Azure CLI and other tools where relevant.
- Balance the presentation order of endpoints and examples so that Linux and Windows are treated equally.
- Clarify which endpoints/services are required for Linux, Windows, or both, and provide guidance for each platform.
- Add notes or examples for Linux-specific log collection, package management, and time sync.
Azure Arc
Azure Arc resource bridge security overview
...rticles/azure-arc/resource-bridge/security-overview.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation mentions retrieving activity log entries with PowerShell and Azure CLI, listing PowerShell first and referencing it as a primary tool. There are no explicit Linux/macOS examples or references to platform-specific tools, but the mention of PowerShell before Azure CLI suggests a subtle Windows-first bias. No critical steps are Windows-only, and Azure CLI is cross-platform, so Linux/macOS users are not blocked but may feel secondary.
Recommendations
- List Azure CLI before PowerShell when describing cross-platform operations, as Azure CLI is natively supported on Linux/macOS.
- Explicitly mention that Azure CLI commands work on Linux/macOS and provide example commands for both platforms where appropriate.
- Avoid implying PowerShell is the default or primary tool unless necessary for a specific scenario.
- Add a note clarifying platform compatibility for all tools mentioned.
Azure Arc
Archive for What's new with Azure Connected Machine agent
...icles/azure-arc/servers/agent-release-notes-archive.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation consistently lists Windows download links before Linux, references Windows-specific tools (PowerShell, MSI installer, Windows Event Logs, WMI, Win32 API), and highlights Windows features and fixes in detail. PowerShell upgrades and telemetry are frequently mentioned, and Windows installer improvements are called out. While Linux features and fixes are present, Windows patterns and terminology are more prominent and often appear first. There are no critical sections that are Windows-only, but the overall framing and example order favor Windows.
Recommendations
- Alternate the order of Windows and Linux download links or present them together to avoid Windows-first perception.
- Ensure Linux-specific tools (e.g., systemd, journalctl, shell commands) are mentioned with equal prominence and detail as Windows tools.
- Highlight Linux features and fixes in summary sections, not just as bracketed notes.
- Include Linux/macOS equivalents for Windows-specific terminology (e.g., mention .deb/.rpm installers alongside MSI, systemd/journalctl alongside Event Logs).
- Balance PowerShell mentions with Bash/shell scripting references for Linux users.
- Add explicit parity notes when a feature or fix applies to both platforms, or clarify when it is platform-specific.
Azure Arc
Overview of the Azure Connected Machine agent
...blob/main/articles/azure-arc/servers/agent-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides detailed, separate sections for Windows and Linux agent installation, but the Windows section appears first and is more verbose, including tips about Group Policy and Windows-specific service accounts. Windows tools and patterns (MSI installer, Group Policy, NT SERVICE accounts) are described in detail, while Linux equivalents (systemd, package managers) are covered but with less depth. The overall structure and example order favor Windows, and troubleshooting/logging paths are described with Windows locations first.
Recommendations
- Reorder sections so Linux and Windows installation details are presented in parallel or alternate order, or begin with Linux to balance representation.
- Provide equally detailed tips for Linux, such as SELinux/AppArmor considerations, systemd unit permissions, and package manager troubleshooting.
- Include Linux-specific troubleshooting advice (e.g., dealing with systemd failures, log rotation, permissions).
- Ensure examples and tables list Linux and Windows paths side-by-side, rather than Windows first.
- Add parity for advanced configuration topics, such as customizing service accounts or security groups on Linux.
- Explicitly mention macOS support or lack thereof, if relevant.
Azure Arc
CLI reference for `azcmagent connect`
...b/main/articles/azure-arc/servers/azcmagent-connect.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by listing the 'Interactive browser login (Windows only)' authentication method first and referencing PowerShell's Get-AzAccessToken as the primary example for obtaining access tokens, while not providing equivalent Linux/macOS command examples (such as Azure CLI). However, the majority of examples and instructions are cross-platform and mention Linux explicitly where relevant.
Recommendations
- Reorder authentication options so that cross-platform or Linux-default methods (e.g., device code login) appear first.
- Provide explicit Linux/macOS equivalents for PowerShell commands, such as showing how to obtain an access token using Azure CLI (e.g., 'az account get-access-token').
- Clarify that most examples are OS-agnostic unless otherwise stated, and add notes where behavior differs by platform.
- Add a Linux/macOS-specific example for interactive login, if supported, or clarify its availability.
Azure Arc
Automatic extension upgrade for Azure Arc-enabled servers
...e-arc/servers/manage-automatic-vm-extension-upgrade.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides parity between Windows and Linux in most conceptual sections and explicitly states that Azure Arc-enabled servers can be Windows or Linux. However, there is a mild Windows bias in tooling references: Azure PowerShell is given its own section and detailed examples, while Linux users are directed to Azure CLI (which is cross-platform) but not to native Linux tools or shell scripts. The PowerShell section is more prominent and detailed, and Windows-only extensions are listed before Linux equivalents. The documentation mentions Windows tools (PowerShell) and provides installation guidance for the PowerShell module, but does not offer similar guidance for Linux-specific environments or scripting. The order of examples and extension lists tends to favor Windows-first presentation.
Recommendations
- Add explicit bash/zsh shell script examples for common extension management tasks, especially for Linux users who may not use Azure CLI or PowerShell.
- Provide installation and usage guidance for Azure CLI on Linux in the same detail as PowerShell on Windows.
- When listing extensions, group or order them by platform support (Windows-only, Linux-only, cross-platform) to clarify applicability.
- Ensure that Linux-specific troubleshooting or management patterns are mentioned where relevant.
- Consider adding a section on using automation tools common in Linux environments (e.g., Ansible, shell scripts) for extension management.
Azure Arc
CLI reference for `azcmagent disconnect`
...ain/articles/azure-arc/servers/azcmagent-disconnect.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation shows mild Windows bias by describing the interactive browser login as 'Windows only' and listing it first among authentication options. It also references the PowerShell cmdlet Get-AzAccessToken as an example for obtaining an access token, without mentioning Linux/macOS alternatives. However, Linux authentication flows (device code, Azure CLI) are described and supported, and examples are generally cross-platform.
Recommendations
- Explicitly mention Linux/macOS equivalents for obtaining access tokens (e.g., Azure CLI: 'az account get-access-token').
- Clarify that device code login is the default for Linux and Windows Server Core, and consider listing it first or in parallel with Windows options.
- Provide example commands for both Windows (PowerShell) and Linux/macOS (bash) where relevant.
- Add a note that all examples are cross-platform unless otherwise stated, and specify OS requirements for each authentication method.
Azure Arc
Enable VM extensions to Arc-enabled servers from the Azure portal
...icles/azure-arc/servers/manage-vm-extensions-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally presents a platform-neutral workflow for managing VM extensions via the Azure portal, which applies equally to Linux and Windows servers. However, in the example configuration step, only a Windows-specific scenario (deploying the Azure Monitor agent for Windows with a proxy) is mentioned, with no equivalent Linux example or clarification. This subtly prioritizes Windows use cases and may leave Linux users uncertain about their own configuration requirements.
Recommendations
- Include example configuration scenarios for both Windows and Linux extensions, or clarify when steps are platform-specific.
- When mentioning extension configuration, provide at least one Linux-specific example (e.g., deploying the Azure Monitor agent for Linux, or configuring a Linux extension with a proxy).
- Explicitly state that the portal workflow applies equally to Linux and Windows, and highlight any differences if they exist.
- Ensure screenshots and illustrations alternate or include both Linux and Windows perspectives where relevant.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows VM extensions before Linux equivalents, listing a larger number of Windows-specific extensions and providing more detailed links for Windows. However, Linux extensions are also covered in a dedicated section with parity for core functionality. No examples, commands, or tools are shown exclusively for Windows, and both platforms are mentioned in all major deployment methods.
Recommendations
- Alternate the order of Windows and Linux sections or present them side-by-side to avoid implicit prioritization.
- Ensure that extension lists for both platforms are equally comprehensive and detailed.
- Add explicit examples or links for Linux where Windows-specific links are provided.
- Consider a summary table showing extension parity across platforms.
Azure Arc
Authenticate against Azure resources with Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation presents Windows/Powershell examples and tools before Linux equivalents in several sections. PowerShell is referenced multiple times as the primary method for access policy assignment and token retrieval, with Windows-specific instructions and screenshots shown first. Linux/Bash examples are provided, but often after Windows instructions, and some links and guidance (e.g., assigning access policies) default to PowerShell before mentioning Azure CLI.
Recommendations
- Alternate the order of Windows and Linux examples so that neither platform is consistently prioritized.
- Provide Azure CLI examples alongside PowerShell for resource assignment and management tasks, as CLI is cross-platform.
- Ensure screenshots and sample outputs are provided for both Windows and Linux, not just PowerShell.
- Explicitly mention that all steps can be performed on Linux/macOS, and link to platform-neutral or Linux-first tutorials where available.
- Where possible, use platform-neutral language and tools (e.g., Azure CLI, REST API) in introductory and summary sections.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents the Windows example before the Linux example in the section on blocking Run commands locally. Both platforms are covered with equivalent Azure CLI commands, but Windows is shown first, which may subtly prioritize Windows users.
Recommendations
- Alternate the order of examples so that Linux is sometimes presented first.
- Explicitly state that the instructions apply equally to both Windows and Linux, and clarify any differences.
- Consider grouping platform-specific instructions together under clear headings, or provide a combined example for both platforms.
Azure Arc
Use Azure Private Link to Connect Servers to Azure Arc by Using a Private Endpoint
...in/articles/azure-arc/servers/private-link-security.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation generally maintains parity between Windows and Linux, especially in agent installation and DNS configuration. However, there are several instances of Windows bias: Windows examples and instructions are often presented first (e.g., Hosts file editing), Windows-specific tools and terminology (e.g., Windows Admin Center, C:\Windows\System32\drivers\etc\hosts) are mentioned before Linux equivalents, and screenshots and portal instructions use Windows-centric UI language. There is also a lack of explicit Linux command-line examples or references to Linux-specific troubleshooting tools.
Recommendations
- Alternate the order of Windows and Linux instructions/examples, or present them side-by-side.
- Include explicit Linux command-line examples for troubleshooting (e.g., dig, host) alongside nslookup.
- Mention Linux-specific management tools (e.g., Cockpit, SSH) where Windows Admin Center is referenced.
- Provide more detailed Linux agent installation steps, including package manager commands for common distributions.
- Ensure screenshots and UI instructions clarify that the process is identical for Linux servers where applicable.
Azure Arc
Quickstart - Connect a machine to Arc-enabled servers (Windows or Linux install script)
...n/articles/azure-arc/servers/quick-enable-hybrid-vm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Windows instructions before Linux in the agent installation section and specifies the use of PowerShell for Windows, which may signal a slight Windows bias. However, Linux instructions are present and clear, and both platforms are supported throughout the guide.
Recommendations
- Present Windows and Linux installation instructions in parallel or alternate which is shown first.
- Include explicit mention of Linux shell requirements (e.g., bash, sudo) for parity with the Windows PowerShell note.
- Where possible, provide cross-platform script invocation examples together, emphasizing equal support.
- Add troubleshooting tips for both platforms, not just Windows (e.g., common Linux errors, log locations).
Azure Arc
Extensions security for Azure Arc-enabled servers
...main/articles/azure-arc/servers/security-extensions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally maintains parity between Windows and Linux, but there is a consistent pattern of presenting Windows examples and instructions before Linux equivalents. PowerShell is used for Windows examples, while Bash is used for Linux, but Windows commands are often shown first. There are references to Windows-specific tools and scenarios (e.g., elevated command console, Windows Server 2012 ESU) before Linux ones. However, Linux examples are present for all major configuration steps, and there are no critical omissions for Linux users.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Explicitly state that all features and controls apply equally to Linux and Windows, and highlight any differences.
- Where Windows-specific scenarios (e.g., ESU) are mentioned, provide Linux context or clarify that the scenario is Windows-only.
- Ensure that references to management tools (PowerShell, Bash) are balanced and that CLI examples are shown for both platforms.
- Add a summary table or section that lists all commands for both platforms together for quick reference.
Azure Arc
Overview of Azure Connected Machine agent to manage Windows and Linux machines
...center-virtual-machine-manager/agent-overview-scvmm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides a balanced overview of both Windows and Linux agent installation, configuration, and resource management. However, the Windows installation details are presented before the Linux section, which may subtly prioritize Windows. Both platforms receive equivalent technical depth and coverage, with directories, services/daemons, environment variables, and logs described for each. No Windows-only tools, examples, or patterns are present, and Linux-specific details are included where appropriate.
Recommendations
- Present Windows and Linux installation details in parallel sections or alternate the order in different documentation pages to avoid implicit prioritization.
- Explicitly state that both platforms are equally supported at the beginning of the installation section.
- Where possible, use platform-neutral terminology and examples, or provide side-by-side comparisons.
- Ensure that any referenced scripts, troubleshooting steps, or advanced configuration are equally available for both platforms.