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 326-350 of 377 flagged pages
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-queue-bicep.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-queue-bicep.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment, validation, and cleanup, but consistently lists PowerShell examples after CLI and highlights PowerShell-specific management in the 'Next steps' section. There is a dedicated link to managing Service Bus with PowerShell, but no equivalent for Bash or Linux shell scripting. While Azure CLI is cross-platform, the presence of PowerShell-specific instructions and links, without similar Linux/Bash-focused content, shows a mild Windows/PowerShell bias.
Recommendations
  • Add a 'Manage Service Bus with Azure CLI' link in the 'Next steps' section, similar to the PowerShell management link.
  • Include brief notes or links about using Bash scripting with Azure CLI for Linux users.
  • Ensure parity in advanced management examples for both PowerShell and CLI, not just basic deployment.
  • Consider mentioning that Azure CLI commands work identically on Linux, macOS, and Windows, to reinforce cross-platform support.
  • If possible, provide examples of automating deployments with Bash scripts, not just PowerShell.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-topic.md ...saging/service-bus-resource-manager-namespace-topic.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for deploying the ARM template, but PowerShell is presented first in both the deployment commands and the 'Next steps' section. Additionally, the 'Next steps' section highlights PowerShell-based management before mentioning cross-platform tools, which may suggest a Windows-centric workflow.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to reflect its cross-platform nature.
  • In the 'Next steps' section, mention Azure CLI management options alongside or before PowerShell to ensure Linux users see relevant guidance.
  • Explicitly state that both PowerShell and Azure CLI are available on all major platforms, and provide links to installation instructions for each.
  • Consider including Bash or shell script examples where appropriate, especially for Linux users.
  • Review linked resources (e.g., 'Manage Service Bus with PowerShell') to ensure Linux-friendly alternatives are referenced or provided.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-tutorial-topics-subscriptions-cli.md ...aging/service-bus-tutorial-topics-subscriptions-cli.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by mentioning Azure PowerShell as an alternative to Cloud Shell before referencing installation instructions, and by referencing PowerShell mode in Cloud Shell before Bash. However, all command examples use the Azure CLI, which is cross-platform and shown in Bash syntax. There are no exclusive Windows tools or missing Linux examples, but the ordering and language slightly prioritize Windows/PowerShell users.
Recommendations
  • When mentioning Cloud Shell, present Bash as the default or mention Bash and PowerShell equally, rather than referencing PowerShell mode first.
  • Clarify that Azure CLI works identically on Windows, Linux, and macOS, and that all examples are cross-platform.
  • If referencing Azure PowerShell, also mention that it is available on Linux and macOS, or provide a parallel Linux-native alternative if relevant.
  • Ensure introductory and prerequisite sections do not imply a Windows-first workflow or tool preference.
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-queues.md ...-messaging/service-bus-typescript-how-to-use-queues.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation generally uses cross-platform language (e.g., 'command prompt', 'terminal'), but there is a notable reference to 'Node.js cloud service using Windows PowerShell' before any mention of Linux or macOS equivalents. The instructions for running commands and installing tools are mostly generic, but the explicit mention of Windows PowerShell and the lack of Linux/macOS-specific guidance or examples indicate a mild Windows bias.
Recommendations
  • When referencing command-line instructions, explicitly mention that they work on Windows, Linux, and macOS, or provide separate tabs or notes for each OS if there are differences.
  • Replace or supplement the reference to 'Node.js cloud service using Windows PowerShell' with equivalent Linux/macOS deployment guides, or link to cross-platform deployment documentation.
  • Where 'command prompt' is mentioned, clarify that this could be Command Prompt, PowerShell, Terminal, or Bash, depending on the user's OS.
  • Ensure that all tool installation instructions (e.g., Azure CLI, Node.js) include links or commands for Linux and macOS, not just Windows.
  • If screenshots or step-by-step instructions are OS-specific, provide alternatives for Linux/macOS users.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation provides examples for enabling auto forwarding in Azure Service Bus using Azure Portal, Azure CLI, Azure PowerShell, ARM templates, and several programming languages. While the CLI and ARM template examples are cross-platform, the PowerShell section is Windows-centric and presented as a full, parallel method to CLI, without explicit mention of its Windows-only nature or Linux alternatives. However, Linux/macOS users are not blocked from completing the task due to the presence of CLI and SDK examples.
Recommendations
  • Add a note to the PowerShell section clarifying that Azure PowerShell is primarily supported on Windows, and recommend Azure CLI for Linux/macOS users.
  • Consider presenting Azure CLI examples before PowerShell, or grouping them together with a clear indication of platform compatibility.
  • Ensure that all critical workflows have CLI or ARM template examples, and explicitly mention cross-platform options where relevant.
GitHub Create Pull Request
Service Bus Messaging Enable dead lettering for Azure Service Bus queues and subscriptions ...n/articles/service-bus-messaging/enable-dead-letter.md
Low 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 examples for enabling dead lettering in Azure Service Bus using the Azure portal, Azure CLI, Azure PowerShell, and ARM templates. While the CLI and ARM template methods are cross-platform, the PowerShell section is extensive and presented before any programming language samples. There is a slight Windows-first bias, as PowerShell is a Windows-centric tool and its section is given equal prominence to the CLI, despite CLI being more universally available. However, Linux/macOS users can fully complete all tasks using the Azure CLI and ARM templates, and programming language samples are referenced for all major languages.
Recommendations
  • Clarify that Azure PowerShell is primarily for Windows, and recommend Azure CLI for cross-platform users.
  • Consider presenting Azure CLI examples before PowerShell, or explicitly state both are supported but CLI is cross-platform.
  • Add a brief note at the start of the PowerShell section indicating its Windows-centric nature.
  • Ensure parity in example detail between CLI and PowerShell sections.
GitHub Create Pull Request
Service Bus Messaging Enable partitioning in Azure Service Bus basic or standard ...vice-bus-messaging/enable-partitions-basic-standard.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for enabling partitioning in Azure Service Bus, but PowerShell (a Windows-centric tool) is given its own section and is presented before ARM template examples. The CLI examples are cross-platform and shown before PowerShell, but there are no Linux/macOS-specific notes or parity checks. There is a slight Windows bias in the prominence and separation of PowerShell instructions, and the absence of explicit Linux/macOS shell examples (e.g., bash).
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS.
  • Add explicit bash/zsh shell examples or notes for Linux/macOS users where relevant.
  • Consider grouping PowerShell and CLI examples together, or explicitly stating platform compatibility for each tool.
  • Add a brief note that PowerShell Core is available on Linux/macOS, if relevant.
  • Ensure that no steps require Windows-only tools unless absolutely necessary.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides examples for enabling partitioning in Azure Service Bus Premium namespaces using the Azure portal, Azure CLI, Azure PowerShell, and ARM templates. The PowerShell example is given its own section immediately after the CLI example, which is cross-platform. While PowerShell is primarily associated with Windows, Azure PowerShell is available on Linux and macOS, but its usage is still more common on Windows. No Linux/macOS-specific tools or shell examples (e.g., Bash scripts) are provided, but the CLI and ARM template examples are fully cross-platform. No critical steps are Windows-only.
Recommendations
  • Clarify that Azure PowerShell is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
  • Consider adding a Bash shell script example for the Azure CLI usage to reinforce Linux parity.
  • Ensure that examples and instructions do not imply PowerShell is required for non-Windows users.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for enabling Azure Service Bus message sessions using the Azure portal, Azure CLI, Azure PowerShell, and ARM templates. While the CLI and ARM template methods are cross-platform, the PowerShell section is Windows-centric and presented before programming language samples. The PowerShell examples are given equal prominence to CLI, but PowerShell is primarily a Windows tool (though available on Linux, it's less commonly used there). No Linux shell (bash) or macOS-specific instructions are provided, and PowerShell is listed before programming language samples, which may create a subtle Windows-first impression.
Recommendations
  • Clarify that Azure CLI and ARM templates are fully cross-platform and recommend them for Linux/macOS users.
  • Consider adding bash shell examples (if relevant) or explicitly stating that CLI commands work on Linux/macOS.
  • Reorder sections so that cross-platform methods (CLI, ARM templates) appear before PowerShell.
  • Add a note that PowerShell is available on Linux/macOS, but CLI is generally preferred on those platforms.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus - message count ...ain/articles/service-bus-messaging/message-counters.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for retrieving Service Bus message counts. While Azure CLI is cross-platform and shown first, the PowerShell section is detailed and includes sample output, which may be seen as Windows-centric since PowerShell is most commonly used on Windows. However, no critical functionality is locked to Windows-only tools, and Linux/macOS users can fully complete the task using Azure CLI.
Recommendations
  • Clarify that Azure CLI works on Windows, Linux, and macOS.
  • Mention that PowerShell Core is available cross-platform, or link to instructions for using PowerShell on Linux/macOS.
  • Consider adding sample output for Azure CLI, as is done for PowerShell, to ensure parity.
  • Explicitly state that both CLI and PowerShell methods are equivalent and users can choose based on their OS preference.
GitHub Create Pull Request
Service Bus Messaging Configure IP firewall rules for Azure Service Bus ...cles/service-bus-messaging/service-bus-ip-filtering.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for configuring IP firewall rules, but PowerShell is mentioned as a primary method and has its own dedicated section, while Linux-native tools and examples (such as Bash scripts or explicit Linux/macOS CLI walkthroughs) are not shown. The ordering of sections also places PowerShell after CLI, but both are presented as valid options. No explicit Windows-only tools are used, and the Azure CLI is cross-platform. However, there is a slight bias in the prominence and explicit mention of PowerShell, which is more commonly used on Windows.
Recommendations
  • Add explicit Linux/macOS CLI examples, such as Bash scripts for Azure CLI commands.
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS/Windows.
  • Consider providing example commands for both PowerShell and Bash side-by-side, especially for common tasks.
  • Note that PowerShell Core is available on Linux/macOS, but most Linux users will prefer Bash/Azure CLI.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus Geo-Disaster Recovery | Microsoft Docs ...n/articles/service-bus-messaging/service-bus-geo-dr.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page for Azure Service Bus Geo-Disaster Recovery demonstrates mild Windows bias. While the main setup and management instructions are portal-centric and platform-neutral, the only code samples referenced are .NET-based (which is cross-platform but traditionally Windows-centric), and the instructions mention enabling Geo-Disaster Recovery via 'PowerShell or CLI' with PowerShell listed first and no explicit Linux/bash examples. There are no Linux-specific CLI walkthroughs, and the sample code is exclusively .NET, with no Python, Java, or other cross-platform SDK examples. No explicit Windows-only tools are required, but the ordering and sample selection favor Windows users.
Recommendations
  • Add explicit Azure CLI (bash) examples for setup, failover, and management tasks alongside PowerShell instructions.
  • Reference or provide sample code in other cross-platform languages (e.g., Python, Java) in addition to .NET.
  • When listing automation options, mention CLI and REST API before or alongside PowerShell to avoid Windows-first ordering.
  • Clarify that .NET samples work cross-platform and link to documentation for running them on Linux/macOS.
  • Consider including screenshots or instructions for Linux/macOS environments where relevant.
GitHub Create Pull Request
Service Bus Messaging Get started with Azure Service Bus queues (Go) ...vice-bus-messaging/service-bus-go-how-to-use-queues.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell instructions for setting environment variables, but Bash is presented first. There are no Windows-specific tools, patterns, or examples given priority elsewhere in the document. All code samples and instructions are cross-platform and do not rely on Windows-only features.
Recommendations
  • Consider alternating the order of Bash and PowerShell tabs in different documentation pages to avoid consistent 'windows_first' bias.
  • Explicitly state that all instructions and code samples work on Linux, macOS, and Windows.
  • Add a note clarifying that Azure CLI and Go SDK are cross-platform, and provide troubleshooting tips for Linux/macOS users if needed.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus - messaging exceptions | Microsoft Docs ...s-messaging/service-bus-messaging-exceptions-latest.md
Low 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 is primarily focused on .NET and Service Bus exceptions, which are cross-platform. However, in the 'SocketException' section, only a PowerShell example is provided for DNS resolution, and the command prompt shown is Windows-specific (PS C:\>). No Linux/macOS equivalent (e.g., nslookup or dig in bash/zsh) is given. This is a minor but clear Windows-first bias in example tooling.
Recommendations
  • Provide Linux/macOS equivalents for DNS resolution commands (e.g., show 'nslookup <mynamespace>.servicebus.windows.net' in a bash prompt, or mention 'dig' as an alternative).
  • When showing command-line troubleshooting steps, include both Windows (PowerShell/CMD) and Linux/macOS (bash/zsh) examples side-by-side.
  • Clarify that the .NET client library and Service Bus are cross-platform, and troubleshooting steps apply to all OSes.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation is focused on .NET Framework APIs and Service Bus messaging exceptions, which are cross-platform in .NET Core/.NET 5+, but historically Windows-centric in .NET Framework. The only command-line example given for troubleshooting (nslookup) is shown in PowerShell syntax and Windows path, with no Linux/macOS equivalent. There is a slight Windows-first bias in example formatting and troubleshooting steps, but the core guidance is platform-neutral.
Recommendations
  • Include Linux/macOS equivalents for command-line troubleshooting steps, such as showing 'nslookup' or 'dig' usage in Bash.
  • Clarify that .NET Core/.NET 5+ APIs are cross-platform and provide links or notes for Linux/macOS users where relevant.
  • Where file paths or shell commands are shown, provide both Windows and Linux/macOS formats side-by-side.
  • Explicitly mention that the guidance applies to cross-platform .NET workloads where appropriate.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation occasionally references Windows-specific tools and patterns, such as 'Windows PowerShell' and 'command prompt', and links to a Windows PowerShell-based deployment guide before mentioning Linux alternatives. However, the main instructions and code samples are cross-platform (Node.js, Azure CLI) and do not require Windows. There is minor Windows-first bias in tool references, but Linux/macOS users can follow all steps without significant friction.
Recommendations
  • Replace references to 'command prompt' with 'terminal or command prompt' throughout, clarifying cross-platform usage.
  • When linking to deployment guides, provide parity by linking to both Windows PowerShell and Bash/CLI guides, or clarify that the instructions work on Linux/macOS as well.
  • Explicitly mention that all steps and code samples work on Linux/macOS, and provide links to relevant Linux/macOS documentation where available.
  • Avoid mentioning Windows-specific tools (e.g., Windows PowerShell) unless necessary, or provide equivalent Linux/macOS instructions.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias by referencing 'Command Prompt' and Windows PowerShell, and by listing Windows-centric instructions and links before mentioning cross-platform alternatives. The example for creating and deploying a Node.js application includes a link to a Windows PowerShell guide, and instructions repeatedly refer to 'Command Prompt' rather than a neutral term like 'terminal' or 'shell'. However, the actual code and commands (npm, node, az CLI) are cross-platform and work on Linux/macOS without modification.
Recommendations
  • Replace 'Command Prompt' with 'terminal' or 'shell' to be platform-neutral.
  • Add explicit notes that all CLI commands (npm, node, az CLI) work on Linux/macOS as well as Windows.
  • Provide links to Linux/macOS-specific guides for creating and deploying Node.js applications, alongside the Windows PowerShell link.
  • Where editors are mentioned, clarify that Visual Studio Code is available cross-platform, and suggest alternatives if desired.
GitHub Create Pull Request
Service Bus Messaging Create a Service Bus authorization rule using an Azure template ...ng/service-bus-resource-manager-namespace-auth-rule.md
Low 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 both PowerShell and Azure CLI deployment examples, but PowerShell is presented first and is referenced in the 'Next steps' section for management tasks. There is a slight preference for Windows/PowerShell tooling, though Azure CLI is also included and is cross-platform. No critical Linux/macOS omissions are present.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred for Linux/macOS users.
  • In the 'Next steps' section, add links to managing Service Bus resources with Azure CLI, not just PowerShell.
  • Clarify that both PowerShell and CLI are supported on all platforms, and highlight CLI as the recommended choice for Linux/macOS.
  • Consider including Bash or scripting examples for Linux users where appropriate.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus messaging - queues, topics, and subscriptions ...s-messaging/service-bus-queues-topics-subscriptions.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists PowerShell as a primary method for creating Service Bus entities (queues, topics, subscriptions) before mentioning the Azure CLI, which is cross-platform. PowerShell is a Windows-centric tool, and its placement before CLI may signal a Windows-first bias. However, CLI and ARM templates are also mentioned, and programming language samples are provided for multiple platforms. No critical functionality is Windows-only, and Linux/macOS users can complete all tasks using CLI or portal.
Recommendations
  • List Azure CLI before PowerShell in all 'create' instructions to emphasize cross-platform options.
  • Explicitly state that both PowerShell and CLI are supported, and recommend CLI for Linux/macOS users.
  • Add brief notes or links for Linux/macOS users on how to install and use Azure CLI.
  • Ensure that all example links (e.g., 'service-bus-quickstart-cli.md') are as prominent as PowerShell examples.
GitHub Create Pull Request
Service Bus Messaging Create Azure Service Bus namespace and queue using Bicep ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-queue-bicep.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and managing Service Bus resources with Bicep. However, PowerShell examples are given equal prominence to CLI, and PowerShell is referenced in next steps for management tasks, which may create a slight Windows bias. The CLI examples are cross-platform, but PowerShell is Windows-centric (though it can run on Linux/macOS, it's less common). The order of presentation sometimes puts PowerShell examples immediately after CLI, and the 'Manage Service Bus with PowerShell' link is included in 'Next steps' without a CLI equivalent.
Recommendations
  • Add links or references to managing Service Bus resources with Azure CLI in the 'Next steps' section, similar to the PowerShell management link.
  • Clarify that Azure CLI is fully cross-platform and may be preferred for Linux/macOS users.
  • Consider listing CLI examples first in each section, or explicitly noting parity between CLI and PowerShell.
  • If Service Bus Explorer is cross-platform, clarify its platform support.
GitHub Create Pull Request
Service Bus Messaging Create Service Bus topic subscription and rule using Azure template ...service-bus-resource-manager-namespace-topic-with-rule.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both PowerShell and Azure CLI examples for deploying the template, but PowerShell is listed first and referenced in the 'Next steps' section before CLI or cross-platform tools. There is a slight Windows-first bias in ordering and in the emphasis on PowerShell management, though all core deployment tasks are covered with cross-platform CLI commands.
Recommendations
  • List Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • In 'Next steps', provide management options using Azure CLI or SDKs before PowerShell.
  • Explicitly mention that both PowerShell and CLI are supported on Windows, Linux, and macOS, and link to installation guides for each.
  • Consider adding examples for managing Service Bus resources with Azure CLI, not just PowerShell.
  • Highlight cross-platform tools (such as Service Bus Explorer) earlier in the management section.
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-14 00:00
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 highlighted as a primary method alongside CLI. PowerShell is a Windows-centric tool, and its inclusion may suggest a bias towards Windows users. However, the CLI example is given first and is cross-platform, which helps mitigate the bias. No Linux-specific tools or examples are missing, and the CLI commands are fully usable on Linux/macOS.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Explicitly state that PowerShell examples are intended for Windows users, and Azure CLI is suitable for all platforms.
  • Consider adding a note or section for Linux/macOS users, confirming that all tasks can be completed using Azure CLI.
  • If possible, provide bash or shell script examples for common tasks to further improve Linux parity.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation generally presents cross-platform instructions, but there is minor Windows bias in the 'Prerequisites' and 'Notes' sections. Specifically, it references deploying Node.js applications using Windows PowerShell and links to Windows-centric deployment guides before mentioning general or Linux alternatives. The phrase 'open a command prompt' is used throughout, which may be interpreted as Windows-centric, though it is not exclusive. No Linux/macOS-specific instructions or examples are provided, but the core workflow (Node.js, npm, Azure CLI) is inherently cross-platform.
Recommendations
  • Add explicit references to Linux/macOS terminals (e.g., 'open a terminal or command prompt') throughout the instructions.
  • Provide links to Linux/macOS deployment guides for Node.js applications alongside or before Windows PowerShell guides.
  • Clarify that the instructions and tools (Node.js, npm, Azure CLI) work on Windows, Linux, and macOS.
  • Include troubleshooting notes for common Linux/macOS issues if relevant.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation is generally cross-platform and uses Node.js/TypeScript, which is inherently OS-neutral. However, there are minor signs of Windows bias: references to 'command prompt' and examples that mention Windows PowerShell and Windows-specific deployment guides before Linux equivalents. The phrase 'open a command prompt' is used throughout, which is more closely associated with Windows than Linux/macOS, where 'terminal' is preferred. Additionally, the note about deploying Node.js applications links to a Windows PowerShell guide before mentioning general instructions.
Recommendations
  • Replace 'command prompt' with 'terminal or command prompt' throughout to be inclusive of Linux/macOS users.
  • When referencing deployment guides, provide links for both Windows and Linux/macOS environments, or clarify that instructions apply to all platforms.
  • Avoid mentioning Windows-specific tools (like PowerShell) unless necessary, and always provide Linux/macOS alternatives or equivalents.
  • Ensure screenshots and instructions for Azure portal actions do not assume Windows-only workflows.
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-13 00:00
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, and there is no explicit mention of Bash or Linux-specific tools. The mention of PowerShell and Resource Manager template (often used in Windows environments) before CLI may indicate a subtle Windows-first bias. However, the samples themselves are language-focused and do not show platform bias, and CLI is included in the list.
Recommendations
  • Explicitly mention Bash or Linux shell equivalents alongside PowerShell for command-line examples.
  • List CLI before PowerShell when describing cross-platform options.
  • Provide examples or links for enabling sessions using Bash/Unix shell commands.
  • Clarify that Azure CLI is fully supported on Linux/macOS and provide links to installation guides for those platforms.
GitHub Create Pull Request
← Previous Page 14 of 16 Next →