Azure Web Pubsub

280
Total Pages
259
Linux-Friendly Pages
21
Pages with Bias
7.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

37 issues found
Showing 1-25 of 37 flagged pages
Azure Web Pubsub Add a custom domain .../main/articles/azure-web-pubsub/howto-custom-domain.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways. PowerShell/Windows examples are presented before Bash/Linux equivalents, with the PowerShell tab listed first in the 'Verify your custom domain' section. The PowerShell example uses 'curl.exe' and the 'PS C:\>' prompt, both of which are Windows-specific tools and conventions. Throughout the document, there is a lack of explicit Linux or cross-platform guidance, and the Azure portal screenshots and instructions do not mention platform-specific alternatives or considerations.
Recommendations
  • Present Bash/Linux examples before or alongside PowerShell/Windows examples, or randomize tab order to avoid implicit prioritization.
  • Use platform-neutral tools and prompts in examples (e.g., generic 'curl' usage, avoid 'PS C:\>' prompt).
  • Explicitly mention that all steps and portal instructions apply equally to Linux, macOS, and Windows, or provide notes where there are differences.
  • Include CLI examples using Azure CLI (az) for certificate and managed identity operations, which are cross-platform.
  • Add guidance or screenshots for Linux/macOS users where relevant, especially for command-line operations.
GitHub Create Pull Request
Azure Web Pubsub Move an Azure Web PubSub resource to another region | Microsoft Docs ...articles/azure-web-pubsub/howto-move-across-regions.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides detailed instructions for moving an Azure Web PubSub resource using the Azure Portal and Azure PowerShell, with all command-line examples exclusively using PowerShell. The use of 'notepad' for editing files and the absence of Azure CLI or bash examples further indicate a Windows-centric approach. No Linux or cross-platform command-line alternatives are mentioned, and PowerShell is presented as the only scripting option.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, including exporting templates, editing files, creating resource groups, and deploying resources.
  • Replace or supplement 'notepad' with cross-platform editors such as 'vim', 'nano', or 'code' (Visual Studio Code), or simply refer to 'your preferred text editor'.
  • Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and provide guidance for non-Windows environments.
  • Reorder or parallelize sections so that Azure CLI and PowerShell instructions are presented together, rather than PowerShell being the only command-line option.
  • Include notes or links to documentation for installing and using Azure CLI and PowerShell on Linux/macOS.
GitHub Create Pull Request
Azure Web Pubsub Quickstart - Publish messages using Azure Web PubSub service SDK ...b/main/articles/azure-web-pubsub/quickstart-use-sdk.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Bash and Azure PowerShell examples for all CLI steps, but PowerShell is given equal prominence to Bash throughout, and is explicitly listed as a prerequisite alongside Bash. There is a slight Windows bias in the repeated mention of PowerShell, the use of PowerShell variable syntax, and the assumption that users may be using PowerShell locally. The prerequisites mention 'a Bash and PowerShell command shell' but do not mention Linux shells or environments specifically. There are no explicit Linux-only examples, and Windows tools (PowerShell) are always presented as an equal option, sometimes before Bash. There is also an assumption that VS Code is the editor, which is cross-platform but often associated with Windows.
Recommendations
  • Clarify that Bash examples work on Linux/macOS and Windows (via WSL or Git Bash), and that PowerShell is primarily for Windows users.
  • Add explicit references to Linux/macOS environments in the prerequisites, e.g., 'Linux/macOS terminal' or 'Bash shell on Linux/macOS'.
  • Consider listing Bash examples before PowerShell, or noting that Bash is the default on Linux/macOS.
  • Where PowerShell is mentioned, add a note that it is most relevant for Windows users.
  • Provide guidance for Linux users on installing prerequisites (e.g., Python, Node.js, Java) using native package managers.
  • Ensure that all steps and code samples are tested and confirmed to work on Linux/macOS as well as Windows.
GitHub Create Pull Request
Azure Web Pubsub Tutorial - Publish and subscribe messages using WebSocket API and Azure Web PubSub service SDK ...articles/azure-web-pubsub/tutorial-pub-sub-messages.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows command shell usage is mentioned before Bash, and Windows-specific instructions (such as using 'set' instead of 'export') are called out in multiple places. The Java section uses Windows-style 'cmd' for directory creation, and there is a general tendency to mention Windows tools and patterns before their Linux equivalents. However, most code and CLI examples are cross-platform and use Bash syntax, and Linux is not excluded from any steps.
Recommendations
  • Present Bash/Linux instructions before or alongside Windows instructions, rather than after.
  • Use neutral language when referring to command shells (e.g., 'In Bash, use export; in Windows cmd.exe, use set').
  • Include explicit Linux/MacOS instructions for activating Python virtual environments (e.g., 'source env/bin/activate' vs 'env\Scripts\activate' for Windows).
  • Avoid using Windows-style directory creation ('cmd') in Java sections; use Bash syntax or clarify both.
  • Add a note at the beginning clarifying that all steps are cross-platform unless otherwise specified.
  • Where possible, provide PowerShell examples alongside Bash, or clarify that Azure CLI commands work in both environments.
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-custom-domain.md .../main/articles/azure-web-pubsub/howto-custom-domain.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. PowerShell/Windows examples are presented before Bash/Linux equivalents (e.g., in the Health API verification section, PowerShell is the first tab). The use of 'curl.exe' and 'PS C:\>' prompt in examples further emphasizes Windows-centric instructions. There are no explicit Linux-specific instructions or screenshots, and the Azure Portal screenshots do not clarify cross-platform parity. The documentation does not mention Linux tools or workflows outside of the Bash/cURL example, and Windows patterns (such as PowerShell) are prioritized.
Recommendations
  • Present Bash/Linux examples before or alongside PowerShell/Windows examples, or randomize their order to avoid implicit prioritization.
  • Include explicit instructions or notes for Linux users, such as command-line differences, certificate management, and DNS configuration.
  • Add Linux-specific screenshots or clarify that the Azure Portal UI is platform-agnostic.
  • Avoid using Windows-specific prompts (e.g., 'PS C:\>') in generic examples; use neutral prompts or include both Windows and Linux prompts.
  • Mention cross-platform compatibility for all command-line instructions and tools.
  • Where relevant, provide guidance for Linux-native certificate creation and management.
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-move-across-regions.md ...articles/azure-web-pubsub/howto-move-across-regions.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing detailed instructions and examples exclusively for Azure PowerShell, which is most commonly used on Windows. It references Windows-specific tools (e.g., Notepad for editing JSON files) and omits equivalent Linux/macOS command-line examples (such as Azure CLI or cross-platform editors). The PowerShell workflow is presented as the only scripting alternative to the portal, with no mention of Linux-friendly options. The order of presentation also puts Windows-centric methods before any cross-platform alternatives.
Recommendations
  • Add Azure CLI examples for all steps currently shown with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Replace or supplement 'notepad' with cross-platform editors (e.g., 'nano', 'vim', 'code') or generic instructions for editing JSON files.
  • Explicitly mention that PowerShell Core is available cross-platform, or clarify the instructions for Linux/macOS users.
  • Provide bash shell command equivalents for resource group and template management.
  • Reorder sections or provide parallel instructions so that Linux/macOS users do not feel secondary to Windows users.
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-secure-rotate-access-key.md ...les/azure-web-pubsub/howto-secure-rotate-access-key.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page primarily describes rotating access keys via the Azure portal, a web-based tool, and mentions the Azure CLI only as a future option. There are no command-line examples, and no Linux-specific instructions or parity with Windows tools. The Azure portal is often associated with Windows workflows, and there is no mention of Linux shells or automation approaches.
Recommendations
  • Add Azure CLI examples for rotating access keys, including command-line instructions that work on both Windows and Linux.
  • Explicitly mention that the Azure portal is web-based and platform-agnostic to avoid the perception of Windows bias.
  • When Azure CLI support is available, provide both PowerShell and Bash (Linux/macOS) command examples.
  • Include notes or links for automating key rotation using cross-platform tools (e.g., Bash scripts, Azure CLI in Linux environments).
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-web-pubsub-tunnel-tool.md ...icles/azure-web-pubsub/howto-web-pubsub-tunnel-tool.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides credential setup instructions for both Linux/macOS and Windows, but Windows instructions (cmd) are presented after Linux/macOS (bash). There are no PowerShell examples, but the Windows example uses cmd syntax. The rest of the documentation uses bash commands for installation and usage, which are suitable for Linux/macOS and also work in Windows environments with WSL or Git Bash, but there are no explicit instructions or examples for PowerShell or native Windows environments beyond setting environment variables. There is a slight bias toward bash/Linux in command examples, and Windows users may need more guidance for running Node.js scripts and npm commands in native Windows terminals.
Recommendations
  • Add PowerShell examples for setting environment variables and running commands, as many Windows users prefer PowerShell over cmd.
  • Clarify that bash commands can be run in Windows using WSL, Git Bash, or similar tools, and provide native Windows alternatives where appropriate.
  • Ensure parity in examples by providing both Linux/macOS and Windows (cmd and PowerShell) instructions for all steps, not just environment variable setup.
  • Explicitly mention any Windows-specific considerations for running Node.js/npm commands (e.g., path differences, administrative permissions).
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/tutorial-serverless-iot.md ...n/articles/azure-web-pubsub/tutorial-serverless-iot.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The tutorial demonstrates some Windows bias, primarily in the tooling and troubleshooting sections. The documentation references the Azure Storage Emulator, which is a Windows-only tool, as the recommended solution for local storage emulation. There is no mention of Linux alternatives (such as Azurite) or cross-platform instructions for storage emulation. The troubleshooting note for the Event Hub trigger only references the Storage Emulator and links to Windows-centric documentation. While most CLI and function examples are cross-platform, the absence of Linux-specific guidance for local development and emulation is notable.
Recommendations
  • Explicitly mention Azurite as the recommended cross-platform storage emulator for local development, and provide installation and usage instructions for Linux/macOS.
  • Update troubleshooting notes to reference both Storage Emulator (Windows) and Azurite (Linux/macOS), with appropriate links.
  • Ensure all tool recommendations and troubleshooting steps include Linux/macOS equivalents or alternatives.
  • Where possible, clarify that all CLI commands and function tools work on both Windows and Linux, and highlight any platform-specific caveats.
GitHub Create Pull Request
Azure Web Pubsub Move an Azure Web PubSub resource to another region | Microsoft Docs ...articles/azure-web-pubsub/howto-move-across-regions.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides detailed instructions for moving an Azure Web PubSub resource using the Azure Portal and Azure PowerShell. All CLI-based examples use Azure PowerShell, which is primarily a Windows tool, and reference Windows-specific tools like 'notepad' for editing files. There are no examples using cross-platform tools such as Azure CLI, nor are Linux/macOS-friendly editors or shell commands mentioned. The PowerShell section is extensive and lacks Linux/macOS alternatives, making it harder for non-Windows users to follow along.
Recommendations
  • Add equivalent instructions using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Replace or supplement 'notepad' references with cross-platform editors (e.g., 'vim', 'nano', 'code', or 'gedit').
  • Explicitly mention that PowerShell Core is available on Linux/macOS, or provide bash/zsh shell examples.
  • Ensure that all steps that involve file editing or command-line operations include Linux/macOS alternatives.
  • Consider presenting CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
GitHub Create Pull Request
Azure Web Pubsub Move an Azure Web PubSub resource to another region | Microsoft Docs ...articles/azure-web-pubsub/howto-move-across-regions.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides detailed instructions for moving an Azure Web PubSub resource using the Azure Portal and Azure PowerShell. The PowerShell section is extensive and assumes the use of Windows-specific tools (e.g., Notepad for editing JSON files), and all CLI examples use PowerShell cmdlets. There are no examples or guidance for Linux/macOS users, such as using Azure CLI or cross-platform editors. The documentation also references PowerShell before mentioning any alternative approaches, and does not provide parity for Linux/macOS workflows.
Recommendations
  • Add equivalent instructions using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Replace or supplement references to Notepad with cross-platform editors (e.g., VS Code, nano, vim).
  • Explicitly mention that PowerShell Core is available on Linux/macOS, or provide Bash script examples.
  • Reorder or parallelize sections so that Windows and Linux/macOS approaches are presented together.
  • Include notes or links for Linux/macOS users on how to perform each step without relying on Windows-specific tools.
GitHub Create Pull Request
Azure Web Pubsub Quickstart - Publish messages using Azure Web PubSub service SDK ...b/main/articles/azure-web-pubsub/quickstart-use-sdk.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Bash and Azure PowerShell examples for all CLI operations, but there is a notable bias toward Windows/PowerShell environments. PowerShell examples are given equal prominence to Bash, even though Bash is the default shell on Linux/macOS and required for most language samples. There are no explicit Linux/macOS-specific instructions or troubleshooting tips, and PowerShell is referenced as a prerequisite alongside Bash, which may confuse Linux/macOS users. Some commands (e.g., Python venv activation) assume Bash, but PowerShell alternatives are not shown. The overall flow and examples are slightly Windows-centric, especially in the initial setup and environment variable usage.
Recommendations
  • Clarify that Bash is the default shell for Linux/macOS and PowerShell for Windows; make this explicit in the prerequisites.
  • Present Bash examples before PowerShell examples to reflect the majority of cross-platform usage.
  • Add Linux/macOS-specific notes for environment setup, such as activating Python venv or installing dependencies.
  • Include troubleshooting tips for common Linux/macOS issues (e.g., permissions, path differences).
  • Consider omitting PowerShell examples in sections where Bash is required (e.g., Python, JavaScript, Java samples), or provide equivalent Bash commands first.
  • Add a table or section summarizing shell differences and which to use on each platform.
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-disable-local-auth.md .../articles/azure-web-pubsub/howto-disable-local-auth.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows by only referencing the Azure portal (a web-based tool), Azure Resource Manager templates, and Azure Policy—all of which are platform-agnostic but are typically accessed via the Azure portal, which is often associated with Windows-centric workflows. There are no examples using cross-platform command-line tools such as Azure CLI or Azure PowerShell, and there are no Linux-specific instructions or screenshots. This omission may disadvantage Linux users who prefer or require command-line or automation-based workflows.
Recommendations
  • Add Azure CLI examples for turning off local authentication, as Azure CLI is cross-platform and widely used on Linux.
  • Include Azure PowerShell examples for parity, but ensure CLI examples are presented first or alongside PowerShell.
  • Explicitly mention that all steps can be performed from any OS via the Azure portal, and clarify that the portal is web-based and not Windows-specific.
  • Provide screenshots or terminal output from Linux environments where relevant.
  • Consider adding a section on automating this process using bash scripts or other Linux-native tools.
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-use-managed-identity.md ...rticles/azure-web-pubsub/howto-use-managed-identity.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses the Azure Portal UI for all instructions and does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash scripts). While this avoids explicit Windows-only tools, the lack of CLI examples can disadvantage Linux users, who often prefer or require command-line automation. Additionally, there is no mention of Linux-specific workflows or tools, and any references to command-line management (e.g., Azure CLI) are absent.
Recommendations
  • Add Azure CLI examples for all major steps, such as enabling managed identity, assigning user/system identities, and configuring event handlers. Azure CLI is cross-platform and widely used on Linux.
  • If PowerShell examples are added in the future, ensure Azure CLI or Bash equivalents are always provided and presented first or side-by-side.
  • Explicitly mention that all portal-based instructions are platform-agnostic, but provide links or references to CLI documentation for users who prefer command-line workflows.
  • Include a section or callout for automation scenarios, highlighting how Linux users can script these operations using Azure CLI.
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-web-pubsub-write-upstream-server.md ...e-web-pubsub/howto-web-pubsub-write-upstream-server.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently presents Windows-specific instructions (using 'set' for environment variables) before mentioning Linux/macOS equivalents (using 'export'), both in the main language samples and in the tunnel tool section. In several places, the Linux/macOS instructions are only given as comments or after the Windows example, and there are no Linux-specific shell or tool usage examples (e.g., no bash scripts, systemd, or Linux-native patterns). The documentation does not provide parity in terms of Linux-first or Linux-specific guidance.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, rather than as comments or afterthoughts.
  • Provide explicit bash/zsh commands for environment setup, not just as comments.
  • Include Linux-native troubleshooting tips (e.g., systemd service setup, common Linux firewall issues).
  • Add examples of running the upstream server as a background process or service on Linux.
  • Ensure all CLI and code samples use cross-platform patterns (e.g., avoid 'set' in favor of 'export' or show both explicitly).
  • Where possible, mention Linux tools or patterns (such as using curl for testing endpoints, or journalctl for logs).
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/includes/web-pubsub-add-role-assignments.md ...web-pubsub/includes/web-pubsub-add-role-assignments.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation primarily describes the role assignment process using the Azure Portal, which is a cross-platform web interface, but in the 'To learn more' section, Azure PowerShell is listed before Azure CLI. This ordering can be interpreted as a subtle Windows-first or PowerShell-heavy bias, as Azure CLI is generally more cross-platform and Linux-friendly, while PowerShell is more associated with Windows environments. No explicit Linux examples or Linux-specific tools are mentioned.
Recommendations
  • List Azure CLI before Azure PowerShell in the 'To learn more' section to reflect cross-platform parity.
  • Explicitly mention that both Azure CLI and PowerShell are available on all major platforms, and provide guidance for users on Linux.
  • Consider adding a brief example or link for performing the role assignment using Azure CLI directly in the main steps, not just in the 'To learn more' section.
  • If possible, provide a table or section comparing how to perform the task using both CLI and PowerShell, highlighting cross-platform options.
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/quickstart-use-sdk.md ...b/main/articles/azure-web-pubsub/quickstart-use-sdk.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and Azure PowerShell examples for all CLI steps, but PowerShell is given equal prominence to Bash, and is mentioned in prerequisites and throughout the guide. There is a slight Windows bias in the explicit inclusion of PowerShell examples and instructions, while Linux-specific shells or tools (e.g., zsh, fish) are not mentioned. The guide does not provide Windows-only tools, but the parity between Bash and PowerShell may suggest a prioritization of Windows users, as PowerShell is primarily a Windows shell (though available on Linux).
Recommendations
  • Clarify that Bash instructions work on Linux, macOS, and Windows (with WSL or Git Bash), while PowerShell is primarily for Windows users.
  • Add explicit notes about running Bash commands on Linux/macOS, and provide troubleshooting tips for those platforms.
  • Consider including examples for other common Linux shells if relevant (e.g., zsh), or at least mention their compatibility.
  • Ensure that all prerequisites and steps are equally clear for Linux users, including installation instructions for dependencies on Linux.
  • If PowerShell is included for Windows parity, consider adding a note that Bash is the default shell on most Linux distributions.
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/quickstarts-push-messages-from-server.md ...re-web-pubsub/quickstarts-push-messages-from-server.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation demonstrates a mild Windows bias, primarily in the Java section, where directory creation and navigation commands use Windows-style syntax (e.g., `mkdir pubsub` and `cd pubsub` in a `cmd` block, and Maven commands chained with `&`, which is a Windows shell operator). Additionally, the Java quickstart uses `cmd` and `console` blocks with Windows-centric instructions, and does not provide explicit Linux/Unix alternatives. However, most other language sections (JavaScript, Python, C#) use cross-platform Bash commands and avoid Windows-specific tools or PowerShell examples. No explicit PowerShell or Windows-only tools are used, and Linux examples are present for most workflows.
Recommendations
  • For Java sections, provide both Windows (`cmd`) and Linux/macOS (`bash` or `sh`) command examples, especially for Maven commands. For example, use `&&` for Unix shells and `&` for Windows, or note the difference.
  • Avoid using Windows-style command prompts (`cmd`) exclusively; use neutral or dual syntax blocks where possible.
  • Explicitly state that the instructions work on both Windows and Linux/macOS, and clarify any differences in command syntax.
  • Where possible, use cross-platform commands and avoid shell-specific chaining operators.
  • Add a note or section for Linux/macOS users in the Java quickstart, especially for project setup and execution commands.
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/reference-server-sdk-csharp.md ...ticles/azure-web-pubsub/reference-server-sdk-csharp.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on .NET and NuGet, which are traditionally associated with Windows environments. All code examples are in C#, and installation instructions use the dotnet CLI without mentioning cross-platform compatibility or Linux-specific instructions. There are no references to Linux tools, package managers, or shell environments, nor are there any examples or troubleshooting steps tailored for Linux users.
Recommendations
  • Explicitly mention that .NET Core and the dotnet CLI are cross-platform and supported on Linux and macOS, not just Windows.
  • Provide installation instructions for .NET SDK on Linux (e.g., using apt, yum, or snap).
  • Include example commands for installing the package on Linux systems.
  • Add troubleshooting steps or logging setup instructions for Linux environments (e.g., using Bash or Linux-specific log viewers).
  • Clarify that the SDK and examples work on Linux and macOS, and provide sample code or screenshots from those platforms.
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/socket-io-howto-integrate-web-app.md .../azure-web-pubsub/socket-io-howto-integrate-web-app.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for compressing files, but Bash is presented first. However, the PowerShell example is included, which is positive. There is a slight 'windows_first' bias in that the PowerShell example is given equal prominence, and the documentation does not mention Linux-specific tools beyond Bash, nor does it discuss platform-specific deployment considerations. The rest of the guide uses Azure CLI, which is cross-platform, and the prerequisites mention Azure CLI or Cloud Shell, both of which are platform-agnostic.
Recommendations
  • Ensure that Linux/Bash examples are always presented before or at least equally with PowerShell/Windows examples.
  • Explicitly mention that all steps work on Linux, macOS, and Windows, and clarify any platform-specific differences.
  • Include a note about using Bash on Windows (e.g., via WSL or Git Bash) for users who may not have PowerShell.
  • If possible, provide a table summarizing commands for Bash, PowerShell, and any other relevant shells.
  • Add troubleshooting tips for common platform-specific issues (e.g., file permissions on Linux).
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/socket-io-serverless-tutorial-python.md ...ure-web-pubsub/socket-io-serverless-tutorial-python.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by using Windows-style path separators (e.g., 'azurite\debug.log'), referencing 'command prompt' terminology, and omitting explicit Linux/macOS equivalents for commands and file paths. There are no PowerShell-specific commands, but the instructions and examples assume a Windows environment, especially in the Azurite emulator section. No Linux-specific setup or troubleshooting is mentioned, and commands are not shown with Linux-style paths or shell conventions.
Recommendations
  • Provide explicit Linux/macOS instructions alongside Windows steps, especially for file paths and shell commands (e.g., use './azurite/debug.log' for Linux/macOS).
  • Use cross-platform terminology such as 'terminal' instead of 'command prompt', or clarify when instructions differ.
  • Add notes or tabs for Linux/macOS users where setup or command syntax differs (e.g., Azurite startup, file paths).
  • Include troubleshooting tips for common Linux/macOS issues (e.g., permissions, npm global installs).
  • Review all code and command examples to ensure they are platform-agnostic or provide both Windows and Linux/macOS variants.
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/tutorial-pub-sub-messages.md ...articles/azure-web-pubsub/tutorial-pub-sub-messages.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally provides cross-platform instructions, with most shell commands shown in Bash and explicit notes for Windows users. However, there is a subtle Windows bias: Windows command shells and tools are mentioned first or as the default in several places, and some directory creation commands for Java use Windows-style (cmd) syntax. The guidance for setting environment variables also references Windows ('set') before Linux ('export'). There are no missing Linux examples, but the documentation sometimes assumes Windows as the primary environment.
Recommendations
  • When referencing both Windows and Linux commands, list Linux/Bash instructions first, as Bash is more common in cross-platform and cloud environments.
  • For directory creation and navigation, provide both Bash and Windows (cmd.exe) command blocks, or clarify which is being used in each code block.
  • When mentioning environment variable setting, give equal prominence to both 'export' (Linux/macOS) and 'set' (Windows), or provide a table showing both.
  • Where possible, use neutral, platform-agnostic language (e.g., 'command shell' instead of 'Windows command shell'), and clarify that all steps are supported on both platforms.
  • Add explicit notes or tabs for PowerShell if relevant, or clarify that Azure CLI commands work identically on all platforms.
GitHub Create Pull Request
Azure Web Pubsub How to collect a network trace ...s/azure-web-pubsub/howto-troubleshoot-network-trace.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation shows a mild Windows bias: Fiddler is introduced first, and while it is cross-platform, its historical association is with Windows. The browser section consistently lists Windows/Linux shortcuts before macOS, and Microsoft Edge is described before other browsers. There are no PowerShell-only examples or Windows-exclusive tools, and Linux/macOS users are provided with tcpdump instructions and browser steps. However, Windows patterns and terminology are often presented first.
Recommendations
  • Alternate the order of platform-specific instructions (e.g., list macOS shortcuts first in some places).
  • Explicitly mention Linux and macOS compatibility for Fiddler and other tools.
  • Provide parity in tool recommendations, such as suggesting Wireshark alongside tcpdump for Linux/macOS.
  • Consider grouping browser instructions by OS or browser popularity rather than Microsoft-first.
  • Where possible, use neutral language (e.g., 'Ctrl+Shift+I (Windows/Linux), Command+Option+I (macOS)') or list shortcuts for all platforms together.
GitHub Create Pull Request
Azure Web Pubsub Quickstart - Publish messages using Azure Web PubSub service SDK ...b/main/articles/azure-web-pubsub/quickstart-use-sdk.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Bash and Azure PowerShell examples for all CLI steps, but repeatedly lists PowerShell as a required shell and gives PowerShell examples equal prominence to Bash. However, the language SDK quickstarts (Python, JavaScript, Java) explicitly require Bash and do not provide Windows/PowerShell equivalents for those steps. There is a slight Windows bias in the prerequisites, with PowerShell mentioned as required even though only Bash is needed for most SDK samples. The ordering of examples sometimes lists PowerShell before Bash, and PowerShell is referenced throughout, which may confuse Linux/macOS users. No Windows-only tools are used, and all critical steps have Bash equivalents.
Recommendations
  • Clarify in prerequisites that Bash is required for Python, JavaScript, and Java samples, and PowerShell is optional for CLI steps.
  • List Bash examples before PowerShell in all sections to prioritize cross-platform usage.
  • Explicitly state which steps are cross-platform and which are Windows-specific.
  • Remove PowerShell as a 'required shell' for SDK samples that only work in Bash.
  • Consider adding macOS-specific notes or examples where relevant.
GitHub Create Pull Request
Azure Web Pubsub Create an Azure Web PubSub resource ...cles/azure-web-pubsub/howto-develop-create-instance.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and managing resources, but PowerShell (a Windows-centric tool) is consistently presented alongside CLI, and sometimes before or equally with CLI. There is no mention of Linux/macOS-specific considerations, and PowerShell is not contextualized as a Windows-only tool. The documentation does not clarify that PowerShell is primarily for Windows, nor does it provide any Linux/macOS-specific instructions or troubleshooting tips. However, Azure CLI is cross-platform and shown first in most cases, mitigating the bias somewhat.
Recommendations
  • Clearly indicate that Azure PowerShell is primarily a Windows tool and provide installation or usage notes for Linux/macOS if relevant.
  • Prioritize Azure CLI examples, as it is cross-platform, and present PowerShell as an alternative for Windows users.
  • Add explicit notes or links for Linux/macOS users, such as how to install Azure CLI and run commands in their environment.
  • If PowerShell is shown, clarify its platform compatibility and recommend CLI for non-Windows users.
  • Consider including screenshots or terminal examples from Linux/macOS environments where appropriate.
GitHub Create Pull Request
← Previous Page 1 of 2 Next →