Service Bus Messaging

134
Total Pages
71
Linux-Friendly Pages
63
Pages with Bias
47.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (85)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/authenticate-application.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by primarily referencing the Azure portal (a GUI tool most closely associated with Windows workflows), providing only .NET/C# code samples (which are most common on Windows), and omitting Linux-specific examples or command-line authentication flows. While Azure CLI is mentioned in the 'Next steps', the main authentication and role assignment instructions focus on portal and .NET SDK usage, with no parity for Linux-native tools, languages, or shell environments.
Recommendations:
  • Add equivalent authentication code samples using cross-platform languages such as Python (with azure-identity and azure-servicebus), Java, or Node.js.
  • Include examples of using Azure CLI (az login, az ad sp create-for-rbac, etc.) for authentication and role assignment, showing commands runnable on Linux/macOS.
  • Provide guidance for authenticating from Linux-based environments, such as using managed identities on Linux VMs, containers, or Azure Functions running on Linux.
  • Reference Linux-friendly editors and environments (e.g., VS Code, bash) alongside or instead of Windows-centric tools.
  • Ensure that all screenshots and step-by-step instructions are not specific to the Windows Azure portal experience, or clarify that the portal is cross-platform.
  • Where .NET is used, add parallel samples for other languages/platforms that are popular on Linux.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/configure-customer-managed-key.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation demonstrates a Windows bias by providing all command-line examples exclusively in PowerShell, referencing PowerShell cmdlets (e.g., New-AzResourceGroupDeployment, Set-AzureRmKeyVaultAccessPolicy) without Bash or Linux shell equivalents. There are no explicit Linux/Unix shell examples, and the use of PowerShell is presented as the default method for scripting and automation. While Azure CLI is mentioned for some vault creation steps, all automation and scripting for deployment and identity management is shown only with PowerShell, which is traditionally associated with Windows environments.
Recommendations:
  • Provide equivalent Bash/Azure CLI examples for all PowerShell commands, especially for deployment and access policy steps.
  • Explicitly mention that all PowerShell commands can be run cross-platform (if true), or clarify any Windows-specific requirements.
  • For each PowerShell example, add a corresponding Azure CLI or Bash example, and consider presenting CLI first or side-by-side.
  • Reference cross-platform tools and patterns (e.g., Azure CLI, REST API) before or alongside Windows-specific tools.
  • Add a section or note for Linux/macOS users, highlighting any differences or prerequisites.
  • Ensure that automation and scripting guidance is not limited to Windows/PowerShell, to support users on all platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/message-sessions.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-typescript-how-to-use-topics-subscriptions.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a mild Windows bias. While most instructions are cross-platform (using Node.js, npm, and Azure CLI), there are several references that prioritize or exclusively mention Windows tools or patterns. Notably, the instructions refer to 'command prompt' (a Windows term) instead of 'terminal' or 'shell', and a key link for deploying Node.js apps points to a Windows PowerShell-based tutorial, with no equivalent Linux/Mac instructions or links. There are no explicit Linux shell or macOS Terminal examples, and the language used assumes a Windows environment.
Recommendations:
  • Replace or supplement 'command prompt' with 'terminal' or 'shell' to be inclusive of Linux and macOS users.
  • Where links are provided for deploying Node.js applications (e.g., 'Node.js Cloud Service using Windows PowerShell'), add equivalent links or instructions for Linux and macOS environments.
  • Explicitly mention that all npm and Node.js commands work on Linux, macOS, and Windows, and provide example shell commands where appropriate.
  • If referencing editors, note that Visual Studio Code is cross-platform, or suggest alternatives available on Linux/macOS.
  • Review included snippets and referenced tutorials to ensure they do not contain Windows-specific commands or paths, or provide alternatives if they do.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-duplicate-detection.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation provides both Azure CLI and Azure PowerShell examples for enabling duplicate message detection in Azure Service Bus. However, there is a notable emphasis on PowerShell, which is traditionally a Windows-centric tool, and the PowerShell section is given equal prominence to the cross-platform Azure CLI. There are no explicit Linux shell (bash) or scripting examples, and no mention of Linux-specific tools or patterns. The ordering of sections places Azure CLI before PowerShell, which is positive, but the heavy inclusion of PowerShell commands and lack of Linux-native shell examples may make the documentation feel Windows-biased.
Recommendations:
  • Add bash (Linux shell) script examples alongside Azure CLI, demonstrating how to use the CLI in a Linux environment.
  • Clarify in the PowerShell section that Azure PowerShell is available cross-platform, but also provide equivalent bash or shell scripting examples for Linux users.
  • Consider including a table or summary comparing the different approaches (Azure portal, CLI, PowerShell, ARM templates) and their platform compatibility.
  • If possible, add notes or links to Linux-specific guidance for installing and using the Azure CLI and PowerShell on Linux.
  • Ensure that future documentation includes Linux-native command-line examples where applicable, not just PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-partitions-premium.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation presents both Azure CLI and Azure PowerShell examples for enabling partitioning, but the PowerShell section is given equal prominence to the CLI, despite PowerShell being primarily a Windows-centric tool (even though it is now cross-platform, its usage is still most common on Windows). There are no Linux shell or Bash-specific examples, and the order of examples (CLI before PowerShell) is good, but the PowerShell section could be seen as Windows-focused. No explicit Windows-only tools or patterns are used, but the lack of Linux/Bash-specific guidance or troubleshooting tips may disadvantage Linux users.
Recommendations:
  • Clarify that Azure CLI commands are fully cross-platform and preferred for Linux/macOS users.
  • Add Bash shell scripting examples or notes for Linux users, especially for automation scenarios.
  • Mention that PowerShell is available cross-platform, but note its prevalence on Windows.
  • Provide troubleshooting tips or common issues for both Windows and Linux environments.
  • Consider adding a table comparing CLI and PowerShell usage scenarios for different OSes.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-ip-filtering.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by explicitly providing a dedicated 'Azure PowerShell' section with command references, while the 'Azure CLI' section is minimal and lacks concrete command examples. The PowerShell section is more detailed and appears after the CLI, but the CLI section is underdeveloped. There are no Linux-specific instructions or examples, and the only deployment link for Resource Manager templates points to a PowerShell-based deployment guide. No Bash or Linux shell examples are provided, and the documentation assumes familiarity with Windows-centric tools.
Recommendations:
  • Provide explicit Azure CLI command examples for managing IP firewall rules, similar to the PowerShell section.
  • Include Bash/Linux shell examples for deploying ARM templates (e.g., using 'az deployment group create').
  • Ensure that deployment links reference both PowerShell and CLI (Bash) guides, or provide a cross-platform deployment section.
  • Balance the order and depth of CLI and PowerShell sections, ensuring Linux users are equally supported.
  • Add notes or examples for common Linux environments, such as using the Azure CLI in Bash or Cloud Shell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-partitions-basic-standard.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation provides both Azure CLI and Azure PowerShell examples, but the PowerShell section is given equal prominence to the CLI section, and PowerShell is a Windows-centric tool. There are no explicit Linux shell (bash) or cross-platform scripting examples beyond Azure CLI. The PowerShell examples use Windows-style syntax (backticks for line continuation), and there is no mention of Linux-specific considerations or alternative tools. The ordering of sections (CLI before PowerShell) is good, but the presence of PowerShell as a primary method and the lack of bash or Linux-native scripting tips indicate a mild Windows bias.
Recommendations:
  • Clearly indicate that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
  • Add bash/zsh shell examples or notes for Linux users, especially for scripting or automation.
  • Mention that PowerShell Core is available cross-platform, or clarify that the examples use Windows PowerShell syntax.
  • Consider adding a note about line continuation differences (backtick vs. backslash) between PowerShell and bash.
  • Ensure that all examples and instructions are tested and presented in a way that is accessible to both Windows and Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-amqp-dotnet.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation is focused exclusively on the legacy WindowsAzure.ServiceBus .NET Framework library, which is inherently Windows-centric. There are no examples or mentions of Linux or cross-platform usage, and all configuration and usage patterns assume a Windows/.NET environment. No Linux-specific instructions, tools, or parity considerations are provided.
Recommendations:
  • Add explicit notes about cross-platform support or limitations, clarifying whether the library can be used on Linux via Mono or .NET Core/5+.
  • Provide examples or guidance for using the newer Azure.Messaging.ServiceBus package in cross-platform (Linux, macOS) environments, especially since it is recommended for new development.
  • Include instructions or references for setting up the development environment and running .NET-based Service Bus clients on Linux.
  • Mention any differences or caveats when using the library on non-Windows platforms, if supported.
  • If the legacy library is Windows-only, state this clearly and direct Linux users to supported alternatives.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-tutorial-topics-subscriptions-portal.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and workflows (e.g., Command Prompt, PowerShell, Visual Studio) exclusively or before any Linux alternatives. There are no explicit instructions or examples for Linux users, such as using Bash, VS Code, or .NET CLI on Linux. The prerequisites and step-by-step instructions assume a Windows environment, and no mention is made of cross-platform considerations.
Recommendations:
  • Add explicit instructions and examples for Linux users, such as using Bash or terminal commands instead of Command Prompt/PowerShell.
  • Mention and provide steps for installing and using .NET SDK and running the sample code on Linux/macOS, including any differences in file paths or command syntax.
  • Include VS Code as an alternative to Visual Studio in the prerequisites, and provide guidance for Linux/macOS users.
  • When referencing command-line actions, use cross-platform .NET CLI commands and clarify that they work on Windows, Linux, and macOS.
  • Add screenshots or terminal output examples from Linux environments where appropriate.
  • Avoid assuming the use of Notepad or other Windows-only tools for copying/storing connection strings; suggest cross-platform alternatives.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/private-link-service.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows First
Summary:
The documentation demonstrates a Windows bias by providing only Azure PowerShell examples for CLI-based integration, omitting equivalent Azure CLI (cross-platform) or Bash scripts. Additionally, the validation section explicitly instructs users to create a Windows VM and does not mention Linux VMs or provide Linux-specific instructions, reinforcing a Windows-first approach.
Recommendations:
  • Add equivalent Azure CLI (az) command examples alongside or instead of PowerShell scripts for creating and managing private endpoints.
  • In the validation section, provide instructions for both Windows and Linux VMs, including how to run nslookup or dig on Linux.
  • When referencing VM creation, link to both Windows and Linux VM quickstart guides.
  • Ensure screenshots and UI instructions are platform-neutral or clarify when steps differ between OSes.
  • Consider including Bash script examples for automation, especially for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-to-event-grid-integration-concept.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Azure CLI and PowerShell examples for creating Event Grid subscriptions, but lists PowerShell after Azure CLI. However, the PowerShell example is given equal prominence, and there are no explicit Linux-specific instructions or examples. The use of PowerShell (a Windows-centric tool, though now cross-platform) may still be seen as Windows-biased, especially since no Bash or Linux-native scripting examples are provided. There are no references to Windows-only tools, but the absence of explicit Linux/Bash examples or notes on cross-platform compatibility could be improved.
Recommendations:
  • Add explicit Bash/Linux shell examples for all command-line instructions, or clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
  • Mention that PowerShell Core is cross-platform, or provide Bash equivalents for PowerShell examples.
  • Where possible, avoid presenting PowerShell as the only scripting alternative to Azure CLI; consider including Python or REST API examples for broader platform parity.
  • Add a note clarifying the cross-platform compatibility of the Azure CLI and PowerShell modules.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-dead-letter.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation provides detailed instructions for both Azure CLI and Azure PowerShell, but the PowerShell section is prominent and uses Windows-centric tooling. PowerShell is a Windows-first tool, and its inclusion as a primary automation method can be seen as a Windows bias, especially since there are no equivalent Bash or Linux shell script examples. The CLI examples are cross-platform, but the ordering (CLI before PowerShell) is good; however, the presence of PowerShell without any Linux shell scripting alternatives (e.g., Bash) or explicit mention of cross-platform PowerShell Core may disadvantage Linux users. There are no explicit Linux-only tools or patterns, and the documentation does not mention or show Linux-specific considerations.
Recommendations:
  • Add Bash shell script examples alongside PowerShell, especially for automation scenarios.
  • Explicitly mention that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • If including PowerShell, clarify whether the examples work with PowerShell Core on Linux/macOS or are Windows-only.
  • Consider providing parity in scripting examples: for every PowerShell example, provide a Bash or shell equivalent.
  • Highlight any OS-specific considerations (if any) for using these tools on Linux.
  • If possible, add a section or note for Linux users, e.g., how to install and use Azure CLI/PowerShell on Linux.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-messaging-sql-rule-action.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation page lists both Azure CLI and PowerShell commands for managing Service Bus rules, but the PowerShell cmdlet (New-AzServiceBusRule) is mentioned in the 'Next steps' section after the CLI, and there are no explicit OS-specific examples. However, the only SDKs linked are .NET, Java, and JavaScript, with .NET (a Microsoft/Windows-centric technology) listed first. There are no Linux-specific tools or shell examples, and the documentation references .NET types and methods (e.g., System.Char.IsLetter, System.Guid.NewGuid()), which may be more familiar to Windows/.NET developers.
Recommendations:
  • Add explicit Linux shell (bash) examples alongside Azure CLI commands, demonstrating parity with PowerShell.
  • Include references to cross-platform SDKs (such as Python) and provide usage examples.
  • When referencing types or methods, provide language-agnostic explanations or equivalents in other languages (e.g., Python, Java).
  • Ensure that examples and tool references are balanced between Windows and Linux environments.
  • Consider listing cross-platform tools and SDKs before Windows-specific ones to avoid perceived prioritization.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/transport-layer-security-enforce-minimum-version.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation page provides only Azure PowerShell examples for deploying and managing a Service Bus namespace, with no equivalent Azure CLI (cross-platform) or Bash examples. The instructions and code blocks are PowerShell-specific, and the workflow assumes familiarity with PowerShell and Windows-centric patterns (e.g., Write-Host, Read-Host). While there is a brief mention of Azure CLI as an alternative, no CLI or Linux-native examples are provided, and PowerShell is presented as the default and primary method.
Recommendations:
  • Add equivalent Azure CLI examples for all PowerShell scripts, using Bash syntax where appropriate.
  • Present both PowerShell and CLI/Bash examples side-by-side, or allow users to toggle between them.
  • Avoid assuming the use of Windows tools or PowerShell-specific commands in instructions and explanations.
  • Explicitly mention that Azure Cloud Shell supports both PowerShell and Bash, and provide guidance for both environments.
  • Ensure that Linux/macOS users can follow the quickstart without needing to adapt PowerShell scripts themselves.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-auth-rule.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools
Summary:
The documentation page demonstrates a moderate Windows bias. PowerShell is presented as the first and primary example for deploying the ARM template, with the Azure CLI example following. The 'Next steps' section prioritizes PowerShell-based management and does not mention Linux-specific tools or workflows. There is no explicit mention of Linux or cross-platform considerations in the deployment or management sections, and the use of PowerShell and Service Bus Explorer (a Windows desktop tool) further reinforces a Windows-centric approach.
Recommendations:
  • Present Azure CLI deployment commands before or alongside PowerShell, emphasizing its cross-platform compatibility.
  • Include explicit references to Linux and macOS compatibility, especially in deployment and management sections.
  • Add examples for deploying ARM templates using Bash scripts or from Linux/macOS terminals.
  • Highlight cross-platform tools for managing Service Bus resources, such as Azure CLI, REST API, or SDKs, rather than focusing on Windows-only tools like PowerShell and Service Bus Explorer.
  • In the 'Next steps' section, provide links to CLI-based management guides and mention Service Bus management via the Azure Portal, which is OS-agnostic.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-geo-replication.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation does not show overt Windows or PowerShell bias in terms of explicit command-line examples, but it does exhibit 'windows_first' and 'missing_linux_example' bias in a few subtle ways. For example, the only command-line example for checking the current primary region uses the 'ping' command, which is available on both Windows and Linux, but the documentation does not clarify this cross-platform applicability or provide Linux-specific context. Additionally, all screenshots and portal instructions are platform-agnostic, but the sample code references only .NET (commonly associated with Windows), and there are no explicit Linux or cross-platform SDK/sample references. There are no PowerShell-specific or Windows tool-specific instructions, but the lack of explicit Linux parity in examples and sample references is a form of bias.
Recommendations:
  • When providing command-line instructions (e.g., 'ping'), clarify that the command works on both Windows and Linux, or provide equivalent Linux shell commands if differences exist.
  • Include sample references or code snippets in languages and SDKs commonly used on Linux (e.g., Python, Java, Node.js), not just .NET.
  • If referencing the Azure CLI, note that it is cross-platform and provide any necessary shell syntax for both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh).
  • Add explicit statements or sections confirming that all features and management tasks are supported equally on Linux and Windows, especially for automation and scripting.
  • Where screenshots are used, consider including at least one from a Linux environment or clarify that the portal experience is identical across platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-queue-bicep.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Azure CLI and PowerShell examples for deployment, validation, and cleanup, but consistently lists PowerShell as the second option and highlights PowerShell-specific management resources in the 'Next steps' section. There is a slight Windows bias in the prominence of PowerShell, and the 'Manage Service Bus with PowerShell' article is specifically called out, while equivalent Linux/bash management resources are not.
Recommendations:
  • Ensure parity by including links to Linux/bash management guides in the 'Next steps' section, such as 'Manage Service Bus with Azure CLI' or scripting with bash.
  • When listing tools or examples, alternate the order (e.g., sometimes show CLI first, sometimes PowerShell) or clarify that both are cross-platform, with CLI being natively available on Linux/macOS.
  • Add explicit notes that Azure CLI commands work on Windows, Linux, and macOS, and consider including bash script examples where appropriate.
  • If mentioning PowerShell, also mention that PowerShell Core is cross-platform, or provide bash alternatives for scripting scenarios.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-dotnet-get-started-with-queues.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation demonstrates a strong bias toward Windows development environments. All instructions for creating and running the .NET applications are centered around Visual Studio, a Windows-centric IDE, with no mention of cross-platform alternatives like Visual Studio Code or JetBrains Rider. Package installation is shown exclusively using the NuGet Package Manager Console (PowerShell), with no examples for .NET CLI (dotnet) commands, which are platform-agnostic. There are no instructions or screenshots for Linux or macOS users, and the workflow assumes the user is operating within a Windows GUI environment.
Recommendations:
  • Add instructions for using Visual Studio Code and/or JetBrains Rider, including how to create and run .NET console applications on Linux and macOS.
  • Provide .NET CLI (dotnet add package ...) commands as an alternative to the NuGet Package Manager Console for installing packages.
  • Include notes or screenshots for Linux/macOS environments where relevant, especially for authentication (e.g., DefaultAzureCredential) and running the sample code.
  • Clarify that Visual Studio is not required, and that the sample can be built and run on any platform supported by .NET 6+.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., port/firewall settings, credential management).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/transport-layer-security-configure-minimum-version.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation demonstrates a moderate Windows bias. While Azure CLI examples (cross-platform) are provided, there are several areas where Windows-specific tools and patterns are prioritized or Linux alternatives are missing. For example, the section on checking the minimum TLS version uses ARMClient.exe (a Windows executable) and PowerShell commands, with no mention of Linux-compatible alternatives. PowerShell examples are given equal prominence to Azure CLI, and the documentation refers to tools and workflows (like ARMClient.exe) that are not natively available on Linux or macOS. There are no Bash/cURL or Linux-native instructions for querying the ARM API or obtaining tokens.
Recommendations:
  • Provide Linux/macOS-compatible alternatives for ARMClient.exe, such as using Azure CLI (az account get-access-token) and curl for querying the ARM API.
  • Include Bash/cURL examples alongside or before PowerShell examples when demonstrating API queries.
  • Clearly indicate which tools are cross-platform and which are Windows-only, and suggest alternatives for non-Windows users.
  • Consider reordering examples to present cross-platform or Linux-native tools first, or at least in parallel with Windows tools.
  • Add explicit notes or links for Linux/macOS users where a tool or workflow is Windows-specific.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-dotnet-how-to-use-topics-subscriptions.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation is heavily oriented toward Windows and Visual Studio workflows. All instructions for creating projects, managing dependencies, and authenticating are based on Visual Studio UI and PowerShell commands. There are no instructions or examples for Linux or cross-platform .NET development (e.g., using VS Code, JetBrains Rider, or the .NET CLI). The NuGet installation steps use PowerShell exclusively, and there is no mention of how to perform equivalent steps on Linux or macOS. The use of Visual Studio sign-in for authentication assumes a Windows environment.
Recommendations:
  • Add parallel instructions for Linux/macOS users, including how to use the .NET CLI (e.g., 'dotnet new console', 'dotnet add package') for project creation and package management.
  • Include examples for installing NuGet packages via the CLI (e.g., 'dotnet add package Azure.Messaging.ServiceBus') instead of only PowerShell.
  • Describe authentication options that work cross-platform, such as using Azure CLI or environment variables for DefaultAzureCredential, not just Visual Studio sign-in.
  • Mention and provide examples for alternative editors like VS Code or JetBrains Rider, and clarify that the code samples work on any OS supported by .NET.
  • Where UI steps are described (e.g., creating projects), provide equivalent CLI commands for non-Windows users.
  • Explicitly state that the tutorial is cross-platform and highlight any OS-specific steps or requirements.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/test-locally-with-service-bus-emulator.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows-first bias by presenting Windows and PowerShell instructions before Linux/macOS equivalents, referencing Windows-specific tools (WSL, PowerShell), and providing more detailed, step-by-step guidance for Windows users. Linux and macOS instructions are less detailed and sometimes only mentioned in passing. Some file path examples and configuration notes are Windows-centric, and Linux-specific nuances (such as file permissions or shell differences) are not addressed.
Recommendations:
  • Present Linux/macOS instructions before or alongside Windows instructions to ensure parity.
  • Provide equally detailed, step-by-step instructions for Linux and macOS users, including terminal commands and navigation.
  • Avoid assuming use of PowerShell or WSL; provide native Linux/macOS shell commands and workflows.
  • Include Linux/macOS file path examples (using forward slashes) alongside Windows examples.
  • Explicitly mention any Linux/macOS prerequisites or dependencies (such as bash, chmod, or Docker Compose installation methods).
  • Ensure that all scripts and configuration steps are validated and described for Linux/macOS environments, not just Windows.
  • Add troubleshooting tips or notes specific to Linux/macOS where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-typescript-how-to-use-queues.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First
Summary:
The documentation is mostly cross-platform in its instructions and code samples, but there is a subtle Windows bias in the references to development tools and supporting documentation. Specifically, the only explicit mention of a platform-specific tool is 'Windows PowerShell' in the context of deploying a Node.js app, and the phrase 'command prompt' is used throughout, which is more commonly associated with Windows than with Linux or macOS. There are no Linux- or macOS-specific instructions or examples, and the documentation does not clarify that all steps work equally well on non-Windows systems.
Recommendations:
  • Replace or supplement references to 'command prompt' with 'terminal' or 'shell', and clarify that the instructions apply to Windows, Linux, and macOS.
  • When referencing supporting documentation (such as deploying Node.js apps), include links or notes for Linux/macOS equivalents alongside Windows/PowerShell instructions.
  • Explicitly state that all commands and code samples are cross-platform, or provide platform-specific notes where minor differences exist.
  • Mention popular Linux/macOS editors (such as Vim, nano, or Sublime Text) alongside Visual Studio Code, or simply refer to 'your preferred code editor'.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/includes/get-namespace-connection-string.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation suggests pasting the copied connection string into Notepad, a Windows-specific tool, and does not mention Linux or cross-platform alternatives. There are no examples or instructions tailored for Linux users.
Recommendations:
  • Replace 'Notepad' with a cross-platform term such as 'a text editor' or mention alternatives like 'Notepad (Windows), TextEdit (macOS), or gedit (Linux)'.
  • Include a note or example for Linux/macOS users, e.g., 'Paste this value into a text editor such as gedit, nano, or TextEdit.'
  • Review the documentation for other Windows-centric language or screenshots and provide Linux/macOS equivalents where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/build-message-driven-apps-nservicebus.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows-first bias by referencing Visual Studio and Solution Explorer as the primary tools for running and configuring the solution, with only a brief mention of Visual Studio Code. There are no Linux-specific instructions or examples for running the solution, managing projects, or configuring the environment. All tooling and workflow examples assume a Windows development environment, and there is no mention of Linux equivalents for tasks such as multi-project startup or debugging.
Recommendations:
  • Provide explicit instructions for running and debugging the solution on Linux, including using .NET CLI commands (e.g., 'dotnet run') for both Sender and Receiver projects.
  • Include examples for configuring multi-project startup in cross-platform editors like Visual Studio Code (e.g., using launch.json and tasks.json).
  • Mention and link to cross-platform tools and workflows, such as JetBrains Rider or the .NET CLI, alongside Visual Studio.
  • Clarify that the solution can be developed and run on Linux and macOS, not just Windows, and provide any necessary steps or caveats.
  • If referencing ServiceInsight or ServicePulse, note their platform compatibility or suggest alternatives if they are Windows-only.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/deprecate-service-bus-management.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation page provides extensive mapping between deprecated and current Azure Service Manager and Resource Manager APIs, with a strong focus on PowerShell cmdlets for both old and new command sets. There are no examples or references to cross-platform CLI tools (such as Azure CLI), Bash, or Linux-native workflows. All scripting and automation examples are PowerShell-based, which is traditionally associated with Windows environments, though it is now cross-platform. There is no mention of Linux, macOS, or alternative scripting environments.
Recommendations:
  • Add equivalent Azure CLI (az) command mappings alongside PowerShell cmdlets, as Azure CLI is widely used on Linux and macOS.
  • Provide Bash or shell script examples for common operations, or at least reference their availability.
  • Explicitly state that PowerShell is available cross-platform, but also highlight and link to documentation for Linux/macOS users.
  • Include a section or table mapping deprecated Service Manager commands to both PowerShell and Azure CLI equivalents.
  • Mention other automation options (e.g., ARM templates, Bicep, SDKs) that are platform-agnostic.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-dead-letter.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation provides both Azure CLI and PowerShell examples, but the PowerShell section is prominent and detailed, reflecting a Windows-centric approach. PowerShell is a Windows-native tool (though now cross-platform), and its inclusion before any Linux shell scripting or bash alternatives may signal a Windows-first bias. There are no bash or Linux shell script examples, and no mention of Linux-specific tools or considerations. The CLI examples are cross-platform, but the documentation does not explicitly highlight Linux usage or parity.
Recommendations:
  • Add bash or Linux shell script examples alongside PowerShell, especially for automation scenarios.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample terminal prompts (e.g., $ for bash, PS> for PowerShell) to clarify context.
  • If PowerShell is included, consider also including bash equivalents for common tasks, or at least reference that PowerShell is available cross-platform.
  • In sections where PowerShell is used, add a note or link to guidance for using Azure CLI or bash on Linux.
  • Ensure that any references to tools or scripting environments are balanced between Windows and Linux, or clarify their cross-platform support.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/authenticate-application.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First Dotnet Heavy
Summary:
The documentation page demonstrates bias towards Windows environments by providing only .NET (C#) code samples, referencing Windows-centric libraries (Azure.Messaging.ServiceBus, Azure.Identity), and omitting equivalent Linux or cross-platform code examples (such as Python, Java, or Node.js). The registration and authentication steps are described using the Azure portal UI, which is platform-agnostic, but the only code sample is for .NET, which is most commonly associated with Windows. Additionally, in the 'Next steps' section, PowerShell is mentioned before Azure CLI, which is more commonly used on Linux/macOS.
Recommendations:
  • Add code samples for other popular cross-platform languages such as Python (using azure-identity and azure-servicebus), Java, and Node.js to demonstrate authentication from Linux or macOS environments.
  • Include explicit instructions or examples for using Azure CLI (which is cross-platform) to perform authentication and role assignments, and consider listing Azure CLI before PowerShell in the 'Next steps' section.
  • Mention that the .NET libraries are cross-platform, but also provide links or references to SDKs and samples for other languages.
  • If possible, include a table or section comparing authentication approaches across different operating systems and programming languages.
  • Ensure that screenshots and UI steps are clearly marked as platform-agnostic, and provide command-line alternatives for users who prefer not to use the Azure portal.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-duplicate-detection.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation provides both Azure CLI and Azure PowerShell examples for enabling duplicate message detection in Azure Service Bus. However, the PowerShell section is prominent and detailed, and PowerShell is a Windows-centric tool. There are no explicit Linux shell (bash) or cross-platform scripting examples outside of Azure CLI. The ordering places Azure CLI before PowerShell, but the PowerShell section is equally detailed and assumes familiarity with Windows scripting patterns. No Linux-specific tools or shell scripts are mentioned, and there is no explicit mention of running PowerShell Core cross-platform.
Recommendations:
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows.
  • Add bash shell examples alongside Azure CLI commands to demonstrate usage in a typical Linux environment.
  • If including PowerShell, specify that PowerShell Core is available cross-platform, or clarify when examples are Windows-specific.
  • Avoid assuming PowerShell as the default scripting tool; present CLI/bash examples first or in parallel.
  • Consider including notes or links for Linux users on installing and using the Azure CLI and PowerShell Core.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-partitions-premium.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation presents both Azure CLI and Azure PowerShell examples for enabling partitioning, but the PowerShell section is given equal prominence to the CLI, and there is no explicit mention of Linux or Bash scripting. The PowerShell example is not marked as Windows-specific, and there is no clarification that PowerShell is primarily a Windows tool (though it is now cross-platform, many users still associate it with Windows). No Linux-specific tools or shell examples (e.g., Bash, shell scripts) are provided, and the order of sections (CLI before PowerShell) is good, but the PowerShell example could be perceived as Windows-centric.
Recommendations:
  • Explicitly note that Azure CLI commands work cross-platform (Windows, Linux, macOS) and are the recommended approach for Linux users.
  • Label the PowerShell example as optional or as 'for Windows/PowerShell users', and clarify that PowerShell Core is available cross-platform if relevant.
  • Consider adding a Bash shell script example or a note for Linux users to reinforce parity.
  • Where possible, provide links to platform-specific setup guides (e.g., installing Azure CLI on Linux).
  • Review the language to ensure that Windows tools are not implied as the default or primary method.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-auto-forward.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation provides detailed instructions for enabling auto forwarding in Azure Service Bus using the Azure portal, Azure CLI, Azure PowerShell, ARM templates, and several programming languages. However, there is a notable Windows bias: PowerShell is given a dedicated section with full examples, and Windows-centric tools (PowerShell) are presented before cross-platform programming language SDKs. There is no mention of Bash scripting or Linux-native automation tools, and the PowerShell section appears before the programming language SDKs, which are cross-platform. The Azure CLI section is present and uses Unix-style line continuations, but there is no explicit mention of Linux or macOS environments, nor are there Bash or shell script examples.
Recommendations:
  • Add explicit Bash or shell script examples for common automation scenarios, especially for updating or creating Service Bus resources.
  • Clarify in the Azure CLI section that the commands are cross-platform and provide both Windows (using `^` for line continuation) and Linux/macOS (using `\`) variants if necessary.
  • Consider adding a section or note on using Azure CLI and SDKs on Linux/macOS, including any prerequisites or differences.
  • Reorder the sections so that cross-platform tools (Azure CLI, SDKs) are presented before Windows-specific tools (PowerShell), or at least clarify the cross-platform nature of each tool.
  • If possible, mention or link to Linux-native automation options (such as Bash scripts or Ansible modules) for managing Azure Service Bus.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/entity-suspend.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation provides a detailed PowerShell example for changing the status of Service Bus queues, but does not provide equivalent command-line examples for Linux users (e.g., Azure CLI, Bash). The only code sample is in PowerShell, which is a Windows-centric tool, and there is no mention or demonstration of how to perform the same operation on Linux or macOS platforms. This creates a bias towards Windows users and leaves Linux users without clear guidance.
Recommendations:
  • Add equivalent Azure CLI examples for all PowerShell commands shown, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that the operations can be performed using Azure CLI, and provide sample commands.
  • Where possible, provide Bash script examples alongside PowerShell to ensure parity.
  • Structure sections so that cross-platform tools (like Azure CLI) are presented before or alongside Windows-specific tools (like PowerShell).
  • Include a note clarifying platform compatibility for each tool and example.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/configure-customer-managed-key.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a significant Windows/Powershell bias. All imperative command-line examples for deploying templates, managing identities, and setting access policies use Azure PowerShell cmdlets, with no Bash, Linux shell, or cross-platform Azure CLI equivalents provided for these critical steps. While some resource creation steps reference Azure CLI, all step-by-step automation and scripting guidance defaults to PowerShell. This may hinder Linux or macOS users, who are more likely to use Bash and Azure CLI. Additionally, PowerShell is mentioned before CLI in several places, and no Linux-specific instructions or screenshots are present.
Recommendations:
  • Provide Azure CLI equivalents for all PowerShell commands, especially for template deployments, identity management, and key vault access policy configuration.
  • Include Bash shell command examples alongside PowerShell, or use CLI as the primary example for cross-platform parity.
  • When referencing both PowerShell and CLI, present CLI first or side-by-side to avoid the impression of Windows-first bias.
  • Add a note or section clarifying that all steps can be performed on Linux/macOS using Azure CLI, and link to relevant CLI documentation.
  • Where screenshots are used, ensure they are not Windows-specific or supplement with cross-platform visuals.
  • Audit for any references to Windows-only tools or patterns and replace with cross-platform alternatives where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/enable-partitions-basic-standard.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation provides both Azure CLI and Azure PowerShell examples, but the PowerShell section is given equal prominence to the CLI, despite PowerShell being primarily associated with Windows environments. There is no explicit mention of Linux shell (bash) or cross-platform scripting alternatives in the PowerShell section, and no guidance for Linux users on how to adapt PowerShell commands. The CLI examples are cross-platform, but the presence and prominence of PowerShell may suggest a Windows-centric approach. Additionally, the PowerShell section appears before the ARM template section, which is platform-neutral.
Recommendations:
  • Clearly indicate that Azure CLI commands work on all platforms (Windows, Linux, macOS), and consider placing the CLI section before PowerShell to emphasize cross-platform support.
  • In the PowerShell section, note that PowerShell Core is available cross-platform, but that most Linux users will prefer CLI or bash.
  • Add explicit bash shell examples or notes for Linux users where relevant, especially for scripting scenarios.
  • Review the ordering of sections to ensure that cross-platform tools (CLI, ARM templates) are not de-emphasized compared to Windows-centric tools.
  • Consider adding a table or quick-reference that maps each method (Portal, CLI, PowerShell, ARM) to its platform compatibility.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/includes/service-bus-event-grid-prerequisites.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE), Solution Explorer, and .sln files, with no mention of Linux-compatible tools or workflows. There are no instructions or examples for Linux users, such as using VS Code, .NET CLI, or alternative editors, nor are there any Linux-specific setup or run instructions.
Recommendations:
  • Add instructions for Linux users, such as how to open and run the sample using the .NET CLI (e.g., 'dotnet build', 'dotnet run') and editors like VS Code.
  • Mention cross-platform tools and workflows alongside Windows-specific ones, ensuring parity in steps and screenshots.
  • Provide alternative instructions for opening and editing the project without Visual Studio, such as using VS Code or JetBrains Rider.
  • Include notes or sections that explicitly address Linux and macOS users, clarifying any differences in setup or execution.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/includes/service-bus-create-topic-subscription-portal.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/message-sessions.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation page demonstrates a Windows bias by listing 'Azure portal, PowerShell, CLI, Resource Manager template, .NET, Java, Python, and JavaScript' as ways to enable message sessions, with PowerShell (a Windows-centric tool) mentioned before the cross-platform Azure CLI. There are no explicit Linux-specific instructions or examples, and the ordering of tools and languages tends to prioritize Windows-first technologies. The absence of Linux shell (bash) or cross-platform command-line examples further highlights this bias.
Recommendations:
  • Reorder the list of tools to mention cross-platform options (such as Azure CLI) before Windows-specific ones (like PowerShell).
  • Provide explicit Linux/bash command examples alongside or before PowerShell examples.
  • Clarify which tools and instructions are cross-platform and which are Windows-only.
  • Include references to Linux package managers or shell environments where relevant.
  • Ensure that all code samples and setup instructions are validated on both Windows and Linux platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/message-transfers-locks-settlement.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation page provides only C# code examples and references .NET-specific APIs, which are most commonly associated with Windows development. There are no Linux-specific or cross-platform command-line examples, nor are there any references to Linux tools or patterns. While the text mentions support for Java, JavaScript, Python, and Go, all code samples and API references are for .NET/C#, and there is no parity in examples for other platforms or languages. This creates a subtle Windows bias by centering the documentation around Windows-centric technologies and omitting Linux/Unix or cross-platform usage patterns.
Recommendations:
  • Provide equivalent code samples in at least one other major language (e.g., Python, Java, or JavaScript) that is commonly used on Linux.
  • Include cross-platform command-line examples (e.g., using Azure CLI or REST API) where appropriate.
  • Reference SDKs and APIs for multiple languages/platforms, not just .NET/C#.
  • Explicitly mention and, where possible, demonstrate usage on Linux or macOS environments.
  • Consider adding a section or callout for Linux users, highlighting any differences or best practices.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/move-across-regions.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples (such as Azure CLI, PowerShell, or Bash). However, the workflow and screenshots are heavily oriented toward the graphical interface, which is more familiar to Windows users. There is no mention of Linux command-line tools or automation approaches, and no parity for users who prefer or require CLI-based workflows, which are common in Linux environments.
Recommendations:
  • Add Azure CLI examples for exporting, editing, and deploying Resource Manager templates, as Azure CLI is cross-platform and widely used on Linux.
  • Include instructions for performing the move using command-line tools (e.g., az group export, az deployment group create) alongside the portal-based steps.
  • Mention and provide links to documentation for automating these tasks via scripts (Bash, PowerShell) to support both Windows and Linux users.
  • Ensure that screenshots and instructions do not assume a Windows environment (e.g., file paths, UI conventions) and clarify that the process is platform-agnostic where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/jms-developer-guide.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-dead-letter-queues.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by primarily referencing .NET APIs and GUI tools (Service Bus Explorer) that are most accessible on Windows. There is a lack of Linux- or cross-platform-specific examples, and no mention of command-line or scripting approaches (e.g., Bash, Python, or PowerShell) for Linux users. The only CLI example is Azure CLI, which is cross-platform, but the overall focus is on Windows-centric tools and patterns.
Recommendations:
  • Include code examples for moving messages to the DLQ and resubmitting them using cross-platform SDKs (e.g., Python, Java, Node.js) in addition to .NET.
  • Highlight command-line tools and scripting approaches (e.g., Bash scripts using Azure CLI or REST API) for Linux users.
  • Mention and provide examples for open-source or cross-platform tools for managing Service Bus DLQs, if available.
  • Ensure that GUI tools like Service Bus Explorer are clearly marked as Windows-only (if applicable), and suggest alternatives for Linux/macOS users.
  • Balance .NET-specific guidance with equivalent instructions for other languages and platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/private-link-service.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows First
Summary:
The documentation page demonstrates a Windows bias by providing only Azure PowerShell CLI examples for automation, omitting equivalent Azure CLI (cross-platform) or Bash scripts. Additionally, the validation steps explicitly instruct users to create and use a Windows virtual machine, with no mention of Linux alternatives or parity. This prioritizes Windows tools and environments, leaving Linux users without direct guidance.
Recommendations:
  • Provide equivalent Azure CLI (az) and/or Bash examples alongside the PowerShell automation steps, ensuring Linux and macOS users have clear instructions.
  • In the validation section, offer instructions for creating and using a Linux virtual machine, including relevant command-line examples (e.g., using dig or nslookup on Linux).
  • Where possible, use neutral language and cross-platform tools (e.g., Azure CLI, REST API) as the primary automation example, or present both Windows and Linux options in parallel.
  • Explicitly state that the steps can be performed from any supported OS, and link to both Windows and Linux VM creation guides.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-go-how-to-use-queues.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation provides both Bash and PowerShell instructions for setting environment variables, but Bash is presented first. There is a minor Windows bias in the mention of Visual Studio/MSDN subscriber benefits for Azure subscriptions, which are Windows-centric. However, the overall documentation is largely cross-platform, with the Go code and Azure CLI usage being platform-agnostic. No exclusive use of Windows tools or missing Linux examples were found.
Recommendations:
  • Continue to provide both Bash and PowerShell instructions for environment variables, but consider explicitly stating that Bash commands work on Linux/macOS and PowerShell on Windows.
  • When mentioning Azure subscription options, add links or notes for non-Windows users (e.g., 'You can also sign up for a free account if you are not a Visual Studio/MSDN subscriber').
  • Ensure that any references to tools or workflows (such as Azure CLI) clarify their cross-platform availability.
  • If referencing file paths or shell commands elsewhere, provide both Windows and Linux/macOS equivalents where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-dotnet-multi-tier-app-using-service-bus-queues.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation is heavily oriented towards Windows development environments, specifically Visual Studio and Azure Cloud Service roles, with all instructions, screenshots, and tooling references assuming a Windows OS. There are no Linux or cross-platform development instructions, nor are alternative tools (such as VS Code, CLI, or Docker) mentioned. The use of the Azure Compute Emulator and the requirement to run Visual Studio as administrator further reinforce the Windows-only focus.
Recommendations:
  • Add parallel instructions and examples for developing and running the application on Linux and macOS, using cross-platform tools such as VS Code, .NET CLI, and Docker.
  • Include steps for setting up the development environment on Linux (e.g., installing the .NET SDK, using the Azure CLI for resource management, and configuring environment variables).
  • Replace or supplement Visual Studio-specific steps and screenshots with instructions for using VS Code or JetBrains Rider, and provide CLI commands for project creation, dependency management, and running the application.
  • Document how to run and debug the application locally without the Azure Compute Emulator, which is Windows-only, possibly using Docker Compose or Azure Functions Core Tools.
  • Ensure that all code snippets and configuration steps are OS-agnostic, and explicitly call out any platform-specific requirements or alternatives.
  • Provide guidance on how to view logs and trace output on Linux, replacing references to Windows notification area and emulator UI with cross-platform solutions.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-amqp-dotnet.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily oriented toward Windows and .NET, with all examples and configuration instructions focused on the WindowsAzure.ServiceBus .NET Framework library. There are no Linux-specific instructions, cross-platform considerations, or examples for non-Windows environments. The documentation assumes use of Windows tools (e.g., Azure portal) and .NET APIs, with no mention of Linux command-line tools, PowerShell alternatives, or cross-platform SDKs.
Recommendations:
  • Add explicit guidance or examples for using the Service Bus library from Linux environments, such as with .NET Core/.NET 5+ on Linux.
  • Mention and provide examples for cross-platform SDKs (e.g., Azure.Messaging.ServiceBus) that work on Linux, and clarify platform compatibility.
  • Include instructions for obtaining connection strings and managing Service Bus namespaces using cross-platform tools like Azure CLI or Azure Cloud Shell, not just the Azure portal.
  • Where possible, provide code/configuration examples that are OS-agnostic or explicitly show both Windows and Linux usage.
  • Clarify in the introduction that while the legacy library is Windows/.NET Framework-specific, modern alternatives are available for Linux and cross-platform development.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-ip-filtering.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation provides explicit instructions and command references for Azure PowerShell (a Windows-centric tool) but does not provide equivalent, detailed examples for Azure CLI (which is cross-platform and preferred on Linux). The PowerShell section lists specific cmdlets, while the Azure CLI section only mentions the command group without concrete examples. There are no Linux- or bash-specific instructions or screenshots, and the only deployment link for ARM templates points to a PowerShell-based deployment guide. This creates a Windows-first impression and lacks Linux parity.
Recommendations:
  • Add concrete Azure CLI command examples for managing IP firewall rules, similar to the PowerShell cmdlet examples.
  • Provide bash shell examples for deploying ARM templates, or link to cross-platform deployment instructions (e.g., az deployment group create).
  • Ensure that CLI examples appear before or alongside PowerShell examples to avoid a Windows-first ordering.
  • Include notes or sections highlighting that all steps can be performed on Linux/macOS using Azure CLI.
  • Where screenshots or UI references are given, clarify that the Azure portal is OS-agnostic.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-tutorial-topics-subscriptions-portal.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and workflows (Command Prompt, PowerShell) as the default environment for running commands. There are no explicit instructions or examples for Linux or macOS users, such as using a Bash shell or Linux-specific command-line conventions. The prerequisites focus on Visual Studio (a Windows-centric IDE), and all command-line instructions assume a Windows environment. No mention is made of cross-platform .NET development tools or editors, nor are alternative shell environments or package managers referenced.
Recommendations:
  • Add explicit instructions and examples for Linux/macOS users, such as using Bash or zsh shells.
  • Mention and provide examples using cross-platform .NET tools (e.g., .NET CLI on Linux/macOS) and editors like VS Code.
  • Replace 'Command Prompt or PowerShell' with 'terminal' or 'command line', and clarify that the steps work on all major platforms.
  • Include Linux/macOS-specific notes for file paths, navigation, and command syntax where appropriate.
  • List prerequisites for Linux/macOS (e.g., .NET SDK installation instructions for those platforms).
  • Reference cross-platform Service Bus management tools (e.g., Azure CLI) and show parity in usage.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-federation-overview.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation provides a command-line example using the Azure CLI, which is cross-platform, but does not include any OS-specific shell context or examples. However, there is a subtle 'windows_first' bias in that no explicit Linux or Bash shell context is shown, and the only CLI example is presented without clarifying its cross-platform applicability. There are no PowerShell-specific commands, but the absence of Linux- or macOS-specific notes or examples (such as Bash scripting, environment variable usage, or file path conventions) may leave Linux users uncertain about parity. No Windows-only tools are mentioned, but the documentation does not actively demonstrate Linux parity.
Recommendations:
  • Explicitly state that the Azure CLI example works on Windows, Linux, and macOS, and provide sample invocations in both Bash and PowerShell if relevant.
  • Where command-line examples are given, show both Bash and PowerShell syntax if there are differences, or clarify that the syntax is identical.
  • Add notes or callouts for Linux/macOS users regarding any environment-specific considerations (e.g., line continuations, authentication methods, file paths).
  • If referencing tools or scripts, ensure both Windows and Linux equivalents are mentioned or provide guidance for both environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-filter-examples.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation page provides examples for setting Azure Service Bus subscription filters. While it covers the Azure portal, Azure CLI, and Azure PowerShell, the only detailed code samples are in .NET/C#, with no Linux-specific shell (bash) or cross-platform language examples. PowerShell is mentioned as a primary automation tool alongside CLI, and .NET is the only language with inline code samples, which may implicitly favor Windows users. There are no explicit Linux or bash scripting examples for managing filters, and the ordering of sections (CLI, then PowerShell) is neutral, but the lack of bash or Python code samples is a gap.
Recommendations:
  • Add bash shell examples using Azure CLI for common filter management tasks, including end-to-end scripts for creating topics, subscriptions, and rules.
  • Include code samples in at least one cross-platform language such as Python or JavaScript, demonstrating filter creation and message sending/receiving.
  • Provide explicit notes or callouts that all Azure CLI commands work identically on Linux, macOS, and Windows.
  • Balance PowerShell examples with bash equivalents, especially for automation scenarios.
  • Consider reordering or grouping CLI and PowerShell sections under a broader 'Command-line tools' heading to emphasize parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-auth-rule.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation page provides both PowerShell and Azure CLI commands for deploying the template, but the PowerShell example is presented first and is visually emphasized. Additionally, the 'Next steps' section highlights PowerShell-based management before other cross-platform tools, and there is no explicit mention of Linux-specific considerations or parity in tooling. The Azure CLI example uses the legacy 'azure' CLI rather than the modern 'az' CLI, which is more cross-platform and recommended.
Recommendations:
  • Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Update the Azure CLI example to use the modern 'az' CLI instead of the deprecated 'azure' CLI.
  • Include explicit statements that all commands work on Linux, macOS, and Windows, and provide any necessary Linux-specific notes (e.g., shell syntax differences, installation instructions).
  • In the 'Next steps' section, add links to Azure CLI and/or REST API management guides before or alongside PowerShell resources.
  • Consider including a Bash shell example for template deployment to further demonstrate Linux parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-end-to-end-tracing.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy
Summary:
The documentation page demonstrates a strong bias toward Windows and .NET environments. All code samples, configuration guidance, and tracing instrumentation are exclusively provided for .NET (C#), ASP.NET, and Microsoft Application Insights, with no mention of equivalent approaches for Linux, non-.NET languages, or cross-platform tools. There are no examples or references for Linux environments, open-source tracing tools (other than a brief mention of OpenTelemetry in .NET), or how to achieve similar diagnostics in non-Windows ecosystems.
Recommendations:
  • Add equivalent code samples and configuration instructions for Linux environments, such as using Python, Java, or Node.js Service Bus SDKs.
  • Include examples of integrating with open-source tracing and monitoring tools commonly used on Linux, such as Jaeger, Zipkin, or Prometheus, alongside Application Insights.
  • Provide guidance for setting up distributed tracing and diagnostics in cross-platform scenarios, including Docker and Kubernetes deployments.
  • Mention and demonstrate the use of OpenTelemetry in non-.NET languages, and show how to propagate trace context across heterogeneous services.
  • Ensure that references to SDKs, libraries, and tools are not limited to Windows/.NET, and present Linux/cross-platform options either first or in parallel.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-geo-dr.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First Powershell Heavy
Summary:
The documentation page exhibits a Windows bias by primarily referencing the Azure Portal (a GUI often used on Windows), mentioning PowerShell and CLI as alternatives but not providing explicit Linux/bash examples or parity. The only code samples referenced are .NET-based (a traditionally Windows-centric stack, though now cross-platform), and there is no mention of Linux-specific tools, shell commands, or patterns. PowerShell is mentioned before CLI, and there are no bash or Linux-native command examples. The documentation assumes a Windows/Portal-centric workflow and does not address Linux users directly.
Recommendations:
  • Provide explicit Azure CLI (bash) command examples alongside or before PowerShell examples for all setup and failover steps.
  • Include Linux shell (bash) usage instructions for common tasks such as pairing, failover, and monitoring.
  • Reference cross-platform SDKs and samples (e.g., Python, Java) in addition to .NET, and link to relevant repositories.
  • Clarify that all management operations can be performed from Linux environments and provide step-by-step Linux terminal instructions.
  • Ensure that any mention of PowerShell is balanced with equivalent Azure CLI/bash examples, and avoid listing PowerShell first unless it is the only supported method.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-managed-service-identity.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a mild Windows bias by referencing Windows-specific resources before Linux equivalents and omitting explicit Linux or cross-platform examples. For example, the link for configuring managed identities on a VM points only to a Windows VM guide, and there are no Linux-specific or cross-platform instructions for enabling managed identities. Additionally, the code samples and tool references (such as Azure CLI) are platform-neutral, but the absence of Linux-focused guidance or parity in example coverage is notable.
Recommendations:
  • Include links or references to both Windows and Linux VM managed identity configuration guides, or use a cross-platform guide where available.
  • When listing platform-specific instructions, present Linux and Windows options together or in parallel, rather than defaulting to Windows.
  • Add explicit Linux (or cross-platform) examples for enabling managed identity and for any command-line steps.
  • Ensure that all code and CLI examples are clearly marked as cross-platform, and provide any necessary notes for Linux users (e.g., shell syntax differences, environment variable usage).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-geo-replication.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools Windows First
Summary:
The documentation page predominantly references tools and patterns common in Windows environments, such as the use of 'ping' (with Windows syntax) and screenshots from the Azure Portal (which is platform-agnostic but often associated with Windows workflows). There are no explicit PowerShell or Windows-only command-line examples, but there is a notable absence of Linux-specific or cross-platform command-line examples (e.g., Bash, curl, or az CLI with Linux shell syntax). The only command-line example provided is Azure CLI, which is cross-platform, but there are no explicit Linux shell or scripting examples. Additionally, the 'ping' example is presented without clarifying its usage on Linux, and the sample code references only .NET (commonly associated with Windows), with no mention of other languages or platforms.
Recommendations:
  • Provide Linux shell (bash) equivalents for command-line instructions, such as 'ping' (e.g., 'ping your-namespace-fully-qualified-name' works on both, but clarify any OS-specific differences).
  • Include examples using cross-platform tools (e.g., curl, wget) where relevant.
  • Add sample code references for other languages/platforms (e.g., Python, Java, Node.js) to ensure parity with .NET.
  • Explicitly state that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
  • Where screenshots or UI instructions are given, clarify that the Azure Portal is accessible from any OS.
  • If referencing tools or commands that behave differently on Windows vs. Linux (such as 'ping'), provide notes or examples for both.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-messaging-sql-filter.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation page references both Azure CLI and PowerShell (New-AzServiceBusRule) for managing Service Bus rules, but it lists the PowerShell cmdlet after the Azure CLI command. However, the examples and references to .NET and C# semantics (such as operator binding and type conversion) are prominent, and the only explicit SDK function examples are for .NET, Java, and JavaScript. There are no Linux-specific tools or shell examples, and the PowerShell module is referenced directly, which is traditionally associated with Windows environments. The documentation does not provide Linux shell (bash) or cross-platform scripting examples, and the focus on .NET/C# semantics may be less familiar to Linux-first users.
Recommendations:
  • Add explicit bash/shell examples for using az CLI to create and manage Service Bus rules, demonstrating parity with PowerShell.
  • Clarify that Azure CLI is fully cross-platform and provide usage examples in a Linux shell context.
  • Include references to Python SDK usage (which is popular on Linux) alongside .NET, Java, and JavaScript.
  • When discussing operator semantics, mention language-agnostic behavior or provide equivalent semantics for other languages (e.g., Python) to avoid .NET/C#-centric explanations.
  • If referencing PowerShell, clarify that PowerShell Core is cross-platform, or provide equivalent bash scripts for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-messaging-sql-rule-action.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation page references both Azure CLI and PowerShell (New-AzServiceBusRule) tools for managing Service Bus rules, but does not provide Linux-specific examples or mention Linux tools explicitly. PowerShell, a Windows-centric tool, is mentioned in the 'Next steps' section, and .NET is listed first among SDKs, which may suggest a Windows-first perspective. No Linux shell or scripting examples are provided, and there is no mention of Linux-specific considerations.
Recommendations:
  • Provide explicit Bash or Linux shell examples for managing Service Bus rules using Azure CLI.
  • List cross-platform tools (such as Azure CLI) before Windows-specific tools (like PowerShell) in the 'Next steps' section.
  • Include a note clarifying that Azure CLI is fully supported on Linux, macOS, and Windows.
  • Add links or references to Linux/macOS installation and usage guides for Azure CLI.
  • If mentioning PowerShell, clarify that PowerShell Core is cross-platform, or provide equivalent Bash examples.
  • Ensure SDK examples are balanced across languages/platforms (e.g., Python, Java, JavaScript) and not just .NET.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-nodejs-how-to-use-queues.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools
Summary:
The documentation demonstrates a mild Windows bias by referencing Windows tools (such as Command Prompt and Windows PowerShell) and presenting Windows-centric patterns (e.g., 'open a Command Prompt window', 'Node.js cloud service using Windows PowerShell') without equivalent or parallel Linux/macOS instructions. There are no explicit Linux or macOS terminal references, and the guidance for running commands and setting up the environment implicitly assumes a Windows environment.
Recommendations:
  • Provide explicit instructions for Linux and macOS users alongside Windows instructions, such as referencing 'Terminal' or 'shell' in addition to 'Command Prompt'.
  • When mentioning Windows PowerShell or Command Prompt, also mention Bash or Terminal for Linux/macOS users.
  • Include links or references to Linux/macOS-specific guides for creating and deploying Node.js applications, not just Windows PowerShell.
  • Use neutral language such as 'open a terminal window' instead of 'open a Command Prompt window' where possible.
  • Ensure that all command-line examples are cross-platform or provide platform-specific notes if differences exist.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-messaging-exceptions-latest.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias in its troubleshooting guidance, particularly in the section on resolving SocketException errors. The only command-line example provided is a PowerShell nslookup command with a Windows-style prompt, and there is no mention of equivalent Linux/macOS commands or shell environments. No Linux or cross-platform troubleshooting steps are offered, and the documentation assumes a Windows-centric context for command-line operations.
Recommendations:
  • Provide equivalent Linux/macOS command-line examples alongside Windows/PowerShell commands (e.g., show nslookup or dig usage in bash/zsh).
  • Use neutral or cross-platform prompts (e.g., $ or #) when showing command-line examples, or show both Windows and Linux prompts.
  • Explicitly mention that troubleshooting steps apply to all platforms and clarify any platform-specific differences.
  • Include guidance for common Linux/macOS tools (such as dig, host, or nslookup) and troubleshooting patterns.
  • Review other sections for implicit Windows assumptions and ensure parity in examples and troubleshooting steps for non-Windows environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples for all deployment, verification, and cleanup steps. There are no equivalent Azure CLI (cross-platform) or Bash examples, and PowerShell is presented as the default and only scripting environment. While a link to Azure CLI deployment is provided, no direct CLI or Linux-native instructions are included in the main flow.
Recommendations:
  • Add Azure CLI examples alongside PowerShell for all steps (deployment, verification, cleanup) to ensure parity for Linux and macOS users.
  • Present both PowerShell and CLI examples in parallel or allow users to select their preferred environment.
  • Explicitly mention that Azure Cloud Shell supports both Bash (with Azure CLI) and PowerShell, and provide guidance for both.
  • Avoid language that assumes PowerShell as the default or only shell; instead, use neutral phrasing and highlight cross-platform options.
  • Consider including Bash script snippets for users who prefer scripting in Bash with Azure CLI.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-messaging-exceptions.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias primarily by providing only Windows/Powershell command-line examples (e.g., nslookup shown as 'PS C:\> nslookup ...'), and by referencing .NET Framework APIs exclusively, which are most commonly associated with Windows. There are no equivalent Linux or cross-platform command-line examples, nor any mention of Linux-specific troubleshooting steps or tools. The documentation assumes a Windows environment for diagnostics and omits Linux or macOS parity.
Recommendations:
  • For every command-line example (such as nslookup), provide both Windows (Powershell/cmd) and Linux/macOS (bash/sh) equivalents side by side.
  • Explicitly mention that the .NET APIs can be used cross-platform, or provide links/examples for other supported SDKs (such as Java, Python, or Node.js) if applicable.
  • Include troubleshooting steps and command examples that are relevant to Linux/macOS environments (e.g., using 'dig' or 'host' for DNS resolution, checking network connectivity with 'curl' or 'telnet').
  • Avoid assuming the use of Windows-specific tools or patterns; where possible, use generic, cross-platform terminology and examples.
  • If the documentation is intentionally .NET/Windows-specific, clarify this scope at the beginning and provide links to equivalent guidance for other platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-java-how-to-use-queues.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a mild Windows bias. It references Windows tools (Eclipse, IntelliJ, Azure CLI for Windows), and installation links default to Windows versions. Instructions for running the app and installing prerequisites are oriented toward Windows users, with no explicit Linux or macOS alternatives. There are no shell or terminal examples for Linux/macOS, and the 'Run the app' section assumes a Windows workflow (e.g., right-clicking in Eclipse).
Recommendations:
  • Provide explicit instructions for Linux and macOS users, including links to platform-specific Azure CLI installation guides.
  • Include terminal/command-line examples using Bash or sh for Linux/macOS, especially for running the Java JAR file.
  • When referencing IDEs like Eclipse or IntelliJ, mention that they are cross-platform and provide any platform-specific notes if needed.
  • Avoid defaulting to Windows-specific UI actions (like right-clicking) without also describing the equivalent for other platforms.
  • In 'Run the app', show both Windows and Linux/macOS command-line instructions for running the JAR and signing in with Azure CLI.
  • Where possible, use neutral language and tool references that apply to all platforms, or clearly indicate when a step is platform-specific.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-nodejs-how-to-use-topics-subscriptions.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools
Summary:
The documentation generally uses cross-platform language (e.g., 'command prompt', 'terminal'), but there are subtle Windows biases. Notably, in the 'NOTE' section, Windows PowerShell is mentioned as a deployment method for Node.js apps, and the phrase 'command prompt' is used throughout, which is more closely associated with Windows. There are no explicit Linux or macOS-specific instructions or examples, and no mention of Linux tools or terminals. The only editor recommended is Visual Studio Code, which is cross-platform, but no Linux-native editors are mentioned.
Recommendations:
  • Replace or supplement 'command prompt' with 'terminal' or 'shell', and clarify that instructions apply to Windows, Linux, and macOS.
  • When referencing deployment guides, include links to Linux/macOS deployment instructions (e.g., deploying Node.js apps using Bash or other Linux-native tools) alongside or before Windows PowerShell.
  • Explicitly state that all commands (npm, node) work on Linux/macOS terminals as well as Windows.
  • Consider mentioning popular Linux editors (e.g., Vim, Nano, Gedit) in addition to Visual Studio Code.
  • Where possible, provide screenshots or notes that reflect Linux/macOS environments, not just Windows/Azure Portal.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-java-how-to-use-topics-subscriptions.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First
Summary:
The documentation demonstrates a mild Windows bias by referencing Windows-specific tools (such as Eclipse and IntelliJ, which are cross-platform but often associated with Windows), and by providing instructions for installing the Azure CLI with a direct link to the Windows installation page. Additionally, the workflow for creating a runnable JAR file is described using Eclipse's Windows-oriented UI conventions (e.g., right-click, Export, Runnable JAR file), and there is no mention of Linux-specific instructions, terminal commands, or alternative editors/environments. The documentation does not provide explicit Linux or macOS command-line examples for running the Java application or installing prerequisites, nor does it mention platform-specific considerations for non-Windows users.
Recommendations:
  • Include explicit instructions for Linux and macOS users, such as how to install the Azure CLI on those platforms (with appropriate links).
  • Provide terminal/command-line examples for compiling and running the Java application (e.g., using javac and java commands), in addition to or instead of IDE-based instructions.
  • Mention that Eclipse and IntelliJ are cross-platform, and provide guidance for users on Linux/macOS, including any differences in UI or workflow.
  • Where file paths or commands are shown, use platform-agnostic syntax or provide both Windows and Linux/macOS variants.
  • Add a note or section addressing any platform-specific dependencies or troubleshooting steps for Linux/macOS users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-python-how-to-use-queues.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation consistently refers to 'Command Prompt' and instructs users to 'open a Command Prompt window' or 'open a command prompt that has Python in its path' when installing packages or running code. There are no explicit instructions or examples for Linux or macOS users (e.g., using 'terminal', 'bash', or 'shell'). The only shell command shown uses a semicolon (;) to chain commands, which is Unix-style, but the surrounding text is Windows-centric. No PowerShell-specific commands or Windows-only tools are mentioned, but the language and setup steps assume a Windows environment.
Recommendations:
  • Replace 'Command Prompt' with 'terminal' or 'command prompt/terminal' to be inclusive of Linux/macOS users.
  • Add explicit instructions for Linux/macOS users, such as 'Open a terminal window' and clarify that the commands work on all platforms.
  • Where appropriate, show both Windows (cmd.exe) and Unix (bash/zsh) command examples, especially for chained commands or environment variable setup.
  • Mention that Visual Studio Code is cross-platform, or suggest other editors available on Linux/macOS.
  • Ensure that all prerequisite and setup steps are platform-agnostic or provide platform-specific notes as needed.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-queues-topics-subscriptions.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation consistently lists Windows-centric tools (PowerShell) before cross-platform or Linux-native options (CLI) when describing how to create Service Bus entities. PowerShell is explicitly mentioned as a primary method, and the linked PowerShell documentation is Windows-focused. There are no explicit Linux command-line examples or references to Linux-specific tools, and the ordering of options subtly prioritizes Windows workflows.
Recommendations:
  • List cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell) when presenting options for creating or managing resources.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide example commands for both PowerShell and Bash/shell environments.
  • Where PowerShell is referenced, ensure equivalent Bash or shell examples are provided, or link to Linux/macOS-specific quickstarts.
  • Avoid using 'PowerShell' as a default or primary example; instead, present CLI or REST API as the first and most universal option.
  • Add a note clarifying that all management operations can be performed from Linux, macOS, and Windows, and provide links to relevant documentation for each platform.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-quickstart-cli.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation page demonstrates a mild Windows bias by mentioning Azure PowerShell as a local option before any mention of installing or using the Azure CLI natively on Linux or macOS. While the primary example uses Azure Cloud Shell (which is cross-platform), the only explicit local tool mentioned is Azure PowerShell, with no guidance for Linux users on installing or running the Azure CLI locally. There are no Linux- or macOS-specific instructions or examples, and the documentation does not mention Linux command-line environments outside of Cloud Shell Bash.
Recommendations:
  • Explicitly mention that the Azure CLI can be installed and used natively on Linux and macOS, not just via Cloud Shell.
  • Provide installation instructions or a link for Azure CLI on Linux/macOS alongside the PowerShell mention.
  • Avoid suggesting Azure PowerShell as the only local alternative; clarify that Bash and CLI are fully supported on all platforms.
  • Include a note or section for Linux/macOS users to ensure parity and inclusivity.
  • If referencing PowerShell, also mention that PowerShell Core is cross-platform, but emphasize that Bash/CLI is the primary focus for this quickstart.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-queue.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation page demonstrates a mild Windows bias by listing PowerShell as the only command-line management option in the 'Next steps' section, and by referencing PowerShell before mentioning the Azure CLI (which is cross-platform) in the reference links. No Linux-specific tools or examples are provided, and the workflow is centered around the Azure Portal UI, which is platform-agnostic but often associated with Windows environments.
Recommendations:
  • Include explicit Azure CLI examples for deploying and managing Service Bus resources, as the CLI is cross-platform and widely used on Linux.
  • In the 'Next steps' section, add a link to a guide on managing Service Bus with the Azure CLI, and list it before or alongside PowerShell to avoid Windows-first ordering.
  • If mentioning Service Bus Explorer or other tools, clarify their cross-platform availability or suggest alternatives for Linux users if any exist.
  • Consider adding a section or callout that highlights cross-platform command-line options, ensuring Linux users see parity in management workflows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-to-event-grid-integration-concept.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation provides both Azure CLI and PowerShell examples for creating Event Grid subscriptions, but PowerShell is featured as a primary method alongside CLI, with no mention of Bash or Linux-specific tools. PowerShell is a Windows-centric tool, and its inclusion without equivalent Bash or Linux-native scripting examples may disadvantage Linux users. Additionally, the PowerShell example is given equal prominence to CLI, which can be interpreted as a Windows-first approach.
Recommendations:
  • Ensure that all code examples are available in both Azure CLI (which is cross-platform) and PowerShell, but clearly indicate that PowerShell is primarily for Windows users.
  • Add explicit Bash shell examples where scripting is shown, or clarify that Azure CLI commands are intended for Bash or cross-platform shells.
  • Where PowerShell is used, provide a note or alternative for Linux/macOS users, such as Bash or Python scripts.
  • Review the order of examples to present cross-platform (CLI/Bash) options before Windows-specific (PowerShell) ones.
  • Consider adding a table or section summarizing all available tooling options for different platforms (Windows, Linux, macOS) to help users choose the best fit.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-transactions.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-queue-bicep.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-namespace-topic.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-python-how-to-use-topics-subscriptions.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation consistently refers to 'command prompt' and 'Visual Studio Code' as the default terminal and editor, and uses semicolon-separated command chaining (e.g., 'python send.py; python recv.py') which is a Windows CMD pattern. There are no explicit Linux or macOS terminal instructions or mentions of Bash, nor are alternative editors or shells suggested. The phrase 'open a command prompt that has Python in its path' is Windows-centric. No Linux-specific instructions, screenshots, or troubleshooting are provided.
Recommendations:
  • Use neutral terms like 'terminal' or 'shell' instead of 'command prompt', and clarify that instructions apply to Windows, Linux, and macOS.
  • Provide both Windows and Linux/macOS command examples, e.g., use '&&' for Bash and ';' for CMD/PowerShell, or explain the difference.
  • Mention alternative editors such as 'nano', 'vim', or 'gedit' for Linux users alongside Visual Studio Code.
  • Include notes or callouts for any OS-specific steps, such as how to ensure Python is in the PATH on different platforms.
  • Add Linux/macOS screenshots or clarify that the Azure CLI and Python code work cross-platform.
  • Explicitly state that the instructions are valid for all major operating systems, and provide troubleshooting tips for common Linux/macOS issues (e.g., permissions, package installation).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-typescript-how-to-use-topics-subscriptions.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation displays a mild Windows bias by referencing Windows-specific tools and patterns (such as PowerShell and 'command prompt') and mentioning Windows deployment options before Linux equivalents. There are no explicit Linux or cross-platform terminal instructions, and a key deployment link refers to using Windows PowerShell, with no Linux alternative provided. The language used (e.g., 'command prompt') and the absence of explicit Linux shell examples or instructions may confuse or exclude Linux users.
Recommendations:
  • When referring to terminals, use cross-platform language such as 'terminal' or 'shell' instead of 'command prompt', and clarify that instructions apply to both Windows and Linux.
  • For deployment and running commands, provide both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) examples where syntax or context differs.
  • Where links reference Windows-specific guides (e.g., deploying Node.js with Windows PowerShell), add or link to equivalent Linux/macOS guides.
  • Explicitly state that all npm and Node.js commands work on Linux/macOS, and provide any necessary Linux-specific prerequisites or troubleshooting tips.
  • Consider including screenshots or terminal output from both Windows and Linux environments to reinforce cross-platform support.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-resource-manager-overview.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page exclusively provides instructions and examples for deploying Azure Service Bus resources using PowerShell, a tool most commonly associated with Windows environments. There are no examples or references for Linux or cross-platform tools such as Azure CLI, Bash, or Cloud Shell. The workflow, installation instructions, and command syntax are all PowerShell-centric, which may alienate or confuse users on Linux or macOS.
Recommendations:
  • Add parallel instructions and examples for deploying ARM templates using Azure CLI (az deployment group create), which is cross-platform and widely used on Linux and macOS.
  • Include Bash shell command examples for template deployment, especially for users working in Linux environments.
  • Mention and provide examples for using Azure Cloud Shell, which supports both Bash and PowerShell and is accessible from any OS.
  • Reorganize the documentation to present both PowerShell and CLI/Bash instructions side-by-side or in clearly separated sections, ensuring neither platform is prioritized over the other.
  • Explicitly state that the instructions apply to all platforms, and provide links to platform-specific setup guides where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-service-endpoints.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation provides detailed instructions for configuring network service endpoints for Azure Service Bus, but it demonstrates a Windows bias. The Azure PowerShell section is more detailed than the Azure CLI section, and PowerShell is mentioned after CLI but before REST API. There are no explicit Linux or cross-platform shell (bash) examples, and no mention of Linux-specific tools or workflows. The instructions for deploying ARM templates link to PowerShell deployment guidance, with no reference to Azure CLI or other cross-platform deployment methods.
Recommendations:
  • Add explicit Linux/bash examples alongside or before PowerShell examples, especially in sections about deploying ARM templates and managing network rules.
  • Provide parity in command-line examples: for every PowerShell command, include the equivalent Azure CLI (bash) command.
  • When referencing deployment instructions, link to both PowerShell and Azure CLI documentation, or provide a cross-platform deployment example.
  • Avoid assuming the use of Windows tools or the Azure portal; clarify that all steps can be performed from any OS using CLI or REST.
  • Consider a 'Choose your platform' section at the start of command-line sections, guiding users to Windows (PowerShell), Linux/macOS (bash/CLI), or REST API instructions.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-to-event-grid-integration-function.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a strong Windows bias by exclusively referencing Visual Studio 2022 (a Windows-centric IDE) and its publishing workflow, including screenshots and instructions that are specific to Windows. There are no examples or instructions for Linux or cross-platform development environments (such as Visual Studio Code, Azure CLI, or command-line deployment). The tutorial assumes the user is on Windows and does not mention or provide parity for Linux users.
Recommendations:
  • Add a section or parallel instructions for developing and deploying Azure Functions using cross-platform tools such as Visual Studio Code, Azure CLI, or Azure Functions Core Tools, which work on Linux and macOS.
  • Provide command-line examples (e.g., using Azure CLI or PowerShell Core) for deployment and management tasks, ensuring these commands are cross-platform.
  • Include screenshots and workflow steps for Linux/macOS environments, or at least reference official guides for those platforms.
  • Explicitly state that the tutorial is Windows-specific if Linux/macOS parity is not intended, or update the tutorial to ensure full parity.
  • Mention alternative editors (e.g., Visual Studio Code) and provide guidance for users who do not use Visual Studio 2022.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-troubleshooting-guide.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias in several areas: troubleshooting steps and examples often present Windows commands (e.g., PowerShell's 'tnc', use of '.\psping.exe') before or instead of Linux equivalents; Windows-specific tools (psping, PowerShell) are highlighted, with Linux alternatives mentioned only briefly or as an afterthought. Some diagnostic instructions and logging/tracing guidance are .NET/.NET Core-centric, with little to no mention of Linux-native or cross-platform approaches. Linux users may find the guidance less accessible or discoverable.
Recommendations:
  • For every Windows/Powershell command or tool mentioned (e.g., 'tnc', '.\psping.exe'), provide the Linux/macOS equivalent (e.g., 'telnet', 'nc', 'ss', 'ping', 'hping3') side-by-side and with equal prominence.
  • When referencing tools like 'psping', suggest cross-platform alternatives (e.g., 'iperf', 'hping3', 'nmap') and provide download links or installation instructions for Linux/macOS.
  • Avoid presenting Windows commands or tools first by default; instead, group instructions by platform or present them in parallel.
  • Expand diagnostic and logging sections to include examples for non-.NET environments and cross-platform SDKs (e.g., Java, Python), and mention Linux-native logging/tracing tools (e.g., journalctl, syslog, strace, tcpdump).
  • Where .NET or Visual Studio is referenced, add notes or links for equivalent workflows in Linux development environments (e.g., VS Code, JetBrains Rider, command-line SDK usage).
  • Audit the documentation for other subtle Windows-first language or assumptions (e.g., references to 'Console.ReadKey()', Visual Studio, or Windows-specific troubleshooting patterns) and provide Linux/macOS context or alternatives.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-sas.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a moderate Windows bias. Administrative instructions and tooling references (such as Azure PowerShell and the Azure portal) are presented before or more prominently than cross-platform alternatives. The only code sample is in C#, a language most associated with Windows development. There are no explicit Linux shell or scripting examples, and no mention of Linux-native tools or workflows. While Azure CLI is mentioned, it is listed after PowerShell, and there are no Bash or Linux-specific command examples. The documentation assumes familiarity with Windows-centric patterns and tools.
Recommendations:
  • Provide example commands for both Azure PowerShell and Azure CLI side-by-side, making clear that Azure CLI is fully cross-platform and often preferred for Linux/macOS users.
  • Include at least one example of generating a SAS token using Bash/shell scripting (e.g., using openssl and curl), or link to such examples.
  • When referencing the Azure portal, clarify that it is web-based and platform-agnostic, but also provide CLI alternatives for all portal actions.
  • Add code samples in additional languages commonly used on Linux (e.g., Python, JavaScript/Node.js), or link to such samples.
  • Avoid using Windows-centric language (such as referencing PowerShell or C# first) unless there is a technical reason; strive for neutral ordering or explicit cross-platform parity.
  • Explicitly mention that all SDKs and tools are available on Linux, and provide links to relevant installation guides for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-tutorial-topics-subscriptions-cli.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-typescript-how-to-use-queues.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/transport-layer-security-enforce-minimum-version.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page does not provide any platform-specific examples or commands (such as PowerShell, CLI, or scripting) for configuring the minimum TLS version for Azure Service Bus. However, it also does not mention any Windows-specific tools, commands, or patterns. The absence of both Windows and Linux examples means there is a lack of parity, but no explicit Windows bias is present. Still, the lack of Linux (or cross-platform) command-line examples is a missed opportunity for inclusivity.
Recommendations:
  • Add explicit examples for configuring the minimum TLS version using cross-platform tools such as Azure CLI and Azure PowerShell.
  • Ensure that any scripting or command-line instructions are provided for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI).
  • If referencing Azure Portal steps, clarify that these are platform-agnostic.
  • Where possible, provide sample commands for both PowerShell and Bash to demonstrate parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/topic-filters.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively provides .NET code examples and does not include any platform-specific command-line examples (such as PowerShell or Windows tools). However, it also does not provide any Linux-specific examples, such as using Azure CLI, Bash scripts, or cross-platform SDKs outside of .NET. This lack of Linux or cross-platform command-line examples may make it less accessible to Linux users or those preferring non-.NET environments.
Recommendations:
  • Add Azure CLI examples for creating and managing filters and rules, as the CLI is cross-platform and widely used on Linux.
  • Include code samples in additional languages that are popular on Linux, such as Python (using the Azure SDK for Python) or JavaScript/TypeScript.
  • If relevant, provide Bash script snippets for automating Service Bus rule/filter management.
  • Explicitly mention cross-platform tools (e.g., Azure CLI, REST API) and provide usage instructions.
  • Clarify that the .NET examples are cross-platform, but also offer guidance for users on Linux who may not use .NET.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/test-locally-with-service-bus-emulator.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows-first bias by presenting Windows and PowerShell-based instructions before Linux/macOS equivalents, requiring WSL for Windows users, and referencing Windows-specific tools and path conventions. Linux and macOS instructions are less detailed and sometimes only mentioned after Windows steps. There is also an emphasis on Docker Desktop (with a Windows install link) and WSL configuration, while native Linux workflows are less emphasized.
Recommendations:
  • Present Linux/macOS instructions alongside or before Windows instructions, or use parallel tabbed sections for each OS.
  • Provide native Linux and macOS setup steps with equal detail, including terminal commands and file path conventions.
  • Avoid requiring WSL for Windows users unless absolutely necessary; if used, clarify why and provide alternatives.
  • Include Linux and macOS Docker installation links in prerequisites, not just Windows.
  • When referencing file paths, show both Windows and Unix-style examples.
  • Ensure all scripts and commands are demonstrated for both PowerShell/Windows and Bash/Linux environments.
  • Where possible, use cross-platform tools and language in examples, minimizing Windows-specific terminology.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/transport-layer-security-configure-minimum-version.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary:
The documentation page exhibits several signs of Windows bias. It references Windows-specific tools (ARMClient.exe), provides PowerShell examples, and omits equivalent Linux-native instructions or tools (e.g., using curl/jq for REST API calls, or az CLI for token retrieval). The order of presentation also often places Windows/PowerShell approaches before cross-platform or Linux-friendly alternatives. There are no explicit Linux or bash examples for key tasks such as querying the ARM API or obtaining tokens.
Recommendations:
  • Provide Linux/bash-native examples for all command-line operations, such as using curl and jq to query the ARM API and az CLI to obtain tokens.
  • Mention and demonstrate cross-platform tools (e.g., az CLI, curl) before or alongside Windows-specific tools like ARMClient.exe.
  • Where PowerShell is shown, also provide bash/zsh equivalents.
  • Clarify that ARMClient.exe is a Windows-only tool and suggest alternatives for Linux/macOS users.
  • Audit all screenshots and instructions to ensure they are not Windows-centric unless the feature is truly Windows-only.