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 201-225 of 377 flagged pages
Service Bus Messaging Azure messaging services - Service Manager to Resource Manager ...vice-bus-messaging/deprecate-service-bus-management.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides extensive mapping between deprecated Service Manager APIs and their Resource Manager equivalents, with a strong focus on PowerShell cmdlets for both the old and new models. There are no CLI (az CLI), Bash, or cross-platform scripting examples, nor is there mention of Linux/macOS tooling or parity. All automation examples are PowerShell-based, which may create friction for Linux/macOS users who typically use Azure CLI or REST directly.
Recommendations
  • Add equivalent Azure CLI (az) command mappings for each PowerShell cmdlet shown, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
  • Include Bash/cURL examples for REST API calls to demonstrate how to interact with the APIs from any OS.
  • Explicitly mention that PowerShell Core is cross-platform if recommending PowerShell, and clarify if the cmdlets work in PowerShell Core on Linux/macOS.
  • Reorganize the automation section to present both PowerShell and CLI examples side-by-side, or at least mention both approaches.
  • Link to Azure CLI documentation for Service Bus, Event Hubs, and Relay management.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus - suspend messaging entities .../main/articles/service-bus-messaging/entity-suspend.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides explicit instructions and code examples for changing Service Bus entity status using Azure PowerShell, but does not offer equivalent examples for Azure CLI or other cross-platform tools. The only command-line example is PowerShell, which is primarily a Windows tool, and there is no guidance for Linux/macOS users who may prefer or require Azure CLI or REST API methods.
Recommendations
  • Add equivalent Azure CLI examples for changing entity status, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API or ARM template JSON snippets to show how to perform these operations programmatically, independent of OS.
  • Clearly indicate that both Azure PowerShell and Azure CLI can be used, and provide links or references to CLI documentation.
  • Consider reordering or presenting PowerShell and CLI examples side-by-side to avoid implying Windows-first preference.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides only C# code examples, which are most commonly associated with Windows development environments. There is no mention of Linux/macOS-specific tools, patterns, or code samples (such as Python, Java, or JavaScript), nor any guidance for running Service Bus code on non-Windows platforms. The focus on .NET and C# may create friction for Linux/macOS users who use other languages or development environments.
Recommendations
  • Add code examples in other supported languages (e.g., Python, Java, JavaScript, Go) alongside C# to demonstrate cross-platform usage.
  • Explicitly mention that Service Bus SDKs are available for Linux/macOS and provide links or brief instructions for installing and using them on those platforms.
  • Include notes or sections clarifying that the concepts and patterns apply equally across platforms, and highlight any platform-specific considerations if relevant.
  • When discussing asynchronous programming models, reference equivalent constructs in other languages (e.g., asyncio in Python, Promises in JavaScript, Futures in Java/Go).
GitHub Create Pull Request
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a detailed Azure PowerShell example for creating a private endpoint, but does not offer equivalent CLI or Linux/macOS shell examples. The validation steps exclusively reference creating and using a Windows VM, with no mention of Linux VMs or cross-platform alternatives. Windows tools and workflows (PowerShell, Windows VM creation) are presented first and exclusively, which may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI (az) examples for creating private endpoints alongside PowerShell scripts.
  • Include instructions for creating and validating with a Linux VM, or clarify that the validation steps (e.g., nslookup) work identically on Linux/macOS.
  • Explicitly state that all steps can be performed from Linux/macOS environments using Azure CLI and standard shell tools.
  • Where screenshots or instructions reference Windows-specific UI or workflows, add Linux/macOS equivalents or clarify cross-platform applicability.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation is notably Windows/Visual Studio-centric. All instructions for creating projects, managing NuGet packages, and running code are written for Visual Studio, a Windows-first IDE. NuGet package installation is shown only via the Package Manager Console (PowerShell), with no mention of cross-platform alternatives like the .NET CLI. There are no instructions for Linux/macOS users (e.g., using VS Code, JetBrains Rider, or command-line workflows), nor are there any Linux-specific notes or examples.
Recommendations
  • Add instructions for creating and running .NET console apps using the .NET CLI (dotnet new, dotnet run, etc.), which works on Windows, Linux, and macOS.
  • Include NuGet package installation examples using 'dotnet add package' in addition to Package Manager Console.
  • Mention and provide guidance for using cross-platform editors like VS Code or JetBrains Rider.
  • Clarify that the .NET SDK and Azure Service Bus client library work on Linux and macOS, not just Windows.
  • Where screenshots or UI steps are given for Visual Studio, provide equivalent steps or notes for other platforms/editors.
  • Add a short section or callout for Linux/macOS users, outlining any differences or prerequisites.
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
Medium Priority View Details →
Scanned: 2026-01-14 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 towards Windows development environments, specifically Visual Studio. All instructions for creating projects, managing NuGet packages, and authentication use Visual Studio GUI and PowerShell-based Package Manager Console, with no mention of cross-platform alternatives (e.g., .NET CLI, VS Code, or Linux/macOS workflows). There are no examples or guidance for Linux/macOS users, even though .NET 6+ and Azure Service Bus SDK are fully cross-platform.
Recommendations
  • Add instructions for using the .NET CLI (e.g., 'dotnet new console', 'dotnet add package') for project creation and package management, which work on Windows, Linux, and macOS.
  • Include guidance for using VS Code or other cross-platform editors, not just Visual Studio.
  • Clarify that the code samples work on Linux/macOS as well, and provide any necessary notes for authentication (e.g., using DefaultAzureCredential outside Visual Studio).
  • Add explicit steps for running the sample on Linux/macOS, including terminal commands and environment setup.
  • Mention that PowerShell commands can be replaced with Bash equivalents on non-Windows 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
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page provides examples for setting subscription filters in Azure Service Bus, with a clear emphasis on .NET/C# code samples and references to Azure PowerShell. While Azure CLI is mentioned (which is cross-platform), the only command-line example given is for PowerShell, and all code samples are in C#. There are no Linux/macOS shell (bash) or non-.NET SDK examples. The ordering of sections places PowerShell before CLI, and the only concrete code samples are for .NET, which may create friction for users on Linux/macOS or those using other languages.
Recommendations
  • Add bash/Azure CLI command examples for creating and managing subscription filters, demonstrating equivalent functionality to the PowerShell example.
  • Include code samples for other supported languages (e.g., Python, Java, JavaScript) to illustrate filter creation and management.
  • Reorder the 'Use Azure CLI' section before 'Use Azure PowerShell' to emphasize cross-platform tools.
  • Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Provide links or references to language-specific samples directly in the main content, not just in the 'Next steps' section.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus messages, payloads, and serialization | Microsoft Docs ...service-bus-messaging/service-bus-messages-payloads.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides a conceptual overview of Azure Service Bus messages, payloads, and serialization. While it is largely platform-neutral, there are subtle indications of Windows/.NET bias: .NET and Java clients are mentioned first and in more detail, and serialization examples focus on .NET Framework-specific features (e.g., BrokeredMessage object serialization), with no equivalent Linux/macOS or cross-platform code samples. There are no PowerShell or Windows tool references, but the lack of Python, JavaScript, or Linux CLI examples may create friction for non-Windows users.
Recommendations
  • Add code samples for Python, JavaScript, or other cross-platform Service Bus SDKs to illustrate message creation and serialization.
  • Clarify which features (e.g., BrokeredMessage object serialization) are .NET Framework-specific and suggest alternatives for .NET Core, Java, Python, etc.
  • Include links to cross-platform SDK documentation and usage guides.
  • Ensure that examples and explanations do not assume a Windows/.NET development environment.
GitHub Create Pull Request
Service Bus Messaging Create Azure Service Bus namespace and queue using Azure template ...saging/service-bus-resource-manager-namespace-queue.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page primarily describes deploying Azure Service Bus resources via the Azure Portal and ARM templates, which are cross-platform. However, in the 'Next steps' section, PowerShell is mentioned before the Azure CLI, and the link to managing Service Bus with PowerShell is given more prominence than the CLI equivalent. There are no explicit Linux/macOS examples, and the Service Bus Explorer tool referenced is Windows-only, but this is not highlighted or alternatives suggested.
Recommendations
  • Add explicit Azure CLI examples for managing Service Bus resources, and reference them alongside or before PowerShell examples.
  • Clarify that Service Bus Explorer is Windows-only and suggest cross-platform alternatives or note how Linux/macOS users can perform equivalent tasks (e.g., via Azure CLI, SDKs, or portal).
  • Ensure that links to management tools and documentation for Linux/macOS users are as prominent as those for Windows/PowerShell.
  • Consider including a section or note on how to perform deployment and management tasks from Linux/macOS environments using CLI or SDKs.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both PowerShell and Azure CLI examples for deploying the template, but PowerShell is listed first, which may signal a Windows-first bias. In the 'Next steps' section, resource management is only referenced via PowerShell and Service Bus Explorer, with no mention of Azure CLI or other cross-platform tools for management tasks. This creates a subtle but notable preference for Windows-centric tools and workflows.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform support.
  • Include links to documentation on managing Service Bus resources with Azure CLI, especially in the 'Next steps' section.
  • Explicitly mention that both PowerShell and Azure CLI are supported on Windows, Linux, and macOS.
  • Add examples or references for managing Service Bus resources using REST API or SDKs in languages/platforms common on Linux/macOS.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only Azure PowerShell examples for deploying and managing the Service Bus namespace, with no equivalent Azure CLI or Bash examples. The workflow assumes use of PowerShell and Cloud Shell, which can create friction for Linux/macOS users who may prefer or require Azure CLI or Bash. While alternative deployment methods are mentioned, they are not demonstrated or linked directly in the main workflow.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all deployment, verification, and cleanup steps.
  • Explicitly mention that both PowerShell and CLI are available in Azure Cloud Shell, and clarify how users can switch between them.
  • Reorder or parallelize instructions so that Linux/macOS users see CLI/Bash options as prominently as PowerShell.
  • Provide direct links or inline code blocks for the CLI-based deployment, verification, and cleanup steps.
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-14 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 provides a detailed, step-by-step guide for deploying Azure Service Bus resources using Azure Resource Manager templates, but all command-line examples and workflow instructions are exclusively for PowerShell. There is no mention of Azure CLI, Bash, or cross-platform alternatives, nor are Linux/macOS-specific instructions or examples provided. The focus on PowerShell and Windows tooling creates friction for users on Linux or macOS, who would typically use Azure CLI or Bash scripts.
Recommendations
  • Add equivalent instructions and examples for deploying ARM templates using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include a section or note clarifying that PowerShell commands are shown for Windows users, and provide links or inline examples for Linux/macOS users.
  • Show both PowerShell and Azure CLI examples side-by-side, or alternate their order to avoid Windows-first bias.
  • Reference Azure CLI documentation in the 'Next steps' section, such as https://learn.microsoft.com/azure/azure-resource-manager/templates/deploy-cli.
  • Explicitly state that the workflow is applicable on all platforms, and highlight any platform-specific differences.
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-14 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 moderate Windows bias in its example ordering and tooling. Windows/PowerShell instructions are presented first and in greater detail, including explicit steps to open PowerShell and use WSL, while Linux/macOS instructions are less detailed and lack equivalent step-by-step guidance. There is also a reliance on Windows-specific tools (PowerShell, WSL) and file path examples default to Windows conventions, with Linux paths only mentioned in passing.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, with equal detail and clarity.
  • Provide explicit step-by-step guidance for Linux/macOS users, including terminal commands and navigation.
  • Include Linux/macOS file path examples and clarify differences in path syntax.
  • Avoid assuming PowerShell or WSL as the default shell; offer Bash/zsh examples for Linux/macOS.
  • Add screenshots or terminal output examples from Linux/macOS environments.
  • Clarify any platform-specific requirements or differences in setup steps.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The troubleshooting guide for Azure Service Bus generally provides cross-platform guidance, but there are several instances of Windows bias. In the connectivity section, PowerShell (`tnc`) and Windows-specific tools (`psping.exe`) are mentioned first or exclusively, with Linux equivalents provided later or less prominently. The logging and diagnostics sections focus on .NET and Windows-centric tools, with little mention of Linux/macOS alternatives. Some troubleshooting steps and examples (e.g., using Visual Studio, PowerShell, or Windows-only utilities) may create friction for Linux/macOS users.
Recommendations
  • Present Linux/macOS commands and tools alongside Windows examples, and avoid listing Windows tools first unless they are more widely applicable.
  • For network troubleshooting, provide equivalent Linux/macOS commands (e.g., `nc`, `telnet`, `ss`, `nmap`) with equal prominence and detail.
  • When referencing Windows-only tools (e.g., `psping.exe`), suggest cross-platform alternatives (e.g., `hping`, `iperf`, or native shell scripts) and provide usage examples.
  • Expand logging and diagnostics guidance to include cross-platform approaches, such as using OpenTelemetry, native Linux/macOS logging tools, or SDK features available on all platforms.
  • Clarify when instructions are Windows-specific and provide parallel steps for Linux/macOS where possible.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial demonstrates how to use Azure Service Bus topics and subscriptions with .NET, and provides instructions for building and running the sample using the command line. However, the prerequisites and instructions reference Windows-centric tools (Visual Studio, Command Prompt, PowerShell) and do not mention Linux/macOS equivalents or alternatives. There are no explicit Linux/macOS instructions or notes about cross-platform compatibility for .NET Core/.NET 5+.
Recommendations
  • Clarify that .NET Core/.NET 5+ is cross-platform and can be used on Linux/macOS as well as Windows.
  • Add installation instructions for .NET SDK on Linux/macOS.
  • Replace or supplement 'Command Prompt or PowerShell' with 'terminal' or 'shell' for cross-platform language.
  • Mention that Visual Studio Code or other editors can be used on Linux/macOS.
  • Provide explicit Linux/macOS command-line examples (e.g., using bash/zsh) for building and running the sample.
  • Note any platform-specific differences (e.g., file paths, environment variables) if relevant.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy 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, without mentioning Linux/macOS alternatives or cross-platform tools. Additionally, the order of examples sometimes places PowerShell before CLI, and the ARMClient workflow is Windows-centric.
Recommendations
  • Include instructions for obtaining a Bearer token using Azure CLI (az account get-access-token) or cross-platform tools, not just ARMClient.exe.
  • Explicitly mention that ARMClient.exe is Windows-only and suggest alternatives for Linux/macOS users (e.g., curl, Postman, or Azure CLI).
  • Provide example commands for querying the ARM API using curl or Azure CLI, which work on all platforms.
  • Ensure that CLI examples are presented before or alongside PowerShell examples to reinforce cross-platform usability.
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
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 detailed instructions for enabling dead lettering on Azure Service Bus using the Azure portal, Azure CLI, Azure PowerShell, and ARM templates. While Azure CLI and ARM templates are cross-platform, the PowerShell section is extensive and uses Windows-centric tooling. PowerShell examples are given equal prominence to CLI, but PowerShell is primarily a Windows tool (though available on Linux, it's less commonly used there). The documentation does not provide Linux shell (bash) or macOS-specific examples, nor does it mention platform differences or recommend CLI for Linux/macOS users. The order of presentation puts PowerShell before ARM templates, which may reinforce Windows-first patterns.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add bash shell script examples for common tasks, especially for enabling dead lettering, to improve parity.
  • Mention that PowerShell is available on Linux/macOS but is less common, and provide guidance for those platforms.
  • Consider reordering sections to present CLI before PowerShell, or clarify platform suitability.
  • Add a table or note summarizing which tools are best for each OS.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus JMS 2.0 developer guide .../articles/service-bus-messaging/jms-developer-guide.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation references Windows-specific Azure portal instructions first when describing how to create a system assigned managed identity, linking directly to a Windows VM portal guide. Equivalent Linux VM instructions are not mentioned or linked, which may cause friction for Linux users. However, the core Java code and Service Bus usage instructions are platform-agnostic.
Recommendations
  • Include links or references to Linux VM managed identity setup guides alongside the Windows VM instructions.
  • When mentioning platform-specific Azure portal steps, provide parity for Linux and macOS users, or clarify that the instructions apply to all platforms.
  • Consider adding a short note or table listing both Windows and Linux VM managed identity setup documentation.
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
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 exhibits a notable Windows bias, especially in sections involving command-line operations and automation. PowerShell is the exclusive scripting language used for all imperative examples (e.g., deploying templates, setting access policies, retrieving identities). There are no Bash or Linux shell equivalents provided, and the CLI examples are limited to resource creation/update, not identity or access management. The use of PowerShell is assumed for all users, and Windows-centric tools are referenced first and exclusively in critical steps.
Recommendations
  • Provide equivalent Bash/Azure CLI commands for all PowerShell examples, especially for identity management and access policy configuration.
  • Explicitly mention cross-platform compatibility for all command-line instructions.
  • Add notes or tabs indicating how Linux/macOS users can perform each step, including links to relevant Azure CLI documentation.
  • Where possible, use Azure CLI as the default example, as it is cross-platform, and supplement with PowerShell only as an alternative.
  • Ensure screenshots and UI references are not Windows-specific unless necessary.
GitHub Create Pull Request
Service Bus Messaging Authenticate an application to access Azure Service Bus entities ...cles/service-bus-messaging/authenticate-application.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page provides authentication guidance for Azure Service Bus, but all code examples are in C# (.NET), and sample links point to .NET repositories. There are no Linux/macOS-specific instructions or examples, and the only programming language shown is one most commonly associated with Windows. While Azure CLI is mentioned, it is not demonstrated, and the primary workflow assumes use of the Azure portal or .NET libraries, which may not be the first choice for Linux users.
Recommendations
  • Add code samples in cross-platform languages such as Python (using azure-identity and azure-servicebus SDKs), Java, or Node.js.
  • Include explicit Azure CLI examples for authentication and role assignment, as Azure CLI is cross-platform.
  • Reference or link to Linux/macOS-specific guidance for environment setup, especially for managed identities and credential storage.
  • Balance the order of examples so that cross-platform tools (like Azure CLI) are presented before or alongside Windows-centric tools/languages.
  • Provide links to sample repositories in multiple languages, 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
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page exclusively provides PowerShell command mappings for Azure Service Manager to Resource Manager, with no mention of Linux/macOS-friendly alternatives such as Azure CLI, Bash, or cross-platform scripting. REST API mappings are platform-neutral, but all command-line automation guidance is Windows-centric, referencing only PowerShell cmdlets and their evolution. There are no Linux/macOS equivalents or examples, and PowerShell is presented as the default automation tool.
Recommendations
  • Add Azure CLI command equivalents for each PowerShell cmdlet, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script examples for common operations, especially for REST API calls.
  • Explicitly mention that PowerShell Core is available cross-platform, but also provide CLI alternatives for users who prefer native Linux/macOS tools.
  • Reorganize command-line sections to present both PowerShell and CLI examples side-by-side, or indicate which tools are available on which platforms.
  • Add a note clarifying platform compatibility for each tool mentioned.
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
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is focused exclusively on the legacy WindowsAzure.ServiceBus .NET Framework library, which is inherently Windows-centric. All examples and configuration instructions assume usage of .NET Framework and Windows tooling, with no mention of Linux or macOS compatibility, alternative libraries, or cross-platform usage patterns. There are no Linux-specific instructions, examples, or troubleshooting notes.
Recommendations
  • Clarify whether the WindowsAzure.ServiceBus .NET Framework library can be used on Linux/macOS via Mono or .NET Core/5+/6+.
  • If cross-platform usage is possible, provide explicit instructions and examples for Linux/macOS environments, including installation steps and any platform-specific caveats.
  • Mention and link to cross-platform alternatives (such as Azure.Messaging.ServiceBus for .NET Standard/.NET Core) earlier and more prominently.
  • Add troubleshooting notes for non-Windows environments, if supported.
  • If the library is Windows-only, state this clearly at the top of the documentation.
GitHub Create Pull Request
Service Bus Messaging Enable duplicate message detection - Azure Service Bus ...es/service-bus-messaging/enable-duplicate-detection.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 enabling duplicate message detection in Azure Service Bus. However, the PowerShell section is detailed and uses Windows-specific tooling, which may not be natively available on Linux/macOS. PowerShell examples are given equal prominence to CLI, and no mention is made of Bash or Linux-native scripting alternatives. The use of PowerShell and references to its cmdlets can create friction for non-Windows users, although Azure CLI is cross-platform and included. The ordering places Azure CLI before PowerShell, but the PowerShell section is extensive and assumes familiarity with Windows tooling.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add Bash or shell script examples where appropriate, or clarify that Azure CLI commands work in Bash/zsh/fish shells.
  • Note that Azure PowerShell is available on Linux/macOS via PowerShell Core, but may require additional installation steps.
  • Consider reducing the prominence of PowerShell or providing links to installation guides for non-Windows platforms.
  • Add a short section or callout for Linux/macOS users to clarify tool availability and recommend CLI for parity.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus - suspend messaging entities .../main/articles/service-bus-messaging/entity-suspend.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 Missing Linux Example
Summary
The documentation provides explicit instructions and code examples for changing queue status using Azure PowerShell, a Windows-centric tool. There are no equivalent examples for Linux/macOS users (e.g., Azure CLI, REST API, or SDKs), and PowerShell is mentioned as the only command-line method. This creates friction for non-Windows users who may not have PowerShell installed or prefer native Linux tools.
Recommendations
  • Add Azure CLI examples for suspending and reactivating messaging entities, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Include REST API or SDK (e.g., Python, .NET, Java) examples for programmatic access, which are platform-agnostic.
  • Explicitly mention that PowerShell is available on Linux/macOS, but provide alternatives for users who do not wish to install it.
  • Reorder or parallelize examples so that Windows and Linux/macOS methods are presented together, avoiding implicit prioritization of Windows tools.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides C# code examples exclusively and references .NET APIs and concepts throughout, which are most commonly associated with Windows development. There are no Linux/macOS-specific code samples, nor are cross-platform CLI or language examples (such as Python, JavaScript, or Java) shown, despite mentioning that these languages are supported. No Windows-only tools or PowerShell commands are referenced, but the overall example and API focus is Windows-centric.
Recommendations
  • Add equivalent code samples for Linux-friendly languages (e.g., Python, JavaScript, Java) alongside C# examples.
  • Include CLI-based examples (such as Azure CLI or Bash scripts) where appropriate.
  • Explicitly mention cross-platform support and provide guidance for Linux/macOS environments.
  • Consider reordering or grouping examples so that Windows and Linux/macOS parity is clear.
GitHub Create Pull Request
← Previous Page 9 of 16 Next →