Azure Web Pubsub

140
Total Pages
123
Linux-Friendly Pages
17
Pages with Bias
12.1%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

80 issues found
Showing 26-50 of 80 flagged pages
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
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. The verification example for the Health API lists PowerShell (Windows) before Bash (Linux), and the PowerShell example uses 'curl.exe' with a Windows-style prompt. There are no explicit Linux or cross-platform CLI examples for other steps, and all screenshots and instructions are based on the Azure Portal GUI, which is platform-agnostic but does not mention or provide parity for Azure CLI or automation via Linux shell. The page lacks Linux-specific instructions or examples for certificate management, DNS configuration, and managed identity setup.
Recommendations
  • Provide Azure CLI and Bash examples for all steps, especially for certificate management, DNS configuration, and managed identity setup.
  • List Bash/Linux examples before or alongside PowerShell/Windows examples to avoid ordering bias.
  • Include references to Linux tools and workflows where applicable, such as OpenSSL for certificate handling.
  • Add explicit instructions for performing tasks on Linux, including command-line alternatives to portal actions.
  • Ensure that all code snippets and examples are cross-platform or clearly indicate platform specificity.
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-develop-create-instance.md ...cles/azure-web-pubsub/howto-develop-create-instance.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and managing resources, but PowerShell is featured equally alongside CLI in all relevant sections. PowerShell is a Windows-centric tool, and its inclusion as a primary method (rather than, for example, Bash or shell scripting) reflects a Windows bias. Additionally, the documentation refers to Azure PowerShell before mentioning Linux equivalents or alternatives, and does not provide any Linux-specific guidance or examples (such as Bash scripts or notes about running CLI commands on Linux/macOS).
Recommendations
  • Prioritize Azure CLI examples, as it is cross-platform, and clarify that CLI commands work on Windows, Linux, and macOS.
  • Add explicit Bash/shell script examples for resource deployment and management to demonstrate Linux parity.
  • Clearly indicate that PowerShell is primarily for Windows users, and provide guidance for Linux/macOS users where appropriate.
  • If PowerShell is included, ensure it is presented after CLI/Bash examples, or in a separate section labeled for Windows users.
  • Include notes or tips about running Azure CLI commands in Bash on Linux/macOS, and mention installation instructions for these platforms.
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: 2026-01-08 00:53
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 using PowerShell and Windows-specific tools (e.g., notepad). There are no examples or guidance for Linux or macOS users, such as using Azure CLI or Linux-native editors. The PowerShell workflow is presented as the only scripting option, and Windows tools are referenced without alternatives.
Recommendations
  • Add equivalent Azure CLI instructions for exporting, editing, and deploying Resource Manager templates, suitable for Linux/macOS users.
  • Replace or supplement 'notepad' references with cross-platform editors (e.g., 'nano', 'vim', 'code', or 'your preferred editor').
  • Explicitly mention that the process can be performed on Linux/macOS and provide relevant command-line examples.
  • Reorder or parallelize sections so that PowerShell and CLI/Linux instructions are presented together, rather than PowerShell first.
  • Include notes or links to platform-specific documentation for both Windows and Linux/macOS users.
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
High Priority View Details →
Scanned: 2026-01-08 00:53
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 PowerShell is featured equally and sometimes first, which can indicate a Windows bias. The prerequisites mention Bash and PowerShell, but clarify that Python, JavaScript, and Java samples require Bash, suggesting partial parity. However, PowerShell is presented as a first-class option throughout, and there are no explicit Linux-specific instructions or troubleshooting notes. The use of PowerShell may be confusing for Linux users, and there are no WSL or native Linux shell alternatives for PowerShell steps. The file editor recommendation (VS Code) is cross-platform, but no Linux-specific editors are mentioned.
Recommendations
  • Clearly indicate when PowerShell is only supported on Windows, and recommend Bash for Linux/macOS users.
  • Provide explicit Linux/macOS instructions for all steps, including environment setup and dependency installation.
  • Add troubleshooting notes for Linux users, especially for PowerShell commands that may not work natively.
  • Consider listing Bash examples before PowerShell to avoid implicit Windows-first bias.
  • Mention Linux-native editors (e.g., Vim, Nano, Gedit) alongside VS Code.
  • Clarify that Azure CLI commands are cross-platform and provide guidance for running them on Linux/macOS.
  • Remove PowerShell examples from steps where Bash is required (e.g., Python, JavaScript, Java samples), or add a note explaining the limitation.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. It references Windows-specific tools (such as the Storage Emulator) without mentioning Linux alternatives, and the troubleshooting note for local development only describes the Windows storage emulator. There is no mention of Linux/macOS equivalents or cross-platform alternatives for storage emulation. The examples and CLI commands themselves are generally cross-platform, but the troubleshooting and tool recommendations prioritize Windows solutions.
Recommendations
  • Explicitly mention and provide instructions for using Azure Storage Emulator alternatives on Linux/macOS, such as Azurite.
  • Add troubleshooting notes for Linux/macOS users, including how to install and run Azurite for local storage emulation.
  • Review all tool recommendations to ensure cross-platform parity, and avoid referencing Windows-only tools without alternatives.
  • Where possible, clarify that Azure CLI and Azure Functions Core Tools are cross-platform and provide installation links for Linux/macOS.
  • Consider adding a section or callouts for Linux/macOS users to ensure their experience is equally supported.
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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates mild Windows bias. Windows command shell usage is mentioned before Bash, and Windows-specific instructions (e.g., using 'set' instead of 'export') are provided more prominently than Linux equivalents. The Java section uses Windows-style 'cmd' for directory creation, and there is frequent mention of Windows command shell alternatives. There are no PowerShell-only examples, but Windows tools and patterns are referenced before or alongside Linux ones.
Recommendations
  • Present Bash/Linux instructions before Windows alternatives, or side-by-side, to avoid implying Windows primacy.
  • Use platform-neutral commands (e.g., 'mkdir' and 'cd' are cross-platform, but avoid 'cmd' prompt style unless necessary).
  • Explicitly state Linux/MacOS compatibility for all steps, and provide equivalent commands for both platforms where environment variable setting differs.
  • Add a table or section summarizing command differences between Windows and Linux/MacOS shells.
  • Avoid mentioning Windows command shell unless there is a specific difference; otherwise, use generic shell terminology.
  • Ensure that all code and CLI examples run as-is on Linux/MacOS, and note any platform-specific caveats.
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/tutorial-serverless-notification.md ...s/azure-web-pubsub/tutorial-serverless-notification.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 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).
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/tutorial-build-chat.md .../main/articles/azure-web-pubsub/tutorial-build-chat.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
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
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
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
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/tutorial-build-chat.md .../main/articles/azure-web-pubsub/tutorial-build-chat.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
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-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Azure Web Pubsub Create an Azure Web PubSub resource ...cles/azure-web-pubsub/howto-develop-create-instance.md
Medium Priority View Details →
Scanned: 2026-01-14 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 resource deployment, review, and cleanup. While Azure CLI is cross-platform, Azure PowerShell is primarily a Windows tool (though it is available on Linux/macOS, it is less commonly used there). PowerShell examples are given equal prominence to CLI, and in some sections, PowerShell is mentioned before CLI. There are no Linux/macOS-specific instructions or examples, and no mention of shell environments like Bash. The documentation assumes familiarity with PowerShell, which may create friction for Linux/macOS users.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Present CLI examples before PowerShell examples, or group them by platform.
  • Add notes clarifying PowerShell availability and usage on non-Windows platforms.
  • Consider including Bash script examples for common tasks.
  • Explicitly mention that all CLI commands work on Linux/macOS terminals.
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-14 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 command-line examples use PowerShell cmdlets, which are native to Windows and require extra setup on Linux/macOS. There are no CLI (az) or Bash examples, and even the editor example uses Notepad, a Windows-only tool. No Linux/macOS-specific guidance or parity is offered.
Recommendations
  • Add equivalent instructions using Azure CLI (az) commands, which are cross-platform.
  • Replace or supplement Notepad references with cross-platform editors (e.g., 'edit with your preferred text editor').
  • Explicitly mention that PowerShell Core is available on Linux/macOS, and provide installation links or notes.
  • Present CLI/Bash examples before or alongside PowerShell examples to avoid Windows-first bias.
  • Include notes or sections for Linux/macOS users, highlighting any differences or requirements.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Bash and Azure PowerShell examples for all CLI steps, but PowerShell is given equal prominence and is sometimes mentioned first. There is a notable bias in the prerequisites and instructions: Bash is required for Python, JavaScript, and Java samples, but no Windows Command Prompt (cmd.exe) or Linux-specific shell examples are provided. The documentation assumes users have access to PowerShell, which is primarily a Windows tool (though available on Linux/macOS), and does not offer native Linux/macOS alternatives for PowerShell commands. There are no explicit Linux/macOS-only instructions or troubleshooting notes, and Windows/PowerShell patterns are presented as the default or only alternative to Bash.
Recommendations
  • Clearly indicate which examples are cross-platform and which are Windows-specific.
  • Provide Linux/macOS-specific instructions or troubleshooting notes, especially for PowerShell commands.
  • Add native Linux shell (e.g., sh, zsh) and Windows Command Prompt (cmd.exe) examples where appropriate.
  • Clarify that PowerShell is available on Linux/macOS, but Bash is preferred for non-Windows platforms.
  • List Bash examples first to reflect the majority of cross-platform developer usage.
  • Explicitly state platform requirements for each language sample (e.g., 'Python sample requires Bash on Linux/macOS, PowerShell on Windows').
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-13 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 command-line examples use PowerShell, and references to tools (e.g., 'notepad') are Windows-specific. There are no CLI or bash examples, nor are cross-platform editors or Linux/macOS alternatives mentioned. The PowerShell section is extensive, while no equivalent Azure CLI or bash workflow is described.
Recommendations
  • Add Azure CLI examples for all steps currently shown with PowerShell, including exporting templates, editing files, deploying resources, and verifying results.
  • Replace or supplement 'notepad' with cross-platform editors (e.g., 'code', 'vim', 'nano') or generic instructions ('edit the file in your preferred editor').
  • Explicitly mention that PowerShell Core is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
  • Reorder or balance examples so that cross-platform methods (Azure CLI, REST API) are presented before or alongside Windows-specific tools.
  • Add notes or sections for Linux/macOS users, highlighting any differences or additional steps.
GitHub Create Pull Request
Azure Web Pubsub include file ...web-pubsub/includes/web-pubsub-add-role-assignments.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Portal Heavy Missing Linux Example
Summary
The documentation focuses almost exclusively on using the Azure portal UI for role assignment, which is platform-agnostic but tends to favor Windows users due to historical usage patterns. While alternative methods (REST API, PowerShell, CLI, ARM templates) are listed at the end, no examples or instructions are provided for command-line approaches, especially those relevant to Linux/macOS users (e.g., Azure CLI). The PowerShell method is mentioned before the CLI, which is more commonly used on Linux/macOS.
Recommendations
  • Add step-by-step examples for Azure CLI usage, highlighting cross-platform compatibility.
  • Provide explicit Linux/macOS command-line instructions alongside PowerShell examples.
  • Reorder alternative method links to list CLI before PowerShell, or group them by platform.
  • Clarify that the portal method is available on all platforms, but command-line methods may be preferred for automation or non-Windows environments.
GitHub Create Pull Request
Azure Web Pubsub Create an Azure Web PubSub resource ...cles/azure-web-pubsub/howto-develop-create-instance.md
Medium Priority View Details →
Scanned: 2026-01-13 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 consistently includes PowerShell (a Windows-centric tool) alongside CLI, and sometimes lists PowerShell examples before or equally with CLI. There is no mention of Linux/macOS-specific shell environments (e.g., Bash), nor any explicit guidance for non-Windows users. The documentation assumes familiarity with PowerShell and does not clarify cross-platform compatibility, which may cause friction for Linux/macOS users.
Recommendations
  • Clearly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit Bash shell examples or clarify that CLI commands work in Bash, Zsh, etc.
  • Relegate PowerShell examples to a separate section or mark them as Windows-specific.
  • Add notes about installing and using Azure CLI on Linux/macOS.
  • Ensure CLI examples are shown first, with PowerShell as an alternative for Windows users.
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-13 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 PowerShell is featured equally and sometimes first, which can be interpreted as a Windows bias. There are no explicit Linux/macOS-specific instructions or troubleshooting notes, and some steps (e.g., Python, JavaScript, Java SDK usage) require Bash, but this is only briefly mentioned. There is no mention of Linux-specific nuances, nor are alternative shells (e.g., zsh, fish) or macOS-specific instructions provided.
Recommendations
  • Clearly indicate which steps are platform-specific, especially where Bash is required for Python, JavaScript, and Java samples.
  • Provide explicit instructions for Linux/macOS users, including shell compatibility notes and troubleshooting tips for common issues (e.g., path separators, environment variable syntax).
  • Add parity for PowerShell Core on Linux/macOS, or clarify that Azure PowerShell examples are for Windows only.
  • Consider listing Bash examples first, as Bash is more universal across platforms.
  • Include notes about alternative editors and shells commonly used on Linux/macOS.
  • Add a table or section summarizing platform compatibility for each step.
GitHub Create Pull Request
Azure Web Pubsub How to collect a network trace ...s/azure-web-pubsub/howto-troubleshoot-network-trace.md
Medium 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 page exhibits mild Windows bias. Fiddler, a tool with historical Windows roots, is presented first and in most detail, despite being cross-platform. The browser section lists Microsoft Edge (Chromium) first, and instructions often mention Windows shortcuts before Linux/macOS equivalents. There is no mention of Linux-native GUI tools (e.g., Wireshark) for network tracing, and tcpdump is only briefly covered for Linux/macOS, with no Windows equivalent (e.g., Wireshark or Windows packet capture tools).
Recommendations
  • Add examples and instructions for Linux-native GUI tools such as Wireshark, including installation and usage steps.
  • Include Windows equivalents for tcpdump (e.g., mention Wireshark or Microsoft Message Analyzer) and clarify cross-platform options.
  • Balance ordering in browser sections by rotating which browser is presented first, or group by OS rather than browser vendor.
  • When listing keyboard shortcuts, present all platforms equally (e.g., Windows, Linux, macOS) rather than Windows first.
  • Expand the tcpdump section to include more detailed usage examples and troubleshooting tips for Linux users.
  • Consider adding a summary table comparing tools available on Windows, Linux, and macOS for network tracing.
GitHub Create Pull Request
Azure Web Pubsub Create an Azure Web PubSub resource ...cles/azure-web-pubsub/howto-develop-create-instance.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying and managing resources, but PowerShell is given equal prominence to Azure CLI, despite PowerShell being primarily a Windows tool. In deployment and resource review/cleanup sections, PowerShell examples are presented alongside CLI, which may suggest a Windows-centric approach. There is no explicit mention of Linux-specific tools or shell environments, nor are there notes about running Azure CLI on Linux or macOS. The documentation does not provide Linux-specific guidance or highlight cross-platform usage beyond Azure CLI.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows.
  • Note that PowerShell examples are primarily for Windows users, and suggest Bash or other shell environments for Linux/macOS users.
  • Provide explicit Bash shell examples for Linux/macOS users where appropriate, especially in sections currently showing only Azure CLI and PowerShell.
  • Add a brief section or note about installing and using Azure CLI on Linux/macOS.
  • Consider listing CLI (cross-platform) examples before PowerShell (Windows-centric) examples to avoid implicit Windows-first bias.
GitHub Create Pull Request
Azure Web Pubsub include file ...web-pubsub/includes/web-pubsub-add-role-assignments.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page primarily describes role assignment using the Azure portal, which is a GUI-centric approach more commonly used on Windows. In the 'Learn more' section, Azure PowerShell is listed before Azure CLI, which is the preferred cross-platform command-line tool for Linux users. There are no explicit Linux-specific examples or references to Linux tools or workflows.
Recommendations
  • Add explicit Linux CLI examples for role assignment, using Azure CLI commands.
  • Ensure Azure CLI is mentioned before Azure PowerShell in lists, as it is cross-platform.
  • Include screenshots or instructions for using the Azure CLI in Linux environments.
  • Clarify that the Azure portal is accessible from any OS/browser, and mention alternatives for users who prefer command-line workflows.
  • Consider adding a section comparing PowerShell and CLI usage for role assignment, highlighting cross-platform compatibility.
GitHub Create Pull Request
Azure Web Pubsub Integrate - Build a real-time collaborative whiteboard using Web PubSub for Socket.IO and deploy it to Azure App Service .../azure-web-pubsub/socket-io-howto-integrate-web-app.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for compressing the application into a zip file, but Bash is presented first and PowerShell is included as an alternative. No Linux-specific tools or patterns are missing, and Azure CLI is cross-platform. However, the explicit inclusion of PowerShell commands and references may indicate a slight Windows bias, especially since PowerShell is not the default shell on Linux systems.
Recommendations
  • Clarify that Bash commands are for Linux/macOS and PowerShell commands are for Windows, to help users quickly identify which instructions apply to their environment.
  • Consider providing Linux-specific notes where relevant (e.g., mention that zip is pre-installed on most Linux distributions, but may require installation on Windows).
  • If possible, add a table or section summarizing commands for different platforms (Windows, Linux, macOS) for common tasks like compression.
  • Ensure that all examples and instructions are equally clear and accessible for both Windows and Linux users, and avoid assuming PowerShell usage unless necessary.
GitHub Create Pull Request
Azure Web Pubsub Quickstart: Create an Azure Web PubSub service with a Bicep file ...articles/azure-web-pubsub/quickstart-bicep-template.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment, resource review, and cleanup. However, PowerShell is featured as a primary option alongside CLI, and there is no mention of Bash, Linux shell, or platform-specific considerations. The use of PowerShell as a first-class example may suggest a Windows-centric approach, as PowerShell is most commonly used on Windows, even though it is available cross-platform. There are no explicit Linux-specific instructions or examples, and the documentation does not address platform differences or recommend Linux-native tooling.
Recommendations
  • Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, while PowerShell is available cross-platform but may require installation on Linux/macOS.
  • Add Bash shell examples or clarify that the Azure CLI commands can be run directly in Bash or other Linux shells.
  • Include notes about installing Azure CLI and PowerShell on Linux/macOS, with links to relevant documentation.
  • Consider listing Azure CLI (which is platform-neutral) before PowerShell in examples to reduce perceived Windows-first bias.
  • Add troubleshooting or environment setup notes for Linux users, such as file path conventions or shell differences.
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 00:00
Reviewed by: LLM Analysis
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 called out explicitly as a required shell in the prerequisites, and PowerShell examples are always presented alongside Bash, sometimes with slightly more detail. There is a subtle Windows bias in the explicit mention of PowerShell and the inclusion of PowerShell examples throughout, even though all actual commands use the cross-platform Azure CLI. There are no Linux-specific tools or patterns mentioned, and Bash is required for most language samples, but Windows/PowerShell is always given equal or slightly more prominence.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, but Bash is preferred for Linux/macOS users.
  • Add explicit instructions for Linux/macOS users where relevant (e.g., activating Python venv, file paths).
  • Consider listing Bash examples first, or making Bash the default, with PowerShell as an alternative for Windows users.
  • Mention that VS Code is cross-platform, and suggest other editors for Linux users.
  • Remove the implication that PowerShell is required for non-Windows platforms; emphasize Bash for Linux/macOS.
GitHub Create Pull Request
← Previous Page 2 of 4 Next →