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 301-325 of 1023 flagged pages
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-host-json.md ...b/main/articles/azure-functions/functions-host-json.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page displays mild Windows bias, primarily through its emphasis on PowerShell-based features (managedDependency is only supported for PowerShell), references to Windows-specific environment variables (e.g., %TEMP%), and the use of Windows-centric terminology and examples (such as referencing Kudu performance counters and default folder locations). Linux-specific equivalents are mentioned only in passing (e.g., DisableColors for console logs), and Linux patterns or examples are generally absent or relegated to secondary notes.
Recommendations
  • Provide Linux-specific examples and notes alongside Windows references, especially for environment variables and file paths (e.g., clarify what tempFolder defaults to on Linux).
  • Expand managedDependency documentation to clarify support for other platforms/languages, or note Linux alternatives if available.
  • Include parity for tooling references (e.g., explain Kudu alternatives for Linux environments, or clarify its availability).
  • Ensure that configuration examples and troubleshooting steps include both Windows and Linux scenarios, especially for file paths, environment variables, and logging behaviors.
  • Where PowerShell is referenced, mention equivalent scripting options for Linux (such as Bash or Python) if relevant.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-premium-plan.md ...ain/articles/azure-functions/functions-premium-plan.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits several signs of Windows bias. Windows and PowerShell examples are consistently presented alongside Azure CLI, but Linux-specific instructions or parity are missing. The migration section explicitly states that migration between plans is only supported on Windows, with no Linux alternative. Throughout, Windows tools (PowerShell) are given equal or greater prominence than cross-platform options, and there are no Linux shell or bash examples. The region scale-out table lists Windows before Linux, and some regions have Windows-only availability.
Recommendations
  • Add explicit bash/Linux shell examples for all CLI instructions, clarifying cross-platform usage.
  • Where PowerShell is shown, clarify its availability on Linux and macOS, or provide equivalent bash commands.
  • For migration, document Linux limitations and provide workarounds or roadmap for Linux support.
  • Review ordering in tables and lists to avoid Windows-first presentation; consider alphabetical or neutral ordering.
  • Highlight Linux container deployment support with practical configuration examples.
  • Ensure documentation for portal and CLI instructions notes any OS-specific differences or limitations.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/how-to-create-function-vs-code.md ...cles/azure-functions/how-to-create-function-vs-code.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates some Windows bias, primarily through the use of Windows-specific tools, instructions, and patterns. Windows and PowerShell are given dedicated pivots and examples, and certain instructions (such as compiling Go and Rust custom handlers for Linux) provide Windows-specific steps and mention Windows file conventions (e.g., .exe). Troubleshooting advice singles out Windows terminal settings. However, Linux and macOS are also supported and referenced, especially for Java, Go, and Rust, but Windows is often mentioned first or with more detail.
Recommendations
  • Ensure all platform-specific instructions (Windows, Linux, macOS) are presented together and with equal detail, rather than listing Windows first or with more explanation.
  • Where possible, avoid Windows-centric terminology (e.g., .exe) in cross-platform contexts, or clarify platform differences explicitly.
  • Add Linux-specific troubleshooting steps, such as common issues with permissions, shell environments, or package managers.
  • For PowerShell, clarify that it is available cross-platform and provide equivalent Bash or shell examples for Linux/macOS users.
  • Review all pivots and examples to ensure Linux and macOS users receive parity in guidance, especially for installation, configuration, and troubleshooting.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-run-local.md ...b/main/articles/azure-functions/functions-run-local.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates some Windows bias, primarily through repeated references to Windows-specific tools (PowerShell, command prompt), explicit mention of func.exe, and examples that distinguish between Bash and Windows command line. Windows tools (Azure PowerShell, command prompt) are mentioned alongside cross-platform options, sometimes before Linux equivalents. There is also a notable presence of PowerShell as a first-class language pivot, which may reinforce a Windows-centric perspective. However, Linux and macOS usage is generally supported, and most commands are cross-platform.
Recommendations
  • Ensure that Linux/macOS equivalents (e.g., bash, zsh, terminal) are mentioned wherever 'command prompt' or 'PowerShell' is referenced.
  • When listing required tools for publishing (Azure CLI, Azure PowerShell), clarify that Azure CLI is cross-platform and highlight its use for Linux/macOS users.
  • Avoid using 'func.exe' as the default process name; use 'func' or clarify that on Linux/macOS it is simply 'func'.
  • Where examples are given for both Bash and Windows command line, consider presenting Bash/Linux examples first, or side-by-side, to avoid Windows-first ordering.
  • Add explicit notes or sections for Linux/macOS users, especially in areas where Windows-specific instructions or terminology are used.
  • Review language pivots to ensure that PowerShell does not dominate or imply Windows-only usage; clarify cross-platform support for PowerShell Core.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/migrate-version-1-version-4.md ...rticles/azure-functions/migrate-version-1-version-4.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily by providing only PowerShell scripts for identifying function apps to migrate, with no equivalent Bash or Azure CLI examples for Linux/macOS users. The instructions for migration and tooling (such as Visual Studio publishing) also reference Windows-centric workflows first or exclusively. There is a lack of explicit Linux or cross-platform guidance in key migration steps, especially in initial app identification and deployment sections.
Recommendations
  • Add equivalent Azure CLI and/or Bash script examples alongside PowerShell scripts for identifying function apps to migrate.
  • Explicitly mention cross-platform tools and workflows (e.g., VS Code, Azure CLI) in migration and deployment sections, not just Visual Studio.
  • Ensure that instructions for local development and testing reference both Windows and Linux/macOS environments, including any platform-specific considerations.
  • Review all code and command examples for platform neutrality, and provide alternatives where Windows-only tools or patterns are used.
  • Consider adding a dedicated section or callouts for Linux/macOS users to highlight any differences or additional steps.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/scenario-blob-storage-events.md ...ticles/azure-functions/scenario-blob-storage-events.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Visual Studio Code is presented as the primary development environment, and instructions often reference Windows-specific workflows (e.g., command palette, F1, terminal settings). PowerShell is included as a first-class language, and Windows-specific details (such as avoiding WSL Bash as the default terminal) are mentioned. While Linux/macOS instructions are present for Python virtual environments, Windows instructions are given in multiple variants (bash, cmd), and some steps (such as stopping the func.exe host process) reference Windows executables. There is a lack of explicit parity for Linux tools and troubleshooting, and Windows-centric patterns (e.g., reliance on VS Code extensions and GUI actions) are emphasized.
Recommendations
  • Ensure all command-line examples are provided for both Windows and Linux/macOS, not just for Python virtual environments.
  • Include troubleshooting notes for Linux/macOS environments (e.g., permissions, terminal issues) alongside Windows-specific notes.
  • Present Linux/macOS instructions before or alongside Windows instructions, rather than after.
  • Avoid referencing Windows executables (e.g., func.exe) in generic steps; use cross-platform terminology.
  • Highlight alternative development environments and workflows for Linux users (e.g., using CLI tools outside VS Code, or alternative editors).
  • Provide parity for PowerShell examples with Bash or other shell equivalents where possible.
  • Clarify that all steps can be performed on Linux/macOS, and explicitly mention any platform-specific limitations or requirements.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/migrate-version-3-version-4.md ...rticles/azure-functions/migrate-version-3-version-4.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only a PowerShell script to identify function apps for migration, with no equivalent Bash, Azure CLI, or Linux-native example. The initial migration steps and tooling references (such as Visual Studio and .NET Upgrade Assistant) also assume a Windows-centric workflow, and Linux or cross-platform alternatives are not mentioned or are relegated to later sections. There is a lack of explicit Linux command-line examples or guidance for users on non-Windows systems.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts alongside PowerShell for identifying function apps, ensuring Linux and macOS users have clear guidance.
  • When referencing tools like Visual Studio, also mention cross-platform alternatives such as Visual Studio Code or JetBrains Rider, and clarify which steps are platform-agnostic.
  • Explicitly state when instructions or tools are Windows-only, and offer Linux/macOS alternatives where possible.
  • Include examples of running Azure Functions Core Tools and other migration steps in a Linux shell environment.
  • Ensure that all code snippets and migration steps are validated for cross-platform compatibility, and highlight any OS-specific considerations.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/ip-addresses.md ...ocs/blob/main/articles/azure-functions/ip-addresses.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides command-line examples for Azure CLI and Azure PowerShell, with PowerShell examples included for each relevant section. There are no explicit Linux- or Bash-specific examples, and PowerShell is presented as a primary alternative to Azure CLI. The use of PowerShell commands and terminology may implicitly favor Windows users, and there is no mention of Linux-native tools or shell environments beyond the generic 'nslookup' utility. The ordering of examples sometimes places PowerShell before or alongside CLI, but never Bash or Linux-specific guidance.
Recommendations
  • Add Bash/Linux shell examples where appropriate, especially for common tasks (e.g., using curl/jq for JSON parsing, or Bash scripting for automation).
  • Clarify that Azure CLI commands work cross-platform and can be run in Bash, PowerShell, or other shells.
  • Where PowerShell is shown, consider also providing equivalent Bash or shell script snippets for Linux/macOS users.
  • Explicitly mention that 'nslookup' is available on both Windows and Linux, or suggest alternatives like 'dig' for Linux users.
  • Avoid assuming PowerShell as the default scripting environment; highlight cross-platform options.
  • Consider reordering examples to present Azure CLI (which is cross-platform) before PowerShell, and add Bash/Linux-native examples where possible.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/recover-python-functions.md ...n/articles/azure-functions/recover-python-functions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas: Windows/Powershell commands are often presented before their Linux equivalents, Windows-specific tools and patterns (e.g., PowerShell, 'py' launcher) are referenced, and some examples lack parity for Linux users. While Linux is acknowledged as the runtime environment for Azure Functions, troubleshooting and local development instructions frequently prioritize or exclusively mention Windows workflows and tools.
Recommendations
  • Ensure all command-line examples are provided for both Windows (PowerShell/CMD) and Linux (Bash), with equal prominence and ordering.
  • When referencing tools (e.g., 'py' launcher), clarify Linux equivalents (e.g., 'python3') and provide usage examples.
  • Avoid presenting Windows commands first; alternate or parallelize instructions for Windows and Linux users.
  • Explicitly mention Linux-specific troubleshooting steps and tools where relevant (e.g., package management, file paths, environment variables).
  • Review all sections for missing Linux/Bash examples and add them where only Windows/PowerShell commands are shown.
  • Highlight that Azure Functions runs on Linux at runtime and encourage cross-platform development practices.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/how-to-create-function-azure-cli.md ...es/azure-functions/how-to-create-function-azure-cli.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Command examples and instructions frequently reference Windows-specific tools and patterns, such as PowerShell and Cmd, and these are presented alongside or before Linux alternatives. In the Java section, explicit tabs for Bash, PowerShell, and Cmd are provided, but Bash is not consistently prioritized. The file path examples use backslashes (\), which are Windows conventions. There is a lack of explicit Linux-specific instructions, such as setting environment variables or handling permissions, and no mention of common Linux shells (other than Bash) or package managers. The documentation does not consistently provide parity for Linux users, and Windows-centric terminology and tooling are prevalent.
Recommendations
  • Ensure that Bash (Linux/macOS) examples are presented before or alongside Windows (PowerShell/Cmd) examples, especially in tabbed sections.
  • Include explicit instructions for Linux users, such as setting environment variables, installing prerequisites, and handling file permissions.
  • Use platform-neutral file paths (forward slashes) or provide both Windows and Linux/macOS path examples.
  • Mention Linux package managers (apt, yum, etc.) for installing dependencies where relevant.
  • Avoid Windows-centric terminology (e.g., 'command prompt') in favor of platform-neutral terms like 'terminal'.
  • Review all code and command snippets to ensure Linux/macOS compatibility and provide troubleshooting tips for non-Windows platforms.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-monitoring.md .../main/articles/azure-functions/functions-monitoring.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates some Windows bias, primarily through the lack of Linux-specific examples and by referencing features and tools that are either unavailable or limited on Linux. For example, Performance Counters are not supported on Linux, and built-in log streaming does not work for Linux Consumption plans. The documentation does not provide alternative Linux-friendly approaches or highlight Linux limitations upfront. Windows-centric features and limitations are mentioned before Linux equivalents, and there is no parity in troubleshooting or monitoring guidance for Linux users.
Recommendations
  • Add explicit Linux examples and instructions for monitoring and log streaming, especially where features differ or are unavailable.
  • Clearly indicate limitations for Linux users at the start of relevant sections, and provide alternative solutions or workarounds.
  • Include parity tables or comparison charts showing feature availability for Windows vs. Linux, with links to Linux-specific documentation.
  • Where Windows tools or patterns are mentioned (e.g., Performance Counters, built-in log streaming), immediately follow with Linux alternatives or guidance.
  • Ensure troubleshooting and diagnostic guidance is equally detailed for both Windows and Linux environments.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-scale.md .../blob/main/articles/azure-functions/functions-scale.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows-first bias in several areas. Windows hosting options and features are often mentioned before Linux equivalents, and Windows-specific scenarios (e.g., PowerShell modules, .NET Framework) are highlighted as primary use cases for the Consumption plan. There is a lack of Linux-specific examples or guidance, and Windows tools/patterns (such as PowerShell) are referenced without equivalent Linux alternatives. Linux support is discussed mainly in terms of limitations or retirement, rather than as a first-class option.
Recommendations
  • Provide Linux-specific examples and scenarios, especially for deployment and runtime choices.
  • Mention Linux hosting options and features before or alongside Windows options, rather than after.
  • Include references to Linux tools and patterns (e.g., Bash, shell scripts, Linux-native modules) wherever Windows tools (like PowerShell) are mentioned.
  • Clarify parity between Windows and Linux features, and highlight Linux advantages where applicable.
  • Add troubleshooting and migration guidance for Linux users, especially in light of Linux Consumption plan retirement.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/scenario-custom-remote-mcp-server.md ...s/azure-functions/scenario-custom-remote-mcp-server.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias in several areas. Windows-specific tools and patterns (such as PowerShell and Windows CMD) are mentioned and provided as examples, sometimes before or alongside Linux/macOS equivalents. The prerequisites and scripting instructions include explicit references to PowerShell and Windows installation instructions, and the script for retrieving the MCP server key provides a PowerShell example for Windows, while Linux/macOS users are given a Bash alternative. Additionally, some instructions (such as setting environment variables for Java) reference Windows conventions (JAVA_HOME), and the Visual Studio Code workflow is more commonly associated with Windows development environments.
Recommendations
  • Ensure Linux/macOS examples are always presented alongside Windows examples, and in some cases, consider listing Linux/macOS instructions first to balance the order.
  • Where PowerShell is used, provide equivalent Bash or shell script examples for Linux/macOS users, and clarify any platform-specific differences.
  • Avoid language that assumes Windows as the default environment (e.g., 'command prompt'), and use more neutral terms like 'terminal'.
  • Explicitly mention and link to Linux/macOS installation instructions for all required tools (e.g., .NET SDK, Azure CLI, Azurite, etc.), not just Windows.
  • Review all code snippets and setup steps to ensure parity and clarity for Linux/macOS users, including troubleshooting tips for common platform-specific issues.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/machine-learning-pytorch.md ...n/articles/azure-functions/machine-learning-pytorch.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides command examples for Bash, PowerShell, and Cmd, but Windows-specific tools and patterns are often mentioned first or exclusively. Windows command-line tools (PowerShell, Cmd) are given equal or greater prominence than Bash, and Windows-specific issues (such as long path errors and registry edits) are described in detail, while Linux/macOS troubleshooting is minimal. The use of 'py' for Python version checks and virtual environment activation is Windows-centric. Visual Studio Code is recommended as the editor, which is cross-platform but often associated with Windows. Some troubleshooting tips are Windows-only.
Recommendations
  • Ensure Linux/macOS troubleshooting tips are provided with equal detail as Windows (e.g., common pip/venv issues on Linux).
  • Present Bash/Linux/macOS examples first, or alternate the order in code tabs to avoid Windows-first bias.
  • When discussing errors (such as long path issues), include equivalent Linux/macOS filesystem or permissions issues and their solutions.
  • Mention Linux/macOS equivalents for Windows-specific commands (e.g., use 'python' instead of 'py' for version checks and venv activation on non-Windows systems).
  • Highlight cross-platform editors and tools, and avoid implying Visual Studio Code is the only recommended option.
  • Add troubleshooting sections for Linux/macOS environments, such as common package installation errors, permission issues, or Python path problems.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/update-language-versions.md ...n/articles/azure-functions/update-language-versions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several areas. Instructions and examples for updating the language stack configuration are consistently presented for Windows before Linux, both in Azure portal and Azure CLI sections. Some features (such as Python on Windows) are explicitly unsupported, but the documentation does not always provide Linux alternatives in the same context. The use of Windows-specific terminology and ordering may make Linux users feel secondary. Additionally, some CLI examples and troubleshooting steps are more detailed for Windows scenarios, and there is a lack of parity in local development tool guidance for Linux environments.
Recommendations
  • Present Linux and Windows instructions in parallel, or default to a neutral ordering (e.g., alphabetical or based on detected user OS).
  • Ensure that for every Windows-specific example or instruction, a Linux equivalent is provided with equal prominence and detail.
  • Where features are unsupported on one OS (e.g., Python on Windows), provide a clear and direct link or inline instructions for the supported OS, rather than simply redirecting.
  • In sections discussing local development tools, explicitly mention Linux-compatible tools and workflows (e.g., VS Code on Linux, .NET SDK installation on Linux, etc.).
  • Avoid using Windows terminology (such as 'net-framework-version') without clarifying the Linux equivalent (such as 'linuxFxVersion').
  • Review troubleshooting and verification steps to ensure Linux users receive the same level of detail and actionable guidance as Windows users.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/scenario-database-changes-azure-sqldb.md ...ure-functions/scenario-database-changes-azure-sqldb.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively using Visual Studio Code and its extensions (such as the SQL Server (mssql) extension and Azure Functions Core Tools) for all steps, without mentioning or providing alternatives for Linux users. All instructions assume the use of VS Code's command palette and GUI features, which are most commonly used on Windows. There are no examples or guidance for using command-line tools (e.g., sqlcmd, Azure CLI, or other editors) on Linux or macOS, nor any mention of Linux-specific considerations for local development, database connectivity, or deployment.
Recommendations
  • Add explicit instructions and examples for Linux users, including how to perform each step using the terminal and command-line tools (e.g., sqlcmd, Azure CLI, nano/vim for editing files).
  • Mention and provide alternatives to Visual Studio Code, such as using VS Code on Linux, or other editors and tools available on Linux.
  • Include guidance for installing and using Azure Functions Core Tools and the Azure Developer CLI on Linux, with troubleshooting tips for common Linux issues.
  • Provide examples for connecting to Azure SQL Database using command-line tools (e.g., sqlcmd, mssql-cli) on Linux.
  • Clarify any platform-specific differences in authentication (e.g., Microsoft Entra ID) and how to handle them on Linux.
  • Ensure that all steps (provisioning, running, deploying, cleaning up) can be completed entirely from the command line, and document those workflows.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/storage-considerations.md ...ain/articles/azure-functions/storage-considerations.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several forms of Windows bias. Windows hosting plans and behaviors are mentioned before Linux equivalents, and PowerShell-specific features and examples are highlighted (e.g., managed dependencies in PowerShell, PowerShell commands for mounting shares). Windows-specific settings and deployment patterns (such as Azure Files usage in Windows Consumption plans) are described in detail, while Linux alternatives are less emphasized or only mentioned later. There are sections where Linux examples or guidance are missing or less detailed, and Windows tools or terminology (such as Visual Studio and PowerShell) are referenced more frequently and prominently than Linux equivalents.
Recommendations
  • Ensure Linux hosting plans and features are described with equal prominence and detail as Windows equivalents.
  • Provide Linux-specific examples and guidance wherever Windows-specific instructions are given (e.g., deployment automation, troubleshooting, mounting shares).
  • Include CLI and Bash examples alongside PowerShell, especially in sections about automation and configuration.
  • Highlight cross-platform tools (such as VS Code, Az CLI) before platform-specific ones (e.g., Visual Studio, PowerShell).
  • Clarify when features or settings are Windows-only, and provide Linux alternatives or workarounds where possible.
  • Add explicit Linux troubleshooting and best practices sections to match Windows coverage.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/set-runtime-version.md ...b/main/articles/azure-functions/set-runtime-version.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows and PowerShell examples are consistently provided and often appear before or alongside Linux equivalents. PowerShell cmdlets are described in detail, while Linux-specific instructions (such as for pinning runtime versions) are less prominent and sometimes require external support (e.g., for Docker image URIs). Some operations (like setting linuxFxVersion) are explicitly unavailable in the portal or PowerShell, but this limitation is only mentioned in the Linux section. The documentation does not provide parity in tooling or example depth for Linux users compared to Windows users.
Recommendations
  • Ensure that Linux instructions and examples are presented with equal prominence and detail as Windows/PowerShell examples.
  • Provide Linux-specific command-line examples (e.g., bash scripts) where PowerShell scripts are given for Windows.
  • Include guidance for Linux users on how to obtain valid Docker image URIs without requiring support intervention.
  • Clarify limitations and alternatives for Linux users (e.g., inability to use portal or PowerShell for certain settings) in both Windows and Linux sections for transparency.
  • Where possible, offer cross-platform examples (e.g., bash, PowerShell, CLI) side-by-side for each operation.
  • Review the order of presentation to avoid consistently listing Windows instructions before Linux, or use a neutral, parallel structure.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/dotnet-isolated-process-guide.md ...icles/azure-functions/dotnet-isolated-process-guide.md
High Priority View Details →
Scanned: 2025-09-07 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools and configuration steps (such as Visual Studio, PowerShell, and Windows-specific CLI flags) are often mentioned before or more prominently than their Linux equivalents. Some deployment and configuration examples are Windows-first or reference Windows-specific concepts before Linux. In several places, Linux instructions are present but less detailed or appear after Windows instructions. There is a lack of explicit Linux shell (bash) or cross-platform CLI examples in some sections, and PowerShell is referenced as a primary automation tool.
Recommendations
  • Ensure all CLI examples are provided in both Windows (PowerShell/CMD) and Linux (bash) syntax, using tabs or side-by-side formatting.
  • When listing tools or workflows (e.g., Visual Studio, Visual Studio Code, Azure CLI, PowerShell), present cross-platform options first or equally, rather than Windows-only or Windows-first.
  • Where PowerShell is mentioned, also provide equivalent bash or shell scripts for Linux users.
  • In deployment and configuration sections, ensure Linux and container scenarios are described with equal detail and prominence as Windows scenarios.
  • Add explicit notes or callouts for any Windows-only features, and provide Linux alternatives or workarounds where possible.
  • Review all references to Visual Studio and ensure Visual Studio Code and CLI-based workflows are equally documented and discoverable.
  • Audit for any missing Linux-specific troubleshooting or debugging guidance, and add parity where gaps exist.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-reference-java.md ...n/articles/azure-functions/functions-reference-java.md
High Priority View Details →
Scanned: 2025-09-02 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation generally aims for cross-platform parity, but there is a subtle Windows bias. Command-line examples are consistently provided for both Bash (Linux/macOS) and Cmd (Windows), but the Windows/Cmd examples are always listed second, which is positive. However, there is a notable absence of PowerShell-specific examples, which is good. The main bias is that some sections refer to 'command prompt' (a Windows term) alongside 'terminal' and mention Windows in tables before Linux. There are no Linux-specific tools or troubleshooting steps, and some language (e.g., 'open a new command prompt, Bash, or Terminal session') puts Windows terminology first or on equal footing, which can be confusing for Linux users. There are no Linux-only examples or guidance, and the documentation does not mention WSL or other Linux-specific workflows.
Recommendations
  • Ensure that references to 'command prompt' are always paired with 'terminal' or 'shell', and consider putting 'terminal' first to reflect cross-platform usage.
  • Where possible, add Linux-specific troubleshooting tips or notes (e.g., file permissions, environment variable export syntax).
  • Consider including a short section or callout for WSL users, or for common Linux distributions, to address any OS-specific caveats.
  • Continue to provide both Bash and Cmd examples, but consider putting Bash (Linux/macOS) first in all cases to reflect the growing popularity of Linux development environments.
  • Review all language to ensure that Windows-specific terms are not used generically (e.g., use 'terminal' instead of 'command prompt' when referring to any shell).
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-add-openai-text-completion.md ...zure-functions/functions-add-openai-text-completion.md
High Priority View Details →
Scanned: 2025-09-02 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-centric tools and workflows (such as Azurite emulator and Visual Studio Code commands) without clarifying Linux/Mac compatibility or providing alternative instructions. Powershell is included as a primary language, but there are no explicit Bash or Linux shell examples. The instructions for starting Azurite and running the function app assume Visual Studio Code and Windows keybindings, and there is no mention of Linux-specific nuances or terminal commands.
Recommendations
  • Explicitly mention that Azurite and Visual Studio Code are cross-platform, and provide instructions for starting Azurite from the command line (e.g., `npx azurite` or `azurite` for Linux/Mac users).
  • Include Bash or Linux shell equivalents for any Powershell or Windows-specific commands.
  • Clarify that Visual Studio Code commands and keybindings may differ on Linux/Mac (e.g., <kbd>Cmd</kbd> instead of <kbd>Ctrl</kbd>).
  • Add a note or section for Linux/Mac users highlighting any differences in setup, file paths, or environment variables.
  • Where possible, provide terminal-based alternatives to GUI steps (such as using the Azure CLI for resource creation and management).
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-how-to-azure-devops.md ...icles/azure-functions/functions-how-to-azure-devops.md
High Priority View Details →
Scanned: 2025-09-02 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows-based build agents ('windows-latest') are used by default or listed first in C# and PowerShell YAML examples, while Linux ('ubuntu-latest') is only used by default for JavaScript and Python. PowerShell is included as a first-class language, but there is no equivalent Bash or shell scripting example for Linux users. The deployment instructions and YAML snippets often default to Windows app types and only mention Linux as an alternative, sometimes as a comment or secondary option. There are no explicit Linux shell scripting or Linux-native tool examples outside of the Python/JavaScript YAML, and the documentation assumes Visual Studio Code as the editor, which is cross-platform but often associated with Windows workflows.
Recommendations
  • For each language, provide both Windows and Linux YAML build examples, or clearly indicate parity and differences.
  • In C# examples, show both 'windows-latest' and 'ubuntu-latest' agent pools, and explain when to use each.
  • For PowerShell, clarify if Linux PowerShell Core is supported and provide Bash equivalents for packaging/deployment steps.
  • In deployment sections, present Linux and Windows app deployment YAML side by side, not with Windows as the default.
  • Explicitly mention Linux-native tools and workflows where possible, and avoid assuming Windows as the default environment.
  • Add a table or matrix summarizing OS support and recommended agent pools for each language and scenario.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-reference-python.md ...articles/azure-functions/functions-reference-python.md
High Priority View Details →
Scanned: 2025-09-02 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation is generally cross-platform and Linux-oriented for hosting, but there are subtle Windows biases in development and publishing workflows. Windows terminology ("command prompt"), tools (Visual Studio Code, Azure Functions Core Tools), and recommendations for remote build when developing on Windows are mentioned before or instead of Linux equivalents. There is also a lack of explicit Linux shell examples, and some folder structure examples use Windows-style command prompt formatting. However, the documentation does clarify that Python Functions are only supported on Linux in Azure, and most content is platform-neutral.
Recommendations
  • Provide explicit Linux shell (bash) examples alongside or before Windows command prompt examples, especially for commands like pip install and func azure functionapp publish.
  • Use neutral terms like 'terminal' or 'shell' instead of 'command prompt' when referring to cross-platform development environments.
  • Include instructions or notes for Linux/macOS users wherever Windows-specific guidance is given (e.g., Visual Studio Code, Azure Functions Core Tools).
  • Show folder structure examples using POSIX-style paths (with /) or provide both Windows and Linux versions.
  • Clarify that all development and deployment steps are fully supported on Linux, and highlight any differences or additional steps required for Linux users.
  • If recommending remote build for Windows, also explain the equivalent or best practice for Linux/macOS users.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-add-openai-text-completion.md ...zure-functions/functions-add-openai-text-completion.md
High Priority View Details →
Scanned: 2025-09-01 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and workflows (such as Visual Studio Code, Azurite emulator, and PowerShell), and by omitting explicit Linux/macOS command-line instructions or alternatives. The use of PowerShell as a language example and the assumption of Visual Studio Code as the primary environment further reinforce this bias. There are no explicit instructions for Linux/macOS users regarding starting Azurite, running the function app, or managing dependencies, and the documentation does not mention platform-specific differences or alternatives.
Recommendations
  • Provide explicit instructions for Linux/macOS users, including terminal commands for starting Azurite and running the function app.
  • Include bash/zsh shell command examples alongside PowerShell where applicable.
  • Clarify that Visual Studio Code and Azurite are cross-platform, and provide installation or usage notes for Linux/macOS.
  • Add notes about any platform-specific differences in file paths, environment variable configuration, or command usage.
  • Where PowerShell is used as a language example, ensure parity by providing bash or shell script equivalents, or clarify that the example is cross-platform if applicable.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-how-to-azure-devops.md ...icles/azure-functions/functions-how-to-azure-devops.md
High Priority View Details →
Scanned: 2025-09-01 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows-based build agents (vmImage: 'windows-latest') are used by default for C# and PowerShell examples, and Windows is the default appType for deployment. PowerShell is included as a first-class language, but Linux shell scripting is only shown for JavaScript and Python. In deployment examples, Windows is presented first, and Linux options are secondary or require explicit configuration. There is little mention of Linux-native tooling or patterns outside of specifying 'ubuntu-latest' for some languages.
Recommendations
  • For C# and PowerShell, provide both Windows and Linux build pipeline examples, or clarify when Linux is supported.
  • Present Linux and Windows deployment examples side-by-side, rather than defaulting to Windows.
  • Highlight Linux-native tools or patterns where appropriate (e.g., bash for PowerShell alternatives, or cross-platform scripting).
  • Clarify the support matrix for each language and platform early in the documentation.
  • Avoid language such as 'default is Windows' without immediately showing the Linux equivalent.
  • For PowerShell, note if cross-platform PowerShell Core is supported and provide Linux agent examples if possible.
GitHub Create Pull Request
← Previous Page 13 of 41 Next →