Event Grid
295
Total Pages
234
Linux-Friendly Pages
61
Pages with Bias
20.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
289 issues found
Showing 101-125 of 289 flagged pages
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/mqtt-certificate-chain-client-authentication.md
...t-grid/mqtt-certificate-chain-client-authentication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides certificate generation instructions and examples exclusively for Windows PowerShell, with no equivalent Linux or macOS command-line examples. The phrase 'Consider installing manually for Windows' suggests a Windows-first approach, and all command snippets are in PowerShell syntax. No Linux or cross-platform shell commands are provided, despite the step CLI being cross-platform.
Recommendations
- Provide equivalent Linux/macOS shell (bash) commands for certificate generation using step CLI.
- Explicitly mention that the step CLI works on all major platforms and link to installation instructions for Linux/macOS.
- Rephrase instructions to present cross-platform steps first, or at least in parallel, rather than focusing on Windows/PowerShell.
- Where possible, use generic command syntax or provide both PowerShell and bash examples side by side.
Create Pull Request
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/handler-service-bus.md
...s/blob/main/articles/event-grid/handler-service-bus.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 Service Bus queues and topics as event handlers for Azure Event Grid events. While Azure CLI is cross-platform, the inclusion of Azure PowerShell commands (which are most commonly used on Windows, despite cross-platform support) and the explicit labeling of 'Azure PowerShell' sections may signal a Windows-centric approach. Additionally, there are no Linux-specific shell examples (e.g., Bash scripts), and PowerShell examples are given equal prominence to CLI, which can be perceived as Windows bias. The documentation does not mention or provide guidance for Linux-native tools or scripting patterns.
Recommendations
- Add explicit Bash or shell script examples alongside Azure CLI to demonstrate Linux-native usage patterns.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and consider providing sample shell environments or notes for Linux users.
- If PowerShell is included, note that PowerShell Core is cross-platform, and provide installation or usage notes for Linux users.
- Consider the order of examples: present Azure CLI (cross-platform) before PowerShell, and make it clear that both are supported on all major OSes.
- Include troubleshooting or environment setup notes for Linux users where relevant, especially for authentication or identity scenarios.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/mqtt-topic-spaces.md
...ocs/blob/main/articles/event-grid/mqtt-topic-spaces.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing escaping instructions and examples specifically for PowerShell, without mentioning or providing equivalent guidance for Linux shells (such as Bash or Zsh). The special character escaping section is Windows/PowerShell-centric, and there are no Linux or cross-platform examples for handling topic template syntax in non-Windows environments.
Recommendations
- Add explicit instructions and examples for escaping special characters (such as $ and |) in common Linux shells (e.g., Bash, Zsh), alongside the existing PowerShell examples.
- Clearly label which examples are for PowerShell and which are for Linux/macOS shells to avoid confusion.
- Where possible, provide cross-platform examples or note any differences in behavior between Windows and Linux environments.
- Review other sections for implicit Windows-first assumptions and ensure parity in tooling and workflow descriptions for Linux users.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/scripts/powershell-webhook-secure-delivery-microsoft-entra-app.md
...powershell-webhook-secure-delivery-microsoft-entra-app.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively provides a PowerShell script for configuring secure webhook delivery with Microsoft Entra Application in Azure Event Grid. All examples and instructions are tailored to PowerShell, which is traditionally a Windows-centric tool, and there are no equivalent Bash, CLI, or Linux-native examples or guidance. The use of PowerShell modules and cmdlets (e.g., Get-MgServicePrincipal, New-MgServicePrincipal) further reinforces the Windows bias, and there is no mention of how to perform these steps using cross-platform tools or on Linux/macOS environments.
Recommendations
- Provide equivalent examples using Azure CLI (az) and Microsoft Graph CLI or REST API, which are cross-platform and commonly used on Linux/macOS.
- Explicitly mention that PowerShell Core is available cross-platform, if PowerShell must be used, and provide installation instructions for Linux/macOS.
- Add Bash script examples or step-by-step instructions for Linux users.
- Include a section comparing the different approaches (PowerShell, CLI, REST API) and when to use each.
- Ensure screenshots and portal instructions are not Windows-specific, and clarify that the Azure Portal is web-based and OS-agnostic.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/subscribe-to-resource-notifications-containerservice-events.md
...ribe-to-resource-notifications-containerservice-events.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and Azure Portal. However, there is a notable bias toward Windows environments: PowerShell is given equal prominence to Azure CLI, despite PowerShell being primarily a Windows-centric tool (even though cross-platform PowerShell Core exists, most users associate it with Windows). In several places, PowerShell examples are presented immediately after CLI, and there is no mention of Linux-specific shell usage, scripting, or troubleshooting. The document does not clarify that Azure CLI commands are cross-platform and suitable for Linux/macOS, nor does it provide any bash/zsh-specific guidance or highlight differences that Linux users might encounter. There are also no references to Linux-native tools or patterns.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and suitable for Linux, macOS, and Windows.
- Add bash/zsh shell examples or notes where relevant (e.g., multi-line commands, environment variable usage, quoting).
- Clarify that PowerShell examples are optional and primarily for users on Windows or those using PowerShell Core.
- Add troubleshooting notes for common Linux issues (e.g., line endings, path formats, CLI installation).
- Where scripting is shown, provide both PowerShell and bash script snippets to ensure Linux users are equally supported.
- Consider reordering tabs so that Azure CLI (the most cross-platform tool) appears first, and PowerShell is clearly marked as an alternative.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/subscribe-to-resource-notifications-health-resources-events.md
...ribe-to-resource-notifications-health-resources-events.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and the Azure portal. However, the inclusion of Azure PowerShell throughout, with detailed PowerShell command examples, introduces a Windows bias. PowerShell is primarily a Windows-native tool, and its prominence may disadvantage Linux users who are less likely to use PowerShell. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-native scripting or tooling. The CLI examples are cross-platform, but the documentation does not clarify this or provide Linux-specific guidance. The PowerShell sections are always present and sometimes precede the CLI sections, reinforcing the Windows-centric approach.
Recommendations
- Clarify that Azure CLI commands are fully cross-platform and provide explicit Bash or Linux terminal examples where appropriate.
- De-emphasize PowerShell as a primary automation tool unless specifically targeting Windows users; consider moving PowerShell sections after CLI sections or marking them as Windows-specific.
- Add notes or callouts for Linux/macOS users, such as any differences in CLI usage, environment setup, or authentication.
- If scripting examples are provided, include Bash scripts or references to shell scripting for Linux users.
- Review the order of sections to ensure CLI (cross-platform) instructions come before PowerShell (Windows-centric) instructions.
- Explicitly state that PowerShell examples are optional and primarily for users on Windows or those who have installed PowerShell Core on Linux/macOS.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/mqtt-certificate-chain-client-authentication.md
...t-grid/mqtt-certificate-chain-client-authentication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides certificate generation instructions and examples exclusively using Windows PowerShell, with explicit mention of Windows and no equivalent Linux/macOS commands or guidance. The only installation note for the step CLI is 'Consider installing manually for Windows,' with no mention of Linux or macOS. This creates a Windows-first impression and omits Linux parity for a common cross-platform task.
Recommendations
- Add Linux and macOS examples for generating certificates using the step CLI, including equivalent bash/zsh commands.
- Provide installation instructions or a link for step CLI on Linux and macOS, not just Windows.
- Avoid specifying 'in Windows PowerShell' unless also providing a Linux/macOS shell alternative.
- Where possible, use cross-platform command syntax or clearly separate instructions for each OS.
- Review screenshots and UI references to ensure they are not Windows-specific unless necessary.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/mqtt-publish-and-subscribe-cli.md
.../articles/event-grid/mqtt-publish-and-subscribe-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the certificate generation section, where only Windows-specific instructions and PowerShell commands are provided for using the step CLI. There are no equivalent Linux or macOS command-line examples, and the instructions reference opening a Command Prompt and using Windows environment variables. The .NET code sample also assumes usage in Visual Studio, a Windows-centric IDE, without mentioning cross-platform alternatives.
Recommendations
- Provide explicit Linux and macOS command-line examples for generating certificates with the step CLI, including terminal commands and file paths.
- Avoid referencing Windows-specific actions (e.g., 'Win+R type %USERPROFILE%') without cross-platform equivalents; instead, mention generic terminal navigation or provide alternatives for different OSes.
- Include instructions for running the .NET sample on Linux/macOS (e.g., using VS Code, JetBrains Rider, or the dotnet CLI) and clarify that the code is cross-platform.
- Where file paths are referenced, use cross-platform path examples or note the differences.
- If referencing IDEs or tools, mention cross-platform options and not just Visual Studio.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/mqtt-topic-spaces.md
...ocs/blob/main/articles/event-grid/mqtt-topic-spaces.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing special instructions and examples for escaping special characters in PowerShell, without mentioning or providing equivalent guidance for Linux shells (e.g., Bash). The only shell-specific examples are for PowerShell, and there is no discussion of how to handle these cases on Linux or macOS. This may confuse or disadvantage users on non-Windows platforms.
Recommendations
- Add equivalent examples and instructions for escaping special characters in common Linux shells (e.g., Bash, Zsh) and macOS.
- When discussing shell-specific behavior, present Linux/Bash guidance alongside or before PowerShell instructions to ensure parity.
- Explicitly state that the examples are for PowerShell and provide a clear section for Linux/macOS users.
- Consider including a table or side-by-side examples showing how to escape special characters in both PowerShell and Bash.
- Audit other sections for similar shell-specific instructions and ensure cross-platform coverage.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/authenticate-with-microsoft-entra-id.md
...les/event-grid/authenticate-with-microsoft-entra-id.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: it references enabling managed identities specifically on a Windows VM, provides detailed PowerShell examples for disabling local authentication, and does not provide equivalent Linux shell or cross-platform CLI examples for some operations. The Azure CLI example is present, but PowerShell is given a dedicated section and example, while Linux-specific instructions or screenshots are missing. There is also a lack of explicit Linux or cross-platform guidance for environment variable setup and SDK usage, with examples using Windows-centric tools and patterns.
Recommendations
- Add explicit Linux/Unix shell (bash) examples for all operations currently shown only in PowerShell, such as creating resources and setting environment variables.
- When referencing enabling managed identities, provide links and instructions for both Windows and Linux VMs, not just Windows.
- Ensure screenshots and portal instructions are not Windows-specific, or clarify that the UI is the same across platforms.
- In code samples that require environment variables (e.g., AZURE_CLIENT_ID), show both Windows (set in PowerShell/cmd) and Linux (export in bash) syntax.
- Review all tool references to ensure cross-platform parity, and avoid giving Windows tools or patterns prominence over their Linux equivalents.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/blob-event-quickstart-bicep.md
...ain/articles/event-grid/blob-event-quickstart-bicep.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides deployment instructions for both Azure CLI and Azure PowerShell, but the PowerShell example is given equal prominence to the CLI example, which may suggest a Windows-centric approach. There are no explicit Linux-specific instructions or examples, and the PowerShell tab may be confusing or irrelevant for Linux users. The documentation does not mention or link to Linux shell alternatives or clarify cross-platform compatibility for the CLI commands.
Recommendations
- Clearly indicate that Azure CLI commands are cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows (unless using PowerShell Core).
- List the Azure CLI example first, as it is the most cross-platform option, and consider making it the default tab.
- Add a note clarifying that Azure CLI works on Windows, Linux, and macOS, and provide installation links for each OS.
- If PowerShell is included, specify that it is for users who have PowerShell installed (Windows or PowerShell Core on Linux/macOS).
- Consider providing bash/zsh shell examples for Linux users, especially for common tasks like file upload to Blob storage.
- Explicitly mention that all steps (except PowerShell) are fully supported on Linux, and provide troubleshooting tips or links for Linux environments.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/cloud-event-schema.md
...cs/blob/main/articles/event-grid/cloud-event-schema.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 PowerShell examples alongside Azure CLI, referencing Visual Studio (a primarily Windows IDE) and its GUI workflows, and omitting explicit Linux or cross-platform alternatives (such as Bash scripting or VS Code on Linux). There are no Linux-specific instructions or examples, and Windows tools and patterns are mentioned first or exclusively.
Recommendations
- Provide Bash shell equivalents for all PowerShell examples, especially for variable assignment and command usage.
- When referencing IDEs, mention cross-platform options such as VS Code on Linux and Mac, and include instructions for those environments.
- Avoid assuming the use of Windows tools (e.g., Visual Studio, Solution Explorer) as the default; instead, present VS Code or CLI-based workflows first or equally.
- Explicitly state that the Azure CLI commands work on all platforms, and provide examples of running them in Bash or other common Linux shells.
- Include a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/configure-private-endpoints.md
...ain/articles/event-grid/configure-private-endpoints.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides comprehensive coverage for both Azure CLI and PowerShell, but the PowerShell section is notably detailed and includes full sample scripts, which may favor Windows users. PowerShell is a Windows-centric tool, and its inclusion as a primary automation method can be seen as a Windows bias. The documentation does not mention or provide examples for Linux-native scripting environments (such as Bash), nor does it clarify cross-platform PowerShell Core compatibility. The order of presentation (CLI before PowerShell) is good, but the heavy PowerShell focus and lack of Linux-native examples indicate some Windows bias.
Recommendations
- Add explicit Bash shell script examples for Linux/macOS users, especially for automation scenarios.
- Clarify that Azure CLI commands work cross-platform and can be run in Bash, Zsh, or other Linux shells.
- If PowerShell examples are included, specify whether they are compatible with PowerShell Core (cross-platform) or only Windows PowerShell.
- Consider including a section or note for Linux users, highlighting any differences or prerequisites.
- Ensure parity in the depth and complexity of examples between CLI and PowerShell sections.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/delivery-and-retry.md
...cs/blob/main/articles/event-grid/delivery-and-retry.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation references both Azure CLI and PowerShell for configuring retry policies and batching, but it consistently lists PowerShell alongside CLI, and refers to 'PowerShell command' without clarifying cross-platform support. The only explicit command-line example provided is for Azure CLI, which is cross-platform, but references to PowerShell are present without corresponding Linux shell (bash) or scripting examples. There are no explicit Linux- or macOS-specific instructions, nor are there any bash or shell script examples. The documentation does not mention platform-specific differences, but the pattern of referencing PowerShell and CLI together, and the absence of Linux-specific examples or notes, suggests a subtle Windows-first bias.
Recommendations
- When referencing PowerShell, clarify that Azure PowerShell is cross-platform, or provide equivalent bash/shell examples where appropriate.
- Include explicit bash or shell script examples for common Linux/macOS usage scenarios, especially where PowerShell is mentioned.
- When linking to further documentation (e.g., 'Set retry policy'), ensure that both PowerShell and bash/CLI examples are present and equally prominent.
- Avoid phrasing such as 'CLI and PowerShell' as the only options; mention bash/shell scripting or note that Azure CLI works on all platforms.
- Add a note or section on platform compatibility for all command-line tools referenced, making it clear that Linux/macOS users are equally supported.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/custom-event-to-function.md
...b/main/articles/event-grid/custom-event-to-function.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. While it does provide Azure CLI and cURL examples (which are cross-platform), it consistently references Windows-centric tools and workflows first, such as Visual Studio Code with .NET/C#, and provides detailed Azure PowerShell instructions. The PowerShell example is given equal prominence to the CLI example, and the workflow assumes familiarity with Visual Studio Code and the Azure portal, both of which are more commonly used on Windows. There are no explicit Linux-specific instructions, troubleshooting tips, or alternative editors/IDEs mentioned.
Recommendations
- Add explicit Linux/macOS instructions or notes, especially for environment setup and tool installation.
- Include examples using other popular languages and runtimes (such as Python or Node.js) that are commonly used on Linux.
- Mention alternative editors (such as Vim, Emacs, or JetBrains IDEs) or at least clarify that Visual Studio Code is cross-platform.
- Provide troubleshooting tips for Linux users (e.g., file permissions, shell differences).
- Clarify that both Azure CLI and cURL commands work natively on Linux/macOS, and provide any necessary adjustments (such as date command syntax differences).
- Consider adding a section or callout for Linux users to ensure parity and inclusivity.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/event-grid-dotnet-get-started-pull-delivery.md
...nt-grid/event-grid-dotnet-get-started-pull-delivery.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE), using only PowerShell commands for package installation, and providing step-by-step instructions and screenshots that assume a Windows environment. There are no instructions or examples for Linux or cross-platform .NET development tools (such as VS Code, JetBrains Rider, or the .NET CLI), nor are alternative package installation methods (like 'dotnet add package') shown. This may hinder accessibility for Linux and macOS users.
Recommendations
- Add instructions for using the .NET CLI (e.g., 'dotnet new console', 'dotnet add package Azure.Messaging.EventGrid.Namespaces') alongside Visual Studio steps.
- Include screenshots and steps for cross-platform editors like VS Code, or provide generic instructions not tied to a specific IDE.
- Replace PowerShell-only package installation commands with cross-platform alternatives, or provide both PowerShell and shell/bash equivalents.
- Explicitly mention that the sample code and instructions work on Linux and macOS, and provide any OS-specific notes if needed.
- Consider a 'tabbed' format for instructions, allowing users to select their OS or preferred development environment.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/event-hubs-integration.md
...lob/main/articles/event-grid/event-hubs-integration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by requiring Visual Studio (a Windows-centric IDE) for publishing the Azure Functions app and running the sample generator, with no mention of cross-platform alternatives. All development and deployment steps involving code are described using Visual Studio, and there are no instructions or examples for Linux or macOS users (e.g., using VS Code, Azure Functions Core Tools, or .NET CLI). The prerequisites and workflow assume a Windows environment, omitting Linux-native development tools and workflows.
Recommendations
- Add instructions for publishing the Azure Functions app using cross-platform tools such as Azure Functions Core Tools and the .NET CLI, which work on Linux and macOS.
- Include examples for running the sample data generator using the .NET CLI (dotnet run) instead of only referencing the Windows .exe file.
- Mention and provide guidance for using Visual Studio Code as an alternative to Visual Studio, including relevant extensions for Azure Functions and C# development.
- Explicitly state that the tutorial can be completed on Linux and macOS, and provide any necessary setup steps for those platforms.
- Ensure that all code publishing, deployment, and sample running steps have Linux/macOS equivalents, and present them alongside or before Windows-specific instructions.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/subscribe-to-graph-api-events.md
...n/articles/event-grid/subscribe-to-graph-api-events.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While it provides code samples for multiple languages and includes an Azure CLI example, it also features a dedicated PowerShell tab and references to Windows-centric tools and patterns. The instructions for obtaining Azure region names use the Azure CLI, which is cross-platform, but the presence of both CLI and PowerShell tabs (with no explicit mention of Bash or Linux shell scripting) suggests a preference for Windows environments. There are no explicit Linux-specific examples or guidance, and the sample web application links do not mention Linux deployment or setup. The documentation does not address Linux-specific development environments or tools, and the order of examples (PowerShell is included, but no Bash or Linux shell) further reinforces the Windows-first approach.
Recommendations
- Add explicit Linux/Bash shell scripting examples alongside PowerShell, especially for common setup and management tasks.
- Include instructions or notes for Linux/macOS users regarding environment setup, authentication, and running the CLI commands.
- Provide sample code or deployment instructions for Linux-based environments (e.g., Ubuntu, CentOS) in the 'Samples with detailed instructions' section.
- Ensure parity in tooling references—if PowerShell is included, also include Bash or other popular Linux shells.
- Clarify that Azure CLI is cross-platform and provide any Linux-specific caveats or tips where relevant.
- Consider the order of code tabs: avoid placing Windows-specific tools (PowerShell) before cross-platform or Linux-native options.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/handler-service-bus.md
...s/blob/main/articles/event-grid/handler-service-bus.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 Service Bus as an event handler for Event Grid. However, it includes detailed PowerShell instructions and examples, which are primarily relevant to Windows environments, without offering equivalent Linux-native scripting examples (such as Bash or shell scripting). The PowerShell sections are given equal prominence to the CLI, and there is no mention of Linux-specific tools or patterns. This may give the impression of a Windows-centric approach, especially for users seeking Linux-native automation guidance.
Recommendations
- Clarify that Azure CLI commands are fully cross-platform and can be run on Linux, macOS, and Windows.
- Consider providing Bash or shell script examples for automation scenarios, especially in sections where PowerShell is featured.
- Explicitly mention that PowerShell Core is available cross-platform, or provide links to Linux installation instructions if PowerShell examples are retained.
- Add a note or section highlighting Linux and macOS support for all command-line operations, and recommend CLI as the default for cross-platform compatibility.
- Where possible, include troubleshooting or environment setup notes relevant to Linux users (e.g., authentication, environment variables).
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/manage-event-delivery.md
...blob/main/articles/event-grid/manage-event-delivery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring dead-letter and retry policies in Azure Event Grid. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and there are explicit references to installing Azure PowerShell, which is most commonly used on Windows. There are no Linux shell-specific examples (e.g., Bash scripting), and the sample application linked is .NET-based, which is also more common in Windows environments. The documentation does not mention or demonstrate Linux-native tools or workflows, and PowerShell is presented as a primary automation option alongside Azure CLI.
Recommendations
- Add explicit Bash shell examples for all CLI commands, demonstrating variable assignment and command usage in a Linux context.
- Clarify that Azure CLI is fully cross-platform and can be used on Linux, macOS, and Windows, and provide installation links for all platforms.
- De-emphasize PowerShell as a primary automation tool by placing Azure CLI (and Bash) examples before PowerShell examples.
- Include sample applications or links for other languages and platforms (e.g., Python, Node.js) that are popular in Linux environments.
- Mention that all features described are available and supported on Linux, and provide troubleshooting tips for common Linux-specific issues if any.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/secure-webhook-delivery.md
...ob/main/articles/event-grid/secure-webhook-delivery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias by exclusively using PowerShell scripts and the Azure Cloud Shell (with PowerShell environment) for all scripting and automation steps. There are no Bash, Linux shell, or cross-platform scripting examples provided. The instructions assume the user is familiar with PowerShell and do not mention or provide alternatives for Linux users, despite Azure Cloud Shell supporting Bash. This could hinder Linux users or those who prefer Bash scripting from following the guide effectively.
Recommendations
- Provide equivalent Bash shell script examples for all PowerShell scripts and commands, especially for steps involving Microsoft Graph and Azure CLI.
- Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and offer instructions for both environments.
- Where referencing downloadable scripts, provide both .ps1 (PowerShell) and .sh (Bash) versions.
- Ensure that all variable setup and authentication steps are shown in both PowerShell and Bash syntax.
- Review diagrams and screenshots to ensure they are not Windows-specific (e.g., showing only PowerShell prompts or Windows UI elements).
- Add a note at the beginning clarifying that the instructions are cross-platform and that users can choose their preferred shell environment.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/send-events-webhooks-private-destinations.md
...vent-grid/send-events-webhooks-private-destinations.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing code samples and command-line instructions that are Windows-centric. The only code sample is in C# (commonly associated with Windows development), and the CLI example for Azure Relay Bridge uses a Windows-style executable invocation ('.\azbridge.exe'), with no Linux equivalent shown. There are no Linux shell or cross-platform code examples, and Windows tools and patterns are mentioned or implied before any Linux alternatives.
Recommendations
- Provide equivalent Linux/bash shell command examples for running Azure Relay Bridge (e.g., './azbridge' instead of '.\azbridge.exe').
- Include code samples in additional languages commonly used on Linux (such as Python, Node.js, or Java), or explicitly mention that the logic can be implemented in any language.
- Clarify that Azure Relay Bridge can be run on Linux, and provide Docker usage examples.
- When showing CLI commands, use cross-platform syntax or show both Windows and Linux variants.
- Avoid using only Windows file path and executable conventions; include Linux equivalents.
- Explicitly state the cross-platform nature of the tools and provide links or instructions for Linux users.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/subscribe-to-resource-notifications-containerservice-events.md
...ribe-to-resource-notifications-containerservice-events.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure portal. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is traditionally Windows-centric, though now available cross-platform) and the absence of any Linux shell-specific examples (e.g., Bash scripting, environment variable usage, or Linux-native tools) indicates a bias towards Windows users. Additionally, PowerShell examples are given equal prominence to CLI, and there are no Linux-first or Linux-specific instructions or troubleshooting notes. The documentation also uses PowerShell cmdlets and patterns that are more familiar to Windows administrators.
Recommendations
- Add explicit Bash/Linux shell examples, especially for scripting or automation scenarios (e.g., using environment variables, piping, jq for JSON parsing).
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
- If PowerShell is included, consider also including Bash or shell script equivalents for common tasks.
- Highlight cross-platform compatibility in the introduction and in each section, reassuring Linux users.
- If there are any differences in behavior or prerequisites on Linux (e.g., authentication, file paths), call these out in notes or tips.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/troubleshoot-network-connectivity.md
...ticles/event-grid/troubleshoot-network-connectivity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation shows a clear Windows bias: PowerShell/Windows tools (psping.exe) are featured prominently, with Windows commands given first and in more detail. Linux alternatives are either missing or only briefly mentioned. For example, the main port-checking example uses a Windows-only tool, and the Linux example (telnet) is less robust and not equivalent. Other troubleshooting steps reference Windows tools without Linux parity.
Recommendations
- Provide Linux-native command examples (e.g., use 'nc' or 'nmap' instead of 'telnet' for port checking, and show full command syntax).
- Present Windows and Linux examples side-by-side for all troubleshooting steps, ensuring parity in detail and capability.
- Mention cross-platform or Linux tools (e.g., 'tcpping' for Linux, or 'hping3') wherever Windows tools are referenced.
- Avoid giving Windows examples first by default; alternate or present both at the same time.
- Clarify tool availability and installation steps for both platforms.
- Ensure that all troubleshooting steps are actionable on both Windows and Linux environments.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/subscribe-to-resource-notifications-health-resources-events.md
...ribe-to-resource-notifications-health-resources-events.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and Azure Portal. However, it demonstrates a Windows bias by including extensive PowerShell examples (which are primarily associated with Windows environments) and referencing Azure PowerShell modules, which are more familiar to Windows users. There is no mention of Bash, Linux shell scripting, or cross-platform scripting alternatives. Additionally, PowerShell examples are given equal prominence to CLI examples, and the documentation does not clarify that Azure CLI is cross-platform and preferred for Linux/macOS users. There are no Linux-specific notes or troubleshooting tips.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
- Add Bash shell scripting examples or notes for Linux users, especially for scripting and automation scenarios.
- Clarify that Azure PowerShell is available cross-platform, but is more familiar to Windows users, and recommend Azure CLI for Linux/macOS users.
- Include troubleshooting tips or environment setup notes for Linux users (e.g., installing Azure CLI on Ubuntu, handling authentication).
- Avoid assuming PowerShell as the default scripting environment; consider reordering sections to present Azure CLI before PowerShell, or add a note explaining the intended audience for each.
- Where screenshots or portal instructions are given, note any differences in experience for Linux/macOS users if applicable.