Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 376-400 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/automate-add-lab-user.md
...b/main//articles/devtest-labs/automate-add-lab-user.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing PowerShell examples, referencing Windows-centric tools and cmdlets (such as Get-AzRoleDefinition, Get-AzADUser, New-AzResourceGroupDeployment), and omitting Linux-specific or cross-platform CLI alternatives for key steps (such as obtaining object IDs or deploying templates). Azure CLI is mentioned, but its example is less detailed and appears after extensive PowerShell coverage. There are no explicit Linux shell (bash) examples or guidance for non-Windows environments.
Recommendations
- Provide equivalent bash/Azure CLI examples for all PowerShell commands, especially for obtaining object IDs and deploying ARM templates.
- List Azure CLI and bash examples before or alongside PowerShell to avoid 'windows_first' ordering.
- Reference cross-platform tools and commands (e.g., az ad user show) when discussing how to retrieve user or group object IDs.
- Clarify that Azure CLI and ARM templates are fully supported on Linux/macOS, and provide explicit instructions for those environments.
- Where PowerShell-specific features (like New-Guid) are used, offer alternatives using standard Linux tools (e.g., uuidgen).
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/configure-event-hub-properties.md
.../articles/event-hubs/configure-event-hub-properties.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for configuring Event Hub properties, but it gives equal prominence to PowerShell (a Windows-centric tool) and does not mention Linux-native alternatives (such as Bash scripting or REST API usage). The PowerShell section is detailed and appears before ARM template instructions, which are platform-neutral. No Linux-specific examples or shell scripting guidance is provided, and the PowerShell tool is mentioned without noting its limited cross-platform support.
Recommendations
- Add explicit Bash shell examples for Azure CLI commands to demonstrate Linux parity.
- Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
- Mention REST API usage as a platform-neutral alternative for automation.
- Reorder sections to present Azure CLI (cross-platform) before PowerShell (Windows-centric), or clarify the intended audience for each.
- Note PowerShell Core's cross-platform capability if relevant, or clarify if examples are for Windows PowerShell only.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-core-tools-reference.md
...cles/azure-functions/functions-core-tools-reference.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page for Azure Functions Core Tools demonstrates some Windows bias. It refers to the tool as 'func.exe' in the description, which is a Windows-specific executable extension. There is a notable emphasis on PowerShell support and features (e.g., managed dependencies only for PowerShell), and some options or behaviors are described in the context of Windows (such as trusted certificate creation for HTTPS). Additionally, some instructions and terminology (e.g., references to .pfx files and certificate handling) are more familiar to Windows users. There are no explicit Linux shell or cross-platform command examples, and Linux-specific behaviors are only mentioned in passing or as exceptions.
Recommendations
- Use cross-platform terminology for the tool (e.g., 'func' instead of 'func.exe') throughout the documentation.
- Provide Linux/macOS shell command examples alongside or instead of Windows-centric ones, especially where file paths, certificates, or environment variables are involved.
- When discussing features only available on Windows or PowerShell, clearly indicate platform limitations and suggest Linux/macOS alternatives or workarounds where possible.
- Ensure that any references to file types, tools, or workflows (such as .pfx files, certificate creation, or managed dependencies) include Linux/macOS equivalents or guidance.
- Review the documentation for implicit assumptions about the user's platform and add clarifying notes or parity instructions for Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-identity-based-connections-tutorial.md
...tions/functions-identity-based-connections-tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows environments: it explicitly states support for C# class library functions on Windows, references Azure Files (the default file system for Windows deployments), and omits Linux-specific instructions or examples. There is no mention of Linux-specific deployment patterns, nor are there examples or caveats for Linux users, despite Azure Functions supporting Linux hosting. The ARM template and portal steps are generic, but the underlying assumptions and examples are Windows-centric.
Recommendations
- Add explicit instructions and examples for Linux-based function apps, including how to handle storage and identity-based connections on Linux.
- Clarify which steps differ for Linux Consumption and Premium plans, especially regarding Azure Files and deployment artifacts.
- Include Linux-specific caveats, such as the need for external deployment packages when using identity-based AzureWebJobsStorage in Linux Consumption.
- Provide parity in examples and guidance for both Windows and Linux environments, or clearly state any limitations or differences up front.
- Where possible, provide cross-platform CLI (e.g., Azure CLI) commands instead of relying solely on portal-based instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/devtest-lab-add-devtest-user.md
.../articles/devtest-labs/devtest-lab-add-devtest-user.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell scripting examples (with no Bash/CLI or Linux-native alternatives), referencing Microsoft accounts (with a link to Windows Server documentation), and listing PowerShell as the only automation method. The prerequisites and instructions focus on PowerShell and Windows-centric tools, with no mention of Azure CLI or cross-platform scripting options. The order of presentation also places PowerShell before any mention of CLI or Linux-friendly tools.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include instructions for installing and using Azure CLI on Linux/macOS, alongside PowerShell.
- Reference generic Microsoft Entra ID documentation rather than Windows Server-specific Microsoft account links.
- Present automation options in a neutral order (e.g., 'Azure portal', 'Azure CLI', 'Azure PowerShell') or group them by platform-neutrality.
- Explicitly state that all procedures can be performed from any OS using Azure CLI or the portal, not just from Windows/PowerShell environments.
Azure Docs
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows-specific tools and paths are mentioned before or instead of cross-platform or Linux equivalents (e.g., use of Windows environment variables, Windows installer for Core Tools, and Windows-specific runtime identifiers in ReadyToRun examples). Command-line installation examples are provided for Windows (cmd, PowerShell) but not for Bash or other Unix shells. There is a lack of explicit Linux/macOS examples or guidance, and some tool references (like Visual Studio) are Windows-centric.
Recommendations
- Provide parallel Linux/macOS examples for all command-line instructions, including Bash/zsh equivalents for package installation and usage.
- When discussing tool installation (e.g., Azure Functions Core Tools), include Linux/macOS installation methods (such as apt, yum, Homebrew) alongside Windows MSI and npm.
- In ReadyToRun and deployment examples, show both Windows and Linux RuntimeIdentifiers (e.g., 'win-x86' and 'linux-x64') and explain how to choose the appropriate one.
- Avoid referencing Windows-specific paths (like %USERPROFILE%\AppData\...) without also providing the Linux/macOS equivalents (e.g., ~/.local/share/...).
- When listing development environments, clarify cross-platform support for Visual Studio Code and the CLI, and provide links or notes for Linux/macOS users.
- Ensure that all environment variable usage and configuration file instructions are clear for both Windows and Linux/macOS shells.
- Add explicit notes or sections for Linux/macOS users where behavior or setup differs from Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-create-first-function-bicep.md
...ure-functions/functions-create-first-function-bicep.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides deployment instructions using both Azure CLI and Azure PowerShell, but PowerShell is featured as a first-class option throughout, despite being primarily a Windows-centric tool. There are no Linux shell (bash/sh) or Mac-specific examples or notes, and PowerShell is presented alongside CLI as an equal, which may suggest a Windows-first or Windows-heavy approach. The documentation does not mention or link to Linux-native tools or workflows, and there is no explicit guidance for Linux or Mac users, even though Azure CLI is cross-platform.
Recommendations
- Clearly indicate that Azure CLI commands work on Windows, Linux, and Mac, and are recommended for cross-platform use.
- De-emphasize Azure PowerShell as a primary deployment method, or move PowerShell examples to a secondary position after CLI.
- Add explicit bash/zsh shell examples or notes for Linux/Mac users, especially for file paths and environment variable usage.
- Include a section or note on platform compatibility, clarifying that PowerShell is available on Linux/Mac but is less common than bash/zsh.
- Where PowerShell is shown, provide equivalent bash commands for common validation or resource management tasks.
- Consider adding a 'Platform differences' or 'Cross-platform notes' section to address any OS-specific considerations.
Azure Docs
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 →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation demonstrates a mild Windows bias. While it is generally cross-platform in language, there are several areas where Linux parity is lacking or Windows/App Service (which is Windows-centric) is assumed. Notably, built-in log streaming is described as unsupported for Linux Consumption plans, and there are no Linux-specific troubleshooting or monitoring examples. Windows/App Service features are mentioned first or exclusively, and there is no mention of Linux-native tools or command-line examples.
Recommendations
- Provide explicit Linux examples or guidance, especially for features that behave differently or are unsupported on Linux (e.g., log streaming).
- Include alternative Linux-native tools or workflows (such as using 'tail' on log files, or Azure CLI examples for Linux environments).
- Clearly indicate feature parity or gaps between Windows and Linux hosting plans, and suggest workarounds or alternatives where features are missing.
- Avoid assuming App Service (Windows) as the default; mention Linux hosting options and their specifics early and equally.
- Add troubleshooting steps or examples for both Windows and Linux environments to ensure parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-create-your-first-function-visual-studio.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-create-your-first-function-visual-studio.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows users by exclusively using Visual Studio (Windows-only) for all instructions and examples. There are no Linux or cross-platform alternatives provided in the main flow, and all tooling and setup steps assume a Windows environment. Linux users are only briefly referred to a separate article for Visual Studio Code, but no parity is offered within this page.
Recommendations
- Include parallel instructions for Visual Studio Code and/or command-line tools (such as Azure Functions Core Tools and .NET CLI) that work on Linux and macOS.
- Explicitly mention cross-platform alternatives in each section, not just in the introduction.
- Provide screenshots and step-by-step guidance for Linux/macOS environments where possible.
- Clarify which steps are Windows-specific and offer equivalent Linux/macOS commands or workflows.
- Consider restructuring the quickstart to offer a platform selection tab or callout, ensuring Linux users are not sidelined.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-develop-local.md
...n//articles/azure-functions/functions-develop-local.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates some Windows bias by listing Windows-centric tools (Visual Studio, PowerShell) before cross-platform or Linux-native alternatives, and by providing more detailed guidance for Windows-specific workflows (e.g., Visual Studio, PowerShell). While cross-platform support is mentioned, Linux-specific tools or workflows are not highlighted or prioritized, and some examples (such as changing ports in Visual Studio) are Windows-specific. PowerShell is also featured as a primary HTTP test tool, which is less common on Linux.
Recommendations
- Ensure Linux-native tools (such as curl, HTTPie, or Linux terminal usage) are listed before or alongside Windows-specific tools in all tool recommendation lists.
- Provide explicit Linux/macOS examples or workflows, especially where Windows/Visual Studio/PowerShell workflows are described in detail (e.g., changing ports, running commands).
- Highlight Linux/macOS compatibility in all tool descriptions, not just in passing.
- Include Linux/macOS-specific troubleshooting tips or notes where relevant, especially for command-line and environment configuration.
- Balance the prominence of PowerShell with Bash or other Linux-native scripting tools in examples and tool recommendations.
Azure Docs
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows-based deployment methods and tools (such as Visual Studio and Visual Studio Code) are mentioned first and more frequently, with Linux-specific considerations often appearing later or as exceptions. Some deployment methods are described as 'Windows-only' without providing Linux alternatives or clear guidance for Linux users. There is a lack of Linux-specific command-line examples, and Windows-centric tools and patterns are emphasized.
Recommendations
- Provide Linux-specific examples and workflows alongside Windows ones, especially for deployment methods marked as 'Windows-only' or 'Linux-only'.
- Ensure that Linux command-line tools (e.g., Bash, Azure CLI on Linux) are given equal prominence to Windows tools (e.g., PowerShell, Visual Studio).
- When listing deployment methods or tools, alternate or parallelize the presentation of Windows and Linux options, rather than defaulting to Windows-first ordering.
- Clarify and expand on Linux deployment scenarios, especially where certain features are unavailable or behave differently, and offer recommended alternatives.
- Include explicit Linux shell command examples (not just Azure CLI, but also Bash scripting where appropriate) to improve parity for Linux users.
Azure Docs
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Visual Studio, a primarily Windows-based IDE, and assumes the use of Windows tooling and workflows throughout. All examples, instructions, and screenshots are based on Visual Studio UI, with no mention of cross-platform alternatives such as Visual Studio Code or command-line workflows. Package installation is shown only via the Visual Studio Package Manager Console (PowerShell), and there are no CLI or Linux-native instructions. Remote debugging and publishing steps are described exclusively for Visual Studio, with no guidance for Linux or macOS users. The use of the Azurite emulator is mentioned, but only in the context of Visual Studio integration. There is no mention of how to perform equivalent tasks on Linux or macOS, nor are there any Bash or cross-platform CLI examples.
Recommendations
- Provide parallel instructions for developing, running, and debugging Azure Functions using Visual Studio Code and/or CLI tools, which are cross-platform.
- Include examples of installing NuGet packages using the dotnet CLI (e.g., 'dotnet add package ...') alongside PowerShell/Package Manager Console commands.
- Add guidance for running and debugging Azure Functions projects using Azure Functions Core Tools on Linux/macOS, including relevant terminal commands.
- Offer instructions for publishing and managing app settings using the Azure CLI or Azure Functions Core Tools, not just Visual Studio UI.
- Include screenshots or terminal output from Linux/macOS environments where applicable.
- Clearly indicate which steps are Windows/Visual Studio-specific and provide links or sections for cross-platform alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-custom-handlers.md
.../articles/azure-functions/functions-custom-handlers.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation exhibits a Windows bias by consistently using Windows-style executable names (e.g., 'handler.exe') in configuration and file structure examples, mentioning Windows executables before Linux equivalents, and omitting explicit Linux/macOS command-line examples or file naming conventions. There are no Linux shell or cross-platform deployment instructions, and the documentation assumes familiarity with Windows patterns.
Recommendations
- In all file structure and configuration examples, show both Windows (e.g., 'handler.exe') and Linux/macOS (e.g., 'handler' or './handler') executable naming conventions side by side.
- Explicitly mention that the 'defaultExecutablePath' can be set to platform-specific executables, and provide examples for both Windows and Linux/macOS.
- Wherever a command or tool is referenced (such as deployment with Azure Functions Core Tools), include both PowerShell/Windows Command Prompt and Bash/Linux/macOS equivalents.
- Add a section or callouts that clarify any platform-specific behaviors or requirements, such as file permissions for executables on Linux/macOS.
- Provide at least one end-to-end example (including file structure, configuration, and deployment) that is explicitly shown for Linux/macOS users.
- Avoid using Windows-specific terminology or file extensions as the default; instead, use neutral or dual-platform examples (e.g., 'handler.exe' and 'handler').
Azure Docs
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates several forms of Windows bias. Windows and PowerShell tools are consistently presented alongside or before Linux/CLI equivalents, and some features/tools (such as Kudu, App Service Editor, and in-portal console) are either only available on Windows or have limited/no Linux support. Migration instructions and examples are focused on Windows, with explicit notes that migration is not supported on Linux. There are also missing Linux-specific examples or guidance in several sections, and Windows terminology and tools are prioritized throughout.
Recommendations
- Provide explicit Linux examples and guidance where features are supported, including command-line usage and screenshots.
- Clearly indicate feature parity or lack thereof for Linux in each relevant section, and provide alternative workflows or workarounds for Linux users.
- Avoid presenting Windows/PowerShell instructions first by default; consider parallel presentation or Linux-first ordering where appropriate.
- Expand documentation for Linux-specific deployment, management, and troubleshooting scenarios, including use of SSH-based consoles and Linux-compatible tools.
- Where features are Windows-only, offer links or references to Linux alternatives or explain the roadmap for Linux support.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-reference-python.md
...articles/azure-functions/functions-reference-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation generally provides a cross-platform experience, but there are subtle signs of Windows bias. Windows terminology ("command prompt") is used alongside "terminal" without explicit mention of Linux or macOS shells. Remote build is recommended specifically for Windows users, and local build is discouraged for Windows, but Linux is not explicitly highlighted as the primary local development environment. There is a lack of explicit Linux/macOS CLI examples (e.g., bash/zsh), and some folder structure examples use Windows-centric notation (e.g., <project_root>/). No PowerShell-specific commands are shown, but the overall pattern assumes familiarity with Windows development environments and tools.
Recommendations
- Explicitly mention Linux and macOS as supported and recommended environments for local development, especially in sections discussing local builds.
- When referring to the command line, use 'terminal (Linux/macOS)' and 'command prompt (Windows)' or provide separate instructions/examples for each platform.
- Provide bash/zsh shell command examples alongside any Windows command prompt or PowerShell examples, especially for common tasks like running pip or publishing functions.
- Clarify in folder structure examples that the layout applies to all platforms, and use platform-agnostic path notation (e.g., <project_root>/ instead of <project_root>\).
- Highlight any Linux/macOS-specific considerations or advantages, such as native support for certain features or better compatibility with Azure Functions hosting.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dev-box/reference-dev-box-customizations.md
...//articles/dev-box/reference-dev-box-customizations.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows environments. All examples use Windows-specific images, tools (PowerShell, WinGet), and scripting patterns. There are no examples or mentions of Linux-based images, shell scripts, or Linux-native package managers. The built-in tasks and customization mechanisms are described exclusively in terms of Windows tools and workflows.
Recommendations
- Add examples using Linux-based images (e.g., Ubuntu, Debian) in the 'image' field.
- Include built-in tasks or guidance for running shell scripts (bash/sh) alongside PowerShell.
- Provide Linux equivalents for package installation, such as apt, yum, or snap, in addition to WinGet.
- Show sample task.yaml and devbox.yaml files that use Linux shell commands and Linux file paths.
- Clarify in the documentation whether Linux environments are supported, and if not, explicitly state this limitation.
- If Linux is supported, ensure parity in documentation coverage for both Windows and Linux customization scenarios.
Azure Docs
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides cross-platform instructions, but there is a subtle Windows bias. In several places, Windows-specific tools and commands (PowerShell, Cmd, 'py' launcher) are mentioned before or more prominently than their Linux equivalents. Troubleshooting advice and environment setup tips are also Windows-centric, such as registry edits and path length issues. While bash/Linux instructions are present, Windows is often prioritized or receives more detailed guidance.
Recommendations
- Alternate the order of platform-specific tabs so that Linux/bash is sometimes listed first, or use alphabetical order.
- Provide equally detailed troubleshooting steps for Linux/macOS users, not just Windows (e.g., common pip/venv issues on Linux).
- When referencing the 'py' launcher or Windows registry, add equivalent Linux/macOS advice or explicitly state when a step is Windows-only.
- Ensure all platform-specific commands are presented with equal prominence and explanation.
- Consider a summary table of commands for all platforms at the start of each section to reinforce parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-identity-based-connections-tutorial-2.md
...ons/functions-identity-based-connections-tutorial-2.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation is explicitly scoped to C# class library functions on Windows, with no mention of Linux or cross-platform development. All examples and instructions assume the use of the Azure portal, .NET CLI, and C# on Windows. There are no Linux-specific instructions, nor are there examples for other operating systems or languages. The tutorial does not address how to perform these steps on Linux or using cross-platform tools, and it does not mention Powershell directly but assumes a Windows-centric workflow.
Recommendations
- Add explicit instructions and examples for Linux environments, including any differences in CLI commands or deployment steps.
- Clarify which steps are cross-platform and which are Windows-specific. Where possible, provide parity for Linux and macOS users.
- Include examples for other supported languages and runtimes, or clearly state the limitations.
- If certain features are Windows-only, explain why and provide workarounds or alternatives for Linux users.
- Mention and demonstrate the use of cross-platform tools (such as Azure CLI, VS Code, or Bash) where applicable.
- Consider adding a section or callout for Linux/macOS users, highlighting any environment-specific setup or troubleshooting tips.
Azure Docs
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 →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows-based build agents (vmImage: 'windows-latest') are the default or first shown for C# and PowerShell examples, while Linux (ubuntu-latest) is only used for JavaScript and Python. PowerShell is included as a first-class language example, but there is no equivalent for Bash or shell scripting for Linux users. In deployment sections, the default appType is Windows, and Windows deployment YAML is shown before Linux. There is little mention of Linux-native tooling or patterns outside of Python and JavaScript, and no explicit Bash or Linux shell scripting examples for general tasks.
Recommendations
- Provide both Windows and Linux build agent examples for all languages where possible, especially for C#/.NET, to show parity.
- When showing YAML snippets, present Linux and Windows examples side by side or in parallel tabs, rather than defaulting to Windows first.
- Include Bash or shell scripting examples for general tasks, not just PowerShell, to support Linux users.
- Clarify when Windows is required (e.g., for PowerShell or certain .NET workloads), and otherwise encourage cross-platform approaches.
- Highlight Linux-native tools and workflows where relevant, and avoid assuming Visual Studio Code or PowerShell as the default environment.
- In deployment sections, avoid defaulting to Windows appType; instead, explain both Windows and Linux options equally and early.
Azure Docs
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 →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Hybrid Connections are only supported on Windows, with Linux explicitly not supported. In automation and configuration sections, Azure PowerShell examples are provided alongside Azure CLI, but there are no Linux-specific shell or scripting examples. In subnet sizing, Windows is mentioned before Linux, and minimum subnet sizes are given for Windows first. Troubleshooting and portal instructions are Windows-centric, with no mention of Linux-specific tools or workflows. There are no examples or guidance for Linux-specific networking scenarios or tools.
Recommendations
- Provide Linux-specific examples and guidance, especially for automation (e.g., bash scripts, Linux CLI usage).
- Clarify feature parity and limitations for Linux throughout (e.g., Hybrid Connections).
- When listing subnet requirements, alternate the order or present Linux and Windows equally.
- Include troubleshooting steps or tools relevant to Linux environments.
- Where PowerShell is used, provide equivalent bash or shell script examples.
- Explicitly call out any differences in portal experience or tooling for Linux-hosted function apps.
- Add a summary table of feature support by OS (Windows/Linux) for quick reference.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-event-hub-cosmos-db.md
...icles/azure-functions/functions-event-hub-cosmos-db.md
High Priority
View Details →
Detected Bias Types
Windows First
Cmd Examples
Missing Linux Example
Summary
The documentation provides both Bash (Linux/macOS) and Cmd (Windows) examples for all command-line instructions, ensuring cross-platform coverage. However, in each case, the Windows (Cmd) examples are presented immediately after the Bash examples, and there is no mention of PowerShell, WSL, or other Windows-specific tools. The documentation does not provide Linux-specific troubleshooting, nor does it mention platform-specific caveats or alternatives. There are no Linux-only examples, and the structure always presents Bash first, then Cmd, which could be interpreted as a mild 'windows_first' bias in the sense that Windows is always given equal or more prominence, but not exclusively so.
Recommendations
- Consider including PowerShell examples for Windows users, as PowerShell is more common than Cmd for scripting on modern Windows systems.
- Add a brief note about cross-platform compatibility, explicitly stating that all commands are supported on Linux, macOS, and Windows (with Bash or Cmd).
- If there are any platform-specific caveats (such as line endings, file permissions, or environment variable persistence), mention them explicitly.
- Consider grouping Bash and Cmd examples in tabs labeled 'Linux/macOS' and 'Windows', or clarify that Bash commands work in WSL and Git Bash on Windows.
- Provide troubleshooting tips for both Linux/macOS and Windows environments, especially for common issues like environment variable persistence or file system differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-reference.md
.../main//articles/azure-functions/functions-reference.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias, primarily by listing Windows-centric tools (Visual Studio, PowerShell) before cross-platform or Linux-native equivalents, and by referencing 'command prompt' (a Windows term) rather than 'terminal' or 'shell'. PowerShell is given its own language pivot, and Azure PowerShell is mentioned as a deployment tool alongside Azure CLI, but there is no mention of Bash or Linux shell examples. Linux-specific tooling or patterns are not highlighted, and terminology is sometimes Windows-centric.
Recommendations
- Use neutral terminology such as 'terminal' or 'shell' instead of 'command prompt' to be inclusive of Linux/macOS users.
- When listing tools, alternate the order or explicitly mention cross-platform compatibility (e.g., 'Visual Studio Code (Windows, macOS, Linux)').
- Provide Linux/macOS-specific instructions or examples where relevant, especially for local development and deployment.
- Clarify that Azure CLI and Azure Functions Core Tools are cross-platform, and provide Bash or shell command examples where appropriate.
- If referencing PowerShell, also mention Bash or other common Linux shells for parity.
- Consider adding a section or callout for Linux/macOS users highlighting any differences or tips for those environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/devtest-lab-auto-shutdown.md
...in//articles/devtest-labs/devtest-lab-auto-shutdown.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing 'Windows Plan' and defaulting to Office 365 Outlook for email integration, without mentioning Linux alternatives or cross-platform options. There are no CLI, PowerShell, or shell script examples, but the only platform-specific mention is Windows. The documentation does not provide Linux-specific guidance or acknowledge Linux users, especially in the context of Logic Apps and email integration.
Recommendations
- When referencing 'Windows Plan' in Logic Apps creation, clarify if this is required for all users or provide guidance for Linux-based or cross-platform plans if available.
- Offer alternative email integration examples, such as using SMTP or other email providers (e.g., Gmail, SendGrid), not just Office 365 Outlook.
- Explicitly state that the Azure portal and Logic Apps are cross-platform and accessible from any OS, and provide guidance for Linux/macOS users where relevant.
- If any CLI or scripting is involved, provide both PowerShell and Bash/Azure CLI examples.
- Review screenshots and instructions to ensure they are not Windows-specific, or add notes for Linux/macOS users if UI or steps differ.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-run-local.md
.../main//articles/azure-functions/functions-run-local.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation generally aims for cross-platform parity but demonstrates some Windows bias. Windows command line and PowerShell are mentioned explicitly and sometimes before Linux equivalents. Windows-specific tools (e.g., PowerShell, MSI installer) are referenced, and in some cases, Windows command syntax is shown alongside (or before) Bash. There is also a focus on Windows-specific installation and usage patterns, and PowerShell is treated as a first-class language option.
Recommendations
- Ensure all command examples are provided for both Windows (cmd/PowerShell) and Linux/macOS (Bash), and present them in parallel or with equal prominence.
- When referencing tools like PowerShell or MSI installers, also mention Linux/macOS equivalents (e.g., Bash, Homebrew, apt, yum) and provide installation instructions for those platforms.
- Avoid phrases like 'command prompt' or 'func.exe' that are Windows-centric; use 'terminal' or 'func' where possible.
- When listing prerequisites or dependencies (e.g., Azure CLI, PowerShell), clarify cross-platform availability and provide links to Linux/macOS installation guides.
- In sections where Windows-specific behaviors or limitations are described (e.g., Core Tools v1.x only on Windows), clearly call out Linux/macOS alternatives or workarounds.
- Consider adding a dedicated section or callouts for Linux/macOS users to highlight any platform-specific considerations.
Azure Docs
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only a PowerShell script to identify function apps for migration, referencing Azure PowerShell as the primary tool, and omitting equivalent Bash/Azure CLI/Linux shell examples. Windows/PowerShell tools and workflows are mentioned first and exclusively, with no Linux or cross-platform alternatives presented for key administrative steps.
Recommendations
- Provide equivalent Azure CLI (az) or Bash scripts alongside PowerShell examples for identifying and managing function apps, ensuring Linux and macOS users have clear guidance.
- Reference cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools like Azure PowerShell.
- Explicitly mention that all steps can be performed on Linux/macOS, and provide any necessary command-line adjustments or prerequisites for those platforms.
- Include notes or links to documentation for Linux/macOS environments where relevant, especially for local development and deployment.
- Review all code and command examples to ensure parity between Windows and Linux, avoiding exclusive reliance on Windows tools or patterns.