Service Bus Messaging

268
Total Pages
221
Linux-Friendly Pages
47
Pages with Bias
17.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

91 issues found
Showing 76-91 of 91 flagged pages
Service Bus Messaging Azure Service Bus - message count ...ain/articles/service-bus-messaging/message-counters.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for retrieving message counts, with CLI examples shown first. While Azure CLI is cross-platform, the PowerShell section is Windows-centric and does not mention Linux/macOS compatibility or alternatives. No Linux-specific tools or shell examples (e.g., Bash scripting) are provided, and PowerShell is presented as a primary method without clarifying its cross-platform status.
Recommendations
  • Explicitly state that Azure CLI commands work on Windows, Linux, and macOS.
  • Clarify that PowerShell Core is available cross-platform, or provide equivalent Bash examples for Linux/macOS users.
  • Add a note or section on how to use Bash or other Linux-native shells to retrieve and parse message counts.
  • Ensure that examples for Linux/macOS are given equal prominence and detail as Windows/PowerShell examples.
GitHub Create Pull Request
Service Bus Messaging Get started with Azure Service Bus topics (TypeScript) ...service-bus-typescript-how-to-use-topics-subscriptions.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows Examples Windows First
Summary
The documentation page exhibits mild Windows bias, primarily through references to Windows-specific tools and examples. Notably, it mentions 'Node.js Cloud Service using Windows PowerShell' as a deployment option and refers to 'command prompt' throughout, which is a Windows-centric term. The instructions do not explicitly mention Linux/macOS equivalents (such as Bash or Terminal), nor do they provide parity for deployment or development workflows outside Windows. However, most commands (npm, az CLI) are cross-platform, and there are no critical Windows-only steps.
Recommendations
  • Replace or supplement 'command prompt' with 'terminal' or 'shell' to be inclusive of Linux/macOS users.
  • Add explicit references and links to Linux/macOS deployment guides (e.g., deploying Node.js apps on Azure from Linux/macOS).
  • If mentioning PowerShell, also mention Bash or other common Linux/macOS shells.
  • Clarify that all CLI commands (npm, az) work on Linux/macOS and Windows.
  • Ensure screenshots and instructions do not assume Windows file paths or UI unless necessary.
GitHub Create Pull Request
Service Bus Messaging Get started with Azure Service Bus queues (TypeScript) ...-messaging/service-bus-typescript-how-to-use-queues.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page is generally cross-platform but shows minor Windows bias. The only explicit OS-specific reference is in the note: 'For instructions on how to create a Node.js application, see ... or Node.js cloud service using Windows PowerShell.' This mentions Windows PowerShell as a deployment method, without referencing Linux/macOS equivalents. Additionally, Windows tools (PowerShell) are mentioned before any Linux alternatives, and there is no mention of Linux/macOS-specific deployment or command-line patterns. However, the main workflow (using npm, Node.js, Azure CLI) is cross-platform, and all code samples use generic shell commands.
Recommendations
  • Add references to Linux/macOS deployment guides alongside the Windows PowerShell link, such as instructions for deploying Node.js apps using Bash or the Azure CLI on Linux/macOS.
  • Clarify that the npm and Azure CLI commands work on all major platforms.
  • Avoid mentioning Windows-specific tools (like PowerShell) without also mentioning Linux/macOS equivalents.
  • Consider showing cross-platform terminal commands or explicitly stating platform compatibility in relevant sections.
GitHub Create Pull Request
Service Bus Messaging Enable auto forwarding for Azure Service Bus queues and subscriptions .../articles/service-bus-messaging/enable-auto-forward.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing Service Bus auto forwarding. However, the PowerShell section is extensive and presented before ARM templates and SDKs, and PowerShell is a Windows-centric tool. There are no explicit Linux shell (bash) or macOS-specific instructions, and no mention of cross-platform scripting alternatives to PowerShell. The CLI section is present and cross-platform, but PowerShell is given equal prominence, which may imply Windows preference. No Linux/macOS-specific friction is introduced, but the presence and order of PowerShell examples may signal a slight Windows bias.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add bash or shell script examples where appropriate, or clarify that CLI commands work on Linux/macOS.
  • Reorder sections to present CLI before PowerShell, or clarify platform applicability for each tool.
  • Add a note about PowerShell Core availability on Linux/macOS, if relevant.
  • Consider including a table comparing tool/platform compatibility.
GitHub Create Pull Request
Service Bus Messaging Enable Azure Service Bus message sessions | Microsoft Docs ...icles/service-bus-messaging/enable-message-sessions.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for enabling Service Bus message sessions, but PowerShell (a Windows-centric tool) is given a dedicated section and detailed examples. The CLI section is present and shown before PowerShell, which is good for Linux parity. However, the presence of PowerShell examples and references to PowerShell modules may create a slight Windows bias, especially since PowerShell is still most commonly used on Windows. No Linux-specific tools (e.g., Bash scripts) or explicit Linux/macOS instructions are provided, and there is no mention of platform-specific considerations.
Recommendations
  • Clarify that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for Linux/macOS users.
  • Add explicit notes or examples for Linux/macOS users, such as Bash or shell script usage, or mention that the CLI commands work natively on those platforms.
  • Consider including a brief comparison table of CLI vs PowerShell, indicating platform compatibility.
  • If PowerShell is shown, mention that PowerShell Core is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus message sessions | Microsoft Docs ...ain/articles/service-bus-messaging/message-sessions.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page mentions enabling message sessions using Azure portal, PowerShell, CLI, Resource Manager template, .NET, Java, Python, and JavaScript. PowerShell is listed before CLI, which is more cross-platform. There is a slight Windows bias in the ordering of tools, as PowerShell is a Windows-centric tool and is mentioned before CLI, which is available on Linux/macOS. However, the page does not provide command-line examples, and the samples section covers multiple programming languages without Windows bias.
Recommendations
  • List CLI before PowerShell when mentioning cross-platform tools.
  • Provide explicit Linux/macOS examples or clarify that CLI commands work on all platforms.
  • Add a note that PowerShell Core is available cross-platform, if relevant.
  • Ensure that future examples or walkthroughs include both Windows and Linux/macOS command-line instructions.
GitHub Create Pull Request
Service Bus Messaging Enable partitioning in Azure Service Bus Premium namespaces ...les/service-bus-messaging/enable-partitions-premium.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for enabling partitioning, but PowerShell (a Windows-centric tool) is given equal prominence and is shown immediately after the CLI. There is no explicit Linux/macOS example (such as Bash scripting or shell-specific notes), and PowerShell is still primarily associated with Windows environments. The CLI example is cross-platform, but the documentation does not clarify this or prioritize it over PowerShell.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • List Azure CLI examples before PowerShell to emphasize Linux/macOS parity.
  • Add a note clarifying that PowerShell Core is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
  • Consider including Bash or shell script examples where appropriate.
  • Add a table or section summarizing which tools are supported on which platforms.
GitHub Create Pull Request
Service Bus Messaging Troubleshoot AMQP errors in Azure Service Bus | Microsoft Docs ...service-bus-messaging/service-bus-amqp-troubleshoot.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page references 'Service Bus for Windows Server' in its next steps, suggesting a Windows-centric approach. No Linux/macOS-specific tools, troubleshooting steps, or examples are provided, and the only platform-specific resource mentioned is Windows-focused. There are no explicit PowerShell examples, but the overall framing and resource linking prioritize Windows environments.
Recommendations
  • Include troubleshooting guidance or examples for Linux and macOS environments, such as using common AMQP clients on those platforms.
  • Add links to documentation for cross-platform Service Bus usage, including Linux and macOS.
  • Balance resource links by referencing both Windows and non-Windows guides where available.
  • Clarify that the guidance applies to all platforms, or specify platform differences if relevant.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus - messaging exceptions (deprecated) | Microsoft Docs ...vice-bus-messaging/service-bus-messaging-exceptions.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. The only explicit command-line example is given in PowerShell syntax, and the troubleshooting steps reference Windows command-line patterns (e.g., 'PS C:\> nslookup ...') without providing equivalent Linux/macOS shell commands. There is no mention of Linux/macOS tools or alternative commands, and Windows-style output is shown first and exclusively.
Recommendations
  • Provide equivalent Linux/macOS shell commands (e.g., 'nslookup <mynamespace>.servicebus.windows.net' or 'dig ...') alongside PowerShell examples.
  • Show example outputs from Linux/macOS terminals as well as Windows.
  • Explicitly mention that troubleshooting steps apply to all platforms and clarify any platform-specific differences.
  • Avoid using Windows paths (e.g., 'C:\>') as the sole example prompt; include '$' or '%' for Unix-like systems.
GitHub Create Pull Request
Service Bus Messaging Quickstart: Get started with Azure Service Bus queues (JavaScript) ...-bus-messaging/service-bus-nodejs-how-to-use-queues.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation shows minor Windows bias by referencing Windows-specific tools and patterns, such as 'Command Prompt' and 'Windows PowerShell', and by linking to Windows deployment instructions before mentioning cross-platform alternatives. However, all code and CLI instructions are cross-platform, and Linux/macOS users can follow the steps without issue.
Recommendations
  • Replace 'Command Prompt' with 'terminal' or 'command line' to be platform-neutral.
  • When referencing deployment guides, include Linux/macOS equivalents alongside or before Windows-specific links.
  • Clarify that Azure CLI and Node.js instructions work on Linux/macOS as well as Windows.
  • Add explicit notes or links for Linux/macOS users where appropriate (e.g., how to install Node.js or Azure CLI on those platforms).
GitHub Create Pull Request
Service Bus Messaging Get started with Azure Service Bus topics (JavaScript) ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-nodejs-how-to-use-topics-subscriptions.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation demonstrates minor Windows bias by referencing Windows-specific tools and patterns, such as suggesting 'Node.js Cloud Service using Windows PowerShell' and using 'command prompt' terminology throughout. The instructions do not provide explicit Linux/macOS equivalents or mention cross-platform alternatives when discussing development environments and command-line usage. However, the actual code and commands (npm, node, az CLI) are cross-platform, and Linux/macOS users can follow the tutorial with minimal friction.
Recommendations
  • Replace or supplement references to 'Windows PowerShell' with cross-platform alternatives (e.g., Bash, Terminal, zsh).
  • Use neutral terms like 'terminal' or 'shell' instead of 'command prompt' when describing where to run commands.
  • Explicitly mention that all commands and tools (npm, node, Azure CLI) work on Linux/macOS, and provide links to installation instructions for those platforms.
  • If linking to deployment guides, include Linux/macOS deployment documentation alongside Windows-specific ones.
GitHub Create Pull Request
Service Bus Messaging Create Azure Service Bus namespace and queue using Azure template ...saging/service-bus-resource-manager-namespace-queue.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page primarily describes deploying Azure Service Bus resources via the Azure portal and ARM templates, which are cross-platform. However, in the 'Next steps' section, it lists PowerShell management first and does not mention Azure CLI management directly, despite linking to a CLI page in the references. This ordering and emphasis may subtly favor Windows users and PowerShell workflows.
Recommendations
  • Add explicit instructions or links for managing Service Bus resources using Azure CLI, especially in the 'Next steps' section.
  • Present Azure CLI and PowerShell management options side-by-side, or list CLI first to balance the ordering.
  • Include examples or links for Linux/macOS users, such as using Azure CLI or REST API.
  • Ensure that screenshots and instructions are not exclusively portal-based, and clarify that the portal is cross-platform.
GitHub Create Pull Request
Service Bus Messaging Quickstart - Use the Azure CLI to create a Service Bus queue | Microsoft Docs ...es/service-bus-messaging/service-bus-quickstart-cli.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions Azure PowerShell as an alternative to Azure Cloud Shell and references switching between Bash and PowerShell modes. While the main instructions use Bash and Azure CLI, the initial mention of PowerShell and the need to switch away from PowerShell mode may suggest a slight Windows-first or PowerShell-heavy bias. However, all example commands are cross-platform Azure CLI commands, and Bash is explicitly recommended for the walkthrough.
Recommendations
  • Clarify that Azure CLI and Bash are fully supported on Linux/macOS and provide installation links for those platforms.
  • Mention that Azure PowerShell is optional and not required for Linux/macOS users.
  • Consider listing Bash as the default mode before mentioning PowerShell, or provide parity by referencing Linux/macOS terminal usage.
  • Add a note that all CLI commands work on Linux, macOS, and Windows equally.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus access control with Shared Access Signatures ...main/articles/service-bus-messaging/service-bus-sas.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits mild Windows bias, primarily in the tooling references and ordering. When discussing key regeneration, Azure PowerShell is mentioned before Azure CLI, and the only code sample for AMQP-level SAS token usage is in C#, a language most associated with Windows development. The references to PowerShell and the Azure portal (which is platform-agnostic but often associated with Windows environments) appear before Linux-friendly options like Azure CLI. There are no explicit Linux/macOS examples, nor are there references to Linux-specific tools or shell commands.
Recommendations
  • Present Azure CLI instructions before or alongside PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Add code samples in languages popular on Linux/macOS (e.g., Python, JavaScript, Java) for AMQP-level SAS token usage.
  • Explicitly mention that all operations can be performed on Linux/macOS and provide shell/bash examples where appropriate.
  • Clarify that the Azure portal and CLI are fully supported on Linux/macOS.
  • Include links to Linux/macOS setup guides for Azure CLI and SDKs.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus to Event Grid integration overview | Microsoft Docs ...aging/service-bus-to-event-grid-integration-concept.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 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. PowerShell is a Windows-centric tool, and its inclusion without equivalent Linux/macOS shell examples (e.g., Bash, zsh) or explicit mention of cross-platform compatibility introduces a mild Windows bias. The CLI example is cross-platform, but PowerShell's presence may suggest a preference for Windows users.
Recommendations
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and recommend it as the default cross-platform method.
  • Indicate that PowerShell Core is available on Linux/macOS if PowerShell examples are retained, or provide Bash/zsh equivalents where relevant.
  • Ensure that any references to tools or patterns are explicitly marked as cross-platform or provide alternatives for Linux/macOS users.
  • Consider listing CLI examples before PowerShell to reinforce cross-platform parity.
GitHub Create Pull Request
Service Bus Messaging Use the Azure CLI to create Service Bus topics and subscriptions ...aging/service-bus-tutorial-topics-subscriptions-cli.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions Azure PowerShell as an alternative to Azure Cloud Shell and instructs users to switch to Bash if Cloud Shell is in PowerShell mode, implying a default Windows/PowerShell orientation. The mention of PowerShell occurs before any Linux-specific instructions, and there is no explicit mention of Linux or macOS CLI usage outside of Bash in Cloud Shell. However, all command examples use Azure CLI, which is cross-platform and Bash-friendly.
Recommendations
  • Explicitly mention that Azure CLI works on Linux and macOS, and provide installation links for those platforms.
  • Add a brief note or section highlighting Linux/macOS compatibility and usage outside of Cloud Shell.
  • Provide parity in instructions for launching Azure CLI locally on Linux/macOS, not just PowerShell on Windows.
  • Consider reordering the prerequisites to mention Bash/CLI before PowerShell, or present both equally.
GitHub Create Pull Request
← Previous Page 4 of 4 Next →