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 976-1000 of 1023 flagged pages
Azure Functions Memory profiling of Python apps in Azure Functions ...es/azure-functions/python-memory-profiler-reference.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates minor Windows bias in the local development setup instructions. Windows PowerShell is mentioned first, and Windows-specific commands (e.g., 'py -m venv .venv', '.venv\Scripts\Activate.ps1') are presented before their Linux equivalents. However, Linux alternatives are provided for each step, and no critical functionality is missing for Linux/macOS users.
Recommendations
  • Present Linux/macOS and Windows instructions side-by-side or in tabs, rather than listing Windows first.
  • Use platform-neutral language (e.g., 'Open a terminal') instead of 'Open a Windows PowerShell or any Linux shell as you prefer.'
  • Explicitly mention macOS where Linux is referenced, as many users develop on macOS.
  • Consider using bash-style commands as the default, with Windows alternatives shown as needed.
GitHub Create Pull Request
Azure Functions Respond to blob storage events using Azure Functions ...ticles/azure-functions/scenario-blob-storage-events.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates minor Windows bias by listing Windows-specific instructions and PowerShell examples alongside other languages, and occasionally referencing Windows-specific behaviors (e.g., terminal settings). However, Linux/macOS instructions are present and parity is generally maintained, especially for Python virtual environments and Azurite usage.
Recommendations
  • Ensure Linux/macOS instructions are always presented alongside Windows instructions, not after them.
  • Where Windows-specific troubleshooting is mentioned (e.g., VS Code terminal settings), add equivalent notes for Linux/macOS users if relevant.
  • For PowerShell, clarify cross-platform compatibility and provide Bash equivalents where possible.
  • Explicitly state that all CLI commands (azd, func, az) work on Linux/macOS, and link to platform-specific installation guides.
  • Review command palette instructions to ensure they are not Windows-centric (e.g., clarify Ctrl-click vs. right-click for Mac).
GitHub Create Pull Request
Azure Functions Respond to database changes in Azure Cosmos DB using Azure Functions ...-functions/scenario-database-changes-azure-cosmosdb.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
πŸ”§ Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias in several areas. Windows-specific tools and patterns (such as PowerShell's Set-ExecutionPolicy) are presented alongside Linux/macOS equivalents, but the Windows command is more complex and receives explicit troubleshooting advice. Additionally, there is a troubleshooting tip specifically for Windows users regarding WSL Bash, which is not mirrored for Linux/macOS users. However, most commands and workflows are cross-platform, and Linux/macOS instructions are present and not omitted.
Recommendations
  • Ensure troubleshooting tips are provided for all platforms, not just Windows (e.g., issues with default terminals on Linux/macOS).
  • Present Linux/macOS and Windows instructions in parallel, with equal detail and prominence.
  • Where possible, use cross-platform commands or clarify platform-specific requirements without prioritizing Windows.
  • Add explicit troubleshooting steps for Linux/macOS environments (e.g., permissions, shell compatibility) if relevant.
  • Review the order of example presentation to avoid always listing Windows first.
GitHub Create Pull Request
Azure Functions Storage considerations for Azure Functions ...ain/articles/azure-functions/storage-considerations.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Windows Tools
Summary
The documentation generally maintains cross-platform neutrality, but there are some signs of Windows bias. Windows plans and behaviors are often mentioned first or in more detail, especially in sections about Azure Files and scaling. PowerShell examples are provided alongside Azure CLI, but CLI is shown first for Linux-specific features. Some features and limitations are described as 'Windows only' or with more detail for Windows, and PowerShell is referenced for managed dependencies. However, Linux-specific instructions and parity are present, especially in the mounting file shares section.
Recommendations
  • Ensure that Linux and macOS instructions/examples are given equal prominence and detail as Windows, especially in sections about deployment, scaling, and storage configuration.
  • Where features are Windows-only, clearly state Linux/macOS alternatives or workarounds.
  • Provide explicit Linux/macOS examples for tasks that currently only reference PowerShell or Windows tools.
  • Consider adding Bash or Python scripting examples where PowerShell is referenced, especially for managed dependencies.
  • Review ordering so that Linux and cross-platform options are not consistently listed after Windows options.
GitHub Create Pull Request
Azure Functions Azure Functions Scenarios ...b/main/articles/azure-functions/functions-scenarios.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation provides parity across multiple programming languages, including C#, Python, JavaScript, TypeScript, Java, and PowerShell. While PowerShell is included as a first-class language pivot throughout, there is no evidence of Windows-specific tools, Windows-only examples, or Windows-first ordering. No Windows-exclusive patterns or missing Linux examples are present. The only mild bias is the inclusion of PowerShell as a language pivot, which may be perceived as Windows-centric, but all examples are cross-platform and do not rely on Windows-specific tooling.
Recommendations
  • Clarify that PowerShell examples are cross-platform and can run on Linux hosts.
  • Where relevant, mention that all Azure Functions features and triggers are supported on both Windows and Linux hosting plans.
  • If any example or tutorial relies on Windows-only tooling (such as Visual Studio), provide equivalent instructions for Linux (such as VS Code or CLI).
  • Explicitly state platform compatibility in introductory sections to reassure Linux users.
GitHub Create Pull Request
Azure Functions Apache Kafka trigger for Azure Functions ...es/azure-functions/functions-bindings-kafka-trigger.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation provides examples for multiple languages, including PowerShell, which is primarily a Windows-centric shell. However, there is no evidence of Windows bias in terms of exclusive use of Windows tools, Windows-first ordering, or missing Linux examples. All examples are provided for C#, JavaScript, Python, Java, and PowerShell, and the content is cross-platform in nature. There are no references to Windows-only tools, nor is PowerShell given priority over other languages. However, the inclusion of PowerShell examples may be interpreted as a mild bias towards Windows environments, since PowerShell is most commonly used on Windows, though it is available on Linux and macOS as well.
Recommendations
  • Clarify that PowerShell examples are cross-platform and can be run on Linux/macOS with PowerShell Core.
  • Consider adding Bash or other Linux-native shell examples if relevant for scripting scenarios.
  • Explicitly mention platform compatibility for all code samples, especially for PowerShell, to reinforce Linux parity.
  • Ensure that any references to file paths, certificates, or environment variables use platform-neutral syntax or provide both Windows and Linux/macOS variants.
GitHub Create Pull Request
Azure Functions Azure Functions Web PubSub output binding ...zure-functions/functions-bindings-web-pubsub-output.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides code samples for C# and JavaScript, but omits complete examples for Python and PowerShell, and states that Java is not supported. There is no evidence of Windows-specific tools, PowerShell-heavy content, or Windows-first ordering. However, the lack of Linux-oriented examples (e.g., bash, Linux shell, or explicit Linux instructions) and the absence of parity for Python and PowerShell may disadvantage Linux users.
Recommendations
  • Add complete Python examples, ensuring they are runnable on Linux environments.
  • If PowerShell examples are provided, also offer bash or shell script equivalents for Linux users.
  • Explicitly mention cross-platform compatibility in setup/configuration instructions.
  • Include troubleshooting steps or logging instructions relevant to Linux (e.g., using tail, journalctl, or bash commands).
  • Clarify any platform-specific requirements or differences, if applicable.
GitHub Create Pull Request
Azure Functions Apache Kafka trigger for Azure Functions ...es/azure-functions/functions-bindings-kafka-trigger.md
Low Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation provides examples for multiple languages, including C#, JavaScript, PowerShell, Python, and Java. However, the inclusion of PowerShell as a first-class example language introduces a Windows bias, as PowerShell is primarily associated with Windows environments. There are no explicit references to Windows-only tools, nor are Windows-specific instructions or patterns prioritized over Linux equivalents. The documentation does not provide OS-specific setup or troubleshooting guidance, so there is no evidence of 'windows_first', 'windows_tools', or 'missing_linux_example' bias types. However, the presence of PowerShell examples without corresponding Bash or shell script examples may disadvantage Linux users.
Recommendations
  • Add Bash or shell script examples alongside PowerShell to provide parity for Linux users.
  • Clarify that PowerShell examples can be run cross-platform (if true), or provide guidance for Linux users on how to adapt PowerShell scripts.
  • Explicitly mention OS compatibility for all code samples, especially for scripting languages.
  • Consider including troubleshooting or setup notes for both Windows and Linux environments where relevant.
GitHub Create Pull Request
Azure Functions Apache Kafka output binding for Azure Functions ...les/azure-functions/functions-bindings-kafka-output.md
Low Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation includes PowerShell as a first-class language for Azure Functions Kafka output binding examples, but does not show any Linux-specific shell (e.g., Bash) examples or mention Linux-native tools. All examples are language-specific and do not reference OS-specific tooling, but the inclusion of PowerShell without a Linux shell equivalent may suggest a slight Windows bias.
Recommendations
  • Add Bash or other Linux shell examples alongside PowerShell for parity, especially in sections where PowerShell is used for scripting.
  • Explicitly mention that all examples work cross-platform unless otherwise noted.
  • If any OS-specific configuration or troubleshooting is relevant, provide both Windows and Linux instructions.
  • Clarify that PowerShell Core is available on Linux, or provide examples using Bash for Linux users.
GitHub Create Pull Request
Azure Functions Azure OpenAI text completion input binding for Azure Functions ...ions/functions-bindings-openai-textcompletion-input.md
Low Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation provides code examples and configuration details for multiple programming languages, including C#, Java, JavaScript, TypeScript, Python, and PowerShell. However, PowerShell is the only shell scripting language represented, and its examples and configuration sections are given equal prominence to other languages. There is no evidence of Windows-specific tools or patterns being mentioned exclusively or before Linux equivalents, nor are there missing Linux examples for the languages covered. The documentation does not mention Linux shell scripting (e.g., Bash) or provide parity for Linux-native automation scenarios.
Recommendations
  • Add Bash or other Linux shell scripting examples alongside PowerShell to ensure parity for Linux users.
  • Include notes or examples for configuring and running Azure Functions with OpenAI bindings on Linux environments.
  • Clarify that PowerShell examples are applicable on Linux (via PowerShell Core) or provide alternative Linux-native scripting approaches.
  • Review related content and links to ensure Linux users have guidance for their environments.
GitHub Create Pull Request
Azure Functions Azure Functions Web PubSub output binding ...zure-functions/functions-bindings-web-pubsub-output.md
Low Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides code samples only for C# and JavaScript, with explicit notes stating that Python and PowerShell samples are pending and Java is not supported. There is no evidence of Windows-specific tools, PowerShell-heavy content, or Windows-first ordering. However, the absence of Linux-oriented examples (e.g., bash, CLI usage, or Linux-specific instructions) and the lack of parity for Python and PowerShell may disadvantage Linux users.
Recommendations
  • Add complete Python samples, as Python is widely used on Linux.
  • Provide PowerShell samples, but also include bash or Azure CLI equivalents for Linux users.
  • Where configuration or troubleshooting steps are given, include both Windows and Linux command-line instructions.
  • Ensure that any references to tools or patterns (such as logging or environment variable setup) include Linux-compatible alternatives.
  • Explicitly mention cross-platform compatibility in setup and usage instructions.
GitHub Create Pull Request
Azure Functions Azure OpenAI assistant post input binding for Azure Functions ...tions/functions-bindings-openai-assistantpost-input.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation provides a dedicated section for PowerShell, including both code and configuration examples, while not offering equivalent coverage for Linux shell scripting (e.g., Bash) or other Linux-specific tools. There is no mention of Linux-specific patterns or examples, and PowerShell is the only OS-specific language featured, which may suggest a Windows bias in the examples and configuration guidance.
Recommendations
  • Add equivalent examples for Bash or other common Linux shells, especially for configuration and scripting tasks.
  • Clarify that PowerShell examples can be run cross-platform, or provide explicit instructions for Linux users where relevant.
  • Include notes or sections on how to perform the same tasks using Linux-native tools or scripting languages.
  • Ensure that documentation does not assume Windows as the default environment, and mention Linux compatibility where appropriate.
GitHub Create Pull Request
Azure Functions Apache Kafka trigger for Azure Functions ...es/azure-functions/functions-bindings-kafka-trigger.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation provides code examples for multiple languages, including C#, JavaScript, Python, Java, and PowerShell. However, PowerShell is included as a first-class language example, which is uncommon for cross-platform cloud/Kafka scenarios and is primarily a Windows-centric shell. There are no explicit Windows-only tools, nor are Windows instructions or patterns prioritized over Linux equivalents. No CLI or OS-specific setup instructions are present, and examples are language-focused rather than platform-focused. There are no missing Linux examples, but the inclusion of PowerShell may suggest a slight Windows bias.
Recommendations
  • Clarify that PowerShell examples are cross-platform (PowerShell Core) if applicable, or provide equivalent Bash/shell script examples for Linux users.
  • If PowerShell is included for automation, consider adding Bash or other Linux-native scripting examples to ensure parity.
  • Explicitly mention that all code samples are OS-agnostic unless otherwise noted, and provide guidance for both Windows and Linux environments where relevant.
  • Review any referenced external tools or setup instructions in linked pages to ensure Linux parity.
GitHub Create Pull Request
Azure Functions Apache Kafka output binding for Azure Functions ...les/azure-functions/functions-bindings-kafka-output.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation provides code examples for multiple languages, including C#, JavaScript, Python, Java, and PowerShell. However, the inclusion of PowerShell as a first-class example language may indicate a subtle Windows bias, as PowerShell is primarily a Windows-centric shell (though now cross-platform). There is no evidence of exclusive use of Windows tools, Windows-only patterns, or Windows-first ordering in examples or configuration instructions. Linux parity is generally maintained, but the prominence of PowerShell may suggest a slight preference for Windows environments.
Recommendations
  • Clarify that PowerShell examples are cross-platform, or provide equivalent Bash/shell script examples for Linux users where relevant.
  • Explicitly mention that all code samples (including PowerShell) are intended to work on both Windows and Linux environments, especially for Azure Functions hosted on Linux.
  • If any operational steps (such as local development, deployment, or troubleshooting) are referenced elsewhere, ensure Linux-specific instructions or alternatives are provided alongside Windows/PowerShell examples.
  • Consider adding a note or section highlighting Linux compatibility and best practices for Kafka output bindings in Azure Functions.
GitHub Create Pull Request
Azure Functions Azure Functions Web PubSub output binding ...zure-functions/functions-bindings-web-pubsub-output.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides code samples for C# and JavaScript, but for Python and PowerShell, it states that complete samples are pending. There is no evidence of Windows-specific tools, PowerShell-heavy content, or Windows-first ordering. However, the lack of Linux-oriented or cross-platform examples (such as bash, CLI, or Python samples) indicates a bias towards languages and patterns more commonly used on Windows, with incomplete parity for Linux-preferred environments.
Recommendations
  • Add complete Python samples, as Python is widely used on Linux.
  • If PowerShell samples are added, ensure bash or shell equivalents are also provided for Linux users.
  • Include Azure CLI examples for configuration and troubleshooting steps, not just .NET/C# references.
  • Explicitly mention cross-platform compatibility in setup and troubleshooting sections.
  • Ensure all language pivots (Python, PowerShell, Java) have equal coverage and working samples.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-kafka-output.md ...les/azure-functions/functions-bindings-kafka-output.md
Low Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation provides language-specific examples for C#, JavaScript, PowerShell, Python, and Java, but the PowerShell section may indicate a slight Windows bias due to the prominence of PowerShell as a Windows-centric scripting language. However, there are no explicit signs of Windows-first ordering, exclusive mention of Windows tools, or missing Linux examples. The documentation avoids platform-specific instructions and focuses on language parity, with configuration and usage sections applicable across platforms.
Recommendations
  • Clarify in the PowerShell section that Azure Functions PowerShell worker is cross-platform and can run on Linux, not just Windows.
  • Add a brief note or link in the PowerShell section about using PowerShell Core on Linux, to reinforce cross-platform support.
  • Ensure that any references to file paths, certificates, or environment variables use platform-neutral syntax or provide both Windows and Linux examples if relevant.
  • If any troubleshooting or deployment steps are added in future updates, include both Windows and Linux command-line instructions (e.g., Bash and PowerShell).
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-kafka-trigger.md ...es/azure-functions/functions-bindings-kafka-trigger.md
Low Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation provides examples for multiple programming languages, including C#, JavaScript, PowerShell, Python, and Java. While PowerShell is included as a first-class language for Azure Functions, its presence may indicate a mild Windows bias, as PowerShell is most commonly associated with Windows environments. However, there are no explicit signs of Windows-first ordering, exclusive use of Windows tools, or missing Linux examples. The documentation avoids mentioning Windows-specific tools or patterns and does not prioritize Windows over Linux in its instructions or examples.
Recommendations
  • Clarify that PowerShell examples are cross-platform, and mention compatibility with PowerShell Core on Linux/macOS.
  • Add explicit notes or examples for Bash or other Linux-native scripting languages if relevant to Azure Functions usage.
  • Ensure any references to file paths, certificates, or environment variables use platform-agnostic syntax or provide both Windows and Linux examples.
  • If troubleshooting or deployment steps are added in future, provide parity for both Windows and Linux command-line tools.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-openai-assistantpost-input.md ...tions/functions-bindings-openai-assistantpost-input.md
Low Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation provides dedicated and detailed coverage for PowerShell, including explicit configuration and code examples, while not offering equivalent treatment for Linux shell environments (such as Bash). There are no Windows-specific tools or patterns outside of PowerShell, but the presence of a PowerShell section without a corresponding Bash or Linux shell section indicates a bias toward Windows scripting environments.
Recommendations
  • Add equivalent Bash or Linux shell examples alongside PowerShell, especially for configuration and scripting scenarios.
  • Clarify that PowerShell examples can be run cross-platform (if true), or provide explicit instructions for Linux users.
  • Ensure that any references to function.json or other configuration files include notes or examples for editing and deploying from Linux environments.
  • Where possible, provide parity in documentation structure and depth for both Windows (PowerShell) and Linux (Bash) users.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-web-pubsub-output.md ...zure-functions/functions-bindings-web-pubsub-output.md
Low Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides code examples for C# and JavaScript, but omits examples for Python and PowerShell, stating that samples are pending. There is no evidence of Windows-specific tools, PowerShell-heavy content, or Windows-first ordering. However, the lack of Linux-oriented examples (e.g., bash, Linux CLI) or explicit Linux parity is a subtle bias, as users on Linux may not find relevant guidance.
Recommendations
  • Add complete Python and PowerShell code samples to match the C# and JavaScript examples.
  • Include examples or notes for running Azure Functions and Web PubSub bindings on Linux environments (e.g., using Azure Functions Core Tools on Linux, bash commands for setup).
  • Ensure troubleshooting and configuration sections mention cross-platform considerations, such as differences in environment variables or logging on Linux vs. Windows.
  • If PowerShell examples are added, clarify their cross-platform compatibility (Windows PowerShell vs. PowerShell Core on Linux).
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-kafka-output.md ...les/azure-functions/functions-bindings-kafka-output.md
Low Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation provides full parity examples for C#, JavaScript, Python, Java, and PowerShell. However, the inclusion of PowerShell as a primary example language may indicate a slight Windows bias, as PowerShell is predominantly used on Windows systems. There are no explicit references to Windows-only tools, Windows-first instructions, or missing Linux examples. All configuration and code samples are cross-platform, and no OS-specific instructions are present.
Recommendations
  • Clarify that PowerShell examples can be run cross-platform (PowerShell Core), or provide Bash examples alongside PowerShell for shell scripting parity.
  • Explicitly mention that all examples are intended to work on both Windows and Linux hosts, unless otherwise noted.
  • If any platform-specific setup is required (e.g., certificate paths, file permissions), provide notes for both Windows and Linux.
  • Consider adding a section on running Azure Functions with Kafka bindings on Linux, including any differences in environment setup or troubleshooting.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-web-pubsub-output.md ...zure-functions/functions-bindings-web-pubsub-output.md
Low Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides code samples for C# and JavaScript, but for Python and PowerShell, it only states that 'complete samples for this language are pending.' There is no evidence of Windows-specific tools, PowerShell-heavy content, or Windows-first ordering. However, the lack of Linux-oriented examples (e.g., bash, Linux CLI, or Python samples) means Linux users do not have parity in guidance.
Recommendations
  • Add complete Python samples, as Python is widely used on Linux.
  • If PowerShell samples are provided, also provide bash or shell script equivalents for Linux users.
  • Include instructions or examples for configuring and running Azure Functions on Linux environments (e.g., using Azure Functions Core Tools on Linux).
  • Ensure troubleshooting and logging sections mention cross-platform tools and do not assume Windows-only environments.
  • Explicitly state cross-platform compatibility in setup/configuration sections.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-kafka-trigger.md ...es/azure-functions/functions-bindings-kafka-trigger.md
Low Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation provides examples for multiple programming languages, including C#, JavaScript, PowerShell, Python, and Java. However, the inclusion of PowerShell as a first-class example language may indicate a mild Windows bias, as PowerShell is primarily a Windows-centric shell, though it is now cross-platform. There are no explicit references to Windows-only tools, Windows-first instructions, or missing Linux equivalents. All code samples and configuration instructions are generic and do not reference OS-specific tooling, paths, or patterns. No explicit Windows tools or patterns are mentioned, and Linux parity appears to be maintained in all other respects.
Recommendations
  • Clarify that PowerShell examples are cross-platform and provide guidance for using PowerShell on Linux/macOS if relevant.
  • Consider including Bash or other Linux-native shell examples alongside PowerShell to further demonstrate parity.
  • Explicitly state that all examples (including PowerShell) are intended to work on both Windows and Linux environments unless otherwise noted.
  • If any OS-specific configuration is required (e.g., file paths, certificate locations), provide examples for both Windows and Linux formats.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-first-java-gradle.md .../azure-functions/functions-create-first-java-gradle.md
Low Priority View Details →
Scanned: 2025-08-12 00:00
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation specifies 'os = windows' as the default in the Gradle configuration example, which may lead users to assume Windows is the primary or preferred deployment target. There are no explicit PowerShell or Windows command-line examples, and all shell commands use Bash syntax, which is cross-platform. However, the documentation does not mention or show how to set up for Linux or macOS, nor does it clarify the implications of the 'os' setting or provide parity for non-Windows environments.
Recommendations
  • Explicitly mention that the Gradle 'os' setting can be changed to 'linux' or 'windows', and explain the implications of each.
  • Provide an example Gradle configuration for Linux (e.g., 'os = "linux"') and note when/why to use it.
  • Clarify that all command-line examples work on Linux, macOS, and Windows (with appropriate shells), or provide platform-specific notes if there are differences.
  • Highlight that Java 21 is currently supported on Linux only, and provide guidance for users on other platforms.
  • Consider adding a short section or callout for macOS/Linux users, especially regarding environment variable setup and any platform-specific steps.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-versioning.md ...le-task-scheduler/durable-task-scheduler-versioning.md
Low Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display overt Windows bias in terms of command-line examples or tool references. However, it lacks any platform-specific operational guidance or examples (such as shell commands, deployment steps, or environment setup) for either Windows or Linux. This omission is notable because, in sections where PowerShell is mentioned as a pivot, there are no actual PowerShell-specific examples or instructionsβ€”nor are there any for Linux (e.g., Bash). The documentation is focused on SDK usage in various programming languages, but does not provide parity for Linux users in terms of platform-specific instructions or examples.
Recommendations
  • If platform-specific pivots (such as PowerShell) are included, ensure that equivalent Linux (e.g., Bash) pivots and examples are also provided.
  • If operational steps (such as deployment, environment setup, or CLI usage) are required, provide both Windows and Linux examples, or clarify that the steps are platform-agnostic.
  • Remove empty or placeholder pivots (such as the PowerShell pivot with no content) or fill them with meaningful content for both Windows and Linux users.
  • Explicitly state in the documentation when features or instructions are platform-independent to avoid confusion.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-versioning.md ...le-task-scheduler/durable-task-scheduler-versioning.md
Low Priority View Details →
Scanned: 2025-08-10 00:00
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not show explicit Windows bias in terms of examples or tooling, as it focuses on SDK usage (C#, Java, JavaScript, Python) and does not mention Windows-specific tools or PowerShell. However, there is a lack of Linux-specific examples, shell commands, or references to cross-platform development environments. The documentation does not address platform-specific setup, deployment, or usage scenarios, which may leave Linux users without guidance for parity.
Recommendations
  • Add explicit notes or examples for running Durable Task Scheduler on Linux environments, including any differences in setup or deployment.
  • Include shell (bash) command-line examples for SDK installation, orchestration deployment, or environment configuration, not just code snippets.
  • Mention and link to cross-platform tools (such as Azure CLI) where relevant, and ensure that instructions are not implicitly Windows-centric.
  • If any platform-specific considerations exist (such as file paths, environment variables, or service dependencies), document them for both Windows and Linux.
  • Consider adding a section or callout confirming that all SDKs and features are fully supported on Linux, or note any limitations.
GitHub Create Pull Request
← Previous Page 40 of 41 Next →