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 1-25 of 233 flagged pages
Azure Functions Develop Azure Functions using Visual Studio .../main/articles/azure-functions/functions-develop-vs.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation is heavily focused on Visual Studio 2022, a Windows-centric IDE, and describes workflows, dialogs, and features that are only available on Windows. All examples and instructions assume use of Visual Studio, with no mention of cross-platform alternatives like VS Code or CLI-based workflows. Package installation is shown only via the PowerShell-based Package Manager Console, and remote debugging is explicitly stated as supported only on Windows. There are no Linux/macOS-specific instructions or parity notes.
Recommendations
  • Add equivalent instructions for developing, running, and publishing Azure Functions using Visual Studio Code and Azure Functions Core Tools, which are cross-platform.
  • Provide CLI-based examples for project creation, binding addition, and package installation (e.g., using dotnet CLI and func CLI), alongside or before Visual Studio steps.
  • Include Linux/macOS-specific notes for local development, debugging, and deployment, especially for remote debugging and app settings management.
  • Clarify which features are Windows-only and offer alternative workflows for non-Windows users.
  • Show how to install NuGet packages using dotnet CLI (e.g., 'dotnet add package ...') in addition to PowerShell.
  • Reorder examples so that cross-platform approaches are presented before or alongside Windows/Visual Studio-specific instructions.
GitHub Create Pull Request
Azure Functions Develop Azure Functions using Visual Studio .../main/articles/azure-functions/functions-develop-vs.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation is heavily focused on Visual Studio 2022 and its integrated tooling, which is only available on Windows. All examples, workflows, and screenshots assume the use of Visual Studio, with no mention of cross-platform alternatives like VS Code or CLI-based workflows. Package installation instructions use PowerShell syntax, and remote debugging is explicitly stated to only work on Windows. There are no Linux/macOS-specific instructions or parity examples, making it difficult for non-Windows users to follow or complete the documented tasks.
Recommendations
  • Add equivalent instructions for developing, running, and publishing Azure Functions using Visual Studio Code and Azure Functions Core Tools, which are cross-platform.
  • Provide CLI-based examples for project creation, binding addition, and deployment, using Bash/zsh syntax alongside PowerShell.
  • Include screenshots and step-by-step guides for Linux/macOS environments, especially for tasks like managing app settings and debugging.
  • Clarify which features are Windows-only and suggest alternatives for Linux/macOS users (e.g., remote debugging via VS Code or CLI).
  • Reorder sections so that cross-platform approaches are presented before or alongside Windows/Visual Studio-specific instructions.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/bring-dependency-to-functions.md ...icles/azure-functions/bring-dependency-to-functions.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways: Java examples use Windows-style paths and reference ffmpeg.exe, with no Linux equivalent shown. The Java section does not mention Linux deployment considerations, while the Python section does. PowerShell is mentioned as an upload option before Linux alternatives. There is no parity in showing Linux-specific examples for Java, and Windows tools/patterns (e.g., .exe, Windows paths) are presented first or exclusively.
Recommendations
  • Add Linux-specific examples for Java, including how to reference and execute Linux binaries (e.g., ffmpeg) and handle permissions.
  • In the Java section, clarify cross-platform deployment considerations, such as path formats and executable extensions.
  • When mentioning upload options, list Azure CLI and Linux-native tools before or alongside PowerShell, not after.
  • Avoid using Windows-only file extensions (e.g., .exe) in generic examples; provide both Windows and Linux variants.
  • Explicitly note any platform differences in environment variables, file system paths, and permissions for both Python and Java.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides examples for the Azure Portal, Azure CLI, and Azure PowerShell, with PowerShell (a Windows-centric tool) given equal prominence to the cross-platform Azure CLI. There are no explicit Linux shell (bash) examples, and PowerShell is presented as a primary method. The documentation does not mention or provide parity for Linux-native tools or scripting environments, and the only local example is for local.settings.json, not for command-line usage. There is also a note about a Linux limitation, but no guidance or alternatives are provided for Linux users.
Recommendations
  • Add bash (Linux shell) command-line examples for managing app settings, using Azure CLI in a Linux context.
  • Clarify that Azure CLI is cross-platform and recommend it as the primary command-line tool for both Windows and Linux.
  • De-emphasize PowerShell as a primary method, or clearly label it as Windows-specific, and ensure it is not presented before cross-platform solutions.
  • Provide guidance or workarounds for the Linux-specific limitation regarding hyphens in function names.
  • Include explicit instructions or examples for Linux users, such as using environment variables or configuration files in Linux environments.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-isolated-create-first-csharp.md ...able/durable-functions-isolated-create-first-csharp.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively providing instructions for Visual Studio and Visual Studio Code, both of which are primarily Windows-focused tools (though VS Code is cross-platform). The Visual Studio section is entirely Windows-specific, with no mention of Linux or macOS alternatives. There are no command-line or platform-agnostic instructions, and no explicit Linux/macOS examples or troubleshooting notes. The use of Azurite and Azure Functions Core Tools is mentioned, but only in the context of Visual Studio/VS Code workflows, not in standalone CLI or non-Windows IDE scenarios.
Recommendations
  • Add explicit instructions for creating and testing Durable Functions apps on Linux and macOS, including terminal/CLI workflows using Azure Functions Core Tools.
  • Provide examples using cross-platform editors (e.g., VS Code on Linux/macOS) and clarify any OS-specific steps or differences.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., permissions, path differences, firewall configuration).
  • Mention alternative tools or workflows for users who do not use Visual Studio or Visual Studio Code, such as JetBrains Rider or plain text editors.
  • Ensure that all screenshots and step-by-step instructions are either platform-neutral or include Linux/macOS variants.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-roslyn-analyzer.md ...functions/durable/durable-functions-roslyn-analyzer.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation primarily references Windows-centric tools (Visual Studio, Visual Studio Code) and configuration paths, with detailed instructions and screenshots for Visual Studio, which is predominantly used on Windows. There are no examples or instructions for configuring the Roslyn Analyzer in Linux-native editors or environments (e.g., JetBrains Rider, command-line usage, or cross-platform .NET CLI integration). The documentation does not mention or prioritize Linux or cross-platform workflows.
Recommendations
  • Add instructions for configuring and running the Roslyn Analyzer using the .NET CLI (dotnet build/analyze) on Linux and macOS.
  • Include examples or references for using the analyzer in JetBrains Rider or other cross-platform editors.
  • Clarify that Visual Studio Code is available on Linux and macOS, and provide any Linux/macOS-specific notes if needed.
  • Provide screenshots or terminal examples from Linux environments to demonstrate parity.
  • Mention any differences or limitations when using the analyzer on non-Windows platforms.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/quickstart-python-vscode.md ...es/azure-functions/durable/quickstart-python-vscode.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation shows some Windows bias. While it does provide activation commands for Linux, macOS, and Windows, the Windows (PowerShell) example is given last, which is less problematic. However, the overall tooling focus is on Visual Studio Code and its integrated terminal, which is more commonly used on Windows. The storage emulator section only mentions Azurite via the Visual Studio Code extension, not the CLI, which is more cross-platform. There are no explicit Linux-specific tools or troubleshooting steps, and the HTTP test tool is referenced generically without mentioning common Linux tools like curl or httpie. The documentation does not provide terminal or shell-specific guidance for Linux users beyond the virtual environment activation.
Recommendations
  • Add explicit Linux and macOS CLI instructions for installing and running Azurite (e.g., 'npm install -g azurite; azurite') in addition to the Visual Studio Code extension.
  • Include example HTTP requests using curl or httpie for testing the function, not just browser-based instructions.
  • Mention common Linux package managers (apt, yum, brew) for installing prerequisites like Python and Azure Functions Core Tools.
  • Ensure troubleshooting steps or notes are included for common Linux/macOS issues (e.g., permissions, path issues).
  • Where possible, provide parity in screenshots or terminal output from Linux/macOS environments, not just Visual Studio Code on Windows.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation shows mild Windows bias, primarily by referencing Windows tools and patterns first or exclusively in certain sections. For example, the use of the 'cmd' prompt in CLI examples, explicit instructions for Windows storage emulation, and the mention of 64-bit architecture validation for Windows apps. Linux equivalents are mentioned but often as afterthoughts or in notes, and there are no explicit Linux shell examples or Linux-first instructions.
Recommendations
  • Provide CLI examples using both Windows (cmd/PowerShell) and Linux (bash) syntax where applicable.
  • Include explicit instructions for Linux users, such as how to install dependencies or validate settings on Linux.
  • Mention Linux tools and workflows alongside Windows ones, not only in notes or as exceptions.
  • Ensure screenshots and portal instructions clarify any OS-specific differences, especially for Linux users.
  • Where a section is Windows-only (e.g., 64-bit architecture validation), provide a parallel Linux section explaining the default behavior and how to check architecture if needed.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation shows a Windows bias in several ways: PowerShell is used exclusively for local SQL Server setup, with no Bash or native Linux shell equivalents provided. Windows tools and patterns (e.g., SQL Server Express on Windows, PowerShell scripting, Visual Studio Code instructions referencing Windows dialogs) are mentioned before or instead of Linux alternatives. There are no explicit Bash or Linux-native command examples for common developer tasks, and troubleshooting steps reference Docker Desktop, which is more common on Windows. While Docker is cross-platform, the instructions assume familiarity with Windows-centric tools and workflows.
Recommendations
  • Provide Bash/zsh shell equivalents for all PowerShell commands, especially for Docker-based SQL Server setup and validation.
  • Explicitly mention and show examples for Linux and macOS users, including native package installation commands for tools like sqlcmd.
  • When referencing tools (e.g., SQL Server Express), clarify cross-platform options and provide links or instructions for Linux and macOS.
  • Balance the order of tool mentions (e.g., mention SQL Server Docker image before SQL Server Express on Windows) to avoid Windows-first impression.
  • Add troubleshooting steps relevant to Linux (e.g., using 'docker ps' and 'docker logs' instead of Docker Desktop UI).
  • Ensure all screenshots and UI instructions are either cross-platform or have Linux/macOS equivalents.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0008.md ...tions/errors-diagnostics/diagnostic-events/azfd0008.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation references file paths using backslashes (e.g., 'azure-webjobs-secrets\<FUNCTION_APP_NAME>\host.json'), which is a Windows convention. There are no explicit Linux or cross-platform examples for file paths or command-line instructions. The documentation does not mention or provide parity for Linux/macOS users, nor does it clarify that the instructions apply equally across platforms.
Recommendations
  • Use forward slashes (/) in file paths or clarify that both backslash (\) and forward slash (/) can be used, depending on the platform.
  • Explicitly state that the instructions apply to all platforms, or provide platform-specific notes where relevant.
  • If command-line instructions are added, provide both Windows (PowerShell/CMD) and Linux/macOS (Bash/CLI) examples.
  • Add a note for cross-platform users about how to navigate to the blob storage location using Azure Portal, Azure CLI, or Azure Storage Explorer, with examples for both Windows and Linux environments.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Visual Studio Code and the Azurite storage emulator without clarifying cross-platform compatibility or providing Linux/macOS-specific instructions. The use of 'Press F1' and 'Press F5' in Visual Studio Code, as well as references to 'Terminal' and 'Core Tools', implicitly assume a Windows environment. There are no explicit Linux/macOS terminal commands, nor are there troubleshooting notes for non-Windows users. The Azurite emulator is referenced, but its installation and usage are not shown for Linux/macOS. The documentation does not mention or link to platform-specific guidance for Linux users, and all examples and instructions are presented in a way that is most familiar to Windows users.
Recommendations
  • Explicitly state that Visual Studio Code and Azurite are cross-platform, and provide installation and usage instructions for Linux/macOS alongside Windows.
  • For all command-line instructions (e.g., 'dotnet add package', Azurite usage), show both Windows (PowerShell/CMD) and Linux/macOS (bash/zsh) command examples where syntax or behavior differs.
  • Clarify that 'Press F1' and 'Press F5' in Visual Studio Code work on all platforms, and mention any keyboard shortcut differences for macOS.
  • Add troubleshooting notes or links for common Linux/macOS issues (e.g., permissions, path differences, dependency installation).
  • When referencing tools like Azurite, provide platform-agnostic installation commands (e.g., 'npm install -g azurite') and mention how to start Azurite from the terminal on Linux/macOS.
  • Ensure that any references to file paths or environment variables use cross-platform conventions or provide both Windows and Linux/macOS examples.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-add-output-binding-azure-sql-vs-code.md ...ions/functions-add-output-binding-azure-sql-vs-code.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
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 referencing Visual Studio Code's integrated command palette and Azure portal UI for all steps, with no mention of Linux-specific tools, CLI alternatives, or terminal-based workflows. All instructions for creating resources, managing settings, and interacting with Azure SQL Database rely on GUI-based tools that are most familiar to Windows users. There are no examples using cross-platform command-line tools (e.g., Azure CLI, sqlcmd), and no explicit guidance for Linux users. The use of keyboard shortcuts and right-click actions further reinforces a Windows-centric workflow.
Recommendations
  • Add parallel instructions using Azure CLI and/or PowerShell for resource creation, app settings management, and deployment, making sure to show cross-platform commands.
  • Include examples of connecting to Azure SQL Database and running SQL queries using sqlcmd or Azure Data Studio, both of which are available on Linux.
  • Explicitly mention that all steps can be performed on Linux, and provide Linux-specific keyboard shortcuts or terminal commands where applicable.
  • Provide screenshots or terminal output from Linux environments to reinforce parity.
  • Clarify that Visual Studio Code and Azure Functions Core Tools are cross-platform, and ensure all instructions are validated on Linux and macOS as well as Windows.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits mild Windows bias. It references Windows-specific connection string formats (e.g., <cacheName>.redis.cache.windows.net:6380), includes PowerShell as a first-class example language, and uses Windows-centric terminology in configuration and examples. There is no explicit mention of Linux-specific tools, patterns, or troubleshooting, and the examples do not address platform differences (such as environment variable handling or file permissions) that may affect Linux users.
Recommendations
  • Add notes or examples for Linux users, such as how to set environment variables and file permissions for function apps running on Linux.
  • Include Bash or shell script examples alongside PowerShell to demonstrate parity for Linux environments.
  • Clarify that the connection string format is platform-agnostic, or provide Linux-specific examples if differences exist.
  • Mention any platform-specific limitations or considerations (e.g., file paths, case sensitivity, permissions) for Linux-hosted Azure Functions.
  • Ensure that troubleshooting and advanced configuration sections address both Windows and Linux scenarios.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on .NET/C# and NuGet, which are Windows-centric tools and patterns. There are no explicit Linux or cross-platform command-line examples (e.g., using pip for Python, npm for JavaScript, or CLI commands for Linux environments). The only installation instructions are for NuGet, and there are no mentions of Linux-specific workflows or tools. The documentation does not provide parity in examples or instructions for Linux users, nor does it mention cross-platform considerations. Additionally, PowerShell is listed as a supported language, but there are no Linux shell (bash) equivalents or examples.
Recommendations
  • Add installation instructions and examples for Linux environments, such as using the Azure Functions Core Tools on Linux/macOS.
  • Provide cross-platform command-line examples (e.g., bash, zsh) alongside PowerShell or Windows-specific instructions.
  • Include package installation instructions for other languages (e.g., pip for Python, npm for JavaScript) and clarify cross-platform compatibility.
  • Explicitly mention that the .NET/NuGet instructions are cross-platform if applicable, or provide guidance for .NET development on Linux/macOS.
  • Add a section or note on cross-platform support and any OS-specific considerations for Azure Functions development.
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: 2025-12-29 18:00
Reviewed by: Unknown
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 referencing Windows-centric tools and patterns (e.g., PowerShell, Visual Studio, .cmd/.bat scripts) and mentioning them before or instead of Linux equivalents. Examples and management tooling focus on PowerShell and Visual Studio, with limited or no mention of Linux-native tools or workflows (such as Bash, VS Code on Linux, or Azure CLI usage on Linux). There is also a lack of explicit Linux examples or guidance for Linux users, especially in sections about management and supported languages.
Recommendations
  • Add explicit Linux/Bash examples alongside PowerShell and .cmd/.bat script references.
  • Highlight Azure CLI usage and provide examples for both Windows and Linux environments.
  • Mention and demonstrate development workflows using VS Code on Linux, not just Visual Studio.
  • Clarify cross-platform support for all tools and SDKs, including how to use them on Linux.
  • Include references to Linux package managers (e.g., apt, yum) where relevant.
  • Ensure parity in documentation for Linux users by providing step-by-step guides for common Linux scenarios (deployment, monitoring, management).
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-http-endpoint.md ...cles/azure-functions/functions-create-http-endpoint.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias by consistently listing Windows-centric tools (Visual Studio, Visual Studio Code) before cross-platform or Linux-native tools, and by including a dedicated PowerShell section. References to 'Terminal/command prompt' are ambiguous and may not clearly address Linux users. There is little explicit mention of Linux-specific tools, workflows, or terminology, and Windows development environments are often presented first.
Recommendations
  • Explicitly mention Linux and macOS compatibility in all references to 'Terminal/command prompt', or use 'Terminal (Linux/macOS)' and 'Command Prompt (Windows)' to clarify.
  • Add Linux-native editor options (e.g., JetBrains Rider, Vim, Emacs) where appropriate, or clarify that Visual Studio Code is cross-platform.
  • Ensure that cross-platform or Linux-native tools (such as Azure CLI in bash) are listed before or alongside Windows tools like Visual Studio.
  • Provide explicit Linux/macOS shell commands and screenshots where relevant, not just generic or Windows-centric instructions.
  • Balance PowerShell examples with bash/zsh equivalents, or provide tabs for both where scripting is involved.
  • Review and update terminology to avoid Windows-first language (e.g., avoid 'command prompt' as a generic term).
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying ARM templates. However, the PowerShell examples are given equal prominence to Azure CLI, and there is no mention of Bash or Linux-native scripting alternatives beyond Azure CLI. The use of PowerShell (a Windows-centric tool, though now cross-platform) and the absence of Bash or shell script examples may indicate a Windows bias. Additionally, the PowerShell section is presented as a primary tab, which may reinforce the perception of Windows-first documentation.
Recommendations
  • Add Bash or shell script examples for Linux/macOS users, especially for common deployment tasks.
  • Clarify that Azure CLI commands can be run in Bash, Cloud Shell (Bash), or other shells, and provide explicit Bash examples where appropriate.
  • If PowerShell is included, note its cross-platform availability, but avoid implying it is the default or preferred method for all users.
  • Consider reordering or balancing the prominence of PowerShell and CLI sections, or explicitly stating that Azure CLI is recommended for cross-platform use.
  • Include troubleshooting notes or tips for Linux/macOS users if there are known differences in behavior or prerequisites.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-your-first-function-visual-studio.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-your-first-function-visual-studio.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows by exclusively using Visual Studio (Windows-only) for all steps, referencing Windows UI elements and workflows, and omitting any Linux or cross-platform development instructions. There are no examples or guidance for using Linux tools or workflows, and the only mention of Linux is in the context of the Azure hosting environment, not the development process.
Recommendations
  • Provide parallel instructions for developing C# Azure Functions using Visual Studio Code, which is cross-platform, or JetBrains Rider, which also supports Linux.
  • Include CLI-based examples (using Azure Functions Core Tools and .NET CLI) for creating, running, and deploying functions, suitable for Linux and macOS users.
  • Explicitly mention and link to Linux/macOS development guides in the prerequisites and introduction, not just as an alternative buried in the introduction.
  • When referencing tools like Azurite, clarify installation and usage steps for Linux/macOS environments.
  • Balance screenshots and UI walkthroughs with terminal/command-line equivalents where possible.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-how-to-github-actions.md ...les/azure-functions/functions-how-to-github-actions.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Windows is consistently mentioned before Linux in OS selection instructions and example tabs, and Windows-specific tools and terminology (such as PowerShell and Windows-latest runners) are prominent. PowerShell is included as a language option, but Python is explicitly noted as unsupported on Windows, which is a positive for Linux parity. However, the overall structure and ordering favor Windows, and Windows terminology is used more frequently and with more detail.
Recommendations
  • Alternate the order of Windows and Linux examples/tabs to avoid always listing Windows first.
  • Provide equal detail and prominence for Linux-specific instructions, tools, and terminology.
  • Explicitly mention Linux equivalents for any Windows-specific tools or commands, and ensure Linux is not treated as a secondary option.
  • Add more context or tips for Linux users, such as troubleshooting or environment setup guidance.
  • Review the language and structure to ensure both platforms are presented as first-class options throughout the documentation.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-identity-access-azure-sql-with-managed-identity.md ...ctions-identity-access-azure-sql-with-managed-identity.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. It references PowerShell and Azure portal as primary methods for several steps, with Azure CLI examples provided but not always emphasized first. The SQL tool example uses sqlcmd in Cloud Shell, which is cross-platform, but there is no mention of Linux-specific tools or workflows (e.g., Azure Data Studio, native Linux authentication patterns). There are no explicit Linux shell or environment examples, and the documentation does not address differences or considerations for Linux users.
Recommendations
  • Include explicit Linux shell examples (e.g., bash, zsh) and clarify that Azure CLI commands work cross-platform.
  • Provide examples using Linux-native tools (e.g., Azure Data Studio, or mention that sqlcmd is available on Linux).
  • When referencing PowerShell, also provide equivalent bash/CLI commands and note platform compatibility.
  • Add a section or callout for Linux users, highlighting any differences in authentication, tool installation, or environment setup.
  • Ensure that instructions do not assume use of Windows or PowerShell as the default, and present CLI examples before or alongside portal/PowerShell instructions.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-identity-based-connections-tutorial.md ...tions/functions-identity-based-connections-tutorial.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a clear Windows bias. It explicitly states that the tutorial 'currently supports C# class library functions on Windows specifically,' and references Azure Files as the default file system for Windows deployments. There are no equivalent Linux examples, nor is there guidance for Linux-specific scenarios or tools. The ARM template and portal instructions are generic, but the context and examples are tailored to Windows environments, with Linux considerations only briefly mentioned as caveats.
Recommendations
  • Add explicit Linux examples, including how to configure function apps on Linux plans (e.g., Consumption, Premium, Dedicated) and how to handle storage and identity scenarios specific to Linux.
  • Provide parity in instructions for Linux, such as how to avoid secrets in app settings for Linux-based function apps, and clarify any differences in deployment or configuration steps.
  • Mention Linux tools and patterns (e.g., Azure CLI, Bash scripting) alongside or before Windows/portal instructions, and provide sample commands.
  • Clearly state any limitations or differences for Linux up front, and link to relevant Linux documentation or workarounds.
  • Where features are Windows-only, provide alternative recommendations or timelines for Linux support.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-monitoring.md .../main/articles/azure-functions/functions-monitoring.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias. It references features and tools (such as built-in log streaming) that are not available or are limited on Linux, without always providing Linux alternatives or calling out Linux limitations up front. The order of presentation and examples tends to assume Windows/App Service as the default, and there are no explicit Linux command-line or tooling examples. Some features (like Performance Counters and log streaming) are described without clear Linux parity or alternatives.
Recommendations
  • Explicitly call out Linux limitations and provide alternative workflows or tools for Linux users where features are not available (e.g., for log streaming and performance counters).
  • Add Linux-specific examples or instructions, such as using Azure CLI, Bash, or cross-platform tools, especially in sections that discuss enabling features or accessing logs.
  • When describing features that are Windows-only or have limited Linux support, mention this early and provide links or guidance for Linux users.
  • Ensure that examples and instructions are balanced between Windows and Linux, or use cross-platform approaches by default.
  • Consider adding a comparison table or section summarizing feature parity and differences between Windows and Linux hosting plans for Azure Functions.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/scenario-custom-remote-mcp-server.md ...s/azure-functions/scenario-custom-remote-mcp-server.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation generally maintains cross-platform parity, but there are subtle signs of Windows bias. In the 'Connect to your remote MCP server' section, the Windows (PowerShell) script is presented after the Linux/macOS (bash) script, which is good, but the PowerShell script is more complex and detailed, and the documentation uses Windows-centric tools and patterns throughout (e.g., Visual Studio Code, Azurite, and Azure CLI, which are cross-platform but often associated with Windows). There are also references to pressing F1 and using the command palette, which are more familiar to Windows users. The PowerShell script is provided for Windows, but there is no explicit mention of WSL or Git Bash as alternatives for Windows users who prefer bash. There are no explicit Linux-only examples, and the documentation does not highlight Linux-specific workflows or tools.
Recommendations
  • Ensure that Linux/macOS and Windows examples are always presented with equal prominence and detail.
  • Explicitly mention that bash scripts can be run on Windows using WSL or Git Bash, not just on Linux/macOS.
  • Where possible, provide examples using native Linux tools or workflows, not just cross-platform tools that are more popular on Windows.
  • Consider adding a section or callout for common Linux-specific troubleshooting or environment setup steps.
  • Avoid assuming Visual Studio Code as the only editor; mention alternatives like Vim, Emacs, or JetBrains IDEs where appropriate.
  • Where keyboard shortcuts are given, clarify if they differ on Linux (e.g., Cmd vs Ctrl, or F1 behavior).
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-premium-plan.md ...ain/articles/azure-functions/functions-premium-plan.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates several forms of Windows bias. In command-line examples, both Azure CLI and Azure PowerShell are consistently provided, but there is a notable emphasis on PowerShell, a Windows-centric tool. In some sections (e.g., migration), only Windows migration is supported and documented, with Linux explicitly excluded. Throughout, Windows is often mentioned first (e.g., in region tables, OS requirements), and there is a lack of Linux-specific guidance or parity in examples. Additionally, Windows tools and patterns (like PowerShell) are given equal or greater prominence than cross-platform tools, and there are no Linux shell (bash) or scripting examples provided.
Recommendations
  • Ensure all command-line examples are clearly marked as cross-platform, and provide bash or shell script equivalents where possible, especially for Linux users.
  • When referencing PowerShell, clarify its cross-platform availability or provide alternatives (e.g., bash/Cloud Shell) for Linux users.
  • Avoid consistently listing Windows first in tables and descriptions; alternate or clarify that both OSes are equally supported where applicable.
  • For migration and other features not supported on Linux, provide clear guidance, workarounds, or timelines for Linux support.
  • Add Linux-specific notes, troubleshooting, and best practices to match the level of detail provided for Windows.
  • Review and balance the use of Windows-centric terminology and tools with Linux equivalents throughout the documentation.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-versions.md ...ob/main/articles/azure-functions/functions-versions.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows tools (Visual Studio, .csproj, .NET Framework) and workflows (Visual Studio project settings) before or instead of Linux equivalents. There are no explicit Linux-specific examples or instructions, and the only mention of Linux is in the context of pinning to a minor version, which refers the reader elsewhere. The focus on Visual Studio and .NET-centric workflows further centers Windows development patterns, with little parity for Linux users.
Recommendations
  • Add explicit Linux development examples, such as using Azure Functions Core Tools on Linux, including relevant shell commands.
  • Provide instructions for configuring runtime versions using Linux-native tools (e.g., Azure CLI, environment variables) and show these before or alongside Windows/Visual Studio instructions.
  • Include examples for non-.NET languages (e.g., Python, JavaScript) that are common on Linux, demonstrating how to set or migrate runtime versions.
  • Clarify any differences in workflow or configuration for Linux users, especially in sections that currently focus on Visual Studio or .csproj files.
  • Ensure that any references to 'how to' guides (such as pinning to a minor version) include both Windows and Linux instructions inline, not just via links.
GitHub Create Pull Request
← Previous Page 1 of 10 Next →