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 201-225 of 289 flagged pages
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/how-to-event-domains.md .../blob/main/articles/event-grid/how-to-event-domains.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 presents PowerShell (a Windows-centric tool) as an equal alternative to Azure CLI, rather than as a secondary or platform-specific option. There are no Linux-specific shell examples (e.g., Bash/curl for HTTP POST), and PowerShell is presented without noting its Windows bias or suggesting cross-platform alternatives. No explicit Linux tools or patterns are mentioned, and PowerShell is given parity with CLI throughout.
Recommendations
  • Add explicit Bash/curl examples for publishing events via HTTP POST, demonstrating Linux-native workflows.
  • Clarify that PowerShell is primarily a Windows tool, and suggest cross-platform alternatives where appropriate.
  • Present Azure CLI examples first, as it is cross-platform, and move PowerShell examples to a secondary position or an 'Alternative: PowerShell' section.
  • Include notes or links to Linux-specific guidance for users who may not use PowerShell.
  • Where SDK samples are referenced, consider adding command-line or scripting examples for Linux users (e.g., Bash, curl, Python scripts).
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/handler-service-bus.md ...s/blob/main/articles/event-grid/handler-service-bus.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring Service Bus queues and topics as Event Grid event handlers. However, PowerShell is a Windows-centric tool and is presented with equal prominence as the CLI, despite CLI being cross-platform. There are no Linux-specific shell examples (such as Bash), nor is there any mention of Linux tools or patterns. The ordering of examples (CLI before PowerShell) is appropriate, but the inclusion of PowerShell as a primary method may signal Windows bias, especially since many enterprise users on Linux would not use PowerShell.
Recommendations
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit Bash shell examples where possible, especially for scripting use cases.
  • Consider including a note that PowerShell is primarily used on Windows, and direct Linux/macOS users to CLI examples.
  • If PowerShell is retained, provide parity by mentioning cross-platform PowerShell Core, or link to installation instructions for Linux/macOS.
  • Review other sections for Windows-specific terminology or assumptions and add Linux/macOS equivalents if missing.
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/monitor-namespaces.md ...cs/blob/main/articles/event-grid/monitor-namespaces.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page does not provide explicit examples or instructions using Windows-specific tools (such as PowerShell), nor does it mention Windows-only patterns. However, there is a subtle bias in that CLI and PowerShell are referenced together for creating diagnostic settings, but no concrete examples are given for either. The majority of instructions and screenshots focus on using the Azure Portal GUI, which is platform-agnostic. There are no Linux-specific examples, nor is there mention of Linux command-line tools (such as Bash or Azure CLI usage on Linux). The order of mention (portal, CLI, PowerShell) places Windows tools before Linux equivalents, and there is an absence of parity in example commands for Linux users.
Recommendations
  • Add explicit Azure CLI examples for all major operations (e.g., creating diagnostic settings, analyzing metrics/logs), and clarify that these can be run on Linux, macOS, and Windows.
  • Include sample Bash scripts for common monitoring tasks to demonstrate Linux usage.
  • When referencing command-line tools, list Azure CLI before PowerShell to avoid implicit Windows-first ordering.
  • Add a section or callout highlighting cross-platform compatibility and best practices for Linux users.
  • Provide links to Linux-specific quickstarts or tutorials where available.
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/subscribe-to-resource-notifications-containerservice-events.md ...ribe-to-resource-notifications-containerservice-events.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and Azure Portal. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows and is presented equally alongside CLI, with no mention of Linux-specific shell patterns (e.g., Bash, scripting, environment variables). There are no Linux-specific examples, nor are Linux shell idioms (such as piping, jq, or bash scripting) demonstrated. The ordering of examples does not always prioritize CLI (which is more universal) over PowerShell (which is Windows-centric), and PowerShell is given parity in all sections.
Recommendations
  • Add explicit Linux/Bash shell examples, including usage with environment variables, piping, and tools like jq for output parsing.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide sample shell scripts for Linux users.
  • Consider reordering examples to present Azure CLI first, emphasizing its cross-platform nature.
  • If PowerShell is included, note that it is available on Linux but less commonly used, and provide guidance for Linux users who may prefer Bash.
  • Include troubleshooting notes for common Linux issues (e.g., quoting, path formats) when using Azure CLI.
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/subscribe-to-resource-notifications-health-resources-events.md ...ribe-to-resource-notifications-health-resources-events.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and Azure Portal, but the PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. There are no Linux-specific shell examples (e.g., Bash, curl, or scripting patterns), nor is there mention of Linux-native tools. The CLI examples are cross-platform, but the presence and parity of PowerShell throughout the documentation may signal a Windows bias, especially for users seeking Linux-first guidance.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and recommend Bash or shell scripting for Linux users.
  • Add Bash script examples or usage patterns (e.g., with environment variables, piping, jq for JSON parsing) to demonstrate Linux-native workflows.
  • Clarify that PowerShell examples are primarily for Windows users, and suggest alternatives for Linux users where appropriate.
  • Consider including curl or REST API examples for advanced users who may not use Azure CLI or PowerShell.
  • Review screenshots and UI instructions for platform neutrality, ensuring that portal steps do not assume Windows conventions.
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/concepts.md ...s/azure-docs/blob/main/articles/event-grid/concepts.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by listing Azure PowerShell samples before Linux-friendly options and referencing PowerShell specifically. While Azure CLI and ARM templates are mentioned, PowerShell is given prominence, and there are no explicit Linux shell (bash) or platform-neutral examples. No Windows-specific tools or patterns are exclusively mentioned, but the ordering and emphasis favor Windows users.
Recommendations
  • Ensure Azure CLI examples are listed before or alongside PowerShell samples, as CLI is cross-platform.
  • Add explicit bash or Linux shell examples where relevant, especially in sections discussing event subscription creation.
  • Clarify that all CLI and ARM template examples work on Linux, macOS, and Windows.
  • Avoid listing Windows-centric tools (PowerShell) before platform-neutral alternatives unless contextually justified.
  • Consider including links to Linux-specific guidance or troubleshooting for Event Grid operations.
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/blob-event-quickstart-bicep.md ...ain/articles/event-grid/blob-event-quickstart-bicep.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 deploying the Bicep file, but lists PowerShell as a primary option alongside CLI, which is more commonly used on Windows. There are no explicit Linux-specific instructions, nor is there mention of Linux shell patterns or tools. The examples do not show Linux terminal screenshots or reference Linux environments, and PowerShell is presented as an equal alternative to CLI, which may imply a Windows-centric approach.
Recommendations
  • Explicitly mention that Azure CLI works natively on Linux and macOS, and is the recommended cross-platform tool.
  • List Azure CLI instructions before PowerShell, or clarify that CLI is platform-agnostic.
  • Include a note or section for Linux/macOS users, confirming that all steps work on those platforms.
  • Add screenshots or terminal examples from Linux environments to balance representation.
  • Avoid implying parity between PowerShell and CLI for cross-platform scenarios, unless PowerShell Core is specifically referenced.
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/configure-private-endpoints.md ...ain/articles/event-grid/configure-private-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 using the Azure portal, Azure CLI, and PowerShell. The PowerShell section is extensive and uses Windows-centric tooling, while no equivalent Bash or Linux shell scripting examples are provided. The ordering of sections places PowerShell after CLI, but the CLI examples are generic and do not include Linux-specific notes or troubleshooting. There is no mention of Linux-specific tools, nor are there any Bash scripts or references to Linux environments. The portal instructions are platform-neutral, but the scripting guidance leans toward Windows/PowerShell usage.
Recommendations
  • Add Bash shell script examples for all CLI workflows, demonstrating usage in a Linux environment.
  • Include notes about running Azure CLI commands on Linux, such as installation steps, authentication, and environment variables.
  • Provide troubleshooting tips for common Linux-specific issues (e.g., permissions, networking).
  • Mention cross-platform compatibility for CLI commands and clarify any differences in behavior between Windows and Linux.
  • Consider adding a section for automating these tasks with Linux-native tools (e.g., cloud-init, Ansible, Terraform) if relevant.
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/custom-event-to-function.md ...b/main/articles/event-grid/custom-event-to-function.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI (Bash/cURL) and Azure PowerShell examples for sending events to Event Grid, but PowerShell is given equal prominence and is introduced immediately after the CLI example. The use of Visual Studio Code and Azure Cloud Shell is cross-platform, but the explicit PowerShell example and references to switching between Bash and PowerShell in Cloud Shell may reinforce Windows-centric workflows. There are no Linux-specific command-line examples (e.g., using native Linux tools beyond cURL), nor is there mention of Linux-specific patterns or troubleshooting. The documentation avoids exclusive use of Windows tools, but the parity for Linux users could be improved.
Recommendations
  • Provide Linux-specific command-line examples, such as using native shell scripting or alternative tools (e.g., wget, httpie) alongside cURL.
  • Clarify that Azure CLI and cURL examples work natively on Linux and macOS, and explicitly mention cross-platform compatibility.
  • Consider adding a section or note for Linux users, highlighting any differences or tips for using Azure Cloud Shell and Visual Studio Code on Linux.
  • If PowerShell is included, explain its availability on Linux and macOS, or provide equivalent Bash scripts for all PowerShell examples.
  • Avoid presenting PowerShell immediately after CLI as an equal alternative; instead, prioritize CLI/Bash examples for broader cross-platform relevance.
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure Portal for deployment and mentioning Azure PowerShell as an alternative before Azure CLI, without providing explicit Linux or cross-platform command-line examples. There are no Linux-specific instructions, nor are there examples using Bash or CLI commands, which are common on Linux and macOS platforms.
Recommendations
  • Add explicit Azure CLI examples for template deployment, including Bash commands suitable for Linux/macOS users.
  • Provide instructions for deploying the ARM template using cross-platform tools (e.g., Azure CLI, REST API) with step-by-step examples.
  • Ensure that references to deployment methods do not prioritize Windows tools (e.g., PowerShell) over cross-platform alternatives.
  • Include screenshots or terminal output from Linux environments to illustrate parity.
  • Mention that the Azure Portal and Azure CLI are both available on all major platforms, and clarify any platform-specific prerequisites if needed.
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/custom-topics.md ...re-docs/blob/main/articles/event-grid/custom-topics.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides parallel tutorials for Azure portal, Azure CLI, Azure PowerShell, and ARM templates. However, the PowerShell section is given equal prominence to the CLI section, despite PowerShell being primarily a Windows-centric tool (even though it is cross-platform now, it is still most commonly associated with Windows). There are no explicit Linux-specific examples or mentions of Linux-native tools (such as Bash scripts or references to Linux environments). The CLI section is generic and does not clarify usage on Linux, nor does it provide Bash or shell script examples. The ordering of sections (CLI before PowerShell) is neutral, but the inclusion of PowerShell as a primary automation method may reinforce a Windows bias.
Recommendations
  • Add explicit Bash or shell script examples for Linux users, especially in the CLI section.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide instructions for installing and using Azure CLI on Linux.
  • Consider adding a section or note about using REST API calls with curl or other Linux-native tools.
  • If PowerShell is included, clarify its cross-platform availability and provide examples for both Windows PowerShell and PowerShell Core on Linux.
  • Ensure that Linux users are aware of equivalent workflows and tools, and provide parity in examples and instructions.
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/configure-firewall.md ...cs/blob/main/articles/event-grid/configure-firewall.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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, but the PowerShell section is given equal prominence and detail as the CLI section. There is no explicit mention of Linux-specific tools or shell environments, and PowerShell (a Windows-centric tool) is featured as a primary method. The ordering of sections places Azure CLI before PowerShell, which is positive, but the inclusion of PowerShell examples without any Linux shell-specific notes or alternatives may suggest a mild Windows bias.
Recommendations
  • Explicitly mention that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
  • Add example shell commands for Linux/macOS environments (e.g., bash, zsh), especially for variable assignment and command chaining.
  • Clarify that PowerShell examples are primarily for Windows users, and suggest using Azure CLI for Linux/macOS.
  • Consider adding a note or section on using Azure CLI in WSL (Windows Subsystem for Linux) or native Linux environments.
  • Ensure screenshots and instructions in the Azure portal section do not assume a Windows environment (e.g., avoid references to Windows-specific UI elements or terminology).
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/custom-event-quickstart-portal.md .../articles/event-grid/custom-event-quickstart-portal.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 to Azure Event Grid, but PowerShell is given equal prominence and is described in detail. The instructions for using Cloud Shell mention PowerShell first, and the clean-up instructions reference resource groups created by Cloud Shell (which defaults to PowerShell on Windows). There is no mention of Linux-specific tools or patterns, and the examples do not address Linux shell environments outside of Azure CLI/Bash. The tutorial assumes use of the Azure Portal, which is platform-agnostic, but scripting examples lean toward Windows/PowerShell usage.
Recommendations
  • Add explicit Linux shell examples outside of Azure CLI, such as native Bash scripts for local environments.
  • Clarify that Azure CLI and Bash examples work natively on Linux and macOS, not just in Cloud Shell.
  • Provide instructions for using curl and jq directly from a Linux terminal, not only via Azure Cloud Shell.
  • Mention that PowerShell Core is available cross-platform, but highlight Bash as the default for Linux users.
  • Ensure that Linux tools and patterns are mentioned before or alongside Windows/PowerShell equivalents.
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation presents Azure portal, PowerShell, and CLI methods for retrieving Event Grid access keys. PowerShell (typically associated with Windows environments) is featured prominently and before the CLI section, which is more cross-platform. There are no explicit Linux-specific examples, nor are Linux shell patterns (e.g., Bash scripting) mentioned. The CLI examples are generic and do not highlight Linux usage or shell integration.
Recommendations
  • Add explicit Bash/Linux shell examples, such as using az commands in shell scripts or with jq for parsing output.
  • Mention that Azure CLI is cross-platform and provide usage notes for Linux/macOS environments.
  • Consider reordering sections to present CLI before PowerShell, emphasizing cross-platform accessibility.
  • Include notes or examples for Linux users, such as installing Azure CLI on Linux and running commands in Bash.
  • If PowerShell is included, clarify that PowerShell Core is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/handler-service-bus.md ...s/blob/main/articles/event-grid/handler-service-bus.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 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 is presented immediately after CLI in each section. There are no explicit Linux shell (bash) examples, nor any mention of Linux-specific tools or considerations. The REST API examples are platform-neutral, but the scripting guidance leans toward Windows environments by including PowerShell throughout.
Recommendations
  • Add explicit bash examples for each CLI scenario, showing usage in a Linux shell environment.
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide sample commands using bash syntax (with environment variable substitution, etc.).
  • Consider reordering examples to present Azure CLI (cross-platform) before PowerShell, or provide a note on platform compatibility.
  • Mention that PowerShell Core is available on Linux/macOS, if PowerShell examples are retained, to reduce perceived Windows bias.
  • Where possible, include troubleshooting or environment setup notes for Linux users (e.g., installing Azure CLI on Ubuntu).
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/how-to-event-domains.md .../blob/main/articles/event-grid/how-to-event-domains.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 operations, but PowerShell is featured as a first-class option throughout, which is primarily a Windows tool. There is no mention of Linux-specific tools, shell patterns, or alternative scripting environments (e.g., Bash, curl, or REST via command line). The CLI examples are cross-platform, but the presence and parity of PowerShell examples may signal a Windows-centric approach. No explicit Linux bias or missing Linux examples are present, but the documentation does not acknowledge Linux-specific workflows or tools.
Recommendations
  • Add explicit Bash/curl/REST API examples for publishing events and managing resources, to demonstrate Linux-native workflows.
  • Include notes clarifying that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Consider adding example scripts for Linux automation (e.g., using Bash, jq, curl) alongside PowerShell.
  • Mention that PowerShell Core is available cross-platform, but clarify that many Linux users may prefer Bash or other native tools.
  • Ensure that any references to scripting or automation do not assume a Windows environment.
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/subscribe-to-resource-notifications-containerservice-events.md ...ribe-to-resource-notifications-containerservice-events.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all operations, as well as Azure portal instructions. However, the PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. There are no Linux-specific shell examples (e.g., Bash scripts, environment variable usage, or platform caveats). The CLI examples are generic and do not address Linux-specific usage patterns, and PowerShell is presented as a first-class option, which may imply a Windows bias. No explicit Windows-only tools are mentioned, but the lack of Linux/Bash-specific guidance is notable.
Recommendations
  • Add explicit notes clarifying that Azure CLI works cross-platform and provide examples of running CLI commands in Bash (with environment variables, quoting, and line continuation suited for Linux).
  • Mention that PowerShell Core is available on Linux/macOS, or clarify if examples require Windows PowerShell.
  • Include troubleshooting or usage notes for Linux users (e.g., differences in shell quoting, authentication, or file paths).
  • Consider adding Bash script snippets for common workflows to improve Linux parity.
  • Where PowerShell is mentioned, clarify platform compatibility and provide links to PowerShell Core installation for Linux/macOS.
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 →
Scanned: 2026-01-08 00:53
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 a specific mention of PowerShell, a Windows-centric tool, with no explicit mention of Bash or Linux shell examples. This ordering and emphasis may indicate a bias toward Windows users and tools.
Recommendations
  • List CLI (az CLI) samples before PowerShell samples to avoid implicit prioritization of Windows tools.
  • Explicitly mention Bash or Linux shell examples and provide links to those samples.
  • Include a note clarifying that all templates and deployment methods are cross-platform, and provide guidance for Linux/macOS users.
  • Ensure parity in documentation by offering equivalent examples for both PowerShell and CLI/Bash where possible.
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/subscribe-to-resource-notifications-health-resources-events.md ...ribe-to-resource-notifications-health-resources-events.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and Azure Portal, but the command-line examples are limited to Azure CLI and PowerShell. PowerShell is a Windows-centric tool, and its inclusion alongside CLI in every example (with no Bash, shell script, or Linux-specific guidance) demonstrates a bias toward Windows users. Additionally, PowerShell examples are always present and sometimes listed before CLI, reinforcing a Windows-first approach. There are no Linux-specific instructions, troubleshooting notes, or alternative shell examples.
Recommendations
  • Add Bash or shell script examples for Linux users where appropriate, especially for scripting scenarios.
  • Clarify that Azure CLI is cross-platform and provide explicit instructions for installing and using it on Linux and macOS.
  • Where PowerShell is referenced, note that PowerShell Core is available cross-platform, and provide guidance for Linux/macOS installation and usage.
  • Include troubleshooting notes or tips for common Linux-specific issues (e.g., permissions, environment variables, path differences).
  • Ensure that CLI examples are listed before PowerShell to avoid implicit Windows-first ordering.
  • Consider referencing automation tools popular on Linux (e.g., cron jobs, systemd) for event handling, where relevant.
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
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 also a specific callout to PowerShell, which is traditionally associated with Windows, without equal prominence given to Linux-native tools or Bash examples.
Recommendations
  • List CLI (az CLI) or Bash samples before or alongside PowerShell samples to avoid implying Windows is the primary platform.
  • Explicitly mention that CLI samples are cross-platform and suitable for Linux, macOS, and Windows.
  • Add Bash or shell script examples where appropriate, or link to them if available.
  • Include a note clarifying that all templates can be deployed from any OS using the Azure CLI, not just PowerShell.
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily describes deploying ARM templates and interacting with Azure services through the Azure Portal, with a brief mention of Azure PowerShell, Azure CLI, and REST API as alternative deployment methods. However, the only explicit link for further deployment instructions points to a PowerShell-specific page, and there are no direct Linux or cross-platform CLI examples provided. This may lead Linux users to feel secondary or unsupported.
Recommendations
  • Provide explicit Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Link to both Azure CLI and PowerShell deployment documentation in the 'Deploy the template' section, not just the PowerShell page.
  • Include a short example of deploying the ARM template using Azure CLI (e.g., az deployment group create ...) directly in the quickstart.
  • Mention that all steps can be performed from Linux, macOS, or Windows, and clarify that the Azure Portal and Azure CLI are fully supported on all platforms.
  • If scripting is shown, ensure both Bash (for Linux/macOS) and PowerShell (for Windows) examples are present.
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively referencing the Azure Portal (a web GUI) and Visual Studio Code for all steps, without mentioning or providing examples for command-line tools commonly used on Linux (such as Azure CLI or deployment via terminal). There are no Linux-specific instructions or alternatives for creating, configuring, or deploying Azure Functions, nor are there any references to Bash or shell commands. The instructions assume GUI-based workflows, which are more common in Windows-centric documentation.
Recommendations
  • Provide equivalent instructions using Azure CLI for all major steps, including function creation, configuration, and deployment.
  • Include examples for deploying and managing Azure Functions from a Linux terminal (Bash), not just via Visual Studio Code.
  • Mention and link to documentation for cross-platform tools (e.g., Azure CLI, azcopy) alongside Azure Portal instructions.
  • Add a note clarifying that all steps can be performed on Linux, macOS, or Windows, and provide links to relevant platform-specific guides.
  • Where screenshots are used, consider including terminal output or command snippets as alternatives for users not using the Azure Portal GUI.
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation exclusively describes how to enable managed identity for an Azure Event Grid partner topic using the Azure portal, which is a graphical interface accessible from any OS, but does not provide any command-line examples (such as Azure CLI or PowerShell). There is no mention of Linux-specific tools or workflows, nor are there any CLI instructions that would be platform-neutral. The absence of CLI examples may implicitly favor Windows users, who are more likely to use the portal or PowerShell, while Linux users often prefer Azure CLI.
Recommendations
  • Add Azure CLI examples for assigning system-assigned and user-assigned identities to Event Grid partner topics.
  • Include explicit instructions or links for performing these tasks using command-line tools on Linux, macOS, and Windows.
  • Ensure that any referenced scripts or commands are cross-platform, and clarify which tools are available on each OS.
  • Consider adding a section titled 'Using Azure CLI' or 'Command-line instructions' to provide parity for users who do not use the Azure portal.
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by exclusively describing role assignment and management steps using the Azure Portal UI, which is most commonly accessed via Windows environments. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), and no Linux-specific instructions or parity for role assignment or authentication workflows. The absence of CLI or cross-platform automation examples may disadvantage Linux users or those who prefer scripting.
Recommendations
  • Add Azure CLI examples for role assignment and authentication, which work across Windows, Linux, and macOS.
  • Include Bash shell command examples for obtaining JWT tokens and interacting with Azure resources.
  • Explicitly mention that the Azure Portal is accessible from any OS, and provide parity for users who prefer command-line or automated approaches.
  • If PowerShell examples are added, ensure equivalent Bash/Azure CLI examples are provided alongside.
  • Highlight any OS-agnostic tools or SDKs (such as the Azure Identity client library) with examples in multiple languages where possible.
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/monitor-virtual-machine-changes-logic-app.md ...vent-grid/monitor-virtual-machine-changes-logic-app.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by linking exclusively to the Windows-specific 'Create a VM tutorial' for the prerequisite virtual machine setup, without mentioning or linking to the equivalent Linux VM creation guide. No Linux-specific instructions or examples are provided, and the only explicit VM creation reference is for Windows. However, the rest of the tutorial is largely platform-agnostic, focusing on Azure portal and Logic Apps UI, and does not use Windows-specific tools or PowerShell.
Recommendations
  • In the prerequisites section, provide links to both the Windows and Linux VM creation tutorials, e.g., '/azure/virtual-machines/windows/quick-create-portal' and '/azure/virtual-machines/linux/quick-create-portal'.
  • Explicitly state that the tutorial applies to both Windows and Linux virtual machines, unless there are platform-specific limitations.
  • Where examples reference interacting with the VM (such as resizing or updating), ensure that the linked documentation covers both Windows and Linux scenarios.
  • Consider including a note or example that demonstrates monitoring changes on a Linux VM to reinforce cross-platform applicability.