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 626-650 of 1023 flagged pages
Azure Functions How to disable functions in Azure Functions ...blob/main/articles/azure-functions/disable-function.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples for the Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, PowerShell is Windows-centric and is given equal prominence. There are no explicit Linux shell (bash) or macOS-specific examples, and the PowerShell section is detailed, potentially implying a Windows-first approach. Additionally, a Linux-specific limitation (hyphens in function names) is mentioned only in the considerations, not in the main workflow, and no workaround is provided.
Recommendations
  • Add explicit bash/shell examples for Linux/macOS users, especially for common tasks like editing local.settings.json or using environment variables.
  • Clarify that Azure CLI commands work on all platforms, and consider showing bash/zsh syntax or terminal screenshots from Linux/macOS.
  • Reorder sections to present cross-platform (CLI) examples before PowerShell, or clearly label PowerShell as Windows-centric.
  • Provide guidance or workarounds for the Linux limitation regarding hyphens in function names earlier in the documentation.
  • Consider mentioning or linking to cross-platform tools (e.g., VS Code, REST API) for managing app settings.
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
Medium Priority View Details →
Scanned: 2026-01-13 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 (Visual Studio, Azure PowerShell) and configuration patterns are mentioned before or more prominently than their Linux equivalents. CLI examples often use Azure CLI, which is cross-platform, but Windows-centric deployment and configuration steps (e.g., netFrameworkVersion, ReadyToRun with win-x64, PowerShell resource creation) are shown first or in more detail. Linux-specific instructions are present but often secondary, and some examples (e.g., debugging, ReadyToRun, .NET Framework targeting) are Windows-only or have limited Linux guidance.
Recommendations
  • Ensure Linux and macOS instructions/examples are presented alongside Windows, not after or as an afterthought.
  • Provide explicit Linux/macOS command-line examples (e.g., bash, zsh) for all CLI steps, especially for deployment, debugging, and configuration.
  • Highlight cross-platform tools (Azure CLI, VS Code) before Windows-only tools (Visual Studio, PowerShell).
  • For ReadyToRun and architecture-specific instructions, clarify Linux support and provide Linux-specific project file and publish examples.
  • For debugging and .NET Framework scenarios, clearly state platform limitations and offer alternative workflows for Linux/macOS users.
  • Where PowerShell is mentioned, provide equivalent bash/zsh commands for Linux/macOS.
  • Review all 'tabs' and code samples to ensure Linux parity and visibility.
GitHub Create Pull Request
Azure Functions Configure monitoring for Azure Functions .../main/articles/azure-functions/configure-monitoring.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for overriding monitoring configuration at runtime, but PowerShell is shown as the only alternative to Azure CLI, which is Windows-centric. Additionally, PowerShell examples are presented in a dedicated section, and there are no Linux shell (bash) or macOS-specific examples for managing app settings. The documentation does not mention Linux-specific tools or patterns, and Windows/PowerShell tooling is referenced before any Linux alternatives.
Recommendations
  • Add bash examples for overriding app settings using Azure CLI, explicitly showing usage on Linux/macOS.
  • Clarify that Azure CLI commands work cross-platform and provide sample commands for Linux/macOS environments.
  • If PowerShell is shown, also show equivalent bash/zsh commands for parity.
  • Mention any platform-specific caveats (e.g., app settings with periods not supported on Linux plans) more prominently and provide Linux/macOS workarounds.
  • Consider adding a table or section comparing Windows, Linux, and macOS approaches for common configuration tasks.
GitHub Create Pull Request
Azure Functions Durable Functions packages .../azure-functions/durable/durable-functions-packages.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents .NET (which is historically Windows-centric) sections first and provides detailed package instructions for .NET in-process and isolated users before mentioning other platforms. PowerShell, a Windows-native shell, is given a dedicated note and migration guidance, whereas Linux/macOS equivalents (e.g., Bash) are not mentioned. Examples and instructions for Linux/macOS users are limited to package names, with no parity in guidance or tooling references.
Recommendations
  • Reorder sections or provide equal prominence to non-Windows platforms (Node.js, Python, Java) at the top or alongside .NET.
  • Add explicit instructions or examples for Linux/macOS users, such as how to install packages using Bash or other native tools.
  • Include notes or tips for Linux/macOS users where PowerShell-specific guidance is given, or mention cross-platform alternatives.
  • Clarify that .NET and PowerShell are cross-platform, but provide links or guidance for Linux/macOS-specific setup where relevant.
GitHub Create Pull Request
Azure Functions How to run Durable Functions as WebJobs - Azure ...ure-functions/durable/durable-functions-webjobs-sdk.md
Medium Priority View Details →
Scanned: 2026-01-13 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 a notable Windows bias. Visual Studio (Windows-only) is presented as the primary development environment, with only brief mention of Visual Studio Code as an alternative. Project creation instructions and screenshots reference Windows-specific templates and dialogs. All NuGet package installation examples use PowerShell commands, with no mention of cross-platform alternatives like dotnet CLI. The use of the Azurite storage emulator is described, but instructions do not clarify how to use it on Linux/macOS. There are no explicit Linux/macOS examples or guidance for users on those platforms.
Recommendations
  • Provide equivalent instructions for Linux/macOS users, including how to create projects using Visual Studio Code or JetBrains Rider.
  • Include dotnet CLI commands for NuGet package installation, which work on all platforms.
  • Add guidance for running Azurite on Linux/macOS, including installation and startup commands.
  • Show how to configure and run the sample using cross-platform tools and editors.
  • Reorder examples or provide parallel instructions so that Windows and Linux/macOS users are equally supported.
GitHub Create Pull Request
Azure Functions Durable Functions Overview - Azure .../azure-functions/durable/durable-functions-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides extensive PowerShell examples and references to Visual Studio, both of which are strongly associated with Windows. PowerShell is given parity with other languages in code samples, and Visual Studio is mentioned as a primary development tool before Visual Studio Code and the Azure portal. There is no explicit mention of Linux/macOS-specific tools or workflows, and the quickstart for C# is only shown with Visual Studio (not VS Code or CLI). However, Linux/macOS users can still follow most of the guidance using VS Code and CLI, and the code samples for JavaScript, Python, and Java are cross-platform.
Recommendations
  • Add explicit instructions and examples for Linux/macOS users, especially for C# development (e.g., using VS Code or the Azure Functions Core Tools CLI).
  • Mention cross-platform alternatives to Visual Studio, such as VS Code and CLI, before or alongside Visual Studio.
  • Clarify that PowerShell examples are primarily for Windows, and suggest Bash or other shell alternatives for Linux/macOS users where relevant.
  • Include notes or links to platform-specific setup guides for Linux/macOS.
  • Ensure parity in tooling recommendations and quickstart links for all supported platforms.
GitHub Create Pull Request
Azure Functions Quickstart: Create a Durable Functions app that uses the MSSQL storage provider ...n/articles/azure-functions/durable/quickstart-mssql.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits moderate Windows bias, particularly in the local database setup section. PowerShell is used exclusively for Docker commands, and SQL Server Express is suggested specifically for Windows users. Windows tools and patterns (PowerShell, SQL Server Express) are mentioned before Linux/macOS equivalents, and no bash/zsh or Linux-native command examples are provided for local database setup. However, Docker is cross-platform and the documentation notes PowerShell can be installed on Linux/macOS, partially mitigating the bias. Azure CLI is used for cloud steps, which is cross-platform.
Recommendations
  • Provide bash/zsh equivalents for all PowerShell commands, especially for Docker setup and validation steps.
  • Explicitly mention and provide examples for SQL Server Express installation and usage on Linux/macOS.
  • Include Linux/macOS-specific troubleshooting tips for Docker and SQL Server setup.
  • Reorder sections to present cross-platform options first, or present Windows and Linux/macOS instructions side by side.
  • Clarify that Visual Studio Code and Azure CLI are cross-platform and provide links to Linux/macOS installation guides.
GitHub Create Pull Request
Azure Functions Build a serverless workflow using Durable Functions - Azure Functions ...unctions/durable/scenario-build-serverless-workflow.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation provides command-line instructions for Linux/macOS and Windows users, including PowerShell and Cmd tabs where relevant. However, Windows-specific tools and patterns (PowerShell, Cmd) are consistently presented alongside bash, sometimes with Windows variants shown first. The use of Windows-specific command syntax (e.g., 'py' instead of 'python3', '.venv\scripts\activate') and explicit PowerShell/Cmd examples demonstrates a moderate Windows bias. Linux/macOS instructions are present and generally complete, but Windows tooling and patterns are given equal or slightly more prominence.
Recommendations
  • Present Linux/macOS examples first where possible, especially in mixed tabs.
  • Clarify that 'py' may not be available on all Linux/macOS systems; recommend 'python3' as the default.
  • Ensure that bash instructions are always shown before Windows-specific shells unless usage data suggests otherwise.
  • Add explicit notes when Windows-only tools or patterns are used, and provide Linux/macOS equivalents or alternatives.
  • Consider grouping all platform instructions together for parity, rather than splitting by shell type.
  • Audit for any subtle assumptions (e.g., file paths, environment activation) that may differ between platforms and clarify for Linux/macOS users.
GitHub Create Pull Request
Azure Functions Create and Manage Function Apps in a Flex Consumption Plan ...in/articles/azure-functions/flex-consumption-how-to.md
Medium Priority View Details →
Scanned: 2026-01-13 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 demonstrates a moderate Windows bias. Visual Studio Code (VS Code) is presented as a primary development tool, but many advanced features (virtual networking, deployment storage, instance memory, always-ready instances, metrics, etc.) are unavailable in VS Code, which is cross-platform. However, the documentation does not provide Linux/macOS-specific examples or mention platform-specific differences in CLI usage, file paths, or deployment nuances. Powershell is included as a runtime, but there are no Bash or Linux shell-specific instructions or troubleshooting notes. Windows-centric tools and workflows (VS Code, Azure CLI, Azure Portal) are mentioned first or exclusively, and Linux users may encounter friction due to missing guidance for platform-specific issues (e.g., Python remote build note is the only exception).
Recommendations
  • Add explicit Linux/macOS shell (Bash/zsh) examples for common tasks, especially for zip creation, file paths, and environment setup.
  • Include troubleshooting notes for Linux/macOS users (e.g., file permissions, case sensitivity, remote build requirements for Python).
  • Clarify that VS Code is cross-platform, but highlight any Windows-specific limitations or differences.
  • Provide parity in examples for Powershell and Bash, especially in scripting and automation sections.
  • Mention alternative Linux-native editors (e.g., Vim, Emacs) or workflows where appropriate.
  • Ensure that CLI commands and scripts are tested and documented for both Windows and Linux/macOS environments.
GitHub Create Pull Request
Azure Functions App settings reference for Azure Functions ...ain/articles/azure-functions/functions-app-settings.md
Medium Priority View Details →
Scanned: 2026-01-13 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 is generally cross-platform and covers both Windows and Linux scenarios for Azure Functions app settings. However, there are several instances of Windows bias: Windows-specific examples and terminology are sometimes presented first (e.g., environment variable delimiters, time zone settings, Node.js version setting), Windows tools (PowerShell) are referenced more heavily than Linux equivalents, and some settings are described as Windows-only without always providing Linux alternatives. PowerShell-specific configuration is documented in detail, while equivalent Linux shell or CLI patterns are not. In a few cases, Linux examples or instructions are missing or less prominent.
Recommendations
  • Ensure that all Windows-only settings are clearly marked and, where possible, provide Linux/macOS equivalents or workarounds.
  • Present examples for both Windows and Linux/macOS side-by-side, especially for environment variable syntax, file paths, and time zone settings.
  • Balance references to PowerShell with equivalent Bash/Azure CLI examples for managing app settings.
  • Where a setting is Windows-only (e.g., WEBSITE_NODE_DEFAULT_VERSION), provide explicit guidance for Linux users.
  • Review all sample values and code snippets to ensure Linux/macOS parity (e.g., avoid only using Windows-style paths like %HOME%).
GitHub Create Pull Request
Azure Functions Azure OpenAI embeddings input binding for Azure Functions ...unctions/functions-bindings-openai-embeddings-input.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides code examples for multiple languages, including C#, Java, JavaScript, TypeScript, Python, and PowerShell. However, PowerShell is the only shell scripting language featured, and its inclusion may indicate a Windows bias, as PowerShell is primarily used on Windows. Additionally, the PowerShell example is given its own section, and configuration details are described in terms of function.json and run.ps1, which are Windows-centric patterns. There are no Bash or Linux shell examples, nor are Linux/macOS-specific tools or patterns mentioned. The order of examples and configuration sections tends to place Windows/PowerShell content before Linux alternatives, if any.
Recommendations
  • Add equivalent examples using Bash or other Linux/macOS shell scripting languages to provide parity with PowerShell.
  • Explicitly mention cross-platform compatibility for configuration files and scripting, clarifying any OS-specific differences.
  • Include notes or examples for Linux/macOS users, such as how to run or configure Azure Functions bindings using their native tools.
  • Balance the order of examples so that Windows and Linux/macOS approaches are presented equally.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides code examples for multiple languages, including C#, Java, JavaScript, TypeScript, Python, and PowerShell. However, only PowerShell is represented as a shell scripting example, with no equivalent Bash or Linux shell example provided. The PowerShell example includes both a function.json and a run.ps1 file, reinforcing a Windows-centric approach for scripting and configuration. There is no mention of Linux shell scripting, nor are Linux/macOS-specific tools or patterns referenced.
Recommendations
  • Add Bash or Linux shell script examples alongside PowerShell to ensure parity for Linux/macOS users.
  • Explicitly mention that PowerShell examples can be run on Linux/macOS (if true), or provide guidance for Linux users.
  • Include notes or links to cross-platform scripting approaches for Azure Functions.
  • Ensure that configuration instructions do not assume Windows-only tooling or file formats.
GitHub Create Pull Request
Azure Functions Azure Functions Core Tools reference ...cles/azure-functions/functions-core-tools-reference.md
Medium Priority View Details →
Scanned: 2026-01-13 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 for Azure Functions Core Tools shows mild Windows bias. The page references func.exe in the description, which is a Windows-specific executable extension. The '--managed-dependencies' option is noted as only supported for the PowerShell worker runtime, which is most commonly used on Windows. Several references to local storage emulators and trusted certificate creation are phrased in a way that assumes Windows usage, and the use of .pfx files for HTTPS certificates is more common on Windows. There are no explicit Linux/macOS command examples or notes about platform differences, and some features (like log streaming for Linux Consumption plans) are noted as not supported, but alternatives are not provided. The documentation does not provide parity in examples or troubleshooting for Linux/macOS users.
Recommendations
  • Replace func.exe in the description with platform-neutral terminology (e.g., 'func' executable).
  • Add explicit Linux/macOS command examples or notes where behavior differs, especially for certificate handling, storage emulators, and managed dependencies.
  • Clarify which features are Windows-only and provide Linux/macOS alternatives or workarounds where possible.
  • Ensure that references to PowerShell are balanced with Bash or other shell examples for cross-platform parity.
  • Where features are not supported on Linux (e.g., log streaming), link to alternative workflows or tools for Linux users.
GitHub Create Pull Request
Azure Functions Azure Functions Web PubSub output binding ...zure-functions/functions-bindings-web-pubsub-output.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides complete examples only for C# and JavaScript, with explicit notes stating that Python and PowerShell samples are pending and Java is not supported. There is no evidence of Windows-specific tools, PowerShell-heavy content, or Windows-first ordering. However, the lack of Linux/macOS-friendly language samples (e.g., Python) creates friction for non-Windows users.
Recommendations
  • Add complete Python examples, as Python is widely used on Linux/macOS.
  • Clarify PowerShell support and provide Bash or shell script equivalents if relevant.
  • Ensure troubleshooting and configuration sections include cross-platform guidance.
  • Provide parity in code samples for all supported languages, especially those popular on Linux/macOS.
GitHub Create Pull Request
Azure Functions Integration and automation platform options in Azure ...ctions/functions-compare-logic-apps-ms-flow-webjobs.md
Medium Priority View Details →
Scanned: 2026-01-13 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 shows moderate Windows bias. Windows-centric tools like PowerShell are mentioned for management, and Windows-specific technologies (Power Automate, WebJobs SDK as .NET console app) are described without equivalent Linux/macOS examples. PowerShell is listed as a supported language, but Linux/macOS alternatives (e.g., Bash, shell scripting) are not highlighted in main tables or examples. Windows tools and patterns are mentioned before cross-platform or Linux-native options, and there are no explicit Linux/macOS usage examples or guidance.
Recommendations
  • Add explicit Linux/macOS examples for management and development tasks (e.g., using Bash, Azure CLI, or shell scripts).
  • Highlight cross-platform capabilities and tools (such as Azure CLI, Visual Studio Code) equally with Windows tools.
  • Include Linux/macOS-specific guidance for running and deploying WebJobs and Functions, especially for local development.
  • List Linux/macOS supported languages and package managers in main comparison tables, not just in footnotes.
  • Provide parity in example workflows, showing both Windows and Linux/macOS approaches where relevant.
GitHub Create Pull Request
Azure Functions Enable private site access to Azure Functions ...zure-functions/functions-create-private-site-access.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively guides users to create a Windows Server virtual machine, with no mention of Linux-based VM options or instructions. All screenshots and step-by-step VM creation instructions are Windows-specific, and there are no parallel examples or notes for Linux users. This creates friction for users who prefer or require Linux environments.
Recommendations
  • Include instructions and screenshots for creating a Linux-based virtual machine (e.g., Ubuntu) alongside the Windows example.
  • Explicitly mention that either Windows or Linux VMs can be used for this scenario, and provide guidance for both.
  • Where VM OS-specific steps are required (such as RDP for Windows or SSH for Linux), provide parallel instructions for each.
  • Ensure that any subsequent steps (such as accessing the VM or deploying code) are not OS-specific, or provide alternatives for both Windows and Linux.
GitHub Create Pull Request
Azure Functions Deployment technologies in Azure Functions ...s/azure-functions/functions-deployment-technologies.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific deployment technologies (e.g., Source control, Local Git, FTPS) are called out as 'Windows-only' in the availability table, with limited or no Linux equivalents. Windows deployment patterns (Kudu/SCM site) are described in more detail and often first. Examples and instructions for deployment tools (Visual Studio, Azure CLI, Core Tools) are presented in a Windows-centric manner, and Linux-specific considerations are often relegated to later sections or footnotes. Some deployment methods (Source control, Local Git, FTPS) are unavailable for Linux Consumption plans, and workarounds are not always provided.
Recommendations
  • Provide explicit Linux/macOS examples and workflows for all deployment methods, especially where Windows-only methods are called out.
  • Where deployment technologies are unavailable for Linux, offer alternative Linux-compatible approaches or guidance.
  • Ensure parity in documentation depth and order: present Linux and Windows instructions side-by-side or in parallel tabs.
  • Clarify limitations for Linux users and link to relevant workaround documentation.
  • Highlight cross-platform tools (e.g., Azure Functions Core Tools) and their usage on Linux/macOS.
  • Add more detail on Linux deployment scenarios, especially for CI/CD and remote build.
GitHub Create Pull Request
Azure Functions host.json reference for Azure Functions 2.x ...b/main/articles/azure-functions/functions-host-json.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page is generally cross-platform, but there are several instances of Windows bias. The 'managedDependency' feature is described as PowerShell-only, with references to Windows-centric tools (e.g., requirements.psd1, PowerShell article). Some settings (e.g., snapshotConfiguration.tempFolder, shadowCopyFolder) default to Windows environment variables and folder conventions (e.g., %TEMP%, LOCALAPPDATA, APPDATA), with no mention of Linux/macOS equivalents. In these cases, Windows paths and conventions are referenced first or exclusively. The console logging section does mention Linux-specific behavior, but overall, Linux/macOS users may need to infer or research platform-specific details.
Recommendations
  • For settings that default to Windows environment variables or folders (e.g., tempFolder, shadowCopyFolder), explicitly document the behavior and defaults on Linux/macOS, including typical paths (e.g., /tmp).
  • Where features are PowerShell-only (managedDependency), clarify if there are equivalent mechanisms for other languages/runtimes and provide links or notes for Linux/macOS users.
  • When referencing environment variables or file paths, provide both Windows and Linux/macOS examples side-by-side.
  • Audit all examples and descriptions to ensure Linux/macOS users are not left to guess how features work on their platforms.
GitHub Create Pull Request
Azure Functions Monitor executions in Azure Functions .../main/articles/azure-functions/functions-monitoring.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page is generally cross-platform but contains notable Windows bias in the 'Streaming Logs' section. The built-in log streaming feature is described as unavailable for Linux Consumption plan apps, with no Linux alternative or workaround provided. Additionally, the documentation references Azure portal and App Service platform tools, which are more commonly associated with Windows environments, and does not mention Linux-native tools or command-line alternatives for log streaming or diagnostics.
Recommendations
  • Provide explicit Linux/macOS alternatives or workarounds for log streaming, such as using Azure CLI, Kudu, or other cross-platform tools.
  • Clarify which features are Windows-only and offer guidance for Linux users to achieve similar monitoring outcomes.
  • Include examples or references for Linux/macOS environments where features differ, especially in sections discussing limitations.
  • Where possible, mention open-source or platform-agnostic tools for diagnostics and log analysis.
GitHub Create Pull Request
Azure Functions Develop legacy C# class library functions using Azure Functions ...cles/azure-functions/functions-dotnet-class-library.md
Medium Priority View Details →
Scanned: 2026-01-13 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-specific tools (Visual Studio, MSI installer, Windows paths) are mentioned first or exclusively in several places. PowerShell and Windows command-line examples are provided, while Linux/macOS equivalents (e.g., bash, zsh, Linux package managers) are missing or relegated to secondary references. The ReadyToRun example only shows a Windows runtime identifier, and installation instructions for Azure Functions Core Tools focus on Windows methods. Linux/macOS users may need to infer or search for platform-specific steps.
Recommendations
  • Add explicit Linux/macOS examples for command-line operations, including bash/zsh equivalents for package installation and usage.
  • Include Linux/macOS runtime identifiers (e.g., linux-x64, osx-x64) in ReadyToRun and deployment examples.
  • Present cross-platform instructions side-by-side or in tabs, rather than listing Windows methods first.
  • Reference Linux/macOS tools and editors (e.g., JetBrains Rider, VS Code on Linux) where appropriate.
  • Clarify any platform-specific limitations or differences in tooling and environment setup.
GitHub Create Pull Request
Azure Functions Continuously update function app code using Azure Pipelines ...icles/azure-functions/functions-how-to-azure-devops.md
Medium Priority View Details →
Scanned: 2026-01-13 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 exhibits a moderate Windows bias. Windows-based build agents ('windows-latest') are used by default for C# and PowerShell examples, with Linux agents ('ubuntu-latest') only mentioned for Java, JavaScript, and Python. Windows examples and terminology (e.g., PowerShell, Windows-based function apps) are often presented first or exclusively. The default deployment type is Windows, and Linux-specific instructions are sometimes secondary or require explicit configuration. There is limited discussion of Linux/macOS developer workflows outside of the YAML agent selection, and PowerShell is included as a primary language example, which is Windows-centric.
Recommendations
  • Present Linux/macOS examples and agent options alongside Windows examples, not after or as an alternative.
  • For C# and PowerShell, provide both 'windows-latest' and 'ubuntu-latest' agent YAML samples, noting any platform-specific requirements.
  • Clarify cross-platform compatibility for all build and deployment steps, especially for .NET and PowerShell.
  • Add explicit notes or sections for Linux/macOS developer workflows, including common tools and patterns.
  • Avoid presenting Windows as the default; instead, show both Windows and Linux options equally.
  • For PowerShell, mention cross-platform alternatives (e.g., bash, pwsh on Linux) and provide Linux-compatible examples where possible.
GitHub Create Pull Request
Azure Functions Configure function app settings in Azure Functions ...ns/functions-how-to-use-azure-function-app-settings.md
Medium Priority View Details →
Scanned: 2026-01-13 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 notable Windows bias. Examples and instructions frequently prioritize Windows tools (PowerShell, Windows-specific features) and omit or limit Linux-specific guidance. Many advanced features (Kudu, App Service editor, console) are unavailable or unsupported on Linux. Migration instructions and development limitations are often Windows-centric, with Linux options described as limited or deprecated. PowerShell examples are given equal or greater prominence than Azure CLI, and some features (like in-portal editing and plan migration) are explicitly Windows-only or have restricted Linux support.
Recommendations
  • Provide explicit Linux/macOS examples and workflows alongside Windows instructions, especially for advanced management and migration tasks.
  • Clearly indicate feature parity and limitations for Linux users at the beginning of each relevant section.
  • Offer alternative Linux-compatible tools or scripts where Windows tools (PowerShell, Kudu, App Service editor) are unavailable.
  • Update or expand CLI examples to cover Linux-specific scenarios, and ensure CLI instructions are not implicitly Windows-centric.
  • Document workarounds or best practices for Linux users where features are missing or deprecated.
  • Regularly review and update documentation as Linux support changes (e.g., Flex Consumption plan, retirement of Linux Consumption plan).
GitHub Create Pull Request
Azure Functions Azure Functions networking options ...ticles/azure-functions/functions-networking-options.md
Medium Priority View Details →
Scanned: 2026-01-13 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 exhibits several Windows-centric biases. Hybrid Connections are only supported for Windows, with Linux explicitly excluded. CLI and PowerShell examples are provided, but PowerShell is highlighted as a primary automation method. Subnet sizing recommendations mention Windows before Linux, and Windows requirements are listed first. There are no Linux/macOS-specific troubleshooting or configuration examples, and Windows hosting plans are referenced more frequently and with greater detail. Linux users may find critical features (Hybrid Connections) unavailable and must infer parity or workarounds for other scenarios.
Recommendations
  • Clearly indicate Linux/macOS support and limitations for all features, especially Hybrid Connections.
  • Provide Linux/macOS-specific configuration and troubleshooting examples where applicable.
  • Offer Bash or cross-platform CLI examples alongside PowerShell, and avoid presenting PowerShell first unless Windows-only.
  • List Linux requirements and recommendations alongside or before Windows equivalents to avoid Windows-first ordering.
  • Where features are Windows-only, suggest alternative approaches for Linux users or link to relevant resources.
GitHub Create Pull Request
Azure Functions Azure Functions Premium plan ...ain/articles/azure-functions/functions-premium-plan.md
Medium Priority View Details →
Scanned: 2026-01-13 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 exhibits several forms of Windows bias. Windows and PowerShell examples are consistently provided alongside Azure CLI, but Linux-specific instructions (e.g., bash scripts, Linux tooling) are absent. In the migration section, only Windows is supported, with Linux explicitly excluded. Throughout, PowerShell is presented as a primary automation tool, and Windows is often mentioned first or exclusively in feature tables and explanations.
Recommendations
  • Add explicit Linux/macOS shell examples (e.g., bash, zsh) where PowerShell is shown.
  • Clarify which CLI commands are cross-platform and note any OS-specific behaviors.
  • Where features are Windows-only (e.g., migration), provide alternative guidance or workarounds for Linux users, or clearly state the roadmap for Linux parity.
  • Balance the order of presentation so Linux is not always mentioned after Windows.
  • Include Linux-specific troubleshooting or configuration notes where relevant.
GitHub Create Pull Request
Azure Functions Create a function in Azure from the command line ...es/azure-functions/how-to-create-function-azure-cli.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates some Windows bias, notably in the Java section where command examples are provided for Bash, PowerShell, and Cmd, with Windows shells (PowerShell, Cmd) shown after Bash but still included. The Maven archetype flow references Windows-style paths (e.g., backslashes in file paths) and mentions setting JAVA_HOME, which is more commonly a friction point for Windows users. There is no explicit Linux/macOS example for setting environment variables or handling file paths. However, most other sections use cross-platform commands (func, az CLI) and do not restrict instructions to Windows tools. Linux tools like jq are mentioned in prerequisites, and Bash examples are present. The severity of bias is moderate, as Linux/macOS users can complete all tasks but may encounter minor friction or lack of parity in examples.
Recommendations
  • Provide explicit Linux/macOS examples for environment variable setup (e.g., export JAVA_HOME=/path/to/jdk).
  • Use forward slashes in file paths or clarify that both Windows and Linux/macOS paths are supported.
  • Ensure all command examples are shown for Bash/zsh and PowerShell/Cmd equally, or default to Bash first.
  • Add notes or callouts for platform-specific differences, such as handling secrets or file permissions.
  • Where possible, avoid Windows-centric terminology or ordering (e.g., mention Bash before PowerShell/Cmd).
GitHub Create Pull Request
← Previous Page 26 of 41 Next →