Event Hubs
122
Total Pages
80
Linux-Friendly Pages
42
Pages with Bias
34.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
211 issues found
Showing 101-125 of 211 flagged pages
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/private-link-service.md
.../blob/main/articles/event-hubs/private-link-service.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell CLI examples for scripting, omitting equivalent Azure CLI (cross-platform) or Bash examples. Additionally, the validation steps explicitly instruct users to create and use a Windows virtual machine, with no mention of Linux VM alternatives. This approach assumes a Windows-centric workflow and does not offer parity for Linux or cross-platform users.
Recommendations
- Provide equivalent Azure CLI (az) and/or Bash scripting examples alongside PowerShell for all automation and resource creation steps.
- In the validation section, include instructions for creating and using a Linux virtual machine, or make the instructions OS-agnostic (e.g., show both Windows and Linux VM creation links, and provide nslookup commands for both environments).
- Where screenshots or UI steps are shown, clarify that the Azure portal is cross-platform and accessible from any OS.
- Explicitly state that all steps can be performed from Windows, Linux, or macOS, and provide links to relevant cross-platform tooling documentation.
- Review for any other Windows-specific terminology or assumptions, and ensure Linux and macOS users are equally supported.
Create Pull Request
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/schema-registry-concepts.md
...b/main/articles/event-hubs/schema-registry-concepts.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While it covers cross-platform SDKs and mentions Azure CLI (which is cross-platform), it specifically highlights PowerShell as a management tool and provides a PowerShell example link, but does not provide equivalent Linux shell or Bash examples. The order of mention also places PowerShell alongside Azure CLI, which may suggest a Windows-first approach. There is no explicit example or guidance for Linux-native tools or shell scripting, and the management samples section omits Bash or Linux command-line usage.
Recommendations
- Add explicit Bash or Linux shell examples for schema management tasks, especially for adding schemas to schema groups.
- Ensure that CLI examples are presented before or alongside PowerShell to avoid a Windows-first impression.
- Where PowerShell is mentioned, clarify that it is primarily for Windows users and provide equivalent commands for Linux/macOS users.
- Consider including a section or links for Linux-native management workflows, such as Bash scripts or usage with common Linux tools.
- Review the order of tool presentation to ensure cross-platform parity and avoid prioritizing Windows tools.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/schema-registry-dotnet-send-receive-quickstart.md
...hubs/schema-registry-dotnet-send-receive-quickstart.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias by exclusively referencing Windows tools (Visual Studio, Package Manager Console), providing only Windows-oriented instructions (e.g., Visual Studio UI steps, PowerShell/Install-Package commands), and omitting any Linux or cross-platform alternatives for project setup, dependency management, or authentication. There are no instructions for using .NET CLI, VS Code, or command-line workflows common on Linux/macOS, nor any mention of Linux-specific considerations.
Recommendations
- Add parallel instructions for Linux/macOS users, including how to create and manage .NET projects using the dotnet CLI (e.g., 'dotnet new console', 'dotnet add package').
- Include examples of installing dependencies using the dotnet CLI instead of only 'Install-Package' via Package Manager Console.
- Mention and provide steps for using cross-platform editors like VS Code, and clarify that Visual Studio is not required.
- Provide authentication guidance for non-Visual Studio environments (e.g., Azure CLI login, environment variables).
- Explicitly state that all code and tools are cross-platform, and note any platform-specific differences or requirements.
- Where screenshots or UI steps are given for Visual Studio, offer equivalent command-line or VS Code instructions.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/resource-governance-with-app-groups.md
...cles/event-hubs/resource-governance-with-app-groups.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell examples (a Windows-centric tool), listing PowerShell before CLI in several sections, and omitting any Linux-specific shell or scripting examples. There are no bash or Linux-native command examples, and the use of PowerShell is assumed as a primary automation tool. The CLI examples are present but are not explicitly shown in a Linux context, and there are no references to Linux tools or scripting patterns.
Recommendations
- Add explicit bash/Linux shell examples for all CLI commands, including sample scripts and environment variable usage.
- Clarify that Azure CLI commands work cross-platform and provide sample outputs from both Windows (CMD/PowerShell) and Linux (bash).
- Avoid listing PowerShell before CLI unless there is a technical reason; alternate the order or clarify parity.
- Include notes or sections on using these commands in Linux environments, including any differences in authentication, file paths, or environment setup.
- Where automation is discussed, provide both PowerShell and bash scripting examples to ensure Linux users are equally supported.
- Explicitly mention that PowerShell Core is cross-platform if recommending PowerShell, and provide Linux installation instructions if relevant.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/test-locally-with-event-hub-emulator.md
...les/event-hubs/test-locally-with-event-hub-emulator.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias by prioritizing Windows-specific instructions and tools, such as PowerShell and WSL, and by providing more detailed, step-by-step guidance for Windows users. Linux and macOS instructions are less detailed and often grouped together, with some steps (like directory navigation) omitted. There is also a focus on Docker Desktop, which is more common on Windows, and explicit notes about Windows path conventions, while Linux equivalents are not discussed.
Recommendations
- Provide equally detailed, step-by-step instructions for Linux and macOS users, including terminal commands for directory navigation and script execution.
- List Linux and macOS instructions before or alongside Windows instructions, rather than after.
- Include Linux-native Docker installation links and prerequisites, not just Docker Desktop (which is Windows/macOS-centric).
- Offer explicit examples of file path conventions for Linux/macOS in addition to Windows.
- Avoid requiring WSL for Windows users unless absolutely necessary, and clarify when native Linux/macOS environments are supported.
- Ensure that all scripts and commands are shown in both PowerShell (Windows) and Bash (Linux/macOS) formats where applicable.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/transport-layer-security-configure-client-version.md
...s/transport-layer-security-configure-client-version.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides only a .NET example for configuring TLS, which is most commonly associated with Windows environments, and references Fiddler—a Windows-centric tool—for verifying TLS versions. There are no examples or tool recommendations for Linux or cross-platform environments, and Windows tools are mentioned first and exclusively.
Recommendations
- Add examples for configuring TLS in client applications using common Linux-compatible languages and frameworks (e.g., Python, Java, Node.js).
- Include instructions or examples for verifying TLS versions using cross-platform or Linux-native tools such as Wireshark, tcpdump, or OpenSSL.
- When mentioning tools, provide both Windows and Linux alternatives, or recommend cross-platform tools first.
- Clarify that the .NET example is applicable on both Windows and Linux (if true), or provide equivalent Linux-specific guidance.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/transport-layer-security-configure-minimum-version.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/transport-layer-security-configure-minimum-version.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the section on checking the minimum required TLS version. It exclusively provides instructions and examples using ARMClient.exe (a Windows executable) and PowerShell commands for authentication, with no mention of Linux or cross-platform alternatives. There are no CLI, Bash, or platform-agnostic REST examples for obtaining the Bearer token or querying the API, which may hinder Linux or macOS users.
Recommendations
- Provide cross-platform instructions for obtaining a Bearer token, such as using Azure CLI (az account get-access-token) or curl commands.
- Include Bash or shell script examples alongside PowerShell/Windows-specific instructions.
- Mention and demonstrate the use of ARMClient alternatives or REST API calls that can be executed on any platform.
- Ensure that any tool or command referenced is available on both Windows and Linux, or provide equivalent alternatives for each platform.
- Explicitly state when a tool is Windows-only and offer a Linux/macOS-compatible workflow in parallel.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/troubleshooting-guide.md
...blob/main/articles/event-hubs/troubleshooting-guide.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing troubleshooting commands and tool recommendations that are Windows-centric (e.g., psping.exe, PowerShell commands), mentioning Windows tools first, and omitting explicit Linux equivalents or examples. While there is a brief mention of using 'wget' for connectivity checks, the majority of actionable examples and tool links are tailored to Windows users, with little guidance for Linux users.
Recommendations
- Provide equivalent Linux commands and tools alongside Windows examples (e.g., use 'nc' or 'nmap' for TCP connectivity tests on Linux, and show example commands).
- List cross-platform tools first, or present both Windows and Linux options together, rather than defaulting to Windows tools.
- Include explicit Linux shell command examples for tasks like checking connectivity, dropped packets, and network tracing.
- Mention and link to Linux-compatible tools (e.g., 'netcat', 'ss', 'tcpdump') where appropriate.
- Clarify that 'psping.exe' is Windows-only and suggest alternatives for Linux/Mac users.
- Ensure parity in troubleshooting steps and tool recommendations for both Windows and Linux environments.
Event Hubs
Geo-disaster recovery - Azure Event Hubs| Microsoft Docs
...ocs/blob/main/articles/event-hubs/event-hubs-geo-dr.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides platform-specific instructions for manual failover using Azure portal, Azure CLI, Azure PowerShell, and C#. While Azure CLI is cross-platform, PowerShell is Windows-centric and is listed before C#. No explicit Linux/macOS shell examples (e.g., Bash) are provided, and the ordering of examples tends to favor Windows tools first. There are screenshots of the Azure portal, which is platform-neutral, but no command-line examples for Linux/macOS users beyond Azure CLI.
Recommendations
- Ensure Azure CLI examples are clearly marked as cross-platform and provide Bash shell usage examples where relevant.
- List cross-platform tools (Azure CLI) before Windows-centric tools (PowerShell) in example sections.
- Add explicit notes or examples for Linux/macOS users, such as using Bash scripts or automation with Azure CLI.
- Consider including sample automation scripts for Linux environments, especially for failover scenarios.
- Clarify that PowerShell examples are primarily for Windows users and suggest alternatives for Linux/macOS.
Event Hubs
Geo-disaster recovery - Azure Event Hubs| Microsoft Docs
...ocs/blob/main/articles/event-hubs/event-hubs-geo-dr.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides platform-specific instructions for manual failover using Azure portal, Azure CLI, PowerShell, and C#. While the Azure CLI is cross-platform, PowerShell is Windows-centric and is listed as a primary method. The examples and screenshots focus on the Azure portal (which is web-based and cross-platform), but PowerShell is mentioned before C# and no explicit Linux/macOS shell examples (e.g., Bash) are provided. There is no mention of Linux-specific tools or patterns, and the CLI example is brief compared to the PowerShell and C# sections.
Recommendations
- Expand the Azure CLI section with a full example, including sample output and error handling, to match the detail of PowerShell and C#.
- Add explicit Bash/shell scripting examples for Linux/macOS users, demonstrating how to use the Azure CLI for failover and management tasks.
- Clarify that PowerShell Core is available cross-platform, or recommend Azure CLI as the preferred cross-platform automation tool.
- Ensure parity in example detail and troubleshooting guidance for CLI and non-Windows environments.
Event Hubs
Geo-disaster recovery - Azure Event Hubs| Microsoft Docs
...ocs/blob/main/articles/event-hubs/event-hubs-geo-dr.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides platform-specific instructions for manual failover using Azure portal, Azure CLI, PowerShell, and C#. While Azure CLI is cross-platform, PowerShell is Windows-centric and is listed before C# and after CLI. There are no explicit Linux/macOS shell examples (e.g., Bash), nor is there mention of Linux-specific tooling or patterns. The ordering of examples tends to favor Windows tools (PowerShell) and the Azure portal, which is most commonly accessed from Windows environments. No Linux/macOS-specific guidance or troubleshooting is provided.
Recommendations
- Add explicit Bash examples for manual failover using Azure CLI to demonstrate Linux/macOS usage.
- Clarify that Azure CLI commands work on Linux/macOS and provide sample shell scripts for automation.
- Reorder platform-specific sections so that cross-platform tools (CLI) are listed before Windows-centric ones (PowerShell).
- Include troubleshooting notes or tips for Linux/macOS users, if any platform-specific issues exist.
- Consider adding a short section or note confirming full parity of features and commands across Windows, Linux, and macOS.
Event Hubs
Test Applications Locally with the Azure Event Hubs Emulator
...les/event-hubs/test-locally-with-event-hub-emulator.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias, with Windows and PowerShell instructions presented before Linux/macOS equivalents. Windows-specific tooling (WSL, PowerShell) is emphasized, and Linux/macOS instructions are less detailed and appear after Windows steps. Some sections, such as the prerequisites and script execution, focus heavily on Windows environments and tools, with Linux/macOS guidance being brief or missing step-by-step detail.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions, not after.
- Provide equally detailed step-by-step instructions for Linux/macOS users, including terminal commands and environment setup.
- Avoid assuming Docker Desktop is the only Docker option; mention alternatives like Docker Engine for Linux.
- Remove or minimize Windows-specific notes unless absolutely necessary, or provide equivalent notes for Linux/macOS (e.g., file path conventions).
- Include explicit Linux/macOS examples for cloning repositories, running scripts, and configuring Docker.
- Clarify when steps are universal and when they are platform-specific, using tabs or clear sectioning.
Event Hubs
Configure the minimum TLS version for an Event Hubs namespace
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/transport-layer-security-configure-minimum-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation shows notable Windows bias in the section on checking the minimum TLS version, where only ARMClient.exe (a Windows tool) and PowerShell commands are provided for authentication. No Linux/macOS alternatives (such as Azure CLI, curl, or OpenSSL) are mentioned for acquiring a bearer token or querying the API, which may hinder non-Windows users.
Recommendations
- Provide equivalent instructions for Linux/macOS users, such as using Azure CLI (az account get-access-token) to obtain a bearer token.
- Include examples using curl or other cross-platform tools to query the Azure Resource Manager API.
- Mention ARMClient alternatives or clarify its platform support.
- Ensure that all code samples and instructions are platform-agnostic or offer both Windows and Linux/macOS options.
Event Hubs
Troubleshoot connectivity issues - Azure Event Hubs | Microsoft Docs
...blob/main/articles/event-hubs/troubleshooting-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation demonstrates a moderate Windows bias, particularly in the troubleshooting commands section. The primary example for checking dropped packets uses the Windows-only 'psping.exe' tool with a PowerShell-style invocation, and no direct Linux/macOS equivalent command is provided. While there is a brief mention that 'equivalent commands' can be used with other tools like 'tnc' and 'ping', no concrete Linux/macOS examples or tool recommendations are given. The rest of the documentation is largely platform-neutral, but the critical troubleshooting step is Windows-centric.
Recommendations
- Provide explicit Linux/macOS command-line examples for checking dropped packets (e.g., using 'nc', 'nmap', or 'telnet').
- Mention and link to cross-platform tools (e.g., 'nmap', 'netcat', 'curl') alongside Windows tools.
- Show both Windows and Linux/macOS commands side by side where relevant.
- Avoid using only PowerShell/Windows command syntax in examples; include Bash or shell equivalents.
- Clarify that 'psping.exe' is Windows-only and suggest alternatives for other platforms.
Event Hubs
Configure Transport Layer Security (TLS) for an Event Hubs client application
...s/transport-layer-security-configure-client-version.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation provides only a .NET example for configuring TLS, which is most commonly used on Windows. The verification step recommends Fiddler, a Windows-centric tool, without mentioning Linux/macOS alternatives. There are no examples or guidance for Linux/macOS users or for other programming languages/platforms commonly used on those systems.
Recommendations
- Add examples for configuring TLS in client applications on Linux/macOS, such as using Python, Java, or Node.js.
- Include instructions for verifying TLS versions using cross-platform tools like Wireshark or OpenSSL.
- Explicitly mention Linux/macOS support and any OS-specific considerations for TLS configuration.
- Present examples for multiple platforms side-by-side, or clearly indicate when instructions are Windows-specific.
Event Hubs
Authenticate an Application with Microsoft Entra ID to Access Event Hubs Resources
...b/main/articles/event-hubs/authenticate-application.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page primarily references the Azure portal and .NET samples, with no explicit mention of Linux/macOS-specific workflows, tools, or code examples. While Azure CLI is listed in related content, the main guidance and samples focus on Windows-centric technologies (Azure portal, .NET, screenshots from Windows UI), and there are no Linux/macOS terminal examples or references to cross-platform authentication flows. Linux users may need to infer how to adapt instructions for their environment.
Recommendations
- Include explicit Azure CLI and REST API step-by-step instructions for application registration, role assignment, and authentication, with example commands.
- Add code samples for Python and Node.js, which are popular on Linux/macOS, showing how to authenticate and access Event Hubs using Microsoft Entra ID.
- Provide screenshots or terminal output from Linux/macOS environments where relevant, or clarify that the steps are cross-platform.
- List CLI and REST API options before or alongside Azure portal instructions to signal parity.
- Reference open-source libraries and tools commonly used on Linux/macOS for authentication.
Event Hubs
SAS Authentication for Azure Event Hubs Resources
...les/event-hubs/authenticate-shared-access-signature.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides code samples for generating SAS tokens in multiple languages, including PowerShell and Bash. However, PowerShell (a Windows-centric tool) is given a dedicated section and full example, while Bash is included but with less explanation and context. The disabling of local/SAS key authentication is described only via the Azure portal (a GUI, typically Windows-centric) and ARM templates, with no mention of CLI alternatives like Azure CLI or direct Linux shell commands. The .NET sample references are also more likely to be Windows-oriented.
Recommendations
- Provide Azure CLI examples for disabling local/SAS key authentication, as CLI is cross-platform and widely used on Linux/macOS.
- Ensure Bash examples are as detailed and contextual as PowerShell ones, including usage notes and prerequisites.
- When listing code samples, alternate the order or explicitly state that all platforms are supported, rather than listing Windows/PowerShell first.
- Reference cross-platform SDK samples (e.g., Python, Go) and include links to Linux/macOS-specific guides if available.
- Mention that the Azure portal is accessible from any OS via browser, and offer alternatives for users who prefer command-line tools.
Event Hubs
Authorize access with shared access signatures
...event-hubs/authorize-access-shared-access-signature.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation mentions using PowerShell and Azure CLI for configuring SAS policies, but only explicitly lists PowerShell (a Windows-centric tool) and does not provide any Linux/macOS-specific examples or mention Bash, shell scripts, or cross-platform CLI usage. There are no explicit Linux/macOS instructions or examples, and Windows tools are referenced first and exclusively.
Recommendations
- Add explicit examples for configuring SAS policies using Azure CLI on Linux/macOS, including Bash syntax.
- When mentioning PowerShell, also mention Bash or shell alternatives for Linux/macOS users.
- Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux/macOS (Bash).
- Avoid referencing Windows tools exclusively; ensure parity by listing Linux/macOS equivalents alongside Windows options.
Event Hubs
Authorize Azure Event Hubs Access With Microsoft Entra ID
.../event-hubs/authorize-access-azure-active-directory.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page does not provide explicit Windows or PowerShell command examples, but all code samples and references are exclusively for .NET (C#) libraries, which are traditionally Windows-centric, and there are no Linux/macOS-specific instructions or examples. There is also no mention of cross-platform command-line tools (e.g., Azure CLI, Bash), nor are there any Linux-first or Linux-parity code samples. This creates a subtle bias by omission, as Linux/macOS users are not directly supported with examples or guidance.
Recommendations
- Add code samples and usage instructions for cross-platform SDKs such as Python, Java, or JavaScript, which are commonly used on Linux/macOS.
- Include Azure CLI examples for role assignment and authentication, showing both Windows (PowerShell/CMD) and Linux (Bash) syntax.
- Explicitly mention that the .NET SDK is cross-platform if applicable, and provide instructions for using it on Linux/macOS.
- Provide links to Linux/macOS-specific documentation or troubleshooting guides where relevant.
Event Hubs
Configure your own key for encrypting Azure Event Hubs data at rest
.../articles/event-hubs/configure-customer-managed-key.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing only PowerShell commands for critical deployment and configuration steps, with no Bash or cross-platform CLI alternatives shown. PowerShell is referenced as the default scripting environment for deploying ARM templates and managing access policies, which can create friction for Linux/macOS users who typically use Bash and the Azure CLI. While some CLI commands are mentioned for key vault creation, all automation and scripting examples for resource deployment and access policy management are PowerShell-only, and these appear before any mention of CLI alternatives.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell deployment and access policy steps, especially for ARM template deployments and key vault access policy management.
- Explicitly note that Azure CLI commands work cross-platform (Windows, Linux, macOS) and show Bash examples alongside PowerShell.
- Add tabs or callouts for both PowerShell and CLI/Bash for every example, ensuring Linux/macOS users can follow without switching environments.
- Clarify which commands are platform-specific and recommend the CLI for cross-platform scenarios.
Event Hubs
Dynamically add partitions to an event hub in Azure Event Hubs
...main/articles/event-hubs/dynamically-add-partitions.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. The PowerShell example is presented first, followed by the Azure CLI example. PowerShell is a Windows-centric tool, and its prominence may suggest Windows as the primary platform. There are no explicit Linux/macOS shell examples (e.g., Bash), nor are there instructions tailored for Linux environments. The CLI example is cross-platform, but the ordering and inclusion of PowerShell as the first method, as well as the lack of Linux-specific context, indicate a Windows-first approach.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that Azure CLI works on Linux/macOS and provide installation links or references.
- Include Bash or shell script examples where appropriate.
- Clarify platform compatibility for each method (e.g., 'PowerShell (Windows only)', 'Azure CLI (Windows, Linux, macOS)').
- Consider adding a table summarizing platform support for each method.
Event Hubs
Quickstart: Send or receive events using .NET
...ent-hubs/event-hubs-dotnet-standard-getstarted-send.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows and Visual Studio workflows. All project creation, package installation, and tooling instructions assume Visual Studio 2022 and the NuGet Package Manager Console (PowerShell), with no mention of cross-platform alternatives like .NET CLI or VS Code. There are no explicit instructions or examples for Linux/macOS users, and Windows-specific tools and UI steps are presented as the default and only option.
Recommendations
- Add .NET CLI commands (e.g., 'dotnet new console', 'dotnet add package ...') alongside or before Visual Studio instructions for project creation and package installation.
- Include guidance for using VS Code or other cross-platform editors, with relevant screenshots or steps.
- Explicitly state that the code samples and SDK work on Linux/macOS, and provide any necessary environment setup instructions for those platforms.
- Reorder instructions so that cross-platform methods (CLI) are presented first or in parallel tabs, not only after Windows/Visual Studio methods.
- Clarify that PowerShell/NuGet Package Manager Console is Windows-specific and provide Bash/zsh equivalents where appropriate.
Event Hubs
Geo-disaster recovery - Azure Event Hubs| Microsoft Docs
...ocs/blob/main/articles/event-hubs/event-hubs-geo-dr.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. In the 'Manual failover' section, PowerShell is given its own tab, and the C#/.NET example is highlighted with a direct code sample link, while Linux/macOS-specific tools or scripting languages (e.g., Bash, Python) are not mentioned. The Azure CLI example is present, which is cross-platform, but there are no explicit Linux/macOS shell examples or guidance. The order of examples (portal, CLI, PowerShell, C#) puts Windows-centric tools (PowerShell, C#) before Linux-native scripting options. There is no mention of Linux-specific tools or troubleshooting, and screenshots and instructions are focused on the Azure portal (which is platform-neutral), but the management and automation guidance leans toward Microsoft technologies.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users, especially for automation tasks.
- Include Python or other cross-platform SDK usage for failover and management operations.
- Reorder example tabs to present Azure CLI (cross-platform) before PowerShell and C#.
- Mention Linux/macOS compatibility and provide troubleshooting tips for those platforms.
- Ensure parity in code samples and links for both .NET and Java/Python SDKs.
Event Hubs
Management libraries - Azure Event Hubs| Microsoft Docs
...articles/event-hubs/event-hubs-management-libraries.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and patterns first (Azure PowerShell, Azure portal), and providing only .NET/C# sample code, which is most commonly used on Windows. There are no Linux/macOS-specific instructions, nor examples in cross-platform languages or tools. While Azure CLI is mentioned, it is listed after PowerShell and portal, and no CLI example is shown. The sample code is exclusively for .NET, with no mention of alternatives for Linux/macOS users.
Recommendations
- Provide explicit Linux/macOS instructions for prerequisites, such as using Azure CLI for service principal creation, and show CLI examples.
- Include sample code in cross-platform languages (e.g., Python, Java) that are commonly used on Linux/macOS.
- Clarify that the .NET libraries can be used on Linux/macOS via .NET Core, and provide guidance or links for setting up .NET on those platforms.
- Reorder prerequisite instructions to present cross-platform tools (Azure CLI) before Windows-centric ones (PowerShell, portal).
- Add a note or section on platform compatibility and any OS-specific considerations.
Event Hubs
Quickstart: Create an Azure event hub with consumer group
...ubs/event-hubs-resource-manager-namespace-event-hub.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page provides only Azure PowerShell examples for deploying, validating, and cleaning up resources, with no Azure CLI or Bash equivalents. This creates friction for Linux/macOS users, as PowerShell is not the default shell on these platforms. The instructions and code blocks are tailored to PowerShell, and there is no mention or prioritization of cross-platform tools like Azure CLI until the reference section, which is less discoverable. The order of presentation also puts Windows-centric tools first.
Recommendations
- Add equivalent Azure CLI examples for all deployment, validation, and cleanup steps, with Bash syntax where appropriate.
- Clearly indicate which examples are cross-platform and which are Windows-specific.
- Present Azure CLI/Bash examples before or alongside PowerShell examples to ensure parity.
- Explicitly mention that Cloud Shell supports both PowerShell and Bash, and provide guidance for both.
- Link to cross-platform resource management documentation more prominently in the main flow, not just in references.