Azure Web Pubsub

The documentation page demonstrates minor Windows bias by mentioning Windows command shell usage before Bash, and by providing instructions for setting environment variables with 'set' for Windows users. The Java section uses 'cmd' for directory creation, but otherwise, examples and instructions are cross-platform and include Bash and Azure CLI commands suitable for Linux/macOS. No critical functionality is locked to Windows, and Linux/macOS users can follow the tutorial without significant friction.

• Present Bash and Windows command shell instructions side-by-side, or clarify platform-specific steps in all relevant code blocks.
• Provide explicit Linux/macOS equivalents for any command-line instructions that mention Windows tools (e.g., 'set' vs 'export'), ideally in a tabbed or callout format.
• Avoid using Windows-specific command prompts (e.g., 'cmd') in code blocks unless also providing the Bash equivalent.
• Add a brief section at the start clarifying cross-platform compatibility and how to adapt commands for different shells.

The documentation generally provides cross-platform instructions, but in the section on setting environment variables for the connection string, the Windows (cmd) example is presented after the Linux/macOS (bash) example. No other significant Windows bias is present: all installation and usage instructions use cross-platform Node.js/npm commands, and there is no exclusive mention of Windows tools or PowerShell.

• Ensure that all platform-specific instructions are presented with equal prominence. Consider using tabbed sections with consistent ordering (e.g., Linux/macOS first, Windows second, or vice versa) and clear labeling.
• Where possible, provide PowerShell examples for Windows users in addition to cmd, as PowerShell is increasingly common.
• Explicitly state that all commands are cross-platform unless otherwise noted, to reassure Linux users.
• Audit future documentation for any accidental omission of Linux or macOS instructions, especially for environment variable setup and tool usage.

The documentation focuses exclusively on .NET SDK usage, with all code examples in C# and installation instructions using the dotnet CLI. There are no explicit references to Windows-specific tools or PowerShell, nor are there any mentions of Windows or Linux platforms. However, there is a lack of Linux-specific guidance or examples, such as shell commands or notes on cross-platform usage, which may implicitly bias the documentation towards Windows users who are more likely to use .NET and related tooling.

• Add explicit notes clarifying that the .NET SDK and dotnet CLI are cross-platform and can be used on Linux, macOS, and Windows.
• Include example commands for installing the .NET SDK on Linux (e.g., using apt, yum, or snap).
• Provide sample shell commands (bash/zsh) for common tasks, such as setting environment variables or running the application, to complement the C# code.
• Mention any platform-specific considerations, if applicable, for Linux users (e.g., file permissions, dependency installation).

The documentation provides both Linux/macOS and Windows instructions for setting environment variables, but the Windows example is presented after the Linux/macOS example. There is no exclusive use of Windows tools, nor are there missing Linux examples or PowerShell-heavy instructions. The documentation is generally cross-platform, but the ordering of examples could be considered a subtle form of bias if consistency across Microsoft documentation is considered.

• Present both Linux/macOS and Windows instructions side-by-side or in a tabbed interface, ensuring equal prominence.
• Consider alternating the order of platform examples in different sections, or default to alphabetical order (Linux, macOS, Windows) to avoid implicit prioritization.
• Explicitly state that the tool is cross-platform and works identically on all supported operating systems.
• If possible, provide PowerShell examples for Windows users in addition to CMD, as PowerShell is increasingly common.

The documentation provides configuration instructions exclusively via the Azure Portal (web UI) and Bicep templates, with no command-line examples for either Windows (e.g., PowerShell, Command Prompt) or Linux (e.g., Bash, Azure CLI). However, the absence of any CLI-based instructions or examples (such as Azure CLI commands) constitutes a bias of omission, as Linux users typically rely on CLI tools for automation and scripting. This results in a lack of parity for Linux users who may prefer or require command-line instructions.

• Add Azure CLI examples for each configuration scenario (public network access, default action, request type rules, IP rules), as Azure CLI is cross-platform and widely used on Linux.
• Where possible, provide Bash shell scripts or command snippets to demonstrate automation workflows.
• Explicitly mention that all instructions are applicable to both Windows and Linux when using the Azure Portal or Bicep, but highlight CLI alternatives for Linux users.
• Consider including PowerShell examples for Windows users only if Azure CLI is also provided for Linux users, ensuring parity.