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 76-100 of 233 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-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 provides examples for Azure CLI (cross-platform), Azure PowerShell (Windows-centric), and the Azure Portal (web-based). However, PowerShell is given equal prominence to CLI, despite being Windows-focused. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is presented as a primary automation tool, which may not be available or preferred on Linux/macOS. Additionally, the documentation notes a Linux-specific limitation (hyphens in function names) but does not offer workarounds or alternatives for Linux users.
Recommendations
  • Add Bash or shell script examples for Linux/macOS users alongside Azure CLI and PowerShell.
  • Clarify that Azure CLI is fully cross-platform and recommend it as the preferred automation tool for non-Windows environments.
  • Explicitly mention that PowerShell examples are primarily for Windows users and provide parity for Linux/macOS users.
  • Offer guidance or workarounds for the Linux limitation regarding hyphens in function names.
  • Consider reordering examples to present Azure CLI (cross-platform) before PowerShell (Windows-centric).
GitHub Create Pull Request
Azure Functions Bindings for Durable Functions - Azure .../azure-functions/durable/durable-functions-bindings.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 🔧 Windows Tools
Summary
The documentation provides examples for multiple languages, including PowerShell, and frequently references Windows-centric tools and patterns (such as function.json and run.ps1 for PowerShell). PowerShell examples are included alongside other languages, but the documentation does not show any Linux-specific shell examples (e.g., Bash), nor does it mention Linux/macOS-specific tooling or patterns. The use of PowerShell and JSON-based configuration is more familiar to Windows users, and the absence of Linux/macOS equivalents may create friction for non-Windows users.
Recommendations
  • Add Linux/macOS shell (e.g., Bash) equivalents for PowerShell examples where possible.
  • Clarify that PowerShell examples can be run cross-platform, or provide explicit instructions for Linux/macOS users.
  • Mention Linux/macOS tooling and patterns (such as file paths, environment variable conventions, and shell usage) where relevant.
  • Ensure that references to configuration files (like function.json) include notes about editing them on different platforms.
  • Consider including a table or section that maps Windows/PowerShell commands to their Linux/macOS equivalents.
GitHub Create Pull Request
Azure Functions Durable entities - Azure Functions .../azure-functions/durable/durable-functions-entities.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 documentation is heavily focused on .NET/C# examples, which are typically associated with Windows environments. There is no mention of Windows-specific tools or PowerShell, but the ordering and depth of .NET examples (including advanced features like locking and class-based syntax) are much greater than for JavaScript or Python. Linux/macOS users (who may prefer Python or JavaScript) receive less detailed coverage, especially for advanced scenarios like entity coordination and locking, which are only shown in C#. There are no explicit references to Windows-only tools, but the .NET-centric approach may create friction for non-Windows users.
Recommendations
  • Provide equivalent advanced examples (e.g., entity coordination, locking) for JavaScript and Python, or explicitly state if such features are unavailable.
  • Balance the depth of examples and explanations across all supported languages, not just .NET/C#.
  • Add notes or tables summarizing feature parity and limitations for each language/platform.
  • Consider adding Linux/macOS-specific guidance or clarifications where relevant.
GitHub Create Pull Request
Azure Functions Work with access keys in Azure Functions .../main/articles/azure-functions/function-keys-how-to.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 provides both Azure CLI and PowerShell examples for managing access keys, but PowerShell scripts are given equal prominence and detail as CLI examples. PowerShell is a Windows-centric tool, while Azure CLI is cross-platform. There are no explicit Linux/macOS shell script examples (e.g., using curl or Bash), and PowerShell examples are presented in full script form, potentially making Windows users feel more supported. Additionally, some instructions mention modifying CLI commands to run in Windows terminals, but do not provide explicit Linux/macOS variants or troubleshooting tips.
Recommendations
  • Add explicit Linux/macOS shell (Bash) examples using curl for REST API calls, especially where PowerShell is used.
  • Clarify that Azure CLI commands work cross-platform and provide troubleshooting notes for common Linux/macOS issues.
  • When showing multiple methods, present CLI (cross-platform) examples before PowerShell (Windows-centric) ones.
  • Include notes or examples for using REST APIs with tools like curl or httpie, which are common on Linux/macOS.
  • Where PowerShell is used, mention that PowerShell Core is available cross-platform, but provide Bash alternatives.
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-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 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 UI. All NuGet package installation examples use PowerShell commands, with no Linux/macOS alternatives (e.g., dotnet CLI). The Azurite storage emulator is referenced, but instructions for installing or running it on Linux/macOS are missing. There are no explicit Linux/macOS development or deployment steps, and the overall workflow assumes a Windows-centric approach.
Recommendations
  • Provide equivalent instructions for Linux/macOS users, including using Visual Studio Code or JetBrains Rider for development.
  • Include dotnet CLI commands for NuGet package installation alongside PowerShell examples.
  • Add instructions for creating projects using command-line tools (dotnet new) on Linux/macOS.
  • Document how to install and run Azurite on Linux/macOS.
  • Ensure screenshots and UI references are not Windows-specific, or provide alternatives.
  • Explicitly mention cross-platform compatibility and any platform-specific caveats.
GitHub Create Pull Request
Azure Functions Create your function app resources in Azure using Bicep ...ure-functions/functions-create-first-function-bicep.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 Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and validating resources. However, Azure PowerShell is a Windows-centric tool and is presented as an equal alternative to Azure CLI, despite CLI being cross-platform. The documentation includes PowerShell examples for all language pivots and does not mention Linux/macOS-specific shell environments (e.g., Bash, zsh) or provide any Linux/macOS-specific notes. There is a subtle Windows-first bias in the inclusion and prominence of PowerShell, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
  • Clearly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add notes or sections clarifying that Azure PowerShell is primarily for Windows and may require additional installation steps on Linux/macOS.
  • Consider providing Bash/zsh shell examples for common operations, or at least mention that Azure CLI commands work natively in those environments.
  • Reorder examples to present Azure CLI first and clarify its cross-platform nature.
  • Add troubleshooting tips for Linux/macOS users if they encounter issues with PowerShell.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, especially in the local SQL Server setup section. PowerShell is used exclusively for scripting, and SQL Server Express is suggested specifically for 'your local Windows computer.' There are no Bash or Linux shell equivalents for database setup, and Windows-centric tools/patterns (PowerShell, SQL Server Express) are mentioned before Linux alternatives. The troubleshooting and validation steps also assume familiarity with Windows tooling. While Docker is cross-platform, the examples and instructions are primarily tailored for Windows users, creating friction for Linux/macOS users.
Recommendations
  • Provide Bash shell equivalents for all PowerShell commands, especially for Docker-based SQL Server setup and validation.
  • Explicitly mention and show how to install and use SQL Server Express or Docker images on Linux/macOS, not just Windows.
  • Include Linux/macOS-specific troubleshooting steps for Docker and SQL Server connectivity.
  • When referencing tools like SQL Server Express, clarify cross-platform alternatives (e.g., Azure Data Studio, sqlcmd) and provide installation instructions for Linux/macOS.
  • Present examples in both PowerShell and Bash, or use a neutral scripting language where possible.
  • Avoid phrases like 'your local Windows computer' unless alternatives are also shown.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page is generally cross-platform but contains a few notable Windows biases. Performance Counters are noted as unsupported on Linux, but no Linux alternatives are suggested. The built-in log streaming feature is described as unsupported for Linux Consumption plans, with the alternative (Live Metrics Stream) mentioned second. No explicit Linux/macOS command-line examples or tooling are provided, and the documentation does not address Linux-specific monitoring patterns or troubleshooting. Windows/portal-centric workflows are implicitly prioritized.
Recommendations
  • Explicitly mention Linux/macOS alternatives or workarounds for unsupported features (e.g., suggest using Live Metrics Stream or other tools for real-time logs on Linux).
  • Provide Linux/macOS-specific examples or references where Windows-only features are described as unsupported.
  • Add a table or section summarizing feature parity and differences between Windows and Linux hosting plans.
  • Where features are unavailable on Linux, link to relevant Azure documentation or community resources for Linux monitoring best practices.
  • Ensure that alternatives for unsupported features are described before or alongside Windows-centric features, not after.
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-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 page generally covers Azure Functions app settings in a cross-platform manner, but there are several instances of Windows bias. Some examples and settings are Windows-specific or mention Windows before Linux equivalents. PowerShell-specific settings are documented in detail, while Linux shell or Bash equivalents are not. Some settings, such as WEBSITE_NODE_DEFAULT_VERSION, are explicitly marked as 'Windows only' without Linux alternatives. In a few cases, environment variable syntax uses Windows-style paths (e.g., %HOME%) without Linux examples. The use of Azure PowerShell and CLI is recommended for programmatic management, but Linux-native tools are not mentioned. Overall, while Linux is supported and referenced, Windows patterns and tools are often prioritized or exclusively documented.
Recommendations
  • For every Windows-specific setting or example (e.g., WEBSITE_NODE_DEFAULT_VERSION), provide the Linux equivalent or clarify Linux behavior.
  • When showing environment variable paths (e.g., AzureWebJobs_TypeScriptPath), include both Windows (%HOME%) and Linux ($HOME) syntax.
  • For PowerShell-heavy sections, add equivalent Bash or shell scripting examples for Linux/macOS users.
  • When recommending Azure CLI or PowerShell, mention that Azure CLI is cross-platform and provide Bash usage examples.
  • Ensure that any references to Windows-only features or behaviors are clearly marked, and alternatives for Linux/macOS are provided where possible.
  • Where settings differ in interpretation between Windows and Linux (e.g., delimiters in setting names), provide explicit Linux examples and clarify differences.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides only PowerShell scripts for identifying function apps to migrate, with no equivalent Bash, Azure CLI, or Linux/macOS shell examples. The instructions for managing Azure subscriptions and querying resources are Windows/PowerShell-centric, and there is no mention of cross-platform alternatives. This creates friction for Linux/macOS users who may not use PowerShell or Cloud Shell, and may not be familiar with Windows-specific tools.
Recommendations
  • Add equivalent Azure CLI (az) commands and Bash examples for identifying function apps and managing subscriptions.
  • Explicitly mention that Azure CLI and Bash can be used on Linux/macOS, and provide sample scripts.
  • Where PowerShell is referenced, clarify its availability on Linux/macOS and provide installation guidance, or prefer cross-platform tools.
  • Ensure that all critical migration steps (such as resource discovery and management) have platform-agnostic instructions.
GitHub Create Pull Request
Azure Functions Bindings for Durable Functions - Azure .../azure-functions/durable/durable-functions-bindings.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides examples for multiple programming languages, including PowerShell, which is primarily a Windows-centric tool. PowerShell examples are given equal prominence alongside other languages, and instructions for configuring triggers and clients in PowerShell reference Windows-specific patterns (function.json and run.ps1). There is no explicit mention of Linux/macOS alternatives for PowerShell users, nor any clarification about cross-platform compatibility. The documentation does not provide Linux shell or bash examples, and PowerShell is presented as a first-class citizen, which may create friction for Linux/macOS users.
Recommendations
  • Clarify that PowerShell examples are intended for Windows environments and note any cross-platform limitations.
  • Provide equivalent examples for bash or other common Linux/macOS shells where relevant.
  • Add notes or links about running Azure Functions with PowerShell on Linux/macOS, including any required setup or differences.
  • Consider reordering or grouping examples so that Windows-specific tools (like PowerShell) do not appear before or more prominently than cross-platform alternatives.
  • Explicitly mention that function.json and run.ps1 patterns are not required for non-Windows environments, or provide guidance for Linux/macOS users.
GitHub Create Pull Request
Azure Functions Work with access keys in Azure Functions .../main/articles/azure-functions/function-keys-how-to.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing access keys, but PowerShell examples are given equal prominence and detail as CLI, and no explicit Linux/macOS shell (e.g., Bash) examples are provided outside of Azure CLI. The CLI examples are described as running in Azure Cloud Shell, but there is no guidance or example for running them in a local Linux/macOS terminal. Additionally, PowerShell scripts are presented in full, but no equivalent Bash scripts are shown. There are minor notes about modifying CLI commands for Windows terminals, but not vice versa.
Recommendations
  • Add explicit Bash shell examples for key management tasks, especially for local Linux/macOS environments.
  • Clarify that Azure CLI commands work natively on Linux/macOS and provide instructions/examples for running them outside Azure Cloud Shell.
  • Present CLI/Bash examples before PowerShell examples to avoid implicit Windows-first bias.
  • Where PowerShell scripts are shown, provide equivalent Bash scripts for parity.
  • Note any platform-specific differences or requirements for Linux/macOS 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-11 06:20
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides complete code examples only for C# and JavaScript, with explicit notes stating that Python and PowerShell samples are 'pending' and Java is 'not supported yet.' There is no evidence of Windows-specific tools, PowerShell-heavy content, or Windows-first ordering. However, the lack of Linux/macOS-friendly language samples (Python) creates friction for non-Windows users.
Recommendations
  • Add complete Python samples to ensure Linux/macOS users have parity with Windows users.
  • Clarify PowerShell support and provide examples if relevant, or remove PowerShell mention if not applicable.
  • Ensure all supported languages have equal coverage and working examples, especially those popular on Linux/macOS.
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-11 06:20
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 in its migration instructions. The only provided script for identifying function apps to migrate is a PowerShell script, and all CLI instructions use Azure PowerShell cmdlets. There are no equivalent examples using Bash, Azure CLI, or other Linux/macOS-friendly tools. This creates friction for users on Linux or macOS, who may not have access to PowerShell or prefer shell scripting. The page also references Visual Studio for publishing, which is primarily a Windows tool, without mentioning cross-platform alternatives like VS Code or CLI-based deployment.
Recommendations
  • Provide equivalent Azure CLI (az) commands and Bash scripts for identifying and managing function apps, alongside PowerShell examples.
  • Include instructions for using cross-platform tools (e.g., VS Code, Azure CLI) for publishing and updating function apps.
  • Explicitly mention platform-agnostic options for running scripts (e.g., Azure Cloud Shell supports Bash and PowerShell).
  • Add notes or links for Linux/macOS users on installing and using Azure Functions Core Tools and other relevant utilities.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the Java example, where only the Windows ffmpeg binary (ffmpeg.exe) is referenced, and no Linux equivalent or cross-platform guidance is provided. The Java code example and instructions assume a Windows-style executable and path, with no mention of Linux/macOS alternatives. Additionally, PowerShell is mentioned as an upload option before Linux equivalents, and the Java section lacks parity with the Python section, which provides Linux-specific guidance (such as chmod and mounting Azure Files).
Recommendations
  • In the Java example, provide instructions and code samples for both Windows (ffmpeg.exe) and Linux/macOS (ffmpeg) binaries, including notes on file permissions (e.g., chmod for Linux).
  • Clarify that the path and executable name may differ between operating systems, and provide guidance for detecting the OS and selecting the correct binary.
  • When listing upload options for Azure Files, mention Azure CLI and Linux-native tools before or alongside PowerShell, and provide explicit Linux/macOS command examples.
  • Ensure all code samples and instructions are cross-platform or provide OS-specific variants where necessary.
  • Add a note in the Java section similar to the Python section about file permissions and Linux deployment specifics.
GitHub Create Pull Request
Azure Functions How to disable functions in Azure Functions ...blob/main/articles/azure-functions/disable-function.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 Azure Portal, Azure CLI, and Azure PowerShell, with PowerShell (a Windows-centric tool) featured as a primary method. There is no mention of Linux/macOS-specific shell commands (e.g., Bash), nor are there examples using native Linux tools or scripting patterns. PowerShell examples are given equal prominence to CLI, and in some cases, PowerShell functionality is discussed even when it is not available for all features (e.g., slot settings). The documentation does not clarify cross-platform compatibility for CLI or PowerShell, and does not provide explicit Linux/macOS usage guidance.
Recommendations
  • Add explicit Bash/shell examples for Linux/macOS users alongside PowerShell examples.
  • Clarify that Azure CLI is cross-platform and provide installation/use guidance for Linux/macOS.
  • Indicate when PowerShell commands are Windows-only or provide instructions for using PowerShell Core on Linux/macOS.
  • Reorder examples so that CLI (cross-platform) comes before PowerShell (Windows-centric).
  • Add notes about any platform-specific limitations (e.g., hyphen limitation for Linux) in a more prominent location.
  • Include troubleshooting or tips for Linux/macOS users where relevant.
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-11 06:20
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, PowerShell) are mentioned before Linux alternatives, and Windows configuration steps are often described first. Some CLI examples use PowerShell syntax or reference Windows-only features. While Linux deployment and configuration are covered, Linux examples are sometimes less detailed or appear after Windows instructions. There are few explicit Linux/macOS code samples, and some instructions (e.g., ReadyToRun, debugging) are Windows-centric or omit Linux parity details.
Recommendations
  • Ensure all CLI examples are shown with both Windows (PowerShell/CMD) and Linux/macOS (bash) syntax, especially for Azure CLI commands.
  • Present Linux and macOS instructions alongside Windows, not after or in separate tabs, and avoid Windows-first ordering.
  • Add explicit Linux/macOS examples for project setup, debugging, and deployment, including VS Code and Azure CLI workflows.
  • Highlight any platform-specific limitations or differences clearly, and provide workarounds or alternatives for Linux/macOS users.
  • Include more references to Linux tools and patterns (e.g., bash scripts, Linux containers) where appropriate.
  • Review and update sections that mention Windows-only features (e.g., PowerShell, Visual Studio) to ensure Linux/macOS parity.
GitHub Create Pull Request
Azure Functions Durable Functions publishing to Azure Event Grid ...unctions/durable/durable-functions-event-publishing.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation shows a mild Windows bias, primarily in the storage emulator recommendations and local development instructions. The Azurite storage emulator is mentioned, but references to the legacy 'Storage Emulator' (which is Windows-only) are present without clarifying Linux/macOS alternatives. The instructions for local.settings.json use 'UseDevelopmentStorage=true', which only works with the Windows Storage Emulator, and do not explicitly guide Linux/macOS users to use Azurite or provide parity instructions. Additionally, screenshots and portal instructions are Windows-centric in style, and PowerShell is mentioned as an alternative to Azure CLI, but no Bash or Linux shell examples are given.
Recommendations
  • Remove references to the legacy Windows-only Storage Emulator, or clarify that Azurite should be used on Linux/macOS.
  • Explicitly provide instructions for installing and running Azurite on Linux/macOS, including sample connection strings.
  • When mentioning PowerShell, also mention Bash or provide equivalent Linux shell commands if relevant.
  • Ensure all CLI examples (Azure CLI) are tested and confirmed to work on Linux/macOS.
  • Add notes or sections for Linux/macOS users to clarify any platform-specific steps, especially for local development and debugging.
GitHub Create Pull Request
Azure Functions Durable Functions packages .../azure-functions/durable/durable-functions-packages.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents .NET (typically associated with Windows) as the primary runtime, with detailed package instructions for .NET in-process and .NET isolated users before mentioning other platforms. PowerShell (Windows-centric) is included as a first-class language in the SDK table and receives a dedicated note and migration guide link, whereas Linux/macOS-specific considerations or examples are absent. There are no explicit Linux/macOS examples, tools, or package management instructions, and the ordering of runtimes and repositories prioritizes Windows-centric technologies.
Recommendations
  • Add explicit instructions or examples for Linux/macOS users, such as how to install and reference packages using Linux tooling (e.g., dotnet CLI, npm, pip, Maven) on those platforms.
  • Balance the order of presentation so that non-Windows runtimes (Node.js, Python, Java) are not always listed after .NET/PowerShell.
  • Include notes or tips for Linux/macOS users regarding compatibility, common issues, or platform-specific steps.
  • Provide parity in migration guidance and troubleshooting for non-Windows platforms, similar to the PowerShell note.
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-11 06:20
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. It consistently references Visual Studio (Windows-only) as the primary development environment, with only a brief mention of Visual Studio Code as an alternative. Project creation instructions are tailored to Windows (e.g., 'Windows Classic Desktop'), and NuGet package installation is shown exclusively using PowerShell commands, with no Linux/macOS CLI equivalents. The use of the Azurite storage emulator is mentioned, but instructions for running it on Linux/macOS are absent. There are no explicit examples or guidance for Linux or macOS users throughout the page.
Recommendations
  • Provide explicit instructions and examples for Linux/macOS users, including project creation using cross-platform tools (e.g., dotnet CLI).
  • Include NuGet package installation commands using 'dotnet add package' or 'nuget' CLI, which work on all platforms.
  • Offer guidance for running Azurite on Linux/macOS (e.g., via npm or Docker).
  • Reorder examples so that cross-platform approaches (e.g., Visual Studio Code, dotnet CLI) are presented before or alongside Windows-specific tools.
  • Clarify which steps are platform-specific and provide alternatives where possible.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias, particularly in the local database setup section, which exclusively provides PowerShell commands and references SQL Server Express 'on your local Windows computer' before mentioning Docker. There are no Linux/macOS-specific command examples for local SQL Server setup, and troubleshooting steps reference Docker Desktop (primarily a Windows/macOS tool). The use of PowerShell as the only scripting language for local setup may create friction for Linux users, who are more likely to use Bash. While Docker is cross-platform, the instructions and examples are tailored to Windows users, and Linux users must adapt them without guidance.
Recommendations
  • Provide Bash shell equivalents for all PowerShell setup commands, especially for Docker-based SQL Server setup.
  • Explicitly mention and show how to install and run SQL Server Express or Docker on Linux/macOS, not just Windows.
  • Include troubleshooting steps for Linux users (e.g., using 'docker ps', 'docker exec', file path differences).
  • Reference cross-platform SQL clients (e.g., Azure Data Studio, sqlcmd) with installation instructions for Linux/macOS.
  • Avoid language like 'on your local Windows computer' unless alternatives are shown for other platforms.
  • Where PowerShell is used, clarify that Bash can be used and provide sample Bash scripts.
GitHub Create Pull Request
Azure Functions Tutorial: Add Azure OpenAI text completions to your functions in Visual Studio Code ...zure-functions/functions-add-openai-text-completion.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 is cross-platform, but several instructions and examples assume or prioritize Windows workflows. Powershell is included as a first-class language, and some steps (such as starting Azurite and debugging) use commands and shortcuts that are Windows-centric (e.g., F5, Ctrl+C, Azurite: Start). There is no mention of Linux/macOS-specific alternatives or shell commands, and no explicit guidance for non-Windows users. The Azurite emulator is referenced, but installation and usage instructions are not platform-specific. The documentation does not provide parity for Linux/macOS users in terms of terminal commands, keyboard shortcuts, or troubleshooting.
Recommendations
  • Add explicit instructions for Linux/macOS users, including terminal commands for starting Azurite (e.g., 'npx azurite' or 'azurite' CLI).
  • Clarify that Visual Studio Code and Azure Functions Core Tools are cross-platform, and provide installation links for Linux/macOS.
  • Include alternative keyboard shortcuts for macOS (e.g., Cmd+F5, Cmd+C) where relevant.
  • Provide bash/zsh shell command equivalents for steps currently shown only with Windows-centric commands or PowerShell.
  • Note any differences in file paths, environment variables, or permissions that may affect Linux/macOS users.
  • Ensure troubleshooting and cleanup instructions include Linux/macOS-specific guidance.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides dedicated code examples for PowerShell, which is primarily a Windows-centric language and shell. PowerShell is given its own section with both code and configuration examples, while there are no equivalent examples for Bash, Linux shell scripting, or macOS-specific workflows. Additionally, the PowerShell example appears before the Python example, suggesting a Windows-first ordering in the example sections. There is no mention of Linux-specific tools, nor are there any examples for Linux/macOS shell environments.
Recommendations
  • Add equivalent examples for Bash or other Linux/macOS shells to ensure parity for non-Windows users.
  • Include notes or guidance for Linux/macOS users on how to accomplish the same tasks using their native tools.
  • Consider reordering examples so that platform-neutral or widely-used languages (e.g., Python, JavaScript) appear before platform-specific ones like PowerShell.
  • Explicitly state cross-platform compatibility and provide links to relevant Linux/macOS documentation where appropriate.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools and patterns (PowerShell, Visual Studio) are mentioned explicitly and often before cross-platform or Linux alternatives. Examples and management instructions reference PowerShell and Visual Studio, with less emphasis on Linux-native tools or workflows. There are no explicit Linux/macOS examples or mentions of Bash, shell scripting, or Linux-specific development environments, despite Azure's cross-platform support.
Recommendations
  • Add explicit Linux/macOS examples for management and development tasks, such as using Bash, Azure CLI, or VS Code on Linux.
  • Mention Linux-native tools and workflows alongside Windows tools (e.g., show both PowerShell and Bash commands for automation and management).
  • Clarify cross-platform support for SDKs, CLI tools, and development environments.
  • Include references to Linux/macOS documentation or quickstarts where relevant.
  • Avoid listing Windows tools (PowerShell, Visual Studio) before cross-platform alternatives unless contextually necessary.
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-11 06:20
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. It references func.exe in the description, which is a Windows-specific executable name, and includes options/features that are only available for PowerShell (a Windows-centric runtime). Some features, such as managed dependencies, are noted as PowerShell-only, and there are references to the Microsoft Azure Storage Emulator, which is Windows-only, without mentioning Linux alternatives. In several places, Windows tools or patterns are mentioned first or exclusively, and Linux/macOS equivalents are not always provided or are mentioned secondarily. There are also features (such as log streaming for Linux Consumption plans) that are not supported, but the documentation does not provide Linux workarounds or alternatives.
Recommendations
  • Use platform-neutral terminology in the description (e.g., refer to 'func' rather than 'func.exe').
  • When mentioning PowerShell-specific features, clarify Linux/macOS alternatives or limitations.
  • Where Windows-only tools (e.g., Storage Emulator) are referenced, provide equivalent Linux/macOS options (such as Azurite) and link to their documentation.
  • Explicitly note platform limitations for features not supported on Linux/macOS and suggest alternative workflows.
  • Ensure that examples and instructions are provided for Linux/macOS users alongside Windows, especially for installation, local development, and debugging.
  • Avoid listing Windows tools or patterns first unless they are universally applicable.
GitHub Create Pull Request
← Previous Page 4 of 10 Next →