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 701-725 of 1023 flagged pages
Azure Functions Configure Durable Functions app with managed identity ...urable/durable-functions-configure-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Microsoft-centric tools and workflows (Visual Studio, Azure CLI, Azure portal) and omitting explicit Linux-specific instructions or examples. All configuration steps and screenshots assume use of the Azure portal and Microsoft developer tools, with no mention of Linux command-line alternatives or cross-platform considerations. There are no PowerShell-specific examples, but the documentation implicitly prioritizes Windows/Microsoft environments and does not provide parity for Linux users.
Recommendations
  • Add explicit instructions for Linux users, such as using Azure CLI commands for role assignment and app configuration instead of relying solely on the Azure portal UI.
  • Include examples of configuring local development environments on Linux, such as using environment variables and JSON configuration files from the Linux shell.
  • Reference cross-platform editors (e.g., VS Code) and clarify steps that work identically on Linux and macOS.
  • Provide screenshots or terminal output examples from Linux environments where relevant.
  • Mention any differences or considerations for Linux users when using Azurite or other local emulators.
GitHub Create Pull Request
Azure Functions Durable entities - Azure Functions .../azure-functions/durable/durable-functions-entities.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows/.NET-first bias by providing all code examples in .NET (C#), JavaScript, and Python, but omits any mention of Linux-specific tools, shell commands, or platform differences. The examples and explanations are heavily oriented toward .NET, which is historically associated with Windows, and there is no discussion of how to use Durable Entities from Linux environments, nor any parity guidance for Linux users. There are no PowerShell examples, but also no bash or Linux CLI examples. The documentation assumes the reader is using .NET and Visual Studio, which are more common on Windows, and does not address Linux workflows or tooling.
Recommendations
  • Add explicit guidance for Linux users, such as how to set up Durable Functions and entities using Linux-native tools (e.g., Azure CLI, VS Code on Linux, bash scripting).
  • Include examples or notes on running Durable Functions in Linux containers, WSL, or on native Linux hosts.
  • Mention cross-platform development environments and how to achieve parity between Windows and Linux, especially for .NET development.
  • Clarify any platform-specific requirements or limitations (e.g., file paths, environment variables, deployment steps) for Linux users.
  • Provide links to Linux-specific documentation or quickstarts where relevant.
GitHub Create Pull Request
Azure Functions Choosing an orchestration framework ...rable-task-scheduler/choose-orchestration-framework.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. In the Durable Functions quickstart table, the PowerShell example is listed alongside other languages, but there is no explicit mention of Linux shell equivalents (e.g., Bash). Additionally, the documentation does not mention Linux-specific development tools or patterns, nor does it provide parity for Linux command-line usage. While most examples are cross-platform (e.g., .NET, Python, JavaScript, Java), the inclusion of PowerShell without Bash or Linux shell examples, and the lack of explicit Linux development instructions, suggests a subtle Windows-first orientation.
Recommendations
  • Add Linux shell (Bash) quickstart examples alongside PowerShell for Durable Functions.
  • Explicitly mention cross-platform development environments and tools (e.g., VS Code on Linux, Bash terminals).
  • Clarify that all SDKs and frameworks are supported on both Windows and Linux, and provide instructions for both platforms where relevant.
  • Include troubleshooting or setup notes for Linux users, especially for local development and deployment scenarios.
  • Ensure parity in sample code and walkthroughs for Linux users, including containerization and orchestration on Linux-native platforms.
GitHub Create Pull Request
Azure Functions Event-driven Scaling in Azure Functions .../main/articles/azure-functions/event-driven-scaling.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias. In the 'Limit scale-out' section, both Azure CLI and Azure PowerShell examples are provided, but PowerShell is given its own tab and is presented directly after CLI, with no mention of Linux-specific tools or shell scripting. Additionally, in the 'Scale-in behaviors' section, a specific note is made about 'apps running on Windows in a Consumption plan', with no equivalent mention for Linux. There are no Linux-specific examples, nor is Bash or other Linux shell scripting referenced. The documentation does not mention Linux hosting or platform-specific behaviors outside of the Windows note.
Recommendations
  • Add explicit Bash or Linux shell examples alongside Azure CLI and PowerShell, especially for configuration and management tasks.
  • Clarify whether scale-in behaviors or other features differ for Linux-hosted function apps, and document any platform-specific considerations.
  • When mentioning platform-specific behaviors (such as drain mode for Windows), include equivalent information for Linux or state if there are no differences.
  • Consider adding a section or note on cross-platform support, highlighting parity between Windows and Linux hosting for Azure Functions.
GitHub Create Pull Request
Azure Functions Tutorial: Add Azure OpenAI text completions to your functions in Visual Studio Code ...zure-functions/functions-add-openai-text-completion.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Visual Studio Code and workflows typical of Windows environments, such as using Azurite and Core Tools, without mentioning Linux-specific alternatives or considerations. Steps like starting Azurite and running the function app are described generically but implicitly assume a Windows setup (e.g., use of F5 for debugging, Ctrl+C for stopping processes), and there is no mention of Linux shell commands, terminal differences, or platform-specific troubleshooting. There are no explicit Linux or macOS examples or notes, and no mention of platform-specific installation or usage patterns for Azurite, .NET Core CLI, or Azure Functions Core Tools.
Recommendations
  • Add explicit instructions or notes for Linux and macOS users, including terminal commands and differences in keyboard shortcuts (e.g., replacing F5 with appropriate shell commands).
  • Include Linux/macOS installation steps for Azurite, .NET Core CLI, and Azure Functions Core Tools, or link to platform-specific guides.
  • Mention any platform-specific issues or troubleshooting tips, such as permissions, file paths, or environment variable configuration.
  • Provide alternative workflows for starting Azurite and running/debugging the function app on Linux/macOS (e.g., using npm or shell commands instead of VS Code UI).
  • Ensure that all code and configuration examples are platform-agnostic, or provide variants where necessary.
GitHub Create Pull Request
Azure Functions Azure SQL trigger for Functions ...zure-functions/functions-bindings-azure-sql-trigger.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias. SQL Server and Azure SQL are inherently Windows-centric technologies, but the documentation reinforces this by listing Windows-based tools (Visual Studio Code, Azure Data Studio, SQL Server Management Studio) as the only examples for running SQL queries. There is no mention of Linux-native SQL tools (such as sqlcmd, DBeaver, or command-line alternatives) for setup or management. Additionally, configuration examples (local.settings.json, host.json) are presented in a way that assumes familiarity with Windows-style development environments, and the connection string documentation references .NET APIs, which are more common in Windows environments.
Recommendations
  • Add references to Linux-native SQL tools (e.g., sqlcmd, DBeaver, SQuirreL SQL, or command-line interfaces) in the 'Set up change tracking' section.
  • Clarify that all SQL setup steps can be performed from Linux, macOS, or Windows environments, and provide examples or links for cross-platform tooling.
  • When referencing configuration files (local.settings.json, host.json), note that these files are used in both Windows and Linux environments and provide guidance for Linux shell usage if relevant.
  • Where .NET APIs or tooling are referenced, mention equivalent cross-platform SDKs or libraries if available.
GitHub Create Pull Request
Azure Functions Model context protocol bindings for Azure Functions ...ain/articles/azure-functions/functions-bindings-mcp.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by only providing an Azure CLI example for retrieving the system key, without mentioning Linux-specific considerations or alternative shell commands. There is no explicit mention of Linux tools, nor are there examples using Bash or other Linux-native environments. The documentation also references Visual Studio Code and Azure Functions Core Tools, which are cross-platform, but does not clarify Linux usage or provide parity in examples.
Recommendations
  • Include explicit instructions and examples for Linux environments, such as using Bash or zsh.
  • Clarify that Azure CLI commands work on both Windows and Linux, and provide sample commands for both platforms.
  • Add a note or section on installing and running Azure Functions Core Tools on Linux, including any platform-specific prerequisites.
  • Provide parity in examples for retrieving keys or configuring MCP servers, such as using curl or wget for HTTP requests in Linux.
  • Ensure that any referenced tools (e.g., Visual Studio Code) are described as cross-platform, and provide links to Linux installation guides where relevant.
GitHub Create Pull Request
Azure Functions Azure OpenAI Semantic Search Input Binding for Azure Functions ...ions/functions-bindings-openai-semanticsearch-input.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides language-specific examples for C#, Java, JavaScript, TypeScript, Python, and PowerShell. However, the PowerShell example is the only shell scripting example provided, which is strongly associated with Windows environments. There are no equivalent examples for Linux-native shells such as Bash or for Linux-specific configuration patterns. Additionally, the configuration section for PowerShell references the use of function.json, which is standard for Azure Functions but does not mention Linux-specific deployment or scripting considerations. There is no explicit Windows-first ordering, but the presence of PowerShell without Bash or Linux shell examples suggests a bias toward Windows tooling.
Recommendations
  • Add example usage for Bash or other Linux-native shells to provide parity with the PowerShell example.
  • Include notes or examples for Linux-specific deployment or scripting scenarios, such as using Azure Functions with Bash or Python on Linux.
  • Clarify that the configuration and usage patterns apply equally to Linux and Windows environments, or highlight any differences.
  • If PowerShell is shown, provide equivalent Bash scripts for common tasks (such as invoking the function or managing configuration files) to ensure Linux users are equally supported.
GitHub Create Pull Request
Azure Functions Azure Functions SignalR Service bindings .../azure-functions/functions-bindings-signalr-service.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing configuration patterns (such as environment variable naming conventions using colons) that are more typical of Windows and .NET environments, without explicitly providing Linux-specific equivalents or examples. There is also a lack of explicit Linux or cross-platform command-line examples (e.g., Bash, CLI), and the configuration file references (like local.settings.json) are presented without clarifying platform differences. No PowerShell-specific examples are present, but the overall guidance assumes a Windows-centric environment.
Recommendations
  • Add explicit Linux/macOS examples for environment variable configuration, showing how to set variables in Bash/zsh and how to handle double underscores versus colons in environment variable names.
  • Clarify any platform-specific differences in configuration files (e.g., local.settings.json) and how they are used on Linux versus Windows.
  • Include cross-platform command-line instructions (such as Azure CLI or Bash) for retrieving connection strings and setting environment variables.
  • Ensure that references to environment variable naming conventions explain both Windows (.NET) and Linux (POSIX) approaches, especially regarding the use of colons and double underscores.
GitHub Create Pull Request
Azure Functions Manually run a non HTTP-triggered Azure Functions ...les/azure-functions/functions-manually-run-non-http.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily references the Azure portal and Azure CLI for key management and function invocation, which are cross-platform. However, there is a subtle Windows bias: the page does not provide any Linux-specific examples or mention Linux tools (such as curl or wget) for making HTTP requests, nor does it reference Linux-specific patterns or troubleshooting. The instructions and screenshots are portal-centric and do not demonstrate parity for Linux users who may prefer command-line tools or alternative workflows.
Recommendations
  • Add explicit examples using Linux command-line tools such as curl for making the HTTP POST request, including sample commands.
  • Include screenshots or instructions for accessing logs and keys via the command line, suitable for Linux environments.
  • Mention that the Azure CLI is cross-platform and provide installation instructions for Linux users.
  • Ensure that any references to HTTP test tools include both Windows and Linux options (e.g., Postman, curl, httpie).
  • Consider adding a section or tab for Linux-specific workflows to demonstrate parity and inclusivity.
GitHub Create Pull Request
Azure Functions Azure Functions runtime versions overview ...ob/main/articles/azure-functions/functions-versions.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows-centric tools (Visual Studio) and patterns before mentioning cross-platform or Linux alternatives. For example, instructions for changing the runtime version and local development begin with Visual Studio (Windows) before mentioning Visual Studio Code and Azure Functions Core Tools, which are cross-platform. There are no explicit Linux-specific examples or instructions, and no mention of Linux command-line patterns or tools beyond the generic Azure Functions Core Tools reference.
Recommendations
  • Add explicit Linux examples for changing runtime versions, such as using Azure CLI or editing settings via the portal on Linux-hosted apps.
  • Provide parity in local development instructions by including Linux-specific steps (e.g., using bash, zsh, or Linux file paths) alongside Windows/Visual Studio instructions.
  • Mention cross-platform tools (Azure Functions Core Tools, Visual Studio Code) before Windows-only tools (Visual Studio) to avoid Windows-first ordering.
  • Include troubleshooting or configuration notes relevant to Linux environments, such as permissions or environment variable differences.
  • Ensure that all code snippets and instructions are platform-agnostic or have variants for both Windows and Linux where differences exist.
GitHub Create Pull Request
Azure Functions Memory profiling of Python apps in Azure Functions ...es/azure-functions/python-memory-profiler-reference.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias in the local development setup instructions. Windows PowerShell is mentioned first when instructing users to open a shell, and Windows-specific commands (such as 'py -m venv .venv' and '.venv\Scripts\Activate.ps1') are listed before their Linux equivalents. The phrase 'Open a Windows PowerShell or any Linux shell as you prefer' puts Windows first, and the examples for creating and activating the virtual environment start with Windows commands. However, Linux equivalents are present and described, and the rest of the documentation is platform-neutral.
Recommendations
  • Present Linux and Windows instructions in parallel, using tabs or side-by-side formatting, so neither platform is prioritized.
  • Use neutral phrasing such as 'Open a terminal (Windows PowerShell or Linux shell)' rather than 'Open a Windows PowerShell or any Linux shell as you prefer'.
  • Alternate the order of Windows and Linux commands, or use platform tabs to avoid implicit prioritization.
  • Explicitly mention macOS where relevant, as its commands often match Linux.
  • Ensure screenshots and file paths use platform-neutral or platform-specific examples as appropriate.
GitHub Create Pull Request
Azure Functions Respond to database changes in Azure SQL Database using Azure Functions ...ure-functions/scenario-database-changes-azure-sqldb.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing Visual Studio Code and its extensions, using Windows-centric terminology (e.g., 'SQL Server explorer', 'Select Top 1000'), and omitting any mention of Linux-native tools or workflows for connecting to Azure SQL Database or running Azure Functions locally. There are no examples using Linux command-line tools (such as sqlcmd), nor are alternative editors or database clients suggested for Linux users.
Recommendations
  • Add instructions and examples for connecting to Azure SQL Database using cross-platform or Linux-native tools such as sqlcmd, Azure Data Studio, or the Azure CLI.
  • Include alternative workflows for running and testing Azure Functions locally on Linux, such as using the terminal and Azure Functions Core Tools directly, outside of Visual Studio Code.
  • Mention and provide examples for database operations (INSERT/UPDATE) using command-line tools available on Linux, not just via the Visual Studio Code SQL Server extension.
  • Clarify that Visual Studio Code and its extensions are available on Linux and macOS, or suggest alternative editors if appropriate.
  • Ensure that all steps referencing UI actions (e.g., right-clicking in SQL Server explorer) have equivalent command-line instructions for Linux users.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by only providing an Azure CLI example for retrieving the system key, without mentioning Linux-specific alternatives or shell differences. There are no PowerShell-heavy sections, but the lack of Linux/macOS-specific instructions or examples (such as bash commands or cross-platform notes) means Linux users may need to infer or adapt steps themselves.
Recommendations
  • Provide explicit bash/zsh examples for key retrieval and other CLI operations, clarifying any differences in output formatting or environment variables.
  • Add notes or sections highlighting cross-platform compatibility of Azure Functions Core Tools, including installation and usage on Linux/macOS.
  • When referencing Visual Studio Code or other tools, mention their availability and usage on Linux/macOS, and provide links to relevant documentation.
  • Ensure that all command-line examples are tested and documented for both Windows and Linux environments, including any required dependencies or setup steps.
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-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 Windows-first bias in several areas. Instructions for creating and managing Azure Functions apps mention Windows-centric tools (Visual Studio, Visual Studio Code) and patterns before Linux alternatives. The section on pinning to a specific minor runtime version explicitly states that the process differs between Windows and Linux, but does not provide Linux-specific instructions or examples. There are no Linux command-line examples (e.g., Bash, shell scripts), and the documentation does not mention Linux-native development environments or package managers. Overall, Linux parity is lacking in practical guidance and examples.
Recommendations
  • Add explicit Linux instructions and examples where processes differ, such as for pinning to a specific minor runtime version.
  • Include Linux-native development environments (e.g., JetBrains Rider, VS Code on Linux) and package managers (e.g., apt, yum) in installation and setup sections.
  • Provide Bash or shell script examples alongside PowerShell or Windows command-line instructions.
  • Ensure that references to tools and workflows do not assume a Windows environment by default.
  • Clarify cross-platform compatibility for all steps, especially for local development and deployment.
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-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, and references Windows-centric tools and patterns (e.g., PowerShell cmdlets like Get-Date, New-Guid). PowerShell is included as a first-class language tab, and guidance is given for using PowerShell-specific APIs. However, there is no explicit prioritization of Windows or PowerShell over Linux or other platforms, and Linux-specific tools or shell examples are not present. The documentation does not mention Linux shell equivalents (e.g., Bash, sh) or provide examples for those environments, which may leave Linux users without direct parity in guidance.
Recommendations
  • Add Linux shell (e.g., Bash) examples alongside PowerShell for relevant scenarios, such as environment variable access or date/time retrieval.
  • Explicitly mention cross-platform considerations when discussing environment variables, file system access, or command-line tools.
  • Clarify that PowerShell examples are applicable on Linux where PowerShell Core is available, and provide alternative examples for native Linux shells.
  • Ensure that any references to Windows-specific APIs or tools are balanced with Linux equivalents or alternatives.
  • Consider adding a section or note about platform neutrality and how Durable Functions constraints apply regardless of OS.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page for Durable Entities in Azure Functions does not show explicit Windows bias in the form of Windows-only tools, PowerShell-heavy examples, or exclusive mention of Windows patterns. However, there is a subtle 'windows_first' bias: the .NET/C# examples (which are most commonly associated with Windows development) are presented first and in greatest detail, including advanced features like class-based syntax, dependency injection, and entity coordination. Linux-specific patterns, tools, or shell commands are not mentioned, and there are no explicit Linux examples or parity notes. Python and JavaScript examples are present, but less detailed and lack coverage of advanced features. There are no PowerShell examples, but this is clearly noted as unsupported.
Recommendations
  • Add explicit notes or sections about cross-platform development, including any OS-specific considerations for running Durable Entities on Linux (e.g., file system, permissions, deployment differences).
  • Ensure parity in example depth: provide equally detailed Python and JavaScript examples for advanced features such as entity coordination, dependency injection, and locking.
  • Include Linux shell (bash) or CLI examples where relevant, especially in deployment or operational contexts.
  • If certain features are only available or best supported on Windows/.NET, clearly document any limitations or workarounds for Linux users.
  • Consider reordering example pivots so that non-Windows languages (Python, JavaScript) are not always after .NET/C#.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents .NET (a Windows-centric technology) package instructions first and in detail, including both in-process and isolated models, before mentioning other language SDKs. PowerShell, another Windows-centric language, is given a dedicated note and migration guide reference. There are no explicit Linux examples, nor are Linux-specific tools or patterns discussed. The order and emphasis may suggest a Windows bias, especially for users seeking parity or guidance for Linux environments.
Recommendations
  • Add explicit instructions or examples for Linux environments, such as referencing package installation via Linux-native tools (e.g., apt, yum, pip for Python, npm for Node, etc.).
  • Include notes or sections on cross-platform compatibility, highlighting any differences or considerations for Linux users.
  • Balance the order of presentation by rotating or grouping language runtimes by popularity or platform neutrality, rather than leading with .NET.
  • Provide examples of configuration or usage in Linux shells (e.g., bash) alongside PowerShell where relevant.
  • Clarify that all SDKs/packages are cross-platform where applicable, and call out any platform-specific limitations.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates subtle Windows bias by listing PowerShell as a primary language in quickstart tables before Linux-native alternatives, and by referencing Windows-centric tools (PowerShell) in parity with other languages. There is no explicit mention of Linux-specific tools, shell environments, or development patterns, and examples for Linux command-line usage (e.g., Bash) are missing. The documentation does not address platform-specific considerations for Linux users, such as differences in local development, deployment, or orchestration monitoring.
Recommendations
  • Add Linux/Bash-specific quickstart examples alongside PowerShell, ensuring parity in instructions for Linux users.
  • Explicitly mention cross-platform compatibility and provide guidance for Linux environments (e.g., using Bash, zsh, or other shells).
  • Include references to Linux-native tools and workflows (such as CLI commands for deployment and orchestration monitoring) in addition to or before Windows/PowerShell equivalents.
  • Clarify any platform-specific requirements or differences in local development, emulator usage, and dashboard access for Linux users.
  • Reorder language and tool listings to avoid implicit prioritization of Windows/PowerShell over Linux-native options.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias in its treatment of platform-specific instructions. In the virtual environment activation section, the Windows (PowerShell) example is presented last, but it is the only example that specifies the shell (PowerShell), while Linux and macOS use bash. The instructions for activating the virtual environment on Windows use PowerShell syntax, which may not be familiar to users of other shells on Windows. Additionally, throughout the document, there is no explicit mention of Linux-specific tools or patterns, nor are there examples using Linux-native editors or shells. The overall workflow is centered around Visual Studio Code and its integrated terminal, which is cross-platform, but the documentation does not provide parity for Linux-specific scenarios or alternative tools.
Recommendations
  • Provide explicit parity for Linux and macOS users by including shell-specific instructions for activating virtual environments (e.g., bash, zsh, fish) on all platforms, including Windows Command Prompt.
  • Add a note clarifying which shell is being used for each platform, and provide alternative commands for common shells on Windows (e.g., Command Prompt: `.venv\Scripts\activate.bat`).
  • Include troubleshooting tips for Linux users, such as dealing with permissions or Python path issues.
  • Mention alternative editors or tools that are popular on Linux, such as Vim or Emacs, or provide links to CLI-based workflows for users who prefer not to use Visual Studio Code.
  • Ensure that any referenced tools (e.g., Azurite, Azure Functions Core Tools) have installation instructions for Linux, and link to those sections.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. In the section on limiting scale-out for Consumption/Premium plans, both Azure CLI and Azure PowerShell examples are provided, but PowerShell is given equal prominence, which is a Windows-centric tool. Additionally, in the scale-in behaviors section, a specific note is made for 'apps running on Windows in a Consumption plan,' with no equivalent mention for Linux. There are no Linux-specific examples, nor are Linux tools (such as Bash scripts or Linux-specific configuration notes) referenced. All command-line examples use Azure CLI, which is cross-platform, but PowerShell is highlighted as an alternative, reinforcing Windows familiarity.
Recommendations
  • Add explicit Linux/Bash examples alongside PowerShell, especially in sections where configuration via command line is shown.
  • Clarify platform-specific behaviors for both Windows and Linux (e.g., scale-in behaviors), not just Windows.
  • If platform differences exist (such as drain mode defaults), document them for Linux as well.
  • Consider mentioning cross-platform tools first (Azure CLI) and move PowerShell examples to a secondary position or a dedicated tab for Windows users.
  • Where possible, include notes or examples for Linux users, such as using environment variables, file paths, or shell scripting relevant to Linux.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-azure-sql-trigger.md ...zure-functions/functions-bindings-azure-sql-trigger.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias in its tooling references and ordering. In the 'Set up change tracking' section, Windows-centric tools (Visual Studio Code, Azure Data Studio, SQL Server Management Studio) are mentioned exclusively and before any Linux alternatives. There is no mention of Linux-native SQL tools (e.g., sqlcmd, DBeaver, or Azure CLI). However, code examples for all supported languages (C#, Java, PowerShell, JavaScript, Python) are provided, and none are exclusively Windows-specific. There are no PowerShell-heavy or missing Linux example biases, but the documentation assumes the use of Windows tools for setup and local development.
Recommendations
  • Add references to Linux-native SQL tools (e.g., sqlcmd, Azure CLI, DBeaver) alongside Windows tools in the 'Set up change tracking' section.
  • Explicitly state that all SQL setup steps can be performed on Linux, macOS, or Windows, and provide example commands or tool links for each platform.
  • Where local.settings.json and host.json are discussed, clarify that these files and workflows are cross-platform and provide guidance for Linux/macOS users if any steps differ.
  • Consider including a brief section or note on cross-platform development environments for Azure Functions, mentioning both Windows and Linux options.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-cache-trigger-redispubsub.md ...ctions/functions-bindings-cache-trigger-redispubsub.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 C#, Java, JavaScript, Python, and PowerShell. However, the inclusion of PowerShell as a primary example language and the use of PowerShell scripts for Azure Functions can indicate a Windows bias, as PowerShell is predominantly a Windows-centric tool. Additionally, references to connection strings in the format '<cacheName>.redis.cache.windows.net:6380,password...' and the use of .NET-centric terminology (such as ILogger and ExecutionContext) may reinforce a Windows/Azure ecosystem bias. There are no explicit Linux shell (bash) or cross-platform CLI examples, and no mention of Linux-specific patterns or tools.
Recommendations
  • Add bash or cross-platform shell examples for triggering/test scenarios, especially in the context of local development or testing.
  • Include notes or examples for Linux users, such as using Azure Functions Core Tools on Linux, or how to run/test these triggers in a Linux environment.
  • Provide parity in scripting examples: if PowerShell is shown, also show equivalent bash scripts for common operations.
  • Clarify that Azure Functions and Redis triggers are fully supported on Linux-hosted environments, and provide links or guidance for Linux deployment.
  • Avoid using Windows-specific terminology or tools as the default or only option; ensure examples and instructions are platform-neutral where possible.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-openai-textcompletion-input.md ...ions/functions-bindings-openai-textcompletion-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 technology. Powershell is given a dedicated section with both code and configuration examples, including references to function.json, which is a Windows-style configuration pattern. There is no explicit mention of Linux shell equivalents (e.g., Bash) or cross-platform scripting alternatives. The documentation does not provide Linux-specific examples or guidance, and Powershell is the only shell scripting language featured.
Recommendations
  • Add Bash or other Linux shell examples alongside Powershell to ensure parity for Linux users.
  • Clarify cross-platform support for the input binding, including any differences in setup or usage on Linux vs. Windows.
  • Provide explicit instructions or notes for Linux users, such as environment variable configuration or file system differences.
  • Ensure that references to configuration files (like function.json) include notes about their location and usage on both Windows and Linux platforms.
  • Consider adding troubleshooting or FAQ sections for common Linux-specific issues.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-openai-embeddings-input.md ...unctions/functions-bindings-openai-embeddings-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 dedicated examples and configuration details for PowerShell, a Windows-centric scripting language, including explicit references to function.json and run.ps1 files. No equivalent examples or configuration guidance are given for Linux shell environments (e.g., Bash), nor is there mention of Linux-specific tooling or patterns. This creates a bias toward Windows users and PowerShell workflows.
Recommendations
  • Add equivalent examples for Linux shell environments (e.g., Bash scripts) alongside PowerShell examples.
  • Include configuration and usage instructions relevant to Linux users, such as file permissions, environment variable setup, and shell script invocation.
  • Clarify cross-platform compatibility of the binding and provide guidance for both Windows and Linux users in all relevant sections.
  • Where PowerShell is referenced, offer Bash or other Linux shell alternatives, especially for automation and scripting tasks.
GitHub Create Pull Request
← Previous Page 29 of 41 Next →