Azure Functions

385
Total Pages
248
Linux-Friendly Pages
137
Pages with Bias
35.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

1023 issues found
Showing 726-750 of 1023 flagged pages
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-openai-semanticsearch-input.md ...ions/functions-bindings-openai-semanticsearch-input.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 Tools
Summary
The documentation provides code examples for multiple languages, including Powershell, which is primarily a Windows-centric scripting language. Powershell receives its own dedicated example and configuration section, including references to function.json and run.ps1, which are typical in Windows environments. There is no equivalent coverage for Linux shell scripting (e.g., Bash), nor are Linux-specific tools or patterns mentioned. This may unintentionally signal a bias toward Windows users and workflows.
Recommendations
  • Add equivalent Bash or shell script examples for semantic search input binding to support Linux users.
  • Explicitly mention cross-platform compatibility for Powershell examples, or clarify if they work on Linux/macOS Powershell Core.
  • Provide guidance or links for Linux users on how to configure and run Azure Functions with semantic search using native Linux tools.
  • Ensure that references to configuration files (such as function.json) are accompanied by instructions relevant to both Windows and Linux environments.
  • Consider including troubleshooting or environment setup notes for both Windows and Linux users to ensure parity.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-signalr-service.md .../azure-functions/functions-bindings-signalr-service.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page shows a mild Windows bias: it references local development using 'local.settings.json' and environment variable naming conventions that are most familiar to Windows users, but does not provide explicit Linux/macOS equivalents or examples. There are no shell (bash/zsh) or Linux-specific instructions, and the only example of environment variable syntax conversion (from '__' to ':') is given in a way that is most relevant to Windows environments. No PowerShell-heavy or Windows tools are mentioned, but Linux parity is lacking in examples and guidance.
Recommendations
  • Add explicit Linux/macOS instructions for setting environment variables, including examples using bash/zsh syntax.
  • Clarify how environment variable naming conventions differ on Linux/macOS (e.g., use of ':' vs '__', export commands).
  • Provide sample commands for setting environment variables in Linux shells for local development.
  • Mention cross-platform development tools and editors (e.g., VS Code on Linux/macOS) where relevant.
  • Ensure that all configuration examples are shown for both Windows and Linux environments, especially for local development scenarios.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-private-site-access.md ...zure-functions/functions-create-private-site-access.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exhibits a Windows bias by exclusively guiding users to create a Windows Server VM, with no mention of Linux VM options or examples. All screenshots and instructions for VM creation are Windows-centric, and the initial search and selection steps explicitly specify 'Windows Server'. There are no Linux alternatives or parity in the walkthrough, and the tutorial does not provide examples or guidance for users who may prefer or require a Linux-based environment.
Recommendations
  • Include instructions and screenshots for creating a Linux VM (e.g., Ubuntu, CentOS) alongside the Windows VM steps.
  • Provide a note or section highlighting that Azure Functions private site access works equally with Linux VMs, and link to relevant Linux VM creation guides.
  • Offer parity in examples for accessing the VM (e.g., SSH for Linux, RDP for Windows) and clarify Bastion usage for both OS types.
  • Ensure that references to tools and workflows (such as deployment agents or remote access) mention Linux equivalents where applicable.
  • Add a table or checklist comparing Windows and Linux setup steps for this scenario, so users can choose their preferred platform.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-manually-run-non-http.md ...les/azure-functions/functions-manually-run-non-http.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing the Azure portal and Visual Studio Code as primary tools, both of which are commonly used on Windows. There is no mention of Linux-specific tools or workflows, and no examples using Linux command-line utilities (such as curl or wget) are provided. The instructions for obtaining the master key and making HTTP requests are platform-neutral, but the lack of explicit Linux examples or references may hinder parity for Linux users.
Recommendations
  • Add explicit examples using Linux command-line tools (e.g., curl, wget) to demonstrate how to make the HTTP POST request.
  • Include screenshots or instructions for accessing the Azure portal from Linux browsers, if relevant.
  • Reference Linux-native editors (such as VS Code on Linux, or alternatives like Vim) when discussing manual function execution.
  • Clarify that the Azure CLI commands work cross-platform and provide terminal examples for both Windows (PowerShell/CMD) and Linux (bash).
  • Consider adding a section or tab specifically for Linux users, outlining any differences or tips for running Azure Functions from Linux environments.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-target-based-scaling.md ...cles/azure-functions/functions-target-based-scaling.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is largely cross-platform and avoids explicit Windows or PowerShell bias in its examples and configuration instructions. However, there are subtle indications of Windows bias: in the Java Kafka example, a comment refers to enabling a line 'for windows' regarding SSL certificate location, and the use of Windows-style environment variable syntax (e.g., %BrokerList%) is present in several code samples. No Linux-specific instructions, examples, or parity notes are provided, and Windows is mentioned before Linux in the only place where platform distinction is made.
Recommendations
  • Add explicit Linux/macOS instructions or notes where platform-specific configuration may differ (e.g., file paths, environment variable syntax).
  • Where environment variables are shown, provide both Windows (%VAR%) and Linux/macOS ($VAR or ${VAR}) examples.
  • In code comments or documentation, mention Linux/macOS usage alongside Windows, especially for file paths and SSL certificate configuration.
  • Review all examples for platform-neutrality and ensure that any platform-specific advice is balanced and presented together.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-scenarios.md ...b/main/articles/azure-functions/functions-scenarios.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 parity across most programming languages, including Python, Java, JavaScript, TypeScript, and PowerShell. However, there is a subtle Windows bias: PowerShell is included as a first-class language throughout, which is primarily a Windows-centric shell. In some sections, C# examples (commonly associated with Windows development) are given code snippets, while other languages only get links. There is no explicit mention of Linux-specific tools, shells, or workflows, and no examples using Bash or Linux CLI tools. The documentation does not reference Linux-specific deployment, troubleshooting, or scripting patterns, and PowerShell is presented as the only shell scripting option.
Recommendations
  • Add Bash or Linux shell scripting examples alongside PowerShell where relevant, especially for automation scenarios.
  • Explicitly mention that Azure Functions supports Linux-based environments and provide links or examples for Linux deployment and management.
  • Include references to Linux tools (e.g., curl, jq) in HTTP/web API scenarios.
  • Where PowerShell is listed, clarify its cross-platform availability, or offer Bash equivalents.
  • Add troubleshooting or operational notes for Linux users, such as file permissions, environment variables, and package installation.
  • Ensure that C# examples are balanced with code snippets for other languages, not just links.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/python-memory-profiler-reference.md ...es/azure-functions/python-memory-profiler-reference.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 demonstrates a Windows bias in the local development setup instructions. Windows tools and patterns (such as PowerShell and the 'py' launcher) are mentioned first and in more detail, while Linux equivalents are only mentioned secondarily. The activation and creation of the Python virtual environment use Windows-specific commands as the default, with Linux commands provided as alternatives. There are no Linux-specific troubleshooting tips or parity checks for cross-platform issues.
Recommendations
  • Present Linux and Windows instructions side-by-side or in parallel tabs, rather than listing Windows first.
  • Use neutral language such as 'In Windows, do X; in Linux/macOS, do Y' rather than 'Open a Windows PowerShell or any Linux shell as you prefer.'
  • Include Linux/macOS troubleshooting notes and parity checks for common issues (e.g., permissions, path separators).
  • Ensure all examples and screenshots use platform-agnostic paths and commands where possible.
  • Explicitly mention macOS where relevant, not just 'Linux'.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-code-constraints.md ...unctions/durable/durable-functions-code-constraints.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 Tools
Summary
The documentation provides code examples for multiple languages, including PowerShell, which is primarily a Windows-centric scripting language. PowerShell is given equal footing with other languages in example tabs, and Windows-specific tools/cmdlets (e.g., Get-Date, New-Guid) are referenced. However, there is no evidence of Windows-first ordering, nor are Linux tools or shell scripting languages (e.g., Bash) mentioned or provided as alternatives. The documentation does not address Linux-specific patterns or tools, and PowerShell is the only shell scripting language included.
Recommendations
  • Add Linux shell scripting examples (e.g., Bash) where relevant, especially for scenarios where PowerShell is shown.
  • Clarify that PowerShell examples are primarily for Windows users, and suggest alternatives for Linux users.
  • Include notes or guidance for Linux environments, such as differences in environment variable handling, file system access, or common scripting patterns.
  • Consider reordering or grouping language examples to avoid implying parity between Windows-centric and cross-platform languages.
  • Explicitly mention platform compatibility for each language example, helping users choose the most appropriate option for their OS.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/event-driven-scaling.md .../main/articles/azure-functions/event-driven-scaling.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 exhibits mild Windows bias, primarily in the 'Limit scale-out' section, where both Azure CLI and Azure PowerShell examples are provided, but no Linux shell or Bash examples are shown. Additionally, in the 'Scale-in behaviors' section, Windows-specific behaviors are mentioned before any cross-platform considerations. There are no explicit Linux-only examples, and the documentation does not mention Linux tools or patterns, nor does it provide parity for Linux users in command-line examples.
Recommendations
  • Add Bash or shell script examples alongside Azure CLI and PowerShell, especially for configuration tasks.
  • Clarify platform applicability for commands and behaviors (e.g., note when something is Windows-specific or cross-platform).
  • Include Linux-specific notes or examples where relevant, such as file system behaviors or environment differences.
  • Ensure that examples and instructions are presented in a platform-neutral order, or provide tabs for both Windows and Linux usage.
  • Reference Linux hosting scenarios and considerations where appropriate, to balance the mention of Windows-specific behaviors.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-overview.md .../azure-functions/durable/durable-functions-overview.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page for Durable Functions provides parity across major programming languages (C#, JavaScript, Python, PowerShell, Java) and does not show strong Windows bias in code examples or patterns. However, there is a subtle bias in tooling recommendations: Visual Studio (Windows-only) is mentioned first for C# quickstarts and templates, while Visual Studio Code (cross-platform) is used for other languages. PowerShell, a Windows-centric language, is included, but Linux equivalents (such as Bash) are not present. There is no explicit mention of Linux-specific development environments or CLI workflows.
Recommendations
  • List Visual Studio Code (cross-platform) before Visual Studio in quickstart and template recommendations for C#.
  • Explicitly mention and provide examples for developing and running Durable Functions on Linux, including CLI workflows (Azure Functions Core Tools) and container-based development.
  • Add references to Linux-friendly editors (e.g., VS Code, Vim) and environments in the 'Jump right in' and template sections.
  • Clarify that PowerShell examples work on Linux (PowerShell Core), or provide Bash equivalents where appropriate.
  • Ensure that all tooling and workflow instructions are platform-neutral or provide both Windows and Linux options.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-mcp.md ...ain/articles/azure-functions/functions-bindings-mcp.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by exclusively referencing Azure Functions Core Tools and Azure CLI for local development and key retrieval, without mentioning Linux-specific usage patterns or alternatives. No Linux shell (bash) or cross-platform examples are provided for key retrieval, and there is no explicit guidance for Linux users regarding installation or usage of required tools.
Recommendations
  • Include explicit instructions and examples for Linux users, such as using bash/zsh to run Azure CLI commands.
  • Clarify that Azure Functions Core Tools and Azure CLI are cross-platform, and provide installation links for Linux/macOS.
  • Add Linux/macOS-specific notes or troubleshooting tips for common issues (e.g., permissions, environment variables).
  • Provide examples of retrieving the system key using bash or PowerShell, and mention that both shells are supported.
  • Ensure that all referenced tools and commands are presented in a way that is platform-agnostic or that alternatives are given for each major OS.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-openai-embeddingsstore-output.md ...ns/functions-bindings-openai-embeddingsstore-output.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 Tools
Summary
The documentation provides dedicated examples and configuration details for PowerShell, including a separate section for function.json and run.ps1 files. PowerShell is a Windows-centric scripting language, and there are no equivalent examples for Linux shell environments (e.g., Bash). This focus on PowerShell may disadvantage Linux users, as no Linux-native scripting or configuration patterns are presented.
Recommendations
  • Add Linux shell (Bash) examples alongside PowerShell, especially for scripting and configuration tasks.
  • Include instructions for creating and configuring function.json using Linux tools (e.g., nano, vim, or command-line utilities).
  • Clarify that Azure Functions can be developed and run on both Windows and Linux, and provide parity in code and configuration samples.
  • Where PowerShell is used, offer equivalent Bash or cross-platform alternatives to ensure accessibility for non-Windows users.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-versions.md ...ob/main/articles/azure-functions/functions-versions.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 exhibits a mild Windows bias, primarily by referencing Windows-centric tools (Visual Studio) and presenting Windows workflows (Visual Studio project settings) before mentioning cross-platform or Linux-friendly alternatives (Visual Studio Code, Azure Functions Core Tools). There are no explicit Linux or bash examples, and instructions for pinning to a minor version mention that the process differs between Windows and Linux, but do not provide Linux-specific guidance or examples. The documentation does not mention Linux tools or provide parity in example commands for Linux environments.
Recommendations
  • Add explicit Linux/bash examples for tasks such as setting app settings, pinning runtime versions, and local development workflows.
  • Provide parity in instructions for Visual Studio Code and Azure Functions Core Tools, including Linux-specific setup and usage details.
  • When referencing platform-specific differences (e.g., pinning minor versions), include both Windows and Linux instructions/examples side by side.
  • Mention Linux package managers or shell commands where appropriate (e.g., installing Azure Functions Core Tools on Linux).
  • Ensure that cross-platform tools and workflows are described before or alongside Windows-specific ones to avoid Windows-first bias.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-scenarios.md ...b/main/articles/azure-functions/functions-scenarios.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 programming language pivots for C#, Python, JavaScript, Java, TypeScript, and PowerShell. PowerShell is included as a first-class language throughout, which is a Windows-centric technology. There are no explicit Linux shell (bash/zsh) examples, nor are Linux-specific tools or patterns mentioned. The order of language pivots often places C# and PowerShell before others, reflecting a subtle Windows-first bias. However, the content does not exclusively use Windows tools, and most examples are cross-platform in nature.
Recommendations
  • Add bash or Linux shell scripting examples where appropriate, especially for automation scenarios.
  • Include references to Linux-native tools or workflows (e.g., CLI usage, deployment from Linux environments).
  • Balance the order of language pivots so that Windows-centric languages (C#, PowerShell) are not always listed first.
  • Explicitly mention cross-platform compatibility in relevant sections, clarifying that Azure Functions can be developed and run on Linux as well as Windows.
  • Provide links or tutorials for setting up and running Azure Functions on Linux environments, including containerization and local development.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-azure-developer-cli.md ...functions/create-first-function-azure-developer-cli.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 examples and instructions for multiple programming languages and platforms, but there are several instances where Windows-specific instructions, tools, or patterns are presented before or alongside Linux/macOS equivalents. PowerShell is given its own pivot and is referenced in detail, and Windows command-line instructions (Cmd, PowerShell) are often listed before or more prominently than Linux/macOS alternatives. However, Linux/macOS instructions are present for most steps, and the use of bash and cross-platform tools like curl is encouraged.
Recommendations
  • Ensure Linux/macOS instructions are always presented before or alongside Windows-specific instructions, especially in command-line sections.
  • Avoid giving PowerShell or Windows Cmd examples priority in ordering or presentation; consider grouping by OS rather than by shell type.
  • Where possible, use cross-platform commands and tools as the primary example, with OS-specific alternatives clearly marked as secondary.
  • Explicitly state cross-platform compatibility for all tools and commands, and provide troubleshooting notes for Linux/macOS users where issues may arise.
  • Review all pivots and tabs to ensure parity in depth and clarity between Linux/macOS and Windows instructions.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-packages.md .../azure-functions/durable/durable-functions-packages.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 mild Windows bias by listing .NET (a Windows-centric technology) package instructions first and in greater detail, followed by .NET isolated, before mentioning other platforms. PowerShell, a Windows-native shell, is included as a first-party SDK and receives a dedicated note and migration guide reference, while Linux-native shells (e.g., Bash) are not mentioned. There are no explicit Linux examples, tools, or patterns referenced, and the documentation focuses on Windows-oriented workflows (e.g., referencing .csproj files and NuGet packages) before mentioning cross-platform alternatives.
Recommendations
  • Add explicit Linux usage examples, such as instructions for installing SDKs/packages using Linux-native tools (e.g., pip for Python, npm for Node.js, Maven for Java) and referencing common Linux file paths.
  • Include parity for Linux shell environments (e.g., Bash) in examples and migration notes, especially where PowerShell is highlighted.
  • Reorder sections or provide a summary table at the top that treats all platforms equally, rather than leading with .NET/Windows-centric instructions.
  • Mention cross-platform compatibility and any platform-specific caveats for SDKs and storage providers.
  • Clarify that .NET and PowerShell are cross-platform, but originated as Windows technologies, to help Linux users contextualize the instructions.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-configure-managed-identity.md ...urable/durable-functions-configure-managed-identity.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 referencing Windows-centric tools and workflows (Visual Studio, Azure portal, user context in Microsoft applications) and omitting explicit Linux-specific instructions or examples. There are no references to Linux tools, shell commands, or alternative workflows for Linux users. The order of example contexts (Visual Studio, VS Code, Azure CLI) also places Microsoft/Windows tools before cross-platform or Linux-native options.
Recommendations
  • Add explicit instructions and examples for Linux users, such as using Azure CLI in Bash or other Linux shells.
  • Mention Linux-compatible editors (e.g., VS Code, JetBrains Rider) and clarify that the steps apply to non-Windows environments.
  • Provide screenshots or terminal commands for role assignment using Azure CLI or REST API, which are platform-agnostic.
  • Clarify that Azurite and Durable Functions can be used on Linux and provide installation instructions for Linux.
  • List Azure CLI as the first option for developer credential context to emphasize cross-platform parity.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-entities.md .../azure-functions/durable/durable-functions-entities.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 does not display overt Windows bias in terms of platform-specific tools or PowerShell examples. However, there is a subtle 'windows_first' bias: .NET/C# examples (which are most commonly associated with Windows development) are consistently presented before JavaScript and Python examples, and are more detailed. There are no explicit Linux-specific examples, nor is there mention of Linux tools or patterns. The documentation does not reference Windows-only tools, but the ordering and depth of .NET coverage may implicitly favor Windows developers.
Recommendations
  • Add explicit notes or examples showing how to use Durable Entities on Linux-based environments (e.g., Azure Functions on Linux, containerized deployments).
  • Balance the depth and detail of examples across all supported languages, not just .NET/C#.
  • Where platform-specific considerations exist (such as file paths, environment setup, or deployment), provide both Windows and Linux instructions.
  • Clarify that .NET examples are cross-platform and can be used on Linux, and provide links or guidance for Linux users.
  • Consider rotating the order of language examples or grouping them by platform-neutral criteria.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-task-hubs.md ...azure-functions/durable/durable-functions-task-hubs.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 code examples for several languages, including PowerShell, which is primarily a Windows-centric shell. PowerShell examples are given equal prominence as other languages, but there are no explicit Linux shell (e.g., Bash) examples or references to Linux-specific tools or patterns. The documentation also references tools like Azure Storage Explorer, which is available on multiple platforms but is often associated with Windows usage. There is no mention of Linux command-line tools or workflows for inspecting storage or managing task hubs, and no Bash or Linux shell scripting examples are provided.
Recommendations
  • Add Linux/Bash shell examples for orchestration triggers and management tasks, especially in sections where PowerShell is shown.
  • Mention Linux-native tools (e.g., az CLI, sqlcmd, or other database inspection tools) alongside Azure Storage Explorer and MSSQL tools.
  • Clarify cross-platform availability of referenced tools, and provide guidance for Linux users where workflows may differ.
  • Consider including troubleshooting or inspection steps using Linux command-line utilities for Azure Storage and MSSQL.
  • Explicitly state that Durable Functions and related tooling are cross-platform, and provide parity in examples and tool references.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-task-scheduler/choose-orchestration-framework.md ...rable-task-scheduler/choose-orchestration-framework.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 mild Windows bias by listing PowerShell as a primary language in the Durable Functions quickstarts table, with no explicit mention of Linux shell equivalents (e.g., Bash). PowerShell is presented alongside other languages, but there are no Linux-specific examples or references to Linux-native tools or patterns. The documentation does not provide parity for Linux users in terms of command-line tooling or development workflow examples.
Recommendations
  • Add Linux/Bash quickstart examples alongside PowerShell, especially for Durable Functions local development and deployment.
  • Explicitly mention cross-platform development workflows, including Linux and macOS, in relevant sections.
  • Provide guidance or links for Linux users on installing prerequisites, running local emulators, and deploying to Azure from Linux environments.
  • Ensure that sample code and instructions are not Windows-centric (e.g., avoid assuming PowerShell is the default shell).
  • Include troubleshooting or tips for common Linux development scenarios (such as file permissions, environment setup, etc.).
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/quickstart-python-vscode.md ...es/azure-functions/durable/quickstart-python-vscode.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 activation instructions for the Python virtual environment on Linux, macOS, and Windows, but lists Windows last and uses PowerShell syntax for Windows. There is no evidence of exclusive use of Windows tools or missing Linux examples; all major steps are cross-platform and use Visual Studio Code and Azure Functions Core Tools, which are available on all platforms. However, the Windows instructions use PowerShell, and the order of presentation puts Linux and macOS before Windows, which is less typical for Microsoft documentation (usually Windows is first). No Linux-specific tools or patterns are omitted, and parity is generally good.
Recommendations
  • Ensure that all platform instructions (Linux, macOS, Windows) are presented with equal prominence and clarity.
  • Consider listing platforms in alphabetical order or explicitly stating that all platforms are supported equally.
  • Provide both PowerShell and Command Prompt activation commands for Windows, as some users may use cmd.exe.
  • Add explicit notes or links for Linux users regarding installation of Azure Functions Core Tools and Azurite, as package managers and installation steps may differ.
  • Verify that all screenshots and UI instructions are equally applicable to Linux and macOS users (e.g., keyboard shortcuts, terminal behavior).
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-service-bus.md ...cles/azure-functions/functions-bindings-service-bus.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 focuses heavily on .NET (C#) and NuGet-based workflows, which are most commonly associated with Windows development environments. There are no explicit Linux or cross-platform command-line examples (e.g., using dotnet CLI, pip, npm, etc.), nor are there any references to Linux-specific tools or patterns. The installation instructions and binding details are presented primarily for C#, with other languages (Python, JavaScript, Java, PowerShell) grouped together and given less detailed treatment. There is no mention of Linux-specific considerations or parity in tooling or workflow.
Recommendations
  • Add explicit cross-platform installation instructions, such as using dotnet CLI for C# (e.g., 'dotnet add package ...'), pip for Python, npm for JavaScript/TypeScript, etc.
  • Include examples or notes about running Azure Functions and Service Bus bindings on Linux environments (e.g., Azure Functions Core Tools, Docker, WSL).
  • Ensure parity in documentation depth for non-Windows languages and platforms, providing detailed binding and configuration examples for Python, JavaScript, Java, and PowerShell.
  • Mention any platform-specific considerations (such as file paths, environment variables, or permissions) for Linux users.
  • Where NuGet is referenced, clarify that it can be used cross-platform, and provide alternative instructions for Linux/macOS users who may not use Visual Studio.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-openai-semanticsearch-input.md ...ions/functions-bindings-openai-semanticsearch-input.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 Tools
Summary
The documentation provides code examples for multiple languages, including C#, Java, JavaScript, TypeScript, Python, and PowerShell. However, the PowerShell example is given special treatment: it includes both a function.json configuration file and a run.ps1 script, whereas other languages only show the main code file. PowerShell is a Windows-centric tool, and there is no equivalent example for Bash or other Linux-native scripting environments. This creates a subtle bias towards Windows users by implying PowerShell is the default or preferred scripting environment for Azure Functions, without offering parity for Linux users.
Recommendations
  • Add equivalent Bash or shell script examples for Linux users, especially for scenarios where PowerShell is shown.
  • Explicitly mention cross-platform alternatives to PowerShell in the documentation, and clarify that Azure Functions can be developed and run on Linux using Bash or other shells.
  • Ensure that configuration examples (such as function.json) are provided for all supported scripting environments, not just PowerShell.
  • Consider adding a section or note highlighting cross-platform development and deployment options for Azure Functions, including Linux and macOS.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-openai-assistantpost-input.md ...tions/functions-bindings-openai-assistantpost-input.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 Tools
Summary
The documentation provides a dedicated section and example for PowerShell, including a function.json and run.ps1 sample, but does not offer equivalent shell or scripting examples for Linux users (e.g., Bash). This focus on PowerShell, a Windows-centric tool, without Linux shell parity, introduces a subtle Windows bias. However, the documentation does not otherwise prioritize Windows tools or patterns in other language sections, and the examples for other languages (C#, Java, Python, JS/TS) are platform-neutral.
Recommendations
  • Add equivalent Bash or shell script examples alongside PowerShell to support Linux users.
  • Clarify in the PowerShell section that the example is for Windows and provide guidance or links for Linux/macOS users.
  • Wherever configuration or scripting is shown, ensure both Windows (PowerShell) and Linux (Bash/sh) approaches are demonstrated or referenced.
  • Review related samples and documentation links to ensure Linux users are equally supported.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-signalr-service.md .../azure-functions/functions-bindings-signalr-service.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 shows subtle Windows bias by referencing configuration patterns and environment variable naming conventions that are more familiar to Windows users (e.g., double underscore `__` separators, which are common in .NET/Windows environments), and by referencing `local.settings.json` and Azure App Configuration without explicit Linux or cross-platform alternatives. There are no explicit Linux shell or configuration examples, nor is there guidance for Linux-specific development scenarios. The documentation does not mention Linux tools or provide parity for Linux-based workflows, such as using environment variables in bash or deployment via Linux-native tools.
Recommendations
  • Add explicit Linux shell examples for setting environment variables (e.g., using `export AzureSignalRConnectionString__serviceUri=...` in bash/zsh).
  • Clarify how environment variable naming conventions (double underscore vs colon) map to Linux shells and configuration files.
  • Include instructions for configuring identity-based connections in Linux environments, such as using `.env` files or direct environment variable exports.
  • Mention Linux-native tools or editors (e.g., VS Code on Linux, Azure CLI) alongside Windows-centric tools.
  • Provide parity in local development instructions for Linux and macOS users, including file paths and shell commands.
GitHub Create Pull Request
← Previous Page 30 of 41 Next →