Event Hubs

242
Total Pages
218
Linux-Friendly Pages
24
Pages with Bias
9.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

59 issues found
Showing 26-50 of 59 flagged pages
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-11 06:20
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. All instructions for project creation, NuGet package installation, and tooling reference Visual Studio 2022 and the Package Manager Console (PowerShell-based), with no mention of Linux/macOS alternatives such as VS Code, JetBrains Rider, or command-line dotnet CLI usage. Steps for creating projects and installing packages are exclusively described using Windows GUI and PowerShell tools, and Linux/macOS users are left to infer their own workflows. No explicit Linux/macOS instructions or screenshots are provided.
Recommendations
  • Add parallel instructions for Linux/macOS users, including project creation and package installation using the dotnet CLI (e.g., 'dotnet new console', 'dotnet add package ...').
  • Mention cross-platform editors like VS Code or JetBrains Rider, and provide guidance for their use.
  • Include notes or tabs indicating which steps are platform-specific, and offer alternatives for non-Windows environments.
  • Provide screenshots or terminal examples for Linux/macOS where appropriate.
  • Clarify that the .NET SDK and Azure libraries work cross-platform, and link to relevant setup guides for Linux/macOS.
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-11 06:20
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 Resource Manager templates, with a detailed PowerShell script shown. While Azure CLI is mentioned, no explicit CLI example is given, and there are no Linux/macOS-specific instructions or screenshots. The PowerShell example is Windows-centric, and the CLI section lacks parity in detail. No Linux shell (bash/zsh) or macOS Terminal examples are present.
Recommendations
  • Add explicit Azure CLI example commands for configuring IP firewall rules, including full command syntax and output.
  • Ensure CLI examples are shown before or alongside PowerShell examples to avoid Windows-first ordering.
  • Include notes or instructions for Linux/macOS users, such as differences in CLI usage, authentication, or environment setup.
  • Provide screenshots or terminal output from Linux/macOS environments where relevant.
  • Clarify that PowerShell examples are primarily for Windows, and offer bash/zsh equivalents if possible.
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-11 06:20
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 (commonly associated with Windows) and recommends using Fiddler, a Windows-centric tool, to verify TLS usage. There are no examples or verification instructions for Linux/macOS users, nor are cross-platform tools mentioned.
Recommendations
  • Add code samples for other platforms and languages commonly used on Linux/macOS (e.g., Python, Java, 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 Linux/macOS users.
  • Reorder or supplement tool recommendations so that cross-platform options are listed alongside or before Windows-only tools.
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 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by exclusively referencing .NET-based sample code (DotNet), which is most commonly associated with Windows environments. There are no Linux/macOS-specific examples, nor are there mentions of cross-platform tools or SDKs (such as Python, Java, or CLI) that are popular on non-Windows systems. The absence of Linux/macOS command-line or code samples may create friction for users on those platforms.
Recommendations
  • Include sample code and usage instructions for other popular cross-platform SDKs, such as Python, Java, and JavaScript.
  • Provide explicit instructions or examples using the Azure CLI and REST API, which are platform-agnostic.
  • Add notes or sections highlighting how Linux/macOS users can perform equivalent tasks, including authentication and role assignment.
  • Ensure that links to sample code repositories include examples for multiple languages and platforms, not just .NET.
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-11 06:20
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 managing SAS authorization policies, but only explicitly references PowerShell (a Windows-centric tool) in the main text. There are no examples or instructions for Linux/macOS users, nor is Azure CLI usage demonstrated, which may create friction for non-Windows users.
Recommendations
  • Add explicit examples using Azure CLI for managing SAS policies, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
  • Avoid mentioning PowerShell exclusively; when referencing management tools, list Azure CLI first or alongside PowerShell.
  • Include notes or links for Linux/macOS users on how to perform equivalent operations.
  • Ensure that all code snippets and instructions are platform-neutral or provide alternatives for each major OS.
GitHub Create Pull Request
Event Hubs Azure Event Hubs Dedicated Tier Overview ...n/articles/event-hubs/event-hubs-dedicated-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page references the use of 'nslookup' with an example targeting a Windows-style namespace ('ns.servicebus.windows.net'), and mentions checking Azure Resource Manager properties via the portal, Azure CLI, or PowerShell. The example and tool references are Windows-centric, with no explicit mention of Linux/macOS equivalents or examples. The documentation does not provide Linux/macOS-specific instructions or examples, and the order of tool mentions (portal, CLI, PowerShell) subtly prioritizes Windows environments.
Recommendations
  • Provide explicit Linux/macOS command examples alongside Windows ones (e.g., show nslookup usage on Linux/macOS).
  • Clarify that Azure CLI is cross-platform and provide example commands for Linux/macOS users.
  • Avoid Windows-centric namespace examples; use neutral or cross-platform examples.
  • Mention alternative tools for DNS lookup (e.g., dig) commonly used on Linux/macOS.
  • Ensure parity in instructions for checking cluster properties, including steps for Linux/macOS users.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias by listing Windows/Azure PowerShell instructions before Linux/Azure CLI equivalents in the prerequisites section. The sample code and tooling are .NET/C#, which are cross-platform but traditionally associated with Windows development. There are no explicit Linux/macOS-specific examples, nor is there guidance for Linux users regarding environment setup or alternative authentication flows.
Recommendations
  • Present Azure CLI instructions before or alongside PowerShell instructions to avoid Windows-first ordering.
  • Explicitly mention that .NET Core and Azure SDKs are cross-platform, and provide setup instructions for Linux/macOS environments.
  • Include sample code snippets or shell commands demonstrating usage on Linux/macOS (e.g., bash scripts for authentication).
  • Add a note clarifying that all management operations can be performed from Linux/macOS as well as Windows.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation relies exclusively on Azure PowerShell examples for deploying, validating, and cleaning up resources, with no Azure CLI or Bash examples provided. This creates friction for Linux/macOS users who typically use Azure CLI or Bash, and may not have PowerShell installed or prefer not to use it. The only command-line instructions are PowerShell-based, and there is no mention or demonstration of Linux-native tools or workflows.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell scripts, covering deployment, validation, and cleanup.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
  • Ensure that Linux/macOS users are guided to install and use Azure CLI if they prefer.
  • Present CLI/Bash examples before or alongside PowerShell examples to avoid implicit Windows-first bias.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, primarily through the exclusive use of PowerShell for command-line examples and deployment instructions. There are no Bash or Linux/macOS shell equivalents provided, and PowerShell commands are presented as the default and only option for scripting and automation tasks. This creates friction for Linux/macOS users who may prefer or require Bash/CLI workflows.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all PowerShell examples, especially for resource deployment and access policy management.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Reorder examples to show CLI/Bash first or side-by-side with PowerShell, or use tabbed code blocks for both.
  • Clarify any platform-specific requirements or limitations for the commands given.
  • Add notes or links to official Azure CLI documentation for each major step.
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
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. The PowerShell example is presented first, suggesting a Windows-centric approach. PowerShell is a Windows-specific tool, and its prominence may disadvantage Linux/macOS users. While the Azure CLI example is provided (which is cross-platform), the ordering and emphasis on PowerShell, as well as references to Windows-specific SDKs (.NET/WindowsAzure.ServiceBus), reinforce a Windows-first perspective. No Linux shell (bash) or macOS-specific examples are given, and there is no explicit mention of platform differences or parity.
Recommendations
  • Present CLI (az) examples before PowerShell, as CLI is cross-platform.
  • Add bash or shell script examples for Linux/macOS users.
  • Explicitly state platform compatibility for each method.
  • Include notes or links for Linux/macOS users regarding installation and usage of Azure CLI.
  • Reference cross-platform SDKs and avoid highlighting Windows-only SDKs unless necessary.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. In the 'Manual failover' section, the order of examples is Azure Portal, Azure CLI, Azure PowerShell, and C#. PowerShell is highlighted as a primary automation method, and C# (commonly used on Windows) is provided as a code sample. While Azure CLI is cross-platform and listed before PowerShell, there are no explicit Linux/macOS shell examples (e.g., Bash scripts), nor are there references to Linux-specific tooling or workflows. The screenshots and UI instructions are based on the Azure Portal, which is platform-agnostic, but the automation examples lean toward Windows-centric tools.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users, especially for automation tasks.
  • Clarify that Azure CLI commands work on all platforms and provide sample usage in Bash.
  • Include references to Linux/macOS environments in automation and scripting sections.
  • Balance code samples by providing Python or Java examples, which are popular on Linux/macOS.
  • Ensure that PowerShell is not presented as the default or only scripting option for automation.
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-11 06:20
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 most commonly used in Windows environments. There are no examples, troubleshooting steps, or references for Linux/macOS users, nor is there mention of cross-platform SDKs or alternative programming languages. The guidance assumes use of Windows-centric tools and patterns, such as the Azure portal and .NET libraries, without acknowledging Linux or macOS workflows.
Recommendations
  • Include examples and exception handling guidance for cross-platform SDKs (e.g., Java, Python, Node.js) that are commonly used on Linux/macOS.
  • Explicitly state which guidance applies to Windows/.NET and provide equivalent documentation for Linux/macOS environments.
  • Add troubleshooting steps and configuration instructions relevant to Linux/macOS users, such as command-line tools (az CLI), environment variables, and platform-specific error messages.
  • Reference cross-platform Event Hubs SDKs and their exception models.
  • Add a section clarifying platform support and differences in exception handling across operating systems.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists Azure PowerShell commands in a dedicated section and references PowerShell deployment instructions before or alongside Azure CLI, but does not provide explicit Linux/macOS shell examples or highlight cross-platform command-line parity. The CLI section is present but less detailed than PowerShell, and the deployment link for Resource Manager templates points to PowerShell instructions, which are Windows-centric. No Linux-specific tools or shell examples (e.g., Bash) are provided.
Recommendations
  • Add explicit Bash/Azure CLI examples for all command-line steps, with sample commands and expected output.
  • Ensure Azure CLI instructions are as detailed as PowerShell, including add/list/update/remove operations.
  • Include links to Azure CLI deployment instructions for Resource Manager templates, not just PowerShell.
  • Clarify that Azure CLI and PowerShell are cross-platform, and provide guidance for Linux/macOS users where relevant.
  • Consider ordering CLI instructions before PowerShell to avoid implicit Windows-first bias.
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-11 06:20
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 notable Windows bias. All CLI examples for creating and configuring private endpoints use Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples. The validation steps explicitly instruct users to create a Windows VM and use Windows-centric instructions, with no mention of Linux VM creation or Linux command-line usage. Windows tools and patterns are referenced exclusively, and Windows is presented first and solely in critical workflow sections.
Recommendations
  • Add Azure CLI (az) and Bash examples alongside PowerShell for all resource creation and configuration steps.
  • Include instructions for creating a Linux VM in the validation section, and provide Linux shell commands for DNS validation (e.g., nslookup, dig).
  • Ensure that screenshots and UI references are OS-neutral or show parity between Windows and Linux where relevant.
  • Explicitly mention that all steps can be performed from Linux/macOS environments using Azure CLI.
  • Where PowerShell is referenced, provide a note or link to equivalent Azure CLI documentation.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation references both Azure CLI and PowerShell for schema registry management, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is listed after CLI, which is cross-platform. There are no explicit Linux/macOS command-line examples, nor are Linux-native tools mentioned. The documentation does not provide shell script or bash examples, and does not clarify platform compatibility for the PowerShell instructions.
Recommendations
  • Add explicit Linux/macOS command-line examples using Azure CLI and bash.
  • Clarify that Azure CLI is cross-platform and recommend it as the default for non-Windows users.
  • If PowerShell is mentioned, note its availability on Linux/macOS, or provide equivalent bash examples.
  • Avoid listing Windows-specific tools (PowerShell) without Linux/macOS alternatives.
  • Consider adding a section on platform compatibility for all tools mentioned.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the section on checking the minimum required TLS version. It exclusively references ARMClient.exe (a Windows executable) and provides only PowerShell command examples for authentication, with no mention of Linux/macOS alternatives (such as Azure CLI, curl, or bash scripting). This may create friction for non-Windows users attempting to follow the instructions.
Recommendations
  • Provide equivalent instructions for Linux/macOS users, such as using Azure CLI (az account get-access-token) or curl for API requests.
  • Mention cross-platform tools (e.g., Azure CLI, REST API via curl) alongside ARMClient.exe.
  • Include bash or shell script examples for authentication and API querying.
  • Clarify that ARMClient.exe is Windows-only and suggest alternatives for other platforms.
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-11 06:20
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 a moderate Windows bias. Troubleshooting steps reference Windows-specific tools (psping.exe), provide only Windows/Powershell-centric command examples, and mention Windows tools before suggesting alternatives. There is no direct Linux/macOS equivalent command or example provided for key troubleshooting steps, such as checking dropped packets. This creates friction for Linux/macOS users who must infer or research their own solutions.
Recommendations
  • Provide Linux/macOS equivalents for all troubleshooting commands, e.g., show how to use 'nc', 'nmap', or 'hping3' to check TCP connectivity and dropped packets.
  • Include example commands for both Windows and Linux/macOS platforms side-by-side.
  • Mention cross-platform tools (e.g., Wireshark, curl, wget) first or equally, rather than Windows-only tools.
  • Clarify when a tool is Windows-only and suggest alternatives for other platforms.
  • Add explicit troubleshooting steps for Linux/macOS environments where relevant.
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-11 06:20
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 moderate Windows bias. Windows prerequisites (Docker Desktop, WSL) are listed first and in detail, with links pointing to Windows-specific installation guides. The main setup instructions for the automated script method begin with Windows/PowerShell steps, including explicit use of PowerShell and WSL, while Linux/macOS instructions are less detailed and appear after the Windows section. There is an explicit note about Windows file path conventions, but no equivalent guidance for Linux/macOS. No Linux/macOS-specific troubleshooting or alternative commands are provided, and the sample code references are .NET-focused, which is more common on Windows.
Recommendations
  • Provide Linux/macOS installation links for Docker Desktop and clarify any differences in setup.
  • Present Linux/macOS instructions before or alongside Windows instructions, ensuring parity in detail and clarity.
  • Include Linux/macOS-specific troubleshooting notes (e.g., permissions, file path conventions).
  • Offer examples using native Linux/macOS terminals and commands, not just PowerShell/WSL.
  • Balance sample code references with cross-platform language examples (e.g., Python, Java).
GitHub Create Pull Request
Event Hubs Authenticate an Application with Microsoft Entra ID to Access Event Hubs Resources ...b/main/articles/event-hubs/authenticate-application.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing the Azure portal (which is web-based but often associated with Windows workflows) and providing .NET (C#) and Java code samples, but does not include explicit Linux/macOS command-line examples or mention Linux-specific tools. The 'Related content' section lists Azure PowerShell before Azure CLI, which is more cross-platform and commonly used on Linux/macOS. There are no explicit Linux/macOS authentication or RBAC assignment walkthroughs, and no Bash or shell script examples.
Recommendations
  • Add explicit Linux/macOS command-line examples for authentication and RBAC assignment, using Azure CLI and Bash.
  • Ensure Azure CLI instructions are presented before or alongside PowerShell instructions, emphasizing cross-platform compatibility.
  • Include code samples in Python and other languages popular on Linux/macOS, and clarify that all steps can be completed on non-Windows platforms.
  • Mention that the Azure portal is accessible from any OS and clarify any platform-specific requirements for client libraries.
GitHub Create Pull Request
Event Hubs Configure properties for an Azure event hub .../articles/event-hubs/configure-event-hub-properties.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for configuring Event Hub properties, but the PowerShell section is given equal prominence to CLI, despite PowerShell being primarily a Windows tool. No Linux/macOS-specific tools or shell examples (e.g., Bash, scripting) are mentioned, and PowerShell is described without noting its cross-platform availability or alternatives. The order of sections places Azure CLI first, which is positive, but the PowerShell section may still suggest a Windows-centric approach.
Recommendations
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Note that PowerShell Core is available on Linux/macOS, or provide Bash/shell script equivalents where relevant.
  • Add explicit Linux/macOS usage notes or examples, such as running Azure CLI in Bash.
  • Consider de-emphasizing PowerShell unless there are unique features not available in CLI.
GitHub Create Pull Request
Event Hubs SAS Authentication for Azure Event Hubs Resources ...les/event-hubs/authenticate-shared-access-signature.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides code examples for generating SAS tokens in multiple languages, including PowerShell and Bash. However, PowerShell is presented as a distinct example, and Windows-centric tools (PowerShell, .NET, C#) are referenced before Linux equivalents (Bash). The Bash example is present, but appears after PowerShell, which may suggest a Windows-first approach. There is no mention of Linux-specific tools or patterns outside the Bash example, and disabling SAS authentication is described only via Azure Portal and ARM templates, which are cross-platform.
Recommendations
  • Present Bash/Linux examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Explicitly mention that Bash examples are suitable for Linux/macOS users and PowerShell for Windows users.
  • Include references to Linux/macOS tools (e.g., curl, openssl, jq) in context, and clarify installation requirements.
  • Add a note about cross-platform support for SDKs and authentication methods.
  • Where possible, provide parity in step-by-step instructions for both Windows (PowerShell) and Linux/macOS (Bash/CLI).
GitHub Create Pull Request
Event Hubs Azure Event Hubs Dedicated Tier Overview ...n/articles/event-hubs/event-hubs-dedicated-overview.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. The only command-line example given is 'nslookup ns.servicebus.windows.net', which uses a Windows-centric namespace and does not mention Linux/macOS equivalents or syntax. The reference to PowerShell in the Azure Resource Manager section places Windows tooling before Linux alternatives (Azure CLI), and no explicit Linux/macOS examples or guidance are provided for cluster management or command-line operations.
Recommendations
  • Provide explicit Linux/macOS command-line examples alongside Windows ones, e.g., show 'nslookup' usage on Linux/macOS and clarify any syntax differences.
  • Mention Azure CLI as an alternative to PowerShell for Resource Manager property checks, and provide example commands for both.
  • Avoid using Windows-centric namespaces in examples (e.g., 'servicebus.windows.net') without clarifying that the commands work cross-platform.
  • Add a section or note confirming that all management operations (portal, ARM templates, CLI, PowerShell) are supported on Linux/macOS, and link to relevant cross-platform documentation.
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
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents the PowerShell (Windows-centric) method first when describing how to update partition count, followed by the Azure CLI (cross-platform) and Resource Manager template methods. While CLI and template approaches are platform-agnostic, the ordering and explicit PowerShell example indicate a mild Windows bias. No Linux/macOS-specific tools or shell examples are provided, but Linux users can use the CLI and Kafka tools without issue.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly mention that Azure CLI and Kafka tools work on Linux/macOS, and provide example commands for Bash/zsh where relevant.
  • Consider adding a short note or section for Linux/macOS users, confirming parity and listing supported tools.
  • If possible, include screenshots or terminal output from Linux environments to reinforce cross-platform support.
GitHub Create Pull Request
Event Hubs Quickstart: Create an event hub with consumer group using Bicep - Azure Event Hubs ...les/event-hubs/event-hubs-bicep-namespace-event-hub.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, validation, and cleanup tasks. However, PowerShell (a Windows-centric tool) is presented alongside CLI in all sections, and some linked images reference PowerShell specifically. The order of presentation sometimes places PowerShell examples immediately after CLI, and the 'Next steps' section references .NET Core first, which is traditionally Windows-focused, though cross-platform now. There are no Linux-specific tools or shell examples (e.g., Bash), nor explicit mention of Linux/macOS environments, but the use of Azure CLI ensures basic parity.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS as well as Windows.
  • Add Bash shell examples where relevant, especially for file operations.
  • Clarify that PowerShell Core is cross-platform, or note that PowerShell examples are for Windows unless otherwise specified.
  • Include screenshots or references for Linux/macOS environments, not just PowerShell.
  • Consider listing CLI examples first, as CLI is more universal across platforms.
GitHub Create Pull Request
Event Hubs Govern resources for client applications with application groups ...cles/event-hubs/resource-governance-with-app-groups.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides full parity across Azure Portal, Azure CLI, PowerShell, and ARM template methods for all major tasks. However, PowerShell examples and references are given equal prominence to CLI, and in some sections (such as 'Enable or disable an application group'), PowerShell is listed before ARM templates. PowerShell is a Windows-centric tool, and its heavy inclusion may signal a slight Windows bias. There are no missing Linux examples, as Azure CLI is cross-platform and always included. No Windows-only tools or patterns are present.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider listing Azure CLI examples before PowerShell in all sections to emphasize Linux parity.
  • Add brief notes for Linux/macOS users, such as shell syntax differences if relevant.
  • Where PowerShell is referenced, clarify that it is available on Linux/macOS (if true), or suggest CLI as the preferred method for non-Windows users.
GitHub Create Pull Request
← Previous Page 2 of 3 Next →