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 51-75 of 83 flagged pages
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-11 06:20
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# and reference Windows-centric patterns (e.g., .NET SDK, Windows-style CLI invocation). The Azure Relay Bridge usage example shows a Windows path ('.\azbridge.exe'), and there are no explicit Linux/macOS examples or instructions. The C# sample is given without alternatives in other languages, and the documentation does not mention Linux-specific usage or troubleshooting.
Recommendations
  • Provide equivalent examples for Linux/macOS, such as shell scripts, Python, or Node.js code for the handshake logic.
  • Show how to run Azure Relay Bridge on Linux/macOS, including Docker usage and Linux path conventions (e.g., './azbridge' instead of '.\azbridge.exe').
  • Include explicit instructions or troubleshooting for Linux/macOS environments, such as firewall configuration or service management.
  • Offer parity in SDK references, mentioning cross-platform options (e.g., Java, Python, Node.js) alongside .NET.
  • When showing CLI commands, clarify that Azure CLI is cross-platform and provide any OS-specific notes if needed.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Windows/Powershell examples and tools (psping.exe, tcpping.exe) first and in more detail, while Linux alternatives are mentioned briefly or omitted. Windows-specific tools are referenced and linked, whereas Linux-native equivalents and usage patterns are not covered. This may create friction for Linux/macOS users who lack direct guidance or tool recommendations.
Recommendations
  • Provide Linux/macOS equivalent commands (e.g., using nc, nmap, or curl) alongside Windows examples.
  • List Linux-native tools for network troubleshooting (e.g., netcat, ss, tcpdump) and give usage examples.
  • Present examples for both platforms in parallel, or group them by OS to avoid Windows-first ordering.
  • Link to cross-platform or Linux-specific tools and documentation where appropriate.
  • Clarify tool availability and installation steps for Linux/macOS users.
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-10 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 interaction via the Azure Portal, with only a brief mention of Azure PowerShell, Azure CLI, and REST API as alternative methods. However, it links first to PowerShell-specific instructions for template deployment, and does not provide explicit Linux or cross-platform CLI examples inline. There are no Linux-specific instructions, screenshots, or terminal commands, and the workflow assumes use of browser-based Azure Portal, which is platform-agnostic but often associated with Windows environments.
Recommendations
  • Add explicit Azure CLI examples for template deployment, including Linux/macOS terminal usage.
  • Provide links to both PowerShell and CLI documentation, mentioning CLI first or equally.
  • Include sample commands for uploading files to Blob storage using cross-platform tools (e.g., Azure CLI, curl, azcopy).
  • Add screenshots or terminal output from Linux environments where relevant.
  • Clarify that all steps can be performed from Linux/macOS as well as Windows, and highlight any platform-specific considerations.
GitHub Create Pull Request
Event Grid Concepts (push delivery) in Event Grid basic ...s/azure-docs/blob/main/articles/event-grid/concepts.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias in the section listing examples for creating event subscriptions. Azure PowerShell samples are mentioned explicitly and listed before Linux-friendly alternatives like Azure CLI. There is no explicit Linux example or mention of Linux-specific tools, and PowerShell (primarily a Windows tool, though now cross-platform) is highlighted. The CLI example is present, but PowerShell is listed immediately after, suggesting a Windows-first approach.
Recommendations
  • Ensure that Linux-friendly tools (such as Azure CLI) are listed before or alongside Windows-centric tools like PowerShell.
  • Provide explicit Linux examples or mention Linux compatibility where appropriate.
  • Include Bash or shell script examples for common operations, especially in sections where PowerShell is referenced.
  • Clarify that PowerShell is now cross-platform, but also offer native Linux command alternatives where possible.
  • Review other documentation links (such as template and script samples) to ensure parity between Windows and Linux environments.
GitHub Create Pull Request
Event Grid Subscribe to Azure Resource Notifications - ContainerService events ...ribe-to-resource-notifications-containerservice-events.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides step-by-step instructions and examples for Azure CLI, Azure PowerShell, and Azure Portal. However, the PowerShell examples are given equal prominence to Azure CLI, and in some cases, PowerShell is listed before CLI in the tab order. PowerShell is a Windows-centric tool, and its inclusion as a primary automation method can signal a Windows bias, especially since there are no Bash, Linux shell, or cross-platform scripting examples. There are no explicit references to Windows-only tools, but the lack of Linux-specific guidance or parity in scripting examples is notable.
Recommendations
  • Add Bash or Linux shell script examples alongside Azure CLI to demonstrate usage in a Linux environment.
  • Clarify that Azure CLI is fully cross-platform and can be used on Windows, macOS, and Linux.
  • If PowerShell is included, mention that PowerShell Core is available on Linux and macOS, and provide examples using PowerShell Core where appropriate.
  • Consider including automation examples using other popular Linux-native tools (e.g., curl, jq) for event subscription management.
  • Review tab ordering to ensure CLI (cross-platform) is listed before PowerShell (Windows-centric) to reduce perceived Windows-first bias.
GitHub Create Pull Request
Event Grid Azure Resource Manager template samples - Event Grid | Microsoft Docs ...docs/blob/main/articles/event-grid/template-samples.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page lists PowerShell samples before CLI samples in the 'Next steps' section, suggesting a Windows-first approach. There is an explicit link to PowerShell examples, which are typically Windows-centric, and no mention of Bash or Linux-specific instructions. The CLI samples are referenced, but not highlighted equally or first.
Recommendations
  • Present CLI (az CLI) samples before or alongside PowerShell samples, as CLI is cross-platform.
  • Add explicit Bash or Linux/macOS instructions or examples where relevant.
  • Clarify that CLI samples work on all platforms, and PowerShell samples are primarily for Windows.
  • Consider renaming 'PowerShell samples' to 'Windows PowerShell samples' for clarity.
GitHub Create Pull Request
Event Grid Send Blob storage events to web endpoint - Bicep ...ain/articles/event-grid/blob-event-quickstart-bicep.md
Low 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 provides deployment instructions for both Azure CLI and Azure PowerShell, but PowerShell examples are shown alongside CLI without explicit mention of Linux/macOS alternatives. The PowerShell example may imply a Windows environment, and there is no explicit mention of Linux/macOS compatibility or terminal usage. The order of examples (CLI first, then PowerShell) is good, but the presence of PowerShell may create minor friction for non-Windows users.
Recommendations
  • Explicitly state that Azure CLI works on Windows, Linux, and macOS, and recommend it for cross-platform usage.
  • Clarify that PowerShell Core is available on Linux/macOS, or link to instructions for installing PowerShell on those platforms.
  • Add a note or section highlighting Linux/macOS compatibility and any platform-specific considerations.
  • Consider including screenshots or terminal examples from Linux/macOS environments to reinforce parity.
GitHub Create Pull Request
Event Grid Concepts (push delivery) in Event Grid basic ...s/azure-docs/blob/main/articles/event-grid/concepts.md
Low 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 Azure PowerShell samples before Linux-friendly options and highlights PowerShell as a primary example. While Azure CLI is mentioned, PowerShell is referenced earlier and more prominently, which may subtly prioritize Windows tooling. No explicit Windows-only instructions or tools are present, and Linux/macOS users can complete all described tasks, but the ordering and emphasis may create minor friction.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform.
  • Explicitly mention that both Azure CLI and PowerShell are supported on Windows, Linux, and macOS.
  • Add Bash or shell script examples where relevant.
  • Ensure that documentation does not imply PowerShell is the default or preferred method unless justified.
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
Low 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 provides both Azure CLI and Azure PowerShell examples for configuring IP firewall rules for Event Grid topics/domains. However, the PowerShell section is given equal prominence to the CLI section, and PowerShell is a Windows-centric tool. There are no Linux/macOS-specific shell examples (e.g., Bash), nor is there mention of platform differences or guidance for Linux/macOS users. The ordering of sections (CLI before PowerShell) is neutral, but the inclusion of PowerShell as a primary automation method reflects a mild Windows bias.
Recommendations
  • Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Add explicit Bash shell examples or notes for Linux/macOS users, such as environment variable setup.
  • Mention that PowerShell Core is available on Linux/macOS, if relevant, and provide installation guidance.
  • Consider adding a short section or note about platform compatibility for each tool.
  • Ensure screenshots and UI instructions do not assume Windows-only environments.
GitHub Create Pull Request
Event Grid Send custom events to web endpoint .../articles/event-grid/custom-event-quickstart-portal.md
Low 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 provides both Azure CLI (Bash) and PowerShell examples for sending events, but PowerShell is given equal prominence and detail. The instructions for using Azure CLI explicitly mention switching from PowerShell to Bash, suggesting a default Windows/PowerShell environment. No Linux/macOS-specific tools or patterns are mentioned, and the overall flow assumes users are comfortable with the Azure portal and Cloud Shell, which are cross-platform but often Windows-centric in documentation tone.
Recommendations
  • Explicitly mention that all CLI steps work on Linux/macOS terminals outside Azure Cloud Shell.
  • Provide a standalone curl example for users who do not use Azure CLI or PowerShell, especially for Linux/macOS users.
  • Add a note clarifying that PowerShell is available on Linux/macOS, but Bash/CLI examples are generally more common for those platforms.
  • Consider listing Bash/CLI examples before PowerShell to reduce Windows-first impression.
  • Reference Linux/macOS terminal usage where appropriate, e.g., 'You can run these commands in your local Linux/macOS terminal as well as in Cloud Shell.'
GitHub Create Pull Request
Event Grid Custom topics in Azure Event Grid ...re-docs/blob/main/articles/event-grid/custom-topics.md
Low 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 lists Azure PowerShell tutorials as a primary method for interacting with Event Grid custom topics, alongside Azure CLI and portal options. PowerShell is a Windows-centric tool, and its inclusion as a major section may signal a Windows bias. However, Azure CLI is also covered, which is cross-platform. The order of sections places PowerShell before ARM templates, but after CLI, which slightly prioritizes Windows tooling but does not exclude Linux/macOS users. No examples are shown directly in the page, but the presence of PowerShell-specific tutorials could be seen as a mild bias.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • If PowerShell examples are provided, consider also providing Bash or shell script equivalents for Linux/macOS users.
  • Clarify that Azure PowerShell is available on Linux/macOS via PowerShell Core, or link to installation instructions for non-Windows platforms.
  • Ensure that all referenced scripts and tutorials include notes about platform compatibility.
GitHub Create Pull Request
Event Grid Function as event handler for Azure Event Grid events ...ocs/blob/main/articles/event-grid/handler-functions.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates mild Windows bias by explicitly listing Azure PowerShell as a method for configuring batch settings, with PowerShell examples and links provided. While Azure CLI and Resource Manager template options are also mentioned (which are cross-platform), the inclusion of PowerShell and its placement after CLI may subtly prioritize Windows tooling. No Linux/macOS-specific issues or missing examples are present, but the documentation could better emphasize cross-platform parity.
Recommendations
  • Clarify that Azure CLI and Resource Manager templates are fully cross-platform and can be used on Linux/macOS.
  • Add explicit notes or examples showing how to use Azure CLI on Linux/macOS.
  • Consider listing CLI before PowerShell to avoid implicit prioritization of Windows tools.
  • If possible, provide bash script examples or highlight usage on non-Windows platforms.
GitHub Create Pull Request
Event Grid Azure subscription as Event Grid source ...main/articles/event-grid/event-schema-subscriptions.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides schema and conceptual information about Azure Event Grid subscription events, with no explicit platform-specific commands or examples in the main content. However, in the 'Tutorials and how-tos' section, PowerShell is listed as a primary automation method, and is mentioned before Linux-friendly alternatives (Azure CLI). There is no explicit mention of Linux shell scripting, Bash, or cross-platform automation tools, and PowerShell is traditionally associated with Windows environments.
Recommendations
  • Add explicit Bash or shell scripting examples for subscribing to events, alongside PowerShell and Azure CLI.
  • Ensure that Azure CLI examples are presented before or alongside PowerShell to emphasize cross-platform support.
  • Clarify in the documentation that PowerShell Core is available cross-platform, or provide links to Linux/macOS setup guides.
  • Include a note or section on how Linux/macOS users can perform equivalent tasks, especially in automation scenarios.
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
Low 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 provides both Azure CLI and PowerShell examples for all major operations, but consistently lists PowerShell (a Windows-centric tool) as the only alternative to Azure CLI. No Linux/macOS-specific shell examples (e.g., Bash/curl) are provided, and PowerShell examples are shown alongside CLI in every section, potentially implying parity or preference for Windows tooling. However, Azure CLI is cross-platform and shown first in each case.
Recommendations
  • Add explicit Bash/curl examples for publishing events (HTTP POST) to the Event Grid domain endpoint, as this is a common Linux/macOS workflow.
  • Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider including notes or examples for using native Linux/macOS tools (e.g., curl, wget) for tasks like publishing events.
  • If PowerShell is mentioned, note that PowerShell Core is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
GitHub Create Pull Request
Event Grid Map custom field to Azure Event Grid schema ...e-docs/blob/main/articles/event-grid/input-mappings.md
Low 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 provides both Azure CLI and PowerShell examples for all major operations. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as variable assignment), the PowerShell syntax is shown directly after CLI, which may suggest a Windows-centric approach. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is primarily a Windows tool, though it is now cross-platform. The CLI examples are generic and suitable for Linux/macOS, but the presence and parity of PowerShell throughout the doc indicate a mild Windows bias.
Recommendations
  • Add explicit Bash examples for Linux/macOS users, especially for variable assignment and scripting.
  • Clarify that Azure CLI examples are cross-platform and suitable for Linux/macOS.
  • Consider reordering examples to show Azure CLI (Linux/macOS-friendly) before PowerShell, or group them by platform.
  • Note that PowerShell is available cross-platform, but most Linux users will prefer Bash/CLI.
GitHub Create Pull Request
Event Grid Dead letter and retry policies - Azure Event Grid ...blob/main/articles/event-grid/manage-event-delivery.md
Low 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 dead-letter and retry policies in Azure Event Grid. However, PowerShell is a Windows-centric tool and is presented alongside Azure CLI in all code sections. There are explicit instructions for installing Azure PowerShell, but no mention of Bash, shell scripting, or Linux/macOS-specific guidance. The related sample application is .NET-focused, which is more common on Windows. While Azure CLI is cross-platform, the presence and prominence of PowerShell examples and installation notes create a mild Windows bias.
Recommendations
  • Clarify that Azure CLI works on Linux/macOS and provide installation links for those platforms.
  • Add Bash or shell scripting examples where appropriate, especially for scripting scenarios.
  • Mention that PowerShell Core is available cross-platform, or de-emphasize PowerShell in favor of CLI for Linux/macOS users.
  • Include sample applications or links for languages and frameworks popular on Linux/macOS (e.g., Python, Node.js).
  • Reorder examples to show Azure CLI first, emphasizing its cross-platform nature.
GitHub Create Pull Request
Event Grid Publish and subscribe on an MQTT topic using portal ...ticles/event-grid/mqtt-publish-and-subscribe-portal.md
Low 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 exhibits mild Windows bias in the certificate generation section, where instructions and command examples are presented using Windows-centric terminology (e.g., opening a command prompt with Win+R and using %USERPROFILE%), and all command examples are shown in PowerShell syntax. There are no explicit Linux/macOS instructions or examples for certificate generation, and no mention of Linux/macOS-specific considerations for file paths or terminal usage. However, the rest of the guide (Azure Portal usage, MQTTX app) is cross-platform and does not favor Windows.
Recommendations
  • Add explicit Linux/macOS instructions for installing and using the step CLI, including terminal commands and file path conventions.
  • Provide bash/zsh command examples alongside PowerShell, or use platform-agnostic syntax where possible.
  • Clarify that the step CLI and MQTTX app are cross-platform, and link to installation guides for all major OSes.
  • Avoid Windows-specific terminology (e.g., Win+R, %USERPROFILE%) or provide equivalent instructions for other platforms.
GitHub Create Pull Request
Event Grid Publish Events to Azure Event Grid Custom Topics .../blob/main/articles/event-grid/post-to-custom-topic.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all key steps, but PowerShell (a Windows-centric tool) is consistently presented alongside CLI, and sometimes with more detailed explanations. There is a slight 'windows_first' bias in the ordering and prominence of PowerShell examples, and the use of PowerShell-specific constructs. However, Azure CLI and Bash examples are present, and Linux users can complete all tasks without significant friction.
Recommendations
  • Ensure Azure CLI/Bash examples are presented before PowerShell examples, or at least with equal prominence.
  • Add explicit notes clarifying that Azure CLI and curl commands work natively on Linux/macOS.
  • Where PowerShell is used, provide equivalent Bash/CLI scripts for all steps, including constructing JSON payloads.
  • Avoid language that implies PowerShell is the default or preferred method.
  • Include troubleshooting tips for Linux/macOS users (e.g., curl usage, date formatting differences).
GitHub Create Pull Request
Event Grid Subscribe to Microsoft Graph Events Using Azure Event Grid ...n/articles/event-grid/subscribe-to-graph-api-events.md
Low Priority View Details →
Scanned: 2026-01-12 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. PowerShell is included as a primary example language, and the Azure CLI is referenced with commands that are most commonly used on Windows. The instructions for obtaining Azure region names use the Azure CLI, which is available cross-platform but is often associated with Windows environments. There is no explicit mention of Linux/macOS equivalents or considerations, and Windows-centric tools (PowerShell, Azure CLI) are listed among the main code samples. However, the page does provide examples in multiple languages (C#, Java, JavaScript, Go, PHP, Python, CLI), which are cross-platform, and does not restrict critical functionality to Windows-only tools.
Recommendations
  • Explicitly mention that Azure CLI and PowerShell are available on Linux/macOS and provide installation links for those platforms.
  • Add Bash or shell script examples for Linux/macOS users, especially for commands like 'az account list-locations'.
  • Clarify that all SDKs and code samples are cross-platform and provide setup instructions for Linux/macOS environments.
  • Include troubleshooting notes or links for common Linux/macOS issues (e.g., authentication, environment setup).
  • Ensure that sample code repositories referenced include Linux/macOS setup instructions.
GitHub Create Pull Request
Event Grid Custom topics in Azure Event Grid ...re-docs/blob/main/articles/event-grid/custom-topics.md
Low 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 provides parallel tutorials for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. However, the CLI section is present and not deprioritized. The ordering of sections places PowerShell immediately after CLI, and both are given equal prominence. There are no explicit Windows-only tools or examples, and Linux users can use Azure CLI and ARM templates without issue. No examples are shown directly in the page, so ordering bias is minor.
Recommendations
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit notes or links for Linux/macOS users to ensure parity and highlight platform compatibility.
  • Consider listing CLI before PowerShell and explicitly mention that PowerShell Core is available cross-platform, but Azure CLI is more common on Linux/macOS.
  • If examples are shown in future, ensure Linux shell (bash) examples are included alongside PowerShell.
GitHub Create Pull Request
Event Grid Function as event handler for Azure Event Grid events ...ocs/blob/main/articles/event-grid/handler-functions.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates mild Windows bias by listing Azure PowerShell as a primary tool for configuring batch settings, with PowerShell examples and links provided. Although Azure CLI and Resource Manager template options are also mentioned, PowerShell (a Windows-centric tool) is given equal prominence, and no Linux/macOS-specific guidance or examples are provided. There are no explicit Linux/macOS examples, nor is there mention of platform-specific considerations for these operating systems.
Recommendations
  • Add explicit Linux/macOS examples, especially for Azure CLI usage, as CLI is cross-platform.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and provide installation/use links for non-Windows platforms.
  • If PowerShell is mentioned, note that PowerShell Core is available cross-platform, or provide CLI alternatives first.
  • Consider listing Azure CLI before PowerShell to emphasize cross-platform parity.
  • Add troubleshooting notes or links for common Linux/macOS issues (e.g., authentication, environment setup).
GitHub Create Pull Request
Event Grid Azure Resource Manager template samples - Event Grid | Microsoft Docs ...docs/blob/main/articles/event-grid/template-samples.md
Low 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 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/macOS-specific instructions or parity, and PowerShell is traditionally associated with Windows environments.
Recommendations
  • List CLI (az CLI) samples before PowerShell samples to signal cross-platform support.
  • Explicitly mention that CLI samples work on Linux/macOS.
  • Add Bash or shell script examples where appropriate.
  • Clarify PowerShell Core compatibility for non-Windows users if PowerShell is required.
GitHub Create Pull Request
Event Grid Send Blob storage events to web endpoint - Bicep ...ain/articles/event-grid/blob-event-quickstart-bicep.md
Low 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 presents both Azure CLI and Azure PowerShell examples for deploying the Bicep file, but PowerShell is shown as an equal alternative rather than a secondary option. The CLI example is cross-platform, but PowerShell is a Windows-centric tool. No Linux/macOS-specific tools or patterns are mentioned, and there is no explicit guidance for Linux/macOS users. The order of examples (CLI first, PowerShell second) is neutral, but the presence of PowerShell as a primary method may suggest a slight Windows bias.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add a note clarifying that Azure PowerShell is primarily for Windows, and provide installation guidance for Linux/macOS if relevant.
  • Consider providing bash or shell script examples for common operations (e.g., file upload to Blob storage) to improve Linux parity.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI.
GitHub Create Pull Request
Event Grid Concepts (push delivery) in Event Grid basic ...s/azure-docs/blob/main/articles/event-grid/concepts.md
Low 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 page lists Azure CLI, PowerShell, and ARM template examples for creating Event Grid subscriptions, but PowerShell is mentioned before Linux-friendly tools (CLI and ARM templates). The explicit mention of 'Azure PowerShell samples' and the ordering of examples (CLI, then PowerShell, then ARM templates) may suggest a slight Windows-first bias. However, Linux-compatible options (CLI, ARM templates) are present and referenced. No exclusive use of Windows tools or missing Linux examples is detected.
Recommendations
  • Ensure that Linux/macOS-friendly tools (Azure CLI, REST API, ARM templates) are always mentioned before or alongside PowerShell.
  • Add explicit notes clarifying cross-platform compatibility for each example.
  • Provide sample commands for both Azure CLI and PowerShell in parallel, especially in quickstart or how-to sections.
  • Consider including Bash or shell script examples where relevant.
GitHub Create Pull Request
Event Grid Configure private endpoints for topics or domains ...ain/articles/event-grid/configure-private-endpoints.md
Low 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 provides detailed instructions for configuring private endpoints for Azure Event Grid topics or domains using the Azure portal, Azure CLI, and PowerShell. The PowerShell section is extensive and included alongside Azure CLI, but there are no Linux/macOS-specific shell examples (e.g., Bash), nor is there any mention of Linux-native tools. The ordering of examples places PowerShell after CLI, but the CLI examples use generic syntax compatible with Linux/macOS and Windows. There is a slight Windows bias due to the inclusion of PowerShell and the absence of explicit Linux/macOS shell examples, but the CLI coverage mitigates this.
Recommendations
  • Add explicit Bash shell script examples for Linux/macOS users, especially for multi-step resource creation and endpoint management.
  • Clarify that Azure CLI commands work cross-platform and provide any OS-specific notes if needed.
  • Consider including a section or note for macOS/Linux users, highlighting any differences in experience (e.g., Azure CLI installation, authentication).
  • If PowerShell is included, mention that PowerShell Core is available on Linux/macOS, or provide Bash alternatives.
GitHub Create Pull Request
← Previous Page 3 of 4 Next →