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 1-25 of 289 flagged pages
Event Grid Configure custom Azure Policies on Event Grid resources to enhance you security posture ...ent-grid/custom-azure-policies-for-security-control.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references both CLI and PowerShell for discovering property aliases, but mentions PowerShell first and does not provide explicit Linux shell (bash) examples. There is a subtle prioritization of Windows tools and patterns, with no demonstration of Linux-specific commands or workflows. The lack of Linux CLI examples may hinder parity for non-Windows users.
Recommendations
  • Explicitly provide both Azure CLI (bash) and PowerShell command examples side-by-side when referencing command-line operations.
  • Avoid mentioning PowerShell before CLI unless there is a technical reason; consider listing CLI first or together.
  • Include Linux-specific instructions or notes where command syntax or environment differs.
  • Add a section or note clarifying cross-platform support for all commands and tools mentioned.
  • Ensure that all code samples and instructions are tested and valid on both Windows and Linux environments.
GitHub Create Pull Request
Event Grid Azure subscription as Event Grid source ...main/articles/event-grid/event-schema-subscriptions.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page shows mild Windows bias, primarily through the inclusion of a PowerShell tutorial and the use of Microsoft Teams as an automation target. The tutorials list PowerShell before Linux-friendly alternatives (Azure CLI), and the automation example uses Microsoft Teams, a Microsoft-centric tool. However, the page does include an Azure CLI tutorial and does not use Windows-specific scripting or tools in the main content or examples. There are no explicit Linux examples or references to Linux tools or shell scripting.
Recommendations
  • Add explicit Linux/bash scripting examples for subscribing to events and handling event data.
  • Include automation tutorials using Linux-native tools (e.g., sending events to Slack or using shell scripts for automation).
  • Ensure parity by listing Azure CLI and Linux-friendly approaches before or alongside PowerShell in tutorial sections.
  • Reference cross-platform endpoints and tools in automation scenarios, not just Microsoft Teams.
  • Clarify that all examples and APIs are platform-agnostic unless otherwise noted.
GitHub Create Pull Request
Event Grid Subscribe to Azure Resource Notifications - Health Resources events ...ribe-to-resource-notifications-health-resources-events.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and Azure Portal, but does not include any Linux-specific shell examples (such as Bash or scripting patterns), nor does it mention Linux tools or workflows. Azure PowerShell, which is traditionally Windows-centric, is given equal prominence to Azure CLI, and in some cases, PowerShell examples appear before CLI examples. There is no discussion of platform-specific considerations, nor any explicit guidance for Linux users beyond the CLI, which is cross-platform but not always used in the same way on Linux.
Recommendations
  • Add explicit Bash shell examples and scripting patterns for Linux users, especially for multi-step workflows.
  • Clarify that Azure CLI commands work cross-platform and provide notes on any platform-specific differences (e.g., quoting, environment variables, file paths).
  • Consider reordering examples to present Azure CLI (the most cross-platform tool) before PowerShell, or explicitly state platform parity.
  • Include troubleshooting tips or links for Linux users, such as common issues with Azure CLI on Linux.
  • If PowerShell is mentioned, clarify that PowerShell Core is available on Linux and provide installation guidance or links.
  • Avoid assuming PowerShell is the default for scripting; highlight Bash and other Linux-native options where appropriate.
GitHub Create Pull Request
Event Grid Authenticate Event Grid publishing clients using Microsoft Entra ID ...les/event-grid/authenticate-with-microsoft-entra-id.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: examples and references for enabling managed identities on VMs link to Windows VM guides, PowerShell is presented as a primary method for resource management, and screenshots/instructions are tailored to the Azure Portal (which is most commonly used on Windows). There are no explicit Linux CLI or shell script examples, and Linux VM configuration is not mentioned or linked. The CLI example is present, but PowerShell is given equal or greater prominence, and no Bash or Linux-specific instructions are provided.
Recommendations
  • Add explicit examples and links for enabling managed identities on Linux VMs, not just Windows VMs.
  • Provide Bash or shell script equivalents for PowerShell commands, especially for resource creation and management.
  • Include screenshots or instructions for Azure Portal usage on Linux (if applicable), or clarify that the portal is cross-platform.
  • Ensure that CLI examples are presented before or alongside PowerShell, and clarify their cross-platform nature.
  • Reference Linux tools and patterns (e.g., environment variable export via 'export' in Bash) in authentication code samples.
  • Where SDK usage is shown, provide sample code snippets for Linux-friendly languages and environments (e.g., Python with Bash environment setup).
GitHub Create Pull Request
Event Grid Send Blob storage events to web endpoint - Bicep ...ain/articles/event-grid/blob-event-quickstart-bicep.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation presents both Azure CLI and Azure PowerShell deployment examples, but PowerShell is featured equally and not as a secondary option. There is no explicit mention of Linux or macOS environments, nor are there instructions or screenshots for those platforms. The cleanup instructions reference the Azure Portal, which is cross-platform, but command-line examples do not clarify Linux usage, and PowerShell is a Windows-centric tool. There are no Linux-specific tools or shell examples (e.g., Bash), nor any mention of Linux file paths or considerations.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and clarify prerequisites for each platform.
  • Add Bash shell examples for deployment and cleanup steps, especially for Linux/macOS users.
  • Indicate that PowerShell examples are primarily for Windows, and suggest using Azure CLI on Linux/macOS.
  • Include screenshots or notes for Linux/macOS environments where relevant.
  • Add a section on installing Azure CLI on Linux/macOS, or link to relevant documentation.
GitHub Create Pull Request
Event Grid CloudEvents v1.0 schema with Azure Event Grid ...cs/blob/main/articles/event-grid/cloud-event-schema.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing PowerShell examples alongside Azure CLI, referencing Visual Studio and Visual Studio Code (both commonly used on Windows), and describing NuGet package management primarily through Visual Studio tooling. There is no mention of Linux-specific workflows, package managers, or shell environments, and no explicit Linux or macOS examples are given for command-line or development tasks.
Recommendations
  • Add explicit Linux/macOS shell examples (e.g., bash/zsh) for Azure CLI commands, including environment variable usage and command chaining.
  • Include instructions for managing NuGet packages using dotnet CLI (cross-platform) rather than only Visual Studio tooling.
  • Mention Linux-compatible editors (e.g., JetBrains Rider, Vim, Emacs) and provide parity in development workflow descriptions.
  • Clarify that Azure CLI commands work on all platforms and provide troubleshooting tips for Linux/macOS users.
  • Add notes or examples for running Azure Functions locally on Linux/macOS, including any platform-specific considerations.
  • Avoid presenting PowerShell examples before or alongside CLI examples unless also providing bash equivalents.
GitHub Create Pull Request
Event Grid Azure Event Grid delivery and retry ...cs/blob/main/articles/event-grid/delivery-and-retry.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and CLI commands together, but only explicitly mentioning 'PowerShell' (a Windows-centric tool) and not providing Linux-specific shell examples. The phrase 'sample CLI and PowerShell command' is used, and the batching configuration section lists 'portal, CLI, PowerShell, or SDKs' as options, with PowerShell mentioned before Linux-native tools. The CLI example uses Bash syntax, but there is no explicit mention or example for Linux shell environments, nor any clarification for differences in command usage between Windows and Linux. There is no mention of Linux tools or patterns, and no guidance for Linux users.
Recommendations
  • Explicitly mention Linux shell environments (e.g., Bash, Zsh) when providing CLI examples.
  • Provide equivalent examples for Linux (e.g., Bash scripts) alongside PowerShell commands, or clarify that the CLI example is cross-platform.
  • When listing tooling options, alternate or balance the order (e.g., 'CLI, PowerShell, portal, SDKs') to avoid Windows-first bias.
  • Add notes or sections clarifying any differences in command syntax or environment setup between Windows and Linux.
  • Include troubleshooting or environment setup guidance for Linux users where relevant.
GitHub Create Pull Request
Event Grid Tutorial: Send Event Hubs data to data warehouse - Event Grid ...lob/main/articles/event-grid/event-hubs-integration.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Visual Studio Only Missing Linux Example
Summary
The tutorial demonstrates a Windows bias by exclusively using Visual Studio for publishing the Azure Functions app and running the sample code, with no mention of cross-platform alternatives like VS Code or CLI-based deployment. All code publishing steps assume a Windows/Visual Studio environment, and there are no instructions or examples for Linux or macOS users. The prerequisites and workflow reinforce this bias by requiring Visual Studio and not offering parity for Linux development environments.
Recommendations
  • Add instructions for publishing the Azure Functions app using cross-platform tools such as Azure Functions Core Tools (func CLI), VS Code, or Azure CLI.
  • Include examples for running the WindTurbineDataGenerator sample on Linux/macOS, such as using .NET CLI (dotnet run) instead of relying on Visual Studio.
  • Update prerequisites to mention cross-platform development environments (VS Code, .NET CLI) and provide links to relevant installation guides.
  • Ensure all steps that currently rely on Visual Studio have equivalent instructions for Linux/macOS users.
  • Explicitly state that the sample projects can be built and run on Linux/macOS, and provide troubleshooting tips for non-Windows platforms.
GitHub Create Pull Request
Event Grid Quickstart: Send custom events to an Azure function - Event Grid ...b/main/articles/event-grid/custom-event-to-function.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI (Bash) and Azure PowerShell examples for sending events, but the PowerShell example is given equal prominence and detail as the Bash/CLI example. There is a slight Windows-first bias in the use of Visual Studio Code and C#/.NET for the function creation, which are more commonly used on Windows. The documentation does not provide explicit Linux-native examples (e.g., using native Linux shells outside Azure Cloud Shell, or alternative editors/environments). There are no references to Linux-specific tools or workflows, and PowerShell is mentioned as a primary option for Cloud Shell, which may reinforce a Windows-centric approach.
Recommendations
  • Add explicit instructions and examples for running the Azure CLI and cURL commands on a local Linux shell, not just in Azure Cloud Shell.
  • Include alternative function creation steps using other languages (such as Python or JavaScript) and editors (such as Vim or VS Code on Linux), to demonstrate cross-platform parity.
  • Clarify that Visual Studio Code and Azure CLI are fully supported on Linux, and provide links or notes for Linux users.
  • Consider providing Linux-native shell script examples for sending events, and mention common Linux tools (e.g., jq for JSON manipulation) where relevant.
  • Reduce the emphasis on PowerShell by presenting Bash/Linux shell examples first, or side-by-side, and clarify that PowerShell is optional for users on Windows.
GitHub Create Pull Request
Event Grid Integrate Azure Automation with Event Grid | Microsoft Docs ...ent-grid/ensure-tags-exists-on-new-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on PowerShell and AzureRM modules, which are traditionally Windows-centric. All code examples and automation steps use PowerShell syntax, with no mention of Bash, CLI, or Linux-native tooling. There are no examples or instructions for performing the same tasks on Linux VMs or using cross-platform tools like Azure CLI. The documentation implicitly assumes a Windows environment for automation and scripting.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for Linux users.
  • Clarify whether the runbook and tagging process works for both Windows and Linux VMs, and provide instructions for both.
  • Include notes or sections on how to import and use modules in cross-platform environments.
  • Add guidance for users who prefer Linux-based automation, such as using Python or shell scripts in Azure Automation.
  • Ensure that screenshots and UI instructions are not Windows-specific, or provide Linux/CLI alternatives where possible.
GitHub Create Pull Request
Event Grid Quickstart - Use Event Grid pull delivery from .NET app ...nt-grid/event-grid-dotnet-get-started-pull-delivery.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All development instructions are centered around Visual Studio (Windows-only), and all package installation examples use PowerShell commands. There are no instructions or examples for Linux or cross-platform development environments (such as VS Code, JetBrains Rider, or CLI-based workflows). The documentation omits Linux-specific guidance for .NET development, such as using the dotnet CLI or installing packages via command line. The exclusive use of Windows tools and patterns may hinder accessibility for Linux or macOS users.
Recommendations
  • Add instructions for using the dotnet CLI to create projects and install NuGet packages, which works cross-platform.
  • Include examples for setting up and running the sample in VS Code or other cross-platform editors.
  • Provide Linux/macOS-specific guidance for prerequisites, such as installing .NET SDK and running the sample from the terminal.
  • Replace PowerShell-specific commands with platform-agnostic alternatives, or provide both PowerShell and bash/zsh equivalents.
  • Clarify that the sample can be run on any OS supported by .NET, and explicitly mention Linux and macOS compatibility.
GitHub Create Pull Request
Event Grid Publish and subscribe on an MQTT topic using portal ...ticles/event-grid/mqtt-publish-and-subscribe-portal.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the certificate generation section, where instructions are tailored for Windows users (e.g., opening a command prompt in %USERPROFILE% and using PowerShell syntax). There are no equivalent Linux or macOS instructions or examples provided for certificate creation, and the initial guidance is Windows-centric. The rest of the guide is platform-neutral, especially when using MQTTX, but the critical setup steps lack Linux parity.
Recommendations
  • Add explicit instructions and example commands for Linux and macOS users, including how to open a terminal and navigate to the home directory.
  • Provide bash/zsh shell command equivalents for certificate generation using step CLI.
  • Mention Linux/macOS file paths (e.g., $HOME instead of %USERPROFILE%) and clarify any platform-specific differences in file handling.
  • Ensure that screenshots and instructions do not assume a Windows environment unless necessary, and offer alternatives for other platforms.
  • Consider a 'Platform differences' callout box in the prerequisites or certificate generation section.
GitHub Create Pull Request
Event Grid Function as event handler for Azure Event Grid events ...ocs/blob/main/articles/event-grid/handler-functions.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. While it covers Azure Functions and Event Grid in a platform-neutral manner, it lists Azure PowerShell as a primary tool for configuring batching, with PowerShell examples and links provided. PowerShell is mentioned before Linux-native tools (Azure CLI), and there are no explicit Linux shell or bash examples. The Azure portal, PowerShell, CLI, and ARM template are all mentioned, but PowerShell receives more detailed attention and is listed before CLI in some sections.
Recommendations
  • Provide explicit bash or shell examples for Linux users alongside PowerShell examples.
  • List Azure CLI before PowerShell when describing cross-platform automation options.
  • Clarify that Azure CLI is fully cross-platform and suitable for Linux/macOS users.
  • Add a note or section highlighting Linux/macOS usage patterns, such as scripting with bash and using the Azure CLI.
  • Ensure parity in example depth and detail between PowerShell and CLI instructions.
GitHub Create Pull Request
Event Grid Map custom field to Azure Event Grid schema ...e-docs/blob/main/articles/event-grid/input-mappings.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations. However, PowerShell is featured alongside CLI in every section, and no Linux-specific shell examples (e.g., Bash scripts, native Linux tools) are given. The CLI examples use Bash-style syntax, but there is no explicit mention or guidance for Linux users, nor are there examples using Linux-native tools beyond curl. PowerShell, a Windows-centric tool, is given equal prominence, which may suggest a Windows bias.
Recommendations
  • Add explicit Bash script examples for Linux users, clarifying CLI usage in Bash environments.
  • Include notes or sections on running Azure CLI commands in Linux/macOS terminals.
  • Reduce the prominence of PowerShell, or move PowerShell examples to a separate tab or section to avoid implying it is the primary method.
  • Where possible, mention Linux-native tools (e.g., wget, jq) for event publishing and processing.
  • Clarify that Azure CLI is cross-platform and provide troubleshooting tips for Linux users.
GitHub Create Pull Request
Event Grid Dead letter and retry policies - Azure Event Grid ...blob/main/articles/event-grid/manage-event-delivery.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring dead-letter and retry policies in Azure Event Grid. However, PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) can signal a Windows bias. There are explicit references to installing Azure PowerShell, but no mention of Linux-specific shell usage (e.g., Bash), nor are there examples using Bash or other Linux-native tools. The documentation does not clarify that Azure CLI commands work natively on Linux/macOS, and the order of examples sometimes places PowerShell before CLI, reinforcing a Windows-first approach. No Linux-specific troubleshooting, shell scripting, or environment notes are provided.
Recommendations
  • Add explicit Bash shell examples alongside Azure CLI, demonstrating usage in Linux environments.
  • Clarify that Azure CLI works natively on Linux/macOS and provide installation instructions for those platforms.
  • Include troubleshooting notes or tips for Linux users (e.g., permissions, environment variables).
  • Where PowerShell is mentioned, note that PowerShell Core is cross-platform, but provide Bash alternatives for Linux users.
  • Ensure that Azure CLI examples are presented before PowerShell, or at least equally, to avoid Windows-first impression.
  • Reference Linux tools or scripting patterns where relevant (e.g., using jq for JSON parsing, environment variable conventions).
GitHub Create Pull Request
Event Grid Azure Event Grid Namespace MQTT client authentication using certificate chain ...t-grid/mqtt-certificate-chain-client-authentication.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides certificate generation instructions exclusively using Windows PowerShell commands, despite referencing a cross-platform tool (step CLI). There are no Linux or macOS shell examples, and the instructions explicitly mention Windows installation and usage first, potentially excluding or confusing users on other platforms.
Recommendations
  • Include equivalent Linux/macOS shell commands (e.g., bash) for certificate generation using step CLI.
  • Add installation instructions for step CLI on Linux and macOS, not just Windows.
  • Present cross-platform examples side-by-side or in tabs, rather than focusing on Windows first.
  • Clarify that the step CLI commands work on all major operating systems and provide OS-specific notes where necessary.
GitHub Create Pull Request
Event Grid Quickstart: Publish on an MQTT topic by using the CLI .../articles/event-grid/mqtt-publish-and-subscribe-cli.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page shows evidence of Windows bias, particularly in the certificate generation section, where instructions and commands are provided specifically for Windows users (Command Prompt, Powershell syntax, Windows environment variables). There are no equivalent Linux or macOS examples for certificate generation, and the guidance assumes a Windows environment (e.g., '%USERPROFILE%' path, Command Prompt). The .NET sample code also references Visual Studio and NuGet, which are primarily Windows-centric tools, with no mention of cross-platform alternatives or instructions for Linux/macOS users.
Recommendations
  • Provide explicit Linux and macOS instructions for certificate generation, including shell commands and file paths.
  • Include bash/zsh examples for using the step CLI and certificate management.
  • Mention cross-platform code editors (e.g., VS Code) and package managers (e.g., dotnet CLI) for running .NET samples.
  • Avoid referencing Windows-specific environment variables and tools unless parity is provided for other platforms.
  • Add notes or sections clarifying steps for Linux/macOS users throughout the quickstart.
GitHub Create Pull Request
Event Grid Topic Spaces ...ocs/blob/main/articles/event-grid/mqtt-topic-spaces.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates Windows bias primarily in its treatment of shell-specific escaping for special characters. It provides detailed PowerShell-specific examples and guidance for escaping characters like '$' and '|', but does not mention or provide equivalent instructions for Linux shells (e.g., Bash, Zsh). The examples and notes are Windows/PowerShell-centric, and there is no parity for Linux users in these sections.
Recommendations
  • Add explicit instructions and examples for escaping special characters in common Linux shells (e.g., Bash, Zsh).
  • Provide side-by-side examples for both PowerShell and Bash when discussing shell-specific syntax or escaping.
  • Include notes or tables summarizing differences in escaping between Windows and Linux environments.
  • Review other sections for similar shell/tool-specific instructions and ensure Linux parity throughout.
GitHub Create Pull Request
Event Grid Publish Events to Azure Event Grid Custom Topics .../blob/main/articles/event-grid/post-to-custom-topic.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by consistently presenting Azure PowerShell examples alongside or before Azure CLI, referencing PowerShell-specific commands and patterns, and mentioning Windows-centric tools (PowerShell, Azure portal) without highlighting Linux alternatives. While Azure CLI is cross-platform, the prominence and detail of PowerShell examples and terminology may disadvantage Linux users. There are no explicit Linux-only examples or references to Linux-specific tools, and Bash scripting is only briefly mentioned within the Azure CLI context.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific instructions where relevant.
  • Add Linux terminal screenshots or examples, especially for steps involving environment variables and curl.
  • Present Azure CLI (Bash) examples before PowerShell, or in parallel, to avoid Windows-first ordering.
  • Avoid referencing PowerShell-specific constructs (e.g., Hashtable, ConvertTo-Json) without offering equivalent Bash/Unix shell alternatives.
  • Clarify that Azure portal and Cloud Shell are accessible from any OS, and highlight Bash as a first-class option in Cloud Shell.
  • Include troubleshooting or tips for Linux users, such as handling JSON formatting or date/time generation in Bash.
GitHub Create Pull Request
Event Grid Azure PowerShell - Secure WebHook delivery with Microsoft Entra user in Azure Event Grid ...owershell-webhook-secure-delivery-microsoft-entra-user.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively provides a PowerShell script for configuring secure webhook delivery with Microsoft Entra user in Azure Event Grid. All example commands and workflow are shown using PowerShell, with no mention of Linux shell equivalents, cross-platform CLI (e.g., Azure CLI), or alternative tooling. The instructions assume the use of PowerShell and Windows-centric workflows, which may disadvantage users on Linux or macOS.
Recommendations
  • Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
  • Include bash shell script samples for key steps, especially for service principal and role assignments.
  • Explicitly state platform requirements and offer guidance for non-Windows users (e.g., how to run PowerShell Core on Linux, or alternatives).
  • Add a section comparing PowerShell and CLI approaches, and link to relevant Linux/macOS documentation.
  • Ensure screenshots and portal navigation instructions are not Windows-specific, or clarify their cross-platform applicability.
GitHub Create Pull Request
Event Grid Send events to webhooks hosted in private destinations ...vent-grid/send-events-webhooks-private-destinations.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing command-line examples using Windows-style syntax (e.g., .\azbridge.exe), referencing .NET/C# code samples exclusively, and omitting explicit Linux or cross-platform examples for running Azure Relay Bridge or implementing webhook validation. The use of backslash in command examples and lack of Linux shell or alternative language samples may hinder Linux developers.
Recommendations
  • Include Linux-specific command examples for running Azure Relay Bridge (e.g., ./azbridge instead of .\azbridge.exe).
  • Provide webhook validation code samples in other languages commonly used on Linux (such as Python, Node.js, or Go).
  • Clarify that Azure Relay Bridge can be run on Linux and provide Docker usage examples.
  • Add explicit instructions or examples for Linux environments when referencing Azure CLI or other tools.
  • Ensure cross-platform parity by listing both Windows and Linux usage patterns side-by-side where applicable.
GitHub Create Pull Request
Event Grid Azure PowerShell - Secure WebHook delivery with Microsoft Entra Application in Azure Event Grid ...powershell-webhook-secure-delivery-microsoft-entra-app.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments, as it exclusively provides PowerShell examples and references PowerShell modules (e.g., Microsoft.Graph.PowerShell). There are no equivalent examples for Bash, Azure CLI, or other Linux-native tools. The instructions and sample script assume the user is familiar with PowerShell and do not mention or prioritize Linux workflows.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for Linux users.
  • Mention cross-platform alternatives to PowerShell modules, such as REST API calls or Azure CLI commands.
  • Clarify which steps are platform-agnostic and which require Windows/PowerShell, and offer guidance for Linux/macOS users.
  • Add notes or links to documentation for performing similar tasks on Linux systems.
GitHub Create Pull Request
Event Grid Secure WebHook delivery with Microsoft Entra ID ...ob/main/articles/event-grid/secure-webhook-delivery.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell scripts and referencing the Azure Portal/Azure Shell (which defaults to PowerShell) for configuration steps. There are no Bash or Linux shell script examples, and the instructions assume use of Windows-centric tools and environments. Azure CLI is mentioned, but only for a few steps, and even then, the context is still within the Azure Shell, which is often used from Windows. There is no guidance for Linux users, nor are Linux-native patterns or tools discussed.
Recommendations
  • Provide equivalent Bash/Linux shell script examples for all PowerShell scripts, especially for steps involving Microsoft Graph and service principal configuration.
  • Explicitly mention that Azure Cloud Shell can be used in Bash mode and provide instructions for switching to Bash.
  • Include guidance for running these steps on Linux/macOS environments, including installation and usage of Azure CLI and Microsoft Graph CLI.
  • Where possible, use cross-platform tools (e.g., Azure CLI, Microsoft Graph CLI) in examples before PowerShell, or at least provide both side-by-side.
  • Add notes or sections highlighting any differences or additional steps required for Linux users.
GitHub Create Pull Request
Event Grid Subscribe to Microsoft Graph Events Using Azure Event Grid ...n/articles/event-grid/subscribe-to-graph-api-events.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation demonstrates a moderate Windows bias. It references Windows-specific tools (PowerShell, Azure CLI, and commands like az account list-locations) and includes PowerShell as a primary code sample. The instructions for obtaining Azure region names specifically mention using the Azure CLI, which is more commonly used on Windows, and do not provide Linux alternatives or mention cross-platform usage. The code sample tabs list PowerShell and CLI before Linux-native shells or tools, and there is no explicit mention of Linux-specific setup or parity in the development environment instructions.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and provide Linux/macOS installation instructions or links.
  • Include Bash or shell script examples alongside PowerShell, especially for common tasks like querying Azure regions.
  • Clarify that all SDKs and samples work on Linux and macOS, and provide guidance for setting up development environments on those platforms.
  • Add notes or sections for Linux users, such as using curl for HTTP requests, and troubleshooting common Linux-specific issues.
  • Ensure that sample code and instructions do not assume a Windows environment (e.g., file paths, environment variables, authentication flows).
GitHub Create Pull Request
Event Grid Troubleshoot network connectivity issues - Azure Event Grid | Microsoft Docs ...ticles/event-grid/troubleshoot-network-connectivity.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting Windows/Powershell examples and tools (psping.exe, tcpping.exe) before Linux equivalents, and in some cases omitting Linux-native alternatives. The troubleshooting commands and tool recommendations are focused on Windows utilities, with only minimal mention of Linux (e.g., telnet) and no parity in advanced troubleshooting steps or tool suggestions for Linux users.
Recommendations
  • Provide Linux-native command examples (e.g., use 'nc' or 'nmap' for port checking instead of only 'telnet').
  • List Linux troubleshooting commands and tools alongside Windows examples, not after or as an afterthought.
  • Include installation instructions or references for Linux tools (e.g., 'sudo apt install nmap').
  • Mention cross-platform tools (e.g., Wireshark, curl) where appropriate, and clarify usage on both Windows and Linux.
  • Ensure parity in troubleshooting steps and tool recommendations for both Windows and Linux environments.
GitHub Create Pull Request
← Previous Page 1 of 12 Next →