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 51-75 of 80 flagged pages
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 →
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 used in the main workflow. PowerShell is mentioned as an alternative, but there is a slight Windows bias in explicitly calling out PowerShell and providing its command, which may not be necessary if Bash is the default. However, most of the guide uses cross-platform tools (Azure CLI, git, npm) and does not rely on Windows-specific tools or patterns.
Recommendations
- Clarify that Bash commands are suitable for both Linux and macOS, and PowerShell is for Windows users.
- Consider grouping platform-specific instructions under clear headings, such as 'On Linux/macOS' and 'On Windows', to improve clarity.
- Ensure that all steps that may differ between platforms (e.g., file compression) provide parity in explanation and troubleshooting.
- Add a note about using Windows Subsystem for Linux (WSL) for Windows users who prefer Bash.
- Review future documentation to avoid unnecessary emphasis on Windows tools when cross-platform alternatives are available.
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 →
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 equally alongside CLI, despite being primarily a Windows tool. There is no explicit mention of Linux-specific patterns, nor are Linux shell examples (e.g., Bash) provided. The documentation refers to 'Azure PowerShell' without clarifying its cross-platform availability, and does not offer guidance for Linux users beyond the CLI.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
- Add explicit Bash shell examples where appropriate, especially for file operations (e.g., saving the Bicep file).
- Note that Azure PowerShell is available on Linux/macOS, but CLI is generally preferred for those platforms.
- Consider reordering examples to present Azure CLI first, and PowerShell second, to avoid implicit Windows-first bias.
- Add a brief section or note addressing Linux/macOS users, confirming that all steps can be performed on those platforms using Azure CLI.
Azure Web Pubsub
How to collect a network trace
...s/azure-web-pubsub/howto-troubleshoot-network-trace.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page shows mild Windows bias by listing Fiddler (a tool with strong Windows heritage) first and providing menu instructions that use Windows terminology (e.g., 'File > Save > All Sessions'). In the browser section, Microsoft Edge is described before Chrome, Firefox, and Safari, and the instructions often mention Windows/Linux shortcuts before macOS. There are no PowerShell-specific examples, and Linux/macOS tools (tcpdump) are covered, but only after Fiddler. The tcpdump section is clearly marked as 'macOS and Linux only', but Windows alternatives (e.g., Wireshark CLI, netsh trace) are not discussed.
Recommendations
- Add examples for Windows-native command-line tools (e.g., netsh trace, Wireshark CLI) to balance the tcpdump section.
- Provide Linux/macOS-specific menu instructions for Fiddler, or clarify differences in UI across platforms.
- Consider listing cross-platform tools (like tcpdump and Wireshark) before platform-specific ones (like Fiddler) to avoid Windows-first ordering.
- In browser sections, alternate the order of browsers or group by OS to avoid implicit prioritization of Microsoft Edge.
- Explicitly mention platform equivalence in shortcut keys and menu paths, rather than listing Windows/Linux first.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on the Azure portal graphical interface for role assignment, which is most commonly accessed via Windows environments. There are no command-line examples shown directly in the main instructions, and the only explicit tool mentioned in the step-by-step guide is the Azure portal. While links to PowerShell and Azure CLI instructions are provided at the end, no Linux-specific or CLI-based examples are given in the main flow, and PowerShell (a Windows-centric tool) is listed before Azure CLI in the further reading section.
Recommendations
- Add step-by-step examples for assigning roles using Azure CLI directly in the main instructions, as Azure CLI is cross-platform and widely used on Linux.
- Ensure that PowerShell and Azure CLI are presented together, or list Azure CLI before PowerShell to avoid Windows-first bias.
- Explicitly mention that the Azure portal is accessible from any OS, but also provide parity for users who prefer or require command-line tools.
- Include screenshots or code snippets for both CLI and portal workflows, highlighting cross-platform compatibility.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for compressing files, but PowerShell is mentioned explicitly and separately, which may suggest a Windows bias. Bash is presented first, but the inclusion of PowerShell commands and the explicit labeling of 'Use PowerShell' can be interpreted as catering to Windows users. No Linux-specific tools or troubleshooting are mentioned, and there is no explicit parity discussion for Linux environments beyond Bash.
Recommendations
- Ensure that Linux and macOS users are addressed explicitly, not just by providing Bash commands but by mentioning compatibility and potential issues.
- Include troubleshooting or environment notes for Linux/macOS users, such as file permissions, zip tool installation, or alternative commands if zip is not available.
- Add a note clarifying that Bash commands work on Linux and macOS, and PowerShell commands are for Windows users.
- Consider including examples for other common Linux utilities (e.g., tar) or mentioning WSL for Windows users who prefer a Linux-like environment.
- Review the order and prominence of examples to avoid implying Windows is the primary or default platform.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation primarily describes role assignment using the Azure portal, which is a graphical interface most commonly used on Windows. In the 'Learn more' section, Azure PowerShell is listed before Azure CLI, suggesting a Windows-first approach. There are no direct Linux-specific examples or screenshots, and command-line instructions (CLI or PowerShell) are not included in the main steps, which could disadvantage Linux users.
Recommendations
- Provide step-by-step instructions for role assignment using Azure CLI alongside (or before) PowerShell, as CLI is cross-platform and preferred by many Linux users.
- Include screenshots or terminal examples for Azure CLI usage on Linux.
- Explicitly mention that the Azure portal is accessible from any OS/browser, but also highlight command-line alternatives for non-Windows environments.
- Ensure that PowerShell and CLI documentation are given equal prominence in 'Learn more' sections, or list CLI first to reflect its cross-platform nature.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for compressing files, but Bash is listed first and PowerShell is included as an alternative. There is no exclusive use of Windows tools or patterns, and Linux workflows (via Bash) are present throughout. However, the explicit inclusion of PowerShell commands and mention of Windows tooling may indicate a slight Windows bias, especially for users who expect Linux-first documentation in cloud-native contexts.
Recommendations
- Ensure Bash/Linux examples are always presented first and clearly marked as the default workflow.
- Add explicit notes clarifying platform compatibility for each command (e.g., 'Use Bash on Linux/macOS, PowerShell on Windows').
- Consider including zsh or other popular Linux shell variants if relevant.
- Where possible, provide troubleshooting tips for both Windows and Linux users.
- Review other sections for subtle Windows-first language or assumptions and balance with Linux/macOS equivalents.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates mild Windows bias by listing Fiddler—a tool strongly associated with Windows—first and providing detailed instructions for its use, even though it is cross-platform. The browser section consistently lists Windows keyboard shortcuts before macOS equivalents, and the Edge section is given priority over Chrome, Firefox, and Safari. There is no mention of Linux-native GUI tools (e.g., Wireshark) for network tracing, and Windows-centric patterns (such as menu navigation and shortcut keys) are presented before Linux/macOS alternatives.
Recommendations
- Add examples and instructions for Linux-native tools such as Wireshark and tshark, alongside tcpdump.
- When listing keyboard shortcuts, alternate the order between Windows and macOS/Linux, or present them together to avoid platform prioritization.
- Consider listing browser sections in alphabetical order or by market share, rather than prioritizing Microsoft Edge.
- Explicitly mention cross-platform compatibility for all tools, and provide installation instructions for Linux where relevant.
- Include screenshots or instructions for Linux desktop environments where applicable (e.g., GNOME, KDE).
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 →
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 PowerShell is mentioned explicitly and given equal prominence, despite Bash being the default on most Linux/macOS systems. The mention of PowerShell may imply a Windows-first audience. However, the rest of the guide uses Azure CLI commands, which are cross-platform, and the prerequisites do not mention Windows-specific tools. There is no explicit omission of Linux equivalents, but the inclusion of PowerShell commands alongside Bash may signal a slight Windows bias.
Recommendations
- Clarify that Bash commands work on Linux/macOS and PowerShell commands are for Windows users.
- List Bash examples first, as Linux is the default environment for many cloud developers.
- Add a note specifying which command to use based on the user's operating system.
- Consider referencing WSL (Windows Subsystem for Linux) for Windows users who prefer Bash.
- Ensure that all steps are equally clear for both Linux/macOS and Windows users.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying and managing Azure Web PubSub resources with Bicep. However, PowerShell is featured equally alongside Azure CLI, and there is no explicit mention of Linux-specific tools or shell environments (such as Bash). The use of PowerShell, which is traditionally associated with Windows, and the lack of explicit Linux shell examples or references, indicates a mild Windows bias. There are no examples using Bash, nor any mention of Linux-specific considerations.
Recommendations
- Explicitly mention that Azure CLI commands can be run in Bash on Linux/macOS, and provide example commands in a Bash context.
- Clarify that PowerShell examples are cross-platform (if using PowerShell Core), or specify if they are Windows-only.
- Add notes or tabs for Bash or Linux terminal usage where relevant, especially in deployment and resource management sections.
- Ensure parity by referencing Linux and macOS environments in prerequisites and instructions, not just Windows/PowerShell.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and Azure PowerShell examples for all CLI operations, but PowerShell is consistently presented as an equal alternative rather than a secondary or optional one. In the prerequisites, both Bash and PowerShell are listed, but it is noted that Python, JavaScript, and Java samples require Bash. However, PowerShell examples are still provided for all CLI steps, which may suggest a slight Windows bias by giving PowerShell parity with Bash even when Bash is required for the main language samples. Additionally, PowerShell is mentioned before Bash in the prerequisites, and PowerShell-specific variable syntax and command formatting are used throughout.
Recommendations
- Clarify that Bash is the primary supported shell for non-.NET SDKs and that PowerShell examples are optional or secondary.
- Present Bash examples first in all code tabs and sections, especially since most SDK samples require Bash.
- Explicitly note any limitations of PowerShell usage with the SDKs (e.g., if certain language samples cannot be run in PowerShell).
- Consider reducing the prominence of PowerShell examples or moving them to an appendix or 'Windows-specific' section to avoid implying equal support.
- Ensure that all instructions and environment variable usage are cross-platform and avoid Windows-centric patterns unless necessary.
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 →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates mild Windows bias by referencing Windows command shells and tools before or in preference to Linux equivalents. For example, it mentions using Windows cmd.exe as an alternative to Bash, and in several places, it provides Windows-specific instructions (such as using 'set' instead of 'export') before or alongside Linux commands. Additionally, the Java quickstart uses a Windows-style 'cmd' code block for directory creation, even though the rest of the instructions are cross-platform.
Recommendations
- Present Linux and Windows command instructions in parallel, using tabbed or side-by-side formatting, rather than mentioning Windows as an alternative to Bash.
- When referencing environment variable setting (e.g., 'export' vs 'set'), provide both commands explicitly in a tabbed or clearly separated format, rather than as a parenthetical note.
- For directory creation and navigation, use cross-platform commands (e.g., 'mkdir', 'cd') in a neutral shell format, or provide both Bash and cmd/PowerShell equivalents.
- Avoid using Windows-specific code block annotations (e.g., 'cmd') unless absolutely necessary; prefer 'bash' or a neutral format.
- Ensure that any references to tools or shells do not assume Windows as the default or primary environment.
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
Medium Priority
View Details →
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 given equal prominence to Azure CLI, despite being a Windows-centric tool. There is no explicit mention of Linux-specific tools or shell environments (such as Bash), and PowerShell is presented as a primary option alongside Azure CLI, which may suggest a bias towards Windows users.
Recommendations
- Clarify that Azure CLI commands are cross-platform and can be used on Windows, Linux, and macOS.
- Consider providing Bash shell examples or explicitly mentioning that CLI commands work in Bash/Terminal on Linux/macOS.
- If PowerShell is included, note that it is available cross-platform, but that Bash is the default shell on most Linux systems.
- Add a section or note for Linux/macOS users, confirming that all CLI steps are fully supported on those platforms.
- Avoid presenting PowerShell as an equally primary option unless there is a specific need for it, or at least indicate the typical platform usage for each tool.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for compressing files, but Bash is presented first and more prominently. There is no exclusive focus on Windows tools, and Linux workflows are included throughout, especially in the deployment steps. However, the explicit labeling of 'Use Bash' and 'Use PowerShell' and the inclusion of PowerShell commands may indicate a slight Windows bias, especially since PowerShell is not as commonly used on Linux. All other steps use cross-platform tools (Azure CLI, git, npm), and there are no Windows-only tools or patterns.
Recommendations
- Ensure that both Bash and PowerShell examples are given equal prominence and are clearly marked as platform-specific (e.g., 'For Linux/macOS' and 'For Windows').
- Consider providing a table or side-by-side comparison for commands that differ by platform, rather than listing Bash first and PowerShell second.
- Explicitly mention which OS each command is for, and clarify that Bash commands work on Linux/macOS and PowerShell on Windows.
- If possible, provide a note about using Windows Subsystem for Linux (WSL) for Windows users who prefer Bash, to further support Linux parity.
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 →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation shows mild Windows bias by referencing Windows command shells and tools before or in preference to Linux equivalents. For example, it mentions using Windows cmd.exe instead of Bash, and provides explicit instructions for Windows environment variable setting (using 'set') before or alongside Linux ('export'). In the Java section, the initial directory creation uses 'cmd' syntax, and there is occasional mention of Windows-specific patterns. However, the majority of code and CLI examples are cross-platform, and Linux/Bash instructions are present throughout.
Recommendations
- When referencing command shells, present Bash/Linux instructions first, or equally with Windows, rather than as an alternative.
- Avoid using Windows-specific command syntax (e.g., 'cmd') as the primary example; provide both Bash and Windows equivalents side by side.
- Where environment variables are set, show both 'export' (Linux/macOS) and 'set' (Windows) examples together, or clarify which is for which OS.
- Ensure all tool installation and usage instructions are platform-agnostic or provide clear, parallel instructions for both Windows and Linux.
- Consider adding a table or section summarizing OS-specific differences for setup and commands, to make parity explicit.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and managing resources, but consistently lists PowerShell (a Windows-centric tool) alongside or immediately after CLI, and sometimes before mentioning cross-platform alternatives. There is no explicit Linux bias, but the presence and parity of PowerShell examples may suggest a slight Windows bias, especially since PowerShell is less commonly used on Linux. However, all core workflows are covered with Azure CLI, which is cross-platform.
Recommendations
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS to reinforce cross-platform support.
- When presenting both CLI and PowerShell, consider listing CLI first, as it is more universally available across platforms.
- Clarify that PowerShell examples are optional and primarily for users already familiar with it.
- Where possible, add notes or callouts for Linux/macOS users (e.g., file path differences, shell syntax) to ensure parity.
- Avoid implying that PowerShell is the default or preferred automation tool unless targeting a Windows-specific audience.
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
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation generally uses cross-platform tools (Azure CLI, Azure Functions Core Tools) and provides language-specific instructions in a tabbed format, which is good for parity. However, there is a subtle Windows bias in the storage emulator guidance: the only local storage emulator mentioned is the classic 'Storage Emulator', which is Windows-only. No mention is made of cross-platform alternatives like Azurite. Additionally, the note about browser compatibility specifically recommends Edge, a Microsoft browser, which may be perceived as a Windows-centric suggestion.
Recommendations
- Mention and provide instructions for using Azurite (the cross-platform Azure Storage emulator) alongside or instead of the classic Windows-only Storage Emulator.
- Clarify that all command-line instructions (Azure CLI, func) are cross-platform and work on Linux, macOS, and Windows.
- When referencing browser compatibility, avoid recommending a specific browser unless necessary, or provide a broader set of options (e.g., Chrome, Firefox, Edge, Safari) to avoid perceived bias.
- Explicitly state that all steps and tools are supported on Linux and macOS as well as Windows, especially in the prerequisites and troubleshooting sections.
Azure Web Pubsub
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-web-pubsub/tutorial-subprotocol.md
...main/articles/azure-web-pubsub/tutorial-subprotocol.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally provides cross-platform instructions, with shell commands and code examples for C#, JavaScript, Python, and Java. However, there is a subtle Windows bias in the way Windows-specific tools and command patterns are introduced before or alongside their Linux equivalents. For example, in several places, the Windows 'dir /s /b' command is mentioned as an alternative to the default 'ls -R' (Linux/macOS), and the .NET Secret Manager tool (which is Windows-centric) is referenced without a Linux-specific alternative. In most cases, Linux commands are primary, but Windows alternatives are always mentioned, sometimes immediately after the Linux example, which can signal a slight preference or assumption of Windows usage.
Recommendations
- When presenting command-line examples, consider grouping Windows and Linux/macOS commands separately, or use tabbed sections (as done for programming languages) to avoid mixing them and to give each platform equal prominence.
- For tools like .NET Secret Manager, clarify cross-platform usage or provide explicit instructions for Linux/macOS environments, including any prerequisites or differences.
- If referencing Windows commands (e.g., 'dir /s /b'), ensure that Linux/macOS equivalents are always given equal visibility and not just as the default with Windows as an afterthought.
- Consider adding a short section at the start of the tutorial that explicitly states the tutorial is cross-platform and that all major OSes are supported, with clear navigation to OS-specific instructions where needed.
- Review all included snippets and ensure that any platform-specific instructions are clearly labeled and not presented as the default or primary approach.
Azure Web Pubsub
Quickstart: Create an Azure Web PubSub service with a Bicep file
...articles/azure-web-pubsub/quickstart-bicep-template.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for all deployment steps, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is mentioned in the page description before Azure CLI. There are no Linux-specific instructions or notes, and PowerShell is not natively available on most Linux/macOS systems. The examples do not clarify platform compatibility, which may cause confusion for non-Windows users.
Recommendations
- Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
- List Azure CLI examples before PowerShell examples, or clarify platform applicability for each.
- Add a note that PowerShell examples are primarily for Windows users, and provide installation guidance for PowerShell Core if Linux/macOS users wish to use it.
- Consider omitting PowerShell examples from the main flow, or moving them to a dedicated section for Windows users.
- Add a brief section or callout for Linux/macOS users to ensure parity and clarity.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on using the Azure portal UI for role assignment, which is platform-agnostic, but in the 'Learn more' section, Azure PowerShell is listed before Azure CLI. There are no command-line examples provided, and no explicit mention of Linux/macOS workflows or tools. The ordering and lack of parity in examples may subtly favor Windows users.
Recommendations
- Provide explicit command-line examples for both Azure PowerShell (Windows/macOS/Linux) and Azure CLI (cross-platform), showing how to assign roles.
- List Azure CLI before or alongside Azure PowerShell in 'Learn more' sections, as CLI is more commonly used on Linux/macOS.
- Add a note clarifying that Azure CLI and PowerShell are available cross-platform, and link to installation guides for each OS.
- Include screenshots or instructions for non-Windows environments if UI differences exist.
Azure Web Pubsub
How to collect a network trace
...s/azure-web-pubsub/howto-troubleshoot-network-trace.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation shows mild Windows bias by listing Windows-centric tools (Fiddler) first and providing Windows keyboard shortcuts before Linux/macOS equivalents. However, Linux and macOS methods (tcpdump, browser DevTools) are included and described with parity.
Recommendations
- Present platform-specific tools in parallel or grouped by OS, rather than listing Windows tools first.
- For Fiddler, clarify installation and usage steps for Linux/macOS (e.g., mention Fiddler Everywhere and its differences).
- When listing keyboard shortcuts, consider listing macOS/Linux shortcuts first or together, not after Windows.
- Include alternative Linux tools (e.g., Wireshark, tshark) alongside tcpdump for completeness.
- Explicitly mention PowerShell or Windows command-line options only if Linux equivalents are also provided.
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
Low Priority
View Details →
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 the PowerShell example is given equal prominence and is shown immediately after Bash. There is a slight 'windows_first' bias in that PowerShell is explicitly called out, and the documentation does not mention Linux or macOS directly, nor does it provide troubleshooting or environment-specific notes for those platforms. However, most commands use Azure CLI and Bash, which are cross-platform.
Recommendations
- Explicitly mention Linux and macOS as supported environments in the prerequisites.
- Clarify that Bash commands work on Linux/macOS and Windows (via WSL or Git Bash), and PowerShell is for Windows users.
- Add troubleshooting notes for common Linux/macOS issues (e.g., zip utility installation).
- Provide parity in example order: show Bash first for cross-platform, then PowerShell for Windows.
- Add a note about using WSL or Git Bash on Windows for Bash commands.
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
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation occasionally references Windows-specific tools and patterns, such as mentioning Windows cmd.exe as an alternative to Bash and providing instructions for setting environment variables using 'set' for Windows users. However, Linux/macOS equivalents are also present, and most code and commands are cross-platform. The ordering sometimes puts Windows notes before Linux/macOS, but Linux instructions are not missing.
Recommendations
- Present cross-platform instructions together, or explicitly show both Windows and Linux/macOS commands side-by-side when environment setup differs.
- Avoid language like 'You can use Windows cmd.exe instead of Bash' at the top; instead, clarify that all commands are cross-platform and note differences inline where relevant.
- Where environment variable setting is mentioned, provide both 'export' (Linux/macOS) and 'set' (Windows) commands equally, not as an afterthought.
- Consider adding a table or section summarizing OS-specific differences for quick reference.
Azure Web Pubsub
How to collect a network trace
...s/azure-web-pubsub/howto-troubleshoot-network-trace.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page shows mild Windows bias by listing Windows-centric tools and patterns first (Fiddler, Microsoft Edge), and by providing Windows keyboard shortcuts before Linux/macOS equivalents. However, Linux and macOS options (tcpdump, browser DevTools) are included and described, and Fiddler is noted as cross-platform.
Recommendations
- Explicitly mention Linux/macOS alternatives in the Fiddler section, such as Wireshark or tshark, and provide brief usage instructions.
- In the browser DevTools sections, present keyboard shortcuts for all platforms together or in a table for parity.
- Consider listing tcpdump (Linux/macOS) before Fiddler (Windows-centric) or in parallel, to avoid Windows-first ordering.
- Add a PowerShell or Windows command-line example for network tracing (e.g., using netsh trace), and Linux equivalents (e.g., iptables logging), for parity.
- Ensure screenshots and instructions are balanced between platforms.
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
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for compressing files, but Bash is shown first and PowerShell is included as an alternative. No other Windows-specific tools or patterns are present, and the Azure CLI commands are cross-platform. The bias is minor, mainly in the order of examples and inclusion of PowerShell.
Recommendations
- Explicitly state that both Bash and PowerShell examples are provided for cross-platform compatibility.
- Consider grouping Bash and PowerShell examples together under a 'Linux/macOS' and 'Windows' heading for clarity.
- Ensure that any future platform-specific steps are equally represented for Linux/macOS and Windows.
- Add a note clarifying that Azure CLI works on all major platforms.