Azure Web Pubsub

138
Total Pages
125
Linux-Friendly Pages
13
Pages with Bias
9.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (18)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-web-pubsub-tunnel-tool.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
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.
Recommendations:
  • 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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/reference-server-sdk-csharp.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
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.
Recommendations:
  • 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).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/tutorial-serverless-notification.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First Missing Linux Example
Summary:
The documentation demonstrates a mild Windows bias primarily through its references to Windows-specific tools (such as the Storage Emulator), lack of explicit Linux alternatives or parity in certain steps, and the ordering of instructions that may implicitly favor Windows users. While the main development workflow is cross-platform (using Azure CLI and Azure Functions Core Tools), there are notable areas where Linux users are underserved or must infer their own solutions.
Recommendations:
  • Where the Storage Emulator is referenced, explicitly mention and provide instructions for the cross-platform Azurite emulator, which is the recommended storage emulator for Linux and macOS.
  • When discussing browser compatibility (e.g., suggesting Edge), clarify that any modern browser can be used and avoid recommending a Windows-specific browser unless necessary.
  • In steps that mention file path handling or project file modifications (such as .csproj updates for static content), add notes or examples for Linux/macOS users, especially regarding case sensitivity and path separators.
  • Ensure that all prerequisite tools and installation instructions are clearly marked as cross-platform, and provide links or commands for Linux/macOS where relevant (e.g., for installing Azure Functions Core Tools or the Azure CLI).
  • Review all command-line examples to ensure they work identically on Linux/macOS, and add troubleshooting notes for common platform-specific issues (such as file permissions or environment variables).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/quickstart-use-sdk.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Bash and Azure PowerShell examples for all CLI operations, but PowerShell is consistently presented as an equal alternative rather than a secondary or optional one. In the prerequisites, both Bash and PowerShell are listed, but it is noted that Python, JavaScript, and Java samples require Bash. However, PowerShell examples are still provided for all CLI steps, which may suggest a slight Windows bias by giving PowerShell parity with Bash even when Bash is required for the main language samples. Additionally, PowerShell is mentioned before Bash in the prerequisites, and PowerShell-specific variable syntax and command formatting are used throughout.
Recommendations:
  • Clarify that Bash is the primary supported shell for non-.NET SDKs and that PowerShell examples are optional or secondary.
  • Present Bash examples first in all code tabs and sections, especially since most SDK samples require Bash.
  • Explicitly note any limitations of PowerShell usage with the SDKs (e.g., if certain language samples cannot be run in PowerShell).
  • Consider reducing the prominence of PowerShell examples or moving them to an appendix or 'Windows-specific' section to avoid implying equal support.
  • Ensure that all instructions and environment variable usage are cross-platform and avoid Windows-centric patterns unless necessary.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/tutorial-pub-sub-messages.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools
Summary:
The documentation demonstrates mild Windows bias by referencing Windows command shells and tools before or in preference to Linux equivalents. For example, it mentions using Windows cmd.exe as an alternative to Bash, and in several places, it provides Windows-specific instructions (such as using 'set' instead of 'export') before or alongside Linux commands. Additionally, the Java quickstart uses a Windows-style 'cmd' code block for directory creation, even though the rest of the instructions are cross-platform.
Recommendations:
  • Present Linux and Windows command instructions in parallel, using tabbed or side-by-side formatting, rather than mentioning Windows as an alternative to Bash.
  • When referencing environment variable setting (e.g., 'export' vs 'set'), provide both commands explicitly in a tabbed or clearly separated format, rather than as a parenthetical note.
  • For directory creation and navigation, use cross-platform commands (e.g., 'mkdir', 'cd') in a neutral shell format, or provide both Bash and cmd/PowerShell equivalents.
  • Avoid using Windows-specific code block annotations (e.g., 'cmd') unless absolutely necessary; prefer 'bash' or a neutral format.
  • Ensure that any references to tools or shells do not assume Windows as the default or primary environment.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/tutorial-build-chat.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation generally provides both Bash (Linux/macOS) and CMD (Windows) commands for environment variable setup, and all code samples are cross-platform. However, there is a subtle Windows bias: (1) In the environment variable setup, the Windows CMD example is given after the Bash example, but both are present. (2) The documentation assumes the use of Azure CLI, which is cross-platform, but does not mention Linux-specific tools or patterns (such as systemd for running servers, or Linux-specific troubleshooting). (3) The documentation references the awps-tunnel tool, which is Node.js-based and cross-platform, but does not mention alternatives like ngrok, which is commonly used in Linux/macOS developer workflows. (4) There is no explicit mention of Linux-specific shell or scripting patterns, and no troubleshooting guidance for Linux users. (5) The documentation does not provide PowerShell-specific examples, but the presence of CMD and Bash examples may still leave PowerShell users (common on Windows) or zsh/fish users (common on Linux/macOS) without direct guidance.
Recommendations:
  • Explicitly state that all commands and tools are cross-platform and tested on both Windows and Linux/macOS.
  • Provide PowerShell examples for environment variable setup, as many Windows users use PowerShell instead of CMD.
  • Include Linux-specific troubleshooting tips (e.g., handling permissions, using systemd or supervisord for running servers in the background).
  • Mention and provide examples for popular Linux/macOS tunneling tools like ngrok as alternatives to awps-tunnel.
  • Clarify any platform-specific prerequisites or differences (e.g., how to install Node.js or Python on Linux vs. Windows).
  • Add notes about activating Python virtual environments on Windows (using .venv\Scripts\activate) as well as on Linux/macOS (using . .venv/bin/activate).
  • Ensure that all code and command snippets are clearly marked for their intended shell (Bash, CMD, PowerShell) and platform.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-web-pubsub-tunnel-tool.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
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.
Recommendations:
  • 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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/quickstart-bicep-template.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Azure CLI and PowerShell examples for deployment, resource review, and cleanup. However, PowerShell is given equal prominence to Azure CLI, despite being a Windows-centric tool. There is no explicit mention of Linux-specific tools or shell environments (such as Bash), and PowerShell is presented as a primary option alongside Azure CLI, which may suggest a bias towards Windows users.
Recommendations:
  • Clarify that Azure CLI commands are cross-platform and can be used on Windows, Linux, and macOS.
  • Consider providing Bash shell examples or explicitly mentioning that CLI commands work in Bash/Terminal on Linux/macOS.
  • If PowerShell is included, note that it is available cross-platform, but that Bash is the default shell on most Linux systems.
  • Add a section or note for Linux/macOS users, confirming that all CLI steps are fully supported on those platforms.
  • Avoid presenting PowerShell as an equally primary option unless there is a specific need for it, or at least indicate the typical platform usage for each tool.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/quickstart-use-sdk.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation provides both Bash and Azure PowerShell examples for all CLI steps, but the PowerShell examples are always presented alongside Bash, and sometimes before or equally with Bash. However, there are no explicit Windows-only tools or patterns, and the CLI commands are cross-platform. The language SDK examples (C#, JavaScript, Python, Java) are all shown with Bash commands, and the prerequisites note that Bash is required for Python, JavaScript, and Java, which may disadvantage Windows users who do not have Bash. There is a slight bias in that PowerShell is given parity with Bash throughout, but there are no explicit Linux-only or Windows-only steps. There are no examples for native Windows CMD usage, nor explicit Linux-only tools.
Recommendations:
  • Clarify in the prerequisites that Bash can be used on Windows via WSL, Git Bash, or similar, and provide links or instructions for Windows users.
  • Consider providing Windows CMD examples or clarify that PowerShell is the recommended shell for Windows users.
  • In each step, explicitly state which shell is recommended for which OS, to avoid confusion.
  • If possible, provide parity in shell examples: for each Bash example, ensure the PowerShell equivalent is equally visible, and vice versa.
  • Add a note for Windows users who may not have Bash, explaining how to install or use Bash-compatible environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/socket-io-howto-integrate-web-app.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Bash and PowerShell examples for compressing files, but Bash is presented first and more prominently. There is no exclusive focus on Windows tools, and Linux workflows are included throughout, especially in the deployment steps. However, the explicit labeling of 'Use Bash' and 'Use PowerShell' and the inclusion of PowerShell commands may indicate a slight Windows bias, especially since PowerShell is not as commonly used on Linux. All other steps use cross-platform tools (Azure CLI, git, npm), and there are no Windows-only tools or patterns.
Recommendations:
  • Ensure that both Bash and PowerShell examples are given equal prominence and are clearly marked as platform-specific (e.g., 'For Linux/macOS' and 'For Windows').
  • Consider providing a table or side-by-side comparison for commands that differ by platform, rather than listing Bash first and PowerShell second.
  • Explicitly mention which OS each command is for, and clarify that Bash commands work on Linux/macOS and PowerShell on Windows.
  • If possible, provide a note about using Windows Subsystem for Linux (WSL) for Windows users who prefer Bash, to further support Linux parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/socket-io-serverless-tutorial-python.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Powershell Heavy
Summary:
The documentation demonstrates a subtle Windows bias: it uses Windows-centric terminology (e.g., 'command prompt'), references Windows-style paths (e.g., 'azurite\debug.log'), and assumes familiarity with Windows tools and conventions. While most commands are cross-platform, the order and phrasing often prioritize Windows users, and there is a lack of explicit Linux/macOS instructions or clarifications.
Recommendations:
  • Replace 'command prompt' with 'terminal' or 'command line' to be OS-neutral.
  • When showing file paths, use forward slashes (/) or provide both Windows (\) and Linux/macOS (/) examples.
  • Explicitly mention that all CLI commands work on Linux/macOS, and provide any OS-specific notes if needed.
  • For Azurite, show both Windows and Linux/macOS invocation examples (e.g., 'azurite -l azurite -d azurite/debug.log' for Linux/macOS).
  • If referencing environment variables or configuration files, clarify any OS-specific differences.
  • Add a note or section confirming that all steps are supported on Linux/macOS, and link to platform-specific setup guides if available.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/tutorial-build-chat.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation provides both Bash and Windows CMD examples for setting environment variables, but Bash (Linux/macOS) is shown first. There is no exclusive use of Windows tools or PowerShell, and all code samples and instructions are cross-platform. However, the documentation assumes the use of Azure CLI, which is available on all platforms, and does not rely on Windows-specific tools. The only minor bias is the inclusion of both Bash and CMD snippets, but not PowerShell, and the use of 'export' (Bash) before 'SET' (CMD), which slightly favors Linux/macOS. There is no evidence of missing Linux examples or exclusive mention of Windows tools.
Recommendations:
  • Ensure that PowerShell examples are included alongside Bash and CMD where relevant, especially for setting environment variables.
  • Explicitly state that all instructions are cross-platform and can be run on Linux, macOS, or Windows.
  • Where CLI commands are shown, clarify that they work in all supported shells (Bash, CMD, PowerShell) and provide examples for each if possible.
  • Consider adding a short section or note about how to adapt the instructions for different operating systems and shells, especially for environment variable management.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/tutorial-pub-sub-messages.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools
Summary:
The documentation shows mild Windows bias by referencing Windows command shells and tools before or in preference to Linux equivalents. For example, it mentions using Windows cmd.exe instead of Bash, and provides explicit instructions for Windows environment variable setting (using 'set') before or alongside Linux ('export'). In the Java section, the initial directory creation uses 'cmd' syntax, and there is occasional mention of Windows-specific patterns. However, the majority of code and CLI examples are cross-platform, and Linux/Bash instructions are present throughout.
Recommendations:
  • When referencing command shells, present Bash/Linux instructions first, or equally with Windows, rather than as an alternative.
  • Avoid using Windows-specific command syntax (e.g., 'cmd') as the primary example; provide both Bash and Windows equivalents side by side.
  • Where environment variables are set, show both 'export' (Linux/macOS) and 'set' (Windows) examples together, or clarify which is for which OS.
  • Ensure all tool installation and usage instructions are platform-agnostic or provide clear, parallel instructions for both Windows and Linux.
  • Consider adding a table or section summarizing OS-specific differences for setup and commands, to make parity explicit.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-develop-create-instance.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and managing resources, but consistently lists PowerShell (a Windows-centric tool) alongside or immediately after CLI, and sometimes before mentioning cross-platform alternatives. There is no explicit Linux bias, but the presence and parity of PowerShell examples may suggest a slight Windows bias, especially since PowerShell is less commonly used on Linux. However, all core workflows are covered with Azure CLI, which is cross-platform.
Recommendations:
  • Explicitly state that Azure CLI commands work on Windows, Linux, and macOS to reinforce cross-platform support.
  • When presenting both CLI and PowerShell, consider listing CLI first, as it is more universally available across platforms.
  • Clarify that PowerShell examples are optional and primarily for users already familiar with it.
  • Where possible, add notes or callouts for Linux/macOS users (e.g., file path differences, shell syntax) to ensure parity.
  • Avoid implying that PowerShell is the default or preferred automation tool unless targeting a Windows-specific audience.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-secure-network-access-control.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
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.
Recommendations:
  • 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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-move-across-regions.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation provides detailed instructions for moving an Azure Web PubSub resource using the Azure Portal and Azure PowerShell, but does not include any examples or guidance for Linux users or alternative CLI tools (such as Azure CLI or Bash scripting). PowerShell is featured exclusively for command-line operations, and Windows-specific tools like 'notepad' are referenced for editing JSON files.
Recommendations:
  • Add equivalent instructions and examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
  • Replace or supplement the 'notepad' editor reference with cross-platform alternatives such as 'vi', 'nano', or 'code', or use generic language like 'open the file in your preferred text editor'.
  • Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI, and provide sample commands.
  • Ensure that any PowerShell-specific instructions are accompanied by Azure CLI equivalents, especially for exporting, editing, and deploying ARM templates.
  • Review the documentation for other Windows-centric terminology or assumptions and revise to be OS-agnostic where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/tutorial-serverless-notification.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First
Summary:
The documentation generally uses cross-platform tools (Azure CLI, Azure Functions Core Tools) and provides language-specific instructions in a tabbed format, which is good for parity. However, there is a subtle Windows bias in the storage emulator guidance: the only local storage emulator mentioned is the classic 'Storage Emulator', which is Windows-only. No mention is made of cross-platform alternatives like Azurite. Additionally, the note about browser compatibility specifically recommends Edge, a Microsoft browser, which may be perceived as a Windows-centric suggestion.
Recommendations:
  • Mention and provide instructions for using Azurite (the cross-platform Azure Storage emulator) alongside or instead of the classic Windows-only Storage Emulator.
  • Clarify that all command-line instructions (Azure CLI, func) are cross-platform and work on Linux, macOS, and Windows.
  • When referencing browser compatibility, avoid recommending a specific browser unless necessary, or provide a broader set of options (e.g., Chrome, Firefox, Edge, Safari) to avoid perceived bias.
  • Explicitly state that all steps and tools are supported on Linux and macOS as well as Windows, especially in the prerequisites and troubleshooting sections.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/tutorial-subprotocol.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools
Summary:
The documentation generally provides cross-platform instructions, with shell commands and code examples for C#, JavaScript, Python, and Java. However, there is a subtle Windows bias in the way Windows-specific tools and command patterns are introduced before or alongside their Linux equivalents. For example, in several places, the Windows 'dir /s /b' command is mentioned as an alternative to the default 'ls -R' (Linux/macOS), and the .NET Secret Manager tool (which is Windows-centric) is referenced without a Linux-specific alternative. In most cases, Linux commands are primary, but Windows alternatives are always mentioned, sometimes immediately after the Linux example, which can signal a slight preference or assumption of Windows usage.
Recommendations:
  • When presenting command-line examples, consider grouping Windows and Linux/macOS commands separately, or use tabbed sections (as done for programming languages) to avoid mixing them and to give each platform equal prominence.
  • For tools like .NET Secret Manager, clarify cross-platform usage or provide explicit instructions for Linux/macOS environments, including any prerequisites or differences.
  • If referencing Windows commands (e.g., 'dir /s /b'), ensure that Linux/macOS equivalents are always given equal visibility and not just as the default with Windows as an afterthought.
  • Consider adding a short section at the start of the tutorial that explicitly states the tutorial is cross-platform and that all major OSes are supported, with clear navigation to OS-specific instructions where needed.
  • Review all included snippets and ensure that any platform-specific instructions are clearly labeled and not presented as the default or primary approach.