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 51-59 of 59 flagged pages
Event Hubs Secure Azure Event Hubs Using Virtual Network Integration ...in/articles/event-hubs/event-hubs-service-endpoints.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents Azure PowerShell usage in a dedicated section and references PowerShell deployment instructions before Linux alternatives. While Azure CLI is mentioned, PowerShell commands and links are given more detail and prominence. There are no explicit Linux/macOS-specific examples, and the deployment instructions link to PowerShell documentation first. However, the core instructions are platform-neutral (portal, ARM templates, REST API, CLI), so Linux/macOS users can complete the tasks, but may experience minor friction.
Recommendations
  • Provide explicit Azure CLI command examples for all operations currently shown with PowerShell.
  • Ensure deployment instructions link to both PowerShell and CLI documentation, with equal prominence.
  • Add notes clarifying that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Consider listing CLI instructions before PowerShell, or side-by-side, to avoid Windows-first perception.
GitHub Create Pull Request
Event Hubs Schema Registry in Azure Event Hubs ...b/main/articles/event-hubs/schema-registry-concepts.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation references both Azure CLI and PowerShell for schema registry management, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is mentioned directly after CLI. There are no explicit Linux shell (bash) or macOS-specific examples, and no mention of Linux-native management tools. The PowerShell sample is highlighted as a primary method, which may suggest a Windows bias. However, the SDK and code samples are cross-platform, and Azure CLI is available on Linux/macOS.
Recommendations
  • Add explicit bash or shell examples for schema registry management, especially for Linux/macOS users.
  • Clarify that Azure CLI is cross-platform and can be used on Linux/macOS, and consider listing CLI before PowerShell.
  • If possible, provide links to Linux/macOS-specific instructions or samples for schema registry operations.
  • Note any platform limitations for PowerShell and encourage use of CLI for non-Windows environments.
GitHub Create Pull Request
Event Hubs Azure Event Hubs - Client SDKs | Microsoft Docs ...tDocs/azure-docs/blob/main/articles/event-hubs/sdks.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page shows mild Windows bias, mainly in the .NET section. It highlights Windows-specific libraries (e.g., WindowsAzure.ServiceBus) and legacy .NET Framework support, and lists .NET packages and management libraries before other platforms. However, the main SDK table includes cross-platform options for Java, Python, JavaScript, Go, and C, and does not provide command-line or PowerShell-only examples.
Recommendations
  • Clarify cross-platform compatibility for .NET Standard libraries, explicitly mentioning Linux/macOS support.
  • Avoid highlighting Windows-only libraries (e.g., WindowsAzure.ServiceBus) without noting their platform limitations.
  • Add a section or callout summarizing Linux/macOS usage and any platform-specific caveats.
  • Ensure that examples and tutorials linked from the page include Linux/macOS instructions where relevant.
GitHub Create Pull Request
Event Hubs Authenticate an Application with Microsoft Entra ID to Access Event Hubs Resources ...b/main/articles/event-hubs/authenticate-application.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing the Azure portal (web UI, which is platform-neutral but often associated with Windows workflows) and providing .NET (Windows-centric) and Java sample links, but does not offer explicit Linux/macOS command-line examples or highlight cross-platform tools for authentication and role assignment. The 'Samples' section prioritizes .NET, and the Azure CLI is mentioned after PowerShell in the 'Related content' section, with no direct Linux/macOS workflow guidance. No PowerShell-heavy or exclusive Windows tool usage is present, but Linux parity is not fully addressed.
Recommendations
  • Add explicit Linux/macOS command-line examples for authentication and role assignment using Azure CLI.
  • Provide sample code and walkthroughs for Python (cross-platform) and other languages commonly used on Linux/macOS.
  • Ensure Azure CLI instructions are presented before or alongside PowerShell, emphasizing cross-platform compatibility.
  • Clarify that all steps can be completed on Linux/macOS, and link to relevant platform-specific guides where available.
  • Include screenshots or terminal output from Linux/macOS environments where appropriate.
GitHub Create Pull Request
Event Hubs SAS Authentication for Azure Event Hubs Resources ...les/event-hubs/authenticate-shared-access-signature.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides code examples for generating SAS tokens in multiple languages (NodeJS, Java, PHP, C#, PowerShell, Bash). While Bash is included for Linux users, PowerShell is presented before Bash, and there is a notable presence of PowerShell and C# examples, which are traditionally Windows-centric. There are no explicit references to Windows-only tools, but the ordering and prominence of PowerShell and C# may subtly favor Windows users. The ARM template and portal instructions are platform-neutral, but the sample links are .NET-focused.
Recommendations
  • Present Bash/Linux examples before PowerShell to improve visibility for Linux users.
  • Include sample links for Java, NodeJS, and Bash/Linux implementations, not just .NET.
  • Add explicit notes clarifying that Bash examples are suitable for Linux/macOS environments.
  • Consider providing CLI (az) examples for disabling SAS key authentication, as the Azure CLI is cross-platform.
  • Balance language and tool coverage so that Linux/macOS users see their options as first-class citizens.
GitHub Create Pull Request
Event Hubs Configure properties for an Azure event hub .../articles/event-hubs/configure-event-hub-properties.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for configuring Event Hub properties, but the PowerShell section is given equal prominence to the CLI, despite PowerShell being primarily a Windows tool. There are no explicit Linux/macOS-specific examples or notes, and the ordering of examples (CLI first, then PowerShell) is reasonable. However, the PowerShell section may imply a Windows-centric approach, and there are no Bash or Linux shell script examples for automation.
Recommendations
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS as well as Windows.
  • Add explicit Bash or shell script examples for Linux/macOS users, especially for common configuration tasks.
  • Note that PowerShell Core is available cross-platform, but most Linux users prefer Bash/CLI.
  • Consider reordering or grouping examples by platform, or explicitly stating platform compatibility for each tool.
GitHub Create Pull Request
Event Hubs Quickstart: Create an event hub with consumer group using Bicep - Azure Event Hubs ...les/event-hubs/event-hubs-bicep-namespace-event-hub.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, validation, and cleanup tasks. However, PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. The order of presentation sometimes places PowerShell before or alongside CLI, which may subtly prioritize Windows workflows. There are also references to PowerShell-specific media files and links, reinforcing the Windows association. No Linux-specific tools or shell examples (e.g., Bash) are provided, but the use of Azure CLI ensures Linux/macOS users can complete all tasks.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform.
  • Explicitly mention that Azure CLI works on Linux/macOS/Windows, while PowerShell is primarily for Windows.
  • Remove or supplement PowerShell-specific media references with CLI equivalents.
  • Add a note clarifying that all steps can be performed on Linux/macOS using Azure CLI.
GitHub Create Pull Request
Event Hubs Azure Event Hubs - Client SDKs | Microsoft Docs ...tDocs/azure-docs/blob/main/articles/event-hubs/sdks.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page lists SDKs for multiple languages and platforms, but the .NET section and legacy SDKs reference Windows-specific libraries (e.g., WindowsAzure.Messaging, .NET Framework) and mention Windows tools and patterns. The .NET packages section discusses Windows-only libraries and places .NET/Windows information before other platforms. However, the main SDK table includes Linux-friendly languages (Java, Python, Go, JavaScript) and does not provide usage examples, so the bias is present but not severe.
Recommendations
  • Clarify cross-platform support for .NET Standard libraries, explicitly stating Linux/macOS compatibility.
  • Avoid using Windows-specific naming (e.g., WindowsAzure.Messaging) without noting platform limitations.
  • Add a section or callout highlighting Linux/macOS usage, especially for .NET SDKs.
  • Ensure that examples and tutorials linked from the page include Linux/macOS instructions where relevant.
  • Present SDKs in a neutral order (e.g., alphabetical by language) rather than .NET/Windows first.
GitHub Create Pull Request
Event Hubs Govern resources for client applications with application groups ...cles/event-hubs/resource-governance-with-app-groups.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parity between Azure Portal, Azure CLI, PowerShell, and ARM template methods for managing application groups in Event Hubs. However, PowerShell examples and references are given equal prominence to CLI, and in some sections (such as 'Enable or disable an application group' and 'Apply throttling policies'), PowerShell is listed before ARM template, which may subtly reinforce Windows-centric workflows. There are no explicit Linux/macOS-only gaps, but the presence of PowerShell throughout and its equal emphasis may create friction for non-Windows users, especially since PowerShell is less commonly used on Linux/macOS compared to CLI.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • List Azure CLI examples before PowerShell in all sections to reinforce CLI as the default cross-platform approach.
  • Add a note clarifying that PowerShell is available on Linux/macOS, but CLI is more commonly used in those environments.
  • Consider adding bash script snippets or references to scripting with Azure CLI for Linux users.
  • Ensure that screenshots and instructions do not assume a Windows environment (e.g., avoid showing Windows-specific UI elements or paths).
GitHub Create Pull Request
← Previous Page 3 of 3 Next →