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 1651-1675 of 2334 flagged pages
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 Windows bias. The 'Interactive browser login' is described as Windows-only and appears first in the authentication options section, while Linux is only mentioned as the default for device code login. Windows certificate store usage is described in detail, but Linux equivalents (such as PEM/PFX file usage) are not explained with equal depth. The access token example references a PowerShell cmdlet ('Get-AzAccessToken') without mentioning Linux alternatives. However, overall, the documentation is usable for Linux users, and most examples are cross-platform.
Recommendations
- Reorder authentication options so that cross-platform methods (device code, service principal, Azure CLI) appear before Windows-only options.
- Provide equivalent Linux tooling or commands for obtaining access tokens (e.g., using Azure CLI: 'az account get-access-token').
- Expand certificate authentication guidance for Linux, including file permissions and typical storage locations.
- Clarify that most examples are cross-platform and explicitly state which options are Windows-only.
- Where Windows certificate store is discussed, briefly mention Linux certificate handling for parity.
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
Powershell Heavy
Windows Tools
Summary
The documentation covers troubleshooting for both Windows and Linux, but there is a mild bias toward Windows. Windows examples and log file paths are presented first, and PowerShell syntax is used for Windows commands. Windows-specific tools and concepts (elevated command prompt, PowerShell version requirements, Windows environment variables) are mentioned before their Linux equivalents. However, Linux examples and paths are included and parity is generally maintained.
Recommendations
- Alternate the order of Windows and Linux examples so Linux is not always second.
- Provide both PowerShell and Bash syntax for commands where applicable.
- Explicitly mention Linux equivalents for Windows-specific instructions (e.g., 'elevated command prompt' vs. 'sudo').
- Ensure troubleshooting steps reference both Windows and Linux log file locations equally.
- Consider grouping Windows and Linux sections together or clarifying parity in introductory text.
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 in the 'Run the script' and 'Retry command' sections. There is a minor bias in ordering, but Linux parity is maintained throughout with equivalent instructions and tooling.
Recommendations
- Alternate the order of Windows and Linux instructions in sections, or present them side-by-side to avoid implicit prioritization.
- Explicitly mention macOS compatibility if the Bash script works on macOS, or clarify if it does not.
- Ensure screenshots and UI references are OS-neutral or provide Linux/macOS-specific guidance if needed.
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
Missing Linux Example
Summary
The documentation provides a generally cross-platform overview of Azure Arc-enabled VMware vSphere, but exhibits minor Windows bias. Windows/PowerShell are mentioned first or exclusively in several places (e.g., Azure Automation runbooks, Windows Server management, and AVS deployment tabs). Linux equivalents are referenced but not always with equal prominence or example depth. No critical sections are Windows-only, but Linux/macOS users may encounter friction due to Windows-first ordering and lack of explicit Linux-focused examples.
Recommendations
- Ensure that Linux examples and references are given equal prominence alongside Windows/PowerShell, especially in sections about automation and VM extensions.
- Where tabs or links are Windows-only (e.g., 'tabs=windows'), add Linux/macOS tabs or clarify parity.
- Expand references to Linux tools and workflows (e.g., Bash, Ansible, shell scripts) in automation and onboarding scenarios.
- Provide explicit Linux/macOS CLI examples where PowerShell is mentioned.
- Review quick start and deployment guides to ensure Linux onboarding is equally documented.
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for each command, but consistently presents Bash examples before PowerShell. There are no Windows-specific tools or patterns, and all commands use the Azure CLI, which is cross-platform. No Linux/macOS examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Continue to provide both Bash and PowerShell examples for parity.
- Consider clarifying that Azure CLI commands work identically on Linux, macOS, and Windows.
- Optionally, add a note at the top stating that Bash examples are suitable for Linux/macOS terminals, and PowerShell for Windows (or cross-platform PowerShell).
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, in some sections, PowerShell examples are presented immediately after Bash, and in a few places, minor copy-paste errors favor Windows variable syntax. There are no Windows-only tools or patterns, and all instructions are cross-platform via Azure CLI. No Linux examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Ensure Bash and PowerShell examples are equally prominent, possibly by alternating their order or using tabs to avoid implicit Windows-first bias.
- Correct minor copy-paste errors in PowerShell examples (e.g., variable assignment syntax) to improve clarity for Windows users.
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows to reinforce cross-platform support.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all commands, but the Bash tab is presented first. There is no evidence of Windows-only tools, Windows-specific patterns, or missing Linux examples. All commands use the Azure CLI, which is cross-platform, and variable definitions are shown for both Bash and PowerShell. No Windows tools or PowerShell-heavy bias is present.
Recommendations
- Continue to provide both Bash and PowerShell examples for parity.
- Consider alternating the order of Bash and PowerShell tabs or explicitly stating that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Ensure that any referenced scripts or files (such as onboarding scripts) are compatible with both Bash and PowerShell environments.
- If possible, clarify in the prerequisites that both Linux/macOS and Windows environments are supported.
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
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell examples are consistently shown immediately after Bash, and the PowerShell syntax is given equal prominence. There is no evidence of Windows-only tools or patterns being prioritized, nor are Linux examples missing. However, the PowerShell examples are sometimes slightly more detailed (e.g., variable assignment), and the structure may subtly imply parity between Windows and Linux, but Bash is always shown first. No Windows-specific tools or patterns are mentioned, and all commands are cross-platform (Azure CLI, kubectl).
Recommendations
- Ensure Bash examples are always shown first, as currently done.
- Consider adding a note clarifying that Azure CLI and kubectl commands are fully cross-platform and can be run on Linux, macOS, and Windows.
- If possible, highlight that PowerShell examples are for Windows users, but Bash is the default for Linux/macOS.
- Review variable assignment sections to ensure Bash and PowerShell examples are equally detailed.
- If the audience is primarily Linux/macOS, consider making Bash the default and PowerShell optional.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Summary
The documentation is generally cross-platform, focusing on Azure CLI and portal usage, which are available on both Windows and Linux/macOS. However, in the May 2025 release section, the CLI examples are shown using PowerShell syntax (with backticks for line continuation and variables with $), which is Windows-centric and may confuse Linux/macOS users who use Bash or other shells.
Recommendations
- Provide CLI examples in both PowerShell and Bash syntax, or use Bash syntax as the default since it is more universally compatible.
- Add a note clarifying that CLI commands work in any shell, and provide guidance on adapting line continuations and variable syntax for different platforms.
- Where possible, avoid using shell-specific syntax (like backticks or $-prefixed variables) in CLI documentation unless the documentation is specifically for that shell.
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. There is no evidence of Windows-only tools or patterns, and all commands use cross-platform Azure CLI and Helm. However, the presence of PowerShell examples throughout may suggest a slight Windows bias, especially since PowerShell is primarily used on Windows, though it is available cross-platform.
Recommendations
- Clarify that PowerShell examples are also valid for PowerShell Core on Linux/macOS.
- Consider adding a note that Bash and PowerShell examples are functionally equivalent and both supported on all platforms.
- Ensure that any platform-specific nuances (such as file path syntax or environment variable usage) are documented for both Bash and PowerShell.
- If possible, provide a brief summary at the top indicating that all steps are cross-platform and do not require Windows.
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-exclusive tools or patterns, and all commands use cross-platform Azure CLI and Helm. No Linux/macOS examples are missing, and no Windows-specific tools are mentioned. The only minor bias is that Bash (Linux/macOS) examples are always shown first, followed by PowerShell (Windows).
Recommendations
- Maintain the current parity between Bash and PowerShell examples.
- Consider clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, especially for new users.
- Optionally, alternate the order of Bash and PowerShell tabs in different sections to avoid implicit prioritization.
- Ensure that any future additions continue to provide both Bash and PowerShell examples.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides installation instructions for client tools across platforms, but Windows links are often listed first and Windows-specific notes (e.g., cmd.exe vs PowerShell, PowerShell's curl alias) are emphasized. Linux installation instructions are less explicit (e.g., 'install curl package' without a link), and Linux/macOS are sometimes mentioned after Windows. There is a minor bias toward Windows in ordering and detail.
Recommendations
- List Linux/macOS installation links before or alongside Windows, rather than after.
- Provide explicit Linux/macOS installation instructions or links for all tools (e.g., link to curl installation for Linux/macOS, not just 'install curl package').
- Balance Windows-specific notes (e.g., PowerShell quirks) with equivalent Linux/macOS notes where relevant.
- Ensure all examples and instructions are equally detailed for Linux/macOS users.
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, but in several sections Windows is presented first (e.g., log file paths, command examples), and Windows-specific tools and patterns (such as PowerShell syntax and environment variables) are referenced. Linux parity is generally maintained, but Windows examples and terminology are often prioritized or shown before Linux equivalents.
Recommendations
- Present Windows and Linux examples side-by-side or alternate their order to avoid Windows-first bias.
- Ensure Linux log file paths and troubleshooting steps are as prominent as Windows paths.
- Where Windows-specific tools (e.g., PowerShell, environment variables) are mentioned, provide equivalent Linux commands and environment variable usage.
- Clarify that both Windows and Linux are equally supported, and avoid defaulting to Windows terminology when describing generic steps.
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 on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first, with more detailed scripting and output imagery. PowerShell is referenced as the primary tool for Windows, while Bash is used for Linux. The prerequisites and links are balanced, but Windows is subtly prioritized in ordering and detail.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side for parity.
- Ensure output examples and screenshots are equally detailed for both platforms.
- Explicitly mention cross-platform tools (e.g., Azure CLI) in the main workflow, not just in 'Related content'.
- Clarify that both Windows and Linux are fully supported and provide links to platform-specific troubleshooting.
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 in the 'Run the script' and 'Retry command' sections. There is a minor bias in ordering, but Linux parity is maintained throughout with equivalent instructions and tools.
Recommendations
- Present Windows and Linux instructions in parallel or alternate their order in sections to avoid implicit prioritization.
- Explicitly state that both Windows and Linux are fully supported at the beginning of relevant sections.
- Consider grouping OS-specific instructions in tabs or collapsible sections for equal visibility.
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 consistently presents Bash examples first, followed by PowerShell. There are no Windows-specific tools or patterns used; all commands rely on the Azure CLI and Helm, which are cross-platform. No critical steps are Windows-only, and Linux/macOS users can complete all tasks without friction.
Recommendations
- Continue to provide both Bash and PowerShell examples for parity.
- Consider alternating the order of Bash and PowerShell tabs in future documentation to avoid subtle 'windows_first' bias.
- Explicitly state that all commands are cross-platform and supported on Linux, macOS, and Windows.
- Add a brief note clarifying that Helm and Azure CLI are available on all major OS platforms.
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 and a Linux-compatible command is provided, SSMS is listed first and no Linux-native GUI tools (such as Azure Data Studio or DBeaver) are referenced. The documentation does not provide parity in GUI client recommendations for Linux/macOS users, but does include a command-line example usable on both platforms.
Recommendations
- Mention cross-platform SQL client tools such as Azure Data Studio, DBeaver, or Squirrel SQL alongside SSMS.
- Provide explicit Linux/macOS connection instructions and examples, including screenshots or steps for using Azure Data Studio.
- Clarify that sqlcmd is available on Linux/macOS and provide installation instructions or links.
- Avoid listing Windows-only tools first unless the feature is Windows-specific.
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, but PowerShell is consistently presented as the only alternative to CLI, with no mention of Bash, shell scripting, or Linux-native tools. In some sections, PowerShell examples are shown before or alongside CLI, and environment variable examples for PowerShell are given for proxy configuration. There are no Linux-specific instructions or troubleshooting tips, and the documentation assumes users are familiar with PowerShell if not using CLI.
Recommendations
- Add explicit Bash/shell scripting examples for Linux/macOS users, especially for environment variable configuration and command-line usage.
- Clarify that Azure CLI commands work cross-platform and can be run in Bash, zsh, or other shells on Linux/macOS.
- Where PowerShell is referenced, note that PowerShell Core is available cross-platform, or provide equivalent Bash commands.
- Include troubleshooting tips or notes relevant to Linux environments (e.g., proxy configuration nuances, file permissions).
- When listing tabs for command examples, consider ordering CLI (Bash) first, then PowerShell, to reflect cross-platform parity.
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 Example
Linux First
Summary
The documentation provides both Linux and Windows methods for base64 encoding files, with Linux (base64) presented first and Windows (certutil) as an alternative. The Windows example includes extra steps (removing headers) and references Windows-specific utilities. All other examples (openssl, Azure CLI, kubectl) are cross-platform or Linux-centric. No PowerShell-specific commands or Windows-first ordering is present outside the base64 encoding section.
Recommendations
- Clarify that certutil is available on Windows and provide a PowerShell-native alternative (e.g., [Convert]::ToBase64String) for users who prefer PowerShell.
- Explicitly state that openssl, Azure CLI, and kubectl commands are cross-platform and provide links or notes on installation for Windows users.
- Consider providing a macOS-specific note if there are any differences in certificate handling or base64 encoding.
- Ensure parity in example output and instructions for both Linux and Windows users, especially regarding file manipulation (e.g., header removal).
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 provides network requirements for Azure Arc Resource Bridge, listing both outbound and inbound connectivity. There is minor evidence of Windows bias: Windows NTP server ('time.windows.com') is mentioned as the default for Hyper-V, and several URLs/services reference 'windows.net' or 'windows.com'. However, Linux-specific requirements are also included (e.g., 'packages.microsoft.com' for Linux package downloads, SSH connectivity, and container registries). Windows tools and endpoints are mentioned, but Linux equivalents are not omitted; the page is generally cross-platform, with only minor Windows-first ordering and terminology.
Recommendations
- Clarify that NTP can use Linux/Unix NTP servers as well, and provide examples or mention alternatives.
- When referencing Windows-specific endpoints (e.g., 'time.windows.com'), note that Linux deployments may use other NTP sources.
- Ensure that any instructions or examples for configuring network settings reference both Windows and Linux methods/tools.
- Consider ordering examples and endpoint lists in a neutral way, or explicitly state cross-platform applicability.
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 a link that defaults to the Windows installation page and mentions Azure CLI x64/32-bit requirements, but does not specify Linux/macOS requirements or provide parity in installation instructions or examples. There are no explicit PowerShell or Windows-only tool references, but the management machine requirements and CLI installation links are Windows-centric.
Recommendations
- Add explicit guidance for installing Azure CLI on Linux and macOS, including links to the relevant installation pages.
- Clarify that the management machine can be Linux, macOS, or Windows, and provide any OS-specific requirements or caveats.
- Provide example commands or configuration file locations for Linux/macOS environments, not just Windows.
- Ensure all CLI commands are shown in a cross-platform way, avoiding assumptions about the user's OS.
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
Summary
The documentation provides both Windows and Linux examples for critical configuration tasks, but Windows/PowerShell examples are consistently presented first and sometimes described in more detail. The section on listing installed extensions mentions the Azure portal, Azure PowerShell, and Azure CLI, but lists PowerShell before CLI. Example commands for Windows use PowerShell, while Linux uses Bash, but the Windows instructions are often more prominent. No Linux tools or patterns are omitted, and Linux parity is generally maintained.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid 'windows_first' bias.
- Ensure equal detail and prominence in Linux example explanations.
- List Azure CLI before PowerShell when both are equally supported, as CLI is cross-platform.
- Consider adding explicit macOS notes if relevant, since macOS users may follow Linux instructions.
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 for `azcmagent connect` is largely cross-platform, but there are minor signs of Windows bias. The authentication options section presents Windows-specific interactive browser login first and references Windows certificate stores for certificate-based authentication. The access token example mentions the Windows PowerShell cmdlet `Get-AzAccessToken` without listing a Linux/macOS equivalent. However, Linux authentication methods (device code, Azure CLI) are well documented, and most examples are generic and applicable to all platforms.
Recommendations
- Present authentication options in a platform-neutral order or explicitly state cross-platform applicability.
- When referencing Windows-specific tools (e.g., PowerShell cmdlets), also mention Linux/macOS equivalents (such as Azure CLI commands or REST API methods for obtaining access tokens).
- Clarify certificate storage options for Linux/macOS users alongside Windows certificate store instructions.
- Add explicit Linux/macOS example commands where Windows-specific instructions are given (e.g., for access token retrieval).
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
Powershell Heavy
Summary
The documentation generally maintains parity between Windows and Linux, but there are subtle signs of Windows bias. Windows-related tools and endpoints (e.g., Windows Admin Center, download.microsoft.com) are mentioned first or more prominently. Windows-specific configuration issues and cipher suite requirements are discussed in detail, while Linux information is more generic and less actionable. Windows examples, tools, and terminology tend to appear before Linux equivalents, and troubleshooting links are Windows-focused.
Recommendations
- Where possible, provide Linux-specific troubleshooting links and configuration guidance (e.g., OpenSSL settings, Linux firewall/proxy configuration examples).
- Ensure Linux endpoints and tools are mentioned with equal prominence and detail as Windows ones.
- When listing URLs or resources, alternate the order or group by platform to avoid always placing Windows first.
- Expand Linux-specific sections to include actionable steps, not just generic references.
- Add examples for Linux agent installation, proxy configuration, and TLS/cipher suite setup, similar to the Windows guidance.
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 are subtle signs of Windows bias: Windows-related features (such as Windows Server management and Extended Security Updates) are highlighted first and more frequently, and PowerShell is mentioned before other automation tools. Some links and examples use Windows as the default tab or context, and Windows-specific features are referenced before Linux equivalents. No critical Linux functionality is missing, but Windows is presented as the primary platform in several sections.
Recommendations
- Ensure Linux examples and references are given equal prominence alongside Windows, especially in links and feature descriptions.
- When listing automation tools (CLI, PowerShell, SDKs), alternate the order or explicitly mention Bash/CLI for Linux users.
- Where links default to Windows tabs or contexts, add Linux tabs or clarify Linux support.
- Highlight Linux-specific benefits and scenarios with equal detail as Windows.
- Add explicit Linux onboarding and management examples where possible.