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 151-175 of 289 flagged pages
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-13 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 displays moderate Windows bias in several areas. While the core authentication concepts are platform-neutral, operational examples and tooling references favor Windows. The Azure PowerShell example is provided for disabling local authentication, but there is no equivalent Bash or Linux shell example. The Azure CLI example is present (which is cross-platform), but the PowerShell example is given its own section and is more detailed. References to enabling managed identities on VMs link to Windows VM instructions first, with no explicit mention of Linux VMs. No Linux/macOS-specific guidance or troubleshooting is provided, and all code samples are in C# (.NET), which is most commonly used on Windows.
Recommendations
  • Add explicit Linux VM managed identity configuration links and examples.
  • Provide Bash or Linux shell equivalents for PowerShell commands, especially for resource creation and configuration.
  • Include code samples in additional languages (e.g., Python, JavaScript) and clarify that SDKs are cross-platform.
  • Balance the order of CLI and PowerShell examples, or combine them in a single section to avoid platform prioritization.
  • Add troubleshooting notes or tips for Linux/macOS users where platform differences may impact authentication or SDK usage.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation primarily describes deployment via the Azure Portal and mentions Azure PowerShell, Azure CLI, and REST API as alternatives, but links only to PowerShell instructions. There are no explicit Linux/macOS examples or CLI instructions, and the deployment workflow is centered around the graphical Azure Portal, which is more familiar to Windows users. The mention of PowerShell before CLI and the lack of direct Linux/macOS guidance creates friction for non-Windows users.
Recommendations
  • Add explicit Azure CLI instructions for deploying the ARM template, including example commands.
  • Provide links to both PowerShell and CLI deployment guides, with CLI shown first or equally.
  • Include notes or examples for Linux/macOS users, such as using the Azure CLI in Bash.
  • Clarify that the Azure Portal is cross-platform, but also highlight command-line alternatives for users who prefer or require them.
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-13 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 is a Windows-centric tool and is featured equally alongside the cross-platform Azure CLI. The Visual Studio instructions for Azure Functions use Windows-specific tooling and UI patterns (e.g., NuGet Package Manager Console, Solution Explorer), with no mention of Linux/macOS equivalents. The CLI examples are shown first, but PowerShell is given equal prominence, and there are no Linux/macOS-specific instructions or alternative editors/tools discussed.
Recommendations
  • Prioritize Azure CLI examples, as it is cross-platform, and clearly indicate PowerShell is Windows-only.
  • Add explicit instructions for Linux/macOS users, such as using VS Code with .NET Core CLI for Azure Functions development.
  • Include package installation instructions using dotnet CLI (e.g., 'dotnet add package') for cross-platform scenarios.
  • Mention alternative editors (e.g., JetBrains Rider, VS Code) and workflows for non-Windows environments.
  • Clarify that Visual Studio instructions are Windows-specific and provide parity for Linux/macOS users.
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-13 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 notable Windows bias by exclusively referencing Visual Studio for publishing Azure Functions and running the sample application, with no mention of cross-platform alternatives such as VS Code, Azure Functions Core Tools, or .NET CLI. All development and deployment steps assume a Windows environment, and there are no Linux/macOS-specific instructions or examples. While Azure CLI is used for infrastructure deployment (which is cross-platform), the lack of Linux/macOS development guidance creates friction for non-Windows users.
Recommendations
  • Add instructions for publishing Azure Functions using VS Code, Azure Functions Core Tools, or .NET CLI, which are cross-platform.
  • Include examples for running the sample application on Linux/macOS, such as using 'dotnet run' or building/running with .NET CLI.
  • Clarify that Visual Studio is optional and provide parity for Linux/macOS users in all development steps.
  • Mention prerequisites for Linux/macOS environments, such as .NET SDK installation and compatible editors.
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-13 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 primarily Windows-centric. All code examples are in PowerShell, with no mention of Bash, Azure CLI, or Linux/macOS alternatives. The tutorial assumes use of Windows tooling and patterns, making it less accessible for Linux/macOS users.
Recommendations
  • Provide equivalent Bash or Azure CLI examples for all PowerShell commands.
  • Mention cross-platform tools and clarify which steps are OS-agnostic (e.g., Azure Portal actions).
  • Explicitly state that Azure Automation runbooks can use Python or other languages, and link to relevant cross-platform documentation.
  • Add a section or notes for Linux/macOS users, including how to install and use Azure CLI for resource management.
GitHub Create Pull Request
Event Grid Webhooks as event handlers for Azure Event Grid events ...docs/blob/main/articles/event-grid/handler-webhooks.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page lists both Azure CLI and PowerShell quickstarts for core webhook scenarios, but PowerShell (a Windows-centric tool) is featured equally and sometimes before Linux-native alternatives. There is no explicit mention of Linux/macOS-specific tools or examples, and PowerShell is presented as a primary option, which may create friction for non-Windows users.
Recommendations
  • Ensure that Azure CLI examples are presented before PowerShell, as CLI is cross-platform.
  • Add explicit notes clarifying that PowerShell is available on Linux/macOS, or provide Bash examples where appropriate.
  • Include links or references to Linux/macOS-specific guidance for webhook endpoints and automation.
  • Consider adding a table or section comparing cross-platform tooling for each scenario.
GitHub Create Pull Request
Event Grid Azure Event Grid Namespace MQTT client authentication using certificate chain ...t-grid/mqtt-certificate-chain-client-authentication.md
Medium Priority View Details →
Scanned: 2026-01-13 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, with no equivalent Linux/macOS shell commands or guidance. The installation note for 'step CLI' mentions Windows specifically, and all sample commands are shown in PowerShell syntax, creating friction for Linux/macOS users who would need to adapt the steps themselves.
Recommendations
  • Provide equivalent certificate generation commands for Linux/macOS (e.g., bash shell examples).
  • Clarify that 'step CLI' is cross-platform and provide installation instructions for Linux/macOS.
  • Show both Windows (PowerShell) and Linux/macOS (bash) command examples side-by-side where relevant.
  • Avoid language that implies Windows is the default platform unless truly required.
GitHub Create Pull Request
Event Grid Dead letter and retry policies - Azure Event Grid ...blob/main/articles/event-grid/manage-event-delivery.md
Medium Priority View Details →
Scanned: 2026-01-13 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 dead-letter and retry policies in Azure Event Grid. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented as a primary automation option. There are explicit instructions for installing Azure PowerShell, but no equivalent guidance for Bash or Linux shell environments. The related sample application is .NET-based, which is also more common on Windows. There are no Linux/macOS-specific examples or troubleshooting notes, and PowerShell examples may not be directly usable on non-Windows platforms.
Recommendations
  • Clarify that Azure CLI works cross-platform (Windows, Linux, macOS) and recommend it as the primary automation tool for non-Windows users.
  • Add Bash or shell script equivalents for all PowerShell examples, especially for variable assignment and command chaining.
  • Provide installation and troubleshooting notes for Azure CLI on Linux/macOS, similar to the PowerShell installation note.
  • Include links to sample applications in other languages (e.g., Python, Node.js) that are popular on Linux/macOS.
  • Explicitly state platform compatibility for each tool and example.
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-13 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 only Windows-specific instructions and PowerShell commands are provided. The instructions reference opening a Command Prompt and using Windows environment variables, with no equivalent Linux/macOS guidance. The sample code section references Visual Studio and NuGet package installation, which are Windows-centric, and does not mention Linux/macOS development environments or alternatives. There are no explicit Linux or macOS examples for certificate generation, development setup, or running the sample code.
Recommendations
  • Add Linux/macOS instructions for certificate generation, including shell commands and file paths.
  • Provide cross-platform guidance for running the sample code, such as using VS Code, JetBrains Rider, or CLI tools.
  • Include Linux/macOS examples for installing dependencies (e.g., using dotnet CLI for NuGet packages).
  • Avoid referencing Windows-specific environment variables and tools without alternatives.
  • Present examples for all platforms side-by-side or indicate platform-specific steps clearly.
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
Medium Priority View Details →
Scanned: 2026-01-13 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 focused on PowerShell, with all examples and scripts provided in Azure PowerShell syntax. There are no Bash, CLI, or Linux-native examples, and the workflow assumes use of PowerShell and Windows-centric tooling. The instructions and sample script do not mention or provide alternatives for Linux/macOS users, nor do they clarify cross-platform compatibility of the PowerShell modules used.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples for Linux/macOS users.
  • Clarify whether the PowerShell modules (e.g., Microsoft.Graph) are supported and easily installable on Linux/macOS, and provide installation instructions if so.
  • Explicitly mention cross-platform support and any prerequisites for running the script on non-Windows systems.
  • Consider presenting CLI/Bash examples before or alongside PowerShell examples to avoid Windows-first bias.
GitHub Create Pull Request
Event Grid Secure WebHook delivery with Microsoft Entra ID ...ob/main/articles/event-grid/secure-webhook-delivery.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell-based setup scripts and instructions, referencing the Azure Cloud Shell in PowerShell mode, and omitting equivalent Bash/Linux shell examples. The CLI steps are present but are secondary to the PowerShell workflow, and there are no explicit instructions or scripts for Linux/macOS users to perform the same setup outside of PowerShell.
Recommendations
  • Provide equivalent Bash scripts for all PowerShell examples, especially for steps involving Microsoft Graph and service principal role assignments.
  • Explicitly mention how Linux/macOS users can perform each step, including using Azure CLI and REST APIs where possible.
  • Reference the Bash environment in Azure Cloud Shell alongside PowerShell, and clarify which commands are cross-platform.
  • Ensure that CLI examples are given equal prominence and detail as PowerShell examples, not just as a follow-up.
  • Add troubleshooting notes for Linux/macOS users, especially regarding authentication and permissions.
GitHub Create Pull Request
Event Grid Publish Events to Azure Event Grid Custom Topics .../blob/main/articles/event-grid/post-to-custom-topic.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major steps, but PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI. In several sections, PowerShell examples are shown alongside CLI, and the Azure portal instructions reference Cloud Shell, which supports both Bash and PowerShell but does not explicitly highlight Linux-native workflows. There are no Linux/macOS-specific examples (e.g., using native curl or scripting outside Azure CLI), and Windows tools/patterns (PowerShell) are given as a primary option throughout.
Recommendations
  • Add explicit Linux/macOS examples using native tools (e.g., curl, bash scripting) outside Azure CLI.
  • Clarify that Azure CLI works cross-platform and highlight Bash as a first-class option for Linux/macOS users.
  • Reorder examples to show Azure CLI/Bash first, followed by PowerShell, to reduce Windows-first perception.
  • Include notes or sections for Linux/macOS users about prerequisites and environment setup.
  • Avoid assuming PowerShell is universally available; mention alternatives for Linux/macOS.
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
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides a PowerShell script for configuring secure webhook delivery with Microsoft Entra Application in Azure Event Grid. There are no examples or guidance for performing these steps using cross-platform tools (such as Azure CLI or Bash scripts), and the script relies on PowerShell modules (e.g., Microsoft.Graph), which are more commonly used and supported on Windows. The instructions and screenshots also assume use of the Azure Portal, with no mention of CLI alternatives.
Recommendations
  • Provide equivalent instructions and sample scripts using Azure CLI and/or Bash, which are natively supported on Linux/macOS.
  • Mention that PowerShell Core is available cross-platform, and provide installation guidance for non-Windows users if PowerShell is required.
  • Where possible, show both PowerShell and CLI/Bash examples side-by-side.
  • Include notes about any platform-specific prerequisites or limitations.
  • Add links to Microsoft Graph API documentation for users who may wish to automate using REST calls from any OS.
GitHub Create Pull Request
Event Grid Send events to webhooks hosted in private destinations ...vent-grid/send-events-webhooks-private-destinations.md
Medium Priority View Details →
Scanned: 2026-01-13 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 exhibits a moderate Windows bias. Examples and code samples are primarily in C# and use Windows-centric patterns (e.g., .NET SDK, Windows-style CLI invocation). The Azure Relay Bridge example uses a Windows executable invocation ('.\azbridge.exe'), and no explicit Linux/macOS command-line equivalents or code samples are provided. The validation handshake sample is only in C#, with no mention of how to implement it in other languages or platforms. While Azure CLI is mentioned (which is cross-platform), the overall guidance and examples favor Windows environments.
Recommendations
  • Provide equivalent code samples for Linux/macOS environments, such as Python, Node.js, or Bash.
  • Show how to run Azure Relay Bridge on Linux/macOS, including Docker usage and Linux command-line syntax.
  • Include examples of webhook validation handshake in other languages (e.g., Python Flask, Node.js Express).
  • Clarify that Azure CLI commands work cross-platform and provide shell syntax for Linux/macOS.
  • Avoid Windows-specific executable invocation (e.g., '.\azbridge.exe') and show Linux usage (e.g., './azbridge', 'docker run ...').
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-13 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 by presenting Windows/Powershell examples and tools (psping.exe, tcpping.exe) first and in detail, while Linux alternatives are mentioned briefly or omitted. The primary troubleshooting commands use Windows-specific executables, and Linux/macOS users are only offered a basic telnet example, which is less suitable for TCP connectivity testing. No Linux-native tools (e.g., nc, nmap, hping) are suggested for equivalent tasks.
Recommendations
  • Provide Linux/macOS equivalents for all troubleshooting commands, such as using 'nc' (netcat), 'nmap', or 'hping' for port and packet checks.
  • List Linux/macOS examples alongside or before Windows examples to ensure parity.
  • Mention cross-platform tools (e.g., Wireshark) more prominently and clarify their usage on different OSes.
  • Avoid referencing Windows-only tools (psping.exe, tcpping.exe) without offering alternatives for other platforms.
  • Add explicit instructions or command examples for macOS users where applicable.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing the Azure Portal for deployment and mentioning Azure PowerShell as an alternative method before Azure CLI and REST API. There are no explicit Linux or cross-platform command-line examples, and no mention of Linux-specific tools or patterns. The deployment workflow and resource cleanup instructions are portal-centric, which is more familiar to Windows users, and the CLI alternative is not demonstrated or prioritized.
Recommendations
  • Provide explicit Azure CLI examples for deployment and resource cleanup alongside PowerShell and portal instructions.
  • Include cross-platform command-line instructions for all major steps, such as deploying the ARM template, validating deployment, and deleting resources.
  • Mention and demonstrate Linux/macOS compatibility for all command-line instructions.
  • Reorder alternative deployment methods to list Azure CLI before PowerShell, or present both equally.
  • Add notes or sections highlighting how the workflow applies to Linux and macOS users, including any differences in tooling or environment setup.
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
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring IP firewall rules for Azure Event Grid topics or domains. However, the PowerShell section is given equal prominence to the CLI section, and PowerShell is a Windows-centric tool. There are no explicit Linux shell examples (e.g., Bash), nor are there references to Linux-specific tools or patterns. The CLI examples are cross-platform, but the inclusion and detailed coverage of PowerShell commands may suggest a Windows bias, especially since PowerShell is traditionally associated with Windows environments. The order of sections (CLI before PowerShell) is neutral, but the presence of PowerShell examples without any Linux shell equivalents could be seen as a subtle bias.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
  • Add explicit Bash shell examples or notes for Linux users, such as variable setting and command usage in Bash.
  • Mention that PowerShell Core is available on Linux and macOS, if PowerShell examples are retained.
  • Consider adding a note or section for Linux users, highlighting any OS-specific considerations or differences.
  • Ensure that screenshots and UI references do not assume a Windows environment (e.g., avoid showing Windows-only UI elements).
GitHub Create Pull Request
Event Grid Concepts (push delivery) in Event Grid basic ...s/azure-docs/blob/main/articles/event-grid/concepts.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by listing Azure PowerShell samples before Linux-friendly alternatives and referencing PowerShell specifically. While Azure CLI (cross-platform) is mentioned, the ordering and explicit PowerShell callout may suggest a preference for Windows tooling. No Linux-specific examples or tools are provided, and there is no mention of Linux shell scripting or native Linux event handling patterns.
Recommendations
  • List Azure CLI examples before PowerShell examples to emphasize cross-platform parity.
  • Add explicit Linux shell (bash) examples for common operations, such as creating subscriptions or querying events.
  • Include references to Linux-native tools or scripting patterns where appropriate.
  • Clarify that Azure CLI and REST API are fully supported on Linux and macOS, and provide links to relevant documentation.
  • Avoid listing Windows-specific tools (like PowerShell) before cross-platform alternatives unless contextually necessary.
GitHub Create Pull Request
Event Grid Send custom events to web endpoint .../articles/event-grid/custom-event-quickstart-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 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 PowerShell examples for sending events, but the structure and language show a subtle Windows bias. PowerShell is given a dedicated section after Azure CLI, and instructions for using Cloud Shell mention PowerShell first, with Bash as an alternative. There are no Linux-specific command-line examples outside Azure CLI, and no mention of Linux-native tools or workflows. The cleanup and navigation instructions are portal-centric, which is platform-neutral, but the command-line focus leans toward Windows users.
Recommendations
  • Add explicit Linux shell (e.g., Bash) instructions outside of Azure CLI, such as using curl directly from a local Linux terminal.
  • Include examples using native Linux tools (e.g., wget, curl from Linux, not just Cloud Shell).
  • Reorder instructions so Bash/Azure CLI is presented first, or clarify parity between Bash and PowerShell.
  • Mention that all CLI examples work equally on Linux, macOS, and Windows, and provide guidance for running them locally (not just in Cloud Shell).
  • Add troubleshooting notes for Linux users if there are any platform-specific differences.
GitHub Create Pull Request
Event Grid Custom topics in Azure Event Grid ...re-docs/blob/main/articles/event-grid/custom-topics.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents tutorials for Azure portal, CLI, PowerShell, and ARM templates. PowerShell, a Windows-centric tool, is given its own dedicated section with multiple examples, while there is no mention of Linux-specific tools (such as Bash scripts or references to Linux shell environments). The CLI section is platform-neutral, but the ordering of sections places PowerShell before ARM templates and does not clarify Linux parity. There are no explicit Linux or Bash examples, nor is there guidance for Linux users on using equivalent tools.
Recommendations
  • Add explicit Bash or shell script examples for Linux users alongside PowerShell examples.
  • Clarify that Azure CLI is cross-platform and provide sample commands in both Windows (cmd/PowerShell) and Linux (Bash) syntax where relevant.
  • Include a note or section on using these tools from Linux environments, with links to Linux-specific quickstarts if available.
  • Consider reordering sections so that platform-neutral tools (CLI, ARM templates) are presented before platform-specific ones (PowerShell).
GitHub Create Pull Request
Event Grid Azure Blob Storage as Event Grid source .../main/articles/event-grid/event-schema-blob-storage.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page provides conceptual and schema information for Azure Blob Storage as an Event Grid source. While the technical content is platform-neutral, the tutorials and quickstarts section lists Windows/PowerShell examples before Linux/Azure CLI equivalents, and includes multiple PowerShell-focused guides. There is no explicit Linux bias, but the ordering and presence of PowerShell examples may suggest a slight Windows-first approach.
Recommendations
  • Reorder the tutorials/how-tos to list Azure CLI (Linux/macOS-friendly) examples before PowerShell examples, or alternate their order.
  • Ensure parity in scripting examples by providing Bash or shell script samples alongside PowerShell where applicable.
  • Explicitly mention cross-platform compatibility in introductory sections, clarifying that all operations can be performed on Linux, macOS, and Windows.
  • Add links to Linux/macOS-specific guides or troubleshooting pages if available.
  • Review other related documentation pages to ensure Linux and open-source tooling are equally represented.
GitHub Create Pull Request
Event Grid Azure resource group as an Event Grid source ...in/articles/event-grid/event-schema-resource-groups.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents both Azure CLI and PowerShell tutorials for subscribing to events, but PowerShell examples are listed after CLI and are present in equal number. There are no explicit Windows-only tools or patterns, nor is there exclusive mention of Windows-specific technologies. However, PowerShell is a Windows-centric tool (though now cross-platform), and its inclusion may indicate some residual Windows bias. There are no Linux-specific examples, nor is Bash or Linux tooling mentioned. The page does not provide explicit Linux examples or discuss platform differences.
Recommendations
  • Add explicit Bash/Linux shell examples for subscribing to events, using Azure CLI in a Linux context.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide sample commands run in Bash.
  • Include notes or sections on platform parity, especially for scripting and automation.
  • If PowerShell is mentioned, clarify its cross-platform availability and provide equivalent Bash examples where possible.
GitHub Create Pull Request
Event Grid Get access key for an Event Grid resource ...-docs/blob/main/articles/event-grid/get-access-keys.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure portal, Azure PowerShell, and Azure CLI. PowerShell, a Windows-centric tool, is given a dedicated section before the CLI, which is more cross-platform. There are no explicit Linux-specific instructions or examples, and the CLI examples do not clarify Linux usage or shell differences. The documentation implicitly prioritizes Windows tools and patterns by listing PowerShell before CLI and omitting any mention of Linux shell environments.
Recommendations
  • Add explicit Linux shell examples (e.g., bash/zsh) for Azure CLI usage, including any OS-specific notes if applicable.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide guidance for installation on Linux.
  • Consider reordering sections to present cross-platform tools (Azure CLI) before Windows-centric tools (PowerShell).
  • Mention alternative Linux-native automation options (e.g., shell scripts) where relevant.
  • Add a note or section about using these commands in Linux environments, including screenshots or terminal output if possible.
GitHub Create Pull Request
Event Grid Configure Service Bus Queues and Topics as Event Handlers for Azure Event Grid ...s/blob/main/articles/event-grid/handler-service-bus.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring Service Bus queues and topics as event handlers for Azure Event Grid. However, PowerShell is featured as a primary automation method alongside CLI, and there are no explicit Bash, shell script, or Linux-native tool examples. PowerShell is traditionally a Windows-centric tool, and its inclusion without Linux-specific alternatives may indicate a Windows bias. Additionally, PowerShell examples are given equal prominence to CLI, which can be interpreted as 'windows_first' since CLI is cross-platform but PowerShell is more commonly used on Windows.
Recommendations
  • Add explicit Bash or shell script examples for Linux users, especially for REST API calls using curl.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • If PowerShell is included, mention that Azure PowerShell is available on Linux and macOS, or provide guidance for Linux users.
  • Consider including a section or note for Linux users highlighting best practices and common patterns for automation.
  • Ensure that any screenshots or UI references do not assume a Windows environment unless necessary.
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
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all operations, but PowerShell is a Windows-centric tool and is presented as a primary alternative throughout. There are no Linux-specific shell examples (e.g., Bash/curl) for publishing events, nor are Linux-native tools or patterns mentioned. The CLI examples are cross-platform, but the presence of PowerShell as an equal tab and the lack of explicit Linux shell examples may suggest a subtle Windows bias.
Recommendations
  • Add Bash/curl examples for publishing events to the Event Grid domain endpoint, demonstrating how to POST JSON event data from a Linux shell.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide guidance for installing and using it on Linux.
  • Consider including Linux-native scripting examples (e.g., using jq, curl, or wget) for common tasks such as retrieving keys and endpoints.
  • If PowerShell is retained, clarify that PowerShell Core is cross-platform, but also provide examples using traditional Linux tools.
  • Review and balance the order of examples, sometimes presenting CLI/Bash first to avoid the impression of Windows-first documentation.
GitHub Create Pull Request
← Previous Page 7 of 12 Next →