Document Details

Create First Function Azure Developer Cli
Home / Scan #41 / Create First Function Azure Developer Cli
Sad Tux - Windows bias detected
This page contains Windows bias

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
GitHub View on GitHub 📚 View on Microsoft Learn

Bias Analysis

Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally provides cross-platform instructions, but there are several areas where Windows-specific tools, shells, or patterns are given prominence or appear before Linux equivalents. PowerShell is treated as a first-class language, and Windows command-line (Cmd) and PowerShell examples are often shown before or alongside bash, sometimes with more detail. Some instructions and prerequisites reference Windows-specific paths or tools, and in a few places, Windows-centric terminology is used (e.g., 'command prompt').
Recommendations
  • Ensure that bash/Linux examples are always presented before or alongside Windows Cmd/PowerShell examples, not after.
  • Where possible, use neutral terms like 'terminal' instead of 'command prompt', or clarify with 'terminal or command prompt (Linux/macOS/Windows)'.
  • For PowerShell-specific instructions, ensure parity by providing bash/zsh/fish equivalents where appropriate, especially for scripting or environment variable manipulation.
  • Review all code blocks and tabs to ensure Linux/macOS users are not required to infer steps from Windows examples (e.g., activating Python venv, environment variable setting).
  • When referencing tools, clarify their cross-platform availability (e.g., Azurite, Azure Functions Core Tools) and provide installation links or instructions for Linux/macOS as well as Windows.
  • Avoid assuming Windows directory structures (e.g., .venv/scripts/activate vs .venv/bin/activate) without explicit cross-platform notes.
  • Consider adding a summary table or section at the start that clearly states all instructions are cross-platform, with explicit notes for any OS-specific differences.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2025-07-12 23:44 #41 cancelled Biased Biased
2025-07-12 00:58 #8 cancelled Clean Clean
2025-07-10 05:06 #7 processing Clean Clean
2025-07-09 23:22 #6 cancelled Clean Clean

Flagged Code Snippets

    azd init --template azure-functions-java-flex-consumption-azd -e flexquickstart-java 
    
    azd init --template functions-quickstart-powershell-azd -e flexquickstart-ps
    
    {
        "IsEncrypted": false,
        "Values": {
            "AzureWebJobsStorage": "UseDevelopmentStorage=true",
            "FUNCTIONS_WORKER_RUNTIME": "powershell",
            "FUNCTIONS_WORKER_RUNTIME_VERSION": "7.2"
        }
    }
    
py -m venv .venv
source .venv/scripts/activate

py -m venv .venv
.venv\scripts\activate

    for /f "tokens=*" %i in ('azd env get-value AZURE_FUNCTION_NAME') do set APP_NAME=%i
    func azure functionapp publish %APP_NAME% 
    
    SET APP_NAME=(azd env get-value AZURE_FUNCTION_NAME)
    func azure functionapp list-functions $APP_NAME --show-keys
    
    for /f "tokens=*" %i in ('azd env get-value AZURE_FUNCTION_NAME') do set APP_NAME=%i
    func azure functionapp list-functions %APP_NAME% --show-keys 
    
    for /f "tokens=*" %i in ('azd env get-value AZURE_FUNCTION_NAME') do set APP_NAME=%i
    func azure functionapp list-functions %APP_NAME% --show-keys 
    
    $APP_NAME = azd env get-value AZURE_FUNCTION_NAME
    func azure functionapp list-functions $APP_NAME --show-keys