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 76-100 of 289 flagged pages
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/authenticate-with-microsoft-entra-id.md ...les/event-grid/authenticate-with-microsoft-entra-id.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-centric tools and workflows (Azure PowerShell, Azure portal screenshots, references to Windows VMs) are presented before or instead of Linux alternatives. CLI examples are present, but PowerShell is given equal prominence, and there are no explicit Linux shell examples or screenshots. The SDK code samples use C#/.NET, which is more common on Windows, and there are no examples in Bash, Python, or other languages popular on Linux. The documentation does not mention Linux-specific hosting scenarios or provide parity in walkthroughs for Linux users.
Recommendations
  • Add explicit Linux shell (bash) examples for resource creation and management, especially for disabling local authentication and assigning roles.
  • Include screenshots or instructions for Azure portal usage on Linux (e.g., browser-agnostic guidance, note that the portal is cross-platform).
  • Provide SDK code samples in Python, JavaScript, or Java, which are popular on Linux, alongside C#/.NET.
  • Mention Linux VM and container hosting scenarios when discussing managed identities, not just Windows VM.
  • Clarify that Azure CLI is cross-platform and highlight its use for Linux/macOS users.
  • Avoid presenting Windows tools (PowerShell, Windows VM) before Linux equivalents; offer both in parallel or alternate order.
GitHub Create Pull Request
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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on PowerShell and AzureRM modules, which are traditionally Windows-centric. There are no examples or guidance for Linux users (e.g., using Azure CLI, Bash, or cross-platform scripting). The only scripting shown is PowerShell, and there is no mention of Linux tools or alternative approaches for non-Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for Linux users.
  • Mention that Azure Automation supports Python runbooks and provide a sample Python implementation.
  • Clarify that AzureRM modules can be used from Linux/macOS via PowerShell Core, and provide instructions for installing and using PowerShell Core on those platforms.
  • Include notes or sections that highlight cross-platform compatibility and alternative tools for Linux environments.
  • Ensure screenshots and UI instructions are not Windows-specific, or clarify when steps are platform-agnostic.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/event-grid-dotnet-get-started-pull-delivery.md ...nt-grid/event-grid-dotnet-get-started-pull-delivery.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias: all IDE instructions are for Visual Studio (Windows-only), package installation is shown only via PowerShell (Package Manager Console), and there are no Linux or cross-platform alternatives (such as VS Code, CLI, or dotnet CLI commands). The workflow assumes a Windows development environment and omits guidance for Linux or macOS users.
Recommendations
  • Add instructions for using VS Code or JetBrains Rider, which are cross-platform IDEs.
  • Include .NET CLI commands (e.g., 'dotnet new console', 'dotnet add package Azure.Messaging.EventGrid.Namespaces') for project creation and package installation, which work on Windows, Linux, and macOS.
  • Mention that the sample code can be run on Linux and macOS, and provide any necessary environment setup steps for those platforms.
  • Provide screenshots or terminal examples for Linux/macOS environments.
  • Clarify that Visual Studio is optional and not required for .NET development, and link to cross-platform .NET documentation.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/delivery-and-retry.md ...cs/blob/main/articles/event-grid/delivery-and-retry.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references both Azure CLI and PowerShell for configuring Event Grid delivery and retry policies, but only provides explicit sample commands for Azure CLI (which is cross-platform) and mentions PowerShell without providing examples. There is no explicit mention of Linux-specific tools, nor are there any examples using Bash or Linux shell scripting. The documentation refers to 'CLI and PowerShell' together, but does not clarify parity or provide Linux-first guidance. The Azure portal instructions are platform-neutral, but the command-line guidance could be perceived as Windows-biased due to the PowerShell emphasis and lack of Linux-specific examples.
Recommendations
  • Provide explicit Bash/Linux shell examples alongside Azure CLI and PowerShell examples to ensure parity.
  • Clarify that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • If mentioning PowerShell, also mention that PowerShell Core is available on Linux and macOS, and provide example commands for those platforms.
  • Avoid grouping 'CLI and PowerShell' as if they are equivalent; instead, specify which commands are for which platforms.
  • Add a section or note highlighting how to perform these operations on Linux, including installation and usage of Azure CLI and PowerShell Core.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/event-hubs-integration.md ...lob/main/articles/event-grid/event-hubs-integration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Visual Studio Only Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Visual Studio for publishing Azure Functions, assuming the use of .sln files and .exe outputs, and omitting any Linux or cross-platform development environment instructions. While the Azure CLI is used (which is cross-platform), all development and deployment steps for the code are tied to Visual Studio, with no mention of alternatives like VS Code, CLI-based publishing, or other OS-agnostic tools. There are no Linux-specific or cross-platform examples for building, running, or deploying the sample projects.
Recommendations
  • Provide instructions for publishing the Azure Functions app using cross-platform tools such as Azure Functions Core Tools and VS Code, in addition to Visual Studio.
  • Include examples for building and running the sample projects on Linux/macOS, such as using 'dotnet build' and 'dotnet run' commands.
  • Mention that the sample projects can be opened and managed in VS Code or JetBrains Rider, not just Visual Studio.
  • Clarify that the Azure CLI and Cloud Shell steps work identically on Linux, macOS, and Windows.
  • If any steps require Windows-only tools (such as .exe outputs), provide equivalent instructions for Linux/macOS environments.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/event-schema-subscriptions.md ...main/articles/event-grid/event-schema-subscriptions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page shows moderate Windows bias. In the tutorials and how-tos section, PowerShell is featured as a primary scripting option, and Microsoft Teams (a Windows-centric collaboration tool) is used in the main automation tutorial. While Azure CLI is included (which is cross-platform), there is no mention of Linux-specific tools or shell scripting (e.g., Bash), and PowerShell is listed as a distinct option. No Linux-first or Linux-only examples are provided, and Windows-centric tools and patterns (PowerShell, Teams) are mentioned before any Linux equivalents.
Recommendations
  • Add explicit Bash or shell script examples for subscribing to events, alongside PowerShell and Azure CLI.
  • Include tutorials that use Linux-native tools (e.g., send events to Slack, use cron jobs, or integrate with Linux-based automation frameworks).
  • Ensure that cross-platform tools (like Azure CLI) are presented as the default or first option, with PowerShell as an alternative.
  • Mention Linux compatibility and provide guidance for Linux users in relevant sections.
  • Avoid using Windows-centric collaboration tools (like Microsoft Teams) as the sole example; add alternatives popular in Linux environments.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/handler-functions.md ...ocs/blob/main/articles/event-grid/handler-functions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a mild Windows bias by explicitly listing Azure PowerShell as a primary method for configuring batch settings, alongside Azure CLI and portal. PowerShell is a Windows-centric tool, and its mention before Linux-native alternatives (like Bash scripting or direct REST API usage) may suggest a preference for Windows environments. There are no explicit Linux examples, nor is there mention of Linux-specific tools or workflows. The CLI is cross-platform, but the absence of Linux-focused guidance or examples (e.g., Bash, curl, or Linux file paths) further reinforces the bias.
Recommendations
  • Add explicit Linux examples, such as using Bash or curl to configure Event Grid subscriptions via REST API.
  • Clarify that Azure CLI is cross-platform and provide sample commands run in a Linux shell.
  • Balance the mention of PowerShell with Linux-native alternatives, or note PowerShell Core's cross-platform support.
  • Include screenshots or instructions for Linux environments where relevant.
  • Consider listing CLI and REST API methods before PowerShell to avoid Windows-first ordering.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/handler-webhooks.md ...docs/blob/main/articles/event-grid/handler-webhooks.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by consistently listing PowerShell examples alongside Azure CLI and Portal, and by referencing Microsoft Teams and Azure Automation (which are Windows-centric tools) in its tutorials. PowerShell is mentioned as a primary method for quickstarts, and Windows tools/patterns (e.g., Automation runbooks, Teams integration) are highlighted, while Linux-specific examples or tools are absent. The ordering of examples often places PowerShell before or alongside CLI, rather than prioritizing cross-platform or Linux-native approaches.
Recommendations
  • Add explicit Linux shell (bash) examples for all quickstarts and tutorials, ensuring parity with PowerShell.
  • Include references to Linux-native tools and workflows, such as curl, wget, or bash scripts, for webhook consumption and event handling.
  • Reorder example listings to place cross-platform (CLI, REST, bash) examples before Windows-specific (PowerShell) ones.
  • Provide guidance on integrating with Linux-based automation and notification systems (e.g., cron jobs, Slack, email via sendmail) in addition to Microsoft Teams.
  • Clarify that Azure CLI is cross-platform and highlight its use on Linux environments.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/input-mappings.md ...e-docs/blob/main/articles/event-grid/input-mappings.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation consistently provides both Azure CLI and PowerShell examples for all operations. However, PowerShell is a Windows-centric tool, and there are no explicit Linux shell (bash) or cross-platform scripting examples beyond Azure CLI. In several sections, PowerShell examples are given equal prominence to Azure CLI, and in some cases, the PowerShell example follows immediately after the CLI example, reinforcing a Windows-first or Windows-equal approach. There are no bash-specific examples, nor is there mention of Linux-native tools or scripting patterns.
Recommendations
  • Add bash-specific examples for publishing events, subscribing, and topic creation, especially for curl usage and scripting.
  • Clarify that Azure CLI is cross-platform and show usage in both Windows (cmd/powershell) and Linux (bash/zsh) shells.
  • Consider providing examples using other Linux-native tools (e.g., wget, jq) where appropriate.
  • Explicitly state platform compatibility for each example, helping users understand which commands work on Windows, Linux, or macOS.
  • If PowerShell is shown, also show equivalent bash scripting for parity.
GitHub 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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in the certificate generation section: it instructs users to open a command prompt in their user profile folder using Windows-specific instructions (Win+R, %USERPROFILE%), and all command examples are shown in PowerShell syntax. There are no equivalent instructions or examples for Linux or macOS users, nor is there guidance on how to run the step CLI commands in a Unix shell or where to find the user profile directory on those platforms. The rest of the guide is platform-neutral, focusing on the Azure portal and MQTTX app, which are cross-platform.
Recommendations
  • Add Linux/macOS instructions for opening a terminal and locating the user profile directory (e.g., '~/').
  • Provide shell command examples in bash/zsh syntax alongside PowerShell, or use platform-neutral syntax.
  • Clarify that the step CLI commands work on all major platforms and provide installation links for Linux/macOS.
  • Explicitly mention any platform-specific considerations for certificate file paths or permissions.
  • Consider reordering instructions so that platform-neutral guidance appears first, or present Windows and Linux/macOS instructions in parallel.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/mqtt-topic-spaces.md ...ocs/blob/main/articles/event-grid/mqtt-topic-spaces.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates Windows bias primarily in its treatment of shell escaping for topic templates. It provides explicit PowerShell examples for escaping special characters, mentioning PowerShell by name and showing only Windows/PowerShell-specific syntax. There are no equivalent examples or guidance for Linux shells (e.g., Bash, Zsh), nor are Linux tools or patterns mentioned. The order of presentation also puts Windows/PowerShell first, with no parity for Linux users.
Recommendations
  • Add examples for escaping special characters in common Linux shells (e.g., Bash, Zsh), showing how to handle $ and | in topic templates.
  • Include notes or tables comparing escaping requirements across Windows (PowerShell, CMD) and Linux shells.
  • Ensure that CLI examples are shell-agnostic or provide variants for both Windows and Linux environments.
  • Explicitly mention Linux shell considerations wherever shell-specific syntax is discussed.
  • Review other sections for similar bias and ensure Linux parity in all configuration and usage examples.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/manage-event-delivery.md ...blob/main/articles/event-grid/manage-event-delivery.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 its inclusion alongside Azure CLI (which is cross-platform) may signal a bias toward Windows users. Additionally, installation notes and references for Azure PowerShell are present, but there is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples showing Linux command-line patterns or considerations. The related content references a .NET sample, which is also more common in Windows environments.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands, showing usage in Linux/macOS environments (e.g., export, variable syntax differences).
  • Clarify that Azure CLI is cross-platform and provide installation instructions for Linux/macOS as well as Windows.
  • Include notes or examples for using Azure CLI in Bash, zsh, or other common Linux shells, especially for variable assignment and command chaining.
  • Consider referencing or providing sample applications in languages/platforms common on Linux (e.g., Python, Node.js) in the related content section.
  • If PowerShell is included, note that PowerShell Core is available on Linux/macOS and provide installation links or usage notes for those platforms.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/mqtt-certificate-chain-client-authentication.md ...t-grid/mqtt-certificate-chain-client-authentication.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides certificate generation instructions exclusively using Windows PowerShell, with no Linux or macOS shell examples. The installation note for 'step CLI' mentions Windows manual installation but does not provide parity guidance for Linux. All command-line examples are shown in PowerShell syntax, and there are no bash or Linux-specific instructions, which may hinder Linux users attempting to follow the guide.
Recommendations
  • Include equivalent bash/Linux shell commands for certificate generation using 'step CLI'.
  • Add installation instructions for 'step CLI' on Linux and macOS, not just Windows.
  • Present command examples for both Windows (PowerShell) and Linux/macOS (bash), or use a platform-agnostic syntax where possible.
  • Explicitly mention cross-platform compatibility for all tools and steps.
  • Consider reordering examples or providing tabs for Windows and Linux to avoid implicit prioritization of Windows.
GitHub Create Pull Request
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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently presenting Azure PowerShell examples alongside or before Azure CLI, referencing PowerShell-specific commands and patterns, and mentioning Windows-centric tools (PowerShell, Azure portal) as primary options. While Azure CLI (cross-platform) is included, PowerShell examples are given equal or greater prominence, and no explicit Linux-specific shell or tool examples (e.g., pure Bash, curl without Azure CLI, or Linux desktop screenshots) are provided. The use of PowerShell and Windows patterns is pervasive, and Linux parity is not fully addressed.
Recommendations
  • Add explicit Linux/Bash-only examples for key workflows (e.g., using curl and jq without Azure CLI or PowerShell).
  • Include screenshots or instructions for Linux desktop environments where relevant.
  • Present Azure CLI (cross-platform) examples before PowerShell examples to signal platform neutrality.
  • Clarify that Azure CLI and curl commands work natively on Linux/macOS, and provide troubleshooting tips for those platforms.
  • Avoid language or patterns that assume PowerShell or Windows as the default environment.
  • Consider a dedicated section for Linux users, highlighting platform-specific nuances or best practices.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/scripts/powershell-webhook-secure-delivery-microsoft-entra-app.md ...powershell-webhook-secure-delivery-microsoft-entra-app.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows and PowerShell. All example scripts are provided exclusively in PowerShell, with no mention of Bash, CLI, or Linux-native tools. The instructions assume use of PowerShell and Windows-centric workflows, and there is no guidance for Linux users or alternative scripting environments.
Recommendations
  • Provide equivalent examples using Azure CLI (az) commands and Bash scripts for Linux users.
  • Include notes or sections that explain how to perform the same steps on Linux or macOS environments.
  • Mention cross-platform tools and clarify which steps are OS-agnostic.
  • Add links to relevant Linux documentation or guides for Azure Event Grid and Microsoft Entra Application management.
  • Consider using generic terminology (e.g., 'terminal' instead of 'PowerShell window') where possible.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/mqtt-publish-and-subscribe-cli.md .../articles/event-grid/mqtt-publish-and-subscribe-cli.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas. The certificate generation section provides only Windows-specific instructions (using Command Prompt and Powershell syntax), with no Linux or macOS equivalents. The sample code is C#/.NET-centric, referencing Visual Studio and NuGet, which are primarily Windows tools, and does not mention Linux development environments or alternative languages. There are no explicit Linux shell or OpenSSL examples for certificate creation, nor guidance for running the sample code on Linux.
Recommendations
  • Add Linux and macOS instructions for certificate generation, e.g., using OpenSSL or step CLI in Bash.
  • Provide Bash shell command examples alongside Powershell/Command Prompt instructions.
  • Include sample code and instructions for running MQTT clients in cross-platform languages (e.g., Python, Node.js) and editors (e.g., VS Code).
  • Mention Linux package managers (apt, yum, brew) for installing required tools.
  • Clarify that the Azure CLI and MQTT workflows are cross-platform, and provide parity in examples and tooling references.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/secure-webhook-delivery.md ...ob/main/articles/event-grid/secure-webhook-delivery.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All scripting examples use PowerShell, and instructions direct users to use the Azure Portal's PowerShell environment (Azure Shell) without mentioning Bash or Linux alternatives. There are no Linux shell or cross-platform CLI examples for steps involving Microsoft Graph or service principal configuration. Windows-centric tools and patterns (PowerShell, Windows-style variable naming, error messages) are presented exclusively and/or before any CLI usage. Azure CLI is used only for later steps, but the initial configuration is PowerShell-only.
Recommendations
  • Provide equivalent Bash or Azure CLI examples for all PowerShell scripts, especially for Microsoft Graph and service principal configuration.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
  • Include Linux/macOS setup instructions and screenshots where appropriate.
  • Add troubleshooting notes for Linux environments, including common permission or environment differences.
  • Ensure that all error messages and code snippets are shown in both PowerShell and Bash/CLI formats where possible.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/troubleshoot-network-connectivity.md ...ticles/event-grid/troubleshoot-network-connectivity.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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) before Linux equivalents, and sometimes exclusively. The troubleshooting commands and tool recommendations are focused on Windows, with only minimal or less detailed Linux alternatives (e.g., telnet) mentioned. Linux-native tools and patterns are underrepresented, and Windows-centric utilities are referenced and linked.
Recommendations
  • Provide Linux-native troubleshooting examples (e.g., using nc, curl, or nmap) alongside or before Windows examples.
  • List Linux commands and tools with equal detail and prominence as Windows/Powershell ones.
  • Include links to Linux tool documentation (e.g., netcat, curl, nmap) where Windows tools are referenced.
  • Avoid referencing Windows-only utilities (psping.exe, tcpping.exe) without offering Linux alternatives.
  • Ensure command syntax and troubleshooting steps are platform-agnostic or clearly separated for Windows and Linux.
  • Add troubleshooting scenarios and examples relevant to common Linux environments.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/subscribe-to-graph-api-events.md ...n/articles/event-grid/subscribe-to-graph-api-events.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by referencing Windows-specific tools and patterns before their Linux equivalents. For example, the use of PowerShell is included as a primary code sample, and the Azure CLI command for region names is presented without explicit mention of Linux compatibility or alternatives. The documentation does not provide Linux-specific setup instructions or highlight cross-platform considerations, and the sample code references (such as C#, PowerShell) are traditionally Windows-centric. There is no explicit mention of Linux shell usage, nor are Linux-specific troubleshooting or environment setup steps provided.
Recommendations
  • Explicitly mention that Azure CLI commands work cross-platform and provide example usage in Bash/zsh.
  • Add Linux-specific setup instructions or notes for environment preparation, especially for authentication and SDK installation.
  • Include sample code or references for Bash scripts alongside PowerShell, or clarify PowerShell usage on Linux.
  • Ensure parity in language and tooling recommendations, e.g., highlight Python and JavaScript (popular on Linux) equally with C# and PowerShell.
  • Add troubleshooting notes for common Linux issues (permissions, environment variables, etc.) when working with Azure and Microsoft Graph SDKs.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/scripts/powershell-webhook-secure-delivery-microsoft-entra-user.md ...owershell-webhook-secure-delivery-microsoft-entra-user.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively provides a PowerShell script for configuring secure webhook delivery with Microsoft Entra user in Azure Event Grid. There are no examples or instructions for Linux-native tools or shell environments (such as Bash or CLI), and the workflow assumes familiarity with PowerShell and Windows-centric patterns. The use of PowerShell modules (e.g., Microsoft.Graph.PowerShell) and cmdlets is pervasive, with no mention of equivalent Azure CLI or REST API approaches that would be more cross-platform.
Recommendations
  • Provide equivalent examples using Azure CLI commands, which are cross-platform and work natively on Linux and macOS.
  • Include Bash script samples for key steps, such as service principal creation, role assignment, and application role management.
  • Mention REST API alternatives for advanced configuration, with sample requests and responses.
  • Clearly indicate any prerequisites or platform dependencies, and offer guidance for users on non-Windows systems.
  • Reorder or parallelize examples so that Linux/macOS approaches are presented alongside or before Windows/PowerShell methods.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/mqtt-publish-and-subscribe-cli.md .../articles/event-grid/mqtt-publish-and-subscribe-cli.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the certificate generation section by providing only Windows-specific instructions (e.g., opening Command Prompt via Win+R and using Powershell syntax), and does not provide equivalent Linux or macOS command-line examples or guidance. The sample code section assumes usage of Visual Studio and NuGet, which are Windows-centric development tools, without mentioning cross-platform alternatives.
Recommendations
  • Provide explicit Linux and macOS instructions for generating certificates with step CLI, including terminal commands and file paths.
  • Replace or supplement 'open a Command Prompt window (Win+R...)' with cross-platform terminal instructions.
  • Show bash/zsh shell commands alongside Powershell, or use bash as the default for CLI examples.
  • Mention and provide instructions for using cross-platform editors (e.g., VS Code) and package managers (e.g., dotnet CLI for NuGet) in the sample code section.
  • Ensure all steps and tools referenced are available and documented for Linux/macOS users, or clearly link to equivalent guides.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/event-hubs-integration.md ...lob/main/articles/event-grid/event-hubs-integration.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Visual Studio Only Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using Visual Studio for publishing the Azure Functions app, with no mention of cross-platform alternatives (such as VS Code, Azure Functions Core Tools, or CLI-based deployment). The instructions for running the sample data generator also assume a Windows environment (building and running a .exe), and there are no Linux/macOS-specific instructions or alternatives provided. While the Azure CLI is used for infrastructure deployment (which is cross-platform), the overall workflow assumes a Windows development environment.
Recommendations
  • Provide instructions for publishing the Azure Functions app using cross-platform tools such as Azure Functions Core Tools, VS Code, or the Azure CLI, in addition to Visual Studio.
  • Include guidance for building and running the WindTurbineDataGenerator on Linux/macOS (e.g., using dotnet CLI to build and run the project, rather than referencing the .exe).
  • Explicitly mention that the sample project can be developed and deployed from Linux/macOS, and provide any necessary prerequisites or steps.
  • Where screenshots or UI instructions are given, note any differences for non-Windows users or provide CLI alternatives.
  • Ensure all code and deployment steps are platform-agnostic or provide parallel instructions for Linux/macOS users.
GitHub Create Pull Request
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
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation presents Azure PowerShell instructions before Azure CLI, which can indicate a Windows-first bias. PowerShell is primarily associated with Windows environments, and its commands are featured prominently. Although Azure CLI is cross-platform and included, there are no Linux- or macOS-specific notes or examples, and no mention of Bash or shell scripting, which are common for Linux users.
Recommendations
  • Present Azure CLI instructions before or alongside PowerShell, as CLI is cross-platform and widely used on Linux.
  • Include explicit notes or examples for Linux/macOS users, such as Bash command usage or environment-specific tips.
  • Clarify that both Azure CLI and PowerShell are available on all major platforms, and link to installation guides for each.
  • Consider adding a section or callout for Linux users, highlighting any differences or best practices.
  • Avoid implying that PowerShell is the default or preferred method unless there is a technical reason.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/authenticate-with-microsoft-entra-id.md ...les/event-grid/authenticate-with-microsoft-entra-id.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While the core authentication concepts are cross-platform and SDK examples are language-agnostic, platform-specific instructions and examples favor Windows and PowerShell. For example, enabling managed identities references a Windows VM link first, and PowerShell is given as a primary scripting example for resource creation. There are no explicit Linux or Bash examples for common tasks, and CLI instructions are present but not highlighted as the default. There is also a lack of parity in step-by-step instructions or screenshots for Linux environments.
Recommendations
  • Provide explicit Linux/Bash examples alongside PowerShell for all resource creation and configuration steps.
  • When referencing enabling managed identities, include links and instructions for both Windows and Linux VMs equally.
  • In sections showing Azure CLI and PowerShell, present CLI (cross-platform) examples first, or at least in parallel with PowerShell.
  • Add screenshots or walkthroughs for Linux environments where UI or OS-specific steps are shown for Windows.
  • Review all references to Windows tools and ensure Linux equivalents are mentioned and documented.
  • Where environment variables are set in code samples, show both Windows (setx, PowerShell) and Linux (export, Bash) approaches.
GitHub Create Pull Request
Event Grid https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/event-grid/delivery-and-retry.md ...cs/blob/main/articles/event-grid/delivery-and-retry.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references both Azure CLI and PowerShell for configuring retry policies and batching, but only provides explicit CLI examples (which are cross-platform). However, it refers to 'PowerShell command' alongside CLI in the retry policy section, but does not provide any PowerShell or Linux shell-specific examples. There is no explicit mention or example of Linux-specific tools, nor are there any bash or shell script examples. The order of mention ('CLI and PowerShell') and the lack of Linux-specific context or troubleshooting may suggest a subtle Windows-first or PowerShell-heavy bias.
Recommendations
  • Provide explicit bash/Linux shell examples alongside Azure CLI and PowerShell examples, especially where scripting or automation is discussed.
  • When referencing both CLI and PowerShell, ensure parity by including example commands for both, or clarify that Azure CLI commands are cross-platform.
  • Include troubleshooting notes or tips relevant to Linux environments (e.g., file permissions, environment variables) where applicable.
  • Avoid listing PowerShell before CLI or Linux tools unless there is a technical reason; consider rotating the order or stating that both are supported equally.
  • Add a note clarifying that Azure CLI commands work on Windows, Linux, and macOS to reinforce cross-platform support.
GitHub Create Pull Request
← Previous Page 4 of 12 Next →