Azure Functions

711
Total Pages
610
Linux-Friendly Pages
101
Pages with Bias
14.2%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

233 issues found
Showing 51-75 of 233 flagged pages
Azure Functions Migrate apps from Azure Functions version 3.x to 4.x ...rticles/azure-functions/migrate-version-3-version-4.md
Medium Priority View Details →
Scanned: 2026-01-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell script as the only example for identifying function apps to migrate, with no equivalent Azure CLI, Bash, or cross-platform example. PowerShell is a Windows-centric tool (despite cross-platform support, it's less common on Linux/macOS), and its exclusive use here may create friction for Linux/macOS users. Additionally, references to Azure PowerShell precede mention of other cross-platform tools.
Recommendations
  • Provide an equivalent Azure CLI (az) or Bash script example for identifying function apps to migrate, and present it alongside or before the PowerShell example.
  • Explicitly mention that users can use Azure CLI or the Azure Portal as alternatives to PowerShell for cross-platform compatibility.
  • Where possible, use neutral/cross-platform terminology (e.g., 'Use Azure CLI or PowerShell') rather than defaulting to PowerShell.
  • Consider adding a table or section comparing PowerShell and Azure CLI commands for common migration tasks.
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 06:17
Reviewed by: LLM Analysis
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 (Visual Studio, Azure PowerShell) are mentioned before or alongside cross-platform options, and Windows configuration steps are often described first. Some CLI examples use Azure PowerShell or reference Windows-specific settings before Linux equivalents. Linux-specific instructions and examples are present but sometimes appear after Windows ones or are less detailed. There are few explicit Linux/macOS shell examples, and some deployment/configuration sections focus on Windows workflows.
Recommendations
  • Ensure Linux/macOS examples (e.g., bash, Azure CLI) are presented alongside or before Windows/PowerShell equivalents.
  • Balance tool recommendations by highlighting cross-platform editors (VS Code, JetBrains Rider) and CLI workflows before Windows-only tools.
  • Provide explicit Linux/macOS shell commands and configuration steps wherever Windows/PowerShell commands are shown.
  • Clarify which steps are OS-agnostic and which are platform-specific, grouping instructions by platform where necessary.
  • Expand troubleshooting and deployment sections with Linux/macOS-specific guidance and examples.
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 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides command examples for Windows-specific shells (PowerShell, Cmd) alongside bash, and sometimes lists Windows options before Linux/macOS. In several places, Windows tools and patterns (such as PowerShell and Cmd) are explicitly called out, and Linux/macOS instructions are not always presented first or with equal prominence. Some sections (e.g., virtual environment activation for Python) offer Windows-specific instructions in more detail than Linux/macOS. There are also places where Windows command syntax is shown before or alongside bash, but Linux/macOS users may need to infer their own equivalents.
Recommendations
  • Present Linux/macOS instructions before Windows ones, or side-by-side with equal prominence.
  • Ensure all command examples are available for bash/zsh and not just Windows shells.
  • Add explicit Linux/macOS instructions wherever Windows-specific tools (PowerShell, Cmd) are mentioned.
  • Use generic, cross-platform CLI commands where possible, and clarify OS-specific differences only when necessary.
  • Review all code blocks and tabs to ensure Linux/macOS users are not required to infer steps from Windows examples.
GitHub Create Pull Request
Azure Functions Migrate apps from Azure Functions version 1.x to 4.x ...rticles/azure-functions/migrate-version-1-version-4.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 notable Windows bias in its migration instructions, especially in the initial steps for identifying function apps to migrate. Only PowerShell scripts are provided for listing apps and setting the active subscription, with no equivalent Azure CLI or Bash examples for Linux/macOS users. The use of Azure PowerShell and references to Visual Studio (a primarily Windows tool) further reinforce this bias. Linux alternatives are not mentioned or provided, and Windows-centric tools and patterns are presented first and exclusively in critical sections.
Recommendations
  • Provide Azure CLI and Bash script examples alongside PowerShell for identifying and managing function apps, ensuring Linux/macOS users have clear instructions.
  • Explicitly mention cross-platform tools (e.g., VS Code, Azure CLI) in addition to Visual Studio, and clarify which steps can be performed on Linux/macOS.
  • Add notes or sections that address Linux/macOS environments, including any differences in workflow or tool usage.
  • Reorder examples or provide parallel instructions so that Windows and Linux/macOS users are equally supported.
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 06:17
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. Examples for configuring Premium plan features are consistently provided for Azure CLI and Azure PowerShell, but no Linux-specific shell examples (e.g., Bash) are given. PowerShell examples are included throughout, which are primarily relevant for Windows users. In the migration section, it is explicitly stated that migration between Consumption and Premium plans is only supported on Windows, with no Linux alternative or workaround. In some tables and feature lists, Windows options are listed before Linux, and the region scale-out table shows higher limits for Windows in most regions, with some regions not supporting Linux at all.
Recommendations
  • Add explicit Bash examples for all CLI commands to demonstrate Linux parity.
  • Clarify that Azure CLI commands work cross-platform and provide notes for Linux/macOS users where relevant.
  • Where PowerShell is mentioned, provide equivalent Bash or shell script examples.
  • In migration section, offer guidance or alternatives for Linux users, or clarify future support plans.
  • In tables and lists, alternate or randomize order of Windows and Linux, or present both equally.
  • Highlight any feature gaps for Linux and provide links to tracking issues or roadmap.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides code examples for C# and JavaScript, but explicitly notes that complete samples for Python and PowerShell are pending, and that Java is not supported yet. There are no OS-specific instructions, but the lack of Python and PowerShell examples means Linux/macOS users (who often use these languages) have less guidance. No Windows-specific tools, patterns, or PowerShell-heavy bias is present.
Recommendations
  • Add complete Python and PowerShell code samples to ensure parity for Linux/macOS users.
  • Clarify any OS-specific setup steps if relevant (e.g., function.json usage, CLI commands).
  • Ensure troubleshooting and logging sections include cross-platform guidance (e.g., for enabling console logging on Linux/macOS).
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-12 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 moderate Windows bias. The introductory description refers to the tool as 'func.exe', which is a Windows-specific executable extension. Several options and features (such as managed dependencies) are noted as PowerShell-only, and references to the Microsoft Azure Storage Emulator (Windows-only) appear before mentioning alternatives. Some instructions, such as certificate generation for HTTPS, imply Windows workflows (trusted certificate creation on 'your computer', which is typically Windows-centric). There is little mention of Linux/macOS equivalents, and examples do not clarify platform-specific differences or provide Linux/macOS-specific guidance.
Recommendations
  • Use platform-neutral terminology (e.g., 'func' instead of 'func.exe') in the description and throughout the documentation.
  • When referencing platform-specific features (such as PowerShell managed dependencies or the Storage Emulator), clearly indicate their platform limitations and provide Linux/macOS alternatives (e.g., Azurite for storage emulation).
  • Add explicit examples or notes for Linux/macOS users, especially for tasks like certificate generation, local development, and storage emulation.
  • Ensure that any references to file paths, shell commands, or environment setup include Linux/macOS syntax and instructions.
  • Where features are Windows-only, provide clear guidance or workarounds for Linux/macOS users.
GitHub Create Pull Request
Azure Functions Create your function app resources using Azure Resource Manager templates ...ns/functions-create-first-function-resource-manager.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying ARM templates. While Azure CLI is cross-platform, the inclusion of Azure PowerShell examples (which are most commonly used on Windows) and the use of PowerShell syntax for all language pivots in the Azure PowerShell tab indicate a Windows bias. The PowerShell examples are given equal prominence to CLI, and there is no mention of Linux/macOS-specific shell usage (e.g., Bash, zsh), nor are there any Linux/macOS-specific troubleshooting notes or alternative instructions. The documentation does not explicitly state that PowerShell Core is available cross-platform, which may cause confusion for non-Windows users. Additionally, the use of Cloud Shell is mentioned, which is cross-platform, but the PowerShell tab may suggest Windows-first thinking.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and recommend CLI for cross-platform usage.
  • Explicitly state that PowerShell Core is available on Linux/macOS, or link to installation instructions for non-Windows users.
  • Add Bash or zsh examples for Linux/macOS users, especially in the 'Deploy the template' section.
  • Add troubleshooting notes or links for Linux/macOS users regarding shell differences and environment setup.
  • Consider reordering examples to show Azure CLI (cross-platform) first and PowerShell second, or clearly indicate platform applicability.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively guides users to create a Windows Server VM, with no mention of Linux VM options or examples. All screenshots and instructions assume Windows, and there is no parity for Linux users in the VM creation or access steps. This creates friction for users who prefer or require Linux environments.
Recommendations
  • Add instructions and screenshots for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM steps.
  • Explicitly mention that either Windows or Linux VMs can be used for this scenario.
  • Provide guidance for connecting to Linux VMs via Azure Bastion (using SSH), including any differences in authentication or browser experience.
  • Ensure that subsequent steps (such as accessing the function app from the VM) include notes for both Windows and Linux users.
GitHub Create Pull Request
Azure Functions Azure Functions custom handlers .../articles/azure-functions/functions-custom-handlers.md
Medium Priority View Details →
Scanned: 2026-01-12 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 Windows bias in several areas. Executable references and examples consistently use the Windows-style '.exe' extension (e.g., 'handler.exe') as the default, with Linux/macOS equivalents only mentioned parenthetically or not at all. File system and configuration examples show Windows conventions first, and deployment instructions do not clarify platform-specific steps or differences. There are no explicit Linux/macOS command-line or tooling examples, and the documentation does not provide parity in demonstrating how to build, run, or deploy custom handlers on non-Windows platforms.
Recommendations
  • Provide explicit examples for Linux/macOS, such as using './handler' instead of 'handler.exe', and clarify when platform-specific naming or permissions are required.
  • Show file system layouts and configuration snippets for both Windows and Linux/macOS, or use platform-neutral naming in examples.
  • Include instructions or notes on building and running custom handler executables on Linux/macOS, including permissions (e.g., chmod +x), and mention any platform-specific dependencies.
  • Ensure deployment steps cover Linux/macOS scenarios, such as using bash scripts or native build tools.
  • When referencing tools or commands, provide both Windows (PowerShell/CMD) and Linux/macOS (bash/zsh) equivalents.
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-12 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. Windows deployment methods (such as source control, local Git, FTPS) are called out as 'Windows-only' in the technology availability table, with Linux equivalents not always described or available. Windows tools (Visual Studio, Kudu) are mentioned before Linux alternatives, and examples often default to Windows scenarios. Some deployment methods (source control, local Git, FTPS) are unavailable or unsupported for Linux Consumption plans, with limited guidance for Linux users. Linux-specific instructions (such as remote build settings) are present but less prominent and often appear after Windows explanations.
Recommendations
  • Provide Linux/macOS-specific examples and workflows for all deployment methods, especially where Windows-only methods are called out.
  • Ensure that Linux deployment options are described with equal detail and prominence as Windows options.
  • Where deployment technologies are unavailable for Linux, offer clear alternative workflows or guidance for Linux users.
  • Reorder examples and tool mentions to avoid always listing Windows tools first; consider grouping by OS or providing parallel instructions.
  • Expand documentation on Linux container deployments, remote builds, and external package URL methods to match the depth of Windows sections.
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-12 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 notable Windows bias. Examples and instructions frequently reference Windows-specific tools (PowerShell, Kudu, App Service Editor, Windows-only portal features) and provide PowerShell examples alongside Azure CLI, but do not offer Linux/macOS shell equivalents or clarify cross-platform differences. Windows features and limitations are often discussed first or exclusively, while Linux support is limited, deprecated, or omitted, especially for plan migration and in-portal development. Some features are marked as Windows-only, and Linux users are directed to local development or CLI without parity in portal tooling.
Recommendations
  • Provide explicit Linux/macOS shell examples (e.g., Bash) where PowerShell is used, especially for scripting and automation.
  • Clarify which Azure CLI commands work identically on Linux/macOS and note any platform-specific caveats.
  • Add instructions or alternatives for Linux users when features (Kudu, App Service Editor, portal console) are Windows-only or unavailable.
  • Reorder examples to present cross-platform (CLI) solutions before Windows-specific tools.
  • Clearly indicate feature availability and limitations for Linux/macOS in each relevant section, and link to Linux-specific guidance where available.
  • Where plan migration is not supported on Linux, provide alternative strategies or workarounds for Linux users.
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-12 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 moderate Windows bias. Windows-specific tools and patterns (such as Visual Studio and Windows installers) are mentioned first or exclusively in several sections. Examples for installing packages are provided for Command Prompt and PowerShell, but not for Bash or Linux shells. The ReadyToRun example only shows a Windows runtime identifier, and Visual Studio is emphasized as the primary development environment. There is minimal mention of Linux/macOS equivalents, and Linux-specific instructions or examples are missing in key areas.
Recommendations
  • Add explicit examples and instructions for Linux/macOS users, such as Bash commands for package installation and project setup.
  • Include ReadyToRun publishing examples for Linux (e.g., 'linux-x64') and macOS runtime identifiers.
  • Present cross-platform development tools (such as Visual Studio Code and Azure Functions Core Tools via npm) with equal prominence to Visual Studio.
  • Ensure that command-line instructions are shown for both Windows (cmd, PowerShell) and Linux/macOS (Bash, zsh).
  • Clarify any platform-specific limitations or differences, especially in sections referencing local development and deployment.
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-12 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 demonstrates a moderate Windows bias. Windows-based examples (e.g., 'windows-latest' agent pools) are shown first for C# and PowerShell, with Linux alternatives mentioned secondarily or only in comments. PowerShell is presented as a language option, but only with Windows-based build agents. The default deployment type is Windows, and Linux-specific instructions are often marked as exceptions or require explicit configuration. Some features (like deployment slots) are not available for Linux in certain plans, and this is noted as a limitation rather than providing alternative Linux guidance.
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which is shown first to avoid implicit prioritization.
  • For C# and PowerShell, provide explicit Linux build agent examples where possible (e.g., for .NET Core apps, show both 'windows-latest' and 'ubuntu-latest' pipelines).
  • Clarify which features are Windows-only and offer Linux alternatives or workarounds where feasible.
  • For PowerShell, mention cross-platform options (PowerShell Core on Linux) and provide Linux-compatible pipeline samples if supported.
  • Avoid language in comments or notes that implies Windows is the default or preferred platform.
  • Where features are unavailable for Linux, link to roadmap or alternatives for Linux users.
GitHub Create Pull Request
Azure Functions Azure Functions networking options ...ticles/azure-functions/functions-networking-options.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Azure Functions networking options exhibits moderate Windows bias. The Hybrid Connections feature is explicitly stated as Windows-only, with Linux support unavailable. In automation and configuration examples, PowerShell and Azure CLI are both provided, but PowerShell is shown as an equal option, which may reinforce Windows-centric workflows. In subnet sizing recommendations, Windows is mentioned before Linux, and minimum subnet sizes for Windows are listed first. There are no Linux-specific troubleshooting or configuration examples, and the Hybrid Connections section lacks any Linux alternatives or guidance.
Recommendations
  • Clearly indicate Linux/macOS alternatives or limitations for features like Hybrid Connections, and provide guidance or workarounds where possible.
  • Present Linux examples (e.g., Azure CLI) before or alongside PowerShell, and clarify cross-platform compatibility for all automation steps.
  • In tables and recommendations, alternate the order of Windows and Linux, or present them side-by-side to avoid Windows-first bias.
  • Add troubleshooting steps and configuration guidance specific to Linux-hosted function apps.
  • Where features are Windows-only, link to feature requests or roadmap items for Linux parity.
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-12 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 types of Windows bias. Windows-specific tools (Azure PowerShell) are consistently presented alongside Azure CLI, and in some cases, migration instructions are Windows-only. Examples and instructions often mention Windows before Linux, and some features (such as plan migration) are explicitly unavailable for Linux users. There is a lack of Linux/macOS-specific guidance, and no alternative shell or scripting examples are provided for Linux users.
Recommendations
  • Add explicit Linux/macOS instructions and examples wherever CLI or scripting is shown, including bash/zsh equivalents if relevant.
  • Clarify which commands and features are cross-platform, and note any platform-specific limitations up front.
  • Provide parity in migration guidance for Linux users, or clearly document workarounds or alternatives.
  • Avoid listing Windows tools (PowerShell) before cross-platform tools (Azure CLI), or present CLI as the primary method.
  • Where features are unavailable on Linux, suggest alternative approaches or link to roadmap/feedback channels.
GitHub Create Pull Request
Azure Functions Create and deploy function code to Azure using Visual Studio Code ...cles/azure-functions/how-to-create-function-vs-code.md
Medium Priority View Details →
Scanned: 2026-01-12 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 generally supports cross-platform development, but there are several instances of Windows bias. Windows tools and patterns are mentioned (e.g., PowerShell, .NET, Windows-specific install links), and troubleshooting advice references Windows-specific issues before Linux/macOS. PowerShell is included as a primary language, but Linux shell equivalents are not shown. Some installation instructions and troubleshooting steps prioritize Windows or reference Windows-specific behaviors, while Linux/macOS alternatives are less visible or missing.
Recommendations
  • Ensure all language and tool installation links include Linux/macOS equivalents, not just Windows.
  • Where PowerShell is shown, provide bash/zsh examples for Linux/macOS users.
  • In troubleshooting, mention Linux/macOS issues and solutions alongside Windows, not after.
  • For SDK/runtime installation, provide explicit Linux/macOS instructions and links, not just generic or Windows-focused ones.
  • Avoid referencing Windows-specific behaviors (e.g., WSL Bash) without also discussing Linux/macOS terminal issues.
  • Review all included links and ensure parity for Linux/macOS users.
GitHub Create Pull Request
Azure Functions Deploy a PyTorch model as an Azure Functions application ...n/articles/azure-functions/machine-learning-pytorch.md
Medium Priority View Details →
Scanned: 2026-01-12 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 provides examples for Bash, PowerShell, and Cmd, but Windows-specific tools and patterns (e.g., 'py' launcher, registry edits) are mentioned first or exclusively. Windows troubleshooting steps are detailed, while Linux/macOS issues are not. The use of Visual Studio Code is suggested without mentioning Linux/macOS alternatives. Some commands (e.g., activating virtual environments, copying files) are shown for all platforms, but Windows examples and terminology appear first or are more detailed.
Recommendations
  • Ensure Linux/macOS troubleshooting steps are included alongside Windows-specific advice (e.g., path length issues, permissions).
  • Present Bash (Linux/macOS) examples before Windows examples, or alternate the order to avoid implicit prioritization.
  • Mention Linux/macOS alternatives to Windows tools (e.g., suggest editors like VS Code, but also mention Vim, nano, etc.).
  • Provide parity in error messages and solutions for Linux/macOS users.
  • Clarify when commands are platform-specific and provide clear guidance for each OS.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing Azure PowerShell scripts for discovery tasks and referencing Visual Studio for deployment, both of which are Windows-centric tools. There are no CLI/bash examples or explicit instructions for Linux/macOS users, and Windows tooling is mentioned without Linux alternatives. This may create friction for users on non-Windows platforms.
Recommendations
  • Provide equivalent Azure CLI (az) commands for identifying function apps and managing subscriptions, as Azure CLI is cross-platform.
  • Include deployment instructions using Azure Functions Core Tools and Azure CLI, which work on Linux/macOS, alongside Visual Studio steps.
  • Add notes or examples for common Linux/macOS editors (e.g., VS Code) and workflows.
  • Explicitly mention that all steps can be performed on Linux/macOS and highlight any platform-specific considerations.
  • Where PowerShell is used, offer bash/zsh alternatives or clarify that PowerShell Core is available cross-platform.
GitHub Create Pull Request
Azure Functions Migrate apps from Azure Functions version 3.x to 4.x ...rticles/azure-functions/migrate-version-3-version-4.md
Medium Priority View Details →
Scanned: 2026-01-12 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 by providing only a PowerShell script for identifying function apps to migrate, with no equivalent Bash, Azure CLI, or Linux-native example. Windows/PowerShell tooling is referenced first and exclusively in critical migration steps, and there is no mention of Linux/macOS alternatives for these tasks. This creates friction for users on non-Windows platforms who may not have access to PowerShell or prefer native tools.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for identifying function apps to migrate, alongside the PowerShell script.
  • Explicitly mention that Azure CLI and Bash can be used on Linux/macOS and provide sample commands.
  • When referencing tools (e.g., Azure Functions Core Tools), clarify installation steps for Linux/macOS and ensure parity in instructions.
  • Avoid assuming PowerShell availability; offer cross-platform alternatives in all critical workflow steps.
GitHub Create Pull Request
Azure Functions Migrate Consumption plan apps to Flex Consumption in Azure Functions ...unctions/migration/migrate-plan-consumption-to-flex.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides migration guidance for both Linux and Windows Azure Functions apps, but there is a notable Windows bias. Windows examples and instructions are often presented first, and Windows-specific tools and patterns (such as deployment via Visual Studio, Visual Studio Code, and references to Windows file share locations) are mentioned before or more prominently than their Linux equivalents. While Linux-specific migration commands (az functionapp flex-migration) are highlighted, the overall structure and many examples default to Windows-centric workflows, especially in the premigration and deployment sections. Some CLI scripts and portal instructions assume Windows conventions, and infrastructure-as-code examples reference Windows tools first.
Recommendations
  • Ensure Linux examples and instructions are presented with equal prominence and ordering as Windows examples.
  • Add explicit Linux shell script examples where only Windows/PowerShell scripts are shown.
  • Highlight Linux-native deployment tools and workflows (e.g., Azure CLI, bash, zip/squashfs handling) before or alongside Windows tools.
  • Clarify platform-specific differences in storage, deployment, and configuration, and provide parity in step-by-step guidance.
  • Where infrastructure-as-code is referenced, provide Linux-first or neutral examples (e.g., bash, az CLI, ARM/Bicep/Terraform) and avoid defaulting to Windows-centric tools.
GitHub Create Pull Request
Azure Functions How to target Azure Functions runtime versions ...b/main/articles/azure-functions/set-runtime-version.md
Medium Priority View Details →
Scanned: 2026-01-12 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 provides both Windows and Linux guidance, but Windows-specific tools (PowerShell, Visual Studio) and examples are presented more prominently and with greater detail. PowerShell examples are included for both viewing and updating settings, while Linux users are limited to Azure CLI and lack parity for some operations (e.g., no portal or PowerShell support for linuxFxVersion). Windows scenarios (such as Visual Studio publishing) are described in detail, while Linux equivalents are not mentioned. The order of examples and the presence of Windows-specific notes indicate a mild Windows-first bias.
Recommendations
  • Add Linux-specific examples for all operations, including portal usage where possible.
  • Clarify which features are unavailable on Linux and provide alternative workflows.
  • Include parity for developer tooling (e.g., mention VS Code or CLI-based deployment for Linux).
  • Present examples in a neutral order or group by platform to avoid implicit prioritization.
  • Explicitly state limitations for Linux (e.g., Consumption plan pinning) and suggest workarounds.
GitHub Create Pull Request
Azure Functions Storage considerations for Azure Functions ...ain/articles/azure-functions/storage-considerations.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation presents several sections where Windows-specific details, examples, and terminology are prioritized or exclusively provided. Windows hosting plans and PowerShell are mentioned before Linux equivalents, and some examples or guidance lack Linux parity. Linux-specific instructions are often relegated to later sections or presented as exceptions, and in some cases, Linux users may need to infer or adapt instructions themselves.
Recommendations
  • Ensure that all example commands and configuration settings are provided for both Windows and Linux environments, with equal prominence.
  • When referencing hosting plans or features, clarify Linux support and limitations upfront, rather than focusing on Windows first.
  • Provide Linux-specific troubleshooting and deployment guidance alongside Windows instructions, not as a separate or secondary section.
  • Include Linux CLI and scripting examples (e.g., Bash) wherever PowerShell is used, especially in sections about mounting file shares, configuring app settings, and deployment automation.
  • Review all references to tools and features (e.g., Azure Files, deployment automation) to ensure Linux users have clear, actionable steps.
GitHub Create Pull Request
Azure Functions Update Language Versions in Azure Functions ...n/articles/azure-functions/update-language-versions.md
Medium Priority View Details →
Scanned: 2026-01-12 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 instructions and examples are consistently presented before Linux equivalents, especially in Azure portal and CLI tabs. PowerShell is included as a first-class language throughout, and Windows-specific configuration commands and patterns are detailed. Linux instructions are present but sometimes relegated to secondary tabs or notes, and certain features (e.g., Python on Windows) are explicitly unsupported, with Linux users redirected. Some CLI examples for Linux are less detailed than their Windows counterparts.
Recommendations
  • Present Windows and Linux instructions in parallel, rather than Windows-first ordering.
  • Ensure all CLI and portal examples for Windows have equally detailed Linux equivalents.
  • Highlight Linux-specific limitations and workarounds more clearly, and provide direct links to relevant Linux documentation.
  • Include Linux-first examples for languages that are Linux-only (e.g., Python), and avoid unnecessary redirection.
  • Consider a summary table comparing Windows and Linux feature support for quick reference.
GitHub Create Pull Request
Azure Functions Bring dependencies and third-party libraries to Azure Functions ...icles/azure-functions/bring-dependency-to-functions.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias in several ways. In the Java example, the code references 'ffmpeg.exe', which is a Windows-specific binary, and does not mention Linux alternatives or provide guidance for Linux users. The instructions for setting the BASE_PATH environment variable are tailored to Azure's Linux hosting, but the example itself is Windows-centric. Additionally, when discussing uploading dependencies to Azure Files, PowerShell is mentioned as an option alongside Azure CLI and Portal, but Linux-specific tools (e.g., rsync, SCP) are not referenced. The Java section does not provide a Linux example for executing binaries, and the order of presentation tends to favor Windows tools and patterns.
Recommendations
  • Provide explicit Linux/macOS examples for Java, including using 'ffmpeg' (not 'ffmpeg.exe') and handling file permissions.
  • Mention Linux-native tools (e.g., rsync, SCP) for uploading files to Azure Files, in addition to PowerShell and Azure CLI.
  • Clarify cross-platform differences in file paths, environment variables, and binary execution for both Python and Java.
  • Avoid using Windows-only binaries in generic examples, or provide parallel Linux/macOS instructions.
  • Present examples for both platforms side-by-side, or clearly indicate platform-specific steps.
GitHub Create Pull Request
← Previous Page 3 of 10 Next →