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 801-825 of 1023 flagged pages
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-vnet.md ...main/articles/azure-functions/functions-create-vnet.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by explicitly stating that the tutorial uses Windows and C#, and by instructing users to select Windows as the operating system in the setup steps. While it mentions that Linux is also supported, there are no Linux-specific instructions, examples, or screenshots. All configuration and deployment steps are described using the Azure Portal UI, with no command-line examples (such as Azure CLI, Bash, or PowerShell), but the default assumption is a Windows environment. There are no Linux-specific troubleshooting notes or guidance, and the runtime stack and deployment examples are focused on .NET/C# on Windows.
Recommendations
  • Provide parallel instructions and screenshots for Linux users, including selecting Linux as the OS during Function App creation.
  • Include examples for other supported runtime stacks (e.g., Node.js, Python) and clarify any differences in networking or deployment for Linux-based Function Apps.
  • Add Azure CLI and/or Bash script examples for resource creation, configuration, and deployment, to support cross-platform and automation scenarios.
  • Explicitly call out any differences or considerations when using Linux, such as file system paths, supported features, or troubleshooting steps.
  • Ensure that language in the documentation does not default to Windows (e.g., 'This tutorial uses Windows but also works for Linux' could be reworded to be more neutral or to offer a choice at the start).
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-cli-csharp.md ...es/azure-functions/create-first-function-cli-csharp.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating Azure resources, but PowerShell is mentioned alongside CLI as a primary tool, and the PowerShell example is given equal prominence. There are no explicit Linux-specific instructions or examples, and the use of PowerShell (which is traditionally associated with Windows, though now cross-platform) may suggest a Windows-centric approach. There are no examples of Linux-specific shells or tools, and no mention of platform-specific differences or considerations.
Recommendations
  • Clearly indicate that both Azure CLI and PowerShell are cross-platform, but highlight that Azure CLI is often pre-installed or more common on Linux/macOS.
  • Provide explicit bash/zsh shell examples or notes for Linux/macOS users, especially for common tasks like environment variable setting or file navigation.
  • If PowerShell is shown, clarify that it is available on Linux/macOS, or provide alternative bash commands where appropriate.
  • Add a section or callout for Linux/macOS users, mentioning any platform-specific considerations (such as file paths, permissions, or installation steps).
  • Ensure that CLI examples are shown before PowerShell, as CLI is more universal across platforms.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-functions-create-portal.md ...e-functions/durable/durable-functions-create-portal.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Kudu console (which is Windows-centric in its UI and terminology) for package installation and file management. The instructions for running commands and uploading files are tailored to the Kudu interface, which is more familiar to Windows users. There are no alternative instructions for Linux-based workflows, such as using SSH, SCP, or Bash in the Azure Cloud Shell. Additionally, the use of 'CMD' in the Kudu console and the absence of Linux-native command-line examples or guidance further reinforce a Windows-first approach.
Recommendations
  • Provide alternative instructions for Linux users, such as using Azure Cloud Shell (Bash) or SSH to interact with the function app's file system.
  • Include examples of using SCP or SFTP to upload files like package.json, in addition to the Kudu drag-and-drop method.
  • Clarify that Kudu is accessible from any OS, but explain the differences in command-line environments (CMD vs Bash) and provide Bash equivalents where appropriate.
  • Mention cross-platform tools and workflows explicitly, ensuring parity for both Windows and Linux users throughout the documentation.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0010.md ...tions/errors-diagnostics/diagnostic-events/azfd0010.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page discusses a Linux-specific error but suggests 'running on Windows' as the only alternative for timezone support, without providing Linux workarounds or parity. No Linux-specific solutions or examples are offered.
Recommendations
  • Provide Linux-compatible alternatives or workarounds for timezone configuration, if available.
  • Offer examples or references for handling timezones on Linux hosting plans (e.g., using UTC or application-level timezone handling).
  • Avoid suggesting Windows as the primary or only solution; instead, present both Windows and Linux options equally.
  • Clarify any platform limitations and guide users to cross-platform best practices.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-private-site-access.md ...zure-functions/functions-create-private-site-access.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively instructing users to create a Windows Server virtual machine and providing only Windows-based setup and screenshots. There are no instructions or examples for creating or using a Linux-based VM, nor are there any Linux-specific considerations or command-line examples. The documentation assumes a Windows environment for the VM used to access the Azure Function, which may not reflect the needs or preferences of all users.
Recommendations
  • Provide parallel instructions and screenshots for creating a Linux-based virtual machine (e.g., Ubuntu) alongside the Windows Server example.
  • Explicitly mention that either Windows or Linux VMs can be used for this scenario, and highlight any differences in setup or access.
  • Include examples of connecting to the VM using SSH (for Linux) as well as RDP (for Windows), and clarify how Azure Bastion supports both.
  • Where relevant, show command-line examples (e.g., using curl or wget on Linux) for invoking the Azure Function from within the VM.
  • Ensure that all steps, especially those involving the VM, are platform-agnostic or provide clear alternatives for both Windows and Linux users.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-how-to-use-nat-gateway.md ...es/azure-functions/functions-how-to-use-nat-gateway.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by explicitly recommending Windows as the operating system for the function app and not providing equivalent guidance or examples for Linux. There are no Linux-specific instructions, notes, or parity checks, and the only runtime stack mentioned is .NET, which is often associated with Windows. No PowerShell or Windows command-line tools are used, but the absence of Linux parity is notable.
Recommendations
  • Provide explicit instructions and notes for both Windows and Linux hosting options, including any differences in configuration or limitations.
  • Include examples for creating and configuring the function app on Linux, and clarify if any steps differ.
  • Mention runtime stack options that are cross-platform (e.g., Node.js, Python) and provide sample code or notes for those.
  • If there are platform-specific recommendations (such as for best experience), explain the rationale and provide alternatives for Linux users.
  • Ensure screenshots and UI instructions are not Windows-specific, or clarify if the experience is identical on Linux.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias by listing Windows-centric tools (such as Visual Studio and PowerShell) before cross-platform or Linux-native alternatives, especially in the C# and HTTP test tools sections. Visual Studio (Windows-only) is presented as the primary environment for C#, with cross-platform options mentioned later. PowerShell is listed as an HTTP test tool before curl, which is more native to Linux. However, the page does provide parity in mentioning Linux and macOS support for Visual Studio Code and Core Tools, and does not omit Linux examples entirely.
Recommendations
  • In C# sections, list Visual Studio Code and command-line/terminal options before Visual Studio, or group them together to avoid implying Windows-first development.
  • In HTTP test tools, list curl before PowerShell, as curl is more universal and native to Linux/macOS.
  • Wherever possible, provide explicit Linux/macOS command-line examples or screenshots alongside Windows ones.
  • Highlight cross-platform tools and workflows first, or equally, to reinforce Linux parity.
  • Explicitly mention Linux package managers (e.g., apt, yum, brew) for installing Core Tools and Azurite, not just npm or Windows installers.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/python-memory-profiler-reference.md ...es/azure-functions/python-memory-profiler-reference.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias, particularly in the local development instructions. Windows PowerShell is mentioned first, and Windows-specific commands (such as 'py -m venv .venv' and '.venv\Scripts\Activate.ps1') are listed before their Linux equivalents. The file path separator in the memory profiler output example also uses Windows-style backslashes. However, Linux alternatives are present, and there are no exclusive Windows-only tools or missing Linux examples.
Recommendations
  • Present Linux and Windows instructions in parallel (side-by-side tabs or clearly separated steps) rather than listing Windows first.
  • Use neutral or platform-agnostic language, e.g., 'Open a terminal' instead of 'Open a Windows PowerShell or any Linux shell as you prefer.'
  • When showing commands, either provide both Windows and Linux/Mac commands together, or use tabs for each OS.
  • In code or output examples, use platform-neutral paths (e.g., <ProjectRoot>/HttpTriggerAsync/__init__.py) or show both Windows and Linux path formats.
  • Ensure that all steps and tooling are equally accessible and clear for Linux users, not just as an afterthought.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-openapi-definition.md ...ticles/azure-functions/functions-openapi-definition.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by referencing Visual Studio (a primarily Windows-based tool) for C# class library functions and omitting any mention of Linux-specific tools, workflows, or command-line examples. All instructions are given via the Azure Portal UI, with no CLI or cross-platform automation examples. There are no Linux or macOS-specific instructions, nor are there alternatives to Visual Studio for non-Windows users.
Recommendations
  • Include examples using Azure CLI and/or Azure PowerShell for all major steps (creating API Management instance, importing functions, downloading OpenAPI definitions) to provide parity for Linux and macOS users.
  • Mention cross-platform IDEs or editors (such as VS Code) alongside Visual Studio, and provide links or instructions for using them with Azure Functions and API Management.
  • Explicitly state that the portal-based workflow is platform-agnostic, but offer command-line alternatives for users who prefer or require non-GUI workflows.
  • If referencing Visual Studio, also reference equivalent workflows for Linux/macOS users (e.g., using VS Code or CLI tools).
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-first-java-gradle.md .../azure-functions/functions-create-first-java-gradle.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a subtle Windows bias by defaulting the Azure Functions runtime OS to 'windows' in the Gradle configuration example, without mentioning Linux as an alternative or providing guidance for Linux users. Additionally, the documentation refers to the Azure portal and Azure CLI, which are cross-platform, but the explicit configuration for 'windows' as the runtime OS may lead Linux users to believe Windows is preferred or required.
Recommendations
  • In the Gradle configuration example, explicitly mention that 'os' can be set to 'linux' as well as 'windows', and provide an example or note for Linux users.
  • Add a short section or note explaining the implications of choosing 'windows' vs 'linux' for the runtime, especially since Java 21 is supported on Linux only.
  • Ensure parity in instructions and examples for both Windows and Linux environments, particularly in configuration files and deployment steps.
  • If there are any OS-specific steps (such as setting JAVA_HOME), provide both Windows and Linux/macOS command examples.
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
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally presents Windows and Linux options in parallel, but there are subtle biases: Windows is often mentioned first in tables and explanations, and some links (such as App Service plan rates) point to Windows-specific resources. There is also a lack of Linux-specific troubleshooting or deployment examples, and some App Service pricing links default to Windows. However, the page does acknowledge Linux container support and Linux-only features where relevant.
Recommendations
  • Alternate the order of Windows and Linux mentions in tables and explanations to avoid always listing Windows first.
  • Ensure pricing and feature links reference both Windows and Linux resources, or provide a clear choice.
  • Add Linux-specific troubleshooting and deployment examples or links, especially where behaviors differ.
  • Where Windows-only features or limitations are mentioned, provide equivalent Linux information or explicitly state the Linux alternative.
  • Review all references to App Service plans and ensure Linux options are equally visible and accessible.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-run-local.md ...b/main/articles/azure-functions/functions-run-local.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation is largely cross-platform and provides examples for multiple programming languages, but there are subtle signs of Windows bias. In several places, Windows command line (cmd) examples are provided alongside Bash, and references to 'command prompt' or 'cmd' often precede 'terminal' or 'Bash'. The use of 'func.exe' and references to MSI installers for upgrades are Windows-specific. The documentation also mentions Azure PowerShell and Azure CLI as required tools for publishing, listing PowerShell (a Windows-first tool) before CLI. However, Linux and macOS users are not excluded, and Bash/cURL examples are present.
Recommendations
  • When providing command examples, always present Bash (Linux/macOS) and Windows (cmd/PowerShell) examples in parallel, and avoid listing Windows examples first by default.
  • Use neutral terminology such as 'terminal' instead of 'command prompt' or 'cmd', or mention both equally.
  • Where 'func.exe' is referenced, clarify that on Linux/macOS the executable is 'func'.
  • When discussing required tools, list Azure CLI before Azure PowerShell, or mention both together without preference.
  • Explicitly note platform differences in installation and usage steps, and provide links or instructions for Linux/macOS where appropriate.
  • Ensure that all cross-platform tools (like cURL) are introduced with equal weight for Linux/macOS and Windows, and avoid implying Windows is the default environment.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-reference-python.md ...articles/azure-functions/functions-reference-python.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation is generally cross-platform and Linux-friendly, with explicit statements that Python Functions run on Linux in Azure. However, there is a subtle Windows bias in the order and phrasing of some development and publishing guidance. Specifically, 'command prompt' is used as a synonym for 'terminal', and remote build is recommended 'when developing Python apps on Windows', with local build discouraged for Windows users. Visual Studio Code is emphasized, but that is cross-platform. There are no PowerShell-specific examples, and Linux is well-represented in hosting and deployment sections.
Recommendations
  • Replace 'command prompt' with 'terminal' or 'shell' to avoid Windows-centric terminology. If both are meant, clarify with 'terminal (Linux/macOS) or command prompt (Windows)'.
  • When discussing remote vs. local build, explain the technical reasons for the recommendation, and provide equivalent Linux/macOS guidance, not just Windows.
  • Where possible, add explicit Linux/macOS CLI examples (e.g., bash/zsh) alongside any Windows-specific instructions.
  • Review all tool references (e.g., Visual Studio Code, Azure Functions Core Tools) to ensure installation and usage instructions are clear for both Windows and Linux users.
  • Consider adding a section or callout summarizing any platform-specific caveats for local development, so Linux users are equally informed.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-cli-csharp.md ...es/azure-functions/create-first-function-cli-csharp.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating Azure resources, but PowerShell is given equal prominence to CLI, which can be seen as a Windows-centric approach. There is no explicit Linux bias, but the inclusion of PowerShell as a primary tool and its parity with CLI may disadvantage Linux/macOS users, for whom PowerShell is less common. Additionally, the order of presentation sometimes puts PowerShell before or alongside CLI, rather than prioritizing cross-platform tools.
Recommendations
  • Prioritize Azure CLI examples before PowerShell, as CLI is more universally available and familiar to Linux/macOS users.
  • Clearly indicate that PowerShell is optional and primarily for Windows users, while CLI is cross-platform.
  • If PowerShell is included, provide a brief note or link on how to install and use PowerShell on Linux/macOS, or clarify its intended audience.
  • Ensure that all steps and examples are fully cross-platform, and avoid assuming familiarity with Windows-specific tools or patterns.
  • Consider adding explicit Linux/macOS shell examples where relevant, especially for common tasks like navigation or environment setup.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-cli-node.md ...cles/azure-functions/create-first-function-cli-node.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for creating the function app in Azure, but consistently lists Azure PowerShell (a Windows-centric tool) alongside or immediately after Azure CLI, without mentioning Linux-native alternatives or clarifying cross-platform compatibility. There are no explicit Linux shell (bash/zsh) or macOS-specific instructions, and PowerShell is given equal prominence to the CLI, which may suggest a Windows-oriented bias.
Recommendations
  • Clearly state that Azure CLI commands work cross-platform (Windows, Linux, macOS), and consider listing CLI examples before PowerShell to emphasize platform neutrality.
  • Add explicit bash/zsh (Linux/macOS shell) command examples or notes where relevant, especially for steps involving environment variables, file paths, or shell-specific syntax.
  • Clarify in the prerequisites and tool installation sections that PowerShell is optional and primarily for Windows users, while Azure CLI is recommended for all platforms.
  • Where PowerShell is shown, consider providing a corresponding bash/zsh example or a note indicating that the CLI commands are suitable for Linux/macOS users.
  • Review included snippets and links to ensure they do not assume a Windows file system or shell environment.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-cli-typescript.md ...zure-functions/create-first-function-cli-typescript.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating the function app in Azure, but consistently lists Azure PowerShell after Azure CLI and does not mention or provide Linux-specific shell examples (e.g., bash/zsh). There is no explicit Windows-only tooling, but the presence of PowerShell as a first-class option and the lack of Linux-specific notes or troubleshooting tips suggest a mild Windows bias.
Recommendations
  • Add explicit bash/zsh/Linux shell examples alongside Azure CLI and PowerShell, especially for common tasks such as file editing, environment variable management, or troubleshooting.
  • Include notes or troubleshooting tips relevant to Linux/macOS users (e.g., differences in using Ctrl+C, file permissions, or path formats).
  • Clarify that Azure CLI commands are cross-platform and, where relevant, provide example terminal prompts or screenshots from both Windows and Linux/macOS environments.
  • Consider providing parity in scripting examples, such as bash scripts for automation, not just PowerShell.
  • Review screenshots and instructions to ensure they are not Windows-centric (e.g., avoid only showing Windows terminal output).
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/dedicated-plan.md ...s/blob/main/articles/azure-functions/dedicated-plan.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by linking exclusively to the Windows-specific App Service pricing page and referencing the App Service plan primarily in the context of Windows hosting. There are no explicit Linux or cross-platform examples, and the terminology and links default to Windows-centric resources.
Recommendations
  • Include links to both Windows and Linux App Service pricing pages, or clarify that the information applies to both platforms.
  • Explicitly mention Linux support for App Service plans and provide examples or notes where behavior may differ between Windows and Linux hosting.
  • Where relevant, reference both Windows and Linux tools or workflows for managing and scaling App Service plans.
  • Add clarifying statements or links for users deploying on Linux, especially regarding features like Always On and scaling.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/event-driven-scaling.md .../main/articles/azure-functions/event-driven-scaling.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally avoids OS-specific bias, but in the 'Limit scale-out' section, both Azure CLI and Azure PowerShell examples are provided, with PowerShell given its own tab. In the 'Scale-in behaviors' section, a specific note is made for 'app running on Windows in a Consumption plan', with no equivalent mention for Linux. There are no Linux shell or bash examples, and the only OS-specific scenario called out is for Windows. This subtly prioritizes Windows and PowerShell users, and omits parity for Linux users.
Recommendations
  • Add explicit bash/Linux shell examples alongside Azure CLI and PowerShell, especially for configuration changes.
  • When mentioning Windows-specific behaviors (such as drain mode), clarify whether there are differences for Linux, or state explicitly if there are none.
  • If PowerShell is given a dedicated example, consider providing equivalent bash scripting for Linux users.
  • Review all examples and notes to ensure Linux users are equally represented and not left to infer behavior or commands.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-first-java-gradle.md .../azure-functions/functions-create-first-java-gradle.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page exhibits a subtle Windows bias by specifying 'os = windows' as the default in the Gradle configuration block, without mentioning or providing guidance for Linux or macOS users. The runtime OS setting is presented as 'windows' without alternatives, and there is no discussion of cross-platform deployment or local development differences. While command-line examples use Bash and cURL (which are cross-platform), the documentation implicitly assumes Windows as the primary target environment.
Recommendations
  • Explicitly mention that the 'os' property in the Gradle configuration can be set to 'linux', and provide an example or table showing possible values and their implications.
  • Add a note or section for Linux/macOS users, clarifying any differences in setup, deployment, or supported Java versions (e.g., Java 21 is Linux-only).
  • Ensure that screenshots, instructions, and references to the Azure portal or CLI are platform-neutral or include platform-specific notes where relevant.
  • Consider providing a sample build.gradle snippet for Linux users, or at least mention that the default 'windows' value can be changed.
  • Review the documentation for any other implicit assumptions (such as file paths or environment variable syntax) that may be Windows-specific, and provide cross-platform guidance.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-cosmos-db-triggered-function.md ...tions/functions-create-cosmos-db-triggered-function.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses the Azure Portal (web UI) for all steps and does not provide any command-line examples. There are no references to Windows-specific tools or PowerShell, but also no mention of Linux or cross-platform CLI alternatives (such as Azure CLI or Azure Functions Core Tools). This omission results in a bias by not addressing users who prefer or require command-line or Linux-native workflows.
Recommendations
  • Add parallel instructions using Azure CLI and Azure Functions Core Tools for each step, including Cosmos DB account creation, function app deployment, and trigger setup.
  • Include code snippets for creating and managing resources via CLI, making it clear these commands work on Linux, macOS, and Windows.
  • Explicitly mention that all portal-based steps can be performed from any OS, but provide links or references to CLI-based documentation for users on Linux or who prefer automation.
  • Where screenshots or UI steps are given, consider adding CLI equivalents in expandable sections or as alternative workflows.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-first-function-terraform.md ...functions/functions-create-first-function-terraform.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell tab is present and the CLI examples use variable assignment syntax that is compatible with Bash (Linux/macOS) but not with Windows CMD. There are no explicit Windows-only tools, but PowerShell is a Windows-centric shell, and its inclusion as a primary tab can indicate a slight Windows bias. However, the main workflow (Terraform, Azure CLI) is cross-platform and the function app is explicitly stated to run on Linux.
Recommendations
  • Clarify in the Azure CLI section that the examples are intended for Bash (Linux/macOS/WSL) and provide equivalent CMD syntax for Windows users.
  • Consider adding a note that Azure PowerShell is available cross-platform, but is most familiar to Windows users.
  • If possible, add a third tab for Windows CMD users, or clarify that PowerShell is the preferred shell for Windows.
  • Ensure that all shell commands are tested on both Linux/macOS and Windows environments, and document any differences.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-private-site-access.md ...zure-functions/functions-create-private-site-access.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses Windows Server as the example operating system for the virtual machine, with no mention of Linux alternatives or instructions. All screenshots, instructions, and default choices are Windows-centric, and there are no parallel steps or notes for deploying or accessing the function app from a Linux VM. This creates a Windows-first impression and omits guidance for users preferring or requiring Linux environments.
Recommendations
  • Include parallel instructions and screenshots for creating a Linux-based virtual machine (e.g., Ubuntu) alongside the Windows Server example.
  • Explicitly mention that either Windows or Linux VMs can be used for this scenario, and provide guidance for both.
  • Add notes or sections on how to connect to a Linux VM via Azure Bastion (using SSH), including any differences in browser-based access.
  • Ensure that any command-line or deployment steps (such as function deployment) include both Windows (PowerShell/Command Prompt) and Linux (Bash) examples where relevant.
  • Review all screenshots and UI instructions to ensure they are not exclusively Windows-focused, or provide Linux equivalents where the experience differs.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-storage-queue-triggered-function.md ...s/functions-create-storage-queue-triggered-function.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows by exclusively using Azure Portal (web UI) instructions, which are platform-agnostic but omit any command-line examples. There are no CLI-based instructions (such as Azure CLI, PowerShell, or Bash), which are important for Linux users and automation. Additionally, there is no mention of Linux-specific tools or workflows, nor are there any examples using Bash or Linux shell commands.
Recommendations
  • Add parallel instructions using Azure CLI commands for all steps (creating the function app, queue, and adding messages), with example commands that work on Linux and macOS.
  • Include Bash shell examples for interacting with Azure Storage queues, such as using az storage queue create and az storage message put.
  • Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide links to CLI documentation.
  • If PowerShell is mentioned in other related pages, ensure Bash/Linux equivalents are always provided and given equal prominence.
GitHub Create Pull Request
Azure Functions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-vnet.md ...main/articles/azure-functions/functions-create-vnet.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently presents Windows as the default or primary operating system for Azure Functions, with explicit statements such as 'This tutorial uses C# and Windows' and 'This tutorial uses Windows but also works for Linux.' However, there are no Linux-specific instructions, screenshots, or examples provided. All steps and guidance are oriented around the Azure Portal UI, which is cross-platform, but the language and defaults reinforce a Windows-centric approach. There are no CLI, PowerShell, or Bash examples, but the lack of Linux parity is evident in the absence of Linux-specific guidance or troubleshooting.
Recommendations
  • Explicitly provide parallel instructions and examples for Linux users, including any differences in setup or behavior.
  • Where the tutorial states 'This tutorial uses Windows but also works for Linux,' add a section or callout with Linux-specific considerations or steps.
  • Include screenshots or CLI commands (e.g., Azure CLI, Bash) that demonstrate how to perform the same actions on Linux systems.
  • If there are no differences, explicitly state that the steps are identical for Linux, and provide confirmation or validation steps for Linux environments.
  • Consider alternating the order of mention (e.g., 'Windows or Linux') or providing a neutral phrasing to avoid reinforcing Windows as the default.
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
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally provides parity between Windows and Linux, offering explicit tabs and templates for both platforms and most languages. However, there is a subtle Windows-first bias: Windows is consistently listed before Linux in tabbed sections, and PowerShell (a Windows-centric shell) is included as a primary language example, even though it's less common on Linux. There are no missing Linux examples, and Linux is acknowledged as the only supported OS for Python. No Windows-only tools or patterns are mandated, but the ordering and language focus suggest a mild preference for Windows.
Recommendations
  • Alternate the order of Windows and Linux tabs or present Linux first in some sections to avoid implicit prioritization.
  • Where PowerShell is shown, also provide Bash or shell script equivalents, especially for cross-platform scenarios.
  • Explicitly state that all workflows and tools are supported equally on both Windows and Linux where applicable.
  • Consider including a general-purpose shell scripting example (Bash) alongside PowerShell to better serve Linux users.
  • Review language and screenshots to ensure equal representation of both OS environments.
GitHub Create Pull Request
← Previous Page 33 of 41 Next →