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 26-50 of 289 flagged pages
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions and code samples for Azure CLI, Azure PowerShell, and the Azure portal. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is historically Windows-centric and still most commonly used on Windows) alongside CLI in every example, and the lack of any Linux-specific shell (e.g., Bash) or scripting examples, indicates a bias toward Windows tooling and patterns. There are no examples using Bash, shell scripting, or Linux-native tools, nor is there any mention of Linux-specific considerations. The PowerShell examples are given equal prominence to CLI, and in some sections, PowerShell is listed before CLI, reinforcing a Windows-first approach. No explicit Linux guidance or troubleshooting is provided.
Recommendations
  • Add explicit Bash/shell scripting examples for each CLI command, demonstrating usage in Linux environments (e.g., with environment variables, piping, jq for JSON parsing).
  • Clarify that Azure CLI is cross-platform and provide guidance for installing and using it on Linux and macOS.
  • Reorder sections to present Azure CLI examples before PowerShell, emphasizing cross-platform compatibility.
  • Include notes or troubleshooting tips for Linux users, such as handling authentication, file paths, or common issues.
  • Mention that PowerShell Core is available on Linux, but clarify differences or limitations compared to Windows PowerShell.
  • Where screenshots are shown, include examples from Linux terminals or macOS, not just Windows/PowerShell environments.
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-10 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 in several ways. Windows-specific tools and workflows (Azure PowerShell, Azure portal screenshots) are presented before or instead of Linux equivalents. PowerShell commands are provided, but there are no Bash or Linux shell examples. Portal instructions and screenshots are Windows-centric, and there is no mention of Linux desktop tools or cross-platform alternatives. There are no explicit Linux command-line examples for tasks like disabling local authentication, nor is there guidance for Linux users on environment setup or SDK usage.
Recommendations
  • Add Bash or Linux shell command examples alongside PowerShell, especially for resource creation and configuration tasks.
  • Include screenshots or instructions for using the Azure portal from Linux browsers, or clarify that the portal is cross-platform.
  • Explicitly mention that the Azure CLI is cross-platform and provide Linux-specific installation or usage notes.
  • Where environment variables are set in code samples, show both Windows (setx, PowerShell) and Linux (export) methods.
  • Provide parity in SDK usage examples by including code snippets that demonstrate authentication and publishing from Linux environments.
  • Reference Linux desktop tools (such as VS Code on Linux) and provide guidance for Linux users where relevant.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides deployment instructions for both Azure CLI and Azure PowerShell, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, which is cross-platform. There is no explicit mention of Linux or macOS environments, nor are there any Linux-specific examples or notes. The cleanup instructions reference deleting a resource group via a link that defaults to the Azure Portal, which is platform-agnostic, but the command-line instructions do not clarify Linux usage or shell differences.
Recommendations
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and recommend it as the default cross-platform tool.
  • Present Azure CLI instructions before PowerShell to reduce Windows-first perception.
  • Add notes or examples for Linux/macOS users, such as shell syntax differences or installation instructions for Azure CLI on Linux.
  • If PowerShell is mentioned, clarify that PowerShell Core is available cross-platform, or link to installation guides for Linux/macOS.
  • Include troubleshooting or environment setup tips for Linux users, such as file path conventions or permissions.
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-10 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 exhibits Windows bias by providing PowerShell examples alongside Azure CLI, referencing Visual Studio and Visual Studio Code (both popular on Windows), and describing NuGet package installation via Visual Studio's GUI and Package Manager Console (Windows-centric). There are no Linux-specific shell examples, nor are Linux-native tools or workflows mentioned. The ordering of examples often places Windows/PowerShell before cross-platform or Linux-friendly alternatives.
Recommendations
  • Add explicit Bash/Linux shell examples for all CLI commands, including environment variable usage and scripting patterns common on Linux.
  • Include instructions for installing NuGet packages using dotnet CLI (cross-platform) and mention package management in Linux environments.
  • Reference Linux-native editors (e.g., Vim, Emacs) or provide generic instructions for editing project files outside Visual Studio/VS Code.
  • Ensure that Azure CLI examples are presented first or equally with PowerShell, and clarify that PowerShell is primarily a Windows tool.
  • Add notes or sections on developing Azure Functions on Linux, including local development and deployment workflows.
  • Mention cross-platform compatibility for all tools and commands, and provide links to Linux installation guides where relevant.
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-10 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 mild Windows bias. While it does mention both Azure CLI and PowerShell for configuring Event Grid delivery and retry policies, it refers to 'sample CLI and PowerShell command' together, and links to a page that likely contains both but does not show explicit Linux shell examples (e.g., bash) or mention Linux-specific tools. The CLI example uses environment variable syntax compatible with bash, but does not clarify platform compatibility or provide explicit Linux/Unix instructions. PowerShell is mentioned by name multiple times, while Linux equivalents (such as Bash, zsh, or other shells) are not. There are no examples or instructions for configuring these settings using Linux-native tools or shells, nor is there any mention of Linux-specific considerations.
Recommendations
  • Provide explicit bash or Linux shell examples alongside PowerShell, clarifying platform compatibility.
  • When referencing CLI commands, specify that they work on both Windows and Linux, or provide separate instructions if needed.
  • Include Linux-specific notes or troubleshooting tips where relevant, especially for environment variable syntax and file paths.
  • Avoid mentioning PowerShell before CLI or Linux tools unless contextually necessary; strive for parity in tool presentation.
  • Add a section or note confirming cross-platform support for all commands and tools referenced.
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-10 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 instructions for creating and running the .NET applications are centered around Visual Studio, a Windows-centric IDE, and use Windows-specific UI steps and screenshots. NuGet package installation is shown only via the Package Manager Console (PowerShell), with no mention of cross-platform alternatives like the dotnet CLI. There are no instructions or examples for Linux or macOS users, such as using VS Code, JetBrains Rider, or command-line workflows. The documentation does not mention how to run or build the sample on Linux, nor does it provide parity for Linux tooling or patterns.
Recommendations
  • Add instructions for using cross-platform editors like VS Code or JetBrains Rider, including steps for project creation and management.
  • Provide NuGet package installation examples using the dotnet CLI (e.g., 'dotnet add package Azure.Messaging.EventGrid.Namespaces'), which works on Windows, Linux, and macOS.
  • Include screenshots and workflow steps for Linux/macOS environments, such as using terminal commands and file explorers.
  • Clarify that the .NET SDK and Event Grid libraries are cross-platform and provide guidance for building and running the sample on Linux/macOS (e.g., 'dotnet build', 'dotnet run').
  • Mention prerequisites for Linux/macOS (e.g., installing .NET SDK, using appropriate IDEs or editors).
  • Avoid assuming Visual Studio is the only or primary development environment.
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-10 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 use PowerShell, with no mention of Bash, Azure CLI, or Linux-native tools. There are no instructions or examples for users working from Linux or macOS environments, nor is there guidance on using cross-platform tools. The tutorial assumes familiarity with Windows/PowerShell workflows and does not provide Linux alternatives.
Recommendations
  • Include equivalent examples using Azure CLI and Bash scripts for each PowerShell example.
  • Explicitly mention that Azure Automation and Event Grid can be used from Linux/macOS environments, and provide steps for those platforms.
  • Add guidance on importing modules and managing runbooks using cross-platform tools (e.g., Azure CLI, REST API).
  • Clarify that the AzureRM modules are deprecated and recommend using Az modules, which are cross-platform.
  • Where possible, provide screenshots or instructions that are not specific to Windows UI conventions.
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-10 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 referencing Visual Studio for publishing the Azure Functions app, with no mention of cross-platform alternatives such as VS Code or CLI-based deployment. The prerequisites and instructions assume a Windows development environment, omitting guidance for Linux users. While Azure CLI is used for resource deployment (which is cross-platform), all code publishing and sample running steps are tailored to Windows and Visual Studio, with no Linux or macOS workflow provided.
Recommendations
  • Add instructions for publishing the Azure Functions app using Azure CLI, Azure Functions Core Tools, or VS Code, which are cross-platform.
  • Include prerequisites and setup steps for Linux and macOS environments, such as installing .NET SDK and using VS Code.
  • Provide alternative steps for running the sample data generator on Linux/macOS, including building and running .NET projects from the command line.
  • Clarify that the Azure CLI and Cloud Shell are available on all platforms, and provide Bash-specific examples where relevant.
  • Mention cross-platform editors (VS Code, JetBrains Rider) and provide links or instructions for their use.
GitHub Create Pull Request
Event Grid How to filter events for Azure Event Grid .../blob/main/articles/event-grid/how-to-filter-events.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides both Azure PowerShell (Windows-centric) and Azure CLI (cross-platform) examples for all operations, but PowerShell examples are consistently presented first, and some explanations are more detailed for PowerShell. The use of PowerShell and Windows-specific tools (e.g., Invoke-WebRequest, ConvertTo-Json, Get-Date) may be less familiar or accessible to Linux users. There are no explicit Linux-only examples or mentions of Linux-specific patterns or tools, and Bash/CLI examples are present but not prioritized.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to avoid implicit prioritization of Windows tools.
  • Add explicit notes clarifying that Azure CLI examples are cross-platform and can be run on Linux, macOS, and Windows.
  • Where PowerShell uses Windows-specific commands (e.g., Invoke-WebRequest), provide equivalent Bash/curl examples for Linux users.
  • Include troubleshooting or environment setup notes for Linux users, such as installing Azure CLI or using curl for HTTP requests.
  • Consider adding a section or callout for Linux/macOS users, highlighting any differences or tips for running the examples on those platforms.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in the certificate generation section, where instructions and examples are tailored for Windows users (e.g., opening a command prompt in %USERPROFILE%, using Powershell syntax, and referencing Windows-specific folder paths). There are no equivalent instructions or examples for Linux or macOS users, and the Windows workflow is presented first and exclusively.
Recommendations
  • Provide explicit Linux and macOS instructions for certificate generation, including terminal commands and typical folder paths.
  • Include bash/zsh shell command examples alongside Powershell, and clarify any OS-specific differences in the step CLI usage.
  • Avoid referencing Windows-specific environment variables (e.g., %USERPROFILE%) without mentioning Linux/macOS equivalents (e.g., $HOME).
  • Add a note or section indicating cross-platform compatibility for the step CLI and MQTTX app, with links to installation guides for all major operating systems.
  • Ensure screenshots and UI instructions are not Windows-centric, or supplement with Linux/macOS visuals where relevant.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides configuration instructions for batching using Azure portal, PowerShell, CLI, and Resource Manager templates. PowerShell is mentioned explicitly and receives its own section, which is a Windows-centric tool. The order of tools presented (portal, Resource Manager template, CLI, PowerShell) puts PowerShell before CLI, which is more cross-platform. There are no explicit Linux shell examples (e.g., Bash), and no mention of Linux-specific tooling or patterns. The REST example is platform-neutral, but the overall guidance leans toward Windows tools and patterns.
Recommendations
  • Provide explicit Bash or shell examples for Linux users alongside PowerShell examples.
  • Mention cross-platform CLI usage before PowerShell, or group them together with equal prominence.
  • Clarify that Azure CLI is cross-platform and suitable for Linux, macOS, and Windows.
  • Add notes or links for Linux users on installing and using Azure CLI.
  • Ensure that all examples and instructions are platform-neutral or have parity for both Windows and Linux environments.
GitHub Create Pull Request
Event Grid Publish events with event domains with Azure Event Grid .../blob/main/articles/event-grid/how-to-event-domains.md
High Priority View Details →
Scanned: 2026-01-10 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, but PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI, and no Linux-specific shell examples (e.g., Bash/curl for HTTP POST) are provided. There is no mention of Linux tools or patterns, and the only scripting examples outside CLI are PowerShell, which may not be available or preferred on Linux systems. The SDK samples are linked for multiple languages, but the core documentation leans towards Windows tooling.
Recommendations
  • Add explicit Bash/curl examples for publishing events via HTTP POST to the Event Grid domain endpoint.
  • Clarify that Azure CLI is cross-platform and highlight its usage for Linux/macOS users.
  • Consider including Linux-native shell commands (e.g., using jq, curl) for common tasks such as listing keys, endpoints, and publishing events.
  • Reorder examples to present Azure CLI first, emphasizing its cross-platform nature, and note PowerShell as an alternative for Windows users.
  • Add a brief section or note on how Linux users can install and use Azure CLI and interact with Event Grid.
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-10 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 steps, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and there are no explicit Linux shell script examples (e.g., Bash). The CLI examples use syntax compatible with Bash, but there is no mention of Linux-specific tools or patterns, nor any guidance for Linux users beyond Azure CLI. PowerShell examples are included throughout, which may suggest a bias toward Windows environments.
Recommendations
  • Explicitly mention that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
  • Add Bash-specific examples for publishing events, including variable assignment and curl usage, to clarify Linux usage.
  • Consider including notes or sections for Linux users, highlighting any differences or best practices.
  • Reduce the prominence of PowerShell by placing CLI/Bash examples first, or by clarifying that PowerShell is primarily for Windows users.
  • If possible, include examples using other Linux-native tools (e.g., wget, jq) where relevant.
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-10 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) may signal a Windows bias. The CLI and PowerShell examples are presented together, but there is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples using native Linux tools or scripting patterns. Additionally, installation notes reference Azure PowerShell and its download page, which is primarily targeted at Windows users. The related sample application is for .NET, another technology with historical Windows roots, and there is no mention of Linux or open-source alternatives.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands, demonstrating usage on Linux and macOS.
  • Clarify that Azure CLI is cross-platform and provide installation instructions for Linux and macOS alongside Windows.
  • Include notes or examples for using Azure CLI in Bash scripts, highlighting differences from PowerShell scripting.
  • Reference open-source or Linux-native sample applications for handling dead-letter events, such as Python or Node.js.
  • Avoid presenting PowerShell as an equal alternative to CLI for cross-platform scenarios; clarify its Windows-centric nature.
  • Ensure screenshots and UI references do not assume Windows-only environments.
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-10 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 examples exclusively using Windows PowerShell, with explicit instructions for Windows users and no equivalent Linux or macOS command-line examples. The installation note for the step CLI mentions Windows specifically, and all sample commands are presented in PowerShell syntax, omitting bash or shell alternatives. This creates a Windows-centric bias and may hinder Linux users from following the guide seamlessly.
Recommendations
  • Add Linux and macOS command-line examples using bash/zsh for certificate generation with step CLI.
  • Provide cross-platform installation instructions for step CLI, including package manager commands for Linux (e.g., apt, yum, brew).
  • Present command examples in a platform-neutral way, or show both PowerShell and bash syntax side-by-side.
  • Avoid language such as 'in Windows PowerShell, run...' unless also providing equivalent instructions for other platforms.
  • Explicitly state that the steps are applicable to all major OSes and highlight any platform-specific differences.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates Windows bias in several areas: certificate generation instructions are given only for Windows (using Command Prompt and Powershell), with no Linux or macOS equivalents; Windows-specific patterns (e.g., Win+R, %USERPROFILE%) are referenced; and the sample code is tailored to Visual Studio and NuGet, which are primarily Windows tools. There are no Linux shell or OpenSSL examples for certificate management, nor instructions for running the sample code on Linux or macOS.
Recommendations
  • Add Linux and macOS instructions for certificate generation, such as using OpenSSL or the step CLI in Bash.
  • Provide Bash shell commands and file path examples for Linux/macOS environments.
  • Include instructions for running the sample code with .NET CLI on Linux/macOS, and mention cross-platform IDEs like VS Code.
  • Avoid referencing Windows-specific shortcuts (e.g., Win+R, %USERPROFILE%) without providing Linux/macOS equivalents.
  • Ensure parity in CLI examples and troubleshooting steps for all major platforms.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page shows evidence of Windows bias in its handling of shell-specific escaping for topic templates. PowerShell is mentioned explicitly, and escaping examples are given only for PowerShell, with no equivalent examples for Linux shells (e.g., Bash, zsh). The documentation also refers to Azure CLI, which is cross-platform, but the only shell-specific guidance is Windows/PowerShell-centric. This may confuse or disadvantage Linux users who need to escape special characters differently.
Recommendations
  • Add equivalent examples for escaping special characters in common Linux shells (e.g., Bash, zsh), alongside the PowerShell examples.
  • Explicitly mention that shell escaping differs between platforms and provide guidance for both Windows and Linux users.
  • Consider reordering or grouping shell-specific instructions so that Linux and Windows users can easily find relevant information.
  • Where possible, use cross-platform syntax or clarify platform-specific differences to ensure parity.
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-10 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 PowerShell-based instructions and examples, which are most commonly used on Windows. There are no equivalent examples for Bash, Azure CLI, or other Linux-native tools. The script and workflow assume familiarity with PowerShell and Windows-centric patterns, with no mention of Linux or cross-platform alternatives.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts to ensure Linux users can follow the same workflow.
  • Explicitly mention cross-platform compatibility and clarify which steps or tools work on Linux/macOS.
  • Add notes or links to documentation for performing these tasks on Linux systems.
  • Consider including a table or section comparing PowerShell and Azure CLI commands for each step.
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-10 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 strong Windows bias. All scripting examples use PowerShell, and users are instructed to use the Azure Cloud Shell in PowerShell mode. There are no Bash or Linux-native shell examples, nor are Linux-specific tools or workflows mentioned. The use of PowerShell is assumed throughout, and steps involving CLI usage are always preceded by PowerShell-based configuration. This may hinder Linux users or those who prefer Bash or other shells.
Recommendations
  • Add equivalent Bash/Azure CLI examples for all PowerShell scripts.
  • Explicitly mention that Azure Cloud Shell supports Bash and provide instructions for using Bash.
  • Where possible, use cross-platform Azure CLI commands for configuration steps, or provide both PowerShell and Bash alternatives.
  • Clarify which steps are platform-agnostic and which require Windows/PowerShell, and offer Linux-friendly alternatives.
  • Include notes or links for Linux users on how to install and use Azure CLI and Microsoft Graph CLI tools.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and examples. The only code sample for the Cloud Events handshake is in C#, a language most commonly used on Windows. The command-line example for Azure Relay Bridge uses Windows path notation ('.\azbridge.exe'), which is not compatible with Linux/macOS shells. There are no explicit Linux or cross-platform code samples, nor are Linux-specific instructions or shell commands provided. The documentation references Azure CLI, which is cross-platform, but does not provide Linux-specific usage patterns or examples.
Recommendations
  • Provide equivalent code samples in a cross-platform language (e.g., Python, Node.js) or explicitly show Linux shell examples.
  • Include Linux/macOS command-line syntax for Azure Relay Bridge (e.g., './azbridge' instead of '.\azbridge.exe').
  • Add instructions or examples for running Azure Relay Bridge in Docker, which is mentioned as an option but not demonstrated.
  • Clarify that Azure CLI commands work on Linux/macOS and provide any OS-specific notes if needed.
  • Offer guidance for implementing the Cloud Events handshake in languages/environments commonly used on Linux.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently presenting Azure PowerShell examples alongside Azure CLI, and by referencing Windows-centric tools and patterns (such as PowerShell and Cloud Shell's PowerShell session). While Azure CLI (cross-platform) examples are present, PowerShell is given equal prominence, and there are no explicit Linux-specific examples (e.g., native Bash scripts outside Azure CLI, or Linux command-line patterns). Windows tools and terminology (PowerShell, Get-Random, Get-Date, ConvertTo-Json) are used without Linux equivalents or alternatives. The structure often lists PowerShell after CLI, but both are always present, and the Cloud Shell instructions mention both Bash and PowerShell, but do not provide a pure Linux terminal workflow.
Recommendations
  • Add explicit Linux/Bash-only examples for key workflows, such as using curl and jq to construct and send events, without relying on Azure CLI or PowerShell.
  • Clarify that Azure CLI commands work natively on Linux, macOS, and Windows, and provide OS-specific notes where relevant.
  • Remove or supplement PowerShell-specific instructions with equivalent Bash/Linux shell commands, especially for tasks like generating random IDs and formatting dates.
  • Include screenshots or terminal output from Linux environments, not just Azure portal or PowerShell.
  • Where Cloud Shell is mentioned, specify that Bash is available and provide Bash-centric instructions, rather than referencing PowerShell equally.
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-10 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 Application in Azure Event Grid. All examples and instructions are based on PowerShell, which is traditionally a Windows-centric tool, and there are no equivalent examples or guidance for Linux users (e.g., Bash, Azure CLI, or cross-platform scripting). The page assumes familiarity with PowerShell and does not mention or prioritize Linux-compatible alternatives.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts, which are natively supported on Linux and macOS.
  • Include cross-platform instructions and clarify which steps can be performed on any OS and which are Windows-specific.
  • Add a section comparing PowerShell and Azure CLI approaches, helping users choose the best tool for their environment.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, and provide installation guidance if PowerShell is required.
  • Ensure screenshots and portal instructions do not assume a Windows environment (e.g., avoid referencing Windows-only clipboard shortcuts).
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-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, Azure CLI) are referenced, and instructions for obtaining Azure region names use the Azure CLI without mentioning Linux alternatives or cross-platform usage. PowerShell is included as a primary code sample, and there is no explicit mention of Linux shell equivalents or setup instructions for Linux environments. The development environment setup and sample code links do not clarify Linux compatibility or provide Linux-specific guidance.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and provide example commands for both Windows (PowerShell/CMD) and Linux/macOS (bash/zsh).
  • Add Linux shell (bash) equivalents for commands like 'az account list-locations', including sample output and usage.
  • Include instructions or notes on setting up development environments on Linux, especially for languages like Python, Java, Node.js, and Go.
  • Provide sample code or links for Linux-based web application hosting (e.g., using Flask, Express, or Spring Boot on Linux).
  • Clarify that PowerShell examples can be run on Linux (PowerShell Core), or provide bash alternatives where appropriate.
  • Review referenced samples to ensure they include Linux deployment and usage instructions.
GitHub Create Pull Request
Event Grid Azure Resource Manager template samples - Event Grid | Microsoft Docs ...docs/blob/main/articles/event-grid/template-samples.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by listing PowerShell samples before CLI samples in the 'Next steps' section, suggesting a preference for Windows tooling. There is no mention of Bash or Linux-specific examples, and the only command-line reference is generic 'CLI', which may not fully address Linux users' needs. No Linux tools or patterns are highlighted, and PowerShell (a Windows-centric tool) is given prominence.
Recommendations
  • List CLI (az CLI) samples before PowerShell samples to avoid implying Windows-first workflows.
  • Explicitly mention Bash or Linux shell examples alongside PowerShell, or provide links to Linux-specific usage guides.
  • Add a section or note clarifying that all templates and examples are cross-platform and can be used on Linux, macOS, and Windows.
  • Where PowerShell is referenced, also provide equivalent Bash/az CLI commands for parity.
  • Consider including troubleshooting or usage notes for Linux users, such as authentication differences or environment setup.
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-10 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) first and in more detail, with only minimal Linux coverage (a single telnet command). Windows-specific tools are referenced and linked, while Linux alternatives are not discussed. Troubleshooting steps and command-line examples are predominantly Windows-centric, and Linux users are not provided with equivalent guidance or tool recommendations.
Recommendations
  • Provide Linux-first or cross-platform command examples (e.g., use 'nc', 'curl', or 'openssl' for port checks on Linux).
  • Include Linux-specific troubleshooting tools and instructions (e.g., mention 'tcping' for Linux, or how to install/use 'telnet', 'nc', or 'ss').
  • Balance the order of examples so that Linux and Windows are treated equally, or group them together under platform-specific headings.
  • Add links to Linux tool documentation and downloads, similar to the Windows tool references.
  • Explicitly mention platform differences and provide guidance for macOS users as well.
GitHub Create Pull Request
← Previous Page 2 of 12 Next →