Azure Functions
711
Total Pages
610
Linux-Friendly Pages
101
Pages with Bias
14.2%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
233 issues found
Showing 226-233 of 233 flagged pages
Azure Functions
Respond to database changes in Azure Cosmos DB using Azure Functions
...-functions/scenario-database-changes-azure-cosmosdb.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page displays minor Windows bias in several areas. Windows-specific tools and patterns (such as PowerShell's Set-ExecutionPolicy and references to func.exe) are mentioned, and in some cases, Windows instructions are presented before or alongside Linux/macOS equivalents. There is also a troubleshooting note specific to Windows terminal settings. However, Linux/macOS instructions are present where needed, and most steps are cross-platform.
Recommendations
- Ensure Linux/macOS instructions are always presented before or alongside Windows instructions, not after.
- Where Windows-specific troubleshooting is mentioned (e.g., default terminal issues), provide equivalent Linux/macOS troubleshooting tips.
- Use neutral language for tool references (e.g., refer to 'the host process' rather than 'func.exe' when possible).
- Expand examples and troubleshooting to cover common Linux/macOS issues, not just Windows.
- Consider adding explicit parity checks to ensure all steps are equally documented for Linux/macOS users.
Create Pull Request
Azure Functions
Respond to database changes in Azure SQL Database using Azure Functions
...ure-functions/scenario-database-changes-azure-sqldb.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by consistently presenting instructions and shortcuts in a Windows-centric manner (e.g., <kbd>Ctrl</kbd>+click, <kbd>F1</kbd>, <kbd>F5</kbd>), with only occasional mention of macOS alternatives and no explicit Linux-specific guidance. All tooling and workflows are described using Visual Studio Code and its extensions, which are cross-platform, but there is no mention of Linux-specific patterns, shell commands, or alternative editors. There are no PowerShell-specific examples or Windows-only tools, but the lack of explicit Linux instructions or troubleshooting steps may create friction for Linux users.
Recommendations
- Add explicit instructions for Linux users, such as referencing <kbd>Ctrl</kbd>+<kbd>Shift</kbd> or other common Linux shortcuts.
- Include troubleshooting steps for common Linux issues (e.g., permissions, installing Azure Functions Core Tools via apt/yum).
- Mention alternative editors or command-line workflows for users who do not use Visual Studio Code.
- Ensure all keyboard shortcuts are mapped for Linux and macOS, not just Windows.
- Highlight any OS-specific requirements for installing dependencies (e.g., azd, mssql extension, Azurite).
Azure Functions
Run scheduled tasks using Azure Functions
...n/articles/azure-functions/scenario-scheduled-tasks.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally presents cross-platform instructions, but there are subtle Windows biases. Windows command prompt and bash instructions are shown for Python virtual environments, with Windows examples listed after Linux/macOS but before Linux-specific troubleshooting. The use of 'command prompt' and references to '.venv\scripts\activate' (Windows path) are present. The use of 'func.exe' in the stopping instructions is a Windows-specific detail. However, most CLI commands are cross-platform, and Linux/macOS instructions are present for all critical steps.
Recommendations
- Present Linux/macOS instructions before Windows instructions, or group them equally.
- Avoid Windows-specific terminology (e.g., 'func.exe') when describing cross-platform tools.
- Clarify that all commands work in bash/zsh/fish on Linux/macOS and PowerShell/Cmd on Windows.
- Add explicit PowerShell examples if relevant, or clarify when examples are for bash/Cmd.
- Ensure troubleshooting steps for Linux/macOS are as visible as Windows ones.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0003.md
...tions/errors-diagnostics/diagnostic-events/azfd0003.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or commands, but it also omits any troubleshooting steps or examples for both Windows and Linux. This lack of parity is a subtle bias, as users on Linux (or any OS) are not given guidance or examples relevant to their environment.
Recommendations
- Add explicit troubleshooting steps or examples for both Windows (e.g., using PowerShell or Azure CLI on Windows) and Linux (e.g., using Bash or Azure CLI on Linux).
- Include sample commands for checking or updating the AzureWebJobsStorage connection string on both platforms.
- Mention platform-agnostic tools (such as Azure CLI or Azure Portal) and clarify that these can be used on any OS.
- If providing scripts or commands, ensure both Windows and Linux variants are shown side by side.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0011.md
...tions/errors-diagnostics/diagnostic-events/azfd0011.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or instructions, but it references 'deployment scripts' and 'application settings' without clarifying how these are set on different platforms. There are no explicit Windows or PowerShell examples, but there is also no mention of Linux, Bash, or cross-platform tooling. This absence may lead to confusion for Linux users who may not know how to set these values outside of the Azure Portal or Windows-centric tools.
Recommendations
- Add explicit examples for setting FUNCTIONS_WORKER_RUNTIME using both Windows (PowerShell, CMD) and Linux (Bash, CLI) environments.
- Clarify how to set application settings via Azure CLI and in deployment scripts for both Windows and Linux.
- Include links or references to platform-specific guides for managing Azure Functions settings.
- Ensure parity in instructions and examples for both Windows and Linux users throughout the documentation.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/flex-consumption-site-updates.md
...icles/azure-functions/flex-consumption-site-updates.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not display overt Windows bias in terms of examples, tools, or terminology. However, it lacks explicit Linux-specific examples or references, and does not mention platform-specific deployment or monitoring patterns. All configuration examples use platform-neutral infrastructure-as-code tools (Bicep, ARM templates), and monitoring is described via Application Insights and KQL, which are cross-platform Azure services. No Windows-specific tools (e.g., PowerShell, CMD) or terminology are present, but there is also no mention of Linux command-line tools, shell scripts, or platform-specific deployment nuances.
Recommendations
- Add explicit notes clarifying that the described strategies and configuration steps apply equally to both Windows and Linux-based Azure Functions apps.
- Include Linux-specific deployment and monitoring examples (e.g., using Azure CLI in Bash, or shell scripting for automation).
- Mention any platform-specific differences in behavior, if applicable, such as nuances in instance lifecycle or logging between Windows and Linux hosts.
- Provide sample troubleshooting steps or log access instructions for both Windows and Linux environments.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-documentdb-input.md
...azure-functions/functions-bindings-documentdb-input.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page provides only C# code examples and configuration guidance for Azure Functions using DocumentDB input binding. There are no references to Windows-specific tools or patterns, nor is there explicit mention of Windows or Powershell. However, the documentation lacks any Linux-specific examples, CLI commands, or guidance for non-Windows environments. All examples assume the use of Visual Studio/.NET, which is more common on Windows, and there is no mention of cross-platform development environments or Linux-specific instructions.
Recommendations
- Add examples or guidance for using Azure Functions with DocumentDB input binding in Linux environments, such as using the Azure Functions Core Tools on Linux.
- Include CLI-based setup instructions (e.g., using Azure CLI or Bash scripts) alongside or in place of Visual Studio-centric workflows.
- Mention and provide guidance for cross-platform development tools (e.g., VS Code, JetBrains Rider) and how to configure them for this scenario.
- Clarify that the .NET SDK and Azure Functions tools are available on Linux and macOS, and provide any platform-specific prerequisites or troubleshooting tips.
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 →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides code examples for C# and JavaScript, but omits complete samples for Python and PowerShell, and explicitly notes that Java support is unavailable. There is no evidence of Windows bias such as PowerShell-heavy examples, Windows-first ordering, or exclusive mention of Windows tools. However, the absence of Linux-specific examples or parity for Python and PowerShell may disadvantage users on Linux platforms.
Recommendations
- Add complete Python and PowerShell code samples, ensuring they work on both Windows and Linux environments.
- Include explicit notes or examples for running Azure Functions and Web PubSub bindings on Linux (e.g., using Azure Functions Core Tools on Linux, Docker, or WSL).
- Ensure troubleshooting and setup instructions are platform-agnostic or provide Linux-specific guidance where relevant.
- If any tooling or configuration differs between Windows and Linux, document both workflows equally.