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 1-25 of 80 flagged pages
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-12 00:00
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 (cmd.exe) is mentioned as an alternative to Bash early in the tutorial, and Windows-specific instructions (such as using 'set' instead of 'export' for environment variables) are provided before or alongside Linux equivalents. Some commands and directory creation steps use Windows syntax (e.g., 'cmd' blocks, single backslashes), and there is an explicit mention of Windows tools and patterns. However, most code and CLI examples are cross-platform, and Linux/Bash instructions are present throughout.
Recommendations
  • Present Linux/Bash instructions before Windows-specific alternatives, or side-by-side, to avoid implying Windows primacy.
  • Clearly mark platform-specific instructions and provide parity for Linux and macOS users (e.g., mention 'export' before 'set').
  • Avoid using Windows-only command syntax (e.g., 'cmd' blocks, backslashes) unless necessary; prefer POSIX-compliant examples.
  • Add explicit notes or tabs for Linux/macOS where Windows alternatives are mentioned.
  • Ensure all tooling and workflow steps are equally documented for Linux (e.g., virtual environment activation, environment variable setting, directory navigation).
GitHub Create Pull Request
Azure Web Pubsub Add a custom domain .../main/articles/azure-web-pubsub/howto-custom-domain.md
High Priority View Details →
Scanned: 2026-01-12 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 by presenting PowerShell/cmd examples before Bash, referencing Windows-specific tools (curl.exe, PS prompt), and using screenshots and instructions that are tailored to the Azure Portal GUI, which is more familiar to Windows users. There is little mention of Linux-specific workflows, and command-line examples default to Windows conventions.
Recommendations
  • Present Bash/Linux examples before or alongside PowerShell examples, especially in command-line sections.
  • Use platform-neutral commands and prompts (e.g., 'curl' instead of 'curl.exe', '$' instead of 'PS C:\>').
  • Include instructions and screenshots for Azure CLI and cross-platform tools, not just the Azure Portal GUI.
  • Explicitly mention Linux and macOS compatibility where relevant, and provide guidance for those platforms.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., certificate validation, DNS configuration).
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-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. The PowerShell section is extensive and uses Windows-centric tools (e.g., notepad for editing JSON files), with no mention of Linux or cross-platform CLI alternatives. There are no Bash, Azure CLI, or Linux editor examples, and PowerShell is presented as the only scripting option. This creates a bias towards Windows users and workflows.
Recommendations
  • Add equivalent instructions using Azure CLI (az) commands, which are cross-platform and widely used on Linux and macOS.
  • Include examples for editing JSON files using cross-platform editors (e.g., vim, nano, code) or generic instructions not tied to notepad.
  • Explicitly mention that PowerShell Core is available cross-platform, or provide Bash script alternatives for Linux users.
  • Reorder or parallelize the documentation so that Azure CLI and PowerShell instructions are presented together, rather than PowerShell-only.
  • Add notes or links for Linux/macOS users on how to perform each step, including authentication and file manipulation.
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-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 PowerShell is given equal prominence to Bash, and is explicitly called out as a required shell in prerequisites. There is a slight Windows bias in the consistent inclusion of Azure PowerShell examples, even for steps that are natively cross-platform (Azure CLI), and in the assumption that users may use PowerShell locally. There are no explicit Linux-only examples or mentions of Linux-specific tools or patterns. The language SDK examples (Python, JavaScript, Java, C#) are Bash-centric, but the overall parity between Windows and Linux is not fully clear, and PowerShell is sometimes presented before Bash in variable naming conventions and explanations.
Recommendations
  • Clarify that Azure CLI commands work equally well on Linux, macOS, and Windows, and that Bash is available on all platforms.
  • Make Bash the default/primary example, with PowerShell as an optional tab for Windows users.
  • Add explicit notes for Linux/macOS users, including shell environment setup and common editors (e.g., mention nano/vim in addition to VS Code).
  • Where PowerShell is used, explain its cross-platform availability, or clarify when it is Windows-specific.
  • Consider including Linux-specific troubleshooting or environment setup steps, such as package manager commands for dependencies.
  • Avoid listing PowerShell as a prerequisite unless it is strictly required; emphasize Bash or sh for cross-platform compatibility.
GitHub Create Pull Request
Azure Web Pubsub Tutorial - Visualize IoT device data from IoT Hub using Azure Web PubSub service and Azure Functions ...n/articles/azure-web-pubsub/tutorial-serverless-iot.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. It references Windows-specific tools (Storage Emulator), mentions enabling the Storage Emulator for local development without suggesting Linux/macOS alternatives, and refers to PowerShell modules and commands. There is no mention of Linux/macOS equivalents for the Storage Emulator, nor are cross-platform alternatives or instructions provided for those environments. The order of presentation and tool recommendations (e.g., Storage Emulator) assume a Windows environment by default.
Recommendations
  • Explicitly mention and provide instructions for using Azure Storage Emulator alternatives on Linux/macOS, such as Azurite.
  • When referencing PowerShell or Windows-specific tools, also provide equivalent Bash/Azure CLI commands and instructions for Linux/macOS users.
  • Add notes or sections clarifying cross-platform compatibility for all tools and commands.
  • Ensure that examples and troubleshooting steps do not assume a Windows environment by default; present cross-platform options equally or in parallel.
  • Where possible, use platform-neutral language and tools (e.g., recommend Azurite for local storage emulation instead of Storage Emulator).
GitHub Create Pull Request
Azure Web Pubsub How to collect a network trace ...s/azure-web-pubsub/howto-troubleshoot-network-trace.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias. Windows tools and patterns (e.g., Fiddler, Microsoft Edge) are mentioned first or given prominence. The Fiddler section, while noting cross-platform availability, is presented before Linux-native tools like tcpdump. Browser instructions consistently list Windows shortcuts before macOS/Linux equivalents. There is no PowerShell-specific example, but Windows-centric navigation and tool choices are emphasized.
Recommendations
  • Present Linux-native tools (e.g., tcpdump, Wireshark) before or alongside Windows tools, especially in sections not inherently Windows-specific.
  • Include explicit Linux command-line examples for exporting or analyzing traces (e.g., using tshark or tcpdump filters).
  • Balance shortcut key instructions by listing macOS/Linux first in some cases, or grouping them together.
  • Add guidance for Linux users on installing and using Fiddler, including any platform-specific caveats.
  • Consider mentioning other Linux-friendly tools (e.g., Wireshark, ngrep) to broaden options.
GitHub Create Pull Request
Azure Web Pubsub Create an Azure Web PubSub resource ...cles/azure-web-pubsub/howto-develop-create-instance.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 presented as a first-class option alongside CLI, which may indicate a Windows bias. PowerShell is a Windows-centric tool, and its inclusion and prominence (equal tabbing, explicit mention) can be seen as favoring Windows users. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-native tools or workflows. The documentation does not clarify that Azure CLI is cross-platform, nor does it provide guidance for Linux users regarding PowerShell's availability or alternatives.
Recommendations
  • Clarify that Azure CLI is cross-platform and works natively on Linux and macOS.
  • Add explicit Bash shell examples where appropriate, especially for resource deployment and management.
  • Note that Azure PowerShell is available on Linux and macOS via PowerShell Core, but CLI is generally preferred for Linux users.
  • Consider reordering examples to present CLI/Bash first, then PowerShell, to avoid implicit Windows-first bias.
  • Add a brief section or tip for Linux users about installing and using Azure CLI and PowerShell Core.
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-11 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 given in PowerShell. Windows-specific tools (e.g., notepad) are referenced, and there are no CLI or bash examples for Linux/macOS users. The PowerShell workflow is presented as the only scriptable option, and Windows tools are mentioned without alternatives.
Recommendations
  • Add equivalent Azure CLI (az) examples for exporting, editing, and deploying Resource Manager templates, which are cross-platform.
  • Replace or supplement references to 'notepad' with cross-platform editors (e.g., 'code', 'vim', 'nano', or 'your preferred editor').
  • Explicitly mention that PowerShell Core is available on Linux/macOS, or provide bash script alternatives.
  • Ensure that instructions for deleting resources include both PowerShell and Azure CLI commands.
  • Reorder sections or provide parallel instructions so that Linux/macOS-friendly methods (Azure CLI, bash) are not presented as secondary or omitted.
GitHub Create Pull Request
Azure Web Pubsub include file ...web-pubsub/includes/web-pubsub-add-role-assignments.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily describes role assignment using the Azure portal, which is a graphical interface most commonly used on Windows. The list of further reading links mentions Azure PowerShell before Azure CLI, despite CLI being more cross-platform and preferred on Linux. There are no explicit Linux or cross-platform command-line examples, nor is there mention of Linux-specific workflows or tools.
Recommendations
  • Provide explicit Azure CLI examples for role assignment, as CLI is cross-platform and preferred on Linux.
  • Mention that the Azure portal is accessible from any OS/browser, but also highlight command-line alternatives for automation and Linux users.
  • Reorder the 'Learn more' links to list Azure CLI before PowerShell, or group them together as cross-platform options.
  • Include a note or section for Linux users, suggesting best practices and tools for role assignment from Linux environments.
GitHub Create Pull Request
Azure Web Pubsub Add a custom domain .../main/articles/azure-web-pubsub/howto-custom-domain.md
High Priority View Details →
Scanned: 2026-01-11 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 and Windows command-line examples (curl.exe) are presented before Bash/Linux equivalents, and screenshots and instructions consistently reference the Azure Portal UI, which is more familiar to Windows users. There is no mention of Linux-specific tools or command-line patterns outside of a single Bash/cURL example, and the PowerShell example uses Windows-style paths and tools (curl.exe).
Recommendations
  • Present Bash/Linux examples before or alongside PowerShell/Windows examples, rather than after.
  • Use platform-neutral tools and commands (e.g., 'curl' instead of 'curl.exe') in examples.
  • Include CLI-based instructions using Azure CLI for both Linux and Windows users, not just portal-based steps.
  • Add notes or sections highlighting any platform-specific differences or requirements.
  • Ensure screenshots and UI references are supplemented with equivalent CLI commands for users who prefer or require non-GUI workflows.
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-11 00:00
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 called out in multiple places. The initial environment setup notes Windows cmd.exe as an alternative, but does not equally highlight Linux or macOS shells. Java project setup uses Windows-style 'cmd' blocks for directory creation, and there is no explicit mention of Linux/macOS equivalents for activating Python virtual environments or running commands. No PowerShell-specific examples are present, but Windows command patterns are referenced more frequently and sometimes first.
Recommendations
  • Present Linux/macOS and Windows command shell instructions side-by-side, or default to cross-platform syntax where possible.
  • Explicitly mention Linux/macOS alternatives for commands like 'set' (use 'export'), and for activating Python virtual environments (e.g., 'source env/bin/activate' vs 'env\Scripts\activate').
  • Avoid using Windows-specific command blocks (e.g., 'cmd') unless necessary, and provide Bash equivalents.
  • Where environment setup is described, equally highlight Bash/zsh/fish shells and Linux/macOS platforms.
  • Add notes or tabs for PowerShell, Bash, and other shells if command syntax differs.
  • Review all examples to ensure Linux users are not required to infer or adapt Windows instructions.
GitHub Create Pull Request
Azure Web Pubsub Tutorial - Visualize IoT device data from IoT Hub using Azure Web PubSub service and Azure Functions ...n/articles/azure-web-pubsub/tutorial-serverless-iot.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. It references Windows-specific tools such as the Azure Storage Emulator without mentioning Linux alternatives, and the instructions for local development and troubleshooting (e.g., storage emulator) are Windows-centric. The documentation does not provide explicit Linux equivalents or guidance for Linux users in these areas, and the mention of the emulator appears before any cross-platform alternatives. However, most CLI and code examples are cross-platform, and there is no heavy use of PowerShell or Windows-only commands.
Recommendations
  • Explicitly mention and provide instructions for Linux/macOS equivalents of the Azure Storage Emulator, such as Azure Storage Azurite.
  • Add notes or sections for Linux/macOS users where Windows-specific tools (e.g., Storage Emulator) are referenced.
  • Ensure troubleshooting steps and environment setup instructions cover both Windows and Linux/macOS platforms.
  • Where possible, use cross-platform terminology and avoid assuming a Windows environment in examples and notes.
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 instructions for environment variable setting explicitly call out Windows (using 'set') before Linux ('export'). The phrase 'You can use the Windows cmd.exe command shell instead of a Bash shell' is presented early, suggesting Windows as a default. The Java section uses 'cmd' for directory creation, and there are occasional references to Windows-specific patterns. However, most code samples and CLI instructions are cross-platform, and Bash is used in most examples.
Recommendations
  • Present Bash/Linux instructions before Windows equivalents, or side-by-side, to avoid suggesting Windows as the default.
  • Use neutral language when referring to shells (e.g., 'In Bash, use export; in Windows cmd.exe, use set').
  • Ensure all examples and instructions are explicitly cross-platform, and avoid using Windows-specific commands (such as 'cmd') unless necessary.
  • Add explicit Linux/macOS instructions where Windows alternatives are mentioned.
  • Consider including a table or section summarizing shell differences for environment variable setting and command execution.
GitHub Create Pull Request
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 demonstrates a Windows bias in several ways. PowerShell/Windows examples are presented first in code tabs, with explicit use of 'PS C:\>' and 'curl.exe', while Bash/Linux examples are secondary. The use of Windows-specific command prompts and tools (curl.exe) further reinforces the bias. There are no Linux-first or cross-platform neutral instructions, and screenshots and instructions are exclusively based on the Azure Portal UI, which is platform-agnostic but does not address CLI or automation scenarios that are common on Linux.
Recommendations
  • Present Bash/Linux examples before or alongside PowerShell/Windows examples in code tabs.
  • Use platform-neutral command syntax (e.g., 'curl' instead of 'curl.exe') in examples.
  • Include Azure CLI instructions for key steps (e.g., managed identity, certificate upload, DNS record creation) to support Linux and automation users.
  • Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and provide parity in example commands.
  • Add screenshots or instructions for Azure CLI/Cloud Shell usage, which is accessible from any platform.
GitHub Create Pull Request
Azure Web Pubsub Create an Azure Web PubSub resource ...cles/azure-web-pubsub/howto-develop-create-instance.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 provides examples for both Azure CLI and Azure PowerShell when deploying and managing resources, but PowerShell is given equal prominence to CLI, despite being a Windows-centric tool. There are no explicit Linux shell examples (e.g., Bash scripts), and PowerShell is presented as the alternative to CLI, which may suggest a Windows-first approach. The documentation does not mention or provide examples for Linux-specific tools or patterns, nor does it clarify CLI usage on Linux/macOS platforms.
Recommendations
  • Clarify that Azure CLI works cross-platform (Windows, Linux, macOS) and provide explicit Bash/shell examples where appropriate.
  • De-emphasize PowerShell as the primary alternative to CLI, or note that PowerShell Core is available cross-platform.
  • Add notes or examples for Linux/macOS users, such as using Bash or Zsh, and mention installation steps for Azure CLI on those platforms.
  • If PowerShell is included, clarify its cross-platform availability or provide links to installation instructions for Linux/macOS.
  • Ensure that instructions and screenshots do not assume a Windows environment unless necessary.
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. All command-line examples use PowerShell, and Windows-specific tools (e.g., notepad) are referenced. There are no CLI (az), Bash, or Linux/macOS shell examples, nor are cross-platform editor alternatives mentioned. The PowerShell method is presented as the only scripting option, which may exclude Linux/macOS users or those who prefer Azure CLI.
Recommendations
  • Add equivalent instructions and examples using Azure CLI (az), which is cross-platform and widely used on Linux/macOS.
  • Replace or supplement references to Windows-only tools (e.g., 'notepad') with cross-platform editors (e.g., 'code', 'vim', 'nano', or generic 'open in your preferred editor').
  • Explicitly mention that PowerShell is available cross-platform, but provide Bash/Azure CLI alternatives for each step.
  • Ensure that all command-line steps are shown for both PowerShell and Azure CLI, with clear headings for each.
  • Review and update the documentation to avoid assuming a Windows environment, especially in sections about file editing and command execution.
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 referenced in prerequisites as a required shell. There is a slight Windows bias in the explicit mention of PowerShell and the use of PowerShell syntax, which is primarily relevant for Windows users. There are no Linux-specific examples (e.g., zsh, fish, or Linux-native tools), and PowerShell is listed as a prerequisite alongside Bash, which may imply parity or preference for Windows environments. The file editor recommendation (VS Code) is cross-platform, but no Linux-specific editors are mentioned. The SDK usage examples for Python, JavaScript, and Java require Bash, but this is only noted in passing.
Recommendations
  • Clarify that PowerShell is optional and primarily for Windows users, while Bash is standard for Linux/macOS.
  • Add explicit Linux/macOS instructions or notes, such as using native shells (zsh, fish) and editors (vim, nano, gedit).
  • In prerequisites, list Bash first and PowerShell as an alternative for Windows users.
  • Provide troubleshooting notes for Linux/macOS users, such as handling environment variables and file paths.
  • Consider including screenshots or terminal output from Linux/macOS environments to balance visual representation.
  • Where possible, highlight cross-platform compatibility of Azure CLI and SDKs.
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: 2026-01-09 00:34
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: PowerShell/Windows examples are presented before Linux/Bash equivalents, especially in the 'Verify your custom domain' section, where the PowerShell/curl.exe example is listed first. The use of Windows-specific tools (curl.exe, PS prompt) is prominent, and there is a lack of parity in instructions for Linux users in other sections (e.g., portal navigation, certificate management) where only GUI steps are described, which may differ on Linux. There are no CLI or automation examples using Azure CLI or Bash for key steps like managed identity setup, certificate addition, or DNS record creation.
Recommendations
  • Present Bash/Linux examples before or alongside PowerShell/Windows examples, especially in code tabs.
  • Include Azure CLI and Bash command examples for all major steps, such as managed identity setup, certificate addition, and DNS record creation.
  • Avoid Windows-specific tool references (e.g., curl.exe, PS C:\>) unless necessary; use platform-neutral commands (e.g., curl).
  • Clarify that portal instructions apply equally to all platforms, or provide CLI alternatives for users who prefer command-line interfaces.
  • Explicitly mention Linux and macOS support and provide troubleshooting notes for non-Windows environments where relevant.
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-09 00:34
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 Bicep deployments, resource listing, and cleanup. However, PowerShell is featured alongside CLI in every example, and is mentioned as an equal alternative for deployment and management tasks. This can be interpreted as a Windows bias, since PowerShell is primarily a Windows tool (though available cross-platform), and no Linux-specific shell examples (e.g., Bash) or explicit Linux instructions are given. The documentation does not mention or show Linux terminal screenshots, nor does it address Linux-specific considerations, which may leave Linux users feeling secondary.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
  • Add explicit Bash shell examples or notes for Linux users, especially for file paths and environment setup.
  • Include screenshots or instructions showing usage from a Linux terminal.
  • Mention that PowerShell is available on Linux, but that Bash is the default shell for most Linux distributions.
  • Consider listing CLI (Bash) examples before PowerShell, or providing a Linux-first workflow.
  • Add troubleshooting notes or tips for Linux users where relevant (e.g., file permissions, path formats).
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/howto-troubleshoot-network-trace.md ...s/azure-web-pubsub/howto-troubleshoot-network-trace.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. Fiddler, a cross-platform tool, is presented first, but its usage is most familiar to Windows users and its UI instructions are Windows-centric. The browser DevTools instructions consistently list Windows keyboard shortcuts before macOS/Linux equivalents, and menu navigation is described in terms most familiar to Windows users. There is no mention of Linux-native GUI network trace tools (e.g., Wireshark), and the tcpdump section is brief and lacks parity with the Fiddler section (no export instructions, no GUI alternatives). No PowerShell examples are present, but the overall structure and ordering favor Windows tools and workflows.
Recommendations
  • Add Linux-native GUI tools (e.g., Wireshark) as alternatives to Fiddler, with installation and usage instructions.
  • Expand the tcpdump section to include instructions for exporting and analyzing traces, and mention tools for viewing .pcap files (e.g., Wireshark, tshark).
  • Present keyboard shortcuts and menu navigation for all platforms in parallel, not Windows-first.
  • Include more detailed Linux/macOS examples for network trace collection, including troubleshooting permissions and interface selection.
  • Where possible, balance the ordering of Windows and Linux/macOS instructions, or provide platform-specific subsections.
GitHub Create Pull Request
Azure Web Pubsub https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/quickstart-bicep-template.md ...articles/azure-web-pubsub/quickstart-bicep-template.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell is a Windows-centric tool, and its inclusion alongside CLI in every example may suggest a Windows bias. The documentation refers to PowerShell before CLI in the description and prerequisites, and does not mention Linux-specific shell environments (e.g., Bash) or provide guidance for Linux users. There is no explicit mention of Linux or macOS compatibility, nor are there examples tailored to those platforms.
Recommendations
  • Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and recommend it as the default for non-Windows users.
  • Add Bash-specific instructions or notes for Linux/macOS users, such as file path conventions and shell usage.
  • Reorder example sections to present Azure CLI before PowerShell, or clarify that CLI is platform-agnostic.
  • Include a note that PowerShell Core is available on Linux/macOS, if relevant, and provide installation guidance.
  • Add a 'Platform compatibility' section to clarify which tools work on which operating systems.
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-09 00:34
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 and tooling focused exclusively on PowerShell. There are no examples or guidance for Linux/macOS users, such as using Azure CLI or cross-platform editors. Windows-specific tools (e.g., Notepad) are referenced, and PowerShell is presented as the only scripting option, indicating a Windows-centric approach.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands to support Linux/macOS users.
  • Replace or supplement 'notepad' references with cross-platform editors (e.g., 'code', 'vim', 'nano', or 'your preferred editor').
  • Explicitly mention that both Azure CLI and PowerShell can be used, and provide links to relevant CLI documentation.
  • Ensure that instructions do not assume a Windows environment; clarify steps for Linux/macOS where appropriate.
  • Consider reordering examples so that cross-platform options (Azure CLI, editors) are presented before or alongside Windows-specific tools.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. It references Windows-specific tools (e.g., Storage Emulator), mentions Windows patterns (such as using Visual Studio Code and Storage Emulator) without Linux alternatives, and includes PowerShell/Azure CLI commands but does not clarify Linux-specific differences or provide Linux-first instructions. The Storage Emulator is a Windows-only tool, and no mention is made of cross-platform alternatives like Azurite. The tutorial assumes familiarity with Windows environments and does not address Linux-specific setup or troubleshooting.
Recommendations
  • Explicitly mention and provide instructions for Linux/macOS users, especially for local Azure Storage emulation (e.g., recommend Azurite for non-Windows platforms).
  • Where Windows-only tools are referenced (e.g., Storage Emulator), add cross-platform alternatives and usage notes.
  • Ensure all CLI commands are verified to work on Linux/macOS and note any differences (such as file paths, permissions, or shell syntax).
  • Provide troubleshooting steps for common Linux/macOS issues (e.g., port conflicts, permissions, environment variables).
  • Add a section or callouts for Linux/macOS users in prerequisites and setup steps, including editor recommendations and platform-specific tips.
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-09 00:34
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 featured as a primary shell alongside Bash, and is referenced throughout. The prerequisites mention both Bash and PowerShell, but clarify that Python, JavaScript, and Java samples require Bash, implying limited Linux/Unix parity for PowerShell users. There are no explicit Linux-specific instructions or examples (e.g., for native Linux tools, environment setup, or shell differences). Windows-centric tools (PowerShell) are presented equally or before Linux equivalents, and there is no mention of Linux distributions, package managers, or troubleshooting for Linux environments.
Recommendations
  • Clarify that Azure PowerShell is primarily for Windows, and Bash is recommended for Linux/macOS users.
  • Add explicit instructions for Linux users, such as using package managers (apt, yum, etc.) to install prerequisites.
  • Provide troubleshooting notes for common Linux issues (e.g., permissions, path differences).
  • Consider including a Linux-specific tab or section for environment setup and shell usage.
  • Mention cross-platform compatibility of Azure CLI and SDKs, and highlight differences in shell commands where relevant.
  • List Bash examples first to reflect the prevalence of Linux/macOS in cloud development.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits 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 initial environment setup mentions Windows cmd.exe as an alternative, and Java project directory creation uses 'cmd' syntax. There are no PowerShell-specific examples, but Windows command patterns and terminology are referenced more frequently and earlier than Linux equivalents.
Recommendations
  • Present Linux/Bash instructions before Windows alternatives, or side-by-side, to avoid implying Windows is the default.
  • Include explicit instructions for Linux and macOS users wherever Windows-specific commands or terminology are mentioned.
  • Use cross-platform command syntax (e.g., 'mkdir' and 'cd' are universal, but avoid 'cmd' blocks unless necessary).
  • Add notes for activating Python virtual environments on Windows (e.g., 'env\Scripts\activate') as well as Linux/macOS ('source ./env/bin/activate').
  • Where environment variables are set, show both 'export' (Linux/macOS) and 'set' (Windows) together, or use a table for clarity.
  • Avoid phrases like 'You can use the Windows cmd.exe command shell instead of a Bash shell' unless Bash is actually the default; clarify parity.
GitHub Create Pull Request
← Previous Page 1 of 4 Next →