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 1551-1575 of 2185 flagged pages
Azure Docs
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating Azure resources, but consistently lists Azure PowerShell as an alternative to Azure CLI, which can be interpreted as a Windows-first approach. There are no explicit Linux-only instructions or examples, and PowerShell is highlighted as a primary tool alongside the cross-platform Azure CLI. However, the core function development and local testing steps are platform-agnostic, using only .NET and Azure Functions Core Tools commands.
Recommendations
- Clearly indicate that both Azure CLI and PowerShell are cross-platform, but highlight Azure CLI as the default for Linux/macOS users.
- Present Azure CLI examples before PowerShell examples, or group them in tabs labeled by OS (e.g., Windows, Linux, macOS).
- Explicitly mention that all steps (except PowerShell) work on Linux/macOS, and provide any necessary Linux-specific notes (such as shell syntax differences, if any).
- Add a short section or callout for Linux/macOS users, confirming that the instructions are fully supported on those platforms.
- If referencing PowerShell, clarify that it is available cross-platform, but that Bash or other shells are also supported for Linux users.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-fluid-relay/how-tos/use-audience-in-fluid.md
...les/azure-fluid-relay/how-tos/use-audience-in-fluid.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referring exclusively to 'Command Prompt', using Windows-style paths (e.g., C:\My Fluid Projects, \src\App.js), and not mentioning or providing examples for Linux or macOS environments. There are no Linux shell equivalents, and all navigation and file path instructions assume a Windows context.
Recommendations
- Include instructions for Linux/macOS users, such as using 'Terminal' instead of 'Command Prompt', and provide equivalent shell commands.
- Use cross-platform file path notation (e.g., src/App.js) or mention both Windows and POSIX-style paths.
- When giving navigation examples, show both Windows (cd C:\My Fluid Projects) and Linux/macOS (cd ~/My\ Fluid\ Projects) equivalents.
- Explicitly state that the commands work on all platforms where Node.js is supported, and note any platform-specific caveats.
- Consider adding a table or callout box summarizing command and path differences between Windows and Linux/macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/connect-environment-lab-virtual-network.md
...evtest-labs/connect-environment-lab-virtual-network.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page provides only Windows-based examples and parameters, such as Windows Server OS versions and MicrosoftWindowsServer images. There are no examples or references for deploying Linux VMs or using Linux images, which may lead users to believe that only Windows environments are supported or prioritized.
Recommendations
- Include Linux OS options (e.g., Ubuntu, CentOS) in the template parameters and variables.
- Provide a parallel example or section demonstrating how to connect a Linux-based environment to the lab's VNet.
- Mention that both Windows and Linux VMs are supported, and provide guidance or links for Linux users.
- Adjust variable and parameter names to be OS-agnostic where possible, or clearly indicate how to adapt for Linux.
- Add a note or table comparing Windows and Linux deployment steps if there are differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/dedicated-plan.md
.../blob/main//articles/azure-functions/dedicated-plan.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a subtle Windows bias by linking to the Windows-specific App Service pricing page and not mentioning Linux explicitly when discussing App Service plans. It also does not provide Linux-specific guidance or parity in examples, terminology, or links, and references to the Azure portal and App Service plans implicitly assume the Windows context, which is the historical default for Azure App Service.
Recommendations
- Include explicit mention of Linux-based App Service plans and clarify that dedicated hosting is available for both Windows and Linux.
- Provide links to both Windows and Linux App Service pricing pages, or use a neutral pricing page that covers both platforms.
- Add Linux-specific considerations or differences, if any, for features like Always On, scaling, and custom images.
- Use neutral terminology (e.g., 'App Service plan (Windows or Linux)') throughout the documentation.
- Where relevant, provide examples or notes for both Windows and Linux users, especially if there are differences in configuration or behavior.
Azure Docs
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 →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a bias toward Windows by exclusively referencing the Kudu console (which is most familiar to Windows/Azure users) and using CMD as the default shell in examples. There are no references to Linux-native tools, shells, or workflows, and the instructions for uploading files and running commands are tailored to a Windows-centric portal experience. While the cURL example is cross-platform, the overall workflow assumes familiarity with Windows/Azure portal conventions.
Recommendations
- Include explicit instructions or screenshots for using the Kudu console's Bash shell, not just CMD, to accommodate Linux users.
- Mention that the Azure portal and Kudu tools are accessible from any OS, and clarify that both Bash and CMD are available in Kudu.
- Provide alternative instructions for uploading files and running npm install using Bash commands.
- Reference cross-platform CLI tools (such as Azure CLI) for creating and managing function apps, not just portal-based workflows.
- Ensure that any screenshots or step-by-step instructions do not assume a Windows environment (e.g., file paths, shell prompts).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/durable/durable-functions-serialization-and-persistence.md
...ble/durable-functions-serialization-and-persistence.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on .NET (C#) and other language SDKs for Durable Functions, but does not show any explicit Windows-only tools or PowerShell commands. However, it demonstrates a 'windows_first' bias by presenting .NET/C# examples and explanations first and in the most detail, with other languages (JavaScript, Python, Java) covered only in brief, and with no mention of Linux-specific considerations or parity. There are no Linux-specific examples, tools, or notes, and the documentation assumes the reader is using .NET, which is historically Windows-centric.
Recommendations
- Add explicit Linux and cross-platform notes, especially regarding any differences in serialization libraries or behaviors on Linux vs. Windows.
- Provide parity in code samples: for every .NET example, include equivalent JavaScript, Python, and Java code samples, and ensure these are as detailed as the .NET examples.
- Include a section or callout about platform compatibility, clarifying that Durable Functions and its serialization features are fully supported on Linux-hosted Azure Functions and not just Windows.
- If there are any OS-specific behaviors (e.g., file system paths, environment variables, or dependency installation), document these for both Windows and Linux.
- Consider reordering sections or using tabs to present all language examples equally, rather than leading with .NET/C#.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/deploy-nested-template-environments.md
...es/devtest-labs/deploy-nested-template-environments.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation references Azure PowerShell before Azure CLI when describing deployment commands, and mentions the Visual Studio Azure Resource Group project template as a related tool, both of which are Windows-centric. There are no explicit Linux or cross-platform tool examples, and no mention of Linux-native editors or workflows.
Recommendations
- Present Azure CLI examples before or alongside Azure PowerShell, as Azure CLI is cross-platform.
- Include examples or references for deploying ARM templates using Linux-native tools or shell environments (e.g., Bash scripts, Cloud Shell).
- Mention cross-platform editors such as VS Code, or provide instructions for using ARM templates with editors available on Linux.
- Avoid highlighting Windows-specific tools (like Visual Studio) without also mentioning cross-platform alternatives.
Azure Docs
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation suggests switching to Windows hosting as the primary workaround for Linux limitations, without offering Linux-specific alternatives or examples. There is a lack of guidance for Linux users beyond removing the settings, and no parity in solutions or troubleshooting steps for Linux environments.
Recommendations
- Provide Linux-specific alternatives or workarounds for timezone handling, such as using UTC or handling timezones within application code.
- Offer examples or links to best practices for managing timezones in Linux-based Azure Functions.
- Avoid recommending Windows as the primary or sole solution; instead, present it as one of several options.
- Clarify any platform limitations and suggest cross-platform approaches where possible.
Azure Docs
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by presenting Azure PowerShell examples alongside Azure CLI, and by specifically referencing Windows behaviors (such as drain mode defaults) before or without mentioning Linux equivalents. There are no Linux-specific examples or explicit parity statements, and the CLI examples are platform-agnostic but do not highlight Linux usage or considerations.
Recommendations
- When providing command-line examples, include explicit Linux shell (bash) usage or notes where behaviors or syntax may differ.
- If referencing Windows-specific behaviors (e.g., drain mode defaults), add clarifying statements about Linux or cross-platform applicability.
- Consider including examples or notes for Linux users, such as using Azure CLI in bash, or referencing Linux-specific operational considerations.
- Ensure parity in tool recommendations—if PowerShell is shown, also show bash or shell script equivalents where possible.
- Explicitly state when a feature or behavior is the same or different between Windows and Linux hosting environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-maps/how-to-create-data-registries.md
...//articles/azure-maps/how-to-create-data-registries.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exhibits Windows bias primarily by recommending the use of the Windows-specific Guidgen.exe tool (available with Visual Studio) for generating GUIDs, without mentioning cross-platform or Linux alternatives. There are no command-line examples for Linux or macOS users, and all portal instructions are generic but omit CLI or script-based alternatives that would be relevant for non-Windows environments.
Recommendations
- When suggesting GUID generation, mention cross-platform tools such as 'uuidgen' (available on Linux/macOS) or provide a PowerShell and Bash example.
- Where possible, provide Azure CLI or REST API command examples for tasks like creating managed identities, storage containers, and uploading blobs, in addition to portal-based instructions.
- Avoid referencing Windows-only tools (e.g., Guidgen.exe) without also listing platform-neutral or Linux/macOS equivalents.
- Explicitly state that all steps can be performed on any OS using the Azure Portal, and provide links or examples for CLI/script-based workflows for automation and parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-bindings-openai-embeddingsstore-output.md
...ns/functions-bindings-openai-embeddingsstore-output.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation provides dedicated sections and examples for PowerShell, including explicit mention of function.json and run.ps1 files, which are specific to PowerShell scripting (commonly used on Windows). There are no equivalent bash or shell script examples for Linux users, nor are Linux-specific tools or patterns mentioned. The presence of PowerShell as a first-class example, without Linux shell parity, indicates a Windows/PowerShell bias.
Recommendations
- Add Linux shell (bash/sh) script examples for ingesting files, alongside the PowerShell examples.
- Include instructions or code snippets for configuring and running the binding on Linux environments, not just Windows/PowerShell.
- Where function.json is referenced for PowerShell, clarify its cross-platform usage or provide Linux-specific context/examples.
- Ensure that any tooling or scripting examples are provided for both Windows (PowerShell) and Linux (bash/sh) users.
- Review the order and prominence of examples to avoid implying Windows/PowerShell is the primary or preferred environment.
Azure Docs
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 →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a subtle Windows bias by specifying 'os = windows' as the default in the Gradle configuration and not discussing Linux deployment options or differences. The instructions and examples are otherwise cross-platform (using Bash, Gradle, Azure CLI, and cURL), but the configuration and deployment steps implicitly prioritize Windows as the runtime OS without mentioning Linux alternatives or considerations.
Recommendations
- Explicitly mention that Azure Functions supports both Windows and Linux runtimes, and explain the implications of choosing each.
- Show how to set 'os = linux' in the Gradle configuration, and discuss when a user might want to do so (e.g., for Java 21 support, as noted in the prerequisites).
- Add a note or section describing any differences in deployment, runtime behavior, or supported features between Windows and Linux hosting for Azure Functions.
- Ensure that screenshots, portal instructions, and troubleshooting tips are inclusive of both Windows and Linux scenarios where relevant.
Azure Docs
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 →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented around the Azure Portal GUI and does not provide any command-line examples for creating or managing resources. There is no mention of cross-platform CLI tools (such as Azure CLI or Azure Functions Core Tools), nor are there any Linux-specific instructions or examples. All steps assume use of a browser-based GUI, which is more common in Windows-centric workflows. There is also an implicit bias toward Windows by omission, as no Linux or macOS terminal workflows are described.
Recommendations
- Add parallel instructions using Azure CLI and Azure Functions Core Tools for all resource creation and management steps.
- Provide code snippets for creating the Cosmos DB account, function app, and containers using CLI commands that work on Linux, macOS, and Windows.
- Include a section on developing and deploying Azure Functions locally from Linux/macOS environments, referencing relevant tools and patterns.
- Explicitly mention that all steps can be performed from any OS, and provide links to cross-platform tooling documentation.
- Balance screenshots and examples by including terminal/CLI output in addition to GUI images.
Azure Docs
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 →
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 specifically recommended is .NET, which is often associated with Windows. No PowerShell or Windows-only CLI commands are present, but the lack of Linux parity is notable.
Recommendations
- Provide explicit instructions and notes for both Windows and Linux hosting options for Azure Functions, including any differences in configuration or limitations.
- Include examples or callouts for Linux-based function apps, such as supported runtime stacks and any OS-specific considerations.
- Avoid recommending Windows as the default or 'best experience' unless there are clear technical reasons, and if so, explain those reasons and provide guidance for Linux users.
- Where possible, use cross-platform language and screenshots, or provide both Windows and Linux variants.
- Add a section or note clarifying any differences in NAT gateway integration for Linux-hosted function apps.
Azure Docs
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 providing instructions for creating a Windows Server virtual machine and showing only Windows-based screenshots and steps. There are no examples or guidance for creating or using a Linux-based VM, nor are there any Linux-specific instructions or considerations. This may lead Linux users to believe that the tutorial is only applicable to Windows environments.
Recommendations
- Provide parallel instructions and screenshots for creating both Windows and Linux virtual machines in Azure.
- Explicitly mention that either Windows or Linux VMs can be used, and highlight any differences in setup or access.
- Include examples of accessing the function app from both Windows and Linux VMs (e.g., using SSH for Linux, RDP for Windows).
- Where tools or commands are referenced (such as for function deployment or testing), provide both Windows (PowerShell/Command Prompt) and Linux (Bash) equivalents.
- Add a note or section addressing Linux users, clarifying that the steps are applicable regardless of the VM OS, and link to relevant Linux VM creation documentation.
Azure Docs
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell tab is present and detailed, which may indicate a slight Windows bias. However, the CLI examples use Bash-style variable assignment, which is cross-platform but most familiar to Linux/macOS users. There are no explicit Linux-only instructions or tools, but also no exclusive Windows tools or patterns. The order of tabs (CLI before PowerShell) helps reduce bias, but the presence of PowerShell as a primary alternative (rather than, for example, Bash scripting) still reflects a mild Windows-centric approach.
Recommendations
- Add explicit Bash/Linux shell scripting examples where appropriate, especially for users on Linux/macOS.
- Clarify that Azure CLI commands work on all platforms and provide any necessary notes for platform-specific differences.
- Consider including a 'Bash' or 'Linux/macOS' tab alongside or instead of PowerShell for parity.
- If PowerShell is included, note that PowerShell Core is cross-platform, or provide links to install it on Linux/macOS.
- Review all instructions to ensure no steps assume a Windows environment (e.g., file paths, environment variable syntax).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-create-vnet.md
...ain//articles/azure-functions/functions-create-vnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by explicitly stating that the tutorial uses Windows and C#, and by selecting Windows as the operating system in the setup instructions. While it mentions that Linux is also supported, there are no Linux-specific examples, screenshots, or guidance. All configuration steps, deployment, and testing are described using the Azure Portal UI, which is platform-agnostic, but the language and defaults reinforce a Windows-centric approach. There are no command-line (CLI) or scripting examples for either Windows or Linux, but the explicit focus on Windows in the narrative and configuration tables, without parallel Linux guidance, constitutes a bias.
Recommendations
- Provide parallel instructions or explicit notes for Linux users, including screenshots or callouts where UI or behavior may differ.
- Include examples or references for deploying function apps using Linux as the operating system, such as selecting Linux in the setup tables.
- Offer sample code or deployment steps for other supported languages (e.g., Python, JavaScript) to reduce the C#/Windows focus.
- Add CLI (Azure CLI, Bash) or PowerShell command examples for resource creation and configuration, ensuring both Windows and Linux shells are represented.
- Clarify in each step where the instructions are identical for Linux, or highlight any differences, to reassure Linux users of parity.
Azure Docs
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 →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by exclusively using Azure Portal (web UI) instructions and omitting any command-line examples. There are no CLI, PowerShell, or Bash commands provided for creating or managing the function or storage queue, which would be important for Linux or cross-platform users. The workflow assumes users interact with Azure resources via the portal, a pattern more common among Windows users.
Recommendations
- Add Azure CLI examples for creating the function app, queue trigger, and storage queue. These commands work cross-platform (Windows, Linux, macOS).
- Include Bash shell examples for Linux users, especially for queue message insertion and verification.
- If PowerShell examples are added, ensure equivalent Bash/Azure CLI examples are provided and presented with equal prominence.
- Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and link to relevant CLI documentation.
- Consider a section or callout for 'Command-line alternative' to the portal steps, ensuring parity for users who prefer or require non-GUI workflows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/functions-identity-access-azure-sql-with-managed-identity.md
...ctions-identity-access-azure-sql-with-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by referencing tools and workflows that are more familiar or accessible to Windows users (such as SQLCMD and the Azure Portal), and by omitting explicit Linux or cross-platform command-line examples. While Azure CLI is used (which is cross-platform), there are no Linux-specific instructions or examples, and the SQL tool example assumes the use of SQLCMD, which is less common on Linux. There is also a tendency to mention PowerShell as an alternative, but not to provide Bash or Linux-native alternatives.
Recommendations
- Explicitly mention that Azure CLI and SQLCMD are available on Linux, macOS, and Windows, and provide installation links or notes for non-Windows users.
- Include example commands for common Linux shells (e.g., Bash) where appropriate, especially for SQLCMD usage.
- When referencing PowerShell, also reference Bash or other Linux-native shells, and provide equivalent commands.
- Consider including screenshots or instructions for both Windows and Linux environments when demonstrating portal or CLI workflows.
- Add a note or section addressing any differences or prerequisites for Linux/macOS users, such as package installation or environment setup.
Azure Docs
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 →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally presents Windows and Linux options in parallel, but there are subtle signs of Windows bias. Windows is often mentioned first in tables and explanations (e.g., 'Windows: 100, Linux: 20-100'), and pricing links for Dedicated plans point to the Windows App Service pricing page. There are no explicit PowerShell-heavy examples or missing Linux examples, but the ordering and some references (such as App Service plan rates) prioritize Windows.
Recommendations
- Alternate the order of Windows and Linux mentions in tables and explanations, or present Linux first where it is the primary or only supported OS (e.g., Flex Consumption plan).
- Provide equivalent pricing links for both Windows and Linux App Service plans in the Dedicated plan section.
- Ensure that references to App Service plan rates and features clarify differences between Windows and Linux hosting, rather than defaulting to Windows.
- Where features are Linux-only (e.g., container support), highlight Linux as the primary platform rather than as an alternative.
- Consider adding explicit Linux-focused examples or callouts where relevant, especially for container scenarios.
Azure Docs
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Visual Studio (a primarily Windows tool) for C# class library functions and omitting any mention of Linux or cross-platform alternatives for development or management tasks. There are no command-line examples (PowerShell, Bash, or otherwise), but the only development tool mentioned is Windows-centric. No Linux-specific instructions, tools, or parity examples are provided.
Recommendations
- Include references to cross-platform development tools such as Visual Studio Code, Azure CLI, or other editors that work on Linux and macOS.
- Provide examples or links for managing Azure Functions and API Management using the Azure CLI or Bash scripts, not just portal or Visual Studio workflows.
- Explicitly state that the steps apply equally to Linux and macOS users, or provide any necessary caveats or alternative instructions.
- If mentioning Visual Studio, also mention Visual Studio Code and other cross-platform IDEs, especially for non-Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-functions/manage-connections.md
...b/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 omits any explicit Linux- or Unix-specific tools, patterns, or shell commands. References to configuration files (such as local.settings.json) and project files (function.proj) are presented in a way that assumes a Windows/.NET-centric development environment. There are no Linux shell or cross-platform CLI examples, and the guidance on connection strings and application settings does not mention Linux-specific deployment or configuration patterns.
Recommendations
- Include examples or notes for Linux/macOS environments, such as using environment variables or configuration files in Linux deployments.
- When referencing configuration files (like local.settings.json), clarify their usage in both Windows and Linux environments, and mention any differences in file paths or environment variable handling.
- Provide shell command examples (e.g., using Azure CLI or Bash) for setting application settings or connection strings, not just through the Azure Portal or Windows-based methods.
- Ensure that any project or dependency management instructions (such as function.proj) are accompanied by equivalent guidance for non-.NET stacks or clarify how to manage dependencies in Linux-based environments.
- Explicitly state that the patterns and recommendations apply equally to Linux-hosted Azure Functions, and provide troubleshooting tips or links for Linux-specific issues if applicable.
Azure Docs
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 provides both Windows and Linux examples for most ARM/Bicep template scenarios, and covers Linux-specific hosting plans (e.g., Flex Consumption, Container Apps, Azure Arc) in detail. However, there is a consistent pattern of presenting Windows examples and terminology before Linux equivalents, especially in code tabs and explanatory text. Additionally, the only explicit command-line deployment examples outside of Azure CLI are for PowerShell, with no Bash or cross-platform shell equivalents provided. Some references to tools (e.g., Visual Studio Code extensions) are cross-platform, but the deployment section is PowerShell-centric.
Recommendations
- Alternate the order of Windows and Linux examples/tabs, or present Linux first where it is the default or recommended platform.
- Provide Bash or cross-platform shell equivalents for all PowerShell deployment examples, especially for template deployment and resource group creation.
- Explicitly mention that all ARM/Bicep templates and Azure CLI commands are cross-platform, and provide sample commands for both Windows and Linux environments.
- Where possible, use neutral language (e.g., 'on your system' instead of 'on Windows') unless the content is truly OS-specific.
- Highlight Linux-specific considerations or best practices earlier in the document, not only as addenda to Windows instructions.
Azure Docs
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 explanations for Windows-based Azure Functions hosting plans, while repeatedly noting missing or unsupported features for Linux plans. There are explicit statements that certain metrics are not supported for Premium and Dedicated (App Service) plans running on Linux, and that metrics are unavailable for Linux in Consumption plans. No Linux-specific guidance, workarounds, or parity information is provided, and no Linux command-line or tooling examples are present.
Recommendations
- Provide Linux-specific guidance or alternatives where metrics or features are not supported, including suggested workarounds or links to feature requests.
- Include explicit examples or documentation for monitoring Azure Functions on Linux, such as using Linux-native tools or Application Insights queries.
- Clarify roadmap or expected support for Linux parity, so users are aware of future improvements.
- Where features are unsupported on Linux, suggest equivalent monitoring strategies or third-party tools that Linux users can employ.
- Ensure that documentation structure does not always present Windows/Windows App Service as the default, but instead treats Linux and Windows equally in explanations and examples.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/devtest-lab-hibernate-vm.md
...ain//articles/devtest-labs/devtest-lab-hibernate-vm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by only providing examples and screenshots for Windows VMs (e.g., explicitly referencing Windows 11 Pro as the base image and showing 'select your Windows VM'). There are no Linux-specific instructions, examples, or screenshots, and the process is described only in the context of Windows, with no mention of Linux compatibility or differences.
Recommendations
- Add explicit instructions and screenshots for creating and managing Linux VMs with hibernation enabled in DevTest Labs.
- Mention Linux as a supported OS (if applicable), including any prerequisites or differences in the hibernation process for Linux VMs.
- When listing example base images, include both Windows and popular Linux distributions (e.g., Ubuntu, CentOS) to demonstrate parity.
- Ensure that screenshots and step-by-step guides are provided for both Windows and Linux VM scenarios, or clarify if the process is identical.
- If there are limitations or unsupported scenarios for Linux, clearly document them to inform users.