Event Grid

The documentation provides both Azure CLI (Bash) and PowerShell examples for sending events, but the PowerShell section is given equal prominence and detail, and the instructions for using Cloud Shell mention PowerShell sessions first. There is a slight Windows-first bias in the ordering and presentation, but Linux users are not blocked from completing the tutorial, as Bash/CLI instructions are present and complete.

• Present Bash/Azure CLI instructions before PowerShell, as Bash is more universally available across platforms.
• Explicitly mention that Bash/CLI instructions work on Linux/macOS and that PowerShell is optional.
• Add a note clarifying that all steps can be completed on Linux/macOS using Bash/CLI.
• Consider including a curl-only example outside of Azure CLI for users who may not use Azure CLI or PowerShell.

The documentation provides both Azure CLI (Bash) and Azure PowerShell examples for sending events, but the PowerShell example is given equal prominence, and there is a slight tendency to mention Windows-centric tools (PowerShell, Visual Studio Code) without explicit Linux/macOS alternatives. However, the main workflow (Azure CLI and cURL) is cross-platform and the instructions for Bash are clear and complete. No critical steps are Windows-only, and Linux/macOS users can follow the guide without significant friction.

• Explicitly mention that Visual Studio Code and Azure CLI instructions work on Linux/macOS, and provide links to installation guides for those platforms.
• Add a note clarifying that Azure PowerShell is available on Linux/macOS, or provide a Bash-only workflow for users who prefer not to use PowerShell.
• Where PowerShell is referenced, clarify its cross-platform availability, or offer alternative commands for Linux/macOS users.
• Consider listing Bash/Azure CLI instructions before PowerShell to reduce perceived Windows-first bias.

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 the CLI, and detailed PowerShell commands are included without mentioning cross-platform alternatives or clarifying PowerShell Core compatibility. There is also a slight 'Windows first' bias, as PowerShell is presented as a primary automation option alongside CLI, which may confuse Linux/macOS users. No Linux-specific tools or shell examples (e.g., Bash scripts) are provided.

• Clarify that Azure PowerShell is available cross-platform (PowerShell Core), or specify if examples require Windows-only PowerShell.
• Add Bash or shell script examples for Linux/macOS users, especially for automation tasks.
• Consider mentioning the parity and limitations between CLI and PowerShell for different platforms.
• Explicitly state that all CLI commands work on Linux/macOS and Windows.
• If REST API examples are shown, consider including curl commands for Linux/macOS users.

The documentation provides both Azure CLI and PowerShell examples for all major operations, but consistently presents PowerShell examples alongside CLI, and sometimes with more detail. PowerShell is a Windows-centric tool, and its prominence may signal a Windows bias. However, Azure CLI is cross-platform and shown first in every example, mitigating the bias. No Linux-specific tools or shell examples (e.g., curl for HTTP POST) are given, and no macOS-specific notes are present.

• Add Linux/macOS-specific notes or examples where relevant (e.g., using curl or wget for HTTP POST requests).
• Include Bash shell script examples for tasks like publishing events, especially for HTTP POST operations.
• Explicitly mention that Azure CLI works on Linux/macOS and Windows, and provide installation links.
• Consider adding a section or tab for REST API usage with curl, which is common on Linux/macOS.
• If PowerShell is shown, clarify that PowerShell Core is cross-platform, or provide Bash alternatives.

The documentation page lists both Azure CLI and PowerShell quickstarts for key scenarios, but consistently mentions PowerShell (a Windows-centric tool) alongside Azure CLI, and sometimes before or equally with CLI. There is no explicit Linux/macOS example, nor are Linux-specific tools or shell patterns referenced. The presence of PowerShell examples may create a subtle Windows bias, especially for users seeking Linux-native instructions.

• Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and provide bash shell examples where relevant.
• Add Linux/macOS-specific instructions or notes, such as using curl for REST calls or bash for scripting.
• If PowerShell is referenced, clarify that PowerShell Core is available cross-platform, or provide alternative shell commands.
• Consider listing Azure CLI examples before PowerShell to emphasize platform neutrality.
• Include troubleshooting or setup notes for Linux/macOS environments where differences may arise.

The documentation provides both Azure CLI and PowerShell examples for all major steps, but PowerShell (a Windows-centric tool) is always shown immediately after CLI, and receives equal prominence. There are no Linux-specific shell examples (e.g., Bash), nor are cross-platform scripting patterns (like Python or REST) mentioned. The CLI examples are cross-platform, but the repeated inclusion of PowerShell may signal a Windows bias, especially for users who expect Linux-native scripting approaches.

• Clarify that Azure CLI examples are cross-platform and can be run on Windows, Linux, and macOS.
• Consider including Bash shell examples for Linux/macOS users, especially for tasks involving environment variables and curl.
• Add a note that PowerShell examples are primarily for Windows users, and suggest alternatives for Linux/macOS.
• Where possible, provide REST API or Python SDK snippets to further increase platform neutrality.
• If PowerShell is included, ensure parity by including equivalent Bash or shell script examples.

The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for all key steps, but PowerShell is consistently presented as a first-class option, and Windows tools/patterns (PowerShell, screenshots from Azure portal on Windows) are given equal or more prominence than Linux-native workflows. There are no Linux/macOS-specific shell examples (e.g., pure Bash/curl without Azure CLI), and PowerShell is referenced as a default in Cloud Shell instructions, which may cause friction for Linux/macOS users.

• Add explicit Bash/curl examples for sending events, independent of Azure CLI, to help users on Linux/macOS who may not use PowerShell.
• In Cloud Shell instructions, clarify that Bash is available and provide Bash-first examples.
• When listing options (CLI, PowerShell, portal), alternate the order or present CLI/Bash examples before PowerShell to reduce Windows-first bias.
• Include notes or links for installing Azure CLI on Linux/macOS, and clarify that all CLI commands work cross-platform.
• Add troubleshooting tips for common Linux/macOS issues (e.g., curl syntax, date formatting differences).

The documentation page shows mild Windows bias. While code samples are provided for multiple languages and platforms, there is a notable emphasis on Windows-specific tools and patterns. The only explicit CLI command shown is 'az account list-locations', which is cross-platform, but the documentation references PowerShell as a sample language and includes it in the code tabs. Additionally, the instructions for obtaining the Azure region name mention using the Azure CLI, which is available on Linux/macOS, but do not mention Linux/macOS-specific alternatives or shell patterns. The order of code samples and examples often places Windows-centric tools (PowerShell, C#) before Linux-friendly ones (Python, JavaScript). There are no Linux-specific troubleshooting notes, nor are there explicit mentions of Linux/macOS development environments or shell commands.

• Add explicit notes and examples for Linux/macOS users, such as bash/zsh shell commands for obtaining Azure region names.
• Ensure parity in code sample ordering by rotating or randomizing the order, or by starting with a neutral language (e.g., Python or JavaScript).
• Include troubleshooting or setup notes for Linux/macOS environments, especially for authentication and SDK installation.
• Clarify that Azure CLI and SDKs are cross-platform and provide links or instructions for installing them on Linux/macOS.
• Provide sample code or links for Linux shell scripting where relevant, especially for automation tasks.