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 51-75 of 211 flagged pages
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-service-endpoints.md ...in/articles/event-hubs/event-hubs-service-endpoints.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 tools separately and before Linux alternatives, and by referencing deployment instructions that default to PowerShell. There is no mention of Linux-specific shell usage, nor are there explicit Bash or Linux command examples. The CLI section is brief and lacks parity with the detailed PowerShell section. Resource Manager template deployment links point to PowerShell guides, not Bash or cross-platform alternatives.
Recommendations
  • Provide explicit Bash and Linux shell examples alongside PowerShell instructions, especially for Azure CLI usage.
  • Ensure deployment instructions for Resource Manager templates include both PowerShell and Bash (Linux/macOS) options, with links to respective guides.
  • Balance the depth of CLI and PowerShell sections, giving equal detail and command breakdown for both.
  • Avoid referencing Windows tools (like PowerShell) before cross-platform alternatives; present CLI and PowerShell together or in parallel.
  • Add notes or examples for Linux users, such as using az CLI in Bash, and clarify that all steps can be performed on Linux/macOS.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/private-link-service.md .../blob/main/articles/event-hubs/private-link-service.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. All command-line automation is shown using Azure PowerShell, with no mention of Azure CLI or Bash alternatives. The validation steps explicitly reference creating a Windows VM, and there are no Linux VM instructions or screenshots. The use of Windows tools and terminology is prevalent, and Linux equivalents are absent throughout the guide.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all automation steps, including private endpoint creation and DNS configuration.
  • Include instructions and screenshots for creating and validating with a Linux VM in Azure, not just Windows.
  • When demonstrating command-line validation (e.g., nslookup), clarify that the commands work on both Windows and Linux, and provide Linux shell syntax where appropriate.
  • Reference cross-platform tools and avoid Windows-specific terminology unless necessary; mention Linux equivalents when discussing network configuration and VM setup.
  • Ensure that prerequisites and step-by-step guides are platform-neutral or offer parallel instructions for both Windows and Linux environments.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/test-locally-with-event-hub-emulator.md ...les/event-hubs/test-locally-with-event-hub-emulator.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 presenting Windows and PowerShell instructions before Linux/macOS equivalents, referencing Windows-specific tools (WSL, PowerShell), and providing more detailed steps for Windows users. Linux/macOS instructions are less detailed and lack parity in step-by-step guidance. There are also notes and path conventions tailored to Windows users, with limited attention to Linux-specific nuances.
Recommendations
  • Present Linux/macOS instructions before or alongside Windows instructions, ensuring equal detail and clarity.
  • Provide explicit Linux/macOS terminal command examples, including navigation and script execution steps.
  • Include Linux-specific notes about file paths, permissions, and Docker usage (e.g., sudo requirements, shell differences).
  • Avoid assuming PowerShell or WSL as the default; offer Bash/Zsh examples and alternatives.
  • Add troubleshooting tips for Linux/macOS environments, such as Docker daemon issues or file permission errors.
  • Ensure all referenced tools and links have Linux/macOS equivalents (e.g., Docker Desktop for Linux, not just Windows).
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/transport-layer-security-configure-minimum-version.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/transport-layer-security-configure-minimum-version.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by providing only PowerShell commands for ARMClient usage, referencing a Windows-specific tool (ARMClient.exe), and omitting equivalent Linux/macOS instructions or alternatives. No cross-platform CLI (e.g., Azure CLI, curl) examples are provided for authentication or querying the API, and Windows-centric tools are mentioned before any platform-neutral options.
Recommendations
  • Include Azure CLI and/or curl examples for obtaining a Bearer token and querying the ARM API, with explicit instructions for Linux/macOS.
  • Mention platform-neutral tools (e.g., REST Client, curl, Postman) before or alongside Windows-specific tools.
  • Provide step-by-step instructions for Linux/macOS users, including installation and usage of relevant tools.
  • Add notes clarifying cross-platform compatibility for all commands and scripts.
  • Ensure screenshots and UI references are not Windows-specific, or provide parity for other platforms if differences exist.
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-08 00:53
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, referencing Windows-specific tools and SDKs (e.g., PowerShell, WindowsAzure.ServiceBus), and providing no explicit Linux shell (bash) examples. While Azure CLI is cross-platform, the ordering and emphasis on PowerShell and Windows-centric SDKs suggest a preference for Windows environments.
Recommendations
  • Provide bash (Linux shell) examples for updating partition count using Azure CLI, explicitly showing usage on Linux/macOS.
  • Reorder examples so that cross-platform tools (Azure CLI, REST API) appear before Windows-specific tools like PowerShell.
  • Reference cross-platform SDKs (e.g., Java, Python, Node.js) in client behavior sections, not just .NET/WindowsAzure.ServiceBus.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide sample commands for each where relevant.
  • Include troubleshooting or operational notes for Linux users, such as file system or environment differences.
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-08 00:53
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 authentication tools (Azure PowerShell and Azure Portal) before mentioning Azure CLI, and providing only C# code samples. There are no Linux-specific instructions, examples, or parity for non-Windows platforms, and no mention of cross-platform SDKs or usage patterns outside .NET.
Recommendations
  • Provide equivalent sample code for Linux-friendly languages (e.g., Python, Java, Node.js) using their respective Azure SDKs.
  • Include instructions and examples for authenticating and managing Event Hubs using Azure CLI and REST API, which are cross-platform.
  • Reorder the prerequisites section to mention Azure CLI before Azure PowerShell and Azure Portal, emphasizing cross-platform tooling.
  • Explicitly state platform compatibility for the .NET management libraries and suggest alternatives for Linux/macOS users.
  • Add links to cross-platform samples and documentation, such as Python or Java management libraries for Azure Event Hubs.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/test-locally-with-event-hub-emulator.md ...les/event-hubs/test-locally-with-event-hub-emulator.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 presenting Windows instructions and tools (PowerShell, WSL) first and in greater detail, while Linux/macOS instructions are brief and lack equivalent step-by-step guidance. Windows-specific tooling (WSL, PowerShell) is emphasized, and file path conventions are explained only for Windows. Linux and macOS users are given minimal instructions, and there are no Linux/macOS-specific examples or troubleshooting notes.
Recommendations
  • Provide step-by-step instructions for Linux and macOS environments, including terminal commands and navigation.
  • Include Linux/macOS-specific troubleshooting notes, such as file permissions and Docker configuration.
  • Explain file path conventions for Linux/macOS (e.g., forward slashes) alongside Windows notes.
  • Present Linux/macOS instructions before or alongside Windows instructions to avoid 'windows_first' bias.
  • Offer examples using native Linux/macOS shells (bash/zsh) rather than focusing on PowerShell/WSL.
  • Ensure parity in detail and clarity between Windows and Linux/macOS sections.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/private-link-service.md .../blob/main/articles/event-hubs/private-link-service.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias by providing only Azure PowerShell examples for CLI automation, referencing Windows VM creation for validation, and omitting equivalent Linux or cross-platform instructions. The validation steps specifically direct users to create a Windows VM, and there are no Bash, Azure CLI, or Linux VM examples. Windows tools and patterns (PowerShell, Windows VM) are mentioned exclusively and before any Linux alternatives, which are not present.
Recommendations
  • Add Azure CLI (az) and Bash examples alongside PowerShell scripts for creating private endpoints and DNS zones.
  • Include instructions for creating and validating with a Linux VM, referencing the appropriate Azure documentation.
  • Provide cross-platform command-line validation steps (e.g., nslookup on Linux, dig) and clarify that the process works on both Windows and Linux VMs.
  • Balance screenshots and walkthroughs to show both Windows and Linux environments where applicable.
  • Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and link to relevant platform-specific guides.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/transport-layer-security-configure-minimum-version.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/transport-layer-security-configure-minimum-version.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by providing only PowerShell/Windows-specific instructions for obtaining a Bearer token (using ARMClient.exe), with no equivalent Linux/macOS examples or CLI alternatives. The use of ARMClient.exe (a Windows tool) is described exclusively and before any mention of cross-platform tools. There are no Bash, Azure CLI, or REST API examples for Linux users, and the documentation assumes a Windows environment for command execution.
Recommendations
  • Provide equivalent instructions for Linux/macOS users, such as using Azure CLI (az account get-access-token) or curl to obtain a Bearer token.
  • Include Bash or shell script examples alongside PowerShell examples.
  • Mention cross-platform tools (e.g., Azure CLI, curl, httpie) before or alongside Windows-specific tools.
  • Clarify that ARMClient.exe is Windows-only and suggest alternatives for other platforms.
  • Ensure that all code samples and instructions are platform-agnostic or have parity between Windows and Linux/macOS.
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-08 00:53
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 is given a dedicated section and is mentioned alongside CLI. PowerShell is a Windows-centric tool, and its inclusion without mentioning Linux alternatives (such as Bash scripting or cross-platform shells) introduces a Windows bias. No explicit Linux shell examples or references to Linux-native tools are provided. The ordering also places PowerShell before ARM templates, reinforcing Windows-first patterns.
Recommendations
  • Add explicit Bash or shell script examples for Azure CLI usage, demonstrating commands in a Linux terminal context.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Include notes or examples for configuring Event Hub properties using Linux-native automation tools (e.g., shell scripts, Ansible).
  • Balance the prominence of PowerShell by either moving it after CLI and ARM template sections or by adding equivalent Linux scripting guidance.
  • State that PowerShell Core is cross-platform if mentioning PowerShell, and provide usage examples for Linux/macOS if relevant.
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-08 00:53
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 strong Windows bias. All instructions for creating and managing the .NET projects assume the use of Visual Studio 2022, a Windows-centric IDE, and reference Windows UI elements (menus, dialog boxes). Package installation is shown exclusively using the NuGet Package Manager Console with PowerShell commands, which is not standard on Linux/macOS. There are no CLI or cross-platform instructions (e.g., using dotnet CLI or Visual Studio Code), and no mention of Linux or macOS environments. This may hinder Linux or cross-platform .NET developers.
Recommendations
  • Add equivalent instructions for Linux and macOS users, including how to create and manage .NET projects using the dotnet CLI.
  • Provide package installation examples using the dotnet CLI (e.g., 'dotnet add package ...') alongside or instead of PowerShell/NuGet Package Manager Console.
  • Mention and provide steps for using cross-platform editors such as Visual Studio Code.
  • Avoid assuming Visual Studio is the only development environment; clarify that .NET Core/.NET 5+ is cross-platform.
  • Explicitly state that the instructions work on Windows, Linux, and macOS, and call out any OS-specific differences.
  • Where UI navigation is described (e.g., menu clicks), provide CLI alternatives or note the equivalent steps for non-Windows environments.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is included as a dedicated example for SAS token generation, and Windows-centric tools (such as PowerShell and .NET/C#) are featured prominently. The disable-local-auth instructions focus on the Azure Portal (a GUI often used on Windows) before mentioning ARM templates. While Bash is included for Linux users, Windows tools and patterns appear first or with more detail, and there is no mention of Linux-specific tooling (e.g., CLI, shell scripts for disabling local auth).
Recommendations
  • Ensure Linux/Bash examples are presented with equal prominence and detail as Windows/PowerShell examples.
  • Provide instructions for disabling local/SAS key authentication using Azure CLI, which is cross-platform and popular on Linux.
  • Include references to Linux-native tools and workflows (e.g., shell scripts, CLI commands) alongside Windows/PowerShell equivalents.
  • Alternate the order of example presentation so that Linux/Bash is not always last.
  • Clarify that all code samples are cross-platform where applicable, and note any OS-specific requirements.
  • Add links to Linux-focused samples or documentation, if available.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by mentioning PowerShell and Azure CLI as tools for managing authorization policies, but does not provide equivalent Linux-specific examples or mention cross-platform alternatives. PowerShell is referenced before Azure CLI, and no explicit Linux command-line or scripting examples are given. The absence of Linux-specific instructions or parity in tool recommendations may hinder Linux users.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and provide examples for both Windows (PowerShell) and Linux (Bash).
  • Include Linux/Bash command examples alongside PowerShell instructions when describing how to manage authorization policies.
  • Reference Linux tools and workflows (such as Bash scripts or native Linux utilities) where appropriate.
  • Ensure tool recommendations are presented in a platform-neutral order, or clarify cross-platform compatibility.
  • Add a section or note highlighting how Linux users can perform the same operations, with links to relevant documentation.
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-08 00:53
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 in several ways. In the 'Manual failover' section, the order of examples is Azure portal, Azure CLI, PowerShell, and C#. PowerShell is given a dedicated example, but there is no mention of Bash, shell scripting, or Linux-specific tools. The CLI example is present, but there are no explicit Linux shell or automation examples. The screenshots and UI references are all for the Azure portal, which is platform-agnostic, but the code samples and management instructions favor Windows-centric tools and languages (PowerShell, C#). There are no Linux shell script examples, nor is there mention of Linux automation patterns or tools.
Recommendations
  • Add explicit Bash/shell script examples for failover and management tasks using Azure CLI, demonstrating usage on Linux.
  • Include references to Linux automation tools (e.g., cron jobs, systemd timers) for automating failover.
  • Provide parity in code samples for other languages commonly used on Linux (e.g., Python, JavaScript), not just C#.
  • Reorder example sections to present platform-neutral or Linux-friendly options (CLI, REST API) before Windows-specific ones (PowerShell).
  • Clarify that Azure CLI commands work cross-platform and provide sample outputs for both Windows and Linux terminals.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-service-endpoints.md ...in/articles/event-hubs/event-hubs-service-endpoints.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 commands separately and in detail, referencing PowerShell in metadata, and linking to PowerShell deployment instructions before CLI equivalents. While Azure CLI is mentioned, there are no explicit Linux shell (bash) examples, and no mention of Linux-specific tooling or patterns. The Resource Manager template deployment link points to PowerShell instructions, and the overall structure and examples favor Windows/PowerShell users over Linux users.
Recommendations
  • Add explicit bash/Azure CLI command examples for all operations currently shown with PowerShell.
  • Ensure deployment instructions for Resource Manager templates include both PowerShell and Azure CLI (bash) options, with equal prominence.
  • Reference Linux shell environments and tools where applicable, not just Windows/PowerShell.
  • Review metadata and navigation to avoid prioritizing PowerShell or Windows-first approaches.
  • Include troubleshooting or usage notes relevant to Linux environments (e.g., Azure CLI installation, authentication differences).
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell usage. Most command-line examples for deploying templates, managing identities, and configuring access policies are provided only in PowerShell, with no Bash or Linux shell equivalents. The use of PowerShell is presented as the default, and there is little mention of cross-platform alternatives or explicit Linux support. This may hinder Linux users or those who prefer Bash/CLI workflows.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all PowerShell examples, especially for template deployment, identity management, and key vault access policy configuration.
  • Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and encourage its use for non-Windows environments.
  • Add Bash script examples where appropriate, especially for steps involving file manipulation, environment variables, or automation.
  • Clarify in notes or callouts which commands are platform-specific and which are cross-platform.
  • Consider reordering examples so that CLI/Bash alternatives are presented before or alongside PowerShell, or use tabs to allow users to select their preferred environment.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-dedicated-overview.md ...n/articles/event-hubs/event-hubs-dedicated-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Determine the cluster type' section, where the use of the 'nslookup' command is illustrated with a Windows-specific namespace (ns.servicebus.windows.net), and the example syntax aligns with Windows conventions. Additionally, references to Azure CLI and PowerShell are made together, but PowerShell (a Windows tool) is mentioned explicitly, while Linux alternatives are not. No Linux-specific examples, tools, or command-line patterns are provided, and Windows-centric terminology (such as 'servicebus.windows.net') appears first or exclusively.
Recommendations
  • Provide Linux-specific command examples alongside Windows ones, such as using 'dig' or 'nslookup' on Linux with appropriate syntax.
  • Mention Azure CLI usage explicitly for Linux/macOS environments, including example commands.
  • Avoid using Windows-specific namespaces or terminology exclusively in examples; include generic or Linux-relevant equivalents.
  • Add notes or sections clarifying cross-platform compatibility for all tools and commands referenced.
  • Ensure parity in instructions for both PowerShell (Windows) and Bash/Azure CLI (Linux/macOS) environments.
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-08 00:53
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. All command-line examples use Azure PowerShell, with no Azure CLI (bash) equivalents provided for Linux/macOS users. The instructions for deploying, validating, and cleaning up resources exclusively use PowerShell scripts, and the Cloud Shell examples are PowerShell-centric. There is no mention or prioritization of Linux-native tools or workflows, and the documentation does not provide Linux-specific guidance or parity.
Recommendations
  • Add Azure CLI (bash) examples alongside PowerShell for all deployment, validation, and cleanup steps.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
  • Ensure that Linux/macOS users are given equal guidance and visibility for their preferred tools and workflows.
  • Reorder or parallelize examples so that Windows and Linux approaches are presented together, rather than PowerShell/Windows first.
  • Link to Azure CLI documentation and usage guides in the prerequisites and relevant sections.
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-08 00:53
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 examples for configuring IP firewall rules using the Azure portal, Resource Manager templates, Azure CLI, and Azure PowerShell. However, the PowerShell example is the only code sample given for scripting, and it is presented in detail, while the Azure CLI section only mentions the relevant command group without any example. There are no explicit Linux shell (bash) examples, and PowerShell (a Windows-centric tool) is given more prominence and detail. This creates a bias towards Windows users and PowerShell workflows, potentially making it less accessible for Linux users.
Recommendations
  • Add explicit Azure CLI examples for configuring IP firewall rules, including sample commands for adding, listing, updating, and removing rules.
  • Provide bash shell examples for common operations, especially for users on Linux and macOS.
  • Ensure that CLI and PowerShell examples are presented with equal prominence and detail.
  • Clarify that Azure CLI works cross-platform and highlight its usage for Linux/macOS users.
  • Consider adding a section comparing PowerShell and CLI workflows, helping users choose the best tool for their platform.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/schema-registry-concepts.md ...b/main/articles/event-hubs/schema-registry-concepts.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by providing explicit PowerShell examples and references, listing PowerShell as a primary management tool, and not offering equivalent Linux shell or bash examples. While Azure CLI is mentioned (which is cross-platform), the presence of PowerShell-specific instructions and the absence of Linux/Unix shell examples or references may hinder parity for Linux users. Additionally, PowerShell is mentioned after Azure CLI, but before any Linux-native tooling or examples, and there is no mention of bash or other Linux command-line environments.
Recommendations
  • Add explicit bash or Linux shell examples for schema management tasks, especially where PowerShell is referenced.
  • Clarify that Azure CLI commands work cross-platform and provide sample commands in both Windows (PowerShell) and Linux (bash) syntax.
  • If PowerShell is mentioned, also mention Linux-native tools or scripting environments, or at least provide parity in examples.
  • Consider including a section or links for Linux users, outlining any differences or tips for using the SDKs and tools on Linux.
  • Review all code and command examples to ensure they are not Windows-centric and provide equivalent Linux-friendly alternatives where appropriate.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page shows evidence of Windows bias. The primary troubleshooting command for checking dropped packets uses 'psping.exe', a Windows-only tool, and the example is given in Windows shell syntax. PowerShell and Windows tools are mentioned before alternatives, with no explicit Linux equivalent commands or tools (such as 'nc', 'telnet', or 'ss') provided. The mention of 'tnc' (Test-NetConnection) is also a PowerShell/Windows tool. There is a lack of Linux-specific troubleshooting guidance or examples.
Recommendations
  • Provide equivalent Linux commands and examples for troubleshooting connectivity, such as using 'nc', 'telnet', or 'ss' for TCP connectivity checks.
  • List cross-platform tools (e.g., Wireshark, curl, wget) with usage examples for both Windows and Linux.
  • When mentioning a tool, specify its platform and offer alternatives for other platforms.
  • Include Linux shell command syntax alongside Windows/PowerShell examples.
  • Ensure that troubleshooting steps are not dependent on Windows-only utilities.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates bias toward Windows by exclusively providing a .NET example (which is most commonly used on Windows) and recommending Fiddler—a Windows-only tool—for verifying TLS versions. There are no examples or guidance for Linux users, such as using OpenSSL, curl, or other cross-platform methods to set or verify TLS versions.
Recommendations
  • Add examples for configuring TLS in client applications on Linux, such as using Python, Java, or Node.js.
  • Include instructions for verifying TLS versions using cross-platform tools like OpenSSL, curl, or Wireshark.
  • Mention Linux and macOS environments explicitly and provide parity in troubleshooting and verification steps.
  • Avoid recommending Windows-only tools (e.g., Fiddler) as the primary or sole method for verification; suggest alternatives for other platforms.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/transport-layer-security-configure-minimum-version.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/transport-layer-security-configure-minimum-version.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by providing command-line examples exclusively using Windows tools (ARMClient.exe) and PowerShell syntax, with no mention of Linux or cross-platform alternatives for obtaining bearer tokens or interacting with the Azure Resource Manager API. There are no CLI or shell examples for Linux/macOS users, nor are Linux-compatible tools suggested.
Recommendations
  • Provide equivalent instructions and examples for Linux/macOS users, such as using Azure CLI (az) or curl to obtain bearer tokens and query the ARM API.
  • Mention cross-platform tools (e.g., Azure CLI, REST API with curl) alongside Windows-specific tools like ARMClient.exe.
  • When presenting command-line examples, offer both PowerShell and Bash/shell alternatives, or use cross-platform syntax where possible.
  • Explicitly state when a tool or command is Windows-only, and offer a Linux-compatible alternative in the same section.
GitHub Create Pull Request
Event Hubs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/test-locally-with-event-hub-emulator.md ...les/event-hubs/test-locally-with-event-hub-emulator.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by prioritizing Windows and PowerShell instructions, referencing Windows-specific tools (WSL, PowerShell), and providing more detailed, step-by-step guidance for Windows users. Linux and macOS instructions are less detailed and lack parity in example commands or troubleshooting. There are also references to Windows path conventions and Docker Desktop, with less emphasis on native Linux workflows.
Recommendations
  • Provide equally detailed, step-by-step instructions for Linux and macOS users, including explicit shell commands for cloning repositories, navigating directories, and running scripts.
  • Avoid assuming Docker Desktop as the default; mention native Docker Engine for Linux and provide installation links for all platforms.
  • List Linux/macOS instructions before or alongside Windows instructions to avoid a Windows-first impression.
  • Include troubleshooting notes and path conventions relevant to Linux/macOS (e.g., forward slashes, permissions).
  • Where PowerShell or Windows-specific commands are given, provide equivalent bash/zsh commands for Linux/macOS.
  • Clarify when WSL is only needed for Windows, and offer native Linux alternatives where possible.
  • Add screenshots or terminal output examples from Linux/macOS environments, not just Windows.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides a balanced set of code samples for generating SAS tokens in multiple languages (NodeJS, Java, PHP, C#, PowerShell, Bash). However, there is a mild Windows bias: PowerShell (a Windows-centric tool) is given a dedicated section, and the Bash example (for Linux/macOS) is placed last. Additionally, disabling SAS authentication is only described via the Azure Portal (a GUI tool most accessible on Windows) and ARM templates, with no mention of CLI or Linux-native tooling. There are no explicit Linux command-line (Azure CLI) examples for management tasks, and the documentation references .NET samples first in the 'Samples' section.
Recommendations
  • Reorder code samples so that Bash (Linux/macOS) appears before PowerShell, or present them side-by-side.
  • Add Azure CLI examples for management tasks such as disabling SAS/local authentication, alongside ARM template and Portal instructions.
  • Include references to SDK samples in other languages (e.g., Python, Java) and not just .NET, to improve cross-platform parity.
  • Explicitly mention that Bash scripts are suitable for Linux/macOS environments, and PowerShell for Windows, to guide users.
  • Where possible, provide parity in tooling instructions (e.g., show how to perform management tasks using both Azure CLI and Portal).
GitHub Create Pull Request
← Previous Page 3 of 9 Next →