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 26-50 of 377 flagged pages
Service Bus Messaging Migrate Azure Service Bus namespaces - standard to premium ...-bus-messaging/service-bus-migrate-standard-premium.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by explicitly mentioning PowerShell as a migration tool alongside Azure CLI, but does not provide any Linux-specific instructions or examples. The CLI examples are generic, but the reference to PowerShell and the absence of Linux shell examples (e.g., bash) or explicit Linux guidance suggest a preference for Windows tooling. Additionally, there are no mentions of Linux-specific considerations, nor are any Linux command-line examples provided, which may leave Linux users without clear guidance.
Recommendations
  • Include explicit bash shell examples for environment variable setup and command execution, alongside PowerShell.
  • Clarify that Azure CLI commands work cross-platform and provide sample commands for both Windows (PowerShell) and Linux (bash).
  • Remove or balance references to PowerShell by mentioning Linux shell alternatives wherever CLI usage is described.
  • Add a section or note addressing any Linux-specific considerations for Service Bus migration, if applicable.
  • Ensure that screenshots and instructions for the Azure portal do not assume a Windows environment (e.g., file paths, UI differences).
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a subtle Windows bias. Windows-centric tools such as Visual Studio and IntelliJ are mentioned for authentication before Linux alternatives. The phrase 'servicebus.windows.net' is used in all code samples, reinforcing a Windows branding. While Azure CLI is used for most automation, references to Visual Studio (Windows-only or Windows-first experience) and IntelliJ (primarily Windows/Mac) are made before mentioning Linux-friendly alternatives. There are no explicit Linux shell or environment examples (e.g., Bash, zsh, Linux desktop authentication), and no mention of Linux-specific development environments or patterns. PowerShell is referenced in the metadata, suggesting its use, but not shown in the main content.
Recommendations
  • Include explicit examples for Linux environments, such as authentication via Bash or zsh, and mention Linux desktop tools (e.g., GNOME Keyring, KDE Wallet) where relevant.
  • List cross-platform tools (e.g., VS Code) before Windows-only tools (e.g., Visual Studio) when discussing authentication and development environments.
  • Add examples or notes for Linux users on how to authenticate locally (e.g., using Azure CLI in Bash, configuring environment variables in Linux shells).
  • Clarify that 'servicebus.windows.net' is a branding and not a Windows-only endpoint; reassure Linux users of full support.
  • If PowerShell is referenced, provide parity with Bash examples for all command-line instructions.
  • Mention Linux package managers (e.g., apt, yum) for installing SDKs and CLI tools where appropriate.
GitHub Create Pull Request
Service Bus Messaging Quickstart: Get started with Azure Service Bus queues (JavaScript) ...-bus-messaging/service-bus-nodejs-how-to-use-queues.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. It refers to 'Command Prompt' and 'Windows PowerShell' as environments for running commands and deploying Node.js applications, without mentioning Linux or macOS equivalents (e.g., Bash, Terminal). The instructions for installing Node.js and running npm commands are written generically, but the explicit references to Windows tools and lack of Linux/macOS-specific guidance or screenshots suggest a Windows-first approach. No Linux-specific examples, screenshots, or troubleshooting steps are provided.
Recommendations
  • Add explicit instructions and screenshots for Linux/macOS environments, such as using Bash or Terminal instead of Command Prompt.
  • When referencing command-line environments, use inclusive language (e.g., 'open a terminal or command prompt') instead of only 'Command Prompt'.
  • Provide links or notes for installing Node.js and Azure CLI on Linux/macOS, not just Windows.
  • Include troubleshooting steps relevant to Linux/macOS users, such as permission issues or environment variable setup.
  • Avoid mentioning Windows PowerShell exclusively; if scripting is needed, offer Bash alternatives.
  • Ensure screenshots and UI references are platform-neutral or provide variants for different OSes.
GitHub Create Pull Request
Service Bus Messaging Create Azure Service Bus namespace topic using a template ...saging/service-bus-resource-manager-namespace-topic.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 both deployment and management sections, and management guidance is focused on PowerShell and Service Bus Explorer (a Windows-only tool). There is no mention of Linux-specific management tools or parity in examples, and the CLI section is less emphasized than PowerShell. The 'Manage Service Bus' section links only to PowerShell and a Windows desktop tool, omitting Linux-native or cross-platform alternatives.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell, emphasizing CLI's cross-platform nature.
  • Include management examples using Azure CLI for Service Bus resources, not just PowerShell.
  • Mention and link to cross-platform tools for managing Service Bus (e.g., Azure Portal, CLI, REST API), not just Service Bus Explorer.
  • Explicitly state that both CLI and PowerShell commands work on Windows, Linux, and macOS, and provide usage notes for each.
  • Add a section or note on Linux/macOS usage, including installation and environment-specific considerations.
GitHub Create Pull Request
Service Bus Messaging Configure network service endpoints ...service-bus-messaging/service-bus-service-endpoints.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page provides examples and instructions for configuring network service endpoints for Azure Service Bus. While it mentions Azure CLI and Resource Manager templates (which are cross-platform), it gives explicit PowerShell command examples and links, but does not provide equivalent Linux shell (bash) or Azure CLI command examples. The PowerShell section is more detailed than the CLI section, and PowerShell is mentioned after CLI but with more command-level detail. There are no Linux-specific instructions or examples, and no mention of Linux tools or shell patterns. The deployment instructions reference a PowerShell deployment link, with no explicit bash or Linux shell alternative. This creates a subtle Windows bias by favoring PowerShell and omitting Linux-specific or bash examples.
Recommendations
  • Add explicit Azure CLI command examples for all operations currently shown with PowerShell (add, list, remove, update network rules).
  • Provide bash shell script examples for deploying Resource Manager templates, or link to cross-platform deployment guides.
  • Ensure that CLI and PowerShell instructions are equally detailed and presented in parallel, with CLI examples shown before or alongside PowerShell.
  • Include notes or sections for Linux users, clarifying that all operations can be performed on Linux/macOS using Azure CLI.
  • Reference documentation for deploying templates using bash/CLI, not just PowerShell.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
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. PowerShell is presented first in the deployment commands section, and the 'Next steps' section recommends PowerShell and Service Bus Explorer (a Windows-only GUI tool) for management. While Azure CLI is included and is cross-platform, the ordering and tool recommendations favor Windows users. There are no Linux-specific management examples or tool suggestions.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Include management instructions using Azure CLI in the 'Next steps' section, alongside or before PowerShell.
  • Mention and link to cross-platform alternatives to Service Bus Explorer, such as Azure Portal or open-source CLI tools.
  • Explicitly state that all deployment and management steps can be performed on Linux, macOS, and Windows, and clarify any platform-specific limitations.
  • Where PowerShell is referenced, also provide equivalent Bash or CLI commands for Linux/macOS users.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
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 cross-platform tools like Service Bus Explorer. There is no explicit mention of Linux-specific patterns or tools, and the CLI example is present but not emphasized as cross-platform. Windows-centric tools and patterns (PowerShell) are mentioned more frequently and with higher prominence than Linux equivalents.
Recommendations
  • Present Azure CLI examples before PowerShell, emphasizing its cross-platform nature.
  • Explicitly state that Azure CLI works on Linux, macOS, and Windows.
  • Add examples or references for Linux-specific deployment patterns (e.g., Bash scripts, automation via shell).
  • Balance the 'Next steps' section by listing cross-platform tools (CLI, Service Bus Explorer) before Windows-specific tools (PowerShell).
  • Where PowerShell is mentioned, also mention Bash or shell alternatives for Linux users.
  • Consider adding a short section on deploying from Linux environments, including screenshots or terminal output.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell management articles before mentioning Azure CLI, and by listing Service Bus Explorer (a Windows-only tool) as a primary management option. There are no explicit Linux or cross-platform command examples, and the management section prioritizes Windows-centric tools.
Recommendations
  • Add explicit Azure CLI examples for deploying and managing Service Bus resources, and reference them alongside or before PowerShell examples.
  • Include instructions and screenshots for managing resources using Azure CLI on Linux and macOS.
  • Mention cross-platform alternatives to Service Bus Explorer, or clarify its Windows-only nature and suggest equivalent tools or approaches for Linux users.
  • Ensure that management and cleanup steps include both portal and CLI options, with parity for Linux environments.
GitHub Create Pull Request
Service Bus Messaging Create an Azure Service Bus namespace using template ...us-messaging/service-bus-resource-manager-namespace.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 and instructions, which are most familiar to Windows users. There are no Linux-specific examples (such as Azure CLI or Bash), and PowerShell is presented as the default method for template deployment and resource management. Although alternative methods (Azure CLI, REST API, Portal) are mentioned, they are only referenced in a list at the end, without any example or parity in step-by-step instructions.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell scripts, including template deployment, verification, and cleanup.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both environments.
  • Reorder or parallelize the documentation so that Linux-friendly tools (Azure CLI, Bash) are presented alongside PowerShell, not only as alternatives.
  • Include notes or callouts for platform differences, such as command syntax or environment setup, to help Linux users follow along.
GitHub Create Pull Request
Service Bus Messaging Troubleshooting guide for Azure Service Bus | Microsoft Docs ...ice-bus-messaging/service-bus-troubleshooting-guide.md
High Priority View Details →
Scanned: 2026-01-11 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 exhibits Windows bias in several ways: Windows tools and commands (PowerShell, psping.exe, tnc) are mentioned first or exclusively, with Linux alternatives often presented as secondary or less detailed. Diagnostic and troubleshooting instructions favor Windows-native utilities, and examples reference Visual Studio and .NET-specific logging and tracing, with little or no parity for Linux or cross-platform development environments. Some troubleshooting steps lack Linux equivalents or provide only minimal Linux guidance.
Recommendations
  • Present Linux and Windows troubleshooting commands side-by-side, giving equal prominence to both (e.g., show telnet/nc examples before or alongside tnc/PowerShell).
  • Include Linux-native diagnostic tools (e.g., netcat, ss, lsof, tcpdump) in troubleshooting steps, with clear instructions.
  • Provide examples for cross-platform SDKs (Java, Python, Node.js) where .NET or Visual Studio is referenced.
  • Reference cross-platform logging and tracing solutions (OpenTelemetry, Jaeger, etc.) alongside Application Insights and .NET EventSource.
  • When mentioning downloadable tools (e.g., psping.exe), suggest Linux alternatives (e.g., hping, nping) and provide installation instructions.
  • Avoid assuming Visual Studio or Windows-only development environments; mention VS Code, JetBrains, or CLI-based workflows.
  • Ensure parity in troubleshooting steps for authentication, permissions, and connectivity for both Windows and Linux environments.
GitHub Create Pull Request
Service Bus Messaging Create Azure Service Bus resources using templates ...bus-messaging/service-bus-resource-manager-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 deployment instructions and examples, with no mention of Linux-native tools or cross-platform alternatives. All command-line steps use PowerShell cmdlets, and installation instructions reference Azure PowerShell, which is most commonly associated with Windows environments. There is no guidance for using Azure CLI, Bash, or other Linux-friendly approaches, nor is there any indication of how to perform these tasks on Linux or macOS systems.
Recommendations
  • Add equivalent deployment instructions using Azure CLI, which is cross-platform and widely used on Linux and macOS.
  • Provide Bash script 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.
  • Include a section comparing PowerShell and Azure CLI approaches, helping users choose the best tool for their environment.
  • Ensure that all examples and workflow steps are presented for both Windows and Linux users, or clarify platform requirements at the beginning of the article.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus access control with Shared Access Signatures ...main/articles/service-bus-messaging/service-bus-sas.md
High Priority View Details →
Scanned: 2026-01-11 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 exhibits mild Windows bias. When discussing key regeneration, PowerShell is mentioned before Azure CLI, and the PowerShell cmdlet is described in more detail. The only code sample for AMQP-level SAS token usage is in C#, a language strongly associated with Windows development. There are no explicit Linux shell or cross-platform code examples (e.g., Bash, Python, JavaScript) for generating SAS tokens or performing Service Bus operations. References to tools and SDKs are generally platform-agnostic, but the ordering and example choices favor Windows and Windows-centric patterns.
Recommendations
  • Present Azure CLI commands before or alongside PowerShell commands, emphasizing CLI as a cross-platform tool.
  • Add code samples for SAS token generation and AMQP-level usage in other languages (e.g., Python, JavaScript, Java) and/or using Bash scripts.
  • Include explicit Linux/macOS shell examples for common administrative tasks (e.g., using curl for HTTP requests, using Azure CLI for key management).
  • Clarify that all management operations can be performed from Linux/macOS as well as Windows, and provide links to cross-platform SDK documentation.
  • Where possible, use neutral language and ordering (e.g., 'Using Azure CLI or PowerShell' rather than 'PowerShell or Azure CLI').
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation presents 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 mentioned directly after CLI. There is no explicit mention of Linux shell equivalents (e.g., Bash scripts), nor is there guidance for Linux users regarding installation or usage. The use of PowerShell and references to Azure portal navigation patterns may reinforce a Windows-centric approach.
Recommendations
  • Prioritize Azure CLI examples, as it is cross-platform, and place them before PowerShell examples.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Add Bash script examples or clarify that the CLI commands can be run in Bash or other Linux shells.
  • Provide guidance for Linux users on installing and using Azure CLI.
  • If PowerShell is included, clarify that PowerShell Core is available cross-platform, or provide links to relevant installation instructions for non-Windows users.
  • Avoid assuming portal navigation patterns are familiar to all users; consider platform-neutral instructions.
GitHub Create Pull Request
Service Bus Messaging Tutorial: Update inventory using Azure portal and topics/subscriptions ...ng/service-bus-tutorial-topics-subscriptions-portal.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The tutorial exhibits Windows bias by exclusively referencing Windows tools and environments (Visual Studio, Command Prompt, PowerShell) and omitting explicit Linux or cross-platform instructions. All command-line examples assume Windows shells, and prerequisites only mention Visual Studio, with no alternatives for Linux users (e.g., VS Code, .NET CLI on Linux). There are no examples or notes for running the tutorial on Linux or macOS, nor are Linux-specific tools or shell commands provided.
Recommendations
  • Add instructions for Linux and macOS users, including how to install .NET SDK and run the sample using Bash/zsh.
  • Mention and provide examples using VS Code or JetBrains Rider as cross-platform IDEs.
  • Replace or supplement 'Command Prompt/PowerShell' references with 'terminal' and provide equivalent Bash commands.
  • Clarify that the .NET CLI and Azure portal steps are cross-platform, and explicitly state Linux/macOS compatibility.
  • Include troubleshooting notes or links for Linux-specific issues (e.g., file paths, permissions).
GitHub Create Pull Request
Service Bus Messaging Get started with Azure Service Bus topics (TypeScript) ...service-bus-typescript-how-to-use-topics-subscriptions.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily by referencing Windows-specific tools and patterns, such as recommending Windows PowerShell and linking to Windows deployment guides before mentioning cross-platform alternatives. There are no explicit Linux or macOS-specific instructions or examples, and the guidance for running commands is generic but leans toward Windows terminology (e.g., 'command prompt'). The inclusion of Windows PowerShell as a deployment method without a Linux equivalent, and the absence of explicit Linux shell or terminal instructions, further reinforce the bias.
Recommendations
  • Add explicit Linux and macOS instructions for all command-line steps, including using 'terminal' or 'shell' terminology alongside 'command prompt'.
  • Provide links to Linux/macOS deployment guides for Node.js applications, not just Windows PowerShell.
  • Include examples or notes for installing prerequisites (Node.js, TypeScript, Azure CLI) on Linux and macOS, with appropriate package manager commands (e.g., apt, yum, brew).
  • When referencing editors or tools, mention cross-platform options (e.g., Visual Studio Code, Vim, Sublime Text) and clarify that instructions apply to all operating systems.
  • Ensure troubleshooting and clean-up steps include Linux/macOS equivalents for command-line actions and resource management.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by presenting Windows setup instructions before Linux/macOS, relying heavily on PowerShell and WSL for the Windows workflow, and referencing Windows-specific tools and patterns (e.g., Docker Desktop for Windows, WSL configuration). The Linux/macOS instructions are less detailed and lack parity in step-by-step guidance. File path examples and environment variable notes are Windows-centric, with limited Linux-specific guidance.
Recommendations
  • Provide Linux/macOS setup instructions with equal detail and step-by-step guidance as Windows, including terminal commands and troubleshooting tips.
  • Include Linux/macOS-specific examples for file paths, environment variable settings, and script execution (e.g., bash commands, path conventions).
  • Present Linux/macOS instructions before or alongside Windows instructions to avoid 'windows_first' ordering.
  • Avoid assuming Docker Desktop is the only option; mention Docker Engine for Linux and provide links to Linux/macOS installation guides.
  • Add explicit examples for running scripts and configuring Docker on Linux/macOS, including permissions and common issues.
  • Clarify any differences in workflow or requirements between platforms, and ensure all screenshots and code snippets are cross-platform or clearly labeled.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing PowerShell and Windows-specific tools (ARMClient.exe) for authentication and querying, with no equivalent Linux or cross-platform examples. Windows/PowerShell approaches are presented before or instead of Linux alternatives, and there is a lack of guidance for Linux users on how to perform the same operations (e.g., acquiring a Bearer token, using curl or other native tools).
Recommendations
  • Provide Linux/macOS equivalents for authentication and querying, such as using Azure CLI (`az account get-access-token`) or curl for REST API calls.
  • Include examples using bash shell and native Linux tools for all steps currently shown with PowerShell or Windows executables.
  • Mention cross-platform tools first or alongside Windows-specific tools to ensure parity.
  • Clarify that ARMClient.exe is Windows-only and suggest alternatives for other platforms.
  • Ensure all code samples (especially for REST API calls and scripting) have both PowerShell and bash/curl versions.
GitHub Create Pull Request
Service Bus Messaging Enable auto forwarding for Azure Service Bus queues and subscriptions .../articles/service-bus-messaging/enable-auto-forward.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 managing Service Bus auto forwarding, but PowerShell (a Windows-centric tool) is given a dedicated section with detailed examples, and is mentioned before programming language SDKs. There is no mention of Linux-native scripting alternatives (e.g., Bash scripts), nor is there parity in showing Linux-specific patterns or tools. The CLI examples are cross-platform, but the prominence and detail of PowerShell coverage, and the lack of explicit Linux scripting guidance, indicate a moderate Windows bias.
Recommendations
  • Add explicit Bash or shell script examples for common operations, especially for updating and creating queues/subscriptions.
  • Clarify that Azure CLI is cross-platform and highlight its use on Linux/macOS as well as Windows.
  • Consider reordering sections so that CLI (cross-platform) examples appear before PowerShell (Windows-centric) examples.
  • Mention Linux-native automation tools (e.g., shell scripts, cron jobs) where appropriate.
  • Ensure parity in troubleshooting and tool recommendations for both Windows and Linux environments.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
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 Windows bias by listing Azure PowerShell usage as a primary method for managing Service Bus subscription filters, with no mention of Linux-specific tools or shell examples (e.g., Bash). All code samples are in C#/.NET, with no parity for other languages or platforms. The CLI example is present, but PowerShell is given equal prominence and is listed immediately after CLI, which is often associated with Windows environments. There are no Linux-specific instructions, nor are there examples using Bash, Python, or other cross-platform SDKs. The sample code and GitHub references are exclusively .NET/C#.
Recommendations
  • Add explicit Bash/Azure CLI examples for all operations shown in PowerShell, including creating rules and filters.
  • Include sample code in other languages (Python, Java, JavaScript) for creating and managing filters, not just .NET.
  • Clarify that Azure CLI works cross-platform and provide Linux/macOS usage notes where relevant.
  • Reorder sections to present CLI before PowerShell, and clarify platform compatibility.
  • Provide links to Linux/macOS setup guides for Azure Service Bus management.
  • Add troubleshooting notes for common Linux scenarios (e.g., authentication, environment variables).
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus - messaging exceptions (deprecated) | Microsoft Docs ...vice-bus-messaging/service-bus-messaging-exceptions.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates Windows bias by providing only a Windows PowerShell example for DNS resolution (nslookup), referencing Windows-specific command syntax and output, and omitting equivalent Linux/macOS commands (e.g., dig, host, nslookup on Linux). No Linux tools or patterns are mentioned, and troubleshooting steps assume a Windows environment. This may hinder Linux users from following the guidance effectively.
Recommendations
  • Include Linux/macOS equivalents for all command-line examples, such as 'dig <mynamespace>.servicebus.windows.net' or 'nslookup <mynamespace>.servicebus.windows.net' on Linux.
  • Provide sample outputs for both Windows and Linux/macOS commands.
  • Mention cross-platform troubleshooting steps and tools where applicable.
  • Avoid assuming the use of Windows-specific shells (e.g., PowerShell) and provide generic or platform-agnostic instructions.
  • Add notes or sections specifically addressing Linux/macOS environments, especially for networking and connectivity troubleshooting.
GitHub Create Pull Request
Service Bus Messaging Create an Azure Service Bus namespace using template ...us-messaging/service-bus-resource-manager-namespace.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively uses Azure PowerShell scripts for all deployment, verification, and cleanup steps, with no examples or instructions for Azure CLI, Bash, or Linux-native workflows. The step-by-step guidance assumes use of PowerShell and Windows-centric patterns, even though Azure Cloud Shell supports Bash and Azure CLI, which are more common on Linux and cross-platform environments. Alternative deployment methods (CLI, REST, portal) are only referenced as links, not shown inline or prioritized.
Recommendations
  • Provide equivalent Azure CLI (az) examples alongside PowerShell scripts for all steps, including deployment, verification, and cleanup.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select the shell.
  • Reorder or parallelize examples so that CLI/Bash instructions are presented before or alongside PowerShell, not only as links.
  • Add notes or code blocks for Linux/macOS users, clarifying any differences in environment or prerequisites.
  • Ensure that terminology and instructions do not assume a Windows/PowerShell context by default.
GitHub Create Pull Request
Service Bus Messaging Get started with Azure Service Bus topics (TypeScript) ...service-bus-typescript-how-to-use-topics-subscriptions.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. It references Windows-specific tools and patterns, such as PowerShell and Azure Website deployment, and mentions Windows deployment options before Linux alternatives. There are no explicit Linux or cross-platform terminal instructions, and the only command-line examples are generic (npm, az login) without platform-specific guidance. The page also links to Windows PowerShell-based deployment guides, but does not provide equivalent Linux shell or cross-platform deployment instructions.
Recommendations
  • Add explicit Linux/macOS terminal instructions alongside generic command prompt references (e.g., clarify that npm and az login work in bash/zsh/fish).
  • Provide links to Linux/macOS deployment guides for Node.js applications on Azure, not just Windows PowerShell-based guides.
  • When referencing deployment instructions, mention both Windows and Linux options equally, or provide a cross-platform guide.
  • Avoid mentioning Windows tools (e.g., PowerShell) without also mentioning Linux equivalents (e.g., Bash scripts, Azure CLI in Linux).
  • Where 'command prompt' is mentioned, clarify that any terminal (cmd, PowerShell, Bash, etc.) can be used.
GitHub Create Pull Request
Service Bus Messaging Tutorial: Update inventory using Azure portal and topics/subscriptions ...ng/service-bus-tutorial-topics-subscriptions-portal.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and workflows, such as Command Prompt and PowerShell, without mentioning Linux equivalents. The prerequisites specify Visual Studio (Windows-centric), and all command-line instructions assume a Windows environment. There are no examples or instructions for running the tutorial on Linux (e.g., using Bash, VS Code, or .NET CLI on Linux), nor any mention of cross-platform compatibility.
Recommendations
  • Add explicit instructions and examples for Linux users, including using Bash and .NET CLI on Linux.
  • Mention and provide guidance for cross-platform editors like Visual Studio Code.
  • Clarify that the .NET code and command-line steps can be executed on Linux and macOS, not just Windows.
  • Include screenshots or terminal output from Linux environments.
  • Avoid referencing only Windows tools (e.g., Command Prompt, PowerShell); provide parity with Linux equivalents.
  • List prerequisites for both Windows and Linux (e.g., .NET SDK installation instructions for Linux).
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
High Priority View Details →
Scanned: 2026-01-10 00:00
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 automation and scripting steps are shown using PowerShell, with no Bash, Linux shell, or cross-platform CLI examples provided. The instructions for key vault configuration, managed identity setup, and template deployment are PowerShell-centric, which may disadvantage users on Linux or macOS platforms. Additionally, PowerShell is mentioned before Azure CLI in several places, and there are no explicit Linux-specific notes or examples.
Recommendations
  • Provide equivalent Azure CLI (az) command examples for all PowerShell scripts, especially for resource deployment and access policy configuration.
  • Include Bash or shell script snippets where appropriate, and clarify cross-platform compatibility for all command-line instructions.
  • Add explicit notes or sections for Linux/macOS users, including any platform-specific prerequisites or differences.
  • Where PowerShell is referenced, ensure Azure CLI is mentioned at least equally, and consider presenting CLI examples first or side-by-side.
  • Review troubleshooting and advanced scenarios to ensure they do not assume a Windows/PowerShell environment.
GitHub Create Pull Request
Service Bus Messaging Enable duplicate message detection - Azure Service Bus ...es/service-bus-messaging/enable-duplicate-detection.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides detailed examples for both Azure CLI and Azure PowerShell, but the PowerShell section is extensive and uses Windows-centric tooling. PowerShell is a Windows-native tool (though now cross-platform), and its inclusion as a primary automation method can indicate Windows bias, especially since there is no mention of Linux shell equivalents (e.g., Bash scripts) or other Linux-native tools. The ordering also places PowerShell before ARM templates and after CLI, which is commonly used on Linux, but the PowerShell examples are more verbose and detailed. There are no explicit Bash or Linux shell script examples, nor references to Linux-specific patterns or tools.
Recommendations
  • Add Bash shell script examples for all CLI commands to demonstrate usage in Linux environments.
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Clarify that PowerShell Core is available on Linux and macOS, or provide links to installation instructions for non-Windows platforms.
  • Consider reordering sections to present CLI (cross-platform) before PowerShell, or provide parity in detail and explanation for CLI and PowerShell.
  • Add a note or section highlighting Linux-native automation options and best practices for Azure Service Bus management.
GitHub Create Pull Request
← Previous Page 2 of 16 Next →