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 126-150 of 377 flagged pages
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-08 00:53
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 towards Windows development environments, specifically Visual Studio and Azure Compute Emulator, with no mention of Linux or cross-platform alternatives. All instructions, screenshots, and tooling references are for Windows. There are no examples or guidance for Linux users, such as using VS Code, .NET CLI, or running/testing the application outside of Windows. The use of Windows-specific tools and patterns is pervasive, and Linux parity is missing throughout.
Recommendations
  • Add instructions for setting up the development environment on Linux, including using VS Code and the .NET CLI.
  • Provide equivalent steps for project creation, package management, and running/testing the application on Linux.
  • Include screenshots and examples for Linux workflows, such as using terminal commands instead of Visual Studio dialogs.
  • Mention cross-platform options for emulating Azure services locally, such as Azure Functions Core Tools or Docker-based solutions.
  • Clearly indicate which steps are Windows-specific and provide alternatives for macOS and Linux users.
  • Avoid assuming Visual Studio is the only development environment; reference other IDEs and editors where appropriate.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example Dotnet Heavy
Summary
The documentation page exhibits a Windows/.NET bias. While it mentions both Azure CLI and PowerShell for managing subscription filters, PowerShell is listed separately and given equal prominence, despite being Windows-specific. All code samples are in C#/.NET, with no examples for other languages or Linux-native scripting (e.g., Bash). There are no Linux-specific command-line examples, nor are cross-platform SDKs (Python, Java, JavaScript) demonstrated. The 'Next steps' section links to .NET samples first and provides only links (not inline examples) for other languages.
Recommendations
  • Add Bash/Azure CLI examples for all operations currently shown in PowerShell.
  • Provide code samples in at least one non-.NET language (e.g., Python, Java, JavaScript) for creating filters and sending/receiving messages.
  • Ensure that cross-platform tools (Azure CLI, REST API) are mentioned before or alongside Windows-specific tools (PowerShell).
  • Include explicit Linux usage notes or examples, such as running Azure CLI commands in Bash.
  • Balance the 'Next steps' section by including inline examples or walkthroughs for other languages, not just .NET.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio and PowerShell. All instructions for creating projects, managing NuGet packages, and authentication are given using Visual Studio UI and PowerShell commands, with no mention of cross-platform alternatives (e.g., VS Code, CLI, or Linux/Mac workflows). There are no examples or guidance for Linux users, such as using the .NET CLI, alternative editors, or shell commands. The documentation assumes the reader is using Windows and Visual Studio, which may exclude or confuse developers on Linux or macOS.
Recommendations
  • Add instructions for creating and managing .NET projects using the .NET CLI (dotnet new, dotnet add package, etc.), which works on Windows, Linux, and macOS.
  • Include examples of installing NuGet packages via the CLI (e.g., 'dotnet add package Azure.Messaging.ServiceBus') instead of only PowerShell.
  • Mention and provide guidance for using cross-platform editors like Visual Studio Code.
  • Clarify that the code samples work on Linux and macOS as well, and provide any OS-specific notes if needed (e.g., for authentication via DefaultAzureCredential).
  • Add screenshots or steps for Linux/macOS environments, or at least note differences in workflow.
  • Avoid assuming Visual Studio is required; note that .NET development is fully supported on other platforms.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively using Visual Studio for project creation and management, referencing Windows-specific UI elements and workflows, and providing NuGet installation instructions only via the PowerShell-based Package Manager Console. There are no instructions or examples for Linux users, such as using VS Code, JetBrains Rider, or .NET CLI commands for project setup and package installation. The documentation assumes the reader is on Windows and using Visual Studio, omitting Linux-compatible development patterns and tooling.
Recommendations
  • Add instructions for creating and managing .NET projects using the .NET CLI (dotnet new, dotnet add package) suitable for Linux, macOS, and Windows.
  • Include examples for installing NuGet packages via the CLI, not just the Visual Studio Package Manager Console.
  • Reference cross-platform editors such as VS Code or JetBrains Rider, and provide guidance for their use.
  • Clarify that the .NET SDK and Azure Service Bus libraries are cross-platform and can be used on Linux and macOS.
  • Provide screenshots or descriptions for Linux/macOS environments where relevant, or note differences in workflow.
  • Avoid assuming Visual Studio is required; mention alternatives and ensure parity in 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-ip-filtering.md ...cles/service-bus-messaging/service-bus-ip-filtering.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples and instructions for configuring IP firewall rules for Azure Service Bus using the Azure portal, Resource Manager templates, Azure CLI, and Azure PowerShell. However, there is a noticeable Windows bias: PowerShell is highlighted as a primary method, and the deployment link for Resource Manager templates points to a PowerShell-based deployment guide. There are no explicit Linux shell (bash) or cross-platform CLI examples, and PowerShell is mentioned before CLI in some sections. The documentation does not provide parity for Linux users or those using bash scripts.
Recommendations
  • Add explicit bash/Azure CLI examples for all operations currently shown with PowerShell.
  • Ensure that Azure CLI instructions are presented before or alongside PowerShell instructions, as CLI is cross-platform.
  • Update deployment links to include both PowerShell and Azure CLI (bash) guides.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and provide sample commands for each.
  • Consider adding a table or section comparing PowerShell and CLI usage for common tasks.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Windows-based validation steps (creating a Windows VM and using Windows command line), exclusively using Azure PowerShell for CLI examples, and omitting equivalent Linux instructions or examples. There are no references to Linux tools, Azure CLI, or Linux VM creation, and all command-line validation assumes a Windows environment.
Recommendations
  • Add Azure CLI examples alongside Azure PowerShell for creating private endpoints, as Azure CLI is cross-platform and widely used on Linux.
  • Include instructions for creating and validating with a Linux virtual machine (e.g., Ubuntu) in Azure, with appropriate shell commands (e.g., using bash and nslookup).
  • Present both Windows and Linux validation steps, such as connecting via SSH and running nslookup from a Linux shell.
  • Avoid assuming the reader is using Windows; use neutral language and provide parity in examples for both platforms.
  • Reference Linux documentation links where appropriate, such as 'Create a Linux virtual machine in the Azure portal'.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-migrate-azure-credentials.md ...bus-messaging/service-bus-migrate-azure-credentials.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits subtle Windows bias by consistently referencing Windows-centric tools and development environments (Visual Studio, Azure PowerShell) before or alongside cross-platform options. The authentication instructions mention Visual Studio and Azure PowerShell as primary tools for local development, with IntelliJ as a secondary mention. There are no explicit Linux-specific examples or mentions of Linux-native tools (such as bash, zsh, or Linux desktop environments). The Azure CLI is used throughout, which is cross-platform, but the overall narrative and tool recommendations lean toward Windows-first developer experiences.
Recommendations
  • Explicitly mention Linux and macOS as supported development environments in local development sections.
  • Provide examples or screenshots using Linux-native tools (e.g., GNOME Terminal, VS Code on Linux, bash shell) alongside Visual Studio and PowerShell.
  • List Azure CLI before Windows-specific tools (Visual Studio, PowerShell) when describing authentication options.
  • Include troubleshooting notes or tips for Linux users (e.g., credential caching, environment variable setup).
  • Reference cross-platform editors (VS Code, JetBrains IDEs) equally with Visual Studio.
  • Add a note confirming that all CLI commands work on Linux/macOS and provide any OS-specific caveats if relevant.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-service-endpoints.md ...service-bus-messaging/service-bus-service-endpoints.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Azure PowerShell and references to PowerShell commands before mentioning Azure CLI. There are no explicit Linux shell (bash) examples, nor are there instructions for Linux-specific tools or environments. The Resource Manager template and portal instructions are platform-neutral, but the command-line guidance leans toward Windows/PowerShell usage, with CLI coverage present but not emphasized or illustrated with examples.
Recommendations
  • Add explicit bash/Azure CLI examples for all operations currently shown with PowerShell.
  • Ensure that Azure CLI instructions are presented before or alongside PowerShell, not after.
  • Include notes or guidance for Linux/macOS users, such as installation steps for Azure CLI and usage in bash/zsh.
  • Where screenshots or UI references are given, clarify that the Azure portal is cross-platform and accessible from any OS.
  • Provide parity in example scripts, showing both PowerShell and bash/CLI equivalents for key tasks.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-messaging-exceptions-latest.md ...s-messaging/service-bus-messaging-exceptions-latest.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the troubleshooting section for SocketException, where only a PowerShell example (nslookup) is provided and the command prompt path (PS C:\>) is shown. There are no equivalent Linux/macOS command examples (e.g., dig, host, nslookup on bash), nor is there mention of Linux troubleshooting patterns. The documentation also references .NET and Windows-centric concepts (ServicePointManager, OS update) without clarifying cross-platform applicability, but the most direct evidence is the exclusive use of Windows/PowerShell tools for DNS resolution.
Recommendations
  • Provide equivalent Linux/macOS command examples for DNS resolution (e.g., 'nslookup', 'dig', or 'host' in bash/zsh).
  • When showing PowerShell or Windows command prompt examples, also show the corresponding bash/zsh shell prompt and output.
  • Clarify that troubleshooting steps apply to all platforms, and note any platform-specific differences.
  • Explicitly mention cross-platform compatibility for .NET client libraries and exception handling.
  • Add troubleshooting guidance for common Linux networking issues (e.g., checking /etc/resolv.conf, using 'ping', 'traceroute').
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-nodejs-how-to-use-topics-subscriptions.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-nodejs-how-to-use-topics-subscriptions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. It references Windows-specific tools (e.g., Windows PowerShell) and deployment patterns, and provides links to Windows-centric instructions before Linux equivalents. There are no explicit Linux or cross-platform command-line examples (e.g., Bash, Linux terminal), and the language around 'command prompt' and 'Visual Studio Code' is generic but leans toward Windows conventions. The page lacks explicit Linux instructions or parity in deployment and environment setup examples.
Recommendations
  • Add explicit Linux/macOS instructions for creating and running Node.js applications, including terminal commands and environment setup.
  • Provide links to Linux/macOS deployment guides alongside Windows PowerShell guides, and mention them equally or in parallel.
  • Replace or supplement 'command prompt' language with 'terminal' and clarify that commands work on Windows, Linux, and macOS.
  • Include examples or notes for using Bash or other Linux shells where appropriate.
  • Ensure all referenced guides (e.g., for deploying Node.js apps) have Linux/macOS equivalents and are linked from this page.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-messaging-sql-filter.md ...vice-bus-messaging/service-bus-messaging-sql-filter.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and APIs, such as PowerShell cmdlets (New-AzServiceBusRule) and .NET/C# semantics (System.Char, System.Guid, operator binding). These references are made before or in addition to cross-platform alternatives, and there is no mention of Linux-specific usage patterns or shell examples. The examples and function descriptions rely on Windows-centric terminology and technologies, potentially making it less accessible for Linux users.
Recommendations
  • Include Linux shell (bash) examples for CLI usage, such as az servicebus topic subscription rule create.
  • Reference cross-platform SDKs and usage patterns (e.g., Python, Go) alongside .NET, Java, and JavaScript.
  • Clarify that .NET/C# semantics are implementation details and provide equivalent explanations for other platforms.
  • Add explicit notes or sections for Linux/macOS users, including any differences or considerations.
  • Avoid listing PowerShell or Windows tools before cross-platform alternatives; present them together or in platform-specific subsections.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The tutorial demonstrates a Windows bias by exclusively referencing Windows tools and workflows, such as Command Prompt and PowerShell, and requiring Visual Studio (Windows-centric) for .NET development. There are no Linux or cross-platform instructions for running the sample code, installing prerequisites, or using equivalent Linux tools (e.g., Bash, VS Code, .NET CLI on Linux). All command-line examples assume a Windows environment, and there is no mention of Linux or macOS compatibility or alternative steps.
Recommendations
  • Add explicit instructions for Linux and macOS users, including how to install .NET SDK and run the sample code using Bash or other Unix shells.
  • Mention and provide examples using VS Code or other cross-platform editors, not just Visual Studio.
  • Include Linux/macOS equivalents for command-line steps (e.g., cloning the repo, building, and running the app).
  • Clarify that the .NET code and Azure Service Bus SDK are cross-platform, and provide troubleshooting tips for non-Windows environments.
  • Avoid referencing Windows-specific tools (e.g., Notepad) or provide alternatives (e.g., nano, vim, or text editors available on Linux/macOS).
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/test-locally-with-service-bus-emulator.md ...us-messaging/test-locally-with-service-bus-emulator.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting Windows and PowerShell instructions first and in greater detail, including explicit steps for opening PowerShell and using WSL. Linux/macOS instructions are less detailed and lack equivalent step-by-step guidance. Windows-specific tools (PowerShell, WSL) are mentioned and explained, while Linux-native workflows are not described in depth. File path examples and environment variable notes prioritize Windows conventions, with Linux alternatives only implied.
Recommendations
  • Provide step-by-step Linux and macOS instructions equivalent to the Windows walkthrough, including terminal commands and navigation.
  • Include Linux/macOS file path examples and environment variable usage alongside Windows examples.
  • Present Linux/macOS instructions before or alongside Windows instructions to avoid Windows-first ordering.
  • Mention Linux-native tools and workflows explicitly (e.g., bash, standard Linux terminal usage) rather than focusing on WSL for Windows.
  • Ensure parity in troubleshooting and verification steps for Linux/macOS users, not just Docker Desktop on Windows.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-auth-rule.md ...ng/service-bus-resource-manager-namespace-auth-rule.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented first in the deployment commands section, and the 'Next steps' section prioritizes PowerShell and Windows-centric tools (Service Bus Explorer). While Azure CLI is included, the CLI example uses the deprecated 'azure' command rather than the modern 'az', and does not highlight Linux/Mac usage or shell integration. There are no Linux-specific or cross-platform management tool examples, and the documentation references PowerShell management articles before CLI equivalents.
Recommendations
  • Present Azure CLI examples before PowerShell, using the modern 'az' command syntax.
  • Explicitly mention that Azure CLI works on Linux, Mac, and Windows, and provide shell-specific usage notes.
  • Include cross-platform management tool examples (e.g., Azure CLI, REST API, or SDKs) in the 'Next steps' section.
  • Reference CLI-based management articles alongside or before PowerShell articles.
  • Add notes or examples for Linux/Mac users, such as using bash/zsh, and clarify that Service Bus Explorer is a Windows-only tool.
  • Ensure parity in troubleshooting and advanced usage examples for both CLI and PowerShell.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-sas.md ...main/articles/service-bus-messaging/service-bus-sas.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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. It mentions Azure PowerShell before Azure CLI when discussing key regeneration, and references PowerShell cmdlets directly. The only code sample provided is in C#, a language most commonly associated with Windows development, and the AMQP library example is for .NET. There are no Linux-specific command-line examples, nor are there any explicit references to Linux tools or shell scripting. The documentation does mention Azure CLI, but only after PowerShell, and does not provide any Bash or Linux shell examples for SAS token generation or management.
Recommendations
  • Provide explicit Bash/Linux shell examples for SAS token generation and management, including using openssl or curl.
  • Include Python or JavaScript code samples for SAS token generation, as these languages are popular on Linux and cross-platform.
  • Mention Azure CLI before or alongside PowerShell, and provide step-by-step CLI instructions with sample output.
  • Reference Linux tools (e.g., base64, openssl) for cryptographic operations and token manipulation.
  • Clarify that all operations can be performed on Linux/macOS as well as Windows, and link to cross-platform SDKs and libraries.
  • Add a section or note on using Service Bus from Linux environments, including Docker containers and cloud-native scenarios.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-topic-with-rule.md ...service-bus-resource-manager-namespace-topic-with-rule.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. PowerShell is presented before Azure CLI in the deployment commands section, and a dedicated link for managing Service Bus with PowerShell is included in 'Next steps'. The Service Bus Explorer tool, which is Windows-only, is mentioned as a management option, with no Linux-native alternatives listed. While Azure CLI is included and cross-platform, the ordering and tool recommendations favor Windows users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred for Linux/macOS users.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows in the deployment section.
  • Include links to Linux-friendly Service Bus management tools (e.g., az CLI, SDKs, or third-party cross-platform GUIs) alongside Service Bus Explorer.
  • Add a section or note on using Bash scripts for deployments, or reference automation options for Linux environments.
  • Ensure parity in 'Next steps' by including articles or guides for managing Service Bus with Azure CLI and SDKs on Linux.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/transport-layer-security-configure-minimum-version.md ...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-08 00:53
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 tool examples (ARMClient.exe), referencing Windows-centric patterns first, and omitting Linux-native alternatives or examples for key steps such as bearer token acquisition and ARM API querying.
Recommendations
  • Include Linux-native examples for acquiring a bearer token, such as using Azure CLI (`az account get-access-token`) or `curl`/`jq` for REST API calls.
  • Provide cross-platform instructions for ARM API queries, e.g., using `curl` or `httpie` on Linux/macOS.
  • Mention Linux equivalents for ARMClient.exe, or clarify that ARMClient is Windows-only and suggest alternatives.
  • Balance PowerShell examples with Bash/Azure CLI examples, especially for scripting and automation tasks.
  • Explicitly state platform compatibility for each tool or script, and provide guidance for both Windows and Linux users.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-troubleshooting-guide.md ...ice-bus-messaging/service-bus-troubleshooting-guide.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias in several areas. Troubleshooting steps and diagnostic commands frequently present Windows/PowerShell tools (e.g., 'tnc', 'psping.exe') before or instead of Linux equivalents. Windows-specific tools are referenced (Sysinternals, Visual Studio), and .NET/PowerShell patterns dominate code and logging examples. Linux alternatives (e.g., 'telnet') are mentioned but often after Windows commands, and some tools (like 'psping.exe') lack clear Linux equivalents or guidance. There are few, if any, examples for Linux-specific workflows, and the documentation assumes familiarity with Windows-centric environments.
Recommendations
  • Present Linux and Windows troubleshooting commands side-by-side, with equal prominence.
  • Include Linux-native tools (e.g., 'nc', 'ss', 'tcpdump') and provide installation instructions where appropriate.
  • Offer examples for Bash, systemd, and other common Linux patterns in addition to PowerShell and .NET.
  • Reference cross-platform tools and frameworks (e.g., Application Insights SDK for Java/Python, OpenTelemetry for multiple languages) and link to their documentation.
  • Avoid assuming Visual Studio or Windows-only development environments; mention VS Code, JetBrains Rider, or CLI workflows.
  • Where Windows-specific tools are referenced (e.g., 'psping.exe'), suggest Linux alternatives or note their absence.
  • Ensure parity in troubleshooting steps, logging, and diagnostics for both Windows and Linux users.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (Azure PowerShell, Service Bus Explorer) and listing PowerShell management before CLI alternatives. There are no explicit Linux or cross-platform command-line examples for deploying or managing Service Bus resources, and the guidance assumes use of the Azure Portal or Windows tools, with no mention of Linux-specific workflows or screenshots.
Recommendations
  • Add explicit Azure CLI examples for deploying and managing Service Bus resources, with commands runnable on Linux, macOS, and Windows.
  • Include references and links to Azure CLI documentation before or alongside PowerShell documentation.
  • Provide screenshots or instructions that are platform-neutral, or include Linux/macOS variants where UI differs.
  • Mention cross-platform tools (such as az CLI) in the main flow, not just as a footnote.
  • Ensure that management and cleanup instructions include CLI commands as alternatives to portal navigation.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by primarily referencing the Azure portal (a GUI tool most closely associated with Windows workflows), providing only .NET/C# code samples (which are most common on Windows), and omitting Linux-specific examples or command-line authentication flows. While Azure CLI is mentioned in the 'Next steps', the main authentication and role assignment instructions focus on portal and .NET SDK usage, with no parity for Linux-native tools, languages, or shell environments.
Recommendations
  • Add equivalent authentication code samples using cross-platform languages such as Python (with azure-identity and azure-servicebus), Java, or Node.js.
  • Include examples of using Azure CLI (az login, az ad sp create-for-rbac, etc.) for authentication and role assignment, showing commands runnable on Linux/macOS.
  • Provide guidance for authenticating from Linux-based environments, such as using managed identities on Linux VMs, containers, or Azure Functions running on Linux.
  • Reference Linux-friendly editors and environments (e.g., VS Code, bash) alongside or instead of Windows-centric tools.
  • Ensure that all screenshots and step-by-step instructions are not specific to the Windows Azure portal experience, or clarify that the portal is cross-platform.
  • Where .NET is used, add parallel samples for other languages/platforms that are popular on Linux.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by providing all command-line examples exclusively in PowerShell, referencing PowerShell cmdlets (e.g., New-AzResourceGroupDeployment, Set-AzureRmKeyVaultAccessPolicy) without Bash or Linux shell equivalents. There are no explicit Linux/Unix shell examples, and the use of PowerShell is presented as the default method for scripting and automation. While Azure CLI is mentioned for some vault creation steps, all automation and scripting for deployment and identity management is shown only with PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for all PowerShell commands, especially for deployment and access policy steps.
  • Explicitly mention that all PowerShell commands can be run cross-platform (if true), or clarify any Windows-specific requirements.
  • For each PowerShell example, add a corresponding Azure CLI or Bash example, and consider presenting CLI first or side-by-side.
  • Reference cross-platform tools and patterns (e.g., Azure CLI, REST API) before or alongside Windows-specific tools.
  • Add a section or note for Linux/macOS users, highlighting any differences or prerequisites.
  • Ensure that automation and scripting guidance is not limited to Windows/PowerShell, to support users on all platforms.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While most instructions are cross-platform (using Node.js, npm, and Azure CLI), there are several references that prioritize or exclusively mention Windows tools or patterns. Notably, the instructions refer to 'command prompt' (a Windows term) instead of 'terminal' or 'shell', and a key link for deploying Node.js apps points to a Windows PowerShell-based tutorial, with no equivalent Linux/Mac instructions or links. There are no explicit Linux shell or macOS Terminal examples, and the language used assumes a Windows environment.
Recommendations
  • Replace or supplement 'command prompt' with 'terminal' or 'shell' to be inclusive of Linux and macOS users.
  • Where links are provided for deploying Node.js applications (e.g., 'Node.js Cloud Service using Windows PowerShell'), add equivalent links or instructions for Linux and macOS environments.
  • Explicitly mention that all npm and Node.js commands work on Linux, macOS, and Windows, and provide example shell commands where appropriate.
  • If referencing editors, note that Visual Studio Code is cross-platform, or suggest alternatives available on Linux/macOS.
  • Review included snippets and referenced tutorials to ensure they do not contain Windows-specific commands or paths, or provide alternatives if they do.
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: 2025-07-13 21:37
Reviewed by: Unknown
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, there is a notable emphasis on PowerShell, which is traditionally a Windows-centric tool, and the PowerShell section is given equal prominence to the cross-platform Azure CLI. There are no explicit Linux shell (bash) or scripting examples, and no mention of Linux-specific tools or patterns. The ordering of sections places Azure CLI before PowerShell, which is positive, but the heavy inclusion of PowerShell commands and lack of Linux-native shell examples may make the documentation feel Windows-biased.
Recommendations
  • Add bash (Linux shell) script examples alongside Azure CLI, demonstrating how to use the CLI in a Linux environment.
  • Clarify in the PowerShell section that Azure PowerShell is available cross-platform, but also provide equivalent bash or shell scripting examples for Linux users.
  • Consider including a table or summary comparing the different approaches (Azure portal, CLI, PowerShell, ARM templates) and their platform compatibility.
  • If possible, add notes or links to Linux-specific guidance for installing and using the Azure CLI and PowerShell on Linux.
  • Ensure that future documentation includes Linux-native command-line examples where applicable, not just PowerShell.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by explicitly providing a dedicated 'Azure PowerShell' section with command references, while the 'Azure CLI' section is minimal and lacks concrete command examples. The PowerShell section is more detailed and appears after the CLI, but the CLI section is underdeveloped. There are no Linux-specific instructions or examples, and the only deployment link for Resource Manager templates points to a PowerShell-based deployment guide. No Bash or Linux shell examples are provided, and the documentation assumes familiarity with Windows-centric tools.
Recommendations
  • Provide explicit Azure CLI command examples for managing IP firewall rules, similar to the PowerShell section.
  • Include Bash/Linux shell examples for deploying ARM templates (e.g., using 'az deployment group create').
  • Ensure that deployment links reference both PowerShell and CLI (Bash) guides, or provide a cross-platform deployment section.
  • Balance the order and depth of CLI and PowerShell sections, ensuring Linux users are equally supported.
  • Add notes or examples for common Linux environments, such as using the Azure CLI in Bash or Cloud Shell.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-partitions-basic-standard.md ...vice-bus-messaging/enable-partitions-basic-standard.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but the PowerShell section is given equal prominence to the CLI section, and PowerShell is a Windows-centric tool. There are no explicit Linux shell (bash) or cross-platform scripting examples beyond Azure CLI. The PowerShell examples use Windows-style syntax (backticks for line continuation), and there is no mention of Linux-specific considerations or alternative tools. The ordering of sections (CLI before PowerShell) is good, but the presence of PowerShell as a primary method and the lack of bash or Linux-native scripting tips indicate a mild Windows bias.
Recommendations
  • Clearly indicate that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
  • Add bash/zsh shell examples or notes for Linux users, especially for scripting or automation.
  • Mention that PowerShell Core is available cross-platform, or clarify that the examples use Windows PowerShell syntax.
  • Consider adding a note about line continuation differences (backtick vs. backslash) between PowerShell and bash.
  • Ensure that all examples and instructions are tested and presented in a way that is accessible to both Windows and Linux users.
GitHub Create Pull Request
← Previous Page 6 of 16 Next →