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 1951-1975 of 2334 flagged pages
Azure Arc
Run command on Azure Arc-enabled servers (Preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Azure CLI, PowerShell, and REST API as supported experiences, listing PowerShell (a Windows-centric tool) alongside Azure CLI and REST API. However, it does state that both Windows and Linux operating systems are supported. There are no explicit examples or instructions favoring Windows, but PowerShell is mentioned before Linux-native tools or scripting languages. The 'Next steps' section links to PowerShell guidance before REST API, which may subtly reinforce Windows-first patterns.
Recommendations
- Ensure that Linux-specific scripting examples and tools (such as Bash or shell scripts) are equally represented alongside PowerShell.
- In 'Next steps', consider listing Azure CLI (cross-platform) and REST API before PowerShell, or clarify that PowerShell is available on Linux/macOS as well.
- Add explicit statements or links highlighting Linux support and any Linux-specific considerations (e.g., shell script examples, file path conventions).
- Where PowerShell is mentioned, note its cross-platform availability to avoid implying Windows exclusivity.
Create Pull Request
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation covers troubleshooting for both Windows and Linux Azure Arc-enabled servers. However, there is some evidence of Windows bias: Windows log file paths and PowerShell/Windows command syntax are mentioned first in several sections, and Windows-specific tools (e.g., PowerShell, Windows environment variables) are referenced before Linux equivalents. Linux examples and paths are provided, but often after Windows, and some remediation steps reference Windows tools or concepts (e.g., `%TEMP%`, `%ProgramData%`) before Linux ones.
Recommendations
- Present Windows and Linux examples side-by-side, or alternate which OS is shown first in each section.
- When referencing log file locations or configuration paths, list both Windows and Linux paths together, rather than Windows first.
- Ensure remediation steps mention Linux equivalents (e.g., `/tmp` for `%TEMP%`) where applicable.
- Where PowerShell or Windows-specific commands are given, provide equivalent Bash/Linux commands.
- Consider adding a summary table or section highlighting OS-specific troubleshooting steps for quick reference.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally presents Azure Arc-enabled VMware vSphere as a cross-platform solution, supporting both Windows and Linux VMs. However, there are subtle biases: Windows tools and technologies (such as PowerShell, Windows Server management, and Windows registry/files) are mentioned first or more prominently in several sections. Some links and examples default to Windows tabs or scenarios, and PowerShell is highlighted as a primary automation tool. Linux support is present but often listed after Windows, and Linux-specific examples or tools are less emphasized.
Recommendations
- Ensure that all automation and configuration examples (such as runbooks, onboarding, and VM extensions) explicitly mention and provide parity for Linux alongside Windows.
- When referencing Azure Automation or runbooks, highlight Bash or Python examples equally with PowerShell, and provide links or tabs for both Windows and Linux where applicable.
- In sections discussing configuration, monitoring, and management, balance the order of presentation between Windows and Linux (e.g., 'Windows and Linux servers' instead of 'Windows servers and Linux servers').
- Where links default to Windows-specific tabs or content, ensure Linux tabs or documentation are equally visible and accessible.
- Add Linux-specific scenarios or callouts where unique steps or considerations exist, to help Linux users feel equally supported.
Azure Arc
Whats new in Azure Arc-enabled VMware vSphere
...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page provides a chronological list of new features for Azure Arc-enabled VMware vSphere. Windows-specific features (such as customizing guest OS settings for Windows VMs and Windows Server Management) are mentioned, but Linux features (like SSH-based agent installation) are also included. However, in several instances, Windows tools and patterns (e.g., System Center Configuration Manager, Group Policy, Azure PowerShell) are listed before or more prominently than their Linux equivalents (e.g., Ansible, Azure CLI). Windows examples and tools tend to appear first in lists, and Windows-specific enhancements are sometimes highlighted without equal Linux coverage.
Recommendations
- When listing tools or methods for agent installation or VM management, alternate the order so Linux tools (e.g., Ansible, Azure CLI) are not always last.
- Where Windows-specific features are described, ensure Linux equivalents (if available) are also mentioned or linked.
- Add explicit Linux/macOS examples or references alongside Windows/PowerShell ones, especially for common tasks (e.g., agent installation, VM management).
- Clarify when features are Windows-only to avoid confusion for Linux users.
- Consider a dedicated section for Linux enhancements or parity features.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently presented immediately after Bash examples, which could be interpreted as a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used, and all instructions are cross-platform via Azure CLI. No Linux/macOS examples are missing.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in some sections, or explicitly state that Bash examples are suitable for Linux/macOS and PowerShell for Windows.
- Add a brief note at the start clarifying that all CLI commands are cross-platform and Bash examples are intended for Linux/macOS users.
- Ensure screenshots and portal instructions do not reference Windows-only features or UI elements (none detected here).
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring parity for Linux/macOS and Windows users. However, in some sections, PowerShell examples are presented immediately after Bash, and occasionally Windows-specific encoding instructions are given (e.g., removing carriage returns in PowerShell). The order of examples is consistently Bash first, then PowerShell, which is a minor bias but does not impact functionality or clarity for Linux/macOS users.
Recommendations
- Maintain Bash-first ordering, but clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows.
- Explicitly state at the top which platforms each example is for, to help users quickly identify their relevant section.
- Ensure that any platform-specific instructions (such as encoding or file handling) are clearly labeled as Windows or Linux/macOS.
- Consider adding a brief note that all CLI commands (az, kubectl, docker) are cross-platform, and users can use Bash or PowerShell as appropriate for their OS.
Azure Arc
Create a Solution with Shared Adapter Dependency with Workload Orchestration
...ation/quickstart-solution-shared-adapter-dependency.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands and variable definitions, ensuring parity for Linux/macOS and Windows users. However, in most sections, Bash examples are presented before PowerShell, which is a minor bias ('windows_first') as Windows users may expect PowerShell examples first. No exclusive Windows tools, patterns, or terminology are used, and Linux/macOS users can fully follow the tutorial.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in each section, or explicitly state that Bash is for Linux/macOS and PowerShell for Windows at the top of the page.
- Add a brief note clarifying that all CLI commands are cross-platform and that Bash and PowerShell are provided for user convenience.
- Ensure that any future additions (e.g., troubleshooting, file manipulation) include both Bash and PowerShell examples.
Azure Arc
Multiple Solutions with a Single Shared Dependency at Different Levels
...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are consistently presented before PowerShell examples, which is a minor 'windows_first' bias in ordering. There are no Windows-only tools, patterns, or missing Linux examples. All commands use cross-platform Azure CLI and Helm tools.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in some sections, or clarify that Bash is shown first for consistency, not platform preference.
- Explicitly state that both Bash and PowerShell are fully supported and that the Azure CLI commands work on all platforms.
- If possible, add a short note at the top indicating Linux/macOS and Windows parity is maintained throughout.
Azure Arc
Solution with Multiple Shared Dependencies at Different Hierarchy Levels
...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for every step, but consistently presents Bash examples first, followed by PowerShell. There is no exclusive use of Windows tools or patterns, and all commands are cross-platform (using Azure CLI and Helm). However, the PowerShell examples are present throughout, which may suggest a slight Windows bias, but Linux/macOS users are fully supported.
Recommendations
- Maintain Bash examples as the primary example for cross-platform parity.
- Consider clarifying that all commands are cross-platform and can be run on Linux, macOS, or Windows (with Bash or PowerShell).
- Optionally, add a note that PowerShell Core is available on Linux/macOS for users preferring PowerShell.
- Ensure that any references to file paths or shell-specific syntax are correct for both platforms (e.g., use ./file for Bash, .\file for PowerShell).
Azure Arc
Customer intent: "As a network administrator, I want to configure secure outbound connectivity for the Azure Connected Machine agent so that I can ensure proper communication with Azure Arc while adhering to my organization's security policies."
...les/azure-arc/servers/includes/network-requirements.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides both Linux and Windows information for the Azure Connected Machine agent, but Windows-related resources and tools (such as Windows Admin Center and Windows installation package URLs) are often mentioned first or in more detail. Windows-specific service tags and tools are listed before Linux equivalents, and Windows Admin Center scenarios are highlighted, while Linux management tools are not mentioned. However, Linux installation URLs and OpenSSL guidance are present, and most instructions are cross-platform.
Recommendations
- Ensure Linux examples and tools are given equal prominence alongside Windows tools (e.g., mention Linux management tools if relevant).
- When listing URLs or service tags, alternate the order or group by platform to avoid always listing Windows first.
- Add explicit references to Linux equivalents for Windows Admin Center scenarios, or clarify if no equivalent exists.
- Include troubleshooting links for Linux networking/TLS issues, similar to the Windows-specific troubleshooting link provided.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are sometimes shown immediately after Bash, and some minor details (such as base64 encoding commands) are slightly more Windows-centric. The documentation does not exclusively mention Windows tools or patterns, and Linux-specific commands are present throughout. There is no critical bias preventing Linux/macOS users from completing the tasks.
Recommendations
- Ensure Bash and PowerShell examples are equally prominent, possibly by alternating which is shown first or by clarifying that Bash is for Linux/macOS and PowerShell for Windows.
- Where minor differences exist (such as file encoding or base64 commands), add explicit notes for both platforms.
- Consider adding a brief section at the top clarifying which shell to use for which OS, and that all steps are cross-platform unless otherwise noted.
- Review PowerShell snippets for unnecessary Windows-specific syntax and ensure Bash equivalents are accurate and complete.
Azure Arc
Multiple Solutions with a Single Shared Dependency at Different Levels
...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell examples are consistently shown after Bash. There are no Windows-specific tools or patterns used, and Linux examples are present throughout. The Azure CLI and Helm are cross-platform tools, and no steps are exclusive to Windows or PowerShell. However, the ordering of examples (Bash first, PowerShell second) is the only minor evidence of bias.
Recommendations
- Consider explicitly stating that both Bash and PowerShell examples are equivalent and supported on all platforms.
- Ensure that Bash and PowerShell tabs are equally visible and accessible.
- If possible, clarify that PowerShell examples can be run on Linux/macOS as well (using PowerShell Core).
- Add a note about cross-platform compatibility of Azure CLI and Helm.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page primarily references SQL Server Management Studio (SSMS), a Windows-only tool, as the first example for connecting to SQL Managed Instance enabled by Azure Arc. While sqlcmd is mentioned as cross-platform, SSMS is listed before sqlcmd, and no Linux-native graphical client alternatives (such as Azure Data Studio or DBeaver) are suggested. The examples and instructions are generally applicable to both Windows and Linux, but the documentation subtly prioritizes Windows tools and patterns.
Recommendations
- Mention cross-platform graphical SQL clients such as Azure Data Studio or DBeaver alongside SSMS.
- Provide explicit examples for connecting using sqlcmd on Linux (e.g., specifying the shell environment or package installation instructions).
- List sqlcmd before SSMS to emphasize cross-platform parity.
- Add a note clarifying that SSMS is Windows-only and suggest alternatives for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides installation instructions for client tools used with Azure Arc-enabled data services. While it includes links for Windows, Linux, and macOS for most tools, there are signs of Windows bias: Windows installation links are listed first, PowerShell/cmd.exe is referenced specifically for Windows users, and Linux installation instructions for curl are vague ('install curl package') compared to explicit Windows links. There is also a note about PowerShell's curl alias, but no equivalent Linux/macOS shell guidance.
Recommendations
- List Linux/macOS installation links before or alongside Windows links to avoid Windows-first ordering.
- Provide explicit Linux/macOS installation commands for tools like curl (e.g., 'sudo apt install curl', 'brew install curl').
- Add shell-specific notes for Linux/macOS users where PowerShell-specific guidance is given (e.g., explain curl usage in bash/zsh).
- Ensure parity in detail and clarity for Linux/macOS instructions compared to Windows.
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
Summary
The documentation provides cross-platform instructions and examples, with explicit Linux/Ubuntu guidance for kubelogin installation and generic shell commands for cluster configuration. However, in the section on installing Azure kubelogin, Windows and Mac are mentioned first, with Linux/Ubuntu instructions following. The overall guidance is platform-neutral, but minor ordering bias is present.
Recommendations
- Present Linux/macOS installation instructions alongside Windows, or in a neutral order (e.g., alphabetical).
- Where possible, clarify that all CLI commands are cross-platform unless otherwise noted.
- Explicitly mention macOS in shell command examples if relevant.
- Ensure that screenshots and portal instructions are equally applicable to all platforms.
Azure Arc
Simplify network configuration requirements with Azure Arc gateway
...zure-arc/kubernetes/arc-gateway-simplify-networking.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major tasks, but consistently lists Azure PowerShell examples after Azure CLI. There are no Linux-specific command-line examples (e.g., Bash scripts), but the CLI examples are cross-platform. The PowerShell examples, while useful for Windows users, may create friction for Linux/macOS users who are less likely to use PowerShell. No Windows-only tools or patterns are mentioned, and Linux parity is generally maintained, but the documentation could better highlight Linux/macOS workflows.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and preferred for Linux/macOS environments.
- Add brief notes or examples for Bash scripting or shell environments where relevant (e.g., setting environment variables).
- Consider mentioning that Azure PowerShell is available on Linux/macOS, but CLI is typically more native.
- Ensure that Linux/macOS users are guided to use Azure CLI for all tasks, and clarify any differences in environment variable syntax (e.g., export vs. $Env).
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
Summary
The documentation references Azure CLI installation links that default to Windows, and mentions Azure CLI x64 and x86 requirements without clarifying Linux/macOS support. However, the overall guidance is generic and does not appear to exclude Linux/macOS management machines or tools.
Recommendations
- Add explicit statements clarifying that Linux and macOS management machines are supported for Azure CLI and Arc resource bridge deployment.
- Provide installation links for Azure CLI on Linux and macOS alongside Windows, or use the main Azure CLI install page that covers all platforms.
- Mention any OS-specific requirements or limitations for the management machine, if applicable.
- If possible, include example commands or screenshots for Linux/macOS environments.
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent. While most features and fixes are presented in parallel for both platforms, Windows download links and version numbers are consistently listed first, and Windows-specific tools (such as PowerShell, msiexec, and GUI installer instructions) are mentioned without Linux equivalents. Some instructions and known issues are Windows-only, but Linux parity is generally maintained for core agent functionality.
Recommendations
- Alternate the order of Windows and Linux download links and version numbers to avoid implicit prioritization.
- When referencing Windows installation methods (e.g., msiexec, PowerShell), provide equivalent Linux installation instructions (e.g., using rpm, deb, or shell scripts) in the same section.
- Include troubleshooting tips for Linux installer issues alongside Windows installer known issues.
- Ensure that improvements or bug fixes referencing Windows tools (such as PowerShell scripts) also mention Linux alternatives if applicable.
Azure Arc
Simplify Network Configuration Requirements with Azure Arc Gateway
...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples throughout, but PowerShell examples are often shown alongside CLI, and occasionally Windows-specific notes are included (e.g., log file paths, PowerShell command syntax). Windows tools and patterns are referenced (such as PowerShell and Windows log locations), but Linux equivalents are also provided. In some sections, Windows is mentioned first (e.g., log viewing), and download.microsoft.com is referenced as the Windows installation package source, while packages.microsoft.com is referenced for Linux. Overall, Linux parity is good, but minor Windows-first ordering and PowerShell emphasis are present.
Recommendations
- Ensure CLI examples are presented before PowerShell, as CLI is cross-platform.
- Explicitly state that all CLI commands work on both Windows and Linux/macOS.
- Where file paths or log locations are mentioned, always provide both Windows and Linux equivalents side-by-side.
- Avoid phrasing that implies Windows is the default (e.g., 'On Windows...' before 'On Linux...').
- Consider adding Bash shell examples for Linux users where relevant.
- Clarify that onboarding and management can be performed equally from Linux/macOS systems.
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
Summary
The documentation page lists connectivity requirements for the Arc resource bridge, including both Windows and Linux-related endpoints. However, Windows-specific services (such as 'time.windows.com' for NTP and 'sts.windows.net' for authentication) are mentioned, and Windows terminology (e.g., 'Management machine', 'Windows NTP') appears before Linux equivalents. There is a slight bias toward Windows tools and endpoints, but Linux endpoints (such as 'packages.microsoft.com' and 'linuxgeneva-microsoft.azurecr.io') are also included. No OS-specific command examples are given, and the requirements are generally platform-neutral.
Recommendations
- Clarify when Windows-specific endpoints (e.g., 'time.windows.com', 'sts.windows.net') are only required for Windows deployments, and provide Linux equivalents (such as 'pool.ntp.org' for NTP) where appropriate.
- Add notes or examples for Linux management machines, including any differences in required endpoints or ports.
- Ensure that Linux-related endpoints and requirements are given equal prominence and are not listed after Windows-specific ones.
- Where possible, use OS-neutral language (e.g., 'management machine' instead of 'Windows management machine') unless the requirement is truly OS-specific.
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 provides parity between Windows and Linux VM extensions, listing both in separate, equally detailed tables. However, Windows extensions are presented first, which may subtly prioritize Windows users. All management methods (CLI, PowerShell, portal, templates) are mentioned together, and partner extensions are shown for both OSes. No examples or instructions are Windows-only, and Linux extensions are well-represented.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side, to avoid implicit prioritization.
- Explicitly state that all management methods (CLI, PowerShell, portal, templates) support both Windows and Linux, and provide links to Linux-specific usage guides where relevant.
- If possible, add a brief section or example showing deployment of an extension to a Linux VM using Azure CLI or templates, to reinforce parity.
Azure Arc
Access Azure resources with managed identity on Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Windows/PowerShell examples before Linux/Bash equivalents and uses PowerShell as the primary scripting language for Windows. Linux instructions are present and reasonably complete, but Windows examples and terminology are given first, which may create minor friction for Linux users.
Recommendations
- Alternate the order of Windows and Linux examples, or present both in parallel to avoid implicit prioritization.
- Explicitly state that both Windows and Linux are equally supported at the start of technical sections.
- Where possible, provide cross-platform examples (e.g., Azure CLI) in addition to OS-specific scripts.
- Ensure that screenshots and sample outputs are provided for both Windows and Linux, not just one platform.
Azure Arc
Run command on Azure Arc-enabled servers (Preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page references Azure CLI, PowerShell, and REST API as supported experiences, but PowerShell is mentioned alongside Azure CLI in metadata and in the 'Next steps' section, potentially implying a Windows-first or PowerShell-heavy bias. However, the page does state that both Windows and Linux are supported, and notes a Linux-specific limitation. No explicit Linux command examples or Linux-specific tooling are provided on this overview page.
Recommendations
- Ensure Linux-specific examples and limitations are equally highlighted, especially in introductory and 'Next steps' sections.
- Consider mentioning Bash or shell scripting as a supported experience for Linux users, if applicable.
- Add explicit links or references to Linux-focused documentation or examples, not just PowerShell.
- Clarify parity between Windows and Linux in terms of supported scripting languages and tools.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally presents Azure Arc-enabled VMware vSphere as a cross-platform solution, supporting both Windows and Linux VMs. However, there are subtle signs of Windows bias: Windows-specific tools and features (e.g., PowerShell, Windows Server management, Windows registry, Windows tabs in links) are often mentioned first or exclusively, and some links default to Windows-focused tabs. While Linux is supported and referenced, Linux examples or tools are less prominent or are mentioned after Windows equivalents.
Recommendations
- Ensure that all feature and tool mentions (e.g., Azure Automation, Update Manager, VM extensions) explicitly reference both Windows and Linux where supported, and provide parity in examples.
- When linking to docs with OS-specific tabs, use neutral or Linux-first tabs where possible, or clarify support for both OSes in the surrounding text.
- In lists of supported tools (CLI, PowerShell, SDKs), avoid placing PowerShell or Windows tools first by default; alternate or group by platform.
- Add explicit Linux examples or references (e.g., Bash, Linux daemons, Linux configuration) alongside Windows/PowerShell examples.
- Highlight Linux-specific capabilities or considerations where relevant, to reassure Linux users of full support.
Azure Arc
Connect VMware vCenter Server to Azure Arc by using the helper script
...ere/quick-start-connect-vcenter-to-arc-using-script.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows instructions and PowerShell notes are presented first and in greater detail. Windows-specific guidance (e.g., Set-ExecutionPolicy, PowerShell ISE warning) is more prominent, while Linux instructions are concise and lack equivalent troubleshooting or environment-specific notes. The retry command section also lists Windows before Linux.
Recommendations
- Present Windows and Linux instructions in parallel or alternate their order to avoid 'Windows first' bias.
- Add Linux-specific troubleshooting notes (e.g., common Bash issues, permissions, shell environment advice) similar to the PowerShell ISE warning for Windows.
- Ensure parity in detail and guidance for both platforms, including any script prerequisites or environment setup steps.
- Consider a tabbed interface or clear separation for Windows and Linux instructions to improve clarity and accessibility.