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 676-700 of 1023 flagged pages
Azure Functions
Azure Functions runtime versions overview
...ob/main/articles/azure-functions/functions-versions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias in several areas. Instructions and examples for creating and managing Azure Functions apps reference Windows tools (Visual Studio, Visual Studio Code) and workflows before mentioning cross-platform or Linux alternatives. There are no explicit Linux-specific examples or instructions, especially in sections discussing runtime version pinning and local development. The documentation assumes familiarity with Windows development environments and omits parity for Linux users.
Recommendations
- Add explicit Linux examples and instructions for tasks such as pinning runtime versions, including command-line steps using Azure Functions Core Tools on Linux.
- Include references to Linux package managers (e.g., apt, yum) for installing Azure Functions Core Tools, alongside Windows installation instructions.
- Provide parity in local development sections by describing workflows for popular Linux editors (e.g., VS Code on Linux, Vim, etc.) and terminal usage.
- Ensure that any references to Visual Studio or Windows-specific tooling are matched with equivalent Linux or cross-platform alternatives, and present them side-by-side or in a neutral order.
- Clarify when instructions are platform-specific and offer alternatives for both Windows and Linux users.
Create Pull Request
Azure Functions
Manage connections in Azure Functions
...ob/main/articles/azure-functions/manage-connections.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses primarily on .NET/C# examples and tools, which are most commonly associated with Windows environments. There is a lack of explicit Linux-specific guidance, such as examples using Linux shell tools, environment variables, or configuration patterns. The instructions for project setup reference .NET SDK and project files, which are Windows-centric, and there are no mentions of Linux equivalents or cross-platform considerations. No PowerShell-specific bias is present, but the overall pattern is Windows/.NET-first, with limited parity for Linux users.
Recommendations
- Include explicit Linux shell (bash) examples for environment variable configuration and client instantiation.
- Add instructions for installing and using .NET SDK on Linux, or mention cross-platform compatibility.
- Provide guidance for managing connection strings and app settings using Linux tools (e.g., Azure CLI on bash).
- Clarify that the patterns and recommendations apply equally to Linux-hosted Azure Functions, and highlight any platform-specific caveats.
- Consider adding examples for Python (a popular cross-platform language) to improve parity.
Azure Functions
Migrate AWS Lambda workloads to Azure Functions
...ons/migration/migrate-aws-lambda-to-azure-functions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows-centric tools and workflows, such as Visual Studio Code, Azure Functions Core Tools, and Azure CLI, without providing explicit Linux or cross-platform alternatives or examples. Deployment, local development, and troubleshooting instructions focus on Windows-friendly tools and do not mention Linux-specific patterns, package managers, or shell environments. There are no explicit Linux shell (bash) or Linux-native tool examples, and PowerShell is referenced as a supported language for Azure Functions, but not for AWS Lambda. The documentation assumes the use of Visual Studio Code and GitHub Copilot, which are available on Linux but are more commonly associated with Windows workflows.
Recommendations
- Add explicit Linux shell (bash) examples for deployment and local development, such as using Azure CLI or Azure Functions Core Tools from a Linux terminal.
- Mention Linux package managers (apt, yum, etc.) for installing Azure Functions Core Tools and other dependencies.
- Clarify cross-platform compatibility for tools like Visual Studio Code, Azure CLI, and Azure Functions Core Tools, and provide installation instructions for Linux.
- Include troubleshooting steps and diagnostic tool usage for Linux environments, such as log file locations and common Linux-specific issues.
- Provide parity in code samples and workflow instructions by referencing both Windows and Linux environments where applicable.
- Avoid assuming Visual Studio Code as the only development environment; mention alternatives like Vim, Emacs, or JetBrains IDEs, especially for Linux users.
Azure Functions
Durable entities - Azure Functions
.../azure-functions/durable/durable-functions-entities.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page does not show explicit Windows bias in terms of examples or tooling (e.g., PowerShell, Windows-specific tools, or CLI patterns). However, there is a subtle 'windows_first' bias: .NET (C#) examples and explanations are presented first and in greater detail, including advanced features like class-based syntax and entity coordination. These .NET examples implicitly assume a Windows-centric development environment, as .NET historically has stronger ties to Windows. Linux-specific considerations, CLI commands, or platform differences are not discussed. There are no PowerShell examples, and no explicit mention of Windows-only tools, but the lack of parity in depth and advanced features for JavaScript and Python (which are more cross-platform) is notable. Linux users may find the documentation less comprehensive for their preferred languages and environments.
Recommendations
- Provide equal depth and advanced examples for JavaScript and Python, including entity coordination and locking scenarios.
- Add notes or sections discussing platform differences, such as running Durable Functions on Linux vs. Windows, and any implications for .NET, JavaScript, or Python.
- Include CLI-based examples (e.g., Azure CLI, Bash) for common tasks, especially for Linux users.
- Ensure that links and 'Next steps' are not .NET-centric; offer developer guides for JavaScript and Python durable entities.
- Explicitly state that all examples are cross-platform unless otherwise noted, and clarify any platform-specific limitations.
Azure Functions
Configure Durable Functions app with managed identity
...urable/durable-functions-configure-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing development environments and tools primarily associated with Windows (Visual Studio, Visual Studio Code, Azure CLI) and omitting explicit Linux/macOS equivalents or examples. The instructions for local development and authentication focus on Microsoft-centric tools and user contexts, with no mention of Linux-specific authentication patterns, environment variable management, or alternative editors. There are no shell (bash/zsh) or Linux-specific configuration examples, and screenshots and UI instructions are tailored to the Azure portal, which is platform-agnostic but the developer context is implicitly Windows-centric.
Recommendations
- Add explicit Linux/macOS examples for local development, such as using environment variables, configuration files, or authentication via Azure CLI on Linux.
- Include instructions for setting up Durable Functions projects using common Linux tools and editors (e.g., VS Code on Linux, JetBrains Rider, or command-line workflows).
- Provide bash/zsh shell command examples for authentication and configuration alongside PowerShell or Windows-centric instructions.
- Clarify that Azure CLI and VS Code are cross-platform, and provide steps for Linux users where workflows differ (e.g., file paths, environment variable management).
- Mention how to assign RBAC roles using Azure CLI or Azure Portal from Linux/macOS, and provide command-line examples.
- Ensure screenshots and UI instructions are supplemented with CLI alternatives for users who prefer or require non-GUI workflows.
Azure Functions
Build a scalable web API using Azure Functions
...functions/create-first-function-azure-developer-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides cross-platform instructions and examples for all major languages, but there are several instances of Windows bias. Windows-specific command shells (Cmd, PowerShell) are presented alongside bash, sometimes with Windows variants listed before Linux/macOS. PowerShell is treated as a first-class language option, and Windows-specific instructions (such as activating Python venv) are given in multiple tabs. However, Linux/macOS instructions are present and generally complete, and most tooling (azd, func, curl) is cross-platform.
Recommendations
- Present Linux/macOS instructions before Windows instructions where possible, or group them together with equal prominence.
- Ensure that bash examples are clearly marked as suitable for both Linux and macOS, and that Windows bash instructions are not conflated with native Linux usage.
- Add explicit notes about cross-platform compatibility for all CLI tools (azd, func, curl) to reassure Linux users.
- Where PowerShell is shown as a language, clarify its cross-platform availability and provide guidance for Linux users who may wish to use PowerShell Core.
- Review all command examples for unnecessary Windows-centric phrasing (e.g., 'command prompt') and use neutral terms like 'terminal' where possible.
- Consider adding troubleshooting notes for common Linux/macOS issues (e.g., file permissions, path separators) to further improve parity.
Azure Functions
Versioning in Durable Functions - Azure
...zure-functions/durable/durable-functions-versioning.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides code examples in C#, PowerShell, and Java, but omits Linux-native scripting languages such as Bash or Python. PowerShell, which is primarily associated with Windows environments, is given equal prominence to C# and Java, despite its limited usage on Linux. There are no examples or guidance tailored to Linux command-line tools or deployment patterns, and Windows-centric concepts (such as PowerShell and deployment slots) are mentioned without Linux-specific alternatives or parity.
Recommendations
- Add Linux-native scripting examples, such as Bash or Python, alongside PowerShell for orchestration scenarios.
- Include guidance or examples for Linux deployment patterns, such as using containers, systemd, or Linux-native automation tools.
- Clarify the cross-platform availability of features like deployment slots, and mention any Linux-specific considerations or alternatives.
- Where Windows-specific tools or terminology are used (e.g., PowerShell), provide Linux equivalents or note platform differences.
- Consider reordering examples so that Windows and Linux approaches are presented with equal prominence, or alternate their order.
Azure Functions
Durable Functions packages
.../azure-functions/durable/durable-functions-packages.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page presents .NET (a Windows-centric technology) as the primary runtime, with detailed package instructions for .NET in-process and .NET isolated projects before mentioning other languages. PowerShell, another Windows-focused technology, is given special attention with a dedicated note and migration guidance. There are no explicit Linux-specific examples, tools, or instructions, and the documentation assumes familiarity with Windows development patterns (e.g., referencing .csproj files, NuGet packages) before mentioning cross-platform alternatives.
Recommendations
- Add explicit instructions and examples for Linux/macOS environments, such as how to install and reference packages using cross-platform tools (e.g., CLI commands for npm, pip, Maven).
- Include parity in example order: present Node.js, Python, and Java SDKs before or alongside .NET and PowerShell to avoid Windows-first impression.
- Provide guidance for non-Windows users, such as how to manage dependencies and configuration files on Linux/macOS.
- Balance PowerShell coverage with Bash or other shell examples for scripting Durable Functions on Linux.
- Clarify that .NET and PowerShell are cross-platform, but acknowledge their historical Windows bias and offer tips for non-Windows environments.
Azure Functions
Choosing an orchestration framework
...rable-task-scheduler/choose-orchestration-framework.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by listing PowerShell as a primary language option for Durable Functions quickstarts, and by referencing .NET and PowerShell examples before Linux-native equivalents. There is no explicit mention of Linux-specific tools, nor are Linux development patterns (such as Bash scripting or Linux CLI) highlighted. The quickstart and sample tables include PowerShell alongside other languages, but do not provide parity for Linux shell scripting or highlight Linux-first development experiences.
Recommendations
- Add Linux/Bash shell quickstart and sample options alongside PowerShell, or clarify cross-platform support for scripting.
- Explicitly mention Linux development environments and tools (e.g., Bash, Linux CLI) in quickstart and sample tables.
- Ensure examples and instructions are provided for both Windows and Linux platforms, including any OS-specific setup steps.
- Avoid listing Windows-centric tools (e.g., PowerShell) before Linux equivalents unless there is a technical reason; consider alphabetical or platform-neutral ordering.
- Include notes or sections on developing and deploying Durable Functions and Durable Task SDKs from Linux environments, including common patterns and troubleshooting.
Azure Functions
Event-driven Scaling in Azure Functions
.../main/articles/azure-functions/event-driven-scaling.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias. In the section on limiting scale-out, both Azure CLI and Azure PowerShell examples are provided, but PowerShell is presented as a first-class option, which is primarily a Windows tool. Additionally, in the scale-in behaviors section, a specific note is made for 'apps running on Windows in a Consumption plan', with no equivalent mention for Linux. There are no Linux-specific examples, nor is Bash or shell scripting referenced. The documentation does not mention Linux tools or patterns, and Windows is referenced explicitly in at least one scaling behavior note.
Recommendations
- Add explicit Linux/Bash examples alongside PowerShell, especially for configuration tasks.
- Clarify whether scale-in behaviors and drain mode apply differently to Linux-hosted apps, or explicitly state parity.
- Avoid referencing Windows-specific behaviors without noting Linux equivalents or differences.
- Where PowerShell is shown, provide equivalent Bash/Azure CLI examples and indicate cross-platform applicability.
- Review and update documentation to ensure Linux hosting scenarios are equally represented and described.
Azure Functions
Azure SQL input binding for Functions
.../azure-functions/functions-bindings-azure-sql-input.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for multiple languages, including PowerShell, which is primarily a Windows-centric technology. PowerShell examples are given equal prominence to Python, Java, and JavaScript, but there are no explicit Linux shell (e.g., Bash) examples or references to Linux-specific tooling or patterns. The documentation references local.settings.json for local development, which is cross-platform, but the inclusion of PowerShell as a primary example and the lack of Linux shell alternatives indicates a mild Windows bias. There are no explicit references to Windows-only tools, but the presence of PowerShell and absence of Linux shell scripting is notable.
Recommendations
- Add Bash or other Linux shell examples alongside PowerShell for scripting scenarios.
- Explicitly mention cross-platform compatibility for local.settings.json and other configuration files.
- Where PowerShell is referenced, note that equivalent functionality is available via Bash or other shells on Linux.
- Consider including instructions or code samples for Linux-based development environments, especially for local testing and deployment.
Azure Functions
Azure SQL trigger for Functions
...zure-functions/functions-bindings-azure-sql-trigger.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page exhibits mild Windows bias by referencing Windows-centric SQL tooling (SQL Server Management Studio) before cross-platform or Linux-friendly alternatives (Visual Studio Code, Azure Data Studio). The order of tool listing and the prominence of SSMS may suggest a Windows-first approach. However, example code and configuration instructions are generally cross-platform and do not rely on Windows-specific technologies or PowerShell-heavy patterns. There are no missing Linux examples, and the documentation does not use Windows-only tools for required steps.
Recommendations
- List cross-platform tools (Visual Studio Code, Azure Data Studio) before Windows-only tools (SQL Server Management Studio) when describing how to run SQL queries.
- Explicitly mention that all SQL setup steps can be performed on Linux, macOS, or Windows, and provide links to installation guides for cross-platform tools.
- Where possible, add notes or examples for using CLI tools (such as sqlcmd) that are available on Linux and macOS, in addition to GUI tools.
- Review other sections for implicit assumptions about Windows environments (such as references to local.settings.json usage) and clarify that these steps are platform-agnostic.
Azure Functions
Model context protocol bindings for Azure Functions
...ain/articles/azure-functions/functions-bindings-mcp.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by exclusively providing an Azure CLI example for retrieving the system key, without offering a Linux shell or cross-platform alternative. There is also a reference to Azure Functions Core Tools for local development, but no explicit mention of Linux-specific installation or usage instructions, nor any PowerShell-heavy content. The documentation does not provide Linux-specific examples or parity for key retrieval or local development.
Recommendations
- Provide explicit Linux/macOS shell examples for retrieving the system key (e.g., using curl or bash scripts) alongside Azure CLI.
- Clarify that Azure Functions Core Tools can be installed and used on Linux/macOS, and provide installation instructions or links for those platforms.
- Ensure that all command-line examples are cross-platform or offer alternatives for both Windows and Linux users.
- Avoid assuming Visual Studio Code or other Windows-centric tooling; mention alternatives or note cross-platform compatibility.
Azure Functions
Azure OpenAI assistant post input binding for Azure Functions
...tions/functions-bindings-openai-assistantpost-input.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation provides explicit, detailed examples for PowerShell, including both code and configuration file samples, while not offering equivalent examples for Linux shell environments (e.g., Bash). The PowerShell example is the only one to include a function.json configuration file and specific instructions, suggesting a bias toward Windows tooling and workflows. There is no mention of Linux-specific tools, shell scripts, or parity in configuration instructions for non-Windows environments.
Recommendations
- Add equivalent Linux/Bash shell examples alongside PowerShell, including sample scripts and configuration usage.
- Provide instructions for creating and managing function.json files in Linux environments, noting any differences or considerations.
- Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux users in setup and usage sections.
- Ensure that examples for configuration and code are available for both PowerShell and Bash (or other common Linux shells) to avoid Windows-centric bias.
Azure Functions
Azure OpenAI Semantic Search Input Binding for Azure Functions
...ions/functions-bindings-openai-semanticsearch-input.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation provides code examples for multiple languages, including C#, Java, JavaScript, TypeScript, Python, and PowerShell. However, PowerShell is the only shell scripting example provided, with no equivalent Bash or Linux shell example. The configuration section for PowerShell is detailed, referencing function.json and run.ps1, which are Windows/PowerShell-centric tools. There is no mention of Linux shell scripting, Bash, or cross-platform command-line usage, which may disadvantage Linux users or those using non-Windows environments.
Recommendations
- Add equivalent Bash or Linux shell scripting examples alongside PowerShell examples to ensure parity for Linux users.
- Include notes or examples for configuring and running Azure Functions using Linux-native tools (e.g., Bash, zsh) where applicable.
- Clarify that function.json and related configuration files are cross-platform, and provide guidance for Linux/macOS environments.
- Where PowerShell is referenced, explicitly mention alternatives for Linux/macOS users, such as Bash scripts or Azure CLI commands.
- Ensure that any references to Windows-specific tools or patterns are balanced with Linux equivalents, and avoid assuming PowerShell as the default shell.
Azure Functions
Azure Functions SignalR Service bindings
.../azure-functions/functions-bindings-signalr-service.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing configuration patterns and environment variable syntax that are Windows-centric (e.g., double underscore '__' separators), and only mentioning the need to replace '__' with ':' for certain tools, which is a workaround for Linux/macOS environments. There are no explicit Linux or cross-platform examples for environment variable configuration, nor are Linux-specific tools or shell commands referenced. The documentation also lacks explicit parity in local development instructions for Linux users.
Recommendations
- Provide explicit Linux/macOS examples for environment variable configuration, including shell syntax (e.g., export statements) and file formats.
- Clarify how to set environment variables for both Windows (using PowerShell/cmd) and Linux/macOS (using bash/zsh), especially in local development scenarios.
- Include cross-platform instructions for using local.settings.json, Azure App Configuration, and Key Vault, highlighting differences in naming conventions and access methods.
- Add references to Linux-compatible tools and workflows for Azure Functions development, such as Azure CLI usage in bash.
- Ensure that all configuration examples are presented for both Windows and Linux/macOS environments, or use platform-agnostic formats where possible.
Azure Functions
Enable private site access to Azure Functions
...zure-functions/functions-create-private-site-access.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server as the example operating system for the virtual machine setup, with no mention of Linux alternatives. All screenshots and instructions for VM creation reference Windows Server, and there are no Linux VM creation steps or examples. The tutorial does not provide parity for Linux users, who may wish to use Ubuntu or other Linux distributions in Azure. Additionally, the quickstart links for function creation prioritize Visual Studio and Visual Studio Code, which are more commonly used on Windows, with Linux-friendly CLI and Maven options listed last.
Recommendations
- Include instructions and screenshots for creating a Linux-based VM (e.g., Ubuntu) alongside the Windows Server example.
- Explicitly mention that either Windows or Linux VMs can be used for the scenario, and provide guidance for both.
- Reorder or balance quickstart links to give equal prominence to Linux-friendly tools (e.g., Azure CLI, Maven) and IDEs.
- Where VM OS selection is discussed, clarify that the choice depends on user preference and provide pros/cons or considerations for each.
- Add troubleshooting notes or tips relevant to Linux users (e.g., SSH access, package installation) when accessing the VM via Bastion.
Azure Functions
Use GitHub Actions to make code updates in Azure Functions
...les/azure-functions/functions-how-to-github-actions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by consistently listing Windows options before Linux in tabbed examples and instructions, and by providing PowerShell-specific examples (which are inherently Windows-centric) while Linux shell equivalents are not emphasized. However, Linux examples and templates are present for all supported languages, and the documentation does not omit Linux instructions. The Azure CLI, which is cross-platform, is recommended for command-line operations.
Recommendations
- Alternate the order of Windows and Linux tabs/examples so Linux is not always second.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Where PowerShell is referenced, provide equivalent Bash or shell examples for Linux users.
- Add notes or callouts for Linux-specific considerations (e.g., file permissions, environment variables) where relevant.
- Ensure that screenshots and UI instructions do not assume a Windows environment unless necessary.
Azure Functions
Manually run a non HTTP-triggered Azure Functions
...les/azure-functions/functions-manually-run-non-http.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page shows a Windows bias by referencing the Azure portal and Visual Studio Code as primary tools, which are more commonly used on Windows. There are no explicit Linux-specific instructions, examples, or mentions of Linux command-line tools (such as curl or wget) for making HTTP requests. The Azure CLI example is cross-platform, but no Linux shell example is provided for sending the HTTP request, and the documentation does not mention Linux-specific considerations or alternatives to the Azure portal.
Recommendations
- Add explicit Linux shell examples (e.g., using curl or wget) for sending the HTTP POST request to manually run the function.
- Mention Linux-friendly editors and tools (such as VS Code on Linux, or alternatives like Vim/Emacs) for local development and testing.
- Clarify that the Azure CLI commands work on Linux, macOS, and Windows, and provide sample terminal commands for Linux users.
- Include screenshots or instructions for accessing logs and keys using Linux tools or terminal commands, not just the Azure portal.
- Add a section or note on Linux-specific considerations, such as environment setup, authentication, or troubleshooting.
Azure Functions
Memory profiling of Python apps in Azure Functions
...es/azure-functions/python-memory-profiler-reference.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias in the local development setup instructions. Windows PowerShell is mentioned first, and Windows-specific commands (such as 'py -m venv .venv' and '.venv\Scripts\Activate.ps1') are listed before their Linux equivalents. The phrase 'Open a Windows PowerShell or any Linux shell as you prefer' places Windows first, and the example output uses Windows-style paths (e.g., '<ProjectRoot>\HttpTriggerAsync\__init__.py'). However, Linux alternatives are provided for all steps, and the rest of the documentation is platform-neutral.
Recommendations
- Present Linux and Windows instructions side-by-side or in separate tabs, rather than listing Windows first.
- Use platform-neutral language, e.g., 'Open a terminal (PowerShell, Command Prompt, or Linux shell)'.
- Show both Windows and Linux path formats in example outputs, or clarify that the output may differ by platform.
- Consider starting with Linux commands in at least one example to balance representation.
- Explicitly state that all steps apply equally to macOS, and provide macOS-specific commands if they differ.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples and links for multiple programming languages, including PowerShell, which is primarily a Windows-centric technology. PowerShell is given equal footing as a development language for Azure Functions, and its presence throughout the documentation (with dedicated tutorials and samples) may indicate a Windows bias. However, the documentation does not exclusively use Windows tools or patterns, and most examples are generic or cloud-native. There is no explicit mention of Windows-only tools, nor are Windows instructions given before Linux equivalents. The documentation does not provide OS-specific examples (e.g., CLI commands, file paths, deployment instructions) that would further indicate Windows bias.
Recommendations
- Clarify PowerShell's cross-platform capabilities, noting that it is available on Linux and macOS as well as Windows.
- Where PowerShell is presented, offer alternative shell examples (e.g., Bash) for Linux users, especially in sections involving scripting or automation.
- Add explicit notes or links to Linux/macOS setup guides if any steps differ from Windows, particularly for local development or deployment.
- Ensure that any references to development tools (such as Visual Studio Code) include instructions for both Windows and Linux environments.
- If possible, include Bash or other Linux shell examples alongside PowerShell in relevant sections to improve parity.
Azure Functions
IP addresses in Azure Functions
...ocs/blob/main/articles/azure-functions/ip-addresses.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides command-line examples for Azure CLI, Azure PowerShell, and the Azure portal. PowerShell examples are given equal prominence to CLI, and the use of PowerShell (a Windows-centric tool) is explicit. There is no mention of Linux-specific tools or shell environments (e.g., Bash), nor are there examples tailored for Linux users. The documentation assumes familiarity with PowerShell and does not clarify cross-platform usage for CLI commands. The order of examples sometimes places PowerShell before or alongside CLI, but never provides Linux-specific context.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash shell examples where relevant.
- Clarify that PowerShell examples are primarily for Windows users, and suggest alternatives for Linux/macOS users.
- Add notes or tabs for Linux-specific tools or commands (e.g., using curl, dig, or jq for JSON parsing).
- Ensure that CLI examples are presented before PowerShell, or provide parity in example ordering.
- Include guidance on installing and using Azure CLI on Linux, and reference common Linux shell environments.
Azure Functions
Durable Functions packages
.../azure-functions/durable/durable-functions-packages.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page presents .NET (in-process and isolated) as the primary runtime, with detailed package instructions and storage provider information, before mentioning other languages. PowerShell is explicitly called out with a dedicated note and migration guidance, while Linux-specific patterns, package management, or examples are absent. There is no mention of Linux tools, nor are Linux-specific instructions or parity considerations discussed.
Recommendations
- Add explicit Linux instructions or examples for package installation and configuration, especially for .NET users (e.g., using CLI tools on Linux).
- Include parity notes for Linux users, such as differences in file paths, environment setup, or package management.
- Balance PowerShell coverage with equivalent Bash or shell scripting guidance for Linux users.
- Ensure that examples and instructions for all supported languages are presented with equal prominence, not prioritizing Windows-centric runtimes.
- Mention cross-platform compatibility and provide troubleshooting tips for Linux environments where relevant.
Azure Functions
Build a scalable web API using Azure Functions
...functions/create-first-function-azure-developer-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples and instructions for both Windows and Linux/macOS environments, but Windows-specific instructions (Cmd, PowerShell) are often listed before Linux equivalents, and PowerShell is given its own language pivot and tab. In some places, Windows command shells (Cmd, PowerShell) are described in more detail than Linux/bash, and PowerShell is treated as a first-class language option. However, Linux/bash instructions are present and not missing.
Recommendations
- Ensure Linux/bash instructions are listed before or alongside Windows equivalents, not after.
- Provide equal detail and explanation for Linux/bash commands as for Windows/PowerShell/Cmd.
- Avoid treating PowerShell as a primary or default language unless justified by user data.
- Where possible, use cross-platform commands and tools (e.g., bash, curl) as the default, with Windows-specific alternatives in side notes or tabs.
- Explicitly state cross-platform compatibility for all CLI commands and tools.
- Review the order of tabs and pivots to avoid implicit prioritization of Windows tools.
Azure Functions
Enable private site access to Azure Functions
...zure-functions/functions-create-private-site-access.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively providing instructions and screenshots for creating a Windows Server virtual machine, with no mention of Linux VM options or examples. The initial VM creation steps explicitly direct users to select Windows Server, and all subsequent access instructions assume a Windows environment. There are no Linux alternatives or parity in the walkthrough, and the order of presentation puts Windows tools and patterns first (and only).
Recommendations
- Include parallel instructions and screenshots for creating a Linux-based VM (e.g., Ubuntu Server) alongside Windows Server.
- Add explicit steps for connecting to a Linux VM via Azure Bastion using SSH, including command-line examples.
- Where VM OS selection is discussed, present both Windows and Linux options equally, or default to a neutral 'choose your preferred OS' approach.
- Ensure that function invocation and deployment steps mention cross-platform tools (e.g., Azure CLI, SSH, curl) and provide examples for both Windows and Linux environments.
- Review all screenshots and UI references to ensure they are not exclusively Windows-centric.