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 26-50 of 211 flagged pages
Event Hubs Configure your own key for encrypting Azure Event Hubs data at rest .../articles/event-hubs/configure-customer-managed-key.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 Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is the only scripting example provided for deploying templates and managing access policies, with no Bash or Linux shell equivalents. All command-line instructions for resource deployment and access policy configuration use PowerShell, and the documentation refers to PowerShell before CLI in several places. There are no explicit Linux or Bash examples for key management, identity assignment, or template deployment, which may hinder Linux users or those using non-Windows environments.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all PowerShell examples, especially for template deployment and access policy management.
  • Include Bash shell script examples for template deployment and resource management, demonstrating cross-platform usage.
  • Clearly indicate which commands are platform-agnostic (e.g., Azure CLI) and which are Windows-specific (e.g., PowerShell), and recommend platform-agnostic tools where possible.
  • Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
  • Where PowerShell is referenced, offer links or inline examples for CLI/Bash alternatives, ensuring parity for Linux users.
GitHub Create Pull Request
Event Hubs Quickstart: Send or receive events using .NET ...ent-hubs/event-hubs-dotnet-standard-getstarted-send.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 demonstrates a Windows bias by exclusively referencing Windows tools (Visual Studio 2022), using Windows-centric UI instructions, and providing only PowerShell-based NuGet installation commands. There are no instructions or examples for Linux or cross-platform development environments (such as VS Code, JetBrains Rider, or CLI-based workflows). Linux users are not guided on how to install packages, create projects, or run the code outside of the Windows/Visual Studio ecosystem.
Recommendations
  • Add instructions for creating and managing .NET projects using the dotnet CLI, which works on Windows, Linux, and macOS.
  • Provide NuGet package installation commands using the dotnet CLI (e.g., 'dotnet add package ...') alongside PowerShell examples.
  • Include guidance for using cross-platform editors like VS Code, including relevant screenshots and steps.
  • Clarify that the code samples are platform-agnostic and can be run on Linux and macOS, not just Windows.
  • Mention prerequisites for Linux and macOS users, such as installing the .NET SDK and any required dependencies.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, environment variables for authentication).
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 (C#) for management library usage, referencing Windows-centric tools (PowerShell and Azure Portal) before mentioning Azure CLI, and providing no Linux-specific or cross-platform code samples. The sample code is written in C#, a language most commonly associated with Windows development environments, and there is no mention of Linux-compatible alternatives or instructions for running the sample on Linux. Additionally, the prerequisites section lists PowerShell before Azure CLI, which is more commonly used on Linux.
Recommendations
  • Provide equivalent sample code in a cross-platform language (e.g., Python, JavaScript) or clarify .NET Core compatibility on Linux.
  • Include explicit instructions and examples for running the management libraries on Linux (e.g., using .NET Core on Ubuntu).
  • List Azure CLI instructions before or alongside PowerShell, and clarify CLI usage on Linux.
  • Mention Linux-friendly authentication and environment setup steps (e.g., using environment variables, .NET Core installation on Linux).
  • Add links to Linux-specific documentation or troubleshooting guides for Event Hubs management libraries.
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 exhibits mild Windows bias. The only command-line example given is 'nslookup ns.servicebus.windows.net', which uses a Windows-centric namespace and does not mention Linux equivalents or provide Linux-specific instructions. Additionally, the Azure Resource Manager instructions mention PowerShell and the Azure CLI together, but PowerShell is listed explicitly, and Linux shell usage is not highlighted. There are no explicit Linux examples or references to Linux tools, and Windows terminology (e.g., '.windows.net') appears first and exclusively in examples.
Recommendations
  • Provide Linux-specific command-line examples alongside Windows ones (e.g., show 'nslookup' usage in bash/zsh, clarify that the command works on Linux/Mac as well).
  • When mentioning Azure Resource Manager access, explicitly list Linux shell/CLI usage (e.g., 'You can check this property in the portal, the Azure CLI, PowerShell, or Bash').
  • Use neutral namespace examples (e.g., 'ns.servicebus.azure.com') or clarify that '.windows.net' is used across platforms.
  • Add a note or section clarifying cross-platform compatibility for all tools and commands mentioned.
  • Ensure parity in instructions for both Windows and Linux users throughout the documentation.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell as a primary management option and providing explicit PowerShell cmdlet instructions, while omitting Linux-specific shell examples (such as Bash or scripting with az CLI on Linux). The ordering of management instructions places PowerShell before C# and after CLI, but does not provide parity for Linux-native tooling or scripting. There are no references to Linux tools, nor are there examples of using Bash scripts or Linux automation patterns for failover. The sample code and references are .NET and Java, but operational instructions are Windows-centric.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands, including sample scripts for automating failover on Linux.
  • Include instructions or references for using Azure CLI in Linux environments, such as cron jobs or systemd timers for monitoring and failover.
  • Provide parity in management instructions by listing CLI and Bash examples before or alongside PowerShell, not after.
  • Reference Linux automation tools (e.g., Ansible, shell scripts) for disaster recovery orchestration.
  • Clarify that Azure CLI is cross-platform and provide links to Linux installation and usage guides.
  • Include troubleshooting steps or considerations specific to Linux environments, such as permissions or networking differences.
GitHub Create Pull Request
Event Hubs Integrate Azure Event Hubs with Azure Private Link Service .../blob/main/articles/event-hubs/private-link-service.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 providing only Windows-centric examples and instructions. The only CLI example is in Azure PowerShell, with no Bash, Azure CLI, or Linux shell equivalents. The validation steps explicitly reference creating a Windows VM and running commands in its command line, without mentioning Linux VMs or alternative platforms. All screenshots and step-by-step instructions are tailored to the Azure portal UI, which is platform-agnostic, but the only OS-specific guidance is for Windows. There is no mention of Linux tools, patterns, or parity in the examples.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all resource creation and configuration steps.
  • Include instructions for creating and validating with a Linux VM, including relevant shell commands.
  • Provide Bash or cross-platform shell examples for DNS validation (e.g., nslookup, dig) on Linux.
  • Explicitly state that steps apply to both Windows and Linux unless there are platform-specific differences.
  • Add screenshots or notes for Linux VM creation in Azure portal, or link to Linux VM documentation.
  • Ensure parity in troubleshooting and validation steps for both Windows and Linux environments.
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 bias toward Windows and PowerShell environments. All command-line examples use Azure PowerShell, with no mention or example of Azure CLI (which is cross-platform and preferred on Linux/macOS). The instructions and code blocks assume the use of PowerShell, and there are no Bash or Linux-native shell examples. The validation and cleanup steps also rely exclusively on PowerShell commands. While the Azure Cloud Shell is cross-platform, the exclusive use of PowerShell commands and terminology (e.g., Write-Host, Read-Host) reinforces a Windows-centric approach. There is no guidance or parity for Linux users who may prefer Bash and Azure CLI.
Recommendations
  • Add equivalent Azure CLI (az) command 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.
  • Where PowerShell-specific commands are shown, offer side-by-side or tabbed examples for Bash/Azure CLI.
  • Review terminology and instructions to ensure they are not PowerShell- or Windows-specific (e.g., avoid Write-Host, Read-Host in Bash examples).
  • Include a note at the start of the 'Deploy the template' section indicating that both PowerShell and Bash/CLI options are available.
GitHub Create Pull Request
Event Hubs Secure Azure Event Hubs Using Virtual Network Integration ...in/articles/event-hubs/event-hubs-service-endpoints.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 demonstrates a Windows bias by listing Azure PowerShell instructions and references before or alongside Azure CLI, with explicit PowerShell command references and links. The 'Next steps' section links to PowerShell deployment instructions, and there are no Linux-specific examples, shell scripts, or references to Linux tools or workflows. The page does not provide parity for Linux users, such as Bash or cross-platform CLI walkthroughs, and omits any mention of Linux-specific considerations or troubleshooting.
Recommendations
  • Provide explicit Bash/Linux shell examples for Azure CLI commands, including step-by-step walkthroughs.
  • Ensure CLI instructions are listed before or at least equally with PowerShell, emphasizing cross-platform compatibility.
  • Add links to Linux deployment guides and troubleshooting resources.
  • Avoid referencing PowerShell-specific modules or instructions without also providing CLI or REST API alternatives.
  • Clarify that Azure CLI is cross-platform and suitable for Linux and macOS users.
  • Include notes or sections for Linux-specific networking considerations, such as firewall configuration or subnet setup.
GitHub Create Pull Request
Event Hubs Schema Registry in Azure Event Hubs ...b/main/articles/event-hubs/schema-registry-concepts.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 a mild Windows bias. It explicitly mentions PowerShell and provides a link to a PowerShell-based example for managing schema groups, while the only Linux-native tool referenced is Azure CLI. The PowerShell example is listed after Azure CLI, but there is no mention of Bash, shell scripts, or Linux-specific management patterns. There are no explicit Linux or Bash examples, and the management tooling references (PowerShell and Azure CLI) may implicitly favor Windows users.
Recommendations
  • Add explicit Bash or shell script examples for schema registry management tasks, such as adding schemas to schema groups.
  • Clarify that Azure CLI is cross-platform and provide usage instructions or examples for Linux/macOS terminals.
  • Include references to Linux-native tools or workflows (e.g., curl, REST API usage from Bash) for schema registry operations.
  • Ensure parity in example coverage by providing both Windows (PowerShell) and Linux (Bash/CLI) examples side-by-side where management tasks are demonstrated.
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 a Windows bias by presenting Windows-specific instructions and tools (PowerShell, WSL) before Linux/macOS equivalents, providing more detailed steps for Windows users, and referencing Windows-specific Docker Desktop installation and path conventions. Linux/macOS instructions are less detailed and appear after Windows steps. There are also notes and examples that specifically address Windows path formatting, but do not equivalently address Linux/macOS nuances.
Recommendations
  • Present Linux/macOS instructions alongside or before Windows instructions to avoid 'Windows first' ordering.
  • Provide equally detailed step-by-step instructions for Linux/macOS users, including terminal commands and environment setup.
  • Include Linux/macOS-specific Docker installation links and troubleshooting notes, not just Windows/WSL.
  • Add notes about Linux/macOS path conventions (e.g., forward slashes) where Windows path notes are given.
  • Avoid assuming PowerShell as the default shell; provide bash/zsh examples where applicable.
  • Where WSL is mentioned, clarify that it is only relevant for Windows users and provide native Linux/macOS alternatives.
  • Ensure all examples and screenshots are platform-neutral or provide platform-specific variants.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits Windows bias by providing only PowerShell/Windows command-line examples for acquiring a Bearer token (ARMClient.exe), referencing a Windows-specific tool (ARMClient.exe) without mentioning Linux/macOS alternatives, and omitting equivalent Linux commands or cross-platform instructions. No Linux-native CLI (e.g., curl, az CLI) or shell examples are provided for key steps, and Windows tooling is introduced first and exclusively.
Recommendations
  • Provide equivalent Linux/macOS instructions for acquiring a Bearer token, such as using Azure CLI (az account get-access-token) or curl.
  • Include cross-platform examples for querying the Azure Resource Manager API (e.g., using curl or httpie).
  • Mention and demonstrate how to perform the same operations on Linux and macOS, not just Windows.
  • Avoid referencing Windows-only tools (ARMClient.exe) as the sole method; offer alternatives or clarify platform compatibility.
  • Where scripts or commands are shown, present both PowerShell and Bash (or POSIX shell) versions side-by-side.
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 by exclusively providing a .NET example (commonly associated with Windows environments), referencing Fiddler (a Windows-only tool) for TLS verification, and omitting Linux-specific instructions or examples. There are no examples for Linux-based clients, nor are Linux-compatible tools mentioned for verifying TLS connections.
Recommendations
  • Add examples for configuring TLS in client applications commonly used on Linux, such as Python, Java, or Node.js.
  • Include instructions for verifying TLS connections using cross-platform or Linux-native tools, such as OpenSSL, Wireshark, or curl.
  • Present examples for both Windows and Linux platforms, or clarify platform-specific steps where necessary.
  • Avoid referencing Windows-only tools (like Fiddler) exclusively; suggest alternatives for other operating systems.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-ip-filtering.md ...ob/main/articles/event-hubs/event-hubs-ip-filtering.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions and code samples for configuring IP firewall rules using the Azure portal, Resource Manager templates, Azure CLI, and Azure PowerShell. However, the only explicit command-line example given is for Azure PowerShell, which is Windows-centric. The CLI section mentions the relevant az command group but does not provide any example usage, while the PowerShell section provides a full example script. There are no Linux-specific instructions, nor are cross-platform shell examples (e.g., Bash) provided. The PowerShell example appears before any CLI example, and the CLI section is less detailed.
Recommendations
  • Add explicit Azure CLI example commands for managing IP firewall rules, including add, list, update, and remove operations.
  • Provide Bash shell examples for Linux users, demonstrating how to use Azure CLI to accomplish the same tasks as the PowerShell example.
  • Ensure that CLI and PowerShell examples are presented with equal detail and prominence, ideally side-by-side or in parallel sections.
  • Clarify that Azure CLI is cross-platform and suitable for both Windows and Linux environments.
  • Consider adding a note or section on scripting these operations in Bash for automation on Linux systems.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-geo-dr.md ...ocs/blob/main/articles/event-hubs/event-hubs-geo-dr.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways. In the 'Manual failover' section, the Azure portal (GUI), Azure CLI, Azure PowerShell, and C# are presented as options. PowerShell (a Windows-centric tool) is given its own section, and C# (commonly associated with Windows development) is highlighted with sample code. There are no explicit Linux shell (bash) or scripting examples, nor are Linux-specific tools or workflows mentioned. The CLI example is present, but there is no demonstration of usage in a Linux environment, nor are Linux-specific considerations or parity discussed. The ordering of examples (portal, CLI, PowerShell, C#) also places Windows-centric tools before cross-platform or Linux-native approaches.
Recommendations
  • Add explicit bash/Linux shell examples for CLI commands, including sample output and error handling.
  • Include Linux-specific instructions or screenshots for Azure CLI usage, especially for failover operations.
  • Mention Linux-native automation tools (e.g., shell scripts, cron jobs) for automating failover.
  • Ensure parity by providing examples in Python or JavaScript (cross-platform languages) alongside C#.
  • Reorder the example sections to present CLI (cross-platform) before PowerShell (Windows-centric).
  • Explicitly state that all CLI commands work on Linux, macOS, and Windows, and provide troubleshooting tips for Linux users.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-resource-manager-namespace-event-hub.md ...ubs/event-hubs-resource-manager-namespace-event-hub.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias towards Windows and PowerShell environments. All command-line examples use Azure PowerShell, with no Azure CLI or Bash examples provided. This excludes native Linux shell usage and may hinder Linux/Mac users. The instructions and scripts assume familiarity with PowerShell, which is traditionally a Windows tool, despite its cross-platform availability. There is no mention or prioritization of Linux-specific workflows or tools.
Recommendations
  • Add equivalent Azure CLI examples for all deployment, validation, and cleanup steps, as Azure CLI is natively available on Linux and Mac.
  • Include Bash shell script samples alongside PowerShell, or clarify cross-platform compatibility of Cloud Shell.
  • Explicitly mention that Cloud Shell supports both Bash and PowerShell, and provide guidance for Linux users.
  • Reorder or balance examples so that Azure CLI/Bash instructions are presented before or alongside PowerShell, to avoid Windows-first perception.
  • Reference documentation for using ARM templates with Azure CLI and Bash, not just PowerShell.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
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 by exclusively providing a .NET example (primarily used on Windows), referencing the ServicePointManager API (Windows-centric), and recommending Fiddler (a Windows-only tool) for TLS verification. There are no examples or tool recommendations for Linux or cross-platform scenarios, nor is there mention of Linux-native verification methods.
Recommendations
  • Add examples for configuring TLS in client applications on Linux, such as using Python, Java, or Node.js SDKs.
  • Include instructions for verifying TLS versions using Linux-native tools, such as tcpdump, Wireshark, or OpenSSL.
  • Mention cross-platform alternatives to Fiddler, like Wireshark, and provide guidance for their use.
  • Clarify that the .NET example is applicable on both Windows and Linux (if true), or provide platform-specific notes.
  • Present examples for both Windows and Linux environments, or explicitly state platform requirements for each step.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by primarily referencing Windows-specific tools (e.g., psping.exe), providing command-line examples in Windows syntax (PowerShell/Command Prompt), and mentioning Windows tools before their Linux equivalents. There is a lack of explicit Linux command examples for troubleshooting connectivity, and Linux-native tools are only mentioned generically or as alternatives without concrete usage instructions.
Recommendations
  • Provide explicit Linux command examples for troubleshooting, such as using 'nc', 'telnet', or 'ss' for connectivity checks.
  • Include sample usage of Linux-native tools (e.g., 'ping', 'curl', 'wget', 'nc') alongside Windows tools, with equivalent command syntax.
  • When referencing downloadable tools, mention cross-platform alternatives (e.g., 'psping' for Windows, 'hping3' or 'nping' for Linux) and provide installation instructions.
  • Ensure that examples are presented for both Windows and Linux platforms, ideally side-by-side, to improve parity and accessibility for all users.
  • Avoid using Windows-specific paths or syntax (e.g., '.\psping.exe') without also showing the Linux equivalent.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/authenticate-shared-access-signature.md ...les/event-hubs/authenticate-shared-access-signature.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
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 full example, and the Bash example is present but less detailed and uses tools (jq, iconv) that may not be available by default on all Linux distributions. There is a slight Windows bias in the presence and completeness of PowerShell examples, and the use of .NET samples in the 'Samples' section, which are more Windows-oriented. The instructions for disabling local/SAS key authentication focus on the Azure portal (GUI, often used on Windows) and ARM templates, with no mention of CLI alternatives (e.g., Azure CLI or REST API), which are more commonly used on Linux.
Recommendations
  • Ensure Bash examples use only standard Linux utilities (avoid jq, iconv if possible, or provide installation instructions).
  • Provide Azure CLI examples for management tasks such as disabling local/SAS key authentication.
  • Include Linux-specific instructions or troubleshooting notes where relevant (e.g., file permissions, environment setup).
  • Balance PowerShell and Bash examples in terms of detail and completeness.
  • Add sample links for Java, Node.js, and other cross-platform SDKs alongside .NET in the 'Samples' section.
  • Explicitly mention cross-platform compatibility for all code samples and management instructions.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/authorize-access-shared-access-signature.md ...event-hubs/authorize-access-shared-access-signature.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by mentioning PowerShell and Azure CLI as tools for configuring SAS policies, but does not provide Linux-specific examples or mention Linux shell usage. PowerShell is referenced before Azure CLI, and there are no explicit Linux command-line or scripting examples, nor guidance for Linux users. This may make the documentation less accessible or immediately useful for users on Linux or macOS platforms.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and provide examples for both Windows (PowerShell) and Linux/macOS (Bash).
  • Include sample commands for creating and managing SAS policies using Bash or other Linux shells.
  • Clarify tool availability and usage on different operating systems, ensuring parity in instructions and examples.
  • Avoid listing Windows tools (PowerShell) before cross-platform tools (Azure CLI) unless contextually necessary; consider presenting Azure CLI first or in parallel.
  • Add a note or section addressing Linux/macOS users, with relevant tips or caveats.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/configure-customer-managed-key.md .../articles/event-hubs/configure-customer-managed-key.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily through the heavy use of PowerShell for command-line examples and deployment instructions. PowerShell commands are presented as the main or only method for key operations such as deploying Resource Manager templates, managing Key Vault access policies, and retrieving service principal IDs. While Azure CLI is mentioned for some Key Vault operations, it is not used for deployment or identity management examples. There are no explicit Linux shell (bash) or cross-platform CLI examples for template deployment or identity management, and PowerShell is referenced before Azure CLI in several places. This may disadvantage users on Linux or macOS who do not use PowerShell.
Recommendations
  • Provide Azure CLI (bash) equivalents for all PowerShell commands, especially for template deployment and identity management tasks.
  • Include explicit instructions and examples for Linux/macOS users, such as using Azure CLI in bash or sh.
  • Where both PowerShell and CLI are supported, present CLI examples first or side-by-side with PowerShell to avoid implicit prioritization of Windows tools.
  • Clarify that all operations can be performed from Linux/macOS using Azure CLI, and link to relevant cross-platform documentation.
  • Consider adding a section or tabbed examples for 'Windows (PowerShell)' and 'Linux/macOS (CLI)' to improve parity and accessibility.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/authorize-access-azure-active-directory.md .../event-hubs/authorize-access-azure-active-directory.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing .NET-based samples (DotNet/Microsoft.Azure.EventHubs and Azure.Messaging.EventHubs), which are primarily associated with Windows environments. There are no examples or explicit mentions of Linux tools, command-line patterns, or cross-platform SDKs (such as Python, Java, or CLI usage). The documentation does not provide parity for Linux users, nor does it mention Linux-specific authentication workflows or sample code.
Recommendations
  • Add sample code and walkthroughs for Linux environments, including usage with Python, Java, or Node.js SDKs.
  • Include command-line examples using Azure CLI or Bash scripts for role assignment and authentication, alongside any Powershell or Windows-centric instructions.
  • Reference cross-platform tools and libraries, and clarify that authentication and RBAC workflows are supported on Linux and macOS as well as Windows.
  • Provide links to Linux-specific tutorials or documentation, especially for Kafka clients and OAuth token acquisition on Linux.
  • Ensure that sample repositories include folders or instructions for non-Windows platforms, and highlight their usage in the documentation.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/configure-event-hub-properties.md .../articles/event-hubs/configure-event-hub-properties.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring Event Hub properties, but PowerShell (a Windows-centric tool) is given its own dedicated section and is mentioned before Linux-native alternatives like Bash scripting or REST API usage. There are no explicit Linux shell examples, and the PowerShell section is detailed, reinforcing a Windows bias. No Linux-specific tools or instructions are provided.
Recommendations
  • Add explicit Bash or shell script examples using Azure CLI to demonstrate usage on Linux/macOS.
  • Include REST API examples for cross-platform configuration.
  • Ensure that CLI examples are presented before PowerShell, or at least in parallel, to avoid Windows-first ordering.
  • Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Consider adding a table comparing available tools for different platforms.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/dynamically-add-partitions.md ...main/articles/event-hubs/dynamically-add-partitions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell as the first method for updating partition counts, referencing Windows-specific tools (PowerShell cmdlets and .NET SDKs), and mentioning WindowsAzure.ServiceBus. There is no explicit Linux shell (bash) example, and the CLI section, while cross-platform, is listed after PowerShell. The documentation does not provide parity for Linux users in terms of command-line examples or tool references.
Recommendations
  • Provide bash or shell script examples for updating partition counts, especially using Azure CLI, and explicitly mention that CLI works cross-platform.
  • List Azure CLI examples before PowerShell to emphasize cross-platform support.
  • Reference Linux-native tools or SDKs (e.g., Python, Java) where appropriate, especially in the Event Processor Host section.
  • Clarify that PowerShell is primarily for Windows and suggest alternatives for Linux/macOS users.
  • Add explicit instructions for Linux users, such as installation steps for Azure CLI and usage in bash/zsh environments.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-dotnet-standard-getstarted-send.md ...ent-hubs/event-hubs-dotnet-standard-getstarted-send.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All instructions for project creation, package installation, and tooling are centered around Visual Studio 2022 and the NuGet Package Manager Console (PowerShell-based), with no mention of cross-platform alternatives. There are no examples or instructions for Linux or macOS users, such as using the .NET CLI (dotnet commands) or VS Code. The documentation assumes the user is on Windows and using Visual Studio, omitting guidance for developers on other platforms.
Recommendations
  • Add parallel instructions for Linux and macOS users, including how to create and manage .NET projects using the dotnet CLI (e.g., 'dotnet new console', 'dotnet add package').
  • Include examples for installing NuGet packages via the command line (dotnet add package) instead of only via the Visual Studio Package Manager Console.
  • Mention and provide guidance for using cross-platform editors like Visual Studio Code, including how to open, build, and run .NET projects.
  • Clearly indicate that the steps are for Visual Studio on Windows, and provide alternative steps for users on other operating systems.
  • Where screenshots or UI steps are shown, offer equivalent command-line or VS Code workflows.
  • Explicitly state the OS-agnostic nature of .NET Core and encourage cross-platform usage.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-management-libraries.md ...articles/event-hubs/event-hubs-management-libraries.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by focusing exclusively on .NET (C#) management libraries, referencing Windows-centric tools (PowerShell) before Linux equivalents (Azure CLI), and omitting any Linux or cross-platform code samples. All sample code is in C#, with no mention of Linux-friendly SDKs or usage patterns, and the prerequisites section lists PowerShell before CLI, reinforcing a Windows-first approach.
Recommendations
  • Add equivalent code samples for Linux-friendly languages (e.g., Python, JavaScript) using Azure SDKs.
  • Provide explicit instructions and examples for using Azure CLI on Linux/macOS, and list CLI before PowerShell in prerequisites.
  • Mention cross-platform development environments and tools, such as VS Code, and clarify that .NET Core/.NET 6+ is cross-platform.
  • Include guidance on authenticating and managing Event Hubs from Linux systems, possibly with Bash scripts or Python samples.
  • Balance references to Windows and Linux tools throughout the documentation to ensure parity.
GitHub Create Pull Request
← Previous Page 2 of 9 Next →