Scan Details - Linux-first Docs for Azure

1443

Pages Scanned

48

Pages Flagged

1443

Changed Pages

3.3%

% Pages Flagged

Scan Information

Started At: 2025-08-01 00:00:07

Finished At: 2025-08-01 00:30:23

Status: completed

Target URL: https://github.com/MicrosoftDocs/azure-docs/tree/main/articles

Current Phase: discovery

Problematic Pages

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for command-line operations, with no mention of Azure CLI (which is cross-platform and more commonly used on Linux/macOS). All scripting and automation examples use PowerShell cmdlets, and there are no Bash, shell, or Linux-native instructions. The installation instructions and links are PowerShell-specific, and there is no guidance for users on Linux or macOS platforms. This prioritizes Windows tooling and patterns, potentially excluding or confusing Linux users.

Recommendations:

Add equivalent Azure CLI (az) examples for all PowerShell command snippets, including resource creation, identity assignment, and updates.
Include installation and authentication instructions for Azure CLI, with links to cross-platform documentation.
Explicitly mention that Azure CLI is supported on Linux/macOS and provide Bash/shell script examples where appropriate.
Where PowerShell is referenced, clarify that it is available cross-platform, but also provide native Bash/CLI alternatives.
Review and update screenshots or UI references to ensure they are not Windows-specific, or add notes for Linux/macOS users if UI differences exist.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Visual Studio Code (VS Code) and GitHub Copilot for testing and interacting with the MCP server, without mentioning or providing examples for Linux-native tools or command-line alternatives. The workflow assumes use of the Azure Portal (web-based, but often associated with Windows environments) and does not provide any Linux shell, curl, or cross-platform CLI examples for interacting with the MCP server. There are no PowerShell-specific commands, but the focus on VS Code and lack of Linux/CLI parity is notable.

Recommendations:

Add examples using cross-platform command-line tools such as curl, httpie, or wget to demonstrate how to interact with the MCP server from Linux or macOS terminals.
Explicitly mention that VS Code is available on Linux and macOS, or provide alternative editors or tools commonly used on those platforms.
Include a section or callout showing how to configure and test the MCP server using the Azure CLI or REST API directly, rather than only through the Azure Portal and VS Code.
Provide sample requests and authentication headers in a format that can be used in bash scripts or Linux shell environments.
If possible, include screenshots or walkthroughs from Linux desktop environments to reinforce cross-platform support.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for finding outbound IP addresses, but the PowerShell examples are given equal prominence to CLI, and there is no explicit mention of Linux-specific tools or workflows. The only non-Azure tool example is 'nslookup', which is cross-platform, but there are no Linux shell or scripting examples (e.g., Bash, grep, jq). Additionally, outbound IPv6 support is noted as being available only for Windows apps, with no Linux parity. The documentation does not mention Linux-specific considerations or provide Linux-first examples.

Recommendations:

Provide Linux/Bash-native examples alongside or before PowerShell, such as using jq with az CLI output.
Clarify that Azure CLI commands work cross-platform and highlight usage in Bash or other Linux shells.
Explicitly mention the lack of outbound IPv6 support for Linux apps and provide a roadmap or workaround if possible.
Include Linux-specific troubleshooting or verification steps (e.g., using dig, curl, or ip commands).
Where PowerShell is shown, add equivalent Bash or shell scripting examples to ensure Linux users are equally supported.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell scripts and cmdlets for migration and preview registration tasks, without providing equivalent Bash or Linux-native Azure CLI examples. The use of 'Set-AzContext', 'Get-AzProviderFeature', and 'Register-AzProviderFeature' in code blocks is PowerShell-specific, and the only tutorial linked is for PowerShell. There is no mention of Linux or Bash alternatives, and the documentation does not provide parity for users on non-Windows platforms.

Recommendations:

Provide Azure CLI (bash/shell) examples alongside PowerShell commands for all operations, especially for preview registration and migration tasks.
Explicitly mention that all features and management tasks are available cross-platform, and clarify any exceptions.
Include links to tutorials and guides that use Azure CLI in Bash or Cloud Shell, not just PowerShell.
When referencing scripts or tools, note their platform compatibility and provide alternatives where possible.
Balance references to Azure PowerShell and Azure CLI in both prose and code samples to ensure Linux and macOS users are equally supported.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing PowerShell in the automation section and not providing Linux-specific or cross-platform CLI examples inline. The automation section lists Azure CLI and PowerShell, but only the PowerShell script is directly embedded, with no equivalent Bash or Linux shell example. There are no explicit Linux or macOS workflow instructions, and the documentation does not mention Linux tools or provide parity in example scripts.

Recommendations:

Include inline Azure CLI (cross-platform) script examples alongside or before PowerShell examples in the 'Automate with scripts' section.
Provide explicit instructions or notes for Linux/macOS users, especially for certificate upload steps (e.g., how to generate or convert .pfx files on Linux).
Ensure that any referenced scripts or automation workflows are available in both PowerShell and Bash (or at least Azure CLI) formats.
Add links or references to Linux-specific documentation or troubleshooting guides where relevant.
Review screenshots and UI instructions to ensure they are not Windows-specific and clarify any platform-agnostic steps.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing PowerShell as the only CLI example for checking Application Gateway settings, exclusively recommending and illustrating Fiddler (a Windows-centric tool) for network capture, and referencing Windows-specific installation steps (e.g., 'Run as administrator'). There are no Linux or cross-platform alternatives mentioned for either command-line management or network debugging, and Windows tools and patterns are presented first and exclusively.

Recommendations:

Provide equivalent Azure CLI (az network application-gateway backend-http-settings list) or Azure Resource Manager REST API examples for checking Application Gateway settings, which are cross-platform.
Include examples using Linux-compatible network debugging tools such as tcpdump, Wireshark, or mitmproxy, and provide basic usage instructions for these tools.
When referencing downloadable tools, mention cross-platform options and clarify which tools are available on which operating systems.
Avoid Windows-specific installation instructions (like 'Run as administrator') unless also providing Linux/Mac equivalents (e.g., 'use sudo').
Structure sections so that cross-platform or platform-neutral approaches are presented before or alongside Windows-specific guidance.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell and Windows-centric tools and patterns as the primary or sole method for configuring and viewing TLS policy details. There is a lack of Linux/Unix-specific examples or parity in command-line instructions, and PowerShell is mentioned before CLI or REST in several places. The 'Next steps' section links only to a PowerShell-based configuration guide, omitting equivalent Linux/CLI documentation.

Recommendations:

Provide Azure CLI examples alongside or before PowerShell examples for all configuration and inspection tasks, as Azure CLI is cross-platform and widely used on Linux.
Include explicit Linux/Unix shell command examples (e.g., Bash) where relevant, especially for scripting or automation.
Ensure all references to configuration guides or 'Next steps' include links to both PowerShell and CLI (and, if available, ARM template or REST API) documentation.
Avoid language that prioritizes PowerShell or Windows tools (e.g., 'refer to the PowerShell, CLI, REST API or the Listeners blade in portal')—instead, use a neutral or Linux-first ordering, or group tools by platform.
Add a section or callout for Linux administrators, highlighting any platform-specific considerations or best practices.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias, particularly in the Helm installation section, where Windows instructions (including a PowerShell/winget example) are presented before Linux instructions. The use of the Windows-specific 'winget' tool is highlighted, and the Windows tab is listed first. However, Linux instructions are present and functional, and most of the CLI examples use cross-platform tools (Azure CLI, Helm, kubectl) with Bash syntax.

Recommendations:

Present Linux and Windows installation instructions in parallel or with Linux first, as Linux is the more common OS for Kubernetes administrators.
Avoid giving Windows-specific tools (like 'winget') prominence over Linux equivalents; mention both with equal weight.
Where possible, use cross-platform installation methods (e.g., package managers like apt, yum, or Homebrew) and provide explicit commands for both platforms.
Ensure that all examples and instructions are clearly marked for their respective platforms, and that neither platform is given preferential placement.
Consider adding macOS-specific instructions where relevant, as many Kubernetes administrators use macOS.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page references Azure PowerShell as the only example for creating an autoscaling, zone-redundant application gateway with a reserved virtual IP address. There are no equivalent examples or links for Linux/CLI users, and the only step-by-step tutorial provided is PowerShell-based, which is typically associated with Windows environments. This suggests a Windows-first and PowerShell-heavy bias, with a lack of parity for Linux users who would use Azure CLI or other cross-platform tools.

Recommendations:

Add equivalent Azure CLI (az) examples and tutorials for all PowerShell-based instructions.
Ensure that links to tutorials or how-to guides include both PowerShell and CLI options, ideally side-by-side.
When referencing tools or scripts, mention cross-platform options first or equally (e.g., 'using Azure CLI or PowerShell').
Review all 'Next steps' and related links to ensure Linux users have clear, accessible guidance.
Consider including Bash script examples where appropriate, especially for automation scenarios.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page does not provide any platform-specific command-line examples, but the only 'Next steps' link points to a PowerShell-based tutorial, which is primarily a Windows tool. There are no references to Linux tools, Bash, or CLI equivalents, and the documentation does not mention cross-platform approaches or parity for Linux users. This suggests a bias towards Windows and PowerShell usage, and a lack of Linux-first or cross-platform guidance.

Recommendations:

Include links to equivalent tutorials for Azure CLI (az), which is cross-platform and commonly used on Linux and macOS.
Provide example commands or configuration steps using Bash or shell scripting in addition to PowerShell.
Ensure that all referenced tutorials and guides have Linux-compatible instructions, or clearly indicate platform compatibility.
Mention both Windows and Linux tools and workflows when describing configuration steps, to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing only PowerShell-based examples for configuring Application Gateway with Key Vault certificates, with no equivalent Azure CLI, Bash, or Linux-native instructions. PowerShell is featured as the primary automation tool, and the 'Next steps' section links exclusively to a PowerShell guide. There is no mention or example of cross-platform tools or Linux-first workflows.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell command sequences, especially for certificate reference and managed identity configuration.
Include Bash shell script examples for common tasks to support Linux users.
In sections where PowerShell is referenced, mention that Azure CLI is also supported and provide links or inline examples.
Update the 'Next steps' section to include links to Azure CLI and ARM/Bicep template guides, not just PowerShell.
Where possible, use neutral, cross-platform language (e.g., 'use your preferred automation tool') and avoid implying PowerShell is the default or only option.
Consider adding a table or callout comparing PowerShell and CLI commands for key tasks.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a significant Windows and PowerShell bias. PowerShell (and specifically Windows PowerShell) is presented as the default and recommended runbook type, with extensive detail and examples provided only for PowerShell. Many examples and troubleshooting steps reference Windows-specific paths (e.g., C:\modules), environment variables, and tools. Linux support is mentioned but not illustrated with examples, and Linux-specific considerations are minimal or absent. Python runbooks receive less coverage, and Linux Hybrid Worker scenarios are only briefly referenced, often in the context of limitations.

Recommendations:

Provide Linux-specific examples and troubleshooting steps, especially for Hybrid Runbook Worker scenarios.
Include sample scripts and code snippets for Linux environments (e.g., referencing /var/tmp or /opt/modules instead of only C:\ paths).
Balance the order of presentation so that Python and Linux options are not always listed after Windows/PowerShell.
Explicitly document any differences in behavior, limitations, or setup steps for Linux Hybrid Runbook Workers.
Where Windows tools or environment variables are referenced, provide Linux equivalents (e.g., $HOME, /tmp, etc.).
Add parity in known issues and workarounds for Linux users, not just Windows/PowerShell scenarios.
Clarify in tables and overviews which features are cross-platform and which are Windows-only.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a strong bias towards Windows and PowerShell environments. Most examples, screenshots, and REST API payloads focus on PowerShell runbooks and the Az PowerShell module. Windows/PowerShell-specific tooling and patterns (such as PowerShell Gallery, .zip modules, and Get-Module cmdlet) are described in detail, while Linux/Python equivalents are only briefly mentioned or omitted. There is minimal guidance for Python or Linux-based automation, and Linux-specific package management is only referenced in passing.

Recommendations:

Provide parallel, detailed examples for Python runbooks, including REST API payloads and portal workflows.
Include Linux-specific instructions and screenshots, such as uploading .whl files, using pip, or viewing installed Python packages.
Mention and demonstrate the use of Azure CLI and Python modules with the same depth as PowerShell/Az modules.
Reorder sections or examples to present PowerShell and Python/Linux options equally, rather than PowerShell/Windows first.
Clarify when instructions or features are specific to Windows/PowerShell versus cross-platform or Linux/Python.
Add troubleshooting and best practices sections for Python/Linux automation scenarios.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page exclusively references Azure PowerShell scripts for migration tasks and does not mention or provide examples for Linux/Unix environments, Bash, Azure CLI, or cross-platform tooling. All migration automation is described in terms of PowerShell, which is traditionally associated with Windows, and there is no guidance for users on non-Windows platforms.

Recommendations:

Provide equivalent Azure CLI (az) commands and scripts for migration tasks, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that PowerShell Core is available cross-platform, if PowerShell must be used, and provide instructions for installing it on Linux/macOS.
Include Bash script examples or references for common migration steps.
Add a section or note clarifying support and best practices for users on Linux/macOS environments.
Ensure that all tooling references (scripts, automation) are presented in a platform-neutral way, or provide parallel instructions for both Windows and Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation shows some Windows bias, particularly in the sections related to uploading certificates to Application Gateway and configuring web servers. Azure PowerShell (a Windows-centric tool) is featured with detailed sample code, while equivalent Azure CLI (cross-platform) instructions are missing. Windows tools and patterns (such as referencing IIS and the Windows hosts file) are mentioned first or exclusively in some places. There is also a lack of explicit Linux-oriented examples for some steps, such as uploading certificates using Azure CLI or configuring trusted root certificates on Linux systems.

Recommendations:

Provide Azure CLI examples alongside or before Azure PowerShell for certificate upload and Application Gateway configuration, as Azure CLI is cross-platform.
Include explicit instructions or links for adding root certificates to trusted stores on Linux (e.g., update-ca-certificates on Ubuntu) as well as Windows.
When referencing web server configuration, balance IIS (Windows) with Apache/NGINX (Linux) by giving equal prominence and detail.
When mentioning editing the hosts file, include Linux/MacOS paths (e.g., /etc/hosts) and instructions, not just Windows.
Review the order of tool and platform mentions to avoid always listing Windows first.
Add notes or examples for Linux users wherever platform-specific steps are required.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The tutorial is heavily biased toward Windows and PowerShell usage. All examples and instructions are provided exclusively using Azure PowerShell cmdlets and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate). There are no equivalent instructions or examples for Linux or cross-platform environments (such as Azure CLI or OpenSSL for certificate creation). The documentation assumes the user is running a local administrative PowerShell session, which is not the default on Linux/macOS, and does not mention or link to Linux-compatible alternatives.

Recommendations:

Provide parallel instructions and code examples using Azure CLI (az) for all resource creation and configuration steps.
Include Linux/macOS-compatible methods for certificate creation, such as using OpenSSL, and show how to export certificates in the required format.
Explicitly state that the tutorial is Windows/PowerShell-specific, or better, restructure it to be cross-platform by default.
Add notes or sections for users on Linux/macOS, including how to install and use Azure CLI and how to perform each step in a non-Windows environment.
Where Windows-specific tools or paths are mentioned (e.g., cert:\localmachine\my, c:\appgwcert.pfx), provide Linux/macOS equivalents or clarify the differences.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples. The only scripting interface shown is PowerShell, which is most familiar to Windows users. Additionally, the structure and ordering of examples consistently present PowerShell before any mention of CLI, and in some cases, CLI is not mentioned at all. There is no guidance for Linux users or those preferring Bash or Azure CLI, and no mention of Linux-native tools or workflows.

Recommendations:

Add Azure CLI examples alongside all PowerShell commands, using Bash syntax where appropriate.
Where possible, provide both PowerShell and CLI tabs for all command-line operations.
Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
Ensure that instructions and screenshots are not Windows-specific and clarify that the Azure portal is platform-agnostic.
Review the ordering of examples so that PowerShell and CLI are presented with equal prominence, or alternate their order.
Consider including a section or note for Linux/macOS users to highlight any platform-specific considerations.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. In general troubleshooting steps and scenarios, Windows examples, tools, and paths are consistently listed before Linux equivalents. Several scenarios provide detailed PowerShell-based instructions and registry edits for Windows, while Linux instructions are less detailed or missing for similar cases (e.g., registry permissions, event log checks). Windows-specific tools (e.g., PowerShell scripts, registry, event logs) are referenced without always providing Linux analogs or guidance. Some troubleshooting steps and resolutions are Windows-only, with no Linux equivalent provided.

Recommendations:

Alternate the order of Windows and Linux instructions, or present them in parallel, to avoid always listing Windows first.
Where PowerShell or Windows registry/event log instructions are given, provide equivalent Linux commands or log file locations (e.g., systemd journal, syslog, Linux file permissions).
For troubleshooting tools, ensure Linux scripts/utilities are described with the same level of detail as Windows (e.g., how to run, interpret output).
For scenarios that are Windows-specific (e.g., registry, UAC), clarify that they do not apply to Linux, and consider adding Linux-specific troubleshooting scenarios where relevant.
Where only Windows event logs are referenced, include Linux logging equivalents (e.g., journalctl, /var/log/messages) for parity.
Ensure that all steps for installation, troubleshooting, and uninstallation are equally detailed for both platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation generally strives for cross-platform parity, but there are subtle signs of Windows bias. In several places, Windows command-line environments (Cmd, PowerShell) are listed before Linux/macOS equivalents, and PowerShell is given its own language pivot. Windows-specific tools and patterns (such as .venv activation paths and command syntax) are described in detail, sometimes before or with more prominence than Linux/macOS equivalents. The presence of a dedicated PowerShell language pivot, and the inclusion of both Cmd and PowerShell tabs for commands, further highlights a Windows-centric approach. However, Linux/macOS instructions are present and functional throughout.

Recommendations:

Ensure that Linux/macOS examples are always presented with equal prominence and, where possible, listed before or alongside Windows examples.
Where multiple OS-specific tabs are used, consider listing Linux/macOS first, or randomizing order to avoid implicit prioritization.
Review the use of PowerShell as a primary language pivot; ensure that Linux shell scripting or Bash is equally represented where relevant.
Audit all command examples to ensure that Linux/macOS paths and conventions are accurate and not derived from Windows-centric assumptions.
Where possible, provide cross-platform (e.g., Bash, PowerShell Core) command examples that work on all systems, or clearly indicate OS-specific differences.
Explicitly state in the prerequisites or introduction that all major platforms are supported and that instructions are provided for each.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is generally cross-platform in intent, focusing on Visual Studio Code and the Azure Functions extension, which are available on Windows, macOS, and Linux. However, there are subtle signs of Windows bias: troubleshooting steps specifically mention Windows and WSL Bash, and there are no explicit Linux- or macOS-specific instructions or examples. The documentation does not provide parity in addressing potential Linux/macOS issues or terminal usage, and references to shell environments are Windows-centric.

Recommendations:

Add explicit notes or troubleshooting steps for Linux and macOS users, such as common issues with permissions, shell environments, or dependencies.
When mentioning Windows-specific issues (e.g., WSL Bash), also mention possible Linux/macOS equivalents or clarify if the issue is Windows-only.
Include example terminal commands or screenshots for Linux/macOS where relevant, especially in sections about running or deploying functions.
Ensure that all references to tools (such as Azure Functions Core Tools) clarify their cross-platform availability and provide installation instructions for all supported OSes.
Consider adding a table or section that highlights any OS-specific considerations for Visual Studio Code and Azure Functions development.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation exhibits a Windows bias by providing detailed instructions and screenshots for managing LDAP POSIX attributes using Windows-only tools (Active Directory Users and Computers MMC snap-in), without offering equivalent Linux-based methods. The section on accessing the Attribute Editor is exclusively Windows-focused, and there are no examples or guidance for managing POSIX attributes from Linux environments. Additionally, Windows terminology and tools are mentioned first or exclusively in several places, while Linux/NFS client configuration is referenced only via a link, with no in-page examples.

Recommendations:

Add equivalent instructions and examples for managing LDAP POSIX attributes using common Linux tools (e.g., ldapmodify, ldapadd, or Apache Directory Studio).
Include screenshots or command-line examples for Linux-based LDAP management to ensure parity with the Windows MMC snap-in instructions.
Where Windows tools or workflows are described, provide Linux alternatives in parallel, or at least mention them explicitly.
Ensure that configuration steps for both Windows and Linux clients are given similar prominence and detail, rather than linking out only for Linux.
Review the order of presentation to avoid always listing Windows tools or concepts first, especially in dual-protocol or cross-platform contexts.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation generally provides both Bash and Cmd (Windows Command Prompt) examples for command-line operations, but Cmd/Windows examples are consistently presented alongside or immediately after Bash, sometimes with more detailed explanations. There is a notable absence of explicit Linux-specific tools, troubleshooting, or environment setup guidance. No PowerShell-specific examples are present, but the documentation does not mention or show Linux-specific package managers, shell peculiarities, or troubleshooting steps. The focus on Visual Studio Code, IntelliJ, and Eclipse is cross-platform, but some references (such as environment variable setup and folder structure) assume familiarity with Windows conventions. There are no Linux-only examples or sections, and some tables and explanations list Windows before Linux.

Recommendations:

Ensure Linux examples are always presented alongside Windows examples, and not only as Bash tabs but also in narrative explanations.
Include Linux-specific troubleshooting tips, such as permissions, file paths, and environment variable setup (e.g., export JAVA_HOME).
Add explicit notes about differences in file system case sensitivity, path separators, and common issues on Linux.
When listing supported OS or Java versions, alternate the order or present Linux first in some cases.
Provide examples using Linux package managers (apt, yum) for installing Java or Maven where appropriate.
Clarify that all CLI commands work on both Windows and Linux, and highlight any OS-specific caveats.
Consider adding a dedicated section for Linux/macOS development environment setup and common pitfalls.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing detailed PowerShell instructions and command tables, while omitting equivalent Linux or Bash examples. The CLI section is present but lacks Linux-specific context or troubleshooting. There is no mention of Linux tools or shell environments, and PowerShell is given a dedicated, detailed section, reinforcing a Windows-centric approach.

Recommendations:

Add explicit Bash/Linux shell examples for connecting to Azure Government, including environment variable setup and troubleshooting tips for common Linux distributions.
Include a section or notes on using Azure NetApp Files from Linux/macOS environments, highlighting any differences or additional steps required.
Balance PowerShell instructions with equivalent Bash or cross-platform scripting examples, especially for authentication and automation.
Mention cross-platform tools (such as Azure CLI in Bash, or REST API usage with curl) before or alongside PowerShell examples.
Ensure that references to tools and commands do not assume a Windows environment by default, and clarify when instructions are platform-specific.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

Summary:

The documentation presents Windows (SMB) client instructions and screenshots before Linux (NFS) client instructions, and provides more detailed steps and visual aids for Windows users (e.g., File Explorer, 'dir' command). The REST API section references PowerShell specifically, but does not mention Linux scripting or tools. This ordering and tool emphasis may give the impression of a Windows-centric approach.

Recommendations:

Present Linux and Windows client instructions in parallel or alternate the order in different sections to avoid always listing Windows first.
Provide equivalent screenshots and detailed step-by-step instructions for Linux clients, such as using graphical file managers (e.g., Nautilus, Dolphin) to check NFS mount properties.
In the REST API section, mention and provide examples for using curl or other common Linux command-line tools, not just PowerShell.
Where possible, use neutral language and tool references (e.g., 'command prompt or terminal') and ensure parity in the depth of examples and visual aids for both platforms.
Explicitly state that all major platforms are supported and provide links or references to platform-specific documentation if available.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing only Windows/PowerShell command examples for Active Directory management (e.g., Get-ADUser, Set-ADUser), referencing Windows-specific tools and policies (such as Group Policy, registry keys, and Windows security privileges), and focusing on Windows terminology and workflows. There are no equivalent Linux or cross-platform command examples or guidance for managing AD connections from non-Windows environments. Azure CLI is mentioned, but only as an alternative for Azure resource registration, not for AD management. The documentation assumes the admin is operating in a Windows-centric environment.

Recommendations:

Provide equivalent Linux command-line examples (e.g., using ldapmodify, kinit, or samba-tool) for managing AD user properties and Kerberos encryption types.
Reference cross-platform tools (such as Samba, sssd, or realmd) for joining and managing Active Directory from Linux systems.
Include Linux/Unix-specific considerations and workflows for AD integration, especially for NFS and Kerberos scenarios.
Balance the order of presentation so that Linux and Windows tools are introduced together, or provide parallel instructions for both platforms.
Clarify which steps are Windows-only and offer alternatives or guidance for non-Windows environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for registering and unregistering the feature, mentioning PowerShell commands first, and not including equivalent Linux/Unix shell or Azure CLI examples inline. This may disadvantage users who administer Azure from non-Windows platforms or prefer command-line tools common on Linux.

Recommendations:

Provide Azure CLI examples alongside PowerShell for all feature registration and status commands, as Azure CLI is cross-platform and widely used on Linux.
Explicitly mention that all operations can be performed from Linux/macOS terminals using Azure CLI, and provide those command examples in the main steps (not just as a side note).
Consider including Bash shell script examples for automation scenarios relevant to Linux administrators.
Reorder examples or present both PowerShell and CLI commands together to avoid implying a Windows-first workflow.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. Azure PowerShell is given equal or greater prominence compared to Azure CLI, and PowerShell-specific tooling and syntax are used throughout. There are no explicit Linux/Bash examples or notes about cross-platform usage, and PowerShell is presented as a primary automation tool. In some cases, PowerShell appears before or alongside CLI, but Linux/Bash scripting is not addressed. The examples for scripting (outside of Python) assume a Windows/PowerShell environment, and there is no mention of Linux-specific considerations or terminal environments.

Recommendations:

Explicitly state that Azure CLI commands work cross-platform (Windows, macOS, Linux) and provide Bash-specific examples where appropriate.
When showing scripting examples, provide both PowerShell and Bash shell script versions, especially for automation scenarios.
Clarify when a command or script is intended for PowerShell (Windows/macOS/Linux) versus Bash (Linux/macOS/Windows with WSL).
Avoid using PowerShell variable assignment syntax ($var=...) in Azure CLI examples; instead, show Bash-compatible syntax (e.g., var=$(...) ) for Linux users.
Add a section or note about running Azure CLI in different environments (Windows Command Prompt, PowerShell, Bash, Cloud Shell, etc.).
Where PowerShell modules or cmdlets are referenced, mention cross-platform support or provide alternatives for Linux users if available.
Ensure that all automation and scripting guidance is accessible to both Windows and Linux users, with clear, parallel examples.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides a Windows-specific example (PowerShell command and mount syntax) for NFS client configuration but does not provide equivalent Linux commands or examples. Windows tools and patterns are mentioned explicitly, and Linux examples are missing in sections where both platforms are relevant. In the section about persistent NFS mounts, the Linux method is mentioned first, but no example is given, while the Windows section later provides detailed commands.

Recommendations:

For every Windows-specific example (such as enabling CaseSensitiveLookup or mounting NFS volumes), provide an equivalent Linux example (e.g., relevant mount commands, configuration file edits).
When mentioning tools or commands (like PowerShell or Mount), also mention the Linux/Unix equivalents (e.g., mount command, /etc/fstab editing).
Ensure that Linux and Windows instructions/examples are presented in parallel or side-by-side, rather than focusing on one platform.
Where possible, use neutral language and avoid assuming the reader is using Windows unless the section is explicitly Windows-only.
Add explicit Linux troubleshooting tips for NFS client issues, similar to the Windows guidance provided.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides both Azure CLI (Bash) and PowerShell examples side by side, but there are subtle signs of Windows bias. Windows/PowerShell tools and patterns are sometimes referenced first or exclusively (e.g., references to Connect-AzAccount, CommandLineToArgvW, and PowerShell-specific error handling). The documentation assumes familiarity with Windows/PowerShell concepts and tools, and some explanations (like argument parsing) reference Windows APIs. However, Linux/Bash examples are present throughout, and the CLI examples use Bash syntax. There are no outright missing Linux examples, but the documentation could better balance the presentation order and tool references.

Recommendations:

Where possible, avoid referencing Windows-specific APIs (e.g., CommandLineToArgvW) in general explanations, or provide equivalent Linux context.
Alternate the order of CLI (Bash) and PowerShell examples, or present them in parallel, to avoid always listing PowerShell second.
When discussing authentication (e.g., Connect-AzAccount), mention cross-platform alternatives or clarify that PowerShell Core is available on Linux.
In sections about argument parsing or environment variables, provide both Windows and Linux/Bash perspectives if system-level details are discussed.
Audit for any subtle language that assumes a Windows-first audience and revise to be OS-neutral where possible.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation displays a moderate Windows bias. Windows-specific tools (Visual Studio, PowerShell, Chocolatey, Winget) are given prominent and detailed coverage, and Windows installation instructions are often listed before or with more detail than Linux/macOS equivalents. PowerShell is used as the default scripting language for manual installation on Windows, and Windows-centric package managers are highlighted. Linux and macOS instructions are present and generally complete, but Windows tools and patterns are more heavily emphasized.

Recommendations:

Ensure Linux and macOS installation instructions are as detailed and prominent as Windows instructions, including troubleshooting tips and validation steps.
When listing installation options or tools, rotate or randomize the order, or explicitly avoid always listing Windows first.
Provide Bash or cross-platform shell examples alongside PowerShell for manual installation steps.
Highlight cross-platform editors (like VS Code) before Windows-only tools (like Visual Studio) to reinforce parity.
Where Windows-specific package managers (Chocolatey, Winget) are mentioned, also mention Linux/macOS equivalents (e.g., apt, yum, Homebrew) with equal detail.
Add a summary table or section explicitly comparing platform support and installation nuances to help users quickly find their path.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by providing detailed, step-by-step instructions for setting SACLs using Windows GUI tools, referencing Windows administration hosts, and using PowerShell commands for feature registration. Equivalent Linux/NFS instructions are either missing, less detailed, or deferred to external links. The registration section leads with PowerShell examples, and the process for setting Audit ACEs on NFS volumes is not described inline, but instead refers to another document.

Recommendations:

Provide step-by-step instructions for setting Audit ACEs on NFSv4.1 volumes directly in this document, similar to the Windows SACL steps.
Include Linux command-line examples (e.g., using setfacl or nfs4_setfacl) for configuring Audit ACEs.
When presenting feature registration, show Azure CLI examples before or alongside PowerShell, not after.
Balance the prominence of Windows and Linux tools and terminology throughout the document.
Add screenshots or command examples for Linux/NFS workflows where Windows GUI screenshots are provided.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell-specific instructions and links (e.g., 'import-export-ps.md'), mentioning Azure PowerShell before Azure CLI, and not providing explicit Linux or cross-platform command-line examples. There is no mention of Linux-specific tools or workflows, and the sample focuses on Bicep/ARM templates without showing how to execute migration steps using cross-platform tools.

Recommendations:

Provide Azure CLI examples alongside or before Azure PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux.
Update links and references to include both PowerShell and CLI documentation, or use neutral phrasing such as 'see Export your blueprint definition using Azure CLI or PowerShell'.
Explicitly mention that all migration steps can be performed on Linux, macOS, and Windows, and provide command-line examples for each where relevant.
Avoid using '-ps' (PowerShell) documentation links exclusively; link to general or CLI documentation where possible.
Add a section or note on how to perform the migration steps in a Linux environment, including any prerequisites or differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation generally presents Windows/SMB concepts and tools before or with more detail than Linux/NFS equivalents. Windows terminology (NTFS, SID, Active Directory, NTLM) is used as the default or primary reference, and there are no Linux command-line examples for SMB/Samba access. Official support is stated for Windows and macOS SMB clients, but not for Linux, despite Samba being widely used. Linux/NFS examples are present, but Linux SMB usage is downplayed and lacks parity in guidance.

Recommendations:

Provide explicit Linux/Samba command-line examples for accessing SMB shares, similar to the NFS rpcinfo example.
Clarify and expand support guidance for Linux SMB clients, including common troubleshooting tips.
Balance the order of presentation so that Linux/NFS and Windows/SMB are introduced with equal prominence.
When discussing permissions and ACLs, include both NTFS and POSIX/NFSv4 ACLs side by side, with examples.
Reference Linux tools (e.g., mount.cifs, smbclient) and configuration patterns where appropriate.
Avoid language that implies Windows is the default or primary environment (e.g., 'SMB is primarily used with Windows clients'), and instead acknowledge the prevalence of mixed environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page exhibits a mild Windows bias. In sections describing how to create and manage snapshots, PowerShell is mentioned explicitly and linked alongside Azure Portal, REST API, and Azure CLI, but there are no explicit Linux shell or Bash examples. The order of tools often lists PowerShell before or alongside CLI, but never provides Linux-specific command-line examples or scripts. There are no references to Linux-native tools or workflows, and no sample commands for Linux users. This may make Linux administrators feel less directly supported.

Recommendations:

Add explicit Bash/Azure CLI examples for common snapshot operations (e.g., creating, listing, deleting snapshots) to demonstrate parity with PowerShell.
When listing management tools, alternate the order or group Azure CLI and PowerShell together, or mention CLI first to avoid a Windows-first impression.
Include example scripts or links for Linux environments, not just PowerShell or Windows-centric scripting.
Reference Linux-native workflows or tools where applicable, especially for scripting and automation.
Clarify that all operations can be performed equally from Linux environments using Azure CLI and REST API, and provide sample commands.
If referencing PowerShell, consider also referencing Bash or shell scripting for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation contains a subtle Windows bias, primarily in the use of the 'osPlatform' property set to 'Windows' in several JSON examples (e.g., credentials, user name, VM size selectors), and the absence of equivalent Linux or cross-platform examples. There are no explicit Linux examples or mentions of Linux-specific patterns, and the documentation does not clarify cross-platform support or differences. No PowerShell or Windows command-line examples are present, but the repeated use of Windows as the default or sole platform in UI control examples suggests a Windows-first perspective.

Recommendations:

Include examples where 'osPlatform' is set to 'Linux' or provide dual examples for both Windows and Linux where relevant (e.g., credentials, VM size selectors, user name controls).
Clarify in the documentation whether the controls and patterns shown are applicable to both Windows and Linux, or specify any differences in behavior or requirements.
Add a section or note discussing cross-platform considerations, especially for managed applications that may target Linux VMs.
Ensure that any platform-specific properties or behaviors are documented for both Windows and Linux, and provide guidance for users deploying to Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page is generally platform-neutral, focusing on Azure Portal and DNS provider interfaces. However, in the troubleshooting section for clearing DNS cache, only the Windows-specific command ('ipconfig /flushdns') is mentioned, with no equivalent commands for Linux or macOS. This presents a subtle 'windows_first' and 'missing_linux_example' bias.

Recommendations:

When providing troubleshooting steps such as clearing DNS cache, include equivalent commands for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo resolvectl flush-caches') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder').
Wherever OS-specific instructions are given, present them in a cross-platform format (e.g., using tabs or bullet points for Windows, Linux, and macOS).
Review other sections for any implicit platform assumptions and ensure parity in examples and troubleshooting guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation assumes a development environment that is compatible with .NET and Azure App Service, and it references GitHub Codespaces and Azure CLI for deployment. However, it does not provide any Linux-specific instructions, terminal commands, or examples, nor does it mention Linux tooling or patterns. The workflow and examples are generic enough to work cross-platform, but the absence of explicit Linux or non-Windows guidance, especially for local development, may disadvantage Linux users.

Recommendations:

Explicitly mention that all commands and steps work on Linux, macOS, and Windows, or call out any differences.
Provide example terminal commands for both Windows (PowerShell/CMD) and Linux/macOS (bash/zsh) where applicable.
Include a note about installing .NET SDK and Azure CLI on Linux, with links to official installation guides.
If using Codespaces, clarify that it provides a Linux-based environment, and offer alternative steps for users developing locally on Linux.
Add troubleshooting tips for common Linux-specific issues (e.g., file permissions, environment variables).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation is generally platform-neutral, focusing on Azure Portal UI steps. However, in the troubleshooting section for clearing DNS cache, only the Windows-specific command (`ipconfig /flushdns`) is mentioned, with no equivalent instructions for Linux or macOS users. This constitutes a 'windows_first' and 'missing_linux_example' bias.

Recommendations:

When providing troubleshooting steps such as clearing DNS cache, include equivalent commands for Linux (e.g., `sudo systemd-resolve --flush-caches` or `sudo resolvectl flush-caches`) and macOS (e.g., `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`).
Explicitly mention that the instructions apply to all platforms, or provide platform-specific notes where relevant.
Review other troubleshooting or command-line instructions to ensure parity across Windows, Linux, and macOS.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation presents configuration options in the order: Azure portal, Azure PowerShell, and then Azure CLI. The PowerShell section is detailed and comes before the CLI section, which can be interpreted as a Windows-first and PowerShell-heavy bias. There are no explicit Linux or Bash-specific examples, and the CLI section, while cross-platform, is presented after PowerShell. No Windows-only tools are mentioned, but the ordering and depth of PowerShell coverage may suggest a preference for Windows environments.

Recommendations:

Present Azure CLI examples before or alongside PowerShell examples to signal equal support for Linux and cross-platform users.
Add explicit Bash/Linux shell example blocks where relevant, especially for scripting scenarios.
Clarify in the introduction that Azure CLI is fully supported on Linux, macOS, and Windows.
Ensure parity in detail and completeness between PowerShell and CLI sections.
Consider adding a table comparing PowerShell and CLI commands for each step.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both Windows Command Prompt and PowerShell commands. Linux/macOS instructions are present but come after the Windows examples. There are no missing Linux examples or exclusive use of Windows tools, but the ordering and emphasis show a mild Windows-first bias.

Recommendations:

Present Linux/macOS and Windows instructions in parallel tabs or in the same order throughout the document, rather than listing Windows first.
Avoid giving Windows instructions (cmd, PowerShell) more prominence than Linux/macOS; consider starting with Linux/macOS or presenting all platforms equally.
If using tabbed instructions, ensure the default tab is not always Windows.
Explicitly mention that all commands work cross-platform where applicable, and highlight any platform-specific differences only when necessary.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS, and includes both Windows command prompt and PowerShell commands. Linux/macOS instructions are present and correct, but are always listed after Windows instructions. There are no missing Linux examples, but the ordering and inclusion of multiple Windows-specific shells (cmd, PowerShell) before Linux suggest a mild Windows-first bias.

Recommendations:

Present Linux/macOS and Windows instructions in parallel tabs or with equal prominence, rather than always listing Windows first.
Consider listing Linux/macOS instructions first, or randomizing the order to avoid implicit prioritization.
If including both cmd and PowerShell for Windows, consider also mentioning common Linux shells (bash, zsh) for parity, or simply use a tabbed interface for OS selection.
Review other sections for subtle Windows-centric language or assumptions, and ensure all CLI examples are cross-platform where possible.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation focuses exclusively on ASP.NET Core and C# examples, with no mention of Linux-specific workflows, tools, or command-line instructions. All instructions assume use of the Azure Portal or .NET tooling, which are cross-platform, but the context and language are heavily oriented toward Windows developers. There are no examples or notes for Linux environments, shell commands, or non-Windows development patterns.

Recommendations:

Add explicit notes clarifying that all .NET Core and Azure SDK instructions apply equally to Linux, macOS, and Windows.
Include example commands for common Linux shells (e.g., bash) where relevant, such as for environment variable setup or CLI usage.
Mention and link to cross-platform development tools and editors (e.g., Visual Studio Code, dotnet CLI) to reinforce Linux compatibility.
If any steps require the Azure Portal, note that it is web-based and platform-agnostic.
Provide troubleshooting tips or references for Linux users, such as permissions or certificate store differences.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally maintains parity between Windows and Linux by mentioning both rsync (Linux/Unix) and robocopy (Windows) as migration tools. However, in both migration-related sections, the SMB/Windows tool (robocopy) is mentioned after the NFS/Linux tool (rsync), but the phrasing 'workloads tools such as rsync' and 'workloads robocopy in the same manner' may subtly prioritize Linux tools for NFS and Windows tools for SMB. There is no explicit PowerShell or Windows-only example, but robocopy (a Windows tool) is the only SMB migration tool mentioned, with no Linux-based SMB alternatives (e.g., smbclient, cifs-utils) provided. There are no command-line examples for either platform, but the documentation could be seen as slightly Windows-biased for SMB scenarios by only mentioning robocopy.

Recommendations:

Include Linux-based SMB migration tools (e.g., smbclient, cifs-utils, or mount.cifs with cp/rsync) alongside robocopy when discussing SMB data migration.
Provide example commands for both Windows and Linux platforms for common migration scenarios (NFS and SMB).
Explicitly state that both Windows and Linux clients can be used for SMB migration, and list equivalent tools for each.
Consider a table or matrix summarizing migration tools for both NFS and SMB, with platform compatibility clearly indicated.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias, primarily by listing Windows-centric tools (such as Visual Studio and PowerShell) before cross-platform or Linux-native alternatives, especially in the C# section. Visual Studio (Windows-only) is presented as the primary environment for C#, with cross-platform options like Visual Studio Code and command-line tools mentioned afterward. PowerShell is listed as an HTTP test tool before curl, and Microsoft Edge's Network Console (Windows-only) is also highlighted. However, the documentation does make efforts to mention Linux and macOS support for most tools and provides parity in examples for other languages.

Recommendations:

In the C# section, present Visual Studio Code and command-line/terminal options before or alongside Visual Studio to emphasize cross-platform support.
When listing HTTP test tools, mention curl (a ubiquitous Linux tool) before PowerShell and Microsoft Edge, or group tools by platform.
Explicitly mention Linux-native editors (such as Vim, Emacs, or JetBrains Rider) where appropriate, or clarify that Visual Studio Code is the recommended cross-platform editor.
Where possible, provide Linux-specific setup or example commands (e.g., for installing Azurite or Core Tools) alongside Windows instructions.
Ensure that all tool and environment lists are ordered in a platform-neutral or rotating manner, rather than defaulting to Windows-first.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation is generally cross-platform and Linux-focused for hosting, but there are subtle Windows biases in the development and publishing workflow sections. Specifically, references to 'command prompt' and recommendations for remote build 'when developing Python apps on Windows' appear before or instead of explicit Linux or macOS guidance. The term 'command prompt' is more associated with Windows, and there is no explicit mention of Linux/macOS terminals in some places. Additionally, the documentation recommends against local builds 'when developing locally on Windows' but does not provide equivalent guidance for Linux/macOS users, potentially implying a Windows-centric development workflow.

Recommendations:

Use neutral, cross-platform terminology such as 'terminal' instead of 'command prompt', or explicitly mention 'terminal (Linux/macOS) or command prompt (Windows)'.
Provide explicit instructions and recommendations for Linux/macOS users alongside Windows users, especially in sections about local development and publishing.
Where recommendations are made specifically for Windows (e.g., remote build), clarify the guidance for Linux/macOS users to ensure parity.
Include example commands or screenshots from both Windows and Linux/macOS environments where relevant.
Review all sections for subtle ordering bias (e.g., mentioning Windows before Linux) and alternate or balance the order to avoid implicit prioritization.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation provides environment variable setup instructions in a Windows-first order, listing Windows Command Prompt and PowerShell commands before the equivalent macOS/Linux bash command. However, all other instructions and code samples are platform-agnostic and do not show a preference for Windows-specific tools or patterns.

Recommendations:

Present environment variable setup instructions in a platform-neutral order, such as listing Linux/macOS first or grouping all OS instructions together without prioritizing Windows.
Consider using a tabbed or side-by-side format for environment variable setup commands, allowing users to easily find instructions for their operating system.
Explicitly state that the tutorial is cross-platform and that all steps apply equally to Windows, Linux, and macOS, except where OS-specific commands are required.
Ensure future documentation sections maintain parity by providing examples for all major platforms where relevant.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation mentions Azure PowerShell before Azure CLI when discussing supported versions for the 'count' property, and the 'Next steps' section links only to PowerShell deployment instructions, omitting Linux/CLI-focused deployment guides. There are no explicit PowerShell command examples, but the ordering and linking show a subtle preference for Windows tooling.

Recommendations:

When listing supported tools or versions, alternate the order (e.g., mention Azure CLI before PowerShell, or list both together without preference).
In the 'Next steps' section, include links to both PowerShell and Azure CLI deployment instructions to ensure parity for Linux and cross-platform users.
Where deployment instructions are referenced, provide both Windows (PowerShell) and Linux (CLI) examples or links.
Review other related documentation to ensure that Linux/CLI users are equally supported and not implicitly deprioritized.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation provides detailed network design guidance for Azure VMware Solution but does not include any platform-specific examples, scripts, or tooling references. However, it also does not provide any practical configuration examples (such as CLI commands or scripts) for either Windows (e.g., PowerShell) or Linux (e.g., Bash). This absence means Linux users do not see parity in practical guidance, but there is no explicit Windows bias in the form of Windows-first or Windows-only examples.

Recommendations:

Add practical configuration examples for both Windows (PowerShell) and Linux (Bash/CLI) environments, especially for common tasks such as configuring BGP, advertising routes, or setting up NVAs.
When referencing network appliances or tools, mention both Windows and Linux-compatible options (e.g., show how to configure routing or tunnels using both Windows Server Routing and Remote Access Service and Linux-based solutions like FRRouting or strongSwan).
Include sample scripts or command-line snippets for both platforms where relevant, to ensure users on either OS can follow along without ambiguity.
Explicitly state platform-agnostic requirements and, where possible, link to both Windows and Linux documentation for third-party NVAs or network configuration.

Create pull request

No problematic pages found in this scan. All pages appear to be Linux-friendly! 🐧