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 351-375 of 377 flagged pages
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation presents both PowerShell and Azure CLI examples for deploying the template, but PowerShell (a Windows-centric tool) is listed first. The 'Next steps' section highlights PowerShell and Service Bus Explorer (a Windows desktop tool) for management, with no mention of Linux-native or cross-platform GUI alternatives. While Azure CLI is included and cross-platform, the ordering and tool recommendations show a mild Windows bias.
Recommendations
  • List Azure CLI examples before PowerShell, as CLI is cross-platform and preferred for Linux/macOS users.
  • Include management examples using Azure CLI or SDKs for Linux/macOS users in the 'Next steps' section.
  • Mention cross-platform alternatives to Service Bus Explorer, or clarify its OS support.
  • Explicitly state that all deployment steps can be performed on Linux/macOS using Azure CLI.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is mostly cross-platform, but there is some Windows bias present. Notably, references to Windows PowerShell and Windows-specific deployment guides are included in the 'NOTE' section before any mention of Linux/macOS equivalents. The phrase 'open a command prompt' is used generically, which may be interpreted as a Windows-centric instruction. There are no explicit Linux/macOS examples or mentions of their terminal environments, and Windows tools are referenced without parity for other platforms.
Recommendations
  • Replace or supplement references to 'command prompt' with 'terminal' and clarify that instructions apply to Windows, Linux, and macOS.
  • Add explicit instructions or links for creating and deploying Node.js applications on Linux and macOS, not just Windows PowerShell.
  • Provide parity in deployment and troubleshooting guidance for Linux/macOS users, including references to Bash, zsh, or other common shells.
  • Ensure that all tool references (such as PowerShell) are balanced with Linux/macOS equivalents (e.g., Bash scripts, Terminal usage).
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page shows mild Windows bias by referencing Azure PowerShell (a Windows-centric tool) before Azure CLI when describing key regeneration, and by mentioning the Azure portal (which is most commonly used on Windows) as the primary UI for management tasks. The only explicit code example is in C#, a language most associated with Windows development, and the AMQP example references .NET-specific libraries. However, Azure CLI is also documented, and most instructions are platform-agnostic, with no critical steps that are Windows-only.
Recommendations
  • Present Azure CLI instructions before or alongside Azure PowerShell, as CLI is cross-platform.
  • Include explicit Linux/macOS usage notes or screenshots where UI/UX may differ.
  • Provide code samples in additional languages (e.g., Python, JavaScript) that are popular on Linux/macOS.
  • Reference cross-platform SDKs and libraries, not just .NET/C#.
  • Clarify that the Azure portal and CLI are available on all 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-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows Reference
Summary
The documentation references 'AMQP in Service Bus for Windows Server' in the Next steps section, which is a Windows-specific technology. However, the main troubleshooting content is platform-neutral and does not provide examples or instructions that are specific to Windows, Linux, or macOS. No command-line examples or tooling references are present.
Recommendations
  • Add links or references to Linux/macOS equivalents, such as AMQP usage with Service Bus on those platforms.
  • Include troubleshooting guidance or examples for common Linux/macOS AMQP clients.
  • Clarify that the troubleshooting steps apply to all platforms, or specify any platform-specific differences if they exist.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides examples for Azure portal, Azure CLI, Azure PowerShell, ARM templates, and programming languages. However, it includes a dedicated section for Azure PowerShell (a Windows-centric tool), with detailed examples, but does not mention or provide parity for Bash, shell scripting, or Linux-native automation tools. The PowerShell section appears before ARM templates and programming language examples, and there is no explicit mention of cross-platform alternatives to PowerShell for scripting. The CLI section is cross-platform, but the presence and prominence of PowerShell (without Linux alternatives) introduces a mild Windows bias.
Recommendations
  • Add Bash or shell scripting examples for Linux/macOS users, especially for automation tasks.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Consider reordering sections so that cross-platform tools (CLI, ARM templates) appear before Windows-centric tools (PowerShell).
  • Explicitly mention that PowerShell Core is available on Linux/macOS, or provide guidance for Linux users who may encounter PowerShell scripts.
  • Include links or references to Linux/macOS automation best practices for Azure Service Bus.
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-13 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 Service Bus message sessions, but the PowerShell section is given equal prominence to CLI and is presented immediately after CLI. PowerShell is a Windows-centric tool, and no Linux/macOS shell alternatives (e.g., Bash, zsh) are mentioned. There is no explicit prioritization of Windows tools, but the inclusion of PowerShell examples may suggest a slight Windows bias, especially since PowerShell is less commonly used on Linux/macOS. However, the CLI examples are cross-platform and shown first, and ARM template examples are platform-neutral.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS.
  • Note that PowerShell is available cross-platform, but is more commonly used on Windows.
  • Consider adding Bash or zsh shell examples, or explicitly state that CLI commands are suitable for Linux/macOS users.
  • If scripting examples are given, ensure parity by providing both PowerShell and Bash scripts where appropriate.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure portal, Azure CLI, Azure PowerShell, and ARM templates. The PowerShell example is given equal prominence to the CLI example, and is presented before the ARM template. PowerShell is primarily a Windows tool, and its inclusion as a top-level example (rather than, for instance, Bash or shell scripting) reflects a mild Windows bias. However, the Azure CLI example is cross-platform and shown first, and there are no sections that are Windows-only. No Linux/macOS equivalents are missing, and the CLI example is suitable for all platforms.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Consider adding a Bash or shell scripting example for Linux users, or clarify that the CLI example works on all platforms.
  • If PowerShell is included, note that PowerShell Core is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
  • Ensure that examples and instructions do not imply PowerShell is required for non-Windows users.
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-13 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 message counts, but the PowerShell section is given equal prominence despite being Windows-centric. There is no explicit Linux or macOS bias, but PowerShell is traditionally a Windows tool, and its inclusion may suggest a Windows-first mindset. However, the CLI examples are cross-platform and shown before PowerShell, and no Windows-only tools or patterns are referenced. No critical steps are Windows-only.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
  • Note that PowerShell Core is available on Linux/macOS, but provide guidance or links for installation if users wish to use it.
  • Consider adding a brief section or note highlighting Linux/macOS compatibility for all shown commands.
  • If possible, add sample outputs for Azure CLI in addition to PowerShell to reinforce parity.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page shows a mild Windows bias, most notably in the SocketException troubleshooting section, which provides a PowerShell nslookup command and example output in Windows format, without mentioning Linux/macOS equivalents. The documentation also references .NET Framework APIs and Windows-specific concepts (e.g., ServicePointManager), but this is expected given the deprecated .NET focus. No Linux or macOS troubleshooting commands or examples are given, and Windows command syntax is shown first and exclusively.
Recommendations
  • Add equivalent Linux/macOS troubleshooting commands (e.g., 'nslookup <mynamespace>.servicebus.windows.net' or 'dig <mynamespace>.servicebus.windows.net') alongside the PowerShell example.
  • Show example output for Linux/macOS DNS tools to help users interpret results.
  • Where commands are given, present both Windows and Linux/macOS syntax, or use platform-neutral language.
  • Clarify that the guidance applies to all platforms, and note any platform-specific differences where relevant.
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-13 00:00
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 'Node.js Cloud Service using Windows PowerShell' and using the term 'command prompt' throughout. These references appear before or alongside platform-neutral alternatives, but there are no Linux/macOS-specific instructions or examples. All code and CLI instructions are cross-platform, but the documentation subtly favors Windows terminology and resources.
Recommendations
  • Replace or supplement references to 'command prompt' with 'terminal' or 'shell' to be inclusive of Linux/macOS users.
  • Add explicit instructions or links for creating and deploying Node.js applications on Linux/macOS (e.g., using Bash or zsh).
  • When referencing deployment guides, include both Windows and Linux/macOS options, not just PowerShell.
  • Clarify that all CLI commands (npm, az login, node) work on Linux/macOS as well as Windows.
  • Avoid listing Windows-specific resources (e.g., PowerShell guides) before platform-neutral or Linux/macOS resources.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation exhibits minor Windows bias by referencing Windows-specific tools (such as 'Command Prompt' and 'Windows PowerShell') and by mentioning Windows deployment patterns before Linux alternatives. However, the core instructions and code samples are cross-platform and do not prevent Linux/macOS users from completing the tutorial.
Recommendations
  • Replace references to 'Command Prompt' with more neutral terms like 'terminal' or 'command line', and clarify that commands work on Linux/macOS as well.
  • When mentioning deployment guides, include links to Linux/macOS equivalents alongside or before Windows-specific guides.
  • Explicitly state that the Azure CLI and Node.js instructions are valid on Linux/macOS, and provide any necessary platform-specific notes.
  • Avoid mentioning Windows PowerShell in contexts where Bash or other shells are equally applicable.
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-13 00:00
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 Cloud Shell and refers to switching from PowerShell to Bash in Cloud Shell, indicating a slight Windows-first orientation. However, all command examples use the Azure CLI, which is cross-platform and shown in Bash mode. There are no Windows-only tools or examples, but the initial mention of PowerShell and the need to switch away from it may subtly prioritize Windows users.
Recommendations
  • Clarify that Azure CLI works equally well on Windows, Linux, and macOS.
  • Mention installation instructions for Azure CLI on Linux/macOS alongside Windows.
  • Provide explicit reassurance that all examples work natively on Linux/macOS terminals.
  • Consider mentioning that Bash is the default or recommended shell for cross-platform use, not just as an alternative to PowerShell.
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-13 00:00
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 using the Azure Portal and ARM templates, which are cross-platform. However, in the 'Next steps' section, PowerShell is mentioned first as a management tool, with no explicit mention of Azure CLI examples or Linux/macOS-specific instructions. The Service Bus Explorer tool is referenced, but its cross-platform status is unclear. The ordering and emphasis on PowerShell may create a perception of Windows bias.
Recommendations
  • Add explicit Azure CLI management instructions and links alongside PowerShell, especially in 'Next steps'.
  • Clarify the platform compatibility of Service Bus Explorer (e.g., mention if it runs on Linux/macOS or provide alternatives).
  • Where management tools are listed, alternate the order or group them by platform to avoid Windows-first bias.
  • Include example commands for both PowerShell and Azure CLI where relevant.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias in the sections describing how to create queues and topics/subscriptions. PowerShell is listed before CLI as a method for resource creation, and explicit mention of PowerShell (a Windows-centric tool) is present, with no equivalent emphasis on Linux/macOS shell tools. While Azure CLI is mentioned, there are no direct Bash or Linux shell examples, and PowerShell is referenced with direct links, reinforcing a Windows-first approach. No explicit Linux/macOS examples or tools are highlighted.
Recommendations
  • List Azure CLI before PowerShell in resource creation instructions, as CLI is cross-platform.
  • Provide explicit Bash or Linux/macOS shell examples for queue/topic creation and management.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and link to installation guides for all platforms.
  • Add references to Linux/macOS-specific documentation or troubleshooting where relevant.
  • Avoid using 'PowerShell' as a generic term for scripting unless cross-platform PowerShell is intended and clarify its platform support.
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-13 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 PowerShell examples for creating Event Grid subscriptions, but the PowerShell example is given equal prominence to the CLI example, and PowerShell is a Windows-centric tool. There is no explicit mention of Linux/macOS alternatives for PowerShell, nor is there a clear prioritization of cross-platform tools (CLI) over Windows-specific ones. The CLI example is shown first, which slightly reduces the bias.
Recommendations
  • Clearly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add a note that PowerShell examples are primarily for Windows users, and provide guidance for using PowerShell Core on Linux/macOS if relevant.
  • Ensure CLI examples are always shown before PowerShell, and consider omitting PowerShell examples unless there is a Windows-specific need.
  • Add explicit Linux/macOS instructions or troubleshooting notes where platform differences may arise.
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-13 00:00
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 CLI and refers to switching Cloud Shell from PowerShell to Bash, which may suggest a Windows-first perspective. However, all command examples use Azure CLI in Bash syntax, which is cross-platform. There are no explicit Linux/macOS examples or references to Linux-specific tools or patterns, and PowerShell is mentioned before Bash in the Cloud Shell instructions.
Recommendations
  • Explicitly mention that Azure CLI works on Linux/macOS and provide installation links for those platforms.
  • Include a brief note or section for Linux/macOS users, confirming that all commands work natively in their environments.
  • When referencing Cloud Shell, mention Bash first or equally with PowerShell, and clarify that Bash is the default for many users.
  • Add a sentence or link to Linux/macOS installation instructions for Azure CLI.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation shows mild Windows bias by referencing Windows-specific tools and patterns, such as mentioning 'Node.js cloud service using Windows PowerShell' and using 'command prompt' terminology. Windows deployment instructions are referenced before cross-platform alternatives. However, all code and commands (npm, node, az CLI) are cross-platform, and no critical steps are Windows-only.
Recommendations
  • Replace 'command prompt' with 'terminal' or clarify that all commands work on Windows, Linux, and macOS.
  • Avoid referencing Windows PowerShell as the primary deployment method; provide equivalent Linux/macOS instructions or links.
  • Explicitly state that all steps and tools (Node.js, Azure CLI, npm) work on Linux/macOS.
  • Add a note or section for Linux/macOS users, confirming parity and listing any OS-specific considerations.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus JMS 2.0 developer guide .../articles/service-bus-messaging/jms-developer-guide.md
Low Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page exhibits a subtle Windows bias by linking to instructions for configuring managed identities specifically on Windows VMs when describing system assigned managed identity setup. There are no explicit Linux or cross-platform instructions or examples for this step, and no mention of Linux equivalents or parity. The rest of the guide is Java-centric and platform-neutral, but the identity setup reference is Windows-first.
Recommendations
  • Provide links or instructions for configuring managed identities on Linux VMs and other supported platforms, not just Windows.
  • Add a note clarifying that managed identities are available for both Windows and Linux VMs, with links to both sets of instructions.
  • Review all referenced setup guides to ensure Linux parity and cross-platform applicability.
  • Consider including a general Azure CLI example for managed identity setup, which works on both Windows and Linux.
GitHub Create Pull Request
Service Bus Messaging Azure Service Bus JMS 2.0 developer guide .../articles/service-bus-messaging/jms-developer-guide.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page exhibits a subtle Windows bias by linking to Windows-specific instructions for configuring managed identities (e.g., 'qs-configure-portal-windows-vm.md') when describing authentication setup. No Linux-specific or cross-platform instructions are provided or referenced for these steps, and there are no examples or guidance for Linux VM configuration or command-line tools (such as Azure CLI or Bash). The rest of the page is platform-neutral, focusing on Java code and Azure concepts.
Recommendations
  • Add links and instructions for configuring managed identities on Linux VMs, such as 'qs-configure-portal-linux-vm.md', alongside the Windows VM link.
  • Provide cross-platform guidance for authentication setup, including Azure CLI and Bash examples where relevant.
  • Ensure that all referenced setup guides and quickstarts have Linux equivalents and are mentioned equally.
  • Review other linked documentation to confirm Linux parity and add Linux-specific or cross-platform examples where missing.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-go-how-to-use-queues.md ...vice-bus-messaging/service-bus-go-how-to-use-queues.md
Low Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation shows mild Windows bias by mentioning Windows-specific terminology (e.g., '.servicebus.windows.net') and by listing PowerShell instructions for setting environment variables immediately after Bash, rather than giving Linux-specific instructions more prominence. However, all code examples and CLI instructions are cross-platform, and Bash is presented first for environment variable setup.
Recommendations
  • Clarify that the Azure Service Bus namespace format (e.g., '.servicebus.windows.net') is not Windows-specific and applies to all platforms.
  • Explicitly state that both Bash and PowerShell instructions are provided for cross-platform compatibility, and consider listing Linux/Bash instructions first to reinforce parity.
  • Add a note that the Go SDK and Azure CLI are cross-platform and work on Windows, Linux, and macOS.
  • Consider including a table or section summarizing environment variable setup for Linux, macOS, and Windows, to make parity clear.
  • Avoid using Windows-centric terminology unless necessary, and clarify when terms are platform-agnostic.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/message-sessions.md ...ain/articles/service-bus-messaging/message-sessions.md
Low Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page lists Windows-specific tools (PowerShell) before cross-platform alternatives (CLI, Resource Manager template) when describing how to enable message sessions. No explicit Linux or Bash examples are provided, and the ordering of tools may suggest a Windows-first approach, though the page does mention cross-platform options.
Recommendations
  • Reorder tool mentions to list cross-platform options (e.g., Azure CLI) before Windows-specific tools (e.g., PowerShell).
  • Explicitly mention that Azure CLI and Resource Manager templates are cross-platform and suitable for Linux/macOS users.
  • Provide example commands for both PowerShell and Bash/Azure CLI where relevant.
  • Consider adding a short section or note highlighting Linux/macOS parity and linking to platform-specific guidance if available.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/transport-layer-security-enforce-minimum-version.md ...ng/transport-layer-security-enforce-minimum-version.md
Low Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or tooling references (such as PowerShell or Windows tools), but it also does not provide any command-line or code examples at all. This omission means there is no explicit Windows bias, but there is also a lack of Linux parity, as users on any platform are not shown how to enforce the minimum TLS version using CLI tools (e.g., Azure CLI, which is cross-platform).
Recommendations
  • Add step-by-step examples using Azure CLI commands to configure the minimum TLS version, as Azure CLI is cross-platform and works on both Windows and Linux.
  • If PowerShell or Azure Portal instructions are added in the future, ensure equivalent Azure CLI (or REST API) examples are provided and presented first or alongside to avoid Windows-first bias.
  • Explicitly mention that the configuration can be performed from any platform using Azure CLI or REST API, not just from Windows environments.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/includes/service-bus-create-topic-subscription-portal.md ...cludes/service-bus-create-topic-subscription-portal.md
Low Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation only provides instructions for creating an Azure Service Bus topic and subscription using the Azure portal, with no mention of command-line tools or scripts. There are no examples for either Windows (e.g., PowerShell) or Linux (e.g., Azure CLI, Bash), but the absence of any CLI-based instructions means Linux users do not see parity with potential Windows-centric workflows.
Recommendations
  • Add examples using the Azure CLI for creating topics and subscriptions, which work cross-platform (Linux, macOS, Windows).
  • If scripting is discussed in future updates, ensure both PowerShell and Bash examples are provided.
  • Explicitly mention that the Azure portal is platform-agnostic, but provide links or references to CLI documentation for users who prefer command-line or automated approaches.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/jms-developer-guide.md .../articles/service-bus-messaging/jms-developer-guide.md
Low Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation demonstrates a subtle Windows bias by linking to Windows-specific instructions for creating a system-assigned managed identity (specifically, a portal guide for Windows VMs) without mentioning or linking to Linux VM equivalents. No explicit PowerShell or Windows-only tooling is shown, and most code samples are Java and platform-agnostic, but the initial reference to Windows VM setup may disadvantage Linux users.
Recommendations
  • When referencing identity creation (e.g., system-assigned managed identity), provide links to both Windows and Linux VM setup guides, or use a platform-neutral entry point.
  • Explicitly mention that the instructions apply to both Windows and Linux environments where possible, or clarify any platform-specific steps.
  • If linking to a portal-based guide, ensure it covers both Windows and Linux VMs, or provide parallel links for each.
  • Audit other identity and authentication documentation references to ensure Linux parity.
GitHub Create Pull Request
Service Bus Messaging https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-transactions.md ...cles/service-bus-messaging/service-bus-transactions.md
Low Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not display overt Windows bias in terms of mentioning Windows-specific tools, PowerShell, or Windows-first patterns. However, it demonstrates a bias by only providing C# code examples (with .NET/TransactionScope), which are most commonly associated with Windows development environments. There are no examples or references for Linux-friendly languages (such as Python, Java, or Node.js), nor are there CLI or cross-platform command-line examples. This limits the accessibility of the documentation for Linux or non-Windows developers.
Recommendations
  • Add code examples in additional languages that are popular on Linux, such as Python (using azure-servicebus), Java, or JavaScript/TypeScript.
  • Include Azure CLI or cross-platform command-line examples for relevant operations, where possible.
  • Reference or link to equivalent samples or documentation for Linux/macOS environments.
  • Clarify that the C# example is cross-platform if using .NET Core/5+/6+, or provide explicit instructions for running on Linux.
GitHub Create Pull Request
← Previous Page 15 of 16 Next →