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 76-100 of 377 flagged pages
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-10 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 in several ways. Windows instructions and tools (PowerShell, WSL) are presented first and in more detail, with explicit step-by-step guidance. The Linux and macOS section is brief and lacks equivalent command-line examples. Windows-specific tooling (WSL, PowerShell) is emphasized, and file path examples default to Windows syntax. There are no Linux/macOS terminal command examples for cloning the repo or running scripts, and Docker Desktop is referenced with a Windows-centric install link.
Recommendations
  • Provide Linux/macOS terminal command examples for cloning the repo and running the setup script (e.g., using bash/zsh).
  • Present Linux/macOS instructions before or alongside Windows instructions to avoid 'windows_first' bias.
  • Include Linux/macOS file path examples (e.g., /home/user/config/Config.json) in environment variable documentation.
  • Reference Docker Desktop installation for Linux/macOS, not just Windows.
  • Avoid requiring WSL for Windows users if native PowerShell/bash can be used, or clarify parity for Linux users.
  • Ensure all steps and troubleshooting guidance are equally detailed for Linux/macOS as for Windows.
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-10 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 API queries, with no Linux or cross-platform alternatives. PowerShell examples are given equal prominence to Azure CLI, but the authentication workflow for ARM API queries is Windows-centric. There is no mention of Linux equivalents or how to perform these steps on non-Windows platforms.
Recommendations
  • Provide Linux/macOS alternatives for ARMClient.exe, such as using curl, httpie, or Azure CLI to obtain bearer tokens and make API requests.
  • Include example commands for authentication and API queries using cross-platform tools (e.g., Azure CLI, curl, bash scripts).
  • Clarify that Azure CLI and PowerShell are both cross-platform, but show explicit Linux/macOS shell examples (e.g., bash) alongside PowerShell.
  • List cross-platform methods before or alongside Windows-specific tools to avoid Windows-first impression.
  • Add notes or links to documentation for Linux/macOS users on how to perform equivalent operations.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-message-sessions.md ...icles/service-bus-messaging/enable-message-sessions.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 Tools Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for enabling Service Bus sessions, but PowerShell (a Windows-centric tool) is given a dedicated section and detailed examples. There is no mention of Linux-specific tools or shell patterns (e.g., Bash), and PowerShell is presented as an equal alternative to CLI, despite being primarily used on Windows. The CLI examples are cross-platform, but the presence and prominence of PowerShell may signal a Windows bias. No Linux-specific examples or notes are provided.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and consider adding explicit Bash examples or notes for Linux users.
  • De-emphasize PowerShell as a primary automation tool, or provide equivalent Bash scripts for Linux users.
  • Add a section or note on using Service Bus with Linux-native tools or environments.
  • Ensure that examples and instructions do not assume a Windows environment by default.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions and examples for changing Azure Service Bus entity status using the Azure portal and Azure PowerShell, but does not include equivalent examples for Linux users (e.g., Azure CLI, Bash). PowerShell is a Windows-centric tool, and its usage is presented exclusively for command-line operations, which may disadvantage users on Linux or macOS platforms.
Recommendations
  • Add Azure CLI examples for suspending and reactivating queues, topics, and subscriptions, as Azure CLI is cross-platform and widely used on Linux.
  • Present both PowerShell and CLI examples side-by-side, or at least mention CLI before PowerShell to avoid Windows-first bias.
  • Explicitly state that PowerShell examples are for Windows users and provide guidance for Linux/macOS users.
  • Include Bash script snippets where appropriate to demonstrate cross-platform usage.
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-09 00:34
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 environments. It references .NET and .NET Framework APIs and object models extensively, with no mention of Linux-specific tools, patterns, or examples. Java is mentioned briefly, but most code and serialization examples focus on .NET. There are no Linux or cross-platform command-line examples, nor references to Linux-native tools or workflows.
Recommendations
  • Add code examples for Java, Python, and JavaScript clients, especially for serialization and message handling.
  • Include references to Linux command-line tools (e.g., curl for HTTP messaging) and workflows.
  • Provide parity in documentation for Linux and cross-platform environments, such as instructions for using Service Bus from Linux shells.
  • Mention open-source libraries and SDKs that are popular in Linux environments.
  • Ensure that .NET-specific features are clearly marked as such, and alternatives for other platforms are provided.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-queue.md ...saging/service-bus-resource-manager-namespace-queue.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 a Windows bias by referencing PowerShell management first in the 'Next steps' section, mentioning Service Bus Explorer (a Windows-only tool), and omitting explicit Linux/macOS CLI examples or parity in resource management instructions. Although the Azure portal and ARM templates are cross-platform, the management recommendations and tooling references prioritize Windows-centric solutions.
Recommendations
  • Add explicit Azure CLI examples for resource management and deployment, highlighting usage on Linux/macOS.
  • Mention and provide instructions for cross-platform tools (e.g., Azure CLI, VS Code extensions) alongside or before Windows-specific tools like PowerShell and Service Bus Explorer.
  • Reorder 'Next steps' to present cross-platform options first, or present Windows and Linux/macOS alternatives side-by-side.
  • Include links to documentation for managing Service Bus resources using Azure CLI and REST API, emphasizing platform neutrality.
  • Clarify which tools are Windows-only and suggest alternatives for other platforms.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-queues-topics-subscriptions.md ...s-messaging/service-bus-queues-topics-subscriptions.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 Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. When listing options for creating queues and topics/subscriptions, PowerShell is mentioned explicitly and before the CLI, which is more cross-platform. There are direct links to PowerShell instructions, but no mention of Bash or Linux-specific tools. No Linux shell examples or references to Linux-native patterns are provided, and the documentation does not clarify that the CLI is cross-platform or provide parity in example coverage for Linux users.
Recommendations
  • Explicitly mention that the Azure CLI is cross-platform and suitable for Linux, macOS, and Windows.
  • Provide Bash/Linux shell examples alongside PowerShell examples, or at least link to Linux-specific quickstarts.
  • When listing creation options, avoid listing PowerShell before CLI, or alternate the order to avoid implicit prioritization.
  • Include references to Linux-native automation tools (e.g., bash scripts, cron jobs) where relevant.
  • Add a note clarifying that all features are available on Linux and macOS, not just Windows.
  • Ensure parity in documentation links: if PowerShell is linked, also link to Bash/CLI equivalents.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-tutorial-topics-subscriptions-portal.md ...ng/service-bus-tutorial-topics-subscriptions-portal.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 Missing Linux Example
Summary
The tutorial exhibits Windows bias by referencing Windows-specific tools (Visual Studio, Command Prompt, PowerShell) as the default environment for running commands and building code. There are no explicit instructions or examples for Linux or macOS users, such as using Bash, alternative IDEs, or platform-agnostic command-line patterns. The prerequisites and step-by-step instructions assume a Windows environment, and PowerShell is mentioned as a primary shell. No Linux-specific commands, screenshots, or troubleshooting notes are provided.
Recommendations
  • Add instructions for Linux and macOS users, including using Bash or other shells for command-line steps.
  • Mention cross-platform IDEs such as VS Code, and clarify that .NET Core and Azure CLI work on Linux/macOS.
  • Provide Linux/macOS equivalent commands and folder navigation examples (e.g., use 'cd' instead of Windows path separators).
  • Include screenshots or notes for Linux/macOS environments where relevant.
  • Avoid mentioning Windows tools (Command Prompt, PowerShell) exclusively; use neutral language like 'terminal' or 'command line'.
  • Explicitly state cross-platform compatibility in the prerequisites and throughout the tutorial.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-typescript-how-to-use-topics-subscriptions.md ...service-bus-typescript-how-to-use-topics-subscriptions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. It references Windows-specific tools and workflows, such as PowerShell and Azure Website deployment instructions, and mentions Windows tools before Linux equivalents. There are no explicit Linux or cross-platform command-line examples (e.g., bash, zsh), and the instructions for running commands use generic 'command prompt' language, which may be interpreted as Windows-centric. The page lacks explicit Linux terminal instructions or screenshots, and does not mention Linux-specific package managers or editors.
Recommendations
  • Add explicit Linux/macOS terminal instructions alongside 'command prompt', e.g., 'open a terminal (Windows: Command Prompt/PowerShell, Linux/macOS: Terminal)'.
  • Include Linux/macOS deployment links and examples, such as instructions for deploying Node.js apps to Azure from Linux.
  • Replace or supplement references to Windows PowerShell with bash/zsh equivalents where appropriate.
  • Add screenshots or notes showing the experience on Linux/macOS, especially for command-line steps.
  • Mention cross-platform editors (e.g., VS Code, Vim, Sublime) equally, not just Visual Studio Code.
  • Clarify that npm and Node.js are cross-platform, and provide troubleshooting tips for Linux/macOS users.
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-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 bias by primarily referencing Windows-centric tools and examples. Azure PowerShell is mentioned before Azure CLI, and all code samples are in .NET/C#, which is most commonly used on Windows. There are no Linux-specific instructions, examples, or mentions of Linux authentication patterns, nor are cross-platform SDKs or code samples (such as Python or Node.js) provided. The workflow assumes use of the Azure portal (which is web-based but often referenced in Windows contexts) and omits command-line examples that would be more familiar to Linux users.
Recommendations
  • Add Linux-specific instructions or notes, such as using Azure CLI on Linux or authenticating from Linux-based environments.
  • Provide code samples in cross-platform languages (e.g., Python, Node.js) alongside .NET/C#.
  • Include explicit Azure CLI examples for authentication and role assignment, and present them before or alongside PowerShell examples.
  • Mention Linux-friendly tools and patterns, such as environment variables for secrets, managed identities in Linux containers, and using the CLI in bash scripts.
  • Clarify that the Azure portal and SDKs are cross-platform, and provide guidance for Linux users where workflows differ.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively referencing PowerShell cmdlets for both deprecated and current management operations. There are no examples or mentions of Linux-native tools, such as Azure CLI, Bash, or scripting alternatives. The PowerShell focus implicitly prioritizes Windows users and omits guidance for Linux or cross-platform users. REST API mappings are provided, but all command-line examples and tool references are PowerShell-centric.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets, showing how to perform the same operations on Linux/macOS.
  • Include Bash scripting examples for REST API calls, using curl or httpie, to demonstrate platform-neutral automation.
  • Explicitly mention cross-platform options (e.g., Azure CLI, SDKs in Python/Node.js) in the 'Next steps' section alongside PowerShell.
  • Reorder sections or provide parallel examples so that Linux-friendly tools are presented before or alongside Windows/PowerShell options.
  • Clarify that PowerShell is available on Linux/macOS, but also highlight native Linux workflows and tools.
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-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 a bias toward Windows environments by providing only PowerShell-based command-line examples for key operations such as deploying Resource Manager templates, managing Key Vault access policies, and retrieving managed identity information. There are no Bash or Azure CLI examples for these tasks, and PowerShell is referenced as the primary or sole method for several critical steps. This approach may disadvantage users working on Linux or macOS systems, where PowerShell is less commonly used and Bash/Azure CLI are preferred.
Recommendations
  • Add equivalent Azure CLI (az) and Bash examples for all PowerShell commands, especially for template deployments and Key Vault access policy management.
  • Where PowerShell is mentioned as a requirement, clarify that Azure CLI and Bash are fully supported and provide links to relevant CLI documentation.
  • Reorder sections so that cross-platform tools (Azure CLI, Bash) are presented before or alongside PowerShell, rather than after.
  • Explicitly state platform compatibility for each example, helping users on Linux/macOS to follow along without confusion.
  • Include troubleshooting notes for common issues encountered on non-Windows platforms (e.g., authentication, environment setup).
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-09 00:34
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. However, PowerShell (a Windows-centric tool) is given a dedicated section with detailed examples, while no equivalent is provided for Linux-native scripting (e.g., Bash, shell scripts) or other Linux-specific tools. The Azure portal section is platform-neutral, but the presence of PowerShell examples and absence of Linux shell scripting or references to Linux package managers/tools indicates a mild Windows bias. Additionally, PowerShell is presented before programming language SDKs, which may reinforce a Windows-first perspective.
Recommendations
  • Add explicit Bash/shell script examples for Azure CLI commands to demonstrate Linux usage.
  • Clarify that Azure CLI works cross-platform and provide sample commands for both Windows (cmd/PowerShell) and Linux (Bash).
  • Consider including Linux-specific automation examples, such as using shell scripts or integrating with cron.
  • Reorder sections so that platform-neutral tools (Azure CLI, ARM templates) appear before PowerShell.
  • Mention that PowerShell Core is available cross-platform, but highlight Linux usage where relevant.
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-09 00:34
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 PowerShell examples for enabling dead lettering in Azure Service Bus. However, the PowerShell section is extensive and detailed, reflecting a bias toward Windows tooling. PowerShell is a Windows-centric tool, and its inclusion as a primary method (with full code samples and explanations) may suggest a Windows-first approach. There are no Linux-specific shell examples (e.g., Bash scripts), nor is there mention of Linux-native tools or patterns. The CLI examples are cross-platform, but PowerShell is given equal or greater prominence, which can be interpreted as a Windows bias.
Recommendations
  • Add explicit Bash or shell script examples for Linux users, especially for automation tasks.
  • Clarify that Azure CLI commands work cross-platform and highlight their use on Linux and macOS.
  • Consider reordering sections so that cross-platform tools (Azure CLI, ARM templates) are presented before Windows-centric tools (PowerShell).
  • Mention Linux and macOS compatibility in the introduction and in relevant sections.
  • If PowerShell is included, note that PowerShell Core is available on Linux/macOS, and provide guidance or examples for those platforms.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides detailed examples for Azure PowerShell, which is primarily a Windows tool, and includes it as a main method for enabling duplicate message detection. PowerShell examples are presented with equal prominence to Azure CLI, but there is no mention of Linux-native alternatives for scripting or automation (such as Bash or shell scripts). The use of PowerShell and its cmdlets may implicitly favor Windows users. There is no explicit guidance for Linux users on how to perform these tasks outside of the CLI, and PowerShell is listed before ARM templates, which are platform-neutral.
Recommendations
  • Add explicit Bash or shell script examples for Linux users alongside PowerShell examples.
  • Clarify that Azure CLI is cross-platform and can be used on both Windows and Linux, and consider listing CLI before PowerShell.
  • Mention that PowerShell Core is available on Linux, or provide links/guidance for Linux users who wish to use PowerShell.
  • Ensure that all automation examples (especially scripting) have Linux-native equivalents or clear cross-platform instructions.
  • Review ordering of sections so that platform-neutral or cross-platform tools (CLI, ARM templates) are presented before platform-specific tools (PowerShell).
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-09 00:34
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 by mentioning PowerShell and Azure portal as primary methods for enabling message sessions, with no explicit mention of Linux-specific tools or command-line examples (e.g., Bash, Azure CLI on Linux). PowerShell is referenced before CLI, and there are no Linux shell or cross-platform command examples for queue creation or session management. The samples section lists .NET first, which is commonly associated with Windows, and does not provide parity in example ordering or highlight Linux usage patterns.
Recommendations
  • Add explicit Bash/Azure CLI examples for enabling message sessions, demonstrating usage on Linux and macOS.
  • Reorder or balance the mention of tools so that cross-platform options (Azure CLI, ARM templates) are listed before or alongside PowerShell and Azure portal.
  • Include a note or section clarifying that all features and APIs are available and supported on Linux, and provide guidance for Linux users.
  • Add links to Linux-specific documentation or tutorials for Service Bus management and development.
  • Ensure sample code ordering is rotated or randomized, or explicitly state that all languages/platforms are supported equally.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-amqp-dotnet.md ...icles/service-bus-messaging/service-bus-amqp-dotnet.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 the legacy WindowsAzure.ServiceBus .NET Framework library, which is inherently Windows-centric. All examples and configuration details assume usage of Windows tools and environments (e.g., Azure portal, .NET Framework, DataContractSerializer), with no mention of Linux or cross-platform usage patterns. There are no Linux-specific instructions, nor examples for using the library on Linux or with alternative tools. The documentation does not address how to use the legacy library in non-Windows environments, nor does it mention Mono or .NET Core/5+/6+ compatibility.
Recommendations
  • Add explicit guidance for using the library on Linux, including any prerequisites (e.g., Mono, .NET Core compatibility, limitations).
  • Provide Linux-specific examples for connection string configuration, environment setup, and running sample code.
  • Mention any cross-platform alternatives or migration paths, especially since the legacy library is Windows-focused.
  • Clarify whether the legacy library can be used on Linux and, if so, document any caveats or additional steps required.
  • Include references to Linux tools (such as CLI usage, environment variables, etc.) where appropriate.
  • Ensure parity in documentation by presenting Linux and Windows instructions side-by-side when relevant.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-dotnet-how-to-use-topics-subscriptions.md ...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-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 is heavily oriented toward Windows development environments, specifically Visual Studio. All instructions for project creation, package management, and authentication are given using Visual Studio UI and PowerShell commands, with no mention of Linux or cross-platform alternatives (e.g., VS Code, CLI, dotnet CLI, or Bash). There are no examples or guidance for Linux users, and the use of Windows-specific tools and terminology is pervasive throughout the page.
Recommendations
  • Add instructions for creating and managing .NET projects using the dotnet CLI, which works on Linux, macOS, and Windows.
  • Include NuGet package installation examples using 'dotnet add package' and 'nuget' CLI, not just PowerShell.
  • Provide guidance for using VS Code or other cross-platform editors, not just Visual Studio.
  • Clarify that the code samples work on Linux and macOS as well as Windows, and provide any necessary platform-specific notes (e.g., authentication via DefaultAzureCredential).
  • Add screenshots or instructions for Linux environments where relevant (e.g., terminal usage, file navigation).
  • Explicitly mention that the quickstart is cross-platform and highlight any steps that differ for Linux/macOS users.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-filter-examples.md ...s/service-bus-messaging/service-bus-filter-examples.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 bias by listing Azure PowerShell as a primary method for managing Service Bus subscription filters, with no mention of Linux-specific tools or shell examples. The CLI section is present but not emphasized, and all code samples are in C#/.NET, which is more common on Windows. There are no Bash, shell, or cross-platform scripting examples, nor any explicit Linux usage patterns. The documentation references Windows-centric tools (PowerShell, .NET) before or instead of Linux equivalents.
Recommendations
  • Add explicit Bash or shell examples for using Azure CLI to create and manage Service Bus subscription filters.
  • Include cross-platform scripting examples (e.g., Python, JavaScript) for filter creation and management.
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows.
  • Provide links to Linux-specific documentation or tutorials for Service Bus management.
  • Balance the order of presentation so CLI examples appear before PowerShell, emphasizing platform neutrality.
  • Add notes or sections on using Service Bus features from Linux environments, including automation and scripting.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/private-link-service.md ...articles/service-bus-messaging/private-link-service.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 bias by providing only Windows-centric examples and instructions. The only CLI example uses Azure PowerShell, which is primarily used on Windows, with no equivalent Azure CLI or Bash example for Linux/macOS users. The validation steps exclusively reference creating and using a Windows VM, omitting instructions for Linux VMs. The command-line validation uses nslookup but is shown only in the context of a Windows VM. There is no mention of Linux tools, patterns, or parity in the walkthroughs.
Recommendations
  • Add equivalent Azure CLI (az) examples alongside Azure PowerShell for creating resources and private endpoints.
  • Include instructions for creating and validating with a Linux VM, referencing the appropriate Azure documentation.
  • Show command-line validation steps (e.g., nslookup, dig) for both Windows and Linux environments.
  • Explicitly mention cross-platform compatibility and provide guidance for users on macOS and Linux.
  • Balance screenshots and walkthroughs by including Linux portal or SSH examples where relevant.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-dotnet-get-started-with-queues.md ...essaging/service-bus-dotnet-get-started-with-queues.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 development environments, specifically Visual Studio. All instructions for project creation, package installation, and authentication are given using Visual Studio UI and PowerShell/NuGet Package Manager Console, with no mention of Linux or cross-platform alternatives (such as VS Code, CLI, or dotnet CLI commands). There are no examples or guidance for Linux users, and Windows-specific tools and patterns are assumed throughout.
Recommendations
  • Add instructions for creating and running .NET console applications using the dotnet CLI, which works on Linux, macOS, and Windows.
  • Include package installation steps using 'dotnet add package' instead of (or in addition to) NuGet Package Manager Console/PowerShell.
  • Mention and provide examples for using VS Code or other cross-platform editors, not just Visual Studio.
  • Clarify that the .NET SDK and Azure Service Bus libraries are cross-platform and can be used on Linux and macOS.
  • Add troubleshooting notes for Linux users (e.g., port requirements, credential management differences).
  • Where screenshots or UI steps are given for Visual Studio, provide equivalent CLI commands or VS Code instructions for non-Windows users.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-dotnet-multi-tier-app-using-service-bus-queues.md ...ice-bus-dotnet-multi-tier-app-using-service-bus-queues.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio and Azure Cloud Service roles, with all examples and instructions assuming Windows usage. There is no mention of Linux or cross-platform development tools, and steps such as running Visual Studio as administrator, using the Azure Compute Emulator, and UI screenshots are Windows-specific. No Linux equivalents or alternatives (such as VS Code, CLI, or Docker) are provided, nor is there any guidance for running or deploying the application on Linux or macOS.
Recommendations
  • Add instructions and examples for developing and running the application on Linux, including using .NET CLI, VS Code, and cross-platform tools.
  • Provide guidance for deploying the application using Docker containers or Azure App Service for Linux.
  • Include Linux/macOS equivalents for environment variable setup and authentication steps.
  • Replace or supplement Visual Studio-specific steps with .NET CLI commands and VS Code workflows.
  • Mention and show how to use the Azure Service Bus SDK in Linux environments, including any platform-specific considerations.
  • Add screenshots or terminal output examples relevant to Linux/macOS users.
  • Clarify which steps are Windows-only and provide alternatives for other platforms.
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-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 Windows bias by referencing PowerShell (PS) and CLI as primary automation methods, linking to .NET sample code (which is Windows-centric), and omitting explicit Linux/bash examples or guidance. The use of PowerShell is mentioned before CLI, and all code samples are .NET-based, with no mention of Linux shell scripts or cross-platform SDKs. There is no discussion of Linux-specific tools, nor are there examples for bash, Azure CLI on Linux, or other non-Windows environments.
Recommendations
  • Provide explicit bash/Azure CLI examples for all operations currently shown via PowerShell.
  • Include Linux/macOS setup and management instructions alongside Windows/PowerShell steps.
  • Reference cross-platform SDKs (such as Python, Java) and provide sample code for these languages.
  • Clarify that Azure CLI is available and supported on Linux/macOS, and show usage in those environments.
  • Add links to Linux-specific documentation or troubleshooting guides.
  • Ensure that any screenshots or walkthroughs using the Azure portal do not assume a Windows environment.
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-09 00:34
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 command-line troubleshooting examples exclusively in PowerShell syntax (e.g., nslookup) and referencing Windows-specific patterns (ServicePointManager, .NET Framework APIs) without offering equivalent Linux or cross-platform alternatives. No Linux shell (bash) or cross-platform command examples are given, and Windows tools are mentioned first or exclusively in troubleshooting scenarios.
Recommendations
  • Provide equivalent Linux/macOS command-line examples (e.g., 'nslookup' or 'dig' in bash) alongside PowerShell commands.
  • Include troubleshooting steps relevant to Linux environments, such as checking DNS resolution or network connectivity using Linux tools.
  • Reference cross-platform SDKs and APIs (such as .NET Core/5+/6+ and Azure SDKs for Python, Java, Node.js) where applicable, not just .NET Framework.
  • Avoid Windows-specific terminology or, where necessary, clarify cross-platform alternatives.
  • Ensure that configuration and troubleshooting guidance is applicable to 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-ip-filtering.md ...cles/service-bus-messaging/service-bus-ip-filtering.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 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 example is given, while PowerShell commands are listed directly. This ordering and detail level favors Windows users and administrators, potentially making it less accessible for Linux or macOS users.
Recommendations
  • Add explicit Azure CLI command examples for managing IP firewall rules, including add, list, update, and remove operations.
  • Ensure CLI examples are presented before or alongside PowerShell examples to avoid implicit prioritization of Windows tooling.
  • Include notes or examples for Linux/macOS users, such as how to run Azure CLI commands in bash/zsh.
  • Where screenshots or UI instructions are given, clarify that the Azure portal is cross-platform and accessible from any OS.
  • Review and balance documentation so that Linux and Windows users have equal clarity and actionable steps.
GitHub Create Pull Request
← Previous Page 4 of 16 Next →