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 1-25 of 211 flagged pages
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-11 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 exclusively referencing Windows tools and workflows, such as Visual Studio 2022 and the NuGet Package Manager Console (PowerShell-based), for project creation and package management. All step-by-step instructions and screenshots are tailored for Windows environments, with no mention of Linux or cross-platform alternatives (e.g., VS Code, CLI commands, or dotnet CLI). There are no examples or guidance for Linux users, and Windows-specific terminology and UI elements are used throughout.
Recommendations
  • Add equivalent instructions for Linux and macOS users, including project creation and package management using the dotnet CLI (e.g., 'dotnet new console', 'dotnet add package').
  • Include examples and screenshots for cross-platform editors like Visual Studio Code.
  • Mention and demonstrate how to run the sample applications from the terminal/command line on Linux and macOS.
  • Clarify that the .NET SDK and Azure libraries are cross-platform and provide explicit steps for non-Windows environments.
  • Avoid referencing Windows-specific UI elements and workflows exclusively; present them as one option among several.
  • Add notes or tabs for Linux/macOS users wherever PowerShell or Windows tools are referenced.
GitHub Create Pull Request
Event Hubs Dynamically add partitions to an event hub in Azure Event Hubs ...main/articles/event-hubs/dynamically-add-partitions.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by presenting PowerShell as the first method for updating partition count, referencing Windows-specific tools (PowerShell, .NET SDK with WindowsAzure.ServiceBus), and mentioning Windows-centric patterns before cross-platform alternatives. While Azure CLI and Apache Kafka CLI are included, the prominence and ordering of Windows tools and examples suggest a bias toward Windows environments.
Recommendations
  • Present cross-platform methods (such as Azure CLI and Kafka CLI) before or alongside Windows-specific methods like PowerShell.
  • Include explicit Linux/macOS usage notes or examples for CLI commands, demonstrating parity across operating systems.
  • Reference .NET SDKs in a platform-neutral way, and mention Java, Python, or other SDKs that are commonly used on Linux.
  • Avoid using Windows-specific terminology (e.g., 'PowerShell') as the default or primary example; clarify that CLI commands work on all platforms.
  • Add guidance for Linux users on installing and using Azure CLI and Kafka 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
High Priority View Details →
Scanned: 2026-01-11 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 presenting Windows/Powershell instructions first, 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 equivalent walkthroughs. There are also notes and tips specific to Windows file path conventions, while Linux equivalents are not mentioned.
Recommendations
  • Provide equally detailed, step-by-step instructions for Linux and macOS, including terminal commands and navigation.
  • Include Linux-specific notes for file path conventions and environment setup, similar to the Windows double-backslash tip.
  • Present Linux/macOS instructions before or alongside Windows instructions to avoid 'windows_first' ordering.
  • Offer examples using native Linux tools (e.g., bash, sh) and avoid assuming WSL usage for Windows users.
  • Add troubleshooting tips and environment setup notes for Linux/macOS users, matching the depth given to Windows users.
GitHub Create Pull Request
Event Hubs SAS Authentication for Azure Event Hubs Resources ...les/event-hubs/authenticate-shared-access-signature.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides code examples for generating SAS tokens in multiple programming languages, including PowerShell and Bash. However, PowerShell (a Windows-centric tool) is given a dedicated section and a full example, and is placed before Bash. There is also a strong presence of .NET/C# and references to Windows-centric tools and patterns (e.g., HttpUtility, PowerShell), while Linux-native tools and workflows are less emphasized. The Bash example is present but appears after PowerShell, and there are no explicit Linux command-line or shell environment instructions outside of Bash. There are no explicit Linux GUI or CLI tool references, and the sample links are .NET-focused.
Recommendations
  • Reorder the code examples so that Bash (Linux shell) appears before PowerShell, or present them side-by-side to avoid implying a Windows-first workflow.
  • Include more Linux-native command-line examples and references, such as using curl, openssl, or other common Linux utilities for token generation and management.
  • Add explicit instructions or notes for Linux users, such as package installation commands for required tools (e.g., jq, openssl).
  • Provide sample links or references for non-.NET SDKs (e.g., Java, Node.js, Python) and include Linux usage scenarios.
  • Where Windows-specific tools or APIs are mentioned (e.g., HttpUtility), provide Linux/Unix equivalents or note any cross-platform considerations.
  • Ensure that all code samples are tested and runnable on both Windows and Linux, and clarify any platform-specific differences.
GitHub Create Pull Request
Event Hubs Authorize access with shared access signatures ...event-hubs/authorize-access-shared-access-signature.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by mentioning PowerShell and Azure CLI as configuration options for SAS policies, but does not provide equivalent Linux-specific examples or mention cross-platform alternatives. The reference to PowerShell appears before Azure CLI, and there is no explicit guidance for Linux users or mention of Bash/Shell usage. This may make the documentation less accessible 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/Shell).
  • Add Linux/macOS-specific instructions or examples for configuring SAS policies, such as using Bash with Azure CLI.
  • Avoid listing PowerShell before Azure CLI unless there is a technical reason; consider presenting CLI examples first for platform neutrality.
  • Include a note clarifying that all operations can be performed on Linux/macOS using Azure CLI or REST API, and provide links to relevant documentation.
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
High Priority View Details →
Scanned: 2026-01-11 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 primarily through the exclusive use of PowerShell commands for deployment and configuration tasks, with no Bash or Linux shell equivalents provided. PowerShell is referenced as the main method for key vault configuration, access policy management, and ARM template deployment. There are no explicit instructions or examples for Linux users (e.g., Bash, sh, or cross-platform Azure CLI usage outside of az commands), and PowerShell commands are presented first and exclusively in all relevant sections.
Recommendations
  • Provide equivalent Bash or shell script examples for all PowerShell commands, especially for ARM template deployment and key vault access policy management.
  • Explicitly mention that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows, and prefer CLI examples where possible.
  • Add a section or callouts for Linux/macOS users, clarifying how to perform these operations without PowerShell.
  • Where PowerShell is used, offer the Azure CLI alternative first, or at least side-by-side, to avoid implying Windows is the default or preferred platform.
  • Ensure that all instructions referencing PowerShell also include links or references to how to install and use Azure CLI on Linux/macOS.
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-11 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, primarily in the 'Determine the cluster type' section. The only command-line example provided is 'nslookup' against a '.windows.net' namespace, which implicitly references Windows environments. Additionally, instructions mention using PowerShell alongside Azure CLI and portal, but do not provide explicit Linux or cross-platform command examples. There are no Linux-specific tools or patterns mentioned, and no explicit parity in example coverage for Linux users.
Recommendations
  • Provide explicit Linux and macOS command-line examples (e.g., using dig or nslookup on Linux/macOS) alongside Windows examples.
  • Clarify that Azure CLI and PowerShell are cross-platform, and provide example commands for both environments.
  • Avoid using '.windows.net' in examples without context; include examples with '.azure.com' or other neutral domains.
  • Add a note or section highlighting cross-platform support and usage patterns for cluster management.
  • Ensure that any references to tools (e.g., PowerShell) are balanced with equivalent Linux/macOS alternatives.
GitHub Create Pull Request
Event Hubs Configure properties for an Azure event hub .../articles/event-hubs/configure-event-hub-properties.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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. However, PowerShell (a Windows-centric tool) is given its own dedicated section, and the CLI section does not mention Linux or shell-specific usage. There is no explicit Linux example, nor are Linux-native tools or shell scripting patterns discussed. The presence of PowerShell and its parameters, without equivalent Bash or Linux shell examples, demonstrates a Windows bias.
Recommendations
  • Add explicit Linux/Bash examples for Azure CLI commands, including sample shell usage.
  • Clarify that Azure CLI is cross-platform and provide OS-specific notes if needed.
  • If PowerShell is mentioned, also mention Bash or other Linux-native shells for parity.
  • Include troubleshooting or usage notes for Linux environments where relevant.
  • Ensure that examples and tool recommendations do not implicitly prioritize Windows tools over cross-platform or Linux-native alternatives.
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-11 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 method alongside Azure portal, CLI, and C#. The PowerShell example is given explicit mention, and there are no Linux-specific shell examples (such as Bash or scripting with curl), nor is there any mention of Linux tools or workflows. The CLI example is present, but the ordering and explicit PowerShell focus suggest a Windows-centric approach. There are no examples or guidance for Linux automation or scripting, and screenshots and UI references are all for the Azure portal, which is platform-neutral but often used from Windows environments.
Recommendations
  • Add explicit Bash/shell examples for Linux users, such as using curl or scripting with az CLI.
  • Include references to Linux automation tools (e.g., cron jobs, systemd timers) for failover orchestration.
  • Reorder examples so that platform-neutral tools (CLI, REST API) appear before PowerShell.
  • Provide sample scripts or code snippets for Linux environments, such as Python or Bash.
  • Clarify that all CLI commands work on Linux/macOS as well as Windows, and provide troubleshooting tips for non-Windows platforms.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for configuring IP firewall rules, and references PowerShell deployment instructions before or in greater detail than Azure CLI. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or workflows. The CLI section is brief and lacks example commands, while the PowerShell section includes a full script. This suggests a bias toward Windows and PowerShell users, with insufficient parity for Linux users.
Recommendations
  • Add detailed Azure CLI examples for all operations currently shown with PowerShell, including step-by-step command usage and sample outputs.
  • Include bash shell examples for deploying Resource Manager templates, not just PowerShell.
  • Ensure that CLI instructions are as comprehensive and visible as PowerShell instructions, including troubleshooting tips and context.
  • Explicitly mention Linux compatibility and workflows where relevant, such as using az CLI on Linux/macOS.
  • Where possible, provide cross-platform guidance or note differences in experience between Windows and Linux.
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-11 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 prioritizing Windows-centric tools and workflows. It lists Azure PowerShell before Azure CLI in the prerequisites for service principal creation, and the only code sample provided is in C#/.NET, which is most commonly used on Windows. There are no examples or references for Linux-native tools, languages, or workflows (such as Python, Java, or bash scripting), nor is there guidance for using the management libraries on Linux or macOS. The documentation also omits any mention of cross-platform compatibility or alternative SDKs.
Recommendations
  • Add explicit guidance and examples for using Azure CLI (which is cross-platform) before or alongside Azure PowerShell.
  • Include sample code in a Linux-friendly language (e.g., Python, Java) or clarify .NET Core compatibility for Linux/macOS.
  • Provide instructions for installing and running the management libraries on Linux and macOS, including any required dependencies.
  • Mention cross-platform support and best practices for non-Windows environments.
  • Link to Linux/macOS-specific tutorials or documentation where available.
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-11 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. All command-line examples use Azure PowerShell, with no Azure CLI (cross-platform) or Bash examples provided. The instructions for deploying, validating, and cleaning up resources are exclusively written for PowerShell, which is more familiar to Windows users. There is no mention of Linux-specific workflows or tools, and the documentation does not provide parity for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell scripts, as Azure CLI is cross-platform and commonly used on Linux and macOS.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide Bash/Azure CLI instructions.
  • Reorder or parallelize instructions so that CLI (cross-platform) examples are presented before or alongside PowerShell examples.
  • Include notes or sections for Linux/macOS users to ensure they can follow the quickstart without needing to use PowerShell.
  • Review and update any references or screenshots that may imply a Windows-only environment.
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-11 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 Windows bias by listing Azure PowerShell instructions and references before or alongside Azure CLI, with explicit PowerShell command examples but no explicit CLI command examples. The deployment instructions link to PowerShell-based deployment guidance, and there are no Linux-specific instructions, examples, or references to bash/shell scripting. The use of 'Service Bus namespace' and other terminology is consistent with Azure's Windows-centric ecosystem, and there is no mention of Linux tools or workflows.
Recommendations
  • Provide explicit Azure CLI command examples for all operations currently shown only with PowerShell.
  • Include bash/shell scripting examples for deploying Resource Manager templates, not just PowerShell.
  • Link to both PowerShell and Azure CLI deployment guides, ensuring parity in instructions for Linux users.
  • Add notes or sections clarifying that all operations can be performed from Linux/macOS environments using Azure CLI.
  • Ensure screenshots and UI references do not assume a Windows environment (e.g., avoid showing PowerShell terminals exclusively).
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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a clear Windows bias. All CLI examples for configuring private endpoints and DNS zones use Azure PowerShell, with no equivalent Azure CLI or Bash examples. The validation steps instruct users to create a Windows VM and run commands from a Windows command line, with no mention of Linux VM creation or Linux shell commands. The documentation references Windows tools and workflows first and exclusively, omitting Linux alternatives.
Recommendations
  • Provide equivalent Azure CLI (az) and Bash examples for all PowerShell commands, ensuring Linux users can follow along.
  • Include instructions for creating and validating with a Linux VM, referencing the relevant Azure documentation for Linux VM creation.
  • Show command-line validation steps using both Windows (cmd/powershell) and Linux (bash) shells, e.g., using nslookup or dig.
  • Avoid referencing only Windows tools or workflows; mention Linux alternatives wherever applicable.
  • Where screenshots or walkthroughs are shown, clarify that the steps apply to both Windows and Linux environments, or provide parallel Linux screenshots if UI differences exist.
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-11 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 by explicitly mentioning PowerShell and providing a PowerShell example for schema management, while Linux-native equivalents (such as Bash or shell scripting) are not referenced. Although the Azure CLI is mentioned (which is cross-platform), the inclusion of PowerShell as a distinct example and the absence of Linux-specific command-line examples or references to Linux tools suggest a preference for Windows environments. The order of presentation also lists PowerShell after Azure CLI, but does not provide parity with Linux shell examples.
Recommendations
  • Add explicit Linux shell (bash) examples for schema registry management tasks, such as using curl or Azure CLI from a Linux terminal.
  • Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (cmd/PowerShell) and Linux (bash).
  • Include references to Linux-native tools or scripting patterns where relevant, to ensure parity with PowerShell examples.
  • Consider reordering examples so that cross-platform or Linux-native approaches are presented before or alongside Windows-specific tools.
  • Review related samples and ensure that they include instructions or scripts for Linux environments, not just Windows/PowerShell.
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-11 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 primarily Windows-centric, and recommends Fiddler—a Windows-only tool—for verifying TLS usage. There are no examples or tool recommendations for Linux or cross-platform environments, nor is there mention of Linux-specific methods for configuring or verifying TLS.
Recommendations
  • Add examples for configuring TLS in client applications running on Linux, such as using Python, Java, or .NET Core on Linux.
  • Include instructions for verifying TLS versions using cross-platform tools like Wireshark or OpenSSL, which are available on both Windows and Linux.
  • Mention Linux-specific considerations for TLS support, such as required OS libraries or commands to check supported TLS versions.
  • Ensure that tool recommendations (e.g., Fiddler) are accompanied by alternatives for Linux users.
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-11 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 demonstrates a bias toward Windows environments by providing only PowerShell examples for authentication (ARMClient.exe), referencing a Windows-specific tool (ARMClient.exe), and omitting equivalent Linux/macOS instructions or tools. No Linux-native command-line examples (such as curl, az CLI, or bash scripts) are provided for checking or configuring the minimum TLS version, and the Windows-centric approach appears first and exclusively in relevant sections.
Recommendations
  • Add Linux/macOS examples for authentication and querying the Azure Resource Manager API, such as using Azure CLI (az), curl, or bash scripts.
  • Mention cross-platform tools before or alongside Windows-specific ones (e.g., show az CLI and curl usage before ARMClient.exe).
  • Provide instructions for obtaining a Bearer token on Linux/macOS (e.g., using az account get-access-token).
  • Include notes or sections explicitly addressing Linux and macOS users, ensuring parity in guidance and tooling.
  • Where screenshots or UI steps are shown, clarify if there are platform-specific differences or provide platform-agnostic instructions.
GitHub Create Pull Request
Event Hubs Troubleshoot connectivity issues - Azure Event Hubs | Microsoft Docs ...blob/main/articles/event-hubs/troubleshooting-guide.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by primarily referencing Windows-specific tools (psping.exe), providing command-line examples only for Windows (PowerShell), and mentioning Windows tools before suggesting alternatives. There is a lack of explicit Linux/macOS troubleshooting commands or tool recommendations, and the guidance does not provide parity for non-Windows users.
Recommendations
  • Include equivalent Linux/macOS commands and tools (e.g., 'nc', 'telnet', 'nmap', or 'ss') alongside Windows examples for connectivity testing.
  • Provide shell/bash examples in addition to PowerShell/Windows CLI commands.
  • Mention cross-platform tools (e.g., Wireshark, curl, wget) with usage examples for both Windows and Linux/macOS.
  • Reorder troubleshooting steps to present platform-neutral or cross-platform solutions first, followed by platform-specific instructions.
  • Explicitly state which tools/commands are platform-specific and offer alternatives for other operating systems.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides configuration instructions for Azure Event Hubs IP firewall rules using the Azure portal, Resource Manager templates, Azure CLI, and Azure PowerShell. However, there is a noticeable bias toward Windows environments: PowerShell examples are given in detail, and the deployment link for Resource Manager templates points to a PowerShell-specific page. There are no explicit Linux shell (bash) examples, and PowerShell is mentioned before CLI in the command-line sections. The documentation also references Windows-centric tools and patterns, such as PowerShell cmdlets, without providing equivalent bash or cross-platform alternatives.
Recommendations
  • Add explicit bash examples for Azure CLI commands, demonstrating how to add, list, update, and remove IP firewall rules.
  • Provide deployment instructions for Resource Manager templates using both Azure CLI (az deployment) and PowerShell, with links to both sets of documentation.
  • Ensure that CLI examples (bash) are presented before or alongside PowerShell examples to avoid Windows-first ordering.
  • Reference cross-platform tools and patterns where possible, and clarify that Azure CLI and REST API methods are fully supported on Linux and macOS.
  • Where screenshots or instructions reference client IP address detection, clarify how this works for Linux/macOS users.
  • Review and update links to point to both PowerShell and CLI documentation, not just PowerShell.
GitHub Create Pull Request
Event Hubs Troubleshoot connectivity issues - Azure Event Hubs | Microsoft Docs ...blob/main/articles/event-hubs/troubleshooting-guide.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing and providing examples for Windows-specific tools (psping.exe), mentioning PowerShell/Windows CLI before Linux equivalents, and lacking explicit Linux command examples for troubleshooting connectivity. While 'wget' is mentioned for network checks, the main troubleshooting commands and tool downloads are Windows-centric, with no parity for Linux users.
Recommendations
  • Provide Linux equivalents for all troubleshooting commands, e.g., show how to use 'nc', 'telnet', or 'ss' for connectivity checks.
  • Include download and usage instructions for cross-platform tools (or Linux-native alternatives) alongside Windows tools like 'psping.exe'.
  • Offer explicit bash/Linux shell command examples in addition to PowerShell/Windows examples.
  • Structure troubleshooting steps so that Windows and Linux approaches are presented side-by-side or in parallel sections.
  • Mention platform-agnostic tools (e.g., Wireshark) with installation instructions for both Windows and Linux.
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
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 a Windows bias by prioritizing Azure portal (a GUI most commonly used on Windows), referencing PowerShell before CLI in related content, and omitting explicit Linux or cross-platform command-line examples for role assignment and authentication. There are no Linux-specific tools or patterns mentioned, and the sample code is focused on .NET and Java without clarifying platform compatibility.
Recommendations
  • Include explicit Linux and cross-platform examples for role assignment and authentication, such as using Azure CLI and Bash scripts.
  • Present Azure CLI instructions before or alongside PowerShell, highlighting CLI's cross-platform nature.
  • Add notes or sections clarifying that the authentication libraries and code samples work on Linux, macOS, and Windows.
  • Reference Linux-friendly tools (e.g., az CLI, Bash) in the main workflow, not just in related content.
  • Provide sample commands for both PowerShell and Bash/CLI when demonstrating administrative tasks.
GitHub Create Pull Request
Event Hubs Authorize Azure Event Hubs Access With Microsoft Entra ID .../event-hubs/authorize-access-azure-active-directory.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Dotnet Heavy
Summary
The documentation page focuses on Azure Event Hubs authorization with Microsoft Entra ID but exhibits bias toward Windows environments. All code samples referenced are for .NET (DotNet), a platform most commonly associated with Windows. There are no examples or references for Linux-native tools, languages, or command-line patterns (e.g., Bash, curl, Python, Java, or CLI usage on Linux). The documentation does not mention Powershell explicitly, but the exclusive use of .NET samples and the lack of Linux or cross-platform examples suggest a Windows-centric approach.
Recommendations
  • Add sample code and walkthroughs for Linux-native languages and tools, such as Python, Java, Node.js, or Bash scripts.
  • Include examples using Azure CLI and REST API calls that can be run from any OS, not just Windows.
  • Reference cross-platform SDKs and provide links to samples for those SDKs.
  • Explicitly mention that the authentication and authorization steps can be performed from Linux environments and provide guidance for doing so.
  • Balance the documentation by listing Linux or cross-platform examples before or alongside Windows/.NET examples.
GitHub Create Pull Request
Event Hubs Authorize access with shared access signatures ...event-hubs/authorize-access-shared-access-signature.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and the Azure portal as primary tools for managing SAS policies, without mentioning Linux-specific alternatives or providing cross-platform command examples. The instructions for creating policy rules mention PowerShell and Azure CLI, but PowerShell is listed first, and there are no explicit Linux shell or CLI examples. This may make Linux users feel secondary or unsupported.
Recommendations
  • Provide explicit Linux shell (bash) examples for managing SAS policies, alongside PowerShell examples.
  • When mentioning tools, list Azure CLI before or alongside PowerShell, and clarify that Azure CLI is cross-platform.
  • Include instructions or examples for using Linux-native tools and environments, such as bash scripts or Linux terminal commands.
  • Avoid implying that PowerShell is the default or primary method, and ensure parity in documentation for both Windows and Linux users.
GitHub Create Pull Request
Event Hubs Configure properties for an Azure event hub .../articles/event-hubs/configure-event-hub-properties.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring Event Hub properties, but PowerShell is highlighted as a primary automation tool, which is Windows-centric. The PowerShell section appears before the ARM template example, and there is no mention of Linux-native scripting tools (e.g., Bash) or cross-platform alternatives to PowerShell. There are no Linux-specific examples or references to Linux shell usage, and PowerShell is presented as a standard approach, which may suggest a Windows bias.
Recommendations
  • Add explicit Bash or shell script examples for Linux users alongside Azure CLI commands.
  • Clarify that Azure CLI is cross-platform and can be used on both Windows and Linux, possibly with installation instructions or links.
  • Mention that PowerShell Core is available on Linux and macOS, or provide examples using PowerShell Core syntax.
  • Reorder examples so that cross-platform tools (Azure CLI, ARM templates) are presented before Windows-centric tools (PowerShell).
  • Include notes or sections addressing Linux-specific usage patterns or considerations.
GitHub Create Pull Request
Event Hubs Dynamically add partitions to an event hub in Azure Event Hubs ...main/articles/event-hubs/dynamically-add-partitions.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by presenting PowerShell instructions first, referencing Windows-specific tools (PowerShell, .NET SDK with WindowsAzure.ServiceBus), and mentioning Windows patterns before cross-platform alternatives. Linux-specific examples or instructions (such as Bash scripting or Linux-native tools) are missing, and the CLI example is presented after PowerShell, reinforcing a Windows-first approach.
Recommendations
  • Present CLI (az) examples before PowerShell, as CLI is cross-platform and preferred for Linux users.
  • Include Bash or shell script examples for Linux users where applicable.
  • Explicitly mention that CLI commands work on Linux, macOS, and Windows.
  • Reference cross-platform SDKs (such as Azure SDK for Python, Java, or Node.js) in client behavior sections, not just .NET/Windows SDKs.
  • Add troubleshooting or usage notes for Linux environments, especially for resource management and deployment.
  • Where Windows-specific tools are mentioned (e.g., PowerShell), provide equivalent Linux-native alternatives or note their absence.
GitHub Create Pull Request
← Previous Page 1 of 9 Next →