Event Hubs

242
Total Pages
218
Linux-Friendly Pages
24
Pages with Bias
9.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

59 issues found
Showing 1-25 of 59 flagged pages
Event Hubs Dynamically add partitions to an event hub in Azure Event Hubs ...main/articles/event-hubs/dynamically-add-partitions.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by presenting PowerShell as the first method for updating partition count, using a Windows-specific tool (Set-AzEventHub), and referencing the old .NET SDK (WindowsAzure.ServiceBus) which is primarily Windows-focused. Although Azure CLI and Apache Kafka CLI examples are included, the ordering and emphasis favor Windows tools and patterns, with no explicit Linux shell or bash examples provided.
Recommendations
  • Reorder the update methods to present cross-platform tools (Azure CLI, Kafka CLI) before Windows-specific tools (PowerShell).
  • Add explicit bash/shell examples for Linux users, especially for Azure CLI and Kafka CLI commands.
  • Mention that Azure CLI and Kafka CLI are cross-platform and provide installation links for Linux/macOS.
  • Reference .NET Core SDKs or other cross-platform libraries instead of (or in addition to) the Windows-only .NET SDK.
  • Clarify that PowerShell Core is available on Linux/macOS, or provide equivalent bash scripts where possible.
GitHub Create Pull Request
Event Hubs SAS Authentication for Azure Event Hubs Resources ...les/event-hubs/authenticate-shared-access-signature.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides code examples for SAS token generation in multiple languages, including PowerShell and Bash. However, PowerShell (a Windows-centric tool) is given a full example and is listed before Bash, and the Bash example requires non-standard tools (jq, iconv) without guidance for Linux users. There is a strong presence of Windows-specific tooling (PowerShell, .NET, C#) and references to Windows patterns (HttpUtility, System.Web), while Linux-native approaches (Bash, openssl) are less detailed and may be harder for Linux users to follow. The ARM template and portal instructions are platform-neutral, but the overall example set and ordering show a Windows-first bias.
Recommendations
  • Provide Linux-native command-line examples (e.g., Bash) with clear instructions and alternatives for required tools (like jq, iconv), or use only POSIX-standard utilities.
  • List Bash examples before PowerShell to avoid implicit prioritization of Windows tools.
  • Add explicit notes on cross-platform compatibility for each code sample, especially for PowerShell and Bash.
  • Include more Linux-friendly programming language examples (e.g., Python) and clarify any platform-specific dependencies.
  • Where .NET or C# examples use Windows-specific libraries (e.g., System.Web), provide alternatives for Linux/Mono environments.
GitHub Create Pull Request
Event Hubs Azure Event Hubs Dedicated Tier Overview ...n/articles/event-hubs/event-hubs-dedicated-overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias in its operational instructions. For example, the 'Determine the cluster type' section provides a command-line example using nslookup with a Windows-style namespace (ns.servicebus.windows.net) and does not mention Linux equivalents or syntax. The instructions reference PowerShell as a tool for checking Azure Resource Manager properties, listing it alongside Azure CLI and the portal, but do not provide Linux-specific guidance or examples. No Linux shell commands (e.g., dig, host) are mentioned, and Windows-centric terminology (servicebus.windows.net) is used without clarifying cross-platform applicability.
Recommendations
  • Add Linux shell command equivalents (e.g., dig, host) alongside nslookup for cluster type determination.
  • Provide explicit Azure CLI examples for resource property checks, and clarify that PowerShell is optional for Windows users.
  • Use neutral terminology for namespaces and endpoints, or clarify that servicebus.windows.net is platform-agnostic.
  • Ensure all operational instructions and examples are presented for both Windows and Linux environments, or indicate platform-specific steps where necessary.
GitHub Create Pull Request
Event Hubs Management libraries - Azure Event Hubs| Microsoft Docs ...articles/event-hubs/event-hubs-management-libraries.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on .NET and C# code samples, referencing Windows-centric tools and workflows (such as PowerShell and Azure Portal tutorials before CLI), and omitting Linux-specific examples or cross-platform alternatives. The prerequisites and sample code are tailored to Windows environments, with no mention of Linux or other platforms, and the management library showcased is only available for .NET, which is traditionally Windows-focused.
Recommendations
  • Include equivalent examples using cross-platform languages (e.g., Python, Java) and SDKs where available.
  • Provide Linux-specific instructions for authentication and environment setup, such as using Azure CLI or bash scripts.
  • Reference Azure CLI tutorials before or alongside PowerShell and Portal instructions to ensure parity.
  • Clarify platform compatibility for the management libraries and suggest alternatives for non-Windows users.
  • Add notes or sections explicitly addressing Linux/macOS usage, including sample code and troubleshooting tips.
GitHub Create Pull Request
Event Hubs Quickstart: Create an Azure event hub with consumer group ...ubs/event-hubs-resource-manager-namespace-event-hub.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples for deploying, validating, and cleaning up Event Hub resources. There are no Azure CLI or Bash examples, which are more common on Linux and macOS. The instructions and code blocks assume the use of PowerShell, which is native to Windows, and do not mention or prioritize cross-platform alternatives. References to Azure CLI are only present in the link section, not in the main workflow.
Recommendations
  • Add equivalent Azure CLI examples for all deployment, validation, and cleanup steps, using Bash syntax.
  • Explicitly mention that Azure Cloud Shell supports both PowerShell and Bash, and provide instructions for both.
  • Reorder or parallelize examples so that CLI/Bash instructions appear alongside PowerShell, rather than only after or not at all.
  • Ensure that tool references and screenshots are platform-neutral or include both Windows and Linux/macOS variants.
  • Review and update language to avoid implying PowerShell is the default or only supported method.
GitHub Create Pull Request
Event Hubs Test Applications Locally with the Azure Event Hubs Emulator ...les/event-hubs/test-locally-with-event-hub-emulator.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by presenting Windows-specific instructions (PowerShell, WSL) before Linux/macOS equivalents, referencing Windows tools (WSL, Docker Desktop for Windows) and providing more detailed step-by-step guidance for Windows users. Linux/macOS instructions are less detailed and lack parity in example commands and troubleshooting notes. Additionally, file path conventions and environment setup tips are Windows-centric.
Recommendations
  • Provide equally detailed step-by-step instructions for Linux and macOS, including terminal commands and troubleshooting tips.
  • Include explicit Linux/macOS examples for cloning repositories, navigating directories, and running scripts.
  • Mention Linux-native Docker installation and usage before or alongside Windows-specific instructions.
  • Add notes on Linux/macOS file path conventions and environment variable usage.
  • Balance the order of presentation so that Linux/macOS instructions are not always secondary to Windows.
  • Avoid referencing Windows tools (WSL, PowerShell) in generic sections; move them to OS-specific tabs or subsections.
  • Ensure all examples (e.g., running scripts, configuring Docker) are shown for both Windows and Linux/macOS.
GitHub Create Pull Request
Event Hubs Configure Transport Layer Security (TLS) for an Event Hubs client application ...s/transport-layer-security-configure-client-version.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates bias towards Windows environments by providing only .NET (typically Windows-centric) code samples, referencing Fiddler (a Windows-only tool) for TLS verification, and omitting any Linux-specific instructions, tools, or code examples. There are no examples for Linux platforms, nor are cross-platform or Linux-native tools mentioned for verifying TLS connections.
Recommendations
  • Add examples for configuring TLS in client applications running on Linux, such as using Python, Java, or .NET Core on Linux.
  • Include instructions for verifying TLS connections using cross-platform or Linux-native tools like tcpdump, Wireshark, or OpenSSL.
  • Mention platform-specific considerations for TLS support, such as differences in .NET Framework vs .NET Core/Mono on Linux.
  • Present verification tools in parallel (e.g., 'On Windows, use Fiddler; on Linux, use Wireshark or OpenSSL') rather than referencing only Windows tools.
  • Ensure that code samples and instructions are clearly marked as platform-specific where applicable, and provide parity for major platforms.
GitHub Create Pull Request
Event Hubs Troubleshoot connectivity issues - Azure Event Hubs | Microsoft Docs ...blob/main/articles/event-hubs/troubleshooting-guide.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by prioritizing Windows-specific tools (e.g., psping.exe), referencing PowerShell/Windows CLI usage, and not providing equivalent Linux commands or examples. Windows tools are mentioned first and in detail, while Linux alternatives are only briefly referenced or omitted.
Recommendations
  • Provide explicit Linux command examples for connectivity checks, such as using 'nc', 'telnet', or 'ss' for port testing.
  • Include installation instructions and usage for Linux-native tools alongside Windows tools (e.g., show how to use 'nc <hostname> <port>' or 'timeout 1 bash -c "echo > /dev/tcp/<hostname>/<port>"').
  • List cross-platform tools (e.g., Wireshark) with platform-specific installation notes.
  • When referencing CLI, clarify if commands work on both Windows and Linux, and provide syntax for both where they differ.
  • Avoid mentioning Windows tools first; present Windows and Linux options side-by-side to ensure parity.
GitHub Create Pull Request
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 →
Scanned: 2026-01-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides platform-specific instructions for manual failover using Azure portal, CLI, PowerShell, and C#. While the Azure CLI is cross-platform, PowerShell and C# are Windows-centric and are listed before Linux-native options (such as Bash scripting or REST API usage). There are no explicit Linux/macOS examples, and no mention of Linux tools or workflows. The sample code references are .NET/C# and Java, but operational examples (e.g., scripting failover) are Windows-first.
Recommendations
  • Add explicit Linux/macOS examples for scripting failover, such as using Bash with Azure CLI or REST API.
  • Clarify that Azure CLI commands work on Linux/macOS and provide sample Bash scripts.
  • Include REST API examples for failover operations, which are platform-neutral.
  • Balance the order of examples so that cross-platform tools (CLI, REST API) are shown before Windows-centric tools (PowerShell, C#).
  • Reference Linux/macOS automation scenarios in the 'Manual failover' section.
GitHub Create Pull Request
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 →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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#. There are no explicit Linux/macOS shell examples (e.g., Bash scripts), and the order of examples tends to favor Windows tools first. No Linux-specific guidance or parity is provided for scripting or automation beyond CLI.
Recommendations
  • Add explicit Bash/shell scripting examples for Linux/macOS users, especially for automation scenarios.
  • Clarify that Azure CLI commands work on Linux/macOS and provide example usage in those environments.
  • Reorder sections so that cross-platform tools (Azure CLI) are listed before Windows-centric tools (PowerShell).
  • Include notes or links to Linux/macOS prerequisites for CLI usage, if relevant.
  • Provide parity in sample code for other languages/platforms (e.g., Python, JavaScript) if possible.
GitHub Create Pull Request
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 →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides platform-specific instructions for manual failover, listing Azure portal, Azure CLI, PowerShell, and C# methods. PowerShell is highlighted as a distinct option, and C#/.NET samples are referenced. While Azure CLI is cross-platform, there are no explicit Linux/macOS shell examples (e.g., Bash), nor are there references to Linux-specific tooling or workflows. Windows/PowerShell options are presented before Linux-native alternatives, and the sample code is .NET-focused.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users, especially for CLI usage.
  • Clarify that Azure CLI commands work on Linux/macOS and provide sample terminal commands.
  • Include references or samples for other languages/platforms (e.g., Python, JavaScript) if available.
  • Ensure that instructions do not assume use of PowerShell or Windows-only tooling.
  • Consider listing cross-platform options (CLI) before Windows-specific ones (PowerShell).
GitHub Create Pull Request
Event Hubs Integrate Azure Event Hubs with Azure Private Link Service .../blob/main/articles/event-hubs/private-link-service.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples for creating and managing private endpoints use Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples provided. The validation section instructs users to create a Windows VM and does not mention Linux VM creation or validation steps. Windows tools and workflows are referenced exclusively or before any Linux alternatives, making it harder for Linux/macOS users to follow along.
Recommendations
  • Add Azure CLI and Bash examples for all PowerShell-based instructions, especially for creating private endpoints and configuring DNS zones.
  • Include instructions and screenshots for creating and validating with a Linux VM, alongside the Windows VM example.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant cross-platform documentation.
  • Where possible, use neutral, cross-platform terminology and tools (e.g., 'command line' instead of 'PowerShell').
GitHub Create Pull Request
Event Hubs Authorize access with shared access signatures ...event-hubs/authorize-access-shared-access-signature.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions using PowerShell and Azure CLI for managing authorization policies, but only explicitly names PowerShell (a Windows-centric tool) and does not provide Linux/macOS-specific examples or mention Bash or shell scripting. There is a lack of parity in tool references and example coverage for non-Windows platforms.
Recommendations
  • Explicitly mention and provide examples for Linux/macOS users, such as using Azure CLI in Bash or shell environments.
  • Avoid referencing PowerShell exclusively; if PowerShell is mentioned, also include equivalent Bash or shell commands.
  • Add a section or note clarifying cross-platform support for all management operations.
  • Ensure that any instructions or examples are available for both Windows and Linux/macOS users.
GitHub Create Pull Request
Event Hubs Management libraries - Azure Event Hubs| Microsoft Docs ...articles/event-hubs/event-hubs-management-libraries.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by listing Windows-centric tools (Azure Portal, Azure PowerShell) before cross-platform options (Azure CLI) in the prerequisites section. The sample code and all instructions are focused exclusively on .NET/C#, with no mention of Linux/macOS-specific considerations or alternative SDKs/languages. There are no examples or guidance for Linux/macOS users, nor any discussion of platform-specific differences.
Recommendations
  • Reorder prerequisite links to present Azure CLI (cross-platform) before Azure PowerShell and Azure Portal.
  • Explicitly state that the .NET SDK and sample code are cross-platform and can run on Linux/macOS as well as Windows.
  • Add notes or examples for authenticating and running the sample code on Linux/macOS, including any required dependencies or environment setup.
  • Provide links or references to equivalent management libraries or samples in other languages (e.g., Python, Java) that may be more commonly used on Linux/macOS.
  • Clarify any platform-specific limitations or considerations, if applicable.
GitHub Create Pull Request
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 →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides command-line examples only for Windows (PowerShell) and references a Windows-specific tool (ARMClient.exe) for obtaining a Bearer token. There are no equivalent instructions or examples for Linux/macOS users, nor are cross-platform alternatives mentioned. This creates friction for non-Windows users attempting to follow the steps.
Recommendations
  • Include instructions for obtaining a Bearer token using cross-platform tools such as Azure CLI (az), curl, or other REST clients available on Linux/macOS.
  • Provide example commands for Linux/macOS environments, e.g., using bash or zsh.
  • Mention and demonstrate cross-platform alternatives to ARMClient.exe, such as Azure CLI or direct REST API calls.
  • Ensure that any referenced tooling is available on all major platforms, or provide platform-specific guidance.
GitHub Create Pull Request
Event Hubs Authorize Azure Event Hubs Access With Microsoft Entra ID .../event-hubs/authorize-access-azure-active-directory.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias toward Windows by exclusively referencing .NET-based samples (Microsoft.Azure.EventHubs and Azure.Messaging.EventHubs), which are primarily used on Windows. There are no Linux/macOS-specific code samples, nor are cross-platform CLI examples (such as Bash, Azure CLI, or Python) provided. The documentation does not mention Linux tools or patterns and lists Windows-centric samples first.
Recommendations
  • Add cross-platform code samples using languages and SDKs popular on Linux/macOS (e.g., Python, Java, Node.js).
  • Include Azure CLI and Bash examples for role assignment and authentication flows.
  • Reference platform-agnostic tools and libraries, and clarify that the process applies equally to Linux/macOS environments.
  • Provide links to Linux/macOS-specific documentation or guides where available.
  • Explicitly mention that the .NET samples can be run on Linux/macOS using .NET Core, if applicable.
GitHub Create Pull Request
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 →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by relying heavily on PowerShell for command-line examples, especially for critical deployment and access policy steps. There are no Bash or Linux/macOS-specific CLI examples for these tasks, and PowerShell commands are presented as the primary or only method for several operations. While Azure CLI is mentioned for some key vault operations, PowerShell is used exclusively for template deployments and access policy configuration, which may create friction for Linux/macOS users.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all PowerShell examples, especially for resource group deployments and key vault access policy configuration.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Where possible, reorder examples to show Azure CLI first or side-by-side with PowerShell.
  • Add notes or links to official documentation for using Azure CLI on Linux/macOS.
  • Consider adding REST API or ARM template deployment examples for users who prefer not to use PowerShell.
GitHub Create Pull Request
Event Hubs Configure IP Firewall Rules for Azure Event Hubs Namespaces ...ob/main/articles/event-hubs/event-hubs-ip-filtering.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for configuring IP firewall rules, but does not offer equivalent Linux/macOS shell examples. The Azure CLI is mentioned briefly, but no concrete CLI command examples are given. PowerShell is presented with a full example, which may create friction for Linux/macOS users who do not use PowerShell. The order of presentation also places PowerShell after CLI, but CLI coverage is minimal.
Recommendations
  • Add explicit Azure CLI command examples for all major tasks, including adding, listing, updating, and removing IP firewall rules.
  • Ensure that CLI examples use bash syntax and are tested on Linux/macOS.
  • Where PowerShell is used, offer equivalent bash/CLI examples side-by-side.
  • Clarify that PowerShell commands can be run on Linux/macOS, but CLI is the preferred cross-platform tool.
  • Consider reordering sections so that CLI and bash examples appear before or alongside PowerShell.
GitHub Create Pull Request
Event Hubs Azure Event Hubs - exceptions (legacy) ...articles/event-hubs/event-hubs-messaging-exceptions.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on .NET Framework APIs and exception types, with all examples and references tailored to .NET and Microsoft.ServiceBus namespaces. There is no mention of Linux/macOS-specific patterns, alternative SDKs, or cross-platform usage. The guidance assumes users are working in a Windows/.NET environment, which may create friction for Linux/macOS users or those using other languages.
Recommendations
  • Add equivalent documentation for other supported SDKs (e.g., Java, Python, Node.js) that are commonly used on Linux/macOS.
  • Include examples and exception handling patterns for cross-platform environments, not just .NET.
  • Clarify which exceptions and troubleshooting steps apply regardless of OS, and note any platform-specific differences.
  • Provide links or references to Linux/macOS-specific troubleshooting guides or tools where relevant.
GitHub Create Pull Request
Event Hubs Quickstart: Send or receive events using .NET ...ent-hubs/event-hubs-dotnet-standard-getstarted-send.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
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 instructions for creating projects, managing NuGet packages, and running commands are based on Visual Studio GUI and PowerShell/Package Manager Console, with no mention of Linux/macOS equivalents (e.g., dotnet CLI, VS Code, or terminal commands). There are no examples or guidance for Linux/macOS users on how to perform these steps, which may cause confusion or friction for non-Windows developers.
Recommendations
  • Add equivalent instructions for Linux/macOS users, such as using the dotnet CLI (e.g., 'dotnet new console', 'dotnet add package ...') for project creation and package management.
  • Include guidance for using VS Code or other cross-platform editors, not just Visual Studio.
  • Explicitly state that the .NET SDK and Azure libraries are cross-platform and provide links or steps for installing and running on Linux/macOS.
  • Where PowerShell or Visual Studio steps are given, provide parallel steps for Bash/zsh and CLI usage.
  • Add screenshots or terminal output examples for Linux/macOS environments.
GitHub Create Pull Request
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 →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides platform-specific instructions for manual failover using Azure portal, CLI, PowerShell, and C#. However, PowerShell (a Windows-centric tool) is given its own section, and there is no mention of Bash, shell scripting, or Linux/macOS-specific patterns. The CLI example is present, but the ordering and emphasis on PowerShell and C# (both more common on Windows) suggest a Windows-first bias. There are no explicit Linux/macOS shell examples, nor are there troubleshooting notes for non-Windows environments.
Recommendations
  • Add explicit Bash/shell script examples for Linux/macOS users, especially for CLI operations.
  • Include notes or troubleshooting tips for Linux/macOS environments, such as authentication or environment variable differences.
  • Reorder platform instructions so that cross-platform tools (CLI) are presented before Windows-specific tools (PowerShell).
  • Mention that Azure CLI is cross-platform and highlight its use for Linux/macOS users.
  • If relevant, provide sample code in Python or other languages popular on Linux/macOS.
GitHub Create Pull Request
Event Hubs Quickstart: Create an Azure event hub with consumer group ...ubs/event-hubs-resource-manager-namespace-event-hub.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively provides Azure PowerShell examples for deploying, validating, and cleaning up Event Hub resources. There are no Azure CLI or Bash examples, which are preferred by many Linux and macOS users. The use of PowerShell commands and terminology throughout the page creates friction for users on non-Windows platforms, despite Azure Cloud Shell supporting Bash and CLI. References to Azure CLI are only present in the link section, not in the main workflow.
Recommendations
  • Add equivalent Azure CLI examples for all deployment, validation, and cleanup steps.
  • Show both PowerShell and CLI/Bash code blocks side-by-side, or allow users to toggle between them.
  • Explicitly mention that Azure Cloud Shell supports Bash and CLI, and provide instructions for those shells.
  • Ensure that Linux/macOS users can follow the quickstart without needing to use PowerShell.
GitHub Create Pull Request
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 →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows prerequisites (Docker Desktop, WSL) are listed first and in detail, with direct links to Windows-specific installation guides. The step-by-step instructions for running the emulator via script are Windows-centric: the Windows section is presented first, uses PowerShell, and requires WSL, while Linux/macOS instructions are brief and lack command-line detail. There are multiple references to Windows-specific tooling and patterns (PowerShell, WSL, Docker Desktop), and file path guidance is Windows-oriented. Linux/macOS users receive less detailed guidance and fewer examples.
Recommendations
  • Provide Linux/macOS prerequisites and installation links alongside Windows, not after.
  • Offer detailed, step-by-step Linux/macOS instructions for running scripts (e.g., terminal commands, navigation, permissions).
  • Present Linux/macOS examples before or alongside Windows examples, not after.
  • Include notes on file path conventions for Linux/macOS (forward slashes) as well as Windows.
  • Avoid assuming Docker Desktop is the only Docker option; mention Docker Engine for Linux.
  • Balance example code blocks between PowerShell and bash/zsh.
  • Clarify any differences in environment setup for Linux/macOS users.
GitHub Create Pull Request
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 →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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. For verifying TLS, it exclusively recommends Fiddler, a Windows-only tool, without mentioning Linux/macOS alternatives. There are no examples or guidance for Linux/macOS users or for other programming languages/platforms common on those systems.
Recommendations
  • Include examples for configuring TLS in client applications written in languages commonly used on Linux/macOS (e.g., Python, Java, Node.js).
  • Provide instructions for verifying TLS using cross-platform tools such as Wireshark, tcpdump, or OpenSSL.
  • Explicitly mention platform differences and provide parity in guidance for Linux/macOS users.
  • If using .NET, clarify how to set TLS versions on .NET Core/.NET 5+ on Linux/macOS.
GitHub Create Pull Request
Event Hubs Troubleshoot connectivity issues - Azure Event Hubs | Microsoft Docs ...blob/main/articles/event-hubs/troubleshooting-guide.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the troubleshooting steps for Azure Event Hubs connectivity. The main example for checking dropped packets uses the Windows-only 'psping.exe' tool, with no explicit Linux/macOS equivalent provided. References to PowerShell and Windows tools appear before mentioning alternatives, and Linux/macOS users are left to infer their own solutions. The lack of direct Linux/macOS command examples and tool recommendations creates friction for non-Windows users.
Recommendations
  • Provide explicit Linux/macOS command examples for troubleshooting steps (e.g., use 'nc', 'nmap', or 'hping3' for dropped packet checks).
  • List cross-platform tools first, or in parallel, rather than Windows-only tools.
  • Include sample commands for Linux/macOS in all sections where Windows tools are referenced.
  • Clarify that 'psping.exe' is Windows-only and suggest alternatives for other platforms.
  • Ensure parity in troubleshooting guidance for all major operating systems.
GitHub Create Pull Request
← Previous Page 1 of 3 Next →