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 1626-1650 of 2334 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides installation links for client tools across platforms, but Windows examples and notes are presented first or more prominently. For 'curl', Linux installation instructions are less explicit than Windows. The kubectl section includes a Windows-specific note about using cmd.exe instead of PowerShell, but does not offer comparable Linux/macOS guidance. There is a PowerShell-specific explanation for curl, but no equivalent for Linux shells. Overall, Linux and macOS users may experience minor friction due to Windows-first ordering and less detailed Linux instructions.
Recommendations
- Ensure installation instructions for Linux and macOS are as explicit and accessible as Windows instructions.
- Provide shell-specific notes for Linux/macOS (e.g., bash/zsh) where PowerShell-specific guidance is given.
- Present platform options in parallel (Windows, Linux, macOS) rather than Windows-first ordering.
- Clarify Linux installation steps for tools like curl (e.g., 'sudo apt install curl' or 'yum install curl').
- Add notes for Linux/macOS users where Windows-specific caveats are mentioned (e.g., shell differences for curl).
Create Pull Request
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation provides both Linux and Windows approaches for base64 encoding files, but the Windows section is more detailed, mentioning certutil and findstr commands, while the Linux section only briefly references base64. The Linux example is minimal, and there is no explicit macOS guidance. The rest of the guide uses cross-platform tools (OpenSSL, Azure CLI, kubectl), but Windows-specific tools are mentioned without equivalent macOS instructions.
Recommendations
- Expand the Linux/macOS section to include decoding as well as encoding, and clarify that the base64 command works on macOS.
- Provide a macOS-specific note or example for base64 usage.
- Mention that certutil and findstr are Windows-only, and suggest alternatives for Linux/macOS (e.g., grep for findstr).
- Ensure parity in detail between Windows and Linux/macOS instructions for file encoding/decoding.
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 steps, but consistently presents Azure PowerShell (a Windows-centric tool) alongside Azure CLI, and sometimes before or equally with CLI. There are no Linux-specific command-line examples (e.g., Bash scripts), but the CLI examples are cross-platform. The PowerShell examples use Windows-style environment variable syntax and commands, which may confuse Linux/macOS users. The documentation does not mention Linux/macOS tools or patterns, and does not clarify that Azure PowerShell can be used cross-platform, potentially leading to a Windows bias.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Explicitly state that Azure PowerShell can run on Linux/macOS, or provide Bash shell equivalents for environment variable setting.
- Show Azure CLI examples first, as it is the most universal tool.
- Add notes or examples for Linux/macOS users, especially for environment variable syntax (e.g., export vs $Env:).
- Consider including Bash script snippets for common tasks where relevant.
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 both Windows and Linux-related endpoints and requirements, but there is a mild bias towards Windows in the ordering and terminology. Windows-specific services (e.g., 'time.windows.com', 'sts.windows.net', 'servicebus.windows.net') are mentioned, and Windows NTP is referenced before any Linux alternatives. The Azure CLI installer is mentioned, but no explicit Linux installation instructions or package managers (other than 'packages.microsoft.com') are referenced. However, Linux endpoints and requirements (e.g., 'linuxgeneva-microsoft.azurecr.io', 'packages.microsoft.com', SSH usage) are present, and the documentation is not Windows-exclusive.
Recommendations
- Explicitly mention Linux NTP alternatives (e.g., 'ntp.ubuntu.com', 'pool.ntp.org') alongside 'time.windows.com', clarifying when each is used.
- Provide examples or references for Linux Azure CLI installation (e.g., apt, yum, zypper) in addition to the generic 'Azure CLI Installer' endpoint.
- Ensure that Linux-related endpoints and requirements are given equal prominence and ordering as Windows-specific ones.
- Clarify that SSH and Kubernetes API server ports are relevant for both Windows and Linux management machines, and provide guidance for both OS types where 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 for all major operations, but PowerShell examples are consistently shown alongside CLI, and some CLI examples use backtick (`) line continuation, which is a Windows/PowerShell convention. Portal instructions are platform-agnostic, but CLI and PowerShell are presented as equivalent, with PowerShell sometimes shown after CLI. There is a minor bias in log file locations, with Windows mentioned first. The documentation references both Linux and Windows endpoints and installation packages, and explicitly includes Linux log file locations and onboarding instructions. Overall, Linux parity is good, but minor Windows-first ordering and Windows conventions are present.
Recommendations
- Use platform-neutral CLI syntax (avoid Windows-style backticks for line continuation; use standard Bash line continuation with \ for Linux/macOS examples).
- Explicitly state that Azure CLI commands work on Linux/macOS and Windows, and provide Bash-style examples where appropriate.
- Alternate the order of Windows and Linux log file locations, or present them together for parity.
- Where PowerShell is presented, clarify its applicability (Windows only, or cross-platform if using PowerShell Core).
- Consider providing Linux/macOS onboarding script examples if there are platform-specific steps.
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 Azure Arc-enabled server connectivity, but there are minor signs of Windows bias. Windows installation package URLs are listed before Linux equivalents, and Windows Admin Center is referenced as a management tool without mentioning Linux alternatives. Cipher suite configuration details are given for Windows first, with Linux relegated to a general OpenSSL note. However, Linux requirements and URLs are present, and critical tasks can be completed on Linux.
Recommendations
- List Linux and Windows installation package URLs in parallel or alternate order to avoid Windows-first bias.
- When referencing Windows Admin Center, mention Linux management alternatives (such as Azure CLI, SSH, or other tools) if applicable.
- Provide more explicit Linux configuration guidance for cryptographic protocols (e.g., OpenSSL configuration examples) alongside Windows-specific instructions.
- Ensure that troubleshooting links and sections for TLS issues include Linux-specific guidance, not just Windows.
- Where possible, add Linux command-line examples or references for endpoint lookups and network configuration.
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/exit codes and log file locations for each OS. However, in the 'Agent verbose log' section, Windows examples are presented first and use PowerShell-specific syntax (& operator, environment variables), while Linux examples follow. The log file paths and troubleshooting steps reference Windows locations before Linux equivalents. There is a minor bias toward Windows in ordering and tool references, but Linux parity is generally maintained.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Where possible, provide generic command syntax before OS-specific examples.
- Ensure Linux log file paths and troubleshooting steps are as prominent as Windows equivalents.
- Clarify that both Windows and Linux are equally supported, perhaps with a summary table or section.
- Use neutral language and avoid referencing Windows tools (e.g., PowerShell) unless necessary for the task.
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. However, there is mild bias in the ordering of examples: Azure PowerShell is presented after Azure CLI, and PowerShell-specific instructions are included, which may be less relevant for Linux users. The CLI section does clarify Linux compatibility, but PowerShell is still given a dedicated section and tip, which could be seen as slightly favoring Windows users. All critical tasks can be completed on Linux via Azure CLI, so Linux users are not blocked.
Recommendations
- Continue to emphasize Azure CLI as the cross-platform tool, and consider listing CLI instructions before PowerShell in all sections.
- Add explicit notes that Azure PowerShell is primarily for Windows, and recommend CLI for Linux/macOS users.
- Where possible, clarify that all CLI commands work identically on Linux, macOS, and Windows.
- Consider adding bash/zsh shell script examples for common extension management tasks to further support Linux users.
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 provides both Windows (PowerShell) and Linux (Bash) examples for acquiring access tokens using managed identity on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first, and the PowerShell script is more detailed, including error handling and output formatting. The Linux/Bash example is present and functional, but less detailed and is shown after the Windows example. The 'Related content' section mentions PowerShell before Azure CLI, which may reinforce Windows-first patterns.
Recommendations
- Present Windows and Linux examples side-by-side or alternate which is shown first to avoid Windows-first bias.
- Ensure parity in script detail and error handling between PowerShell and Bash examples.
- In 'Related content', list Azure CLI and PowerShell equally or alternate their order.
- Add clarifying notes that both Windows and Linux are fully supported and provide links to OS-specific tutorials where relevant.
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
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows instructions and notes are presented first and in greater detail. The Windows section includes additional troubleshooting guidance (e.g., avoiding PowerShell ISE), while the Linux section is more concise. The retry commands for failed deployments are also shown with Windows first. No Linux functionality is missing, but Windows is prioritized in ordering and depth.
Recommendations
- Present Windows and Linux instructions in parallel or in a more balanced order (e.g., side-by-side or alternating which comes first).
- Add any Linux-specific troubleshooting notes if relevant, similar to the PowerShell ISE warning for Windows.
- Ensure that both PowerShell and Bash script download instructions are equally detailed.
- Consider using generic language (e.g., 'On Windows, do X. On Linux, do Y.') instead of always starting with Windows.
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
Summary
The documentation provides a balanced overview of Azure Arc-enabled VMware vSphere, mentioning both Windows and Linux support in several places. However, there is a mild Windows bias: Windows-related features (such as Windows Server management, Extended Security Updates, and Windows registry/file monitoring) are mentioned more prominently and often before Linux equivalents. PowerShell is listed as a primary automation tool, with Linux alternatives (like Bash or shell scripting) not explicitly mentioned. Some links and examples default to Windows tabs or Windows-specific guidance, even when Linux is supported.
Recommendations
- Ensure Linux examples and tools (such as Bash, shell scripting, and Linux-specific agent installation) are presented alongside PowerShell and Windows examples.
- When listing supported automation tools, explicitly mention Bash/shell scripting for Linux users.
- Where links default to Windows tabs, add equivalent Linux tabs or links.
- In sections describing monitoring, configuration, and update management, clarify Linux support and provide Linux-specific guidance or links.
- When describing VM extensions or agent installation, include explicit instructions for Linux VMs.
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 examples, which is a minor 'windows_first' bias. No Windows-specific tools, patterns, or exclusive Windows instructions are present. All instructions are cross-platform via Azure CLI.
Recommendations
- Consider alternating the order of Bash and PowerShell examples or explicitly state that both are equally supported.
- Add a brief note at the start clarifying that all CLI instructions work on Linux, macOS, and Windows.
- Ensure screenshots and portal instructions are not Windows-centric (e.g., avoid referencing Windows-only UI elements).
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all steps, but the PowerShell tab is present and contains full examples, which may suggest a Windows bias. The Bash tab is shown first, but the PowerShell section is equally detailed, and no Linux-specific tools or patterns are discussed. There is no mention of Linux/macOS-specific issues, nor are there any Linux-only examples or troubleshooting tips. All commands use the Azure CLI, which is cross-platform, but the presence of PowerShell examples may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Clarify that PowerShell examples are for Windows users and Bash for Linux/macOS users.
- Add explicit notes about cross-platform compatibility of Azure CLI commands.
- Provide troubleshooting tips for Linux/macOS users if there are known issues.
- Consider adding a section about using the Azure CLI in macOS/Linux environments (e.g., installation, shell differences).
Azure Arc
Create a Solution with Multiple Dependencies with Workload Orchestration
...quickstart-solution-multiple-shared-adapter-dependency.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every CLI operation, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently present and sometimes shown immediately after Bash, which may create a slight Windows-first impression. There are no Windows-only tools or patterns, and all commands are cross-platform (Azure CLI and kubectl). No Linux/macOS examples are missing, and no Windows-specific tools are mentioned.
Recommendations
- Consider alternating the order of Bash and PowerShell examples, or default to Bash first for cross-platform CLI tutorials.
- Explicitly note that Azure CLI and kubectl commands work on Linux, macOS, and Windows, to reassure non-Windows users.
- If possible, add a brief section explaining how to install Azure CLI and kubectl on Linux/macOS for completeness.
- Ensure that any future additions do not introduce Windows-specific tools or patterns unless necessary.
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 PowerShell examples are always shown after Bash. There is no evidence of Windows-only tools or patterns, and all commands use the Azure CLI and Helm, which are cross-platform. However, the presence of PowerShell examples may suggest a slight Windows bias, as Linux/macOS users would not use PowerShell. No Linux-specific tools or patterns are missing, and the Bash examples are complete and functional.
Recommendations
- Consider making Bash the default or first example in each code tab, as Bash is more universal across Linux/macOS and Windows (via WSL).
- Clarify in the introduction that Bash is recommended for Linux/macOS users and PowerShell for Windows users.
- Ensure that any references to file paths or shell syntax are cross-platform (e.g., avoid Windows-style backslashes in Bash examples).
- If possible, provide a brief note on how to use Bash on Windows (e.g., via WSL or Git Bash) for users who may not have PowerShell.
- Explicitly state that all commands are cross-platform and that Azure CLI and Helm work on Linux, macOS, and Windows.
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 references SQL Server Management Studio (SSMS) as the primary GUI client, which is Windows-only, and mentions it before the cross-platform sqlcmd tool. However, it does provide a sqlcmd example that works on both Linux and Windows. There are no Linux-specific tools (such as Azure Data Studio or DBeaver) mentioned, and the instructions for connecting focus on SSMS and sqlcmd. The Azure CLI commands are cross-platform, but the overall tone and examples prioritize Windows tools and patterns.
Recommendations
- Mention cross-platform GUI tools such as Azure Data Studio or DBeaver alongside SSMS.
- Provide explicit Linux/macOS connection instructions, including any OS-specific considerations.
- Show examples for both Windows and Linux/macOS environments, especially for sqlcmd usage.
- Clarify that SSMS is Windows-only and recommend alternatives for non-Windows users.
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 Azure Arc-enabled servers, but Windows-specific tools and terminology (e.g., Windows Admin Center, Windows installation package) are mentioned first or more prominently. Windows endpoints and tools are often listed before their Linux equivalents, and Windows-specific notes are included in several sections. However, Linux is also covered, and critical information for Linux users is present.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, alternating order where possible.
- Where Windows-specific tools (e.g., Windows Admin Center) are mentioned, provide equivalent Linux management options or clarify if none exist.
- In tables and lists, avoid always listing Windows resources first; consider grouping by platform or alternating order.
- Add explicit Linux troubleshooting links or references, similar to the Windows TLS configuration issues link.
- Clarify any Windows-only requirements to avoid confusion for Linux users.
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 provides both Windows (PowerShell) and Linux (Bash) examples for acquiring access tokens using managed identity on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first, and the PowerShell script is more detailed and visually emphasized (with a screenshot). The Linux/Bash example follows, but is slightly less prominent. The prerequisites and instructions mention both OSes, and links to both Windows and Linux guides are provided. Overall, the bias is minor and does not prevent Linux/macOS users from completing the task.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side for parity.
- Ensure screenshots and visual aids are provided for both Windows and Linux examples.
- Explicitly mention that the instructions apply equally to both Windows and Linux, and highlight any OS-specific differences.
- Consider adding a brief summary table comparing Windows and Linux steps for quick reference.
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 (Linux/macOS) and PowerShell (Windows) examples for all major steps, ensuring parity for cross-platform users. However, in most sections, PowerShell examples are presented after Bash, which is a minor 'windows_first' bias. There are no Windows-only tools or patterns, and Linux/macOS users are not missing any critical information or examples.
Recommendations
- Continue to provide Bash and PowerShell examples side-by-side for all steps.
- Consider alternating the order of Bash and PowerShell tabs in some sections, or explicitly state that both platforms are equally supported.
- Ensure that any platform-specific notes (e.g., handling UTF-8 BOM, base64 encoding) are clear for both Bash and PowerShell users.
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides both Linux and Windows methods for base64 encoding, but the Linux example is presented first and is more concise. The Windows method relies on certutil and findstr, which are Windows-specific tools, and requires manual header removal. No PowerShell-specific examples are given, and all other steps (openssl, Azure CLI, kubectl) are cross-platform. The bias is minor, as Windows users are given explicit instructions, but Linux is treated as the default.
Recommendations
- Provide a PowerShell example for base64 encoding and header removal for Windows users, as PowerShell is more commonly used than certutil/findstr.
- Clarify that Azure CLI and kubectl commands are cross-platform and can be run on Windows, Linux, or macOS.
- Consider mentioning macOS explicitly alongside Linux where relevant.
- Add a note about using openssl on Windows, including installation guidance if needed.
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 operations. However, Azure PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI, and in some sections, PowerShell examples are presented before or alongside CLI examples. There are no explicit Linux/macOS-specific instructions or troubleshooting notes, and no Bash/shell script examples beyond Azure CLI. The use of PowerShell as a primary example may create friction for Linux/macOS users who may not have PowerShell installed or prefer native shell scripting.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and recommend it as the default for Linux/macOS users.
- Present Azure CLI examples before PowerShell examples in all sections.
- Add explicit notes or callouts for Linux/macOS users, e.g., confirming that all steps are supported on those platforms.
- Where environment variables are set, show both Bash (export) and PowerShell ($Env:) syntax side-by-side.
- Add troubleshooting tips for common Linux/macOS issues (e.g., permissions, proxy settings).
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
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but the PowerShell examples are given equal prominence to Azure CLI, and PowerShell-specific instructions (including environment variable setup) are included. There is minor Windows bias in the use of PowerShell as a primary scripting option alongside Azure CLI, and in the explicit mention of Windows as a Docker installation target before Linux/Mac in some lists. However, Linux-specific instructions and requirements are present, and the documentation is generally cross-platform.
Recommendations
- Consider clarifying that Azure PowerShell is available on Linux/macOS, or add Bash scripting equivalents where PowerShell is used for environment variable setup.
- When listing Docker installation options, consider mentioning Linux first, or listing all platforms equally (Linux, Mac, Windows) to avoid subtle Windows-first ordering.
- Explicitly note that Azure CLI and PowerShell are both cross-platform, and provide links to installation instructions for Linux/macOS where relevant.
- Where possible, provide Bash shell examples alongside PowerShell for tasks like setting environment variables, especially in proxy configuration sections.
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 for Azure Arc resource bridge system requirements exhibits minor Windows bias. While the Azure CLI is referenced as the primary management tool, links and instructions for installing Azure CLI are Windows-focused (e.g., linking to the Windows install page and specifying x64/32-bit requirements without mentioning Linux/macOS equivalents). There are no explicit Linux/macOS instructions or examples for management machine setup, CLI installation, or file paths, which may create friction for non-Windows users.
Recommendations
- Add explicit instructions and links for installing Azure CLI on Linux and macOS management machines.
- Clarify that the management machine can be Windows, Linux, or macOS, and provide parity in examples and requirements.
- Mention file path conventions for Linux/macOS when discussing configuration file storage.
- Ensure CLI commands and prerequisites are platform-agnostic or provide platform-specific guidance where necessary.
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 (CLI) examples for all major operations, but Windows/PowerShell examples are often presented before Linux/CLI. Some minor notes reference Windows-specific behaviors (e.g., setting --gateway-resource-id to null in PowerShell). The monitoring section gives both Windows and Linux log locations. There is a slight preference for Windows-first ordering and PowerShell usage, but Linux parity is generally maintained.
Recommendations
- Alternate the order of CLI and PowerShell examples so Linux users see their platform represented first in some sections.
- Explicitly state that all CLI commands are cross-platform and can be run on Linux, macOS, or Windows.
- Where possible, clarify any Windows-specific notes (such as setting --gateway-resource-id to null) and provide equivalent Linux guidance if needed.
- Consider adding a short section at the start confirming that all features and instructions apply equally to Linux and Windows servers unless otherwise noted.