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 151-175 of 377 flagged pages
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: 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 page demonstrates a Windows bias by referencing Windows-specific tools and workflows (e.g., Command Prompt, PowerShell, Visual Studio) exclusively or before any Linux alternatives. There are no explicit instructions or examples for Linux users, such as using Bash, VS Code, or .NET CLI on Linux. The prerequisites and step-by-step instructions assume a Windows environment, and no mention is made of cross-platform considerations.
Recommendations
  • Add explicit instructions and examples for Linux users, such as using Bash or terminal commands instead of Command Prompt/PowerShell.
  • Mention and provide steps for installing and using .NET SDK and running the sample code on Linux/macOS, including any differences in file paths or command syntax.
  • Include VS Code as an alternative to Visual Studio in the prerequisites, and provide guidance for Linux/macOS users.
  • When referencing command-line actions, use cross-platform .NET CLI commands and clarify that they work on Windows, Linux, and macOS.
  • Add screenshots or terminal output examples from Linux environments where appropriate.
  • Avoid assuming the use of Notepad or other Windows-only tools for copying/storing connection strings; suggest cross-platform alternatives.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by providing only Azure PowerShell examples for CLI-based integration, omitting equivalent Azure CLI (cross-platform) or Bash scripts. Additionally, the validation section explicitly instructs users to create a Windows VM and does not mention Linux VMs or provide Linux-specific instructions, reinforcing a Windows-first approach.
Recommendations
  • Add equivalent Azure CLI (az) command examples alongside or instead of PowerShell scripts for creating and managing private endpoints.
  • In the validation section, provide instructions for both Windows and Linux VMs, including how to run nslookup or dig on Linux.
  • When referencing VM creation, link to both Windows and Linux VM quickstart guides.
  • Ensure screenshots and UI instructions are platform-neutral or clarify when steps differ between OSes.
  • Consider including Bash script examples for automation, especially for Linux users.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-dead-letter.md ...n/articles/service-bus-messaging/enable-dead-letter.md
High Priority View Details →
Scanned: 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 detailed instructions for both Azure CLI and Azure PowerShell, but the PowerShell section is prominent and uses Windows-centric tooling. PowerShell is a Windows-first tool, and its inclusion as a primary automation method can be seen as a Windows bias, especially since there are no equivalent Bash or Linux shell script examples. The CLI examples are cross-platform, but the ordering (CLI before PowerShell) is good; however, the presence of PowerShell without any Linux shell scripting alternatives (e.g., Bash) or explicit mention of cross-platform PowerShell Core may disadvantage Linux users. There are no explicit Linux-only tools or patterns, and the documentation does not mention or show Linux-specific considerations.
Recommendations
  • Add Bash shell script examples alongside PowerShell, especially for automation scenarios.
  • Explicitly mention that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • If including PowerShell, clarify whether the examples work with PowerShell Core on Linux/macOS or are Windows-only.
  • Consider providing parity in scripting examples: for every PowerShell example, provide a Bash or shell equivalent.
  • Highlight any OS-specific considerations (if any) for using these tools on Linux.
  • If possible, add a section or note for Linux users, e.g., how to install and use Azure CLI/PowerShell on Linux.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace.md ...us-messaging/service-bus-resource-manager-namespace.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page provides only Azure PowerShell examples for deploying and managing a Service Bus namespace, with no equivalent Azure CLI (cross-platform) or Bash examples. The instructions and code blocks are PowerShell-specific, and the workflow assumes familiarity with PowerShell and Windows-centric patterns (e.g., Write-Host, Read-Host). While there is a brief mention of Azure CLI as an alternative, no CLI or Linux-native examples are provided, and PowerShell is presented as the default and primary method.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell scripts, using Bash syntax where appropriate.
  • Present both PowerShell and CLI/Bash examples side-by-side, or allow users to toggle between them.
  • Avoid assuming the use of Windows tools or PowerShell-specific commands in instructions and explanations.
  • Explicitly mention that Azure Cloud Shell supports both PowerShell and Bash, and provide guidance for both environments.
  • Ensure that Linux/macOS users can follow the quickstart without needing to adapt PowerShell scripts themselves.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented as the first and primary example for deploying the ARM template, with the Azure CLI example following. The 'Next steps' section prioritizes PowerShell-based management and does not mention Linux-specific tools or workflows. There is no explicit mention of Linux or cross-platform considerations in the deployment or management sections, and the use of PowerShell and Service Bus Explorer (a Windows desktop tool) further reinforces a Windows-centric approach.
Recommendations
  • Present Azure CLI deployment commands before or alongside PowerShell, emphasizing its cross-platform compatibility.
  • Include explicit references to Linux and macOS compatibility, especially in deployment and management sections.
  • Add examples for deploying ARM templates using Bash scripts or from Linux/macOS terminals.
  • Highlight cross-platform tools for managing Service Bus resources, such as Azure CLI, REST API, or SDKs, rather than focusing on Windows-only tools like PowerShell and Service Bus Explorer.
  • In the 'Next steps' section, provide links to CLI-based management guides and mention Service Bus management via the Azure Portal, which is OS-agnostic.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a strong bias toward Windows development environments. All instructions for creating and running the .NET applications are centered around Visual Studio, a Windows-centric IDE, with no mention of cross-platform alternatives like Visual Studio Code or JetBrains Rider. Package installation is shown exclusively using the NuGet Package Manager Console (PowerShell), with no examples for .NET CLI (dotnet) commands, which are platform-agnostic. There are no instructions or screenshots for Linux or macOS users, and the workflow assumes the user is operating within a Windows GUI environment.
Recommendations
  • Add instructions for using Visual Studio Code and/or JetBrains Rider, including how to create and run .NET console applications on Linux and macOS.
  • Provide .NET CLI (dotnet add package ...) commands as an alternative to the NuGet Package Manager Console for installing packages.
  • Include notes or screenshots for Linux/macOS environments where relevant, especially for authentication (e.g., DefaultAzureCredential) and running the sample code.
  • Clarify that Visual Studio is not required, and that the sample can be built and run on any platform supported by .NET 6+.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., port/firewall settings, credential management).
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While Azure CLI examples (cross-platform) are provided, there are several areas where Windows-specific tools and patterns are prioritized or Linux alternatives are missing. For example, the section on checking the minimum TLS version uses ARMClient.exe (a Windows executable) and PowerShell commands, with no mention of Linux-compatible alternatives. PowerShell examples are given equal prominence to Azure CLI, and the documentation refers to tools and workflows (like ARMClient.exe) that are not natively available on Linux or macOS. There are no Bash/cURL or Linux-native instructions for querying the ARM API or obtaining tokens.
Recommendations
  • Provide Linux/macOS-compatible alternatives for ARMClient.exe, such as using Azure CLI (az account get-access-token) and curl for querying the ARM API.
  • Include Bash/cURL examples alongside or before PowerShell examples when demonstrating API queries.
  • Clearly indicate which tools are cross-platform and which are Windows-only, and suggest alternatives for non-Windows users.
  • Consider reordering examples to present cross-platform or Linux-native tools first, or at least in parallel with Windows tools.
  • Add explicit notes or links for Linux/macOS users where a tool or workflow is Windows-specific.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented toward Windows and Visual Studio workflows. All instructions for creating projects, managing dependencies, and authenticating are based on Visual Studio UI and PowerShell commands. There are no instructions or examples for Linux or cross-platform .NET development (e.g., using VS Code, JetBrains Rider, or the .NET CLI). The NuGet installation steps use PowerShell exclusively, and there is no mention of how to perform equivalent steps on Linux or macOS. The use of Visual Studio sign-in for authentication assumes a Windows environment.
Recommendations
  • Add parallel instructions for Linux/macOS users, including how to use the .NET CLI (e.g., 'dotnet new console', 'dotnet add package') for project creation and package management.
  • Include examples for installing NuGet packages via the CLI (e.g., 'dotnet add package Azure.Messaging.ServiceBus') instead of only PowerShell.
  • Describe authentication options that work cross-platform, such as using Azure CLI or environment variables for DefaultAzureCredential, not just Visual Studio sign-in.
  • Mention and provide examples for alternative editors like VS Code or JetBrains Rider, and clarify that the code samples work on any OS supported by .NET.
  • Where UI steps are described (e.g., creating projects), provide equivalent CLI commands for non-Windows users.
  • Explicitly state that the tutorial is cross-platform and highlight any OS-specific steps or requirements.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by presenting Windows and PowerShell instructions before Linux/macOS equivalents, referencing Windows-specific tools (WSL, PowerShell), and providing more detailed, step-by-step guidance for Windows users. Linux and macOS instructions are less detailed and sometimes only mentioned in passing. Some file path examples and configuration notes are Windows-centric, and Linux-specific nuances (such as file permissions or shell differences) are not addressed.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions to ensure parity.
  • Provide equally detailed, step-by-step instructions for Linux and macOS users, including terminal commands and navigation.
  • Avoid assuming use of PowerShell or WSL; provide native Linux/macOS shell commands and workflows.
  • Include Linux/macOS file path examples (using forward slashes) alongside Windows examples.
  • Explicitly mention any Linux/macOS prerequisites or dependencies (such as bash, chmod, or Docker Compose installation methods).
  • Ensure that all scripts and configuration steps are validated and described for Linux/macOS environments, not just Windows.
  • Add troubleshooting tips or notes specific to Linux/macOS where relevant.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/deprecate-service-bus-management.md ...vice-bus-messaging/deprecate-service-bus-management.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides extensive mapping between deprecated and current Azure Service Manager and Resource Manager APIs, with a strong focus on PowerShell cmdlets for both old and new command sets. There are no examples or references to cross-platform CLI tools (such as Azure CLI), Bash, or Linux-native workflows. All scripting and automation examples are PowerShell-based, which is traditionally associated with Windows environments, though it is now cross-platform. There is no mention of Linux, macOS, or alternative scripting environments.
Recommendations
  • Add equivalent Azure CLI (az) command mappings alongside PowerShell cmdlets, as Azure CLI is widely used on Linux and macOS.
  • Provide Bash or shell script examples for common operations, or at least reference their availability.
  • Explicitly state that PowerShell is available cross-platform, but also highlight and link to documentation for Linux/macOS users.
  • Include a section or table mapping deprecated Service Manager commands to both PowerShell and Azure CLI equivalents.
  • Mention other automation options (e.g., ARM templates, Bicep, SDKs) that are platform-agnostic.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-dead-letter.md ...n/articles/service-bus-messaging/enable-dead-letter.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples, but the PowerShell section is prominent and detailed, reflecting a Windows-centric approach. PowerShell is a Windows-native tool (though now cross-platform), and its inclusion before any Linux shell scripting or bash alternatives may signal a Windows-first bias. There are no bash or Linux shell script examples, and no mention of Linux-specific tools or considerations. The CLI examples are cross-platform, but the documentation does not explicitly highlight Linux usage or parity.
Recommendations
  • Add bash or Linux shell script examples alongside PowerShell, especially for automation scenarios.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample terminal prompts (e.g., $ for bash, PS> for PowerShell) to clarify context.
  • If PowerShell is included, consider also including bash equivalents for common tasks, or at least reference that PowerShell is available cross-platform.
  • In sections where PowerShell is used, add a note or link to guidance for using Azure CLI or bash on Linux.
  • Ensure that any references to tools or scripting environments are balanced between Windows and Linux, or clarify their cross-platform support.
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-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example Windows First Dotnet Heavy
Summary
The documentation page demonstrates bias towards Windows environments by providing only .NET (C#) code samples, referencing Windows-centric libraries (Azure.Messaging.ServiceBus, Azure.Identity), and omitting equivalent Linux or cross-platform code examples (such as Python, Java, or Node.js). The registration and authentication steps are described using the Azure portal UI, which is platform-agnostic, but the only code sample is for .NET, which is most commonly associated with Windows. Additionally, in the 'Next steps' section, PowerShell is mentioned before Azure CLI, which is more commonly used on Linux/macOS.
Recommendations
  • Add code samples for other popular cross-platform languages such as Python (using azure-identity and azure-servicebus), Java, and Node.js to demonstrate authentication from Linux or macOS environments.
  • Include explicit instructions or examples for using Azure CLI (which is cross-platform) to perform authentication and role assignments, and consider listing Azure CLI before PowerShell in the 'Next steps' section.
  • Mention that the .NET libraries are cross-platform, but also provide links or references to SDKs and samples for other languages.
  • If possible, include a table or section comparing authentication approaches across different operating systems and programming languages.
  • Ensure that screenshots and UI steps are clearly marked as platform-agnostic, and provide command-line alternatives for users who prefer not to use the Azure portal.
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-12 23:44
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, the PowerShell section is prominent and detailed, and PowerShell is a Windows-centric tool. There are no explicit Linux shell (bash) or cross-platform scripting examples outside of Azure CLI. The ordering places Azure CLI before PowerShell, but the PowerShell section is equally detailed and assumes familiarity with Windows scripting patterns. No Linux-specific tools or shell scripts are mentioned, and there is no explicit mention of running PowerShell Core cross-platform.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows.
  • Add bash shell examples alongside Azure CLI commands to demonstrate usage in a typical Linux environment.
  • If including PowerShell, specify that PowerShell Core is available cross-platform, or clarify when examples are Windows-specific.
  • Avoid assuming PowerShell as the default scripting tool; present CLI/bash examples first or in parallel.
  • Consider including notes or links for Linux users on installing and using the Azure CLI and PowerShell Core.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-auto-forward.md .../articles/service-bus-messaging/enable-auto-forward.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides detailed instructions for enabling auto forwarding in Azure Service Bus using the Azure portal, Azure CLI, Azure PowerShell, ARM templates, and several programming languages. However, there is a notable Windows bias: PowerShell is given a dedicated section with full examples, and Windows-centric tools (PowerShell) are presented before cross-platform programming language SDKs. There is no mention of Bash scripting or Linux-native automation tools, and the PowerShell section appears before the programming language SDKs, which are cross-platform. The Azure CLI section is present and uses Unix-style line continuations, but there is no explicit mention of Linux or macOS environments, nor are there Bash or shell script examples.
Recommendations
  • Add explicit Bash or shell script examples for common automation scenarios, especially for updating or creating Service Bus resources.
  • Clarify in the Azure CLI section that the commands are cross-platform and provide both Windows (using `^` for line continuation) and Linux/macOS (using `\`) variants if necessary.
  • Consider adding a section or note on using Azure CLI and SDKs on Linux/macOS, including any prerequisites or differences.
  • Reorder the sections so that cross-platform tools (Azure CLI, SDKs) are presented before Windows-specific tools (PowerShell), or at least clarify the cross-platform nature of each tool.
  • If possible, mention or link to Linux-native automation options (such as Bash scripts or Ansible modules) for managing Azure Service Bus.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/entity-suspend.md .../main/articles/service-bus-messaging/entity-suspend.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a detailed PowerShell example for changing the status of Service Bus queues, but does not provide equivalent command-line examples for Linux users (e.g., Azure CLI, Bash). The only code sample is in PowerShell, which is a Windows-centric tool, and there is no mention or demonstration of how to perform the same operation on Linux or macOS platforms. This creates a bias towards Windows users and leaves Linux users without clear guidance.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands shown, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that the operations can be performed using Azure CLI, and provide sample commands.
  • Where possible, provide Bash script examples alongside PowerShell to ensure parity.
  • Structure sections so that cross-platform tools (like Azure CLI) are presented before or alongside Windows-specific tools (like PowerShell).
  • Include a note clarifying platform compatibility for each tool and example.
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-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a significant Windows/Powershell bias. All imperative command-line examples for deploying templates, managing identities, and setting access policies use Azure PowerShell cmdlets, with no Bash, Linux shell, or cross-platform Azure CLI equivalents provided for these critical steps. While some resource creation steps reference Azure CLI, all step-by-step automation and scripting guidance defaults to PowerShell. This may hinder Linux or macOS users, who are more likely to use Bash and Azure CLI. Additionally, PowerShell is mentioned before CLI in several places, and no Linux-specific instructions or screenshots are present.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell commands, especially for template deployments, identity management, and key vault access policy configuration.
  • Include Bash shell command examples alongside PowerShell, or use CLI as the primary example for cross-platform parity.
  • When referencing both PowerShell and CLI, present CLI first or side-by-side to avoid the impression of Windows-first bias.
  • Add a note or section clarifying that all steps can be performed on Linux/macOS using Azure CLI, and link to relevant CLI documentation.
  • Where screenshots are used, ensure they are not Windows-specific or supplement with cross-platform visuals.
  • Audit for any references to Windows-only tools or patterns and replace with cross-platform alternatives where possible.
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-12 23:44
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, despite PowerShell being primarily associated with Windows environments. There is no explicit mention of Linux shell (bash) or cross-platform scripting alternatives in the PowerShell section, and no guidance for Linux users on how to adapt PowerShell commands. The CLI examples are cross-platform, but the presence and prominence of PowerShell may suggest a Windows-centric approach. Additionally, the PowerShell section appears before the ARM template section, which is platform-neutral.
Recommendations
  • Clearly indicate that Azure CLI commands work on all platforms (Windows, Linux, macOS), and consider placing the CLI section before PowerShell to emphasize cross-platform support.
  • In the PowerShell section, note that PowerShell Core is available cross-platform, but that most Linux users will prefer CLI or bash.
  • Add explicit bash shell examples or notes for Linux users where relevant, especially for scripting scenarios.
  • Review the ordering of sections to ensure that cross-platform tools (CLI, ARM templates) are not de-emphasized compared to Windows-centric tools.
  • Consider adding a table or quick-reference that maps each method (Portal, CLI, PowerShell, ARM) to its platform compatibility.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/includes/service-bus-event-grid-prerequisites.md ...aging/includes/service-bus-event-grid-prerequisites.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE), Solution Explorer, and .sln files, with no mention of Linux-compatible tools or workflows. There are no instructions or examples for Linux users, such as using VS Code, .NET CLI, or alternative editors, nor are there any Linux-specific setup or run instructions.
Recommendations
  • Add instructions for Linux users, such as how to open and run the sample using the .NET CLI (e.g., 'dotnet build', 'dotnet run') and editors like VS Code.
  • Mention cross-platform tools and workflows alongside Windows-specific ones, ensuring parity in steps and screenshots.
  • Provide alternative instructions for opening and editing the project without Visual Studio, such as using VS Code or JetBrains Rider.
  • Include notes or sections that explicitly address Linux and macOS users, clarifying any differences in setup or execution.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/message-sessions.md ...ain/articles/service-bus-messaging/message-sessions.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing 'Azure portal, PowerShell, CLI, Resource Manager template, .NET, Java, Python, and JavaScript' as ways to enable message sessions, with PowerShell (a Windows-centric tool) mentioned before the cross-platform Azure CLI. There are no explicit Linux-specific instructions or examples, and the ordering of tools and languages tends to prioritize Windows-first technologies. The absence of Linux shell (bash) or cross-platform command-line examples further highlights this bias.
Recommendations
  • Reorder the list of tools to mention cross-platform options (such as Azure CLI) before Windows-specific ones (like PowerShell).
  • Provide explicit Linux/bash command examples alongside or before PowerShell examples.
  • Clarify which tools and instructions are cross-platform and which are Windows-only.
  • Include references to Linux package managers or shell environments where relevant.
  • Ensure that all code samples and setup instructions are validated on both Windows and Linux platforms.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-dead-letter-queues.md ...ervice-bus-messaging/service-bus-dead-letter-queues.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing .NET APIs and GUI tools (Service Bus Explorer) that are most accessible on Windows. There is a lack of Linux- or cross-platform-specific examples, and no mention of command-line or scripting approaches (e.g., Bash, Python, or PowerShell) for Linux users. The only CLI example is Azure CLI, which is cross-platform, but the overall focus is on Windows-centric tools and patterns.
Recommendations
  • Include code examples for moving messages to the DLQ and resubmitting them using cross-platform SDKs (e.g., Python, Java, Node.js) in addition to .NET.
  • Highlight command-line tools and scripting approaches (e.g., Bash scripts using Azure CLI or REST API) for Linux users.
  • Mention and provide examples for open-source or cross-platform tools for managing Service Bus DLQs, if available.
  • Ensure that GUI tools like Service Bus Explorer are clearly marked as Windows-only (if applicable), and suggest alternatives for Linux/macOS users.
  • Balance .NET-specific guidance with equivalent instructions for other languages and platforms.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell CLI examples for automation, omitting equivalent Azure CLI (cross-platform) or Bash scripts. Additionally, the validation steps explicitly instruct users to create and use a Windows virtual machine, with no mention of Linux alternatives or parity. This prioritizes Windows tools and environments, leaving Linux users without direct guidance.
Recommendations
  • Provide equivalent Azure CLI (az) and/or Bash examples alongside the PowerShell automation steps, ensuring Linux and macOS users have clear instructions.
  • In the validation section, offer instructions for creating and using a Linux virtual machine, including relevant command-line examples (e.g., using dig or nslookup on Linux).
  • Where possible, use neutral language and cross-platform tools (e.g., Azure CLI, REST API) as the primary automation example, or present both Windows and Linux options in parallel.
  • Explicitly state that the steps can be performed from any supported OS, and link to both Windows and Linux VM creation guides.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-dotnet-multi-tier-app-using-service-bus-queues.md ...ice-bus-dotnet-multi-tier-app-using-service-bus-queues.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
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 Cloud Service roles, with all instructions, screenshots, and tooling references assuming a Windows OS. There are no Linux or cross-platform development instructions, nor are alternative tools (such as VS Code, CLI, or Docker) mentioned. The use of the Azure Compute Emulator and the requirement to run Visual Studio as administrator further reinforce the Windows-only focus.
Recommendations
  • Add parallel instructions and examples for developing and running the application on Linux and macOS, using cross-platform tools such as VS Code, .NET CLI, and Docker.
  • Include steps for setting up the development environment on Linux (e.g., installing the .NET SDK, using the Azure CLI for resource management, and configuring environment variables).
  • Replace or supplement Visual Studio-specific steps and screenshots with instructions for using VS Code or JetBrains Rider, and provide CLI commands for project creation, dependency management, and running the application.
  • Document how to run and debug the application locally without the Azure Compute Emulator, which is Windows-only, possibly using Docker Compose or Azure Functions Core Tools.
  • Ensure that all code snippets and configuration steps are OS-agnostic, and explicitly call out any platform-specific requirements or alternatives.
  • Provide guidance on how to view logs and trace output on Linux, replacing references to Windows notification area and emulator UI with cross-platform solutions.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-amqp-dotnet.md ...icles/service-bus-messaging/service-bus-amqp-dotnet.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows and .NET, with all examples and configuration instructions focused on the WindowsAzure.ServiceBus .NET Framework library. There are no Linux-specific instructions, cross-platform considerations, or examples for non-Windows environments. The documentation assumes use of Windows tools (e.g., Azure portal) and .NET APIs, with no mention of Linux command-line tools, PowerShell alternatives, or cross-platform SDKs.
Recommendations
  • Add explicit guidance or examples for using the Service Bus library from Linux environments, such as with .NET Core/.NET 5+ on Linux.
  • Mention and provide examples for cross-platform SDKs (e.g., Azure.Messaging.ServiceBus) that work on Linux, and clarify platform compatibility.
  • Include instructions for obtaining connection strings and managing Service Bus namespaces using cross-platform tools like Azure CLI or Azure Cloud Shell, not just the Azure portal.
  • Where possible, provide code/configuration examples that are OS-agnostic or explicitly show both Windows and Linux usage.
  • Clarify in the introduction that while the legacy library is Windows/.NET Framework-specific, modern alternatives are available for Linux and cross-platform development.
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-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides explicit instructions and command references for Azure PowerShell (a Windows-centric tool) but does not provide equivalent, detailed examples for Azure CLI (which is cross-platform and preferred on Linux). The PowerShell section lists specific cmdlets, while the Azure CLI section only mentions the command group without concrete examples. There are no Linux- or bash-specific instructions or screenshots, and the only deployment link for ARM templates points to a PowerShell-based deployment guide. This creates a Windows-first impression and lacks Linux parity.
Recommendations
  • Add concrete Azure CLI command examples for managing IP firewall rules, similar to the PowerShell cmdlet examples.
  • Provide bash shell examples for deploying ARM templates, or link to cross-platform deployment instructions (e.g., az deployment group create).
  • Ensure that CLI examples appear before or alongside PowerShell examples to avoid a Windows-first ordering.
  • Include notes or sections highlighting that all steps can be performed on Linux/macOS using Azure CLI.
  • Where screenshots or UI references are given, clarify that the Azure portal is OS-agnostic.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and workflows (Command Prompt, PowerShell) as the default environment for running commands. There are no explicit instructions or examples for Linux or macOS users, such as using a Bash shell or Linux-specific command-line conventions. The prerequisites focus on Visual Studio (a Windows-centric IDE), and all command-line instructions assume a Windows environment. No mention is made of cross-platform .NET development tools or editors, nor are alternative shell environments or package managers referenced.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, such as using Bash or zsh shells.
  • Mention and provide examples using cross-platform .NET tools (e.g., .NET CLI on Linux/macOS) and editors like VS Code.
  • Replace 'Command Prompt or PowerShell' with 'terminal' or 'command line', and clarify that the steps work on all major platforms.
  • Include Linux/macOS-specific notes for file paths, navigation, and command syntax where appropriate.
  • List prerequisites for Linux/macOS (e.g., .NET SDK installation instructions for those platforms).
  • Reference cross-platform Service Bus management tools (e.g., Azure CLI) and show parity in usage.
GitHub Create Pull Request
← Previous Page 7 of 16 Next →