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 1576-1600 of 2334 flagged pages
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, PowerShell examples are consistently shown after Bash, which could be considered a minor 'windows_first' bias, but no critical Windows-only tools or patterns are used. All commands rely on cross-platform Azure CLI and Helm tools.
Recommendations
- Maintain the current parity by continuing to provide both Bash and PowerShell examples.
- Consider alternating the order of Bash and PowerShell tabs in future documentation to avoid perceived bias.
- Explicitly mention that all commands are cross-platform and can be run on Linux, macOS, or Windows.
Create Pull Request
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
Summary
The documentation provides both Bash and PowerShell examples for every step, 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-only tools or patterns are used, and all commands are cross-platform (az CLI, Helm). There are no missing Linux examples, and no exclusive mention of Windows tools.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in some sections, or clarify that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Explicitly state that Bash commands can be run on Linux/macOS terminals and PowerShell commands on Windows, for user clarity.
- Ensure that any future additions (e.g., troubleshooting, environment setup) also provide cross-platform instructions.
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 every major step, ensuring Linux/macOS and Windows users are supported. However, PowerShell examples are consistently presented after Bash examples, indicating a minor 'windows_first' bias in ordering. There are no Windows-only tools or patterns, and Linux examples are not missing.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in some sections, or explicitly state that Bash is for Linux/macOS and PowerShell for Windows to reinforce parity.
- Ensure that any OS-specific nuances (such as file encoding or base64 commands) are clearly explained for both platforms, as is done here.
- Maintain the current approach of providing both Bash and PowerShell examples for all commands.
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
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 shown immediately after Bash examples, rather than exclusively or before Bash. There are no Windows-specific tools or patterns used, and all commands are cross-platform (Azure CLI, kubectl). No Linux/macOS examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Maintain the current structure, as Bash and PowerShell parity is achieved.
- Consider alternating the order of Bash and PowerShell tabs in future documentation to avoid minor 'windows_first' bias.
- Explicitly note that Azure CLI and kubectl commands are cross-platform and can be used on Linux, macOS, and Windows.
- If possible, add a brief note for macOS users regarding any prerequisites (e.g., installing Azure CLI, kubectl) to further improve inclusivity.
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 commands, ensuring parity between Linux/macOS and Windows users. However, in several sections, PowerShell examples are presented immediately after Bash, which is a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used, and Linux/macOS users can complete all tasks without friction.
Recommendations
- Continue to provide both Bash and PowerShell examples for CLI commands.
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is for Linux/macOS and PowerShell for Windows, to reinforce cross-platform support.
- Ensure screenshots and portal instructions are not Windows-specific (they are not in this page).
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides SQL connectivity examples using PowerShell syntax (e.g., kubectl exec ... -- /opt/mssql-tools/bin/sqlcmd) and labels them as 'powershell', which may confuse Linux/macOS users. There are no explicit Linux/macOS shell examples, and PowerShell is used as the default for command snippets. However, most commands are cross-platform (kubectl, yaml, sqlcmd), but the labeling and example order suggest a Windows-first bias.
Recommendations
- Replace 'powershell' code block labels with 'console' or 'bash' where appropriate, especially for kubectl and sqlcmd commands that are cross-platform.
- Add explicit Linux/macOS shell examples or clarify that the commands work on all platforms.
- Ensure that instructions for decoding base64 secrets mention common Linux/macOS tools (e.g., 'base64 -d') alongside any Windows-specific guidance.
- Avoid labeling cross-platform commands as 'powershell' unless there is actual PowerShell-specific syntax.
- Consider showing Linux/macOS examples first or in parallel with Windows examples.
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 for both Linux and Windows, and does not exclusively use Windows tools or patterns. The bias is minor, mainly in the ordering and emphasis of Windows tools.
Recommendations
- Mention cross-platform tools (such as Azure Data Studio) alongside SSMS, and list them first or equally.
- Provide explicit examples for connecting from macOS and Linux, including GUI options.
- Clarify that sqlcmd is available on Linux/macOS and provide installation instructions or links.
- Consider adding a note about Azure Data Studio as a cross-platform alternative to SSMS.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides installation links for client tools across Windows, Linux, and macOS, but Windows links are often listed first. There are Windows-specific notes (e.g., using cmd.exe instead of PowerShell for curl), and Linux installation instructions for curl are less explicit than Windows. There is also a PowerShell-specific note about curl aliasing, but no equivalent Linux/macOS shell notes.
Recommendations
- List installation links for all platforms in parallel order (e.g., Windows, Linux, macOS) or rotate the order to avoid Windows-first bias.
- Provide explicit Linux/macOS installation instructions for curl (e.g., 'sudo apt install curl' for Ubuntu) rather than just 'install curl package'.
- Add shell-specific notes for Linux/macOS where relevant, similar to the PowerShell note for curl.
- Ensure examples and notes reference all major platforms equally, not just Windows-specific behaviors.
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 files, but the Windows-specific certutil tool is mentioned after the Linux base64 command. The Windows example includes additional steps for removing headers, which are not discussed for Linux. All other instructions and examples use cross-platform tools (OpenSSL, Azure CLI, kubectl) and are not Windows-specific.
Recommendations
- Explicitly mention macOS compatibility for base64 and OpenSSL commands.
- Provide equivalent Linux/macOS commands for removing certificate headers (e.g., using grep or sed), as done for Windows with findstr.
- Clarify that Azure CLI and kubectl commands are cross-platform and can be run on Windows, Linux, or macOS.
- Consider showing Linux/macOS and Windows commands side-by-side for encoding and header removal, rather than listing Windows separately.
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
Powershell Heavy
Summary
The documentation is largely cross-platform, focusing on Azure CLI and kubectl commands, which are available on Windows, Linux, and macOS. However, there is a minor bias in the ordering of installation instructions for Azure kubelogin, where Windows and Mac are mentioned first, and Linux instructions are provided separately. There are no PowerShell-specific examples, but Azure CLI is used throughout, which is cross-platform. No Windows-only tools or patterns are mentioned, and Linux/macOS users can complete all tasks described.
Recommendations
- Present installation instructions for Azure kubelogin for Linux, macOS, and Windows in parallel or in a single section, rather than listing Windows/Mac first.
- Explicitly state that all Azure CLI and kubectl commands are cross-platform and provide links to installation instructions for Linux/macOS where relevant.
- Where possible, add notes or links for Linux/macOS users about any OS-specific nuances (e.g., file paths, SSH access).
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 PowerShell examples are consistently presented alongside CLI, sometimes with more detail. Azure PowerShell is a Windows-centric tool, and its inclusion may suggest a Windows bias, especially since Linux-native tools (like Bash scripts or shell commands) are not referenced. However, Azure CLI is cross-platform and the examples use standard environment variables for proxy configuration, which are compatible with Linux/macOS. There are no Windows-only tools or instructions, and the documentation does not prioritize Windows tools over Linux equivalents, but PowerShell is always present.
Recommendations
- Explicitly note that Azure CLI commands work on Linux, macOS, and Windows.
- Add clarifying statements that Azure PowerShell is primarily for Windows, while Azure CLI is cross-platform.
- Consider including Bash script examples or referencing Linux/macOS shell environments where relevant.
- Ensure that environment variable examples use syntax for both Windows (PowerShell) and Linux/macOS (Bash).
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 32-bit and 64-bit requirements without clarifying Linux/macOS support. However, it does not provide Windows-only commands or tools, nor does it exclude Linux/macOS users from completing the tasks. The CLI commands shown are cross-platform, but the management machine requirements and CLI installation links could be clearer about Linux/macOS compatibility.
Recommendations
- Add explicit mention that Azure CLI is supported on Linux and macOS, and provide installation links for those platforms.
- Clarify whether 32-bit/64-bit requirements apply to Linux/macOS or are Windows-specific.
- Include a note that the az arcappliance extension and commands are cross-platform unless there are known limitations.
- If possible, provide example CLI installation commands for Linux/macOS alongside Windows.
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 parity between Windows and Linux for most Azure Arc gateway operations, including CLI and PowerShell examples, and explicitly mentions Linux-specific endpoints. However, Windows/PowerShell examples are sometimes presented before Linux equivalents, and there are minor references to Windows tools (e.g., PowerShell, Windows Admin Center) before Linux tools. The documentation does not omit Linux instructions, but the ordering and emphasis slightly favor Windows.
Recommendations
- Ensure that CLI examples are presented before PowerShell examples, or provide both simultaneously, to avoid Windows-first ordering.
- Where possible, clarify that CLI commands work on both Windows and Linux, and explicitly state OS-agnostic instructions.
- When referencing tools like Windows Admin Center, also mention comparable Linux management tools or clarify if none exist.
- Review ordering in tabbed sections to ensure Linux/CLI is not always secondary to Windows/PowerShell.
- Continue to highlight Linux-specific endpoints and installation requirements, as done with 'packages.microsoft.com'.
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, but there is a notable Windows bias: Windows NTP server (time.windows.com) is mentioned specifically, and several endpoints (e.g., login.windows.net, sts.windows.net, servicebus.windows.net) use 'windows' in their domain names. The Windows NTP server is described as the default for Hyper-V, but no Linux NTP server example is provided. Additionally, Windows-related endpoints are listed before Linux-specific ones (e.g., Microsoft open source packages manager for Linux appears later in the table). There are no PowerShell-only examples or instructions, but the ordering and endpoint naming favor Windows.
Recommendations
- Add Linux NTP server examples (e.g., ntp.ubuntu.com or pool.ntp.org) alongside time.windows.com, clarifying when each is used.
- Explicitly mention that appliance VMs and management machines can be Linux-based, and provide guidance for Linux environments where relevant.
- Reorder the endpoint tables to avoid listing Windows-specific endpoints first unless required by the deployment sequence.
- Where endpoints are Windows-branded but required for all platforms, clarify their cross-platform relevance.
- Add notes for Linux users about any differences in network configuration or required tools.
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 covers both Linux and Windows platforms for the Azure Connected Machine agent, but there is a mild Windows bias. Windows tools and terminology (e.g., Windows Admin Center, Windows installation package) are mentioned before Linux equivalents in several places. Windows-specific resources and features (such as Windows Admin Center and Windows Server benefits) are referenced more frequently and often appear first in lists and tables. However, Linux is also addressed, and Linux-specific URLs and OpenSSL are mentioned, so Linux users can complete the task without significant friction.
Recommendations
- Present Linux and Windows examples/resources in parallel or alternate their order to avoid Windows-first bias.
- Add explicit Linux configuration guidance or troubleshooting links where Windows-specific troubleshooting is provided (e.g., for TLS issues).
- Clarify when features/tools are Windows-only to avoid confusion for Linux users.
- Where Windows Admin Center is referenced, provide Linux alternatives or note that it is Windows-specific.
- Ensure parity in documentation for proxy configuration, firewall rules, and cryptographic protocol guidance for both platforms.
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 Azure Arc-enabled servers, and provides parity in most sections. However, there is a mild Windows bias: PowerShell examples are given equal prominence to Azure CLI, and PowerShell is a Windows-centric tool. In some sections, Windows is mentioned first (e.g., 'Windows and Linux'), and PowerShell is presented alongside CLI, but not with Linux-native tools. The CLI examples are cross-platform, but Linux-specific shell examples (bash, zsh) are not shown explicitly.
Recommendations
- Explicitly state that Azure CLI commands work in Linux shells (bash, zsh) and provide sample commands in those contexts.
- Consider providing sample scripts or command sequences for common Linux shell environments (e.g., bash) to demonstrate parity.
- Where PowerShell is referenced, clarify its availability on Linux (PowerShell Core), or provide links to Linux installation instructions.
- When listing supported tools, avoid always mentioning Windows first; alternate or use 'Linux and Windows' where appropriate.
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 clear parity between Windows and Linux VM extensions, including separate tables for each OS and links to relevant resources. However, Windows extensions are listed first, which may subtly signal Windows as the primary platform. All deployment methods (CLI, PowerShell, portal, templates) are mentioned equally, and partner extensions are shown for both OSes. No critical Linux examples or tools are missing.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or explicitly state that both are equally supported.
- Add a brief introductory statement clarifying that all extension management methods and most extensions are available for both Windows and Linux, to reinforce parity.
- Ensure that CLI and PowerShell guides referenced in the 'Related content' section provide Linux-specific examples where appropriate.
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 with 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 is present and functional, but is shown after the Windows example. References to Azure CLI are only in the 'Related content' section, and the main workflow focuses on PowerShell for Windows.
Recommendations
- Present Windows and Linux examples side-by-side or alternate their order to avoid implicit prioritization.
- Ensure equal detail and visual emphasis (screenshots, explanations) for both Windows and Linux examples.
- Mention Azure CLI as a cross-platform tool for relevant tasks in the main workflow, not just in 'Related content'.
- Clarify that both Windows and Linux are fully supported throughout the article, especially in introductory sections.
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 locations. However, in the 'Agent verbose log' section, Windows examples are presented first and use PowerShell syntax, while Linux examples follow. There is a minor bias in presenting Windows tools and paths (e.g., `%ProgramData%`, PowerShell commands) before Linux equivalents, but Linux parity is maintained throughout with equivalent examples and instructions.
Recommendations
- Present Windows and Linux examples side-by-side or alternate their order to avoid Windows-first bias.
- Explicitly mention Linux log file locations and commands before or alongside Windows equivalents.
- Where possible, provide cross-platform command syntax in a unified table or section.
- Ensure troubleshooting steps reference both Windows and Linux paths/tools equally.
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, PowerShell examples are consistently shown after Bash examples, indicating a minor 'windows_first' bias in ordering. No Windows-specific tools or patterns are used, and all commands are cross-platform (az CLI, Helm).
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in different sections, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows.
- Add a brief note clarifying that az CLI and Helm commands are fully supported on Linux/macOS and Windows.
- Ensure that any future examples or troubleshooting steps include both Bash and PowerShell variants.
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 before Linux equivalents in several sections. The retry command for Windows is shown first, and the Windows-specific PowerShell execution policy step is detailed, while Linux instructions are more concise. However, Linux parity is generally maintained, with clear Bash instructions and references.
Recommendations
- Present Windows and Linux instructions in parallel or in a tabbed format to avoid implicit prioritization.
- Ensure that Linux-specific troubleshooting or preparatory steps (e.g., script permissions, required packages) are as detailed as Windows steps.
- Consider listing Linux instructions before Windows in some sections, or alternating order to demonstrate equal support.
- Add explicit confirmation that both PowerShell and Bash scripts are functionally equivalent and supported.
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 minor instances of Windows bias: PowerShell is listed before other automation tools in the SDKs/tools section, and some links (such as Azure Automation and AVS onboarding) default to Windows examples or tabs. Windows-specific features are referenced, but these are appropriate given Azure's hybrid focus and the nature of VMware environments.
Recommendations
- Ensure Linux CLI and Bash examples are provided alongside PowerShell in automation sections.
- Where links default to Windows tabs, add explicit references or links to Linux/macOS instructions.
- When listing tools (CLI, PowerShell, SDKs), alternate order or clarify cross-platform support.
- Highlight Linux support in onboarding and management scenarios, especially in quick start guides.
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, but consistently presents Bash examples first. However, the PowerShell examples are equally comprehensive and not prioritized over Bash. There is no evidence of Windows-only tools or patterns, and the Azure CLI commands are cross-platform. The documentation does not mention Linux-specific tools or workflows, but Linux users can follow all instructions without friction.
Recommendations
- Explicitly state that all commands are cross-platform and can be run on Linux, macOS, and Windows.
- Consider adding a brief note clarifying that Bash examples are suitable for Linux/macOS terminals, while PowerShell is for Windows or PowerShell Core on other platforms.
- If possible, provide a short section on running Azure CLI commands in Linux/macOS environments (e.g., installation, shell compatibility).
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; all commands use the Azure CLI and Helm, which are cross-platform. No Windows-specific tools or terminology are used, and Linux/macOS users can follow the Bash instructions without issue. However, the presence of PowerShell examples throughout may suggest a slight Windows bias, as PowerShell is primarily used on Windows, though it is available cross-platform.
Recommendations
- Consider clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, or for users who prefer PowerShell.
- If possible, add a note at the top explaining that both Bash and PowerShell are supported on all platforms, but Bash is the default for Linux/macOS.
- Ensure that Bash instructions are complete and do not reference Windows-only concepts.
- If usage statistics show most users are on Linux/macOS, consider showing Bash examples first and PowerShell examples as optional.
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-only tools or patterns used, and all commands are based on cross-platform Azure CLI and Helm. No Windows-specific tools or behaviors are mentioned. Linux parity is strong, but Bash examples are always shown first, which is a minor bias.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in different sections to avoid always showing Bash first.
- Explicitly state that all commands are cross-platform and can be run on Linux, macOS, or Windows.
- Add a note clarifying that PowerShell examples are for Windows or PowerShell Core users, while Bash is for Linux/macOS or Windows users with WSL.