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 226-250 of 1023 flagged pages
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-develop-local.md ...in/articles/azure-functions/functions-develop-local.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Visual Studio (Windows-only) is listed first and described in detail for C# development, while Linux/macOS alternatives (VS Code, command line) are mentioned second. Windows-specific tools such as PowerShell and Visual Studio are referenced before cross-platform or Linux-native tools (e.g., curl, Bruno). PowerShell is featured as a recommended HTTP test tool, and Windows-centric patterns (e.g., Visual Studio project properties) are described, sometimes without Linux/macOS equivalents. However, the page does acknowledge Linux/macOS support for most environments and tools.
Recommendations
  • List cross-platform tools (VS Code, command line, curl) before Windows-only tools (Visual Studio, PowerShell) in tables and recommendations.
  • Provide explicit Linux/macOS equivalents for any Windows-specific instructions (e.g., project property configuration, PowerShell commands).
  • Include more examples using Linux-native tools (e.g., curl, bash) alongside or before Windows tools.
  • Clarify which tools are cross-platform and which are Windows-only in environment tables and tool lists.
  • Add links or references to Linux/macOS setup guides for Azure Functions development where appropriate.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-dotnet-class-library.md ...cles/azure-functions/functions-dotnet-class-library.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: Windows tools and patterns (Visual Studio, MSI installer, Windows paths) are mentioned before or exclusively compared to Linux equivalents; command examples are provided for Windows (cmd, PowerShell) but not for bash or Linux shells; references to Windows-specific dependencies (WindowsAzure.Storage) and file paths (e.g., %USERPROFILE%) are present; and ReadyToRun publishing is shown only for Windows targets. There is a lack of explicit Linux/macOS examples, instructions, or parity in tool usage and environment setup.
Recommendations
  • Add explicit Linux/macOS instructions and examples alongside Windows ones, especially for command-line operations, environment setup, and project publishing.
  • Provide bash/zsh command examples for package installation and Azure Functions Core Tools usage, not just cmd/PowerShell.
  • Include Linux/macOS file paths and environment variable references (e.g., $HOME/.local/Azure.Functions.Cli) where Windows paths are mentioned.
  • Show ReadyToRun publishing examples for Linux (e.g., <RuntimeIdentifier>linux-x64</RuntimeIdentifier>) and discuss cross-platform deployment considerations.
  • Mention cross-platform editors (e.g., JetBrains Rider) and clarify Visual Studio Code usage on Linux/macOS.
  • Review dependency references (e.g., WindowsAzure.Storage) and clarify their applicability or alternatives for non-Windows environments.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-event-grid-blob-trigger.md ...s/azure-functions/functions-event-grid-blob-trigger.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The tutorial demonstrates a bias toward Windows environments by exclusively using Visual Studio Code and its Azure extensions for all steps, including storage emulation (Azurite), resource creation, and deployment. All CLI instructions and screenshots are tailored to VS Code, which is most commonly used on Windows, and there is no mention of Linux-native tools or command-line alternatives (such as Azure CLI, Bash scripts, or Linux file upload methods). The documentation does not provide parity for Linux users who may prefer terminal-based workflows or alternative editors.
Recommendations
  • Add equivalent instructions using Azure CLI and Bash for all resource creation, deployment, and file upload steps.
  • Include examples and screenshots for Linux environments, such as using the terminal, file system navigation, and storage emulation.
  • Mention and provide steps for using Azurite from the command line (npm package) rather than only the VS Code extension.
  • Offer instructions for alternative editors (e.g., Vim, VS Codium) and terminal workflows, especially for local development and debugging.
  • Clarify that all steps can be performed on Linux and macOS, and explicitly note any platform-specific limitations or differences.
  • Provide links to official Azure CLI documentation for each relevant step.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-deployment-technologies.md ...s/azure-functions/functions-deployment-technologies.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a Windows bias by frequently mentioning Windows-specific deployment options (such as FTPS, Local Git, and Source Control) as 'Windows-only', and by listing Windows options before Linux equivalents in tables and explanations. Examples and instructions often reference Visual Studio and Windows-centric tools, with less emphasis or detail on Linux workflows. Some deployment methods are described as default or recommended for Windows, while Linux options are presented as exceptions or with additional manual steps. There is a lack of parity in example commands and tool coverage for Linux users.
Recommendations
  • Provide Linux-specific examples and workflows alongside Windows instructions, especially for deployment methods like FTPS, Local Git, and Source Control.
  • Ensure tables and lists present Windows and Linux options with equal prominence, or group by OS to clarify availability.
  • Include more detailed guidance for Linux users, such as using Bash, Linux-native tools, and troubleshooting common Linux deployment issues.
  • Highlight cross-platform tools (e.g., Azure CLI, Core Tools) with explicit instructions for both Windows and Linux environments.
  • Avoid describing Windows methods as the default or recommended without noting Linux equivalents or alternatives.
  • Add notes or links for Linux users where features are Windows-only, and suggest alternative approaches where possible.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-develop-vs.md .../main/articles/azure-functions/functions-develop-vs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page is heavily focused on Windows development using Visual Studio, with all examples, instructions, and screenshots tailored to the Windows environment. There is no mention of Linux or cross-platform alternatives for project creation, debugging, or publishing. The use of Visual Studio-specific features, dialogs, and tooling (such as Package Manager Console and PowerShell commands) further reinforces a Windows-centric approach. Remote debugging is explicitly stated as only supported on Windows, and there are no Linux or VS Code instructions provided.
Recommendations
  • Add equivalent instructions and examples for developing Azure Functions using VS Code and/or command-line tools on Linux and macOS.
  • Provide cross-platform steps for project creation, dependency management (e.g., using dotnet CLI instead of Visual Studio dialogs), and local development.
  • Include screenshots and workflow descriptions for Linux/macOS environments, such as using Azure Functions Core Tools and VS Code.
  • Clarify which features are Windows-only and suggest alternatives for non-Windows users.
  • Offer remote debugging guidance for Linux-hosted function apps, or explicitly state limitations and workarounds.
  • Replace or supplement PowerShell/Package Manager Console commands with dotnet CLI equivalents.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-how-to-azure-devops.md ...icles/azure-functions/functions-how-to-azure-devops.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-based examples (e.g., 'windows-latest' agent pools) are presented first for C# and PowerShell, and the default appType for deployment is Windows. PowerShell is included as a first-class language tab, and Windows-specific instructions/tools are referenced before Linux equivalents. While Linux examples are present (especially for JavaScript, Python, and Java), Windows options are often the default or primary focus, and some language/platforms (e.g., PowerShell) are only shown with Windows agents.
Recommendations
  • Present Linux and Windows examples side-by-side or in parallel, rather than Windows first.
  • For languages like C#, provide both 'windows-latest' and 'ubuntu-latest' agent pool examples, with notes on when each is appropriate.
  • For PowerShell, clarify Linux support (if any) or explain the Windows-only limitation.
  • When referencing deployment tasks, avoid stating Windows as the default; instead, highlight both options equally.
  • Add explicit notes or links for Linux tooling and troubleshooting, especially for .NET and PowerShell.
  • Ensure all language tabs (including PowerShell) mention platform support and limitations.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-how-to-github-actions.md ...les/azure-functions/functions-how-to-github-actions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page generally provides parity between Windows and Linux, offering workflow templates and examples for both platforms and most languages. However, there is a subtle Windows bias: Windows is consistently listed first in tabbed examples and instructions, and Windows-specific tools and terminology (such as PowerShell and 'windows-latest') are prominent. Additionally, PowerShell examples are only relevant for Windows, but Linux PowerShell templates are included for completeness. The Azure CLI instructions are platform-neutral, but the overall flow and ordering tend to prioritize Windows over Linux.
Recommendations
  • Alternate the order of Windows and Linux examples or present them side-by-side to avoid implying priority.
  • Explicitly state platform parity in introductory sections to reassure Linux users.
  • Where possible, highlight Linux-specific considerations or advantages, especially as some features (e.g., Python support) are Linux-only.
  • Include notes about platform limitations (such as planned retirement of Linux Consumption plan) in both Windows and Linux sections.
  • Ensure that CLI instructions and screenshots show both Windows and Linux terminal environments.
  • Review tab naming and ordering to avoid always listing Windows first.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-how-to-use-azure-function-app-settings.md ...ns/functions-how-to-use-azure-function-app-settings.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias in several ways: Windows and PowerShell tools are consistently presented alongside or before Linux alternatives, with many examples and features described as Windows-only or with limited Linux support. Some features (like Kudu, App Service editor, and console access) are unavailable or unsupported on Linux. Migration scenarios and in-portal editing are focused on Windows, with Linux options described as limited or deprecated. There is a lack of Linux-specific command examples, and Linux limitations are often highlighted without offering equivalent alternatives.
Recommendations
  • Provide Linux-specific examples and workflows for all CLI and PowerShell commands, including explicit bash or shell usage where relevant.
  • Clearly indicate Linux support status for each feature, and offer alternative Linux-compatible tools or approaches when Windows-only tools are mentioned (e.g., alternatives to Kudu, App Service editor, or Windows console).
  • Add parity for plan migration scenarios, including explicit instructions for Linux-based function apps and clarify any limitations with actionable alternatives.
  • Where features are unavailable on Linux, suggest best practices or workarounds for Linux users (e.g., using local development, deployment via Core Tools, or SSH access).
  • Ensure that documentation does not default to Windows-first language or examples, and strive for equal prominence of Linux and Windows throughout the page.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-infrastructure-as-code.md ...es/azure-functions/functions-infrastructure-as-code.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Examples Prominent Powershell Heavy
Summary
The documentation provides both Windows and Linux examples for most deployment scenarios, but Windows examples are consistently listed first and often described before Linux equivalents. In several places, Windows-specific settings and deployment instructions are highlighted or given precedence. PowerShell is featured as a primary deployment method, with less emphasis on Linux-native tools or shell scripts. While Linux parity is generally good, the ordering and prominence of Windows content may suggest a subtle bias toward Windows users.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
  • Where PowerShell is shown, also provide equivalent Bash/Azure CLI scripts for Linux users.
  • Ensure that all deployment instructions and code samples are equally detailed for both Windows and Linux, including troubleshooting and validation steps.
  • Highlight cross-platform tools (like Azure CLI) as the default or preferred method, with platform-specific tools as secondary options.
  • Review headings and introductory text to ensure Linux is mentioned as prominently as Windows, especially in summary tables and prerequisites.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-identity-access-azure-sql-with-managed-identity.md ...ctions-identity-access-azure-sql-with-managed-identity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. Examples for enabling Microsoft Entra authentication reference PowerShell and Azure CLI, but the PowerShell option is mentioned before CLI, and no explicit Linux shell examples are provided. The SQL access step uses sqlcmd in Cloud Shell, which is cross-platform, but there are no examples for native Linux SQL tools (e.g., mssql-cli, isql, or ODBC). The instructions for enabling managed identity focus on the Azure Portal and PowerShell, with CLI as a secondary option. There is no mention of Linux-specific patterns, nor are Linux command-line examples or troubleshooting tips included.
Recommendations
  • Provide explicit Linux shell examples for all command-line instructions, including Azure CLI and SQL access.
  • Mention and demonstrate alternative SQL tools available on Linux (e.g., mssql-cli, isql) for connecting to Azure SQL.
  • Ensure Azure CLI instructions are presented before or alongside PowerShell instructions to avoid Windows-first ordering.
  • Add troubleshooting notes or tips for Linux environments, such as package installation or authentication differences.
  • Clarify that all CLI commands work on Linux, macOS, and Windows, and provide platform-agnostic guidance where possible.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-networking-options.md ...ticles/azure-functions/functions-networking-options.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 signs of Windows bias. Hybrid Connections are explicitly stated to be supported only for Windows, with Linux apps not supported. In automation and configuration examples, Azure PowerShell is presented alongside Azure CLI, but PowerShell is a Windows-centric tool. The subnet sizing recommendations for Elastic Premium plans mention Windows before Linux, and the minimum subnet size for Windows is described first. There are no Linux-specific configuration or troubleshooting examples, and the documentation does not provide parity for Linux users in areas where features are Windows-only or where Linux support is limited.
Recommendations
  • Clearly indicate feature parity and limitations for Linux throughout the documentation, especially where features are Windows-only (e.g., Hybrid Connections).
  • Provide Linux-specific examples and instructions, especially for automation and configuration (e.g., bash scripts, Azure CLI, or cross-platform tools).
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux users.
  • Where subnet sizing or other platform-specific recommendations are given, present Linux and Windows options side-by-side, rather than Windows first.
  • Add troubleshooting steps and tools relevant to Linux environments.
  • Explicitly state when a feature is not available on Linux, and suggest alternatives or workarounds if possible.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-monitoring.md .../main/articles/azure-functions/functions-monitoring.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows/App Service features and examples, such as built-in log streaming, which is noted as unsupported for Linux Consumption plans. There is a lack of Linux-specific guidance or parity in examples, and Windows/App Service tools are mentioned without equivalent Linux alternatives or troubleshooting steps. Performance Counters are noted as unsupported on Linux, but no Linux alternatives are suggested.
Recommendations
  • Provide Linux-specific examples and troubleshooting steps for monitoring and log streaming, especially for features not supported on Linux (e.g., suggest alternatives for Performance Counters and log streaming).
  • Explicitly mention cross-platform differences earlier in the documentation and link to Linux-specific guides where available.
  • Include parity tables or sections that clarify which features are available on Windows vs. Linux, and offer workarounds or alternatives for Linux users.
  • When referencing tools or patterns (e.g., App Service log streaming), also mention or link to equivalent Linux-native tools or commands (such as using Azure CLI, Kudu, or custom logging solutions).
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-premium-plan.md ...ain/articles/azure-functions/functions-premium-plan.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways. Examples and instructions for configuring Azure Functions Premium plan settings are consistently provided for Azure PowerShell (a Windows-centric tool) alongside Azure CLI, but there are no Linux-specific shell examples (e.g., bash scripts) or references to Linux-native tools. The migration section explicitly states that migration between plans is supported only on Windows, with no Linux support. In several places, Windows is mentioned first or exclusively, and there is a lack of parity in guidance for Linux users, especially regarding tooling and operational patterns.
Recommendations
  • Provide Linux-specific examples and instructions, such as bash scripts or references to Linux-native tools where applicable.
  • Clarify which commands and features are cross-platform, and explicitly note any Windows-only limitations.
  • Where PowerShell is used, offer equivalent bash/CLI examples for Linux users, or clarify that Azure CLI is fully supported on Linux.
  • In migration scenarios, offer guidance or alternatives for Linux users, or clearly state the roadmap for Linux support.
  • Ensure that references to operating systems are balanced and do not consistently prioritize Windows over Linux.
  • Add troubleshooting and configuration notes specific to Linux environments, especially for container deployments and app settings.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-reference.md ...b/main/articles/azure-functions/functions-reference.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools like Visual Studio are mentioned first and more prominently in C# sections, and PowerShell is included as a first-class language. There is a lack of explicit mention of Linux-specific tools or workflows, and the command prompt references are ambiguous (could refer to Windows CMD or generic shell). Visual Studio is prioritized over cross-platform editors like VS Code, and there are no examples or guidance for Linux-specific development environments or shell usage.
Recommendations
  • Explicitly mention Linux and macOS compatibility for all tools and workflows, especially in quickstart and development sections.
  • Provide examples using Linux shells (bash/zsh) and clarify when 'command prompt' refers to cross-platform CLI usage.
  • Include Linux-native editors (e.g., JetBrains Rider, Vim) in tool recommendations where appropriate.
  • Add parity for Linux-specific setup instructions, such as package installation, environment variable configuration, and file paths.
  • Ensure that Visual Studio is not always listed first, and that VS Code or CLI options are equally highlighted for all languages.
  • Clarify PowerShell usage on Linux/macOS, or provide bash equivalents where relevant.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-scale.md .../blob/main/articles/azure-functions/functions-scale.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Windows hosting options and features are frequently mentioned first, especially in the Consumption plan, which is described as 'Windows - GA' while Linux is marked as 'Retired.' Windows-specific dependencies (such as PowerShell modules and the full .NET Framework) are highlighted as reasons to choose the Consumption plan, with no equivalent Linux-specific examples or guidance. Pricing links for Dedicated plans point to Windows App Service rates, and there is a lack of Linux-focused usage scenarios or examples. The documentation does not provide parity in examples or guidance for Linux users, and Windows-centric language and tooling are prioritized.
Recommendations
  • Provide Linux-specific usage scenarios and examples, such as dependencies on Linux-only runtimes or tools (e.g., Python, Node.js, Bash scripts).
  • List Linux and Windows hosting options in parallel, rather than prioritizing Windows in tables and descriptions.
  • Include guidance for Linux users migrating from the retired Linux Consumption plan, with clear alternatives and migration steps.
  • Reference Linux pricing pages and documentation alongside Windows equivalents for Dedicated plans.
  • Highlight Linux container support and advanced Linux features where applicable, and provide links to Linux-focused documentation.
  • Avoid framing Windows-specific features (such as PowerShell modules) as the default or primary use case for Azure Functions.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/how-to-create-function-vs-code.md ...cles/azure-functions/how-to-create-function-vs-code.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias. Windows-specific tools and patterns are referenced, such as PowerShell and instructions for setting environment variables in Windows syntax. Troubleshooting guidance mentions Windows-specific issues before Linux equivalents. PowerShell is included as a first-class language, and some SDK installation links default to Windows. However, Linux and macOS are also supported and referenced, especially for Java, Go, and Rust, and most instructions are cross-platform.
Recommendations
  • Ensure all tool installation links (e.g., PowerShell, .NET) include Linux and macOS options, not just Windows.
  • When showing environment variable setting commands (e.g., for Go cross-compilation), present Linux/macOS syntax before or alongside Windows syntax.
  • In troubleshooting tables, mention Linux/macOS issues and solutions with equal prominence to Windows.
  • For PowerShell, clarify that it runs cross-platform and provide installation instructions for Linux/macOS.
  • Review all language-specific prerequisites to ensure parity in instructions and links for all platforms.
  • Explicitly state platform support in each section, and avoid defaulting to Windows-specific instructions unless necessary.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/manage-connections.md ...ob/main/articles/azure-functions/manage-connections.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows/.NET environments. All code examples for HTTP requests, Cosmos DB, and SQL connections are provided for C# (.NET) and JavaScript, with C# examples presented first. The SQL section exclusively references .NET's SqlClient and ADO.NET, with no mention of Linux-native database drivers or connection management for other platforms. There are references to configuration files and patterns (such as local.settings.json and Application settings) that are more common in Windows-centric development. No Linux-specific tools, shell commands, or configuration patterns are discussed, and there are no examples for Python or other languages popular on Linux.
Recommendations
  • Add code examples for Python (using requests, Azure SDKs, and database drivers like pyodbc or SQLAlchemy), which are widely used on Linux.
  • Include guidance for Linux-native database drivers and connection management, such as using environment variables for connection strings.
  • Present examples for multiple languages in parallel, rather than always listing C#/.NET first.
  • Reference Linux configuration patterns (e.g., .env files, systemd environment variables) alongside Windows-centric settings.
  • Mention cross-platform tools for monitoring and troubleshooting connections, such as using Linux command-line utilities (netstat, lsof) in addition to Application Insights.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/how-to-create-function-azure-cli.md ...es/azure-functions/how-to-create-function-azure-cli.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates some Windows bias, particularly in the Java section, where command examples are provided for PowerShell and Cmd (Windows shells) alongside Bash, and instructions reference Windows-style environment variables (JAVA_HOME). The project file paths use backslashes (\), which are Windows-specific. There is a lack of explicit Linux shell examples outside of Bash, and Windows tools (Cmd, PowerShell) are mentioned before Linux equivalents. The overall structure assumes familiarity with Windows conventions and tools, with less emphasis on Linux-specific patterns.
Recommendations
  • Provide explicit Linux shell examples (e.g., Bash, Zsh) wherever PowerShell or Cmd examples are given.
  • Use forward slashes (/) for file paths or clarify path differences between Windows and Linux.
  • Mention Linux environment variable conventions (e.g., export JAVA_HOME=/path/to/jdk) alongside Windows instructions.
  • Ensure that all command-line instructions work seamlessly on Linux, and note any platform-specific differences.
  • List Bash/Linux examples before Windows-specific ones to avoid implicit prioritization.
  • Include troubleshooting notes for common Linux issues (e.g., permissions, dependency installation).
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/ip-addresses.md ...ocs/blob/main/articles/azure-functions/ip-addresses.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides command-line examples for Azure CLI and Azure PowerShell, but does not include Linux-specific shell examples (e.g., Bash scripts) or mention Linux tools where relevant. PowerShell examples are given equal prominence to Azure CLI, and in some cases, Windows-centric tools (like PowerShell) are presented without Linux alternatives. The documentation also does not clarify that Azure CLI commands are cross-platform, nor does it provide guidance for Linux users in sections where Windows tools are referenced.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash shell examples where appropriate.
  • When referencing tools like PowerShell, clarify that PowerShell Core is available cross-platform, or provide equivalent Bash or shell script examples.
  • In sections that use Windows-centric terminology or tools (e.g., PowerShell), add Linux-native alternatives or note that the same steps can be performed on Linux.
  • For DNS lookups, mention both nslookup and dig, as dig is more common on Linux systems.
  • Review all command examples to ensure Linux users are equally supported and not implicitly deprioritized.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/migrate-dotnet-to-isolated-model.md ...es/azure-functions/migrate-dotnet-to-isolated-model.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively providing Azure PowerShell scripts for app discovery, referencing Visual Studio and VS Code (primarily Windows tools), and omitting equivalent Linux shell (Bash/CLI) examples. The initial migration steps and tooling recommendations are Windows-centric, with no mention of Linux-native workflows or cross-platform alternatives. This may hinder Linux users or those working in non-Windows environments from following the migration process seamlessly.
Recommendations
  • Provide Azure CLI (az) and Bash script equivalents alongside PowerShell examples for identifying and managing function apps.
  • Explicitly mention cross-platform compatibility for tools like Azure Functions Core Tools, and provide installation and usage instructions for Linux/macOS.
  • Include guidance for common Linux editors (e.g., Vim, Nano) and CI/CD workflows that do not rely on Visual Studio or VS Code.
  • Add notes or sections highlighting any platform-specific differences in migration steps, especially for local development and deployment.
  • Ensure all code and configuration examples are platform-agnostic or provide variants for both Windows and Linux environments.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/migrate-version-3-version-4.md ...rticles/azure-functions/migrate-version-3-version-4.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only a PowerShell script for identifying function apps to migrate, referencing Azure PowerShell multiple times, and not offering equivalent Bash, Azure CLI, or Linux-native command examples. The initial migration steps and tooling references (such as .NET Upgrade Assistant and Visual Studio) also implicitly assume a Windows environment, with no mention of Linux or cross-platform alternatives. There are no explicit Linux or Bash examples, and Linux-specific considerations are only mentioned in passing (e.g., timeout enforcement), not in migration steps or tooling.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts alongside PowerShell examples for identifying and managing function apps, ensuring Linux users have clear guidance.
  • When referencing tools like Visual Studio or .NET Upgrade Assistant, mention cross-platform alternatives (e.g., Visual Studio Code, JetBrains Rider, or CLI-based workflows) and clarify their compatibility with Linux.
  • Explicitly include Linux-specific instructions or notes where relevant, such as differences in local development, deployment, or environment setup.
  • Ensure that all code and command-line examples are presented in both Windows (PowerShell) and Linux (Bash/Azure CLI) formats, or at least indicate how to adapt them.
  • Highlight any Linux-specific migration considerations in a dedicated section or as inline notes to ensure parity and visibility.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/recover-python-functions.md ...n/articles/azure-functions/recover-python-functions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 mild Windows bias. In several troubleshooting sections, Windows/Powershell commands are presented before their Linux equivalents (e.g., checking Python bitness, deleting cache directories). Windows-specific tools and patterns (PowerShell, 'py' launcher) are referenced, sometimes with more detail than Linux alternatives. Some examples and instructions are Windows-first or Windows-heavy, and in a few cases, Linux examples are less emphasized or missing.
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which platform is shown first to avoid Windows-first bias.
  • Ensure all command-line instructions are provided for both Linux (bash/sh) and Windows (PowerShell/CMD), with equal detail and prominence.
  • Where Windows-specific tools (e.g., 'py' launcher, PowerShell) are mentioned, provide equivalent Linux alternatives (e.g., 'python3', bash commands) and clarify platform applicability.
  • Explicitly state when instructions or tools are platform-specific, and offer cross-platform alternatives where possible.
  • Review all troubleshooting steps to ensure Linux users are equally supported, especially given Azure Functions Python runs on Linux at runtime.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/migrate-version-1-version-4.md ...rticles/azure-functions/migrate-version-1-version-4.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page displays Windows bias primarily through its use of PowerShell as the only example for identifying function apps to migrate, and by referencing Windows-centric tools and workflows (such as Visual Studio and PowerShell) without providing equivalent Linux or cross-platform alternatives (e.g., Bash, Azure CLI). The initial migration steps and scripting guidance are Windows-first, which may hinder Linux users or those on other platforms. There are no Linux-specific examples or parity in tooling instructions for key migration tasks.
Recommendations
  • Provide equivalent Azure CLI and/or Bash script examples for identifying function apps to migrate, alongside the PowerShell example.
  • Mention cross-platform tools (such as VS Code, Azure CLI, and Functions Core Tools) in migration and deployment instructions, not just Visual Studio.
  • Ensure that scripting and automation guidance is platform-neutral or includes both Windows and Linux alternatives.
  • Add explicit notes or sections for Linux/macOS users, especially for common tasks like local development, deployment, and configuration.
  • Review all code and command examples to ensure Linux parity and avoid Windows-first ordering.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/migration/migrate-plan-consumption-to-flex.md ...unctions/migration/migrate-plan-consumption-to-flex.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides detailed migration steps for both Linux and Windows Azure Functions Consumption plan apps, but there is a noticeable Windows bias. Windows (and Windows-style tools) are often presented first, with more exhaustive step-by-step instructions, especially in the 'platform-windows' pivots. Many CLI examples and scripts use Windows-centric patterns (e.g., PowerShell/bash scripts with az CLI, references to Windows-specific storage/file share settings). The Linux migration process is described as more automated (via az functionapp flex-migration), but the Windows process is more manual and verbose, with more granular configuration steps. In some sections, Linux examples are missing or less detailed, and Windows tools and patterns (such as file share locations, deployment slots, and authentication) are described in greater depth or appear before their Linux equivalents.
Recommendations
  • Ensure Linux and Windows sections are equally detailed, especially in manual migration steps. For example, provide Linux equivalents for all CLI scripts and portal walkthroughs.
  • Avoid presenting Windows-first in pivoted sections; alternate the order or explicitly state parity.
  • Where Windows-specific tools or patterns are described (e.g., file share locations, deployment slots), provide clear Linux alternatives or note differences up-front.
  • Expand Linux migration guidance to include troubleshooting, manual configuration, and recovery steps at the same level of detail as Windows.
  • Audit all CLI and script examples for OS-specific assumptions, and provide Linux shell (bash/zsh) and Windows PowerShell versions where appropriate.
  • Add a summary table comparing migration steps and requirements for both platforms, highlighting any differences or limitations.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/scenario-custom-remote-mcp-server.md ...s/azure-functions/scenario-custom-remote-mcp-server.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides both Linux/macOS (bash) and Windows (PowerShell) examples for key deployment steps, but the Windows/PowerShell script is given equal prominence and detail. There is a slight Windows bias in the explicit mention of PowerShell and Windows-specific instructions, and the historical presence of PowerShell prerequisites (even if commented out) suggests a tendency to prioritize Windows tooling. Visual Studio Code is used as the primary editor, which is cross-platform, but the workflow and instructions are tailored to a Windows-centric developer experience, especially in scripting and command palette usage.
Recommendations
  • Ensure Linux/macOS instructions are always presented before or alongside Windows instructions, not after.
  • Where possible, use generic shell commands and avoid Windows-specific scripting unless absolutely necessary.
  • Explicitly mention that all steps are supported and tested on Linux, macOS, and Windows, and provide troubleshooting tips for non-Windows platforms.
  • If PowerShell is referenced, also provide equivalent bash/zsh commands for Linux/macOS users.
  • Highlight any platform-specific prerequisites or limitations up front, and provide links to platform-specific setup guides.
  • Consider adding screenshots or terminal output examples from Linux/macOS environments to balance the visual representation.
GitHub Create Pull Request
← Previous Page 10 of 41 Next →