Service Bus Messaging
134
Total Pages
61
Linux-Friendly Pages
73
Pages with Bias
54.5%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
377 issues found
Showing 51-75 of 377 flagged pages
Service Bus Messaging
Authenticate an application to access Azure Service Bus entities
...cles/service-bus-messaging/authenticate-application.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and examples. The authentication and role assignment instructions reference Azure PowerShell and .NET code samples, with no mention of Linux-specific workflows or cross-platform SDKs. The code sample is in C# using .NET, which is traditionally Windows-focused, and there are no equivalent examples for Linux environments (such as Python, Java, or Node.js). The instructions for registering applications and assigning roles are centered around the Azure portal and PowerShell, with CLI mentioned only in the 'Next steps' section and not in the main workflow. There is no guidance for Linux users or those using non-Windows development stacks.
Recommendations
- Provide equivalent code samples in cross-platform languages such as Python, Java, or Node.js, using their respective Azure SDKs.
- Include explicit instructions and examples for using Azure CLI for authentication and role assignment, placing them alongside or before PowerShell instructions.
- Add guidance for Linux/macOS environments, including any OS-specific considerations for authentication and SDK usage.
- Reference cross-platform tools and workflows earlier in the documentation, not just in the 'Next steps' section.
- Ensure that screenshots and UI instructions clarify that the Azure portal is accessible from any OS.
Create Pull Request
Service Bus Messaging
Azure messaging services - Service Manager to Resource Manager
...vice-bus-messaging/deprecate-service-bus-management.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page focuses heavily on PowerShell cmdlets for both deprecated and new Azure Service Manager/Resource Manager operations. There are no examples or mentions of Linux-native tools (such as Azure CLI, Bash, or scripting with curl), nor are cross-platform alternatives discussed. The PowerShell commands are presented as the primary or sole method for scripting and automation, which may disadvantage Linux users or those preferring platform-neutral tooling.
Recommendations
- Add equivalent Azure CLI commands for each PowerShell example, with links to CLI documentation.
- Include REST API usage examples using curl or HTTPie, demonstrating cross-platform access.
- Explicitly mention that PowerShell Core is available on Linux and macOS, but also provide CLI/Bash alternatives for users who do not use PowerShell.
- Reorganize examples so that platform-neutral (REST API, CLI) approaches are presented before or alongside PowerShell commands.
- Add a section comparing PowerShell and Azure CLI usage for common tasks, highlighting cross-platform options.
Service Bus Messaging
Enable dead lettering for Azure Service Bus queues and subscriptions
...n/articles/service-bus-messaging/enable-dead-letter.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for enabling dead lettering on Azure Service Bus queues and subscriptions. However, the PowerShell section is extensive, with multiple code blocks and detailed object manipulation, which is specific to Windows environments. PowerShell is presented as a primary automation option alongside CLI, but no equivalent Linux-native scripting (such as Bash or shell scripting) is shown. There is also no mention of Linux-specific tools or patterns, and PowerShell examples appear before programming language samples, reinforcing a Windows-centric approach.
Recommendations
- Add Bash or shell script examples for common operations, especially for users on Linux or macOS.
- Clarify that Azure CLI is cross-platform and highlight its usage for Linux/macOS users.
- Consider including automation examples using other Linux-native tools (e.g., curl with REST API, or Terraform).
- Reorder sections so that cross-platform tools (CLI, ARM templates) are presented before Windows-specific tools (PowerShell).
- Explicitly mention platform compatibility for each tool, helping users choose the best option for their OS.
Service Bus Messaging
Enable Azure Service Bus message sessions | Microsoft Docs
...icles/service-bus-messaging/enable-message-sessions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for enabling Service Bus sessions, but PowerShell (a Windows-centric tool) is given its own dedicated section and detailed examples. There is no mention of Linux-specific tools or shell patterns (e.g., Bash), nor are cross-platform considerations discussed. PowerShell is presented as a primary method alongside CLI, which may suggest a Windows-first bias. The Resource Manager template section is platform-neutral, but the lack of Linux shell examples or explicit parity recommendations is notable.
Recommendations
- Add explicit Bash or shell script examples for Linux users, especially for Azure CLI usage.
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and recommend CLI for cross-platform scenarios.
- Consider mentioning cross-platform alternatives to PowerShell, such as Bash or zsh, and provide equivalent command examples.
- Reorder sections to present Azure CLI before PowerShell, emphasizing CLI as the default cross-platform tool.
- Include notes or tips for Linux/macOS users where relevant, such as installation or usage differences.
Service Bus Messaging
Azure Service Bus - suspend messaging entities
.../main/articles/service-bus-messaging/entity-suspend.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides explicit instructions and code examples for changing queue status using Azure PowerShell, a Windows-centric tool. There are no equivalent examples for Linux users (e.g., using Azure CLI or REST API), and PowerShell is mentioned before any cross-platform alternatives. This creates a bias toward Windows users and may hinder Linux users from easily following the instructions.
Recommendations
- Add Azure CLI examples for changing queue, topic, and subscription status, as Azure CLI is cross-platform and widely used on Linux.
- Include REST API example or reference for advanced users who may prefer direct API calls.
- Present PowerShell and CLI examples side-by-side or in parallel sections, making it clear that both are supported and available.
- Explicitly mention that Azure CLI and REST API can be used on Linux, macOS, and Windows, improving inclusivity.
- Review other sections for similar bias and ensure Linux parity throughout the documentation.
Service Bus Messaging
Azure Service Bus message sessions | Microsoft Docs
...ain/articles/service-bus-messaging/message-sessions.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page displays Windows bias by mentioning PowerShell and Azure portal as primary tools for enabling message sessions, with no explicit mention of Linux-specific tools or shell commands (e.g., Bash, Azure CLI on Linux). PowerShell is listed before CLI, and there are no direct Linux or cross-platform command-line examples. The samples section lists programming languages but omits platform-specific setup instructions, which could disadvantage Linux users.
Recommendations
- Add explicit Linux/Bash/Azure CLI examples for enabling message sessions, alongside PowerShell.
- Mention Azure CLI as a cross-platform tool before or alongside PowerShell, and provide sample commands for both.
- Clarify that all SDKs and tools (CLI, PowerShell) are available on Linux, and provide installation/setup links for Linux users.
- Include a section or note on platform parity, reassuring users that all features are accessible on Linux and macOS, not just Windows.
- Where possible, provide screenshots or walkthroughs for Linux environments in addition to Windows/Azure portal.
Service Bus Messaging
Integrate Azure Service Bus with Azure Private Link Service
...articles/service-bus-messaging/private-link-service.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits Windows bias in several ways. All command-line examples for automating private endpoint creation use Azure PowerShell, which is most commonly used on Windows. There are no equivalent examples using Azure CLI, which is cross-platform and preferred on Linux/macOS. The validation section instructs users to create a Windows VM and references the Windows VM creation guide, with no mention of Linux VM alternatives or instructions. All screenshots and portal instructions are Windows-centric, and there is no guidance for Linux users or parity in tooling.
Recommendations
- Add Azure CLI examples for creating and managing private endpoints, alongside or before PowerShell examples.
- Include instructions and links for creating a Linux VM in Azure, and provide validation steps using Linux command-line tools (e.g., nslookup, dig) on Linux.
- Ensure that portal screenshots and instructions are platform-neutral, or include notes for Linux/macOS users where relevant.
- Explicitly mention that Azure CLI can be used on all platforms and provide sample commands.
- Review documentation for other Windows-specific references and provide Linux/macOS equivalents.
Service Bus Messaging
Quickstart - Use Azure Service Bus queues from .NET app
...essaging/service-bus-dotnet-get-started-with-queues.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All instructions assume the use of Visual Studio (Windows-only or Windows-first experience), and package installation is shown exclusively via the NuGet Package Manager Console using PowerShell commands. There are no instructions or examples for Linux users, such as using VS Code, JetBrains Rider, or .NET CLI commands. The workflow and screenshots are tailored to Windows environments, and there is no mention of how to perform equivalent steps on Linux or macOS.
Recommendations
- Add instructions for using cross-platform editors like VS Code and JetBrains Rider, including project creation and management.
- Provide .NET CLI commands for creating projects and installing NuGet packages (e.g., 'dotnet new console', 'dotnet add package Azure.Messaging.ServiceBus').
- Include screenshots and workflow steps for Linux and macOS environments.
- Clarify which steps are platform-agnostic and which are Windows-specific, and offer alternatives where possible.
- Mention that the .NET SDK and Azure Service Bus libraries are cross-platform, and provide guidance for non-Windows users.
- Avoid assuming Visual Studio is the only development environment; offer parity for Linux and macOS users.
Service Bus Messaging
Use legacy WindowsAzure.ServiceBus .NET framework library with AMQP 1.0 | Microsoft Docs
...icles/service-bus-messaging/service-bus-amqp-dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on the legacy WindowsAzure.ServiceBus .NET Framework library, which is inherently Windows-centric. All examples and configuration details assume usage of .NET on Windows, with no mention of Linux or cross-platform usage. The instructions reference Windows-specific tools (Azure portal, .NET Framework) and do not provide Linux equivalents or guidance for running the library on Linux (e.g., via Mono or .NET Core). There are no Linux or cross-platform code samples, nor any discussion of platform-specific considerations.
Recommendations
- Add explicit guidance for using the library on Linux, including any prerequisites (e.g., Mono, .NET Core compatibility, limitations).
- Provide Linux-specific or cross-platform examples for connection string configuration and usage.
- Mention any differences or caveats when running the library on non-Windows platforms.
- Reference Linux tools or command-line alternatives for obtaining connection strings and managing Service Bus namespaces (e.g., Azure CLI, az commands).
- Clarify whether the legacy library is supported or recommended for Linux environments, and suggest alternatives if not.
Service Bus Messaging
Get started with Azure Service Bus topics (.NET)
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-dotnet-how-to-use-topics-subscriptions.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio and PowerShell. All instructions for creating projects, managing packages, and authentication are given using Visual Studio GUI and PowerShell commands, with no mention of Linux or cross-platform alternatives such as VS Code, dotnet CLI, or Bash. There are no instructions for Linux users or guidance for using non-Windows tools, making it difficult for developers on Linux or macOS to follow the quickstart.
Recommendations
- Add instructions for using the dotnet CLI to create projects, add packages, and run applications, which works on Windows, Linux, and macOS.
- Include alternative steps for package installation using 'dotnet add package' instead of only PowerShell/Visual Studio NuGet Package Manager.
- Provide guidance for using VS Code or other cross-platform editors, not just Visual Studio.
- Explicitly mention that the code and libraries work on Linux and macOS, and provide any necessary setup steps for those platforms.
- Add screenshots or terminal examples for Linux/macOS environments where appropriate.
- Clarify that authentication via DefaultAzureCredential works outside Visual Studio, and provide instructions for signing in with Azure CLI or environment variables on Linux/macOS.
Service Bus Messaging
Azure Service Bus messages, payloads, and serialization | Microsoft Docs
...service-bus-messaging/service-bus-messages-payloads.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Dotnet Heavy
Summary
The documentation page demonstrates a bias towards Windows and .NET environments. It references .NET, .NET Framework, and .NET Standard APIs extensively, with examples and explanations tailored to those platforms. There are no Linux-specific or cross-platform code samples, nor are Java or Python examples provided despite mentioning Java clients. The focus on .NET serialization and related APIs, as well as links to .NET documentation, suggests a Windows-first approach. Linux tools, patterns, or equivalent code samples are absent.
Recommendations
- Add code samples for Java, Python, and other supported languages, especially for serialization and message handling.
- Include examples and references for Linux environments, such as using Service Bus with Java or Python on Linux.
- Balance .NET-specific explanations with equivalent details for other platforms and SDKs.
- Provide links to cross-platform SDK documentation and usage guides.
- Explicitly mention platform parity and any differences in behavior or support between Windows/.NET and Linux/other languages.
Service Bus Messaging
.NET multi-tier application using Azure Service Bus | Microsoft Docs
...ice-bus-dotnet-multi-tier-app-using-service-bus-queues.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio and Azure Cloud Service roles. All setup and workflow instructions assume Windows, with no mention of Linux or cross-platform alternatives. Windows tools such as Visual Studio, Azure Compute Emulator, and Windows-specific UI dialogs are referenced exclusively. There are no Linux or CLI-based examples, nor any guidance for developing or running the application on non-Windows platforms.
Recommendations
- Add instructions for setting up and running the sample on Linux, including using .NET CLI and VS Code.
- Provide examples for creating and managing Azure resources using Azure CLI or PowerShell Core (cross-platform), not just through the Azure Portal.
- Include guidance for running and debugging the application locally on Linux and macOS, such as using Docker containers or local emulators compatible with non-Windows OS.
- Reference cross-platform tools and editors (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
- Clarify which steps are Windows-specific and provide Linux/macOS equivalents where possible.
- Avoid exclusive reliance on Windows-only features like Azure Compute Emulator; suggest alternatives or note limitations for non-Windows users.
Service Bus Messaging
Azure Service Bus Geo-Disaster Recovery | Microsoft Docs
...n/articles/service-bus-messaging/service-bus-geo-dr.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and patterns. Examples and instructions reference PowerShell (PS) and .NET samples, with no explicit mention of Linux shell equivalents or cross-platform command-line instructions. The use of 'PS/CLI' is ambiguous and does not clarify Linux support, and all sample code is .NET-focused, which is more common on Windows. There are no Bash, Azure CLI (az), or Linux-specific examples, and Windows terminology (PowerShell, .NET) is used before or instead of Linux alternatives.
Recommendations
- Add explicit Azure CLI (az) command examples for all management operations, including pairing, failover, and monitoring, with syntax suitable for Bash/Linux shells.
- Include sample code in cross-platform languages (e.g., Python, Java) alongside .NET, and reference their respective GitHub samples.
- Clarify in all instructions whether commands/tools are cross-platform, and provide Linux/Bash equivalents where PowerShell is mentioned.
- Add a section or callouts for Linux users, detailing any differences in setup or tooling, and ensure parity in step-by-step instructions.
- Reference Linux-friendly tools and patterns (e.g., Bash scripts, cron for automation) alongside Windows tools.
- Ensure screenshots and UI instructions are not Windows-centric, or provide notes for Linux/macOS users where relevant.
Service Bus Messaging
Configure IP firewall rules for Azure Service Bus
...cles/service-bus-messaging/service-bus-ip-filtering.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides examples and instructions for configuring IP firewall rules for Azure Service Bus using the Azure portal, Resource Manager templates, Azure CLI, and Azure PowerShell. However, there is a noticeable Windows bias: PowerShell is mentioned explicitly and given its own section, while Linux-native tools or shell scripting are not referenced. The CLI section is present but lacks concrete examples, and there are no bash or Linux shell script samples. The deployment instructions for Resource Manager templates link to PowerShell-based deployment guidance, not to Azure CLI or bash equivalents. Overall, Windows-centric tools and patterns are mentioned first or exclusively, with Linux parity missing in example coverage.
Recommendations
- Add explicit bash/Azure CLI examples for managing IP firewall rules, including full command samples for add, list, update, and remove operations.
- Provide deployment instructions for Resource Manager templates using Azure CLI (az deployment) and bash, not just PowerShell.
- Ensure that CLI and Linux-native instructions are presented before or alongside PowerShell examples to avoid Windows-first ordering.
- Reference cross-platform tools and patterns (e.g., az CLI, REST API via curl) in equal detail to PowerShell.
- Include notes or sections for Linux/macOS users, clarifying any differences or prerequisites.
Service Bus Messaging
Azure Service Bus - messaging exceptions | Microsoft Docs
...s-messaging/service-bus-messaging-exceptions-latest.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates Windows bias primarily in the troubleshooting section for SocketException, where only a PowerShell example (nslookup) is provided, and the output is shown in a Windows-centric format. There is no mention of equivalent Linux commands (e.g., dig, nslookup on Linux, host), nor is there guidance for users on non-Windows platforms. Additionally, the use of Windows-style paths (PS C:\>) and terminology further reinforces the Windows-first approach. No Linux or cross-platform alternatives are presented, which may hinder users working in Linux or macOS environments.
Recommendations
- Provide equivalent Linux/macOS command-line examples (e.g., 'nslookup', 'dig', or 'host') alongside PowerShell examples.
- Show sample outputs for both Windows and Linux/macOS environments to help users recognize expected results.
- Avoid using only Windows paths or prompts (e.g., 'PS C:\>'); instead, use generic or platform-neutral prompts, or show both.
- Explicitly mention that troubleshooting steps apply to all platforms, and clarify any platform-specific differences.
- Audit other examples and troubleshooting steps to ensure Linux parity throughout the documentation.
Service Bus Messaging
Quickstart: Get started with Azure Service Bus queues (JavaScript)
...-bus-messaging/service-bus-nodejs-how-to-use-queues.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. References to Windows-specific tools (such as Command Prompt and PowerShell) are present, and instructions often mention 'Command Prompt' or 'Windows PowerShell' without equivalent Linux/macOS terminal guidance. The example for deploying a Node.js cloud service specifically references Windows PowerShell, and the instructions for running commands default to 'Command Prompt' terminology. There are no explicit Linux/macOS examples or terminal instructions, and no mention of platform-specific differences or considerations.
Recommendations
- Provide explicit instructions for Linux/macOS users, such as using 'Terminal' instead of 'Command Prompt', and clarify that commands work cross-platform.
- Add Linux/macOS equivalents for any references to Windows tools (e.g., mention Bash, zsh, or Terminal alongside Command Prompt/PowerShell).
- Where deployment or development instructions reference Windows PowerShell, add links or steps for Bash or other common Linux shells.
- Review screenshots and UI instructions to ensure they are not Windows-specific, or provide alternatives if necessary.
- Add a note at the beginning clarifying cross-platform compatibility and pointing to platform-specific guidance if available.
Service Bus Messaging
Migrate Azure Service Bus namespaces - standard to premium
...-bus-messaging/service-bus-migrate-standard-premium.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by explicitly mentioning PowerShell as a migration tool alongside Azure CLI, but does not provide any Linux-specific examples or mention Linux shell environments. The instructions and environment variable setup are generic, but the reference to PowerShell and the absence of Linux/Bash examples or notes suggest a preference for Windows tooling. There is no mention of Linux-specific considerations, nor are there examples using Bash or other Linux-native scripting environments.
Recommendations
- Add explicit Bash/Linux shell examples for all CLI commands, including environment variable setup and command execution.
- Clarify that Azure CLI commands work cross-platform and provide notes or links for Linux users regarding installation and usage.
- Remove or balance references to PowerShell by including equivalent Bash scripts or instructions.
- Mention any OS-specific caveats or considerations (e.g., file paths, environment variable syntax) where relevant.
- Ensure screenshots and UI references do not assume a Windows environment when showing the Azure portal.
Service Bus Messaging
Get started with Azure Service Bus topics (JavaScript)
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-nodejs-how-to-use-topics-subscriptions.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. It references Windows-specific tooling (e.g., Windows PowerShell and Azure Website deployment guides), and in some places, Windows tools are mentioned before Linux alternatives. There are no explicit Linux-specific instructions or examples, and the guidance for running commands is generic ('command prompt'), which may confuse Linux users. The documentation does not provide parity for Linux environments or mention Linux-specific editors, shells, or deployment workflows.
Recommendations
- Add explicit instructions for Linux users, such as using 'terminal' or 'shell' instead of only 'command prompt', and clarify that commands work on both Windows and Linux.
- Provide links to Linux-specific deployment guides (e.g., deploying Node.js apps to Azure App Service from Linux).
- Mention Linux-friendly editors (such as Vim, Nano, or even VS Code for Linux) alongside Visual Studio Code.
- Where Windows PowerShell is referenced, also mention Bash or other common Linux shells.
- Clarify that Azure CLI works on Linux, macOS, and Windows, and provide installation instructions for all platforms.
- Avoid using Windows-centric terminology (e.g., 'command prompt') exclusively; use cross-platform terms or provide both.
Service Bus Messaging
Quickstart - Use the Azure CLI to create a Service Bus queue | Microsoft Docs
...es/service-bus-messaging/service-bus-quickstart-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While it recommends using Azure Cloud Shell (which is cross-platform), it mentions Azure PowerShell as an alternative before mentioning local CLI installation on Linux or macOS. There are no explicit Linux/macOS installation or usage examples, and the only alternative to Cloud Shell is 'install and use Azure PowerShell on your machine,' which is more common on Windows. No Linux-specific tools, shells, or instructions are provided.
Recommendations
- Explicitly mention that Azure CLI can be installed and used on Linux and macOS, not just Windows.
- Provide installation instructions or a link for Azure CLI on Linux/macOS alongside the PowerShell mention.
- Clarify that Azure Cloud Shell supports both Bash and PowerShell, and that Bash is the default and cross-platform friendly.
- Include a note or example for running the Azure CLI locally on Linux/macOS.
- Avoid suggesting PowerShell as the primary or only local alternative to Cloud Shell.
Service Bus Messaging
Create a Service Bus authorization rule using an Azure template
...ng/service-bus-resource-manager-namespace-auth-rule.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. PowerShell is presented as the first deployment example, and the 'Next steps' section prioritizes PowerShell and Service Bus Explorer (a Windows-only tool) for resource management. While Azure CLI is included, the CLI example uses the deprecated 'azure' CLI rather than the modern 'az' CLI, and does not highlight Linux-specific usage or parity. There are no Linux-specific management tools or workflows mentioned.
Recommendations
- Present Azure CLI examples before or alongside PowerShell, using the current 'az' CLI syntax, and clarify cross-platform compatibility.
- Include Linux-specific management options, such as using Azure CLI on Linux, Bash scripts, or other open-source tools.
- Mention Service Bus Explorer alternatives for Linux/macOS, or clarify platform limitations.
- Add notes or sections highlighting how all steps can be performed on Linux and macOS, not just Windows.
- Ensure links to management guides include both PowerShell and CLI options, and avoid Windows-centric phrasing.
Service Bus Messaging
Azure Service Bus messaging - queues, topics, and subscriptions
...s-messaging/service-bus-queues-topics-subscriptions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as a primary method for creating Service Bus entities, mentioning it before the cross-platform Azure CLI, and not providing explicit Linux/bash examples or guidance. The use of 'PowerShell' as a top-level option and the lack of parity in example coverage for Linux users may make the documentation less approachable for non-Windows audiences.
Recommendations
- List Azure CLI before PowerShell in creation instructions, as CLI is cross-platform and more inclusive for Linux/macOS users.
- Explicitly mention Bash or shell scripting as an option for automation, and provide links to bash-specific quickstarts or examples where available.
- Ensure that all PowerShell examples have equivalent Azure CLI/bash examples, and that these are shown side-by-side or with equal prominence.
- Avoid using 'PowerShell' as a synonym for scripting or automation; clarify when instructions are Windows-specific.
- Consider adding a table or section summarizing all available tooling (Portal, CLI, PowerShell, ARM templates) with notes on platform compatibility.
Service Bus Messaging
Create Service Bus topic subscription and rule using Azure template
...service-bus-resource-manager-namespace-topic-with-rule.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page displays mild Windows bias. The PowerShell example is presented before the Azure CLI example, and there is a dedicated 'Manage Service Bus with PowerShell' link in the next steps, but no equivalent for Bash or Linux shell scripting. The Service Bus Explorer tool referenced is a Windows desktop application, with no mention of Linux-native alternatives. While Azure CLI is included and is cross-platform, the ordering and tool recommendations favor Windows users.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Add Bash or shell script examples for common deployment and management tasks, especially in 'Next steps'.
- Include links to Linux-compatible Service Bus management tools (e.g., mention az CLI, REST API, or third-party cross-platform GUIs).
- Explicitly state that all commands (especially Azure CLI) work on Linux, macOS, and Windows.
- If referencing Service Bus Explorer, note its platform limitations and suggest alternatives for non-Windows users.
Service Bus Messaging
Create Azure Service Bus resources using templates
...bus-messaging/service-bus-resource-manager-overview.md
High Priority
View Details →
Detected Bias Types
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. There are no equivalent examples or guidance for Linux users (e.g., using Azure CLI, Bash, or cross-platform tools). The workflow and commands are tailored to PowerShell, and installation instructions are only given for Azure PowerShell, reinforcing a Windows-centric approach.
Recommendations
- Add equivalent deployment instructions and examples using Azure CLI, which is cross-platform and widely used on Linux and macOS.
- Include Bash shell examples for template deployment, resource group creation, and parameter file usage.
- Mention and link to documentation for deploying ARM templates via the Azure Portal and REST API, which are platform-agnostic.
- Clearly indicate that PowerShell is one of several options, and provide a section or sidebar for Linux/macOS users.
- Ensure installation instructions for Azure CLI are present alongside PowerShell instructions.
Service Bus Messaging
Azure Service Bus access control with Shared Access Signatures
...main/articles/service-bus-messaging/service-bus-sas.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. It references Windows-specific tools (Azure PowerShell) before mentioning Azure CLI, and provides explicit instructions for key regeneration using Azure PowerShell and the Azure portal, both of which are more commonly used on Windows. There are no explicit Linux shell or cross-platform code examples for SAS token generation or management, nor are there any Bash or Linux-specific instructions. The only code sample is in C#, which is cross-platform but traditionally associated with Windows development. No Linux-specific patterns, tools, or examples are provided, and the order of presentation generally favors Windows-centric approaches.
Recommendations
- Provide explicit Bash or Linux shell examples for SAS token generation and management, especially for tasks like HTTP requests or key rotation.
- Include instructions for using Azure CLI before or alongside Azure PowerShell, and clarify CLI usage on Linux/macOS.
- Add cross-platform code samples (e.g., Python, JavaScript) for SAS token generation and usage.
- Mention Linux-compatible tools (e.g., curl, wget) for HTTP-level operations.
- Ensure screenshots and UI instructions are not Windows-specific, or provide Linux/macOS equivalents where relevant.
- Clarify that all SDKs and tools are available on Linux and macOS, and provide links or notes for installation on those platforms.
Service Bus Messaging
Troubleshooting guide for Azure Service Bus | Microsoft Docs
...ice-bus-messaging/service-bus-troubleshooting-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: Windows-specific tools (PowerShell, tnc, psping) are mentioned first or exclusively, with Linux alternatives sometimes provided only as an afterthought. Diagnostic and troubleshooting examples rely heavily on Windows tools, and some sections (such as logging and diagnostics) reference .NET and Windows-centric SDKs and patterns without offering equivalent Linux or cross-platform guidance. There is a lack of parity in example commands and recommended tooling for Linux users.
Recommendations
- Provide Linux and macOS command examples alongside Windows/PowerShell examples, not just as secondary notes.
- List cross-platform tools (e.g., netcat, nmap, tcping) and usage for network troubleshooting, and avoid recommending Windows-only tools like psping without alternatives.
- Ensure that diagnostic and logging instructions include guidance for non-.NET environments and Linux-native logging/tracing tools.
- When referencing SDKs or libraries, clarify cross-platform compatibility and provide links or examples for Java, Python, or other non-Windows languages.
- Review and update troubleshooting steps to ensure Linux users can follow them without needing to translate Windows commands or tools.
- Where possible, use platform-neutral terminology and avoid assuming the reader is on Windows or using Visual Studio.