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 51-75 of 91 flagged pages
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, validation, and cleanup, but PowerShell is presented as an equal alternative throughout. In the 'Next steps' section, PowerShell is mentioned first for management tasks, and there is a dedicated link for managing Service Bus with PowerShell, while no equivalent Linux/macOS management guide is referenced. The Service Bus Explorer tool is referenced, which is Windows-only, without mentioning cross-platform alternatives.
Recommendations
- Ensure that CLI examples are presented before PowerShell, as CLI is cross-platform.
- Add links to CLI-based management guides for Service Bus, not just PowerShell.
- Explicitly mention that Azure CLI works on Linux/macOS/Windows, and clarify PowerShell's platform support.
- Reference cross-platform Service Bus management tools (e.g., Azure Portal, CLI scripts, or third-party tools that run on Linux/macOS) alongside Service Bus Explorer.
- In 'Next steps', provide parity by listing CLI management resources and tools for Linux/macOS users.
Create Pull Request
Service Bus Messaging
Configure network service endpoints
...service-bus-messaging/service-bus-service-endpoints.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides Azure PowerShell instructions and mentions Azure CLI, but PowerShell examples are given more detail and are listed after CLI, which is cross-platform. There are no explicit Linux/macOS-specific instructions or examples, but the CLI section is present. The Resource Manager template and REST API sections are platform-neutral. However, PowerShell is a Windows-centric tool (despite being available on Linux, it's less commonly used there), and its prominence may create friction for Linux/macOS users.
Recommendations
- Provide explicit Azure CLI command examples for all operations currently shown only in PowerShell.
- List Azure CLI instructions before PowerShell, as CLI is cross-platform and more widely used on Linux/macOS.
- Clarify that both CLI and PowerShell are available on all platforms, but CLI is typically preferred on Linux/macOS.
- Add a note or section for Linux/macOS users, highlighting CLI usage and any platform-specific considerations.
Service Bus Messaging
Troubleshooting guide for Azure Service Bus | Microsoft Docs
...ice-bus-messaging/service-bus-troubleshooting-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, .exe utilities) are mentioned first or exclusively in troubleshooting steps, with Linux equivalents sometimes provided but less prominently. Some diagnostic recommendations (e.g., using 'psping.exe') are Windows-only, and logging/tracing guidance is .NET-centric, which is more common on Windows. Linux/macOS users may need to infer or research equivalent commands/tools.
Recommendations
- Present Linux/macOS commands and tools alongside Windows examples, giving them equal prominence.
- For every Windows-specific tool (e.g., 'psping.exe'), suggest cross-platform alternatives (e.g., 'hping', 'nmap', 'nc').
- Include Bash or shell script examples for connectivity and diagnostics, not just PowerShell.
- Reference cross-platform SDKs and logging/tracing solutions, not only .NET.
- Add explicit notes or sections for Linux/macOS troubleshooting steps where workflows differ.
Service Bus Messaging
Create Azure Service Bus resources using templates
...bus-messaging/service-bus-resource-manager-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exclusively provides instructions and examples using PowerShell, which is traditionally a Windows-centric tool, and does not mention or provide equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash). All deployment steps, authentication, and resource management are described using PowerShell cmdlets, with no reference to cross-platform alternatives.
Recommendations
- Add equivalent deployment instructions using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Include Bash shell examples for template deployment and resource group management.
- Explicitly mention that Azure PowerShell is available on Linux/macOS, if relevant, and provide installation instructions for those platforms.
- Present both PowerShell and Azure CLI examples side-by-side, or at least link to CLI documentation.
- Avoid language or structure that assumes a Windows environment (e.g., file path syntax, tool installation).
Service Bus Messaging
Tutorial: Update inventory using Azure portal and topics/subscriptions
...ng/service-bus-tutorial-topics-subscriptions-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The tutorial demonstrates a notable Windows bias. It references Windows-specific tools (Visual Studio), uses Windows-centric terminology ('Command Prompt', 'PowerShell'), and omits explicit instructions or examples for Linux/macOS users. There are no mentions of cross-platform alternatives (e.g., VS Code, Bash), and steps assume a Windows environment for building and running .NET code. No Linux/macOS shell commands or setup guidance are provided.
Recommendations
- Add explicit instructions for Linux/macOS users, including terminal commands and environment setup.
- Mention and provide examples using VS Code or JetBrains Rider as cross-platform IDE alternatives.
- Replace 'Command Prompt' and 'PowerShell' references with 'terminal' or provide both Windows and Linux/macOS command examples.
- Clarify that .NET Core/.NET 5+ is cross-platform and provide installation links for Linux/macOS.
- Include screenshots or notes showing the process on Linux/macOS.
- Reference cross-platform tools (e.g., Azure CLI) for resource management alongside portal instructions.
Service Bus Messaging
Configure the minimum TLS version for a Service Bus namespace using ARM
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/transport-layer-security-configure-minimum-version.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation demonstrates a moderate Windows bias. While Azure CLI examples (cross-platform) are provided, PowerShell examples are given equal prominence. The section on checking the minimum TLS version recommends ARMClient.exe (a Windows-only tool) and provides only PowerShell commands for token acquisition, with no mention of Linux/macOS alternatives (e.g., Azure CLI, curl, or native REST calls). Windows-centric tools and patterns are mentioned first or exclusively in some critical steps.
Recommendations
- Provide Linux/macOS-friendly alternatives for ARMClient.exe, such as using Azure CLI (`az account get-access-token`) or curl for REST API calls.
- Include bash or shell script examples alongside PowerShell, especially for authentication and API querying.
- Clearly indicate which tools are cross-platform and which are Windows-only.
- Where PowerShell is used, offer equivalent commands for bash/zsh environments.
- Avoid recommending Windows-only tools as the primary method for critical steps.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows setup instructions are presented first and in more detail, with explicit PowerShell and WSL steps. Linux/macOS instructions are less detailed and lack step-by-step guidance. Windows-specific tooling (PowerShell, WSL) is emphasized, and file path examples default to Windows format. Linux/macOS users must infer some steps and may encounter friction.
Recommendations
- Provide equally detailed, step-by-step instructions for Linux and macOS, including terminal commands and navigation.
- Include Linux/macOS-specific file path examples (e.g., /home/user/config.json) alongside Windows examples.
- Avoid presenting Windows instructions first; use tabs or parallel sections for each OS.
- Clarify any OS-specific prerequisites (e.g., Docker installation links for Linux/macOS).
- Add explicit Linux/macOS commands for running scripts (e.g., bash ./LaunchEmulator.sh) and navigating directories.
- Mention any differences in Docker Desktop usage or alternatives for Linux/macOS.
Service Bus Messaging
Azure Service Bus - message count
...ain/articles/service-bus-messaging/message-counters.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for retrieving message counts, but the PowerShell section is prominent and detailed, which may favor Windows users. The CLI examples are cross-platform, but PowerShell is typically associated with Windows, and no Linux/macOS-specific shell examples (e.g., Bash scripting, piping, jq usage) are provided. The order of presentation puts Azure CLI before PowerShell, but the PowerShell section is more verbose and includes sample outputs, which may subtly prioritize Windows workflows.
Recommendations
- Add Linux/macOS-specific examples, such as using Bash and jq to parse Azure CLI output.
- Include notes clarifying that Azure CLI works on all platforms, and PowerShell Core is available cross-platform.
- Provide sample outputs for Azure CLI, not just PowerShell.
- Consider mentioning or linking to platform-specific setup guides for both CLI and PowerShell.
Service Bus Messaging
Troubleshoot AMQP errors in Azure Service Bus | Microsoft Docs
...service-bus-messaging/service-bus-amqp-troubleshoot.md
Low Priority
View Details →
Detected Bias Types
Windows Reference
Summary
The documentation page is largely platform-neutral in its error descriptions and troubleshooting guidance. However, in the 'Next steps' section, one of the three recommended links is specifically about 'AMQP in Service Bus for Windows Server', which may suggest a Windows-centric focus in additional resources. No examples, tools, or commands are given that are specific to Windows or PowerShell, nor are Windows patterns prioritized in the main content.
Recommendations
- Add equivalent Linux/macOS resources in the 'Next steps' section, such as guides for using AMQP with Service Bus on Linux or cross-platform SDKs.
- Clarify that the troubleshooting steps and errors apply equally to all platforms, or provide platform-specific notes if there are differences.
- Ensure that future documentation includes examples or references for both Windows and Linux/macOS environments where relevant.
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 →
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 automation method, which is Windows-centric. The CLI example is present, but PowerShell is listed as a separate main method, potentially implying parity. There are no Linux-specific tools or shell examples, and PowerShell is not cross-platform by default for many users.
Recommendations
- Explicitly state that Azure CLI works cross-platform (Linux, macOS, Windows) and is recommended for non-Windows environments.
- Add bash/zsh shell script examples for Linux/macOS users, especially for automation scenarios.
- Clarify that PowerShell Core is available cross-platform, or provide links/instructions for Linux/macOS PowerShell usage if PowerShell examples are retained.
- List Azure CLI examples before PowerShell to reduce Windows-first perception.
- Mention that all tasks can be completed on Linux/macOS using Azure CLI.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions Azure PowerShell as an alternative to Azure Cloud Shell and refers to switching Cloud Shell from PowerShell to Bash, indicating a Windows-first perspective. However, all command examples use Azure CLI, which is cross-platform, and instructions do not rely on Windows-only tools or patterns.
Recommendations
- Mention Linux/macOS terminal usage explicitly alongside Windows/PowerShell.
- Clarify that Azure CLI works natively on Linux/macOS and provide installation links for those platforms.
- Avoid listing PowerShell as the primary alternative; instead, present Bash and PowerShell equally.
- Add a brief note that all CLI commands work identically on Linux, macOS, and Windows.
Service Bus Messaging
Enable Azure Service Bus message sessions | Microsoft Docs
...icles/service-bus-messaging/enable-message-sessions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for enabling Service Bus message sessions. However, the PowerShell section is given equal prominence to the CLI, despite PowerShell being primarily a Windows tool (with limited cross-platform adoption compared to Bash/CLI). The PowerShell examples are presented immediately after the CLI, rather than being clearly marked as Windows-specific or de-emphasized for cross-platform users. There are no Linux/macOS-specific instructions or notes clarifying platform compatibility for PowerShell. No explicit Windows-only tools are mentioned, and CLI examples are present, but the documentation does not prioritize Linux-native workflows.
Recommendations
- Clearly label PowerShell sections as 'Windows only' or 'Windows-focused', and note cross-platform limitations.
- Present Azure CLI examples before PowerShell, emphasizing CLI as the recommended cross-platform approach.
- Add a brief note at the top clarifying that Azure CLI works natively on Linux/macOS/Windows, while PowerShell is primarily for Windows.
- Consider adding Bash script examples or links to Linux/macOS-specific guidance for parity.
- If PowerShell is cross-platform, clarify its installation and usage on Linux/macOS.
Service Bus Messaging
Enable partitioning in Azure Service Bus Premium namespaces
...les/service-bus-messaging/enable-partitions-premium.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for enabling partitioning in Azure Service Bus Premium namespaces. However, the PowerShell example is given its own dedicated section, and appears immediately after the CLI example, which may suggest a slight Windows-first bias. There is no explicit Linux/macOS example for PowerShell (which is Windows-centric), nor is there mention of Bash or shell scripting alternatives. The CLI example is cross-platform, but PowerShell is highlighted as a primary method, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Consider reordering sections to present CLI before PowerShell, or explicitly state platform applicability.
- Add a note that PowerShell Core is available on Linux/macOS, if relevant, or provide Bash/shell script alternatives where appropriate.
- Ensure parity in examples for all major platforms, especially in sections where Windows-specific tools are featured.
Service Bus Messaging
Azure Service Bus message sessions | Microsoft Docs
...ain/articles/service-bus-messaging/message-sessions.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references enabling message sessions using Azure portal, PowerShell, CLI, and Resource Manager templates before mentioning programming languages. PowerShell is a Windows-centric tool, and its mention before CLI (which is cross-platform) and without explicit Linux/macOS instructions suggests a mild Windows-first bias. However, the actual code samples provided are language-specific (.NET, Java, Python, JavaScript) and do not show platform bias, and there are no sections that are Windows-only or PowerShell-heavy.
Recommendations
- Explicitly mention that Azure CLI and Resource Manager templates are cross-platform and provide example commands for both Windows (PowerShell) and Linux/macOS (Bash).
- If PowerShell is referenced, also provide equivalent Bash or shell commands for Linux/macOS users.
- Consider listing CLI before PowerShell to emphasize cross-platform support.
- Add a note clarifying that all features and APIs described are available on Linux and macOS, not just Windows.
Service Bus Messaging
Azure Service Bus JMS 2.0 developer guide
.../articles/service-bus-messaging/jms-developer-guide.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild Windows bias by linking to Windows-specific instructions first when describing how to create a system assigned managed identity. The referenced quickstart guide for managed identities points to configuring via the Azure Portal for a Windows VM, without mentioning Linux VM equivalents or providing parity in Linux/macOS instructions. However, the core Java code samples and authentication flows are platform-agnostic and do not rely on Windows-specific tools or patterns.
Recommendations
- When referencing managed identity creation, include links and instructions for both Windows and Linux VMs, or use a neutral Azure Portal guide that covers all platforms.
- Explicitly state that the Java code samples and authentication flows work on Linux/macOS as well as Windows.
- Where possible, avoid referencing platform-specific quickstarts unless all major platforms are covered equally.
- Add a note or section clarifying any platform requirements or differences for identity setup, especially for Linux users.
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 →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell instructions for setting the required environment variable, with Bash shown first. There are no Windows-only tools or patterns, and all examples are cross-platform. The only minor bias is the order in which Bash and PowerShell instructions are presented.
Recommendations
- Continue providing both Bash and PowerShell instructions for environment variable setup.
- Consider explicitly mentioning that all steps work on Linux, macOS, and Windows.
- If possible, add a short note confirming Linux/macOS compatibility for authentication (e.g., Azure CLI works on all platforms).
Service Bus Messaging
Azure Service Bus - messaging exceptions (deprecated) | Microsoft Docs
...vice-bus-messaging/service-bus-messaging-exceptions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. The only explicit command-line example for troubleshooting (nslookup) is shown using Windows PowerShell syntax (PS C:\>), with no mention of Linux/macOS equivalents. There are no Linux/macOS-specific troubleshooting steps or command examples, and Windows-style output is shown first and exclusively. The rest of the content is platform-neutral, focusing on .NET exceptions and Azure Service Bus concepts.
Recommendations
- Provide Linux/macOS equivalents for command-line examples, e.g., show 'nslookup' or 'dig' usage in bash/zsh.
- Include troubleshooting steps relevant to Linux/macOS environments (e.g., DNS resolution, firewall checks).
- When showing command-line output, alternate or combine Windows and Linux/macOS formats.
- Clarify that the guidance applies to all platforms supported by the .NET SDK, not just Windows.
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 →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates minor Windows bias by referencing Windows-specific tools and patterns before their cross-platform or Linux equivalents. Notably, instructions repeatedly refer to 'Command Prompt' and mention 'Node.js cloud service using Windows PowerShell' as a deployment option, while omitting explicit references to Linux/macOS terminals or shell environments. The language used (e.g., 'open a Command Prompt window') may cause confusion or friction for Linux/macOS users, though the actual code and commands (npm, node, az CLI) are cross-platform.
Recommendations
- Replace references to 'Command Prompt' with 'terminal' or 'command-line interface' to be inclusive of all platforms.
- Explicitly state that all commands (npm, node, az CLI) work on Linux, macOS, and Windows.
- Add links or notes for Linux/macOS users on installing Node.js and Azure CLI using their native package managers.
- Include example terminal commands for Linux/macOS (e.g., bash/zsh) alongside Windows examples if platform-specific nuances exist.
- Remove or supplement references to 'Node.js cloud service using Windows PowerShell' with equivalent Linux/macOS deployment guides.
Service Bus Messaging
Azure Service Bus messaging - queues, topics, and subscriptions
...s-messaging/service-bus-queues-topics-subscriptions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation lists PowerShell as a primary method for creating Service Bus entities, and in both the 'Create queues' and 'Create topics and subscriptions' sections, PowerShell is mentioned before the Azure CLI. This ordering and emphasis may suggest a Windows-centric approach, as PowerShell is most commonly used on Windows. There are no explicit Linux/macOS-only examples, but the CLI is present as an option. No critical functionality is Windows-only, but the ordering and tool emphasis may create friction for Linux/macOS users.
Recommendations
- List Azure CLI before PowerShell in creation instructions, as CLI is cross-platform.
- Add explicit notes that both PowerShell and CLI are available on all platforms, and link to installation guides for each.
- Provide example commands for both PowerShell and CLI side-by-side, or default to CLI for cross-platform parity.
- Ensure that any referenced scripts or samples do not assume Windows-only tools.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page generally avoids platform-specific instructions, focusing on ARM templates and Azure Portal, which are cross-platform. However, in the 'Next steps' section, PowerShell is mentioned as the first management tool, and there is no explicit mention of Azure CLI usage for Linux/macOS users. The Service Bus Explorer tool is also referenced, which is Windows-only, but this is not emphasized. Overall, the bias is minor and mostly present in tool recommendations and ordering.
Recommendations
- Add explicit instructions or links for managing Service Bus resources using Azure CLI, especially for Linux/macOS users.
- List Azure CLI management options before or alongside PowerShell in the 'Next steps' section.
- Clarify platform compatibility for Service Bus Explorer and suggest cross-platform alternatives if available.
- Ensure that any referenced management tools or scripts include both Windows and Linux/macOS examples.
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 →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation demonstrates minor Windows bias, primarily by referencing Windows-specific tools and patterns. Notably, it suggests using 'Node.js Cloud Service using Windows PowerShell' as an option for creating and deploying Node.js applications, and refers to 'command prompt' throughout, which is a Windows-centric term. Linux/macOS equivalents (e.g., Bash, Terminal) are not mentioned, and the order of tool references sometimes places Windows options first.
Recommendations
- Replace 'command prompt' with 'terminal or command prompt' throughout, or clarify that any shell (Bash, zsh, PowerShell, etc.) can be used.
- When referencing deployment guides, include links to Linux/macOS equivalents (e.g., deploying Node.js apps with Azure CLI on Linux/macOS).
- Mention that Azure CLI is cross-platform and works on Linux/macOS as well as Windows.
- Avoid referencing Windows PowerShell as the primary example; if mentioned, also provide Bash or shell alternatives.
- Add explicit notes or examples for Linux/macOS users where file paths, shell commands, or environment setup may differ.
Service Bus Messaging
Get started with Azure Service Bus topics (TypeScript)
...service-bus-typescript-how-to-use-topics-subscriptions.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page displays minor Windows bias by referencing Windows-specific tools and patterns, such as mentioning 'Node.js Cloud Service using Windows PowerShell' as a deployment option and using the generic term 'command prompt' instead of 'terminal'. Windows tools are mentioned before Linux equivalents, and there is no explicit mention of Linux/macOS alternatives in deployment or command-line instructions. However, the actual code and commands (npm, node) are cross-platform, and Linux/macOS users can follow the instructions with minimal adaptation.
Recommendations
- Replace 'command prompt' with 'terminal' or clarify that instructions apply to both Windows and Linux/macOS.
- Add explicit references to Linux/macOS deployment guides alongside Windows PowerShell options.
- Ensure that all tooling instructions (Azure CLI, npm, node) mention cross-platform compatibility.
- Provide links or notes for Linux/macOS users where Windows-specific tools (like PowerShell) are mentioned.
- Use inclusive language such as 'open a terminal (Windows Command Prompt, PowerShell, macOS Terminal, or Linux shell)'.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions Azure PowerShell as an alternative to Cloud Shell and instructs users to switch to Bash if Cloud Shell is in PowerShell mode, indicating a Windows-first approach. PowerShell is referenced before Bash, and there is no mention of Linux/macOS-specific installation or usage patterns. However, all command examples use Azure CLI in Bash syntax, which is cross-platform.
Recommendations
- Mention Linux/macOS explicitly as supported platforms for Azure CLI.
- Provide installation instructions or links for Azure CLI on Linux/macOS alongside Windows.
- List Bash as the default Cloud Shell mode, or present Bash before PowerShell.
- Clarify that all CLI commands work on Linux/macOS terminals, not just in Cloud Shell.
- Avoid referencing PowerShell before Bash unless contextually necessary.
Service Bus Messaging
Get started with Azure Service Bus queues (TypeScript)
...-messaging/service-bus-typescript-how-to-use-queues.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates minor Windows bias by referencing Windows-specific tools and patterns, such as suggesting deployment using Windows PowerShell and mentioning 'command prompt' as the default terminal. The link to creating and deploying a Node.js application includes a Windows PowerShell tutorial before any Linux equivalent. However, the actual code samples and instructions (npm, Node.js, Azure CLI) are cross-platform and do not prevent Linux/macOS users from completing the tutorial.
Recommendations
- Add explicit references to Linux/macOS terminals (e.g., Bash, Terminal.app) alongside 'command prompt' and PowerShell.
- Provide links or brief instructions for deploying Node.js applications on Linux/macOS, not just Windows PowerShell.
- Where examples mention 'open a command prompt', clarify that any terminal (Bash, zsh, etc.) can be used.
- Ensure that any referenced deployment guides include Linux/macOS options or alternatives.
Service Bus Messaging
Enable partitioning in Azure Service Bus basic or standard
...vice-bus-messaging/enable-partitions-basic-standard.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for enabling partitioning in Azure Service Bus. While the CLI is cross-platform, PowerShell is traditionally associated with Windows, and its inclusion may signal a Windows bias. However, the CLI examples are presented before PowerShell, and there are no sections that are Windows-only or missing Linux equivalents. No Windows-specific tools or patterns are mentioned exclusively, and the ARM template examples are platform-neutral. The severity of bias is low, as Linux/macOS users can fully complete the task using the CLI or ARM templates.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, but CLI is generally preferred for Linux/macOS users.
- Add a brief note or table comparing CLI and PowerShell usage across platforms.
- Ensure future documentation includes Bash shell examples where relevant, especially for scripting.
- Explicitly mention that all shown methods (CLI, ARM templates) work on Linux/macOS.