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 176-200 of 211 flagged pages
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-storm-getstarted-receive.md
...cles/event-hubs/event-hubs-storm-getstarted-receive.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by using Windows-style path separators (backslashes) in the Maven command and by referencing Eclipse GUI steps without mentioning Linux alternatives or command-line options. There are no explicit Linux-specific instructions or examples, and the documentation does not clarify cross-platform compatibility or provide parity for Linux users.
Recommendations
- Provide both Windows and Linux/macOS command examples, especially for Maven commands (e.g., use forward slashes for Linux/macOS).
- Mention that Eclipse is available on multiple platforms, and consider including command-line alternatives for project creation (e.g., using 'mvn archetype:generate').
- Explicitly state that the instructions are cross-platform, or call out any platform-specific steps.
- Add notes or sections for common Linux development environments and tools (e.g., IntelliJ IDEA, VS Code, or command-line workflows).
- Ensure all file paths and configuration examples use platform-neutral syntax or provide both variants.
Create Pull Request
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-federation-patterns.md
.../articles/event-hubs/event-hubs-federation-patterns.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Azure DNS (which is tightly integrated with Azure and often managed via Windows-centric tooling) and by providing code and configuration examples that assume .NET and C# (which are historically more common on Windows). There are no explicit Linux or cross-platform command-line examples (e.g., Bash, curl, dig for DNS), nor are Linux-native tools or patterns mentioned. The only DNS client library referenced is DnsClient.NET, with no mention of Linux tools like dig or nslookup. No PowerShell is present, but the absence of Linux/Unix equivalents and the focus on .NET/C# patterns suggest a Windows-oriented perspective.
Recommendations
- Include Linux-native command-line examples for DNS operations, such as using 'dig' or 'nslookup' to query CNAME and SRV records.
- Mention cross-platform or Linux-friendly DNS client libraries (e.g., Python's dnspython, Node.js dns module) alongside DnsClient.NET.
- Provide code samples in additional languages popular on Linux (e.g., Python, JavaScript, Java) in addition to C#.
- Explicitly state that the patterns and techniques are platform-agnostic where possible, and highlight any platform-specific considerations.
- Reference Linux-based infrastructure options (e.g., hosting the failover file on an NGINX/Apache server) in the file-share failover section.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/apache-kafka-migration-guide.md
...in/articles/event-hubs/apache-kafka-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by referencing Azure portal UI patterns and domain names that are Windows-centric (e.g., *.servicebus.windows.net) without mentioning Linux tools or command-line alternatives. There are no examples or instructions for Linux users (e.g., using Azure CLI, shell commands, or Linux-based verification methods), and all post-migration verification is described via the Azure portal, which is platform-agnostic but often more familiar to Windows users. No PowerShell or explicit Windows-only tools are mentioned, but the absence of Linux-specific guidance or parity is notable.
Recommendations
- Add Linux command-line examples for creating namespaces and event hubs using Azure CLI.
- Include instructions for retrieving the connection string and FQDN using Azure CLI or az commands.
- Provide alternative post-migration verification steps using Azure CLI or REST API, not just the Azure portal.
- Explicitly mention that the instructions apply equally to Linux and macOS users, and provide shell command snippets where appropriate.
- If referencing domain names, clarify that these are not Windows-specific and apply to all platforms.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/authenticate-managed-identity.md
...n/articles/event-hubs/authenticate-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by linking to instructions for enabling managed identity specifically on Windows VMs, without mentioning or providing equivalent Linux VM instructions. Additionally, the sample application and walkthrough focus exclusively on .NET (ASP.NET Core) and do not provide Linux-oriented or cross-platform examples, nor do they reference Linux command-line tools or deployment scenarios.
Recommendations
- Include links and instructions for enabling managed identities on both Windows and Linux VMs, or reference a platform-agnostic guide.
- Provide sample applications or walkthroughs for Linux-based environments (e.g., using Python or Java on Linux App Service or VMs).
- Add examples or references for deploying and authenticating from Linux containers or command-line tools (such as Azure CLI on Linux).
- Ensure that sample code and deployment steps are not limited to Windows/.NET, but also cover other common stacks used on Linux.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/authenticate-application.md
...b/main/articles/event-hubs/authenticate-application.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing the Azure portal and .NET samples first, and by not providing explicit Linux or cross-platform command-line examples for authentication or role assignment. While it does mention Azure CLI in the related content, the main instructions and code samples focus on .NET (a Windows-centric technology) and the Azure portal, with no explicit Linux shell or cross-platform scripting examples. There are no PowerShell-heavy sections, but the absence of Linux-specific or cross-platform examples is notable.
Recommendations
- Include explicit Linux and cross-platform command-line examples (e.g., using Azure CLI in Bash) for key tasks such as application registration, role assignment, and token acquisition.
- Balance .NET code samples with equivalent samples in Python or JavaScript, which are widely used on Linux.
- When referencing the Azure portal, also provide CLI alternatives for users who prefer or require non-GUI workflows.
- Ensure that sample links and walkthroughs include Linux-friendly instructions and note any OS-specific requirements or differences.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-quickstart-stream-large-messages.md
...nt-hubs/event-hubs-quickstart-stream-large-messages.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by referencing the Azure portal and .NET SDK examples, which are more commonly associated with Windows environments. There are no Linux-specific instructions, command-line examples, or cross-platform SDK references (such as Python, Java, or CLI usage). No mention is made of Linux tools or workflows, and all example links and references are oriented toward Windows-centric development.
Recommendations
- Include examples and references for cross-platform SDKs, such as Python, Java, or Node.js, in addition to .NET.
- Provide instructions for configuring Event Hubs using the Azure CLI or Azure PowerShell, and clarify which commands work on Linux, macOS, and Windows.
- Add explicit guidance for Linux users, such as how to use the Azure portal or CLI from Linux systems.
- Balance references to .NET with equivalent links for other languages and platforms.
- Mention any platform-specific considerations (such as client configuration or environment setup) for Linux and macOS users.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/includes/event-hubs-connectivity.md
...rticles/event-hubs/includes/event-hubs-connectivity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides command-line instructions exclusively using Windows tools (nslookup from 'command prompt'), without mentioning or providing equivalent Linux/macOS commands or context. There are no PowerShell-specific commands, but the guidance assumes a Windows environment and omits Linux/Unix alternatives.
Recommendations
- For all command-line instructions (such as nslookup), explicitly mention that these commands are available on both Windows and Linux/macOS, or provide Linux/macOS shell equivalents (e.g., 'Run nslookup <namespace> from your terminal or command prompt').
- Where 'command prompt' is mentioned, clarify that this could be Windows Command Prompt, PowerShell, or a Unix shell (bash/zsh), and that the command works cross-platform.
- If there are any differences in output format or command usage between platforms, note them or provide example outputs for both Windows and Linux.
- Consider including a table or note listing common tools (e.g., nslookup, dig) and their availability on different operating systems.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-node-get-started-send.md
...rticles/event-hubs/event-hubs-node-get-started-send.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing 'Command Prompt' and showing a Windows-style command prompt path in example output, while not explicitly mentioning or illustrating Linux/macOS terminal usage. There are no Linux-specific instructions or screenshots, and the initial instruction to 'open a Command Prompt window' may confuse non-Windows users. However, the actual commands (npm, node) are cross-platform.
Recommendations
- Replace 'open a Command Prompt window' with 'open a terminal window' or mention both Command Prompt (Windows) and Terminal (Linux/macOS).
- Provide example terminal commands and output for both Windows and Linux/macOS (e.g., show both C:\... and ~/... paths).
- Include a note clarifying that all commands work on Windows, Linux, and macOS, and adjust screenshots or code blocks to reflect this parity.
- When referencing editors or tools, mention cross-platform options (e.g., 'such as Visual Studio Code, which is available on Windows, Linux, and macOS').
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/apache-kafka-migration-guide.md
...in/articles/event-hubs/apache-kafka-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates subtle Windows bias by referencing Azure portal workflows and domain names with a strong Windows association (e.g., *.servicebus.windows.net) and by omitting any Linux-specific or cross-platform command-line examples. There are no CLI or shell commands (such as Azure CLI or Bash), and all instructions assume use of the Azure portal, which is more familiar to Windows users. There are no references to Linux tools, nor are there any examples for Linux environments.
Recommendations
- Include Azure CLI and Bash command-line examples for creating namespaces, event hubs, and retrieving connection strings, alongside or before portal instructions.
- Mention Linux and macOS compatibility explicitly, and provide sample commands for those environments.
- When referencing domain names, clarify that the instructions apply equally to Linux and macOS users.
- Add verification steps using cross-platform tools (e.g., kafkacat, curl, or Azure CLI) instead of relying solely on the Azure portal.
- Ensure screenshots and walkthroughs are not portal-exclusive; include terminal-based alternatives.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/authenticate-managed-identity.md
...n/articles/event-hubs/authenticate-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by referencing Windows-specific resources (such as enabling managed identities on Azure VMs via a Windows-focused link) and providing only .NET/C# (commonly associated with Windows development) sample code. There are no explicit Linux or cross-platform command-line examples, nor are there instructions for enabling managed identities on Linux VMs or using Linux-native tools. The primary sample application is an ASP.NET Core web app, and while Java and Kafka samples are mentioned, they are only linked and not described in the main flow.
Recommendations
- Include explicit instructions and links for enabling managed identities on Linux VMs, not just Windows VMs.
- Provide sample code and walkthroughs for Linux-based environments, such as using Python or Java on Linux VMs or containers.
- Add command-line examples using Azure CLI (which is cross-platform) for key steps like enabling managed identities and assigning roles.
- Ensure that references to sample applications and code are balanced between Windows and Linux (e.g., include both .NET and Python/Java samples in the main text, not just in links).
- Mention Linux and cross-platform scenarios early in the documentation to signal parity and inclusivity.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates mild Windows bias by referencing Windows-centric tools and patterns first. For example, the use of 'nslookup' is illustrated with a Windows-specific namespace ('ns.servicebus.windows.net'), and the documentation refers to checking properties in the portal, Azure CLI, or PowerShell, listing PowerShell explicitly but not mentioning Linux shells or tools. There are no explicit Linux or cross-platform command examples, and no mention of Linux-specific tools or instructions.
Recommendations
- Provide command examples for both Windows (PowerShell/CMD) and Linux (Bash) environments when referencing tools like 'nslookup' or Azure CLI.
- When mentioning Azure CLI or scripting, clarify that it is cross-platform and provide example commands for both Windows and Linux shells.
- Avoid using Windows-specific namespaces or examples exclusively; include generic or Linux-relevant examples as well.
- Explicitly mention Linux and macOS compatibility where applicable, especially for management tools and command-line operations.
- Consider adding a section or callout noting that all features and management operations are supported on Linux, and provide links to Linux-specific documentation if available.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-federation-patterns.md
.../articles/event-hubs/event-hubs-federation-patterns.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by referencing .NET and C# code exclusively for all code examples, and by mentioning Windows-centric tools (such as DnsClient.NET) without Linux or cross-platform alternatives. There are no PowerShell-specific examples, but the lack of Linux or open-source tool examples (e.g., dig, nslookup, or Linux SDKs) and the absence of code samples in languages commonly used on Linux (such as Python or Java) indicate a lack of Linux parity.
Recommendations
- Provide equivalent code samples in cross-platform languages such as Python, Java, or Node.js, especially for event processing and DNS queries.
- When referencing DNS client libraries, mention and provide examples for Linux-friendly tools (e.g., dig, nslookup) and libraries (e.g., dnspython for Python, or Java DNS libraries).
- Explicitly state that the guidance and code samples are cross-platform where applicable, and note any platform-specific limitations.
- Include instructions or references for setting up and running the provided samples on Linux environments.
- Balance the documentation by alternating or combining Windows and Linux examples, ensuring both audiences are equally served.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-messaging-exceptions.md
...articles/event-hubs/event-hubs-messaging-exceptions.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation is focused exclusively on .NET Framework APIs and exception handling, which are primarily associated with Windows environments. There are no examples, notes, or references to Linux-specific usage, cross-platform .NET Core/.NET 5+ considerations, or command-line tools/environments outside of Windows. The documentation implicitly assumes a Windows-first context by referencing only Windows-centric APIs and tools, and by omitting any mention of Linux or cross-platform scenarios.
Recommendations
- Include notes or sections clarifying cross-platform support, especially for .NET Core/.NET 5+ users on Linux and macOS.
- Add examples or references for handling exceptions in cross-platform environments, including any differences in behavior or configuration on Linux.
- Mention any relevant Linux troubleshooting steps, such as checking systemd logs, network configuration, or environment-specific issues that may affect Event Hubs connectivity.
- If applicable, provide parity in documentation for command-line tools (e.g., Azure CLI, Bash scripts) that are commonly used on Linux, not just Windows or PowerShell.
- Explicitly state when guidance is Windows-specific, and provide equivalent guidance for Linux where differences exist.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-quickstart-stream-large-messages.md
...nt-hubs/event-hubs-quickstart-stream-large-messages.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by referencing the Azure portal and .NET SDKs, which are more commonly associated with Windows environments. There are no explicit examples or instructions for Linux users, such as command-line (CLI), Bash, or cross-platform SDKs (like Python or Java). The only SDK reference is for .NET, and the only example link is for .NET, omitting Linux-prevalent languages and tools.
Recommendations
- Include examples and links for cross-platform SDKs such as Python, Java, or Node.js, which are widely used on Linux.
- Provide instructions for configuring Event Hubs using the Azure CLI or Azure PowerShell (with clear cross-platform notes), not just the Azure portal.
- Add a section or note explicitly addressing Linux users, including any relevant differences or considerations.
- Reference SDK documentation for multiple languages, not just .NET, to ensure parity for Linux and non-Windows developers.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently refers to 'command prompt' and recommends Visual Studio Code, both of which are more closely associated with Windows environments. There are no explicit Linux or macOS terminal instructions, nor are there any bash- or shell-specific notes. All command-line instructions are generic and do not clarify cross-platform differences, potentially leading Linux users to assume Windows-centric defaults. No PowerShell-specific commands are present, but the lack of Linux-specific context or examples is a subtle form of bias.
Recommendations
- Explicitly mention that all command-line instructions work in Linux/macOS terminals as well as Windows command prompt.
- Where 'command prompt' is mentioned, add 'or terminal (Linux/macOS)' to clarify cross-platform applicability.
- Provide at least one example of running commands in a Linux/macOS terminal, such as using bash.
- When recommending editors, mention popular Linux/macOS editors (e.g., PyCharm, Sublime Text, vim) alongside Visual Studio Code.
- If there are any platform-specific considerations (e.g., differences in environment variable syntax, package installation, or permissions), call them out in notes or tips.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-quickstart-kafka-enabled-event-hubs.md
...hubs/event-hubs-quickstart-kafka-enabled-event-hubs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by instructing users to create a Windows virtual machine as a prerequisite, without mentioning Linux alternatives or providing Linux-specific instructions. All setup and configuration steps assume a Windows environment, and there are no examples or guidance for users on Linux systems.
Recommendations
- Include instructions for creating and configuring a Linux virtual machine as an alternative to Windows.
- Provide Linux-specific guidance for installing prerequisites such as JDK, Maven, and Git (e.g., using apt, yum, or other package managers).
- Ensure that all command-line instructions are cross-platform or provide both Windows and Linux command examples where differences exist.
- Mention that the Kafka client code and Event Hubs integration are platform-agnostic, and clarify any OS-specific steps.
- Update screenshots and portal instructions to indicate that managed identities and role assignments apply to both Windows and Linux VMs.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/sdks.md
...tDocs/azure-docs/blob/main/articles/event-hubs/sdks.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page exhibits a mild Windows bias, primarily by listing .NET (a Microsoft/Windows-centric technology) SDKs and tools first in all tables and sections, and by providing extra detail and historical context for .NET/Windows libraries. There is also mention of 'WindowsAzure.Messaging' and .NET Framework-specific packages, which are Windows-specific tools. However, there are no explicit PowerShell examples or exclusive Windows command-line instructions, and Linux/Java/Python/JavaScript/Go SDKs are also documented with parity in the main tables.
Recommendations
- Reorder SDK tables or alternate the order of language listings to avoid always placing .NET/.NET Framework first.
- Provide equivalent historical and technical context for non-Windows SDKs (e.g., Java, Python) in their own sections, not just for .NET.
- Clarify cross-platform compatibility for all SDKs, especially for .NET Standard libraries, and explicitly mention Linux/Mac support where applicable.
- Avoid using Windows-specific package names (like 'WindowsAzure.Messaging') in section headers or summaries unless absolutely necessary, and always provide cross-platform alternatives.
- Consider adding a brief statement at the top clarifying that all major SDKs are cross-platform unless otherwise noted.
Event Hubs
Geo-disaster recovery - Azure Event Hubs| Microsoft Docs
...ocs/blob/main/articles/event-hubs/event-hubs-geo-dr.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides platform-specific instructions for manual failover, listing Azure portal, Azure CLI, PowerShell, and C#. While Azure CLI is cross-platform, PowerShell is Windows-centric and is listed before C#. There are no explicit Linux/macOS shell examples (e.g., Bash), and no mention of Linux-specific tools or workflows. The ordering and inclusion of PowerShell may create minor friction for Linux/macOS users, though the CLI option is sufficient for most tasks.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS and provide example shell usage.
- Consider listing Azure CLI before PowerShell to emphasize cross-platform support.
- Add a Bash shell example for CLI usage, showing command execution and output.
- Clarify that PowerShell is optional and primarily for Windows users.
- Ensure parity in code samples and management instructions for Linux/macOS environments.
Event Hubs
Azure Event Hubs - Client SDKs | Microsoft Docs
...tDocs/azure-docs/blob/main/articles/event-hubs/sdks.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows a mild Windows bias, primarily in the .NET section. Windows-specific libraries (e.g., WindowsAzure.ServiceBus) are mentioned, and .NET Framework is referenced multiple times. However, the SDK tables and tutorials cover multiple languages/platforms, including Python, Java, JavaScript, and Go, which are cross-platform. There are no explicit PowerShell-only examples, and Linux/macOS users are not blocked from using the SDKs.
Recommendations
- Clarify that .NET Standard libraries are cross-platform and can be used on Linux/macOS.
- Avoid using Windows-specific package names (e.g., WindowsAzure.ServiceBus) in prominent positions unless necessary; provide context about platform compatibility.
- Add explicit notes or examples for Linux/macOS environments, especially in sections discussing .NET usage.
- Consider listing cross-platform SDKs before legacy Windows-only libraries.
- Where possible, link to tutorials or documentation that demonstrate usage on Linux/macOS.
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 after the CLI. There are no explicit Linux/macOS-specific instructions or examples, and the PowerShell section may imply a Windows-first audience. However, the CLI instructions are platform-neutral and presented first, mitigating the bias somewhat.
Recommendations
- Explicitly state that Azure CLI works on Linux/macOS and provide example commands run in Bash or zsh.
- Add a note clarifying that PowerShell Core is cross-platform, or provide instructions for running PowerShell on Linux/macOS if relevant.
- Consider including screenshots or references to Linux/macOS environments where appropriate.
- Ensure parity in troubleshooting steps or caveats for non-Windows users.
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 First
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias in its example for determining cluster type, where the 'nslookup' command is shown with a Windows-specific namespace (ns.servicebus.windows.net) and no explicit Linux/macOS example is provided. Additionally, PowerShell is mentioned as a tool for checking Azure Resource Manager properties, but alternatives like Azure CLI are only referenced in passing and not exemplified. No Windows-only tools or patterns are exclusively required, but the examples and terminology lean toward Windows-first usage.
Recommendations
- Provide explicit Linux/macOS command examples alongside Windows ones, e.g., show 'nslookup' usage in a Linux terminal.
- Include Azure CLI examples for checking cluster properties, not just PowerShell.
- Use neutral namespaces in examples (not 'servicebus.windows.net') or clarify that the commands work identically on Linux/macOS.
- Add notes or sections highlighting cross-platform compatibility for all commands and tools mentioned.
Event Hubs
Secure Azure Event Hubs Using Virtual Network Integration
...in/articles/event-hubs/event-hubs-service-endpoints.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions Azure PowerShell and Azure CLI as automation options, but PowerShell is referenced first in metadata and in the main text. The PowerShell section provides explicit command references, while the Azure CLI section is brief and lacks example commands. No Linux-specific tools or shell examples are given, and the CLI is not prioritized. However, the core instructions are platform-neutral (portal, ARM templates, REST API).
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, with equal detail and explicit command references.
- Include sample Azure CLI commands for adding, listing, updating, and removing network rules, similar to the PowerShell section.
- Clarify that Azure CLI works natively on Linux/macOS and highlight cross-platform usage.
- Avoid listing PowerShell first in metadata and main text unless justified by usage statistics.
- Consider adding Bash script snippets for common tasks to further support Linux users.
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 both Azure CLI and PowerShell examples for all major operations, but PowerShell examples are always present and detailed, and are shown before ARM template examples. There is no explicit mention of Linux/macOS-specific tools or shell environments, and no Bash or shell script examples. The CLI examples are present and correct, but PowerShell is given equal or greater prominence, which can be interpreted as a mild Windows bias.
Recommendations
- Add explicit Bash/shell script examples for Linux/macOS users where appropriate.
- Clarify that Azure CLI commands work cross-platform and highlight this fact.
- Consider listing CLI examples before PowerShell, as CLI is more universally available.
- Add notes or links for Linux/macOS users regarding installation and usage of Azure CLI.
- Review screenshots and UI instructions to ensure they do not assume Windows-only environments.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides step-by-step instructions for updating partition count in Azure Event Hubs, starting with a PowerShell example (Windows-centric), followed by Azure CLI and Resource Manager template methods. The PowerShell example is presented first, which may signal a Windows-first bias. There are no explicit Linux/macOS-specific instructions or examples, though the Azure CLI is cross-platform. No Linux shell (bash) or macOS Terminal examples are given, and no mention is made of platform-specific considerations for Linux/macOS users.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux/macOS and provide sample bash usage.
- Add a note clarifying platform compatibility for each method (PowerShell: Windows only; CLI: Windows, Linux, macOS).
- Include Linux/macOS-specific instructions or screenshots where relevant.
- Consider providing REST API or SDK-based examples, which are platform-agnostic.
Event Hubs
Azure Event Hubs - Client SDKs | Microsoft Docs
...tDocs/azure-docs/blob/main/articles/event-hubs/sdks.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page lists SDKs for multiple languages and platforms, but the .NET section and legacy package references show a bias toward Windows and .NET technologies. The .NET Framework and WindowsAzure.Messaging are highlighted, and .NET packages are described in more detail than other platforms. Windows-specific naming and legacy references are present, and .NET/Windows libraries are discussed first and at greater length than Linux/macOS equivalents.
Recommendations
- Add equivalent detail sections for other major platforms (Java, Python, JavaScript, Go), describing their client and management libraries.
- Avoid Windows-specific naming in headings and package lists unless necessary.
- Ensure examples and tutorials for Linux/macOS environments are equally visible and detailed.
- Present platform/language sections in a neutral order or rotate which is shown first.
- Explicitly mention cross-platform compatibility for all SDKs, not just .NET.