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 126-150 of 289 flagged pages
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-27 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 moderate Windows bias. Windows/PowerShell examples (using psping.exe) are shown first and in more detail, with Linux equivalents (telnet) mentioned briefly and only for port checking, not for packet drops or latency. The recommended troubleshooting tools (psping.exe, tcpping.exe) are Windows-only, and there is no guidance or example for Linux/macOS users to perform equivalent packet drop or latency tests. This creates friction for non-Windows users attempting network troubleshooting.
Recommendations
  • Provide Linux/macOS equivalents for all troubleshooting commands, such as using 'nc', 'nmap', or 'hping3' for port and packet tests.
  • Show Linux/macOS examples alongside Windows/PowerShell examples, not after or as an afterthought.
  • Mention cross-platform tools (e.g., Wireshark, curl) where possible.
  • Clarify which steps/tools are Windows-only and offer alternatives for other platforms.
  • Consider reordering examples so that Windows and Linux/macOS are presented equally.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in its troubleshooting examples: Windows/PowerShell tools (psping.exe) are presented first and in more detail, with Linux alternatives (telnet) mentioned briefly and without equivalent depth. The recommended tools and commands are predominantly Windows-centric, and some troubleshooting steps lack Linux/macOS parity or omit cross-platform alternatives.
Recommendations
  • Present Linux/macOS examples alongside Windows examples, giving equal detail and prominence.
  • List Linux/macOS commands (e.g., nc, curl, tcpping for Linux) before or alongside Windows/PowerShell commands.
  • Include download or installation instructions for Linux/macOS tools (e.g., how to install telnet, netcat, or tcpping on Ubuntu).
  • Reference cross-platform tools (e.g., Wireshark, curl) where possible, and clarify platform-specific differences.
  • Avoid assuming the use of Windows-only tools (like psping.exe) and provide alternatives for non-Windows users.
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: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias by presenting Windows/PowerShell examples and tools (psping.exe) before Linux equivalents. The primary troubleshooting commands use Windows-specific tools and syntax, with Linux alternatives mentioned only briefly and without equivalent detail. The use of Windows tools like psping.exe and references to tcpping.exe further reinforce the Windows-centric approach.
Recommendations
  • Provide Linux/macOS examples alongside Windows examples, ensuring parity in detail and explanation.
  • List Linux/macOS commands (e.g., 'telnet', 'nc', 'curl', or 'openssl') before or alongside Windows commands, not after.
  • Include download or installation instructions for Linux troubleshooting tools (e.g., how to install 'telnet', 'nc', or 'tcping' on Linux).
  • Offer troubleshooting steps using cross-platform tools (e.g., Wireshark, curl) with example commands for both Windows and Linux/macOS.
  • Avoid using Windows-only tools (like psping.exe) as the primary example; instead, use platform-neutral or widely available tools.
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 consistently presents Windows/PowerShell examples and tools (psping.exe, tcpping.exe) first and in more detail, with Linux alternatives (telnet) mentioned only briefly and lacking parity in explanation. The troubleshooting steps and sample commands are Windows-centric, which may create friction for Linux/macOS users seeking equivalent workflows.
Recommendations
  • Provide Linux/macOS equivalents for all troubleshooting commands (e.g., use 'nc' or 'nmap' for port checks, 'hping3' or 'tcping' for TCP pinging).
  • Present Linux/macOS examples alongside Windows/PowerShell examples, not only as a brief mention.
  • Include installation instructions or links for Linux/macOS tools where Windows tools are referenced.
  • Ensure tool recommendations are cross-platform (e.g., Wireshark is good, but also mention tcpdump for Linux).
  • Reorder examples so that Windows and Linux/macOS commands are presented with equal prominence.
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 01:38
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides certificate generation instructions exclusively using PowerShell commands and Windows-centric guidance (e.g., opening Command Prompt via Win+R), without offering equivalent Linux/macOS shell commands or workflows. The .NET sample code is cross-platform, but the certificate generation steps are Windows-focused, which may hinder Linux/macOS users.
Recommendations
  • Provide Linux/macOS shell (bash) equivalents for certificate generation using the step CLI, including commands for common Linux/macOS environments.
  • Avoid referencing Windows-specific UI actions (such as 'Win+R') without offering alternatives for other platforms.
  • Clarify that the step CLI is cross-platform and provide installation and usage notes for Linux/macOS.
  • If possible, include a table or section showing certificate generation commands for Windows (PowerShell), Linux (bash), and macOS (zsh/bash).
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Visual Studio Heavy Missing Linux Example
Summary
The tutorial demonstrates a notable Windows bias by exclusively referencing Visual Studio for publishing the Azure Functions app and running the sample projects. There are no instructions or examples for Linux/macOS users, such as using VS Code, Azure Functions Core Tools, or .NET CLI. The prerequisites and workflow assume a Windows development environment, which may hinder Linux/macOS users from following the tutorial without significant adaptation.
Recommendations
  • Add instructions for publishing the Azure Functions app using VS Code, Azure Functions Core Tools, or .NET CLI, which are cross-platform.
  • Include steps for running the sample projects on Linux/macOS, such as using 'dotnet run' or Python/Node.js equivalents if available.
  • Mention alternative editors (VS Code, JetBrains Rider) in the prerequisites.
  • Clarify that the Azure CLI commands work on Linux/macOS and provide screenshots or terminal examples from those platforms.
  • Provide troubleshooting tips for non-Windows environments.
GitHub Create Pull Request
Event Grid Map custom field to Azure Event Grid schema ...e-docs/blob/main/articles/event-grid/input-mappings.md
Medium Priority View Details →
Scanned: 2026-01-14 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 PowerShell examples for all major steps, but PowerShell (a Windows-centric tool) is always shown immediately after Azure CLI and receives equal prominence. There are no Linux/macOS-specific shell examples (e.g., Bash), and PowerShell is presented as the only alternative to Azure CLI, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Add explicit Bash examples for Linux/macOS users, especially for scripting tasks.
  • Clarify that Azure CLI commands work cross-platform and highlight this fact.
  • Consider moving PowerShell examples to a separate section or appendix, or clearly label them as Windows-specific.
  • If PowerShell is not required for any unique functionality, reduce its prominence and focus on CLI/Bash workflows.
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-14 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 exhibits moderate Windows bias. While the core authentication concepts are platform-agnostic, operational examples and tooling references favor Windows environments. The Azure portal instructions and screenshots are inherently Windows-centric, and PowerShell is given a dedicated section for disabling local authentication, whereas Linux/macOS equivalents (such as Bash or CLI scripting) are not shown. The Azure CLI example is present, but PowerShell is highlighted separately and with more detail. There are no explicit Linux/macOS shell examples for environment variable setup or SDK usage, and no mention of platform-specific considerations for those users.
Recommendations
  • Add explicit Linux/macOS shell examples for environment variable setup (e.g., export AZURE_CLIENT_ID=...) alongside the Windows/PowerShell examples.
  • Provide screenshots or instructions for Azure portal usage on non-Windows platforms, or clarify that the portal is web-based and platform-neutral.
  • Balance PowerShell and CLI coverage by including Bash or zsh script examples for common tasks (e.g., resource creation, authentication setup).
  • Where SDK usage is shown (e.g., C#), add code snippets or links for other languages/platforms, and clarify any OS-specific prerequisites.
  • Note any platform-specific caveats or requirements for Linux/macOS users (e.g., installation steps, authentication flows).
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-14 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 with CloudEvents, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is shown immediately after CLI examples. In the Azure Functions section, instructions for Visual Studio and Visual Studio Code are provided, with Visual Studio (Windows-only) steps listed first and in more detail, including use of NuGet Package Manager Console (Windows tool). There are no explicit Linux/macOS instructions for package installation or development environments, and no mention of Linux-specific patterns or alternatives.
Recommendations
  • Prioritize Azure CLI examples, as it is cross-platform, and list PowerShell examples after CLI examples.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide any OS-specific notes if needed.
  • For Azure Functions, include instructions for installing NuGet packages using dotnet CLI (cross-platform) and highlight VS Code workflows on Linux/macOS.
  • Add notes or links for Linux/macOS users regarding development environment setup and package management.
  • Avoid assuming Visual Studio as the default IDE; provide parity for VS Code and command-line workflows.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation primarily describes deployment and validation steps using the Azure Portal, with only a brief mention of alternative methods (Azure PowerShell, Azure CLI, REST API) in a single sentence. The main deployment instructions and links are portal-centric, which is most familiar to Windows users. There are no explicit Linux/macOS CLI examples, nor are cross-platform command-line instructions provided for key steps such as deploying the template or uploading a file to Blob storage.
Recommendations
  • Add explicit Azure CLI examples for deploying the ARM template and uploading files to Blob storage, with step-by-step instructions.
  • Include PowerShell and Bash/Linux shell commands side-by-side where relevant.
  • Clarify that Azure CLI and REST API methods work on all platforms and provide direct links to those sections.
  • Reorder the deployment instructions to present CLI and portal methods equally, or offer a platform-neutral summary before diving into specifics.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation relies exclusively on PowerShell cmdlets (e.g., Update-AzureRmVM) and does not provide equivalent examples for Linux/macOS users (such as Azure CLI or REST API usage). The instructions and code samples are tailored to Windows environments, with no mention of Linux shell commands or cross-platform alternatives. This creates friction for users who do not use Windows or PowerShell.
Recommendations
  • Include Azure CLI examples alongside PowerShell for all automation steps, especially for VM tagging.
  • Add notes or sections clarifying how Linux/macOS users can perform equivalent actions using Bash, Azure CLI, or REST APIs.
  • Explicitly state platform requirements for the runbook code and provide guidance for adapting scripts to non-Windows environments.
  • Where possible, use cross-platform tools and commands in examples, or provide both PowerShell and Bash/CLI versions.
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-14 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 towards Windows users, specifically those using Visual Studio and PowerShell. All instructions for creating and managing projects use Visual Studio GUI steps, and NuGet package installation is shown only via PowerShell in the Package Manager Console. There are no instructions or examples for Linux/macOS users (e.g., using VS Code, CLI tools, or dotnet CLI for project/package management). This creates friction for non-Windows users attempting to follow the quickstart.
Recommendations
  • Add instructions for creating .NET projects and managing NuGet packages using the dotnet CLI, which works cross-platform.
  • Include alternative steps for Linux/macOS users, such as using VS Code or JetBrains Rider instead of Visual Studio.
  • Show package installation commands using 'dotnet add package' in addition to PowerShell.
  • Clarify that the .NET SDK and Azure Event Grid libraries are cross-platform, and provide explicit guidance for non-Windows environments.
  • Add screenshots or terminal examples relevant to Linux/macOS where appropriate.
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-14 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 dead letter and retry policies. However, PowerShell is a Windows-centric tool and is featured equally alongside Azure CLI, which is cross-platform. There are explicit installation notes for Azure PowerShell, but no mention of Bash, shell scripting, or Linux/macOS-specific workflows. The related sample application is .NET-based, which is more common on Windows. While Linux/macOS users can use Azure CLI, the prominence of PowerShell and .NET may create a perception of Windows bias.
Recommendations
  • Add explicit Bash or shell scripting examples for Linux/macOS users, especially for tasks involving environment variables and command chaining.
  • Clarify that Azure CLI works on all platforms and provide links or notes for Linux/macOS installation and usage.
  • Include sample applications or code snippets in languages popular on Linux/macOS (e.g., Python, Node.js) in the 'Related content' section.
  • Consider mentioning cross-platform alternatives to PowerShell, such as using Azure CLI in shell scripts.
  • Where PowerShell is shown, note its availability on Linux/macOS and provide installation guidance if relevant.
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-14 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 Linux/macOS shell examples. The guidance assumes a Windows environment, mentioning manual installation for Windows and omitting equivalent Linux/macOS commands or workflows. This creates friction for non-Windows users attempting to follow the guide.
Recommendations
  • Add equivalent certificate generation commands for Linux/macOS (e.g., bash shell examples).
  • Explicitly mention cross-platform support for the step CLI and provide installation instructions for Linux/macOS.
  • Present examples for both Windows and Linux/macOS, or use platform-agnostic commands where possible.
  • Clarify that the steps are not Windows-specific and provide guidance for users on other operating systems.
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-14 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 PowerShell examples for all major operations, but consistently lists PowerShell examples immediately after CLI, giving them equal prominence. There are no Linux-specific tools or shell examples (e.g., Bash, curl) for publishing events, and no explicit mention of Linux/macOS environments. The use of PowerShell throughout may signal a Windows-centric approach, although Azure CLI is cross-platform.
Recommendations
  • Add explicit Bash/curl examples for publishing events to the Event Grid domain endpoint, demonstrating how to POST event data from Linux/macOS.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and provide guidance for installing and using it on non-Windows platforms.
  • Consider including a section or tab for Bash or generic shell commands where appropriate, especially for HTTP operations.
  • Ensure that any references to 'your favorite method of making an HTTP POST' include at least one Linux-friendly example (e.g., curl).
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-14 00:00
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 in the certificate generation section, where only Windows/PowerShell instructions are provided, and the workflow is described from a Windows perspective (e.g., opening Command Prompt, using Win+R, referencing %USERPROFILE%). There are no Linux or macOS-specific instructions or examples for certificate creation, and the .NET sample code references Visual Studio and NuGet, which are Windows-centric tools, without mentioning cross-platform alternatives.
Recommendations
  • Add Linux/macOS instructions for certificate generation, including example commands for Bash/zsh and typical file paths.
  • Provide cross-platform guidance for running the step CLI, including installation and usage on Linux/macOS.
  • Mention and provide examples for using .NET CLI and VS Code for the sample code, highlighting cross-platform development options.
  • Avoid Windows-specific shortcuts and environment variables (e.g., Win+R, %USERPROFILE%) or provide their Linux/macOS equivalents.
  • Order examples so that cross-platform or Linux instructions are presented first or alongside Windows instructions.
GitHub Create Pull Request
Event Grid Publish and subscribe on an MQTT topic using portal ...ticles/event-grid/mqtt-publish-and-subscribe-portal.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias in the certificate generation section, where instructions and examples are tailored for Windows users (mentioning command prompt, Win+R, %USERPROFILE%, and using PowerShell syntax), with no explicit Linux/macOS equivalents or terminal instructions. The rest of the guide uses cross-platform tools (MQTTX app) and is portal-centric, but the initial setup may create friction for non-Windows users.
Recommendations
  • Add explicit Linux/macOS instructions for running step CLI commands, including terminal usage and file path conventions.
  • Provide shell (bash/zsh) command examples alongside PowerShell, and clarify that the step CLI works cross-platform.
  • Avoid Windows-specific environment variable references (like %USERPROFILE%) or provide Unix equivalents (e.g., $HOME).
  • Mention that the step CLI can be installed and used on Linux/macOS, and link to installation guides for those platforms.
GitHub Create Pull Request
Event Grid Topic Spaces ...ocs/blob/main/articles/event-grid/mqtt-topic-spaces.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias primarily in its handling of shell-specific escaping for topic templates. PowerShell is mentioned explicitly, with examples and guidance for escaping special characters, while Linux/macOS shells (e.g., Bash, zsh) are not referenced. This may cause confusion or friction for users on non-Windows platforms. Additionally, the ordering and examples implicitly prioritize Windows tooling and patterns.
Recommendations
  • Add explicit instructions and examples for escaping special characters in common Linux/macOS shells (e.g., Bash, zsh).
  • Include notes or tables comparing escaping requirements across PowerShell, Bash, and other shells.
  • Ensure that CLI examples are shell-agnostic or provide variants for both Windows and Linux/macOS environments.
  • Review and balance the ordering of examples so that Windows and Linux/macOS users are equally supported.
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-14 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 biased towards Windows by exclusively providing a PowerShell script and referencing PowerShell modules (e.g., Microsoft.Graph.PowerShell). There are no CLI, Bash, or cross-platform examples, and no mention of how to perform these tasks on Linux or macOS. The only prerequisite mentioned is 'az login', which is cross-platform, but the main workflow is Windows-centric.
Recommendations
  • Provide equivalent Azure CLI and/or Microsoft Graph CLI examples for each step.
  • Include Bash or shell script alternatives where possible.
  • Explicitly state whether the PowerShell script can be run on PowerShell Core (pwsh) on Linux/macOS, and provide installation instructions if so.
  • Add notes or links for Linux/macOS users on how to install and use PowerShell modules cross-platform.
  • Consider reordering or parallelizing examples so Linux/macOS users are not left out.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias: all scripting examples use PowerShell, and users are instructed to use the Azure Portal's Cloud Shell in PowerShell mode. There are no Bash or Linux-native shell examples, nor any mention of how to perform equivalent steps on Linux/macOS. The PowerShell scripts are referenced before any Azure CLI commands, and the workflow assumes familiarity with Windows-centric tools and environments.
Recommendations
  • Provide equivalent Bash/Azure CLI scripts for all PowerShell examples, especially for steps involving Microsoft Graph and service principal assignments.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and clarify which steps can be performed in Bash.
  • Add Linux/macOS-specific instructions for environment setup and authentication, including any differences in tool installation or usage.
  • Where possible, use cross-platform tools (e.g., Azure CLI, REST API) in examples, and avoid exclusive reliance on PowerShell.
  • Reorder examples so that cross-platform (CLI/Bash) instructions appear before or alongside PowerShell instructions.
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-14 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 demonstrates a moderate Windows bias. Examples and code samples are primarily in C# (a Windows-centric language), and the Azure Relay Bridge usage example shows a Windows-style command (using .\azbridge.exe), with no Linux/macOS equivalent. There are no explicit Linux/macOS shell or tool examples, and Windows tools/patterns (like .NET SDK and .exe executables) are mentioned before cross-platform alternatives.
Recommendations
  • Provide equivalent examples for Linux/macOS, such as bash or shell commands for running Azure Relay Bridge (e.g., 'dotnet azbridge.dll' or './azbridge' for Linux).
  • Include sample code in other languages (e.g., Python, Node.js) to demonstrate the Cloud Events handshake for non-Windows environments.
  • Clarify that Azure Relay Bridge can be run as a Docker container and provide a sample Docker run command.
  • Explicitly mention cross-platform support and provide instructions for installing and running tools on Linux/macOS.
  • Order examples so that cross-platform or Linux/macOS instructions are shown alongside or before Windows-specific instructions.
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-14 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 instructions using Azure PowerShell and Microsoft Graph PowerShell modules. There are no equivalent examples or guidance for Linux/macOS users who may prefer Bash, Azure CLI, or cross-platform scripting. The instructions and script assume familiarity with PowerShell, which is most commonly used on Windows, and do not mention or provide alternatives for Linux environments.
Recommendations
  • Provide equivalent Azure CLI and Bash script examples for each PowerShell command.
  • Explicitly state cross-platform requirements and note that PowerShell Core is available on Linux/macOS, with installation instructions if PowerShell is required.
  • Add notes or links for Linux/macOS users on how to install and use PowerShell modules in their environment.
  • Where possible, use Azure CLI commands, which are natively supported on all platforms, for authentication and resource management steps.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows/Powershell tools (psping.exe) are mentioned first and in detail, with Linux alternatives (telnet) only briefly referenced and lacking parity in explanation. The primary troubleshooting examples and tool recommendations are Windows-centric, with no Linux/macOS-specific troubleshooting commands or tools (e.g., nmap, nc, curl) provided for key steps. Some sections only mention Windows tools, leaving Linux users to infer equivalents.
Recommendations
  • Provide Linux/macOS equivalents for all troubleshooting commands (e.g., use 'nc', 'curl', or 'nmap' alongside 'telnet').
  • List Linux/macOS examples before or alongside Windows examples to avoid Windows-first ordering.
  • Include links to cross-platform tools and instructions for installation/use on Linux/macOS.
  • Explain how to interpret results from Linux/macOS commands, matching the detail given for Windows tools.
  • Mention platform-agnostic tools (e.g., Wireshark) earlier and more prominently.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides extensive coverage of Azure portal and PowerShell workflows, both of which are Windows-centric. PowerShell examples are given in detail, and the Azure portal is emphasized for management tasks. While Azure CLI examples are present (which are cross-platform), there is a lack of explicit Linux/macOS-specific guidance, such as shell scripting nuances, environment setup, or troubleshooting for non-Windows platforms. PowerShell is presented as a primary automation method, which may create friction for Linux/macOS users who typically use Bash or other shells.
Recommendations
  • Add explicit Bash shell script examples for Linux/macOS users, especially for resource creation and management tasks.
  • Include notes or troubleshooting tips for running Azure CLI on Linux/macOS, such as authentication, environment variables, and file path differences.
  • Clarify that PowerShell examples are primarily for Windows and suggest alternatives for Linux/macOS users (e.g., Bash, Python, or Azure CLI).
  • Ensure that CLI examples use syntax compatible with Bash (e.g., variable assignment, quoting) and avoid Windows-specific conventions.
  • Provide parity in automation examples, such as showing how to approve/reject endpoints using Azure CLI or REST API, not just PowerShell.
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-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 is heavily oriented toward Windows development environments, specifically Visual Studio and PowerShell. All instructions for project creation, package management, and tooling reference Visual Studio UI and PowerShell commands, with no mention of Linux/macOS alternatives such as VS Code, CLI workflows, or Bash. This creates friction for non-Windows users, who must adapt instructions themselves.
Recommendations
  • Add instructions for creating .NET projects using the dotnet CLI, which works cross-platform.
  • Include NuGet package installation examples using 'dotnet add package' (CLI) and mention that PowerShell is not required.
  • Reference VS Code as an alternative IDE, and provide steps for Linux/macOS users.
  • Clarify that all code samples are platform-agnostic and can be run on Linux/macOS, but tooling steps may differ.
  • Provide screenshots or terminal commands for Linux/macOS environments where appropriate.
GitHub Create Pull Request
← Previous Page 6 of 12 Next →