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 126-150 of 1023 flagged pages
Azure Functions Respond to database changes in Azure SQL Database using Azure Functions ...ure-functions/scenario-database-changes-azure-sqldb.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively using Visual Studio Code and its extensions for all examples and workflows, referencing Windows-centric tools (such as SQL Server extension and Azure Functions Core Tools), and omitting any mention of Linux-specific alternatives or command-line workflows. There are no examples or instructions for using Linux-native editors, CLI-only approaches, or connecting to Azure SQL Database from Linux environments. The documentation also uses keyboard shortcuts and UI patterns that are primarily familiar to Windows users, with only minor references to macOS.
Recommendations
  • Include explicit instructions and examples for Linux users, such as using Azure Developer CLI (azd) directly from the terminal, and connecting to Azure SQL Database using cross-platform tools like sqlcmd or Azure Data Studio.
  • Provide alternative workflows that do not require Visual Studio Code, such as using CLI commands for provisioning, deploying, and testing functions.
  • Mention and demonstrate the use of Linux-compatible SQL clients and editors, and clarify any platform-specific requirements or limitations.
  • Add keyboard shortcut references for Linux environments and clarify any differences in UI or workflow.
  • Ensure that all steps and tools are validated and documented for Linux, and highlight any platform-specific caveats.
GitHub Create Pull Request
Azure Functions Respond to database changes in Azure Cosmos DB using Azure Functions ...-functions/scenario-database-changes-azure-cosmosdb.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 several signs of Windows bias. Windows-specific instructions (such as PowerShell commands and references to Windows command prompt) are presented alongside or before Linux/macOS equivalents. The use of PowerShell for script permissions is emphasized, while Linux/macOS instructions are limited to a simple chmod command. Troubleshooting advice is focused on Windows (e.g., issues with WSL Bash), and there is a lack of parity in examples or troubleshooting steps for Linux users. The documentation also references Windows tools and patterns (e.g., pwsh, func.exe) without providing equivalent Linux details.
Recommendations
  • Ensure Linux/macOS instructions are given equal prominence and detail as Windows instructions, including troubleshooting steps and tool usage.
  • Provide explicit Linux/macOS examples for all commands, including alternatives to PowerShell (e.g., bash scripts, terminal commands).
  • Avoid assuming Windows as the default environment; use neutral language and structure instructions so that Linux/macOS users are not secondary.
  • Include troubleshooting tips for Linux/macOS environments, such as common issues with permissions, shell configuration, or dependencies.
  • Reference cross-platform tools and commands (e.g., func CLI, azd) with clear notes about differences in usage or behavior across operating systems.
GitHub Create Pull Request
Azure Functions How to target Azure Functions runtime versions ...b/main/articles/azure-functions/set-runtime-version.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 moderate Windows bias. Windows and PowerShell examples are presented alongside Azure CLI and portal instructions, but Windows-specific tools (PowerShell cmdlets, Visual Studio behaviors) are described in detail, while Linux-specific instructions are less prominent and sometimes limited to Azure CLI. The Windows platform is often discussed before Linux, and some features (such as pinning via portal or PowerShell) are unavailable or not documented for Linux. There is also an absence of Linux shell (bash) or scripting examples, and Linux-specific limitations (e.g., Consumption plan pinning) are mentioned but not deeply explained.
Recommendations
  • Ensure Linux instructions are presented with equal prominence and detail as Windows instructions, including step-by-step guides for common tasks.
  • Add Linux shell (bash) scripting examples where PowerShell scripts are provided for Windows.
  • Clarify limitations and alternatives for Linux users, such as the inability to pin runtime versions in the portal or via PowerShell, and provide guidance for these scenarios.
  • Where features are unavailable on Linux (e.g., portal or PowerShell pinning), explicitly state this and suggest workarounds or alternatives.
  • Consider presenting platform-specific instructions in parallel (side-by-side tabs or sections) rather than Windows-first ordering.
  • Expand documentation on Linux-specific settings and behaviors, such as the use of linuxFxVersion, with more real-world examples and troubleshooting tips.
GitHub Create Pull Request
Azure Functions Storage considerations for Azure Functions ...ain/articles/azure-functions/storage-considerations.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific hosting plans and configuration settings are frequently mentioned before Linux equivalents, and PowerShell examples and features are highlighted (such as managed dependencies in PowerShell and Windows-only Consumption plan details). Linux-specific instructions and examples are less prominent, sometimes relegated to later sections or marked as exceptions. Some features (like mounting Azure Files) are described as Linux-only, but Windows parity or alternatives are not discussed. The use of Windows-centric tools and terminology (e.g., Visual Studio, PowerShell) is prevalent, while Linux development workflows (such as VS Code, bash, or Linux CLI) are underrepresented or missing.
Recommendations
  • Ensure that Linux hosting plans and configuration settings are described alongside Windows equivalents, not as exceptions or afterthoughts.
  • Provide Linux-specific examples and instructions for all major features, including deployment, configuration, and troubleshooting.
  • Include CLI/bash examples and workflows in addition to PowerShell, especially for mounting file shares and managing storage.
  • Highlight Linux development tools (such as VS Code, bash scripting) and workflows where appropriate.
  • Clarify feature parity between Windows and Linux, noting any limitations or differences explicitly.
  • Where features are Windows-only (e.g., portal editing, log streaming), suggest Linux alternatives or workarounds.
GitHub Create Pull Request
Azure Functions Update Language Versions in Azure Functions ...n/articles/azure-functions/update-language-versions.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Instructions and examples for updating language versions in Azure Functions are consistently presented with Windows options first, both in Azure portal and Azure CLI sections. Windows-specific tools and patterns (such as .NET SDK, Visual Studio Code settings, and Windows-specific CLI flags) are described in detail, while Linux equivalents are less emphasized or deferred to later sections. Some examples, especially for Python, explicitly state that Windows is unsupported and redirect users to Linux, but Linux instructions are not always presented with equal clarity or prominence.
Recommendations
  • Present Linux and Windows instructions side-by-side or in parallel, rather than defaulting to Windows-first ordering.
  • Provide equally detailed Linux-specific examples and troubleshooting steps, including references to Linux development tools and patterns (e.g., VS Code settings for Linux, Linux package managers).
  • Ensure that all language and platform pivots (especially for Python and Node.js) include complete, step-by-step Linux instructions, not just notes redirecting users.
  • Highlight any differences in workflow or limitations for Linux users early in the documentation, rather than as footnotes or afterthoughts.
  • Where possible, use neutral, cross-platform CLI examples and avoid assuming Windows as the default operating system.
GitHub Create Pull Request
Azure Functions Guide for running C# Azure Functions in an isolated worker process ...icles/azure-functions/dotnet-isolated-process-guide.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and configuration patterns (such as Visual Studio, PowerShell, and Windows-specific CLI commands) are mentioned before or more prominently than their Linux equivalents. Examples for checking and setting process architecture, debugging, and deployment often default to Windows, with Linux instructions sometimes relegated to tabs or brief mentions. PowerShell and Visual Studio are frequently referenced, while Linux alternatives (e.g., Bash, VS Code, Azure CLI) are less emphasized or missing in some sections. Some examples and guidance (e.g., ReadyToRun, debugging, deployment requirements) are Windows-centric or lack equivalent Linux detail.
Recommendations
  • Ensure all CLI and configuration examples are provided for both Windows and Linux, with equal prominence and detail.
  • When listing tools or getting started options, present cross-platform tools (e.g., VS Code, Azure CLI) before or alongside Windows-specific ones.
  • Add Linux/Bash equivalents for PowerShell commands and Windows-specific instructions, especially in deployment, debugging, and configuration sections.
  • Where features or behaviors differ between Windows and Linux (e.g., ReadyToRun, process architecture), clearly document both scenarios and provide guidance for Linux users.
  • Review all code and command snippets to ensure Linux users are not required to infer or adapt Windows-centric instructions.
  • Highlight Azure CLI and VS Code as first-class options for Linux/macOS users, and avoid assuming Visual Studio or PowerShell as defaults.
GitHub Create Pull Request
Azure Functions Sub-orchestrations for Durable Functions - Azure ...ctions/durable/durable-functions-sub-orchestrations.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page includes a prominent PowerShell-specific note and full PowerShell code samples alongside other languages. PowerShell is a Windows-centric tool, and its inclusion (with a special note and examples) signals a bias toward Windows environments. There is no mention of Linux shell equivalents (e.g., Bash), nor any discussion of cross-platform scripting options. The PowerShell note appears before any Linux or cross-platform considerations, and no Linux-specific guidance or parity notes are present.
Recommendations
  • Add notes or examples for Linux users, such as Bash or cross-platform shell scripting, where relevant.
  • Clarify that PowerShell Core is cross-platform, if applicable, and provide guidance for Linux users on installing and using it.
  • Balance platform-specific notes by including any Linux/macOS caveats or SDK differences if they exist.
  • Explicitly mention that the Durable Functions SDKs and orchestration features are available and supported on Linux, and link to relevant Linux setup guides.
  • If PowerShell is required for certain features, state whether PowerShell Core on Linux is supported and provide installation instructions.
GitHub Create Pull Request
Azure Functions Work with access keys in Azure Functions .../main/articles/azure-functions/function-keys-how-to.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing access keys in Azure Functions. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and detailed PowerShell scripts are included. There is no explicit mention of Linux shell scripting or Bash alternatives for REST API calls, nor are there examples using curl or other cross-platform tools. The CLI examples are stated to run in Azure Cloud Shell (Bash), but users are told to modify them for Windows terminals, suggesting a Windows-first orientation. No Linux-specific or cross-platform scripting examples are provided for REST API usage.
Recommendations
  • Add explicit Bash/curl examples for REST API calls to demonstrate Linux parity.
  • Clarify that Azure CLI commands work natively on Linux, macOS, and Windows, and provide any necessary platform-specific notes.
  • Include instructions or examples for using Azure CLI or REST API from Linux/macOS terminals, not just Azure Cloud Shell.
  • Reduce emphasis on PowerShell by making CLI/Bash examples primary, or at least present them before PowerShell.
  • Where PowerShell scripts are provided, offer equivalent Bash scripts for Linux/macOS users.
GitHub Create Pull Request
Azure Functions Bring dependencies and third-party libraries to Azure Functions ...icles/azure-functions/bring-dependency-to-functions.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-specific tools (e.g., ffmpeg.exe, PowerShell) are referenced or used in code examples, especially in the Java section. Windows paths and patterns (e.g., .exe extension, BASE_PATH usage) are presented without Linux equivalents or parity. PowerShell is mentioned as a method for uploading files, but Linux alternatives (such as SCP, rsync, or SFTP) are not discussed. In some cases, Linux-specific notes are relegated to side notes rather than being integrated into the main workflow, and Linux examples are not always provided alongside Windows ones.
Recommendations
  • Provide Linux-specific code examples and instructions alongside Windows ones, especially for file paths, executable names, and environment variables.
  • When referencing tools like ffmpeg, clarify differences in usage between Windows (.exe) and Linux (no extension), and provide examples for both.
  • Include Linux-native upload methods (e.g., SCP, rsync, SFTP) in addition to PowerShell and Azure CLI.
  • Avoid using Windows-centric paths (e.g., BASE_PATH, .exe) as defaults; instead, show both Windows and Linux conventions.
  • Ensure that any notes about Linux permissions (e.g., chmod) are integrated into the main workflow, not just as side notes.
  • Where possible, use cross-platform tools and patterns, or clearly indicate platform-specific steps.
GitHub Create Pull Request
Azure Functions Deployment technologies in Azure Functions ...s/azure-functions/functions-deployment-technologies.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-specific deployment technologies (e.g., FTPS, Local Git, Source Control) are called out as 'Windows-only' in the availability table, with Linux equivalents either missing or less emphasized. Examples and instructions often reference Visual Studio and Visual Studio Code (Windows-centric tools) before mentioning cross-platform or Linux-specific options. The Kudu/SCM site and remote build explanations are more detailed for Windows, while Linux instructions are less prominent and sometimes require additional manual configuration. Linux deployment methods (such as Docker container and external package URL) are described as exceptions or alternatives, rather than first-class options.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for deployment methods like FTPS, Local Git, and Source Control.
  • Ensure that Linux tools and workflows (e.g., Azure CLI, Core Tools, Docker) are mentioned first or equally with Windows tools in each section.
  • Clarify which deployment methods are available for Linux and provide parity where possible, or explain the rationale for any limitations.
  • Include more detailed Linux deployment walkthroughs, especially for remote build, trigger syncing, and storage configuration.
  • Highlight cross-platform tools and approaches (e.g., Azure CLI, Core Tools) before Windows-only tools (e.g., Visual Studio).
  • Add troubleshooting and best practices sections specifically for Linux deployments, similar to those provided for Windows.
GitHub Create Pull Request
Azure Functions Configure monitoring for Azure Functions .../main/articles/azure-functions/configure-monitoring.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is explicitly used for configuration examples, and Windows-centric tools (PowerShell, Visual Studio) are mentioned for setup and management. While Azure CLI is provided (which is cross-platform), PowerShell examples are given equal prominence, and Windows tools are referenced before their Linux equivalents or alternatives. There is no explicit mention of Linux-specific patterns, nor are Linux shell examples (e.g., Bash) provided alongside PowerShell. The documentation does not address Linux-specific caveats except in a single note about app settings with periods, and does not provide parity in example commands or tool recommendations for Linux users.
Recommendations
  • Provide Bash or shell script equivalents for all PowerShell examples, especially for configuration and app settings management.
  • Mention Linux-friendly tools (e.g., VS Code, Azure CLI) before or alongside Windows-centric tools like Visual Studio and PowerShell.
  • Add explicit instructions or examples for Linux users, including any platform-specific caveats or best practices.
  • Clarify cross-platform compatibility for all CLI commands and configuration steps, and highlight any differences in behavior or limitations on Linux.
  • Where screenshots or UI instructions are given, note any differences for Linux users (e.g., portal UI, environment variables).
GitHub Create Pull Request
Azure Functions Integration and automation platform options in Azure ...ctions/functions-compare-logic-apps-ms-flow-webjobs.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-centric tools (PowerShell, Visual Studio), and mentions them before or instead of Linux equivalents. Examples and management instructions frequently highlight PowerShell and Visual Studio, with limited or no mention of Linux-native tools or workflows. There are no explicit Linux shell (bash) examples, and Linux development environments are not discussed in parity with Windows ones.
Recommendations
  • Add explicit examples and instructions for Linux users, such as using Bash, Azure CLI, and VS Code on Linux.
  • Include Linux-native management tools and workflows alongside PowerShell and Visual Studio, and present them with equal prominence.
  • Provide sample scripts or walkthroughs for common Linux scenarios (e.g., deploying WebJobs or Functions from Linux, using bash scripts).
  • Clarify cross-platform support for all tools, and note any differences in experience between Windows and Linux.
  • Ensure that tables and lists mention Linux options (e.g., Azure CLI, bash, VS Code on Linux) before or alongside Windows tools.
GitHub Create Pull Request
Azure Functions How to disable functions in Azure Functions ...blob/main/articles/azure-functions/disable-function.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides examples for disabling Azure Functions using the Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric and is presented as a primary method alongside CLI. There are no Linux shell (bash) or scripting examples, nor is there mention of Linux-specific tools or workflows. The documentation also notes a Linux limitation (hyphens in function names) but does not offer Linux workarounds or alternatives. The ordering and emphasis on PowerShell and Portal (both Windows-oriented) suggest a Windows-first bias.
Recommendations
  • Add explicit bash/shell examples for Linux users, especially for CLI commands.
  • Clarify that Azure CLI works on both Windows and Linux, and recommend it as the preferred cross-platform method.
  • Include notes or alternatives for Linux users where PowerShell is not available or supported.
  • Mention Linux-native tools or scripting options where relevant.
  • Reorder examples to present CLI (cross-platform) before PowerShell, and explicitly address Linux workflows.
  • Provide troubleshooting or workaround guidance for Linux-specific limitations (e.g., function names with hyphens).
GitHub Create Pull Request
Azure Functions Bindings for Durable Functions - Azure .../azure-functions/durable/durable-functions-bindings.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page provides examples and configuration details for multiple languages, including PowerShell, which is primarily a Windows-centric tool. PowerShell examples are given equal prominence to other languages, and the configuration instructions reference Windows-specific tools (e.g., function.json and run.ps1 for PowerShell). The use of PowerShell as a first-class example, and the reliance on Windows-centric patterns (such as PowerShell scripts and function.json configuration), indicate a bias towards Windows environments. There is little to no mention of Linux-specific equivalents or considerations for running Durable Functions on Linux, especially for PowerShell users.
Recommendations
  • Add explicit notes or examples for running Durable Functions in Linux environments, especially for PowerShell users (e.g., using PowerShell Core on Linux, or alternatives).
  • Provide bash or shell script equivalents for configuration and invocation steps where PowerShell is used.
  • Clarify cross-platform compatibility for all tools and configuration files mentioned (e.g., function.json, run.ps1).
  • Ensure that Linux-native languages and tools (such as bash, zsh, or Python) are given equal prominence and that examples are provided for Linux workflows.
  • Where PowerShell is referenced, specify whether the instructions apply to PowerShell Core (cross-platform) or Windows PowerShell (Windows-only), and provide guidance for Linux users.
GitHub Create Pull Request
Azure Functions Develop Azure Functions using Visual Studio .../main/articles/azure-functions/functions-develop-vs.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on development using Visual Studio 2022, a Windows-centric IDE, with all examples and workflows assuming use of Visual Studio and its integrated tools. There are no instructions or examples for developing Azure Functions on Linux or macOS, nor for using cross-platform tools like VS Code or CLI workflows. Package installation is shown only with PowerShell commands, and remote debugging is explicitly stated as only supported on Windows. The use of Windows-specific dialogs, screenshots, and terminology further reinforces the Windows bias.
Recommendations
  • Add equivalent instructions and examples for developing Azure Functions using VS Code and Azure Functions Core Tools on Linux and macOS.
  • Include CLI-based workflows for project creation, binding addition, and publishing, using Bash and cross-platform commands.
  • Provide screenshots and walkthroughs for Linux/macOS environments, including file management and configuration steps.
  • Document remote debugging and monitoring options available for Linux-hosted function apps, or clarify platform limitations.
  • Present PowerShell and Bash/NPM examples side by side for package installation and other commands.
  • Explicitly mention platform support and limitations at the start of the article, and link to Linux/macOS guides where available.
GitHub Create Pull Request
Azure Functions Deploy a PyTorch model as an Azure Functions application ...n/articles/azure-functions/machine-learning-pytorch.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 moderate Windows bias. Windows-specific tools and patterns (such as 'py' launcher, PowerShell, registry edits) are mentioned frequently and sometimes before Linux equivalents. Troubleshooting advice is Windows-centric, and some commands (e.g., activating virtual environments, copying files) are shown for Windows shells (PowerShell, Cmd) alongside bash, but Windows-specific issues (like long path errors) are explained in detail while Linux/macOS issues are less covered. The use of Visual Studio Code (a cross-platform editor but often associated with Windows) is highlighted, and the 'py' launcher is referenced for Python version checks and script execution, which is not standard on Linux/macOS. Some troubleshooting and installation steps are missing Linux/macOS equivalents or deeper explanations.
Recommendations
  • Ensure troubleshooting advice covers Linux/macOS issues with equal detail (e.g., permissions, package manager errors, path length limits on Linux).
  • Present Linux/macOS examples before or alongside Windows examples, rather than after.
  • Avoid assuming the presence of the 'py' launcher; use 'python3' for Linux/macOS and clarify differences.
  • Include Linux/macOS-specific troubleshooting tips for common problems (e.g., venv activation issues, dependency installation errors).
  • Mention cross-platform editors other than Visual Studio Code, or clarify its cross-platform nature.
  • When referencing Windows registry edits, provide equivalent advice for Linux/macOS (e.g., handling long paths, file system limits).
  • Balance the depth of explanation for platform-specific errors and solutions.
GitHub Create Pull Request
Azure Functions Connect a function app to Azure SQL with managed identity and SQL bindings ...ctions-identity-access-azure-sql-with-managed-identity.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows, such as PowerShell and Azure Portal, and referencing them before or instead of Linux alternatives. Examples and instructions for enabling managed identity and interacting with Azure SQL are primarily given for Azure Portal, PowerShell, and Azure CLI, but there is little to no mention of Linux-specific workflows, shell environments, or cross-platform SQL tools. The SQLCMD example is generic but does not clarify Linux compatibility or alternatives. There are no explicit Linux shell or scripting examples, and the documentation does not address platform-specific nuances for Linux users.
Recommendations
  • Add explicit Linux shell examples for all CLI commands, including environment variable usage and authentication nuances.
  • Mention and provide instructions for using cross-platform SQL tools (e.g., sqlcmd on Linux, Azure Data Studio) and clarify installation steps for Linux.
  • Ensure parity in instructions for enabling managed identity via CLI and PowerShell by providing equivalent bash and zsh examples.
  • Clarify that all CLI commands work on Linux/macOS and provide troubleshooting tips for common platform-specific issues.
  • Include screenshots or terminal output from Linux environments where appropriate.
  • Avoid referencing Windows-specific tools (like PowerShell) before their cross-platform equivalents, or present them in parallel.
GitHub Create Pull Request
Azure Functions Develop Azure Functions locally using Core Tools ...b/main/articles/azure-functions/functions-run-local.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation generally aims for cross-platform parity, but there are subtle Windows biases. Windows command line and PowerShell are frequently referenced, sometimes before or instead of Linux equivalents. Examples for HTTP triggers and non-HTTP triggers show both Bash and Windows CMD, but the Windows example is always present and sometimes appears first. The use of 'func.exe' in explanations and references to Windows-specific tools (such as MSI installers) further reinforce a Windows-centric perspective. There is also a strong presence of PowerShell as a primary language pivot, which may not be as relevant for Linux users. However, Linux and macOS are not excluded, and Bash/cURL examples are provided.
Recommendations
  • Ensure that Bash/Linux examples are always presented first or equally alongside Windows CMD/PowerShell examples.
  • Avoid using Windows-specific terminology like 'func.exe' in general explanations—use 'func' unless specifically discussing Windows.
  • Where PowerShell is referenced, ensure that equivalent Bash or shell commands are also provided and clearly labeled.
  • Explicitly mention Linux/macOS support and installation methods where Windows-specific instructions (e.g., MSI) are given.
  • In tool prerequisites, mention Linux-native tools (e.g., Bash, zsh, sh) and package managers (apt, yum, brew) alongside Windows tools.
  • Review quickstart and reference links to ensure they do not default to Windows/PowerShell pivots.
  • Consider adding a short section or callout for Linux/macOS users to highlight any differences or tips for those platforms.
GitHub Create Pull Request
Azure Functions Azure Functions networking options ...ticles/azure-functions/functions-networking-options.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Feature Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the Hybrid Connections section, which is explicitly stated as only supported for Windows function apps, with Linux apps not supported. Additionally, CLI and PowerShell examples are provided for enabling dynamic scale monitoring, but Linux-specific shell or automation examples (e.g., Bash scripts) are missing. There are several places where Windows requirements or recommendations are mentioned before Linux equivalents (e.g., subnet sizing), and Linux parity is not always addressed or explained. Overall, the documentation favors Windows scenarios and tools, with Linux support and examples either missing or secondary.
Recommendations
  • Add explicit Linux support status and alternatives for features like Hybrid Connections, or clarify when Linux support is planned.
  • Provide Linux-specific automation examples (e.g., Bash, shell scripts) alongside PowerShell and Azure CLI, especially for configuration tasks.
  • Ensure subnet sizing recommendations for Linux are presented with equal prominence and detail as Windows, possibly in a side-by-side comparison.
  • Where features are Windows-only, suggest Linux alternatives or workarounds, or link to tracking issues/roadmap for Linux support.
  • Review all examples and tutorials to ensure Linux users are not excluded, and add Linux-specific quickstart resources where possible.
GitHub Create Pull Request
Azure Functions Automate function app resource deployment to Azure ...es/azure-functions/functions-infrastructure-as-code.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Examples Prominence Powershell Heavy
Summary
The documentation provides both Windows and Linux examples for most resource definitions, but Windows examples are consistently presented first in code tabs and explanations. PowerShell is the only scripting language shown for deployment automation, with no Bash or Linux shell equivalents. Some references and sample links default to Windows-based templates, and Windows terminology (e.g., 'Windows Consumption plan') is used more frequently and earlier in the text. Linux examples are present, but often appear after Windows, and Linux-specific deployment methods (e.g., Bash, az CLI) are not highlighted in automation sections.
Recommendations
  • Present Linux examples before or alongside Windows examples in code tabs and explanations, especially for resource definitions and deployment steps.
  • Add Bash or Azure CLI shell script examples for deployment automation, not just PowerShell.
  • Ensure sample links and references include both Windows and Linux templates, or default to a neutral/OS-agnostic example.
  • Use OS-neutral terminology where possible, and clarify when instructions apply to both Windows and Linux.
  • Highlight Linux-specific considerations and workflows (such as remote builds, container deployment, and managed identity usage) equally with Windows.
  • Consider adding a parity checklist or table summarizing differences and equivalencies between Windows and Linux deployments.
GitHub Create Pull Request
Azure Functions Migrate C# app from in-process to isolated worker model ...es/azure-functions/migrate-dotnet-to-isolated-model.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell scripts for identifying function apps, referencing Visual Studio as the publishing tool, and omitting equivalent Linux-friendly instructions (such as Azure CLI or bash examples). Windows tools and workflows (PowerShell, Visual Studio) are mentioned first and exclusively, with no mention of Linux alternatives or parity for common developer scenarios.
Recommendations
  • Add Azure CLI and/or bash script examples alongside PowerShell for identifying function apps and managing Azure resources.
  • Include instructions for publishing and deploying using cross-platform tools such as Azure Functions Core Tools, Azure CLI, and VS Code, rather than focusing solely on Visual Studio.
  • Explicitly mention Linux/macOS compatibility and provide steps for those environments where relevant (e.g., updating settings.json in VS Code, running local development tools).
  • Ensure that all automation and CI/CD references include examples for popular Linux-based pipelines (e.g., GitHub Actions, Azure Pipelines with Ubuntu runners).
  • Review all tooling references to ensure parity between Windows and Linux, and avoid presenting Windows tools as the default or only option.
GitHub Create Pull Request
Azure Functions Durable Functions best practices and diagnostic tools ...s/durable/durable-functions-best-practice-reference.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates mild Windows bias. Windows-centric tools (Visual Studio, Roslyn Analyzer) are mentioned as primary options for code analysis and monitoring, with Visual Studio Code as a cross-platform alternative. PowerShell is listed as a key language for performance tuning, but Linux shell equivalents are not mentioned. Diagnostic tooling references (Application Insights, Azure portal) are platform-neutral, but the emphasis on Visual Studio and Roslyn Analyzer may disadvantage Linux users. No explicit Linux examples, shell commands, or Linux-specific guidance are provided.
Recommendations
  • Include Linux shell (bash) and cross-platform CLI examples alongside PowerShell for performance tuning and diagnostics.
  • Highlight cross-platform alternatives to Visual Studio and Roslyn Analyzer, such as VS Code extensions or language-agnostic linters.
  • Explicitly mention Linux compatibility for all tools and extensions, and provide installation/configuration instructions for Linux environments.
  • Add references to Linux-friendly monitoring and logging tools (e.g., Azure CLI, az monitor, open-source log aggregators) where appropriate.
  • Ensure that examples and tool recommendations are presented in a platform-neutral order, or with equal prominence for Windows and Linux.
GitHub Create Pull Request
Azure Functions Durable Functions publishing to Azure Event Grid ...unctions/durable/durable-functions-event-publishing.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page shows evidence of Windows bias primarily through the use and mention of Windows-centric tools and patterns. The Storage Emulator, referenced for local development, is a Windows-only tool, and instructions for clearing storage data assume its use. While Azure CLI is cross-platform, PowerShell is mentioned as an alternative for resource creation, but no Bash or Linux-specific alternatives are highlighted. There are no explicit Linux or macOS examples for local development, nor is there guidance for using Linux-native storage emulators (such as Azurite in Docker or npm). The order of tool presentation and the lack of Linux-specific troubleshooting or parity guidance further reinforce a Windows-first approach.
Recommendations
  • Replace or supplement references to the Windows-only Storage Emulator with instructions for using Azurite on Linux/macOS (via npm or Docker).
  • Provide explicit examples for local development on Linux/macOS, including how to install and run Azurite.
  • Where PowerShell is mentioned, also provide Bash or shell script equivalents, or clarify that Azure CLI commands work cross-platform.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., file permissions, port conflicts with Azurite).
  • Reorder tool mentions so that cross-platform options (Azure CLI, Azurite) are presented before Windows-specific tools.
  • Review all screenshots and UI instructions to ensure they are not Windows-centric, or add notes for Linux/macOS users where UI differs.
GitHub Create Pull Request
Azure Functions Orchestration versioning in Durable Functions - Azure .../durable/durable-functions-orchestration-versioning.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides extensive PowerShell examples and references the PowerShell SDK, which is primarily a Windows-centric tool. PowerShell is presented as a first-class language alongside C#, JavaScript, Python, and Java, but there are no equivalent Linux shell (e.g., Bash) examples or references to Linux-native tools. The documentation does not mention or provide examples for Linux command-line usage, nor does it discuss cross-platform CLI tools (such as Azure CLI) for orchestration management. The PowerShell examples and SDK references may implicitly favor Windows users, and the lack of Linux-specific guidance or parity in examples constitutes a Windows bias.
Recommendations
  • Add Bash or Linux shell examples for orchestration management and function invocation, especially in sections where PowerShell is used.
  • Reference cross-platform tools such as Azure CLI and provide examples for both Windows (PowerShell) and Linux (Bash).
  • Clarify that PowerShell Core is available cross-platform, but also provide equivalent Linux-native examples for users who do not use PowerShell.
  • Include notes or guidance for Linux users on how to achieve the same orchestration versioning tasks using their preferred tools.
  • Ensure that SDK and tool recommendations are balanced, mentioning both Windows and Linux options where available.
GitHub Create Pull Request
Azure Functions Versioning in Durable Functions - Azure ...zure-functions/durable/durable-functions-versioning.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through the inclusion of PowerShell examples alongside C# and Java, but omits any Linux-native shell (e.g., Bash) or cross-platform scripting examples. PowerShell is traditionally associated with Windows environments, and its presence without equivalent Linux shell examples may disadvantage Linux users. Additionally, there are no explicit references to Linux tools, deployment patterns, or command-line instructions that would be familiar to Linux users.
Recommendations
  • Add Bash or other Linux shell scripting examples where PowerShell is used, or clarify cross-platform compatibility of PowerShell Core.
  • Include guidance or examples for Linux-native deployment workflows, such as using Azure CLI or shell scripts for queue management and deployment.
  • Explicitly mention that PowerShell examples are cross-platform if using PowerShell Core, or provide alternatives for Linux users.
  • Ensure that documentation references both Windows and Linux tools and patterns equally, especially in sections discussing deployment, storage management, and orchestration control.
  • Consider adding a note or section on platform-specific considerations for Durable Functions, including any differences in local development or deployment between Windows and Linux.
GitHub Create Pull Request
← Previous Page 6 of 41 Next →