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 601-625 of 1023 flagged pages
Azure Functions Azure Functions Core Tools reference ...cles/azure-functions/functions-core-tools-reference.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation for Azure Functions Core Tools shows moderate Windows bias. It refers to the tool as 'func.exe' in the description, which is a Windows-specific executable extension. The '--managed-dependencies' option is noted as only supported for the PowerShell worker runtime, which is most commonly used on Windows. Several sections reference Windows-specific tools or patterns, such as the Microsoft Azure Storage Emulator (Windows-only), and mention creating trusted certificates 'on your computer' for HTTPS, which is a Windows-centric phrasing. In the 'func azure functionapp logstream' section, it is explicitly stated that streaming logs are 'not yet supported for Linux' in certain plans, with no workaround or parity for Linux users. The documentation also tends to mention Windows tools and behaviors before Linux equivalents, and does not provide Linux/macOS-specific examples or alternatives where features are missing.
Recommendations
  • Replace references to 'func.exe' with 'func' to reflect cross-platform usage.
  • Where features are Windows-only (e.g., Storage Emulator, logstream on Linux), provide Linux/macOS alternatives or workarounds, or explicitly state the limitation and link to feature requests.
  • Add Linux/macOS-specific examples and notes throughout, especially where behaviors differ (e.g., certificate creation for HTTPS, storage emulation).
  • Ensure that documentation does not assume Windows as the default environment (e.g., clarify file paths, shell commands, and tool availability).
  • When listing options or features, avoid putting Windows-specific ones first unless they are most widely used cross-platform.
GitHub Create Pull Request
Azure Functions Azure Functions Web PubSub output binding ...zure-functions/functions-bindings-web-pubsub-output.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not show any Windows-specific bias in terms of examples, tools, or ordering. However, there is a notable lack of Linux/macOS parity: Python and PowerShell samples are marked as 'pending', and Java is not supported yet. No OS-specific tools or patterns (such as PowerShell, CMD, or Windows utilities) are mentioned. All provided examples are language-focused and cross-platform (C#, JavaScript).
Recommendations
  • Add complete Python and PowerShell examples, ensuring they work on both Windows and Linux/macOS.
  • Clarify any OS-specific setup steps if relevant (e.g., environment variables, file paths) for all supported platforms.
  • If troubleshooting or configuration involves platform-specific commands, provide both Windows and Linux/macOS equivalents.
  • Explicitly state cross-platform compatibility where applicable.
GitHub Create Pull Request
Azure Functions Azure Functions custom handlers .../articles/azure-functions/functions-custom-handlers.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Examples and configuration snippets consistently use Windows-style executable names (handler.exe) and mention Windows conventions first, with Linux/macOS alternatives only parenthetically. There are no explicit Linux/macOS shell commands or deployment examples, and the use of .exe as the default executable path may confuse non-Windows users. The deployment instructions and troubleshooting sections do not provide platform-specific guidance for Linux/macOS users.
Recommendations
  • Provide explicit Linux/macOS examples alongside Windows ones, such as using 'handler' or './handler' instead of 'handler.exe' in configuration and file structure diagrams.
  • In configuration snippets, show both Windows and Linux/macOS variants, e.g., 'defaultExecutablePath': 'handler.exe' (Windows) and 'defaultExecutablePath': 'handler' (Linux/macOS).
  • Include Linux/macOS shell commands for deployment and testing, not just generic or Windows-centric instructions.
  • Clarify platform-specific requirements for building and deploying custom handler executables, including file permissions and binary formats.
  • Ensure troubleshooting and support sections mention platform-specific logging and diagnostic tools for Linux/macOS.
GitHub Create Pull Request
Azure Functions Deployment technologies in Azure Functions ...s/azure-functions/functions-deployment-technologies.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally covers both Windows and Linux deployment options for Azure Functions, but there is a notable Windows-first bias. Windows-specific tools (Visual Studio, Kudu/SCM) and deployment patterns are mentioned before Linux equivalents, and some deployment technologies (Source control, Local Git, FTPS) are described as 'Windows-only' in the availability table, with limited or no Linux guidance. Examples and instructions often reference Windows tools first, with Linux-specific steps sometimes relegated to later sections or footnotes. Some deployment methods lack explicit Linux/macOS command examples, and the documentation assumes familiarity with Windows-centric workflows.
Recommendations
  • Provide Linux/macOS-specific examples and command-line instructions alongside Windows examples, especially for deployment methods marked as 'Windows-only' or with limited Linux support.
  • Clearly indicate platform limitations and offer alternative Linux/macOS workflows where possible (e.g., for Source control, Local Git, FTPS).
  • Balance the order of examples and tool mentions so that Linux/macOS users see their options presented equally or in parallel with Windows.
  • Expand documentation for Linux-specific deployment scenarios, such as remote build and container deployments, with step-by-step guides and troubleshooting tips.
  • Add explicit notes or tables summarizing which deployment methods are supported on each OS, and link to Linux/macOS-focused guides where available.
GitHub Create Pull Request
Azure Functions Create your function app resources using Azure Resource Manager templates ...ns/functions-create-first-function-resource-manager.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
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. While Azure CLI is cross-platform, the PowerShell examples are inherently Windows-centric, and PowerShell is presented as a primary alternative to CLI. There are no Bash, Linux shell, or macOS-specific instructions, nor is there mention of Linux-native tooling or patterns. The structure presents PowerShell as an equal alternative to CLI, which may suggest Windows bias, especially since PowerShell is less commonly used on Linux/macOS. The Cloud Shell reference helps mitigate this somewhat, as it is cross-platform, but the lack of explicit Linux/macOS shell examples is notable.
Recommendations
  • Add Bash or Linux shell script examples for ARM template deployment using Azure CLI.
  • Clarify that Azure CLI commands work natively on Linux/macOS terminals, and provide explicit instructions for those environments.
  • Mention that PowerShell Core is available on Linux/macOS, or clarify any differences if relevant.
  • Consider reordering or labeling examples to avoid implying PowerShell is the default or preferred method for all users.
  • Include notes or links to Linux/macOS setup guides for Azure CLI and PowerShell Core.
GitHub Create Pull Request
Azure Functions Enable private site access to Azure Functions ...zure-functions/functions-create-private-site-access.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias by exclusively instructing users to create a Windows Server virtual machine, with no mention of Linux-based alternatives. All VM creation steps, screenshots, and references are for Windows Server, and there are no examples or guidance for users who prefer or require Linux VMs. This can create friction for Linux/macOS users who may want to use a Linux VM for testing or access.
Recommendations
  • Include parallel instructions and screenshots for creating a Linux-based virtual machine (e.g., Ubuntu Server) alongside the Windows Server steps.
  • Explicitly mention that either Windows or Linux VMs can be used for this scenario, and provide guidance for both.
  • Where possible, use neutral language (e.g., 'virtual machine') and avoid defaulting to Windows unless there is a technical requirement.
  • Add a note or section explaining any differences in accessing the function app from Linux vs. Windows VMs, if applicable.
GitHub Create Pull Request
Azure Functions host.json reference for Azure Functions 2.x ...b/main/articles/azure-functions/functions-host-json.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page is generally cross-platform, but there are some areas of Windows bias. The 'managedDependency' feature is described as PowerShell-only, which is a Windows-centric technology. There are several references to Windows environment variables (e.g., %TEMP%) and folders (LOCALAPPDATA, APPDATA, TEMP) as defaults, with no mention of Linux/macOS equivalents. In the snapshotConfiguration section, the default temp folder is given as *%TEMP%\Dumps*, which is a Windows path format. These references may create friction for Linux/macOS users who need to map these settings to their own environments. Additionally, Windows-centric terminology and examples (such as the use of backslashes in paths) appear before any Linux alternatives, and Linux/macOS equivalents are not explicitly documented.
Recommendations
  • For all environment variable references (e.g., %TEMP%, LOCALAPPDATA, APPDATA), add Linux/macOS equivalents (e.g., $TMPDIR, /tmp) and clarify how the runtime resolves these on non-Windows systems.
  • When showing default folder paths, provide both Windows and Linux/macOS formats (e.g., %TEMP%\Dumps and /tmp/Dumps).
  • For features described as PowerShell-only, clarify if there are equivalent features for other languages/runtimes, or explicitly state that Linux/macOS users cannot use them.
  • Add explicit notes or examples for Linux/macOS users where Windows-centric terminology or tools are mentioned.
  • Consider listing cross-platform or Linux/macOS examples before or alongside Windows examples to avoid 'windows_first' bias.
GitHub Create Pull Request
Azure Functions Develop legacy C# class library functions using Azure Functions ...cles/azure-functions/functions-dotnet-class-library.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-centric tools (Visual Studio, MSI installer paths, Windows environment variable paths) are mentioned first or exclusively in several sections. Command-line examples are provided for Windows (cmd, PowerShell), but Linux/macOS equivalents (bash, zsh, etc.) are missing or referenced only indirectly. ReadyToRun publishing is shown with a Windows runtime identifier, with no mention of Linux/macOS equivalents. The use of Windows paths and references to WindowsAzure.Storage further reinforce the bias.
Recommendations
  • Provide explicit Linux/macOS examples for command-line operations, including package installation and usage of Azure Functions Core Tools.
  • Include bash/zsh equivalents for package installation commands (e.g., dotnet CLI, npm) alongside cmd and PowerShell.
  • Show ReadyToRun publishing examples for Linux (e.g., linux-x64) and macOS (e.g., osx-x64) in addition to Windows.
  • Mention cross-platform editors (e.g., VS Code) and CLI workflows before or alongside Visual Studio.
  • Avoid Windows-specific environment variable paths (e.g., %USERPROFILE%\AppData...) without cross-platform alternatives.
  • Clarify that dependencies like WindowsAzure.Storage are compatible with non-Windows platforms, or provide alternatives if needed.
GitHub Create Pull Request
Azure Functions Continuously update function app code using Azure Pipelines ...icles/azure-functions/functions-how-to-azure-devops.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation exhibits moderate Windows bias. Windows-based build agents ('windows-latest') are used by default for C# and PowerShell examples, and Windows is the default platform for function apps unless Linux is explicitly specified. PowerShell is included as a first-class language, but Linux shell scripting is not equivalently highlighted. Windows deployment examples and slot deployment are described before Linux equivalents, and some features (like slots) are not supported or are being retired for Linux Consumption plans. There is limited guidance for Linux/macOS users outside of the YAML pipeline agent selection and a few Linux-specific notes.
Recommendations
  • Provide Linux/macOS equivalents for all Windows/Powershell examples, including shell scripting and troubleshooting steps.
  • Present Linux and Windows examples side-by-side or in parallel tabs, rather than Windows-first ordering.
  • Clarify platform limitations and provide alternative solutions or workarounds for Linux users where features are missing or being retired.
  • Include explicit instructions for setting up and using Linux/macOS development environments, not just agent selection.
  • Highlight Linux support for all languages where applicable, and avoid implying Windows as the default unless truly required.
GitHub Create Pull Request
Azure Functions Configure function app settings in Azure Functions ...ns/functions-how-to-use-azure-function-app-settings.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. Windows-specific tools (PowerShell, Kudu, App Service Editor) are frequently mentioned and shown before or instead of Linux equivalents. Many examples and features (such as in-portal editing, Kudu, App Service Editor, console access) are available only or primarily for Windows. PowerShell is presented as a primary automation tool, and Linux limitations are called out but not addressed with alternative workflows. Migration guidance is Windows-only, with Linux migration explicitly unsupported. Some features (like CORS management) are unavailable in PowerShell, but this is noted.
Recommendations
  • Provide explicit Linux/macOS command examples and workflows alongside Windows/PowerShell instructions, especially for automation and management tasks.
  • Highlight and document Linux-compatible alternatives for Windows-only tools (e.g., Kudu, App Service Editor, in-portal console).
  • Clarify which features are unavailable on Linux and offer recommended Linux-native workarounds or guidance.
  • Where migration is unsupported for Linux, offer links to alternative strategies or explain the roadmap for Linux parity.
  • Avoid presenting Windows/PowerShell instructions first; use parallel tabbed examples for both platforms.
  • Expand documentation for local development and deployment on Linux/macOS, including use of Azure CLI and Core Tools.
GitHub Create Pull Request
Azure Functions Azure Functions networking options ...ticles/azure-functions/functions-networking-options.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias, particularly in the Hybrid Connections section, which is explicitly Windows-only. Example automation commands are provided for Azure CLI, PowerShell, and portal, but PowerShell is highlighted and no Linux-specific troubleshooting or tool guidance is present. Subnet sizing recommendations mention Windows before Linux, and some features (Hybrid Connections) are unavailable for Linux. The order of examples and recommendations tends to favor Windows, and Linux/macOS users may need to seek additional guidance or workarounds.
Recommendations
  • Clearly indicate feature parity and limitations for Linux/macOS throughout the documentation, especially in sections like Hybrid Connections.
  • Provide Linux/macOS equivalents for all automation and scripting examples (e.g., Bash, Azure CLI, and Linux troubleshooting tools).
  • Present examples for both Windows and Linux equally, or alternate their order to avoid implicit prioritization.
  • Add troubleshooting guidance and screenshots for Linux environments where relevant.
  • Explicitly state when a feature is Windows-only and suggest alternatives for Linux users.
GitHub Create Pull Request
Azure Functions Azure Functions Premium plan ...ain/articles/azure-functions/functions-premium-plan.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits several forms of Windows bias. Windows-specific tools (Azure PowerShell) are consistently presented alongside Azure CLI, with PowerShell examples given equal prominence. In some sections, migration guidance is explicitly Windows-only, with Linux migration unsupported. Portal instructions do not clarify OS differences, and there is no mention of Linux/macOS-specific patterns or shell commands. The region scale-out table lists Windows before Linux, and some regions are 'Not Available' for Linux without further explanation or alternatives. Overall, Linux users are left with less guidance and, in some cases, cannot complete certain tasks (e.g., migration).
Recommendations
  • Add explicit Linux/macOS shell examples (e.g., bash, zsh) where PowerShell is used.
  • Clarify which portal instructions apply to Linux-hosted apps and note any differences.
  • Provide alternative migration strategies or workarounds for Linux users, or clearly state limitations.
  • Where features/tools are Windows-only, offer parity or document the gap and expected roadmap.
  • In tables and lists, present Linux options with equal prominence and detail as Windows.
  • Explain 'Not Available' regions for Linux and suggest alternatives or escalation paths.
GitHub Create Pull Request
Azure Functions Azure Functions Scale and Hosting .../blob/main/articles/azure-functions/functions-scale.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows is frequently mentioned first in tables and explanations, and the Consumption plan is described as Windows-first, with Linux support retired or secondary. Windows-specific features (such as PowerShell modules and .NET Framework) are highlighted as use cases, while Linux equivalents are not discussed. There is little mention of Linux-specific tooling, patterns, or developer workflows, and no Linux/macOS command-line examples or troubleshooting steps are provided.
Recommendations
  • Present Linux and Windows options equally in tables and explanations, alternating which is listed first.
  • Include Linux-specific examples, such as Bash or CLI commands, and discuss Linux-native developer workflows.
  • Highlight Linux-compatible tools and patterns, such as Python or Node.js runtime stacks, and mention Linux equivalents for Windows-specific features.
  • Add troubleshooting steps and recommendations for Linux/macOS users, especially where platform-specific limitations exist.
  • Clarify the impact of retired Linux Consumption plan support and provide migration guidance for affected users.
GitHub Create Pull Request
Azure Functions Create and deploy function code to Azure using Visual Studio Code ...cles/azure-functions/how-to-create-function-vs-code.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation generally aims for cross-platform parity, but several sections show Windows bias. Windows-specific tools (PowerShell, .NET) are mentioned, and in some cases, Windows instructions or links are given before Linux equivalents. The troubleshooting section references Windows-specific issues (WSL Bash) without similar Linux/macOS troubleshooting. PowerShell is included as a first-class language, but Linux shell alternatives are not. Some SDK installation links default to Windows, and certain steps (like compiling Go/Rust for Linux from Windows) require extra configuration for Windows users, but Linux/macOS instructions are more straightforward.
Recommendations
  • Ensure all prerequisite installation links include both Windows and Linux/macOS instructions, not just Windows.
  • In troubleshooting, add Linux/macOS-specific issues and solutions, not only Windows/WSL notes.
  • For PowerShell, clarify cross-platform support and provide equivalent bash/zsh examples where applicable.
  • When mentioning tools (e.g., .NET, PowerShell), explicitly state platform compatibility and provide installation instructions for all OSes.
  • In code and command examples, alternate the order of Windows and Linux/macOS instructions, or present them side-by-side.
  • Highlight any platform-specific caveats for Linux/macOS users, especially where Windows defaults differ.
GitHub Create Pull Request
Azure Functions Migrate apps from Azure Functions version 3.x to 4.x ...rticles/azure-functions/migrate-version-3-version-4.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias primarily by providing only a PowerShell script for identifying function apps to migrate, referencing Azure PowerShell multiple times, and omitting equivalent Linux/macOS CLI (Azure CLI, Bash) examples. Windows-centric tools and patterns (Visual Studio, PowerShell) are mentioned before or instead of cross-platform alternatives, which may create friction for Linux/macOS users.
Recommendations
  • Provide Azure CLI and/or Bash script examples alongside PowerShell scripts for identifying function apps to migrate.
  • Explicitly mention cross-platform tools such as VS Code and Azure CLI in relevant sections, not just Visual Studio.
  • Ensure instructions for local development and migration reference both Windows and Linux/macOS environments, including installation and usage of Azure Functions Core Tools.
  • Add notes or links for Linux/macOS users where Windows-specific tools or patterns are referenced.
  • Where possible, use neutral language and order (e.g., 'Use PowerShell or Azure CLI' instead of 'Use PowerShell').
GitHub Create Pull Request
Azure Functions How to target Azure Functions runtime versions ...b/main/articles/azure-functions/set-runtime-version.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Windows and Linux guidance, but Windows and PowerShell examples are often presented first and in more detail. PowerShell cmdlets are included for Windows, but there is no Linux shell equivalent (e.g., Bash scripts) for comparable tasks. Some portal instructions are not available for Linux users, and Linux-specific steps require Azure CLI or manual intervention. The Linux section is less detailed and relies on support professionals for certain actions.
Recommendations
  • Present Windows and Linux instructions in parallel, with equal detail and visibility.
  • Provide Bash or shell script equivalents for PowerShell cmdlets where possible.
  • Clarify which portal actions are unavailable for Linux and suggest CLI alternatives.
  • Expand Linux examples to cover all steps shown for Windows, including troubleshooting and edge cases.
  • Avoid language that implies Windows is the default or preferred platform.
GitHub Create Pull Request
Azure Functions Migrate C# app from in-process to isolated worker model ...es/azure-functions/migrate-dotnet-to-isolated-model.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a notable Windows bias, primarily by providing only Azure PowerShell scripts for identifying function apps to migrate, without offering equivalent Bash, Azure CLI, or cross-platform alternatives. The use of PowerShell is presented as the default and only method, and there is no mention of Linux/macOS-specific tools or workflows. This may create friction for users on non-Windows platforms, especially in the initial migration identification step.
Recommendations
  • Provide equivalent Azure CLI (az) commands and/or Bash scripts for identifying function apps using the in-process model.
  • Explicitly mention that PowerShell examples are for Windows and offer alternatives for Linux/macOS users.
  • Where tooling is referenced (e.g., Visual Studio), clarify cross-platform options such as VS Code and CLI-based deployment.
  • Ensure that all critical steps (especially those involving scripting or automation) have cross-platform instructions.
  • Consider ordering examples so that cross-platform (CLI/Bash) options are presented before or alongside Windows/PowerShell examples.
GitHub Create Pull Request
Azure Functions Migrate Consumption plan apps to Flex Consumption in Azure Functions ...unctions/migration/migrate-plan-consumption-to-flex.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides parallel instructions for both Linux and Windows, but Windows examples and CLI commands are often presented first or in greater detail, especially in the migration steps for Windows. There is a notable emphasis on Windows-specific tools and patterns (e.g., Azure CLI commands, PowerShell scripts, Visual Studio, and Windows file share details), while Linux equivalents are sometimes less detailed or omitted. Some advanced migration steps and troubleshooting are described primarily for Windows, with Linux instructions being less comprehensive or missing in certain sections.
Recommendations
  • Ensure all CLI and portal instructions are equally detailed for both Linux and Windows platforms.
  • Provide Linux-specific examples and scripts where Windows/PowerShell commands are shown.
  • Highlight Linux tools and workflows (e.g., bash scripts, Linux file system paths, Linux deployment patterns) alongside Windows tools.
  • Avoid presenting Windows instructions before Linux unless there is a technical reason; alternate or combine examples.
  • Expand troubleshooting and post-migration sections to include Linux-specific guidance and error scenarios.
GitHub Create Pull Request
Azure Functions Troubleshoot Python function apps in Azure Functions ...n/articles/azure-functions/recover-python-functions.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates some Windows bias, notably by presenting Windows/PowerShell commands before Unix/Linux equivalents, referencing Windows-specific tools (e.g., PowerShell, 'py' launcher), and sometimes omitting explicit Linux/macOS examples or guidance. While Linux is acknowledged as the Azure Functions runtime environment, and some Unix commands are included, the structure and examples often prioritize or assume Windows usage, which can create friction for Linux/macOS users.
Recommendations
  • Present Linux/macOS and Windows examples side-by-side, or default to Linux first since Azure Functions runs on Linux.
  • Avoid referencing Windows tools (e.g., 'py' launcher, PowerShell) without providing equivalent Linux/macOS commands.
  • Ensure all command-line examples are provided for both Windows (PowerShell/CMD) and Linux/macOS (Bash), using clear tabs or sections.
  • Where possible, use cross-platform commands (e.g., 'python3' instead of 'py') in documentation.
  • Explicitly mention when a step or tool is Windows-only, and provide alternatives for Linux/macOS.
  • Review all troubleshooting steps to ensure Linux/macOS users have clear, actionable guidance.
GitHub Create Pull Request
Azure Functions Storage considerations for Azure Functions ...ain/articles/azure-functions/storage-considerations.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific plans and settings are referenced before Linux equivalents, and PowerShell examples are provided alongside Azure CLI, but Linux-specific examples are less detailed or absent in some sections. Windows hosting plans and deployment patterns are described first or exclusively in several places, and some features (like Azure Files mounting) are only available for Linux but are explained after Windows-centric content. There is also a tendency to mention Visual Studio and Azurite (Windows tools) before cross-platform alternatives.
Recommendations
  • Ensure Linux examples and instructions are provided wherever Windows/Powershell examples are given, especially for deployment and configuration tasks.
  • Present Linux and Windows hosting plans and settings in parallel, rather than Windows-first.
  • Include cross-platform tooling (e.g., VS Code, CLI) and avoid referencing Windows-only tools (Visual Studio, Azurite) as the primary development environment.
  • Clarify which features and settings apply to Linux, Windows, or both, and provide explicit guidance for Linux/macOS users.
  • Add Linux/macOS-specific troubleshooting and best practices sections where relevant.
GitHub Create Pull Request
Azure Functions Work with access keys in Azure Functions .../main/articles/azure-functions/function-keys-how-to.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key management tasks, but PowerShell examples are given equal prominence and detail as CLI, and are not clearly marked as Windows-only. There is no mention of Linux/macOS-specific shell usage (e.g., Bash), nor are there explicit examples for Linux/macOS users beyond Azure CLI. Some instructions (e.g., running CLI in Cloud Shell) note the need to modify commands for Windows, but do not provide Linux/macOS terminal examples or guidance. PowerShell is featured as a primary method, which may be confusing or inaccessible for non-Windows users.
Recommendations
  • Clearly label PowerShell examples as Windows-only and provide equivalent Bash or shell script examples for Linux/macOS users.
  • When presenting multiple methods, list cross-platform options (Azure CLI, REST API via curl, Azure Functions Core Tools) before Windows-specific tools.
  • Add explicit instructions and examples for running Azure CLI commands in local Linux/macOS terminals, not just in Cloud Shell.
  • Include troubleshooting notes for platform-specific issues (e.g., authentication, environment variables) on Linux/macOS.
  • Ensure parity in detail and guidance for Linux/macOS users, especially for critical tasks like key renewal and deletion.
GitHub Create Pull Request
Azure Functions Use Python and TensorFlow for machine learning in Azure ...ure-functions/functions-machine-learning-tensorflow.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides examples for Bash, PowerShell, and Cmd, but frequently lists Windows-specific tools and patterns first (e.g., 'py' launcher, PowerShell/Cmd examples before Bash in some sections). Windows-specific troubleshooting (e.g., registry edits for long paths) is included, while Linux/macOS issues are only briefly mentioned. The use of 'py' launcher and PowerShell is emphasized, which may be unfamiliar or unavailable to Linux/macOS users.
Recommendations
  • Present Bash/Linux/macOS examples before or alongside Windows examples, especially in sections where Linux is likely to be used.
  • Include Linux/macOS-specific troubleshooting tips (e.g., permissions, package manager issues) in parity with Windows-specific advice.
  • Avoid assuming the presence of Windows-only tools like the 'py' launcher; clarify alternatives for Linux/macOS users.
  • Explicitly state when commands differ between platforms, and provide clear guidance for each.
  • Where possible, use cross-platform commands (e.g., 'python' instead of 'py') in generic instructions.
GitHub Create Pull Request
Azure Functions Create your function app resources in Azure using Bicep ...ure-functions/functions-create-first-function-bicep.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for deploying and validating resources. However, Azure PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) may create a perception of Windows bias. The documentation gives equal prominence to Azure PowerShell as to Azure CLI, despite PowerShell being less commonly used on Linux/macOS. There are no Linux/macOS-specific instructions, nor is there mention of shell environments (e.g., Bash, zsh) or platform-specific considerations. The examples do not explicitly state that Azure CLI is recommended for Linux/macOS users, and PowerShell examples are shown for all language pivots, reinforcing the Windows bias.
Recommendations
  • Explicitly recommend Azure CLI for Linux/macOS users and clarify that Azure PowerShell is primarily for Windows environments.
  • Add notes or sections highlighting cross-platform compatibility, especially for CLI commands.
  • Consider removing or de-emphasizing Azure PowerShell instructions unless there is a clear use case for non-Windows platforms.
  • Add platform-specific notes or troubleshooting tips for Linux/macOS users.
  • Ensure that CLI examples are shown first, or at least clarify their cross-platform nature.
GitHub Create Pull Request
Azure Functions Respond to database changes in Azure SQL Database using Azure Functions ...ure-functions/scenario-database-changes-azure-sqldb.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively recommending and providing instructions for Visual Studio Code and its SQL Server (mssql) extension, which are most commonly used on Windows. There are no examples or guidance for connecting to Azure SQL Database using Linux-native tools (such as sqlcmd, Azure Data Studio, or command-line utilities). All examples and workflow steps assume the use of Visual Studio Code and its extensions, which may not be the preferred or available tooling for many Linux/macOS users.
Recommendations
  • Add alternative instructions for connecting to Azure SQL Database using cross-platform or Linux-native tools, such as sqlcmd, Azure Data Studio, or the Azure CLI.
  • Explicitly mention that Visual Studio Code and its extensions are available on Linux/macOS, and provide installation guidance if required.
  • Provide examples of running the workflow using only the Azure CLI and command-line tools, without relying on Visual Studio Code.
  • Include troubleshooting or notes for users who may not have access to Visual Studio Code or its extensions.
GitHub Create Pull Request
Azure Functions Bring dependencies and third-party libraries to Azure Functions ...icles/azure-functions/bring-dependency-to-functions.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation shows a moderate Windows bias, especially in the Java example where the ffmpeg binary is referenced as 'ffmpeg.exe' and the pathing assumes Windows conventions. PowerShell is mentioned as an upload option before Linux equivalents. Windows-style paths and tools are referenced before or instead of Linux alternatives, and there is no explicit Linux Java example. However, Python examples and Linux mounting instructions are present, mitigating the severity.
Recommendations
  • Provide explicit Linux/macOS Java examples, including use of ffmpeg (not ffmpeg.exe) and Linux-style paths.
  • Mention Linux upload tools (e.g., rsync, scp) alongside PowerShell and Azure CLI for uploading dependencies.
  • Avoid using Windows-specific binary names (e.g., ffmpeg.exe) in cross-platform code samples; use generic names or show both.
  • Clarify platform-specific requirements for executable permissions (e.g., chmod for Linux) in all relevant sections.
  • Ensure examples and instructions are presented in a platform-neutral order, or provide parallel examples for each OS.
GitHub Create Pull Request
← Previous Page 25 of 41 Next →