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 751-775 of 1023 flagged pages
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-private-site-access.md ...zure-functions/functions-create-private-site-access.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions for creating a Windows Server virtual machine and referencing Windows-specific tooling (e.g., RDP via Bastion). There are no examples or guidance for creating or using a Linux VM, nor are Linux tools or patterns mentioned. The tutorial assumes the user will use a Windows VM for network access and function invocation, omitting Linux alternatives.
Recommendations
  • Add parallel instructions and screenshots for creating a Linux VM (e.g., Ubuntu) in the Azure portal.
  • Include guidance for connecting to a Linux VM via SSH using Azure Bastion, with relevant screenshots.
  • Mention Linux as an option when describing VM creation, and provide a table comparing Windows and Linux VM setup steps.
  • Reference Linux command-line tools (curl, wget) for invoking the Azure Function from the VM, in addition to browser-based access.
  • Ensure all steps that mention Windows-specific actions (such as RDP) also mention Linux equivalents (such as SSH).
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-manually-run-non-http.md ...les/azure-functions/functions-manually-run-non-http.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing the Azure portal and Visual Studio Code for manual function execution, both of which are commonly used on Windows. The instructions for obtaining the master key via Azure CLI are cross-platform, but there are no explicit Linux-specific examples or mentions of Linux tools (such as curl or wget) for making HTTP requests. The HTTP test tool is referenced generically, but no concrete Linux command-line examples are provided, and the workflow is described primarily in terms of portal interactions, which are more familiar to Windows users.
Recommendations
  • Add explicit Linux command-line examples using curl or wget to demonstrate how to manually trigger the function.
  • Include references to Linux-native tools (e.g., curl, HTTPie) alongside or before Windows tools.
  • Provide screenshots or terminal output examples from Linux environments.
  • Clarify that the Azure CLI commands work cross-platform and show sample usage in a Linux shell.
  • Balance portal-based instructions with command-line alternatives for users who prefer or require non-GUI workflows.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/manage-connections.md ...ob/main/articles/azure-functions/manage-connections.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows/.NET environments by providing code examples and tooling instructions primarily for C#/.NET (Windows-centric) and JavaScript, with no explicit mention or examples for Linux-specific tools, patterns, or environments. The SQL client section only references .NET libraries and configuration patterns typical of Windows deployments, omitting Linux-native database clients or configuration practices. There is no mention of Linux shell commands, environment variables, or deployment patterns that differ from Windows.
Recommendations
  • Add examples for Python and other languages commonly used on Linux, such as Python's requests library for HTTP clients and SQLAlchemy for database connections.
  • Include instructions or examples for configuring connection strings and application settings using Linux-native tools (e.g., environment variables, bash scripts, or configuration files like .env).
  • Reference Linux deployment patterns, such as using appsettings.json or environment variables, and clarify any differences from Windows configuration.
  • Mention Linux-native database clients (e.g., PostgreSQL's psycopg2, MySQL's mysqlclient) and provide examples for connection pooling and management.
  • Ensure parity in troubleshooting and monitoring instructions by referencing Linux-compatible tools (e.g., Azure CLI, shell scripts) alongside Windows tools.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/python-memory-profiler-reference.md ...es/azure-functions/python-memory-profiler-reference.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias in the local development setup instructions. Windows/PowerShell commands are presented first, and the use of 'py' for venv creation and '.venv\Scripts\Activate.ps1' for activation are Windows-specific, with Linux alternatives mentioned secondarily. The phrase 'Open a Windows PowerShell or any Linux shell as you prefer' also places Windows first. However, most of the content, including Python code and Azure Functions usage, is cross-platform.
Recommendations
  • Present Linux and Windows instructions side-by-side or in tabs, rather than listing Windows first.
  • Use neutral language such as 'Open a terminal (Windows PowerShell or Linux shell)' to avoid prioritizing Windows.
  • For commands, provide both Windows and Linux/macOS versions equally, and consider using cross-platform commands where possible.
  • Add explicit notes or sections for macOS users if relevant.
  • Where file paths are shown (e.g., <ProjectRoot>\HttpTriggerAsync\__init__.py), clarify that path separators differ on Linux/macOS (use /).
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-mcp.md ...ain/articles/azure-functions/functions-bindings-mcp.md
Medium Priority View Details →
Scanned: 2025-09-02 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides an example for retrieving the system key using the Azure CLI, which is cross-platform, but does not include any Linux- or macOS-specific shell examples (such as bash or zsh). There are no explicit Windows-only tools or PowerShell commands, but the absence of Linux/macOS terminal examples and the lack of explicit mention of Linux environments may make the documentation feel Windows-centric. Additionally, there is no mention of Linux-specific installation or troubleshooting steps, nor any explicit parity checks for Linux users.
Recommendations
  • Include explicit bash/zsh shell examples alongside Azure CLI commands, demonstrating usage in Linux/macOS terminals.
  • Mention that Azure CLI works on Windows, Linux, and macOS, and provide links to installation instructions for each OS.
  • If there are any OS-specific considerations (such as file paths, environment variables, or permissions), document them for both Windows and Linux/macOS.
  • Add troubleshooting notes or tips for common issues encountered on Linux (e.g., permissions, dependency installation, or differences in local development environments).
  • Ensure that all code snippets and instructions are validated on both Windows and Linux/macOS platforms.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-reference-python.md ...articles/azure-functions/functions-reference-python.md
Medium Priority View Details →
Scanned: 2025-09-01 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation is generally cross-platform and Linux-focused for hosting, but there are subtle Windows biases in the development and publishing workflow sections. Specifically, Windows is mentioned first or as the default in several places (e.g., 'command prompt', 'developing on Windows', 'use remote build when developing Python apps on Windows'), and there is a lack of explicit Linux shell examples (e.g., bash/zsh) in command snippets. The term 'command prompt' is ambiguous and can be interpreted as Windows-centric. Visual Studio Code is referenced as a primary tool, which is cross-platform, but no mention is made of Linux-specific editors or shell environments. The documentation does not provide PowerShell-specific examples, but the ordering and language suggest a slight preference for Windows development environments.
Recommendations
  • Replace ambiguous terms like 'command prompt' with 'terminal (Bash, zsh, or Command Prompt)' and provide explicit bash/zsh examples alongside any Windows-specific instructions.
  • When mentioning development environments, list Linux terminals and shells (e.g., Bash, zsh) before or alongside Windows Command Prompt to avoid 'windows_first' bias.
  • In publishing and build workflow sections, clarify that both Windows and Linux are supported for local development and publishing, and provide shell-agnostic or dual examples (e.g., both bash and cmd).
  • Highlight Linux-native editors (e.g., Vim, Emacs, GNOME Terminal) as alternatives to Visual Studio Code, or at least acknowledge their use.
  • Where remote build is recommended for Windows, also provide guidance for Linux users, ensuring parity in workflow descriptions.
  • Audit all command snippets to ensure they are not Windows-centric (e.g., avoid using only .cmd file extensions or Windows path separators).
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
Medium Priority View Details →
Scanned: 2025-08-27 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a subtle Windows bias by referencing Windows-centric tools and workflows (such as Visual Studio Code and Azurite) without explicitly addressing Linux alternatives or usage differences. The instructions for starting Azurite and running the function app use command palette steps that are most familiar to Windows users, and there is no mention of Linux-specific considerations or terminal commands. Additionally, the documentation assumes the use of Visual Studio Code, which, while cross-platform, is more commonly associated with Windows development environments.
Recommendations
  • Explicitly mention that Visual Studio Code and Azurite are cross-platform, and provide links or notes for Linux installation and usage.
  • Include terminal command alternatives for starting Azurite and running/debugging the function app (e.g., `azurite` and `func start`), especially for Linux users who may prefer CLI workflows.
  • Add a brief section or callout for Linux/macOS users highlighting any differences in setup, permissions, or file paths.
  • Ensure that all steps referencing the command palette or keyboard shortcuts clarify any OS-specific differences (e.g., <kbd>Ctrl</kbd> vs <kbd>Cmd</kbd> on macOS).
  • Where possible, provide bash/zsh shell commands alongside GUI instructions, especially for steps like updating configuration files or starting services.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-reference-java.md ...n/articles/azure-functions/functions-reference-java.md
Medium Priority View Details →
Scanned: 2025-08-22 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally maintains cross-platform parity, but there is a subtle Windows bias in the ordering and presentation of command-line examples. In several places, Windows (cmd) examples are presented alongside or before Bash, and PowerShell/CMD tabs are always present even when not strictly necessary. However, Linux-specific tools, patterns, or troubleshooting are not missing, and Linux is treated as a first-class citizen in most technical content.
Recommendations
  • Ensure that Bash (Linux/macOS) examples are always presented first or at least equally with Windows CMD/PowerShell examples, especially in tabbed code blocks.
  • Where possible, clarify that all CLI commands work identically on Linux, macOS, and Windows, and highlight any OS-specific differences.
  • Consider including explicit Linux/macOS troubleshooting tips or environment notes where relevant (e.g., JAVA_HOME setup, file path conventions).
  • Avoid defaulting to Windows-centric terminology such as 'command prompt' without mentioning 'terminal' or 'shell' for Linux/macOS users.
  • Audit the order of tool recommendations (e.g., Visual Studio Code, IntelliJ, Eclipse) to ensure no implicit prioritization of Windows-preferred tools.
  • Add a brief section or callout at the top confirming full Linux/macOS support for all development workflows described.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-reference.md ...b/main/articles/azure-functions/functions-reference.md
Medium Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias, primarily by listing Windows-centric tools such as Visual Studio before cross-platform or Linux-friendly alternatives, and by referencing Visual Studio (a Windows-first IDE) as the primary quickstart and deployment tool for C#. However, the documentation does provide parity for other languages and mentions cross-platform tools like Visual Studio Code and Azure CLI throughout. There are no PowerShell-heavy examples, and Linux is not excluded, but Windows tools are often mentioned first or more prominently.
Recommendations
  • Ensure that cross-platform tools (Visual Studio Code, Azure CLI, Maven, etc.) are listed before or alongside Windows-specific tools like Visual Studio, especially in introductory and quickstart sections.
  • Explicitly mention Linux and macOS compatibility where applicable, particularly when referencing the 'command prompt' or CLI-based workflows.
  • For C# and other languages where Visual Studio is highlighted, provide equal visibility to Visual Studio Code and CLI-based workflows, including links to Linux/macOS instructions where available.
  • Avoid using 'command prompt' as a generic term; specify 'terminal' or 'shell' to be inclusive of Linux/macOS users.
  • Where PowerShell is referenced, ensure that Bash or other shell equivalents are also mentioned if possible.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/how-to-create-function-azure-cli.md ...es/azure-functions/how-to-create-function-azure-cli.md
Medium Priority View Details →
Scanned: 2025-08-20 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally uses cross-platform command-line tools (Azure CLI, Azure Functions Core Tools) and avoids explicit Windows-only instructions. However, there is subtle Windows bias in the ordering and presentation of examples: in the Java section, PowerShell and Cmd examples are given alongside Bash, and Windows-specific command shells are mentioned before Bash. File path examples (e.g., '\src\main\java\com\fabrikam') use Windows-style backslashes. There is no explicit Linux example for certain steps, and Windows command-line environments are referenced more prominently than Linux equivalents.
Recommendations
  • In the Java section, present Bash examples before PowerShell and Cmd, or group all shell examples equally without implying priority.
  • When referencing file paths, use POSIX-style forward slashes or provide both Windows and Linux path formats.
  • Explicitly mention that all Azure CLI and Azure Functions Core Tools commands work on Linux, macOS, and Windows, and provide example terminal commands for both Bash and PowerShell/Cmd where appropriate.
  • Ensure that any references to command prompts or shells (e.g., 'terminal or command prompt') clarify that this includes Linux/macOS terminals, not just Windows Command Prompt.
  • If referencing tools like jq, clarify installation steps for both Windows and Linux, or link to cross-platform installation instructions.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-reference-python.md ...articles/azure-functions/functions-reference-python.md
Medium Priority View Details →
Scanned: 2025-08-20 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally maintains good cross-platform parity, but there are subtle signs of Windows bias. In particular, references to 'command prompt' and 'Terminal or command prompt' as development environments, and recommendations to use remote build when developing on Windows, suggest a Windows-first perspective. The documentation also mentions that Python is supported only on Linux-based hosting plans, but local development on Windows is possible. There are no explicit PowerShell-heavy examples, and Linux is well-represented in hosting and deployment sections. However, Linux CLI tools (like bash) are not mentioned, and Windows terminology (e.g., 'command prompt') is used preferentially.
Recommendations
  • Use neutral terminology such as 'terminal' or 'shell' instead of 'command prompt' to avoid Windows-centric language.
  • Explicitly mention both Windows and Linux/macOS development environments and tools (e.g., 'Command Prompt or Bash terminal') in all relevant sections.
  • Provide example commands for both Windows and Linux shells where applicable, especially in setup and deployment instructions.
  • Clarify that Azure Functions Core Tools and related workflows are fully supported on Linux/macOS, and link to any Linux/macOS-specific guidance if available.
  • When recommending remote or local build, explain the rationale for both Windows and Linux users, and avoid implying that Windows is the default or primary development environment.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-reference-python.md ...articles/azure-functions/functions-reference-python.md
Medium Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation is generally cross-platform and Linux-focused for hosting, but there is a subtle Windows bias in the development and publishing workflow sections. Windows tools and development on Windows are mentioned first or exclusively in some places, and recommendations for local development and build workflows are sometimes Windows-centric. However, Linux is clearly the only supported hosting environment, and most code and configuration examples are OS-agnostic.
Recommendations
  • When listing development options, avoid phrases like 'Terminal or command prompt' and instead use 'Terminal (Linux/macOS) or Command Prompt (Windows)' to clarify cross-platform support.
  • In the publishing section, avoid recommending remote build specifically for Windows users; instead, explain the pros and cons of remote vs. local build for all platforms.
  • Add explicit Linux/macOS CLI examples where appropriate (e.g., using bash/zsh instead of only generic or Windows-centric command syntax).
  • Where Visual Studio Code is mentioned, clarify that it is cross-platform and works on Linux/macOS as well as Windows.
  • Review all references to 'command prompt' and 'cmd' to ensure parity with bash/zsh/terminal instructions.
  • If mentioning Windows-specific behaviors (such as Python standard library installation), provide the equivalent Linux/macOS context immediately after or alongside.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-reference.md ...b/main/articles/azure-functions/functions-reference.md
Medium Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation exhibits a mild Windows bias, primarily by listing Windows-centric tools (Visual Studio) before cross-platform or Linux-native alternatives, especially in C# sections. Visual Studio is mentioned first for C# quickstarts and deployment, which can imply a Windows-first development workflow. However, the documentation does provide cross-platform alternatives (Visual Studio Code, Azure CLI, Maven, etc.) and does not omit Linux-compatible instructions. There are no PowerShell-heavy examples or missing Linux examples, but the ordering and tool emphasis can subtly prioritize Windows.
Recommendations
  • When listing development tools or quickstart options, alternate the order or explicitly mention cross-platform tools (e.g., Visual Studio Code, Azure CLI) before or alongside Windows-only tools like Visual Studio.
  • Clearly indicate which tools are cross-platform and which are Windows-only, especially in tool lists and quickstart sections.
  • Where possible, provide explicit Linux/macOS terminal instructions or screenshots alongside Windows/Visual Studio steps.
  • Consider adding a table or section summarizing tool compatibility across Windows, Linux, and macOS for each language.
  • Ensure that all references to 'command prompt' clarify that Bash/zsh (Linux/macOS) and Command Prompt/PowerShell (Windows) are supported equally.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-reference-java.md ...n/articles/azure-functions/functions-reference-java.md
Medium Priority View Details →
Scanned: 2025-08-18 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally maintains good cross-platform parity, but there are subtle signs of Windows bias. In command-line examples, both Bash and Windows CMD are provided, but CMD examples are always listed second, which is a positive sign for Linux parity. However, the documentation refers to 'command prompt' in the getting started section, which is a Windows-specific term, and does not mention Linux shells (e.g., Bash, Zsh) equivalently. There is also a lack of explicit mention of Linux-specific tools or troubleshooting steps, and some terminology (e.g., 'command prompt', 'Terminal') is inconsistent. All Azure CLI examples are provided for both Bash and CMD, but there are no PowerShell-specific examples, which is good. There are no Windows-only tools or patterns, but the documentation could be more explicit in addressing Linux users and their environments.
Recommendations
  • In the getting started section, replace 'command prompt' with 'terminal or command prompt' or explicitly mention both Windows and Linux shells (e.g., 'command prompt (Windows) or terminal (Linux/macOS)').
  • Wherever 'Terminal' is mentioned, clarify that it refers to Bash, Zsh, or other shells on Linux/macOS, and Command Prompt or PowerShell on Windows.
  • Add troubleshooting tips or notes specific to Linux environments, such as file permissions, environment variable configuration, or common issues with Maven/Java on Linux.
  • Ensure that any references to environment variables (e.g., JAVA_HOME) include Linux export syntax as well as Windows set syntax.
  • Consider including at least one explicit example of running or debugging on a Linux system, or referencing Linux-specific documentation where appropriate.
  • Audit for any other subtle terminology that may assume a Windows-first perspective, and rephrase for cross-platform inclusivity.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/dotnet-aspire-integration.md .../articles/azure-functions/dotnet-aspire-integration.md
Medium Priority View Details →
Scanned: 2025-08-12 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by providing Visual Studio (a Windows-centric IDE) instructions for tooling updates and omitting any explicit Linux or cross-platform development environment guidance. There are no examples or notes for Linux users regarding equivalent tools, commands, or workflows (e.g., VS Code, CLI usage, or emulator setup on Linux). All example instructions and environment setup steps implicitly assume a Windows/Visual Studio context.
Recommendations
  • Add explicit instructions for Linux and macOS users, including how to set up the development environment using VS Code or the .NET CLI.
  • Provide alternative steps for updating Azure Functions tools outside of Visual Studio (e.g., using the Azure Functions Core Tools CLI).
  • Mention cross-platform emulator options and how to configure or avoid conflicts on Linux/macOS.
  • Include notes or examples for common Linux development patterns, such as using terminal commands for project creation, dependency management, and running the emulator.
  • Clarify that .NET Aspire and Azure Functions development is supported on Windows, Linux, and macOS, and link to platform-specific setup guides where appropriate.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-private-site-access.md ...zure-functions/functions-create-private-site-access.md
Medium Priority View Details →
Scanned: 2025-08-12 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively guiding users to create a Windows Server virtual machine, with no mention of Linux alternatives. All VM creation steps, screenshots, and instructions are tailored for Windows Server, and there are no examples or guidance for deploying or accessing the function app from a Linux VM. This may lead Linux users to believe that only Windows is supported or recommended for this scenario.
Recommendations
  • Provide parallel instructions and screenshots for creating a Linux-based virtual machine (e.g., Ubuntu) alongside the Windows Server example.
  • Explicitly mention that either Windows or Linux VMs can be used for this scenario, and highlight any differences in setup or access.
  • Include a note or section on how to connect to and use a Linux VM via Azure Bastion, including SSH access instructions.
  • Where relevant, provide command-line examples (e.g., using curl or wget) for invoking the function from within a Linux VM.
  • Ensure that all steps referencing the VM (such as browser access or deployment) clarify that the process is similar for both Windows and Linux environments.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-reference.md ...b/main/articles/azure-functions/functions-reference.md
Medium Priority View Details →
Scanned: 2025-08-12 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias, primarily by listing Windows-centric tools (Visual Studio) first in several places, especially for C#. Visual Studio is a Windows-only IDE, and its mention precedes cross-platform or Linux-friendly tools like Visual Studio Code or command-line options. There are no explicit Linux-specific examples or tools highlighted, and the documentation does not provide parity in mentioning Linux-native workflows or editors. However, the use of Azure Functions Core Tools and Visual Studio Code (both cross-platform) is present, and PowerShell is only referenced in the context of the PowerShell language, not as a system shell.
Recommendations
  • When listing development tools or quickstart options, avoid always listing Visual Studio (Windows-only) first. Instead, either list cross-platform tools first (e.g., Visual Studio Code, Azure Functions Core Tools) or clarify platform compatibility.
  • Explicitly mention that Visual Studio Code and Azure Functions Core Tools are fully supported on Linux and macOS, and provide links or notes for Linux users.
  • Where 'command prompt' is mentioned, clarify that this refers to any terminal (e.g., Bash, zsh, PowerShell, Command Prompt) and provide Linux/macOS-specific terminal instructions or examples where appropriate.
  • Consider including a section or callout for Linux/macOS users, highlighting any differences or additional steps required for those platforms.
  • If possible, add examples or references to popular Linux editors (e.g., Vim, Emacs) or workflows, or at least acknowledge their use.
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
Medium Priority View Details →
Scanned: 2025-08-12 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Windows-centric tools and workflows (such as Visual Studio and .csproj configuration) before mentioning cross-platform or Linux-specific alternatives. In particular, the section on pinning to a specific minor version explicitly states that the process differs between Windows and Linux, but does not provide the Linux-specific instructions or examples. Additionally, the local development section focuses on Visual Studio (a primarily Windows tool) and only later mentions Visual Studio Code and Azure Functions Core Tools, which are cross-platform.
Recommendations
  • When mentioning that pinning to a specific minor version differs between Windows and Linux, provide explicit Linux instructions or examples alongside the Windows ones.
  • Balance the order of tool mentions: introduce cross-platform tools (like Azure Functions Core Tools and Visual Studio Code) before or alongside Windows-specific tools (like Visual Studio).
  • Wherever project file examples are given (such as .csproj for Visual Studio), consider also providing equivalent instructions or examples for non-Windows environments (such as command-line or VS Code workflows).
  • Ensure that all platform-specific differences are clearly documented with equal detail for both Windows and Linux users.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-azure-developer-cli.md ...functions/create-first-function-azure-developer-cli.md
Medium Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally provides cross-platform instructions, but there are subtle signs of Windows bias. In several places, Windows command-line (Cmd) instructions are listed before Linux/macOS equivalents, and PowerShell is given its own dedicated section with examples, even when not strictly necessary. However, Linux/macOS instructions are present and functional, and the use of 'terminal or command prompt' is inclusive. The documentation does not omit Linux examples, but the ordering and emphasis sometimes favor Windows tools and patterns.
Recommendations
  • When providing command examples for multiple platforms, consider listing Linux/macOS instructions first or side-by-side with Windows, rather than defaulting to Windows-first ordering.
  • Avoid giving PowerShell its own section unless it is truly necessary for the scenario; otherwise, group shell instructions by platform (e.g., Bash, Cmd, PowerShell) in a parallel structure.
  • Ensure that all references to 'terminal or command prompt' clarify that any shell (Bash, Zsh, etc.) is supported, not just Windows Command Prompt or PowerShell.
  • Where possible, use platform-agnostic commands or highlight differences only when strictly necessary.
  • Review the use of file paths and environment activation commands to ensure Linux and macOS users are not confused by Windows-centric syntax.
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
Medium Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias, primarily by listing Windows-centric tools (Visual Studio, PowerShell, Microsoft Edge Network Console) before cross-platform or Linux-native alternatives. Visual Studio, a Windows-first IDE, is consistently mentioned as the primary environment for C# development, with Visual Studio Code and command-line options listed after. In the HTTP test tools section, PowerShell and Microsoft Edge are highlighted before curl, a ubiquitous Linux tool. However, the documentation does acknowledge Linux and macOS support in most places and provides parity in instructions for Visual Studio Code and Core Tools.
Recommendations
  • When listing development environments, avoid always listing Visual Studio (Windows-only) first; consider listing cross-platform options (like Visual Studio Code and Core Tools) before or alongside Windows-only tools.
  • In tool recommendations (such as HTTP test tools), list cross-platform and Linux-native tools (e.g., curl, HTTPie) before or alongside Windows-specific tools like PowerShell and Microsoft Edge.
  • Where possible, provide explicit Linux/macOS command-line examples or notes, especially in sections referencing command prompts or terminals.
  • Highlight Linux/macOS support more prominently in introductory sections, not just in table descriptions.
  • Include links or references to Linux package managers or installation instructions for Core Tools and Azurite.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-bindings-expressions-patterns.md ...e-functions/functions-bindings-expressions-patterns.md
Medium Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page focuses exclusively on C# and .NET examples, with all code samples and configuration references tailored to those environments. There is no mention of platform-specific tools, but the absence of any Linux- or cross-platform-specific instructions, shell commands, or examples (such as Bash, Linux file paths, or environment variable handling) creates an implicit Windows/.NET-first bias. Additionally, the only mention of local development references 'local.settings.json', which is not explained for Linux environments.
Recommendations
  • Add examples using other languages and platforms, such as Python or JavaScript, and demonstrate how binding expressions work in those environments.
  • Include instructions or notes on how to manage app settings and environment variables in Linux/macOS environments, such as using Bash or exporting variables.
  • Provide parity in code samples by including both Windows (PowerShell/C#) and Linux (Bash/Python/JavaScript) equivalents where applicable.
  • Clarify that 'local.settings.json' is used cross-platform, and provide guidance for editing and managing it on Linux/macOS.
  • Where file paths or environment-specific details are mentioned, include both Windows and Linux/macOS conventions.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-infrastructure-as-code.md ...es/azure-functions/functions-infrastructure-as-code.md
Medium Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Windows and Linux examples for most ARM/Bicep template scenarios, using tabbed sections for parity. However, in several key areas, Windows is presented first (e.g., in hosting plan and function app resource definitions), and PowerShell is the only scripting/deployment example shown in the 'Deploy using PowerShell' section, with no Bash or Linux-native shell equivalents. There are also more references to Windows-specific settings and behaviors, and some sample links default to Windows Consumption plans.
Recommendations
  • Alternate the order of Windows and Linux examples in tabbed sections, or present Linux first in some cases to balance visibility.
  • Add Bash/Azure CLI script examples for deployment (especially in the 'Deploy using PowerShell' section) to support Linux users.
  • Ensure that all sample links and references are available for both Windows and Linux, and not defaulting to Windows plans.
  • Where Windows-specific settings are discussed, ensure equivalent Linux settings are equally described and linked.
  • In summary tables and introductory text, avoid language that implies Windows is the default or primary platform.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-vs-code-java.md .../azure-functions/create-first-function-vs-code-java.md
Medium Priority View Details →
Scanned: 2025-08-10 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation does not provide any explicit Windows-only commands or tools, but it implicitly assumes a Windows environment by omitting any mention of Linux or macOS-specific steps, shell commands, or terminal usage. All instructions are given in a way that is platform-neutral but lack parity for Linux users (e.g., no mention of using bash, Linux file paths, or terminal commands). There is also a subtle 'windows_first' bias in the absence of Linux-specific guidance, which may leave Linux users uncertain about environment setup or command usage.
Recommendations
  • Add explicit instructions or notes for Linux and macOS users, such as how to open the terminal, run commands, or install dependencies.
  • Include examples of file paths and commands in both Windows and Linux/macOS formats where relevant.
  • Mention any platform-specific prerequisites or troubleshooting steps (e.g., JAVA_HOME setup, permissions).
  • Ensure that screenshots or UI references are not Windows-centric, or provide alternatives for other operating systems.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-infrastructure-as-code.md ...es/azure-functions/functions-infrastructure-as-code.md
Medium Priority View Details →
Scanned: 2025-08-10 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally provides both Windows and Linux examples for ARM/Bicep templates and application settings, often using tabbed sections. However, in several key sections, Windows examples are presented before Linux equivalents ("windows_first"), and PowerShell is the only scripting language shown for deployment automation ("powershell_heavy"). There are no CLI or Bash examples for Linux users in the deployment automation section. The documentation does not appear to omit Linux-specific information or tools, but the ordering and scripting language choices may give the impression of a Windows-centric approach.
Recommendations
  • Alternate the order of Windows and Linux examples in tabbed sections, or default to the user's platform when possible.
  • Provide equivalent Azure CLI/Bash examples alongside PowerShell for deployment automation, especially in the 'Deploy your template' section.
  • In sections where both Windows and Linux are supported, clarify that both platforms are equally supported and highlight any differences up front.
  • Where possible, use cross-platform language (e.g., 'Azure CLI' instead of 'PowerShell') as the primary example, or provide both.
  • Ensure that all references to tools, commands, and scripts are available and demonstrated for both Windows and Linux environments.
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
Medium Priority View Details →
Scanned: 2025-08-10 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally aims for cross-platform parity, but there is a subtle Windows bias. Visual Studio (a Windows-only tool) is listed first and described in detail for C# development, while Linux/macOS options (like Visual Studio Code and command line) are presented after. Some instructions and examples, such as changing ports in Visual Studio, are specific to Windows workflows. In the HTTP test tools section, PowerShell and Microsoft Edge (both Windows-centric) are listed before curl, a ubiquitous cross-platform tool. There are no explicit Linux-only examples or tools highlighted, and Linux/macOS users are not given equal prominence in tool ordering or example specificity.
Recommendations
  • In each language section, list cross-platform tools (like Visual Studio Code and command line) before Windows-only tools such as Visual Studio.
  • When describing environment-specific instructions (e.g., changing ports), provide equivalent steps for Linux/macOS users or clarify if a step is Windows-only.
  • In tool lists (such as HTTP test tools), list cross-platform tools (like curl) before Windows-specific tools (like PowerShell or Microsoft Edge).
  • Explicitly mention and provide links to Linux/macOS-specific guides or troubleshooting where relevant.
  • Where possible, add Linux/macOS screenshots or terminal commands alongside Windows examples to reinforce parity.
GitHub Create Pull Request
← Previous Page 31 of 41 Next →