Scan Details - Linux-first Docs for Azure

1508

Pages Scanned

63

Pages Flagged

1508

Changed Pages

4.2%

% Pages Flagged

Scan Information

Started At: 2025-08-10 00:00:11

Finished At: 2025-08-10 00:33:19

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 demonstrates a Windows bias by providing only Azure PowerShell command-line examples for scripting and automation, with no mention or examples of Azure CLI (which is cross-platform and preferred by many Linux users). The PowerShell sections are prominent and detailed, while there are no Bash, shell, or Linux-native instructions. The installation instructions and references are exclusively for PowerShell, and there is no guidance for Linux users on how to perform equivalent tasks. This may hinder Linux users or those who prefer non-Windows environments.

Recommendations:

Add Azure CLI examples alongside PowerShell for all scripting/automation tasks, including creating and managing managed identities.
Include Bash/shell command examples where appropriate, especially for ARM template deployments.
Explicitly mention that Azure CLI is cross-platform and provide installation links for Linux/macOS.
Structure sections so that Azure CLI and PowerShell examples are presented with equal prominence, or provide a tabbed interface for users to select their preferred environment.
Reference Linux tools and workflows where relevant, and avoid assuming PowerShell is the default or only scripting environment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation displays a Windows bias by consistently presenting Windows-related information and tools first (e.g., Windows SKU availability before Linux, Azure PowerShell section before mentioning Linux scripting alternatives), providing PowerShell examples without corresponding Bash or Linux-native scripting examples, and referencing Windows-specific behaviors. Linux-specific instructions are present but less detailed, and there are no examples using Linux-native tools or shell scripting beyond Azure CLI.

Recommendations:

Present Linux and Windows options in parallel, or alternate which is shown first to avoid 'windows_first' ordering.
Provide Bash or Linux shell script equivalents for all PowerShell automation examples.
Explicitly mention Linux-native tools or workflows where relevant, not just Azure CLI.
Clarify any differences in behavior or limitations between Windows and Linux App Service plans.
Ensure screenshots and UI instructions are not Windows-centric (e.g., avoid only showing Windows portal views if Linux differs).

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by referencing Visual Studio Code (a Microsoft product often associated with Windows) and GitHub Copilot as the only suggested tools for testing the MCP server, without mentioning Linux-native alternatives or command-line tools. All UI navigation and screenshots are based on the Azure Portal, which is cross-platform but often optimized for Windows environments. There are no Linux-specific instructions, CLI examples, or references to Linux tools for testing or interacting with the MCP server.

Recommendations:

Include examples of testing the MCP server using cross-platform or Linux-native tools such as curl, httpie, or Postman.
Mention that Visual Studio Code and GitHub Copilot are available on Linux and macOS, or suggest alternative editors and tools commonly used on those platforms.
Provide Azure CLI or PowerShell Core (cross-platform) command examples for relevant operations, ensuring parity for Linux users.
Add explicit notes or sections for Linux/macOS users where workflows or tool usage might differ.
Ensure screenshots and instructions are not overly tailored to a Windows-centric experience, or supplement with Linux/macOS equivalents.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exhibits a Windows bias primarily in the section addressing Azure Traffic Manager endpoints, where only a PowerShell script is provided for identifying non-Azure endpoints. There are no equivalent Bash, Azure CLI, or cross-platform scripting examples for Linux/macOS users. The instructions for running the script assume a Windows/PowerShell environment, and there is no mention of alternatives or parity for non-Windows platforms. Elsewhere, REST API and Azure CLI commands are referenced, which are cross-platform, but the exclusive use of PowerShell for a key scenario stands out as a bias.

Recommendations:

Provide equivalent Bash or Azure CLI scripts for identifying non-Azure Traffic Manager endpoints, ensuring Linux/macOS users can perform the same checks.
Explicitly mention that the PowerShell script can be run on PowerShell Core (pwsh) on Linux/macOS, if applicable, or provide guidance for cross-platform usage.
When referencing scripts or tools, offer both Windows (PowerShell) and Linux/macOS (Bash/CLI) options, or clarify when a solution is platform-agnostic.
Review documentation for other scenarios to ensure that all platform-specific tooling (e.g., scripts, commands) is accompanied by alternatives or clear cross-platform instructions.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by featuring PowerShell as the only explicit scripting example, referencing Azure CLI only as a link without an inline example, and omitting Linux-specific command-line or scripting workflows. The automation section lists PowerShell after Azure CLI but provides only a PowerShell code snippet, with no Bash or Linux-native example. There is also a lack of explicit Linux tooling or parity in the walkthrough steps.

Recommendations:

Add inline Azure CLI (Bash) examples alongside or before PowerShell examples in the 'Automate with scripts' section.
Include Linux-native workflows or notes (e.g., using Bash, OpenSSL, or Linux file paths) when discussing certificate upload and management.
Ensure that all scripting/code examples are provided for both Windows (PowerShell) and Linux (Bash/CLI), and that neither platform is prioritized in ordering.
Reference Linux-specific documentation or troubleshooting where relevant, especially in sections about certificate file handling and environment-specific configuration.
Review screenshots and UI instructions to ensure they are not Windows-centric, or provide Linux/CLI alternatives where possible.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides detailed PowerShell instructions first and in more depth, with a secondary Azure CLI example. There are no explicit Linux shell (bash) or cross-platform scripting examples, and the PowerShell example is more prominent. There is also an assumption of Visual Studio usage, which is Windows-centric.

Recommendations:

Provide bash or shell script examples for Linux users alongside PowerShell.
List Azure CLI or bash examples before or alongside PowerShell to avoid Windows-first bias.
Mention cross-platform development tools (such as VS Code) in addition to Visual Studio.
Clarify that all steps can be performed on Linux/macOS as well as Windows, and note any OS-specific requirements.
Ensure screenshots and UI instructions are not Windows-specific if the Azure Portal experience is the same across platforms.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias by presenting Windows-related tools and examples before their Linux equivalents, and by providing Azure PowerShell automation examples (which are more common on Windows) alongside Azure CLI. The Azure portal UI, which is more familiar to Windows users, is emphasized throughout. While Linux is mentioned (e.g., Linux container availability, Linux-specific CLI flag), there are no Linux shell-specific examples, and PowerShell is highlighted as a primary automation method.

Recommendations:

Provide Linux shell (bash) scripting examples alongside or before PowerShell examples for automation.
Ensure parity in example order: present Linux and Windows options together, or alternate which comes first.
Mention and link to Azure CLI usage from both Windows and Linux environments, clarifying cross-platform compatibility.
Include screenshots or instructions for the Azure portal experience on Linux (if differences exist), or clarify that the portal is OS-agnostic.
Where PowerShell is referenced, note that Azure CLI is fully supported on Linux and macOS, and provide bash/zsh equivalents where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides installation instructions for the required NuGet packages using both the .NET Core CLI and the Visual Studio Package Manager Console (PowerShell-based), but it lists the Visual Studio/PowerShell method second. However, there is no explicit mention of Linux or cross-platform development environments beyond the .NET CLI, and no Linux-specific guidance or examples are provided. The focus on Visual Studio and PowerShell may implicitly favor Windows users, and the absence of Linux terminal or editor examples (such as VS Code or bash) further highlights this bias.

Recommendations:

Explicitly mention that the .NET Core CLI commands work on Linux, macOS, and Windows, and recommend it as the primary cross-platform method.
Add Linux-specific instructions or examples, such as using bash or zsh terminals, and reference popular Linux editors (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
Clarify that the Package Manager Console is only available in Visual Studio on Windows, and suggest alternatives for Linux users.
Include a note or section on verifying package installation in Linux environments.
Ensure parity in tooling and workflow coverage for both Windows and Linux users throughout the documentation.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a strong Windows bias by providing only PowerShell examples for per-app scaling, referencing Azure PowerShell cmdlets exclusively, and omitting equivalent CLI or scripting instructions for Linux or cross-platform users. There are no Bash, Azure CLI, or Linux-native tool examples, and the PowerShell approach is presented first and as the primary method. This may hinder accessibility for users on Linux or macOS systems.

Recommendations:

Add equivalent Azure CLI (az) examples for all PowerShell commands, showing how to create and configure per-app scaling using the CLI.
Include Bash script examples where appropriate, especially for configuring app settings or deploying ARM templates.
Clearly indicate that PowerShell is not required and that all operations can be performed cross-platform using the Azure CLI.
Reorder sections or provide parallel examples so that Linux/cross-platform methods are not secondary to Windows/PowerShell.
Mention and link to documentation on installing and using Azure CLI on Linux/macOS.
If possible, provide screenshots or walkthroughs for the Azure Portal UI, which is platform-agnostic.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell in the 'Next steps' section for creating an autoscaling, zone redundant application gateway. There are no equivalent instructions or links for Linux users (e.g., using Azure CLI, ARM templates, or Bicep), and PowerShell is a Windows-centric tool. This prioritizes Windows tooling and patterns, potentially excluding or inconveniencing users on Linux or macOS.

Recommendations:

Add equivalent Azure CLI tutorials and links for creating autoscaling, zone redundant application gateways.
Include ARM template and/or Bicep deployment examples for cross-platform parity.
Ensure that references to tooling in 'Next steps' and throughout the documentation are balanced, mentioning both PowerShell and CLI (and other cross-platform options) together.
Where possible, provide code snippets for both PowerShell and CLI in the main documentation body, not just in linked tutorials.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exhibits a Windows bias by prioritizing Windows-specific tools and workflows (such as Visual Studio deployment to Windows App Service) and omitting explicit Linux deployment examples or Linux-specific considerations. Visual Studio and Windows App Service are mentioned before cross-platform or Linux-native tools, and there is no mention of Linux command-line deployment, file permissions, or troubleshooting on Linux-based App Service plans.

Recommendations:

Add explicit examples and instructions for deploying WebJobs to Linux-based App Service plans, including command-line (Azure CLI) and zip deployment workflows.
Include references to cross-platform development environments (such as VS Code) and clarify any differences in deployment or monitoring on Linux vs. Windows App Service.
Mention Linux-specific considerations, such as file permissions, supported runtimes, and troubleshooting steps for Linux environments.
Reorder deployment options to present cross-platform and automation-first approaches (e.g., Azure CLI, GitHub Actions) before Windows-specific tools like Visual Studio.
Ensure that all tooling and monitoring references (such as Kudu) are clarified for both Windows and Linux App Service plans, noting any 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 PowerShell examples are presented as the only scripting/automation option, and the documentation references Windows-centric tools and patterns (such as PowerShell cmdlets) without mentioning or prioritizing Linux-friendly alternatives. The structure and ordering of examples also place PowerShell before any mention of CLI, and in some sections, CLI is omitted entirely.

Recommendations:

Add equivalent Azure CLI (az) command examples alongside all PowerShell examples to ensure Linux and macOS users have clear guidance.
Where scripting is demonstrated, provide both PowerShell and Bash (or at least CLI) scripts.
In tabbed example sections, present Azure CLI before or alongside PowerShell to avoid implicit prioritization of Windows tools.
Explicitly mention that all operations can be performed from any OS using Azure CLI, and provide links to CLI documentation.
Audit for any terminology or references that assume a Windows environment and update to be OS-neutral where possible.

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 policies. There is a lack of Linux/Unix-specific examples or parity in instructions, and PowerShell is mentioned before or instead of cross-platform or Linux-native tools. The 'Next steps' section links only to a PowerShell-based guide, and throughout the page, PowerShell is referenced as the main interface for configuration and information retrieval, with no mention of Bash, Azure CLI on Linux, or REST API usage from non-Windows environments.

Recommendations:

Provide equivalent Linux/Bash/Azure CLI examples alongside or before PowerShell examples for all configuration and retrieval tasks.
Explicitly mention that Azure CLI and REST API can be used from any platform, and provide sample commands for Linux/macOS users.
In the 'Next steps' section, link to both PowerShell and Azure CLI (and/or REST API) guides for configuring TLS policy.
Avoid referencing PowerShell as the default or only method; instead, present cross-platform tools (like Azure CLI) first or equally.
Add a section or callout for Linux/macOS administrators, highlighting any platform-specific considerations or steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation displays a mild Windows bias, particularly in the Helm installation section, where Windows installation instructions (including a PowerShell/winget example) are presented before Linux, and Windows-specific tooling (winget) is mentioned explicitly. The Linux installation is covered, but the ordering and detail favor Windows. The rest of the guide uses cross-platform tools (Azure CLI, Helm, kubectl) and Bash-style scripting, which is generally Linux-friendly, but the explicit Windows-first ordering and inclusion of Windows package manager commands indicate a subtle bias.

Recommendations:

Present Linux and Windows installation instructions in parallel tabs or in the same order (Linux first or alphabetical), to avoid privileging Windows.
Provide equivalent package manager commands for Linux (e.g., apt, yum, snap) alongside the Windows winget example for Helm installation.
Ensure that all examples and instructions are equally detailed for both Windows and Linux, including troubleshooting notes.
Where possible, use cross-platform shell syntax or clearly mark which commands are for which OS.
Consider adding explicit macOS instructions where relevant, to further improve cross-platform parity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by presenting Azure PowerShell instructions before Azure CLI, referencing PowerShell-specific cmdlets for status checks even in CLI sections, and omitting explicit Linux shell or cross-platform command-line examples. The workflow and screenshots are oriented around the Azure Portal and PowerShell, which are more familiar to Windows users, with no mention of Bash, Linux-specific tooling, or guidance for non-Windows environments.

Recommendations:

Present Azure CLI instructions before or alongside PowerShell to emphasize cross-platform support.
Ensure all command-line examples are shown in both PowerShell and Bash (Linux/macOS) syntax, especially for status checks (e.g., use 'az feature show' instead of referencing Get-AzProviderFeature in CLI sections).
Include explicit guidance or notes for Linux/macOS users, such as terminal screenshots or shell-specific tips.
Avoid referencing PowerShell cmdlets in CLI sections; use the appropriate CLI commands for status checks and other operations.
Where possible, provide ARM/Bicep/Terraform examples in addition to Portal, PowerShell, and CLI to further enhance platform neutrality.

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 alternative tools or platforms, such as Azure CLI or Bash scripts. There are no Linux or cross-platform migration instructions, and the only automation method discussed is PowerShell, which is most commonly associated with Windows environments.

Recommendations:

Provide equivalent Azure CLI (az) commands and scripts for all migration steps, ensuring Linux and macOS users have clear, first-class guidance.
Explicitly mention that migration can be performed from any platform (Windows, Linux, macOS) and clarify any platform-specific requirements or limitations.
Include Bash script examples or references for common migration tasks, especially for configuration and traffic migration.
If certain features are only available in PowerShell, state this clearly and provide a roadmap or alternatives for non-Windows users.
Add a section comparing PowerShell and CLI approaches, helping users choose the best tool for their environment.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exhibits a strong Windows bias. PowerShell is the only command-line example provided for configuring Key Vault integration, with no equivalent Azure CLI (cross-platform) or Bash/Linux shell examples. The 'Next steps' section exclusively links to a PowerShell-based guide. Throughout the document, PowerShell and ARM templates are mentioned before the Azure CLI, and there are no Linux- or macOS-specific instructions or examples. This may hinder Linux users or those preferring cross-platform tools.

Recommendations:

Provide equivalent Azure CLI examples for all PowerShell command snippets, especially for critical tasks like referencing Key Vault secrets and configuring Application Gateway.
In the 'Next steps' section, include links to Azure CLI and/or Bash-based guides alongside PowerShell guides.
When listing tools or methods (e.g., PowerShell, CLI, ARM templates), mention Azure CLI first or equally, and clarify that all steps can be performed cross-platform.
Add explicit Linux/macOS shell examples where relevant, or note that all steps are supported on non-Windows platforms.
Review screenshots and UI instructions to ensure they are not Windows-specific, or add notes for Linux/macOS users if differences exist.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ 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, with no explicit mention of Linux or cross-platform alternatives. The CLI examples provided use Azure CLI, but the commands shown are actually PowerShell cmdlets (e.g., Set-AzContext), which are not native to Linux/macOS environments. There is no mention of Bash, Cloud Shell, or Linux-specific workflows, and the only migration script referenced is a PowerShell script. This may create the impression that Windows or PowerShell is the default or only supported environment.

Recommendations:

Provide equivalent Bash/Azure CLI examples for all PowerShell commands, especially for registration, unregistration, and migration tasks.
Clarify which commands are PowerShell-specific and offer cross-platform alternatives where possible.
Reference Azure Cloud Shell as a cross-platform option for both PowerShell and Bash users.
Include explicit instructions or links for Linux/macOS users, ensuring parity in tooling and workflow documentation.
If migration scripts are only available in PowerShell, note this limitation and provide guidance or a roadmap for Linux support.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation shows a Windows bias by providing PowerShell as the only CLI example for checking settings, exclusively recommending Fiddler (a Windows-centric tool) for network capture, and referencing Windows installation patterns (e.g., 'Run as administrator'). There are no Linux or cross-platform CLI examples (such as Azure CLI or Bash), nor are Linux-friendly network tools (like tcpdump, Wireshark, or curl) mentioned. The step-by-step instructions and screenshots are all based on Windows environments.

Recommendations:

Provide Azure CLI (az) and/or REST API examples alongside PowerShell for configuration checks, with sample commands for Linux/macOS users.
Include Linux-friendly network capture and debugging tools (e.g., tcpdump, Wireshark, curl, httpie) as alternatives to Fiddler, with brief usage instructions.
When referencing installation steps, add Linux/macOS equivalents (e.g., 'use sudo to install', 'install via apt/yum/brew').
Add screenshots or terminal output examples from Linux environments where relevant.
Use neutral language such as 'your preferred web debugger' and list both Windows and Linux options.
Ensure that troubleshooting steps and tool recommendations are platform-agnostic or provide parity for all major operating systems.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a bias towards Windows and PowerShell-centric automation. PowerShell and DSC (Desired State Configuration) are repeatedly emphasized as the primary or default automation and configuration technologies, with Linux support mentioned only in general terms or as an afterthought. Examples, modules, and galleries focus on PowerShell, and there is a lack of concrete Linux-specific examples or equivalent tooling references. Windows tools and scenarios (e.g., Active Directory, SQL Server, SharePoint) are explicitly named, while Linux-specific tools, patterns, or use cases are not highlighted.

Recommendations:

Provide Linux-specific examples and scenarios alongside Windows ones, such as managing Linux services, using Bash or Python runbooks for Linux tasks, and integrating with Linux-native tools (e.g., systemd, cron, logrotate).
Mention Linux configuration management tools or equivalents (e.g., Ansible, Chef, native Linux DSC support) where PowerShell DSC is discussed.
Ensure that references to modules, galleries, and shared resources include Python and Bash examples, and highlight any Linux-specific modules or packages available.
Balance scenario descriptions by including Linux workloads and open-source technologies (e.g., Apache, NGINX, MySQL, PostgreSQL) in addition to Windows-centric ones.
Where Windows tools or patterns are mentioned (e.g., PowerShell Gallery, Active Directory), provide Linux equivalents or alternatives.
Explicitly state the parity or differences in feature support between Windows and Linux for Azure Automation, and link to Linux-specific guidance where available.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a moderate Windows bias. While the core certificate generation steps use OpenSSL (a cross-platform tool) and mention both Windows and Linux, several sections prioritize or exclusively provide Windows-centric instructions and tools. The IIS section is detailed and links to Windows Server documentation, while Apache and NGINX are only given brief configuration snippets. The Azure PowerShell example is provided in detail, but there is no equivalent Azure CLI (cross-platform) example. Instructions for adding the root certificate to the trusted store are vague and do not provide Linux-specific guidance. The hosts file editing note links to a generic article, not platform-specific instructions.

Recommendations:

Provide Azure CLI examples alongside Azure PowerShell for uploading certificates and configuring Application Gateway, as Azure CLI is cross-platform.
Expand the Linux guidance for adding the root certificate to the trusted root store (e.g., update-ca-certificates on Ubuntu, trust anchors on RHEL, etc.).
Offer parity in web server configuration instructions: include links to official documentation for Apache and NGINX, similar to the detailed IIS section.
When referencing file paths (e.g., C:\Users\...), provide Linux equivalents or use generic paths.
When mentioning editing the hosts file, provide explicit instructions or links for both Windows and Linux.
Review the order of presentation to avoid always listing Windows tools or instructions first.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a moderate Windows bias. Windows instructions, tools, and examples are often presented before their Linux equivalents, and PowerShell is the primary scripting language shown in code samples. Several sections (such as credential management and runbook authentication) provide detailed PowerShell/Windows-centric examples, while Linux examples are less detailed or missing. Windows-specific tools and paths (e.g., Control Panel, cert store locations) are referenced more frequently and with more depth than their Linux counterparts.

Recommendations:

Present Windows and Linux instructions in parallel or with equal prominence, rather than listing Windows first in each section.
Provide Linux-specific code samples (e.g., Bash, Python) wherever PowerShell examples are given, especially for runbook authentication and management.
Include Linux-native tools and workflows (e.g., use of environment variables, certificate/key management) with the same level of detail as Windows tools.
Where possible, use cross-platform language and avoid Windows-specific terminology unless necessary.
Expand Linux sections to match the granularity and clarity of Windows instructions, particularly for credential management, runbook signing, and troubleshooting.
Add explicit Linux examples for starting runbooks via CLI (e.g., Azure CLI or Bash scripts), not just PowerShell.
Ensure that troubleshooting and logging sections provide Linux log paths and diagnostic methods with the same detail as Windows.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing and extensively detailing PowerShell (a Windows-centric technology) and Windows-specific patterns. Windows tools, file paths (e.g., C:\modules), and environment variables are referenced throughout, with examples and troubleshooting steps almost exclusively using Windows conventions. Linux support is mentioned, but Linux-specific examples, troubleshooting, or parity guidance are largely absent. The Python section briefly mentions Linux, but most operational details and examples are Windows-focused.

Recommendations:

Provide Linux-specific examples and troubleshooting steps, especially for Hybrid Runbook Workers and file path references.
When discussing file paths, include both Windows (C:\...) and Linux (/usr/...) equivalents.
Expand on Linux support for PowerShell runbooks, including any differences in module management, environment variables, and known issues.
In sections about environment variables and Python versions, clarify the behavior and configuration for Linux Hybrid Workers, not just Windows.
Ensure parity in examples: for every PowerShell/Windows example, provide an equivalent for Linux/Python where applicable.
Highlight any limitations or best practices unique to Linux environments, not just those for Windows.
Reorder or balance the presentation so that Linux and Windows are treated equally, rather than Windows/PowerShell being the default or primary focus.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a clear 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 tools and patterns (e.g., PowerShell Gallery, .zip modules, Get-Module cmdlet) are mentioned and illustrated, while Linux/Python equivalents are only briefly referenced or relegated to notes. There are no concrete Linux or Python-focused examples, and the documentation assumes familiarity with Windows-centric tooling.

Recommendations:

Provide parallel, concrete examples for Python runbooks, including REST API payloads and portal workflows.
Include Linux/Python-specific instructions and screenshots where relevant (e.g., uploading .whl files, using pip or other Linux-native tools).
Mention Python/Linux options before or alongside PowerShell/Windows options, rather than as afterthoughts or notes.
Demonstrate how to view installed Python packages in a runbook, similar to the PowerShell Get-Module example.
Clarify when steps or tools are Windows/PowerShell-specific and provide Linux/Python alternatives.
Balance the documentation structure so that both PowerShell and Python/Linux users can easily find relevant guidance.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation exhibits several forms of Windows bias. In the section on generating wheel files, the Windows (Python 3.8) workflow is presented after the Linux (Python 3.10) workflow, but both are covered. However, in the PowerShell cmdlets section, only Windows PowerShell/Az PowerShell examples are provided for managing Python packages, with no equivalent CLI or bash/Linux-native commands. The documentation also references Windows-specific architectures (win_amd64) and tools (PowerShell), and does not provide parity for Linux users in terms of automation tooling or command-line management. There are no examples using Azure CLI, Bash, or Linux-native scripting for package management, and the PowerShell section is extensive and detailed, reinforcing a Windows-centric approach.

Recommendations:

Provide Azure CLI and/or Bash examples for managing Python packages in Azure Automation, alongside or before PowerShell examples.
Include Linux-native command-line workflows for package management tasks (add, list, remove, update), not just Windows/PowerShell.
Ensure that all automation and scripting examples are available for both Windows and Linux users, or clearly indicate platform-specific limitations.
Where possible, use cross-platform tools and commands, or provide equivalent instructions for both operating systems.
Explicitly mention when a feature or tool is Windows-only, and suggest alternatives for Linux users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ windows_heavy_scenarios

Summary:

The documentation generally provides parity between Windows and Linux for most troubleshooting steps, but there is a noticeable Windows-first bias. In several sections, Windows examples, tools, and troubleshooting steps are listed before their Linux equivalents. Some scenarios are described only for Windows (e.g., registry and event log troubleshooting, PowerShell scripts, UAC issues), and Windows-specific tools (like PowerShell scripts and registry edits) are prominent. Linux steps are present but sometimes less detailed or appear after Windows steps. There are also more scenario-specific troubleshooting sections for Windows than for Linux.

Recommendations:

Alternate the order of Windows and Linux instructions throughout the document to avoid always listing Windows first.
Where possible, provide Linux equivalents for all troubleshooting steps, especially for scenarios currently described only for Windows (e.g., registry, event logs, UAC).
Ensure Linux troubleshooting steps are as detailed and explicit as Windows steps, including command-line examples and log file locations.
Include Linux-specific troubleshooting scenarios (e.g., SELinux/AppArmor issues, systemd service failures, permission issues) to match the depth of Windows coverage.
Where PowerShell scripts are provided for Windows, consider providing Bash or Python scripts for Linux where appropriate.
Review the language and structure to ensure Linux is treated as a first-class platform, not as an afterthought.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation focuses exclusively on configuration steps for Visual Studio and Visual Studio Code, both of which are primarily associated with Windows environments. The Visual Studio instructions are Windows-specific, and there are no examples or guidance for configuring the Roslyn Analyzer in Linux-native editors or workflows (such as JetBrains Rider, command-line tools, or CI pipelines). There is no mention of Linux or cross-platform command-line usage.

Recommendations:

Add instructions for configuring and running the Roslyn Analyzer using .NET CLI commands (e.g., dotnet build, dotnet format) that work across Windows, Linux, and macOS.
Include examples for popular Linux-friendly editors such as JetBrains Rider or Vim/Emacs with OmniSharp.
Mention how to use the analyzer in CI/CD pipelines (e.g., GitHub Actions, Azure Pipelines) that run on Linux agents.
Clarify that Visual Studio Code is cross-platform and provide Linux/macOS-specific notes or screenshots where relevant.
Explicitly state that the analyzer works on all platforms supported by .NET and provide parity in setup instructions.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation exhibits a moderate Windows bias. Windows-specific tools, settings, and instructions are often mentioned before or more prominently than their Linux equivalents. Some examples and configuration steps are Windows-centric, with Linux alternatives either mentioned later, less prominently, or omitted. PowerShell and Visual Studio (Windows) are highlighted as primary tools, while Linux/CLI workflows are less emphasized or lack parity in detail.

Recommendations:

Ensure all instructions and examples that reference Windows tools (e.g., Visual Studio, PowerShell) are immediately accompanied by equivalent Linux/CLI alternatives, not just referenced later or in separate tabs.
When listing deployment and configuration methods, present Linux/CLI options (e.g., Azure CLI, VS Code, Bash) before or alongside Windows/PowerShell options, not after.
Add explicit Linux/Bash examples wherever PowerShell or Windows-specific commands are shown, especially for project setup, deployment, and configuration.
Clarify when a feature or tool is Windows-only, and provide clear Linux alternatives or workarounds.
Balance the prominence of Visual Studio and Visual Studio Code, highlighting VS Code and CLI as cross-platform first-class options.
Review all code snippets and ensure that any file paths, environment variables, or configuration steps are shown for both Windows and Linux environments.
Where tabs are used for OS-specific content, default to the user's OS if possible, or present Linux and Windows equally.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates some Windows bias, particularly in the ordering and inclusion of examples for command-line usage. In several places, Windows-specific shells (Cmd, PowerShell) are presented before or more prominently than Linux/macOS equivalents. PowerShell is treated as a first-class language option, and Windows command-line patterns are detailed alongside or before bash equivalents. However, Linux/macOS instructions are present, and the use of cross-platform tools like curl and azd is consistent.

Recommendations:

Ensure that Linux/macOS examples are always presented first or at least with equal prominence to Windows examples, especially in tabbed code blocks.
Where possible, use neutral terms like 'terminal' instead of 'command prompt' or clarify that both are supported.
For PowerShell, clarify its availability on Linux/macOS or provide bash/zsh equivalents where appropriate.
In sections where multiple shell examples are given, consider defaulting to bash (Linux/macOS) first, as it is more universally available across platforms.
Audit all code snippets and instructions to ensure that Linux users are not required to mentally translate from Windows-specific instructions.
Explicitly mention cross-platform compatibility for all tools and commands, and provide troubleshooting tips for common Linux/macOS issues.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a strong Windows bias, primarily through exclusive use of Windows/PowerShell commands for Active Directory management, references to Windows-specific tools and policies (such as Group Policy and Windows registry keys), and a lack of Linux or cross-platform examples for managing AD connections. Windows terminology and tools are mentioned first or exclusively, with no equivalent instructions for Linux-based environments or tools like Samba or Linux-based AD management.

Recommendations:

Provide equivalent Linux-based command examples (e.g., using Samba tools like 'samba-tool', 'net ads', or 'ldapmodify') for managing Kerberos encryption types and AD user properties.
Include instructions for configuring Kerberos and LDAP settings on Linux clients, such as editing '/etc/krb5.conf' and '/etc/sssd/sssd.conf', and using 'kadmin' or 'ktutil' for keytab and encryption management.
Reference Linux-compatible tools and methods (e.g., 'realm', 'adcli', 'sssd') alongside Windows tools when discussing AD domain joins, account management, and encryption settings.
When discussing Group Policy or registry settings, mention equivalent Linux configuration files or policies, or clarify if certain settings are not applicable to Linux environments.
Add Linux-focused troubleshooting steps and examples for common scenarios (e.g., LDAP query timeouts, Kerberos authentication failures) to ensure parity.
Structure examples so that both Windows and Linux approaches are presented side-by-side where possible, or at least ensure Linux is not omitted.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a mild Windows bias in several areas. While the overall content is cross-platform and Linux is well-supported (especially for hosting), there are multiple instances where Windows terminology, tools, and workflows are mentioned first or exclusively. Specifically, references to 'command prompt', 'Terminal or command prompt', and the recommendation to use remote build when developing on Windows, as well as the use of 'cmd' in folder structure examples, indicate a Windows-centric perspective. There is also a lack of explicit Linux shell (bash) examples or terminology, and no mention of Linux-specific tools or workflows, even though Azure Functions Python hosting is Linux-only.

Recommendations:

Use neutral or inclusive terminology such as 'terminal' or 'shell' instead of 'command prompt', or mention both (e.g., 'terminal (Linux/macOS) or command prompt (Windows)').
Provide explicit bash/zsh shell examples alongside or instead of Windows command prompt examples, especially in code blocks and folder structure listings.
When referencing development environments, list cross-platform options first or in parallel (e.g., 'Terminal (Linux/macOS), Command Prompt or PowerShell (Windows)').
Clarify that 'cmd' in folder structure listings is for illustration, and provide equivalent bash commands or tree outputs.
Highlight Linux development workflows and tools (e.g., bash, zsh, Linux package managers) where appropriate, especially since Azure Functions Python apps are hosted on Linux.
If recommending remote build for Windows users, also provide guidance for Linux/macOS users, and clarify any differences in workflow or recommendations.
Audit all references to Windows-specific tools (e.g., PowerShell, Command Prompt) and ensure Linux equivalents are mentioned with equal prominence.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Bash and Windows CMD examples for command-line operations, but consistently lists Windows CMD examples immediately after Bash, sometimes with more detail. There are no explicit PowerShell examples, but the presence of 'command prompt' and 'CMD' tabs, and the absence of Linux-specific troubleshooting or environment details, indicate a mild Windows-first bias. There are no Linux-specific tools or troubleshooting sections, and some instructions (e.g., setting JAVA_HOME) do not clarify OS-specific differences. The documentation does not provide parity for Linux-specific issues or workflows, and does not mention WSL or other Linux environments for Windows users.

Recommendations:

Ensure that Bash examples are always presented first, or at least alternate the order with CMD to avoid implicit prioritization.
Add explicit Linux troubleshooting sections, especially for environment variable setup (e.g., JAVA_HOME), file permissions, and common Linux-specific issues.
Include PowerShell examples only if they are necessary, and always provide equivalent Bash and CMD examples.
Clarify in all environment variable and path instructions how they differ between Windows and Linux.
Mention WSL as an option for Windows users who prefer a Linux-like environment.
Where IDEs are mentioned, note any OS-specific setup steps or limitations.
Add a section or note about deploying and running on Linux, including any differences in file system case sensitivity, permissions, or supported features.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation page demonstrates a moderate Windows bias. PowerShell and Azure PowerShell commands are given significant prominence, both in the registration of features and in the main procedural sections. In the 'Edit network features' section, PowerShell is presented as a primary method alongside Azure CLI and REST API, but PowerShell commands and terminology (e.g., Register-AzProviderFeature, Get-AzProviderFeature) are referenced first and most frequently. There is no mention of Linux-specific shell usage or examples, and the PowerShell tab is present before REST API and Terraform. The Azure CLI is included, which is cross-platform, but there are no explicit Linux/Bash shell examples or guidance for Linux users. The documentation also references Windows-centric tools and patterns (e.g., PowerShell, Azure PowerShell modules) without equivalent Linux-focused context.

Recommendations:

Add explicit Bash/Linux shell examples for all CLI commands, showing usage in a Linux terminal environment.
Clarify that Azure CLI commands are cross-platform and provide sample invocations in both Windows (CMD/PowerShell) and Linux (Bash) contexts.
Reorder the command tabs (where possible) to present Azure CLI or REST API before PowerShell, or at least alternate the order to avoid Windows-first bias.
Include notes or sections addressing Linux users, such as prerequisites for running Azure CLI on Linux, and troubleshooting tips relevant to Linux environments.
Where PowerShell is referenced, provide equivalent Bash scripts or commands for Linux users, especially for automation scenarios.
Review screenshots and UI references to ensure they are not exclusively from Windows environments (if applicable).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a mild Windows bias. In sections describing how to create and manage snapshots, the order of tooling references consistently lists PowerShell before Linux-native tools (e.g., Azure CLI), and explicit PowerShell module links are provided. There are no explicit Linux/Unix shell or scripting examples, nor are Linux tools or patterns highlighted. The only scripting example referenced is for SQL Server (a Windows-centric workload). There is no mention of Linux-specific client access patterns or examples, and no screenshots or walkthroughs for Linux environments.

Recommendations:

When listing tools or interfaces (Azure portal, REST API, CLI, PowerShell), alternate the order or explicitly mention Linux/Unix shell usage alongside PowerShell.
Provide example commands for both PowerShell and Bash/Azure CLI, especially in sections about creating, restoring, or deleting snapshots.
Include references or links to Linux/Unix scripting guides for Azure NetApp Files, not just Windows/PowerShell.
Add examples or screenshots showing snapshot access and file restore from Linux clients (e.g., using NFS mounts and standard Linux commands like cp, ls, etc.).
Reference Linux/Unix workloads and use cases (e.g., SAP HANA on Linux) more explicitly in relevant sections.
Ensure parity in documentation coverage for both Windows (SMB) and Linux (NFS) protocols, including client-side restore operations.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by exclusively referencing Windows tools (such as Active Directory Users and Computers MMC snap-in) for managing LDAP POSIX attributes, providing step-by-step instructions only for Windows environments, and omitting equivalent Linux-based methods or tools for these tasks. Additionally, the order of presentation and examples prioritizes Windows terminology and workflows, with Linux/NFS client configuration relegated to a brief reference link without in-page guidance.

Recommendations:

Add equivalent Linux-based instructions for managing LDAP POSIX attributes, such as using ldapmodify, ldapadd, or graphical tools like Apache Directory Studio.
Provide example commands or screenshots for configuring POSIX attributes on Linux LDAP servers (e.g., OpenLDAP).
Ensure that both Windows and Linux tools are mentioned together, or alternate their order to avoid Windows-first bias.
Expand the 'Configure the NFS client' section to include at least a basic example or summary inline, not just a link.
Where Windows-specific features or limitations are discussed (e.g., non-browsable share), clarify Linux/NFS client behavior for parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page primarily provides Azure PowerShell commands for feature registration and management, with only a brief mention of Azure CLI as an alternative. There are no explicit Linux shell or cross-platform examples, and the PowerShell approach is presented first and in detail, which may disadvantage Linux users or those who prefer CLI tools.

Recommendations:

Provide full Azure CLI command examples alongside PowerShell, including output examples and usage notes.
List Azure CLI (cross-platform) instructions before or alongside PowerShell to avoid Windows-first bias.
Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide guidance for Linux users.
If applicable, include bash script examples or instructions for automation on Linux.
Clarify any differences or limitations between PowerShell and CLI approaches.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by presenting Azure PowerShell commands as the primary method for feature registration and status checking, with Azure CLI (cross-platform) only mentioned secondarily and without explicit examples. There are no Linux- or macOS-specific instructions or screenshots, and the initial automation steps are shown only with PowerShell, which is most familiar to Windows users.

Recommendations:

Provide Azure CLI examples alongside or before PowerShell examples for all command-line steps, especially for feature registration and status checking.
Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
Include screenshots or instructions that are not specific to the Windows Azure Portal experience, or clarify that the steps are identical across platforms.
Add a section or callout for Linux/macOS users, confirming that all steps can be performed from those environments using Azure CLI.
Ensure parity in automation examples by offering Bash shell scripts or command sequences where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation generally presents Windows/SMB concepts and terminology before or with more detail than Linux/NFS equivalents, especially in areas like authentication, permissions, and supported tools. Windows-centric tools and patterns (Active Directory, NTFS ACLs, Kerberos/NTLM, SID translation) are discussed in depth, while Linux/UNIX tools (Samba, POSIX ACLs, idmapd, nfs-utils) are mentioned less prominently or only in passing. There are no explicit Linux command-line examples for NFS or dual-protocol scenarios, and official support is only noted for Windows/macOS SMB clients, not Linux/Samba. This may leave Linux administrators with less actionable guidance.

Recommendations:

Provide parallel Linux/UNIX command-line examples (e.g., mounting NFS/SMB shares, checking permissions, troubleshooting identity mapping) alongside any Windows/Powershell examples.
Discuss Linux/UNIX tools and patterns (such as Samba configuration, POSIX ACL management, idmapd, nfs-utils) in equal depth as Windows tools (Active Directory, NTFS ACLs).
Clarify support status and best practices for Linux/Samba SMB clients, including any limitations or recommended configurations.
Ensure that Linux/UNIX terminology (e.g., POSIX ACLs, mode bits, LDAP integration) is introduced and explained with the same prominence as Windows/NTFS concepts.
Add troubleshooting and configuration guidance for common Linux/UNIX scenarios, such as resolving UID/GID mismatches, configuring LDAP, or managing dual-protocol permissions from a Linux perspective.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exhibits a Windows bias in the section addressing NFS access from Windows clients. It provides a PowerShell command and a Windows-specific mount example, but does not offer equivalent Linux commands or examples. Additionally, Windows tooling and patterns are mentioned exclusively in this context, and Linux is not given parity in the troubleshooting or configuration guidance for NFS client behavior.

Recommendations:

For every Windows-specific example (such as PowerShell commands and mount instructions), provide equivalent Linux shell commands and mount examples.
In the section on troubleshooting NFS client performance (e.g., CaseSensitiveLookup), include Linux-specific advice or clarify if the issue is Windows-only.
When discussing persistent NFS mounts, provide both Windows and Linux configuration steps or clearly state if a feature is not applicable to one platform.
Ensure that Linux tools and patterns are mentioned alongside Windows tools, and avoid presenting Windows solutions first or exclusively.
Review the documentation for other subtle Windows-first language or assumptions, and update to ensure cross-platform parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing Azure PowerShell commands as the primary example for feature registration, with Azure CLI (cross-platform) commands only mentioned in passing and without explicit usage examples. There are no Linux- or macOS-specific instructions or screenshots, and the UI instructions reference right-click actions, which are more typical of Windows environments. No Linux shell or bash equivalents are shown for command-line operations.

Recommendations:

Provide explicit Azure CLI (az) command examples alongside PowerShell for all registration and configuration steps, including sample output.
Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide bash/zsh shell usage examples where appropriate.
Avoid UI instructions that assume a Windows-style right-click; instead, describe actions in a platform-neutral way (e.g., 'open the context menu for the capacity pool').
Include screenshots or instructions that are not specific to Windows UI conventions.
Add a section or callout for Linux/macOS users, highlighting any differences or confirming parity.

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 the Windows GUI, referencing Windows administration hosts, and using Azure PowerShell cmdlets as the primary example for feature registration. While Linux/NFS is mentioned, equivalent step-by-step instructions for setting Audit ACEs on Linux are missing, and the documentation does not provide Linux CLI or GUI examples for these tasks. Azure CLI is mentioned only as an alternative, not the primary method.

Recommendations:

Provide step-by-step instructions for setting Audit ACEs on NFSv4.1 volumes from a Linux client, including example commands (e.g., using nfs4_setfacl).
Include Linux CLI examples for registering the feature (using az CLI) alongside or before PowerShell examples.
Balance the order of presentation so that Linux/NFS instructions are given equal prominence to Windows/SMB instructions.
Reference common Linux tools and patterns where appropriate, not just Windows tools and workflows.
Ensure all key workflows (enabling/disabling logs, setting permissions) have both Windows and Linux examples.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation only describes how to delete resources using the Azure portal, which is a GUI-based approach commonly associated with Windows workflows. There are no command-line examples (such as Azure CLI or Bash) that would be more familiar to Linux users, nor is there mention of Powershell or Windows-specific tools, but the lack of Linux-friendly instructions constitutes a subtle Windows-first bias.

Recommendations:

Add Azure CLI command-line examples for deleting the resource group (e.g., `az group delete --name <resource-group-name>`), which can be run on both Windows and Linux.
Include Bash and/or PowerShell script examples for automation.
Explicitly mention that the Azure portal is cross-platform, but provide parity by showing both GUI and CLI methods.
Ensure that screenshots and instructions do not assume a Windows environment (e.g., avoid showing Windows-only UI elements or terminology).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a 'windows_first' bias by providing detailed ASP.NET and ASP.NET Web Forms (Windows-centric) code samples before other platforms, and by referencing the HttpRequest.ClientCertificate property, which is specific to Windows/IIS environments. There are no explicit Linux command-line examples (e.g., using curl or OpenSSL to test mutual TLS), nor is there mention of Linux-specific tools or patterns for certificate management or validation. The focus is on Azure portal, Azure CLI, Bicep, and ARM templates for configuration, which are cross-platform, but the application code samples prioritize Windows/.NET technologies.

Recommendations:

Add Linux command-line examples (e.g., using curl or OpenSSL) to demonstrate how to test mutual TLS authentication from a Linux environment.
Include a section or note on how to access and validate client certificates in common Linux web servers (e.g., Nginx, Apache) when running on App Service for Linux.
Provide parity in code sample ordering by rotating or randomizing the order of language/framework examples, or by starting with a cross-platform language (e.g., Node.js or Python) rather than Windows/.NET.
Mention any Linux-specific considerations or troubleshooting steps for mutual TLS in Azure App Service, especially for App Service for Linux.
Reference cross-platform certificate management tools (e.g., OpenSSL) alongside Windows-specific APIs or tools.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page is generally cross-platform and avoids OS-specific instructions, but there is a notable instance of Windows bias: when instructing users to clear the DNS cache, only the Windows command ('ipconfig /flushdns') is mentioned, with no equivalent Linux or macOS instructions. No PowerShell-specific scripts or Windows-only tools are referenced elsewhere, and the portal-based workflow is platform-agnostic.

Recommendations:

When providing troubleshooting steps such as clearing the 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').
Review any automation or scripting sections to ensure that examples are not limited to Windows batch or PowerShell, and provide Bash or cross-platform alternatives if applicable.
Continue to avoid referencing Windows-only tools or patterns unless absolutely necessary, and always provide parity for Linux/macOS users.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation avoids explicit Windows-only tools and PowerShell, but it exhibits subtle Windows bias by omitting any mention of Linux-specific development environments, deployment patterns, or troubleshooting. The use of GitHub Codespaces (which is cross-platform) and Bash commands is positive, but there is no discussion of running or deploying the app on a local Linux machine, nor are there instructions for Linux users who may not use Codespaces. The documentation assumes Azure CLI and .NET CLI are available, but doesn't address installation or environment setup on Linux, nor does it mention WSL or Linux-native workflows. All screenshots and UI references are Azure-centric, with no nod to Linux desktop environments or terminal conventions.

Recommendations:

Add a section or notes on how to set up the development environment on a local Linux machine, including .NET SDK and Azure CLI installation instructions for Linux.
Explicitly state that all CLI commands work on Linux, macOS, and Windows, and provide troubleshooting tips for common Linux-specific issues (e.g., permissions, port usage).
Include at least one example of running the sample app outside Codespaces, such as on Ubuntu or another popular Linux distribution.
Mention that the Azure CLI and .NET CLI are cross-platform, and provide links to Linux installation guides.
If screenshots of terminals are included, show at least one from a Linux terminal emulator.
Clarify that the instructions do not require Windows or PowerShell, and highlight any differences (if any) for Linux users.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation provides both Azure CLI and PowerShell examples for all programmatic tasks, but PowerShell is given equal or greater prominence, including in advanced scenarios and inline code blocks. PowerShell is a Windows-centric tool, and its inclusion as a primary example can be seen as a Windows bias, especially since Linux-native scripting options (such as Bash or shell scripts) are not explicitly mentioned. Additionally, in some advanced scenario sections, PowerShell examples are shown before or without equivalent CLI examples, reinforcing a 'windows_first' pattern.

Recommendations:

Ensure that for every PowerShell example, an equivalent Azure CLI example is provided, especially in advanced scenario sections (e.g., multi-source rules, Azure Front Door filtering).
Where possible, provide Bash/shell script snippets for common Linux workflows, or clarify that Azure CLI commands can be run natively on Linux/macOS.
In introductory and advanced sections, present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more native to Linux environments.
Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and consider linking to guidance on installing and using Azure CLI on Linux.
Avoid assuming the use of PowerShell in narrative text; instead, refer to 'your preferred scripting environment' or similar inclusive language.

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 Developer CLI (azd) for deployment. While these tools are cross-platform, the tutorial is heavily oriented toward ASP.NET Core and does not provide any Linux-specific or non-Windows terminal instructions. There are no examples or notes for Linux users, such as using bash, zsh, or Linux-specific deployment patterns. All code and deployment steps are presented in a way that is most familiar to Windows/.NET developers, and there is no mention of alternative Linux-first workflows or tools.

Recommendations:

Explicitly mention that all terminal commands (dotnet, azd) work on Linux, macOS, and Windows, and provide any necessary prerequisites for Linux users (e.g., installing .NET SDK, azd CLI on Linux).
Include a note or section for Linux users, such as how to run the sample app in a local Linux environment (e.g., using bash, systemd, or Docker).
Provide example commands using bash/zsh syntax where appropriate, especially for steps like exporting environment variables or running the app.
Clarify that Azure App Service supports both Windows and Linux hosting, and provide guidance for deploying to both platforms if there are differences.
If any step is different on Linux (such as file paths, case sensitivity, or permissions), call this out explicitly.

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, the only example given for clearing DNS cache is the Windows-specific 'ipconfig /flushdns' command, with no mention of Linux or macOS equivalents. This presents a subtle Windows-first bias and omits guidance for users on other operating systems.

Recommendations:

When providing command-line 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 examples to ensure parity across Windows, Linux, and macOS.

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 setx (cmd) and PowerShell commands, which may signal a Windows-first approach. However, Linux/macOS instructions are present and correct. There are no missing Linux examples, and no exclusive use of Windows tools or patterns elsewhere in the guide.

Recommendations:

Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
Consider grouping environment variable instructions by platform with equal prominence, or use tabbed sections for each OS.
If possible, provide a single cross-platform command (e.g., using a tool like direnv or dotenv) or clarify that the Go application will work identically on all platforms once the variable is set.
Avoid giving more detailed or prominent instructions for Windows than for Linux/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 more detailed, with extensive step-by-step scripts and a dedicated cmdlet reference, while the Azure CLI section is less detailed and lacks a similar command reference list. There are no Linux-specific shell (e.g., Bash) examples, and the CLI section is not as comprehensive as the PowerShell section. This ordering and depth may implicitly prioritize Windows/PowerShell users.

Recommendations:

Present Azure CLI examples before or alongside PowerShell examples to avoid implying a Windows-first workflow.
Ensure parity in detail and completeness between PowerShell and Azure CLI sections, including providing a CLI command reference list similar to the PowerShell cmdlet reference.
Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and consider adding Bash shell snippets where appropriate.
Where possible, include troubleshooting or usage notes relevant to Linux environments (e.g., file path differences, shell quoting).
Review language to ensure it does not assume a Windows environment or PowerShell familiarity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page assumes the use of ASP.NET Core and provides instructions and code samples exclusively for that environment, which is most commonly associated with Windows development. There are no explicit Linux or cross-platform instructions, nor are there any command-line examples (such as Bash or CLI) for Linux users. The portal navigation and terminology also implicitly assume familiarity with Windows-centric workflows.

Recommendations:

Include explicit notes or sections on how to perform the same steps on Linux or macOS, especially for developers running ASP.NET Core on non-Windows platforms.
Provide command-line examples using Azure CLI or Bash scripts for tasks like adding Key Vault references, in addition to or instead of portal instructions.
Clarify that the instructions and code samples are cross-platform where applicable, and mention any platform-specific considerations.
Add troubleshooting tips or links for common issues encountered on Linux (e.g., file permissions, environment variables, certificate handling).

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation does not provide any explicit Windows-only commands or tools, but it implicitly assumes a Windows environment by omitting any mention of Linux or macOS-specific steps, shell commands, or terminal usage. All instructions are given in a way that is platform-neutral but lack parity for Linux users (e.g., no mention of using bash, Linux file paths, or terminal commands). There is also a subtle 'windows_first' bias in the absence of Linux-specific guidance, which may leave Linux users uncertain about environment setup or command usage.

Recommendations:

Add explicit instructions or notes for Linux and macOS users, such as how to open the terminal, run commands, or install dependencies.
Include examples of file paths and commands in both Windows and Linux/macOS formats where relevant.
Mention any platform-specific prerequisites or troubleshooting steps (e.g., JAVA_HOME setup, permissions).
Ensure that screenshots or UI references are not Windows-centric, or provide alternatives for other operating systems.

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 setx (cmd) and PowerShell examples, which can be seen as a 'windows_first' and 'powershell_heavy' bias. Linux/macOS instructions are present but always listed after Windows. No Linux-specific tools or patterns are omitted, but the ordering and prominence of Windows tooling is evident.

Recommendations:

Present Linux/macOS and Windows instructions in parallel tabs or side-by-side, rather than always listing Windows first.
If using sequential instructions, alternate the order (sometimes Linux/macOS first) or clarify that the order does not imply priority.
Consider using tabbed content blocks for each platform (Windows cmd, PowerShell, Linux/macOS) to provide equal visibility.
Ensure that Linux/macOS users see their instructions as prominently and as early as Windows users.
Where possible, use cross-platform commands (e.g., via Azure CLI) as the primary example, with platform-specific notes as needed.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation generally provides both Windows and Linux examples for ARM/Bicep templates and application settings, often using tabbed sections. However, in several key sections, Windows examples are presented before Linux equivalents ("windows_first"), and PowerShell is the only scripting language shown for deployment automation ("powershell_heavy"). There are no CLI or Bash examples for Linux users in the deployment automation section. The documentation does not appear to omit Linux-specific information or tools, but the ordering and scripting language choices may give the impression of a Windows-centric approach.

Recommendations:

Alternate the order of Windows and Linux examples in tabbed sections, or default to the user's platform when possible.
Provide equivalent Azure CLI/Bash examples alongside PowerShell for deployment automation, especially in the 'Deploy your template' section.
In sections where both Windows and Linux are supported, clarify that both platforms are equally supported and highlight any differences up front.
Where possible, use cross-platform language (e.g., 'Azure CLI' instead of 'PowerShell') as the primary example, or provide both.
Ensure that all references to tools, commands, and scripts are available and demonstrated for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation generally aims for cross-platform parity, but there is a subtle Windows bias. Visual Studio (a Windows-only tool) is listed first and described in detail for C# development, while Linux/macOS options (like Visual Studio Code and command line) are presented after. Some instructions and examples, such as changing ports in Visual Studio, are specific to Windows workflows. In the HTTP test tools section, PowerShell and Microsoft Edge (both Windows-centric) are listed before curl, a ubiquitous cross-platform tool. There are no explicit Linux-only examples or tools highlighted, and Linux/macOS users are not given equal prominence in tool ordering or example specificity.

Recommendations:

In each language section, list cross-platform tools (like Visual Studio Code and command line) before Windows-only tools such as Visual Studio.
When describing environment-specific instructions (e.g., changing ports), provide equivalent steps for Linux/macOS users or clarify if a step is Windows-only.
In tool lists (such as HTTP test tools), list cross-platform tools (like curl) before Windows-specific tools (like PowerShell or Microsoft Edge).
Explicitly mention and provide links to Linux/macOS-specific guides or troubleshooting where relevant.
Where possible, add Linux/macOS screenshots or terminal commands alongside Windows examples to reinforce parity.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing Azure PowerShell commands as the primary example for feature registration and status checking, with Azure CLI (cross-platform) only mentioned in passing. The PowerShell examples are given first and in more detail, while the CLI alternative is referenced as a link without direct command examples. There are no Linux- or Bash-specific instructions or screenshots, and the documentation assumes familiarity with PowerShell, which is more common on Windows.

Recommendations:

Provide Azure CLI command examples directly in the documentation alongside PowerShell examples, not just as a link.
Present both PowerShell and CLI examples in parallel, or default to Azure CLI (which is cross-platform) before PowerShell.
Include notes or instructions relevant to Linux/macOS users, such as how to install and use Azure CLI.
Ensure screenshots and UI references do not assume a Windows environment.
Review the documentation for other places where Windows-specific tools or terminology are used, and add Linux/macOS equivalents where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

Summary:

The documentation presents Windows (SMB) client instructions before Linux (NFS) client instructions, and provides more detailed, step-by-step guidance for Windows users (including both GUI and command-line methods), while Linux instructions are more concise and limited to a single command-line example. Windows-specific tools and patterns (File Explorer, dir command) are mentioned and illustrated, while Linux alternatives are less elaborated.

Recommendations:

Present Linux and Windows client instructions in parallel or alternate the order in different sections to avoid always prioritizing Windows.
Expand the Linux section to include both GUI (if applicable, e.g., Nautilus or other file managers) and multiple command-line methods (e.g., ls, stat, or graphical disk usage tools).
Provide screenshots for Linux GUI tools if available, similar to the Windows File Explorer screenshot.
Clarify that both SMB and NFS clients are equally supported and provide parity in the depth of explanation and examples.
Include a note or table summarizing equivalent commands and tools for both platforms for quick reference.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation page does not provide any platform-specific examples or instructions. However, it also does not mention or demonstrate Linux-specific commands, tools, or workflows, potentially leaving Linux users without clear guidance if platform differences exist.

Recommendations:

Review included content (such as referenced includes) to ensure Linux-specific instructions or examples are present where platform differences exist.
Explicitly mention if steps are platform-agnostic, or provide side-by-side examples for both Windows (PowerShell/Command Prompt) and Linux (Bash/CLI) where relevant.
Add notes or links to Linux-specific troubleshooting or environment setup if applicable.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page demonstrates a 'windows_first' bias by listing .NET and ASP.NET Core (Windows-centric technologies) and their libraries at the top of the provider table, with their samples and release notes featured first. There are no explicit Windows-only tools or PowerShell examples, but the ordering and emphasis on .NET/Windows frameworks over Linux-native or cross-platform frameworks may signal a preference for Windows environments.

Recommendations:

Reorder the provider libraries table to alternate or group by language family (e.g., .NET, Java, Python, JavaScript, Go) rather than placing all .NET/Windows-centric entries first.
Explicitly mention cross-platform compatibility for each provider, especially for .NET libraries that also run on Linux via .NET Core.
Add a section or note highlighting Linux and container-native scenarios (such as Kubernetes), and link to relevant samples or documentation.
Ensure that any future code or CLI examples include both Windows (PowerShell/cmd) and Linux (bash/sh) variants where applicable.
Consider including a summary table or quickstart for Linux users to improve parity and discoverability.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not show explicit Windows bias in terms of examples or tooling, as it focuses on SDK usage (C#, Java, JavaScript, Python) and does not mention Windows-specific tools or PowerShell. However, there is a lack of Linux-specific examples, shell commands, or references to cross-platform development environments. The documentation does not address platform-specific setup, deployment, or usage scenarios, which may leave Linux users without guidance for parity.

Recommendations:

Add explicit notes or examples for running Durable Task Scheduler on Linux environments, including any differences in setup or deployment.
Include shell (bash) command-line examples for SDK installation, orchestration deployment, or environment configuration, not just code snippets.
Mention and link to cross-platform tools (such as Azure CLI) where relevant, and ensure that instructions are not implicitly Windows-centric.
If any platform-specific considerations exist (such as file paths, environment variables, or service dependencies), document them for both Windows and Linux.
Consider adding a section or callout confirming that all SDKs and features are fully supported on Linux, or note any limitations.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation provides environment variable setup instructions in the order: Windows cmd, PowerShell, then macOS/Linux bash. This ordering prioritizes Windows users and may give the impression that Windows is the primary or preferred platform.

Recommendations:

Present environment variable setup instructions for all platforms together, or rotate the order in which platforms are presented (e.g., start with Linux/macOS, then Windows).
Use platform-agnostic language where possible, such as 'In your terminal, set the environment variable as follows:', then provide all variants in a single code block or table.
Ensure that Linux/macOS instructions are as detailed and prominent as Windows instructions.
Consider adding a note that all major platforms are supported equally.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation is largely cross-platform and avoids explicit Windows or PowerShell bias in its main instructions. However, in the Troubleshooting section, Windows-specific advice is given ('When running on Windows, make sure that the default terminal shell for Visual Studio Code isn't set to WSL Bash.') before any mention of Linux or macOS environments, and there are no Linux/macOS-specific troubleshooting tips. There are no PowerShell-specific commands or Windows-only tools mentioned, but the troubleshooting guidance subtly prioritizes Windows scenarios.

Recommendations:

Add troubleshooting tips relevant to Linux and macOS users, such as common issues with permissions, shell configuration, or dependencies on those platforms.
When mentioning Windows-specific advice, provide equivalent guidance for Linux/macOS or clarify that the advice is only relevant to Windows users.
Explicitly state that the instructions are cross-platform and that all steps apply equally to Windows, Linux, and macOS unless otherwise noted.
Consider including a table or section that lists any platform-specific considerations for all supported OSes.

Create pull request

Bias Types:

⚠️ missing_linux_example

Summary:

The documentation does not display overt Windows bias in terms of command-line examples, tooling, or explicit mention of Windows-specific patterns. However, all code samples are in C# (a language most commonly associated with Windows/.NET development), and there are no examples or instructions for Linux-based environments, such as Bash shell commands, Linux file paths, or deployment instructions for non-Windows platforms. There is also no mention of cross-platform considerations or parity for Linux users.

Recommendations:

Add examples or notes for Linux/macOS users, such as how to edit host.json, deploy Azure Functions, or manage Durable Functions on Linux.
Include at least one code sample in a language commonly used on Linux (e.g., Python, JavaScript/TypeScript) if supported by Durable Functions.
Mention any platform-specific considerations, such as file path differences or deployment nuances between Windows and Linux.
Clarify that the instructions and examples are applicable to both Windows and Linux environments, or specify any limitations.
If using .NET isolated model is required, note its cross-platform support and provide guidance for Linux users (e.g., .NET SDK installation on Linux).

Create pull request

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