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 176-200 of 377 flagged pages
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: 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 provides examples for setting Azure Service Bus subscription filters. While it covers the Azure portal, Azure CLI, and Azure PowerShell, the only detailed code samples are in .NET/C#, with no Linux-specific shell (bash) or cross-platform language examples. PowerShell is mentioned as a primary automation tool alongside CLI, and .NET is the only language with inline code samples, which may implicitly favor Windows users. There are no explicit Linux or bash scripting examples for managing filters, and the ordering of sections (CLI, then PowerShell) is neutral, but the lack of bash or Python code samples is a gap.
Recommendations
  • Add bash shell examples using Azure CLI for common filter management tasks, including end-to-end scripts for creating topics, subscriptions, and rules.
  • Include code samples in at least one cross-platform language such as Python or JavaScript, demonstrating filter creation and message sending/receiving.
  • Provide explicit notes or callouts that all Azure CLI commands work identically on Linux, macOS, and Windows.
  • Balance PowerShell examples with bash equivalents, especially for automation scenarios.
  • Consider reordering or grouping CLI and PowerShell sections under a broader 'Command-line tools' heading to emphasize parity.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-end-to-end-tracing.md ...ervice-bus-messaging/service-bus-end-to-end-tracing.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 Powershell Heavy
Summary
The documentation page demonstrates a strong bias toward Windows and .NET environments. All code samples, configuration guidance, and tracing instrumentation are exclusively provided for .NET (C#), ASP.NET, and Microsoft Application Insights, with no mention of equivalent approaches for Linux, non-.NET languages, or cross-platform tools. There are no examples or references for Linux environments, open-source tracing tools (other than a brief mention of OpenTelemetry in .NET), or how to achieve similar diagnostics in non-Windows ecosystems.
Recommendations
  • Add equivalent code samples and configuration instructions for Linux environments, such as using Python, Java, or Node.js Service Bus SDKs.
  • Include examples of integrating with open-source tracing and monitoring tools commonly used on Linux, such as Jaeger, Zipkin, or Prometheus, alongside Application Insights.
  • Provide guidance for setting up distributed tracing and diagnostics in cross-platform scenarios, including Docker and Kubernetes deployments.
  • Mention and demonstrate the use of OpenTelemetry in non-.NET languages, and show how to propagate trace context across heterogeneous services.
  • Ensure that references to SDKs, libraries, and tools are not limited to Windows/.NET, and present Linux/cross-platform options either first or in parallel.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-geo-dr.md ...n/articles/service-bus-messaging/service-bus-geo-dr.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example Windows First Powershell Heavy
Summary
The documentation page exhibits a Windows bias by primarily referencing the Azure Portal (a GUI often used on Windows), mentioning PowerShell and CLI as alternatives but not providing explicit Linux/bash examples or parity. The only code samples referenced are .NET-based (a traditionally Windows-centric stack, though now cross-platform), and there is no mention of Linux-specific tools, shell commands, or patterns. PowerShell is mentioned before CLI, and there are no bash or Linux-native command examples. The documentation assumes a Windows/Portal-centric workflow and does not address Linux users directly.
Recommendations
  • Provide explicit Azure CLI (bash) command examples alongside or before PowerShell examples for all setup and failover steps.
  • Include Linux shell (bash) usage instructions for common tasks such as pairing, failover, and monitoring.
  • Reference cross-platform SDKs and samples (e.g., Python, Java) in addition to .NET, and link to relevant repositories.
  • Clarify that all management operations can be performed from Linux environments and provide step-by-step Linux terminal instructions.
  • Ensure that any mention of PowerShell is balanced with equivalent Azure CLI/bash examples, and avoid listing PowerShell first unless it is the only supported method.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-geo-replication.md ...s/service-bus-messaging/service-bus-geo-replication.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 Tools Windows First
Summary
The documentation page predominantly references tools and patterns common in Windows environments, such as the use of 'ping' (with Windows syntax) and screenshots from the Azure Portal (which is platform-agnostic but often associated with Windows workflows). There are no explicit PowerShell or Windows-only command-line examples, but there is a notable absence of Linux-specific or cross-platform command-line examples (e.g., Bash, curl, or az CLI with Linux shell syntax). The only command-line example provided is Azure CLI, which is cross-platform, but there are no explicit Linux shell or scripting examples. Additionally, the 'ping' example is presented without clarifying its usage on Linux, and the sample code references only .NET (commonly associated with Windows), with no mention of other languages or platforms.
Recommendations
  • Provide Linux shell (bash) equivalents for command-line instructions, such as 'ping' (e.g., 'ping your-namespace-fully-qualified-name' works on both, but clarify any OS-specific differences).
  • Include examples using cross-platform tools (e.g., curl, wget) where relevant.
  • Add sample code references for other languages/platforms (e.g., Python, Java, Node.js) to ensure parity with .NET.
  • Explicitly state that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
  • Where screenshots or UI instructions are given, clarify that the Azure Portal is accessible from any OS.
  • If referencing tools or commands that behave differently on Windows vs. Linux (such as 'ping'), provide notes or examples for both.
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: 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 references both Azure CLI and PowerShell (New-AzServiceBusRule) for managing Service Bus rules, but it lists the PowerShell cmdlet after the Azure CLI command. However, the examples and references to .NET and C# semantics (such as operator binding and type conversion) are prominent, and the only explicit SDK function examples are for .NET, Java, and JavaScript. There are no Linux-specific tools or shell examples, and the PowerShell module is referenced directly, which is traditionally associated with Windows environments. The documentation does not provide Linux shell (bash) or cross-platform scripting examples, and the focus on .NET/C# semantics may be less familiar to Linux-first users.
Recommendations
  • Add explicit bash/shell examples for using az CLI to create and manage Service Bus rules, demonstrating parity with PowerShell.
  • Clarify that Azure CLI is fully cross-platform and provide usage examples in a Linux shell context.
  • Include references to Python SDK usage (which is popular on Linux) alongside .NET, Java, and JavaScript.
  • When discussing operator semantics, mention language-agnostic behavior or provide equivalent semantics for other languages (e.g., Python) to avoid .NET/C#-centric explanations.
  • If referencing PowerShell, clarify that PowerShell Core is cross-platform, or provide equivalent bash scripts for Linux users.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-messaging-sql-rule-action.md ...bus-messaging/service-bus-messaging-sql-rule-action.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 references both Azure CLI and PowerShell (New-AzServiceBusRule) tools for managing Service Bus rules, but does not provide Linux-specific examples or mention Linux tools explicitly. PowerShell, a Windows-centric tool, is mentioned in the 'Next steps' section, and .NET is listed first among SDKs, which may suggest a Windows-first perspective. No Linux shell or scripting examples are provided, and there is no mention of Linux-specific considerations.
Recommendations
  • Provide explicit Bash or Linux shell examples for managing Service Bus rules using Azure CLI.
  • List cross-platform tools (such as Azure CLI) before Windows-specific tools (like PowerShell) in the 'Next steps' section.
  • Include a note clarifying that Azure CLI is fully supported on Linux, macOS, and Windows.
  • Add links or references to Linux/macOS installation and usage guides for Azure CLI.
  • If mentioning PowerShell, clarify that PowerShell Core is cross-platform, or provide equivalent Bash examples.
  • Ensure SDK examples are balanced across languages/platforms (e.g., Python, Java, JavaScript) and not just .NET.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in its troubleshooting guidance, particularly in the section on resolving SocketException errors. The only command-line example provided is a PowerShell nslookup command with a Windows-style prompt, and there is no mention of equivalent Linux/macOS commands or shell environments. No Linux or cross-platform troubleshooting steps are offered, and the documentation assumes a Windows-centric context for command-line operations.
Recommendations
  • Provide equivalent Linux/macOS command-line examples alongside Windows/PowerShell commands (e.g., show nslookup or dig usage in bash/zsh).
  • Use neutral or cross-platform prompts (e.g., $ or #) when showing command-line examples, or show both Windows and Linux prompts.
  • Explicitly mention that troubleshooting steps apply to all platforms and clarify any platform-specific differences.
  • Include guidance for common Linux/macOS tools (such as dig, host, or nslookup) and troubleshooting patterns.
  • Review other sections for implicit Windows assumptions and ensure parity in examples and troubleshooting steps for non-Windows environments.
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-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples for all deployment, verification, and cleanup steps. There are no equivalent Azure CLI (cross-platform) or Bash examples, and PowerShell is presented as the default and only scripting environment. While a link to Azure CLI deployment is provided, no direct CLI or Linux-native instructions are included in the main flow.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all steps (deployment, verification, cleanup) to ensure parity for Linux and macOS users.
  • Present both PowerShell and CLI examples in parallel or allow users to select their preferred environment.
  • Explicitly mention that Azure Cloud Shell supports both Bash (with Azure CLI) and PowerShell, and provide guidance for both.
  • Avoid language that assumes PowerShell as the default or only shell; instead, use neutral phrasing and highlight cross-platform options.
  • Consider including Bash script snippets for users who prefer scripting in Bash with Azure CLI.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-messaging-exceptions.md ...vice-bus-messaging/service-bus-messaging-exceptions.md
High Priority View Details →
Scanned: 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 primarily by providing only Windows/Powershell command-line examples (e.g., nslookup shown as 'PS C:\> nslookup ...'), and by referencing .NET Framework APIs exclusively, which are most commonly associated with Windows. There are no equivalent Linux or cross-platform command-line examples, nor any mention of Linux-specific troubleshooting steps or tools. The documentation assumes a Windows environment for diagnostics and omits Linux or macOS parity.
Recommendations
  • For every command-line example (such as nslookup), provide both Windows (Powershell/cmd) and Linux/macOS (bash/sh) equivalents side by side.
  • Explicitly mention that the .NET APIs can be used cross-platform, or provide links/examples for other supported SDKs (such as Java, Python, or Node.js) if applicable.
  • Include troubleshooting steps and command examples that are relevant to Linux/macOS environments (e.g., using 'dig' or 'host' for DNS resolution, checking network connectivity with 'curl' or 'telnet').
  • Avoid assuming the use of Windows-specific tools or patterns; where possible, use generic, cross-platform terminology and examples.
  • If the documentation is intentionally .NET/Windows-specific, clarify this scope at the beginning and provide links to equivalent guidance for other platforms.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-java-how-to-use-queues.md ...ce-bus-messaging/service-bus-java-how-to-use-queues.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. It references Windows tools (Eclipse, IntelliJ, Azure CLI for Windows), and installation links default to Windows versions. Instructions for running the app and installing prerequisites are oriented toward Windows users, with no explicit Linux or macOS alternatives. There are no shell or terminal examples for Linux/macOS, and the 'Run the app' section assumes a Windows workflow (e.g., right-clicking in Eclipse).
Recommendations
  • Provide explicit instructions for Linux and macOS users, including links to platform-specific Azure CLI installation guides.
  • Include terminal/command-line examples using Bash or sh for Linux/macOS, especially for running the Java JAR file.
  • When referencing IDEs like Eclipse or IntelliJ, mention that they are cross-platform and provide any platform-specific notes if needed.
  • Avoid defaulting to Windows-specific UI actions (like right-clicking) without also describing the equivalent for other platforms.
  • In 'Run the app', show both Windows and Linux/macOS command-line instructions for running the JAR and signing in with Azure CLI.
  • Where possible, use neutral language and tool references that apply to all platforms, or clearly indicate when a step is platform-specific.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-queues-topics-subscriptions.md ...s-messaging/service-bus-queues-topics-subscriptions.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently lists Windows-centric tools (PowerShell) before cross-platform or Linux-native options (CLI) when describing how to create Service Bus entities. PowerShell is explicitly mentioned as a primary method, and the linked PowerShell documentation is Windows-focused. There are no explicit Linux command-line examples or references to Linux-specific tools, and the ordering of options subtly prioritizes Windows workflows.
Recommendations
  • List cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell) when presenting options for creating or managing resources.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide example commands for both PowerShell and Bash/shell environments.
  • Where PowerShell is referenced, ensure equivalent Bash or shell examples are provided, or link to Linux/macOS-specific quickstarts.
  • Avoid using 'PowerShell' as a default or primary example; instead, present CLI or REST API as the first and most universal option.
  • Add a note clarifying that all management operations can be performed from Linux, macOS, and Windows, and provide links to relevant documentation for each platform.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-quickstart-cli.md ...es/service-bus-messaging/service-bus-quickstart-cli.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 mild Windows bias by mentioning Azure PowerShell as a local option before any mention of installing or using the Azure CLI natively on Linux or macOS. While the primary example uses Azure Cloud Shell (which is cross-platform), the only explicit local tool mentioned is Azure PowerShell, with no guidance for Linux users on installing or running the Azure CLI locally. There are no Linux- or macOS-specific instructions or examples, and the documentation does not mention Linux command-line environments outside of Cloud Shell Bash.
Recommendations
  • Explicitly mention that the Azure CLI can be installed and used natively on Linux and macOS, not just via Cloud Shell.
  • Provide installation instructions or a link for Azure CLI on Linux/macOS alongside the PowerShell mention.
  • Avoid suggesting Azure PowerShell as the only local alternative; clarify that Bash and CLI are fully supported on all platforms.
  • Include a note or section for Linux/macOS users to ensure parity and inclusivity.
  • If referencing PowerShell, also mention that PowerShell Core is cross-platform, but emphasize that Bash/CLI is the primary focus for this quickstart.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-to-event-grid-integration-concept.md ...aging/service-bus-to-event-grid-integration-concept.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 for creating Event Grid subscriptions, but PowerShell is featured as a primary method alongside CLI, with no mention of Bash or Linux-specific tools. PowerShell is a Windows-centric tool, and its inclusion without equivalent Bash or Linux-native scripting examples may disadvantage Linux users. Additionally, the PowerShell example is given equal prominence to CLI, which can be interpreted as a Windows-first approach.
Recommendations
  • Ensure that all code examples are available in both Azure CLI (which is cross-platform) and PowerShell, but clearly indicate that PowerShell is primarily for Windows users.
  • Add explicit Bash shell examples where scripting is shown, or clarify that Azure CLI commands are intended for Bash or cross-platform shells.
  • Where PowerShell is used, provide a note or alternative for Linux/macOS users, such as Bash or Python scripts.
  • Review the order of examples to present cross-platform (CLI/Bash) options before Windows-specific (PowerShell) ones.
  • Consider adding a table or section summarizing all available tooling options for different platforms (Windows, Linux, macOS) to help users choose the best fit.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-python-how-to-use-topics-subscriptions.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-python-how-to-use-topics-subscriptions.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation consistently refers to 'command prompt' and 'Visual Studio Code' as the default terminal and editor, and uses semicolon-separated command chaining (e.g., 'python send.py; python recv.py') which is a Windows CMD pattern. There are no explicit Linux or macOS terminal instructions or mentions of Bash, nor are alternative editors or shells suggested. The phrase 'open a command prompt that has Python in its path' is Windows-centric. No Linux-specific instructions, screenshots, or troubleshooting are provided.
Recommendations
  • Use neutral terms like 'terminal' or 'shell' instead of 'command prompt', and clarify that instructions apply to Windows, Linux, and macOS.
  • Provide both Windows and Linux/macOS command examples, e.g., use '&&' for Bash and ';' for CMD/PowerShell, or explain the difference.
  • Mention alternative editors such as 'nano', 'vim', or 'gedit' for Linux users alongside Visual Studio Code.
  • Include notes or callouts for any OS-specific steps, such as how to ensure Python is in the PATH on different platforms.
  • Add Linux/macOS screenshots or clarify that the Azure CLI and Python code work cross-platform.
  • Explicitly state that the instructions are valid for all major operating systems, and provide troubleshooting tips for common Linux/macOS issues (e.g., permissions, package installation).
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-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation displays a mild Windows bias by referencing Windows-specific tools and patterns (such as PowerShell and 'command prompt') and mentioning Windows deployment options before Linux equivalents. There are no explicit Linux or cross-platform terminal instructions, and a key deployment link refers to using Windows PowerShell, with no Linux alternative provided. The language used (e.g., 'command prompt') and the absence of explicit Linux shell examples or instructions may confuse or exclude Linux users.
Recommendations
  • When referring to terminals, use cross-platform language such as 'terminal' or 'shell' instead of 'command prompt', and clarify that instructions apply to both Windows and Linux.
  • For deployment and running commands, provide both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) examples where syntax or context differs.
  • Where links reference Windows-specific guides (e.g., deploying Node.js with Windows PowerShell), add or link to equivalent Linux/macOS guides.
  • Explicitly state that all npm and Node.js commands work on Linux/macOS, and provide any necessary Linux-specific prerequisites or troubleshooting tips.
  • Consider including screenshots or terminal output from both Windows and Linux environments to reinforce cross-platform support.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-overview.md ...bus-messaging/service-bus-resource-manager-overview.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively provides instructions and examples for deploying Azure Service Bus resources using PowerShell, a tool most commonly associated with Windows environments. There are no examples or references for Linux or cross-platform tools such as Azure CLI, Bash, or Cloud Shell. The workflow, installation instructions, and command syntax are all PowerShell-centric, which may alienate or confuse users on Linux or macOS.
Recommendations
  • Add parallel instructions and examples for deploying ARM templates using Azure CLI (az deployment group create), which is cross-platform and widely used on Linux and macOS.
  • Include Bash shell command examples for template deployment, especially for users working in Linux environments.
  • Mention and provide examples for using Azure Cloud Shell, which supports both Bash and PowerShell and is accessible from any OS.
  • Reorganize the documentation to present both PowerShell and CLI/Bash instructions side-by-side or in clearly separated sections, ensuring neither platform is prioritized over the other.
  • Explicitly state that the instructions apply to all platforms, and provide links to platform-specific setup guides where appropriate.
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: 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 detailed instructions for configuring network service endpoints for Azure Service Bus, but it demonstrates a Windows bias. The Azure PowerShell section is more detailed than the Azure CLI section, and PowerShell is mentioned after CLI but before REST API. There are no explicit Linux or cross-platform shell (bash) examples, and no mention of Linux-specific tools or workflows. The instructions for deploying ARM templates link to PowerShell deployment guidance, with no reference to Azure CLI or other cross-platform deployment methods.
Recommendations
  • Add explicit Linux/bash examples alongside or before PowerShell examples, especially in sections about deploying ARM templates and managing network rules.
  • Provide parity in command-line examples: for every PowerShell command, include the equivalent Azure CLI (bash) command.
  • When referencing deployment instructions, link to both PowerShell and Azure CLI documentation, or provide a cross-platform deployment example.
  • Avoid assuming the use of Windows tools or the Azure portal; clarify that all steps can be performed from any OS using CLI or REST.
  • Consider a 'Choose your platform' section at the start of command-line sections, guiding users to Windows (PowerShell), Linux/macOS (bash/CLI), or REST API instructions.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-to-event-grid-integration-function.md ...ging/service-bus-to-event-grid-integration-function.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 demonstrates a strong Windows bias by exclusively referencing Visual Studio 2022 (a Windows-centric IDE) and its publishing workflow, including screenshots and instructions that are specific to Windows. There are no examples or instructions for Linux or cross-platform development environments (such as Visual Studio Code, Azure CLI, or command-line deployment). The tutorial assumes the user is on Windows and does not mention or provide parity for Linux users.
Recommendations
  • Add a section or parallel instructions for developing and deploying Azure Functions using cross-platform tools such as Visual Studio Code, Azure CLI, or Azure Functions Core Tools, which work on Linux and macOS.
  • Provide command-line examples (e.g., using Azure CLI or PowerShell Core) for deployment and management tasks, ensuring these commands are cross-platform.
  • Include screenshots and workflow steps for Linux/macOS environments, or at least reference official guides for those platforms.
  • Explicitly state that the tutorial is Windows-specific if Linux/macOS parity is not intended, or update the tutorial to ensure full parity.
  • Mention alternative editors (e.g., Visual Studio Code) and provide guidance for users who do not use Visual Studio 2022.
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: 2025-07-12 23:44
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 bias in several areas: troubleshooting steps and examples often present Windows commands (e.g., PowerShell's 'tnc', use of '.\psping.exe') before or instead of Linux equivalents; Windows-specific tools (psping, PowerShell) are highlighted, with Linux alternatives mentioned only briefly or as an afterthought. Some diagnostic instructions and logging/tracing guidance are .NET/.NET Core-centric, with little to no mention of Linux-native or cross-platform approaches. Linux users may find the guidance less accessible or discoverable.
Recommendations
  • For every Windows/Powershell command or tool mentioned (e.g., 'tnc', '.\psping.exe'), provide the Linux/macOS equivalent (e.g., 'telnet', 'nc', 'ss', 'ping', 'hping3') side-by-side and with equal prominence.
  • When referencing tools like 'psping', suggest cross-platform alternatives (e.g., 'iperf', 'hping3', 'nmap') and provide download links or installation instructions for Linux/macOS.
  • Avoid presenting Windows commands or tools first by default; instead, group instructions by platform or present them in parallel.
  • Expand diagnostic and logging sections to include examples for non-.NET environments and cross-platform SDKs (e.g., Java, Python), and mention Linux-native logging/tracing tools (e.g., journalctl, syslog, strace, tcpdump).
  • Where .NET or Visual Studio is referenced, add notes or links for equivalent workflows in Linux development environments (e.g., VS Code, JetBrains Rider, command-line SDK usage).
  • Audit the documentation for other subtle Windows-first language or assumptions (e.g., references to 'Console.ReadKey()', Visual Studio, or Windows-specific troubleshooting patterns) and provide Linux/macOS context or alternatives.
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: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Administrative instructions and tooling references (such as Azure PowerShell and the Azure portal) are presented before or more prominently than cross-platform alternatives. The only code sample is in C#, a language most associated with Windows development. There are no explicit Linux shell or scripting examples, and no mention of Linux-native tools or workflows. While Azure CLI is mentioned, it is listed after PowerShell, and there are no Bash or Linux-specific command examples. The documentation assumes familiarity with Windows-centric patterns and tools.
Recommendations
  • Provide example commands for both Azure PowerShell and Azure CLI side-by-side, making clear that Azure CLI is fully cross-platform and often preferred for Linux/macOS users.
  • Include at least one example of generating a SAS token using Bash/shell scripting (e.g., using openssl and curl), or link to such examples.
  • When referencing the Azure portal, clarify that it is web-based and platform-agnostic, but also provide CLI alternatives for all portal actions.
  • Add code samples in additional languages commonly used on Linux (e.g., Python, JavaScript/Node.js), or link to such samples.
  • Avoid using Windows-centric language (such as referencing PowerShell or C# first) unless there is a technical reason; strive for neutral ordering or explicit cross-platform parity.
  • Explicitly mention that all SDKs and tools are available on Linux, and provide links to relevant installation guides for Linux users.
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-12 23:44
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-based instructions before Linux/macOS equivalents, requiring WSL for Windows users, and referencing Windows-specific tools and path conventions. Linux and macOS instructions are less detailed and sometimes only mentioned after Windows steps. There is also an emphasis on Docker Desktop (with a Windows install link) and WSL configuration, while native Linux workflows are less emphasized.
Recommendations
  • Present Linux/macOS instructions alongside or before Windows instructions, or use parallel tabbed sections for each OS.
  • Provide native Linux and macOS setup steps with equal detail, including terminal commands and file path conventions.
  • Avoid requiring WSL for Windows users unless absolutely necessary; if used, clarify why and provide alternatives.
  • Include Linux and macOS Docker installation links in prerequisites, not just Windows.
  • When referencing file paths, show both Windows and Unix-style examples.
  • Ensure all scripts and commands are demonstrated for both PowerShell/Windows and Bash/Linux environments.
  • Where possible, use cross-platform tools and language in examples, minimizing Windows-specific terminology.
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-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page exhibits several signs of Windows bias. It references Windows-specific tools (ARMClient.exe), provides PowerShell examples, and omits equivalent Linux-native instructions or tools (e.g., using curl/jq for REST API calls, or az CLI for token retrieval). The order of presentation also often places Windows/PowerShell approaches before cross-platform or Linux-friendly alternatives. There are no explicit Linux or bash examples for key tasks such as querying the ARM API or obtaining tokens.
Recommendations
  • Provide Linux/bash-native examples for all command-line operations, such as using curl and jq to query the ARM API and az CLI to obtain tokens.
  • Mention and demonstrate cross-platform tools (e.g., az CLI, curl) before or alongside Windows-specific tools like ARMClient.exe.
  • Where PowerShell is shown, also provide bash/zsh equivalents.
  • Clarify that ARMClient.exe is a Windows-only tool and suggest alternatives for Linux/macOS users.
  • Audit all screenshots and instructions to ensure they are not Windows-centric unless the feature is truly Windows-only.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides setup instructions for both Windows and Linux/macOS, but the Windows instructions are presented first and in greater detail, including explicit PowerShell and WSL steps. Linux/macOS instructions are less detailed and lack step-by-step guidance. Some examples (like file paths in .env) default to Windows syntax, and the automated script section is Windows-centric.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, with equal detail.
  • Provide explicit step-by-step commands for Linux/macOS users, including terminal commands for cloning the repo and running scripts.
  • Clarify file path syntax for both Windows and Linux/macOS in environment variable examples.
  • Include screenshots or terminal output examples for Linux/macOS users.
  • Ensure that any PowerShell/WSL steps are matched with equivalent bash/zsh instructions for Linux/macOS.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides many PowerShell-based examples and instructions for key operations (such as deploying Resource Manager templates and managing Key Vault access policies), with no equivalent Bash/Azure CLI examples for Linux/macOS users. PowerShell commands are presented as the primary or only automation method, and are shown before mentioning CLI alternatives. This creates friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI (bash) equivalents for all PowerShell commands, especially for template deployments and Key Vault access policy management.
  • Where possible, present CLI and PowerShell examples side-by-side, or use tabs to allow users to select their preferred environment.
  • Clarify that all operations can be performed via Azure CLI on Linux/macOS, and provide links to relevant CLI documentation.
  • Review and update troubleshooting and automation sections to ensure parity for Linux/macOS users.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Dotnet Heavy
Summary
The documentation primarily provides examples and references for .NET and Azure portal workflows, which are most familiar to Windows users. There are no explicit Linux/macOS command-line examples, nor are cross-platform SDKs or tools (such as Python, Java, or Node.js) demonstrated. The only code sample is in C#, and links to further samples are .NET-focused. While Azure CLI is mentioned in the 'Next steps', it is not shown in the main workflow or examples, and PowerShell is referenced before CLI. No Linux-specific guidance or parity is provided.
Recommendations
  • Add authentication code samples for other cross-platform SDKs (Python, Java, Node.js) alongside the .NET example.
  • Include explicit Azure CLI examples for authentication and role assignment in the main workflow, not just in 'Next steps'.
  • Show how to use environment variables or managed identities from Linux/macOS environments.
  • Balance references to PowerShell and CLI, or show CLI first as it is cross-platform.
  • Clarify that the authentication flow and SDKs are supported on Linux/macOS and provide links to relevant documentation.
GitHub Create Pull Request
← Previous Page 8 of 16 Next →