Service Bus Messaging
134
Total Pages
61
Linux-Friendly Pages
73
Pages with Bias
54.5%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
377 issues found
Showing 301-325 of 377 flagged pages
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-nodejs-how-to-use-queues.md
...-bus-messaging/service-bus-nodejs-how-to-use-queues.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates some Windows bias by referencing Windows-specific tools and patterns before or instead of cross-platform or Linux alternatives. For example, it instructs users to open a 'Command Prompt' and refers to 'Windows PowerShell' for deployment, without mentioning Linux shells or terminals. There are no explicit Linux-specific instructions or examples, and the language assumes a Windows environment in several places.
Recommendations
- Replace or supplement references to 'Command Prompt' with 'terminal' or 'shell', and clarify that the instructions work on Windows, Linux, and macOS.
- When mentioning deployment guides, include links or instructions for Linux and macOS environments alongside Windows PowerShell.
- Explicitly state that the Azure CLI and Node.js commands work cross-platform, and provide example commands or screenshots from Linux/macOS terminals where appropriate.
- Avoid using Windows-centric terminology (e.g., 'Command Prompt') as the default; use neutral, cross-platform language.
- If referencing editors, mention cross-platform options (e.g., Visual Studio Code, nano, vim) and not just those popular on Windows.
Create Pull Request
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-performance-improvements.md
...-bus-messaging/service-bus-performance-improvements.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows/.NET bias by exclusively providing .NET/C# code samples and referencing Windows-centric platforms (e.g., .NET Framework, Universal Windows Platform) without offering equivalent examples or guidance for Linux environments or other programming languages commonly used on Linux (such as Python, Java, or Node.js). There are no mentions of Linux-specific tools, patterns, or deployment considerations, and all operational guidance is framed around .NET SDKs, which are most prevalent on Windows.
Recommendations
- Add code samples for other supported languages/platforms, such as Python, Java, or Node.js, which are commonly used on Linux.
- Include explicit instructions or examples for running Service Bus clients on Linux, such as using .NET Core/Mono on Linux, or using other SDKs.
- Reference Linux-specific deployment and monitoring tools (e.g., systemd, cron, Linux performance metrics) where relevant.
- Clarify cross-platform compatibility in SDK tables, and provide parity in documentation for Linux users.
- Add troubleshooting and best practices sections for Linux environments, including common issues and solutions.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-quickstart-cli.md
...es/service-bus-messaging/service-bus-quickstart-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by mentioning Azure PowerShell as an alternative to Azure Cloud Shell before discussing installation or usage on Linux. The instructions for launching Cloud Shell reference switching from PowerShell to Bash, implying PowerShell (Windows) as the default. There are no explicit Linux-specific instructions or examples, and the mention of Azure PowerShell may lead Linux users to believe it is a primary or preferred tool, despite Bash being more cross-platform.
Recommendations
- Explicitly mention that Azure CLI and Bash are cross-platform and available on Linux, macOS, and Windows.
- Provide installation instructions or links for Azure CLI on Linux and macOS alongside Windows.
- Avoid implying PowerShell is the default or preferred shell; clarify that Bash is available and often recommended for cross-platform scenarios.
- Include a note or section highlighting usage from Linux/macOS terminals, not just Azure Cloud Shell.
- Balance references to PowerShell with equivalent Bash or native Linux command-line instructions.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-typescript-how-to-use-queues.md
...-messaging/service-bus-typescript-how-to-use-queues.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific tools and patterns, such as PowerShell and Windows-based deployment guides, and mentioning them before or instead of Linux equivalents. For example, instructions reference 'Node.js cloud service using Windows PowerShell' and suggest using 'command prompt' terminology, which is more familiar to Windows users. There is no explicit mention of Linux shells (e.g., Bash) or cross-platform terminal usage, and no Linux-specific deployment or troubleshooting examples are provided.
Recommendations
- Add explicit instructions and examples for Linux/macOS users, such as using Bash or Terminal instead of 'command prompt'.
- Reference Linux-based deployment guides alongside or before Windows PowerShell guides.
- Use cross-platform terminology (e.g., 'terminal' instead of 'command prompt') throughout the documentation.
- Include troubleshooting steps relevant to Linux environments (e.g., permissions, environment variables).
- Ensure that all referenced tools (such as Azure CLI) are shown to work on Linux/macOS as well as Windows.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-partitions-premium.md
...les/service-bus-messaging/enable-partitions-premium.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for enabling partitioning, but the PowerShell section is given equal prominence to the CLI, despite PowerShell being primarily a Windows-centric tool (even though it is now cross-platform, its usage is still most common on Windows). There are no Linux shell or Bash-specific examples, and the order of examples (CLI before PowerShell) is good, but the PowerShell section could be seen as Windows-focused. No explicit Windows-only tools or patterns are used, but the lack of Linux/Bash-specific guidance or troubleshooting tips may disadvantage Linux users.
Recommendations
- Clarify that Azure CLI commands are fully cross-platform and preferred for Linux/macOS users.
- Add Bash shell scripting examples or notes for Linux users, especially for automation scenarios.
- Mention that PowerShell is available cross-platform, but note its prevalence on Windows.
- Provide troubleshooting tips or common issues for both Windows and Linux environments.
- Consider adding a table comparing CLI and PowerShell usage scenarios for different OSes.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-amqp-dotnet.md
...icles/service-bus-messaging/service-bus-amqp-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is focused exclusively on the legacy WindowsAzure.ServiceBus .NET Framework library, which is inherently Windows-centric. There are no examples or mentions of Linux or cross-platform usage, and all configuration and usage patterns assume a Windows/.NET environment. No Linux-specific instructions, tools, or parity considerations are provided.
Recommendations
- Add explicit notes about cross-platform support or limitations, clarifying whether the library can be used on Linux via Mono or .NET Core/5+.
- Provide examples or guidance for using the newer Azure.Messaging.ServiceBus package in cross-platform (Linux, macOS) environments, especially since it is recommended for new development.
- Include instructions or references for setting up the development environment and running .NET-based Service Bus clients on Linux.
- Mention any differences or caveats when using the library on non-Windows platforms, if supported.
- If the legacy library is Windows-only, state this clearly and direct Linux users to supported alternatives.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-to-event-grid-integration-concept.md
...aging/service-bus-to-event-grid-integration-concept.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for creating Event Grid subscriptions, but lists PowerShell after Azure CLI. However, the PowerShell example is given equal prominence, and there are no explicit Linux-specific instructions or examples. The use of PowerShell (a Windows-centric tool, though now cross-platform) may still be seen as Windows-biased, especially since no Bash or Linux-native scripting examples are provided. There are no references to Windows-only tools, but the absence of explicit Linux/Bash examples or notes on cross-platform compatibility could be improved.
Recommendations
- Add explicit Bash/Linux shell examples for all command-line instructions, or clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
- Mention that PowerShell Core is cross-platform, or provide Bash equivalents for PowerShell examples.
- Where possible, avoid presenting PowerShell as the only scripting alternative to Azure CLI; consider including Python or REST API examples for broader platform parity.
- Add a note clarifying the cross-platform compatibility of the Azure CLI and PowerShell modules.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-messaging-sql-rule-action.md
...bus-messaging/service-bus-messaging-sql-rule-action.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page lists both Azure CLI and PowerShell commands for managing Service Bus rules, but the PowerShell cmdlet (New-AzServiceBusRule) is mentioned in the 'Next steps' section after the CLI, and there are no explicit OS-specific examples. However, the only SDKs linked are .NET, Java, and JavaScript, with .NET (a Microsoft/Windows-centric technology) listed first. There are no Linux-specific tools or shell examples, and the documentation references .NET types and methods (e.g., System.Char.IsLetter, System.Guid.NewGuid()), which may be more familiar to Windows/.NET developers.
Recommendations
- Add explicit Linux shell (bash) examples alongside Azure CLI commands, demonstrating parity with PowerShell.
- Include references to cross-platform SDKs (such as Python) and provide usage examples.
- When referencing types or methods, provide language-agnostic explanations or equivalents in other languages (e.g., Python, Java).
- Ensure that examples and tool references are balanced between Windows and Linux environments.
- Consider listing cross-platform tools and SDKs before Windows-specific ones to avoid perceived prioritization.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-geo-replication.md
...s/service-bus-messaging/service-bus-geo-replication.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation does not show overt Windows or PowerShell bias in terms of explicit command-line examples, but it does exhibit 'windows_first' and 'missing_linux_example' bias in a few subtle ways. For example, the only command-line example for checking the current primary region uses the 'ping' command, which is available on both Windows and Linux, but the documentation does not clarify this cross-platform applicability or provide Linux-specific context. Additionally, all screenshots and portal instructions are platform-agnostic, but the sample code references only .NET (commonly associated with Windows), and there are no explicit Linux or cross-platform SDK/sample references. There are no PowerShell-specific or Windows tool-specific instructions, but the lack of explicit Linux parity in examples and sample references is a form of bias.
Recommendations
- When providing command-line instructions (e.g., 'ping'), clarify that the command works on both Windows and Linux, or provide equivalent Linux shell commands if differences exist.
- Include sample references or code snippets in languages and SDKs commonly used on Linux (e.g., Python, Java, Node.js), not just .NET.
- If referencing the Azure CLI, note that it is cross-platform and provide any necessary shell syntax for both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh).
- Add explicit statements or sections confirming that all features and management tasks are supported equally on Linux and Windows, especially for automation and scripting.
- Where screenshots are used, consider including at least one from a Linux environment or clarify that the portal experience is identical across platforms.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-queue-bicep.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-queue-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment, validation, and cleanup, but consistently lists PowerShell as the second option and highlights PowerShell-specific management resources in the 'Next steps' section. There is a slight Windows bias in the prominence of PowerShell, and the 'Manage Service Bus with PowerShell' article is specifically called out, while equivalent Linux/bash management resources are not.
Recommendations
- Ensure parity by including links to Linux/bash management guides in the 'Next steps' section, such as 'Manage Service Bus with Azure CLI' or scripting with bash.
- When listing tools or examples, alternate the order (e.g., sometimes show CLI first, sometimes PowerShell) or clarify that both are cross-platform, with CLI being natively available on Linux/macOS.
- Add explicit notes that Azure CLI commands work on Windows, Linux, and macOS, and consider including bash script examples where appropriate.
- If mentioning PowerShell, also mention that PowerShell Core is cross-platform, or provide bash alternatives for scripting scenarios.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-typescript-how-to-use-queues.md
...-messaging/service-bus-typescript-how-to-use-queues.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is mostly cross-platform in its instructions and code samples, but there is a subtle Windows bias in the references to development tools and supporting documentation. Specifically, the only explicit mention of a platform-specific tool is 'Windows PowerShell' in the context of deploying a Node.js app, and the phrase 'command prompt' is used throughout, which is more commonly associated with Windows than with Linux or macOS. There are no Linux- or macOS-specific instructions or examples, and the documentation does not clarify that all steps work equally well on non-Windows systems.
Recommendations
- Replace or supplement references to 'command prompt' with 'terminal' or 'shell', and clarify that the instructions apply to Windows, Linux, and macOS.
- When referencing supporting documentation (such as deploying Node.js apps), include links or notes for Linux/macOS equivalents alongside Windows/PowerShell instructions.
- Explicitly state that all commands and code samples are cross-platform, or provide platform-specific notes where minor differences exist.
- Mention popular Linux/macOS editors (such as Vim, nano, or Sublime Text) alongside Visual Studio Code, or simply refer to 'your preferred code editor'.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/includes/get-namespace-connection-string.md
...-messaging/includes/get-namespace-connection-string.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation suggests pasting the copied connection string into Notepad, a Windows-specific tool, and does not mention Linux or cross-platform alternatives. There are no examples or instructions tailored for Linux users.
Recommendations
- Replace 'Notepad' with a cross-platform term such as 'a text editor' or mention alternatives like 'Notepad (Windows), TextEdit (macOS), or gedit (Linux)'.
- Include a note or example for Linux/macOS users, e.g., 'Paste this value into a text editor such as gedit, nano, or TextEdit.'
- Review the documentation for other Windows-centric language or screenshots and provide Linux/macOS equivalents where appropriate.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/build-message-driven-apps-nservicebus.md
...bus-messaging/build-message-driven-apps-nservicebus.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by referencing Visual Studio and Solution Explorer as the primary tools for running and configuring the solution, with only a brief mention of Visual Studio Code. There are no Linux-specific instructions or examples for running the solution, managing projects, or configuring the environment. All tooling and workflow examples assume a Windows development environment, and there is no mention of Linux equivalents for tasks such as multi-project startup or debugging.
Recommendations
- Provide explicit instructions for running and debugging the solution on Linux, including using .NET CLI commands (e.g., 'dotnet run') for both Sender and Receiver projects.
- Include examples for configuring multi-project startup in cross-platform editors like Visual Studio Code (e.g., using launch.json and tasks.json).
- Mention and link to cross-platform tools and workflows, such as JetBrains Rider or the .NET CLI, alongside Visual Studio.
- Clarify that the solution can be developed and run on Linux and macOS, not just Windows, and provide any necessary steps or caveats.
- If referencing ServiceInsight or ServicePulse, note their platform compatibility or suggest alternatives if they are Windows-only.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-partitions-premium.md
...les/service-bus-messaging/enable-partitions-premium.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for enabling partitioning, but the PowerShell section is given equal prominence to the CLI, and there is no explicit mention of Linux or Bash scripting. The PowerShell example is not marked as Windows-specific, and there is no clarification that PowerShell is primarily a Windows tool (though it is now cross-platform, many users still associate it with Windows). No Linux-specific tools or shell examples (e.g., Bash, shell scripts) are provided, and the order of sections (CLI before PowerShell) is good, but the PowerShell example could be perceived as Windows-centric.
Recommendations
- Explicitly note that Azure CLI commands work cross-platform (Windows, Linux, macOS) and are the recommended approach for Linux users.
- Label the PowerShell example as optional or as 'for Windows/PowerShell users', and clarify that PowerShell Core is available cross-platform if relevant.
- Consider adding a Bash shell script example or a note for Linux users to reinforce parity.
- Where possible, provide links to platform-specific setup guides (e.g., installing Azure CLI on Linux).
- Review the language to ensure that Windows tools are not implied as the default or primary method.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/message-transfers-locks-settlement.md
...ce-bus-messaging/message-transfers-locks-settlement.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page provides only C# code examples and references .NET-specific APIs, which are most commonly associated with Windows development. There are no Linux-specific or cross-platform command-line examples, nor are there any references to Linux tools or patterns. While the text mentions support for Java, JavaScript, Python, and Go, all code samples and API references are for .NET/C#, and there is no parity in examples for other platforms or languages. This creates a subtle Windows bias by centering the documentation around Windows-centric technologies and omitting Linux/Unix or cross-platform usage patterns.
Recommendations
- Provide equivalent code samples in at least one other major language (e.g., Python, Java, or JavaScript) that is commonly used on Linux.
- Include cross-platform command-line examples (e.g., using Azure CLI or REST API) where appropriate.
- Reference SDKs and APIs for multiple languages/platforms, not just .NET/C#.
- Explicitly mention and, where possible, demonstrate usage on Linux or macOS environments.
- Consider adding a section or callout for Linux users, highlighting any differences or best practices.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/move-across-regions.md
.../articles/service-bus-messaging/move-across-regions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash). However, the workflow and screenshots are heavily oriented toward the graphical interface, which is more familiar to Windows users. There is no mention of Linux command-line tools or automation approaches, and no parity for users who prefer or require CLI-based workflows, which are common in Linux environments.
Recommendations
- Add Azure CLI examples for exporting, editing, and deploying Resource Manager templates, as Azure CLI is cross-platform and widely used on Linux.
- Include instructions for performing the move using command-line tools (e.g., az group export, az deployment group create) alongside the portal-based steps.
- Mention and provide links to documentation for automating these tasks via scripts (Bash, PowerShell) to support both Windows and Linux users.
- Ensure that screenshots and instructions do not assume a Windows environment (e.g., file paths, UI conventions) and clarify that the process is platform-agnostic where possible.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-go-how-to-use-queues.md
...vice-bus-messaging/service-bus-go-how-to-use-queues.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell instructions for setting environment variables, but Bash is presented first. There is a minor Windows bias in the mention of Visual Studio/MSDN subscriber benefits for Azure subscriptions, which are Windows-centric. However, the overall documentation is largely cross-platform, with the Go code and Azure CLI usage being platform-agnostic. No exclusive use of Windows tools or missing Linux examples were found.
Recommendations
- Continue to provide both Bash and PowerShell instructions for environment variables, but consider explicitly stating that Bash commands work on Linux/macOS and PowerShell on Windows.
- When mentioning Azure subscription options, add links or notes for non-Windows users (e.g., 'You can also sign up for a free account if you are not a Visual Studio/MSDN subscriber').
- Ensure that any references to tools or workflows (such as Azure CLI) clarify their cross-platform availability.
- If referencing file paths or shell commands elsewhere, provide both Windows and Linux/macOS equivalents where relevant.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-federation-overview.md
...rvice-bus-messaging/service-bus-federation-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a command-line example using the Azure CLI, which is cross-platform, but does not include any OS-specific shell context or examples. However, there is a subtle 'windows_first' bias in that no explicit Linux or Bash shell context is shown, and the only CLI example is presented without clarifying its cross-platform applicability. There are no PowerShell-specific commands, but the absence of Linux- or macOS-specific notes or examples (such as Bash scripting, environment variable usage, or file path conventions) may leave Linux users uncertain about parity. No Windows-only tools are mentioned, but the documentation does not actively demonstrate Linux parity.
Recommendations
- Explicitly state that the Azure CLI example works on Windows, Linux, and macOS, and provide sample invocations in both Bash and PowerShell if relevant.
- Where command-line examples are given, show both Bash and PowerShell syntax if there are differences, or clarify that the syntax is identical.
- Add notes or callouts for Linux/macOS users regarding any environment-specific considerations (e.g., line continuations, authentication methods, file paths).
- If referencing tools or scripts, ensure both Windows and Linux equivalents are mentioned or provide guidance for both environments.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-auth-rule.md
...ng/service-bus-resource-manager-namespace-auth-rule.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides both PowerShell and Azure CLI commands for deploying the template, but the PowerShell example is presented first and is visually emphasized. Additionally, the 'Next steps' section highlights PowerShell-based management before other cross-platform tools, and there is no explicit mention of Linux-specific considerations or parity in tooling. The Azure CLI example uses the legacy 'azure' CLI rather than the modern 'az' CLI, which is more cross-platform and recommended.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Update the Azure CLI example to use the modern 'az' CLI instead of the deprecated 'azure' CLI.
- Include explicit statements that all commands work on Linux, macOS, and Windows, and provide any necessary Linux-specific notes (e.g., shell syntax differences, installation instructions).
- In the 'Next steps' section, add links to Azure CLI and/or REST API management guides before or alongside PowerShell resources.
- Consider including a Bash shell example for template deployment to further demonstrate Linux parity.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-managed-service-identity.md
...-bus-messaging/service-bus-managed-service-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by referencing Windows-specific resources before Linux equivalents and omitting explicit Linux or cross-platform examples. For example, the link for configuring managed identities on a VM points only to a Windows VM guide, and there are no Linux-specific or cross-platform instructions for enabling managed identities. Additionally, the code samples and tool references (such as Azure CLI) are platform-neutral, but the absence of Linux-focused guidance or parity in example coverage is notable.
Recommendations
- Include links or references to both Windows and Linux VM managed identity configuration guides, or use a cross-platform guide where available.
- When listing platform-specific instructions, present Linux and Windows options together or in parallel, rather than defaulting to Windows.
- Add explicit Linux (or cross-platform) examples for enabling managed identity and for any command-line steps.
- Ensure that all code and CLI examples are clearly marked as cross-platform, and provide any necessary notes for Linux users (e.g., shell syntax differences, environment variable usage).
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-nodejs-how-to-use-queues.md
...-bus-messaging/service-bus-nodejs-how-to-use-queues.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by referencing Windows tools (such as Command Prompt and Windows PowerShell) and presenting Windows-centric patterns (e.g., 'open a Command Prompt window', 'Node.js cloud service using Windows PowerShell') without equivalent or parallel Linux/macOS instructions. There are no explicit Linux or macOS terminal references, and the guidance for running commands and setting up the environment implicitly assumes a Windows environment.
Recommendations
- Provide explicit instructions for Linux and macOS users alongside Windows instructions, such as referencing 'Terminal' or 'shell' in addition to 'Command Prompt'.
- When mentioning Windows PowerShell or Command Prompt, also mention Bash or Terminal for Linux/macOS users.
- Include links or references to Linux/macOS-specific guides for creating and deploying Node.js applications, not just Windows PowerShell.
- Use neutral language such as 'open a terminal window' instead of 'open a Command Prompt window' where possible.
- Ensure that all command-line examples are cross-platform or provide platform-specific notes if differences exist.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-nodejs-how-to-use-topics-subscriptions.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-nodejs-how-to-use-topics-subscriptions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally uses cross-platform language (e.g., 'command prompt', 'terminal'), but there are subtle Windows biases. Notably, in the 'NOTE' section, Windows PowerShell is mentioned as a deployment method for Node.js apps, and the phrase 'command prompt' is used throughout, which is more closely associated with Windows. There are no explicit Linux or macOS-specific instructions or examples, and no mention of Linux tools or terminals. The only editor recommended is Visual Studio Code, which is cross-platform, but no Linux-native editors are mentioned.
Recommendations
- Replace or supplement 'command prompt' with 'terminal' or 'shell', and clarify that instructions apply to Windows, Linux, and macOS.
- When referencing deployment guides, include links to Linux/macOS deployment instructions (e.g., deploying Node.js apps using Bash or other Linux-native tools) alongside or before Windows PowerShell.
- Explicitly state that all commands (npm, node) work on Linux/macOS terminals as well as Windows.
- Consider mentioning popular Linux editors (e.g., Vim, Nano, Gedit) in addition to Visual Studio Code.
- Where possible, provide screenshots or notes that reflect Linux/macOS environments, not just Windows/Azure Portal.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-java-how-to-use-topics-subscriptions.md
...ng/service-bus-java-how-to-use-topics-subscriptions.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation demonstrates a mild Windows bias by referencing Windows-specific tools (such as Eclipse and IntelliJ, which are cross-platform but often associated with Windows), and by providing instructions for installing the Azure CLI with a direct link to the Windows installation page. Additionally, the workflow for creating a runnable JAR file is described using Eclipse's Windows-oriented UI conventions (e.g., right-click, Export, Runnable JAR file), and there is no mention of Linux-specific instructions, terminal commands, or alternative editors/environments. The documentation does not provide explicit Linux or macOS command-line examples for running the Java application or installing prerequisites, nor does it mention platform-specific considerations for non-Windows users.
Recommendations
- Include explicit instructions for Linux and macOS users, such as how to install the Azure CLI on those platforms (with appropriate links).
- Provide terminal/command-line examples for compiling and running the Java application (e.g., using javac and java commands), in addition to or instead of IDE-based instructions.
- Mention that Eclipse and IntelliJ are cross-platform, and provide guidance for users on Linux/macOS, including any differences in UI or workflow.
- Where file paths or commands are shown, use platform-agnostic syntax or provide both Windows and Linux/macOS variants.
- Add a note or section addressing any platform-specific dependencies or troubleshooting steps for Linux/macOS users.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-python-how-to-use-queues.md
...-bus-messaging/service-bus-python-how-to-use-queues.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently refers to 'Command Prompt' and instructs users to 'open a Command Prompt window' or 'open a command prompt that has Python in its path' when installing packages or running code. There are no explicit instructions or examples for Linux or macOS users (e.g., using 'terminal', 'bash', or 'shell'). The only shell command shown uses a semicolon (;) to chain commands, which is Unix-style, but the surrounding text is Windows-centric. No PowerShell-specific commands or Windows-only tools are mentioned, but the language and setup steps assume a Windows environment.
Recommendations
- Replace 'Command Prompt' with 'terminal' or 'command prompt/terminal' to be inclusive of Linux/macOS users.
- Add explicit instructions for Linux/macOS users, such as 'Open a terminal window' and clarify that the commands work on all platforms.
- Where appropriate, show both Windows (cmd.exe) and Unix (bash/zsh) command examples, especially for chained commands or environment variable setup.
- Mention that Visual Studio Code is cross-platform, or suggest other editors available on Linux/macOS.
- Ensure that all prerequisite and setup steps are platform-agnostic or provide platform-specific notes as needed.
Service Bus Messaging
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-queue.md
...saging/service-bus-resource-manager-namespace-queue.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by listing PowerShell as the only command-line management option in the 'Next steps' section, and by referencing PowerShell before mentioning the Azure CLI (which is cross-platform) in the reference links. No Linux-specific tools or examples are provided, and the workflow is centered around the Azure Portal UI, which is platform-agnostic but often associated with Windows environments.
Recommendations
- Include explicit Azure CLI examples for deploying and managing Service Bus resources, as the CLI is cross-platform and widely used on Linux.
- In the 'Next steps' section, add a link to a guide on managing Service Bus with the Azure CLI, and list it before or alongside PowerShell to avoid Windows-first ordering.
- If mentioning Service Bus Explorer or other tools, clarify their cross-platform availability or suggest alternatives for Linux users if any exist.
- Consider adding a section or callout that highlights cross-platform command-line options, ensuring Linux users see parity in management workflows.