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 276-300 of 377 flagged pages
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/message-counters.md ...ain/articles/service-bus-messaging/message-counters.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for retrieving message counts, but the PowerShell section is given equal prominence to the CLI, despite PowerShell being primarily a Windows tool. There are no Linux-specific shell examples (e.g., Bash, curl, REST API via shell), and PowerShell is presented without noting its limited cross-platform adoption compared to CLI. The CLI examples are generic and cross-platform, but the presence of PowerShell examples may signal a Windows-centric bias.
Recommendations
  • Add explicit Bash or shell examples using REST API calls for Linux users.
  • Clarify that Azure CLI is cross-platform and preferred for scripting on Linux/macOS.
  • If PowerShell is included, note its cross-platform availability but also its historical Windows focus.
  • Consider reordering sections to present CLI (cross-platform) before PowerShell.
  • Add a brief note or table comparing tool availability and suitability for different OS platforms.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Azure PowerShell as a primary method for enabling partitioning, with a dedicated section and example. PowerShell is a Windows-centric tool, and its inclusion before any Linux-specific alternatives (such as Bash scripting or cross-platform shell examples) indicates a Windows-first bias. The Azure CLI example is present and cross-platform, but no explicit Linux shell or OS-specific instructions are given. There is no mention of Linux-specific tools or patterns, nor are there examples tailored for Linux users.
Recommendations
  • Add explicit instructions or examples for Linux users, such as Bash shell commands or notes on running Azure CLI on Linux.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Consider including screenshots or terminal examples from Linux environments alongside Windows/PowerShell examples.
  • If PowerShell is mentioned, note that PowerShell Core is available cross-platform, or provide equivalent Bash/Unix shell commands where possible.
  • Review the order of sections to avoid implying Windows-first usage patterns; consider listing CLI before PowerShell.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/jms-developer-guide.md .../articles/service-bus-messaging/jms-developer-guide.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by linking to Windows-specific instructions for configuring managed identities (e.g., 'qs-configure-portal-windows-vm.md') and omitting equivalent Linux VM setup guidance. No PowerShell or Windows tool examples are present, but the only explicit platform reference is Windows, and Linux alternatives are not mentioned or linked.
Recommendations
  • Add links to Linux VM managed identity configuration guides alongside Windows VM instructions.
  • Explicitly mention that the authentication and connection procedures apply equally to Java applications running on Linux, macOS, and Windows.
  • Where platform-specific setup is referenced, provide parity by including both Windows and Linux instructions or links.
  • Review all referenced articles for similar platform bias and ensure Linux examples/tools are included where relevant.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides code examples exclusively in C#, which is most commonly associated with Windows development environments. There are no Linux-specific examples, shell commands, or references to Linux tools or patterns. The asynchronous programming and semaphore examples use C# constructs, with no parity shown for equivalent patterns in Python, JavaScript, or other cross-platform languages. The documentation also references .NET Framework clients before mentioning other platforms, which may reinforce a Windows-centric perspective.
Recommendations
  • Add equivalent code examples in Linux-friendly languages such as Python, JavaScript, or Java, especially for asynchronous sending and semaphore/throttling patterns.
  • Include references to cross-platform tools and environments, such as Azure CLI or Bash shell, where relevant.
  • When discussing client libraries, present all supported platforms equally, rather than mentioning Windows/.NET Framework first.
  • Clarify that the concepts and APIs apply equally across Windows and Linux environments, and provide guidance for Linux users where there may be platform-specific considerations.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page references Windows-specific tools such as PowerShell (New-AzServiceBusRule) and .NET APIs before mentioning Linux-friendly alternatives. While the Azure CLI is mentioned (which is cross-platform), the inclusion and ordering of PowerShell and .NET examples suggest a Windows-first bias. There are no explicit Linux shell or scripting examples, and the SDK references begin with .NET, which is traditionally associated with Windows environments.
Recommendations
  • Add explicit Linux shell (bash) examples for managing Service Bus rules, such as using Azure CLI in a Linux terminal.
  • Reorder SDK references to start with a cross-platform language (e.g., JavaScript or Python) before .NET.
  • Include notes clarifying that Azure CLI works on Linux, macOS, and Windows, and provide example commands in a Linux context.
  • If mentioning PowerShell, also mention bash or other Linux-native tools where possible.
  • Ensure that examples and tool references are balanced between Windows and Linux environments.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation shows mild Windows bias by referencing 'Command Prompt' and 'Windows PowerShell' as the default environments for running commands and deploying Node.js applications. There is no explicit mention of Linux or macOS equivalents, nor are cross-platform terminal instructions provided. The phrase 'open a Command Prompt window' is used throughout, and a key link for deploying Node.js apps points to a Windows PowerShell-based workflow. However, the actual code and commands (npm, node, az CLI) are cross-platform, and there are no PowerShell-specific scripts or commands.
Recommendations
  • Replace 'Command Prompt' with 'terminal' or 'command-line interface (CLI)' to be inclusive of Linux and macOS users.
  • When referencing editors or environments, mention alternatives (e.g., 'Open a terminal window (Command Prompt, Terminal, or shell)').
  • Provide links or instructions for deploying Node.js applications on Linux and macOS, not just Windows PowerShell.
  • If showing screenshots or walkthroughs, include cross-platform examples or clarify that steps are the same across operating systems.
  • Explicitly state that all commands (npm, node, az CLI) work on Windows, Linux, and macOS.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-messaging-sql-filter.md ...vice-bus-messaging/service-bus-messaging-sql-filter.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page shows mild Windows bias by referencing .NET types (e.g., System.Char, System.Guid), C# operator semantics, and listing the PowerShell cmdlet (New-AzServiceBusRule) in the 'Next steps' section. Windows/.NET concepts are mentioned before or exclusively, while Linux or cross-platform equivalents (such as Bash scripting or Python SDK usage) are not highlighted. There are no explicit Linux CLI or SDK examples, and the only command-line tool mentioned is Azure CLI, which is cross-platform, but PowerShell is listed as a next step, reinforcing a Windows-centric perspective.
Recommendations
  • Include examples and references to Linux-friendly tools and SDKs, such as Python or Bash scripting.
  • When mentioning system types or operator semantics, clarify their cross-platform equivalents (e.g., Python types, Java types) or provide neutral language.
  • Add explicit Linux usage examples, such as using Azure CLI in Bash or referencing Linux shell scripting.
  • Balance 'Next steps' by listing cross-platform SDKs and tools before or alongside Windows/PowerShell options.
  • Avoid using .NET-specific terminology (e.g., System.Char, System.Guid) without also providing equivalent concepts in other languages.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation exhibits mild Windows bias by referencing Windows-specific tools and deployment patterns, such as 'Node.js Cloud Service using Windows PowerShell', and by suggesting Windows-centric workflows (e.g., 'command prompt') and editors (Visual Studio Code, which is cross-platform but often associated with Windows). Windows tools are mentioned before any Linux equivalents, and there is no explicit mention of Linux-specific instructions or terminal usage, nor are Linux shell examples provided. However, most code and commands (npm, node, az CLI) are cross-platform.
Recommendations
  • Add explicit instructions and examples for Linux and macOS environments, such as using 'terminal' or 'shell' instead of only 'command prompt'.
  • Replace or supplement references to 'Windows PowerShell' with cross-platform alternatives (e.g., Bash, zsh, or generic shell).
  • Clarify that all commands (npm, node, az CLI) work on Linux/macOS as well as Windows.
  • Provide links to Linux/macOS-specific guides for Node.js application deployment and Azure CLI installation.
  • Ensure parity in troubleshooting and resource cleanup steps by mentioning Linux/macOS navigation and command-line usage.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by mentioning Azure PowerShell as an alternative to Cloud Shell before referencing installation instructions, and by referencing PowerShell mode in Cloud Shell before Bash. However, all command examples use Azure CLI, which is cross-platform, and the instructions recommend switching to Bash mode, which is more Linux-friendly. No Linux-specific tools or patterns are mentioned, and Linux parity is generally good, but the initial framing and tool references favor Windows users.
Recommendations
  • Mention Bash and cross-platform CLI usage before referencing PowerShell in the prerequisites.
  • Provide explicit instructions or links for installing Azure CLI on Linux/macOS, not just a generic install link.
  • Include a brief note that Azure CLI commands work identically on Windows, Linux, and macOS.
  • Consider adding a section or sidebar with Linux/macOS-specific tips for users unfamiliar with Azure Cloud Shell.
  • Avoid mentioning PowerShell unless providing equivalent Bash/Linux instructions or examples.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, validation, and cleanup, but PowerShell is featured equally alongside CLI rather than being secondary. In the 'Next steps' section, PowerShell management is highlighted before other tools, and there is no mention of Linux-specific patterns or shell scripting alternatives. The documentation does not show explicit Windows-only tools, but the order and emphasis suggest a slight Windows/PowerShell bias.
Recommendations
  • Ensure Azure CLI examples are presented first, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Include references to Bash scripting or Linux shell usage where appropriate, especially in the 'Next steps' section.
  • Add links or examples for managing Service Bus resources using CLI or SDKs on Linux/macOS.
  • Balance the order of PowerShell and CLI examples throughout the documentation to avoid implicit prioritization of Windows tools.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-topic.md ...saging/service-bus-resource-manager-namespace-topic.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both PowerShell and Azure CLI commands for deploying the template, but PowerShell is listed first and referenced in the 'Next steps' section for resource management. The CLI example is present and not Windows-specific, but PowerShell is given prominence, which may signal a subtle Windows bias. There are no Linux-specific tools or patterns mentioned, and Service Bus Explorer (a Windows desktop app) is referenced for management, with no mention of Linux alternatives.
Recommendations
  • List Azure CLI commands before PowerShell to avoid implying Windows-first workflows.
  • Expand 'Next steps' to include resource management using Azure CLI, not just PowerShell.
  • Mention cross-platform management tools (e.g., Azure Portal, Azure CLI, REST API) alongside Service Bus Explorer.
  • Explicitly note that Azure CLI works on Linux, macOS, and Windows, and provide links to relevant CLI management documentation.
  • If possible, suggest open-source or cross-platform alternatives to Service Bus Explorer for Linux users.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for creating Event Grid subscriptions, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is listed immediately after the CLI example. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or workflows. The use of PowerShell may implicitly favor Windows users, as PowerShell is native to Windows and only more recently available on Linux. The Azure portal instructions are platform-neutral, but the command-line guidance leans toward Windows environments.
Recommendations
  • Add explicit bash examples alongside Azure CLI commands to demonstrate usage in Linux environments.
  • Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any necessary shell syntax for Linux users (e.g., export instead of set for environment variables).
  • If PowerShell is included, note its cross-platform availability, but avoid implying it is the default or preferred method.
  • Consider listing Azure CLI (cross-platform) examples before PowerShell (Windows-centric) ones to reduce perceived Windows-first bias.
  • Include troubleshooting or notes for Linux users where command syntax or environment setup may differ.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
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 by mentioning Windows tooling before Linux equivalents. For example, it links to 'Node.js cloud service using Windows PowerShell' and references 'command prompt' and Visual Studio Code as the default editor, without mentioning Linux shells or editors. There are no explicit Linux or cross-platform examples for project setup, deployment, or command-line usage, and Linux-specific instructions are missing.
Recommendations
  • Include explicit instructions and examples for Linux and macOS environments, such as using Bash or zsh instead of only 'command prompt'.
  • Reference Linux and macOS deployment guides alongside Windows PowerShell guides.
  • Mention cross-platform editors (e.g., Vim, nano, Sublime Text) in addition to Visual Studio Code.
  • Clarify that all npm and Azure CLI commands work on Linux/macOS terminals as well as Windows.
  • Provide troubleshooting steps relevant to Linux/macOS users (e.g., permissions, environment variables).
  • Avoid Windows-centric terminology (e.g., 'command prompt') and use neutral terms like 'terminal' or 'shell'.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-topic.md ...saging/service-bus-resource-manager-namespace-topic.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both PowerShell and Azure CLI examples for deploying the template, but PowerShell is listed first and referenced in the 'Next steps' section for management tasks. The CLI example is present and cross-platform, but there is a subtle preference for PowerShell and Windows-centric tools in ordering and follow-up guidance.
Recommendations
  • List Azure CLI examples before PowerShell to emphasize cross-platform support.
  • Include explicit notes that Azure CLI works on Linux, macOS, and Windows.
  • Provide management examples using Azure CLI in the 'Next steps' section alongside PowerShell.
  • Reference Linux-native tools or workflows where relevant (e.g., bash scripting, automation).
  • Ensure links to CLI documentation are as prominent as PowerShell links.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-tutorial-topics-subscriptions-cli.md ...aging/service-bus-tutorial-topics-subscriptions-cli.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page shows mild Windows bias by mentioning Azure PowerShell as an alternative to Azure CLI in the prerequisites, and by instructing users to switch from PowerShell to Bash in the Azure Cloud Shell. Windows/PowerShell is referenced before Linux/Bash, and no Linux-specific instructions or examples are provided. However, all command examples use Azure CLI, which is cross-platform.
Recommendations
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide installation links for all platforms.
  • Add a brief section or note for Linux/macOS users, confirming that all CLI commands work natively in their environments.
  • Avoid listing PowerShell before Bash or Windows before Linux when describing options; present them equally or in alphabetical order.
  • Consider including a table or sidebar comparing Bash and PowerShell usage for Azure CLI, highlighting cross-platform parity.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-typescript-how-to-use-topics-subscriptions.md ...service-bus-typescript-how-to-use-topics-subscriptions.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias by referencing Windows-specific tools and deployment patterns, such as mentioning 'Node.js Cloud Service using Windows PowerShell' and linking to Windows PowerShell-based deployment instructions before any Linux equivalents. There are no explicit Linux-specific examples or instructions, and Windows tooling is mentioned in a way that could suggest it is the default or preferred environment.
Recommendations
  • Add explicit Linux and macOS instructions for creating and deploying Node.js applications, including links to relevant documentation.
  • When referencing deployment guides, provide both Windows and Linux/macOS options side-by-side, or mention cross-platform alternatives first.
  • Avoid mentioning Windows-specific tools (e.g., PowerShell) without also mentioning Linux/macOS equivalents (e.g., Bash, Terminal).
  • Clarify that all command-line instructions (npm, az CLI) work on Windows, Linux, and macOS, and provide examples or screenshots from multiple platforms where relevant.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/duplicate-detection.md .../articles/service-bus-messaging/duplicate-detection.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions enabling duplicate detection using Azure portal, PowerShell, CLI, Resource Manager template, .NET, Java, Python, and JavaScript. PowerShell (a Windows-centric tool) is listed before CLI (which is cross-platform), and there are no explicit Linux-specific examples or references to Linux tools. The ordering and mention of PowerShell before CLI suggest a subtle Windows-first bias. No explicit Linux examples or Linux command-line tools are provided.
Recommendations
  • List CLI before PowerShell when mentioning command-line options, as Azure CLI is cross-platform and widely used on Linux.
  • Provide explicit Linux examples or references, such as bash scripts or Linux command-line usage.
  • Include instructions or links for enabling duplicate detection using Linux-native tools or environments.
  • Clarify that Azure CLI works on Linux, macOS, and Windows, and provide parity in examples for all platforms.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-partitions-basic-standard.md ...vice-bus-messaging/enable-partitions-basic-standard.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for enabling partitioning in Azure Service Bus. However, the PowerShell section is given equal prominence to the CLI section, despite PowerShell being primarily a Windows tool (though it is available cross-platform now). There is no explicit mention of Linux-specific tools or shell environments, and no Bash or shell script examples are provided. The ordering of examples (CLI before PowerShell) is neutral, but the presence of PowerShell examples may indicate a mild Windows bias, especially since PowerShell is still more commonly used on Windows. No Linux-specific instructions, troubleshooting, or environment notes are present.
Recommendations
  • Add explicit Bash or shell script examples for Linux users, especially for scripting with Azure CLI.
  • Include notes or links about running Azure CLI on Linux and macOS, and clarify cross-platform compatibility.
  • If PowerShell examples are included, clarify that PowerShell Core is available on Linux and macOS, and provide installation instructions or links.
  • Consider adding troubleshooting tips or environment setup instructions for Linux users.
  • Ensure that examples and instructions do not assume a Windows environment (e.g., avoid backticks for line continuation, which are PowerShell-specific).
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure portal, Azure CLI, Azure PowerShell, and ARM templates. The PowerShell example is given equal prominence to the Azure CLI example, and is listed before ARM templates and programming language samples. PowerShell is a Windows-centric tool, and its inclusion as a primary method may suggest a Windows bias, especially since no Bash or Linux shell examples are provided. The CLI example is cross-platform, but there is no explicit mention of Linux-specific workflows or tools. The documentation does not provide Linux shell (bash) or script examples, nor does it mention Linux-specific considerations.
Recommendations
  • Add explicit Bash or Linux shell examples alongside Azure CLI usage to demonstrate Linux parity.
  • Clarify that Azure CLI commands work on both Windows and Linux, and provide sample commands for both environments if there are differences.
  • Consider listing cross-platform tools (Azure CLI, ARM templates) before Windows-centric tools (PowerShell) to avoid Windows-first impression.
  • Mention Linux-specific considerations or workflows where relevant, such as installation or authentication differences.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides code examples exclusively in C#, a language most commonly associated with Windows development. There are no examples or mentions of Linux-specific tools, shell commands, or cross-platform patterns. The asynchronous programming model is described using C# constructs (Tasks, SemaphoreSlim), with no equivalent examples for Linux-preferred languages (e.g., Python, JavaScript) or shell scripting. The documentation references .NET Framework (Windows-centric) before mentioning .NET Standard, and does not provide parity for Linux or open-source developer workflows.
Recommendations
  • Add code examples in Linux-preferred languages such as Python and JavaScript, demonstrating equivalent asynchronous patterns for sending and settling messages.
  • Include references to cross-platform tools and environments, such as Azure CLI or Bash scripting, where relevant.
  • When discussing protocols and APIs, mention Linux and open-source development environments explicitly, and provide guidance for those platforms.
  • Reorder references so that cross-platform or Linux-friendly options (e.g., .NET Standard, Java, Python) are mentioned before or alongside Windows/.NET Framework options.
  • Clarify that the concepts and APIs apply equally to Linux and macOS environments, not just Windows.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/message-counters.md ...ain/articles/service-bus-messaging/message-counters.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples using Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the PowerShell section is prominent and detailed, and there is no mention of Linux-specific tools or patterns (e.g., Bash scripting, Linux shell integration). The PowerShell examples may imply a Windows-centric workflow, and there are no explicit Linux or macOS command-line examples beyond the CLI. The order of sections (CLI before PowerShell) is good, but the PowerShell coverage is more verbose and assumes familiarity with Windows tooling.
Recommendations
  • Add explicit Bash or shell script examples for Linux users, demonstrating how to parse and use Azure CLI output.
  • Mention that Azure CLI works on Linux, macOS, and Windows, and provide platform-specific installation or usage notes.
  • Include references to Linux-native tools (e.g., jq for JSON parsing) in CLI examples.
  • Balance PowerShell examples with equivalent Bash or shell script snippets.
  • Clarify that PowerShell Core is cross-platform if recommending it, or provide alternative Linux-native approaches.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on the legacy WindowsAzure.ServiceBus .NET Framework library, which is inherently Windows-centric. All examples and configuration instructions assume usage of .NET on Windows, with no mention of Linux or cross-platform usage. There are no Linux-specific instructions, examples, or notes about running the library on non-Windows platforms. The use of WindowsAzure.ServiceBus and references to the Azure portal further reinforce a Windows-first perspective.
Recommendations
  • Add explicit notes about cross-platform compatibility (e.g., whether the library works on .NET Core/.NET 5+ on Linux/macOS).
  • Provide Linux/macOS usage examples, including installation, configuration, and troubleshooting steps specific to those platforms.
  • Mention any limitations or requirements for running the legacy library on non-Windows systems.
  • Include references to Linux tools and patterns where relevant (e.g., environment variable configuration, command-line usage).
  • Highlight the newer Azure.Messaging.ServiceBus library's cross-platform support and recommend it for Linux/macOS users.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/jms-developer-guide.md .../articles/service-bus-messaging/jms-developer-guide.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references identity creation steps using links that specifically point to Windows VM instructions for configuring managed identities in Azure. There are no Linux-specific instructions, nor is there mention of Linux equivalents or parity in the identity setup process. All code examples are Java and platform-neutral, but the supporting Azure setup documentation is Windows-centric.
Recommendations
  • Provide parallel links and instructions for configuring managed identities on Linux VMs in Azure.
  • Ensure all referenced quickstart or setup guides include both Windows and Linux options, or use pivot tables to allow users to select their OS.
  • Explicitly mention that the identity creation steps apply to both Windows and Linux, and clarify any OS-specific differences.
  • Audit all referenced documentation for similar bias and update links to point to OS-agnostic or multi-platform guides where possible.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-queues-topics-subscriptions.md ...s-messaging/service-bus-queues-topics-subscriptions.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates Windows bias by consistently listing PowerShell as a primary method for creating Service Bus entities, often before mentioning the cross-platform Azure CLI. PowerShell is a Windows-centric tool, and its prominence may suggest Windows as the default platform. There are no explicit Linux-specific examples or references to Linux-native tools, and the ordering of creation options (portal, PowerShell, CLI, ARM templates) places PowerShell before CLI, which is more universally available. No Linux shell or bash examples are provided, nor is there mention of Linux-specific considerations.
Recommendations
  • List Azure CLI before PowerShell in creation instructions, as CLI is cross-platform.
  • Add explicit bash/Linux shell examples for common tasks, such as queue/topic creation and management.
  • Clarify that both PowerShell and CLI are available on Windows, macOS, and Linux, and provide installation links for each.
  • Include references to Linux-native tools or scripts where appropriate.
  • Avoid implying PowerShell is the default or preferred method; present CLI and PowerShell equally.
  • Consider adding a section or note on platform parity, reassuring users that all features are available on Linux.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, validation, and cleanup. However, PowerShell is featured equally alongside CLI, and in the 'Next steps' section, only PowerShell is mentioned for managing Service Bus resources, with no equivalent Linux-specific management guidance (such as Bash scripting or CLI-based management). The documentation does not mention any Linux-specific tools or patterns, and the order of examples sometimes places PowerShell before CLI, suggesting a slight Windows-first bias.
Recommendations
  • Add explicit Bash scripting examples for resource management tasks, especially in the 'Next steps' section.
  • Include references to Linux-native tools or workflows for managing Service Bus resources.
  • Ensure CLI examples are presented first or equally with PowerShell, as CLI is cross-platform.
  • Mention that Azure CLI works natively on Linux and macOS, and provide links to Linux/macOS setup guides.
  • Add a section or links for managing Service Bus resources using REST API or SDKs from Linux environments.
GitHub Create Pull Request
← Previous Page 12 of 16 Next →