Service Bus Messaging

268
Total Pages
221
Linux-Friendly Pages
47
Pages with Bias
17.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

91 issues found
Showing 26-50 of 91 flagged pages
Service Bus Messaging Troubleshooting guide for Azure Service Bus | Microsoft Docs ...ice-bus-messaging/service-bus-troubleshooting-guide.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Troubleshooting steps and examples often reference Windows tools (PowerShell, .NET EventSource, Application Insights, Sysinternals' psping) and provide Windows commands before Linux equivalents. Some diagnostic and logging guidance is .NET-centric, with limited mention of cross-platform alternatives. Linux/macOS users are given fewer examples, and Windows-specific tools are recommended without clear Linux substitutes.
Recommendations
  • Provide Linux/macOS equivalents for all troubleshooting commands and tools (e.g., show 'telnet' or 'nc' before or alongside 'tnc', suggest 'ss', 'netcat', or 'tcping' for port checks).
  • Include cross-platform logging and tracing instructions (e.g., OpenTelemetry setup for Java, Python, Node.js, not just .NET).
  • Mention and link to Linux/macOS-friendly diagnostic tools (e.g., Wireshark, tcpdump, strace) alongside Windows tools.
  • Ensure code samples and troubleshooting steps are not .NET/.NET Core exclusive; add examples for Java, Python, and other SDKs.
  • Avoid recommending Windows-only utilities (like psping) without suggesting cross-platform alternatives.
  • When referencing PowerShell, provide Bash/zsh equivalents for Linux/macOS users.
  • Balance the order of examples so Linux/macOS instructions are not always secondary.
GitHub Create Pull Request
Service Bus Messaging Tutorial: Update inventory using Azure portal and topics/subscriptions ...ng/service-bus-tutorial-topics-subscriptions-portal.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The tutorial demonstrates a notable Windows bias. It references Windows-specific tools (Visual Studio), and all command-line instructions are given in terms of Command Prompt or PowerShell, with no mention of Linux/macOS equivalents. There are no instructions for using Linux shells, nor are alternative IDEs or .NET SDK installation methods for non-Windows platforms discussed. This may create friction for Linux/macOS users attempting to follow the tutorial.
Recommendations
  • Add explicit instructions for Linux/macOS users, including terminal commands and .NET SDK installation steps.
  • Mention cross-platform IDEs (e.g., VS Code) and provide links to .NET installation guides for Linux/macOS.
  • Clarify that the sample code and dotnet CLI commands work on Linux/macOS, and show example commands in Bash/zsh.
  • Avoid referencing only Windows-specific tools (e.g., Notepad, Command Prompt, PowerShell) or provide alternatives.
  • Include screenshots or notes relevant to Linux/macOS environments where appropriate.
GitHub Create Pull Request
Service Bus Messaging Configure the minimum TLS version for a Service Bus namespace using ARM ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/transport-layer-security-configure-minimum-version.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are given equal prominence to Azure CLI, and ARMClient (a Windows-centric tool) is recommended for acquiring Bearer tokens, with only Windows usage shown. The example commands for checking TLS version use PowerShell and ARMClient.exe, with no mention of Linux/macOS alternatives (such as Azure CLI, curl, or native REST calls). Windows tools and patterns are presented first or exclusively in some sections.
Recommendations
  • Provide Linux/macOS equivalents for ARMClient usage, such as using Azure CLI (`az account get-access-token`) or curl for REST API calls.
  • Include example commands for checking the minimum TLS version using Azure CLI, curl, or bash scripts.
  • When showing PowerShell examples, also show bash/Azure CLI equivalents side-by-side.
  • Mention cross-platform tools and patterns before or alongside Windows-specific ones.
  • Clarify which tools are cross-platform and which are Windows-only, and suggest alternatives for non-Windows users.
GitHub Create Pull Request
Service Bus Messaging Test locally by using the Azure Service Bus emulator ...us-messaging/test-locally-with-service-bus-emulator.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific instructions (PowerShell, WSL) are presented first and in detail, with Linux/macOS instructions given less prominence and detail. The automated script section for Windows includes explicit PowerShell and WSL steps, while the Linux/macOS section is brief and lacks step-by-step guidance. There are references to Windows tools (WSL, PowerShell) and file path examples default to Windows format. Linux and macOS users may need to infer steps or adapt instructions, creating friction.
Recommendations
  • Provide step-by-step Linux/macOS instructions for the automated script, matching the detail given for Windows (e.g., which shell to use, navigation commands).
  • Include Linux/macOS file path examples alongside Windows examples in environment variable documentation.
  • Present Linux/macOS instructions before or alongside Windows instructions to avoid 'Windows-first' bias.
  • Clarify which commands and scripts are cross-platform and explicitly state any platform-specific differences.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., Docker permissions, shell compatibility).
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus - suspend messaging entities .../main/articles/service-bus-messaging/entity-suspend.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides explicit instructions and code examples for changing queue status using Azure PowerShell, a Windows-centric tool. There are no equivalent examples or instructions for Linux/macOS users, such as using Azure CLI, REST API, or SDKs. The only non-Windows method described is via the Azure portal, which is platform-agnostic but less suitable for automation or scripting.
Recommendations
  • Add Azure CLI examples for changing queue, topic, and subscription status, as Azure CLI is cross-platform.
  • Include REST API or SDK (e.g., Python, .NET, Java) examples for programmatic access from any OS.
  • Explicitly mention that Azure PowerShell is primarily for Windows and suggest alternatives for Linux/macOS users.
  • Ensure all automation/scripting instructions are available for both Windows and Linux/macOS environments.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus JMS 2.0 developer guide .../articles/service-bus-messaging/jms-developer-guide.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation references Windows-specific resources first when describing how to create a system assigned managed identity, linking to a Windows VM portal guide. No Linux/macOS equivalents or parity links are provided in this section, which may cause friction for non-Windows users. However, the core Java code and Service Bus usage instructions are platform-agnostic.
Recommendations
  • Provide links to Linux and macOS guides for creating managed identities, such as configuring managed identities on Linux VMs or App Services.
  • Add a note clarifying that managed identities and authentication methods are available on Linux/macOS and link to relevant cross-platform documentation.
  • Ensure all platform-specific instructions are presented in parallel or with clear alternatives for Linux/macOS users.
GitHub Create Pull Request
Service Bus Messaging Create an Azure Service Bus namespace using template ...us-messaging/service-bus-resource-manager-namespace.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively provides Azure PowerShell examples for deploying and managing a Service Bus namespace, with no equivalent Azure CLI or Bash examples. The instructions and code blocks assume use of PowerShell, which is most familiar to Windows users. While alternative deployment methods (Azure CLI, REST API, portal) are briefly mentioned, no examples or guidance are given for Linux/macOS users who may prefer Bash or Azure CLI.
Recommendations
  • Add equivalent Azure CLI examples alongside PowerShell scripts for all deployment, verification, and cleanup steps.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
  • Reorder or parallelize examples so that Windows and Linux/macOS users see their preferred tools equally represented.
  • Include notes or links to platform-specific guidance 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-11 06:20
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 is referenced in the 'Next steps' section for management tasks, with no equivalent Bash or Linux shell management guidance. The CLI example is present, but the management section only mentions PowerShell and a Windows-centric GUI tool (Service Bus Explorer), suggesting a Windows-first approach and a PowerShell-heavy bias.
Recommendations
  • List Azure CLI examples before PowerShell, or present them side-by-side to avoid implying preference.
  • Add explicit Bash/Linux shell management examples for Service Bus resources, especially in the 'Next steps' section.
  • Include links or references to cross-platform tools for managing Service Bus (e.g., Azure CLI, REST API usage from Bash, or VS Code extensions).
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and provide platform-agnostic instructions for installation and usage.
GitHub Create Pull Request
Service Bus Messaging Authenticate an application to access Azure Service Bus entities ...cles/service-bus-messaging/authenticate-application.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing .NET/C# code samples, referencing Azure PowerShell before Azure CLI, and linking only to Windows-centric tools and samples. There are no examples or explicit guidance for Linux/macOS users, such as Python or Java SDK usage, nor are Linux-specific authentication flows or CLI commands demonstrated. The reliance on Azure portal screenshots and .NET libraries further centers the experience around Windows environments.
Recommendations
  • Add code samples for other platforms and languages commonly used on Linux/macOS, such as Python, Java, or Node.js.
  • Include explicit Azure CLI examples for authentication and role assignment, and present them before or alongside PowerShell examples.
  • Provide guidance and screenshots for using the Azure portal from non-Windows environments, or clarify that the portal is cross-platform.
  • Reference and link to cross-platform SDKs and samples, not just .NET.
  • Mention Linux/macOS compatibility in relevant sections, and provide troubleshooting tips for those platforms.
GitHub Create Pull Request
Service Bus Messaging Azure messaging services - Service Manager to Resource Manager ...vice-bus-messaging/deprecate-service-bus-management.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page exclusively provides PowerShell command mappings for Azure Service Manager to Resource Manager, with no mention of cross-platform CLI tools (such as Azure CLI), Bash, or Linux/macOS workflows. All automation and scripting examples are Windows-centric, referencing only PowerShell cmdlets and modules. There is no guidance for Linux/macOS users, nor are alternative tools or command examples provided. REST API references are platform-neutral, but all scripting/automation guidance is Windows-focused.
Recommendations
  • Add equivalent Azure CLI command mappings for each PowerShell example, with links to CLI documentation.
  • Include Bash or shell script examples for REST API usage, demonstrating cross-platform approaches.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, and clarify compatibility if relevant.
  • Reorder or parallelize scripting sections to present Windows (PowerShell) and Linux/macOS (CLI/Bash) options side-by-side.
  • Reference platform-agnostic tools (e.g., Terraform, ARM templates) where appropriate.
GitHub Create Pull Request
Service Bus Messaging Configure your own key for encrypting Azure Service Bus data at rest ...ervice-bus-messaging/configure-customer-managed-key.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a notable Windows bias, particularly in sections involving command-line operations and automation. Most step-by-step instructions for deploying templates, managing identities, and configuring access policies use PowerShell commands exclusively, with no Bash or Linux CLI equivalents provided. References to 'PowerShell' are frequent and examples are given only in PowerShell syntax, even though Azure CLI is cross-platform and could be used. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Bash. Additionally, Windows-centric tools and patterns (e.g., PowerShell cmdlets, 'New-AzResourceGroupDeployment', 'Set-AzureRmKeyVaultAccessPolicy') are mentioned before or instead of their cross-platform alternatives.
Recommendations
  • Provide Azure CLI (az) command equivalents for all PowerShell examples, especially for resource deployment and access policy management.
  • Explicitly state that all operations can be performed using Azure CLI on Linux/macOS, and link to relevant CLI documentation.
  • Where possible, show both PowerShell and Bash/CLI examples side-by-side, or use tabs to allow users to select their preferred environment.
  • Clarify prerequisites for Linux/macOS users, such as installing Azure CLI, and avoid assuming PowerShell is available.
  • Review screenshots and UI instructions to ensure they are not Windows-specific.
GitHub Create Pull Request
Service Bus Messaging Enable duplicate message detection - Azure Service Bus ...es/service-bus-messaging/enable-duplicate-detection.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for enabling duplicate message detection in Azure Service Bus. However, the PowerShell section is extensive and detailed, and PowerShell is a Windows-centric tool. The CLI examples are present and shown before PowerShell, but the PowerShell section is longer and includes more advanced update scenarios. There is no mention of Linux/macOS-specific tools or shell patterns (e.g., Bash), nor are there notes about running PowerShell cross-platform. The documentation does not provide parity for Linux/macOS users regarding scripting or automation beyond Azure CLI.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, or provide guidance for Linux/macOS users if applicable.
  • Expand CLI examples to cover all scenarios shown in PowerShell (e.g., updating queue/topic properties with complex objects).
  • Add Bash or shell script equivalents for advanced scenarios, or explicitly state that CLI covers all Linux/macOS needs.
  • Consider mentioning that PowerShell Core is available on Linux/macOS, if relevant, and provide installation links.
  • Ensure that advanced update scenarios are equally documented for CLI users.
GitHub Create Pull Request
Service Bus Messaging Enable dead lettering for Azure Service Bus queues and subscriptions ...n/articles/service-bus-messaging/enable-dead-letter.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides examples for enabling dead lettering in Azure Service Bus using the Azure portal, Azure CLI, Azure PowerShell, and ARM templates. While the Azure CLI and ARM templates are cross-platform, the PowerShell section is extensive and uses Windows-centric tooling. PowerShell is presented as a primary automation method, and its examples are detailed and prominent. There are no Linux shell (bash) or macOS-specific examples, nor are there references to Linux-native scripting approaches. The ordering of sections places PowerShell before ARM templates, which are more platform-neutral.
Recommendations
  • Add bash or shell scripting examples for Linux/macOS users, especially for automation tasks.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and consider providing explicit bash examples.
  • Reorder sections so that platform-neutral tools (CLI, ARM templates) appear before Windows-specific tools (PowerShell).
  • Mention alternatives to PowerShell for Linux/macOS users, such as using Azure CLI in shell scripts.
  • Explicitly state platform compatibility for each tool at the start of relevant sections.
GitHub Create Pull Request
Service Bus Messaging Use legacy WindowsAzure.ServiceBus .NET framework library with AMQP 1.0 | Microsoft Docs ...icles/service-bus-messaging/service-bus-amqp-dotnet.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 code and configuration examples assume .NET Framework usage, with no mention of Linux or macOS environments, nor any cross-platform .NET Core/.NET 5+ guidance. There are no Linux-specific instructions, examples, or troubleshooting notes, and Windows terminology (e.g., 'WindowsAzure', 'Windows tools') is used throughout.
Recommendations
  • Add explicit guidance for using the newer Azure.Messaging.ServiceBus package, which is cross-platform and works on Linux/macOS.
  • Include examples and instructions for running .NET code on Linux/macOS (e.g., using .NET Core/.NET 5+).
  • Clarify platform compatibility for the legacy library and recommend alternatives for non-Windows users.
  • Add troubleshooting notes or links for Linux/macOS environments, such as certificate handling or networking differences.
  • Reorder sections to mention cross-platform options first, or provide parity in example ordering.
GitHub Create Pull Request
Service Bus Messaging Get started with Azure Service Bus topics (.NET) ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-dotnet-how-to-use-topics-subscriptions.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented toward Windows users, with all instructions and screenshots referencing Visual Studio and Windows-specific workflows. Package installation is shown only via the NuGet Package Manager Console (PowerShell), and there are no instructions for Linux/macOS users (e.g., using VS Code, JetBrains Rider, or CLI tools like dotnet CLI). The prerequisites and steps assume Visual Studio is available, and no alternative editors or workflows are mentioned. There are no Linux/macOS-specific notes, nor any parity in example ordering or tooling.
Recommendations
  • Add instructions for Linux/macOS users, including how to use VS Code, JetBrains Rider, or the dotnet CLI to create and run .NET projects.
  • Provide package installation examples using 'dotnet add package' CLI commands, which work cross-platform.
  • Include screenshots or descriptions for non-Windows environments, or clarify that the steps are similar across platforms.
  • Explicitly mention that .NET and Azure SDKs are cross-platform and provide links to relevant setup guides for Linux/macOS.
  • Reorder or parallelize instructions so that Windows and Linux/macOS workflows are presented side-by-side or in tabs.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides only C# code examples and references .NET Framework and .NET Standard clients, which are most commonly associated with Windows environments. There are no examples or explicit mentions of Linux/macOS-specific tools, languages, or usage patterns, and the examples are written in C# without showing parity for other supported languages (Java, Python, JavaScript, Go). This creates a subtle Windows-first bias and leaves Linux/macOS users with less direct guidance.
Recommendations
  • Add code examples for other supported languages (Java, Python, JavaScript, Go) alongside C# to ensure cross-platform parity.
  • Explicitly mention that the APIs and patterns shown are applicable on Linux/macOS as well as Windows, and clarify any platform-specific differences if they exist.
  • Include links or references to SDK documentation for Linux/macOS environments.
  • If discussing .NET Framework (Windows-only), clarify its platform limitations and provide alternatives for Linux/macOS users (e.g., .NET Core/.NET 6+, Java, Python, etc.).
GitHub Create Pull Request
Service Bus Messaging Integrate Azure Service Bus with Azure Private Link Service ...articles/service-bus-messaging/private-link-service.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for CLI automation, referencing the creation of a Windows VM for validation, and omitting equivalent Linux/macOS instructions or examples. Windows tools and patterns (PowerShell, Windows VM) are mentioned exclusively, with no mention of Azure CLI, Bash, or Linux VM alternatives.
Recommendations
  • Add Azure CLI (az) examples alongside or before PowerShell examples for creating private endpoints.
  • Include instructions for creating and validating with a Linux VM, referencing the appropriate Azure documentation.
  • Provide Bash shell command examples for DNS validation (e.g., using dig or nslookup on Linux/macOS).
  • Explicitly state that the steps are cross-platform where possible, and highlight any platform-specific differences.
GitHub Create Pull Request
Service Bus Messaging Quickstart - Use Azure Service Bus queues from .NET app ...essaging/service-bus-dotnet-get-started-with-queues.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows users, specifically those using Visual Studio. All instructions for creating projects, managing NuGet packages, and authentication are based on Visual Studio GUI and PowerShell commands, with no mention of cross-platform alternatives such as .NET CLI, VS Code, or Linux/macOS workflows. This creates friction for Linux/macOS users who do not use Visual Studio or PowerShell.
Recommendations
  • Add instructions for using the .NET CLI (e.g., 'dotnet new console', 'dotnet add package') for project creation and package management, which work on all platforms.
  • Include guidance for using VS Code or other cross-platform editors, not just Visual Studio.
  • Replace PowerShell-specific commands with .NET CLI equivalents, or provide both.
  • Clarify that the code samples work on Linux/macOS as well, and provide any necessary notes (e.g., regarding authentication, environment variables, or port requirements).
  • Add a 'Platform compatibility' section early in the document to reassure non-Windows users and point to relevant cross-platform resources.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus Geo-Disaster Recovery | Microsoft Docs ...n/articles/service-bus-messaging/service-bus-geo-dr.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Examples and sample code are primarily in .NET (Windows-centric), and PowerShell is mentioned as a primary automation tool. There is no explicit mention of Linux/macOS-specific CLI examples, nor are cross-platform tools or shell commands (e.g., Bash, Azure CLI on Linux) shown. The ordering and language suggest Windows/PowerShell approaches are the default, with Linux alternatives missing or relegated to secondary status.
Recommendations
  • Add explicit Azure CLI examples for all setup and failover steps, showing usage on Linux/macOS.
  • Include sample code in cross-platform languages (e.g., Python, Java) alongside .NET.
  • Clarify that Azure CLI and REST API are fully supported on Linux/macOS and provide links to relevant documentation.
  • Reorder sections so that cross-platform tools (Azure CLI, REST API) are mentioned before or alongside PowerShell.
  • Add notes or callouts for Linux/macOS users where UI or tooling may differ.
GitHub Create Pull Request
Service Bus Messaging Set subscriptions filters in Azure Service Bus | Microsoft Docs ...s/service-bus-messaging/service-bus-filter-examples.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example Dotnet Heavy
Summary
The documentation page demonstrates a notable bias toward Windows and .NET users. Windows-specific tools (PowerShell) are mentioned explicitly, and examples for creating and managing Service Bus filters are almost exclusively provided in C#/.NET. There are no Linux/macOS-specific command-line examples (e.g., Bash), and PowerShell is referenced without equivalent Bash or cross-platform scripting alternatives. The CLI is mentioned, but not exemplified, and all code samples are in C# with no parity for other languages or platforms.
Recommendations
  • Provide explicit Bash/Azure CLI examples for common tasks, such as creating rules and filters.
  • Include sample code snippets in other supported languages (e.g., Python, Java, JavaScript) for creating and managing filters.
  • When referencing PowerShell, also show equivalent CLI/Bash commands to ensure parity.
  • Add notes or sections clarifying cross-platform compatibility and any OS-specific caveats.
  • Reorder sections so that cross-platform tools (CLI) are presented before Windows-specific tools (PowerShell).
GitHub Create Pull Request
Service Bus Messaging Configure IP firewall rules for Azure Service Bus ...cles/service-bus-messaging/service-bus-ip-filtering.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides explicit PowerShell instructions for managing IP firewall rules, but does not offer equivalent Linux/macOS shell examples (e.g., Bash). The Azure CLI is mentioned, but no concrete CLI command examples are shown, while PowerShell commands are listed. The Resource Manager template section is platform-neutral, but deployment instructions link to a PowerShell page. Overall, Windows/PowerShell tools and patterns are mentioned before or instead of Linux equivalents, creating friction for non-Windows users.
Recommendations
  • Add explicit Azure CLI command examples for all tasks currently shown with PowerShell.
  • Ensure deployment instructions for Resource Manager templates include Bash/CLI options, not just PowerShell.
  • Present CLI and PowerShell examples side-by-side or alternate their order to avoid Windows-first bias.
  • Include notes clarifying cross-platform support for Azure CLI and REST API usage.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus - messaging exceptions | Microsoft Docs ...s-messaging/service-bus-messaging-exceptions-latest.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the troubleshooting section for SocketException, where only a PowerShell 'nslookup' command is provided and the prompt is shown as 'PS C:\>', implying Windows usage. No Linux/macOS equivalent commands (e.g., 'nslookup' or 'dig' in bash/zsh) are given. Additionally, the example output is formatted as Windows command line output, and there is no mention of Linux or macOS troubleshooting steps for DNS resolution.
Recommendations
  • Provide Linux/macOS equivalents for all command-line troubleshooting steps, e.g., show 'nslookup <mynamespace>.servicebus.windows.net' and/or 'dig <mynamespace>.servicebus.windows.net' with bash/zsh prompt.
  • Include example outputs for Linux/macOS commands.
  • Avoid using only Windows-specific prompts (e.g., 'PS C:\>'); show both Windows and Linux/macOS prompts or use a neutral format.
  • Explicitly mention that the troubleshooting steps apply to all platforms and clarify any platform-specific differences.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus messaging - queues, topics, and subscriptions ...s-messaging/service-bus-queues-topics-subscriptions.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias in the sections describing how to create queues, topics, and subscriptions. PowerShell is listed before CLI as a method for resource creation, and explicit links to PowerShell modules are provided, while Linux-native tools (Azure CLI) are mentioned but not highlighted or explained first. There are no direct Linux/macOS examples or references to Bash scripting, and no mention of platform-specific considerations for non-Windows users.
Recommendations
  • List Azure CLI before PowerShell when describing cross-platform resource creation, as CLI is natively supported on Linux/macOS.
  • Provide explicit Bash or shell examples alongside PowerShell, or clarify that Azure CLI commands work on all platforms.
  • Add notes or links for Linux/macOS users about installation and usage of Azure CLI.
  • Ensure parity in step-by-step guides for both PowerShell and CLI, and avoid assuming PowerShell as the default automation tool.
  • Consider including screenshots or walkthroughs from Linux/macOS terminals where appropriate.
GitHub Create Pull Request
Service Bus Messaging Create a Service Bus authorization rule using an Azure template ...ng/service-bus-resource-manager-namespace-auth-rule.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented as the first deployment example, and the 'Next steps' section prioritizes PowerShell and Windows-centric tools (Service Bus Explorer) for resource management. While Azure CLI is included, the CLI example uses the deprecated 'azure' command rather than the current 'az' CLI, which is cross-platform. There are no Linux/macOS-specific instructions or parity in tool recommendations.
Recommendations
  • Present Azure CLI examples before PowerShell, using the current 'az' CLI syntax for cross-platform compatibility.
  • Include explicit instructions and examples for Linux/macOS users, such as shell commands and environment setup.
  • Highlight cross-platform management tools (e.g., Azure Portal, 'az' CLI) equally or before Windows-specific tools.
  • Add links to Linux/macOS documentation for Service Bus management.
  • Clarify that Service Bus Explorer is a Windows-only tool and suggest alternatives for other platforms.
GitHub Create Pull Request
Service Bus Messaging Create Service Bus topic subscription and rule using Azure template ...service-bus-resource-manager-namespace-topic-with-rule.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both PowerShell and Azure CLI examples for deploying the template, but PowerShell is presented first and referenced in multiple places, including the 'Next steps' section. There is a slight preference for Windows-centric tools and workflows, such as PowerShell and Service Bus Explorer (which is Windows-only), with less emphasis on Linux/macOS alternatives or parity.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform.
  • Explicitly mention that Azure CLI works on Linux/macOS/Windows, and provide links to installation guides for each OS.
  • Include management tool recommendations that work on Linux/macOS (e.g., mention cross-platform alternatives to Service Bus Explorer, or clarify its OS limitations).
  • Balance 'Next steps' by including links to CLI management guides alongside PowerShell guides.
  • Where possible, avoid referring to PowerShell as the default or primary method for resource management.
GitHub Create Pull Request
← Previous Page 2 of 4 Next →