Event Grid

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

Bias Trend Over Time

Pages with Bias Issues

83 issues found
Showing 26-50 of 83 flagged pages
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring Service Bus queues and topics as Event Grid event handlers. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and explicit PowerShell examples are included throughout. There is no mention of Linux/macOS-specific shell patterns, nor are there Bash or scripting examples for non-Windows platforms. PowerShell is presented as a primary automation method alongside CLI, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommend it as the primary automation tool for Linux/macOS users.
  • Add Bash or shell script examples for common tasks, or explicitly show how to use the REST API with curl.
  • Note that PowerShell Core is available cross-platform, but provide guidance or links for Linux/macOS installation if PowerShell is to be used.
  • Consider listing CLI examples before PowerShell, or grouping them under 'Automation' with platform notes.
  • Explicitly state platform compatibility for each tool in the documentation.
GitHub Create Pull Request
Event Grid Webhooks as event handlers for Azure Event Grid events ...docs/blob/main/articles/event-grid/handler-webhooks.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page lists both Azure CLI and PowerShell quickstarts for key scenarios, but PowerShell (a Windows-centric tool) is consistently mentioned alongside or before Linux-friendly alternatives. There is no explicit Linux/macOS example or mention of Bash scripting, and PowerShell is presented as a primary method for event handler configuration, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users in quickstart sections.
  • Ensure Azure CLI examples are presented before PowerShell, or at least equally.
  • Clarify that Azure CLI is cross-platform and recommend it for non-Windows environments.
  • Include notes or links to Linux/macOS setup guides for webhook endpoints.
  • 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-12 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 examples. The phrase 'Consider installing manually for Windows' implies Windows is the primary platform, and all CLI commands are shown in PowerShell syntax. There are no bash or Linux/macOS instructions for generating certificates, despite the cross-platform nature of the step CLI tool.
Recommendations
  • Add equivalent bash/zsh examples for certificate generation using step CLI on Linux/macOS.
  • Clarify that step CLI is cross-platform and provide installation instructions for Linux/macOS.
  • Present examples for both Windows and Linux/macOS, or use platform-agnostic syntax where possible.
  • Avoid presenting Windows instructions first unless there is a clear user demographic justification.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation shows a Windows bias in the certificate generation section, where only Windows-specific instructions and PowerShell commands are provided. The instructions explicitly mention opening a Command Prompt and using Windows environment variables, without offering equivalent Linux/macOS shell commands or guidance. The sample application is in C#/.NET, which is cross-platform but the development workflow described (Visual Studio, NuGet) is Windows-centric. There is no explicit mention or example for Linux/macOS users for certificate generation or development environment setup.
Recommendations
  • Add Linux/macOS shell commands for certificate generation using step CLI (e.g., bash commands for creating certificates and viewing thumbprints).
  • Include instructions for running the sample code on Linux/macOS (e.g., using VS Code, .NET CLI, or Mono).
  • Present cross-platform instructions first, or side-by-side, rather than Windows-specific steps.
  • Avoid referencing Windows environment variables (like %USERPROFILE%) without Linux/macOS equivalents (like $HOME).
  • Clarify that the sample code can be run on Linux/macOS and provide any necessary setup steps.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page shows a Windows/Powershell bias in the section on escaping special characters in topic templates. Only PowerShell-specific escaping is described and examples are given, with no mention of Linux/macOS shells (e.g., Bash, zsh) or their escaping requirements. This may confuse or hinder non-Windows users when configuring topic templates with special characters.
Recommendations
  • Add examples for escaping special characters in common Linux/macOS shells (e.g., Bash, zsh), showing how to handle $ and | in topic templates.
  • Include a general note about shell differences and link to external resources or documentation for shell-specific escaping.
  • Present escaping instructions for multiple platforms side-by-side, or at least mention Linux/macOS considerations before or alongside Windows examples.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
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 Linux/macOS users, such as Bash, Azure CLI, or cross-platform scripting alternatives. The use of PowerShell and references to PowerShell modules (e.g., Microsoft.Graph.PowerShell) creates friction for users on non-Windows platforms.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples for each step.
  • Explicitly mention cross-platform alternatives and how to install required modules on Linux/macOS.
  • Clarify which steps can be performed in the Azure Portal or via REST API, and provide links or examples.
  • Add a note about PowerShell Core compatibility and installation instructions for Linux/macOS if PowerShell must be used.
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-12 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 using PowerShell scripts and referencing the Azure Cloud Shell in PowerShell mode for critical configuration steps. There are no Bash or Linux-native shell examples provided, and PowerShell commands are presented first and as the only option for key tasks such as service principal role assignments. This creates friction for Linux/macOS users who may prefer Bash or native CLI tools.
Recommendations
  • Provide equivalent Bash/Azure CLI scripts for all PowerShell examples, especially for service principal and role assignment steps.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and clarify which steps can be performed in Bash.
  • Add Linux/macOS-specific notes or troubleshooting tips for common issues encountered outside of Windows environments.
  • Where possible, use cross-platform Azure CLI commands instead of PowerShell for resource management tasks.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Examples and code samples are predominantly in Windows-centric formats: the C# sample is Windows-oriented, and the Azure Relay Bridge usage example uses Windows path notation ('.\azbridge.exe'), with no explicit Linux/macOS command or example. There is no mention of Linux-specific tools, patterns, or code samples, nor are alternative shell commands (e.g., Bash) shown. The documentation references .NET and C# as the primary implementation language, which is more common on Windows, and does not provide parity examples for Linux/macOS users.
Recommendations
  • Provide Linux/macOS command examples for Azure Relay Bridge (e.g., './azbridge' instead of '.\azbridge.exe').
  • Include sample code for the Cloud Events validation handshake in a cross-platform language (e.g., Python, Node.js) alongside the C# example.
  • Explicitly mention that Azure Relay Bridge can run on Linux/macOS and provide Docker usage instructions.
  • Add Bash or shell script equivalents for Azure CLI commands where appropriate.
  • Clarify cross-platform support in each step, especially for implementation and tooling.
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-12 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 sample scripts and instructions using Azure PowerShell and Microsoft Graph PowerShell modules. There are no Bash, CLI, or Linux/macOS shell examples provided. The instructions assume familiarity with PowerShell and Windows-centric tooling, which may create friction for Linux/macOS users who typically use Bash and the Azure CLI.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for Linux/macOS users.
  • Explicitly mention cross-platform alternatives and clarify which steps can be performed using CLI or REST APIs.
  • Add notes about installing and using PowerShell Core on Linux/macOS if PowerShell is required.
  • Reorder or balance examples so that Linux/macOS approaches are presented alongside or before Windows/PowerShell ones.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting Windows/Powershell examples and tools (psping.exe, tcpping.exe) first and in greater detail, while Linux alternatives are mentioned briefly or omitted. The primary troubleshooting commands and tool recommendations are Windows-centric, with only a minimal Linux example (telnet) provided, lacking parity in explanation and depth.
Recommendations
  • Provide Linux/macOS equivalents for all troubleshooting commands (e.g., use 'nc' or 'nmap' for port checks, 'hping3' for TCP ping).
  • List Linux/macOS examples alongside or before Windows examples to ensure equal visibility.
  • Recommend cross-platform tools (e.g., Wireshark, curl) where possible, and clarify installation steps for both Windows and Linux/macOS.
  • Avoid referencing Windows-only tools (psping.exe, tcpping.exe) without Linux/macOS alternatives.
  • Expand Linux/macOS troubleshooting sections to match the detail given to Windows instructions.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring Event Grid topics and subscriptions, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented immediately after CLI examples. The Visual Studio instructions for Azure Functions are Windows-focused, referencing Windows-only tools and workflows (NuGet Package Manager Console, Solution Explorer), with no mention of Linux/macOS alternatives or cross-platform .NET CLI usage. There are no explicit Linux/macOS examples or guidance for users developing on those platforms.
Recommendations
  • Prioritize Azure CLI examples, as it is cross-platform, and move PowerShell examples to a separate section or appendix.
  • Add explicit Linux/macOS instructions for .NET development, such as using the dotnet CLI to manage NuGet packages and edit project files.
  • Include guidance for using VS Code on Linux/macOS, and clarify any platform-specific steps.
  • Where Windows-only tools are mentioned (e.g., Visual Studio Solution Explorer), provide equivalent steps for VS Code or command-line workflows.
  • Add a note clarifying that PowerShell examples are primarily for Windows users, and recommend Azure CLI for cross-platform scenarios.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation contains a section specifically about escaping special characters in PowerShell, with examples shown only for PowerShell. There is no mention of how to escape these characters in Linux/macOS shells (e.g., Bash), nor are examples provided for those platforms. This creates friction for non-Windows users, as they may not know how to adapt the instructions for their environment.
Recommendations
  • Add equivalent examples for escaping special characters in Bash and other common Linux/macOS shells.
  • Explicitly mention the differences in escaping between PowerShell and Bash/zsh, and provide guidance for each.
  • Ensure that CLI examples and instructions are platform-neutral or include platform-specific notes for both Windows and Linux/macOS users.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, especially in sections related to enabling managed identities and disabling local authentication. Windows-specific tools (PowerShell) are given explicit examples, while Linux/macOS equivalents (such as Bash or Azure CLI) are either mentioned after or not provided with parity in detail. Screenshots and walkthroughs reference the Azure portal, which is platform-agnostic, but command-line examples favor Windows environments. There are no explicit Linux/macOS shell examples for environment variable setup or SDK usage, and PowerShell is presented as the main scripting tool for resource management.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for all PowerShell commands, especially for resource creation and configuration.
  • Include environment variable setup examples for Linux/macOS (e.g., export in Bash) alongside Windows (SetEnvironmentVariable in C#).
  • Ensure that CLI examples are presented before or alongside PowerShell, not after.
  • Add notes or sections clarifying any platform-specific differences in SDK usage or authentication flows.
  • Where screenshots are used, clarify that the Azure portal is accessible from any OS.
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 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation primarily demonstrates deployment via the Azure Portal and references Azure PowerShell as an alternative, with no explicit Linux/macOS-specific instructions or CLI examples. The mention of Azure PowerShell precedes Azure CLI, and there are no bash or Linux/macOS terminal examples for deploying the ARM template or interacting with Blob storage. This may create friction for Linux/macOS users who prefer command-line tools.
Recommendations
  • Add explicit Azure CLI examples for template deployment and resource management, as Azure CLI is cross-platform.
  • Include bash or shell commands for uploading files to Blob storage, demonstrating how to trigger events from Linux/macOS.
  • Reference Linux/macOS compatibility and provide links to platform-agnostic tools.
  • Ensure that alternative deployment methods (CLI, REST API) are shown with parity and not only mentioned.
  • Reorder mentions so that Azure CLI is listed before or alongside PowerShell, emphasizing cross-platform support.
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 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring IP firewall rules for Azure Event Grid topics or domains. However, PowerShell (a Windows-centric tool) is given a dedicated section with multiple examples, and the CLI examples are presented using Azure CLI, which is cross-platform but not explicitly shown in a Linux/macOS context. There are no Linux-specific shell examples (e.g., bash scripts), nor is there mention of Linux tools or patterns. The PowerShell section is detailed and assumes familiarity with Windows tooling, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit bash or shell script examples for Linux/macOS users, especially for common tasks like variable assignment and command chaining.
  • Clarify that Azure CLI commands work on Linux/macOS and provide example shell environments (e.g., bash, zsh).
  • Consider adding a note or section for Linux/macOS users, highlighting any differences or prerequisites.
  • Balance the PowerShell section with equivalent Linux/macOS scripting guidance, or link to cross-platform scripting resources.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows users, specifically those using Visual Studio and PowerShell. All instructions for creating projects, managing dependencies, and running code are given in the context of Visual Studio, with no mention of cross-platform alternatives like VS Code or command-line .NET tools. NuGet package installation is shown only via the PowerShell Package Manager Console, which is Windows-specific. There are no Linux/macOS-specific instructions or examples, and the workflow assumes a Windows development environment throughout.
Recommendations
  • Add instructions for creating and managing .NET projects using the cross-platform dotnet CLI (e.g., 'dotnet new console', 'dotnet add package').
  • Include guidance for using VS Code or other cross-platform editors, not just Visual Studio.
  • Show NuGet package installation using 'dotnet add package' in addition to PowerShell.
  • Explicitly state that the .NET SDK and Azure SDK are cross-platform, and provide steps for Linux/macOS users.
  • Add screenshots or terminal examples from Linux/macOS environments.
  • Clarify any Windows-only requirements (if any), or remove them if not necessary.
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-11 06:20
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 use PowerShell syntax, with no mention of Bash, Azure CLI, or Linux/macOS alternatives. There are no instructions or examples for completing the tutorial from a Linux or macOS environment, and the required tooling (AzureRM.Tags module) is PowerShell-specific.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell commands, especially for updating VM tags.
  • Clarify whether the runbook and module steps can be performed from Linux/macOS, and provide guidance if so.
  • Mention cross-platform alternatives to the AzureRM.Tags module, such as using the Az CLI or REST API.
  • Add a note about installing and using PowerShell Core on Linux/macOS if PowerShell is required.
  • Ensure screenshots and UI instructions are not Windows-specific unless necessary.
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-11 06:20
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 building and publishing the Azure Functions app and the sample data generator. There are no instructions or examples for Linux/macOS users, such as using VS Code, Azure Functions Core Tools, or .NET CLI. All development and deployment steps assume a Windows environment and Visual Studio usage, creating friction for users on other platforms.
Recommendations
  • Add instructions for publishing the Azure Functions app using VS Code and Azure Functions Core Tools, which are cross-platform.
  • Include steps for building and running the WindTurbineDataGenerator using the .NET CLI (dotnet build/run) instead of only Visual Studio.
  • Clarify that the sample project can be used on Linux/macOS and provide any necessary setup steps for those platforms.
  • Provide screenshots or terminal examples for Linux/macOS environments where appropriate.
  • Mention alternative editors (VS Code, JetBrains Rider) and provide parity in guidance.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation shows a moderate Windows bias in the certificate generation section. The instructions for installing and using the Step CLI are written with Windows users in mind, including references to opening a command prompt in the user profile folder and using Powershell syntax for commands. There is no explicit mention of Linux/macOS equivalents, nor are there examples or instructions for those platforms. However, the rest of the guide (Azure portal usage, MQTTX app) is cross-platform and does not favor Windows.
Recommendations
  • Add explicit instructions for installing Step CLI on Linux and macOS, including links to platform-specific installation guides.
  • Provide command examples using bash/zsh syntax for Linux/macOS users, and clarify any differences in file paths or environment variables.
  • Replace or supplement references to '%USERPROFILE%' and 'Win+R' with cross-platform alternatives (e.g., '~' for home directory on Unix-like systems).
  • Note that the Step CLI commands are identical across platforms, but clarify any OS-specific steps for certificate file access and permissions.
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-11 06:20
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 is a Windows-centric tool and is presented as a primary automation option alongside Azure CLI. There are explicit instructions and notes for installing Azure PowerShell, but no equivalent Linux/macOS-specific guidance or alternative shell examples (e.g., Bash, zsh). The CLI and PowerShell examples are presented in parallel, but PowerShell is given equal prominence, which may suggest Windows bias. The sample application for dead-letter event processing is .NET-based, further reinforcing a Windows-centric approach.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommend it as the preferred automation tool for Linux/macOS users.
  • Add explicit Bash/zsh scripting examples where relevant, especially for tasks involving environment variables or shell scripting.
  • Include installation notes or troubleshooting tips for Azure CLI on Linux/macOS, similar to the PowerShell installation note.
  • Provide sample applications or code snippets in languages/platforms popular on Linux/macOS (e.g., Python, Node.js) in addition to .NET.
  • Consider reordering examples to present Azure CLI first, emphasizing its cross-platform nature.
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-11 06:20
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 examples. The installation note for 'step CLI' mentions Windows manual installation but omits Linux/macOS guidance. All command-line examples are shown in PowerShell syntax, and there is no mention of Linux or macOS workflows, creating friction for non-Windows users.
Recommendations
  • Add Linux/macOS shell (bash/zsh) examples for certificate generation using 'step CLI'.
  • Include installation instructions or links for 'step CLI' on Linux and macOS.
  • Present cross-platform command examples side-by-side or indicate platform-specific steps.
  • Clarify that the Azure CLI commands are platform-agnostic and can be run on any OS.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation displays a Windows bias in the certificate generation section, where all example commands are shown in PowerShell and instructions reference Windows-specific actions (e.g., opening Command Prompt via Win+R and %USERPROFILE%). There are no Linux/macOS shell equivalents for the certificate creation steps, and the sample code is tailored for Visual Studio and NuGet, which are primarily Windows-centric tools. While the Azure CLI commands themselves are cross-platform, the initial setup and examples favor Windows users.
Recommendations
  • Provide Linux/macOS shell equivalents for certificate generation commands (e.g., bash commands for step CLI).
  • Include instructions for opening a terminal and navigating to the user profile directory on Linux/macOS.
  • Mention cross-platform IDEs (e.g., VS Code) and package managers (e.g., dotnet CLI) for running the sample code.
  • Present examples for both Windows and Linux/macOS side-by-side, or clarify that the commands work on all platforms.
  • Add explicit notes or sections for Linux/macOS users where workflows differ.
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-11 06:20
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 sample scripts and instructions using PowerShell syntax and cmdlets. There are no equivalent examples or guidance for Linux/macOS users, such as Bash or Azure CLI alternatives. The use of PowerShell and references to 'Write-Host' and other Windows-centric patterns may create friction for users on non-Windows platforms.
Recommendations
  • Provide equivalent sample scripts using Azure CLI (az) and/or Bash for Linux/macOS users.
  • Explicitly mention cross-platform compatibility of Azure PowerShell and how to install/use it on Linux/macOS.
  • Add notes or links to documentation for Linux/macOS users, including prerequisites and environment setup.
  • Consider showing Azure CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All examples and instructions are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or Linux/macOS workflows. The script relies on PowerShell-specific cmdlets and patterns, making it difficult for Linux/macOS users to follow without adaptation.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for Linux/macOS users.
  • Explicitly mention cross-platform alternatives and note any platform-specific requirements.
  • Add a section clarifying whether the PowerShell script can run on PowerShell Core on Linux/macOS, or provide tested instructions for those platforms.
  • List prerequisites for both Windows and Linux/macOS environments, including installation steps for required modules.
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-11 06:20
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 using PowerShell scripts and referencing the Azure Cloud Shell with PowerShell as the default environment for critical configuration steps. There are no Bash or Linux-native shell examples, and instructions for using PowerShell appear before any mention of Azure CLI (which is cross-platform). This may create friction for Linux/macOS users who are less familiar with PowerShell or prefer Bash.
Recommendations
  • Provide equivalent Bash/Azure CLI scripts for all steps currently shown only in PowerShell.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
  • Ensure all referenced scripts (linked .md files) have Linux/Bash versions or alternatives.
  • Where possible, use Azure CLI (which is cross-platform) for examples, or show both PowerShell and CLI side-by-side.
  • Add notes clarifying that all steps can be performed on Linux/macOS, and highlight any platform-specific caveats.
GitHub Create Pull Request
← Previous Page 2 of 4 Next →