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 276-300 of 1023 flagged pages
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-bindings.md .../azure-functions/durable/durable-functions-bindings.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page provides examples for multiple languages, including C#, Java, JavaScript, Python, and PowerShell. However, there is a noticeable Windows bias: PowerShell is included as a first-class language throughout, with detailed examples and configuration instructions. The use of PowerShell and references to function.json (a pattern most common in Windows/PowerShell development) are prominent. There is no mention of Linux-specific tools, shell scripts, or cross-platform alternatives to PowerShell. The documentation also references Windows-centric patterns (e.g., function.json editing, PowerShell cmdlets) before or instead of Linux equivalents.
Recommendations
  • Add Bash or shell script examples alongside PowerShell for Linux users.
  • Clarify that function.json editing and PowerShell usage are not required or typical on Linux, and provide guidance for Linux-native workflows.
  • Include notes or sections on running Durable Functions on Linux, including any differences in setup, tooling, or recommended practices.
  • Where PowerShell is used, offer equivalent code snippets in Bash or Python for Linux parity.
  • Explicitly mention cross-platform compatibility and highlight any OS-specific considerations for Durable Functions development.
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-08 00:53
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, Azure PowerShell) and configuration patterns are frequently mentioned, often before their Linux equivalents. Examples for checking/changing app bitness and framework version use Windows-centric Azure CLI commands and PowerShell, with Linux alternatives only briefly referenced or omitted. In deployment and debugging sections, Windows is discussed first and in more detail. Some CLI commands and configuration steps lack explicit Linux instructions or examples, and PowerShell is listed as a primary resource creation method, while Bash or Linux shell scripts are not mentioned.
Recommendations
  • Ensure Linux-specific instructions and examples are provided alongside Windows ones, especially for CLI commands, configuration, and deployment.
  • Present Linux and Windows options in parallel (e.g., side-by-side tabs), rather than listing Windows first or in more detail.
  • Include Bash/shell script examples for resource creation and management, not just PowerShell.
  • When referencing tools, mention cross-platform alternatives (e.g., VS Code, Azure CLI) before or alongside Windows-only tools (e.g., Visual Studio, PowerShell).
  • Clarify any platform-specific limitations or requirements, and provide guidance for both Windows and Linux users.
  • Add explicit Linux container deployment walkthroughs and troubleshooting tips.
  • Review all code snippets and ensure they are runnable on both platforms, or provide platform-specific variants where necessary.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias. PowerShell is listed as a primary language for performance tuning, and Windows-centric tools like Visual Studio and Roslyn Analyzer are mentioned as the main options for code analysis and monitoring. Visual Studio Code is referenced, but Linux-specific tools, patterns, or examples are not provided. Diagnostic and monitoring guidance focuses on Application Insights and Azure portal, which are cross-platform but often used with Windows tooling. There are no explicit Linux examples or mentions of Linux command-line tools or workflows.
Recommendations
  • Include Linux-specific examples for performance tuning and diagnostics, such as using Bash or Linux-native monitoring tools.
  • Mention alternative code analysis tools or workflows available on Linux (e.g., running Roslyn Analyzer via command line or in JetBrains Rider).
  • Provide parity in instructions for enabling diagnostics and monitoring, referencing both Windows and Linux environments.
  • List PowerShell and Bash examples side-by-side when discussing scripting or automation.
  • Clarify that Visual Studio Code and Azure portal are cross-platform, and provide links or notes for Linux users where appropriate.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias. In the manual setup section, the default runtime OS in the Maven plugin configuration is set to 'windows', with no mention of Linux or cross-platform alternatives. In the Maven command section, PowerShell and Cmd examples are given alongside Bash, and Windows shells are listed after Bash but before Linux-specific shells (if any). Visual Studio Code is used as the primary IDE, which is cross-platform but often associated with Windows workflows. There is no explicit mention of Linux-specific configuration or parity, and Windows appears as the default or first-mentioned platform in several places.
Recommendations
  • Explicitly mention Linux as a supported runtime OS in the Maven plugin configuration, and provide an example with <os>linux</os>.
  • Add Linux-specific instructions or notes where platform differences exist (e.g., file paths, shell commands).
  • Ensure that Bash examples are clearly labeled as suitable for Linux/macOS, and consider listing Linux/macOS instructions before Windows/PowerShell/Cmd where appropriate.
  • Include troubleshooting notes for common Linux issues (e.g., permissions, environment variables).
  • Clarify that Visual Studio Code is cross-platform and provide links to Linux/macOS installation guides.
  • Where Azure Functions Core Tools are referenced, note installation steps for Linux/macOS as well as Windows.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-orchestration-versioning.md .../durable/durable-functions-orchestration-versioning.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides extensive PowerShell examples and references the PowerShell SDK, which is primarily a Windows-centric tool. PowerShell is presented as a first-class language alongside C#, JavaScript, Python, and Java, but there are no equivalent Linux shell (e.g., Bash) examples or references to Linux-native tools. The orchestration client API support for starting orchestrations with a specific version is explicitly unavailable for JavaScript, Python, and PowerShell, but the PowerShell section does not mention any Linux alternatives. The documentation does not mention or provide examples for Linux-specific deployment, configuration, or troubleshooting patterns, and the use of PowerShell as the only shell scripting example reinforces a Windows-first approach.
Recommendations
  • Add Bash or other Linux shell examples for orchestration triggers and activity invocation, especially in sections where PowerShell is used.
  • Reference Linux-native tools and scripting environments where appropriate, or clarify cross-platform compatibility for PowerShell Core.
  • Include guidance for Linux deployment scenarios, such as using Azure Functions on Linux hosts, and troubleshooting with Linux tools.
  • Explicitly mention whether PowerShell examples are compatible with PowerShell Core on Linux, or provide alternatives if not.
  • Balance the language tabs by including Linux shell scripting as an option, or clarify that PowerShell is cross-platform if that is the intent.
  • Where orchestration client API features are unavailable for certain languages, suggest Linux-friendly workarounds or note platform parity plans.
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-08 00:53
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 mild Windows bias. Windows-specific tools (such as Azure Storage Emulator) are mentioned, and instructions for local storage emulation explicitly reference Windows OS. The use of Azurite is described in the context of Windows, with no Linux-specific instructions or parity checks. The 'Ensure 64-bit architecture' section is labeled 'Windows only,' and Linux users are told to skip it, but no equivalent Linux validation steps are provided. Command-line examples use generic CLI commands, but there is a lack of explicit Linux shell or environment examples. Screenshots and portal instructions are platform-neutral, but overall, the documentation assumes a Windows-first perspective and omits Linux-specific guidance in several places.
Recommendations
  • Add explicit instructions and examples for Linux users, especially for local storage emulation with Azurite (e.g., how to install and run Azurite on Linux).
  • Provide Linux-specific validation steps for 64-bit architecture, such as using 'uname -m' or checking the platform via Azure portal for Linux apps.
  • Include CLI examples using bash/zsh syntax where appropriate, and clarify any differences in environment setup between Windows and Linux.
  • Mention any Linux-specific caveats or troubleshooting tips, especially for local development and deployment.
  • Ensure that references to Windows-only tools (like Azure Storage Emulator) are balanced with Linux alternatives and guidance.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides code examples in C#, PowerShell, and Java, but omits Linux-native scripting languages (such as Bash or Python). PowerShell, which is traditionally associated with Windows, is given equal prominence as C# and Java, despite its limited use on Linux. There are no examples or guidance for Linux shell scripting, nor are Linux-specific deployment or operational patterns discussed. The documentation also references Azure Storage and deployment slots in a way that assumes familiarity with Windows-centric tools and workflows.
Recommendations
  • Add example orchestrator code snippets in Bash and/or Python to reflect common Linux usage.
  • Include guidance for Linux-based deployment strategies, such as using Azure Functions on Linux, Docker containers, or CI/CD pipelines with Linux runners.
  • Mention Linux equivalents or alternatives to PowerShell where appropriate, and clarify cross-platform compatibility for all examples.
  • Discuss operational patterns for Durable Functions that are relevant to Linux environments, such as using Azure CLI, shell scripts, or Linux-native monitoring tools.
  • Ensure that references to storage providers and deployment slots include notes on Linux support and any platform-specific considerations.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page includes PowerShell-specific notes and examples, referencing the PowerShell SDK and migration guides. PowerShell is a Windows-centric tool, and its mention is prominent in the introductory note and example tabs. There is no equivalent mention of Linux shell scripting or Linux-specific SDKs. The documentation does not provide parity for Linux command-line tools or scripting languages, and PowerShell is presented before other language examples in some sections.
Recommendations
  • Add notes or examples for Linux shell scripting (e.g., Bash) if relevant for orchestration scenarios.
  • Clarify cross-platform support for SDKs, including any Linux-specific considerations or alternatives.
  • Balance introductory notes by mentioning both PowerShell and Linux/Unix environments where applicable.
  • Ensure that PowerShell-specific information is presented alongside or after cross-platform alternatives, not before.
  • Provide guidance for Linux users on how to achieve similar orchestration tasks using native tools or supported SDKs.
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-08 00:53
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 bias toward Windows environments, primarily through the use of PowerShell for Docker and SQL Server setup, references to Windows-specific tools (e.g., SQL Server Express on Windows), and a lack of explicit Linux/macOS command examples. While Docker is cross-platform, all setup instructions and troubleshooting are presented in PowerShell, and Windows is mentioned first or exclusively in several places. There are no bash or Linux-native command examples for common developer workflows.
Recommendations
  • Provide equivalent bash shell commands for Docker and SQL Server setup, especially for Linux/macOS users.
  • Include explicit instructions for installing and running SQL Server on Linux (e.g., using native packages or Docker with bash).
  • Mention Linux and macOS as first-class development environments alongside Windows, not just as an afterthought.
  • Reference cross-platform tools (e.g., Azure Data Studio) before or alongside Windows-only tools (e.g., SQL Server Management Studio).
  • Add troubleshooting steps relevant to Linux/macOS (e.g., file permissions, Docker networking differences).
  • Ensure all code blocks and examples are available in both PowerShell and bash/zsh syntax where applicable.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation shows some Windows bias, particularly in the Python quickstart where Windows virtual environment activation commands are presented before Linux equivalents. Powershell is included as a pivot, but there is no equivalent Bash or Linux shell pivot. In the Python section, Windows commands are listed first, and in some places, Linux instructions are only present as secondary tabs. There are no explicit Linux-specific troubleshooting tips or parity for command-line patterns (e.g., no mention of Bash scripts or Linux package managers).
Recommendations
  • For all language pivots, present both Windows and Linux/macOS commands side-by-side or in a neutral order (e.g., use tabbed code blocks with 'Windows' and 'Linux/macOS' labels, and alternate which OS is shown first).
  • Add a Bash or Linux shell pivot alongside Powershell, or provide Bash equivalents for all Powershell commands/examples.
  • Where troubleshooting tips are provided (e.g., permission errors for ./gradlew), include both Windows and Linux/macOS scenarios.
  • Explicitly mention Linux/macOS compatibility in the prerequisites and setup steps (e.g., clarify that Docker Desktop is available for both Windows and Linux, and provide links to Linux installation instructions).
  • Wherever possible, avoid presenting Windows-specific commands or paths before Linux/macOS ones, or alternate the order to avoid implicit prioritization.
  • Consider including a section or callout for common Linux/macOS issues or environment differences (e.g., file permissions, path separators, activating virtual environments).
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-08 00:53
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 and detail as CLI commands. PowerShell is a Windows-centric tool, while Bash or shell scripting is more common on Linux/macOS. The CLI examples mention Azure Cloud Shell (Bash), but there are no explicit Bash or Linux shell script examples. Additionally, the CLI command includes a note that it must be modified to run in a Windows terminal, but there is no reciprocal guidance for running PowerShell on Linux/macOS. The documentation does not mention Linux-specific tools or patterns, and PowerShell examples may be less accessible to Linux users.
Recommendations
  • Add explicit Bash shell script examples for key management tasks, especially for REST API calls, to complement PowerShell scripts.
  • Clarify that Azure PowerShell can be used cross-platform, but provide instructions or examples for installing and running it on Linux/macOS.
  • Ensure that CLI and Bash examples are presented before or alongside PowerShell examples to avoid Windows-first perception.
  • Include notes or links for Linux/macOS users on how to perform equivalent operations, especially where file handling or environment setup differs.
  • Where possible, use platform-agnostic tools (e.g., Azure CLI, REST API via curl) as primary examples, with PowerShell as an additional option.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a Windows bias primarily through its use of Windows-centric tools and patterns, such as Visual Studio Code and Azurite, without providing explicit Linux alternatives or instructions. The instructions for starting Azurite and running the function app assume Visual Studio Code and its command palette, which is more common on Windows. There are no explicit examples or troubleshooting steps for Linux users, such as using CLI commands outside VS Code or handling permissions and emulator setup on Linux. The documentation also references Core Tools and the Azurite emulator without clarifying cross-platform installation or usage, and does not mention Linux-specific considerations for local development.
Recommendations
  • Add explicit instructions for installing and running Azurite and Azure Functions Core Tools on Linux, including common package managers (e.g., apt, yum, Homebrew).
  • Provide CLI-based alternatives for steps currently described via Visual Studio Code command palette (e.g., starting Azurite via npm or CLI).
  • Include troubleshooting notes for Linux users, such as handling file permissions, environment variables, and emulator networking.
  • Clarify that all tools (VS Code, Azurite, Core Tools) are cross-platform and provide links or steps for Linux installation.
  • Where possible, show parity in examples (e.g., bash commands for Linux alongside VS Code instructions).
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-cache-trigger-redispubsub.md ...ctions/functions-bindings-cache-trigger-redispubsub.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides code samples for multiple languages, including C#, Java, JavaScript, Python, and PowerShell. However, there is a noticeable Windows bias: PowerShell is included as a first-class example language, and the connection string examples use the '.redis.cache.windows.net' domain, which is strongly associated with Azure's Windows-centric Redis offering. There is no mention of Linux-specific tools or shell examples (e.g., Bash), nor are there references to Linux-native scripting or configuration patterns. PowerShell is presented alongside other languages, but no equivalent Bash or Linux shell scripting example is given. The documentation also refers to application settings using Windows/Azure conventions, with no mention of Linux environment variable patterns or deployment scenarios.
Recommendations
  • Add Bash or Linux shell scripting examples for parity with PowerShell, especially for automation scenarios.
  • Explicitly mention that the Redis connection string and configuration patterns work on both Windows and Linux, and provide Linux-specific guidance where relevant.
  • Include references to Linux-native tools or commands (e.g., using Bash, systemd, or environment variables in Linux) in the configuration and setup sections.
  • Clarify that Azure Functions and Redis triggers are cross-platform, and provide links or notes for Linux deployment scenarios.
  • If PowerShell is included, ensure that Bash or other Linux shell examples are presented with equal prominence.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-openai-embeddings-input.md ...unctions/functions-bindings-openai-embeddings-input.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides explicit examples and configuration details for PowerShell, a Windows-centric scripting language, including dedicated sections for function.json and run.ps1 files. No equivalent Linux shell (e.g., Bash) examples or references are present. The prominence of PowerShell and the lack of Linux-specific tooling or examples suggest a bias toward Windows environments.
Recommendations
  • Add equivalent Bash or shell script examples for Linux users alongside PowerShell examples.
  • Include notes or sections on how to configure and run Azure Functions bindings in Linux environments.
  • Ensure that references to configuration files (e.g., function.json) are accompanied by cross-platform guidance.
  • Where PowerShell is used, clarify if the steps are cross-platform or provide alternatives for Linux/macOS.
  • Review all code samples and tooling references to ensure parity for Linux users, including troubleshooting and environment setup.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples and instructions for registering Azure Functions binding extensions, but demonstrates a Windows bias by referencing PowerShell as a primary language, mentioning Visual Studio and Visual Studio Code developer guides (which are Windows-centric), and omitting explicit Linux/macOS command-line examples or tooling alternatives. The use of 'func extensions install' is described without platform-specific guidance, and there is no mention of Linux package managers, shell commands, or editor alternatives.
Recommendations
  • Add explicit Linux/macOS examples for installing and managing extensions, such as using Bash or zsh commands.
  • Include references to cross-platform editors (e.g., VS Code on Linux/macOS, JetBrains Rider) and clarify that steps apply on all platforms.
  • Provide instructions for using Azure Functions Core Tools on Linux/macOS, including installation via npm or package managers.
  • Mention platform-specific considerations for file paths, permissions, and environment setup.
  • Balance PowerShell references with Bash/zsh equivalents where command-line actions are described.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example Powershell Heavy Windows First
Summary
The documentation provides code samples for C#, JavaScript, and Python, but omits complete examples for PowerShell and Java, noting that samples are 'pending' or 'not supported.' There is no evidence of explicit Windows bias in terms of tooling or instructions, but the presence of PowerShell as a language option (with incomplete samples) and the lack of Linux-specific instructions or shell examples (e.g., Bash, CLI) may suggest a subtle bias toward Windows environments. The documentation does not mention OS-specific tools or patterns, but the absence of Linux shell or CLI examples and the focus on PowerShell (a Windows-centric language) can be considered a form of bias.
Recommendations
  • Provide complete PowerShell samples and clarify their cross-platform compatibility (Windows/Linux/macOS).
  • Add Linux/Bash shell or Azure CLI examples for configuration and deployment steps, if relevant.
  • Ensure parity in sample completeness and clarity across all supported languages, including Linux-friendly scripting options.
  • Explicitly mention that the examples are OS-agnostic where applicable, or provide notes about OS-specific considerations.
  • Consider adding troubleshooting or environment setup notes for both Windows and Linux users to ensure inclusivity.
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-08 00:53
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 'func.exe' in the description and the use of Windows-centric terminology (such as .pfx certificates, trusted certificates, and PowerShell-specific options) suggest a preference for Windows environments. There is an emphasis on PowerShell as a supported worker runtime, with features like managed dependencies only available for PowerShell. Some features, such as log streaming, are noted as 'not yet supported for Linux' in certain plans, but Windows support is implied or assumed. There are no explicit Linux or cross-platform command examples, and Windows tools and patterns (e.g., .NET Framework 4.8, Microsoft Azure Storage Emulator) are mentioned without Linux equivalents or alternatives.
Recommendations
  • Add explicit Linux and macOS command examples alongside Windows ones, including shell syntax (bash/zsh) and platform-specific notes.
  • Replace or supplement references to Windows-only tools (e.g., Microsoft Azure Storage Emulator) with Linux alternatives (e.g., Azurite) and provide installation instructions for each platform.
  • Clarify cross-platform support for features such as certificate creation, log streaming, and managed dependencies, and note any platform-specific limitations.
  • Avoid using Windows-centric terminology (such as 'trusted certificate on your computer') without explaining how the same functionality works on Linux/macOS.
  • Ensure parity in feature availability and documentation for PowerShell and other runtimes, and highlight any differences in support between platforms.
  • Where features are not supported on Linux, provide workarounds or roadmap information 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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page 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 may suggest a Windows bias, especially since PowerShell is less commonly used on Linux for Azure resource management. There are no explicit Bash or shell script examples, nor is there mention of Linux-specific tools or workflows. The page does not clarify cross-platform compatibility for PowerShell, nor does it provide guidance for Linux users who may prefer Bash. The use of Cloud Shell mitigates some bias, as it is cross-platform, but the overall presentation favors Windows tools and patterns.
Recommendations
  • Add explicit Bash or shell script examples for deploying ARM templates, especially for Linux users.
  • Clarify that Azure PowerShell can be used on Linux and macOS, or note any limitations.
  • Include a section comparing Azure CLI, PowerShell, and Bash, and recommend the best tool for each platform.
  • Ensure that instructions and screenshots do not assume a Windows environment (e.g., avoid referencing Windows-only features or UI patterns).
  • Mention cross-platform compatibility in the prerequisites and deployment sections.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-develop-local.md ...in/articles/azure-functions/functions-develop-local.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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. Visual Studio (Windows-only) is consistently listed first in environment tables for C#, and is referenced as a primary development tool. PowerShell is included as a language option, which is inherently Windows-centric, and PowerShell's Invoke-RestMethod is listed as an HTTP test tool before curl. Windows-specific tools and patterns (Visual Studio, PowerShell) are mentioned before or alongside cross-platform options, but Linux/macOS equivalents are present. There are no outright missing Linux examples, and Visual Studio Code and Core Tools are emphasized as cross-platform.
Recommendations
  • List cross-platform tools (Visual Studio Code, Core Tools) before Windows-only tools (Visual Studio) in environment tables and recommendations.
  • When referencing HTTP test tools, list curl (cross-platform) before PowerShell Invoke-RestMethod.
  • Add explicit examples or notes for Linux/macOS users where Windows-specific instructions are given (e.g., changing ports in Visual Studio).
  • Clarify when tools are Windows-only (e.g., Visual Studio) and provide parity instructions for Linux/macOS.
  • Consider including more Linux/macOS screenshots or terminal examples to balance visual representation.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-develop-vs.md .../main/articles/azure-functions/functions-develop-vs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on development using Visual Studio 2022, a Windows-centric IDE, and provides step-by-step instructions and screenshots for Windows workflows only. There are no examples or guidance for Linux or cross-platform development environments (such as VS Code or CLI-based workflows). Package installation is shown only with PowerShell commands, and remote debugging is explicitly stated as supported only on Windows. Windows tools and patterns are mentioned exclusively and before any alternatives.
Recommendations
  • Add equivalent instructions and examples for developing Azure Functions using VS Code and/or CLI tools on Linux and macOS.
  • Provide package installation examples using dotnet CLI (e.g., 'dotnet add package ...') alongside PowerShell.
  • Clarify which steps are Windows-specific and offer alternatives for Linux/macOS users, such as using Azure Functions Core Tools directly.
  • Include screenshots and UI descriptions for VS Code or other cross-platform editors.
  • Explicitly mention remote debugging limitations and provide guidance for Linux/macOS users, including any available alternatives.
  • Reference cross-platform documentation and tooling where appropriate, and avoid assuming Visual Studio is the only development environment.
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-08 00:53
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 Windows bias in several areas. Executable examples and configuration consistently use 'handler.exe' as the default, with Linux/macOS alternatives mentioned only parenthetically or not at all. Deployment instructions reference Azure Functions Core Tools without clarifying cross-platform usage or providing Linux-specific guidance. There is a lack of explicit Linux shell or file permission examples, and Windows naming conventions are prioritized throughout. No Linux-specific troubleshooting, deployment, or file system examples are provided.
Recommendations
  • Provide parallel examples using Linux/macOS conventions, such as 'handler' instead of 'handler.exe', and clarify when file extensions are required.
  • Include explicit instructions for compiling and running custom handlers on Linux/macOS, including file permissions (e.g., 'chmod +x handler').
  • Offer deployment guidance for Linux environments, including containerization and platform-specific dependencies.
  • Add troubleshooting steps relevant to Linux, such as checking executable permissions and using Linux-native diagnostic tools.
  • Ensure all code and configuration samples show both Windows and Linux/macOS variants side-by-side.
  • Reference cross-platform tools and avoid Windows-centric terminology unless necessary, or provide equal coverage for Linux/macOS tools.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-how-to-azure-devops.md ...icles/azure-functions/functions-how-to-azure-devops.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows-based build agents ('windows-latest') are used by default for C# and PowerShell examples, and Windows is the default appType for deployments. PowerShell is included as a first-class language, with no mention of Bash or Linux shell alternatives for scripting. Windows deployment and slot examples are presented before Linux equivalents, and the documentation often defaults to Windows settings or tools, only specifying Linux as an alternative or with additional configuration.
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which is shown first, to avoid implicit prioritization.
  • For C# and PowerShell, provide both 'windows-latest' and 'ubuntu-latest' agent examples where possible, noting any platform-specific requirements.
  • Include Bash or Linux shell scripting examples alongside PowerShell, especially for automation tasks.
  • Clarify when Windows is required and when Linux is equally supported, and avoid language that implies Windows is the default or preferred platform.
  • Ensure all features and tasks (such as deployment slots, build steps, and deployment methods) are documented for both Windows and Linux, noting any limitations explicitly.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-deployment-technologies.md ...s/azure-functions/functions-deployment-technologies.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a Windows-first bias in several areas. Windows-specific deployment methods (such as source control, local Git, and FTPS) are called out as 'Windows-only' in the technology availability table, while Linux equivalents are either missing or less emphasized. Examples and instructions frequently reference Visual Studio and Windows-centric tools before mentioning cross-platform or Linux alternatives. Some deployment scenarios (like remote build) provide more detail for Windows than Linux, and Linux-specific requirements (such as setting environment variables for remote build) are described as exceptions rather than defaults. There is a lack of Linux-specific command-line examples, and the documentation often assumes the use of Windows-based development environments.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows examples for all deployment methods, especially for CLI usage and remote build scenarios.
  • Ensure parity in documentation for deployment technologies that are available on Linux, such as Docker container deployments and remote build, with clear step-by-step guides.
  • Highlight cross-platform tools (such as Azure Functions Core Tools and VS Code) before Windows-only tools (like Visual Studio), or present them together.
  • Clarify which deployment methods are available on Linux and provide guidance for Linux users where Windows-only methods are mentioned.
  • Include troubleshooting and best practices for Linux environments, such as handling dependencies and storage configuration.
  • Avoid presenting Windows tools and workflows as the default; instead, use neutral language and structure to support both platforms equally.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-event-grid-blob-trigger.md ...s/azure-functions/functions-event-grid-blob-trigger.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively using Visual Studio Code and its Azure extensions for all steps, including storage emulation (Azurite), resource creation, and deployment. All instructions and screenshots assume the use of VS Code, which is most commonly used on Windows, and do not mention or provide alternatives for Linux command-line tools (such as Azure CLI, Bash, or Powershell Core on Linux). There are no examples or instructions for performing these tasks outside of VS Code, nor is there guidance for users who prefer terminal-based workflows typical on Linux.
Recommendations
  • Add equivalent instructions using Azure CLI and Bash for all resource creation, deployment, and management steps, including creating storage accounts, blob containers, function apps, and event subscriptions.
  • Provide examples for running and debugging Azure Functions locally using Azure Functions Core Tools directly from the command line, without relying on Visual Studio Code.
  • Include instructions for installing and running Azurite from the command line (npm or Docker), which is platform-agnostic, rather than only through the VS Code extension.
  • Offer screenshots or terminal output examples from Linux environments to demonstrate parity.
  • Explicitly mention that all steps can be performed on Linux and macOS, and provide links to relevant cross-platform documentation.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-how-to-use-azure-function-app-settings.md ...ns/functions-how-to-use-azure-function-app-settings.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 in several ways: Windows and PowerShell tools are consistently presented alongside or before Linux alternatives, and many examples and features are Windows-specific. Linux support is often mentioned as unavailable, limited, or planned for retirement. PowerShell examples are given equal or greater prominence than CLI, and Windows tools like Kudu and App Service Editor are described as unavailable or limited on Linux. Some migration and development scenarios are explicitly Windows-only, with Linux options missing or described as unsupported.
Recommendations
  • Provide explicit Linux examples and workflows wherever Windows or PowerShell examples are given, especially for plan migration, app settings management, and deployment.
  • Clarify which Azure CLI commands and features work on Linux and provide Linux-specific instructions where behavior differs.
  • When describing portal features or tools (e.g., Kudu, App Service Editor), note Linux alternatives or workarounds, and update feature matrices to highlight parity gaps and future plans.
  • Avoid language that presents Windows as the default or primary platform; instead, structure documentation to treat Windows and Linux equally, or clearly indicate platform-specific limitations.
  • Where features are unavailable on Linux, provide guidance or links to alternative approaches for Linux users.
  • Regularly review and update documentation as Linux support evolves, ensuring Linux users are not left with outdated or incomplete information.
GitHub Create Pull Request
← Previous Page 12 of 41 Next →