Event Grid

586
Total Pages
552
Linux-Friendly Pages
34
Pages with Bias
5.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

83 issues found
Showing 1-25 of 83 flagged pages
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 lists PowerShell samples before CLI samples in the 'Next steps' section, suggesting a Windows-first approach. There is a specific mention of PowerShell, which is traditionally associated with Windows, and no explicit mention of Bash or Linux shell examples. The page lacks Linux-specific guidance or parity in examples.
Recommendations
  • List CLI (az CLI) samples before PowerShell samples to avoid Windows-first bias.
  • Add explicit Bash/Linux shell script examples for deploying and managing Event Grid resources.
  • Include notes or links for Linux users, such as installation and usage of Azure CLI on Linux.
  • Ensure that all sample templates and deployment instructions are cross-platform and clarify any platform-specific steps.
GitHub Create Pull Request
Event Grid Configure IP firewall for Azure Event Grid topics or domains ...cs/blob/main/articles/event-grid/configure-firewall.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 provides both Azure CLI and Azure PowerShell examples for configuring IP firewall rules for Azure Event Grid topics or domains. However, there is a notable emphasis on PowerShell, a Windows-centric tool, with a dedicated section and multiple examples. The documentation also refers to PowerShell-specific syntax and patterns, and does not mention or provide examples for Bash, Linux shell scripting, or other Linux-native tools. The PowerShell section appears after the CLI section, but the CLI examples are generic and do not address Linux-specific usage or considerations. There is no explicit Linux bias, and the CLI commands are cross-platform, but the presence of PowerShell examples and terminology may make the documentation feel more Windows-oriented.
Recommendations
  • Add explicit Bash/Linux shell examples alongside Azure CLI commands, including variable assignment and command chaining typical in Linux environments.
  • Clarify that Azure CLI commands are cross-platform and provide notes or examples for Linux/macOS users (e.g., differences in environment variable syntax).
  • Consider mentioning or linking to Linux-specific troubleshooting or scripting resources.
  • Balance PowerShell examples with equivalent Bash or shell script examples to ensure parity for Linux users.
  • Avoid using Windows-specific terminology (e.g., PowerShell) without providing Linux alternatives.
GitHub Create Pull Request
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references running CLI or PowerShell commands to find property aliases, but does not provide explicit examples for either platform. However, by mentioning PowerShell alongside CLI (which is often interpreted as Azure CLI, available cross-platform), there is a subtle Windows-first bias, as PowerShell is traditionally associated with Windows. No Linux-specific tools or shell examples (e.g., bash) are provided, and there is no explicit parity in instructions for Linux users.
Recommendations
  • Provide explicit Azure CLI command examples, as Azure CLI is cross-platform and preferred by many Linux users.
  • If PowerShell examples are given, also provide equivalent bash or shell script examples for Linux.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and link to installation instructions for all platforms.
  • Avoid mentioning PowerShell before CLI unless both are given equal prominence and examples.
  • Add a section or note for Linux/macOS users to ensure they are equally supported in the documentation.
GitHub Create Pull Request
Event Grid Webhooks as event handlers for Azure Event Grid events ...docs/blob/main/articles/event-grid/handler-webhooks.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 listing PowerShell examples alongside Azure CLI and Portal, and by referencing Microsoft Teams and Azure Automation runbooks, which are more commonly used in Windows-centric environments. PowerShell is mentioned as a primary automation tool, and Windows tools/patterns (such as Azure Automation and Teams integration) are highlighted without equivalent Linux-native alternatives or examples. Linux-specific tools, shell scripts, or automation patterns are not mentioned or demonstrated.
Recommendations
  • Add Linux shell (bash) examples for all quickstarts and tutorials, especially for webhook creation and event handling.
  • Include references to Linux-native automation tools (e.g., cron jobs, systemd services, or Ansible playbooks) as possible event handlers via webhooks.
  • Provide parity in examples by listing CLI/bash examples before or alongside PowerShell, rather than always including PowerShell.
  • Mention Linux-compatible notification tools (e.g., Slack, Mattermost, or email via sendmail) in addition to Microsoft Teams.
  • Clarify that Azure Automation runbooks can be authored and triggered from Linux environments, and provide examples if possible.
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 and detail as Azure CLI. There are no explicit Linux shell (bash/curl) examples for publishing events, nor are Linux-specific tools or patterns mentioned. The documentation does not show how to use native Linux utilities (e.g., curl, wget) to POST events, and PowerShell is presented as a first-class option throughout, which may imply a Windows bias.
Recommendations
  • Add explicit bash/curl examples for publishing events to the Event Grid domain endpoint, showing how to POST JSON using standard Linux tools.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, while PowerShell is primarily a Windows tool (though it is available cross-platform).
  • Where HTTP requests are required, provide both PowerShell and bash/curl examples side-by-side.
  • Consider listing Azure CLI examples before PowerShell, or note that CLI is platform-neutral.
  • Add troubleshooting notes or tips for Linux users, such as installing Azure CLI or using curl for REST API calls.
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 documentation demonstrates a Windows bias by exclusively using Visual Studio for publishing the Azure Functions app and running the sample projects, with no mention of cross-platform alternatives like VS Code or CLI-based deployment. The prerequisites and instructions assume a Windows development environment, and there are no examples or guidance for Linux or macOS users for building, publishing, or running the sample code.
Recommendations
  • Include instructions for publishing the Azure Functions app using cross-platform tools such as Azure CLI, Azure Functions Core Tools, or Visual Studio Code.
  • Add guidance for building and running the sample projects on Linux and macOS, including .NET CLI commands and any required dependencies.
  • Update prerequisites to mention cross-platform development environments and tools, not just Visual Studio.
  • Provide alternative steps for users who do not use Visual Studio, such as using VS Code or command-line tools for .NET and Azure Functions.
  • Ensure screenshots and walkthroughs are not exclusively from Windows environments; include examples from Linux/macOS where applicable.
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 ways: certificate generation instructions and examples are provided only for Windows (using Command Prompt and Powershell), with no equivalent Linux or macOS shell commands. The sample code section references Visual Studio and NuGet package installation in a Windows-centric manner, without mentioning cross-platform alternatives. The initial instructions for certificate creation mention 'Consider installing manually for Windows' and direct users to open a Command Prompt, but do not provide Linux or macOS guidance. No Linux shell or OpenSSL examples are given for certificate creation, and the .NET sample code is presented with Windows tooling in mind.
Recommendations
  • Provide equivalent certificate generation instructions and examples for Linux and macOS, using bash and OpenSSL or step CLI in a Unix shell.
  • Include cross-platform guidance for running the sample code, such as using VS Code, JetBrains Rider, or .NET CLI, and mention NuGet installation via dotnet CLI.
  • Add explicit instructions for Linux/macOS users on where to run commands and how to locate certificate files.
  • Ensure all CLI commands and code samples are presented in a platform-neutral way, or provide parallel examples for each major OS.
  • Avoid referencing Windows-specific shortcuts (e.g., Win+R) without alternatives for other 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% and using PowerShell commands), with no equivalent Linux or macOS instructions provided. The phrase 'Consider installing manually for Windows' implies a Windows-first approach, and there are no Bash or Linux terminal examples for certificate generation. The rest of the guide is platform-neutral, focusing on Azure Portal and MQTTX app, which are cross-platform.
Recommendations
  • Add explicit instructions and command examples for Linux and macOS users, including how to open a terminal and navigate to the appropriate directory.
  • Provide Bash shell equivalents for all certificate generation commands, including file path conventions and environment variables (e.g., $HOME instead of %USERPROFILE%).
  • Clarify that the step CLI is cross-platform and link to installation guides for Linux and macOS.
  • Avoid using Windows-specific terminology (such as 'Win+R') without providing cross-platform alternatives.
  • Where screenshots or instructions are OS-specific, include alternatives for other platforms.
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: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows, as it exclusively provides PowerShell examples and references PowerShell modules (e.g., Microsoft.Graph.PowerShell). There are no Linux or cross-platform CLI examples, and the instructions assume the use of Windows tools and patterns. The use of PowerShell and Microsoft-specific tooling is presented as the default and only option, with no mention of alternatives such as Azure CLI, REST API, or scripting in Bash.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash, which are cross-platform and commonly used on Linux.
  • Include instructions for performing the same tasks using REST API calls, which are platform-agnostic.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, and clarify compatibility if PowerShell is required.
  • Add notes or sections for Linux users, including installation and usage of necessary tools.
  • Reorder or supplement examples so that cross-platform approaches are presented alongside or before Windows-specific methods.
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 Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell scripts and the Azure Portal (which is Windows-centric) for configuration steps. All code examples and referenced scripts are in PowerShell, with no Bash, Linux shell, or cross-platform alternatives provided. The instructions repeatedly direct users to use the Azure Shell in PowerShell mode, and there is no mention of Linux-native tools or workflows. The use of Windows tools and patterns is pervasive, and Linux users are left without guidance for equivalent steps.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for all PowerShell examples, ensuring Linux users can follow along without switching environments.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash for Linux users.
  • Add step-by-step instructions for configuring Microsoft Entra ID and Event Grid subscriptions using Linux-native tools and workflows.
  • Reference cross-platform SDKs (e.g., Python, Node.js) for automation, and provide sample code in those languages.
  • Ensure that all referenced scripts (currently PowerShell-only) have Linux shell or Azure CLI equivalents, and link to them.
  • Review diagrams and screenshots to ensure they do not reinforce a Windows-only workflow.
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 consistently presents Azure PowerShell (a Windows-centric tool) examples alongside Azure CLI, and references Azure portal and Cloud Shell (which defaults to PowerShell for many users). PowerShell examples are given equal prominence to CLI, and Windows tools/patterns (PowerShell, Azure portal) are mentioned before or alongside Linux-friendly equivalents. There is a slight Windows-first bias in the ordering and tool selection, but Linux parity is present via Azure CLI and Bash examples.
Recommendations
  • Explicitly mention that Azure CLI and Bash examples work natively on Linux/macOS and in WSL environments.
  • Provide a clear separation between PowerShell and Bash/CLI examples, and consider listing Bash/CLI first to reduce perceived Windows-first bias.
  • Add a note clarifying that Azure PowerShell is available cross-platform, but Bash/CLI is the default on Linux.
  • Include troubleshooting tips or notes for Linux users (e.g., curl installation, date formatting differences).
  • Ensure screenshots and instructions for Azure portal/Cloud Shell show both Bash and PowerShell session options, with Bash as default for Linux users.
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 providing command-line examples using Windows-style paths and executables (e.g., .\azbridge.exe), referencing .NET/C# code samples exclusively, and omitting explicit Linux or cross-platform examples for key steps. Windows tools and patterns (such as .NET SDK and Windows executable invocation) are mentioned before or instead of Linux equivalents, and there is no mention of Linux-specific commands or shell usage.
Recommendations
  • Provide equivalent Linux shell commands and examples (e.g., using ./azbridge or Docker invocation).
  • Include code samples in additional languages (such as Python, Node.js) to demonstrate cross-platform implementation.
  • Clarify that Azure Relay Bridge can be run on Linux and show Docker-based usage explicitly.
  • Add instructions for installing and running Azure Relay Bridge on Linux, including permissions and executable usage.
  • Mention Linux-friendly tools and patterns (such as bash scripts, systemd services) where appropriate.
  • Ensure that examples and instructions do not assume Windows paths or conventions by default.
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 Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page 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 example language. There is an implicit prioritization of Windows development environments, with no explicit mention of Linux equivalents for certain steps (e.g., obtaining Azure region names, setting up development environments, or running CLI commands on Linux/macOS). Additionally, the sample code and setup instructions do not clarify cross-platform compatibility, and there is no guidance for Linux users regarding prerequisites, environment setup, or alternative tools.
Recommendations
  • Explicitly state that Azure CLI and all code samples can be run on Linux/macOS as well as Windows, and provide installation/setup instructions for Linux environments.
  • Include Linux/macOS-specific examples or notes for commands like 'az account list-locations', clarifying shell usage and potential differences.
  • Add guidance for setting up development environments on Linux, including authentication, SDK installation, and any OS-specific considerations.
  • Ensure that PowerShell examples are accompanied by Bash or shell script equivalents where relevant, or clarify that PowerShell Core is cross-platform.
  • Review referenced samples and documentation links to ensure Linux parity and highlight any OS-specific steps or requirements.
GitHub Create Pull Request
Event Grid Troubleshoot network connectivity issues - Azure Event Grid | Microsoft Docs ...ticles/event-grid/troubleshoot-network-connectivity.md
Medium Priority View Details →
Scanned: 2026-01-25 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 frequently presents Windows/PowerShell examples and tools (e.g., psping.exe) first, with Linux alternatives either mentioned after or omitted. Some troubleshooting commands are only shown for Windows (psping.exe), while Linux users are only briefly referenced (telnet) without parity in advanced troubleshooting steps. The use of Windows-specific tools and the lack of equivalent Linux/macOS commands in some sections create friction for non-Windows users.
Recommendations
  • Provide Linux/macOS equivalents for all troubleshooting commands, such as using 'nc' (netcat) or 'nmap' for port checks and connection tests.
  • When introducing tools like psping.exe, also mention cross-platform alternatives (e.g., 'hping3', 'nc', or 'nmap') and provide example commands.
  • Ensure that Linux/macOS examples are given equal prominence, ideally presenting both Windows and Linux/macOS commands side by side.
  • Avoid referencing Windows tools (like .exe utilities) without Linux/macOS counterparts, or clearly state if a step is Windows-only and provide alternatives where possible.
GitHub Create Pull Request
Event Grid Troubleshoot network connectivity issues - Azure Event Grid | Microsoft Docs ...ticles/event-grid/troubleshoot-network-connectivity.md
Medium Priority View Details →
Scanned: 2026-01-24 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 shows a notable Windows bias: network connectivity test examples use Windows tools (psping.exe) and PowerShell syntax first, with only a minimal Linux example (telnet) provided. In the transient issues section, only Windows tools are mentioned for packet testing, and Linux alternatives (like nc, nmap, or tcpping for Linux) are not discussed. This may cause friction for Linux/macOS users who need equivalent troubleshooting steps.
Recommendations
  • Provide Linux/macOS equivalents for all network testing commands (e.g., use nc, nmap, or tcpping for Linux/macOS).
  • Present examples for both Windows and Linux/macOS side by side, or clearly label them.
  • List cross-platform tools (such as curl, nc, or nmap) where possible, and not just Windows-specific tools.
  • When referencing downloadable tools (like psping.exe), mention if there are Linux/macOS alternatives or equivalents.
GitHub Create Pull Request
Event Grid Troubleshoot network connectivity issues - Azure Event Grid | Microsoft Docs ...ticles/event-grid/troubleshoot-network-connectivity.md
Medium Priority View Details →
Scanned: 2026-01-23 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 shows a notable Windows bias. Network connectivity troubleshooting commands are presented first and primarily using Windows tools (psping.exe, PowerShell syntax), with Linux alternatives either missing or only briefly mentioned. Some sections provide only Windows examples, and Linux users are left to infer equivalent commands or tools.
Recommendations
  • Provide Linux/macOS equivalents for all troubleshooting commands (e.g., use 'nc', 'telnet', or 'nmap' for port checks, and 'hping3' or 'tcping' for TCP tests).
  • List Linux/macOS commands alongside Windows commands, not after or as an afterthought.
  • When referencing downloadable tools (like psping.exe), suggest cross-platform alternatives or note their platform limitations.
  • Include example outputs for both Windows and Linux commands to help users interpret results.
  • Avoid using Windows-specific paths or syntax (e.g., '.\psping.exe') without also providing the Linux equivalent.
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
Medium Priority View Details →
Scanned: 2026-01-22 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 in the certificate generation section, where all example commands use PowerShell syntax and Windows-specific instructions (e.g., opening Command Prompt via Win+R and %USERPROFILE%). There are no Linux or macOS equivalents provided for generating certificates, viewing thumbprints, or file path conventions. The rest of the CLI instructions are cross-platform, but the initial setup creates friction for non-Windows users.
Recommendations
  • Provide Linux/macOS shell (bash) equivalents for certificate generation and thumbprint commands using step CLI.
  • Include instructions for opening a terminal and navigating to the user profile/home directory on Linux/macOS.
  • Use platform-neutral file path examples or clarify differences between Windows and Unix-like systems.
  • Explicitly state that the step CLI is cross-platform and link to installation instructions for Linux/macOS.
  • Add notes or tabs to switch between Windows and Linux/macOS instructions where commands differ.
GitHub Create Pull Request
Event Grid Authenticate Event Grid publishing clients using Microsoft Entra ID ...les/event-grid/authenticate-with-microsoft-entra-id.md
Medium Priority View Details →
Scanned: 2026-01-12 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 exhibits moderate Windows bias. While the core authentication and SDK usage instructions are cross-platform, platform-specific tooling examples (Azure PowerShell and Azure portal) are presented, and the PowerShell example is given in full detail. The Azure CLI example is present (which is cross-platform), but there are no explicit Linux/macOS shell or scripting examples, nor are there references to Linux-specific patterns or troubleshooting. The portal instructions are generic but often assume familiarity with the Windows-centric Azure portal UI. The PowerShell example is provided after the CLI, but both are present. There are no bash or Linux-native scripting examples for resource creation or management.
Recommendations
  • Add explicit bash or shell scripting examples for Linux/macOS users, especially for environment variable setup and SDK usage.
  • Include troubleshooting notes or platform-specific caveats for Linux/macOS environments (e.g., authentication issues, SDK installation differences).
  • Clarify that Azure CLI is cross-platform and recommend it as the preferred tool for Linux/macOS users.
  • Provide parity in resource management examples (e.g., show how to disable local authentication using bash/CLI on Linux).
  • Consider adding screenshots or instructions for Azure portal usage on non-Windows platforms, if relevant.
GitHub Create Pull Request
Event Grid CloudEvents v1.0 schema with Azure Event Grid ...cs/blob/main/articles/event-grid/cloud-event-schema.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring Event Grid topics and subscriptions, but PowerShell (a Windows-centric tool) is given equal prominence. In the Azure Functions section, Visual Studio and Visual Studio Code are mentioned as primary development environments, with detailed instructions for NuGet package management in Visual Studio (a Windows tool). There are no Linux/macOS-specific instructions or examples for package management or development workflows, and PowerShell examples are included without Bash or shell equivalents.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, such as using Bash or zsh for scripting and package management.
  • Provide parity for package management steps in cross-platform editors (e.g., show how to update NuGet packages using dotnet CLI or VS Code on Linux/macOS).
  • Include Bash equivalents for PowerShell commands, especially for resource ID extraction and scripting.
  • Clarify that Azure CLI is cross-platform and highlight its usage for non-Windows environments.
  • Mention alternative editors (e.g., JetBrains Rider) and workflows for Linux/macOS users.
GitHub Create Pull Request
Event Grid Send Blob storage events to web endpoint - template .../articles/event-grid/blob-event-quickstart-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation primarily demonstrates deployment via the Azure Portal, with only a brief mention of Azure PowerShell, Azure CLI, and REST API as alternative methods. The link for 'other deployment methods' points to a PowerShell-focused page, and no explicit Linux/macOS CLI examples or instructions are provided. The workflow and tooling references are Windows-centric, with Azure Portal and PowerShell mentioned before CLI or REST, and no Linux-specific guidance is offered.
Recommendations
  • Add explicit Azure CLI examples for template deployment, including command-line instructions suitable for Linux/macOS users.
  • Provide links to both PowerShell and Azure CLI documentation, ensuring CLI instructions are not secondary.
  • Include a section or callout for Linux/macOS users, clarifying that all steps can be completed using Azure CLI on those platforms.
  • Reorder references so that Azure CLI and REST API are mentioned alongside or before PowerShell, to avoid Windows-first perception.
GitHub Create Pull Request
Event Grid Configure private endpoints for topics or domains ...ain/articles/event-grid/configure-private-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides extensive Azure Portal (GUI) instructions and full PowerShell scripts for managing private endpoints, which are Windows-centric tools. While Azure CLI examples are included and are cross-platform, PowerShell coverage is more detailed and is presented after the CLI section. There are no Linux/macOS-specific examples, nor is Bash scripting or Linux-native tooling discussed. The Azure Portal instructions are platform-neutral but implicitly favor Windows due to historical usage patterns. PowerShell is a Windows-first tool, though it is available on Linux, but most Linux users prefer Bash/CLI.
Recommendations
  • Add Bash script equivalents for all PowerShell examples, using Azure CLI.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
  • Consider reordering sections to present CLI/Bash examples before PowerShell.
  • Add notes or links for Linux/macOS users regarding prerequisites (e.g., installing Azure CLI).
  • Clarify that PowerShell is available cross-platform, but Bash/CLI is more common on Linux/macOS.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI (Bash) and Azure PowerShell examples for sending events, but PowerShell is given equal prominence and detail, and instructions for switching between Bash and PowerShell are included. However, there is a subtle Windows-first bias: PowerShell is highlighted as an alternative, and the use of Visual Studio Code (with screenshots) may implicitly favor Windows workflows. There are no Linux-specific tools or examples (e.g., native Linux shell scripts), and PowerShell is not typically a default shell on Linux/macOS. The CLI example uses Bash, which is cross-platform, but the PowerShell example may create friction for Linux/macOS users.
Recommendations
  • Add explicit Linux/macOS instructions for using Azure CLI and cURL from a local terminal, not just Cloud Shell.
  • Clarify that Azure CLI and cURL commands work natively on Linux/macOS, and provide example terminal screenshots from those platforms.
  • De-emphasize PowerShell as a primary alternative, or note its availability on Linux/macOS if relevant.
  • Consider including a Linux shell script example for sending events, or mention how to install Azure CLI and cURL on Linux/macOS.
  • Ensure that screenshots and instructions do not assume a Windows environment (e.g., file paths, UI layout).
GitHub Create Pull Request
Event Grid Integrate Azure Automation with Event Grid | Microsoft Docs ...ent-grid/ensure-tags-exists-on-new-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The tutorial exclusively uses PowerShell cmdlets (e.g., Update-AzureRmVM) for automation tasks, with no mention of Linux/macOS alternatives such as Azure CLI or Bash scripting. All code examples and module references are Windows-centric, and there are no instructions or examples for performing the same actions from Linux or macOS environments.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for all PowerShell commands, especially for VM tagging and automation tasks.
  • Clarify that Azure Automation runbooks can be authored in Python or other languages, and link to relevant documentation.
  • Add notes or sections for Linux/macOS users, including how to import modules and interact with Azure resources using non-Windows tools.
  • Reorder examples or provide parallel instructions so that Windows and Linux/macOS users are equally supported.
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
Medium Priority View Details →
Scanned: 2026-01-12 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 is heavily oriented toward Windows users, with all instructions and screenshots referencing Visual Studio, Windows UI elements, and PowerShell commands for package installation. There are no examples or guidance for Linux/macOS users, such as using VS Code, JetBrains Rider, or .NET CLI commands. This creates friction for non-Windows users attempting to follow the quickstart.
Recommendations
  • Add instructions for creating and running .NET console apps using cross-platform tools like VS Code and the .NET CLI (e.g., 'dotnet new console', 'dotnet add package').
  • Include Linux/macOS-specific guidance for installing .NET SDK and running applications.
  • Provide screenshots or descriptions for non-Windows environments, or clarify that the steps are similar across platforms.
  • Replace PowerShell-specific package installation commands with .NET CLI equivalents, or provide both.
  • Explicitly state platform requirements and alternatives for users not on Windows.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Visual Studio Only Missing Linux Example
Summary
The tutorial exhibits Windows bias primarily by requiring Visual Studio for publishing the Azure Functions app and running the sample projects, with no mention of Linux/macOS alternatives (such as VS Code, Azure Functions Core Tools, or .NET CLI). All development and deployment instructions assume a Windows environment and Visual Studio, and the sample projects are described as .sln solutions, which are not natively supported on Linux/macOS. While Azure CLI is used for infrastructure deployment (which is cross-platform), the critical steps for code publishing and running the sample app lack Linux/macOS guidance.
Recommendations
  • Add instructions for publishing the Azure Functions app using Azure Functions Core Tools or .NET CLI, which work on Linux/macOS.
  • Include guidance for using VS Code or other cross-platform editors to open and work with the sample project.
  • Provide steps for running the sample data generator (WindTurbineDataGenerator) on Linux/macOS, including any necessary build or runtime instructions.
  • Explicitly mention that the Azure CLI steps work on Linux/macOS and clarify any platform-specific differences.
  • Consider providing Docker-based instructions for running the sample apps to ensure platform neutrality.
GitHub Create Pull Request
← Previous Page 1 of 4 Next →