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 51-75 of 289 flagged pages
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/delivery-and-retry.md ...cs/blob/main/articles/event-grid/delivery-and-retry.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. PowerShell is mentioned as a primary method for configuring retry and batching policies, and references to 'sample CLI and PowerShell command' are given together, but no explicit Linux shell (bash) examples are provided. The Azure CLI example is generic and could be run on any platform, but there is no explicit mention or example of Linux-specific usage (such as bash scripting or Linux environment variables). PowerShell is referenced before Linux alternatives, and there is no mention of Linux tools or scripting patterns. No Linux-specific guidance or troubleshooting is provided.
Recommendations
  • Add explicit Linux/bash examples alongside PowerShell, especially where scripting is involved.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide platform-specific notes if needed.
  • Provide links or references to Linux troubleshooting or environment setup for Event Grid.
  • Ensure that PowerShell and CLI examples are presented in parallel, not with PowerShell as the default or first option.
  • Mention Linux tools (such as curl, jq) for interacting with Event Grid endpoints where appropriate.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/template-samples.md ...docs/blob/main/articles/event-grid/template-samples.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 an explicit link to PowerShell samples, but no mention of Bash or Linux-specific examples. The CLI link is present, but it is not clear if it covers Bash or Linux usage. No Linux tools or patterns are mentioned, and there are no examples tailored for Linux users.
Recommendations
  • Add explicit Bash/Linux shell examples alongside PowerShell samples.
  • List CLI (cross-platform) samples before or alongside PowerShell samples to avoid Windows-first ordering.
  • Clarify that CLI samples are suitable for Linux/macOS users and provide links to Bash-specific usage if available.
  • Include a note or section on using ARM templates from Linux environments, mentioning relevant tools and patterns.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/authenticate-with-microsoft-entra-id.md ...les/event-grid/authenticate-with-microsoft-entra-id.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 (PowerShell) are featured with example commands, while equivalent Linux shell commands are missing; references to configuring managed identities on Windows VMs are given before Linux VM equivalents; and Azure CLI and PowerShell are both shown, but no Bash or Linux shell scripting examples are included. Portal screenshots and instructions are platform-neutral, but the command-line guidance and code samples lean toward Windows environments.
Recommendations
  • Add explicit examples for configuring managed identities on Linux VMs, with links to relevant documentation.
  • Provide Bash or Linux shell scripting equivalents for PowerShell commands, especially for resource creation and configuration.
  • Include Linux-focused CLI usage patterns, such as environment variable export via 'export' rather than 'Set-EnvironmentVariable'.
  • Ensure that SDK usage examples (e.g., authentication with environment variables) show both Windows and Linux methods.
  • Where PowerShell is used, add a corresponding Bash/CLI example and clarify platform applicability.
  • Review the order of presenting platform-specific instructions to avoid Windows-first bias; present cross-platform or Linux instructions first or side-by-side.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/cloud-event-schema.md ...cs/blob/main/articles/event-grid/cloud-event-schema.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing both Azure CLI and PowerShell examples for schema configuration, but omits Linux-specific shell examples (e.g., Bash scripting, environment variable usage). The PowerShell examples are given equal prominence to CLI, and Visual Studio tooling (Windows-centric) is described in detail before VS Code. There is no mention of Linux-native tools, nor are there instructions for Linux users (e.g., package installation, shell differences).
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI commands, including environment variable usage and command syntax differences.
  • Include instructions for installing and using Azure CLI and related tools on Linux systems.
  • Provide parity for development tooling by mentioning Linux-compatible editors (e.g., JetBrains Rider, Vim) and their workflows.
  • Clarify that PowerShell examples are for Windows, and suggest alternatives for Linux users (e.g., Bash, zsh).
  • Add notes or sections for Linux users regarding package management (e.g., NuGet via dotnet CLI on Linux), file system paths, and editor usage.
  • Ensure that examples and instructions do not assume Visual Studio or PowerShell availability, and offer cross-platform alternatives.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/custom-azure-policies-for-security-control.md ...ent-grid/custom-azure-policies-for-security-control.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation refers to running CLI or PowerShell commands to find property aliases, but does not provide explicit Linux shell (bash) examples or clarify parity between PowerShell and Azure CLI usage on Linux. The mention of PowerShell is prominent and appears before CLI, suggesting a Windows-first orientation. There are no concrete Linux-specific examples or instructions, and no mention of platform differences or considerations.
Recommendations
  • Provide explicit bash/Azure CLI examples for Linux users alongside PowerShell examples.
  • Clarify that Azure CLI is cross-platform and available on Linux, macOS, and Windows.
  • Avoid listing PowerShell before CLI unless there is a technical reason; consider listing CLI first or presenting both together.
  • Add notes or sections highlighting any platform-specific considerations or differences.
  • Ensure that all command-line instructions are tested and documented for both Windows (PowerShell) and Linux (bash/CLI).
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/ensure-tags-exists-on-new-virtual-machines.md ...ent-grid/ensure-tags-exists-on-new-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 associated with Windows environments. There are no examples or instructions for performing equivalent steps using Linux tools, Azure CLI, or Bash scripts. The VM creation and tagging workflow is shown only with PowerShell, and there is no mention of Linux-specific considerations or cross-platform alternatives.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for Linux users.
  • Include instructions for importing and using modules in environments other than PowerShell (e.g., Python runbooks, Bash).
  • Add notes or sections highlighting any differences or additional steps required for Linux VMs or non-Windows automation environments.
  • Ensure that code snippets and automation workflows are presented in a cross-platform manner, or at least offer parallel examples for both Windows and Linux users.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/event-grid-dotnet-get-started-pull-delivery.md ...nt-grid/event-grid-dotnet-get-started-pull-delivery.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. It exclusively references Visual Studio (a Windows-centric IDE), provides instructions and screenshots for Visual Studio dialogs, and uses PowerShell commands for package installation. There are no instructions or examples for Linux or cross-platform development environments such as VS Code, JetBrains Rider, or CLI-based workflows. No mention is made of Linux-compatible package managers (e.g., dotnet CLI), and all tooling assumes a Windows environment.
Recommendations
  • Add instructions for using .NET CLI (e.g., 'dotnet new console', 'dotnet add package Azure.Messaging.EventGrid.Namespaces') to create and manage projects/packages on Linux and macOS.
  • Include examples and screenshots for cross-platform editors like Visual Studio Code.
  • Provide guidance for installing .NET SDK on Linux and macOS, not just Windows.
  • Replace or supplement PowerShell commands with Bash equivalents.
  • Clarify that the .NET code samples work on Linux, macOS, and Windows, and provide troubleshooting tips for non-Windows environments.
  • Mention alternative IDEs (e.g., Rider, VS Code) and how to perform the same steps in those environments.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/manage-event-delivery.md ...blob/main/articles/event-grid/manage-event-delivery.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring dead-letter and retry policies in Azure Event Grid. However, PowerShell is a Windows-centric tool and its inclusion alongside Azure CLI (which is cross-platform) can signal a Windows bias, especially since PowerShell examples are given equal prominence. There are no explicit Linux shell (bash) or scripting examples, nor is there mention of Linux-specific patterns or tools. The related sample application is for .NET, another technology often associated with Windows environments. There is no guidance for Linux users beyond Azure CLI, and no mention of Linux-first workflows or troubleshooting.
Recommendations
  • Add explicit bash/sh examples for common operations, demonstrating usage in native Linux environments.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Consider including sample scripts or automation patterns for Linux users, such as bash scripts or references to tools like curl or jq.
  • Balance the prominence of PowerShell by either moving it after CLI examples or making it clear that PowerShell Core is available cross-platform.
  • Provide links or references to Linux-focused sample applications or tutorials, not just .NET/Windows-centric ones.
  • Add troubleshooting notes or tips for Linux users, such as common permission or environment issues.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/event-hubs-integration.md ...lob/main/articles/event-grid/event-hubs-integration.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 referencing Visual Studio for publishing Azure Functions, omitting any instructions for Linux or cross-platform tools (such as VS Code, Azure CLI, or GitHub Actions). The workflow assumes the use of Windows-based development environments and does not provide alternative steps for Linux or macOS users. While the Azure Cloud Shell instructions use Bash, the development and deployment steps are tightly coupled to Visual Studio, which is primarily a Windows tool.
Recommendations
  • Add instructions for publishing the Azure Functions app using cross-platform tools such as Visual Studio Code, Azure CLI, or Azure Functions Core Tools.
  • Include Linux/macOS-specific guidance for running and building the sample projects, such as using dotnet CLI commands.
  • Provide alternative deployment workflows (e.g., GitHub Actions, Azure DevOps pipelines) that do not require Visual Studio.
  • Clarify that Visual Studio is not required and offer parity for Linux and macOS users throughout the tutorial.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/handler-functions.md ...ocs/blob/main/articles/event-grid/handler-functions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. In the 'Enable batching' section, PowerShell is mentioned as a primary tool for configuring batch settings, with explicit cmdlet examples and links. Although Azure CLI and Resource Manager templates are also referenced, PowerShell is listed after the portal and before CLI, and receives more detailed coverage. There are no Linux-specific examples, nor is there mention of Linux-native tools or shell scripting. The page assumes familiarity with PowerShell and Windows-centric workflows.
Recommendations
  • Add explicit Linux shell (bash) examples for configuring batch settings, such as using Azure CLI from bash.
  • Clarify that Azure CLI is cross-platform and provide sample commands for Linux/macOS environments.
  • Reorder tooling sections to present Azure CLI before PowerShell, emphasizing cross-platform parity.
  • Include notes or links for Linux users on installing and using Azure CLI and Resource Manager templates.
  • Avoid assuming PowerShell as the default scripting environment; mention alternatives for Linux users.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/input-mappings.md ...e-docs/blob/main/articles/event-grid/input-mappings.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 (topic creation, subscription, publishing events). However, PowerShell examples are given equal prominence to Azure CLI, and there are no explicit Linux/bash examples for scripting outside of Azure CLI. The CLI examples use bash-style syntax, but there is no mention of Linux-specific tools or patterns (e.g., curl usage is shown, but only in the context of Azure CLI variable assignment). PowerShell examples may be less relevant for Linux users, and the documentation does not clarify platform applicability or provide Linux-first guidance.
Recommendations
  • Explicitly state which examples are cross-platform and which are Windows-specific.
  • Provide bash-only examples for publishing events (e.g., using curl with hardcoded values, not relying on Azure CLI variable assignment).
  • Add notes clarifying that PowerShell examples are intended for Windows users, and suggest bash equivalents for Linux/Mac users.
  • Consider listing Azure CLI (bash) examples before PowerShell to prioritize Linux parity.
  • Include troubleshooting or usage notes for Linux users, such as curl installation or shell compatibility.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/mqtt-publish-and-subscribe-cli.md .../articles/event-grid/mqtt-publish-and-subscribe-cli.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the certificate generation section, where only Windows-specific instructions and Powershell commands are provided. The guidance explicitly mentions opening a Command Prompt and using Windows environment variables, with no equivalent Linux or macOS instructions or shell commands. The sample code section references Visual Studio and NuGet package management, which are Windows-centric development tools, without mentioning cross-platform alternatives or instructions for Linux/macOS users.
Recommendations
  • Add explicit instructions and shell commands for generating certificates using step CLI on Linux and macOS, including example bash commands and file paths.
  • Include guidance for running the sample .NET code on Linux/macOS, such as using VS Code, JetBrains Rider, or the dotnet CLI.
  • Mention package installation via dotnet CLI (e.g., 'dotnet add package MQTTnet') as an alternative to Visual Studio/NuGet GUI.
  • Ensure all CLI and code examples use cross-platform file paths and avoid Windows-specific environment variables or folder structures.
  • Where Windows-specific steps are mentioned, provide equivalent steps for Linux/macOS users in parallel.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/mqtt-certificate-chain-client-authentication.md ...t-grid/mqtt-certificate-chain-client-authentication.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 explicit mention of Windows installation and no equivalent Linux or cross-platform shell examples. This prioritizes Windows tooling and omits guidance for Linux or macOS users, despite using the cross-platform 'step CLI'.
Recommendations
  • Add Linux and macOS shell examples for certificate generation using 'step CLI', e.g., bash/zsh commands.
  • Clarify that 'step CLI' is cross-platform and provide installation instructions for multiple OSes.
  • Avoid language that assumes Windows as the default environment (e.g., 'in Windows PowerShell').
  • Present examples for all major platforms side-by-side or in tabs to ensure parity.
  • Include troubleshooting or file path notes relevant to Linux/macOS (e.g., use of forward slashes, home directory).
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/mqtt-publish-and-subscribe-portal.md ...ticles/event-grid/mqtt-publish-and-subscribe-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 paths). There are no explicit Linux or macOS instructions or examples for certificate generation, shell usage, or file paths, despite the cross-platform nature of the tools involved.
Recommendations
  • Provide parallel instructions and examples for Linux/macOS users, including shell commands (bash/zsh) and typical file paths (e.g., ~/).
  • Replace or supplement Powershell examples with generic shell commands where possible, or clearly label platform-specific instructions.
  • Clarify that the step CLI works cross-platform and link to installation guides for Linux/macOS.
  • Include screenshots or notes for Linux/macOS environments where relevant, especially for file navigation and tool usage.
  • Avoid referencing Windows-specific environment variables (e.g., %USERPROFILE%) without Linux/macOS equivalents (e.g., $HOME).
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/scripts/powershell-webhook-secure-delivery-microsoft-entra-app.md ...powershell-webhook-secure-delivery-microsoft-entra-app.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 and PowerShell usage. All examples and instructions are provided in PowerShell, with no mention of Linux shell equivalents (e.g., Bash, CLI). The script uses PowerShell-specific constructs and modules, and the prerequisites and workflow assume a Windows environment. There is no guidance for users on Linux or macOS platforms, nor are cross-platform Azure CLI or REST API alternatives presented.
Recommendations
  • Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and work on Linux, macOS, and Windows.
  • Include Bash script samples for Linux users, especially for authentication, service principal creation, and role assignment.
  • Clarify which steps are platform-independent and which require platform-specific tools, and offer alternatives where possible.
  • Mention prerequisites for Linux/macOS users, such as installing Azure CLI and Microsoft Graph CLI.
  • Add a section comparing PowerShell and CLI approaches, helping users choose the best fit for their environment.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/scripts/powershell-webhook-secure-delivery-microsoft-entra-user.md ...owershell-webhook-secure-delivery-microsoft-entra-user.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively provides a PowerShell script for configuring secure webhook delivery with Microsoft Entra user in Azure Event Grid. There are no examples or instructions for using Bash, Azure CLI, or other Linux-native tools. The script and workflow assume familiarity with PowerShell and Windows-centric patterns, and the only login command mentioned is 'az login', which is cross-platform, but the rest of the automation is strictly PowerShell-based.
Recommendations
  • Provide equivalent instructions and sample scripts using Azure CLI and Bash to support Linux and macOS users.
  • Include notes or links to cross-platform alternatives for each PowerShell command, especially for Microsoft Graph and Azure AD operations.
  • Reorganize the documentation to present both Windows/PowerShell and Linux/Azure CLI approaches side-by-side or in parallel sections.
  • Explicitly state platform requirements and offer guidance for users who may not have access to PowerShell (e.g., on Linux).
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/mqtt-topic-spaces.md ...ocs/blob/main/articles/event-grid/mqtt-topic-spaces.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates Windows bias primarily in its treatment of shell-specific escaping for topic templates. It provides examples and guidance for PowerShell users, including how to escape special characters, but does not offer equivalent examples or instructions for Linux shells (e.g., Bash). The mention of PowerShell comes before any reference to other shells, and no Linux-specific tools or patterns are discussed.
Recommendations
  • Add explicit examples for escaping special characters in Bash and other common Linux shells alongside the PowerShell examples.
  • Include notes or tables comparing escaping requirements across PowerShell, Bash, and other shells.
  • Ensure that CLI examples are tested and presented for both Windows (PowerShell) and Linux (Bash) environments.
  • Avoid presenting Windows-specific instructions before Linux equivalents; instead, group them together or alternate their order.
  • Reference Linux tools or patterns where appropriate, such as using Bash variables or quoting conventions.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/post-to-custom-topic.md .../blob/main/articles/event-grid/post-to-custom-topic.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 or before Linux-friendly alternatives, such as Azure CLI. PowerShell is a Windows-centric tool, and its usage is highlighted in Cloud Shell and example sections. The documentation also references Windows tools and patterns (PowerShell, Azure portal screenshots) without providing equivalent Linux shell or scripting examples beyond Azure CLI. There is no explicit mention of Linux-specific tools or workflows, and PowerShell examples are given equal prominence to CLI, which may disadvantage Linux users.
Recommendations
  • Add explicit Bash-only examples for sending events, using curl and jq, outside of Azure CLI context.
  • Clarify that Azure CLI commands work natively on Linux, macOS, and Windows, and provide guidance for installing CLI on Linux.
  • Reduce reliance on PowerShell examples or move them after CLI/Bash examples to avoid Windows-first impression.
  • Include screenshots or instructions for Linux terminal environments, not just Azure portal and PowerShell.
  • Mention that Cloud Shell supports Bash and show Bash usage as the primary example for cross-platform parity.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/secure-webhook-delivery.md ...ob/main/articles/event-grid/secure-webhook-delivery.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. All step-by-step instructions and scripts use PowerShell, and the Azure Cloud Shell is always shown in PowerShell mode. There are no Bash or Linux shell equivalents for any of the scripting steps, nor are Linux-specific tools or patterns mentioned. The use of PowerShell and Windows-centric terminology is consistent throughout, and Linux alternatives are not referenced or linked.
Recommendations
  • Provide equivalent Bash/Azure CLI scripts for all PowerShell examples, especially for steps involving Connect-MgGraph and role assignments.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
  • Include Linux/Bash command-line examples alongside PowerShell, ideally in parallel tabs or sections.
  • Reference cross-platform tools and patterns, such as using az CLI commands for authentication and resource management.
  • Add troubleshooting notes relevant to Linux environments, such as handling environment variables and authentication.
  • Review all linked scripts and ensure Linux/Bash versions are available and referenced.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/send-events-webhooks-private-destinations.md ...vent-grid/send-events-webhooks-private-destinations.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Azure Relay Bridge example uses a Windows-style executable invocation ('.\azbridge.exe'), with no mention of Linux/Mac equivalents. There are no explicit Linux or cross-platform code samples, and the documentation does not provide parity for Linux users in terms of setup or usage instructions.
Recommendations
  • Provide equivalent code samples in cross-platform languages (e.g., Python, Node.js) and/or explicitly mention Linux/Mac compatibility.
  • Show how to run Azure Relay Bridge on Linux/Mac (e.g., 'dotnet azbridge.dll' or Docker usage) alongside the Windows executable example.
  • Include Linux/Mac shell commands for relevant steps, not just Azure CLI (which is cross-platform but often shown with Windows-centric context).
  • Clarify that the Azure Relay SDK is available for multiple languages and platforms, and link to non-.NET guides.
  • Add explicit instructions or examples for setting up and validating webhooks on Linux servers, including firewall and networking considerations.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/subscribe-to-graph-api-events.md ...n/articles/event-grid/subscribe-to-graph-api-events.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
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 code sample. The instructions for obtaining Azure region names use the Azure CLI, which is available cross-platform but is most commonly associated with Windows environments. There is no explicit mention of Linux-specific patterns, nor are Linux terminal commands or environment setup instructions provided. Windows tools and patterns are referenced before any Linux equivalents, and PowerShell is included as a sample language, reinforcing Windows-centric usage.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and provide installation/setup instructions for Linux and macOS.
  • Include Linux-specific examples for environment setup, such as using bash or zsh for scripting, and reference package managers like apt, yum, or Homebrew for installing prerequisites.
  • Add notes or examples for obtaining Azure region names using Linux shell commands (e.g., curl, jq) in addition to Azure CLI.
  • Ensure parity in code samples by including bash shell scripts and instructions for Linux users alongside PowerShell.
  • Clarify that all SDKs and tools are supported on Linux and macOS, and provide links to relevant documentation for those platforms.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/troubleshoot-network-connectivity.md ...ticles/event-grid/troubleshoot-network-connectivity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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) before Linux equivalents. The primary troubleshooting commands use Windows-specific tools and syntax, with Linux alternatives mentioned only briefly or not at all. There is a lack of parity in tool recommendations and command examples for Linux users.
Recommendations
  • Provide Linux-first or side-by-side examples for all troubleshooting commands, using native Linux tools (e.g., nc, curl, nmap) instead of or alongside Windows tools.
  • Explicitly mention and document Linux equivalents for tools like psping and tcpping, such as 'nc', 'nmap', or 'hping3'.
  • Avoid using Windows path and executable syntax (e.g., '.\psping.exe') as the primary example; use platform-neutral or both Windows and Linux syntax.
  • Include download and installation instructions for Linux tools where Windows tools are referenced.
  • Ensure troubleshooting steps and recommendations are equally detailed for both Windows and Linux environments.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/custom-azure-policies-for-security-control.md ...ent-grid/custom-azure-policies-for-security-control.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references both CLI and PowerShell for finding property aliases, but mentions PowerShell explicitly and links to a section that typically prioritizes PowerShell/Windows tools. There are no explicit Linux shell (bash) examples or instructions, and no mention of Linux-specific tools or patterns. The documentation does not provide parity in examples or guidance for Linux users.
Recommendations
  • Explicitly include Azure CLI (bash) examples alongside PowerShell commands when referencing command-line operations.
  • When linking to external sections, clarify which instructions are for PowerShell and which are for CLI/bash, and ensure both are present.
  • Add a note or section for Linux/macOS users explaining how to perform equivalent tasks using Azure CLI.
  • Avoid mentioning PowerShell first or exclusively; use neutral phrasing such as 'using Azure CLI or PowerShell' and provide both examples.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/send-events-webhooks-private-destinations.md ...vent-grid/send-events-webhooks-private-destinations.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 command-line example for Azure Relay Bridge uses Windows path notation ('.\azbridge.exe'), and the only code sample is in C#. There are no explicit Linux or cross-platform shell examples, nor is there mention of Linux-specific patterns or tools. The documentation references Azure CLI, which is cross-platform, but the usage examples and tooling (azbridge.exe) are presented in a Windows-first manner.
Recommendations
  • Provide equivalent Linux/macOS command-line examples, using './azbridge' or 'docker run' for Azure Relay Bridge.
  • Include code samples in additional languages, such as Python or Node.js, to demonstrate cross-platform parity.
  • Explicitly mention that Azure Relay Bridge can be run on Linux/macOS and provide instructions for those platforms.
  • When showing file paths or executables, use platform-neutral notation or show both Windows and Linux/macOS variants.
  • Add references to Linux-specific tools or patterns where relevant, such as systemd for service management.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/cloud-event-schema.md ...cs/blob/main/articles/event-grid/cloud-event-schema.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by providing PowerShell examples alongside Azure CLI, referencing Visual Studio and NuGet Package Manager (Windows-centric tools) before mentioning VS Code, and omitting Linux-specific guidance or examples. There are no bash or Linux shell examples, and the developer workflow is described primarily in terms of Windows tools and patterns.
Recommendations
  • Add explicit bash/Linux shell examples for all CLI commands, including environment variable usage and command syntax.
  • Include instructions for installing and using the Azure CLI and relevant SDKs on Linux/macOS platforms.
  • Provide parity for developer tooling by referencing cross-platform editors (e.g., VS Code) before or alongside Visual Studio, and include .NET CLI commands for package management (e.g., 'dotnet add package') as alternatives to NuGet Package Manager.
  • Clarify that all examples are cross-platform where applicable, and highlight any platform-specific differences.
  • Add notes or sections for Linux/macOS users, including troubleshooting tips and environment setup guidance.
GitHub Create Pull Request
← Previous Page 3 of 12 Next →