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 226-250 of 289 flagged pages
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/mqtt-client-microsoft-entra-token-and-rbac.md
...ent-grid/mqtt-client-microsoft-entra-token-and-rbac.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by exclusively describing role assignment and management via the Azure Portal UI, which is most commonly accessed and documented in a Windows context. There are no CLI, PowerShell, or command-line examples (which could be cross-platform), nor are there Linux-specific instructions or examples for authentication, token acquisition, or role assignment. The absence of CLI or Linux-native tooling examples may disadvantage Linux users or those automating tasks outside the Azure Portal.
Recommendations
- Add Azure CLI examples for assigning roles (e.g., using `az role assignment create`) alongside or before portal instructions to ensure parity for Linux and automation users.
- Include sample commands for obtaining Microsoft Entra JWT tokens using cross-platform tools such as curl, Azure CLI, or relevant SDKs in Python or Bash.
- Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and provide links to CLI documentation.
- Where possible, provide both portal and command-line instructions, and avoid assuming the user is operating in a Windows environment.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in the certificate generation section, where instructions and context are tailored to Windows users (e.g., opening a command prompt in %USERPROFILE%), and there are no equivalent Linux or macOS instructions or examples. The rest of the guide is platform-neutral, especially when using the cross-platform MQTTX app, but the initial setup lacks Linux parity.
Recommendations
- Provide explicit Linux and macOS instructions for installing and using the step CLI, including example terminal commands for common distributions (e.g., apt, yum, brew).
- Replace or supplement the '%USERPROFILE%' and 'command prompt' references with platform-agnostic or platform-specific alternatives (e.g., '~' for Linux/macOS, and mention Terminal for non-Windows users).
- Add notes or callouts clarifying any platform-specific differences in file paths or environment variables.
- Wherever commands are shown, provide both Windows (PowerShell/cmd) and Linux/macOS (bash) equivalents, especially for certificate generation and file path references.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples, but consistently lists PowerShell examples immediately after CLI, and in some sections, PowerShell is given equal or more detailed coverage. There are no explicit Linux-specific examples or mentions of Linux-native tools (e.g., curl, jq) outside of the CLI section, and the PowerShell examples are more verbose and detailed. The use of Azure Cloud Shell is mentioned, but it defaults to both Bash and PowerShell without highlighting Linux workflows. There is no explicit bias in tool availability, but the structure and example order subtly favor Windows/PowerShell users.
Recommendations
- Add explicit Linux/Bash-native examples (e.g., using curl, jq, or bash scripting) outside of just Azure CLI.
- In sections where both PowerShell and CLI are shown, alternate the order or clarify that CLI is cross-platform and preferred for Linux/Mac users.
- Highlight that Azure CLI commands are fully supported on Linux and Mac, and provide troubleshooting tips for common Linux environments.
- Where Cloud Shell is mentioned, clarify that Bash is the default for Linux users and show Bash-specific workflows.
- Consider adding a 'Linux' or 'macOS' tab in code examples to show parity and avoid the impression of Windows/PowerShell primacy.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/auth0-log-stream-app-insights.md
...n/articles/event-grid/auth0-log-stream-app-insights.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively references Visual Studio Code and Azure portal workflows without specifying or providing parity for Linux environments. All instructions assume the use of VS Code and Azure tools, which are cross-platform, but there is no mention of Linux-specific considerations, CLI alternatives, or examples for Linux users. There are no PowerShell-specific commands, but the lack of explicit Linux examples or terminal/CLI instructions constitutes a subtle Windows-first bias.
Recommendations
- Include explicit instructions or notes for Linux users, such as verifying that all steps work identically on Linux.
- Provide Azure CLI commands as alternatives to portal-based steps, especially for creating and deploying Azure Functions.
- Mention any Linux-specific prerequisites or troubleshooting tips (e.g., Node.js installation, VS Code extensions).
- Add screenshots or terminal examples from Linux environments where applicable.
- Clarify that the process is cross-platform and highlight any differences, if any, for Linux or macOS users.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/auth0-log-stream-blob-storage.md
...n/articles/event-grid/auth0-log-stream-blob-storage.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing the Azure Portal (a web-based GUI) and Visual Studio Code for setup and deployment, without providing any command-line examples (such as Azure CLI or PowerShell) or Linux-specific instructions. There are no explicit Linux or cross-platform terminal commands, and all configuration steps are described via GUI navigation, which is more familiar to Windows users. There is also an assumption that users will use the clipboard and GUI-based workflows, which are more common in Windows environments.
Recommendations
- Add equivalent instructions using Azure CLI for all major steps (function creation, configuration, deployment, event subscription), including sample commands.
- Provide examples for deploying and configuring Azure Functions from Linux/macOS terminals.
- Include notes or links for users who prefer command-line or automation approaches, highlighting cross-platform compatibility.
- Clarify that Visual Studio Code and Azure CLI are available on Linux and macOS, and provide any necessary setup links.
- Offer alternative instructions for copying connection strings and managing secrets using environment variables or CLI tools, not just GUI/clipboard methods.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/authenticate-with-entra-id-namespaces.md
...es/event-grid/authenticate-with-entra-id-namespaces.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by referencing Windows-specific resources first (e.g., linking to configuring managed identities on a Windows VM) and omitting explicit Linux or cross-platform examples. There are no PowerShell-heavy sections or exclusive use of Windows tools, but the absence of Linux/Unix-specific instructions or examples may hinder parity for non-Windows users.
Recommendations
- When referencing enabling managed identities, provide links and instructions for both Windows and Linux VMs (e.g., link to both Windows and Linux VM managed identity guides).
- Include explicit examples or notes for Linux environments, especially in sections discussing enabling managed identities or configuring environment variables.
- If providing code snippets that set environment variables (e.g., using Environment.SetEnvironmentVariable in C#), add equivalent shell commands for Linux/macOS (e.g., export AZURE_CLIENT_ID=...).
- Ensure that all Azure portal instructions are clearly marked as cross-platform, and where CLI or scripting is involved, provide both PowerShell and Bash/Azure CLI equivalents.
- Review all links and references to ensure Linux and cross-platform documentation is equally discoverable and prioritized alongside Windows resources.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/blob-event-quickstart-template.md
.../articles/event-grid/blob-event-quickstart-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation primarily describes deployment using the Azure Portal and references PowerShell in the context of alternative deployment methods, but does not provide explicit examples or instructions for Linux users (e.g., Azure CLI or Bash). The only alternative method directly linked is PowerShell, and there are no Linux-specific tools or command-line examples provided.
Recommendations
- Add explicit Azure CLI (cross-platform) deployment instructions alongside or before PowerShell references.
- Provide Bash shell command examples for uploading files to Blob storage (e.g., using az storage blob upload or curl), not just portal-based instructions.
- When listing deployment methods, mention Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
- Include notes or links to Linux/macOS-specific guidance where relevant, especially for command-line operations.
- Ensure that all referenced documentation (such as 'Deploy templates') includes parity between PowerShell and CLI/Bash examples.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/custom-event-to-hybrid-connection.md
...ticles/event-grid/custom-event-to-hybrid-connection.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily in the application development and event processing sections. While the Azure CLI and curl commands are cross-platform, the only example for building a listener application is for C# using Visual Studio on Windows, with explicit instructions to use Visual Studio 2019 or later. There are no equivalent instructions or examples for Linux or macOS users, nor are alternative languages or tools highlighted for non-Windows environments.
Recommendations
- Add explicit instructions and examples for building and running the listener application on Linux and macOS, including how to use .NET Core/SDK and cross-platform editors like VS Code.
- Provide alternative sample applications in additional languages (e.g., Python, Node.js) that are commonly used on Linux.
- Clarify that Visual Studio is not required and that .NET projects can be built and run using the dotnet CLI on any OS.
- Include links to cross-platform setup guides for .NET and other supported languages.
- Where possible, mention Linux and macOS as supported environments in the prerequisites and throughout the tutorial.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/enable-identity-partner-topic.md
...n/articles/event-grid/enable-identity-partner-topic.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes how to enable managed identity for an Azure Event Grid partner topic using the Azure portal, a web-based interface accessible from any OS. However, it omits any command-line examples (such as Azure CLI or Azure PowerShell), and does not mention Linux-specific workflows or tools. While not overtly Windows-specific, the lack of CLI examples (which are often more relevant to Linux users) and the focus on graphical interface workflows can be considered a subtle 'Windows-first' or 'GUI-first' bias.
Recommendations
- Add Azure CLI examples for assigning system-assigned and user-assigned managed identities, as Azure CLI is cross-platform and widely used on Linux.
- If relevant, provide Azure PowerShell examples as well, but ensure CLI examples are presented first or alongside PowerShell.
- Explicitly mention that the Azure portal is accessible from any OS to clarify cross-platform compatibility.
- Include a section or links for automating these tasks via scripts, which is common in Linux environments.
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
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation exclusively uses PowerShell-based runbooks and AzureRM modules, which are Windows-centric. There are no examples or guidance for using Python or other cross-platform scripting languages in Azure Automation, nor any mention of Linux-specific considerations or alternatives. All code snippets and automation steps assume a Windows/PowerShell environment.
Recommendations
- Provide equivalent examples using Python runbooks, which are supported in Azure Automation and are cross-platform.
- Include notes or sections on how to adapt the automation for Linux VMs, such as using Azure CLI or Bash scripts.
- Mention that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical) and link to relevant documentation for non-Windows users.
- Add guidance or links for users who manage Linux VMs, including tagging and automation best practices for Linux environments.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/event-grid-namespace-managed-identity.md
...es/event-grid/event-grid-namespace-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation exclusively describes how to enable managed identity for an Event Grid namespace using the Azure portal, which is a graphical interface commonly associated with Windows environments. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), and no mention of Linux or cross-platform tooling. This approach implicitly favors Windows users and those comfortable with GUI workflows, while omitting guidance for Linux users or those who prefer automation and scripting.
Recommendations
- Add step-by-step instructions for enabling managed identity using the Azure CLI, which is cross-platform and widely used on Linux.
- Include equivalent examples using Azure PowerShell for parity, but ensure CLI examples are presented first or alongside PowerShell.
- Explicitly mention that the Azure portal is accessible from any OS, but also provide non-GUI alternatives for users on Linux or those automating deployments.
- Where possible, provide Bash script snippets for common tasks to support Linux users.
- Review all images and instructions to ensure they are not specific to Windows-only UI conventions.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/event-schema-container-registry.md
...articles/event-grid/event-schema-container-registry.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is largely platform-neutral, focusing on event schemas and JSON payloads. However, there is a subtle Windows bias in the example event payloads: the 'useragent' field in the image pushed event contains 'os/windows' and 'Docker-Client/18.03.0-ce (windows)', which may suggest Windows as the default or primary environment. No explicit Linux or cross-platform user agents are shown, and no Linux-specific examples or tools are mentioned. There are no PowerShell or Windows command-line examples, but the only concrete client environment shown is Windows.
Recommendations
- Provide example event payloads that include both Windows and Linux user agents in the 'useragent' field to illustrate cross-platform usage.
- Explicitly mention that Azure Container Registry and Event Grid are cross-platform and can be used from Linux, macOS, and Windows.
- If referencing client tools (e.g., Docker), show example user agents or commands from both Windows and Linux environments.
- Ensure that any future command-line or code examples are provided for both Windows (PowerShell/CMD) and Linux (Bash) where applicable.
Event Grid
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/get-access-keys.md
...-docs/blob/main/articles/event-grid/get-access-keys.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation presents Azure PowerShell instructions before Azure CLI, which may suggest a Windows-first approach. PowerShell is typically associated with Windows environments, while Azure CLI is cross-platform and more commonly used on Linux and macOS. No Linux-specific examples or terminal screenshots are provided, and there is no mention of Bash or shell scripting, which are common on Linux.
Recommendations
- Present Azure CLI instructions before PowerShell, as CLI is cross-platform and more inclusive for Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and consider including a Bash example or terminal screenshot.
- Add a note or section highlighting Linux/macOS compatibility and any prerequisites for those platforms.
- If possible, provide troubleshooting tips or environment setup guidance for Linux users.
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
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page lists PowerShell samples before CLI samples in the 'Next steps' section, suggesting a preference for Windows tooling. There is no explicit mention of Linux or Bash examples, and the only command-line sample linked is for Azure CLI, which is cross-platform but is listed after PowerShell.
Recommendations
- List Azure CLI (cross-platform) samples before PowerShell samples to avoid implying a Windows-first approach.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Add Bash or shell script examples where appropriate to ensure Linux users are equally supported.
- Include a note or section highlighting Linux/macOS compatibility and usage patterns.
Event Grid
Concepts (push delivery) in Event Grid basic
...s/azure-docs/blob/main/articles/event-grid/concepts.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page provides links to example resources for creating Event Grid subscriptions, listing Azure CLI, PowerShell, and ARM template samples. The PowerShell sample is mentioned second, immediately after the CLI sample, and before ARM templates. No Linux-specific tools or examples are missing, but the ordering may subtly suggest Windows/PowerShell as a primary approach.
Recommendations
- List cross-platform tools (such as Azure CLI) before Windows-specific tools (PowerShell) to reinforce platform neutrality.
- Explicitly state that Azure CLI and ARM templates are fully supported on Linux/macOS.
- Consider adding Bash or REST API examples if relevant, to further demonstrate Linux parity.
- If possible, clarify that PowerShell is available cross-platform, but is traditionally associated with Windows.
Event Grid
Concepts (push delivery) in Event Grid basic
...s/azure-docs/blob/main/articles/event-grid/concepts.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page provides example links for creating Event Grid subscriptions using Azure CLI, Azure PowerShell, and Azure Resource Manager templates. The PowerShell example is listed before the Resource Manager template, and both CLI and PowerShell are mentioned, but there is no explicit Linux shell (e.g., Bash) example or mention of Linux-specific tools. However, Azure CLI is cross-platform and the page does not contain Windows-specific commands, tools, or patterns. The bias is minor and limited to the order of example links.
Recommendations
- Clarify that Azure CLI is cross-platform and works on Linux/macOS as well as Windows.
- Add explicit Bash or Linux shell examples if there are any platform-specific considerations.
- Consider listing CLI examples before PowerShell to emphasize cross-platform parity.
- Add a note that PowerShell Core is available on Linux/macOS if PowerShell examples are relevant.
Event Grid
Concepts (push delivery) in Event Grid basic
...s/azure-docs/blob/main/articles/event-grid/concepts.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page provides example links for creating Event Grid subscriptions using Azure CLI, Azure PowerShell, and ARM templates. The PowerShell example is listed before the ARM template, and both CLI and PowerShell are mentioned, but no explicit Linux/macOS shell or Bash examples are given. PowerShell is a cross-platform tool, but its historical association with Windows and its placement before other examples may create a perception of Windows bias. No Windows-only tools or patterns are referenced, and the main concepts are platform-neutral.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users, or clarify that Azure CLI examples work identically across platforms.
- List Azure CLI (which is cross-platform) and Bash examples before PowerShell to reduce perceived Windows-first bias.
- Include a note clarifying PowerShell's cross-platform support, if PowerShell examples are retained.
- Ensure that all referenced sample scripts have clear instructions for both Windows and Linux/macOS environments.
Event Grid
Send Blob storage events to web endpoint - Bicep
...ain/articles/event-grid/blob-event-quickstart-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for deploying the Bicep file, but PowerShell is shown as a primary option alongside CLI, and there is no mention of Linux/macOS-specific considerations. The PowerShell example may imply a Windows environment, and the documentation does not clarify that Azure CLI is cross-platform or provide explicit Linux/macOS instructions or screenshots.
Recommendations
- Explicitly state that Azure CLI works on Windows, Linux, and macOS, and recommend it as the default cross-platform option.
- Present Azure CLI examples before PowerShell, or in a separate section labeled for Windows users.
- Add notes or screenshots showing the process on Linux/macOS terminals.
- Clarify that PowerShell Core is available cross-platform, if relevant, or specify that the PowerShell example is for Windows.
- Include troubleshooting tips for Linux/macOS users (e.g., file path differences, installation instructions for Azure CLI).
Event Grid
Concepts (push delivery) in Event Grid basic
...s/azure-docs/blob/main/articles/event-grid/concepts.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page lists Azure PowerShell samples before mentioning Azure CLI examples when referencing how to create Event Grid subscriptions. This ordering subtly prioritizes Windows tooling, as PowerShell is most commonly associated with Windows environments, while CLI is cross-platform. No Linux/macOS-specific tools or examples are missing, and no Windows-only instructions are present.
Recommendations
- List cross-platform tools (such as Azure CLI) before Windows-centric tools (such as PowerShell) when presenting example links or instructions.
- Explicitly mention that both CLI and PowerShell are available on Windows, Linux, and macOS, to avoid reinforcing platform associations.
- Consider providing example commands for both CLI and PowerShell side-by-side, or clarify their cross-platform availability.
Event Grid
Configure private endpoints for topics or domains
...ain/articles/event-grid/configure-private-endpoints.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides extensive Azure portal and PowerShell instructions, with PowerShell scripts and examples included in detail. While Azure CLI examples are present (which are cross-platform), the portal instructions and screenshots are Windows-centric, and PowerShell is a Windows-first tool. There are no Linux/macOS-specific instructions, nor is Bash scripting or Linux terminal usage mentioned. The PowerShell section is as detailed as the CLI section, and appears after CLI, but the overall guidance assumes familiarity with Windows tools and patterns.
Recommendations
- Add explicit Bash script examples for Linux/macOS users, especially for resource creation and management.
- Clarify that Azure CLI commands work identically on Linux/macOS and Windows, and provide any OS-specific notes if needed.
- Include screenshots or instructions for Azure portal usage on macOS/Linux browsers, if there are any differences.
- Mention cross-platform alternatives to PowerShell, such as Bash or Python, for automation.
- If possible, add a section on using Azure Cloud Shell, which is OS-agnostic.
Event Grid
Quickstart: Send custom events to an Azure function - Event Grid
...b/main/articles/event-grid/custom-event-to-function.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI (Bash/cURL) and Azure PowerShell examples for sending events, but PowerShell is given equal prominence and detail, and the workflow assumes use of Visual Studio Code (a cross-platform tool, but with a .NET/C# focus). The instructions for using Azure CLI are presented before PowerShell, but there is a notable emphasis on PowerShell and Windows-centric workflows (e.g., .NET, C#, Visual Studio Code). There are no Linux-specific examples, troubleshooting, or alternative workflows highlighted, and no mention of Linux/macOS-specific considerations.
Recommendations
- Add explicit Linux/macOS instructions or troubleshooting notes, especially for cURL and Azure CLI usage outside Cloud Shell.
- Include examples using Python or other cross-platform languages for event creation and posting, not just PowerShell and Bash.
- Mention alternative editors (e.g., VS Code, Vim, JetBrains IDEs) and clarify that the workflow is cross-platform.
- Highlight any OS-specific differences in Azure CLI or cURL usage, if applicable.
- Ensure that PowerShell is not presented as the default or primary method, and clarify that Bash/CLI is fully supported on Linux/macOS.
Event Grid
Send custom events to web endpoint
.../articles/event-grid/custom-event-quickstart-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI (Bash) and PowerShell examples for sending events, but the structure and language show a slight Windows bias. PowerShell is given its own dedicated section after CLI, and there are repeated references to Cloud Shell's PowerShell mode. However, Linux/macOS users are supported via Bash/CLI instructions, and curl is used for posting events, which is cross-platform.
Recommendations
- Explicitly mention Linux/macOS compatibility in the Azure CLI section.
- Add a note clarifying that all CLI/curl commands work natively on Linux/macOS terminals, not just in Azure Cloud Shell.
- Consider providing a direct Linux/macOS terminal example (outside Cloud Shell) for sending events, to reinforce parity.
- Ensure that PowerShell is not presented as the default or preferred method, but as an alternative for Windows users.
Event Grid
Azure Blob Storage as Event Grid source
.../main/articles/event-grid/event-schema-blob-storage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page is largely platform-neutral in its technical content, focusing on REST APIs and event schemas. However, in the 'Tutorials and how-tos' section, Windows-oriented tools (PowerShell) are listed alongside Azure CLI, and PowerShell examples are given equal prominence. The order of quickstarts and sample scripts often lists Windows/PowerShell before Linux/Azure CLI equivalents, which may subtly signal a Windows-first approach. No explicit Windows-only tools or missing Linux/macOS examples are present, but the ordering and inclusion of PowerShell may create minor friction for non-Windows users.
Recommendations
- List Azure CLI and PowerShell tutorials in alternating or alphabetical order to avoid implicit prioritization.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Add a note clarifying that all REST API and event schema examples are platform-agnostic.
- Consider adding bash or shell script examples for Linux/macOS users where appropriate.
- Ensure parity in depth and detail between CLI and PowerShell tutorials.
Event Grid
Function as event handler for Azure Event Grid events
...ocs/blob/main/articles/event-grid/handler-functions.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation mentions Azure PowerShell as a primary tool for configuring batch settings, listing it alongside Azure CLI, portal, and ARM templates. PowerShell is a Windows-centric tool, and its mention before Linux-native alternatives (like Bash scripting or CLI) may suggest a Windows-first approach. There are no explicit Linux/macOS examples or references to platform-specific considerations, and PowerShell is presented as a standard option without clarifying cross-platform support.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, or provide explicit Linux/macOS instructions where relevant.
- Include Linux/macOS-specific examples, such as Bash scripts or CLI usage in a Linux shell.
- List Azure CLI before PowerShell, as CLI is natively cross-platform.
- Add notes or links for installing and using Azure CLI and PowerShell on Linux/macOS.
- Ensure screenshots and UI references are not Windows-specific, or provide parity for Linux/macOS users.
Event Grid
Webhooks as event handlers for Azure Event Grid events
...docs/blob/main/articles/event-grid/handler-webhooks.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page lists both Azure CLI and PowerShell quickstarts for core webhook scenarios, but consistently mentions PowerShell (a Windows-centric tool) alongside Azure CLI and before the portal. There are no explicit Linux/macOS examples or references to Bash, shell scripting, or Linux-specific tools. The ordering and inclusion of PowerShell may create a subtle Windows bias, though Azure CLI is cross-platform.
Recommendations
- Explicitly mention that Azure CLI works on Linux/macOS and provide example commands or links for those platforms.
- Include Bash or shell script examples where appropriate, especially for webhook setup and event handling.
- Reorder examples to list Azure CLI (cross-platform) before PowerShell (Windows-centric).
- Add a note clarifying platform compatibility for each tool (e.g., 'Azure CLI: Windows, Linux, macOS; PowerShell: Windows, Linux, macOS (with PowerShell Core)').