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 76-100 of 211 flagged pages
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-geo-dr.md
...ocs/blob/main/articles/event-hubs/event-hubs-geo-dr.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by listing Azure PowerShell as a primary management option, providing explicit PowerShell cmdlet references, and not including any Linux-specific shell or scripting examples. While Azure CLI is mentioned (which is cross-platform), there are no explicit Bash or Linux shell examples, and the ordering of examples (Portal, CLI, PowerShell, C#) places Windows-centric tools before cross-platform or Linux-native approaches. No Linux-specific tools, patterns, or troubleshooting steps are provided.
Recommendations
- Add explicit Bash/Linux shell examples for CLI commands, including sample scripts for common failover and management tasks.
- Ensure parity in example ordering: alternate or randomize the order of CLI and PowerShell, or explicitly note that CLI is cross-platform and suitable for Linux/macOS.
- Include troubleshooting or operational notes relevant to Linux environments (e.g., environment variables, authentication methods, file permissions).
- Reference Linux-native automation tools (such as shell scripts or Ansible) where appropriate.
- In code samples, provide both Windows and Linux command-line usage where differences exist.
Create Pull Request
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-resource-manager-namespace-event-hub.md
...ubs/event-hubs-resource-manager-namespace-event-hub.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong bias toward Windows and PowerShell usage. All command-line examples are provided exclusively in Azure PowerShell, with no Azure CLI (cross-platform) or Bash examples. The instructions for deploying, validating, and cleaning up resources rely solely on PowerShell scripts, which are more familiar to Windows users. There is no mention or example of using the Azure CLI, which is commonly used on Linux and macOS, nor are there Bash or shell script equivalents. This limits accessibility and parity for Linux and macOS users.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell scripts, including deployment, validation, and cleanup steps.
- Explicitly mention that Azure Cloud Shell supports both PowerShell and Bash, and show how to select the Bash environment.
- Include Bash script snippets where appropriate, especially for steps that involve scripting or automation.
- Reorder or parallelize instructions so that CLI/Bash and PowerShell examples are presented together, ensuring equal prominence.
- Link directly to Azure CLI documentation and reference pages, not just PowerShell resources.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/schema-registry-concepts.md
...b/main/articles/event-hubs/schema-registry-concepts.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing explicit PowerShell examples and references, while not offering equivalent Linux/bash examples. The CLI and PowerShell are both mentioned, but PowerShell is called out separately, and no bash or Linux shell examples are provided. This may make Linux users feel less supported or require them to adapt Windows-centric instructions.
Recommendations
- Add explicit bash/Linux shell examples alongside PowerShell for all management operations (such as adding a schema to a schema group).
- When referencing command-line tools, mention cross-platform options (e.g., Azure CLI) before platform-specific ones (e.g., PowerShell).
- Ensure that all sample links and instructions are clearly marked as cross-platform or provide separate instructions for Windows and Linux/macOS.
- Include a note clarifying the cross-platform nature of the Azure CLI and provide sample commands for Linux environments.
- Review all references to tools and scripts to ensure Linux users are not required to adapt Windows-specific instructions.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/private-link-service.md
.../blob/main/articles/event-hubs/private-link-service.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by providing only Azure PowerShell CLI examples for automation, omitting equivalent Azure CLI (cross-platform) or Bash examples. Additionally, the validation steps explicitly instruct users to create a Windows VM and do not mention Linux-based alternatives. This prioritizes Windows tools and workflows, making it less accessible for Linux or cross-platform users.
Recommendations
- Provide equivalent Azure CLI (az) and/or Bash script examples alongside PowerShell for all automation and resource creation steps.
- In the validation section, include instructions for creating and using a Linux VM, or at least mention that the nslookup command works identically on Linux and macOS.
- Where screenshots or step-by-step instructions reference Windows-specific UI or terminology, clarify that the process is similar for Linux-based resources.
- Explicitly state that the procedures are platform-agnostic where possible, and highlight any differences for Linux users.
- Consider including a table or toggle to switch between PowerShell and Azure CLI/Bash instructions.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/troubleshooting-guide.md
...blob/main/articles/event-hubs/troubleshooting-guide.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation shows a Windows bias by providing troubleshooting commands and tool recommendations that are primarily Windows-centric. The main example for checking dropped packets uses 'psping.exe', a Windows-only tool, and the command is shown in Windows shell syntax. Alternative tools are only mentioned generically ('tnc', 'ping'), with no concrete Linux equivalents or examples provided. There is no explicit Linux or cross-platform command shown for key troubleshooting steps.
Recommendations
- Provide equivalent Linux/macOS commands for each troubleshooting step, especially for checking connectivity (e.g., using 'nc', 'nmap', or 'curl' on Linux).
- Show both Windows and Linux/macOS command examples side by side where possible.
- Explicitly mention and link to cross-platform tools (e.g., 'nmap', 'netcat', 'curl') and provide usage examples.
- Avoid referencing only Windows-specific tools (like 'psping.exe') without Linux alternatives.
- Ensure that shell command syntax is shown for both Windows (PowerShell/cmd) and Linux (bash/zsh) environments.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-kafka-stream-analytics.md
...ticles/event-hubs/event-hubs-kafka-stream-analytics.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a mild Windows bias. In the section on running the Kafka producer, it specifically references 'On a Windows machine, when using a Node.js command prompt...' and does not provide equivalent instructions or notes for Linux or macOS users. The mention of 'Node.js command prompt' is a Windows-specific tool, and there are no Linux/macOS terminal instructions or clarifications. No PowerShell commands are present, but the guidance assumes a Windows environment for command execution.
Recommendations
- Provide explicit instructions or notes for Linux and macOS users alongside Windows instructions, especially for running Maven commands.
- Replace or supplement references to 'Node.js command prompt' with generic terminal/command-line instructions applicable to all platforms.
- Add a note clarifying that the provided shell commands (mvn clean package, mvn exec:java) work in any terminal (Windows Command Prompt, PowerShell, Linux/macOS Terminal, etc.).
- If there are any platform-specific steps (e.g., setting environment variables, path separators), document them for each OS.
- Review the documentation for any other implicit Windows assumptions and ensure parity for Linux/macOS users.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-dotnet-standard-getstarted-send.md
...ent-hubs/event-hubs-dotnet-standard-getstarted-send.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All instructions for project setup, package installation, and tooling reference Visual Studio 2022 and its GUI, with no mention of cross-platform alternatives like Visual Studio Code or command-line workflows. NuGet package installation is shown exclusively via the Visual Studio Package Manager Console (PowerShell), with no dotnet CLI examples. There are no Linux/macOS-specific instructions or screenshots, and the workflow assumes a Windows development environment throughout.
Recommendations
- Add instructions for creating and managing .NET projects using the dotnet CLI, which is cross-platform.
- Provide NuGet package installation commands using 'dotnet add package' alongside or instead of PowerShell/Package Manager Console examples.
- Mention and provide guidance for using Visual Studio Code or JetBrains Rider as alternative IDEs, especially for Linux/macOS users.
- Include notes or sections that clarify the steps are applicable on Linux/macOS, and highlight any OS-specific differences.
- Replace or supplement screenshots of Visual Studio with equivalent command-line instructions or screenshots from cross-platform editors.
- Explicitly state that the quickstart is cross-platform and provide parity in instructions for all supported operating systems.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/resource-governance-with-app-groups.md
...cles/event-hubs/resource-governance-with-app-groups.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides parity between Azure CLI and Azure PowerShell for most operations, but consistently lists and demonstrates PowerShell (a Windows-centric tool) before CLI, and includes detailed PowerShell scripting examples. There are no Linux-specific shell (e.g., Bash) or scripting examples, and no mention of Linux-native tools or workflows. The documentation assumes familiarity with PowerShell, which is more common on Windows, and does not address Linux users directly or provide guidance for Linux environments.
Recommendations
- Alternate the order of CLI and PowerShell examples, or list CLI (which is cross-platform) first to avoid implicit Windows prioritization.
- Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, and provide Bash shell examples where appropriate.
- Add a note or section for Linux users, highlighting any differences or tips for running these commands in Linux environments.
- Where PowerShell scripting is shown, consider providing equivalent Bash scripting examples for Linux users.
- Avoid assuming PowerShell as the default scripting environment; clarify that both CLI and PowerShell are supported and cross-platform where applicable.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/authenticate-shared-access-signature.md
...les/event-hubs/authenticate-shared-access-signature.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides code samples for multiple languages (NodeJS, Java, PHP, C#, PowerShell, Bash) when generating SAS tokens, which is positive for cross-platform parity. However, the PowerShell example appears before the Bash example, and the Bash example is provided last, which may indicate a subtle 'windows_first' ordering. The PowerShell example is also more detailed and uses Windows-specific .NET libraries, which may not be available or work the same way on Linux. There are no explicit Linux command-line (e.g., curl, openssl) examples outside of Bash, and no mention of Linux-specific tools or patterns. The documentation references Azure portal and ARM templates for configuration, which are cross-platform, but does not mention Azure CLI or other Linux-native tools for disabling SAS authentication. There is also a heavy focus on .NET/.NET samples in the 'Samples' section, with no direct links to Linux/JavaScript/Python samples.
Recommendations
- Reorder code samples so that Bash (or other cross-platform scripting languages) appear before PowerShell, or present them side-by-side to avoid implying a Windows-first approach.
- Provide explicit Linux command-line examples (e.g., using curl and openssl) for generating SAS tokens and authenticating, in addition to Bash functions.
- Include references to Azure CLI commands for configuration tasks (such as disabling SAS authentication), as Azure CLI is widely used on Linux.
- Add links to sample code repositories for non-.NET languages (e.g., Java, Python, Node.js) in the 'Samples' section to ensure parity.
- Where PowerShell is used, clarify if it is cross-platform (PowerShell Core) or Windows-only, and provide equivalent Bash or shell commands for Linux users.
- Mention Linux tools or patterns where appropriate, such as using jq, curl, or openssl, and ensure that all steps can be performed on both Windows and 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
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While it is mostly platform-neutral, it references Azure PowerShell before Azure CLI in the 'Related content' section, and the sample code and walkthroughs focus on .NET and Java, which are more commonly associated with Windows development environments. There are no explicit Linux or cross-platform command-line examples, and no mention of Linux-specific tools or workflows. The documentation does not provide parity in terms of Linux shell (bash) or cross-platform scripting examples for authentication or role assignment.
Recommendations
- Present Azure CLI examples before or alongside Azure PowerShell, as CLI is cross-platform and widely used on Linux.
- Include bash or shell script examples for authentication and role assignment to demonstrate Linux parity.
- Add explicit notes or sections on how to perform key steps (such as registering applications, assigning roles, and acquiring tokens) from Linux or macOS environments.
- Provide sample code or links for Python or Node.js SDKs, which are popular in Linux development, in addition to .NET and Java.
- Ensure that screenshots and walkthroughs do not assume a Windows environment (e.g., avoid showing only Windows-style file paths or UI).
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/authorize-access-azure-active-directory.md
.../event-hubs/authorize-access-azure-active-directory.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page does not provide explicit command-line examples for either Windows or Linux, but all code samples and references are exclusively to .NET (C#) libraries and samples, which are most commonly associated with Windows development environments. There are no Bash, Linux CLI, or cross-platform code examples, nor are there references to Linux-specific tools or workflows. The documentation also omits any mention of Linux authentication patterns (such as using Azure CLI in Bash) or cross-platform SDKs (like Python or Java), and all sample links point to .NET code.
Recommendations
- Add Linux/Bash command-line examples for authenticating and authorizing with Microsoft Entra ID (e.g., using Azure CLI in Bash).
- Include code samples in cross-platform languages such as Python, Java, or Node.js, not just .NET.
- Reference Linux tools and workflows (such as az CLI usage in Linux shells) alongside or before Windows/PowerShell equivalents.
- Provide explicit instructions or links for Linux users, including how to set up managed identities and assign roles from a Linux environment.
- Ensure that sample repositories include folders or instructions for non-Windows environments.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/authorize-access-shared-access-signature.md
...event-hubs/authorize-access-shared-access-signature.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by mentioning PowerShell and Azure CLI as configuration options, but listing PowerShell before Azure CLI and not providing any explicit Linux or cross-platform command-line examples. There are no Linux-specific instructions or examples, and the mention of PowerShell as a primary tool may alienate Linux users. The phrase 'via PowerShell or Azure CLI' puts the Windows tool first, and there is no parity in examples or guidance for Linux environments.
Recommendations
- When listing command-line tools, mention Azure CLI before or alongside PowerShell, as Azure CLI is cross-platform.
- Include explicit Linux/macOS examples or clarify that Azure CLI commands work on all platforms.
- Avoid assuming PowerShell as the default scripting environment; provide Bash or shell script examples where appropriate.
- Add a section or note for Linux users, highlighting any platform-specific considerations or steps.
- Ensure that all instructions and examples are equally accessible and relevant to both Windows and Linux users.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/configure-event-hub-properties.md
.../articles/event-hubs/configure-event-hub-properties.md
High Priority
View Details →
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 (a Windows-centric tool) is given a dedicated section and is mentioned alongside cross-platform tools. There are no explicit Linux shell or scripting examples, and the PowerShell section could be perceived as prioritizing Windows users. The GUI instructions also implicitly assume the Azure Portal, which is platform-agnostic but often associated with Windows workflows.
Recommendations
- Add explicit Linux/Bash shell examples for using the Azure CLI, including command-line snippets that demonstrate usage in a Linux environment.
- Clarify that Azure CLI is cross-platform and works on Windows, Linux, and macOS.
- Consider including examples for automation using Bash scripts or other Linux-native tools where appropriate.
- If mentioning PowerShell, also mention that PowerShell Core is available cross-platform, or provide equivalent Bash/Unix shell alternatives.
- Ensure that the order of examples does not always place Windows/PowerShell first; alternate or clarify cross-platform applicability.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/dynamically-add-partitions.md
...main/articles/event-hubs/dynamically-add-partitions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell as the first and most detailed example for updating partition counts, followed by the Azure CLI. PowerShell is a Windows-centric tool, and its prominence suggests a preference for Windows environments. There is no explicit Linux shell example (e.g., Bash), and the CLI example, while cross-platform, is not highlighted as such. Additionally, references to Windows-specific SDKs (e.g., WindowsAzure.ServiceBus) further reinforce the Windows bias.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Include Bash or shell script examples where appropriate, especially for automation scenarios.
- When referencing SDKs or libraries, avoid Windows-specific naming or clarify cross-platform support.
- Add a note or section for Linux users, highlighting any differences or additional steps required.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/configure-customer-managed-key.md
.../articles/event-hubs/configure-customer-managed-key.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a significant Windows/Powershell bias. Most command-line examples for deploying and configuring resources (such as deploying ARM templates, setting access policies, and retrieving identities) are provided exclusively using PowerShell, with no equivalent Azure CLI (bash/shell) examples. The instructions for running these commands assume a Windows environment, and there is no guidance for Linux or macOS users. While some sections mention that Azure CLI can be used, all concrete step-by-step examples default to PowerShell, and no bash/CLI scripts are shown for critical tasks. This may hinder Linux/macOS users or those who prefer cross-platform tooling.
Recommendations
- For every PowerShell example, provide an equivalent Azure CLI (bash/shell) example, especially for deployment, access policy, and identity management steps.
- When referencing command-line tools, mention both PowerShell and Azure CLI options, and do not assume a Windows environment.
- Where possible, use Azure CLI as the primary example, as it is cross-platform, or present CLI examples before PowerShell to avoid a 'Windows-first' impression.
- Explicitly state that all steps can be performed on Linux/macOS using Azure CLI, and provide links or code blocks for those workflows.
- Add a section or callout for Linux/macOS users, summarizing any differences or additional steps required.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-capture-python.md
.../main/articles/event-hubs/event-hubs-capture-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and patterns (such as 'command prompt', backslash path separators, and lack of Linux/MacOS terminal instructions). There are no explicit Linux or cross-platform instructions for running scripts or handling file paths, and all examples assume a Windows environment.
Recommendations
- Provide equivalent instructions for Linux and MacOS, such as using 'terminal' instead of 'command prompt', and show relevant shell commands.
- Use platform-agnostic path handling in code examples (e.g., os.path.join instead of hardcoded backslashes).
- Show both Windows and Linux/MacOS commands for installing dependencies and running scripts.
- Explicitly mention that the scripts are cross-platform and note any platform-specific considerations.
- Include screenshots or terminal output from Linux/MacOS environments where appropriate.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-management-libraries.md
...articles/event-hubs/event-hubs-management-libraries.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a Windows/.NET bias by providing only .NET (C#) code samples, referencing Windows-centric tools and workflows, and prioritizing Windows/PowerShell instructions for prerequisites. There are no examples or guidance for Linux users or for other programming languages/platforms commonly used on Linux.
Recommendations
- Add equivalent code samples in other languages/platforms commonly used on Linux, such as Python (using Azure SDK for Python) or Java.
- Include explicit instructions and examples for Linux environments, such as using Bash or Azure CLI for authentication and management tasks.
- Reorder or balance prerequisite instructions so that Azure CLI (cross-platform) is listed before or alongside Azure PowerShell.
- Clarify that the management libraries are currently only available for .NET, and provide alternative approaches for Linux users if possible (e.g., using REST API or Azure CLI for management tasks).
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-dotnet-standard-getstarted-send.md
...ent-hubs/event-hubs-dotnet-standard-getstarted-send.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All instructions for project creation, package installation, and tool usage are centered around Visual Studio 2022 and the NuGet Package Manager Console (PowerShell-based), with no mention of cross-platform alternatives like the .NET CLI or Visual Studio Code. There are no Linux or macOS-specific instructions or screenshots, and the workflow assumes a Windows/Visual Studio environment throughout.
Recommendations
- Add parallel instructions for Linux/macOS users, including steps for using the .NET CLI (e.g., 'dotnet new console', 'dotnet add package ...') for project creation and package management.
- Include guidance for using Visual Studio Code or JetBrains Rider, which are cross-platform IDEs.
- Replace or supplement Visual Studio-specific steps and screenshots with .NET CLI commands and generic editor instructions.
- Explicitly state that the .NET SDK and Azure SDK libraries are cross-platform, and provide any necessary notes for running on Linux/macOS (e.g., authentication differences, environment variables).
- Where PowerShell commands are shown, also provide Bash/zsh equivalents if applicable.
- Review all tool references (e.g., 'Tools > NuGet Package Manager > Package Manager Console') and ensure Linux/macOS users are not excluded from the workflow.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-exchange-events-different-protocols.md
...hubs/event-hubs-exchange-events-different-protocols.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows/.NET bias. While the article is cross-platform in its protocol focus (Kafka, AMQP, HTTPS) and provides both Java and C# (.NET) code samples, the .NET examples are consistently present and sometimes more detailed, especially in serialization/deserialization sections. There is an implicit assumption of .NET usage (e.g., references to BitConverter endianness on x86/x64, which is Windows-centric), and no Linux-specific considerations or examples are provided. There are no Linux shell or tool examples, and the .NET code is always C# (not F# or VB.NET, which are less common, but still Windows-centric). There is no mention of Linux-specific issues, tools, or patterns, and the .NET examples sometimes precede or are more detailed than their Java counterparts.
Recommendations
- Add explicit Linux/Unix examples or notes, especially where endianness or filesystem differences may matter.
- Include shell (bash) or Linux command-line examples for interacting with Event Hubs via HTTPS (e.g., using curl), not just code samples in Java or C#.
- Balance the depth and order of .NET and Java examples, ensuring neither is consistently prioritized.
- Mention cross-platform .NET Core/5+/6+ usage explicitly, rather than implicitly assuming Windows/.NET Framework.
- Where platform-specific behavior is discussed (e.g., endianness), clarify that .NET runs cross-platform and note any differences on Linux/macOS.
- Consider adding Python or other popular cross-platform language examples to further reduce perceived Windows bias.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-geo-dr.md
...ocs/blob/main/articles/event-hubs/event-hubs-geo-dr.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in its presentation of manual failover methods. In the 'Manual failover' section, the Azure portal (GUI), Azure CLI, PowerShell, and C# methods are listed, but there is no explicit mention of Linux-specific tools or scripting languages (e.g., Bash, Python). PowerShell is highlighted as a primary automation method, which is traditionally Windows-centric, and there are no Linux shell script or REST API examples. Additionally, the CLI example is generic and does not provide a full command-line walkthrough, and there are no Bash or cross-platform scripting examples. The documentation also lacks explicit mention of Linux environments or considerations for Linux administrators.
Recommendations
- Provide explicit Bash shell script examples for common operations (e.g., using Azure CLI in Bash for failover).
- Include REST API examples with curl commands to demonstrate cross-platform automation.
- Clarify that Azure CLI is fully supported on Linux and macOS, and provide sample commands in a Linux terminal context.
- Add Python or other cross-platform SDK examples alongside C#.
- Avoid listing PowerShell before CLI or cross-platform tools, or alternate the order to avoid implying preference.
- Explicitly mention that all operations can be performed from Linux/macOS as well as Windows, and provide links to relevant setup guides.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-ip-filtering.md
...ob/main/articles/event-hubs/event-hubs-ip-filtering.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing a detailed Azure PowerShell example for configuring firewall rules, while not offering equivalent command-line examples for Linux users (e.g., Bash or Azure CLI scripting). The PowerShell example is given its own section and is more comprehensive than the brief mention of Azure CLI. There is no explicit Linux/Bash example, and the CLI section lacks sample commands. The deployment instructions for ARM templates link to a PowerShell deployment guide, further reinforcing the Windows-centric approach.
Recommendations
- Add detailed Azure CLI examples for managing firewall rules, including sample commands for adding, listing, updating, and removing IP rules, similar in depth to the PowerShell example.
- Provide Bash scripting examples for ARM template deployment, or at least link to cross-platform deployment instructions (e.g., Azure CLI or Bash).
- Ensure that Azure CLI examples are presented before or alongside PowerShell examples to avoid the impression of Windows-first bias.
- Explicitly mention that all Azure CLI commands work cross-platform (Windows, Linux, macOS) to encourage non-Windows users.
- Where possible, include screenshots or references to command-line tools available on Linux/macOS, not just the Azure portal or PowerShell.
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
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits mild Windows bias. It instructs users to 'open a Command Prompt window' to install npm packages, and the sample output for running the receiver is shown with a Windows path prompt (e.g., 'C:\Self Study\Event Hubs\JavaScript>'). There are no explicit Linux/macOS terminal examples or mentions of common Linux shells (e.g., bash, zsh), and the guidance assumes familiarity with Windows tools and conventions.
Recommendations
- Replace 'open a Command Prompt window' with 'open a terminal window' or mention both Command Prompt (Windows) and Terminal (Linux/macOS).
- Provide sample commands and outputs using generic POSIX-style paths (e.g., '/home/user/EventHubs/JavaScript>') or show both Windows and Linux/macOS examples side by side.
- Explicitly state that the instructions apply to Windows, Linux, and macOS, and that Node.js/npm commands work the same way across platforms.
- Where IDEs are mentioned, note that Visual Studio Code is cross-platform, and users may use any editor or terminal of their choice.
- Avoid using Windows-specific path separators (\) in examples, or provide both Windows and Linux/macOS path formats.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-kafka-stream-analytics.md
...ticles/event-hubs/event-hubs-kafka-stream-analytics.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page shows a mild Windows bias. It specifically references running commands on a Windows machine and mentions using a 'Node.js command prompt' on Windows, but does not provide equivalent instructions or considerations for Linux or macOS users. There are no Linux-specific examples or notes, and the only environment-specific guidance is for Windows.
Recommendations
- Add explicit instructions for running the Java/Maven commands on Linux and macOS, including any differences in environment setup or command syntax.
- Replace or supplement references to 'Node.js command prompt' and 'Windows machine' with cross-platform alternatives, such as 'terminal' or 'command line interface', and clarify that the commands work on all major operating systems.
- Include a note or section confirming that the steps and commands are applicable to Linux/macOS, and mention any OS-specific prerequisites or troubleshooting tips.
- If screenshots or UI references are OS-specific, provide alternatives or clarify that the experience may differ on other platforms.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-resource-manager-namespace-event-hub.md
...ubs/event-hubs-resource-manager-namespace-event-hub.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong bias toward Windows and PowerShell usage. All command-line deployment, validation, and cleanup examples use Azure PowerShell exclusively, with no mention or example of Azure CLI, Bash, or other cross-platform tools. This leaves out Linux and macOS users who may prefer or require CLI-based instructions not tied to PowerShell.
Recommendations
- Add equivalent Azure CLI (az) examples for deployment, validation, and cleanup steps, ideally using Bash syntax.
- Present both PowerShell and CLI examples side-by-side or allow the user to select their preferred environment.
- Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
- Ensure that references to scripts, commands, and tooling are not exclusively PowerShell-centric, and avoid implying PowerShell is the default or only option.
- Consider including a table or toggle for users to choose between Windows/PowerShell and Linux/Bash/CLI instructions.
Event Hubs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-hubs/event-hubs-service-endpoints.md
...in/articles/event-hubs/event-hubs-service-endpoints.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell commands in a dedicated section after Azure CLI, without providing any Linux-specific or cross-platform command-line examples. The only explicit command-line examples are for Azure CLI and PowerShell, both of which are available on Windows, but PowerShell is traditionally associated with Windows environments. There are no Linux shell (bash) examples, and no mention of Linux-specific tools or workflows. Additionally, the 'Next steps' section links to PowerShell deployment instructions, reinforcing a Windows-centric approach.
Recommendations
- Provide explicit bash or Linux shell examples for all command-line operations, especially for Azure CLI usage.
- Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- Include links to Linux/macOS deployment guides alongside PowerShell guides in the 'Next steps' section.
- When listing command-line tools, present Azure CLI before PowerShell, or present them together with equal prominence.
- Add notes or examples for using Resource Manager templates with Linux-native tools (e.g., az deployment group create) rather than only referencing PowerShell deployment.