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 1751-1775 of 2334 flagged pages
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 some tools, there are subtle signs of Windows bias: Windows links are listed first, PowerShell/cmd.exe is referenced for Windows-specific instructions, and Linux installation instructions for curl are less explicit. There are no Linux-specific examples or troubleshooting tips, and some notes focus on Windows shell behaviors.
Recommendations
- Present installation links for all platforms in a consistent order (e.g., alphabetical or Linux first).
- Provide explicit Linux/macOS installation instructions for curl (e.g., 'sudo apt install curl' for Ubuntu, 'brew install curl' for macOS).
- Add Linux/macOS shell usage notes where Windows-specific shell behaviors are mentioned (e.g., clarify curl usage in Bash/zsh).
- Include troubleshooting tips or version checks for Linux/macOS environments, not just Windows.
- Avoid referencing Windows-specific shells (cmd.exe, PowerShell) without providing equivalent Linux/macOS guidance.
Create Pull Request
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 First
Windows Tools
Missing Linux Example
Summary
The documentation page lists network requirements for Azure Arc Resource Bridge, but exhibits mild Windows bias. Windows-specific services (e.g., Windows NTP, sts.windows.net, login.windows.net, servicebus.windows.net) are mentioned, and Windows terminology appears in several URLs and notes. The 'Windows NTP Server' is called out specifically, with no mention of Linux NTP alternatives. Azure CLI installation is referenced, but no OS-specific guidance is given. Linux tools and patterns (e.g., Linux NTP, Linux CLI installation) are not mentioned, and Windows-related endpoints are listed before Linux equivalents. However, the documentation does reference Linux package sources (packages.microsoft.com) and log collection for Linux components, indicating some Linux support.
Recommendations
- Add explicit mention of Linux NTP servers (e.g., pool.ntp.org) alongside Windows NTP.
- Clarify that Azure CLI installation instructions apply to both Windows and Linux, or link to OS-specific guides.
- Where Windows-specific endpoints are listed (e.g., sts.windows.net, login.windows.net), clarify if Linux equivalents exist or if these are required for all OSes.
- Ensure examples and notes reference both Windows and Linux management machines, not just Windows terminology.
- Add guidance for Linux firewall/proxy configuration if only Windows tools are referenced elsewhere.
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 critical tasks. However, PowerShell examples are given equal prominence to Azure CLI, and in some sections (such as onboarding clusters), PowerShell is presented immediately after CLI. PowerShell is a Windows-centric tool, and its inclusion alongside CLI may create friction for Linux/macOS users, especially since Azure CLI is cross-platform and more commonly used outside Windows. No Linux-specific commands or shell examples (e.g., Bash scripts) are provided, but the CLI examples are sufficient for Linux/macOS users. There are minor instances where Windows/PowerShell environment variable syntax is shown alongside Linux export syntax, but no Linux-specific tools or patterns are highlighted.
Recommendations
- Consider explicitly stating that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Where environment variables are set, clarify the syntax differences between Bash (Linux/macOS) and PowerShell (Windows), or provide both syntaxes side-by-side.
- Add a brief note that Azure PowerShell is primarily for Windows users, while Azure CLI works on all platforms.
- Ensure that CLI examples are shown first and are clearly marked as the default for non-Windows environments.
- Optionally, provide Bash script examples for common tasks to further improve Linux parity.
Azure Arc
Quickstart: Connect an existing Kubernetes cluster to Azure Arc
...les/azure-arc/kubernetes/quickstart-connect-cluster.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for connecting a Kubernetes cluster to Azure Arc. Azure CLI is cross-platform, while Azure PowerShell is primarily used on Windows, though it is available for Linux/macOS. The CLI and PowerShell instructions are presented in parallel tabs throughout, but Azure PowerShell is mentioned equally and sometimes before Linux-native alternatives. There are no Linux-specific examples or shell scripts provided, and Windows/PowerShell environment variable syntax is shown alongside Bash, but not prioritized. The documentation does mention Docker for Linux/Mac/Windows and emphasizes that clusters must have Linux nodes, but overall, the bias is minor and mostly in the order and prominence of PowerShell examples.
Recommendations
- Consider clarifying that Azure CLI is the recommended, cross-platform tool for Linux/macOS users.
- Add explicit notes or links for Linux/macOS users about Azure PowerShell installation and compatibility.
- Where environment variables are set, ensure both Bash (Linux/macOS) and PowerShell (Windows) syntax are shown side-by-side, not just in separate tabs.
- Provide more Linux/macOS-specific troubleshooting tips or examples if relevant.
- If possible, add a short section at the top indicating which tool is best for which OS, to help users choose the most appropriate instructions.
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 and Linux VM extensions in separate sections, but Windows extensions are listed first and in greater detail. However, Linux extensions are also comprehensively covered, and deployment methods (Azure CLI, PowerShell, Portal, ARM templates) are presented neutrally. There are no Windows-only examples or tools mentioned exclusively, and both OSes are treated with parity in extension support.
Recommendations
- Consider alternating the order of Windows and Linux sections, or presenting them together in a unified table for direct comparison.
- Ensure that deployment examples in linked pages (not shown here) provide both Windows and Linux command-line usage.
- Explicitly state that all deployment methods (CLI, PowerShell, Portal, ARM templates) are available for both Windows and Linux extensions.
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 Windows (PowerShell) and Linux (Azure CLI) examples throughout, but Windows/PowerShell examples are often presented before Linux/CLI equivalents. Some instructions reference Windows-specific paths or tools (e.g., PowerShell, ProgramData), and minor notes are given for Windows PowerShell usage. However, Linux parity is generally maintained, and Linux-specific instructions (e.g., log file locations, package URLs) are included.
Recommendations
- Alternate the order of CLI and PowerShell examples so Linux users see their platform first in some sections.
- Explicitly clarify that Azure CLI commands work on both Windows and Linux, and provide Bash syntax where relevant.
- Ensure all file path references (logs, agent folders) are shown for both Windows and Linux side-by-side.
- Add brief notes for Linux users where Windows-specific instructions (e.g., PowerShell syntax, ProgramData paths) are mentioned.
- Consider including macOS-specific notes if relevant, especially for CLI usage.
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 First
Powershell Heavy
Summary
The documentation covers both Windows and Linux Arc-enabled servers and provides parity in feature descriptions and Azure CLI examples. However, there is a mild Windows bias: PowerShell examples are given equal prominence to Azure CLI, and PowerShell is inherently Windows-centric (though available on Linux, it's less commonly used there). In several sections, Windows is mentioned first (e.g., 'Windows and Linux'), and PowerShell is presented as a primary management option alongside CLI, which may not reflect typical Linux administrator workflows.
Recommendations
- Clarify that Azure CLI is the recommended cross-platform tool for Linux and macOS users.
- Consider listing Azure CLI examples before PowerShell examples, or explicitly note PowerShell's cross-platform availability.
- Add brief guidance for Linux users who may not use PowerShell, such as linking to instructions for installing PowerShell on Linux if needed.
- Where possible, use 'Linux and Windows' instead of 'Windows and Linux' to avoid subtle ordering bias.
- Ensure all screenshots and portal instructions are generic and not Windows-specific.
Azure Arc
How to migrate from legacy Log Analytics agents in non-Azure environments with Azure Arc
...in/articles/azure-arc/servers/migrate-legacy-agents.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux context, but Windows-specific tools (Windows Admin Center, Windows Server Graphical Installer) are mentioned explicitly, and PowerShell is referenced before Bash. Windows deployment options are described in more detail, while Linux equivalents (such as Linux graphical installers or Linux-specific management tools) are not mentioned. The order and depth of Windows examples/tools create a mild Windows bias.
Recommendations
- Add explicit Linux deployment examples, such as using Bash scripts, Ansible, or Linux-native tools for onboarding Azure Arc.
- Mention Linux graphical installers or clarify if only command-line options are available for Linux.
- Provide parity in describing Linux management workflows (e.g., using Ansible, SSH, or other Linux-native automation tools) alongside Windows Admin Center and Group Policy.
- Ensure that PowerShell and Bash examples are given equal prominence, ideally side-by-side.
- Clarify any limitations or differences for Linux users in the deployment and management process.
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 provides troubleshooting guidance for both Windows and Linux, including error codes, exit codes, and log file locations. However, in the 'Agent verbose log' section, Windows examples are presented first and use PowerShell syntax, while Linux examples follow. Windows-specific tools and paths (e.g., PowerShell, %ProgramData%) are mentioned before their Linux equivalents. There is a minor bias in ordering and tool emphasis, but Linux parity is generally maintained.
Recommendations
- Alternate the order of Windows and Linux examples in sections to avoid always showing Windows first.
- Where possible, present Windows and Linux examples side-by-side for easier comparison.
- Explicitly mention Linux log file locations and commands before or alongside Windows equivalents.
- Ensure all troubleshooting steps reference both Windows and Linux paths/tools equally.
- Add clarifying notes when a tool or path is Windows-only, and provide Linux alternatives where applicable.
Azure Arc
Support matrix for Azure Arc-enabled System Center Virtual Machine Manager
...pport-matrix-for-system-center-virtual-machine-manager.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation is primarily focused on System Center Virtual Machine Manager (SCVMM), a Windows-centric technology. Windows tools and patterns (such as WinRM, Windows Management Framework, and Windows Server versions) are mentioned first and in detail. Linux support is referenced, but only as a secondary option for installing Arc agents, and Linux prerequisites are listed after Windows ones. There are minor notes about Linux workstations, but Windows is clearly the primary platform throughout.
Recommendations
- Where Linux is supported (e.g., installing Arc agents), provide Linux examples and instructions with equal prominence to Windows ones.
- Clarify any limitations or performance differences for Linux users (e.g., deployment scripts running slower on Linux), and suggest workarounds or optimizations.
- Include explicit guidance for Linux-based environments where relevant, such as network configuration or firewall rules.
- Ensure that Linux prerequisites and steps are not only listed, but also explained and linked to relevant documentation.
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 shown after Bash, which is a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used, and all instructions are cross-platform via Azure CLI. No critical sections are Windows-only.
Recommendations
- Continue to provide Bash and PowerShell examples side-by-side.
- Consider clarifying that Azure CLI commands work on Linux, macOS, and Windows equally.
- Optionally, add a note for macOS users if there are any OS-specific caveats (none detected here).
- If desired, alternate the order of Bash and PowerShell tabs in future documentation to avoid perceived bias.
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 is a subtle Windows bias: Windows-specific tools, features, and examples (such as PowerShell, Windows Server management, and Windows registry/files) are often mentioned first or in more detail than their Linux counterparts. Some links and tabs default to Windows-focused content, and automation examples reference PowerShell before other options. Linux is supported, but parity in examples and tool coverage could be improved.
Recommendations
- Ensure that all automation and configuration examples (e.g., Azure Automation, Update Manager) explicitly mention and provide parity for Linux, including Bash/CLI and Linux daemon examples where applicable.
- When listing supported tools or interfaces (e.g., CLI, PowerShell, SDKs), alternate the order or explicitly state cross-platform support.
- For links that default to Windows tabs or content, ensure Linux tabs/examples are equally visible or referenced.
- Expand on Linux-specific management scenarios (e.g., managing Linux daemons, file systems) alongside Windows registry/files.
- Highlight Linux support in self-service and automation scenarios, not just as an afterthought.
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) onboarding script options and instructions. However, Windows/PowerShell examples and guidance are consistently presented first, and additional notes are given for Windows users (e.g., avoiding PowerShell ISE). The troubleshooting and retry sections also show Windows commands before Linux equivalents. There is no evidence of missing Linux examples or exclusive mention of Windows tools; Linux parity is maintained, but Windows is prioritized in ordering and detail.
Recommendations
- Alternate the order of Windows and Linux instructions, or present them side-by-side to avoid implicit prioritization.
- Add Linux-specific troubleshooting notes if relevant, similar to the PowerShell ISE note for Windows.
- Ensure screenshots and UI guidance are not Windows-centric if possible.
- Explicitly state that both Windows and Linux are equally supported at the start of relevant sections.
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 lists new features for Azure Arc-enabled VMware vSphere. While most features are platform-neutral or mention both Windows and Linux, there are instances where Windows-specific features (such as customizing guest OS settings for Windows VMs and Windows Server Management) are highlighted before Linux equivalents. Windows tools like Azure PowerShell are mentioned alongside cross-platform tools, but Windows-specific management features are sometimes listed first. Overall, Linux support is present (e.g., SSH-based agent installation, Ansible playbook), but Windows examples and tools tend to be mentioned before or more prominently.
Recommendations
- Ensure Linux-specific features and tools are mentioned with equal prominence and ordering as Windows features.
- Where Windows tools (e.g., PowerShell, Group Policy) are listed, include Linux equivalents (e.g., Bash scripts, Ansible, Puppet) and clarify their applicability.
- Add explicit Linux/macOS examples where possible, especially for agent installation and VM management.
- Review ordering of features to avoid consistently listing Windows features first unless justified by usage statistics.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash (Linux/macOS) examples are consistently presented before PowerShell (Windows) examples. There are no sections or features that are Windows-only, nor are there any missing Linux examples or exclusive references to Windows tools.
Recommendations
- No significant changes needed. The documentation already provides full parity for Linux/macOS and Windows users.
- Optionally, clarify in the introduction that both Bash and PowerShell examples are provided for cross-platform support.
- If desired, alternate the order of Bash and PowerShell tabs in different sections to avoid any perception of bias toward one platform.
Azure Arc
Create a Solution with Shared Adapter Dependency with Workload Orchestration
...ation/quickstart-solution-shared-adapter-dependency.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for every CLI command and variable definition, but consistently presents Bash examples first. There are no Windows-specific tools or patterns used, and all commands are cross-platform via the Azure CLI. No Linux examples are missing, and Linux parity is maintained throughout. However, the presence of PowerShell examples alongside Bash may create minor friction for Linux/macOS users due to the extra content, but does not prevent task completion.
Recommendations
- Continue to provide Bash examples first, as Bash is the default shell for Linux/macOS.
- Consider grouping PowerShell examples in a collapsible section or secondary tab to reduce visual clutter for Linux/macOS users.
- Explicitly state that all commands are cross-platform and can be run on Linux, macOS, or Windows.
- Mention that Azure CLI is available on all major platforms, reinforcing Linux parity.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides CLI examples primarily using PowerShell syntax (with backticks for line continuation), especially in the May 2025 release section. Bash examples are used elsewhere, but there is inconsistency in the shell syntax. There are no Linux-specific tools or patterns mentioned, but the use of PowerShell syntax may create friction for Linux/macOS users. Azure CLI is inherently cross-platform, but the documentation could better reflect this by consistently providing Bash syntax or noting cross-platform compatibility.
Recommendations
- Standardize CLI examples to use Bash syntax (with \ for line continuation) or provide both Bash and PowerShell examples.
- Add a note clarifying that Azure CLI commands work on Windows, Linux, and macOS, and that the examples are not OS-specific.
- Avoid using PowerShell-specific syntax (backticks) unless the feature is Windows-only.
- Where possible, include explicit Bash examples for Linux/macOS users, especially in sections where PowerShell is used.
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 presented first, followed by PowerShell. There are no Windows-specific tools or patterns, and all commands use the Azure CLI or Helm, which are cross-platform. No Linux/macOS examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Maintain the current structure, as Bash and PowerShell parity is excellent.
- Consider explicitly stating that all examples are cross-platform and that Azure CLI and Helm work on Linux, macOS, and Windows.
- If desired, alternate the order of Bash and PowerShell tabs in some sections, or clarify that Bash is shown first for consistency, not preference.
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
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are included throughout, and in some sections (such as variable naming and file paths), Windows conventions (e.g., backslashes in PowerShell) are used. Bash examples are always presented first, but the presence of PowerShell examples may indicate a slight Windows bias, especially since PowerShell is primarily used on Windows, though it is also available on Linux/macOS. No Windows-only tools or patterns are used, and all commands are cross-platform (Azure CLI, Helm).
Recommendations
- Clarify that PowerShell examples are also valid for PowerShell Core on Linux/macOS, or explicitly mention cross-platform compatibility.
- Consider adding a note about file path conventions (e.g., backslash vs. forward slash) for users on different platforms.
- Ensure that Bash and PowerShell examples are equally maintained and that Bash is always presented first for Linux/macOS parity.
- If possible, provide a brief explanation for users who may be unfamiliar with PowerShell on non-Windows systems.
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
Windows Tools
Summary
The documentation provides authentication options and examples for both Windows and Linux, but there is a mild bias in favor of Windows: the interactive browser login is described as 'Windows only' and is presented first, and Windows certificate store options are discussed in detail. The access token section references a Windows-specific PowerShell cmdlet (Get-AzAccessToken) without mentioning Linux alternatives. However, Linux authentication methods (device code, service principal, Azure CLI) are well-covered, and examples are generally OS-neutral.
Recommendations
- Present authentication options in a more OS-neutral order, or explicitly state Linux defaults first when relevant.
- For access token acquisition, mention cross-platform methods (e.g., Azure CLI az account get-access-token) alongside Windows PowerShell cmdlets.
- Clarify that most examples and flags are applicable to both Windows and Linux unless otherwise noted.
- Add a brief note or table summarizing which authentication methods are available on each OS.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides installation instructions for client tools across platforms, but Windows installation links are often listed first. There are several Windows-specific notes, such as recommending cmd.exe over PowerShell for curl, and mentioning PowerShell's curl alias. Linux installation instructions are present but sometimes less detailed or secondary. The overall bias is minor, as Linux/macOS users can still follow the instructions, but Windows is subtly prioritized.
Recommendations
- Present installation links for all platforms in parallel, rather than listing Windows first.
- Provide equally detailed instructions for Linux/macOS, including explicit package installation commands (e.g., 'sudo apt install curl').
- Clarify PowerShell-specific notes as optional, and ensure Linux/macOS equivalents are mentioned where relevant.
- Where possible, avoid platform-specific recommendations unless necessary, or provide alternatives for other OSes.
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 demonstrates mild Windows bias by mentioning SQL Server Management Studio (SSMS) as the primary graphical client tool and referencing Windows-centric patterns first. However, it does provide a Linux-compatible example using sqlcmd and acknowledges Linux environments (AKS, kubeadm, OpenShift). There are no exclusive Windows-only tools or commands, but SSMS is presented as the default GUI option, which is Windows-only.
Recommendations
- Explicitly mention cross-platform GUI tools such as Azure Data Studio alongside SSMS.
- Provide example connection instructions for Azure Data Studio or other Linux/macOS-compatible SQL clients.
- Clarify that sqlcmd is available on Linux, macOS, and Windows, and provide installation guidance or links for non-Windows platforms.
- Consider listing Linux/macOS options first or equally with Windows tools to avoid 'windows_first' bias.
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 with links that default to Windows installation instructions and mentions Azure CLI x64/32-bit requirements without clarifying Linux/macOS support. However, it does not provide Windows-specific commands or tools, and the overall guidance is platform-neutral. There are no PowerShell examples or Windows-only tools mentioned, but the management machine requirements link to Windows installation first and do not explicitly mention Linux/macOS compatibility.
Recommendations
- Add explicit guidance for Linux and macOS users regarding Azure CLI installation and compatibility.
- Provide links to Azure CLI installation instructions for Linux and macOS alongside the Windows link.
- Clarify that the management machine can be Linux, macOS, or Windows, and specify any OS-specific requirements if applicable.
- Ensure examples and instructions are platform-neutral or include platform-specific variations where necessary.
Azure Arc
Troubleshoot Azure Arc resource bridge issues
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is generally cross-platform and focused on Azure Arc resource bridge, which is not Windows-specific. However, there are minor signs of Windows bias: PowerShell is used for some troubleshooting steps (e.g., testing HTTP/2 connectivity and DNS resolution), and Windows paths are referenced in error messages. Windows tools and patterns (PowerShell, RDP) are mentioned before Linux equivalents, and Linux commands are less prominent or sometimes missing. Most CLI examples use Azure CLI, which is cross-platform, but PowerShell is referenced for troubleshooting network issues.
Recommendations
- Provide Linux/macOS equivalents for PowerShell troubleshooting steps, such as using curl or wget for HTTP/2 tests and dig/nslookup for DNS resolution.
- When referencing file paths or error messages, clarify if they are OS-specific and provide Linux/macOS alternatives where relevant.
- Ensure troubleshooting steps and CLI commands are equally documented for Linux/macOS environments, including permissions and SSH folder access.
- Mention Linux/macOS remote access patterns (e.g., SSH, terminal) alongside Windows (RDP, PowerShell) when discussing remote operations.