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 126-150 of 211 flagged pages
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples for Azure PowerShell and references to Resource Manager templates and Azure CLI, but the only explicit code example is for PowerShell. There are no Linux/macOS-specific shell examples (e.g., Bash), and PowerShell is presented before CLI. No mention is made of platform-specific considerations for Linux/macOS users, and the CLI section lacks concrete examples, making it less accessible for non-Windows users.
Recommendations
  • Add explicit Azure CLI command examples for configuring IP firewall rules, including full command syntax and sample output.
  • Provide Bash or shell script examples for Linux/macOS users where applicable.
  • Ensure CLI examples are shown before or alongside PowerShell examples to avoid Windows-first ordering.
  • Include notes on cross-platform compatibility, such as how to install and use Azure CLI on Linux/macOS.
  • Clarify that PowerShell examples can be run on Linux/macOS with PowerShell Core, if relevant.
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-14 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, which are primarily relevant to Windows environments. There are no examples, references, or guidance for Linux or macOS users, nor any mention of cross-platform .NET (e.g., .NET Core/.NET 5+) or alternative SDKs (Java, Python, etc.). All exception references and troubleshooting steps assume Windows-centric tooling and patterns.
Recommendations
  • Add examples and exception handling guidance for .NET Core/.NET 5+ (which are cross-platform) and clarify which exceptions apply to cross-platform scenarios.
  • Include references to Linux/macOS environments, such as troubleshooting steps relevant to those platforms (e.g., network configuration, environment variables).
  • Mention and link to Event Hubs SDKs for other languages (Java, Python, Node.js) and provide parity in exception documentation for those SDKs.
  • Explicitly state platform applicability for each exception and configuration step.
  • Where UI steps are described (e.g., Azure portal), clarify that these are platform-agnostic.
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-14 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 instructions and code samples for integrating Azure Event Hubs with Private Link Service, but all CLI examples use Azure PowerShell, which is Windows-centric. The validation steps explicitly reference creating a Windows VM and do not mention Linux alternatives. There are no Bash/Azure CLI examples or Linux VM instructions, making the documentation notably biased toward Windows users.
Recommendations
  • Add equivalent Azure CLI (az) and Bash examples for all PowerShell scripts.
  • Include instructions for creating and validating with a Linux VM, referencing /azure/virtual-machines/linux/quick-create-portal.
  • Present cross-platform CLI options side-by-side or indicate which steps are OS-agnostic.
  • Clarify that Azure PowerShell can be used on Linux/macOS, but recommend Azure CLI for native Linux workflows.
GitHub Create Pull Request
Event Hubs Schema Registry in Azure Event Hubs ...b/main/articles/event-hubs/schema-registry-concepts.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page mentions both Azure CLI and PowerShell as tools for managing schemas, but it gives explicit PowerShell examples and links, which are Windows-specific. PowerShell is listed after Azure CLI, but its inclusion as a distinct example introduces a Windows bias. There are no explicit Linux/macOS shell examples (e.g., Bash), and no mention of platform-specific considerations for these tools. The SDK samples are cross-platform, but the management tooling examples favor Windows environments.
Recommendations
  • Add explicit Bash or shell examples for Linux/macOS users alongside Azure CLI and PowerShell.
  • Clarify that Azure CLI is cross-platform and provide installation/use instructions for Linux/macOS.
  • If PowerShell is mentioned, note that PowerShell Core is available on Linux/macOS, or provide equivalent Bash commands.
  • Ensure that management tasks (such as adding schemas) are demonstrated with both Windows and Linux/macOS tooling.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for configuring IP firewall rules using Azure portal, Resource Manager templates, Azure CLI, and Azure PowerShell. However, the PowerShell example is the only code sample shown, and it is presented before any CLI example. There are no Linux/macOS-specific shell examples (e.g., Bash), and the CLI section lacks concrete command examples. The PowerShell example is detailed and prominent, which may create friction for users on Linux/macOS who do not use PowerShell.
Recommendations
  • Add explicit Azure CLI command examples for managing IP firewall rules, including add, list, update, and remove operations.
  • Ensure CLI examples are shown before or alongside PowerShell examples to avoid Windows-first perception.
  • Include notes or examples for Bash or other shell environments where relevant.
  • Clarify that Azure CLI is cross-platform and provide parity in example depth and detail.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation shows bias towards Windows by providing a troubleshooting command using only the Windows-specific 'psping.exe' tool, without giving a direct Linux/macOS equivalent. The example command uses Windows path notation ('.\psping.exe'), and while it mentions that 'equivalent commands' can be used, it does not provide concrete examples for Linux/macOS users. The download link for 'psping' is also Windows-only. Other sections are generally platform-neutral.
Recommendations
  • Provide explicit Linux/macOS command examples for checking TCP connectivity, such as using 'nc', 'nmap', or 'telnet'.
  • List Linux/macOS tools (e.g., 'nc', 'curl', 'wget') alongside Windows tools like 'psping', and show example usage.
  • Avoid using only Windows path notation in command examples; show both Windows and Linux/macOS syntax where relevant.
  • Include links to cross-platform tools or note platform-specific alternatives.
  • When referencing downloadable tools, clarify platform compatibility or provide alternatives for other OSes.
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-13 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 configuring SAS policies, but only explicitly lists PowerShell as an example tool. There are no Linux/macOS-specific instructions, nor are cross-platform CLI examples provided. The mention of PowerShell may suggest a Windows-first approach, and the lack of explicit Linux/macOS guidance could create friction for non-Windows users.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and provide example commands for both PowerShell (Windows) and Bash (Linux/macOS).
  • Add notes or sections clarifying how to perform SAS-related tasks on Linux/macOS, including screenshots or terminal commands where appropriate.
  • Avoid referencing only Windows-specific tools when discussing configuration; always pair with cross-platform alternatives.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific command-line examples, but all code samples referenced are exclusively for .NET (C#) and are hosted in DotNet folders. There are no Linux/macOS-specific instructions, nor are there samples for other common cross-platform languages (e.g., Python, Java). No Windows-specific tools or PowerShell commands are mentioned, but the exclusive focus on .NET may create friction for Linux/macOS users who are less likely to use .NET as their primary development environment.
Recommendations
  • Add code samples for other popular cross-platform languages such as Python, Java, or Node.js.
  • Include explicit instructions or links for Linux/macOS users, such as how to authenticate using the Azure CLI or relevant SDKs on those platforms.
  • Clarify that the .NET samples are cross-platform, if applicable, and provide setup instructions for Linux/macOS.
  • Provide at least one example using a command-line tool (e.g., Azure CLI) that works identically on Windows, Linux, and macOS.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a notable Windows bias by relying heavily on PowerShell for command-line examples, especially for critical tasks such as deploying Resource Manager templates and managing Key Vault access policies. While Azure CLI is mentioned for some key vault operations, PowerShell is the primary tool for most automation and scripting steps. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell commands are presented without alternatives or parity for Linux users. The order of presentation also tends to favor Windows-centric tools and workflows.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all PowerShell examples, especially for template deployment and Key Vault access policy management.
  • Include Bash shell examples where possible, or clarify that Azure CLI commands work cross-platform.
  • Add notes or sections explicitly addressing Linux/macOS usage, including any prerequisites or differences in command syntax.
  • Consider reordering examples so that cross-platform tools (Azure CLI) are shown before or alongside PowerShell.
  • Where PowerShell is required, mention that PowerShell Core is available for Linux/macOS and provide installation links.
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-13 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 notable Windows bias. All instructions for project creation, package installation, and tooling are centered around Microsoft Visual Studio and PowerShell-based NuGet Package Manager Console, with no mention of cross-platform alternatives like Visual Studio Code, JetBrains Rider, or .NET CLI commands. Steps for installing NuGet packages exclusively use PowerShell syntax, and there are no Linux/macOS-specific instructions or screenshots. The documentation assumes the user is on Windows and using Visual Studio, creating friction for Linux/macOS users who typically use different tools and workflows.
Recommendations
  • Add instructions for creating and managing .NET projects using the .NET CLI (e.g., 'dotnet new console', 'dotnet add package ...'), which works on all platforms.
  • Include alternative tooling options such as Visual Studio Code or JetBrains Rider, and provide steps/screenshots for those environments.
  • Explicitly state that the quickstart works on Linux/macOS and provide any OS-specific notes (e.g., file paths, terminal commands).
  • Present CLI-based package installation commands before or alongside PowerShell/Visual Studio instructions.
  • Avoid assuming Visual Studio is the only supported IDE; clarify that any .NET Core-compatible IDE or editor can be used.
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-13 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, CLI, PowerShell, and C# methods. While the Azure CLI is cross-platform, PowerShell and C# are Windows-centric and are presented alongside CLI without explicit Linux alternatives. No Linux/macOS-specific shell examples (e.g., Bash scripts) are given, and PowerShell is mentioned as a primary automation method. Windows tools and patterns (PowerShell, C#) are referenced before any Linux-native scripting or automation approaches.
Recommendations
  • Add explicit Bash/shell script examples for Linux/macOS users, especially for automation tasks.
  • Clarify that Azure CLI is cross-platform and provide sample commands for Linux/macOS environments.
  • Include references to Linux-native tools or scripting languages (e.g., Python) for automation, or link to relevant samples.
  • Reorder examples so that cross-platform or Linux-friendly methods (CLI, Bash) are presented before Windows-centric ones (PowerShell, C#).
  • Note any platform-specific limitations or considerations for Linux/macOS users.
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-13 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 (legacy) APIs and exception handling, which are primarily associated with Windows environments. There are no examples, references, or guidance for Linux/macOS users, nor any mention of cross-platform SDKs or usage patterns. All exception types and troubleshooting steps are described in the context of .NET and Microsoft namespaces, with no parity for Linux or other platforms.
Recommendations
  • Add equivalent examples and exception handling guidance for Linux/macOS environments, such as using Java, Python, or Node.js SDKs.
  • Include cross-platform troubleshooting steps and clarify which exceptions or patterns apply to non-Windows platforms.
  • Reference documentation for Event Hubs SDKs available on Linux/macOS and provide links to their exception handling guides.
  • Clearly indicate platform-specific limitations and offer alternative approaches for Linux users where .NET APIs are not available.
GitHub Create Pull Request
Event Hubs Secure Azure Event Hubs Using Virtual Network Integration ...in/articles/event-hubs/event-hubs-service-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page provides instructions for Azure portal, Resource Manager templates, Azure CLI, and Azure PowerShell. However, the PowerShell section is more detailed than the CLI section, listing specific cmdlets and usage patterns, while the CLI section only references the command group. Additionally, PowerShell is mentioned after CLI, but the CLI instructions are minimal compared to PowerShell. There are no explicit Linux/macOS-only tools or examples, and no OS-specific instructions, but the PowerShell focus may create friction for Linux/macOS users who prefer CLI or scripting.
Recommendations
  • Expand the Azure CLI section to include specific example commands for adding, listing, updating, and removing network rules, similar to the PowerShell section.
  • Ensure CLI examples are as detailed and discoverable as PowerShell examples, including parameter usage and output samples.
  • Consider adding notes or links for Bash scripting or automation on Linux/macOS, and clarify that Azure CLI is cross-platform.
  • If possible, provide parity in example depth and troubleshooting steps for CLI and PowerShell.
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-13 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 a Windows bias by listing Windows-centric tools (Azure PowerShell) before Linux-friendly alternatives (Azure CLI) in the prerequisites. The sample code and all instructions are .NET/C#, which is most commonly used on Windows, with no mention of Linux or macOS usage, nor any cross-platform considerations (such as .NET Core/SDK installation on Linux or macOS). There are no Linux/macOS-specific examples or troubleshooting notes, and no parity guidance for non-Windows environments.
Recommendations
  • Add explicit instructions for installing and using .NET SDK on Linux and macOS.
  • Provide sample code and usage notes for running the management libraries on Linux/macOS, including any OS-specific caveats.
  • Present Azure CLI instructions before or alongside Azure PowerShell, as CLI is cross-platform.
  • Include troubleshooting or environment setup notes for Linux/macOS users.
  • Clarify that the management libraries can be used cross-platform, and link to relevant cross-platform guides.
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-13 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 more commonly used on Linux/macOS. The use of PowerShell commands and references to Windows-centric tooling creates friction for Linux/macOS users, who must adapt instructions or seek alternative documentation.
Recommendations
  • Add equivalent Azure CLI examples for all deployment, validation, and cleanup steps.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide Bash/CLI code blocks.
  • Ensure that references and links to resource management include both PowerShell and CLI documentation.
  • Present CLI/Bash examples before or alongside PowerShell to avoid implicit prioritization of Windows tools.
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-13 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 instructions and code samples exclusively using Azure PowerShell, with no equivalent examples for Azure CLI, Bash, or Linux/macOS environments. The validation step specifically references creating a Windows VM and does not mention Linux VM alternatives. This creates friction for users on Linux or macOS, who must adapt Windows-centric instructions and tools.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include instructions for creating and validating with a Linux VM (e.g., Ubuntu) alongside the Windows VM steps.
  • When showing command-line validation (e.g., nslookup), clarify that the command works on both Windows and Linux, and provide Linux shell syntax where appropriate.
  • Avoid assuming the use of Windows tools or environments; mention both Windows and Linux options in prerequisites and validation steps.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the section on checking the minimum required TLS version for a namespace. It exclusively provides instructions using ARMClient.exe (a Windows executable) and PowerShell commands for authentication, without mentioning Linux/macOS alternatives or cross-platform CLI tools. No Linux/macOS-specific examples or guidance are provided for these steps, which may hinder non-Windows users.
Recommendations
  • Provide equivalent instructions using Azure CLI (az), which is cross-platform, to obtain a Bearer token and query the Resource Manager API.
  • Mention ARMClient alternatives for Linux/macOS, such as using curl with Azure CLI-acquired tokens.
  • Include example commands for Linux/macOS shells (bash/zsh) alongside PowerShell examples.
  • Clarify that ARMClient.exe is Windows-only and suggest installation/usage alternatives for other platforms.
GitHub Create Pull Request
Event Hubs Schema Registry in Azure Event Hubs ...b/main/articles/event-hubs/schema-registry-concepts.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page references both Azure CLI and PowerShell for schema registry management, but PowerShell (a Windows-centric tool) is mentioned alongside CLI as a primary management option. There are explicit links to PowerShell samples, but no mention of Bash, Linux shell, or macOS-specific instructions. The order of presentation sometimes places Windows tools before cross-platform alternatives, and there are no Linux/macOS-specific examples or clarifications.
Recommendations
  • Add explicit Bash or Linux shell examples for schema registry management tasks, especially for adding schemas to schema groups.
  • Clarify that Azure CLI is cross-platform and provide sample commands for Linux/macOS users.
  • If PowerShell is referenced, also mention PowerShell Core (pwsh), which is cross-platform, or clarify any Windows-only limitations.
  • Ensure that examples and tooling references are presented in a platform-neutral order (e.g., CLI before PowerShell).
  • Consider adding a section or note about Linux/macOS compatibility for all SDKs and management tools.
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-13 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 notable Windows bias: Windows prerequisites and instructions are listed first and in greater detail, including explicit PowerShell and WSL steps, while Linux/macOS instructions are brief and lack equivalent step-by-step guidance. Windows-specific tools (WSL, PowerShell) are mentioned and explained, but Linux/macOS users are expected to infer steps. File path notes and troubleshooting tips are Windows-centric. No Linux/macOS terminal examples are provided for the automated script method.
Recommendations
  • Provide step-by-step Linux/macOS instructions for running the automated script, including terminal commands and navigation.
  • List prerequisites for Linux/macOS (e.g., Docker installation links for Linux/macOS) alongside Windows prerequisites.
  • Include notes about file path conventions for Linux/macOS (e.g., forward slashes) in addition to Windows-specific notes.
  • Offer troubleshooting tips relevant to Linux/macOS environments.
  • Present examples for all platforms in parallel or in tabs, rather than Windows-first.
  • Avoid assuming familiarity with Windows tools (PowerShell, WSL) and provide equivalent Linux/macOS context.
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-13 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, which is most commonly used on Windows, and recommends Fiddler—a Windows-only tool—for verifying TLS usage. There are no Linux/macOS-specific examples, nor are cross-platform verification tools mentioned. This creates friction for non-Windows users.
Recommendations
  • Add examples for configuring TLS in client applications on Linux/macOS platforms (e.g., using Python, Java, or Node.js).
  • Include instructions for verifying TLS usage with cross-platform tools such as Wireshark or OpenSSL.
  • Explicitly mention platform differences and provide guidance for users on Linux/macOS.
  • Present examples for multiple platforms side-by-side, rather than focusing on Windows/.NET first.
GitHub Create Pull Request
Event Hubs Azure Event Hubs - Client SDKs | Microsoft Docs ...tDocs/azure-docs/blob/main/articles/event-hubs/sdks.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page shows a mild Windows bias. .NET (including .NET Standard and .NET Framework) SDKs are listed first in all tables and sections, and there is explicit mention of Windows-specific libraries (e.g., WindowsAzure.ServiceBus) and .NET Framework support. There are no explicit PowerShell examples or Windows-only command-line tools, but the ordering and emphasis on .NET/Windows technologies suggest a Windows-first approach. Linux equivalents, cross-platform usage, or parity are not discussed, and there is no mention of platform-specific considerations for Linux users.
Recommendations
  • Reorder SDK tables to alternate or randomize language order, or explicitly state that order does not imply preference.
  • Add notes clarifying cross-platform support for .NET Standard libraries, including Linux and macOS compatibility.
  • Include explicit mention of Linux usage, such as installation instructions or platform notes for each SDK.
  • Highlight any platform-specific differences or requirements for Linux users, if applicable.
  • Ensure that tutorials and examples are available for both Windows and Linux environments, and link to them from this page.
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
Medium Priority View Details →
Scanned: 2026-01-11 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 bias by referencing the Azure portal (a web UI most commonly used on Windows), providing .NET (Windows-centric) sample code first, and mentioning Azure PowerShell before Azure CLI in related content. There are no explicit Linux or cross-platform command-line examples, and the code samples prioritize .NET and Java without highlighting cross-platform usage or Linux-specific instructions. The documentation does not offer parity for Linux users in terms of workflow or tooling.
Recommendations
  • Add explicit Linux command-line examples using Azure CLI for all steps where Azure PowerShell is mentioned.
  • Provide sample code and instructions for Python and Node.js, which are widely used on Linux, alongside .NET and Java.
  • Include guidance for using the Azure portal on Linux (e.g., browser compatibility, alternative workflows).
  • Ensure that Azure CLI instructions appear before or alongside Azure PowerShell instructions to avoid Windows-first bias.
  • Highlight cross-platform authentication libraries and usage patterns, not just those commonly used on Windows.
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-11 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 bias by exclusively referencing .NET (DotNet) samples and libraries, which are traditionally associated with Windows environments. There are no Linux-specific examples, nor are cross-platform CLI tools (such as Azure CLI or Bash scripts) mentioned. The documentation does not provide parity for Linux users or highlight platform-agnostic approaches for authorizing Event Hubs access.
Recommendations
  • Include Linux-specific examples, such as using Azure CLI or Bash scripts to assign roles and authenticate to Event Hubs.
  • Provide code samples in languages commonly used on Linux (e.g., Python, Java, Node.js) and reference their respective SDKs.
  • Explicitly mention that the .NET samples can be run cross-platform, or provide instructions for running them on Linux.
  • Add guidance for using platform-agnostic tools (e.g., REST API calls, Azure CLI) for role assignment and authentication.
  • Ensure that sample repositories include Linux setup instructions and highlight any OS-specific considerations.
GitHub Create Pull Request
Event Hubs Enable managed identity for a namespace ...ob/main/articles/event-hubs/enable-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes enabling managed identity for an Azure Event Hubs namespace using the Azure portal, with no mention of command-line or automation options. There are no examples for Linux users (e.g., Azure CLI, Bash), nor are PowerShell or Windows-specific tools mentioned, but the portal-centric approach implicitly favors Windows environments, as Linux users often prefer CLI or automation over GUI.
Recommendations
  • Add Azure CLI examples for enabling managed identity, with sample Bash commands.
  • Include PowerShell examples if relevant, but ensure CLI/Bash examples are presented first or alongside.
  • Explicitly mention that the Azure portal is cross-platform, but highlight automation options for Linux users.
  • Provide links to documentation for both CLI and PowerShell methods, ensuring parity in instructions.
GitHub Create Pull Request
Event Hubs Get Connection String for Azure Event Hubs ...rticles/event-hubs/event-hubs-get-connection-string.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Azure portal instructions first, followed by PowerShell examples before CLI examples. PowerShell is a Windows-centric tool, and its placement before the cross-platform Azure CLI may suggest a Windows bias. There are no explicit Linux-specific instructions or examples, nor is there mention of Linux-native tools or shell patterns. All command-line examples use PowerShell or Azure CLI, which is cross-platform, but the ordering and emphasis favor Windows users.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more commonly used on Linux.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Add example shell commands using bash (e.g., with jq for parsing output) to demonstrate Linux usage.
  • Include a note or section for Linux users, highlighting any OS-specific considerations.
  • Avoid implying PowerShell is the default or preferred method unless justified by user data.
GitHub Create Pull Request
← Previous Page 6 of 9 Next →