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 251-275 of 377 flagged pages
Service Bus Messaging Quickstart - Use the Azure CLI to create a Service Bus queue | Microsoft Docs ...es/service-bus-messaging/service-bus-quickstart-cli.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation shows a mild Windows bias by mentioning Azure PowerShell as an alternative to Cloud Shell before mentioning local CLI installation, and by referencing PowerShell mode in Cloud Shell before Bash. However, all command examples use the cross-platform Azure CLI and explicitly instruct users to switch to Bash mode, which supports Linux parity. There are no exclusive Windows tool examples, but the ordering and mention of PowerShell may subtly prioritize Windows users.
Recommendations
  • Mention Bash and PowerShell equally when discussing Cloud Shell modes, or mention Bash first to reflect cross-platform usage.
  • Clarify that both Bash and PowerShell are available in Cloud Shell, and that Azure CLI works on all platforms.
  • When suggesting local installation, mention both Azure CLI and Azure PowerShell as cross-platform tools, and provide links to both installation guides.
  • Consider adding a note that all CLI commands shown work identically on Windows, Linux, and macOS.
GitHub Create Pull Request
Service Bus Messaging Create Azure Service Bus namespace and queue using Bicep ...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-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, validation, and cleanup, but PowerShell is given equal prominence despite being primarily a Windows tool. In the 'Next steps' section, PowerShell is mentioned first for management tasks, and there is no mention of Linux-specific tools or workflows beyond the CLI. The documentation does not reference Linux shell scripting, nor does it mention cross-platform editors or automation tools that are popular in Linux environments.
Recommendations
  • Ensure that Azure CLI examples are presented before PowerShell, as CLI is cross-platform and more relevant for Linux users.
  • Add references to Linux-native tools and workflows, such as Bash scripting, VS Code on Linux, or automation via shell scripts.
  • Include links to documentation or tutorials for managing Service Bus resources using Linux environments and open-source tools.
  • In the 'Next steps' section, balance PowerShell references with CLI or other Linux-friendly management options.
  • Explicitly state that all CLI commands work on Linux, macOS, and Windows, and provide troubleshooting tips for common Linux issues.
GitHub Create Pull Request
Service Bus Messaging Use the Azure CLI to create Service Bus topics and subscriptions ...aging/service-bus-tutorial-topics-subscriptions-cli.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by mentioning Azure PowerShell as an alternative to Azure CLI in the prerequisites section, and by instructing users to switch Cloud Shell from PowerShell to Bash. Windows/PowerShell tools are referenced before Linux equivalents, and there is an implicit assumption that users may start in PowerShell mode. However, all command examples use Azure CLI in Bash, which is cross-platform.
Recommendations
  • Explicitly mention that Azure CLI works on Windows, Linux, and macOS in the prerequisites.
  • Provide brief instructions or links for installing Azure CLI on Linux and macOS alongside Windows.
  • Clarify that Bash is available on all platforms and is the recommended shell for these examples.
  • Avoid referencing PowerShell as the default or starting point; instead, present Bash and PowerShell equally, or note that Bash is preferred for CLI examples.
  • If mentioning PowerShell, provide equivalent CLI examples for both Bash and PowerShell, or link to PowerShell-specific documentation.
GitHub Create Pull Request
Service Bus Messaging Get started with Azure Service Bus queues (TypeScript) ...-messaging/service-bus-typescript-how-to-use-queues.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally uses cross-platform terminology (e.g., 'command prompt', 'terminal') and does not provide OS-specific code samples. However, there are subtle Windows biases: (1) Windows tools and workflows (such as Visual Studio Code and references to 'command prompt') are mentioned before or instead of Linux alternatives; (2) The only explicit OS-specific deployment link is for 'Node.js cloud service using Windows PowerShell', with no Linux equivalent; (3) There is no mention of Linux-specific editors, shells, or deployment workflows.
Recommendations
  • When referring to opening a command line, use 'terminal or command prompt' and clarify that this applies to both Windows and Linux/macOS.
  • Provide links to both Windows and Linux deployment guides (e.g., add a link to deploying Node.js apps on Azure from Linux/macOS).
  • Mention popular Linux editors (such as VS Code, Vim, or nano) alongside Visual Studio Code.
  • If referencing PowerShell or Windows-specific tools, provide equivalent instructions or links for Bash/Linux users.
  • Explicitly state that all commands (npm, node, az CLI) work on Linux/macOS as well as Windows.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus Subscription Rule SQL Action syntax | Microsoft Docs ...bus-messaging/service-bus-messaging-sql-rule-action.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page references both Azure CLI and PowerShell tools for managing Service Bus subscription rules, but it lists the PowerShell cmdlet (New-AzServiceBusRule) as a primary next step alongside the Azure CLI. There are no explicit Linux-specific examples or mentions of Linux tools, and the SDK references are platform-neutral. The documentation does not provide command-line examples, but the presence of PowerShell and lack of Linux shell (bash) or cross-platform scripting examples suggests a mild Windows bias.
Recommendations
  • Add explicit bash/Linux shell examples for managing Service Bus rules using Azure CLI.
  • Clarify that Azure CLI is cross-platform and provide usage examples on Linux/macOS.
  • Include references to Linux-native tools or scripting patterns where relevant.
  • Ensure that PowerShell references are balanced with Linux shell alternatives in 'Next steps' and example sections.
GitHub Create Pull Request
Service Bus Messaging Troubleshoot AMQP errors in Azure Service Bus | Microsoft Docs ...service-bus-messaging/service-bus-amqp-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. While the main troubleshooting content is platform-neutral, the 'Next steps' section lists 'AMQP in Service Bus for Windows Server' as a recommended resource, highlighting a Windows-specific implementation without mentioning Linux equivalents or cross-platform options. No Linux-specific examples, tools, or troubleshooting patterns are provided, and Windows Server is referenced before any Linux or cross-platform alternatives.
Recommendations
  • Add links or references to Linux-specific AMQP troubleshooting guides or Service Bus usage on Linux.
  • Include examples or notes on how AMQP errors can be diagnosed or resolved using Linux tools (e.g., using system logs, amqp clients on Linux, etc.).
  • Balance the 'Next steps' section with resources for both Windows and Linux users, such as guides for Service Bus on Linux or cross-platform SDKs.
  • Explicitly mention that the troubleshooting steps apply to both Windows and Linux environments, or call out any platform-specific differences.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus Subscription Rule SQL Filter syntax | Microsoft Docs ...vice-bus-messaging/service-bus-messaging-sql-filter.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a mild Windows bias by referencing .NET/C# semantics and Windows-specific tools (PowerShell) before or alongside cross-platform options. Examples and explanations frequently use .NET types and C# operator semantics, which are most familiar to Windows developers. The 'Next steps' section lists PowerShell before Linux-native alternatives, and there is no explicit mention of Linux-specific tools or shell usage (e.g., Bash).
Recommendations
  • Include Linux-specific command-line examples, such as Bash or shell scripting, especially for Azure CLI usage.
  • When referencing system types or operator semantics, clarify their cross-platform applicability or provide equivalent explanations for Java, Python, or other SDKs.
  • In 'Next steps', list cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell), or group them by platform.
  • Add explicit examples or notes for Linux/macOS users, such as environment setup or command syntax differences.
  • Avoid assuming C#/.NET familiarity; provide neutral, language-agnostic explanations where possible.
GitHub Create Pull Request
Service Bus Messaging Use the Azure CLI to create Service Bus topics and subscriptions ...aging/service-bus-tutorial-topics-subscriptions-cli.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
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 Azure CLI in the prerequisites, and by referencing switching from PowerShell to Bash in Azure Cloud Shell. The instructions themselves use Bash syntax and Azure CLI commands, which are cross-platform, but the initial framing and tool suggestions prioritize Windows/PowerShell before Linux equivalents.
Recommendations
  • Mention Bash and PowerShell equally in the prerequisites, clarifying that both are available in Cloud Shell and on local machines.
  • Provide explicit instructions for installing and using Azure CLI on Linux and macOS, not just Windows.
  • If PowerShell is mentioned, also mention Bash or native Linux shells as alternatives, and provide links to their documentation.
  • Avoid language that implies PowerShell is the default or preferred option; instead, present Bash and PowerShell as peer choices.
  • Consider adding a note or section for Linux/macOS users, highlighting any OS-specific considerations.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus duplicate message detection | Microsoft Docs .../articles/service-bus-messaging/duplicate-detection.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references enabling duplicate detection using Azure portal, PowerShell, CLI, Resource Manager template, .NET, Java, Python, and JavaScript. PowerShell is explicitly mentioned as a method for configuration, which is a Windows-centric tool, and it is listed before the cross-platform Azure CLI. There are no explicit Linux shell or bash examples, nor is there mention of Linux-specific tools or workflows. The ordering of tools (PowerShell before CLI) and the lack of Linux-specific examples indicate a mild Windows-first bias.
Recommendations
  • Provide explicit bash or Linux shell examples for enabling duplicate detection.
  • List Azure CLI before PowerShell, or group them together as cross-platform and Windows-specific tools.
  • Mention Linux and macOS compatibility where relevant, especially for CLI and SDK usage.
  • Include links to Linux-specific documentation or tutorials for Service Bus management.
  • Clarify that PowerShell is primarily for Windows users and suggest CLI for cross-platform scenarios.
GitHub Create Pull Request
Service Bus Messaging Enable partitioning in Azure Service Bus basic or standard ...vice-bus-messaging/enable-partitions-basic-standard.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
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, PowerShell is a Windows-centric tool, and its inclusion as a primary example (with a dedicated section) may indicate a Windows bias. The CLI examples are cross-platform, but PowerShell is presented with equal prominence, which can be interpreted as giving Windows tooling parity or preference. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific patterns or tools. The ordering of sections (CLI before PowerShell) slightly mitigates the bias, but the presence of PowerShell examples and lack of Linux-specific guidance or troubleshooting still reflects a subtle Windows bias.
Recommendations
  • Add explicit bash shell examples for Azure CLI commands, showing usage in a typical Linux environment.
  • Clarify that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Add troubleshooting notes or tips for Linux users, such as installation or authentication differences.
  • Consider de-emphasizing PowerShell or moving it after CLI and ARM template sections, or labeling it as 'Windows (PowerShell)' for clarity.
  • Include links to Linux-specific documentation or guides for Service Bus management.
GitHub Create Pull Request
Service Bus Messaging Enable partitioning in Azure Service Bus Premium namespaces ...les/service-bus-messaging/enable-partitions-premium.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for enabling partitioning, but the PowerShell example is given equal prominence to the CLI example, and there is no explicit mention of Linux or Bash scripting. The PowerShell example, which is primarily a Windows tool, is included as a primary method, potentially signaling a Windows-centric approach. However, the Azure CLI example is cross-platform and presented first, which helps mitigate bias. There are no explicit Linux-only tools or examples, and no mention of Bash or shell scripting. The 'Next steps' section is language-agnostic.
Recommendations
  • Clearly indicate that Azure CLI commands are cross-platform and can be run on Windows, Linux, and macOS.
  • Consider including a Bash or shell scripting example or note for Linux users, especially if there are any platform-specific considerations.
  • If PowerShell is included, clarify that it is available cross-platform (PowerShell Core), or specify when the example is Windows-only.
  • Add a brief note or section for Linux/macOS users to reinforce parity and inclusivity.
  • Ensure that any screenshots or UI references do not assume a Windows environment unless unavoidable.
GitHub Create Pull Request
Service Bus Messaging Message transfers, locks, and settlement ...ce-bus-messaging/message-transfers-locks-settlement.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by exclusively providing C# code examples, which are most commonly associated with Windows environments and .NET development. There are no Linux-specific examples, nor are alternative code samples shown for other platforms or languages (such as Python, Java, or JavaScript) that are popular on Linux. Additionally, there is no mention of Linux-specific tools, patterns, or considerations, and the documentation does not address cross-platform usage or parity.
Recommendations
  • Add code examples in other supported languages (e.g., Python, Java, JavaScript, Go) alongside C# to demonstrate cross-platform usage.
  • Explicitly mention that the APIs and concepts apply equally to Linux environments, and clarify any platform-specific differences if they exist.
  • Include notes or examples for using Service Bus from Linux environments, such as running code in containers, using Linux-based SDKs, or integrating with Linux-native tools.
  • Avoid language that implies Windows/.NET is the primary or default platform; present all supported platforms and languages with equal prominence.
  • Provide links to cross-platform SDK documentation and usage guides.
GitHub Create Pull Request
Service Bus Messaging Create Azure Service Bus namespace and queue using Azure template ...saging/service-bus-resource-manager-namespace-queue.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. While the main instructions focus on using the Azure Portal (which is cross-platform via browser), the 'Next steps' section lists PowerShell management before mentioning other tools, and references to Service Bus Explorer (a Windows-only tool) are present. There is no explicit example or guidance for Linux users or for using the Azure CLI, despite a link to CLI documentation in the references.
Recommendations
  • Add explicit Azure CLI examples for deploying and managing Service Bus resources, especially in the 'Next steps' and management sections.
  • Mention cross-platform tools and workflows before or alongside Windows-specific ones (e.g., list Azure CLI before PowerShell).
  • Clarify which tools are cross-platform and which are Windows-only, such as Service Bus Explorer.
  • Provide links to Linux/macOS-specific guidance or troubleshooting where relevant.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus - message count ...ain/articles/service-bus-messaging/message-counters.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, but does not include Linux-specific command-line examples (e.g., Bash scripting, shell pipelines) or mention Linux tools. The PowerShell section is given equal prominence to Azure CLI, despite PowerShell being primarily associated with Windows. There are no explicit Linux examples or references to Linux-native patterns, and the sample outputs are shown in a generic 'bash' format, which may be misleading as PowerShell output formatting differs from Bash.
Recommendations
  • Add explicit Linux/Bash examples for querying message counts, such as using Azure CLI in Bash scripts or with jq for parsing JSON output.
  • Clarify that Azure CLI is cross-platform and provide sample usage in both Windows (CMD/PowerShell) and Linux (Bash/zsh) environments.
  • If PowerShell examples are included, consider adding equivalent examples using Bash or other Linux-native shells to ensure parity.
  • Mention Linux tools (e.g., jq, grep) for processing Azure CLI output, and provide sample commands.
  • Review sample output formatting to ensure it matches the shell context (PowerShell vs Bash).
GitHub Create Pull Request
Service Bus Messaging Get started with Azure Service Bus queues (Go) ...vice-bus-messaging/service-bus-go-how-to-use-queues.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell instructions for setting environment variables, but lists Bash first, which is positive for Linux parity. However, in the prerequisites section, there is a link to Visual Studio/MSDN subscriber benefits, which is Windows-centric and appears before the free account link. The authentication instructions mention Azure CLI, which is cross-platform, and do not reference Windows-only tools. There are no examples or instructions that are exclusive to Windows or PowerShell, and Linux users are not disadvantaged in following the tutorial. Overall, the page is mostly neutral, with a slight Windows-first bias in the ordering of account options.
Recommendations
  • List free Azure account sign-up before Visual Studio/MSDN subscriber benefits to avoid Windows-first perception.
  • Clarify that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Continue to provide Bash instructions first for environment variables, as this supports Linux parity.
  • Avoid mentioning Windows-specific tools or patterns unless Linux/macOS equivalents are also provided.
GitHub Create Pull Request
Service Bus Messaging Migrate an application to use passwordless connections with Azure Service Bus ...bus-messaging/service-bus-migrate-azure-credentials.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias by consistently referencing Windows-centric tools (Visual Studio) and patterns (servicebus.windows.net domain), and mentioning Windows tools before Linux equivalents (e.g., Visual Studio listed before IntelliJ, no mention of VS Code or Linux editors). There are no PowerShell-heavy examples, but the documentation does not explicitly provide Linux-specific instructions or examples for authentication, local development, or tooling. The Azure CLI is used throughout, which is cross-platform, but the overall tone and tool recommendations lean toward Windows environments.
Recommendations
  • Explicitly mention Linux and macOS compatibility for all steps, especially for local development and authentication.
  • Include examples or references for popular Linux/macOS editors (e.g., VS Code, Vim, JetBrains IDEs) alongside Visual Studio.
  • Clarify that Azure CLI commands work on Linux/macOS and provide any necessary shell-specific notes (e.g., quoting, environment variables).
  • Add troubleshooting notes for Linux/macOS environments (e.g., credential caching, file permissions).
  • Where screenshots or UI instructions are given, note any differences for Linux/macOS users.
  • Consider including a section or callout for Linux/macOS developers to ensure parity and inclusivity.
GitHub Create Pull Request
Service Bus Messaging Create Azure Service Bus namespace and queue using Bicep ...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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, validation, and cleanup, but PowerShell is given equal prominence despite being primarily a Windows tool. In the 'Next steps' section, PowerShell management is mentioned before cross-platform tools, and there is no mention of Linux-specific patterns or tools (e.g., Bash scripting, automation via shell scripts). The documentation does not provide Linux-specific guidance or highlight cross-platform considerations beyond the CLI.
Recommendations
  • Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and recommend CLI for cross-platform scenarios.
  • In the 'Next steps' section, mention cross-platform management tools (e.g., Bash scripts, automation via Azure CLI) before PowerShell.
  • Add examples or links for automating deployments using Bash scripts or other Linux-native tools.
  • Clarify that PowerShell Core is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
  • Ensure that Linux users are guided to parity in tooling and workflow, possibly with a dedicated section for Linux/macOS users.
GitHub Create Pull Request
Service Bus Messaging Create Azure Service Bus namespace topic using a template ...saging/service-bus-resource-manager-namespace-topic.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents both PowerShell and Azure CLI examples for deploying the template, but PowerShell is listed first and is referenced in the 'Next steps' section for resource management. There is a notable emphasis on PowerShell-based management, which is traditionally associated with Windows environments, while Linux-native tools and workflows are not mentioned. The CLI example is present, but there is no explicit Linux-specific guidance, and PowerShell is prioritized in both deployment and management instructions.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or list Azure CLI first to avoid implicit Windows prioritization.
  • Include explicit instructions or examples for Linux environments, such as bash scripts or references to Linux package managers for installing Azure CLI.
  • Add links to documentation for managing Service Bus resources using Azure CLI or REST API, especially for Linux/macOS users.
  • Reference cross-platform tools and clarify that Azure CLI works natively on Linux, macOS, and Windows.
  • In the 'Next steps' section, provide parity by including CLI-based management guides alongside PowerShell guides.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus to Event Grid integration overview | Microsoft Docs ...aging/service-bus-to-event-grid-integration-concept.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for creating Event Grid subscriptions, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is listed immediately after. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or workflows. The Azure portal instructions are platform-neutral, but the command-line guidance leans toward Windows environments by including PowerShell and not, for example, bash scripts.
Recommendations
  • Add explicit bash shell examples alongside Azure CLI commands to demonstrate Linux parity.
  • Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide platform-specific notes if necessary.
  • If PowerShell is included, consider also mentioning PowerShell Core (cross-platform) or clarify its Windows focus.
  • Ensure that Linux users are guided on how to perform equivalent tasks, such as using Azure CLI in bash or zsh.
  • Review referenced tutorials to ensure Linux workflows are represented and not just Windows/PowerShell-centric.
GitHub Create Pull Request
Service Bus Messaging Get started with Azure Service Bus queues (TypeScript) ...-messaging/service-bus-typescript-how-to-use-queues.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is mostly cross-platform in its instructions and code examples, but there is a subtle Windows bias in the references to Windows-specific tools and deployment patterns. Notably, a key link for deploying Node.js applications points to a Windows PowerShell-based workflow before mentioning more general approaches. There are no explicit Linux or macOS-specific instructions or examples, and the term 'command prompt' is used generically, which may be interpreted as Windows-centric.
Recommendations
  • When referencing deployment guides, provide links for both Windows (PowerShell/Command Prompt) and Linux/macOS (Bash/Terminal) workflows, or use a platform-agnostic guide as the primary reference.
  • Where 'command prompt' is mentioned, clarify that the instructions work in any terminal (Command Prompt, PowerShell, Bash, etc.) and provide examples or notes for Linux/macOS users.
  • If linking to platform-specific guides (e.g., Windows PowerShell), ensure equivalent Linux/macOS guides are also linked and presented with equal prominence.
  • Consider including explicit notes or tabs for Linux/macOS users in sections where environment setup or command-line usage may differ (e.g., npm installation, Azure CLI usage).
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-amqp-troubleshoot.md ...service-bus-messaging/service-bus-amqp-troubleshoot.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 page references 'Service Bus for Windows Server' as a key next step link, highlighting Windows-specific tooling and deployment. There are no Linux-specific examples, troubleshooting steps, or references to Linux environments or tools. The only platform-specific mention is Windows, and it appears before any mention of cross-platform or Linux equivalents.
Recommendations
  • Add troubleshooting guidance and examples for Linux environments, such as using common Linux AMQP clients or command-line tools.
  • Include references to Service Bus usage and AMQP troubleshooting on Linux, such as links to documentation for Linux SDKs or deployment guides.
  • Balance platform-specific references by mentioning both Windows and Linux environments when discussing Service Bus and AMQP.
  • Provide parity in next steps, e.g., add a link to 'AMQP in Service Bus for Linux' or equivalent cross-platform documentation if available.
GitHub 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 →
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 Windows/.NET bias by exclusively providing .NET/C# code samples and referencing Windows-centric platforms (e.g., .NET Framework, Universal Windows Platform) without mentioning or providing examples for Linux-specific environments, tools, or SDKs. There are no Linux shell, Python, or cross-platform CLI examples, and the documentation assumes familiarity with Windows development patterns.
Recommendations
  • Add equivalent code samples for Linux-friendly SDKs (e.g., Python, Java) and show how to run them on Linux.
  • Include instructions or examples using Azure CLI or REST API, which are cross-platform.
  • Explicitly mention Linux compatibility for the .NET Core SDK and provide guidance for running .NET code on Linux (e.g., using dotnet CLI on Ubuntu).
  • Reference Linux distributions and environments in platform support tables, not just Windows-centric platforms.
  • Provide troubleshooting or performance monitoring guidance using Linux tools (e.g., top, htop, systemd) alongside Azure Monitor.
  • Include links to Linux-specific documentation or community resources for Azure Service Bus.
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-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 Azure CLI in the prerequisites section and by referencing PowerShell mode in Azure Cloud Shell before Bash. No explicit Linux examples or Linux-specific instructions are provided, and the guidance for switching Cloud Shell modes assumes users may start in PowerShell (Windows-centric) mode. 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 instructions for all platforms.
  • In the prerequisites, list Bash and Linux/macOS usage equally with Windows/PowerShell, rather than referencing PowerShell first.
  • Add a note or section for Linux/macOS users, confirming that all CLI commands work natively in their environments.
  • Provide links to platform-specific installation guides for Azure CLI (Linux, macOS, Windows).
  • Clarify that Azure Cloud Shell defaults to Bash for Linux/macOS users and PowerShell for Windows users, and provide instructions for both.
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-09 00:34
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 is listed explicitly and before CLI, which is more cross-platform. There are no explicit Linux-specific examples or mentions of Linux tools (e.g., Bash, shell scripts), and Windows-centric tools (PowerShell) are referenced before cross-platform alternatives.
Recommendations
  • List Azure CLI before PowerShell when describing cross-platform configuration options.
  • Include explicit Linux/Bash examples or references alongside PowerShell, especially for command-line operations.
  • Clarify that Azure CLI is available and supported on Linux and macOS, not just Windows.
  • Provide links to Linux-specific documentation or samples where relevant.
  • Avoid listing Windows-specific tools before cross-platform alternatives unless there is a technical reason.
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-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 enabling partitioning in Azure Service Bus. However, the PowerShell section is given its own dedicated heading and examples, which may suggest a Windows-centric approach, as PowerShell is primarily associated with Windows environments. The CLI examples are cross-platform, but there is no explicit mention of Linux or Bash-specific usage, nor are there any Linux-specific tools or patterns discussed. The ordering of sections places PowerShell immediately after CLI, which is common but may reinforce a Windows-first mindset. No Linux-specific examples or troubleshooting are provided.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash, Zsh).
  • Add sample Bash scripts or usage notes for Linux users, such as how to install Azure CLI on Linux and run the commands.
  • Clarify that PowerShell Core is available cross-platform, but note that most Linux users will prefer CLI.
  • Consider reordering or grouping CLI and PowerShell sections under a common 'Command-line tools' heading to avoid implying platform preference.
  • Add troubleshooting notes or links for Linux users, such as common permission or environment issues.
GitHub Create Pull Request
← Previous Page 11 of 16 Next →