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 1-25 of 377 flagged pages
Service Bus Messaging .NET multi-tier application using Azure Service Bus | Microsoft Docs ...ice-bus-dotnet-multi-tier-app-using-service-bus-queues.md
High Priority View Details →
Scanned: 2026-01-14 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 is heavily oriented toward Windows development environments, specifically Visual Studio and Azure Cloud Service roles (web/worker roles), with step-by-step instructions and screenshots for Windows tools. There are no examples or guidance for developing or running the sample on Linux or macOS, nor are alternative cross-platform .NET development tools (such as VS Code or CLI) mentioned. The use of the Azure Compute Emulator and reliance on Visual Studio features further restricts the tutorial to Windows users.
Recommendations
  • Add instructions for creating and running the sample using cross-platform .NET tools (e.g., .NET CLI, VS Code) on Linux/macOS.
  • Clarify which steps are Windows-specific and provide Linux/macOS alternatives where possible (e.g., environment variable setup, project creation).
  • Mention that Azure Cloud Service web/worker roles are primarily supported on Windows, but suggest alternatives for Linux users (such as Azure App Service, Azure Functions, or container-based deployment).
  • Provide guidance for running and debugging the application without the Azure Compute Emulator, which is Windows-only.
  • Include notes or links to cross-platform Service Bus samples.
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
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows and Visual Studio. All instructions for creating projects, managing NuGet packages, and authentication are given exclusively for Visual Studio, with no mention of Linux/macOS alternatives (such as VS Code, JetBrains Rider, or CLI workflows). NuGet installation commands are shown only for the Visual Studio Package Manager Console (PowerShell), and there are no examples using 'dotnet' CLI or cross-platform editors. The authentication flow assumes Visual Studio sign-in, which is not available on Linux/macOS. There is no guidance for Linux/macOS users on how to complete the quickstart.
Recommendations
  • Add instructions for using the .NET CLI (e.g., 'dotnet new console', 'dotnet add package ...') for project creation and NuGet package installation.
  • Include guidance for using cross-platform editors such as VS Code or JetBrains Rider.
  • Provide authentication instructions for passwordless access using Azure CLI or environment variables, which work on all platforms.
  • Explicitly mention that the code samples work on Linux/macOS and provide steps for those environments.
  • Reorder or parallelize instructions so Windows/Visual Studio steps are not always first or exclusive.
GitHub Create Pull Request
Service Bus Messaging .NET multi-tier application using Azure Service Bus | Microsoft Docs ...ice-bus-dotnet-multi-tier-app-using-service-bus-queues.md
High Priority View Details →
Scanned: 2026-01-13 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 is heavily oriented toward Windows development environments, specifically Visual Studio and Azure Cloud Service roles, with all instructions, screenshots, and tooling focused on Windows. There are no examples or guidance for Linux/macOS users, such as using .NET CLI, VS Code, or cross-platform deployment/testing workflows. Windows-specific tools like the Azure Compute Emulator are referenced exclusively, and all steps assume a Windows GUI workflow.
Recommendations
  • Add parallel instructions for Linux/macOS users, using .NET CLI and VS Code for project creation, package management, and debugging.
  • Include guidance on running and testing Azure Service Bus applications locally on Linux/macOS, such as using Docker containers or Azure Functions Core Tools.
  • Replace or supplement Visual Studio/Compute Emulator steps with cross-platform alternatives, e.g., Azure CLI, dotnet run, or VS Code debugging.
  • Clearly indicate which steps are Windows-only and provide equivalent Linux/macOS workflows where possible.
  • Add screenshots and code snippets for Linux/macOS environments.
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-11 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 auto forwarding in Azure Service Bus. However, PowerShell (a Windows-centric tool) is given a dedicated section with detailed examples, and is referenced before programming language SDKs. There are no Linux shell (bash) or cross-platform scripting examples outside of Azure CLI. The Azure portal instructions are platform-neutral, but the inclusion and emphasis on PowerShell and lack of parity for Linux-native tools or shell scripts indicates 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 fully cross-platform and highlight its use for Linux/macOS users.
  • Consider providing examples using REST API calls with curl, which are platform-agnostic and popular in Linux environments.
  • Reorder sections so that Azure CLI (cross-platform) appears before PowerShell, or combine them under a 'Command Line' heading with clear OS applicability.
  • Mention alternative Linux-native automation options (e.g., using Python scripts or Ansible modules) for Service Bus management.
GitHub Create Pull Request
Service Bus Messaging Authenticate an application to access Azure Service Bus entities ...cles/service-bus-messaging/authenticate-application.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Dotnet Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing authentication examples exclusively in .NET/C#, referencing Windows-centric tools (Azure PowerShell, Azure portal), and linking only to .NET sample code. There are no Linux-specific examples, nor are cross-platform SDKs (such as Python, Java, or Node.js) mentioned. The Azure portal and PowerShell are referenced before Azure CLI, and no Linux shell or CLI usage is shown for authentication flows.
Recommendations
  • Add authentication code samples for other SDKs (Python, Java, JavaScript) to demonstrate cross-platform usage.
  • Include Linux shell/CLI examples for role assignment and authentication, such as using Azure CLI on Linux.
  • Reference cross-platform tools and workflows (e.g., VS Code, Azure CLI) before or alongside Windows-specific tools like PowerShell.
  • Provide explicit guidance for Linux/macOS users, including screenshots or instructions for non-Windows environments.
  • Link to sample repositories for other languages and platforms, not just .NET.
GitHub Create Pull Request
Service Bus Messaging Azure messaging services - Service Manager to Resource Manager ...vice-bus-messaging/deprecate-service-bus-management.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 Tools Missing Linux Example Windows First
Summary
The documentation page focuses heavily on PowerShell commands for both deprecated and current Azure Service Manager/Resource Manager operations. All CLI examples are exclusively PowerShell, with no mention of cross-platform alternatives such as Azure CLI, Bash, or scripting for Linux/macOS. The 'Next steps' section only references PowerShell documentation for scripting, reinforcing a Windows-centric approach. There is no guidance or parity for Linux users or those using non-Windows shells.
Recommendations
  • Add equivalent Azure CLI commands for all PowerShell examples, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script examples for REST API calls, demonstrating how to use curl or similar tools.
  • Reference Azure CLI documentation alongside PowerShell documentation in the 'Next steps' section.
  • Explicitly state that PowerShell is available cross-platform, but also provide guidance for users who prefer native Linux/macOS tools.
  • Consider reordering or balancing examples so that Windows and Linux approaches are presented with equal prominence.
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-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 demonstrates a Windows bias primarily through the exclusive use of PowerShell for command-line examples and deployment instructions. All automation and scripting steps (such as deploying Resource Manager templates, setting access policies, and retrieving identities) are shown using PowerShell commands, with no equivalent Bash, Azure CLI, or Linux shell examples. Additionally, PowerShell is mentioned before Azure CLI in several places, and there are no explicit instructions or examples for Linux users, which may hinder parity and accessibility for cross-platform audiences.
Recommendations
  • Provide equivalent Azure CLI (bash) examples alongside PowerShell commands for all automation and scripting steps, especially for template deployment and key vault access policy management.
  • Clearly indicate which commands work cross-platform and which are Windows-specific, and recommend CLI usage for Linux/macOS users.
  • Add a section or tabbed examples for Linux/macOS users, demonstrating how to perform the same tasks using Bash and Azure CLI.
  • Review all references to PowerShell and ensure Azure CLI is presented with equal prominence, or in some cases, before PowerShell to avoid implicit Windows-first bias.
  • Include troubleshooting and setup notes relevant to Linux environments, such as authentication, file paths, and shell syntax differences.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus messaging - queues, topics, and subscriptions ...s-messaging/service-bus-queues-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 First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in the order and type of tooling examples provided. PowerShell is listed before the cross-platform Azure CLI in both the 'Create queues' and 'Create topics and subscriptions' sections, and no explicit Linux or Bash/Shell examples are given. There is also no mention of Linux-specific tools or workflows, and the PowerShell link points to a Windows-centric tool, potentially confusing for Linux users.
Recommendations
  • List Azure CLI before PowerShell in all sections, as CLI is cross-platform and more accessible to Linux users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Add Bash/Shell script examples or links where relevant, especially for queue/topic creation and management.
  • Clarify that PowerShell is available cross-platform, but provide CLI examples as the default.
  • Where possible, provide direct Linux usage notes or troubleshooting tips.
  • Ensure parity in documentation links: if PowerShell is linked, also link to Bash/CLI guides for Linux.
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-11 00:00
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, and ARM templates. However, the PowerShell section is extensive and detailed, and PowerShell is a Windows-centric tool. There is no mention of Linux-native scripting tools (such as Bash or shell scripts) or cross-platform alternatives for tasks shown in PowerShell. The ordering also places PowerShell before ARM templates, and the CLI examples do not explicitly mention Linux compatibility or shell usage. No Linux-specific guidance or parity is provided for scripting and automation beyond the CLI.
Recommendations
  • Add explicit Bash/shell script examples for each CLI scenario to demonstrate Linux usage.
  • Clarify that Azure CLI commands are cross-platform and provide sample usage in Bash (with environment variables, pipes, etc.).
  • Include notes or sections on using Azure CLI in Linux environments, including installation and authentication steps.
  • Reduce reliance on PowerShell for automation examples, or provide equivalent Bash/shell alternatives.
  • Consider reordering sections so that cross-platform tools (CLI, ARM templates) appear before Windows-specific tools (PowerShell).
  • Mention Linux support and parity in the introduction and tooling sections.
GitHub Create Pull Request
Service Bus Messaging Enable Azure Service Bus message sessions | Microsoft Docs ...icles/service-bus-messaging/enable-message-sessions.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 Tools Windows First
Summary
The documentation provides examples for enabling Azure Service Bus message sessions using the Azure portal, Azure CLI, Azure PowerShell, and ARM templates. While Azure CLI and ARM templates are cross-platform, the PowerShell section is Windows-centric, and it is presented before programming language samples. There are no Linux shell (bash) or scripting examples, and PowerShell is highlighted as a primary automation tool, which may imply Windows bias. The documentation does not mention Linux-specific tools or provide bash equivalents for PowerShell commands.
Recommendations
  • Add bash/sh scripting examples alongside PowerShell for parity, especially for Linux users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Reorder sections so that cross-platform tools (Azure CLI, ARM templates) appear before Windows-specific tools (PowerShell).
  • Include notes or links to Linux-specific guidance for Service Bus management.
  • Consider adding examples using REST API or SDKs directly from Linux environments.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus message sessions | Microsoft Docs ...ain/articles/service-bus-messaging/message-sessions.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 Windows bias by listing Windows-centric tools (Azure portal, PowerShell) before cross-platform alternatives (CLI, Resource Manager template) when describing how to enable message sessions. PowerShell is mentioned explicitly as a sample method, which is primarily a Windows tool, and there are no explicit Linux-specific instructions or examples (such as bash or shell commands). The ordering and emphasis suggest a preference for Windows environments.
Recommendations
  • List cross-platform tools (Azure CLI, Resource Manager templates) before or alongside Windows-specific tools (PowerShell, Azure portal) when describing how to enable message sessions.
  • Provide explicit Linux/macOS command-line examples (e.g., bash scripts using Azure CLI) for enabling message sessions.
  • Clarify that PowerShell is available cross-platform, but also offer bash or shell equivalents for Linux users.
  • Ensure that all instructions and samples are platform-neutral or include both Windows and Linux/macOS variants where relevant.
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
High Priority View Details →
Scanned: 2026-01-11 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 enabling dead lettering on Azure Service Bus, but the PowerShell section is extensive and detailed, reflecting a Windows-centric approach. PowerShell is a Windows-native tool, and its inclusion as a primary method (with full code samples and explanations) demonstrates a bias toward Windows users. There is no mention of Linux-native scripting alternatives (such as Bash), nor are cross-platform shell examples provided. The ordering of sections places PowerShell immediately after CLI, and before ARM templates and programming language samples, which may reinforce a Windows-first perspective.
Recommendations
  • Add Bash shell script examples for Linux/Mac users alongside PowerShell, especially for scripting Service Bus management with Azure CLI.
  • Clarify that Azure CLI is fully cross-platform and highlight its usage for both Windows and Linux environments.
  • Consider reordering the sections to present Azure CLI before PowerShell, or merge scripting examples under a 'Command-line' heading with clear OS applicability.
  • Explicitly mention that PowerShell Core is available on Linux/Mac, and provide usage notes or examples for those platforms if relevant.
  • Ensure that all code samples and instructions are clearly marked with their platform compatibility (Windows, Linux, Mac).
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus - suspend messaging entities .../main/articles/service-bus-messaging/entity-suspend.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 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-friendly tools such as Azure CLI, nor are cross-platform scripting options mentioned. The PowerShell example is given as the sole programmatic method, suggesting a Windows-first approach and omitting Linux parity.
Recommendations
  • Add equivalent Azure CLI examples for changing queue, topic, and subscription status, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that both Azure PowerShell and Azure CLI can be used, and provide links to both sets of documentation.
  • If possible, include REST API or SDK examples (e.g., Python, .NET, Java) to further enhance cross-platform accessibility.
  • Reorder or parallelize instructions so that Windows and Linux methods are presented together, avoiding implicit prioritization of Windows tools.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows and .NET, with all examples and configuration instructions tailored to the WindowsAzure.ServiceBus .NET framework library. There are no examples or guidance for Linux users, alternative platforms, or cross-platform .NET Core/.NET 5+ usage. The use of Windows-specific terminology and tools (e.g., Azure portal, .NET Framework, DataContractSerializer) further reinforces the Windows bias.
Recommendations
  • Add examples for using the Azure.Messaging.ServiceBus package with .NET Core/.NET 5+ on Linux and macOS.
  • Include instructions for configuring AMQP connections on Linux, such as environment variable usage or command-line examples.
  • Mention cross-platform compatibility explicitly and provide guidance for non-Windows environments.
  • Reference Linux-friendly tools (e.g., Azure CLI) for obtaining connection strings and managing Service Bus namespaces.
  • Clarify serialization and interoperability considerations for applications running on Linux or other platforms.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows and Visual Studio. All instructions for creating projects, managing dependencies, and running code are based on Visual Studio GUI workflows and PowerShell/NuGet Package Manager Console commands, which are Windows-centric. There are no examples or guidance for Linux or cross-platform development environments (e.g., VS Code, CLI, dotnet CLI, or Linux package managers). The documentation assumes the user is on Windows and using Visual Studio, omitting alternative workflows for Linux or macOS users.
Recommendations
  • Add instructions for using the dotnet CLI to create projects, add packages, and run applications. For example, show how to use 'dotnet new console', 'dotnet add package', and 'dotnet run'.
  • Include guidance for using VS Code or other cross-platform editors, not just Visual Studio.
  • Provide explicit steps for Linux and macOS users, including terminal commands for project setup and package installation.
  • Mention that the .NET SDK and Azure Service Bus libraries are cross-platform and can be used on Linux and macOS.
  • Replace or supplement PowerShell/NuGet Package Manager Console commands with Bash/zsh equivalents where appropriate.
  • Clarify that the code samples work on any OS with the .NET SDK installed, and provide troubleshooting tips for non-Windows environments.
GitHub Create Pull Request
Service Bus Messaging Integrate Azure Service Bus with Azure Private Link Service ...articles/service-bus-messaging/private-link-service.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 demonstrates a Windows bias by providing only Windows-based validation steps (creating a Windows VM), exclusively using Azure PowerShell for CLI examples, and omitting equivalent Linux or cross-platform instructions. The validation section references Windows-specific VM creation and command-line usage, while no Bash, Azure CLI, or Linux VM examples are given. The use of PowerShell and Windows tools is prioritized, and Linux alternatives are missing throughout.
Recommendations
  • Add Azure CLI (az) examples alongside or instead of PowerShell scripts for resource creation and management.
  • Include instructions for creating and validating with a Linux VM, referencing the official Azure Linux VM quickstart.
  • Show command-line validation steps using Bash or Linux shell (e.g., running nslookup from a Linux VM).
  • Explicitly mention that the steps are cross-platform where applicable, and clarify any OS-specific differences.
  • Balance screenshots and walkthroughs to include both Windows and Linux environments, or use generic Azure portal images.
  • Provide links to both Windows and Linux VM creation guides in the validation section.
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
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 is heavily oriented toward Windows development environments, specifically Visual Studio and PowerShell. All instructions for creating projects, installing NuGet packages, and authenticating use Visual Studio UI or PowerShell commands, with no mention of Linux alternatives (e.g., VS Code, CLI, or Bash). There are no examples or guidance for Linux users, and Windows tools are assumed throughout.
Recommendations
  • Add instructions for creating and managing .NET projects using cross-platform tools such as the .NET CLI (e.g., 'dotnet new console', 'dotnet add package').
  • Include steps for installing NuGet packages using the .NET CLI or editing the .csproj file directly, rather than only via Visual Studio or PowerShell.
  • Provide authentication guidance for Linux/Mac users, such as using Azure CLI for login and setting environment variables for DefaultAzureCredential.
  • Mention and show examples using VS Code or other cross-platform editors, not just Visual Studio.
  • Clarify that the code samples work on Linux and Mac, and provide any necessary platform-specific notes (e.g., how to run the console app in Bash).
  • Add a 'Developing on Linux/Mac' section or tab with equivalent steps and screenshots where relevant.
GitHub Create Pull Request
Service Bus Messaging .NET multi-tier application using Azure Service Bus | Microsoft Docs ...ice-bus-dotnet-multi-tier-app-using-service-bus-queues.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All development instructions assume the use of Visual Studio on Windows, with no mention of Linux or cross-platform alternatives. Steps such as 'Run as administrator', usage of the Azure Compute Emulator, and reliance on Visual Studio project templates are Windows-specific. There are no examples or guidance for developing, building, or running the application on Linux or macOS, nor are there CLI or VS Code alternatives provided. The documentation also references Windows tools (Compute Emulator, Visual Studio dialogs) exclusively and does not mention Linux equivalents or how to achieve parity.
Recommendations
  • Add instructions for developing and running the application on Linux and macOS, including using .NET CLI and VS Code.
  • Provide examples for setting environment variables on Linux/macOS (e.g., export in bash/zsh) as well as Windows.
  • Include steps for building and running the application using the .NET CLI (dotnet new, dotnet build, dotnet run) instead of only Visual Studio.
  • Mention cross-platform Azure development tools, such as Azure Functions Core Tools, Azure CLI, and alternatives to the Compute Emulator.
  • Clarify which steps are Windows-specific and offer Linux/macOS alternatives where possible.
  • Add screenshots or terminal output examples for Linux/macOS environments.
  • Reference documentation for .NET development on Linux/macOS and using Azure Service Bus from those platforms.
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-11 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 exhibits a bias towards Windows and .NET environments. Examples and code samples are exclusively in C#/.NET, with no equivalent samples for other languages or platforms. The PowerShell command is mentioned as a primary method for managing rules, but there is no mention of Linux shell equivalents or cross-platform scripting. The Azure CLI is referenced, but only briefly and without example code, while the PowerShell cmdlet is given equal prominence. There are no Linux-specific instructions, nor are there examples using Bash, Python, or other non-Windows tools. The page assumes familiarity with .NET libraries and Windows-centric workflows.
Recommendations
  • Add equivalent code samples in other languages, such as Python, Java, or JavaScript, to demonstrate cross-platform usage.
  • Provide explicit Bash/Azure CLI command examples for creating and managing Service Bus subscription filters, including full command-line workflows.
  • Include instructions or examples for Linux/macOS environments, such as using Azure CLI in Bash or shell scripts.
  • Balance the prominence of PowerShell and CLI by giving CLI examples equal detail and visibility, and referencing them before or alongside PowerShell.
  • Link to cross-platform SDK samples directly in relevant sections, not just in the 'Next steps'.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus - messaging exceptions | Microsoft Docs ...s-messaging/service-bus-messaging-exceptions-latest.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 displays Windows bias primarily in the troubleshooting section for SocketException, where only a PowerShell command (nslookup) is given with a Windows-style prompt and no Linux equivalent. There are no Bash or Linux shell examples, nor is there mention of Linux tools (e.g., dig, host) for DNS resolution. The page generally assumes a Windows environment when giving command-line instructions, and does not provide parity for Linux users.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., 'dig <mynamespace>.servicebus.windows.net' or 'host <mynamespace>.servicebus.windows.net') alongside PowerShell examples.
  • Use neutral prompts (e.g., '$' for shell, 'PS>' for PowerShell) and clarify which OS each example applies to.
  • Add troubleshooting steps relevant to Linux environments, such as checking /etc/resolv.conf or using systemd-resolve.
  • Explicitly mention that the instructions apply to both Windows and Linux, or provide OS-specific sections where needed.
  • Review other troubleshooting steps to ensure they do not assume Windows-only tools or patterns.
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
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 demonstrates a Windows bias by referencing PowerShell and CLI as primary automation tools, providing .NET sample code (which is most commonly used on Windows), and linking to samples that are Windows-centric (e.g., .NET/PowerShell). There are no explicit Linux shell (bash) or cross-platform language examples (such as Python), nor are Linux-specific tools or workflows mentioned. The ordering and phrasing ("PS/CLI") also places PowerShell before CLI, reinforcing Windows-first patterns. The absence of Linux or bash examples, and the lack of mention of Linux-specific considerations, further highlight the bias.
Recommendations
  • Add explicit bash (Linux shell) examples for all CLI operations, including setup, failover, and monitoring.
  • Include sample code in cross-platform languages such as Python or Java, and link to those samples in addition to .NET.
  • Reference Azure CLI commands directly in the main setup and management sections, not only as an alternative to PowerShell.
  • Ensure that all instructions and screenshots are applicable to both Windows and Linux environments, or clearly indicate any platform-specific differences.
  • Mention Linux-specific considerations for Service Bus management, such as authentication, environment setup, and automation.
  • Provide guidance or links for using REST API from Linux environments, including curl examples.
GitHub Create Pull Request
Service Bus Messaging Configure IP firewall rules for Azure Service Bus ...cles/service-bus-messaging/service-bus-ip-filtering.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 provides explicit instructions and command references for Azure PowerShell, but does not offer equivalent Linux shell (bash) or cross-platform CLI examples. The Azure CLI is mentioned, but no concrete CLI commands or examples are shown, while PowerShell commands are listed. Resource Manager template deployment instructions link to a PowerShell-specific page. This prioritizes Windows-centric tools and patterns, leaving Linux users with less guidance.
Recommendations
  • Add explicit Azure CLI command examples for managing IP firewall rules, including add, list, update, and remove operations.
  • Provide bash shell deployment instructions for Resource Manager templates, or link to cross-platform deployment guides.
  • Ensure that CLI examples are presented before or alongside PowerShell examples to avoid Windows-first ordering.
  • Where screenshots or UI instructions are given, clarify that the Azure portal is cross-platform and accessible from any OS.
  • Include a note or section for Linux/macOS users, highlighting parity and any OS-specific considerations.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus messages, payloads, and serialization | Microsoft Docs ...service-bus-messaging/service-bus-messages-payloads.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Dotnet Heavy
Summary
The documentation page demonstrates a bias toward Windows and .NET by focusing on .NET Framework and .NET Standard APIs, referencing Windows-centric serialization patterns, and omitting Linux-specific or cross-platform code examples. There are no PowerShell examples or explicit Windows tools, but the examples and explanations are centered on .NET, which is historically Windows-first, and there is no mention of Linux, Unix, or open-source alternatives. Java is mentioned briefly, but no examples are provided, and Python/JavaScript are referenced only in passing regarding casing conventions.
Recommendations
  • Add code examples for Linux-friendly languages such as Python and JavaScript using their respective Azure Service Bus SDKs.
  • Include explicit instructions or examples for using Service Bus from Linux environments, such as with curl, Python, or Java clients.
  • Balance .NET-specific content with parallel examples or explanations for Java, Python, and JavaScript SDKs.
  • Reference cross-platform tools and patterns (e.g., CLI, REST API usage from Linux shells) alongside .NET/Windows approaches.
  • Clarify that Service Bus is accessible from any platform and provide links to SDKs and documentation for Linux/macOS users.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus Subscription Rule SQL Filter syntax | Microsoft Docs ...vice-bus-messaging/service-bus-messaging-sql-filter.md
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 Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. It references .NET types and C# semantics (e.g., System.Char, System.Guid, C# operator binding) throughout the grammar and remarks, which are Windows-centric technologies. In the 'Next steps' section, the PowerShell cmdlet (New-AzServiceBusRule) is listed, and .NET is the first SDK mentioned, followed by Java and JavaScript. There is no explicit mention of Linux-specific tools, nor are Linux shell examples (e.g., Bash) provided for CLI usage. The examples and patterns lean toward Windows development environments.
Recommendations
  • Add explicit Bash or Linux shell examples for Azure CLI usage alongside any PowerShell examples.
  • Include references to cross-platform SDKs (such as Python) and their documentation in the 'Next steps' section.
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS users.
  • When referencing .NET types or C# semantics, provide equivalent information for other languages (e.g., Java, Python) where possible.
  • Ensure examples and instructions do not assume a Windows environment by default.
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-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 Windows bias primarily by providing only a Windows PowerShell example for DNS resolution (nslookup), without mentioning or showing equivalent Linux/macOS commands (e.g., dig, host, nslookup on Linux). The example is presented in a Windows-centric format (PS C:\>), and there is no guidance for users on non-Windows platforms. No Linux tools or patterns are mentioned, and troubleshooting steps are written from a Windows perspective.
Recommendations
  • Add equivalent Linux/macOS command-line examples for DNS resolution (e.g., dig <mynamespace>.servicebus.windows.net, host <mynamespace>.servicebus.windows.net, nslookup on Linux).
  • Present command examples for both Windows and Linux/macOS, ideally side-by-side or in tabs.
  • Explicitly mention that the troubleshooting steps apply to all platforms and provide platform-specific guidance where necessary.
  • Avoid using only Windows-specific command prompts (PS C:\>); use generic prompts or clarify platform context.
  • Include references to cross-platform tools and troubleshooting patterns, ensuring parity for Linux users.
GitHub Create Pull Request
← Previous Page 1 of 16 Next →