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 526-550 of 1023 flagged pages
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-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides PowerShell-based examples for setting up a local SQL Server instance in Docker, with no equivalent Bash or Linux/macOS shell examples. The instructions and troubleshooting steps reference Windows tools and patterns first, and do not offer explicit guidance for Linux/macOS users, despite Docker and PowerShell being cross-platform. This creates friction for non-Windows users, especially those unfamiliar with PowerShell or who prefer Bash.
Recommendations
  • Add Bash shell examples alongside PowerShell for Docker-based SQL Server setup, including database creation and validation commands.
  • Explicitly note that all PowerShell commands can be run on Linux/macOS if PowerShell is installed, but provide native Bash alternatives for users who do not wish to install PowerShell.
  • Clarify any OS-specific nuances, such as file paths or Docker networking, for Linux/macOS users.
  • Ensure troubleshooting steps reference both Windows and Linux/macOS environments, including how to browse container files without Docker Desktop.
  • Consider listing Linux/macOS tools (e.g., sqlcmd, Azure CLI) and their installation instructions in the prerequisites section.
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-02-19 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 generally aims for cross-platform parity, but there are several areas where Windows tools, commands, or patterns are mentioned first or exclusively. Windows-specific configuration (such as .NET Framework settings) is often described before Linux equivalents, and some CLI examples default to Windows-centric syntax or ordering. Azure PowerShell is listed as a primary provisioning method, while Linux-native tools (like Bash or shell scripting) are not highlighted. In some sections, Linux-specific nuances are only mentioned in passing or as secondary notes.
Recommendations
  • Ensure that all command-line examples (especially for deployment, configuration, and debugging) include both Windows and Linux syntax, with equal prominence.
  • When listing tools or provisioning methods (e.g., Azure CLI, PowerShell), alternate the order or provide parallel examples for both Windows and Linux users.
  • Where PowerShell is referenced, provide Bash or shell script equivalents for Linux/macOS users.
  • In sections where Windows-specific configuration is discussed (such as .NET Framework or ReadyToRun), ensure Linux configuration is equally detailed and not relegated to a secondary position.
  • Add explicit Linux/macOS troubleshooting and environment setup guidance where relevant, especially for local development and debugging.
  • Review the order of presentation in tables and lists to avoid consistently putting Windows tools or workflows first.
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-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. PowerShell is used for all local database setup commands, and Windows-centric tools (SQL Server Express) are mentioned before their Linux equivalents. While Docker is used for cross-platform database hosting, only PowerShell scripts are provided for setup, with no Bash or Linux-specific instructions. The troubleshooting section also assumes familiarity with Windows/Docker Desktop. Linux/macOS users must adapt the PowerShell commands or use alternatives, which creates friction.
Recommendations
  • Provide equivalent Bash shell commands for Docker-based SQL Server setup, especially for Linux/macOS users.
  • Mention Linux-native SQL Server installation options (e.g., apt/yum install for SQL Server tools) alongside SQL Server Express.
  • Clarify that PowerShell commands are cross-platform, but offer Bash alternatives for common scenarios.
  • Add explicit instructions or links for Linux/macOS users to install and use sqlcmd and Docker.
  • Reorder sections to avoid Windows-first bias (e.g., mention Docker-based SQL Server before SQL Server Express).
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-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell-based examples for setting up a local SQL Server instance in Docker, and references SQL Server Express as an option for local development specifically on Windows. While it notes PowerShell can be installed on Linux/macOS, all setup commands are given in PowerShell syntax, with no equivalent bash or shell script examples. The SQL Server Express option is described as 'on your local Windows computer', and Windows terminology (e.g., Visual Studio Code prompts, screenshots) is used throughout. Linux/macOS users must adapt the PowerShell commands or use bash equivalents, which are not provided.
Recommendations
  • Provide bash/zsh shell script examples for Docker-based SQL Server setup, alongside PowerShell.
  • Clarify that SQL Server Express is available on Linux/macOS, or recommend Docker as the cross-platform default.
  • Add explicit instructions or links for Linux/macOS users on how to run the setup commands in their native shell.
  • Ensure screenshots and UI instructions are not Windows-specific, or add notes for Linux/macOS differences.
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-02-17 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 moderate Windows bias, particularly in the section on setting up a local SQL Server instance with Docker. PowerShell commands are used exclusively for database setup, and Windows-specific patterns (such as referencing SQL Server Express on Windows) are mentioned before Linux alternatives. No explicit Bash or Linux/macOS shell examples are provided for Docker setup, and troubleshooting steps reference Windows tools and folder structures. While Docker and PowerShell are cross-platform, the lack of Bash/Linux-specific instructions may create friction for Linux/macOS users.
Recommendations
  • Provide equivalent Bash shell commands for Docker-based SQL Server setup, including database creation and validation.
  • Mention Linux/macOS installation and usage patterns for SQL Server Express and Docker more explicitly.
  • Add troubleshooting guidance for Linux/macOS users, such as file path differences and permissions.
  • Where PowerShell is used, clarify that Bash alternatives exist and link to relevant resources.
  • Ensure screenshots and instructions in Visual Studio Code are not Windows-centric (e.g., keyboard shortcuts, UI differences).
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-02-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias, particularly in the section on setting up a local SQL Server instance using Docker. PowerShell scripts are provided for database setup and validation, with no equivalent Bash or shell examples for Linux/macOS users. The instructions and troubleshooting steps reference Windows tools and folder structures first, and do not offer explicit Linux/macOS alternatives. While Docker is cross-platform, the use of PowerShell and lack of Bash examples creates friction for non-Windows users.
Recommendations
  • Provide Bash/zsh shell script equivalents for all PowerShell commands, especially for Docker-based SQL Server setup and validation.
  • Explicitly mention that the Docker setup works on Linux/macOS, and clarify any OS-specific differences (such as file paths or Docker command syntax).
  • Add troubleshooting guidance for Linux/macOS users, including how to locate the mssql-tools folder and run sqlcmd.
  • Ensure that instructions for editing files (like local.settings.json) and running Azure Functions Core Tools are OS-neutral or include platform-specific notes.
  • Where possible, show both Windows and Linux/macOS command examples side-by-side.
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-02-15 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 moderate Windows bias, particularly in the section on setting up a local SQL Server instance. PowerShell commands are used exclusively for Docker setup, and Windows tools like SQL Server Express are mentioned before Linux alternatives. No explicit Linux/macOS shell (bash) examples are provided for database setup, and troubleshooting steps reference Windows-centric paths and tools. While Docker is cross-platform, the instructions and examples are tailored toward Windows users, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent bash/zsh shell commands for Docker setup and SQL Server initialization, alongside PowerShell examples.
  • Mention Linux-native SQL Server installation options (e.g., apt/yum install for SQL Server tools) and clarify how to run Docker commands on Linux/macOS.
  • List Linux/macOS tools (such as Azure Data Studio, sqlcmd, or VS Code extensions) equally with Windows tools for database management.
  • Ensure troubleshooting steps reference Linux/macOS file paths and common issues.
  • Consider showing bash examples first or side-by-side with PowerShell to signal parity.
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-02-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell-based examples for setting up a local SQL Server instance in Docker, and references SQL Server Express as a local development option specifically for Windows. While it mentions that PowerShell can be installed on Linux/macOS and that Docker-based SQL Server is cross-platform, the step-by-step commands and troubleshooting are PowerShell-centric. There are no equivalent Bash or shell script examples for Linux/macOS users, and Windows tools (SQL Server Express) are mentioned before Docker as local options.
Recommendations
  • Add Bash/zsh shell script examples for Docker setup and database creation, alongside PowerShell.
  • Explicitly mention and provide instructions for using Docker on Linux/macOS, including any OS-specific caveats.
  • Clarify that SQL Server Express is Windows-only and recommend Docker as the primary cross-platform local development option.
  • Provide troubleshooting steps relevant to Linux/macOS environments (e.g., file permissions, Docker networking).
  • Ensure that all CLI commands (e.g., az CLI, sqlcmd) are shown in a way that is OS-agnostic or with clear platform-specific notes.
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-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias in the local SQL Server setup section. PowerShell is used exclusively for scripting the Docker-based SQL Server instance, and no equivalent Bash or shell script is provided for Linux/macOS users. The troubleshooting and validation steps also assume PowerShell usage. While Docker and SQL Server are cross-platform, the examples and instructions are presented primarily from a Windows/PowerShell perspective, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent Bash shell script examples for setting up the SQL Server Docker container, creating the database, and validating the installation.
  • Explicitly mention that all Docker commands can be run from Bash on Linux/macOS, and show the syntax differences where relevant.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., file permissions, Docker group membership).
  • Where PowerShell is used for variable assignment and command composition, show how to do the same in Bash.
  • Clarify that Visual Studio Code and Azure Functions Core Tools are fully supported on Linux/macOS, and link to installation guides for those platforms.
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-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation is generally cross-platform, but there are several areas where Windows-specific tools, behaviors, and issues are mentioned before Linux equivalents or without Linux parity. Examples include references to PowerShell managed dependencies, Windows build issues for Python apps, and default behaviors that assume Windows environments (such as certificate creation for HTTPS). Windows-specific terminology (like 'command prompt') and tools are referenced more frequently, and Windows issues are discussed in detail, while Linux/macOS guidance is less prominent.
Recommendations
  • Ensure Linux/macOS-specific instructions and caveats are provided wherever Windows-specific issues are mentioned (e.g., Python packaging/build guidance).
  • Where Windows tools or behaviors are referenced (such as certificate creation, command prompt, PowerShell), add equivalent Linux/macOS instructions or clarify cross-platform differences.
  • When discussing managed dependencies or worker runtimes, clarify Linux/macOS support and provide examples for those platforms.
  • Review the order of examples and tool references to avoid consistently mentioning Windows first; alternate or group by platform where appropriate.
  • Add explicit notes or links for Linux/macOS users where friction or workarounds are required.
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-02-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 notable Windows/PowerShell bias in the local SQL Server setup section. PowerShell is used exclusively for Docker commands, and no equivalent Bash or shell script examples are provided for Linux/macOS users. The troubleshooting steps and validation commands also use PowerShell syntax, and the initial suggestion for local SQL Server mentions Windows before Docker. While Docker is cross-platform, the lack of Linux/macOS-specific instructions or examples creates friction for non-Windows users.
Recommendations
  • Provide Bash shell script equivalents for all PowerShell commands, especially for Docker setup and validation steps.
  • Explicitly mention and demonstrate how to run Docker and SQL Server setup on Linux/macOS, including any required permissions or differences.
  • Reorder instructions or add parallel sections so that Linux/macOS users see their options presented equally or first.
  • Include troubleshooting notes relevant to Linux/macOS environments (e.g., file permissions, Docker networking).
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-02-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation for Azure Functions Core Tools is generally cross-platform, but there are several subtle Windows biases. Windows tools and behaviors (such as .pfx certificate handling, trusted certificate creation, and PowerShell managed dependencies) are mentioned without Linux/macOS equivalents or with Windows-specific caveats shown first. The documentation references Windows behaviors and issues (e.g., Python packaging on Windows for Linux deployment) before Linux/macOS, and some options (like managed dependencies) are PowerShell-specific. There are no explicit Linux/macOS command examples or troubleshooting tips, and Windows terminology (e.g., 'command prompt') is used throughout.
Recommendations
  • Add explicit Linux/macOS examples and troubleshooting tips alongside Windows-specific notes.
  • Where Windows-only features or behaviors are described (e.g., certificate creation, Python packaging), provide equivalent Linux/macOS instructions or clarify differences.
  • Avoid using Windows terminology (e.g., 'command prompt') as the default; use 'terminal' or clarify OS-specific terms.
  • Mention cross-platform tools and patterns equally, and ensure Linux/macOS users are not left to infer their workflow.
  • For PowerShell-specific features, clarify their scope and provide alternatives for Bash/zsh users where possible.
GitHub Create Pull Request
Azure Functions Azure Functions networking options ...ticles/azure-functions/functions-networking-options.md
Medium Priority View Details →
Scanned: 2026-02-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 configuring virtual network triggers, but the PowerShell example is given equal prominence and appears immediately after the CLI example. There is no explicit Linux/macOS-specific guidance or troubleshooting, and Hybrid Connections are described as Windows-only without alternative Linux approaches. Some subnet sizing guidance distinguishes Windows and Linux, but overall, Windows tools and patterns are referenced as much or more than Linux equivalents, and Linux users may need to infer their own workflows.
Recommendations
  • Provide explicit Linux/macOS guidance for automation and troubleshooting steps, including Bash or CLI-only workflows.
  • Clarify that Azure CLI commands work cross-platform and highlight them as the preferred method for Linux/macOS users.
  • When listing automation examples, show CLI/Bash first, then PowerShell, or group them by OS.
  • For Hybrid Connections, explicitly state alternatives or workarounds for Linux users, or link to relevant Linux documentation.
  • Add troubleshooting steps for Linux/macOS environments, especially for network issues.
  • Ensure screenshots and portal instructions are OS-neutral or note any Windows-specific UI differences.
GitHub Create Pull Request
Azure Functions Tutorial: Trigger Azure Functions on blob containers using an event subscription ...s/azure-functions/functions-event-grid-blob-trigger.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The tutorial is heavily oriented around Visual Studio Code and its Azure extensions, which are cross-platform but often associated with Windows workflows. All instructions and examples use Visual Studio Code commands and GUI interactions, with no mention of CLI alternatives (such as Azure CLI or PowerShell vs Bash). The documentation does not provide Linux/macOS-specific examples or workflows, but it does not explicitly require Windows-only tools. The use of Azurite and Visual Studio Code is cross-platform, but the documentation assumes Visual Studio Code as the primary development environment, which may create friction for Linux/macOS users preferring CLI or other editors.
Recommendations
  • Add alternative instructions using Azure CLI for creating storage accounts, blob containers, event subscriptions, and deploying function apps.
  • Explicitly mention that Azurite and Visual Studio Code are cross-platform and provide links to installation guides for Linux/macOS.
  • Provide Bash shell examples alongside PowerShell or dotnet CLI commands where relevant.
  • Include a section on how to perform the same tasks without Visual Studio Code, for users who prefer terminal-based workflows.
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-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell in its local SQL Server setup instructions. The Docker-based SQL Server setup is presented exclusively with PowerShell commands, and while a note mentions PowerShell is available on Linux/macOS, no equivalent Bash or shell script examples are provided. The troubleshooting section and validation steps also use PowerShell syntax. Linux/macOS users must adapt these steps themselves, creating friction. Additionally, the page often presents Windows-centric tools (e.g., SQL Server Express) before mentioning cross-platform alternatives.
Recommendations
  • Provide equivalent Bash shell script examples for Docker-based SQL Server setup and validation, alongside PowerShell.
  • Explicitly mention and demonstrate how to run Docker commands in Bash on Linux/macOS, including environment variable handling.
  • Include troubleshooting steps relevant to Linux/macOS users, such as file path differences or Docker nuances.
  • List cross-platform tools (e.g., Docker, SQLCMD) before Windows-specific ones (e.g., SQL Server Express) and clarify their applicability.
GitHub Create Pull Request
Azure Functions Deployment technologies in Azure Functions ...s/azure-functions/functions-deployment-technologies.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally presents deployment technologies in a cross-platform manner, but there is a subtle Windows bias in several areas. Windows-specific deployment options (e.g., source control, local Git, FTPS) are mentioned as 'Windows-only' without always providing Linux alternatives or clarifying Linux limitations. Examples and tool recommendations (Visual Studio, Azure CLI, Core Tools) are often presented with Windows-centric language or order. Some sections, such as remote build, describe Windows behavior first and in more detail, while Linux instructions are secondary. However, Linux deployment options (Docker, external package URL, Flex Consumption) are covered, and Linux-specific caveats are noted.
Recommendations
  • Where deployment methods are Windows-only, explicitly link to Linux alternatives or clarify Linux limitations and workarounds.
  • Present examples and tool instructions for both Windows and Linux in parallel, rather than Windows-first.
  • Add more Linux/macOS-specific examples (e.g., CLI commands, VS Code usage on Linux, Core Tools usage on Linux/macOS).
  • Clarify which features are unavailable or behave differently on Linux, and provide guidance for Linux users.
  • Ensure that tool recommendations (e.g., Visual Studio Code, Core Tools) are not presented as Windows-centric, and highlight their cross-platform nature.
GitHub Create Pull Request
Azure Functions Azure Functions networking options ...ticles/azure-functions/functions-networking-options.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides Azure Functions networking options for all hosting plans, but there are subtle signs of Windows bias. In the 'Hybrid Connections' section, Windows support is highlighted, and Linux is explicitly unsupported. In the 'Virtual network triggers' section, CLI, PowerShell, and portal instructions are given, but PowerShell is presented as a first-class option, and Linux-specific guidance is missing. Throughout, there are no explicit Linux/macOS examples or troubleshooting tips, and Windows-specific subnet sizing is mentioned before Linux. However, most features are cross-platform, and Linux support is generally referenced.
Recommendations
  • Add Linux/macOS-specific examples and troubleshooting steps where relevant, especially for automation and CLI usage.
  • Clarify parity for PowerShell and Azure CLI usage, noting any limitations for Linux users.
  • In subnet sizing tables and guidance, present Linux and Windows requirements equally, not Windows-first.
  • Where features are Windows-only (e.g., Hybrid Connections), clearly state alternatives or workarounds for Linux users.
  • Include explicit Linux/macOS testing and configuration scenarios, especially in sections about automation and troubleshooting.
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-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page presents Azure PowerShell as the sole method for identifying function apps to migrate, without offering equivalent CLI or Bash examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell is mentioned before any cross-platform alternatives, which are absent.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell scripts for identifying function apps, as Azure CLI is fully cross-platform.
  • Explicitly mention that PowerShell scripts can be run on Linux/macOS if PowerShell Core is installed, but provide CLI/Bash alternatives for parity.
  • Where possible, present cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools.
  • Review other sections for implicit Windows-centric assumptions (e.g., Visual Studio references) and clarify cross-platform options (e.g., VS Code, dotnet CLI).
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-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Missing Linux Example
Summary
The documentation provides both Windows and Linux guidance, but Windows/PowerShell examples and explanations are often presented first or in greater detail. Azure PowerShell is featured as a primary method for Windows, while Linux users are limited to Azure CLI and portal methods. Some sections (like pinning runtime versions) offer more detailed Windows instructions and Visual Studio-specific notes, while Linux instructions are more concise and lack parity in tooling (e.g., no PowerShell or portal support for linuxFxVersion).
Recommendations
  • Ensure Linux instructions are given equal prominence and detail as Windows instructions, including example order and depth.
  • Where possible, provide Linux-specific examples for portal operations or clarify limitations explicitly.
  • Add notes about alternative Linux tooling (such as Bash scripts or relevant Linux-native tools) if Azure CLI is not sufficient.
  • Consider grouping Windows and Linux instructions side-by-side or using tabs to avoid implicit prioritization.
  • Clarify in the introduction that some features (like PowerShell or Visual Studio integration) are Windows-specific, and offer Linux alternatives where possible.
GitHub Create Pull Request
Azure Functions Azure Functions networking options ...ticles/azure-functions/functions-networking-options.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and Azure portal, but PowerShell examples are included alongside CLI, and Hybrid Connections are described as Windows-only. The Hybrid Connections section is Windows-focused, and PowerShell is presented as a primary automation tool. Linux-specific guidance is limited, and Linux parity is not always clear in automation or troubleshooting sections.
Recommendations
  • Clearly indicate Linux/macOS compatibility for all features and tools, especially in automation sections.
  • Provide Linux/macOS-specific examples (e.g., Bash scripts, CLI-only workflows) alongside PowerShell examples.
  • In troubleshooting and automation sections, ensure that CLI examples are shown before PowerShell, or at least equally.
  • Explicitly state when a feature is Windows-only, and offer alternative guidance for Linux users where possible.
  • Expand documentation for Hybrid Connections to clarify alternatives for Linux-hosted function apps.
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-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides PowerShell-based setup instructions for the local SQL Server Docker instance, with no equivalent Bash or Linux shell examples. Windows-centric tools and patterns (PowerShell scripting, references to SQL Server Express on Windows) are mentioned before Docker-based approaches, and Linux/macOS users are not given explicit guidance or examples for their platforms. The lack of parity may create friction for non-Windows users, especially in the database setup phase.
Recommendations
  • Add Bash shell script examples for setting up SQL Server Docker containers, alongside the PowerShell examples.
  • Explicitly mention that the PowerShell commands can be run on Linux/macOS with PowerShell Core, but also provide native Bash alternatives.
  • Clarify that SQL Server Express is Windows-only and recommend Docker as the preferred cross-platform local development option.
  • Reorder instructions to present Docker-based setup as the primary, cross-platform method, rather than referencing Windows tools first.
  • Include troubleshooting tips for Linux/macOS users, such as file permissions or Docker networking differences.
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-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides only Azure PowerShell scripting for identifying function apps to migrate, with no mention of Bash, Azure CLI, or cross-platform alternatives. PowerShell is presented as the default tool for subscription-level operations, which may create friction for Linux/macOS users who typically use Azure CLI or Bash. However, the rest of the guide is largely platform-neutral, focusing on .NET code and project files.
Recommendations
  • Add Azure CLI or Bash script examples alongside the Azure PowerShell script for identifying function apps to migrate.
  • Explicitly mention that Azure CLI can be used as an alternative to PowerShell for cross-platform users.
  • Consider presenting cross-platform tools (Azure CLI) before or alongside PowerShell to avoid Windows-first bias.
  • Where possible, clarify that Visual Studio Code and Azure Functions Core Tools are cross-platform and provide links to Linux/macOS installation guides.
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-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides only Azure PowerShell scripts for identifying function apps to migrate, with no mention of Azure CLI or Bash alternatives. PowerShell is primarily a Windows-centric tool, though it is available cross-platform. Additionally, PowerShell is presented first and exclusively, which may create friction for Linux/macOS users who typically use Azure CLI or Bash. However, the rest of the guide is generally platform-agnostic, focusing on .NET and Azure Functions concepts.
Recommendations
  • Add equivalent Azure CLI (az) commands and Bash script examples for identifying function apps to migrate, alongside the PowerShell example.
  • Explicitly mention that PowerShell is available cross-platform, but provide links or instructions for installing it on Linux/macOS.
  • Where scripting is required, offer both PowerShell and CLI/Bash options, or clarify which tools are supported on which platforms.
  • Consider presenting Azure CLI examples first or in parallel with PowerShell to avoid Windows-first bias.
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-02-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell-based setup instructions for the local SQL Server Docker instance, with no equivalent Bash or Linux/macOS shell examples. The PowerShell commands are presented as the primary method, and troubleshooting assumes familiarity with Windows/Docker Desktop. While Docker and SQL Server are cross-platform, Linux/macOS users may face friction due to the lack of explicit Bash instructions and some Windows-centric terminology.
Recommendations
  • Add Bash/zsh shell examples for setting up the SQL Server Docker container, including environment variable usage and database creation.
  • Explicitly note that all Docker commands can be run on Linux/macOS, and provide any OS-specific caveats.
  • Include troubleshooting steps relevant to Linux/macOS users (e.g., using 'docker ps', 'docker exec', and file browsing without Docker Desktop).
  • Where PowerShell is used, provide equivalent Bash syntax or clarify that PowerShell is available cross-platform but Bash is more common on Linux/macOS.
  • Ensure screenshots and instructions reference cross-platform tools (e.g., VS Code, SQLCMD) and avoid Windows-only terminology where possible.
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-02-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows migration paths, but the Windows (platform-windows) sections are often presented first and in more detail, especially for manual migration steps. Windows/PowerShell/Azure CLI examples are more prominent and sometimes appear before Linux equivalents. Some sections (e.g., collecting app settings, configuring app settings, and other configurations) are more detailed for Windows, and the Windows migration path is more step-by-step, while the Linux path relies heavily on a single CLI command. There is also a heavier emphasis on Windows tools and patterns, such as Visual Studio and PowerShell, in some areas.
Recommendations
  • Ensure Linux and Windows instructions are presented with equal prominence and detail, especially in manual migration steps.
  • Where possible, provide Linux-native examples (e.g., bash scripts, Linux-specific CLI usage) alongside or before Windows/PowerShell equivalents.
  • Avoid defaulting to Windows-first ordering in sections where both platforms are supported.
  • Expand Linux migration guidance to include more granular/manual steps, not just the automated CLI command.
  • Highlight cross-platform tools (e.g., Azure CLI, VS Code) before platform-specific ones (e.g., PowerShell, Visual Studio).
GitHub Create Pull Request
← Previous Page 22 of 41 Next →