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 201-225 of 1023 flagged pages
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/configure-monitoring.md .../main/articles/azure-functions/configure-monitoring.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is explicitly mentioned and provided as an example for configuration changes, while Linux equivalents (such as Bash or shell scripts) are not shown. Windows-centric tools and patterns (PowerShell, Visual Studio) are referenced, often before or instead of Linux alternatives. There is a lack of explicit Linux command-line examples, and some notes about limitations on Linux are present but not accompanied by Linux-specific guidance or workarounds.
Recommendations
  • Provide Linux/Bash equivalents for all PowerShell examples, especially for app settings management.
  • Include explicit instructions and examples for Linux users, such as using Bash, sh, or other common Linux shells.
  • Reference cross-platform tools (e.g., Azure CLI) before platform-specific ones (PowerShell, Visual Studio), and clarify their parity.
  • Where limitations for Linux are mentioned (e.g., app settings with periods), offer Linux-specific alternatives or workarounds.
  • Add notes or sections for Linux users regarding local development, configuration, and troubleshooting.
  • Ensure screenshots and UI instructions are not Windows-specific, or provide Linux/portal alternatives.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/disable-function.md ...blob/main/articles/azure-functions/disable-function.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation presents Azure CLI and Azure PowerShell as the primary command-line methods for disabling functions, with PowerShell examples given equal prominence to CLI. PowerShell is a Windows-centric tool, and no Linux shell (e.g., Bash) or cross-platform scripting examples are provided. The documentation does not mention Linux-specific tools or patterns, and the limitations for Linux (e.g., hyphenated function names) are only noted as a caveat rather than providing alternative guidance. The ordering of examples (Portal, CLI, PowerShell) may implicitly prioritize Windows workflows, and the absence of Linux shell examples or explicit Linux parity guidance further reinforces a Windows bias.
Recommendations
  • Add explicit Bash or shell script examples for Linux users, especially for Azure CLI usage.
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS environments.
  • Mention Linux-native tools or workflows where relevant, such as environment variable management or configuration file editing.
  • Reorder examples or add a note that the order does not imply platform preference.
  • Provide troubleshooting or workaround guidance for Linux-specific limitations (e.g., function naming constraints).
  • Consider adding a section or callout for Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-best-practice-reference.md ...s/durable/durable-functions-best-practice-reference.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. PowerShell is mentioned as a primary example language for tuning performance and concurrency settings, and Windows-centric tools such as Visual Studio and Roslyn Analyzer are referenced for code analysis. Visual Studio Code is mentioned, which is cross-platform, but the overall diagnostic tooling and examples tend to prioritize Windows/PowerShell environments and tools before Linux alternatives. There are no explicit Linux-specific examples or mentions of Linux-native tools for diagnostics or development.
Recommendations
  • Include Linux-specific examples and guidance, such as using Bash or other Linux shells for scripting and diagnostics.
  • Mention and provide instructions for using Linux-native editors (e.g., Vim, Emacs) and IDEs (e.g., JetBrains Rider) where appropriate.
  • Highlight cross-platform diagnostic tools and clarify their availability and usage on Linux systems.
  • Add parity for performance tuning examples by including Bash, Python, or other Linux-friendly languages alongside PowerShell.
  • Explicitly state that Visual Studio Code and other tools are available on Linux, and provide installation or usage notes for Linux users.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-configure-managed-identity.md ...urable/durable-functions-configure-managed-identity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page shows Windows bias by referencing Windows-centric tools and workflows (Visual Studio, Azure portal, screenshots of Windows UI), listing Windows/PowerShell development environments first, and omitting explicit Linux-specific instructions or examples. There are no CLI-only or Linux-native configuration steps, and the use of Visual Studio and Azure portal is assumed throughout.
Recommendations
  • Add explicit Linux development instructions, such as using VS Code on Linux or configuring with the Azure CLI.
  • Provide examples for configuring managed identity using cross-platform tools (e.g., Azure CLI, Terraform) and include shell commands.
  • Include screenshots or descriptions for Linux environments (e.g., Ubuntu terminal, VS Code on Linux) where applicable.
  • List cross-platform or Linux-first options before or alongside Windows/PowerShell examples.
  • Clarify that the steps are applicable to both Windows and Linux, and note any OS-specific differences.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/dotnet-isolated-process-guide.md ...icles/azure-functions/dotnet-isolated-process-guide.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools (Visual Studio, PowerShell) are frequently mentioned first or exclusively, and Windows configuration patterns (e.g., netFrameworkVersion, ReadyToRun for win-x64) are described in more detail than Linux equivalents. Some CLI examples and deployment instructions prioritize Windows settings or provide explicit PowerShell/Windows commands, while Linux alternatives are less emphasized or appear later. There are also sections where Linux-specific guidance is missing or less detailed, such as ReadyToRun publishing and debugging instructions.
Recommendations
  • Ensure Linux examples and instructions are provided alongside Windows ones, especially for deployment, configuration, and performance optimization sections.
  • Present Linux and Windows options in parallel (e.g., in side-by-side tabs or tables), rather than listing Windows first.
  • Include more detailed Linux-specific guidance for areas like debugging, ReadyToRun publishing, and configuration (e.g., using bash, Linux file paths, and LinuxFxVersion).
  • Avoid referencing Windows tools (Visual Studio, PowerShell) exclusively; mention cross-platform alternatives (VS Code, Azure CLI, bash) with equal prominence.
  • Where PowerShell or Windows CLI commands are shown, provide equivalent bash/Azure CLI commands for Linux users.
  • Review all examples and ensure Linux deployment and configuration scenarios are covered with the same depth as Windows.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-instance-management.md ...tions/durable/durable-functions-instance-management.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides examples for all supported languages, including PowerShell, which is primarily a Windows-centric shell. PowerShell examples are given equal prominence as other languages, and Azure Functions Core Tools (which are cross-platform but have a Windows legacy and are often associated with Windows development environments) are referenced throughout as the main CLI tooling. There is no explicit mention of Linux-specific shells (e.g., Bash) or Linux-native patterns, nor are there examples using Linux-specific tools or idioms. The documentation does not mention platform-specific differences, nor does it provide guidance for Linux users regarding shell usage, environment setup, or alternative tools.
Recommendations
  • Add explicit Bash or shell script examples for CLI commands, demonstrating usage in Linux environments (e.g., with environment variables, piping, jq for JSON parsing).
  • Clarify that Azure Functions Core Tools are cross-platform and provide installation/setup instructions for Linux and macOS users.
  • Where PowerShell is used, note its availability on Linux and macOS, and provide equivalent Bash examples for common operations.
  • Highlight any platform-specific caveats or differences in behavior, especially for file paths, environment variables, and shell syntax.
  • Consider referencing Linux-native tools (e.g., curl, jq) in examples involving HTTP APIs or JSON manipulation.
  • Add troubleshooting or FAQ sections for common Linux issues (e.g., permissions, dependency installation, path differences).
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-event-publishing.md ...unctions/durable/durable-functions-event-publishing.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page shows evidence of Windows bias primarily through its references to the Azurite storage emulator and the Storage Emulator, both of which are historically Windows-centric tools. The instructions for local development and debugging mention the Storage Emulator without clarifying Linux alternatives or providing parity for Linux users. Additionally, while Azure CLI is used for most examples (which is cross-platform), PowerShell is mentioned as an alternative for creating Event Grid topics before the Azure portal, which may suggest a Windows-first mindset. There are no explicit Linux-specific instructions or troubleshooting tips, and the documentation does not mention Linux-compatible storage emulators or provide guidance for Linux users where Windows tools are referenced.
Recommendations
  • Explicitly mention and provide instructions for using Azurite on Linux and macOS, including installation and startup commands.
  • Remove or clarify references to the legacy Storage Emulator, noting that it is Windows-only and recommending Azurite for cross-platform scenarios.
  • When listing alternatives for resource creation (e.g., Event Grid topic), mention Azure CLI and Azure portal before PowerShell to avoid Windows-first ordering.
  • Add troubleshooting notes or links for common Linux issues (e.g., file permissions, port conflicts) when running local emulators.
  • Ensure all sample commands and configuration steps are verified to work on Linux, and note any platform-specific differences.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-sub-orchestrations.md ...ctions/durable/durable-functions-sub-orchestrations.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page includes a prominent PowerShell-specific note and full PowerShell code samples alongside other languages. PowerShell is a Windows-centric tool, and its usage is highlighted both in the introductory note and in the examples. The note about PowerShell SDK support appears before any mention of Linux or cross-platform alternatives. There is no mention of Bash, Linux shell, or Linux-specific orchestration patterns, nor is there any guidance for Linux users regarding equivalent tooling or SDKs.
Recommendations
  • Add explicit notes or guidance for Linux users, including supported SDKs and any differences in orchestration patterns.
  • Provide Bash or other Linux shell examples if relevant, or clarify that PowerShell examples are cross-platform (if true) and how to use them on Linux.
  • Balance the introductory notes by mentioning cross-platform support and alternatives before or alongside PowerShell-specific information.
  • Clarify whether PowerShell examples are intended for Windows only or if they are supported on Linux/macOS, and provide installation or usage instructions for those platforms.
  • Consider including troubleshooting or migration guidance for Linux users, especially where SDK or tool support differs.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-versioning.md ...zure-functions/durable/durable-functions-versioning.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing code examples only for C#, PowerShell, and Java, with PowerShell being a Windows-centric scripting language. There are no examples for Linux-native scripting languages (such as Bash or Python), nor are Linux-specific tools or deployment patterns mentioned. The use of PowerShell as the only shell scripting example implicitly prioritizes Windows environments. Additionally, deployment guidance references Azure App Service deployment slots, which are more commonly used in Windows-centric workflows, without mentioning Linux alternatives or considerations.
Recommendations
  • Add equivalent examples using Bash or Python to demonstrate orchestration logic for Linux users.
  • Include guidance for Linux-based deployment workflows, such as using Azure Functions on Linux, Docker containers, or CI/CD pipelines that target Linux environments.
  • Mention Linux-native tools and patterns where relevant, such as using Azure CLI (cross-platform) instead of PowerShell for management tasks.
  • Clarify that Durable Functions and Azure Functions are cross-platform, and provide explicit instructions for both Windows and Linux users where deployment or operational steps may differ.
  • Ensure that all code samples and operational guidance are presented in a way that is accessible and relevant to both Windows and Linux users, possibly by using tabs or sections for each platform.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-task-scheduler/quickstart-portable-durable-task-sdks.md ...ask-scheduler/quickstart-portable-durable-task-sdks.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exhibits some Windows bias, particularly in the Python quickstart where Windows-specific commands (such as venv activation) are shown first and Linux commands are secondary. In the PowerShell pivot, only PowerShell is referenced, with no mention of Linux shells or equivalents. There are no explicit Linux shell or tool examples for C# or Java, and the PowerShell pivot lacks parity for Linux users. However, most core commands (such as Docker and directory navigation) are cross-platform, and the Python section does provide both Windows and Linux activation commands.
Recommendations
  • For every PowerShell or Windows-specific example, provide a Linux (bash/sh) equivalent, especially in the PowerShell pivot.
  • In the Python section, consider presenting Linux and Windows commands side-by-side or in a tabbed format, rather than listing Windows first.
  • For C# and Java pivots, clarify that the commands are cross-platform and, where relevant (e.g., .NET CLI, Gradle), mention any OS-specific prerequisites or differences.
  • Add explicit notes or tabs for Linux/macOS users in all language pivots, not just Python.
  • If a PowerShell pivot is included, consider adding a bash/zsh shell pivot or at least a section for Linux/macOS users.
  • Review screenshots and file paths to ensure they are not Windows-centric (e.g., avoid backslashes in paths unless necessary).
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/quickstart-mssql.md ...n/articles/azure-functions/durable/quickstart-mssql.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows environments. PowerShell is used exclusively for local database setup, and SQL Server Express is suggested specifically for 'your local Windows computer.' There are no bash or Linux-native command examples for setting up SQL Server in Docker, and troubleshooting steps reference Docker Desktop, which is primarily a Windows/macOS tool. The documentation does not provide parity for Linux users in terms of command-line examples or tool recommendations.
Recommendations
  • Provide bash shell equivalents for all PowerShell commands, especially for Docker-based SQL Server setup and validation.
  • Explicitly mention and demonstrate how to set up SQL Server Express or Docker containers on Linux distributions.
  • Include troubleshooting steps for Linux users, such as using docker CLI and locating mssql-tools folders via command line.
  • Reference cross-platform tools (e.g., Azure Data Studio) before Windows-only tools (e.g., SQL Server Management Studio).
  • Avoid language such as 'your local Windows computer' and use 'your local machine' or specify both Windows and Linux options.
  • Add notes or sections for Linux/macOS users wherever setup steps may differ.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-webjobs-sdk.md ...ure-functions/durable/durable-functions-webjobs-sdk.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a clear Windows bias. It prioritizes Windows development environments (Visual Studio, Windows Classic Desktop), provides only Windows-specific instructions and examples, and omits Linux or cross-platform alternatives. All package installation commands use PowerShell syntax, and there is no mention of Linux tools, .NET CLI, or VS Code workflows. The use of the Azurite storage emulator is referenced, but only in the context of Visual Studio and Windows. There are no instructions for running or deploying WebJobs from Linux or macOS environments.
Recommendations
  • Provide equivalent instructions for Linux/macOS environments, such as using VS Code and the .NET CLI.
  • Include Bash or shell commands for installing NuGet packages (e.g., 'dotnet add package ...').
  • Describe how to create and run console apps and WebJobs projects using .NET Core on Linux/macOS.
  • Mention cross-platform storage emulator options and how to configure them outside of Windows.
  • Clarify which steps are Windows-specific and offer alternatives for other operating systems.
  • Ensure deployment instructions cover both Windows and Linux-based workflows.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/quickstart-java.md ...in/articles/azure-functions/durable/quickstart-java.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. In the manual setup section, the default runtime OS is set to 'windows' in the Maven plugin configuration, with no mention of Linux or cross-platform alternatives. In the Maven command section, examples are provided for Bash, PowerShell, and Cmd, but PowerShell and Cmd (Windows shells) are listed after Bash, which is positive, but their inclusion may reinforce Windows-centric workflows. Visual Studio Code instructions are cross-platform, but overall, there is a lack of explicit Linux guidance or parity in configuration examples, especially regarding deployment runtime OS and local development nuances.
Recommendations
  • Explicitly mention Linux as a supported runtime OS in the Maven plugin configuration, and provide an example with <os>linux</os>.
  • Add notes or sections describing any Linux-specific steps, caveats, or troubleshooting tips for Azure Functions Core Tools and Durable Functions.
  • Ensure that all command-line examples (Bash, PowerShell, Cmd) are presented with equal prominence, and clarify which are for Windows and which are for Linux/macOS.
  • Include screenshots or terminal output examples from Linux environments alongside Windows examples.
  • Review all references to tools and workflows to ensure Linux users are not excluded or left to infer their own steps.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/quickstart-netherite.md ...ticles/azure-functions/durable/quickstart-netherite.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows-specific tools and patterns (such as the Azure Storage Emulator) are mentioned, and guidance is given for Windows users before Linux equivalents (Azurite). There are sections that explicitly address Windows-only settings (64-bit architecture validation), while Linux users are told to skip those steps. There are no explicit Linux command-line examples or screenshots, and Linux tooling is not discussed in detail. The page assumes familiarity with Windows-centric workflows and does not provide parity for Linux users in terms of examples or troubleshooting.
Recommendations
  • Include explicit Linux command-line examples and workflows (e.g., using Bash, Linux file paths, Linux deployment commands).
  • Add screenshots and instructions for Linux environments, such as using Azurite on Linux, configuring settings via CLI, and validating architecture.
  • Mention Linux tools and patterns alongside Windows ones, not only as notes or exceptions.
  • Provide troubleshooting steps and tips for common Linux issues (e.g., permissions, environment variables, storage emulator setup).
  • Ensure that all steps are clearly marked for both Windows and Linux users, and avoid Windows-first phrasing.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/scenario-build-serverless-workflow.md ...unctions/durable/scenario-build-serverless-workflow.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides command examples for multiple platforms, but Windows-specific tools and patterns (Cmd, PowerShell) are consistently presented alongside or before Linux equivalents. In several places, Windows command-line options are given more detail or are listed before Linux/macOS alternatives. PowerShell and Cmd examples are included for tasks such as activating Python virtual environments and querying Azure Functions endpoints, while Linux/macOS instructions are sometimes less prominent. There is a slight tendency to present Windows tooling and workflows as the default or primary option.
Recommendations
  • Ensure Linux/macOS instructions are presented with equal prominence and detail as Windows examples.
  • Where multiple platforms are supported, consider listing Linux/macOS examples first or side-by-side with Windows examples, rather than after.
  • Provide explicit bash/zsh examples for all major commands, including those for Python, Node.js, and Azure CLI tasks.
  • Avoid grouping Windows-specific tools (PowerShell, Cmd) before Linux/macOS alternatives in tabbed or pivoted sections.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, path differences) to match the depth of Windows guidance.
  • Review all command snippets to ensure parity in explanation and context for both Windows and Linux/macOS users.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/function-keys-how-to.md .../main/articles/azure-functions/function-keys-how-to.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 scripts are given equal prominence to CLI commands, and there are no explicit Linux shell (bash) or cross-platform scripting examples. Azure CLI commands are described as running in Azure Cloud Shell (Bash), but users are told to 'modify it to run in a Windows terminal,' implying a Windows-first perspective. There are no bash or Linux-native examples for REST API calls, and PowerShell is featured as a primary method, which is Windows-centric.
Recommendations
  • Add explicit bash/Linux shell examples for REST API calls, using curl or httpie, alongside PowerShell examples.
  • Clarify that Azure CLI commands work natively on Linux, macOS, and Windows, and provide sample usage in local bash terminals.
  • Avoid language that implies Windows is the default (e.g., 'modify it to run in a Windows terminal'); instead, provide instructions for both Windows and Linux/macOS environments.
  • Where PowerShell is used, offer equivalent bash or Python examples for cross-platform parity.
  • Highlight that Azure Functions Core Tools and Azure CLI are cross-platform, and demonstrate usage in Linux/macOS environments.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-app-settings.md ...ain/articles/azure-functions/functions-app-settings.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 settings and patterns (such as environment variable delimiters, file paths, and PowerShell configuration) are often mentioned first or exclusively. Examples like %HOME%\typescript and WEBSITE_NODE_DEFAULT_VERSION are marked as 'Windows only' without Linux equivalents. PowerShell-specific settings are detailed, while Linux shell or Bash alternatives are not provided. Some settings (e.g., WEBSITE_TIME_ZONE) do include both Windows and Linux examples, but this is inconsistent. There is limited coverage of Linux-specific tools, patterns, or examples, and references to Azure CLI or Bash scripting are less prominent than PowerShell.
Recommendations
  • Ensure every Windows-specific example has a Linux equivalent (e.g., provide Linux file path examples alongside Windows ones).
  • Where settings are OS-specific, clearly label both Windows and Linux usage, and provide parity in documentation.
  • Include Linux/Bash/CLI commands and patterns wherever PowerShell or Windows tools are referenced.
  • Expand examples for Linux-specific scenarios, such as container deployments, file system paths, and environment variable conventions.
  • Review and update sections where Windows is mentioned first or exclusively, to present Linux and Windows options with equal prominence.
  • Add cross-platform scripting examples (e.g., Azure CLI, Bash, PowerShell) for managing app settings.
  • Highlight Linux-specific features and limitations as thoroughly as Windows ones.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-add-openai-text-completion.md ...zure-functions/functions-add-openai-text-completion.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Visual Studio Code and Azurite usage patterns that are most familiar to Windows users, and by omitting explicit Linux/macOS alternatives for key steps such as starting Azurite or running the function app. The instructions for starting Azurite and debugging the function app use Visual Studio Code commands and shortcuts (e.g., F5, Ctrl+C) without mentioning equivalent CLI commands or shortcuts for Linux/macOS environments. There is also an assumption of familiarity with Windows-style tooling and file paths, and no mention of shell or terminal alternatives for non-Windows users.
Recommendations
  • Add explicit instructions for Linux/macOS users, including terminal commands to start Azurite (e.g., `azurite` or `npx azurite`) and to run/debug the function app (e.g., `func start`).
  • Mention keyboard shortcut differences for Visual Studio Code on macOS (e.g., Cmd+F5 instead of F5, Cmd+C instead of Ctrl+C).
  • Where file paths or configuration files are referenced, clarify any differences in path syntax or environment variables for Linux/macOS.
  • Include a note or section summarizing cross-platform compatibility and any required setup steps for Linux/macOS users (such as installing Azurite globally via npm, or using bash/zsh shells).
  • Ensure that all tooling (Azurite, Azure Functions Core Tools) is described in a way that is platform-neutral, and provide installation instructions for each major OS.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-register.md ...rticles/azure-functions/functions-bindings-register.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by including PowerShell as a primary programming language pivot, referencing Visual Studio and Visual Studio Code (Windows-centric tools) for C# development, and omitting explicit Linux/macOS examples or guidance. The instructions for manual extension installation reference Azure Functions Core Tools but do not clarify cross-platform usage or provide Linux/macOS-specific commands or considerations. There is no mention of Linux package managers, shell commands, or development environments outside of Windows.
Recommendations
  • Add explicit examples and instructions for Linux/macOS users, including shell commands (e.g., bash/zsh) for installing and managing extensions.
  • Reference cross-platform editors such as VS Code for both Windows and Linux, and provide parity in guidance for Visual Studio alternatives on Linux.
  • Clarify that Azure Functions Core Tools is cross-platform and provide installation instructions for Linux/macOS (e.g., via npm, apt, brew).
  • Include troubleshooting steps or notes for common Linux/macOS issues (e.g., file permissions, path differences).
  • Ensure that PowerShell is not presented as the default or only scripting environment; include bash/zsh examples where relevant.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-service-bus.md ...cles/azure-functions/functions-bindings-service-bus.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing almost exclusively on .NET/C# examples and NuGet package installation, which are Windows-centric tools and workflows. There is no mention of Linux-specific tools, package managers, or command-line instructions (e.g., apt, yum, pip for Python, npm for JavaScript). The installation and configuration instructions are tailored to Windows development patterns, with no explicit parity for Linux environments. Additionally, PowerShell is listed as a supported language but is not given any examples or instructions, and there are no Linux shell (bash) or cross-platform CLI examples provided.
Recommendations
  • Add explicit instructions and examples for Linux environments, such as using dotnet CLI on Linux, and referencing Linux package managers where appropriate.
  • Include bash shell commands for installing dependencies and configuring projects, alongside NuGet/Visual Studio instructions.
  • Provide parity for PowerShell and other supported languages, including code samples and setup instructions for Linux/macOS.
  • Mention cross-platform development tools (e.g., VS Code, Azure CLI) and clarify that the instructions apply to both Windows and Linux unless otherwise noted.
  • Where possible, avoid assuming Visual Studio or NuGet GUI usage; provide CLI alternatives that work on all platforms.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-web-pubsub-input.md ...azure-functions/functions-bindings-web-pubsub-input.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example Powershell Heavy Windows First
Summary
The documentation page does not show explicit Windows bias in terms of tooling or examples, but there are notable gaps in Linux parity. Powershell samples are marked as 'pending', and there are no Linux-specific shell or CLI examples. The documentation does not mention Windows-specific tools, but the absence of Linux shell (bash/zsh) or CLI examples, and the lack of parity in Powershell and Python samples, suggest a bias toward Windows-centric development environments. Additionally, C# (commonly used on Windows) examples are presented first and most completely.
Recommendations
  • Add complete Powershell samples to achieve parity with other languages.
  • Provide Linux shell (bash/zsh) or Azure CLI examples for common tasks, such as configuring bindings or retrieving connection info.
  • Ensure Python samples are as complete as C# and JavaScript samples.
  • Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux environments.
  • If any configuration or deployment steps differ between Windows and Linux, document both workflows.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-compare-logic-apps-ms-flow-webjobs.md ...ctions/functions-compare-logic-apps-ms-flow-webjobs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and patterns (e.g., PowerShell, Visual Studio, .NET console apps) in management and development sections. Examples and tooling references (such as PowerShell and Visual Studio) are listed before or instead of Linux-friendly alternatives (like Azure CLI or VS Code). There is a lack of explicit Linux or cross-platform examples, and the language and tool choices (e.g., .cmd, .bat, PowerShell) reinforce a Windows-first perspective.
Recommendations
  • Add explicit Linux and cross-platform examples for management and deployment tasks (e.g., bash, Azure CLI, VS Code workflows).
  • Ensure Azure CLI is mentioned before or alongside PowerShell in management tool lists.
  • Include references to Linux-compatible scripting languages and patterns (e.g., bash, Python) in examples and tables.
  • Highlight cross-platform development environments (e.g., VS Code, GitHub Actions) equally with Windows-centric tools.
  • Clarify that App Service WebJobs and related SDKs can be used from Linux environments and provide sample workflows for Linux users.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-first-function-resource-manager.md ...ns/functions-create-first-function-resource-manager.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides deployment instructions using both Azure CLI and Azure PowerShell, with full code samples for each. Azure PowerShell is a Windows-centric tool, and its inclusion as a primary tab (alongside Azure CLI) can be seen as Windows bias, especially since PowerShell is less commonly used on Linux compared to Bash or native shell scripting. There are no Bash or Linux shell script examples, and no mention of Linux-specific tools or patterns. The documentation does not clarify cross-platform compatibility for PowerShell, nor does it offer parity for Linux users who may prefer Bash or other native shells.
Recommendations
  • Add Bash shell script examples for deploying ARM templates using Azure CLI, specifically formatted for Linux/macOS environments.
  • Clarify that Azure CLI commands work natively on Linux/macOS and Windows, and highlight cross-platform usage.
  • Note that Azure PowerShell is available on Linux/macOS, but is most commonly used on Windows; suggest Azure CLI or Bash for Linux users.
  • Consider reordering tabs to present Azure CLI (cross-platform) first, and PowerShell second.
  • Explicitly mention platform compatibility for each tool and provide guidance for Linux/macOS users.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-core-tools-reference.md ...cles/azure-functions/functions-core-tools-reference.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 evidence of Windows bias. The reference to the tool as 'func.exe' in the description, the presence of options and examples specific to PowerShell, and references to Windows-only tools like the Microsoft Azure Storage Emulator suggest a Windows-centric approach. Linux equivalents (such as Azurite for storage emulation) are not mentioned, and there are no explicit Linux or bash examples. Some features (like log streaming) are noted as unsupported for Linux in certain plans, but alternatives for Linux users are not detailed. The documentation generally assumes Windows as the default environment and omits Linux-specific guidance.
Recommendations
  • Replace references to 'func.exe' with platform-neutral terms like 'func' or 'Azure Functions Core Tools executable'.
  • Provide Linux/bash command examples alongside or before PowerShell/Windows examples.
  • Mention Linux equivalents for Windows-only tools (e.g., reference Azurite instead of or alongside the Microsoft Azure Storage Emulator).
  • Clarify cross-platform support for each feature, and provide Linux/macOS alternatives or workarounds where features are Windows-only.
  • Ensure documentation does not assume Windows as the default environment; explicitly state platform requirements and differences.
  • Add notes or sections for Linux/macOS users, especially where setup or usage differs from Windows.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-custom-handlers.md .../articles/azure-functions/functions-custom-handlers.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 examples and configuration consistently use Windows-style naming (e.g., handler.exe) and paths, with Linux/macOS equivalents only briefly mentioned parenthetically and never shown in detail. Deployment instructions and troubleshooting focus on Windows conventions and tools, with no explicit Linux or cross-platform guidance. There are no Linux-specific examples, scripts, or screenshots, and the documentation does not clarify platform differences in file naming, permissions, or execution. Windows tools and patterns are presented first and exclusively in most cases.
Recommendations
  • Provide explicit Linux/macOS examples alongside Windows ones, including sample configurations using 'handler' (no .exe) and relevant file permissions.
  • Show cross-platform deployment instructions, including any differences in using Azure Functions Core Tools on Linux/macOS.
  • Clarify platform-specific requirements for custom handler executables (e.g., file extensions, execution permissions, shebang lines for scripts).
  • Include troubleshooting steps and log access instructions for Linux/macOS environments.
  • Use neutral, cross-platform language and examples wherever possible, or present Windows and Linux/macOS options side-by-side.
GitHub Create Pull Request
← Previous Page 9 of 41 Next →