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 776-800 of 1023 flagged pages
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-vs-code-node.md
.../azure-functions/create-first-function-vs-code-node.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is generally cross-platform, focusing on Visual Studio Code and Azure Functions, which are available on both Windows and Linux. However, there is subtle Windows bias in the troubleshooting section, where Windows-specific advice is given (e.g., references to WSL Bash and default terminal shell settings) without equivalent Linux or macOS troubleshooting guidance. There are no explicit PowerShell-heavy examples or exclusive use of Windows tools, but the mention of Windows-specific issues and lack of Linux/macOS parity in troubleshooting is a form of 'windows_first' and 'windows_tools' bias.
Recommendations
- Add troubleshooting steps relevant to Linux and macOS users, such as common issues with permissions, shell environments, or dependencies on those platforms.
- Where Windows-specific advice is given (e.g., 'default terminal shell for Visual Studio Code isn't set to WSL Bash'), provide equivalent guidance for Linux/macOS (e.g., ensuring the correct shell is used, or how to resolve common shell-related issues).
- Explicitly state that the instructions apply to all supported platforms, and note any platform-specific differences where relevant.
- Include links or references to platform-specific setup or troubleshooting guides for Linux and macOS.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias, primarily by listing Windows-centric tools (such as Visual Studio) before cross-platform or Linux-native alternatives, especially in C# sections. Visual Studio is mentioned as the first option for C# development and deployment, which is a Windows-only tool, while cross-platform tools like Visual Studio Code and Azure Functions Core Tools are listed after. There are no explicit Linux or bash-specific examples, and PowerShell is referenced as a language but not as a tooling bias. However, the documentation does not completely exclude Linux or cross-platform workflows, as Azure CLI and Visual Studio Code are included throughout.
Recommendations
- When listing development tools or quickstart options, present cross-platform tools (such as Visual Studio Code and Azure Functions Core Tools) before or alongside Windows-only tools like Visual Studio.
- Explicitly mention Linux and macOS compatibility where applicable, especially in sections referencing the 'command prompt' or Azure CLI.
- Provide bash or shell command examples alongside any references to 'command prompt', or clarify that instructions apply equally to Linux/macOS terminals.
- Consider adding a section or note highlighting Linux development workflows, including any differences or prerequisites for Linux users.
- Avoid assuming Visual Studio is the default or primary tool for C# development; instead, present it as one option among several, with clear indications of platform support.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally provides parity between Windows and Linux, especially in code examples, which are consistently split into Windows and Linux tabs. However, there is a recurring pattern of presenting Windows examples and explanations before Linux equivalents (windows_first). Additionally, the only explicit command-line deployment walkthroughs outside of Azure CLI are for PowerShell, with no Bash or Linux-native shell examples (powershell_heavy). There are no significant omissions of Linux-specific instructions or tools, but the ordering and emphasis could suggest a subtle Windows bias.
Recommendations
- Alternate the order of Windows and Linux examples/tabs, or present Linux first in some sections to balance perceived priority.
- Add Bash or Linux shell equivalents for PowerShell deployment examples, especially in the 'Deploy using PowerShell' section. For example, provide Azure CLI commands in Bash for creating resource groups and deploying templates.
- Where possible, clarify that all ARM/Bicep deployment methods (CLI, PowerShell, Portal) are cross-platform, and highlight any Linux-specific considerations or best practices.
- In sections where both Windows and Linux are supported, ensure introductory text does not default to Windows terminology or examples before mentioning Linux.
- Consider adding a short note at the top or in relevant sections affirming full Linux support and linking to Linux-specific troubleshooting or guidance.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-azure-developer-cli.md
...functions/create-first-function-azure-developer-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally strives for cross-platform parity, but there is a subtle Windows bias in the ordering and presentation of examples. 'Windows' is often mentioned before Linux/macOS in tabbed instructions, and PowerShell is given a dedicated programming language pivot, which may not be as relevant for Linux users. However, Linux/macOS instructions are present and complete, and most commands are cross-platform.
Recommendations
- Alternate the order of platform tabs (e.g., sometimes list Linux/macOS before Windows) to avoid always privileging Windows.
- Where possible, use neutral terms like 'terminal' instead of 'command prompt' unless specifically referring to Windows Cmd.
- Clarify that PowerShell examples are primarily for Windows, and consider providing Bash equivalents for Linux users where PowerShell scripting is shown.
- Ensure that all code snippets and instructions are validated on both Windows and Linux/macOS, and explicitly mention any platform-specific differences.
- In sections where multiple platforms are supported, consider grouping instructions by task rather than by OS to reinforce parity.
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 →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by consistently listing Windows-centric tools (such as Visual Studio and PowerShell) before cross-platform or Linux-native alternatives. Visual Studio, a Windows-first IDE, is always mentioned first in C# sections, and PowerShell is highlighted as an HTTP test tool before mentioning curl. However, the documentation does include cross-platform options (Visual Studio Code, IntelliJ, Eclipse, Maven, curl, Azurite via npm) and notes Linux/macOS support, but Windows tools and patterns are often foregrounded.
Recommendations
- When listing development environments, alternate the order or explicitly call out cross-platform and Linux-native tools first in relevant sections.
- In tables and lists, avoid always placing Windows-only tools (e.g., Visual Studio, PowerShell) at the top; consider grouping by platform or marking platform compatibility clearly.
- In the HTTP test tools section, list curl (a ubiquitous Linux tool) before PowerShell and Edge, or provide explicit Linux/macOS examples.
- Add explicit Linux/macOS command-line examples where only Windows/PowerShell patterns are described (e.g., for changing ports or running tools).
- Where Visual Studio is mentioned, clarify its platform support and suggest alternatives for Linux users (e.g., JetBrains Rider, MonoDevelop, or VS Code).
- Ensure that all screenshots, code snippets, and walkthroughs are available for Linux/macOS as well as Windows.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally provides both Windows and Linux examples for Bicep and ARM templates, and covers Linux-specific hosting plans (including Flex Consumption, Container Apps, and Azure Arc). However, there is a consistent pattern of presenting Windows examples before Linux ones ("windows_first"), especially in code tabs and explanations. Additionally, PowerShell is the only scripting language shown for command-line deployment automation, with no Bash or Linux shell equivalents ("powershell_heavy"). There are no exclusive references to Windows-only tools, but the ordering and scripting language choices may subtly prioritize Windows users.
Recommendations
- Alternate the order of Windows and Linux examples/tabs, or default to Linux first in some sections, especially for plans that are Linux-only.
- Provide Bash/Azure CLI shell script equivalents for all PowerShell deployment examples, especially in the 'Deploy your template' section.
- Where possible, clarify when a feature or example is Windows- or Linux-specific, and ensure parity in depth and detail for both platforms.
- Highlight cross-platform tools (like Azure CLI) more prominently, and avoid implying PowerShell is the default for all users.
- In summary tables and introductory text, avoid listing Windows before Linux by default—consider alphabetical or usage-based ordering.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally provides parity between Windows and Linux examples, especially in Bicep and ARM template code, and clearly separates instructions for each OS using tabs and pivots. However, there are instances of Windows bias: (1) In several sections, Windows examples are presented before Linux equivalents, making Windows the default or primary context ('windows_first'). (2) The only explicit command-line deployment walkthroughs outside of Azure CLI are for PowerShell, with no Bash or Linux-native shell equivalents ('powershell_heavy'). There are no exclusive references to Windows-only tools, but the ordering and command-line focus may subtly favor Windows users.
Recommendations
- Alternate the order of Windows and Linux examples or present Linux first in some sections to avoid always prioritizing Windows.
- Provide Bash or Azure CLI (Linux shell) equivalents for all PowerShell deployment walkthroughs, especially in the 'Deploy using PowerShell' section.
- Where possible, clarify that all ARM/Bicep templates and Azure CLI commands are fully cross-platform, and highlight any OS-specific caveats.
- Consider including a short section or note on using Linux-native tools (e.g., Bash, curl, jq) for template deployment and validation, to better support Linux users.
- Ensure that any references to the Azure portal or Visual Studio Code extensions are clearly marked as cross-platform, and mention any OS-specific limitations if they exist.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-reference.md
...b/main/articles/azure-functions/functions-reference.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation shows mild Windows bias by consistently listing Windows-centric tools (Visual Studio) before cross-platform or Linux-native tools, especially in C# sections. Visual Studio is highlighted as the primary quickstart and publishing tool for C#, with no mention of Linux-specific editors or workflows. However, most command-line and VS Code instructions are cross-platform, and there are no PowerShell-only examples or missing Linux equivalents.
Recommendations
- When listing development tools or quickstart options, avoid always placing Visual Studio (a Windows-only tool) first. Instead, list cross-platform tools like Visual Studio Code or CLI options before or alongside Visual Studio.
- Explicitly mention that Visual Studio Code and Azure Functions Core Tools are fully supported on Linux and macOS, and provide links or notes for Linux users where appropriate.
- For C# and other languages, include Linux/macOS-specific instructions or notes in quickstart and publishing sections, especially for workflows that do not require Visual Studio.
- Consider adding a table or section summarizing tool support and parity across Windows, Linux, and macOS for each language.
- Where Azure CLI or PowerShell are mentioned together, clarify that Azure CLI is cross-platform and PowerShell Core is available on Linux/macOS.
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 →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally aims for cross-platform parity, explicitly stating support for Linux, macOS, and Windows in most sections. However, there are subtle indications of Windows bias: Visual Studio (a Windows-only IDE) is listed first and most prominently in the C# section, and some instructions (such as changing the port in Visual Studio) are specific to Windows workflows. In the HTTP test tools section, PowerShell (primarily a Windows tool, though now cross-platform) and Microsoft Edge's Network Console (Windows-centric) are listed before curl, which is ubiquitous on Linux. There are no explicit Linux-only examples or tools highlighted, and Linux command-line workflows are not given priority or detailed examples.
Recommendations
- In each language section, list cross-platform tools (such as Visual Studio Code and command-line/terminal) before Windows-only tools like Visual Studio.
- When describing environment-specific instructions (e.g., changing ports), provide equivalent steps for Linux/macOS environments or clarify if a step is Windows-specific.
- In the HTTP test tools list, give equal or higher prominence to cross-platform and Linux-native tools like curl, httpie, or Postman, and clarify PowerShell's cross-platform availability.
- Add explicit Linux/macOS command-line examples or workflows where relevant, especially in sections that currently reference Windows tools or UI.
- Where possible, include screenshots or walkthroughs from Linux/macOS environments, not just Windows.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-azure-developer-cli.md
...functions/create-first-function-azure-developer-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally maintains good cross-platform parity, but there are subtle signs of Windows bias. In several places, Windows command-line instructions (Cmd and PowerShell) are listed before or alongside Linux/macOS equivalents, and PowerShell is given its own language pivot and tab. The use of 'command prompt' as a generic term and the explicit inclusion of PowerShell-specific instructions and pivots may reinforce a Windows-centric perspective, even though Linux/macOS instructions are present. No major Linux examples are missing, and Linux tools (like curl) are included.
Recommendations
- Ensure that Linux/macOS instructions are always presented first or in parallel with Windows instructions, especially in tabbed or pivoted sections.
- Avoid using 'command prompt' as a generic term; instead, specify 'terminal' or clarify the OS context.
- Where PowerShell is used, ensure Bash or equivalent Linux shell examples are equally prominent and not secondary.
- Review tab/pivot ordering to avoid defaulting to Windows/PowerShell first.
- Continue to use cross-platform tools (like curl) in examples, and avoid Windows-only tools or patterns unless absolutely necessary.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-vs-code-java.md
.../azure-functions/create-first-function-vs-code-java.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on using Visual Studio Code and its Azure Functions extension, without providing any OS-specific instructions or examples. However, it implicitly assumes a Windows environment by referencing keyboard shortcuts (e.g., F1) and does not mention or show any Linux- or macOS-specific guidance, terminal commands, or troubleshooting. There are no CLI or shell examples, and no mention of Linux-specific tools or patterns. This results in a lack of parity for Linux users who may use different workflows or encounter different issues.
Recommendations
- Explicitly state that the instructions apply equally to Windows, Linux, and macOS, or provide OS-specific notes where behavior differs.
- Include alternative instructions or notes for Linux/macOS users, such as terminal commands, keyboard shortcuts (e.g., Cmd vs Ctrl), and common troubleshooting steps.
- Provide at least one example of running or deploying the function using a Linux shell or terminal, especially for steps that may differ (e.g., file paths, environment variables).
- Mention any Linux prerequisites or dependencies if applicable (e.g., installing Azure Functions Core Tools on Linux).
- Ensure that referenced tools and extensions are available and supported on Linux, and provide links or instructions for Linux installation where relevant.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/configure-monitoring.md
.../main/articles/azure-functions/configure-monitoring.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for overriding monitoring configuration, but the PowerShell example is given its own tab and is presented immediately after the Azure CLI example. There is no explicit mention of Linux shell (bash) or cross-platform scripting alternatives, and PowerShell is a Windows-centric tool (though available cross-platform, it is still more familiar to Windows users). Additionally, the note about app settings with periods not being supported on Linux plans is present, but no Linux-specific example or workaround is provided. There are no explicit Linux command-line examples or references to Linux-native tools.
Recommendations
- Include bash or shell script examples alongside Azure CLI and PowerShell, especially for common configuration tasks.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- When presenting command-line examples, avoid giving PowerShell its own tab unless also providing a Linux shell tab.
- Where platform-specific limitations exist (e.g., app settings with periods on Linux), provide clear Linux-specific guidance or workarounds.
- Explicitly mention that PowerShell Core is available cross-platform if including PowerShell examples, or clarify which version is being referenced.
- Consider the order of examples: present cross-platform (CLI/bash) examples before Windows-specific (PowerShell) ones.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-azure-developer-cli.md
...functions/create-first-function-azure-developer-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally maintains cross-platform parity, but there are subtle signs of Windows bias. In several places, Windows-specific shells (Cmd, PowerShell) are listed before Linux/macOS equivalents, and PowerShell is treated as a first-class language option. Some command examples and folder structures reference Windows conventions or tools before Linux ones, and the PowerShell language is given equal prominence to others, which may not reflect its usage share across platforms.
Recommendations
- When presenting command-line examples, list Linux/macOS (bash) examples before Windows (Cmd/PowerShell) examples, or present them side-by-side to avoid implying a default platform.
- Ensure that all shell command examples (e.g., for setting environment variables, activating virtual environments) are present for both Linux/macOS and Windows, and that Linux/macOS is not treated as a secondary platform.
- Where possible, use platform-agnostic language (e.g., 'terminal' instead of 'command prompt') and clarify when instructions differ by OS.
- For PowerShell-specific sections, clarify that PowerShell is cross-platform, but also provide bash equivalents where appropriate.
- Review folder structure and file path examples to ensure they are not Windows-centric (e.g., use forward slashes or clarify path differences).
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 →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is generally cross-platform and Linux-friendly, especially in its guidance for Azure Functions Python development. However, there are subtle signs of Windows bias: Windows terminology ('command prompt') is used alongside 'terminal', and remote build is recommended specifically for users developing on Windows. There is also a reference to the Python standard library being installed with Python on Windows, while on Unix-based systems it is provided by package collections, which could be misleading. No explicit Linux shell or Linux-specific examples are given, and no Linux-first guidance is present.
Recommendations
- Use neutral, cross-platform terminology such as 'terminal' or 'shell' instead of 'command prompt', or clarify with 'terminal (Linux/macOS) or command prompt (Windows)'.
- When recommending remote build for Windows users, also provide guidance for Linux/macOS users, and clarify the pros and cons for each OS.
- Add Linux/macOS-specific examples or notes where relevant, such as using bash/zsh for commands, or referencing Linux filesystem paths.
- In the section about the Python standard library, clarify that official Python distributions include the standard library on all platforms, and that package management may differ only for system Python installations on some Linux distributions.
- Ensure that all instructions and examples are explicitly cross-platform, and avoid implying that Windows is the default or primary development environment.
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 →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias, primarily by listing Windows-centric tools (such as Visual Studio and PowerShell) before cross-platform or Linux-native alternatives, especially in the C# section. Visual Studio (Windows-only) is presented as the primary environment for C#, with cross-platform options like Visual Studio Code and command-line tools mentioned afterward. PowerShell is listed as an HTTP test tool before curl, and Microsoft Edge's Network Console (Windows-only) is also highlighted. However, the documentation does make efforts to mention Linux and macOS support for most tools and provides parity in examples for other languages.
Recommendations
- In the C# section, present Visual Studio Code and command-line/terminal options before or alongside Visual Studio to emphasize cross-platform support.
- When listing HTTP test tools, mention curl (a ubiquitous Linux tool) before PowerShell and Microsoft Edge, or group tools by platform.
- Explicitly mention Linux-native editors (such as Vim, Emacs, or JetBrains Rider) where appropriate, or clarify that Visual Studio Code is the recommended cross-platform editor.
- Where possible, provide Linux-specific setup or example commands (e.g., for installing Azurite or Core Tools) alongside Windows instructions.
- Ensure that all tool and environment lists are ordered in a platform-neutral or rotating manner, rather than defaulting to Windows-first.
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 →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is generally cross-platform and Linux-focused for hosting, but there are subtle Windows biases in the development and publishing workflow sections. Specifically, references to 'command prompt' and recommendations for remote build 'when developing Python apps on Windows' appear before or instead of explicit Linux or macOS guidance. The term 'command prompt' is more associated with Windows, and there is no explicit mention of Linux/macOS terminals in some places. Additionally, the documentation recommends against local builds 'when developing locally on Windows' but does not provide equivalent guidance for Linux/macOS users, potentially implying a Windows-centric development workflow.
Recommendations
- Use neutral, cross-platform terminology such as 'terminal' instead of 'command prompt', or explicitly mention 'terminal (Linux/macOS) or command prompt (Windows)'.
- Provide explicit instructions and recommendations for Linux/macOS users alongside Windows users, especially in sections about local development and publishing.
- Where recommendations are made specifically for Windows (e.g., remote build), clarify the guidance for Linux/macOS users to ensure parity.
- Include example commands or screenshots from both Windows and Linux/macOS environments where relevant.
- Review all sections for subtle ordering bias (e.g., mentioning Windows before Linux) and alternate or balance the order to avoid implicit prioritization.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-reference.md
...b/main/articles/azure-functions/functions-reference.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias, primarily by listing Windows-centric tools (such as Visual Studio) before cross-platform or Linux-native alternatives, especially in the C# section. Visual Studio is consistently mentioned first, and there is no explicit mention of Linux-specific editors or shell environments (e.g., Bash, Linux terminal) in examples or tool recommendations. However, the documentation does provide cross-platform options like Visual Studio Code and Azure Functions Core Tools, and avoids exclusive use of PowerShell or Windows-only commands.
Recommendations
- Ensure that cross-platform tools (e.g., Visual Studio Code, Azure Functions Core Tools) are listed before or alongside Windows-specific tools like Visual Studio, especially in introductory and quickstart sections.
- Explicitly mention Linux and macOS compatibility for all tools where applicable, and provide links to Linux/macOS installation guides.
- Include examples or references to using the command line in Bash or other Linux shells, not just 'command prompt', to clarify cross-platform support.
- Where PowerShell is referenced, also mention Bash or sh equivalents if relevant.
- Consider adding a section or callout for Linux/macOS users to highlight any differences or tips for those environments.
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 →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias, primarily by listing Windows-centric tools (such as Visual Studio and PowerShell) before cross-platform or Linux-native alternatives, especially in the C# section. Visual Studio (Windows-only) is always listed first, and PowerShell is mentioned as an HTTP test tool before curl. However, the documentation does make efforts to mention Linux and macOS support, especially for Visual Studio Code and command-line tools. There are no outright missing Linux examples, but the ordering and tool emphasis favor Windows.
Recommendations
- In each language section, list cross-platform tools (such as Visual Studio Code and command-line/terminal) before Windows-only tools like Visual Studio.
- In the HTTP test tools section, list curl (a ubiquitous Linux tool) before PowerShell and Microsoft Edge.
- Where possible, provide explicit Linux/macOS command-line examples alongside or before Windows/PowerShell examples.
- Clarify in tables and descriptions which tools are cross-platform and which are Windows-only, to help Linux users quickly identify their options.
- Consider adding a dedicated section or callout for Linux/macOS development tips or common issues.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively guiding users to create a Windows Server virtual machine, with no mention of Linux alternatives or examples. All screenshots and instructions for VM creation are Windows-centric, and there are no parallel instructions or notes for deploying or accessing the environment using a Linux VM. This may lead Linux users to believe that only Windows is supported or recommended for this scenario.
Recommendations
- Provide parallel instructions and screenshots for creating a Linux-based virtual machine (e.g., Ubuntu Server) alongside the Windows Server steps.
- Explicitly mention that either Windows or Linux VMs can be used for this scenario, and highlight any differences in setup or access.
- Include examples or notes on how to connect to a Linux VM via SSH using Azure Bastion, in addition to RDP for Windows.
- Ensure that any command-line or deployment steps (such as function deployment) include both Windows (PowerShell/Command Prompt) and Linux (Bash) examples where relevant.
- Add a section or callout box clarifying OS-agnostic aspects of the tutorial, reassuring users that the process is not limited to Windows environments.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/how-to-create-function-azure-cli.md
...es/azure-functions/how-to-create-function-azure-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally maintains cross-platform parity, but there are subtle signs of Windows bias. In the Java section, command examples are given for Bash, PowerShell, and Cmd, with Bash listed first but Windows shells (PowerShell, Cmd) included explicitly. File paths in examples use backslashes (\), which are Windows-specific. The mention of 'command prompt' alongside 'terminal' may also suggest a Windows-first mindset. However, Linux tools like jq are mentioned, and most commands are cross-platform.
Recommendations
- Where multiple shell examples are provided, always list Bash (Linux/macOS) first, but ensure all platforms are equally represented.
- Use forward slashes (/) in file paths or clarify when a path is platform-specific.
- When referring to the command line, prefer 'terminal' over 'command prompt' unless specifically referring to Windows.
- Ensure that all scripts and code snippets are tested and work on both Linux and Windows shells.
- Explicitly mention Linux/macOS equivalents for any Windows-specific instructions or tools.
- If referencing PowerShell, also mention Bash or zsh alternatives where appropriate.
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 →
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 and paths are presented before their Linux equivalents. The use of 'py -m venv' (Windows) is shown before 'python3 -m venv' (Linux), and the activation command for PowerShell is listed before the Linux shell equivalent. However, Linux alternatives are present, and the documentation does not omit Linux instructions entirely.
Recommendations
- Present Windows and Linux instructions in parallel or in a tabbed format, rather than listing Windows first.
- Use neutral language such as 'In Windows PowerShell, run: ... In Linux shell, run: ...' or provide both commands together.
- Where file paths are shown (e.g., <ProjectRoot>\HttpTriggerAsync\__init__.py), also show the Linux path (<ProjectRoot>/HttpTriggerAsync/__init__.py).
- Avoid phrases like 'Open a Windows PowerShell or any Linux shell as you prefer'—instead, use 'Open a terminal (Windows PowerShell or Linux shell)'.
- Ensure that all examples, screenshots, and outputs are shown for both platforms where differences exist.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/monitor-functions-reference.md
...rticles/azure-functions/monitor-functions-reference.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page demonstrates bias by providing more complete metric support and examples for Windows-based Azure Functions hosting plans, while repeatedly noting missing or unsupported features for Linux plans. There are no Linux-specific examples or guidance, and Windows support is implicitly prioritized.
Recommendations
- Add Linux-specific examples and guidance for monitoring Azure Functions, including any available metrics or workarounds.
- Clearly indicate feature parity status and provide timelines or alternatives for Linux users where metrics are not supported.
- Where features are unsupported on Linux, suggest equivalent monitoring strategies (e.g., using Application Insights logs or custom metrics).
- Ensure that documentation sections and tables are inclusive of both Windows and Linux, or provide separate, parallel sections for each platform.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/manage-connections.md
...ob/main/articles/azure-functions/manage-connections.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides code examples and configuration guidance primarily for C# (.NET) and JavaScript, but when discussing configuration files and application settings, it references patterns and files (such as 'ConnectionStrings' in configuration files and 'local.settings.json') that are more familiar to Windows/.NET developers. There are no explicit Linux-specific examples, nor are there mentions of Linux-native tools or configuration patterns. The order of presentation also places .NET/C# examples before JavaScript, which may reinforce a Windows-first perspective.
Recommendations
- Include explicit Linux-oriented examples, such as referencing environment variables for connection strings, and demonstrate how to set these in Linux environments (e.g., using bash or export statements).
- When discussing configuration files, clarify cross-platform applicability and provide Linux-specific guidance (e.g., how to set application settings via Azure CLI or environment variables in Linux containers).
- Alternate the order of code examples or provide a neutral introduction to avoid reinforcing a Windows-first perspective.
- Mention Linux-native tools or patterns where relevant, such as using environment variables or configuration management approaches common in Linux deployments.
- Add a section or note on how to manage connections and configuration in Linux-based Azure Functions environments, including Docker/container scenarios.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/configure-encrypt-at-rest-using-cmk.md
...azure-functions/configure-encrypt-at-rest-using-cmk.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by recommending Azure Storage Explorer (a GUI tool with a primary focus on Windows) for uploading files and generating SAS tokens, without mentioning command-line or cross-platform alternatives. The Storage Explorer link specifically references a Windows tab. No Linux-specific or cross-platform CLI examples are provided for these steps, and there is no mention of Linux file upload or SAS generation workflows. However, the main configuration and encryption steps use Azure CLI, which is cross-platform.
Recommendations
- Provide Azure CLI or PowerShell (cross-platform) commands for uploading files to Azure Storage and generating SAS tokens, in addition to or instead of relying on Azure Storage Explorer.
- Explicitly mention that Azure Storage Explorer is available for Linux and macOS, or provide links to platform-specific instructions.
- Include Linux/macOS-specific instructions or examples for all steps involving file operations, such as uploading deployment packages.
- Avoid linking only to Windows-specific tabs or instructions; ensure parity in documentation for all supported platforms.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and managing Azure Functions, but does not explicitly mention or provide Linux/macOS-specific shell commands or considerations. PowerShell is highlighted as an alternative to Azure CLI, which may be less familiar or relevant to Linux users. The order of presentation (CLI first, then PowerShell) is reasonable, but the presence of PowerShell throughout and lack of explicit Linux/macOS guidance or troubleshooting may create a subtle Windows bias.
Recommendations
- Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary shell-specific notes (e.g., quoting, environment variables).
- Add a brief section or callout for Linux/macOS users, clarifying that PowerShell steps are optional and not required on those platforms.
- Where PowerShell is mentioned, clarify its cross-platform availability, or provide bash/zsh equivalents if relevant.
- Include troubleshooting tips or common issues for Linux/macOS environments (e.g., permissions, path issues) if applicable.
- Consider adding a table or tabbed examples for 'Bash (Linux/macOS)' and 'PowerShell (Windows)' to make parity explicit.