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 101-125 of 377 flagged pages
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-messaging-exceptions-latest.md ...s-messaging/service-bus-messaging-exceptions-latest.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the troubleshooting section for SocketException, where only a PowerShell (Windows) example is provided for DNS resolution. There are no equivalent Linux/macOS commands or examples (such as 'nslookup' or 'dig' in bash), and the PowerShell command is presented first and exclusively. The overall documentation does not mention Linux tools or patterns, nor does it provide cross-platform troubleshooting guidance.
Recommendations
  • Add equivalent Linux/macOS command-line examples (e.g., 'nslookup <mynamespace>.servicebus.windows.net' or 'dig <mynamespace>.servicebus.windows.net') alongside the PowerShell example.
  • Use platform-neutral language when suggesting troubleshooting steps (e.g., 'Open a terminal or command prompt and run...').
  • Explicitly mention that the troubleshooting steps apply to both Windows and Linux/macOS environments, and provide guidance for each where necessary.
  • Consider including a table or section that lists common troubleshooting commands for both Windows and Linux/macOS.
  • Review other sections for implicit Windows assumptions and ensure parity in examples and guidance for Linux users.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-auth-rule.md ...ng/service-bus-resource-manager-namespace-auth-rule.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. PowerShell is presented as the first deployment example, and the 'Next steps' section recommends PowerShell and Service Bus Explorer (a Windows-only tool) for management. Although Azure CLI is included, the CLI example uses the legacy 'azure' CLI (deprecated and not cross-platform), and there is no mention of Linux-specific patterns or tools. The documentation does not provide Linux shell examples or highlight cross-platform management options.
Recommendations
  • Present Azure CLI examples before PowerShell, using the current 'az' CLI syntax, which is cross-platform.
  • Include Linux shell (bash) examples for template deployment and resource management.
  • Mention and link to cross-platform management tools (e.g., Azure Portal, az CLI, REST API) in the 'Next steps' section.
  • Clarify that Service Bus Explorer is Windows-only and suggest alternatives for Linux/macOS users.
  • Ensure that all command-line examples are up-to-date and applicable to all supported platforms.
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-with-rule.md ...service-bus-resource-manager-namespace-topic-with-rule.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias. PowerShell is presented before Azure CLI in the deployment commands section, and PowerShell is referenced multiple times in both commands and next steps. The 'Manage Service Bus with PowerShell' article is listed before alternatives, and Service Bus Explorer (a Windows-only tool) is recommended without mention of cross-platform alternatives. While Azure CLI is included and is cross-platform, the ordering and tool recommendations favor Windows users.
Recommendations
  • Present Azure CLI commands before PowerShell, as CLI is cross-platform and preferred for Linux/Mac users.
  • Add explicit notes or examples for Linux/Mac users, such as shell commands or references to Bash scripting.
  • Mention cross-platform management tools (e.g., Azure Portal, az CLI, or third-party tools that run on Linux/Mac) alongside Service Bus Explorer.
  • Balance references to PowerShell with equivalent CLI or REST API documentation links.
  • Ensure that all management and deployment steps are demonstrated with cross-platform tools first, or at least equally.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-overview.md ...bus-messaging/service-bus-resource-manager-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell for deployment instructions, referencing Windows-centric tools and workflows, and omitting any examples or guidance for Linux users (such as Azure CLI or Bash). There are no mentions of cross-platform alternatives, and the step-by-step instructions assume a Windows/PowerShell environment throughout.
Recommendations
  • Add equivalent deployment instructions using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
  • Include Bash shell examples for template deployment, resource group creation, and parameter file usage.
  • Explicitly mention that Azure PowerShell is available on Linux and macOS, but also provide CLI alternatives for users who prefer native Linux tools.
  • Reorganize the documentation to present both PowerShell and CLI/Bash options side-by-side, or in separate sections, to ensure parity and inclusivity.
  • Reference official documentation for deploying ARM templates using Azure CLI and Bash, and link to those resources.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace.md ...us-messaging/service-bus-resource-manager-namespace.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. PowerShell is typically associated with Windows environments, and the instructions (such as 'Right-click the shell console') further reinforce Windows-centric usage patterns. Although alternative deployment methods (Azure CLI, REST API, portal) are briefly mentioned, no actual CLI or Bash code samples are provided, leaving Linux users without direct guidance.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell scripts, including deployment, verification, and cleanup steps.
  • Include Bash shell instructions and usage patterns, such as 'Ctrl+Shift+V to paste' instead of 'Right-click to paste', to better support Linux and macOS users.
  • Reorder or parallelize example sections so that PowerShell and CLI/Bash examples are presented together, rather than PowerShell first.
  • Explicitly mention that Azure Cloud Shell supports both PowerShell and Bash, and provide links or toggles for users to select their preferred shell.
  • Ensure that terminology and instructions are platform-neutral where possible (e.g., avoid Windows-specific actions like 'Right-click').
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/transport-layer-security-configure-minimum-version.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/transport-layer-security-configure-minimum-version.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments. It provides explicit PowerShell examples and references Windows-specific tools (ARMClient.exe) for authentication, without offering equivalent Linux-friendly alternatives. The order of examples often presents Windows-centric methods before cross-platform or Linux-native options. There is a lack of guidance for Linux users, such as using curl, bash, or platform-neutral authentication methods.
Recommendations
  • Provide Linux-specific examples for authentication and API queries, such as using Azure CLI (az account get-access-token) or curl for REST calls.
  • Mention cross-platform alternatives to ARMClient.exe, such as using Azure CLI or scripting with bash.
  • Include bash or shell script examples alongside PowerShell for parity.
  • Clarify which tools and commands are cross-platform, and note any platform limitations.
  • Reorder examples to present platform-neutral or cross-platform methods first, followed by platform-specific (Windows/PowerShell) instructions.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-sas.md ...main/articles/service-bus-messaging/service-bus-sas.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 mild Windows bias. When discussing management and key regeneration, Windows-centric tools (Azure PowerShell) are mentioned before cross-platform alternatives (Azure CLI), and PowerShell is referenced with a specific cmdlet example. No Linux-specific shell examples (e.g., Bash) or explicit parity for Linux environments are provided. The only code sample is in C#, a language most commonly associated with Windows, and no alternative code samples (e.g., Python, Java, Bash) are included. There are no explicit instructions or screenshots for Linux users, and the portal instructions are platform-agnostic but do not address Linux-specific considerations.
Recommendations
  • Present Azure CLI commands before or alongside PowerShell commands, as CLI is cross-platform and more commonly used on Linux.
  • Include Bash shell examples for generating SAS tokens, especially for the 'Generate a Shared Access Signature token' section.
  • Provide code samples in additional languages (Python, Java, JavaScript) that are popular on Linux.
  • Explicitly state that all management operations (including portal, CLI, and SDK usage) are supported on Linux and macOS, not just Windows.
  • Add screenshots or notes relevant to Linux environments where applicable (e.g., terminal usage, file paths).
  • Avoid language or tool ordering that implies Windows is the default or preferred platform.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-troubleshooting-guide.md ...ice-bus-messaging/service-bus-troubleshooting-guide.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits Windows bias in several areas: troubleshooting commands and tooling are presented with Windows/PowerShell examples first or exclusively, such as 'tnc' (Test-NetConnection) and 'psping.exe', with Linux alternatives mentioned only secondarily or not at all. Diagnostic and logging instructions focus on .NET and Windows-centric tools (EventSource, Application Insights), with little or no mention of Linux-native equivalents or cross-platform SDKs. Some troubleshooting steps and recommendations reference Windows-specific patterns and tools before their Linux counterparts, and several examples lack Linux parity.
Recommendations
  • Present Linux and Windows troubleshooting commands side-by-side, giving equal prominence (e.g., show 'telnet' and 'nc' before or alongside 'tnc').
  • Include Linux-native diagnostic tools and instructions (e.g., mention 'tcpdump', 'strace', 'journalctl', or 'systemd' logging for diagnostics).
  • Reference cross-platform SDKs and libraries (e.g., Python, Java, Node.js) in troubleshooting and authentication sections, not just .NET.
  • Provide examples for both PowerShell and Bash/shell scripts where applicable.
  • Mention Linux equivalents for Windows-only tools (e.g., alternatives to 'psping.exe' such as 'hping3', 'nmap', or 'ping' with options).
  • Clarify when a tool or step is Windows-specific and offer Linux/macOS alternatives.
  • Add links to Linux documentation and troubleshooting guides for Azure Service Bus.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/test-locally-with-service-bus-emulator.md ...us-messaging/test-locally-with-service-bus-emulator.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows-first bias in several areas. The step-by-step instructions for running the automated setup script are detailed for Windows (using PowerShell and WSL), while Linux and macOS users receive only a brief, generic instruction. Windows-specific tools (PowerShell, WSL) are mentioned and explained, whereas equivalent Linux/macOS terminal usage is not described. File path examples and environment variable notes are Windows-centric (e.g., double backslashes), and Linux/macOS patterns are not equally represented. The Docker Compose setup is platform-neutral, but the overall flow and examples prioritize Windows.
Recommendations
  • Provide detailed, step-by-step instructions for Linux and macOS users, including terminal commands and navigation.
  • Include Linux/macOS-specific examples for running the setup script and configuring Docker, with appropriate file path formats.
  • Balance the mention of Windows tools (PowerShell, WSL) by referencing standard Linux/macOS shells (bash, zsh, etc.) and their usage.
  • Add screenshots or terminal output examples from Linux/macOS environments to illustrate parity.
  • Clarify platform-specific differences in environment variable and file path handling, giving equal attention to Linux/macOS conventions.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-duplicate-detection.md ...es/service-bus-messaging/enable-duplicate-detection.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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, PowerShell (a Windows-centric tool) is given a dedicated section with detailed examples, and is mentioned before ARM templates and programming language samples. There are no Bash or Linux shell examples, and no mention of Linux-specific tools or patterns. The CLI examples are cross-platform, but the presence and prominence of PowerShell, without equivalent Linux shell scripting, indicates a Windows bias.
Recommendations
  • Add Bash or Linux shell scripting examples for common tasks, such as using Azure CLI in Bash scripts.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide explicit Bash usage examples (e.g., with environment variables, piping, etc.).
  • If PowerShell is shown, consider showing Bash equivalents side-by-side for parity.
  • Mention cross-platform compatibility of tools where relevant, and avoid implying PowerShell is the default or preferred automation tool.
  • Reorder sections so that cross-platform tools (Azure CLI) are presented before Windows-specific tools (PowerShell).
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/deprecate-service-bus-management.md ...vice-bus-messaging/deprecate-service-bus-management.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily focused on PowerShell commands for Azure Service Manager and Resource Manager, with no mention of Linux-native tools or cross-platform alternatives (such as Azure CLI, Bash, or REST API usage via curl). All code examples and migration guidance are provided exclusively in PowerShell, which is traditionally a Windows-centric tool, and there is no parity for Linux users. The 'Next steps' section also only references PowerShell documentation, reinforcing the Windows-first approach.
Recommendations
  • Add equivalent Azure CLI examples for each PowerShell command, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include REST API usage examples using curl or httpie, which are standard tools on Linux.
  • Explicitly mention that PowerShell Core is available cross-platform, but also provide guidance for users who prefer Bash or other shells.
  • In the 'Next steps' section, add links to Azure CLI documentation and REST API guides.
  • Consider reordering or balancing examples so that Linux-friendly tools are presented alongside or before Windows-centric ones.
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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through its 'Next steps' section, which lists 'AMQP in Service Bus for Windows Server' as a recommended resource, without mentioning Linux or cross-platform equivalents. There are no troubleshooting examples, commands, or references for Linux environments, and no mention of Linux-specific tools or patterns. The absence of Linux examples and resources suggests a Windows-centric approach.
Recommendations
  • Include troubleshooting steps and examples for both Windows and Linux environments.
  • Add references to Linux-compatible Service Bus tools and AMQP clients.
  • Provide links to documentation or guides for using Azure Service Bus with Linux (e.g., using Python, Java, or .NET Core on Linux).
  • Ensure parity in 'Next steps' by listing cross-platform or Linux-specific resources alongside Windows resources.
  • Explicitly mention that AMQP and Azure Service Bus are supported on multiple platforms, and provide guidance for each.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-messages-payloads.md ...service-bus-messaging/service-bus-messages-payloads.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Dotnet Heavy
Summary
The documentation page focuses heavily on .NET and .NET Framework APIs, which are most commonly used on Windows. Java is mentioned, but there are no examples or references to Linux-specific tools, patterns, or client libraries (such as Python, Node.js, or CLI usage on Linux). There are no Linux or cross-platform code samples, and the 'Get started' and 'How to use' links point to .NET guides, reinforcing a Windows/.NET-first perspective.
Recommendations
  • Add examples and references for Linux-friendly languages and SDKs, such as Python, Node.js, or Go.
  • Include code samples for Linux shell/CLI usage (e.g., using curl for HTTP APIs, or Azure CLI commands).
  • Balance .NET/.NET Framework references with equivalent instructions for Java, Python, and other cross-platform SDKs.
  • Provide links to 'Get started' guides for non-.NET languages and platforms.
  • Explicitly mention cross-platform compatibility and provide guidance for running on Linux environments.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-messaging-exceptions.md ...vice-bus-messaging/service-bus-messaging-exceptions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily by providing only a Windows PowerShell example for DNS resolution (nslookup), referencing Windows-style paths (e.g., 'PS C:\>'), and omitting equivalent Linux/macOS command-line examples (such as 'dig' or 'nslookup' in bash). The troubleshooting steps and examples are presented from a Windows perspective, with no mention of Linux tools or patterns, despite Service Bus being cross-platform.
Recommendations
  • Add Linux/macOS equivalents for command-line examples, such as showing 'dig <mynamespace>.servicebus.windows.net' or 'nslookup' in bash.
  • Use platform-neutral language when describing troubleshooting steps (e.g., 'Open a terminal and run ...').
  • Include notes or tables that show both Windows and Linux/macOS commands side-by-side for common tasks.
  • Avoid using Windows-specific paths or prompts (e.g., 'PS C:\>') unless also providing the Linux equivalent ('$').
  • Explicitly state that the guidance applies to all supported platforms, and link to cross-platform SDK usage documentation where relevant.
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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page references Windows-specific tools such as PowerShell (New-AzServiceBusRule) and .NET APIs before mentioning Linux-friendly alternatives. The CLI example is present, but PowerShell is listed in the 'Next steps' section alongside CLI, and .NET is the first SDK mentioned. There are no explicit Linux shell or scripting examples, and the documentation leans towards Windows-centric tooling and patterns.
Recommendations
  • Add explicit Linux/bash examples for managing Service Bus rules, such as using Azure CLI in bash scripts.
  • List cross-platform tools (e.g., Azure CLI) before Windows-specific tools (PowerShell) in 'Next steps' and throughout the documentation.
  • Include SDK examples for Python and other languages popular on Linux, and mention them alongside .NET, Java, and JavaScript.
  • Clarify that Azure CLI is cross-platform and provide usage examples for both Windows and Linux environments.
  • Avoid referencing Windows-only APIs (e.g., System.Char.IsLetter) without noting their equivalents or behavior in other platforms/languages.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace.md ...us-messaging/service-bus-resource-manager-namespace.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Service Bus namespaces, with no equivalent Azure CLI or bash examples. The instructions and code samples are tailored to PowerShell, which is traditionally associated with Windows environments, and there is no mention of Linux-specific tools or workflows. Alternative deployment methods (Azure CLI, REST API) are only referenced in a summary list at the end, not demonstrated.
Recommendations
  • Add equivalent Azure CLI examples alongside PowerShell scripts for all deployment, verification, and cleanup steps.
  • Include instructions for running commands in bash or Linux environments, clarifying cross-platform compatibility.
  • Present CLI and PowerShell examples in parallel, or allow users to select their preferred platform at the top of the article.
  • Explicitly mention that Azure Cloud Shell supports both PowerShell and bash, and link to documentation for both.
  • Ensure that Linux users are not required to adapt Windows-centric instructions (e.g., PowerShell-specific syntax) on their own.
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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
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 examples (e.g., Bash), nor is there mention of Linux-specific tools or patterns. The instructions for verifying contributor access reference the Azure portal, which is cross-platform, but the inclusion and parity of PowerShell examples suggest a Windows bias. There is no explicit missing Linux example, but the lack of Bash or Linux shell scripting is notable.
Recommendations
  • Add explicit Bash examples for Linux users, especially for scripting scenarios.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Consider listing Azure CLI examples before PowerShell to emphasize cross-platform support.
  • Mention that PowerShell Core is available on Linux, if PowerShell examples are retained.
  • Where possible, provide parity in examples for both 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-resource-manager-overview.md ...bus-messaging/service-bus-resource-manager-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based instructions and examples for deploying Azure Service Bus resources. There are no references to Linux-native tools, Bash, Azure CLI, or cross-platform alternatives. The workflow assumes the use of PowerShell, which is traditionally associated with Windows, and does not mention or prioritize Linux or macOS environments.
Recommendations
  • Add equivalent deployment instructions using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
  • Provide Bash shell examples for template deployment, including authentication and resource group management.
  • Explicitly mention that Azure PowerShell is available on Linux and macOS, and provide installation instructions for those platforms.
  • Reorganize the documentation to present both PowerShell and Azure CLI workflows side-by-side, or offer a platform-agnostic overview before diving into platform-specific details.
  • Include references to Linux tools and patterns (e.g., curl, jq) where appropriate, especially for template management and validation.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/authenticate-application.md ...cles/service-bus-messaging/authenticate-application.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias by prioritizing .NET and PowerShell examples, referencing Windows-centric tools and libraries, and omitting explicit Linux or cross-platform code samples. The authentication example uses C#/.NET libraries, and the next steps section lists PowerShell before CLI, with no mention of Bash or Linux-specific workflows. There are no Linux or cross-platform code samples or instructions, and the documentation assumes familiarity with Windows development environments.
Recommendations
  • Add equivalent code samples using Python, Java, or Node.js SDKs, which are commonly used on Linux.
  • Include explicit instructions and examples for authenticating and authorizing applications on Linux, such as using Azure CLI in Bash.
  • Present Azure CLI examples before or alongside PowerShell to avoid Windows-first ordering.
  • Reference cross-platform tools and libraries, and clarify which steps are OS-agnostic.
  • Provide links to Linux-specific documentation or troubleshooting guides for Service Bus authentication.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/entity-suspend.md .../main/articles/service-bus-messaging/entity-suspend.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides explicit instructions and code samples for changing Service Bus entity status using Azure PowerShell, a Windows-centric tool. There are no equivalent examples for Linux users (e.g., Azure CLI, Bash), and PowerShell is mentioned before any cross-platform alternatives. This creates a bias towards Windows users and leaves Linux users without clear guidance for command-line operations.
Recommendations
  • Add Azure CLI examples for suspending and reactivating Service Bus entities, as Azure CLI is cross-platform and widely used on Linux.
  • Present both PowerShell and CLI examples side-by-side, or provide CLI instructions before PowerShell to avoid Windows-first bias.
  • Explicitly mention that Azure PowerShell is available on Linux and macOS, or link to installation instructions for non-Windows platforms.
  • Include Bash script examples where appropriate, or reference REST API usage for maximum platform neutrality.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/configure-customer-managed-key.md ...ervice-bus-messaging/configure-customer-managed-key.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily through the exclusive use of PowerShell for command-line examples and deployment instructions. All imperative steps for deploying resources, setting access policies, and managing identities are shown using PowerShell commands, with no Bash, Azure CLI, or Linux shell equivalents provided. This may hinder Linux users or those who prefer cross-platform CLI tools. Additionally, PowerShell is mentioned before Azure CLI in several places, and there are no explicit Linux-specific instructions or examples.
Recommendations
  • Provide Azure CLI (bash/shell) equivalents for all PowerShell commands, especially for resource deployment and access policy management.
  • Include explicit instructions and examples for Linux/macOS environments, such as using Bash scripts or Azure CLI.
  • When listing tools or commands, present Azure CLI and PowerShell together, or mention Azure CLI first to emphasize cross-platform support.
  • Add notes or sections clarifying which commands work on Windows, Linux, and macOS, and highlight any platform-specific caveats.
  • Consider including sample scripts for both PowerShell and Bash in code tabs or expandable sections.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-auto-forward.md .../articles/service-bus-messaging/enable-auto-forward.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides examples for Azure portal, Azure CLI, Azure PowerShell, ARM templates, and programming languages (.NET, Java, Python, JavaScript). However, there is a notable emphasis on Azure PowerShell, which is primarily a Windows-centric tool. PowerShell examples are given equal prominence to CLI, and there is no mention of Bash, shell scripting, or Linux-native tools. The order of presentation places PowerShell before ARM templates and programming languages, which may reinforce a Windows-first perspective. There are no explicit Linux-specific instructions or examples, and the documentation does not clarify cross-platform compatibility for PowerShell or CLI commands.
Recommendations
  • Add explicit Bash or shell scripting examples alongside Azure CLI to demonstrate Linux usage.
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and recommend CLI for Linux users.
  • Note that Azure PowerShell is available on Linux and macOS via PowerShell Core, or provide installation instructions for non-Windows platforms.
  • Consider reordering sections to present CLI before PowerShell, or group them as 'cross-platform command-line tools' and 'Windows-specific tools'.
  • Add a table or note comparing tool/platform compatibility (CLI, PowerShell, portal, ARM templates) for Windows, Linux, and macOS.
  • Ensure parity in troubleshooting and environment setup instructions for both Windows and Linux users.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-dead-letter.md ...n/articles/service-bus-messaging/enable-dead-letter.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 dead lettering on Azure Service Bus queues and subscriptions. However, PowerShell is a Windows-centric tool and is presented with equal prominence as the cross-platform Azure CLI. There are no Linux shell (bash) or scripting examples, and no mention of Linux-specific tools or patterns. The ordering of sections places PowerShell immediately after CLI, which may reinforce a Windows-first mindset. No explicit Linux examples or parity notes are provided.
Recommendations
  • Add bash/sh scripting examples for Azure CLI commands to demonstrate usage on Linux and macOS.
  • Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows.
  • Consider reordering sections to present Azure CLI before PowerShell, or clarify platform applicability at the start of each section.
  • Include troubleshooting or environment setup notes for Linux users (e.g., installing Azure CLI on Ubuntu).
  • Add links to Linux-specific documentation or guides for Service Bus management.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-geo-dr.md ...n/articles/service-bus-messaging/service-bus-geo-dr.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by primarily referencing PowerShell (PS) and .NET samples, with no explicit Linux or Bash examples. The CLI is mentioned only in passing and never shown in detail. All code samples and GitHub links are .NET-focused, which is most commonly used on Windows. There is no mention of Linux-specific tools, patterns, or step-by-step instructions for Linux users. Windows-centric terminology (PowerShell, .NET) appears before or instead of cross-platform alternatives.
Recommendations
  • Add explicit Azure CLI (az) command examples for all management operations, including pairing, failover, and monitoring.
  • Provide Bash shell script examples for Linux users, especially for automation scenarios.
  • Include cross-platform sample code (e.g., Python, Java) in addition to .NET, and link to those in the Samples section.
  • Clarify that all operations can be performed on Linux, macOS, and Windows, and document any platform-specific caveats.
  • Mention and demonstrate usage of REST API via curl or httpie for Linux users.
  • Reorder examples so that CLI and REST API instructions appear before or alongside PowerShell and .NET examples.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/message-sessions.md ...ain/articles/service-bus-messaging/message-sessions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias primarily in the 'Samples' section, where enabling message sessions is described as possible via the Azure portal, PowerShell, CLI, Resource Manager template, and SDKs. PowerShell (a Windows-centric tool) is mentioned before CLI, and there is no explicit mention of Bash, Linux shell, or Linux-specific instructions. The ordering and tool selection suggest a Windows-first approach, and the lack of Linux-specific examples or terminology reinforces this bias.
Recommendations
  • Explicitly mention Bash or Linux shell commands alongside PowerShell and CLI when describing how to enable message sessions.
  • Reorder tooling references to avoid always listing Windows-centric tools first; consider grouping CLI and PowerShell together, or listing CLI before PowerShell.
  • Add examples or links for enabling message sessions using Linux-native tools or scripts.
  • Clarify that the Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux (Bash).
  • Where possible, include screenshots or instructions for Linux environments in addition to Windows.
GitHub Create Pull Request
← Previous Page 5 of 16 Next →