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 201-211 of 211 flagged pages
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While the main authentication and RBAC concepts are platform-neutral, the 'Related content' section lists Azure PowerShell before Azure CLI, and PowerShell is a Windows-centric tool. There are no explicit Linux/macOS examples or screenshots, and sample code references are mostly for .NET (commonly associated with Windows) and Java, with no mention of Linux-specific workflows or tools. The Azure portal is referenced for role assignment, which is cross-platform, but command-line alternatives are not shown in the main flow.
Recommendations
- Add explicit Linux/macOS examples, such as using Azure CLI for role assignments and authentication.
- Present Azure CLI examples before or alongside PowerShell to avoid Windows-first impression.
- Include sample code or links for Python or other languages popular on Linux.
- Add notes or screenshots showing cross-platform compatibility where relevant.
- Clarify that all steps can be performed on Linux/macOS, not just Windows.
Create Pull Request
Event Hubs
Configure properties for an Azure event hub
.../articles/event-hubs/configure-event-hub-properties.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for configuring Event Hub properties, but PowerShell (a Windows-centric tool) is given its own dedicated section and is described in detail. The ordering places Azure CLI first, which is cross-platform, but the presence of a separate PowerShell section and the lack of Linux-specific notes or examples (e.g., bash scripting, Linux shell usage) creates a subtle Windows bias. There are no explicit Windows-only tools or instructions, but the documentation assumes familiarity with PowerShell and does not mention Linux/macOS alternatives or considerations.
Recommendations
- Add explicit notes that Azure CLI is cross-platform and works on Linux/macOS/Windows.
- Include bash or shell scripting examples for Linux/macOS users where appropriate.
- Clarify that PowerShell Core is available cross-platform, or link to installation instructions for non-Windows systems.
- Consider adding a section for Linux/macOS users, highlighting any differences or best practices.
- Ensure parity in detail and troubleshooting for both CLI and PowerShell instructions.
Event Hubs
Azure Event Hubs Dedicated Tier Overview
...n/articles/event-hubs/event-hubs-dedicated-overview.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias in its use of example commands and terminology. The only command-line example given is 'nslookup ns.servicebus.windows.net', which uses a Windows-centric namespace ('windows.net') and does not clarify cross-platform usage. Additionally, the mention of PowerShell as a way to check Azure Resource Manager properties appears before Linux alternatives (Azure CLI), and the documentation refers to the Azure portal and ARM templates without highlighting Linux/macOS parity or CLI-first workflows.
Recommendations
- Provide explicit Linux/macOS examples for command-line operations, such as 'nslookup' and Azure CLI commands.
- Clarify that 'nslookup' and other commands are available on Linux/macOS, and provide sample outputs for those platforms.
- Mention Azure CLI as a primary cross-platform tool before PowerShell, or present both options equally.
- Avoid using Windows-centric namespaces in examples unless necessary, or provide Linux/macOS equivalents.
- Add a section or note on cross-platform management and automation options for Event Hubs clusters.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and managing resources. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is referenced throughout, including in cleanup and validation steps. Additionally, references to PowerShell-specific tutorials and images are present. While Azure CLI is cross-platform and shown first in each example, the consistent inclusion of PowerShell may suggest a slight Windows bias, especially for users on Linux/macOS who are less likely to use PowerShell.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider moving PowerShell examples to a separate section or after CLI examples to reinforce CLI as the default for non-Windows users.
- Add explicit notes or links for Linux/macOS users, such as installation instructions for Azure CLI.
- Remove or minimize references to PowerShell-specific images unless they are essential.
- Ensure that all referenced tutorials and next steps are equally accessible from Linux/macOS environments.
Event Hubs
Govern resources for client applications with application groups
...cles/event-hubs/resource-governance-with-app-groups.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parity between Azure Portal, Azure CLI, PowerShell, and ARM template examples for all major tasks. However, PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool, which may create friction for Linux/macOS users. Additionally, PowerShell examples are sometimes presented before ARM templates, and the documentation references PowerShell modules and commands without noting cross-platform alternatives or limitations. There is no explicit mention of Windows-only tools, but the presence and prominence of PowerShell can be considered a mild Windows bias.
Recommendations
- Clarify that Azure PowerShell is available cross-platform via PowerShell Core, or recommend using Azure CLI for Linux/macOS users.
- Where PowerShell is mentioned, add notes about installation and usage on non-Windows platforms.
- Consider listing Azure CLI examples before PowerShell, as CLI is natively cross-platform.
- Add explicit statements that all shown commands (CLI, PowerShell, ARM) work on Linux/macOS unless otherwise noted.
- Provide links or brief instructions for installing Azure CLI and PowerShell on Linux/macOS.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/transport-layer-security-enforce-minimum-version.md
...bs/transport-layer-security-enforce-minimum-version.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific configuration or command-line examples. However, it also does not include any Windows- or PowerShell-specific instructions, nor does it mention Windows tools or patterns. The absence of any CLI or scripting examples means there is no explicit Windows bias, but there is also a missed opportunity to provide parity for Linux users (e.g., Azure CLI or Bash examples).
Recommendations
- Add examples for configuring the minimum TLS version using cross-platform tools such as Azure CLI, which works on both Windows and Linux.
- If PowerShell examples are added in the future, ensure equivalent Azure CLI or Bash examples are provided alongside.
- Explicitly mention that the configuration steps can be performed from any OS using supported tools (Azure Portal, Azure CLI, REST API, etc.).
- Include troubleshooting steps or verification commands that can be run from both Windows and Linux environments.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-python-get-started-send.md
...icles/event-hubs/event-hubs-python-get-started-send.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation exhibits a mild 'windows_first' bias by consistently referring to 'command prompt' and recommending Visual Studio Code, both of which are more closely associated with Windows environments. However, all code and CLI instructions are cross-platform, and there are no PowerShell-specific commands or Windows-only tools. No Linux-specific examples or terminal references are provided, and the language assumes a Windows-centric workflow.
Recommendations
- Replace references to 'command prompt' with 'terminal' or 'command-line interface' to be more platform-neutral.
- When instructing users to open a shell, mention both 'Command Prompt/PowerShell (Windows)' and 'Terminal (Linux/macOS)'.
- Recommend Visual Studio Code as a cross-platform editor, but also mention other popular editors (e.g., PyCharm, Sublime Text, vim) without platform preference.
- Explicitly state that all CLI and Python commands work on Windows, Linux, and macOS.
- Consider including screenshots or terminal output from both Windows and Linux environments, or at least clarify that the instructions are platform-agnostic.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/authorize-access-event-hubs.md
...ain/articles/event-hubs/authorize-access-event-hubs.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page references Azure RBAC samples specifically in the context of .NET (a technology most commonly associated with Windows environments) and does not provide or mention equivalent Linux or cross-platform examples. There are no explicit Linux or cross-platform command-line examples, and the only sample link points to a Windows-centric technology stack.
Recommendations
- Include links to RBAC and authentication samples in other languages/platforms commonly used on Linux (e.g., Python, Java, Node.js).
- Explicitly mention that the concepts and APIs are cross-platform, and provide example commands or code snippets for both Windows (PowerShell/.NET) and Linux (Bash, Python, etc.).
- Add a section or note clarifying that all features are available on both Windows and Linux, and provide links to Linux-friendly tooling or documentation where appropriate.
- Ensure that sample repositories referenced in 'Next steps' include or point to Linux-compatible samples and instructions.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/enable-managed-identity.md
...ob/main/articles/event-hubs/enable-managed-identity.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation only provides instructions for enabling managed identity via the Azure portal, with no mention of command-line tools or scripts. There are no examples using Azure CLI, PowerShell, or other automation tools. However, the absence of CLI examples means there is no explicit Windows or PowerShell bias, but there is a lack of parity for Linux users who may prefer or require command-line instructions.
Recommendations
- Add step-by-step instructions for enabling managed identity using Azure CLI, which is cross-platform and widely used on Linux.
- If relevant, provide PowerShell examples alongside Azure CLI, but ensure CLI examples are given equal or higher prominence.
- Explicitly mention that the Azure portal is platform-agnostic, but highlight automation options for both Windows and Linux users.
- Include links to official Azure CLI and PowerShell documentation for further automation and scripting guidance.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-federation-configuration.md
...cles/event-hubs/event-hubs-federation-configuration.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not provide any platform-specific examples or instructions, but all linked sample repositories are .NET-based, which may implicitly favor Windows users. There are no explicit Linux or cross-platform instructions or examples.
Recommendations
- Include explicit instructions or examples for running the replication tasks on Linux (e.g., using .NET Core on Linux).
- Mention cross-platform compatibility of the provided samples, if applicable.
- Provide alternative examples or notes for users on macOS/Linux, such as command-line instructions or scripts.
- Highlight any platform-specific prerequisites or differences, if they exist.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/transport-layer-security-enforce-minimum-version.md
...bs/transport-layer-security-enforce-minimum-version.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or tooling instructions, but it also does not include any Windows- or Linux-specific commands, tools, or patterns. However, the absence of any example commands or configuration steps (for either Windows or Linux) means there is a missed opportunity to demonstrate parity or inclusivity for Linux users. The only minor indicator is the use of the endpoint 'yournamespace.servicebus.windows.net', which is Azure-specific but not inherently Windows-biased. No explicit Windows bias is present, but Linux users are not directly supported with examples.
Recommendations
- Add example commands for configuring the minimum TLS version using cross-platform tools such as Azure CLI (az), which works on both Windows and Linux.
- If showing PowerShell or Azure Portal steps, also include equivalent Azure CLI or REST API examples to ensure Linux parity.
- Explicitly mention that the configuration steps apply equally to Windows, Linux, and macOS environments when using cross-platform tools.
- If referencing troubleshooting steps (such as network tracing), suggest tools available on both Windows (e.g., Wireshark) and Linux (e.g., tcpdump, Wireshark).