Azure Functions

711
Total Pages
610
Linux-Friendly Pages
101
Pages with Bias
14.2%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

233 issues found
Showing 101-125 of 233 flagged pages
Azure Functions Enable private site access to Azure Functions ...zure-functions/functions-create-private-site-access.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively guides users to create a Windows Server VM, with no mention of Linux VM options or examples. All screenshots and instructions for VM creation reference Windows Server, and there are no alternative steps or notes for Linux users. This creates friction for those preferring or requiring Linux environments.
Recommendations
  • Include instructions and screenshots for creating a Linux VM (e.g., Ubuntu or CentOS) alongside Windows Server.
  • Add a note or section explaining how to choose a Linux image in the VM creation process.
  • Provide parity in examples for accessing the VM (e.g., SSH for Linux, RDP for Windows) and clarify Bastion usage for both OS types.
  • Mention that Azure Functions and Bastion support both Windows and Linux VMs, and link to relevant documentation.
GitHub Create Pull Request
Azure Functions Azure Functions custom handlers .../articles/azure-functions/functions-custom-handlers.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several areas: executable examples and file naming conventions (e.g., 'handler.exe') are Windows-centric and presented first, with Linux/macOS equivalents mentioned only parenthetically or not at all. Deployment instructions and troubleshooting sections reference Windows-style binaries and tools, without explicit Linux/macOS commands or examples. There are no concrete Linux/macOS-specific examples or guidance for building or running custom handlers, which may create friction for non-Windows users.
Recommendations
  • Explicitly show both Windows and Linux/macOS file naming conventions and executable formats (e.g., 'handler.exe' and './handler').
  • Provide Linux/macOS-specific examples for building and running custom handlers, including commands for compiling Go binaries on those platforms.
  • Include deployment instructions and troubleshooting steps for Linux/macOS environments, such as using chmod, running executables with './', and handling platform-specific dependencies.
  • Present cross-platform examples side-by-side or note platform differences clearly, rather than mentioning Linux/macOS only parenthetically.
  • Clarify that Azure Functions supports custom handlers on all major platforms and provide links to platform-specific guides or samples.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page generally covers both Windows and Linux deployment options for Azure Functions, but there is a noticeable Windows bias. Windows-specific deployment technologies (e.g., source control, local Git, FTPS) are called out as 'Windows-only' in the technology availability table, while Linux equivalents are less emphasized or not available for some plans. Windows tools (Visual Studio, Kudu) are mentioned first or exclusively in several sections, and examples for Linux (such as Linux CLI commands or Linux-specific deployment patterns) are less detailed or absent. Some deployment methods are only available for Windows, with Linux users directed to alternative, sometimes less convenient, approaches.
Recommendations
  • Provide Linux/macOS-specific examples and workflows alongside Windows ones, especially for deployment methods currently described as 'Windows-only'.
  • Where deployment technologies are unavailable for Linux, offer clear alternative Linux-native solutions or workarounds, and document them with step-by-step instructions.
  • Balance the order of presentation so that Linux tools and patterns (e.g., Azure CLI, Core Tools, Docker) are described before or alongside Windows tools like Visual Studio and Kudu.
  • Clarify any limitations for Linux users and provide links to relevant Linux documentation or community resources.
  • Expand sections on remote build and container deployment with more Linux/macOS developer scenarios and troubleshooting tips.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-based examples (e.g., 'windows-latest' agent pools) are shown first for C# and PowerShell, and PowerShell is included as a first-class language. The default appType for deployment is Windows, with Linux requiring explicit configuration. While Linux examples are present for JavaScript, Python, and Java, the C# and PowerShell build examples only use Windows agents, and PowerShell is inherently Windows-centric. Some deployment features (slots, Flex Consumption) are not available or are limited for Linux, but these limitations are called out. The overall structure and ordering favor Windows users, with Linux options often presented as alternatives or requiring additional steps.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which is shown first, especially for C#.
  • Include C# build examples using 'ubuntu-latest' agent pools to demonstrate cross-platform compatibility.
  • Clarify PowerShell's Windows-only nature and suggest Bash or Python for Linux automation.
  • Explicitly state platform limitations (e.g., slot support, Flex Consumption) at the top of relevant sections.
  • Where features are Windows-only, provide Linux workarounds or alternatives if possible.
  • Ensure all language tabs (especially C#) show both Windows and Linux agent pool options.
  • Add notes or links to Linux/macOS-specific troubleshooting and best practices.
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-11 06:20
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-specific tools (Visual Studio, MSI installer paths, Windows environment variable locations) are mentioned first or exclusively in several sections. Command-line examples are provided for Windows (cmd, PowerShell), but Linux/macOS equivalents (bash, zsh) are missing or relegated to links. ReadyToRun publishing is shown only for Windows targets, with no Linux/macOS example. Environment variable access references Windows-centric variables and paths. While Azure Functions Core Tools is cross-platform, installation and usage instructions focus on Windows methods first.
Recommendations
  • Add explicit Linux/macOS examples for command-line operations, such as installing packages and running Core Tools.
  • Include ReadyToRun publishing examples for Linux (e.g., <RuntimeIdentifier>linux-x64</RuntimeIdentifier>) and macOS.
  • Show environment variable access and local.settings.json usage in Linux/macOS contexts, including relevant file paths.
  • Balance Visual Studio/Windows tool references with Visual Studio Code and CLI workflows, and mention cross-platform editors and tools upfront.
  • Provide bash/zsh equivalents for PowerShell/cmd commands, especially for package installation and project setup.
  • Clarify that all major workflows are supported on Linux/macOS, and link to platform-specific guides where available.
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-11 06:20
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. Examples and instructions frequently prioritize Windows tools (PowerShell, CMD, Kudu), with Linux alternatives often missing, unsupported, or mentioned as unavailable. Many features (Kudu, App Service editor, console) are Windows-only or have limited/no Linux support. Migration instructions are Windows-centric, and Linux users face restrictions or lack of guidance for key operations.
Recommendations
  • Provide explicit Linux/macOS examples and instructions alongside Windows/PowerShell, especially for command-line operations and tooling.
  • Clearly indicate feature parity and limitations for Linux, and offer alternative workflows or tools where features are unavailable.
  • Include bash and cross-platform shell examples where possible, not just PowerShell.
  • Document Linux-specific migration paths, or clarify limitations with actionable alternatives.
  • Expand coverage of Linux-compatible tools (e.g., SSH console, Azure CLI) and highlight their usage.
  • Where features are Windows-only, suggest equivalent Linux approaches or workarounds.
GitHub Create Pull Request
Azure Functions Azure Functions networking options ...ticles/azure-functions/functions-networking-options.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Feature Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias in several areas. The Hybrid Connections feature is explicitly stated as Windows-only, with Linux support unavailable. CLI, PowerShell, and portal instructions are provided for enabling virtual network triggers, but Linux-specific guidance is limited. In subnet sizing recommendations, Windows is mentioned before Linux, and minimum subnet sizes are given for both, but Windows is listed first. Some automation examples use PowerShell, and there is a lack of Linux/macOS-specific troubleshooting or example parity throughout.
Recommendations
  • Clearly indicate Linux/macOS alternatives or limitations for features like Hybrid Connections, and provide guidance for Linux users where possible.
  • Ensure that CLI examples are given equal prominence to PowerShell, and provide bash/shell script equivalents where appropriate.
  • Present Linux and Windows instructions side-by-side, or in separate tabs, to avoid Windows-first ordering.
  • Add troubleshooting steps and screenshots for Linux/macOS environments where relevant.
  • Explicitly state feature parity or lack thereof for all major networking features, and link to Linux/macOS documentation when available.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits several forms of Windows bias. Many configuration examples are provided for Azure PowerShell, a Windows-centric tool, alongside Azure CLI, but no Linux-specific shell examples (e.g., Bash scripts) are given. In some cases, PowerShell is presented as an equal alternative to CLI, but the language and structure of examples (especially resource manipulation) are distinctly PowerShell-heavy. The migration section explicitly states that plan migration is only supported on Windows, with no Linux alternative or workaround. Throughout, Windows is often mentioned first in region tables and OS-specific notes, and there is a lack of parity in guidance for Linux users, especially regarding migration and tooling.
Recommendations
  • Add explicit Bash or Linux shell examples where CLI commands are shown, clarifying any OS-specific nuances.
  • Where PowerShell is used, note its platform limitations and provide equivalent Linux/macOS commands if possible.
  • In migration sections, clarify Linux limitations and suggest alternative approaches or workarounds for Linux users.
  • Balance the order of OS mentions (e.g., Windows and Linux) in tables and explanations to avoid implicit prioritization.
  • Highlight any differences in portal experience for Linux-hosted apps, if applicable.
GitHub Create Pull Request
Azure Functions Monitor executions in Azure Functions .../main/articles/azure-functions/functions-monitoring.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation generally avoids platform-specific examples, but there are notable areas of Windows bias. Performance Counters are called out as unsupported on Linux, and built-in log streaming is not available for Linux Consumption plans, with no Linux alternatives or workarounds provided. The documentation references the Azure portal and App Service platform (historically Windows-centric) without clarifying Linux/macOS parity. No Linux/macOS command-line or tooling examples are given, and PowerShell is mentioned in the logging section, but not prioritized.
Recommendations
  • Provide explicit Linux/macOS alternatives or workarounds for features unavailable on those platforms (e.g., Performance Counters, built-in log streaming).
  • Clarify which features are Windows-only and suggest equivalent Linux approaches or third-party tools where possible.
  • Include Linux/macOS-specific examples or notes in sections discussing local development and log streaming.
  • Add parity tables or callouts for platform-specific limitations and solutions.
  • When referencing tools or APIs, ensure both Windows and Linux/macOS options are presented equally.
GitHub Create Pull Request
Azure Functions Deploy a PyTorch model as an Azure Functions application ...n/articles/azure-functions/machine-learning-pytorch.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 Windows-specific tools and patterns (such as 'py' launcher, PowerShell, and registry edits) are mentioned frequently and sometimes before Linux equivalents. Windows troubleshooting tips are more detailed, and Windows command examples often precede or are more prominent than Linux/macOS equivalents.
Recommendations
  • Ensure Linux/macOS instructions are always presented with equal prominence and detail as Windows instructions.
  • Provide troubleshooting tips for common Linux/macOS issues (e.g., permissions, package installation problems) alongside Windows-specific tips.
  • Avoid mentioning Windows tools (such as registry edits) without Linux/macOS equivalents or notes.
  • Where possible, use cross-platform commands (e.g., 'python' instead of 'py') as the default, and clarify platform-specific differences only as needed.
  • Present Bash/Linux/macOS examples first or alternate their order with Windows examples to avoid implicit prioritization.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell scripts for identifying function apps to migrate, without offering equivalent Bash, Azure CLI, or cross-platform alternatives. Windows-centric tooling (PowerShell) is presented as the default and only option, with no mention of Linux/macOS workflows or commands. This may create friction for users on non-Windows platforms who do not use PowerShell.
Recommendations
  • Provide Azure CLI (az) and/or Bash script equivalents alongside PowerShell examples for identifying function apps.
  • Explicitly mention that PowerShell is available cross-platform, but also acknowledge and support users who prefer native Linux/macOS shells.
  • Where possible, present cross-platform commands first, or offer tabs for Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) workflows.
  • Clarify any tooling requirements for Linux/macOS users (e.g., installation of Azure CLI, PowerShell Core, etc.).
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page generally supports cross-platform development in Visual Studio Code, but several areas show Windows bias. Windows-specific tools (PowerShell, .NET) are highlighted, and some instructions or links (e.g., PowerShell install) default to Windows. Troubleshooting tips mention Windows-specific issues before Linux/macOS. Some examples (e.g., Go/Rust cross-compilation) provide Windows instructions, but Linux/macOS are not always equally detailed. The PowerShell language is included as a first-class option, but Linux equivalents (e.g., Bash) are not. In troubleshooting, Windows-specific shell issues are called out, but Linux/macOS issues are not.
Recommendations
  • Ensure all language/tool prerequisites link to cross-platform installation guides, not just Windows.
  • For PowerShell, clarify Linux/macOS installation and usage, or provide Bash alternatives where appropriate.
  • In troubleshooting, add Linux/macOS-specific guidance (e.g., common shell issues, permissions).
  • When listing instructions or examples, present Linux/macOS and Windows in parallel, or default to platform-neutral steps.
  • Include Bash or other Linux-native scripting examples alongside PowerShell.
  • Review all links to ensure they do not default to Windows-only documentation.
GitHub Create Pull Request
Azure Functions Manage connections in Azure Functions ...ob/main/articles/azure-functions/manage-connections.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides code examples only for C# (.NET) and JavaScript, with a strong emphasis on .NET-specific patterns and tools (e.g., HttpClient, SqlClient, Entity Framework). There are no examples or guidance for Linux/macOS-specific tools, environments, or languages commonly used outside Windows, such as Python or Bash. The configuration instructions reference Windows-centric concepts (e.g., Application settings, local.settings.json) without clarifying cross-platform differences. No PowerShell or Windows-only tools are mentioned, but the overall structure and example selection favor Windows/.NET users.
Recommendations
  • Add code examples for other popular Azure Functions languages used on Linux/macOS, such as Python and Java.
  • Include guidance or examples for Linux/macOS environments, such as using environment variables, file permissions, or relevant connection management tools.
  • Clarify that configuration steps (e.g., local.settings.json, Application settings) apply equally on Linux/macOS, and note any platform-specific differences.
  • Present examples for all supported languages in parallel, rather than leading with C#/.NET.
  • Reference Linux/macOS troubleshooting tools (e.g., tailing logs, using CLI tools) where appropriate.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily by providing only a PowerShell script for identifying function apps to migrate, with no equivalent Bash, Azure CLI, or Linux-native example. Windows/PowerShell tooling is mentioned first and exclusively in key migration steps, potentially creating friction for Linux/macOS users. While the rest of the migration instructions are language-dependent and generally cross-platform, initial discovery and preparation steps are Windows-centric.
Recommendations
  • Provide equivalent Azure CLI or Bash scripts for identifying function apps to migrate, ensuring Linux/macOS users can follow along without needing PowerShell.
  • Explicitly mention cross-platform alternatives alongside PowerShell in all relevant steps.
  • Where PowerShell is referenced, clarify that Azure CLI or REST API can be used on Linux/macOS, and link to those instructions.
  • Review all tooling recommendations to ensure parity for Linux/macOS users (e.g., Visual Studio alternatives, Core Tools installation instructions).
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-11 06:20
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 examples and tools (PowerShell, Visual Studio) are presented more prominently and with greater detail. PowerShell commands are included for both viewing and updating settings, while Linux-specific instructions (such as using linuxFxVersion) are less detailed and lack parity in tooling (no PowerShell or portal support for linuxFxVersion). Windows scenarios (e.g., Visual Studio publishing) are described, but Linux equivalents are missing. Azure CLI is used for both platforms, but Windows users have more options and examples.
Recommendations
  • Provide Linux/macOS equivalents for all Windows-specific instructions, especially for tasks like pinning runtime versions and viewing/updating settings.
  • Add guidance for Linux users on how to perform tasks that are currently only described for Windows (e.g., publishing from VS Code, handling pinned versions).
  • Clarify which tools and features are available on each platform, and avoid presenting Windows options first unless they are universally applicable.
  • Where PowerShell is used for Windows, suggest Bash or other native Linux scripting alternatives for Linux users.
  • Ensure that portal instructions explicitly state limitations for Linux (e.g., inability to set linuxFxVersion), and offer alternative workflows.
GitHub Create Pull Request
Azure Functions Update Language Versions in Azure Functions ...n/articles/azure-functions/update-language-versions.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation generally maintains parity between Windows and Linux, but several sections show a Windows-first bias. Windows examples and instructions are presented before Linux equivalents, and Windows-specific tools and patterns (such as PowerShell and .NET in-process/isolated worker details) are more prominently featured. Some instructions, especially for Python, explicitly state lack of Windows support but do not provide alternative Linux guidance in the same section. The troubleshooting and verification steps reference Windows-centric tools and settings before Linux ones.
Recommendations
  • Present Windows and Linux instructions side-by-side or in parallel tabs, rather than Windows first.
  • Ensure all examples (especially CLI commands and portal steps) are provided for both Windows and Linux, even if the steps are similar.
  • Where Windows-only features or limitations exist (e.g., Python not supported on Windows), provide clear Linux alternatives and cross-reference them directly.
  • Reduce the prominence of Windows-specific tools (such as PowerShell) unless necessary, and highlight cross-platform tools (like Azure CLI) equally.
  • Add explicit troubleshooting steps for Linux environments, including log access and dependency management.
  • Review and balance language in notes and tips to avoid assuming Windows as the default platform.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific plans and behaviors are often mentioned first or exclusively, such as Consumption plan (Windows only) and Elastic Premium plan (Windows or Linux). PowerShell examples and features are highlighted, while Linux equivalents are less emphasized or appear later. Some configuration settings and deployment scenarios are described primarily for Windows, with Linux-specific guidance relegated to later sections. In the 'Mount file shares' section, both Azure CLI (Linux-friendly) and PowerShell (Windows-centric) examples are provided, but the CLI example is shown first, which is positive for Linux parity. However, elsewhere, Windows plans and tools are referenced before Linux, and some features (like Azure Files mounting) are noted as Linux-only but with limited cross-platform context.
Recommendations
  • Ensure all examples are provided for both Windows and Linux platforms, especially for deployment and configuration scenarios.
  • When mentioning plans or features, present Windows and Linux options together, or alternate which is listed first.
  • Add explicit Linux/macOS command-line examples (e.g., Bash, CLI) wherever PowerShell is shown.
  • Clarify which features are platform-specific and provide guidance or alternatives for the other platform.
  • Highlight Linux/macOS tooling and workflows (e.g., VS Code, Bash scripts) alongside Windows tools.
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-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally provides cross-platform instructions and examples, including explicit sections for Linux/macOS, Windows (bash), and Windows (Cmd) when relevant (e.g., Python virtual environment activation). However, there is a subtle Windows bias in the ordering of examples, with 'command prompt' and 'PowerShell' often mentioned before Linux terminals, and Windows-specific tools and patterns (such as 'func.exe', 'cmd', and PowerShell) are sometimes referenced or prioritized. The use of 'command prompt' and 'PowerShell' as default terms, and the inclusion of Windows-specific instructions before Linux equivalents in some places, indicate a mild Windows-first bias. All major steps are covered for Linux, but the ordering and terminology could be more neutral.
Recommendations
  • Standardize on 'terminal' as the primary term, with platform-specific clarifications as needed.
  • When presenting multiple platform instructions, consistently list Linux/macOS first, or group all platforms equally.
  • Avoid using Windows-specific tool names (e.g., 'func.exe') in generic instructions; use 'func' unless the extension is required.
  • Ensure that all code and command examples are present for both Linux and Windows, and that Linux examples are not omitted or placed after Windows ones.
  • Where possible, provide bash/zsh examples before Windows cmd/PowerShell, or present them in parallel tabs.
  • Review for any implicit assumptions of Windows environments (e.g., file paths, environment variable syntax) and provide cross-platform equivalents.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/dedicated-plan.md ...s/blob/main/articles/azure-functions/dedicated-plan.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by linking exclusively to the Windows-specific App Service pricing page and by referencing App Service plans in a way that prioritizes Windows terminology and resources. There are no explicit Linux or cross-platform examples, and the documentation does not mention Linux-specific considerations or provide parity in links or terminology.
Recommendations
  • Include links to both Windows and Linux App Service pricing pages, or use a platform-neutral pricing link.
  • Explicitly mention that App Service plans support both Windows and Linux, and highlight any differences or considerations for Linux users.
  • Provide examples or notes for Linux users where platform-specific behavior may differ (e.g., Always On, scaling, or custom images).
  • Review terminology to ensure it is platform-neutral and does not implicitly prioritize Windows.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/develop-python-worker-extensions.md ...es/azure-functions/develop-python-worker-extensions.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates mild Windows bias in a few areas. In the virtual environment activation section, Windows instructions (using Powershell) are presented alongside Linux, but the Windows command uses Powershell syntax (.venv\Scripts\Activate.ps1) rather than the more common cmd.exe syntax (.venv\Scripts\activate.bat). Additionally, the Windows instructions are present and explicit, but Linux instructions are not always given equal detail or context. The use of Visual Studio Code as a prerequisite is cross-platform, but no mention is made of Linux-specific editors or shell environments. Overall, the documentation is mostly neutral but does show a slight preference for Windows patterns in some command examples.
Recommendations
  • Provide both Windows (cmd.exe and Powershell) and Linux/macOS command examples wherever OS-specific instructions are needed.
  • Ensure Linux instructions are presented with equal detail and clarity as Windows instructions, including troubleshooting notes for common Linux issues.
  • Consider mentioning Linux-native editors (e.g., Vim, Nano) or shell environments in prerequisites, or clarify that Visual Studio Code is cross-platform.
  • Where possible, use OS-agnostic commands and highlight platform differences only when necessary.
  • Explicitly state that all steps are supported on Linux and macOS, and provide links to platform-specific documentation if available.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-code-constraints.md ...unctions/durable/durable-functions-code-constraints.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides code examples for multiple languages, including PowerShell, and references Windows-specific tools and patterns (e.g., PowerShell cmdlets like Get-Date, New-Guid). PowerShell is included as a first-class language tab alongside C#, JavaScript, Python, and Java, which is uncommon in cross-platform cloud documentation. The guidance for GUID/UUID generation and date/time APIs specifically mentions PowerShell cmdlets and .NET APIs, which are primarily relevant to Windows environments. There are no explicit Linux shell (e.g., Bash) examples or references, and the documentation does not mention Linux-specific tools or patterns.
Recommendations
  • Add Linux shell (e.g., Bash) examples where relevant, especially for scripting scenarios.
  • Clarify that PowerShell is available cross-platform, but also provide parity for Linux-native tools and patterns.
  • When referencing command-line tools, mention both Windows (PowerShell) and Linux (Bash, sh) equivalents.
  • Consider reordering or grouping language tabs so that Windows-specific languages/tools (PowerShell) do not appear to be prioritized over Linux-native options.
  • Explicitly state cross-platform support for all language examples, and provide guidance for Linux users where differences exist.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-create-portal.md ...e-functions/durable/durable-functions-create-portal.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows by exclusively referencing the Kudu console (which is Windows-centric in its UI and terminology) for package installation and file uploads. All examples for interacting with the Azure portal use Kudu's CMD interface, with no mention of Linux-native tools, Bash, or cross-platform alternatives. There are no examples or instructions for Linux or macOS users, nor is there guidance for using the Bash console or other platform-agnostic methods.
Recommendations
  • Include instructions and screenshots for using the Bash console in Kudu, which is available for Linux-based function apps.
  • Explicitly mention that Kudu is available for both Windows and Linux function apps, and clarify any differences in the interface or commands.
  • Provide alternative examples using Bash commands (e.g., using Bash instead of CMD in Kudu, or using Azure CLI for package installation and file uploads).
  • Add a note or section for Linux/macOS users, highlighting any platform-specific steps or differences.
  • Avoid using Windows-specific terminology (such as CMD) exclusively; instead, show both CMD and Bash options where applicable.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-configure-managed-identity.md ...urable/durable-functions-configure-managed-identity.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Microsoft-centric tools and workflows (Visual Studio, Visual Studio Code, Azure CLI) for local authentication, and by providing configuration steps and screenshots exclusively from the Azure portal (a web interface, but often associated with Windows workflows). There are no explicit Linux-specific examples, nor are cross-platform command-line alternatives (such as Bash or Linux-native tools) mentioned. The documentation does not provide parity for Linux users in terms of example commands, environment variable configuration, or role assignment workflows outside the Azure portal.
Recommendations
  • Include Linux-specific examples for local development, such as using Bash scripts or environment variables.
  • Mention and provide examples for using Azure CLI on Linux for role assignments and managed identity configuration.
  • Clarify that Visual Studio Code and Azure CLI are cross-platform, and provide explicit instructions for Linux users.
  • Add screenshots or terminal commands demonstrating configuration steps on Linux systems.
  • Reference Linux-native editors and workflows (e.g., Vim, nano, gedit) for editing configuration files.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-packages.md .../azure-functions/durable/durable-functions-packages.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
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 users before mentioning other platforms. PowerShell, another Windows-first technology, is given explicit mention and migration guidance, while Linux-specific tools, package managers, or examples are absent. There are no Linux-specific instructions, nor are Linux-first runtimes (e.g., Python, Node.js) given equal prominence or example depth.
Recommendations
  • Add explicit Linux usage examples, such as referencing package installation via pip (Python), npm (Node.js), or Maven (Java), including command-line instructions for Linux shells.
  • Provide parity in configuration instructions for non-.NET platforms, including details on how to configure storage providers for Python, Node.js, and Java.
  • Include a section or callout for Linux users, addressing common setup patterns, file locations, and environment differences.
  • Balance the order of presentation so that non-Windows runtimes (Python, Node.js, Java) are described with equal detail and not only after .NET.
  • If PowerShell is mentioned, also mention Bash or other Linux-native scripting environments where relevant.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-sub-orchestrations.md ...ctions/durable/durable-functions-sub-orchestrations.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides language examples for C#, JavaScript, Python, Java, and PowerShell. PowerShell is included as a first-class example, which is primarily a Windows-centric shell and scripting language. There is a specific note about PowerShell support and SDKs, but there are no equivalent notes or guidance for Bash, sh, or other Linux-native shells. No Linux-specific tools or patterns are mentioned. The inclusion of PowerShell as a main example and the absence of Linux shell examples or guidance indicates a Windows bias.
Recommendations
  • Add equivalent examples using Bash or other Linux-native shells if shell scripting examples are relevant.
  • If PowerShell is included due to its cross-platform support, clarify this and provide Linux installation guidance.
  • Include notes or guidance for Linux users, such as using Azure CLI or Bash for orchestration scripting, where applicable.
  • Balance PowerShell-specific notes with Linux shell or cross-platform scripting notes to avoid the perception of Windows bias.
GitHub Create Pull Request
← Previous Page 5 of 10 Next →