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 226-250 of 377 flagged pages
Service Bus Messaging Integrate Azure Service Bus with Azure Private Link Service ...articles/service-bus-messaging/private-link-service.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. All command-line examples for creating private endpoints use Azure PowerShell, with no equivalent Azure CLI or Linux/macOS shell examples. The validation steps exclusively reference creating and connecting to a Windows VM, omitting instructions for Linux VMs. Windows-centric tools and workflows are presented first and, in some cases, exclusively.
Recommendations
  • Add Azure CLI examples for all PowerShell-based instructions, ensuring parity for Linux/macOS users.
  • Include instructions and screenshots for creating and validating private endpoints using a Linux VM in Azure.
  • When demonstrating command-line operations (e.g., nslookup), clarify that these commands work on both Windows and Linux/macOS, and provide sample outputs from both environments.
  • Avoid referencing only Windows-specific quickstarts; link to both Windows and Linux VM creation guides.
  • Consider reordering examples so that platform-neutral or cross-platform options (Azure CLI, portal) are presented before platform-specific ones.
GitHub Create Pull Request
Service Bus Messaging Quickstart - Use Azure Service Bus queues from .NET app ...essaging/service-bus-dotnet-get-started-with-queues.md
Medium Priority View Details →
Scanned: 2026-01-13 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 and Visual Studio workflows. All instructions for creating projects, managing NuGet packages, and running commands are based on Visual Studio GUI and PowerShell (Package Manager Console), with no mention of Linux/macOS equivalents (e.g., .NET CLI, VS Code, or cross-platform editors). There are no examples or guidance for Linux/macOS users, and the use of Windows-specific tools is assumed throughout.
Recommendations
  • Add instructions for creating and managing .NET projects using the .NET CLI (dotnet new, dotnet add package, dotnet run), which works on Linux/macOS.
  • Include guidance for using VS Code or other cross-platform editors, not just Visual Studio.
  • Show NuGet package installation using 'dotnet add package' commands alongside PowerShell examples.
  • Clarify that the code samples work on Linux/macOS as well, and provide any necessary notes about environment setup (e.g., authentication, port requirements).
  • Reorder or parallelize instructions so that Windows and Linux/macOS workflows are presented together, or in separate tabs.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus Geo-Disaster Recovery | Microsoft Docs ...n/articles/service-bus-messaging/service-bus-geo-dr.md
Medium Priority View Details →
Scanned: 2026-01-13 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 exhibits a moderate Windows bias. Examples and sample code are primarily in .NET (Windows-centric), and PowerShell is mentioned as a primary automation method. There is no explicit mention or example of Linux/macOS command-line usage (e.g., Bash, Azure CLI on Linux), and Windows tools/patterns (PowerShell, .NET) are referenced before their cross-platform or Linux equivalents. Linux users may need to infer or adapt steps, especially for automation and scripting.
Recommendations
  • Add explicit Azure CLI examples for setup, failover, and management tasks, showing usage on Linux/macOS.
  • Include Bash shell scripts or cross-platform code samples alongside PowerShell/.NET examples.
  • Reference cross-platform SDKs (e.g., Python, Java) in sample sections, not just .NET.
  • Clarify that all portal and REST API steps are OS-agnostic, and highlight any OS-specific caveats.
  • Reorder sections so cross-platform tools (Azure CLI, REST API) are mentioned before Windows-specific tools (PowerShell).
GitHub Create Pull Request
Service Bus Messaging Configure IP firewall rules for Azure Service Bus ...cles/service-bus-messaging/service-bus-ip-filtering.md
Medium Priority View Details →
Scanned: 2026-01-13 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 PowerShell instructions for managing IP firewall rules, but does not offer equivalent Linux/macOS shell examples. The Azure CLI is mentioned, but no concrete CLI command examples are given, while PowerShell commands are linked directly. The ordering and emphasis on PowerShell and Resource Manager templates (often used in Windows environments) may create friction for Linux/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 shown before or alongside PowerShell examples to avoid Windows-first bias.
  • Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Where possible, provide bash shell snippets or usage notes for Linux/macOS environments.
  • Review linked deployment instructions to ensure Linux/macOS parity (e.g., not only PowerShell-based deployment guides).
GitHub Create Pull Request
Service Bus Messaging Set subscriptions filters in Azure Service Bus | Microsoft Docs ...s/service-bus-messaging/service-bus-filter-examples.md
Medium Priority View Details →
Scanned: 2026-01-13 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 notable Windows/.NET bias. Examples and code samples are exclusively in C#/.NET, with no equivalent samples for Linux/macOS-friendly languages (e.g., Python, Java, JavaScript). The CLI and PowerShell sections are brief, with PowerShell mentioned before CLI, and no Bash or Linux shell scripting examples are provided. There are no instructions or examples for Linux-specific tools or workflows, and the code samples assume a Windows/.NET development environment.
Recommendations
  • Add code samples in Python, Java, or JavaScript to demonstrate cross-platform usage.
  • Expand Azure CLI examples with full command sequences for creating filters and rules, including Bash scripting samples.
  • Ensure CLI instructions are given equal prominence to PowerShell, and consider listing CLI before PowerShell.
  • Include notes or sections on how to perform these tasks from Linux/macOS environments.
  • Link to cross-platform SDK samples directly in relevant sections, not just in 'Next steps'.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus - messaging exceptions | Microsoft Docs ...s-messaging/service-bus-messaging-exceptions-latest.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page contains a notable Windows bias in the troubleshooting section for SocketException, where only a PowerShell 'nslookup' command is provided, and the output example uses Windows-style formatting. No Linux/macOS equivalent commands (e.g., 'dig', 'nslookup' in bash) or guidance are given. The rest of the documentation is platform-neutral, focusing on .NET exceptions and Service Bus concepts, but the only concrete troubleshooting example is Windows-centric.
Recommendations
  • Add Linux/macOS equivalents for troubleshooting commands, such as 'nslookup <mynamespace>.servicebus.windows.net' or 'dig <mynamespace>.servicebus.windows.net' in bash.
  • Provide output examples for both Windows and Linux/macOS shells.
  • Explicitly mention that the troubleshooting steps apply to all platforms and clarify any platform-specific differences.
  • Consider including cross-platform .NET code samples where relevant, or note any platform-specific behaviors.
GitHub Create Pull Request
Service Bus Messaging Migrate Azure Service Bus namespaces - standard to premium ...-bus-messaging/service-bus-migrate-standard-premium.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides migration instructions using Azure CLI and PowerShell, but refers to 'PowerShell' generically without clarifying platform differences, and does not mention Linux/macOS specifics or alternatives. The examples and environment variable syntax are platform-neutral, but the narrative prioritizes Windows tools (PowerShell) and does not address Linux shell usage or potential differences in command execution. No Linux/macOS-specific caveats, troubleshooting, or screenshots are provided, and Windows terminology (PowerShell) appears before CLI or Bash equivalents.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide example shell syntax (e.g., Bash) alongside PowerShell.
  • Clarify any platform-specific differences in environment variable setting (e.g., $var for PowerShell, export VAR=... for Bash).
  • Include Linux/macOS screenshots or notes where UI or workflow may differ.
  • Avoid using 'PowerShell' as a generic term for CLI usage; specify when instructions are for PowerShell vs. Bash.
  • Add troubleshooting notes for Linux/macOS users, such as authentication or permission issues that may differ from Windows.
GitHub Create Pull Request
Service Bus Messaging Create Azure Service Bus namespace and queue using Bicep ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-queue-bicep.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, validation, and cleanup, but PowerShell is given equal prominence to CLI, and the 'Next steps' section highlights PowerShell and a Windows-only tool (Service Bus Explorer) for management. There is a slight Windows bias due to the emphasis on PowerShell and Windows tools, though Linux users can complete all core tasks using the CLI.
Recommendations
  • Add explicit mention that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for non-Windows users.
  • Include links or examples for managing Service Bus resources using CLI or SDKs on Linux/macOS, not just PowerShell.
  • In the 'Next steps' section, add parity by referencing CLI management guides or cross-platform tools.
  • Clarify that Service Bus Explorer is a Windows-only tool and suggest alternatives for Linux/macOS users if available.
GitHub Create Pull Request
Service Bus Messaging Create Azure Service Bus namespace topic using a template ...saging/service-bus-resource-manager-namespace-topic.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both PowerShell and Azure CLI examples for deploying the template, but PowerShell is presented first and referenced in management links, which may signal a Windows-first approach. The 'Next steps' section only links to PowerShell management documentation, omitting Linux/macOS alternatives such as Azure CLI or SDKs. There is no mention of Linux-specific tools or parity in management tasks.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell to emphasize cross-platform support.
  • Include management instructions and links for Azure CLI and/or SDKs (Python, .NET, etc.) in the 'Next steps' section.
  • Explicitly state that both PowerShell and Azure CLI are cross-platform, and clarify which commands work on Linux/macOS.
  • Add references to Linux/macOS compatible tools for managing Service Bus resources, such as Service Bus Explorer (if cross-platform) or REST API usage examples.
GitHub Create Pull Request
Service Bus Messaging Create a Service Bus authorization rule using an Azure template ...ng/service-bus-resource-manager-namespace-auth-rule.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page shows a moderate Windows bias. PowerShell is presented as the first deployment example, and the 'Next steps' section prioritizes PowerShell and Service Bus Explorer (a Windows-only GUI tool). While Azure CLI is included, the CLI example uses the legacy 'azure' CLI (deprecated and not cross-platform), and there is little mention of Linux/macOS-specific workflows or tools.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell, using the current 'az' CLI syntax, which is cross-platform.
  • Add explicit instructions or examples for Linux/macOS users, including shell commands and environment notes.
  • Mention Service Bus Explorer alternatives for Linux/macOS (e.g., cross-platform tools or SDK usage).
  • Balance 'Next steps' links to include management via Azure CLI and SDKs, not just PowerShell and Windows tools.
GitHub Create Pull Request
Service Bus Messaging Create an Azure Service Bus namespace using template ...us-messaging/service-bus-resource-manager-namespace.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively provides Azure PowerShell examples for deploying and managing the Service Bus namespace, with no equivalent Azure CLI or Bash examples. The workflow assumes use of the Azure Cloud Shell with PowerShell and references Windows-centric actions (e.g., right-click to paste), which may not be intuitive for Linux/macOS users. Alternative deployment methods (CLI, REST, portal) are only mentioned as links at the end, not demonstrated.
Recommendations
  • Add equivalent Azure CLI examples alongside PowerShell for all deployment, verification, and cleanup steps.
  • Include Bash shell instructions for copy/paste actions, avoiding Windows-specific terminology like 'right-click'.
  • Present both PowerShell and CLI examples in parallel, or alternate which is shown first.
  • Explicitly state that Azure Cloud Shell supports both Bash and PowerShell, and guide users to select their preferred shell.
GitHub Create Pull Request
Service Bus Messaging Create Azure Service Bus resources using templates ...bus-messaging/service-bus-resource-manager-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 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 exclusively uses PowerShell for all deployment instructions, with no mention of cross-platform tools such as Azure CLI, Bash, or Cloud Shell. All example commands and workflows are tailored to PowerShell, which is most commonly used on Windows. There are no Linux/macOS-specific instructions or examples, and the installation section only references Azure PowerShell. This creates friction for users on Linux or macOS who may prefer or require alternative tooling.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include a section on using Azure Cloud Shell, which supports both Bash and PowerShell and is accessible from any OS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell is to be retained as an example.
  • Present both PowerShell and Azure CLI examples side-by-side, or at least link to CLI documentation.
  • Update installation instructions to cover Azure CLI and Cloud Shell, not just Azure PowerShell.
GitHub Create Pull Request
Service Bus Messaging Troubleshooting guide for Azure Service Bus | Microsoft Docs ...ice-bus-messaging/service-bus-troubleshooting-guide.md
Medium Priority View Details →
Scanned: 2026-01-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 demonstrates a moderate Windows bias. Troubleshooting steps and diagnostic commands frequently present Windows/PowerShell tools (e.g., 'tnc', 'psping.exe') first or exclusively, with Linux equivalents (e.g., 'telnet') mentioned secondarily or not at all. Some tools (like 'psping.exe') are Windows-only, and logging/tracing sections focus on .NET and Windows-centric tools (Application Insights, EventSource) without mentioning Linux alternatives. There are few explicit Linux/macOS examples, and some sections (e.g., resource deletion recommendations) list PowerShell before CLI, with no bash or Linux-native instructions.
Recommendations
  • Provide Linux/macOS equivalents for all diagnostic commands and troubleshooting steps, such as using 'nc', 'ss', or 'nmap' for port checks.
  • Include Linux/macOS-specific instructions and examples alongside Windows/PowerShell ones, ensuring parity in troubleshooting workflows.
  • Mention cross-platform tools for network diagnostics (e.g., 'tcpdump', 'netcat', 'Wireshark') and clarify their usage on Linux/macOS.
  • Expand logging and tracing sections to reference cross-platform frameworks and tools (e.g., OpenTelemetry, Jaeger, Zipkin) and provide sample code for non-.NET environments.
  • Where Windows tools are referenced (e.g., 'psping.exe'), suggest open-source or platform-agnostic alternatives for Linux/macOS users.
  • Ensure that CLI examples (e.g., Azure CLI) are given equal prominence to PowerShell, and provide bash scripts where relevant.
GitHub Create Pull Request
Service Bus Messaging Tutorial: Update inventory using Azure portal and topics/subscriptions ...ng/service-bus-tutorial-topics-subscriptions-portal.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The tutorial demonstrates a notable Windows bias: prerequisites specify Visual Studio (Windows-centric), and command-line instructions reference Command Prompt and PowerShell, with no mention of Linux/macOS terminals or tooling. There are no explicit Linux/macOS instructions or examples, and the workflow assumes familiarity with Windows environments.
Recommendations
  • Add explicit instructions for Linux/macOS users, including terminal commands and environment setup.
  • Mention cross-platform .NET support and provide examples for running dotnet commands in Bash/zsh.
  • Include alternative IDEs (e.g., VS Code) and installation steps for .NET SDK on Linux/macOS.
  • Clarify that all commands (git, dotnet) are cross-platform and provide OS-agnostic instructions.
  • Reference Service Bus Explorer alternatives or CLI tools available on Linux/macOS.
GitHub Create Pull Request
Service Bus Messaging Test locally by using the Azure Service Bus emulator ...us-messaging/test-locally-with-service-bus-emulator.md
Medium Priority View Details →
Scanned: 2026-01-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 page demonstrates a moderate Windows bias. Windows instructions are presented first and in greater detail, including explicit PowerShell and WSL steps, while Linux/macOS steps are less detailed and lack equivalent terminal commands or troubleshooting notes. Windows-specific tools (PowerShell, WSL) are mentioned and required for the automated script approach, with no Linux/macOS shell equivalents shown. File path examples and environment variable notes prioritize Windows syntax, and Docker Desktop is referenced with a Windows-centric installation link.
Recommendations
  • Provide step-by-step Linux/macOS terminal commands for running the automated script, matching the detail given for Windows.
  • Include Linux/macOS shell equivalents for PowerShell and WSL steps, such as bash/zsh instructions.
  • List Linux/macOS instructions before or alongside Windows instructions to avoid 'windows_first' ordering.
  • Add troubleshooting notes for Linux/macOS environments, such as permissions, path syntax, and Docker installation links.
  • Show file path examples in both Windows and Linux/macOS formats in environment variable documentation.
  • Reference Docker Desktop installation for Linux/macOS, not just 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
Medium Priority View Details →
Scanned: 2026-01-13 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 configuring the minimum TLS version, which is good for cross-platform parity. However, in the section on checking the minimum TLS version, it exclusively recommends ARMClient.exe (a Windows-only tool) and provides PowerShell commands for authentication, with no mention of Linux/macOS alternatives (such as using curl, az CLI, or bash scripting). Additionally, the order of examples sometimes places Windows-centric tools (PowerShell, ARMClient.exe) before cross-platform options.
Recommendations
  • Include Linux/macOS-friendly instructions for obtaining a Bearer token (e.g., using Azure CLI: `az account get-access-token`).
  • Provide examples using curl or HTTPie for querying the Azure Resource Manager API, in addition to ARMClient.exe.
  • Mention that ARMClient.exe is Windows-only and suggest alternatives for other platforms.
  • Ensure that cross-platform tools (Azure CLI, REST API via curl) are presented before or alongside Windows-specific tools.
  • Add bash or shell script examples where PowerShell is used.
GitHub Create Pull Request
Service Bus Messaging Enable partitioning in Azure Service Bus Premium namespaces ...les/service-bus-messaging/enable-partitions-premium.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for enabling partitioning, but the PowerShell section is given equal prominence to the CLI, and no explicit Linux shell (e.g., Bash) or cross-platform scripting examples are provided. The PowerShell example, which is primarily a Windows tool, is featured as a main method, potentially signaling a Windows-centric approach. There are no Linux-specific tools or instructions, and no mention of platform differences or considerations.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and works on Windows, Linux, and macOS, while PowerShell is primarily a Windows tool (though PowerShell Core is cross-platform, but this is not clarified).
  • Provide explicit Bash or Linux shell examples where appropriate, or clarify that the Azure CLI example is suitable for Linux/macOS users.
  • If PowerShell is included, consider including a corresponding Bash script or Linux-native automation example to ensure parity.
  • Note any platform-specific requirements or differences, especially for users on Linux or macOS.
  • Consider reordering sections to present the Azure CLI (cross-platform) before PowerShell, or clarify that both are options depending on user environment.
GitHub Create Pull Request
Service Bus Messaging Enable partitioning in Azure Service Bus basic or standard ...vice-bus-messaging/enable-partitions-basic-standard.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for enabling partitioning in Azure Service Bus. However, PowerShell is a Windows-centric tool and is presented in a dedicated section, with detailed examples. There is no mention of Linux-specific tools or shell patterns (such as Bash), nor are there explicit Linux command-line examples. The CLI examples are cross-platform, but PowerShell's inclusion and prominence may signal a Windows bias. Additionally, PowerShell is listed before ARM templates, which are platform-neutral, and there is no explicit guidance for Linux users.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and consider providing Bash shell examples or notes for Linux users.
  • Add explicit statements or sections for Linux users, such as 'On Linux/macOS' to reinforce cross-platform support.
  • If PowerShell is included, mention that Azure PowerShell is available on Linux and macOS via PowerShell Core, or provide equivalent Bash examples.
  • Ensure that cross-platform tools (like Azure CLI) are presented before platform-specific tools (like PowerShell) to avoid perceived prioritization of Windows.
  • Consider adding troubleshooting or environment setup notes for both Windows and Linux users.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus - message count ...ain/articles/service-bus-messaging/message-counters.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for retrieving message counts, but the PowerShell section is given equal prominence to the CLI, despite PowerShell being primarily a Windows-centric tool. There are no Linux-specific shell examples (e.g., Bash, curl, or Python scripts) for direct API calls, nor is there mention of Linux-native tools or patterns. The CLI examples are cross-platform, but the inclusion and detailed coverage of PowerShell may signal a Windows bias.
Recommendations
  • Add explicit Bash or shell script examples for Linux users, especially for REST API calls or using tools like curl.
  • Clarify that Azure CLI is cross-platform and highlight its usage for both Windows and Linux.
  • Consider de-emphasizing PowerShell or moving it after CLI examples, noting its Windows-centric nature.
  • Include references or links to Linux-native automation tools or SDK usage (e.g., Python scripts) for message count retrieval.
  • Add a note about platform compatibility for each example, helping users choose the best approach for their OS.
GitHub Create Pull Request
Service Bus Messaging Message transfers, locks, and settlement ...ce-bus-messaging/message-transfers-locks-settlement.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its exclusive use of C# code examples, which are most commonly associated with Windows development environments. There is no mention of Linux-specific tools, patterns, or code samples, nor are there examples for other platforms or languages (e.g., Python, Java, JavaScript) despite referencing their support. The documentation also references .NET Framework (Windows-centric) before mentioning .NET Standard and other cross-platform clients.
Recommendations
  • Add code examples for other supported languages (e.g., Python, Java, JavaScript, Go) to illustrate cross-platform usage.
  • Explicitly mention how to run the examples on Linux and macOS, including any platform-specific considerations.
  • Provide parity in tooling references, such as mentioning cross-platform SDKs and avoiding exclusive references to Windows-centric frameworks (e.g., .NET Framework).
  • Include links or notes about setting up Service Bus clients on Linux environments.
  • Ensure that any advanced usage patterns (e.g., semaphores, asynchronous programming) are demonstrated in at least one non-Windows language.
GitHub Create Pull Request
Service Bus Messaging Troubleshoot AMQP errors in Azure Service Bus | Microsoft Docs ...service-bus-messaging/service-bus-amqp-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page references 'Service Bus for Windows Server' in its 'Next steps' section, highlighting a Windows-specific implementation without mentioning Linux equivalents or cross-platform options. No Linux-specific tools, troubleshooting steps, or examples are provided, and the only platform-specific resource is Windows-focused.
Recommendations
  • Add links or references to cross-platform Service Bus implementations, such as Azure Service Bus on Linux or Docker.
  • Include troubleshooting steps or examples relevant to Linux environments (e.g., using Linux command-line tools or logs).
  • Balance the 'Next steps' section by providing parity for Linux users, such as guides for running Service Bus clients or troubleshooting on Linux.
  • Explicitly mention that AMQP errors and solutions apply to both Windows and Linux clients, and provide platform-agnostic guidance where possible.
GitHub Create Pull Request
Service Bus Messaging Get started with Azure Service Bus queues (Go) ...vice-bus-messaging/service-bus-go-how-to-use-queues.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell instructions for setting environment variables, but lists Bash first, which is positive for Linux parity. However, the prerequisites mention activating Visual Studio or MSDN subscriber benefits, which are Windows-centric, before mentioning the free account option. The authentication section references Azure CLI for local development, which is cross-platform, but does not mention OS-specific caveats or alternatives. No explicit Windows-only tools or patterns are used, and the code samples are OS-neutral. Overall, there is mild Windows bias in the order and emphasis of prerequisites, but the main workflow is cross-platform.
Recommendations
  • In the prerequisites, mention the free Azure account option before Windows-centric Visual Studio/MSDN benefits.
  • Explicitly state that Azure CLI is available on Windows, Linux, and macOS, and provide installation links for all platforms.
  • Add a note clarifying that all code samples and instructions work on Linux, macOS, and Windows.
  • Consider adding troubleshooting tips for common OS-specific issues (e.g., environment variable syntax differences, Azure CLI installation).
GitHub Create Pull Request
Service Bus Messaging Programmatically manage Azure Service Bus namespaces and entities ...vice-bus-messaging/service-bus-management-libraries.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a mild Windows bias by referencing Azure portal, CLI, and PowerShell as management tools, with PowerShell (a Windows-centric tool) mentioned explicitly and before any Linux-specific alternatives. There are no Linux shell examples or references to Bash, and no mention of Linux-specific management patterns. However, the code samples and SDKs are cross-platform and cover multiple languages, which mitigates the bias somewhat.
Recommendations
  • Explicitly mention Bash and Linux shell alternatives alongside PowerShell when discussing management tools.
  • Provide examples or references for using Azure CLI in Bash/Linux environments.
  • Avoid listing PowerShell before cross-platform tools, or clarify that Azure CLI and SDKs are cross-platform.
  • Add a note highlighting that all SDKs and management libraries are supported on Linux, macOS, and Windows.
  • Include links to Linux-specific documentation or samples where relevant.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus Subscription Rule SQL Action syntax | Microsoft Docs ...bus-messaging/service-bus-messaging-sql-rule-action.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page references both Azure CLI and PowerShell tools for managing Service Bus subscription rules, but it lists the PowerShell cmdlet (New-AzServiceBusRule) in the 'Next steps' section alongside the CLI command, which may suggest parity. However, there are no explicit Linux-specific examples, nor is there mention of Linux-native tools or shell environments. The documentation refers to .NET types and methods (e.g., System.Char.IsLetter, System.Guid.NewGuid), which are more familiar to Windows/.NET developers, and does not provide equivalent references for other platforms. There are no explicit code examples using Bash, Linux shell, or other cross-platform SDKs, and the PowerShell tool is mentioned in a way that may imply Windows-first usage.
Recommendations
  • Add explicit Linux/Bash shell examples for managing Service Bus rules using Azure CLI.
  • Clarify that Azure CLI is cross-platform and provide usage examples in both Windows (cmd/PowerShell) and Linux (Bash/zsh) environments.
  • Reference Python or other cross-platform SDKs in the 'Next steps' section to balance .NET/Java/JavaScript.
  • Where .NET types/methods are referenced, provide equivalent explanations for other languages/platforms (e.g., Python, Java).
  • Ensure that PowerShell examples are not presented as the primary or sole method for rule management.
GitHub Create Pull Request
Service Bus Messaging Get started with Azure Service Bus topics (JavaScript) ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-nodejs-how-to-use-topics-subscriptions.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation displays mild Windows bias by referencing Windows-specific tools and patterns, such as recommending Windows PowerShell and Azure Website deployment guides before Linux equivalents. The phrase 'open a command prompt' is used generically, but the only explicit deployment example links to a Windows PowerShell guide. There are no Linux-specific instructions or examples, nor is there mention of Linux terminal usage or deployment guides.
Recommendations
  • Provide explicit Linux and macOS equivalents for all referenced Windows tools and guides (e.g., link to Linux terminal deployment guides alongside Windows PowerShell).
  • Replace or supplement 'command prompt' language with 'terminal' and clarify cross-platform compatibility.
  • Add notes or examples for running the code on Linux/macOS, including installation and authentication steps for Azure CLI on those platforms.
  • Ensure that any referenced deployment documentation includes both Windows and Linux instructions, or provide links to both.
  • Avoid mentioning Windows-specific tools (like PowerShell) without also mentioning Linux alternatives (like Bash).
GitHub Create Pull Request
← Previous Page 10 of 16 Next →