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 251-275 of 1023 flagged pages
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/scenario-blob-storage-events.md ...ticles/azure-functions/scenario-blob-storage-events.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 moderate Windows bias. Windows-specific instructions (such as PowerShell examples and references to func.exe) are present, and Windows activation commands are listed before Linux equivalents in some sections. Visual Studio Code and its command palette are emphasized, which is more common in Windows workflows. There is also a reliance on Windows-centric patterns (e.g., references to 'cmd', 'func.exe', and PowerShell modules), and troubleshooting advice is focused on Windows-specific issues (such as default terminal settings in VS Code). However, Linux/macOS instructions are present for Python environments and Azurite usage, and most CLI commands are cross-platform.
Recommendations
  • Ensure Linux/macOS instructions are always presented alongside Windows instructions, and in some cases, consider listing Linux/macOS first.
  • Avoid references to Windows-specific executables (e.g., func.exe) unless necessary; use generic terms like 'function host process'.
  • Provide troubleshooting advice for Linux/macOS environments, not just Windows (e.g., VS Code terminal settings for bash/zsh).
  • Include explicit Linux/macOS examples for all languages, not just Python (e.g., virtual environment activation for Node.js, Java, etc.).
  • Where PowerShell is mentioned, also mention Bash or other Linux shell equivalents for scripting and automation.
  • Clarify that Visual Studio Code is cross-platform and provide alternative instructions for developers using other editors or terminal environments.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/scenario-database-changes-azure-cosmosdb.md ...-functions/scenario-database-changes-azure-cosmosdb.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 demonstrates Windows bias in several ways: Windows/Powershell commands and tools are often presented first or exclusively, such as the use of 'pwsh' and 'Set-ExecutionPolicy' for script permissions, while Linux/macOS equivalents are less emphasized. Troubleshooting advice is Windows-centric (e.g., warning about WSL Bash in VS Code), and some examples or code snippets (e.g., Powershell) are referenced but not provided for Linux. There is limited parity in step-by-step guidance for Linux users, and Windows-specific patterns (like func.exe, Windows command prompt) are mentioned more prominently.
Recommendations
  • Present Linux/macOS and Windows instructions side-by-side or in parallel tabs, ensuring equal prominence.
  • Provide explicit Linux/macOS troubleshooting tips (e.g., for shell/terminal issues in VS Code) alongside Windows advice.
  • Ensure all code and script examples have both Windows and Linux/macOS versions, including permissions and execution steps.
  • Avoid referencing Windows tools (e.g., func.exe, pwsh) without mentioning or providing Linux/macOS equivalents.
  • Review and update any language or instructions that assume a Windows environment by default.
  • Include guidance for common Linux/macOS environments (e.g., bash, zsh, terminal settings) in all relevant sections.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/set-runtime-version.md ...b/main/articles/azure-functions/set-runtime-version.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 demonstrates a moderate Windows bias. Windows and PowerShell examples are consistently present and sometimes appear before or with more detail than Linux equivalents. PowerShell cmdlets are provided for both viewing and updating settings, while Linux users are directed to use Azure CLI only. Some features (such as pinning via portal or PowerShell) are explicitly unavailable for Linux, but this is not always highlighted early. There is more guidance and tooling for Windows users, and Linux instructions sometimes require support intervention or lack parity (e.g., no portal/PowerShell support for linuxFxVersion).
Recommendations
  • Ensure Linux instructions are presented with equal prominence and detail as Windows instructions, including in the order of examples.
  • Provide Linux-specific examples for all major workflows, including viewing and updating settings, and clarify limitations up front.
  • Where PowerShell is used for Windows, consider providing Bash or shell script equivalents for Linux users.
  • Expand portal instructions to clarify what is and isn't supported for Linux, and offer alternative workflows where portal/PowerShell are unavailable.
  • Add a summary table comparing feature parity between Windows and Linux to help users quickly understand differences.
  • Highlight any limitations for Linux (such as lack of portal/PowerShell support for linuxFxVersion) at the beginning of the relevant sections.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/scenario-database-changes-azure-sqldb.md ...ure-functions/scenario-database-changes-azure-sqldb.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 documentation page demonstrates a bias toward Windows environments by exclusively using Visual Studio Code and its extensions (such as the SQL Server extension), and by referencing workflows and tools that are most commonly used on Windows. There are no examples or guidance for Linux-native tools (e.g., sqlcmd, Azure Data Studio, or command-line SQL clients), nor are alternative Linux-friendly workflows mentioned. The instructions assume the use of GUI tools and patterns typical of Windows development environments, with no parity for Linux command-line or non-VS Code scenarios.
Recommendations
  • Add explicit instructions and examples for connecting to Azure SQL Database using Linux-native tools such as sqlcmd, Azure Data Studio, or psql (for PostgreSQL).
  • Include command-line alternatives for all steps that currently rely on Visual Studio Code GUI features, such as running azd commands and connecting to the database.
  • Mention installation and usage of Azure Functions Core Tools on Linux, including any prerequisites or differences.
  • Provide troubleshooting notes or links for common Linux issues (e.g., authentication, environment variables, file permissions).
  • Ensure that all code and deployment steps are demonstrated in both GUI and CLI contexts, and clarify that the azd CLI and Azure Functions Core Tools are cross-platform.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/storage-considerations.md ...ain/articles/azure-functions/storage-considerations.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: Windows hosting plans and behaviors are mentioned before Linux equivalents, PowerShell examples and references are prominent (including managed dependencies in PowerShell), and some configuration settings are described primarily in the context of Windows. Linux-specific guidance and examples are limited, and in some cases, Linux instructions are presented after Windows or as exceptions. There are also references to Windows-only features and tools, such as Azure Files usage in Consumption plans (Windows only), and PowerShell commands are given equal or greater prominence than CLI examples.
Recommendations
  • Ensure Linux hosting plans and behaviors are described with equal prominence and clarity as Windows equivalents.
  • Provide Linux-specific examples and instructions wherever Windows/Powershell examples are given, especially for deployment, configuration, and mounting storage.
  • When referencing tools, mention cross-platform options (e.g., Azure CLI, Bash scripts) before or alongside Windows-specific tools like PowerShell.
  • Clarify which features and settings apply to Linux, Windows, or both, and avoid presenting Windows as the default or primary platform.
  • Expand documentation on Linux-specific scenarios, such as mounting file shares, deployment without Azure Files, and troubleshooting.
  • Where possible, include Bash or shell script examples for Linux users in addition to PowerShell.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/update-language-versions.md ...n/articles/azure-functions/update-language-versions.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 demonstrates a Windows-first approach in several areas: Windows instructions and tabs are consistently presented before Linux equivalents, and some features (such as Python on Windows) are explicitly unsupported, with users redirected to Linux. The use of Azure CLI is cross-platform, but the documentation often refers to Windows-specific tools, settings, and patterns first. There are also sections where Linux examples are only provided as a secondary option or are missing entirely for certain languages. PowerShell is treated as a first-class language, with specific pivots and examples, reinforcing a Windows-centric perspective.
Recommendations
  • Present Linux and Windows instructions in parallel, or default to Linux-first where appropriate, especially for languages more commonly used on Linux (e.g., Python, Node.js).
  • Ensure that all examples and instructions are provided for both Windows and Linux, even if certain features are unsupported, with clear explanations and alternatives.
  • Avoid language in the documentation that assumes Windows as the default or primary OS; instead, use neutral phrasing or clarify when instructions are OS-specific.
  • Where PowerShell is used as an example, provide equivalent Bash or shell script examples for Linux users.
  • Highlight any feature parity gaps and provide workarounds or timelines for Linux support where possible.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-webjobs-sdk.md ...ure-functions/durable/durable-functions-webjobs-sdk.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 a strong Windows bias. It consistently presents Windows/Visual Studio as the default development environment, provides only PowerShell/NuGet Package Manager Console commands for package installation, and references Windows-specific tools (e.g., Storage Emulator, Visual Studio project templates) without offering Linux alternatives or parity. There are no examples or instructions for Linux users, such as using dotnet CLI, Bash, or VS Code workflows. The guidance for creating and running projects is tailored to Windows, and Linux development scenarios are not addressed.
Recommendations
  • Provide equivalent instructions for Linux users, such as using the dotnet CLI to create and manage projects.
  • Include Bash or shell commands for installing NuGet packages, in addition to PowerShell examples.
  • Mention and provide guidance for Linux-compatible storage emulators (e.g., Azurite) and how to run them on Linux/macOS.
  • Offer instructions for using Visual Studio Code or other cross-platform editors, with steps specific to Linux/macOS.
  • Avoid presenting Windows tools and workflows first or exclusively; ensure Linux options are given equal prominence.
  • Add a dedicated section or callouts for cross-platform development, highlighting any differences or additional steps required for Linux/macOS.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-app-settings.md ...ain/articles/azure-functions/functions-app-settings.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates some Windows bias, including presenting Windows-specific details or examples before Linux equivalents, referencing Windows-only settings and tools, and providing more extensive coverage of PowerShell-related configuration. Some settings and examples are either Windows-only or lack Linux parity, and guidance for Linux users is sometimes less prominent or missing.
Recommendations
  • Ensure all examples and configuration settings are presented with both Windows and Linux equivalents, especially for environment variables, file paths, and tooling.
  • Where settings are OS-specific (e.g., WEBSITE_NODE_DEFAULT_VERSION is Windows-only), clearly mark them and provide Linux alternatives or note the Linux behavior.
  • For PowerShell-heavy sections, add equivalent guidance for Bash or other Linux-native scripting environments where possible.
  • When referencing tools (e.g., Azure PowerShell), ensure Azure CLI examples are provided and presented with equal prominence.
  • Review the ordering of OS-specific information to avoid presenting Windows-first unless there is a technical reason.
  • Expand documentation for Linux-specific deployment, troubleshooting, and configuration scenarios to match the depth of Windows coverage.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/disable-function.md ...blob/main/articles/azure-functions/disable-function.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides examples for disabling Azure Functions using the Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the PowerShell examples and references are Windows-centric, and PowerShell is presented as a primary method alongside CLI. There are no explicit Linux shell (e.g., Bash) or scripting examples, nor is there mention of Linux-specific tools or workflows. The documentation does not address Linux-specific nuances except for a brief note about hyphens in function names on Linux. The ordering of examples (Portal, CLI, PowerShell) may also reinforce Windows-first patterns.
Recommendations
  • Add explicit Bash or shell script examples for Linux users, especially for common operations shown in PowerShell.
  • Clarify that Azure CLI is cross-platform and recommend it as the preferred method for Linux and macOS users.
  • Mention Linux-specific considerations or workflows where relevant, such as environment variable management or scripting.
  • Provide parity in example scripts, ensuring both PowerShell and Bash are represented where possible.
  • Reorder examples to present cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell), or group by platform.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-event-publishing.md ...unctions/durable/durable-functions-event-publishing.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. The prerequisites and configuration sections mention the Azurite and Storage Emulator, both of which are historically Windows-centric tools, and the Storage Emulator is only available on Windows. Instructions for clearing storage data reference the Storage Emulator but do not mention Linux alternatives. There are no explicit Linux-specific examples or parity notes for Linux users. PowerShell is mentioned as an alternative to Azure CLI, but not prioritized. Portal-based instructions are platform-neutral, but the overall pattern assumes familiarity with Windows tools and does not address Linux-specific workflows or limitations.
Recommendations
  • Explicitly mention that Azurite is cross-platform and provide installation instructions for Linux and macOS.
  • Replace or supplement references to the Storage Emulator with Azurite, and clarify that Storage Emulator is Windows-only.
  • Add Linux-specific instructions or notes wherever Windows-only tools (like Storage Emulator) are referenced.
  • Provide parity examples for common Linux shell environments (e.g., Bash) where relevant.
  • Add troubleshooting notes for Linux users, especially around local development and storage emulation.
  • Clarify that Azure CLI is cross-platform and recommend it as the default for command-line instructions.
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-08 00:53
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 Windows bias in several ways: Windows-specific tools and patterns (Visual Studio, MSI installer, Windows paths) are mentioned before or more prominently than cross-platform or Linux alternatives. Examples for publishing and building (ReadyToRun) use Windows runtime identifiers and do not show Linux equivalents. Command-line installation instructions include PowerShell and Windows CMD, but do not provide explicit bash or Linux shell examples. Visual Studio is referenced as the primary development environment, with less emphasis on Visual Studio Code or CLI workflows that are more common on Linux/macOS. There is also reliance on WindowsAzure.Storage and Windows-style paths in examples.
Recommendations
  • Provide Linux/macOS equivalents for all Windows-specific instructions, such as ReadyToRun publishing with linux-x64 RuntimeIdentifier.
  • Include bash/zsh shell examples alongside PowerShell and CMD for package installation and CLI usage.
  • Explicitly mention and demonstrate development workflows using Visual Studio Code and Azure Functions Core Tools on Linux/macOS.
  • Avoid using Windows paths (e.g., '..\bin\FunctionApp1.dll') in examples; use platform-agnostic or Linux-style paths where possible.
  • Clarify that Azure Functions Core Tools and SDKs are cross-platform, and provide installation instructions for Linux (apt, yum, Homebrew) and macOS.
  • Balance references to Visual Studio with equivalent instructions for Visual Studio Code and CLI-based workflows.
  • Review dependency mentions (e.g., WindowsAzure.Storage) and clarify cross-platform compatibility or alternatives.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-machine-learning-tensorflow.md ...ure-functions/functions-machine-learning-tensorflow.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides command examples for Bash, PowerShell, and Cmd, but often lists Windows-specific tools and instructions first or more prominently. Windows command-line tools (PowerShell, Cmd) are given equal or greater emphasis compared to Bash, and Windows-specific troubleshooting (e.g., registry edits for long paths) is included without Linux equivalents. Some instructions (such as activating virtual environments) are more detailed for Windows, and Windows tools (Visual Studio Code, py launcher) are mentioned before or without Linux alternatives. There is also a lack of Linux-specific troubleshooting guidance.
Recommendations
  • Ensure Linux/Bash instructions are presented first or equally alongside Windows examples.
  • Add Linux-specific troubleshooting steps (e.g., common pip/venv issues on Linux, file permission errors, path length issues).
  • Mention Linux-native editors (e.g., Vim, VS Code for Linux) alongside Visual Studio Code.
  • Provide parity in command explanations, ensuring Bash/Linux commands are as detailed as Windows/PowerShell ones.
  • Include notes about differences in file paths, permissions, and environment activation between platforms.
  • Where Windows registry edits are mentioned, provide Linux/macOS equivalents or clarify that the issue is Windows-specific.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references PowerShell and Azure portal methods for key steps, with Azure CLI examples provided but not prioritized. There is no explicit mention of Linux-specific tools or workflows, and examples for enabling managed identity and connecting to SQL use Windows-centric terminology (e.g., PowerShell, Azure portal). The SQL connection example uses sqlcmd, which is cross-platform, but does not clarify Linux usage or alternatives. Linux users may find the instructions less tailored to their environment.
Recommendations
  • Explicitly mention that Azure CLI and sqlcmd are cross-platform and provide Linux-specific usage notes (e.g., installation, authentication differences).
  • Provide step-by-step examples for enabling managed identity and configuring SQL access using Linux shell environments (e.g., bash), including screenshots or terminal output.
  • When referencing PowerShell or Azure portal, offer equivalent Linux-friendly alternatives first or side-by-side.
  • Clarify any platform-specific prerequisites or differences (such as environment variables, authentication methods, or tool installation) for Linux users.
  • Add a section or callout for Linux users highlighting best practices and common issues when connecting Azure Functions to Azure SQL with managed identity.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/scenario-build-serverless-workflow.md ...unctions/durable/scenario-build-serverless-workflow.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides command examples for Windows (PowerShell and Cmd) alongside bash, but Windows-specific instructions and tools (PowerShell, Cmd) are often listed before or more prominently than Linux/macOS equivalents. The use of Windows command shells is explicit in several sections, and Windows-centric patterns (such as 'py' for Python, which is a Windows launcher) are used in examples. Linux instructions are present but sometimes appear after Windows ones or are less detailed.
Recommendations
  • Ensure Linux/macOS instructions are presented before or alongside Windows instructions, not after.
  • Provide parity in command examples, ensuring bash/Linux/macOS commands are as detailed and prominent as Windows/PowerShell/Cmd examples.
  • Avoid using Windows-specific tools or patterns (such as 'py' launcher) in cross-platform sections; prefer 'python3' for Python commands.
  • Where possible, group instructions by OS (Linux/macOS, Windows) and clarify which commands apply to which environment.
  • Review all code blocks and tabs to ensure Linux/macOS users have clear, first-class guidance.
  • Explicitly mention cross-platform compatibility for all tools (e.g., Azure Developer CLI, Azurite, Azure Functions Core Tools) and provide installation instructions for Linux/macOS where relevant.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/language-support-policy.md ...in/articles/azure-functions/language-support-policy.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page includes a dedicated PowerShell section and frequently references Azure PowerShell as a method for managing Azure Functions, alongside Azure CLI and portal. There is a slight tendency to mention Windows-centric tools (PowerShell) before or alongside cross-platform alternatives, and PowerShell is given equal prominence to CLI and portal methods, which may suggest a Windows-first approach. However, explicit Linux examples or Linux-specific tools are not present, and there is no overt omission of Linux support, but parity in examples and tool recommendations could be improved.
Recommendations
  • Ensure that Linux-specific instructions and examples are provided where relevant, especially for runtime management and configuration.
  • When listing tools for managing Azure Functions (e.g., checking runtime versions), alternate the order or explicitly note cross-platform compatibility of Azure CLI and PowerShell.
  • Add examples or notes for Linux shell usage (e.g., Bash) where PowerShell is mentioned, to reinforce cross-platform parity.
  • Clarify that Azure CLI and PowerShell are both cross-platform, and consider adding links or notes for Linux users.
  • Review and update documentation to include Linux-native tools or commands where applicable, not just Windows/PowerShell options.
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-08 00:53
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 apps, but there is a noticeable Windows bias. Windows-specific instructions, tools, and patterns (such as deployment slots, certificate management, and app settings) are often presented first or in greater detail. Many CLI examples and scripts use Windows-centric tools or patterns (e.g., Azure CLI commands that assume Windows storage/file share conventions, references to Visual Studio and Windows deployment workflows). In several sections, Linux instructions are either less detailed, deferred to a single CLI command, or rely on the reader to adapt Windows-centric steps. Some advanced migration scenarios (e.g., premigration tasks, app configuration, code package retrieval) are more thoroughly documented for Windows than for Linux, and Windows tools (Visual Studio, PowerShell, Windows file shares) are mentioned before or instead of Linux equivalents.
Recommendations
  • Ensure Linux examples are provided with equal detail and clarity as Windows examples, especially for advanced migration and troubleshooting steps.
  • Present Linux and Windows instructions in parallel, rather than Windows-first, to avoid implicit prioritization.
  • Include Linux-native tools and workflows (e.g., bash scripts, Linux file system conventions, Linux deployment methods) alongside Windows tools.
  • Expand documentation for Linux-specific scenarios, such as retrieving deployment packages from Linux storage accounts, using Linux-based development environments, and troubleshooting Linux-specific issues.
  • Avoid referencing Windows-only tools (e.g., Visual Studio, PowerShell) without mentioning Linux alternatives (e.g., VS Code, Azure Functions Core Tools, bash).
  • Where possible, use cross-platform CLI commands and scripts, and clarify any OS-specific differences.
  • Add explicit notes when a feature or command is Windows-only or Linux-only, and provide guidance for the other platform.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-compare-logic-apps-ms-flow-webjobs.md ...ctions/functions-compare-logic-apps-ms-flow-webjobs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 moderate Windows bias. It references Windows-centric tools (PowerShell, Visual Studio), and mentions them before or instead of Linux equivalents. Examples and management tooling focus on PowerShell and Visual Studio, with limited mention of cross-platform or Linux-native tools. There are no explicit Linux or Bash examples, and Linux-specific patterns (such as shell scripting, Linux package managers, or CLI usage) are underrepresented or omitted.
Recommendations
  • Add explicit Linux/Bash examples alongside PowerShell and Windows-centric instructions.
  • Mention Linux-native tools (e.g., bash, shell scripting, Linux package managers) in management and deployment sections.
  • Ensure Azure CLI usage is demonstrated with both Windows and Linux shells.
  • Highlight cross-platform development environments (e.g., Visual Studio Code, JetBrains Rider) equally with Visual Studio.
  • Clarify that WebJobs and Functions can be developed and managed from Linux and macOS, not just Windows.
  • Provide parity in troubleshooting and monitoring instructions for Linux environments.
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-08 00:53
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 presented first and with more prominence. PowerShell is featured as a primary deployment method, while Linux shell equivalents (e.g., Bash, Azure CLI) are less emphasized. Some references and sample links default to Windows-based templates. This ordering and emphasis may subtly reinforce Windows as the default or preferred platform, even though Linux parity is generally maintained in the technical content.
Recommendations
  • Alternate the order of Windows and Linux examples, or present Linux examples first in some sections to avoid implicit prioritization.
  • Provide equivalent Bash/Azure CLI deployment instructions alongside PowerShell, especially in the 'Deploy your template' section.
  • Ensure sample links and references include both Windows and Linux templates, or clarify when a template is OS-specific.
  • Explicitly state platform parity goals at the beginning of the documentation to reinforce equal support.
  • Audit for any subtle language that implies Windows is the default or preferred platform and revise for neutrality.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Windows and Linux examples for most languages and deployment scenarios, but Windows is often presented first, and Windows-specific tools and terminology (such as PowerShell and Windows runners) are prominent. PowerShell is included as a supported language, with both Windows and Linux templates, but Python is explicitly unsupported on Windows. The documentation references Windows runners and deployment patterns before their Linux equivalents, and some sections (such as workflow template selection and example code) consistently list Windows before Linux. There is limited discussion of Linux-specific considerations or troubleshooting.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
  • Include Linux-specific troubleshooting tips and considerations, especially for deployment methods and authentication.
  • Ensure that all language examples provide equal detail for both Windows and Linux, and clarify any platform limitations (e.g., Python not supported on Windows) with rationale.
  • Highlight Linux-native tools and patterns (such as bash scripting, Linux file permissions, etc.) where relevant.
  • Consider adding a summary table comparing Windows and Linux deployment differences, including supported languages, runners, and limitations.
  • Avoid using Windows terminology (such as 'PowerShell') as the default unless the context is truly Windows-specific.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a moderate Windows bias. Windows-centric tools like Visual Studio and PowerShell are mentioned prominently and often before cross-platform or Linux-friendly alternatives. Visual Studio is listed first in several places, and PowerShell is included as a primary language option. There is little explicit mention of Linux-specific workflows, editors, or shell environments, and no Linux-specific examples or troubleshooting guidance are provided.
Recommendations
  • Include explicit references to Linux development environments, such as VS Code on Linux, JetBrains Rider, or command-line workflows using Bash.
  • Provide Linux-specific examples and troubleshooting steps, especially for local development, environment variable configuration, and deployment.
  • Mention Linux package managers (apt, yum) and installation steps for Azure Functions Core Tools.
  • List cross-platform tools (VS Code, CLI) before Windows-only tools (Visual Studio) to avoid 'windows_first' ordering.
  • Add guidance for using Bash scripts and shell environments alongside PowerShell, especially in examples and automation sections.
  • Clarify that all tools and workflows are supported on Linux and macOS, not just Windows.
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-08 00:53
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 several forms of Windows bias. Hybrid Connections are explicitly stated as only supported on Windows, with Linux support absent. Where automation examples are provided, both Azure CLI and PowerShell are shown, but PowerShell (a Windows-centric tool) is given equal prominence, and there are no Linux shell or scripting examples. In subnet sizing recommendations, Windows is mentioned before Linux, and the minimum subnet size for Windows is described first. There are no Linux-specific troubleshooting or operational examples, and some features (like Hybrid Connections) are unavailable on Linux, but this is only noted in a warning rather than providing Linux alternatives or workarounds.
Recommendations
  • Provide Linux-specific examples and alternatives wherever Windows or PowerShell examples are given (e.g., bash scripts, Linux troubleshooting steps).
  • When describing features that are Windows-only (such as Hybrid Connections), offer Linux workarounds or explicitly state the lack of parity and link to feature requests or roadmaps.
  • In tables and recommendations, avoid listing Windows before Linux by default; alternate or group them together to avoid implicit prioritization.
  • Expand automation sections to include Linux-native tools and scripting approaches (e.g., bash, curl, jq) where relevant.
  • Add explicit notes or callouts when a feature is not available on Linux, and suggest alternative approaches or mitigations for Linux users.
  • Ensure that all screenshots and UI walkthroughs are platform-neutral or provide Linux-specific guidance where the experience differs.
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-08 00:53
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 Windows bias by exclusively providing Azure PowerShell scripts for discovery and management tasks, referencing Visual Studio and VS Code (both primarily Windows-centric tools), and omitting equivalent Linux or cross-platform CLI examples (such as Azure CLI or Bash). There are no instructions or examples for Linux users, and Windows tools and patterns are mentioned first and exclusively throughout the migration process.
Recommendations
  • Provide Azure CLI (az) and Bash script equivalents alongside PowerShell examples for all discovery and management tasks.
  • 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-based development environments (e.g., JetBrains Rider, Visual Studio Code on Linux) and update references to Visual Studio to clarify platform support.
  • Add notes or sections highlighting differences or considerations for Linux deployments, such as file system case sensitivity, environment variable configuration, and package management.
  • Ensure all configuration steps (e.g., updating settings.json, publishing) include Linux/macOS command-line instructions and troubleshooting tips.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/scenario-database-changes-azure-cosmosdb.md ...-functions/scenario-database-changes-azure-cosmosdb.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page displays several signs of Windows bias. Windows-specific instructions (such as setting PowerShell execution policy) are presented alongside Linux/macOS alternatives, but the Windows command is more complex and prominent. Troubleshooting advice is Windows-centric (e.g., warning about WSL Bash as the default terminal). There is a reliance on Windows tools (PowerShell, cmd), and Linux/macOS instructions are less detailed. Some sections (e.g., PowerShell pivot) are placeholders, and Linux-specific troubleshooting or parity is missing.
Recommendations
  • Ensure Linux/macOS instructions are equally detailed and prominent as Windows instructions.
  • Provide troubleshooting steps for Linux/macOS environments (e.g., common shell issues, permissions, dependency installation).
  • Avoid assuming Windows as the default platform in troubleshooting tips (e.g., mention issues with Linux terminals, not just WSL Bash).
  • Include parity in code and deployment examples for Linux/macOS, not just Windows/PowerShell.
  • Where PowerShell is required, clarify cross-platform alternatives or usage (e.g., using pwsh on Linux/macOS).
  • Audit placeholder sections (e.g., PowerShell, JavaScript, Java pivots) to ensure Linux/macOS content is added when available.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/bring-dependency-to-functions.md ...icles/azure-functions/bring-dependency-to-functions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation shows evidence of Windows bias, particularly in the Java example where the ffmpeg binary is referenced as 'ffmpeg.exe', which is Windows-specific. The Java code example does not mention or provide guidance for Linux usage, such as using the Linux binary or setting executable permissions. Additionally, the note for the Python example mentions 'chmod' for Linux but does not provide a corresponding Windows note (e.g., for .exe files or permissions), suggesting a default assumption of Windows. The documentation also references PowerShell as an upload option before CLI, and the Java example's instructions and paths are Windows-centric, with Linux alternatives missing.
Recommendations
  • Provide Linux-specific examples and instructions for Java, including usage of the Linux ffmpeg binary and setting executable permissions.
  • Avoid using Windows-only file extensions (e.g., '.exe') in cross-platform examples; show both Windows and Linux variants.
  • When mentioning upload tools, list Azure CLI and PowerShell together or prioritize CLI for parity.
  • Add notes or code snippets for Windows users where Linux-specific instructions (e.g., chmod) are given, and vice versa.
  • Explicitly state platform differences in environment variables, file paths, and permissions where relevant.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/configure-monitoring.md .../main/articles/azure-functions/configure-monitoring.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 PowerShell examples for overriding monitoring configuration, but PowerShell is Windows-specific and is presented as a main option. There is no mention of Bash or Linux shell scripting alternatives. Additionally, the documentation references Visual Studio and Visual Studio Code as primary tools for enabling Application Insights, which are more commonly used on Windows. There is no explicit Linux example or parity for local development or configuration tasks, and some notes (such as app settings with periods) mention Linux limitations but do not offer Linux-specific guidance or alternatives.
Recommendations
  • Provide Bash or Linux shell script examples alongside PowerShell for configuration tasks.
  • Explicitly mention Linux-compatible tools and workflows (e.g., VS Code on Linux, Azure CLI in Bash) when describing setup and configuration steps.
  • Where PowerShell is referenced, clarify that it is Windows-only and offer equivalent Linux commands.
  • Add examples or notes for Linux users regarding local development, especially where there are known limitations (e.g., app settings with periods).
  • Ensure that all configuration steps (such as enabling Application Insights) are described in a cross-platform manner, not assuming Visual Studio or Windows as the default environment.
GitHub Create Pull Request
← Previous Page 11 of 41 Next →