← Back to Dashboard
208
Pages Scanned
45
Pages Flagged
208
Changed Pages
21.6%
% Pages Flagged

Scan Information

Started At: 2026-02-09 00:00:06

Finished At: 2026-02-10 18:44:36

Status: completed

Target Repo: Azure

Current Phase: discovery

Files Queued: 208

Files Completed: 208

Problematic Pages

46 issues found
Artifact Signing Set up signing integrations to use Artifact Signing ...ticles/artifact-signing/how-to-signing-integrations.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation is heavily focused on Windows, especially in the main 'Set up SignTool to use Artifact Signing' section. All setup instructions, prerequisites, and examples assume a Windows environment, referencing Windows-only tools (SignTool, MSI installers, WinGet, PowerShell, Visual C++ Redistributable). There are no Linux or macOS equivalents or alternative instructions provided for the core signing workflow. Other integrations (GitHub Actions, Azure DevOps, SDK) are mentioned, but not documented in detail here.
Recommendations
  • Clearly state at the beginning if SignTool integration is Windows-only, and direct Linux/macOS users to alternative integrations (e.g., GitHub Actions, SDK).
  • For each integration, specify platform support and provide parity in setup instructions/examples for Linux/macOS where possible.
  • If Artifact Signing supports Linux/macOS workflows (e.g., via SDK, GitHub Actions), add explicit sections or links with step-by-step instructions for those platforms.
  • For PowerShell or WinGet commands, offer equivalent Bash or shell commands if supported, or clarify that these are Windows-only.
  • Summarize all supported platforms and tools in a table at the top, with links to relevant setup guides for each OS.
GitHub Create Pull Request
Application Gateway Overview of mutual authentication on Azure Application Gateway .../application-gateway/mutual-authentication-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page provides configuration instructions for mutual authentication on Azure Application Gateway, with a notable emphasis on Azure PowerShell examples and references. PowerShell instructions are given in detail, with CLI examples present but less comprehensive. The 'Next steps' section directs users specifically to a PowerShell-based guide, and there is no mention of Linux-specific tools or workflows (e.g., Bash scripting, OpenSSL usage for certificate extraction, or Linux-based automation). This creates friction for Linux/macOS users who may prefer Bash/CLI or require platform-agnostic guidance.
Recommendations
  • Ensure CLI examples are as detailed and comprehensive as PowerShell examples, including step-by-step instructions for all major configuration tasks.
  • Add Linux/macOS-specific guidance for certificate extraction and management, such as using OpenSSL commands.
  • Provide parity in 'Next steps' by linking to CLI/Bash-based configuration guides alongside PowerShell guides.
  • Clarify that both PowerShell and CLI are cross-platform, and highlight any platform-specific limitations if present.
  • Consider including example workflows for certificate management and upload using Bash or Linux-native tools.
GitHub Create Pull Request
Automation Configure runbook input parameters in Azure Automation ...b/main/articles/automation/runbook-input-parameters.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation is heavily focused on PowerShell and Windows-centric patterns, with nearly all examples, screenshots, and code snippets using PowerShell or referencing Windows tools. There is minimal coverage of Python runbooks, and no examples or guidance for Linux/macOS users on how to interact with Azure Automation runbooks outside of PowerShell. The REST API and SDK sections are platform-neutral, but the practical, step-by-step instructions and sample workflows are overwhelmingly Windows/PowerShell-oriented.
Recommendations
  • Provide equivalent examples for Linux/macOS users, such as using Azure CLI or Bash scripts to start runbooks and pass parameters.
  • Expand the Python runbook section with concrete examples, including how to start Python runbooks from Linux/macOS environments.
  • Add guidance for using REST API and SDKs from non-Windows platforms, including sample Bash/cURL commands.
  • Clarify that PowerShell examples are applicable on Linux/macOS where PowerShell Core is available, and provide notes or examples for cross-platform usage.
  • Include troubleshooting tips for Linux/macOS users, such as handling authentication and file paths.
GitHub Create Pull Request
Automation Manage certificates in Azure Automation ...n/articles/automation/shared-resources/certificates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page heavily features PowerShell cmdlets and examples, with all certificate management tasks (creation, retrieval, deployment) demonstrated exclusively using PowerShell. There are no Linux/macOS shell (bash/CLI) examples, and PowerShell is presented first and most extensively. The Python section is included for runbooks, but lacks parity in certificate creation and management instructions compared to PowerShell. There is no mention of Linux tools or cross-platform alternatives for certificate handling.
Recommendations
  • Add Azure CLI examples for certificate creation, management, and retrieval to provide Linux/macOS parity.
  • Include bash or shell script examples for uploading and managing certificates where possible.
  • Clarify whether PowerShell examples are cross-platform (PowerShell Core) or Windows-only, and provide guidance for Linux/macOS users.
  • Mention any limitations or differences for Linux/macOS users in Azure Automation certificate management.
  • Ensure Python examples include certificate creation and management, not just retrieval.
GitHub Create Pull Request
Azure Functions Azure Functions networking options ...ticles/azure-functions/functions-networking-options.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and Azure portal, but PowerShell examples are included alongside CLI, and Hybrid Connections are described as Windows-only. The Hybrid Connections section is Windows-focused, and PowerShell is presented as a primary automation tool. Linux-specific guidance is limited, and Linux parity is not always clear in automation or troubleshooting sections.
Recommendations
  • Clearly indicate Linux/macOS compatibility for all features and tools, especially in automation sections.
  • Provide Linux/macOS-specific examples (e.g., Bash scripts, CLI-only workflows) alongside PowerShell examples.
  • In troubleshooting and automation sections, ensure that CLI examples are shown before PowerShell, or at least equally.
  • Explicitly state when a feature is Windows-only, and offer alternative guidance for Linux users where possible.
  • Expand documentation for Hybrid Connections to clarify alternatives for Linux-hosted function apps.
GitHub Create Pull Request
Application Gateway Scaling and Zone-redundant Application Gateway v2 ...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page primarily references Azure PowerShell for creating autoscaling, zone-redundant Application Gateway v2 instances, with no mention of Azure CLI or ARM template equivalents. The 'Next steps' section links only to a PowerShell tutorial, which may create friction for Linux/macOS users who typically use Azure CLI or other tools.
Recommendations
  • Add equivalent Azure CLI and ARM template examples and tutorials for creating autoscaling, zone-redundant Application Gateway v2.
  • In the 'Next steps' section, provide links to both PowerShell and CLI/ARM template guides, or clarify that PowerShell is not required.
  • Ensure that all procedural instructions are platform-neutral or include cross-platform options.
GitHub Create Pull Request
API Management Deploy an Azure API Management Instance to Multiple Azure Regions ...management/api-management-howto-deploy-multi-region.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides command-line examples for managing API Management regional gateways using Azure CLI and Azure PowerShell, mentioning PowerShell before Linux-native alternatives. The PowerShell cmdlet is referenced alongside Azure CLI and REST API, but no Bash or Linux shell scripting examples are provided. The documentation refers to the Azure portal UI, which is cross-platform, but command-line automation examples are Windows-centric.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI commands, including sample scripts for disabling/enabling gateways.
  • Clarify that Azure CLI is cross-platform and can be used on Linux/macOS, and provide installation links for non-Windows platforms.
  • When listing automation tools, mention Azure CLI and REST API before PowerShell, or group them together to avoid Windows-first ordering.
  • Where PowerShell is referenced, provide equivalent Bash or shell scripting examples for parity.
GitHub Create Pull Request
App Service Use TLS/SSL Certificates in App Code ...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page provides detailed, language-specific examples (C#, Java) for loading certificates in Windows apps and containers, including use of the Windows certificate store and related APIs. Linux guidance is limited to generic file loading, with only C# examples for Linux containers. For other languages (Node.js, PHP, Python, Java), Linux users are referred to external documentation, while Windows users get in-page code samples. Windows-specific tools and patterns (certificate store, environment variables) are discussed first and in more depth.
Recommendations
  • Add Linux-specific code samples for popular languages (Node.js, Python, Java, PHP) showing how to load certificates from file paths in Linux containers.
  • Provide parity in guidance for Linux apps, including how to handle certificate permissions, file formats, and environment variables.
  • Reorganize sections so Linux and Windows guidance are presented side-by-side or equally, rather than Windows-first.
  • Clarify that some Windows-specific APIs (like certificate store access) are not available on Linux, and offer Linux alternatives.
  • Expand the 'Load a certificate from a file' section with concrete Linux examples for multiple languages.
GitHub Create Pull Request
App Service Install a TLS/SSL Certificate for Your App ...main/articles/app-service/configure-ssl-certificate.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for RBAC permissions, but PowerShell is mentioned and shown as a primary option in several places. Windows-specific tools (IIS, Certreq.exe) are referenced for certificate export, and Windows tooling is mentioned before Linux equivalents. While OpenSSL is covered for Linux/macOS users, Windows export instructions are more detailed and linked. The FAQ and automation sections also highlight PowerShell scripts alongside CLI, but do not provide Bash or Linux-native scripting examples. Overall, Linux users can complete all tasks, but Windows tools and patterns are more prominent.
Recommendations
  • Provide Linux/macOS-specific instructions and examples alongside Windows tools (e.g., show Bash scripting for automation, not just PowerShell).
  • Ensure OpenSSL instructions are as detailed as Windows export instructions, including troubleshooting and password management.
  • Mention Linux-native certificate management tools (such as certbot or keytool) where relevant, or clarify their applicability.
  • When referencing automation, include Bash/CLI scripts as first-class options, not just PowerShell.
  • Balance the order of examples so Linux/CLI instructions are not always after Windows/PowerShell.
GitHub Create Pull Request
App Service Environment Variables and App Settings Reference ...ob/main/articles/app-service/reference-app-settings.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page covers environment variables and app settings for Azure App Service, which supports both Windows and Linux. However, there is a notable Windows bias: Windows-specific paths, tools, and terminology (e.g., 'D:\home', IIS, msbuild, Web Deploy/MSDeploy, site extensions, .bat files, Windows container settings) are often mentioned first or exclusively. Some examples and explanations use Windows conventions without always providing Linux equivalents. While Linux-specific sections (Oryx, Linux containers, language runtimes) are present, Windows-centric information is more prominent and detailed, and Linux examples or explanations are sometimes missing or less thorough.
Recommendations
  • Ensure all environment variable examples include both Windows and Linux paths/formats (e.g., 'D:\home' and '/home').
  • Where Windows tools (e.g., msbuild, Web Deploy/MSDeploy, .bat files) are mentioned, provide Linux alternatives or clarify applicability.
  • Present Linux and Windows information in parallel, rather than Windows-first (e.g., in tables, list both OSes or use tabs).
  • Expand Linux-specific explanations and examples, especially for deployment, logging, and build automation.
  • Clarify when a variable or feature is Windows-only, Linux-only, or cross-platform.
  • Add more Linux-specific troubleshooting, paths, and tool references where appropriate.
GitHub Create Pull Request
Application Gateway Diagnostic logs ...application-gateway/application-gateway-diagnostics.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides a PowerShell-only example for enabling diagnostic logging, with no equivalent Azure CLI, Bash, or ARM template example. The only programmatic example is Windows-centric, and there is a reference to using Visual Studio and a .NET-based log converter tool, which are also Windows-focused. There are no Linux/macOS-specific instructions or parity in scripting examples.
Recommendations
  • Add equivalent Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script examples where appropriate.
  • Mention and link to cross-platform log conversion tools (e.g., Python-based or jq for JSON processing) instead of only Visual Studio/.NET tools.
  • Reorder or supplement sections so that cross-platform methods (Azure portal, Azure CLI) are presented before or alongside PowerShell.
  • Explicitly state that PowerShell Core is available cross-platform if retaining PowerShell examples, and provide installation guidance if relevant.
GitHub Create Pull Request
Application Gateway Configure Azure Application Gateway TCP/TLS proxy ...n/articles/application-gateway/how-to-tcp-tls-proxy.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation exclusively uses Windows-based SQL Server VM and SQL Server Management Studio (SSMS) for client connectivity. There are no examples or guidance for Linux-based SQL Server VMs or Linux/macOS client tools. Windows options are mentioned first and solely, creating friction for Linux/macOS users who wish to test or deploy the TCP/TLS proxy feature.
Recommendations
  • Include instructions for deploying a SQL Server VM on Linux (e.g., Ubuntu with SQL Server 2019/2022).
  • Provide examples of connecting to the Application Gateway using cross-platform SQL clients such as Azure Data Studio, sqlcmd, or other CLI tools available on Linux/macOS.
  • Mention Linux-compatible SQL Server images in the VM creation step, or clarify that Linux is supported if applicable.
  • Add notes or links for Linux/macOS users about alternative client tools and any relevant configuration differences.
GitHub Create Pull Request
Application Gateway Migrate from V1 to V2 - Azure Application Gateway ...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation is heavily focused on Azure PowerShell scripts and cmdlets for migration, with all examples, installation instructions, and script usage exclusively referencing PowerShell. There are no CLI (az), Bash, or Linux/macOS shell examples or guidance. Script installation and execution instructions assume a Windows/PowerShell environment, and PowerShell Gallery is referenced as the primary distribution method. The documentation does not mention or provide alternatives for Linux/macOS users, nor does it clarify whether the scripts are cross-platform compatible.
Recommendations
  • Add Azure CLI (az) equivalents for key migration steps, or clarify if migration is only possible via PowerShell.
  • Explicitly state PowerShell cross-platform support (if available), and provide instructions for running scripts on Linux/macOS (e.g., using PowerShell Core).
  • Include Bash or shell script alternatives, or at least note limitations for Linux/macOS users.
  • Mention prerequisites for Linux/macOS environments (e.g., PowerShell Core installation, compatibility notes).
  • Provide guidance for users who prefer Azure Cloud Shell (which supports PowerShell and Bash), and clarify which script methods are supported there.
  • Consider reordering or balancing examples so that Windows and Linux/macOS users are equally addressed.
GitHub Create Pull Request
Automation Disaster recovery for Azure Automation ...in/articles/automation/automation-disaster-recovery.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for disaster recovery in Azure Automation is heavily focused on PowerShell scripts and workflows for asset migration, with no equivalent examples or guidance for Linux-native tools (such as Bash, CLI, or Python). All migration instructions and runbook examples are PowerShell-based, and references to script execution are tied to Windows-centric tooling. While the page states applicability to both Linux and Windows VMs, Linux users are left without clear guidance or parity for migration tasks.
Recommendations
  • Provide Bash or Azure CLI script examples for asset migration, or reference Python-based approaches if available.
  • Clarify whether PowerShell Core (cross-platform) is supported and provide instructions for Linux/macOS environments.
  • Add explicit guidance for Linux users on how to execute migration scripts/runbooks, including prerequisites and tooling.
  • Mention or link to any available Python runbooks or modules for asset migration, if supported.
  • Ensure that instructions for Hybrid Runbook Worker installation reference both Windows and Linux tabs equally, not just Windows.
GitHub Create Pull Request
Automation Use Microsoft Entra ID in Azure Automation to authenticate to Azure ...ob/main/articles/automation/automation-use-azure-ad.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page is heavily focused on Windows PowerShell, with all code examples, module references, and credential handling instructions using PowerShell cmdlets and Windows-specific concepts. There are no examples or guidance for Linux/macOS users, such as using Python, Bash, or cross-platform Azure CLI. The page refers to 'Windows PowerShell' explicitly and does not mention alternatives or parity for non-Windows environments.
Recommendations
  • Add examples using Azure CLI, which is cross-platform, for credential asset creation and authentication.
  • Clarify whether Azure Automation runbooks can be authored in Python or other languages, and provide equivalent examples if possible.
  • Mention that PowerShell Core (pwsh) is available on Linux/macOS and indicate whether the provided scripts are compatible.
  • Provide guidance for Linux/macOS users on how to install and use required modules (e.g., Az, Microsoft Graph PowerShell SDK) in their environments.
  • Explicitly state any limitations or Windows-only requirements for Azure Automation, if applicable.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page for Azure Application Gateway v2 shows a notable bias towards Windows/PowerShell tooling. Azure PowerShell is referenced as the primary method for migration and for registering/unregistering the Basic SKU preview, with no equivalent Azure CLI (bash), ARM template, or Terraform examples. The 'Next steps' section also links to a PowerShell-based tutorial first. This creates friction for Linux/macOS users who may prefer cross-platform tools.
Recommendations
  • Provide Azure CLI (bash) equivalents for all PowerShell commands and scripts, especially for migration and feature registration/unregistration.
  • Include ARM template and/or Terraform examples for common deployment and migration scenarios.
  • When listing tutorials or next steps, offer both PowerShell and CLI/ARM/other cross-platform options, or clarify which tools are supported.
  • Explicitly state if certain operations are only possible with PowerShell, and provide guidance for non-Windows users (e.g., using Azure Cloud Shell).
GitHub Create Pull Request
Application Gateway FAQ on V1 retirement ...ob/main/articles/application-gateway/retirement-faq.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page frequently references Azure PowerShell scripts as the primary migration tooling, without mentioning Azure CLI or Bash alternatives. All migration automation examples and scripts are PowerShell-based, and there is no guidance for Linux/macOS users or parity in scripting options. This creates friction for non-Windows users, as PowerShell is not always installed or preferred on Linux/macOS, and Azure CLI is a common cross-platform tool.
Recommendations
  • Provide equivalent Azure CLI/Bash scripts for migration tasks, especially for public IP retention and configuration migration.
  • Explicitly mention that PowerShell scripts can be run cross-platform (on Linux/macOS) if applicable, and link to installation instructions.
  • Add examples or guidance for Linux/macOS users, including any prerequisites or differences in script execution.
  • Where possible, offer both PowerShell and Azure CLI options for key migration steps.
GitHub Create Pull Request
Automation Azure Automation data security ...b/main/articles/automation/automation-managing-data.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides both Windows and Linux guidance for TLS upgrades, but Windows-specific instructions and PowerShell cmdlets are mentioned first or exclusively in several sections. Data retention and backup instructions reference Windows PowerShell cmdlets without Linux CLI or scripting equivalents, and Windows registry settings are linked before Linux OpenSSL guidance. Linux examples are present but less detailed and less prominent.
Recommendations
  • Provide equivalent Linux CLI or scripting examples for data retention and backup tasks, such as using Azure CLI or REST API instead of only PowerShell.
  • Balance the order of platform-specific guidance so Linux instructions are not always secondary to Windows.
  • Where PowerShell cmdlets are referenced, also mention Azure CLI or relevant REST API methods for cross-platform users.
  • Expand Linux-specific backup and export instructions, e.g., how to export runbooks or DSC configurations using Azure CLI or portal.
  • Clarify which tasks are platform-agnostic and which require Windows tools, to help Linux/macOS users navigate the documentation.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page for managing credentials in Azure Automation is heavily focused on PowerShell and Windows-centric tooling. All CLI examples use PowerShell cmdlets, and the process for creating credential assets outside the portal is described only with Windows PowerShell. There is no mention of Linux-native CLI tools or Bash/Az CLI equivalents for credential management. PowerShell examples are presented before Python, and no Linux shell or cross-platform CLI examples are provided.
Recommendations
  • Add equivalent examples using Azure CLI (az) for credential asset management, if supported.
  • Clarify whether PowerShell examples can be run cross-platform (e.g., PowerShell Core on Linux/macOS), or provide instructions for non-Windows environments.
  • Explicitly state any platform limitations (e.g., if credential management is only possible via PowerShell on Windows).
  • Provide guidance or links for Linux/macOS users on how to manage credentials in Azure Automation using supported tools.
  • Consider adding Bash or REST API examples for credential management, if available.
GitHub Create Pull Request
Azure App Configuration Monitor Azure App Configuration ...s/azure-app-configuration/monitor-app-configuration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides monitoring instructions for Azure App Configuration using the Azure Portal, Azure CLI, and PowerShell. While the Azure CLI section is cross-platform, the PowerShell section is Windows-centric and explicitly instructs users to open a Windows PowerShell command window. Additionally, in the CLI section, Windows PowerShell is mentioned as an example of a command console application before any Linux/macOS alternatives. No Linux/macOS-specific instructions or terminal examples are provided, and PowerShell is presented as a primary scripting option, which may create friction for Linux/macOS users.
Recommendations
  • In the Azure CLI section, clarify that CLI commands can be run from any terminal on Windows, Linux, or macOS, not just Windows PowerShell.
  • In the PowerShell section, note that PowerShell Core is available cross-platform and provide instructions for Linux/macOS users, or explicitly state that this section is Windows-specific.
  • Add example terminal instructions for Linux/macOS users (e.g., 'Open a terminal on Linux/macOS').
  • Consider mentioning Bash or other common Linux/macOS shells as alternatives for running Azure CLI commands.
  • Review screenshots and UI references to ensure they are not Windows-specific unless necessary.
GitHub Create Pull Request
Azure Change Tracking Inventory Azure Change Tracking and Inventory Overview by Using Azure Monitor Agent ...change-tracking-inventory/overview-monitoring-agent.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation covers both Windows and Linux for most features, but there is notable bias toward Windows. Registry key tracking is exclusively described for Windows, with no mention of Linux equivalents (such as tracking configuration files or systemd units). Windows terminology and tools (registry, Windows services) are discussed in detail, while Linux-specific examples (daemons, config files) are not provided. Windows registry keys are listed extensively, but no Linux-specific tracking targets are mentioned. Windows is often referenced first in examples and explanations.
Recommendations
  • Add Linux-specific examples for tracked items, such as configuration files, systemd units, or package managers.
  • Provide a table or section listing typical Linux targets for change tracking (e.g., /etc/passwd, /etc/ssh/sshd_config, systemd service files).
  • Balance the registry key section with a corresponding Linux section describing what can be tracked (e.g., important config files, cron jobs, init scripts).
  • Ensure that Linux terminology (daemons, services, config files) is given equal prominence to Windows terminology.
  • Where screenshots or examples are shown, include both Windows and Linux variants.
GitHub Create Pull Request
Azure Functions Quickstart: Create a Durable Functions app that uses the MSSQL storage provider ...n/articles/azure-functions/durable/quickstart-mssql.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page provides PowerShell-based setup instructions for the local SQL Server Docker instance, with no equivalent Bash or Linux shell examples. Windows-centric tools and patterns (PowerShell scripting, references to SQL Server Express on Windows) are mentioned before Docker-based approaches, and Linux/macOS users are not given explicit guidance or examples for their platforms. The lack of parity may create friction for non-Windows users, especially in the database setup phase.
Recommendations
  • Add Bash shell script examples for setting up SQL Server Docker containers, alongside the PowerShell examples.
  • Explicitly mention that the PowerShell commands can be run on Linux/macOS with PowerShell Core, but also provide native Bash alternatives.
  • Clarify that SQL Server Express is Windows-only and recommend Docker as the preferred cross-platform local development option.
  • Reorder instructions to present Docker-based setup as the primary, cross-platform method, rather than referencing Windows tools first.
  • Include troubleshooting tips for Linux/macOS users, such as file permissions or Docker networking differences.
GitHub Create Pull Request
Azure Functions Migrate C# app from in-process to isolated worker model ...es/azure-functions/migrate-dotnet-to-isolated-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides only Azure PowerShell scripting for identifying function apps to migrate, with no mention of Bash, Azure CLI, or cross-platform alternatives. PowerShell is presented as the default tool for subscription-level operations, which may create friction for Linux/macOS users who typically use Azure CLI or Bash. However, the rest of the guide is largely platform-neutral, focusing on .NET code and project files.
Recommendations
  • Add Azure CLI or Bash script examples alongside the Azure PowerShell script for identifying function apps to migrate.
  • Explicitly mention that Azure CLI can be used as an alternative to PowerShell for cross-platform users.
  • Consider presenting cross-platform tools (Azure CLI) before or alongside PowerShell to avoid Windows-first bias.
  • Where possible, clarify that Visual Studio Code and Azure Functions Core Tools are cross-platform and provide links to Linux/macOS installation guides.
GitHub Create Pull Request
Azure Functions Troubleshoot Python function apps in Azure Functions ...n/articles/azure-functions/recover-python-functions.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation generally focuses on cross-platform guidance but exhibits some Windows bias in certain troubleshooting steps. In particular, command examples for checking Python bitness and deleting directories are presented with Windows/PowerShell first or exclusively, and some sections provide more detailed instructions for Windows users. Linux/macOS equivalents are sometimes present but not always given equal prominence or detail.
Recommendations
  • Ensure all command-line examples are presented for both Windows (PowerShell/CMD) and Linux/macOS (Bash), and in parallel tabs or with equal prominence.
  • When listing commands, alternate the order or present Linux/macOS examples first in some cases to avoid always privileging Windows.
  • Where possible, provide explicit Linux/macOS instructions for all troubleshooting steps, not just Windows.
  • Review sections where only Windows tools or patterns are mentioned and add Linux/macOS equivalents where applicable.
  • Clarify when a step is Windows-only, and provide alternative guidance for Linux/macOS users.
GitHub Create Pull Request
API Center Perform API linting and analysis - Azure API Center ...ain/articles/api-center/enable-api-analysis-linting.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides Azure CLI command examples for both bash and PowerShell, but PowerShell syntax is consistently shown immediately after bash, and is explicitly labeled. There are frequent references to running Azure CLI in PowerShell, and notes clarify that commands can run in either shell. However, Linux/macOS users are not given additional guidance or troubleshooting tips, and Visual Studio Code is the only editor mentioned, which is cross-platform but often associated with Windows. No Windows-only tools or patterns are used, but the ordering and explicit PowerShell labeling create a minor Windows-first impression.
Recommendations
  • Provide explicit Linux/macOS troubleshooting tips or notes where relevant (e.g., file path differences, shell environment setup).
  • Consider showing bash examples first, or alternating the order to avoid implicit Windows prioritization.
  • Add references to other popular cross-platform editors (e.g., JetBrains Rider, Vim, etc.) if relevant.
  • Clarify that all steps are fully supported on Linux/macOS, and mention any OS-specific caveats if they exist.
GitHub Create Pull Request
API Center Import APIs from Azure API Management - Azure API Center ...main/articles/api-center/import-api-management-apis.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides Azure CLI command examples for both bash and PowerShell throughout, with both shell types shown side-by-side. However, in several sections, PowerShell examples are labeled as 'Formatted for PowerShell' and are consistently shown after the bash examples, indicating a minor 'windows_first' bias. No Windows-specific tools, patterns, or exclusive Windows instructions are present. Linux parity is generally maintained, but bash examples are always shown first.
Recommendations
  • Consider alternating the order of bash and PowerShell examples in different sections to avoid implicit prioritization.
  • Explicitly state at the beginning that both Linux/macOS (bash) and Windows (PowerShell) are fully supported and that examples are provided for both.
  • Where possible, clarify that Azure CLI commands work identically across platforms, and highlight any platform-specific differences only if they exist.
GitHub Create Pull Request
API Center Include file .../includes/configure-managed-identity-kv-secret-user.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands. However, PowerShell examples are given for every CLI command, and in some cases, PowerShell syntax is shown immediately after Bash, suggesting a Windows-first or PowerShell-heavy bias. There are no Linux-specific tools or patterns missing, but the PowerShell examples may be unnecessary for cross-platform parity, as Bash covers Linux/macOS users.
Recommendations
  • Consider grouping Bash and PowerShell examples under clear tabs (e.g., 'Bash (Linux/macOS)' and 'PowerShell (Windows)') to clarify platform relevance.
  • If Bash examples are sufficient for Linux/macOS, PowerShell examples could be moved to a secondary position or made optional.
  • Explicitly state which examples are for Windows and which are for Linux/macOS to avoid confusion.
  • Ensure Bash examples are shown first or equally prominent for cross-platform parity.
GitHub Create Pull Request
API Center Quickstart - Create Your Azure API Center - ARM Template .../articles/api-center/set-up-api-center-arm-template.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying the ARM template, but PowerShell (a Windows-centric tool) is given equal prominence. There is no explicit Linux/macOS bias, but PowerShell is presented as a standard option, which may create friction for Linux/macOS users. Azure CLI is cross-platform and is shown first, which mitigates the bias somewhat.
Recommendations
  • Clarify that Azure PowerShell is available on Linux/macOS (via .NET Core), or note its Windows origins.
  • Explicitly mention that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Consider adding a Bash shell example (using Azure CLI) to reinforce Linux parity.
  • If relevant, add a note about using Cloud Shell (which supports both CLI and PowerShell) from any OS.
GitHub Create Pull Request
API Center Include file ...ter/includes/configure-managed-identity-apim-reader.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell examples are shown immediately after Bash for every step, indicating a slight Windows-first bias. There is no exclusive use of Windows tools, and Linux examples are present, but the PowerShell formatting is given equal prominence, which may create friction for Linux/macOS users.
Recommendations
  • Clearly label Bash and PowerShell examples with OS context (e.g., 'Linux/macOS (Bash)' and 'Windows (PowerShell)').
  • Consider showing Bash examples first, as Bash is the default shell for Azure CLI and most cross-platform environments.
  • Add a brief note clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users quickly identify the relevant example.
  • If possible, provide a single cross-platform example (Bash) unless PowerShell-specific syntax is required.
GitHub Create Pull Request
API Center Quickstart - Create Your Azure API Center - Bicep ...ob/main/articles/api-center/set-up-api-center-bicep.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell deployment instructions, but PowerShell is featured equally alongside CLI, and PowerShell is a Windows-centric tool. The prerequisites section includes Azure PowerShell requirements, which are primarily relevant for Windows users. However, Azure CLI examples are present and shown first in the deployment section, and Cloud Shell (cross-platform) is mentioned.
Recommendations
  • Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
  • Add explicit notes about cross-platform compatibility, highlighting that Azure CLI works natively on Linux/macOS.
  • Ensure that all instructions (e.g., file upload, path usage) are clear for Linux/macOS users, such as mentioning how to upload files in Cloud Shell or referencing Linux file paths.
  • Consider adding a short section or callout for Linux/macOS users, confirming that all steps are supported and providing any OS-specific tips.
GitHub Create Pull Request
API Management Backup and restore your Azure API Management instance for disaster recovery ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for backup and restore operations, but PowerShell examples are presented first and in greater detail. PowerShell is primarily a Windows-centric tool, and its prominence may create friction for Linux/macOS users. However, full Azure CLI (bash) and REST API examples are also included, ensuring Linux parity for all critical operations.
Recommendations
  • Present Azure CLI examples before PowerShell, or at least in parallel, to avoid Windows-first bias.
  • Expand CLI sections to match the detail and coverage of PowerShell examples, including managed identity scenarios if possible.
  • Explicitly mention that Azure CLI and REST API methods are fully cross-platform and suitable for Linux/macOS users.
  • Add a brief note clarifying that PowerShell is available on Linux/macOS, but CLI is often preferred for those platforms.
GitHub Create Pull Request
API Management Import an OpenAPI specification to Azure API Management | Microsoft Docs ...ob/main/articles/api-management/import-api-from-oas.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. While the Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is most commonly used on Windows) as a primary example, and the explicit mention of PowerShell requirements in the prerequisites, introduces a mild Windows bias. Additionally, PowerShell examples are given equal prominence to CLI examples, and the PowerShell section appears after the CLI section, which is positive, but the overall structure still emphasizes Windows tooling.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
  • Add a note in the PowerShell section indicating that Azure PowerShell is available on Linux/macOS, but CLI is generally more common for non-Windows environments.
  • Consider adding Bash shell scripting examples for CLI usage, highlighting Linux/macOS workflows.
  • Explicitly mention that all tasks can be completed on Linux/macOS using Azure CLI, and link to any relevant Linux/macOS setup guides.
GitHub Create Pull Request
App Service Azure App Service Plans ...ob/main/articles/app-service/overview-hosting-plans.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation for Azure App Service Plans generally maintains OS parity, mentioning both Windows and Linux options throughout. However, in the section about 'Managed Instance on Azure App Service (preview)', Windows-specific features and tools (such as PowerShell, RDP, IIS customization, .NET Framework) are discussed first and exclusively, with explicit mention that this feature is Windows-only. Elsewhere, links and feature tables sometimes reference Windows pricing or features first, but Linux is not omitted.
Recommendations
  • Ensure that all OS-specific features are clearly labeled as Windows-only, as done for Managed Instance.
  • Where possible, provide Linux-specific examples or links alongside Windows ones, especially in pricing and feature comparison sections.
  • When referencing tools or features (e.g., PowerShell, IIS), clarify if Linux equivalents exist or explicitly state if they are Windows-only.
  • Consider linking to Linux-specific documentation or guidance for App Service plans where relevant.
GitHub Create Pull Request
Application Gateway Quickstart: Deploy Application Gateway for Containers ALB Controller ...ploy-application-gateway-for-containers-alb-controller.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides both Windows and Linux instructions for installing Helm, but the Windows example (using winget) is presented first and references Windows-specific tooling. The rest of the guide uses Azure CLI and Bash-compatible commands, which are cross-platform, and explicitly states that Helm commands can be run using Bash. No PowerShell-specific examples are given for core tasks, and Linux parity is generally maintained.
Recommendations
  • Present Linux and Windows installation instructions for Helm in parallel, or default to Linux first, as Linux is the primary OS for most Kubernetes workloads.
  • Explicitly mention macOS installation steps or clarify that Linux instructions also apply to macOS where relevant.
  • Where Windows tools (like winget) are referenced, ensure equivalent Linux/macOS package manager options are also mentioned (e.g., apt, yum, brew).
  • Consider adding a note that Azure CLI and Helm commands are cross-platform and can be run in Bash or PowerShell on any OS.
GitHub Create Pull Request
Azure Cache For Redis Deploy Azure Cache for Redis using Bicep ...s/azure-cache-for-redis/redis-cache-bicep-provision.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and managing Azure Cache for Redis using Bicep. However, PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. There are no explicit Linux/macOS-specific instructions or clarifications, and PowerShell is presented as a primary option alongside CLI, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add a note indicating that Azure PowerShell is primarily for Windows users, and that Azure CLI works on all platforms.
  • Consider showing Azure CLI examples first, or providing additional context for Linux/macOS users.
  • Explicitly mention that all tasks can be completed using Azure CLI on Linux/macOS.
GitHub Create Pull Request
Azure Functions Guide for running C# Azure Functions in an isolated worker process ...icles/azure-functions/dotnet-isolated-process-guide.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides both Windows and Linux guidance for running C# Azure Functions in an isolated worker process. However, there are several instances where Windows-specific tools, commands, or settings are mentioned before their Linux equivalents, and Windows is sometimes presented first in tables or sections. Azure PowerShell and Visual Studio (Windows-only) are listed as deployment options alongside cross-platform tools, and some CLI examples default to Windows syntax or context. Linux-specific guidance is present but often secondary.
Recommendations
  • Ensure Linux and macOS examples are presented alongside Windows examples, not after them.
  • When listing deployment or configuration options, avoid placing Windows tools (e.g., PowerShell, Visual Studio) first unless they are more widely used; consider alphabetical or platform-neutral ordering.
  • Where CLI commands are shown, include both Windows and Linux syntax (e.g., az CLI, bash vs PowerShell) in tabs or side-by-side.
  • Highlight cross-platform tools (Azure CLI, Functions Core Tools, VS Code) as primary options, with Windows-only tools as alternatives.
  • Explicitly state when a tool or method is Windows-only to avoid confusion for Linux/macOS users.
GitHub Create Pull Request
Azure Cache For Redis Azure Cache for Redis with Azure Private Link ...n/articles/azure-cache-for-redis/cache-private-link.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for managing private endpoints, but the PowerShell section appears first and is more detailed, which may create a perception of Windows bias. The portal instructions are platform-neutral, but scripting examples prioritize PowerShell before CLI, and there are no explicit Linux/macOS-specific notes or troubleshooting tips.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Add explicit notes clarifying that Azure CLI works on Linux, macOS, and Windows, while PowerShell is primarily Windows-focused (though PowerShell Core is cross-platform).
  • Include troubleshooting or environment setup tips for Linux/macOS users, such as installing Azure CLI or PowerShell Core.
  • Ensure parity in detail between PowerShell and CLI sections, so Linux/macOS users are not left with less guidance.
  • Consider adding Bash shell script examples for common tasks, or linking to Linux/macOS-specific guides.
GitHub Create Pull Request
Azure Functions Azure Functions Core Tools reference ...cles/azure-functions/functions-core-tools-reference.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation is generally cross-platform, but there are several areas where Windows-specific tools, behaviors, and issues are mentioned before Linux equivalents. Windows-specific terminology (e.g., 'func.exe'), Windows build caveats for Python, and PowerShell-specific options are highlighted. Some options and warnings are Windows-centric, and Windows is referenced first in several places, creating minor friction for Linux/macOS users.
Recommendations
  • Where Windows-specific issues are mentioned (e.g., Python packaging), provide equivalent Linux/macOS guidance and troubleshooting steps.
  • Avoid referencing Windows tools (e.g., 'func.exe') in the description/title unless the tool is actually Windows-only; use 'func' or 'Azure Functions Core Tools' instead.
  • When describing options or caveats (such as Dockerfile generation or managed dependencies), clarify Linux/macOS behavior and provide parity where possible.
  • Ensure examples and warnings are balanced, mentioning Linux/macOS considerations alongside Windows.
  • If PowerShell-specific features are highlighted, note their availability or alternatives for Bash/zsh users.
GitHub Create Pull Request
Azure Functions Develop and run Azure Functions locally ...in/articles/azure-functions/functions-develop-local.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides local development guidance for Azure Functions across multiple languages and platforms. However, Visual Studio (a Windows-only IDE) is consistently listed first in C# sections, and Windows-specific tools like PowerShell Invoke-RestMethod are mentioned before cross-platform alternatives. While Linux and macOS support is referenced throughout, Windows tools and patterns are often prioritized or highlighted first.
Recommendations
  • List cross-platform tools (e.g., Visual Studio Code, Azure Functions Core Tools, curl) before Windows-only tools in tables and tool recommendations.
  • Explicitly mention Linux/macOS compatibility in all relevant sections, not just in Visual Studio Code or command-line entries.
  • Provide Linux/macOS-specific examples or screenshots where appropriate, especially for command-line usage.
  • Add parity in HTTP test tool recommendations by listing curl and Bruno before PowerShell and Visual Studio.
  • Consider a dedicated section or callout for Linux/macOS users to clarify any differences or special considerations.
GitHub Create Pull Request
Azure Functions App settings reference for Azure Functions ...ain/articles/azure-functions/functions-app-settings.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation is generally cross-platform and provides parity for Windows and Linux. However, there are minor instances of Windows bias: Windows-specific syntax (e.g., %HOME% in AzureWebJobs_TypeScriptPath) is used in some examples, and Windows-only settings (e.g., WEBSITE_NODE_DEFAULT_VERSION) are described before their Linux equivalents. Azure CLI and PowerShell are mentioned as preferred tools for managing settings, but Linux-native tools (such as Bash or shell scripting) are not referenced. Overall, Linux-specific settings and considerations are included, and most examples are OS-neutral.
Recommendations
  • Where Windows-specific syntax is used (e.g., %HOME%), provide the Linux equivalent (e.g., $HOME) in examples.
  • When referencing tools for managing settings, mention Bash or shell scripting alongside Azure CLI and PowerShell.
  • For settings that differ between Windows and Linux (such as WEBSITE_TIME_ZONE), ensure both examples are shown side-by-side.
  • In sections where Windows-only settings are described, clarify their scope and provide links or references to Linux equivalents where applicable.
GitHub Create Pull Request
Azure Functions Deployment technologies in Azure Functions ...s/azure-functions/functions-deployment-technologies.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation generally presents deployment methods and examples in a cross-platform manner, but there is a subtle bias towards Windows: in several places, Windows-specific tools (Visual Studio, Visual Studio Code) and deployment flows are mentioned first, and Windows is sometimes the default context for explanations. However, Linux deployment options and differences are well-covered, and Linux-specific instructions are present where needed. There are no critical omissions of Linux guidance, but the ordering and emphasis may create minor friction for Linux/macOS users.
Recommendations
  • Where deployment tools are listed (e.g., Visual Studio, VS Code, Core Tools, Azure CLI), alternate the order or explicitly mention cross-platform compatibility.
  • In sections where Windows and Linux instructions are separated, ensure both are equally detailed and visible, and avoid presenting Windows as the default unless it truly is.
  • Add explicit Linux/macOS command-line examples where only generic or Windows-centric instructions are given.
  • Where possible, clarify when a tool or method is cross-platform (e.g., Azure Functions Core Tools, Azure CLI) to reassure non-Windows users.
  • Consider including a summary table or section highlighting Linux/macOS parity and any known limitations.
GitHub Create Pull Request
Azure Functions host.json reference for Azure Functions 2.x ...b/main/articles/azure-functions/functions-host-json.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation is generally cross-platform, but there are some minor Windows biases. The 'managedDependency' feature is described as PowerShell-only, which is a Windows-centric language (though PowerShell Core is cross-platform, most Azure Functions PowerShell usage is Windows-oriented). There are references to Windows tools and environment variables (e.g., %TEMP% in snapshotConfiguration), and some examples use Windows-style paths or conventions. However, Linux-specific settings (like DisableColors for console logging) are also mentioned, and most examples are generic JSON. No critical sections are Windows-only, but Windows conventions are sometimes referenced first or exclusively.
Recommendations
  • Clarify PowerShell managedDependency support for Linux/macOS (if applicable), or explicitly state Windows-only if so.
  • When referencing environment variables (e.g., tempFolder), provide both Windows and Linux/macOS equivalents.
  • Where paths or folders are mentioned, show both Windows and Linux/macOS formats.
  • Ensure examples and explanations are equally relevant for Linux/macOS users, and add Linux/macOS-specific notes where appropriate.
GitHub Create Pull Request
Azure Functions Migrate Consumption plan apps to Flex Consumption in Azure Functions ...unctions/migration/migrate-plan-consumption-to-flex.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides both Linux and Windows instructions, but Windows/PowerShell/Azure CLI examples and patterns are often presented first or in more detail. Some sections, especially those under 'platform-windows', are more verbose and step-by-step, while Linux sections rely more on CLI automation. There is a slight bias toward Windows-centric tools and workflows, with Windows instructions sometimes appearing before Linux equivalents, and more detailed manual migration steps for Windows users.
Recommendations
  • Ensure Linux and Windows instructions are presented with equal detail and clarity, especially for manual migration steps.
  • Where possible, present Linux and Windows instructions in parallel or with equal prominence, rather than defaulting to Windows-first.
  • Expand Linux sections to include more manual/step-by-step guidance for users who may not want to use the CLI automation.
  • Review the order of tabs and pivots to avoid always listing Windows/PowerShell first.
  • Where Windows-specific tools or patterns are mentioned, ensure Linux equivalents are referenced with equal detail.
GitHub Create Pull Request
Azure Functions Migrate AWS Lambda workloads to Azure Functions ...ons/migration/migrate-aws-lambda-to-azure-functions.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation page provides a comprehensive migration guide from AWS Lambda to Azure Functions, with clear parity between AWS and Azure features. However, there is mild evidence of Windows bias: PowerShell is listed as a supported language for Azure Functions (even though Lambda does not support it), and Windows tooling (Visual Studio, VS Code, Azure Functions Core Tools) is mentioned first and most prominently for local development and deployment. Linux equivalents (such as Azure CLI, Terraform, and Maven) are mentioned, but Windows-centric tools and patterns appear first and more frequently. There are no critical sections that are Windows-only, and Linux/macOS users can complete all tasks, but the ordering and emphasis may create minor friction.
Recommendations
  • When listing local development tools, mention cross-platform options (Azure CLI, Core Tools, Terraform, Maven) before or alongside Windows-centric tools (Visual Studio, VS Code).
  • Explicitly note that Azure Functions Core Tools, Azure CLI, and VS Code are cross-platform and provide links to Linux/macOS installation guides.
  • Add example commands for Linux/macOS (e.g., bash, zsh) where CLI usage is shown, especially for deployment.
  • Clarify that PowerShell support is an Azure-specific feature and not relevant for Lambda migration.
  • Ensure that sample code and instructions do not assume Windows file paths or shell environments.
GitHub Create Pull Request
Azure Functions Storage considerations for Azure Functions ...ain/articles/azure-functions/storage-considerations.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation generally maintains good cross-platform coverage, but there are minor signs of Windows bias. In sections discussing Azure Files and scaling, Windows hosting plans are mentioned before Linux equivalents. In the 'Mount file shares' section, both Azure CLI (Linux-friendly) and PowerShell (Windows-centric) examples are provided, but PowerShell is presented after CLI. The document references features and settings that are Windows-only (such as Consumption plan on Windows), but these are appropriately scoped. There are no critical omissions for Linux/macOS users, and Linux-specific instructions (e.g., mounting shares) are included.
Recommendations
  • Ensure that Linux examples are presented with equal prominence and detail as Windows/PowerShell examples.
  • When listing hosting plans or features, alternate the order or clarify parity between Windows and Linux where applicable.
  • Continue to provide both Azure CLI and PowerShell instructions for all relevant tasks, and consider adding Bash or other Linux-native scripting examples where appropriate.
  • Explicitly note when a feature or setting is Windows-only to avoid confusion for Linux users.
GitHub Create Pull Request
Azure Functions How to target Azure Functions runtime versions ...b/main/articles/azure-functions/set-runtime-version.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides parity for both Windows and Linux users, with clear platform pivots and dedicated instructions. However, in several sections, Windows/PowerShell examples and explanations are presented before Linux equivalents, and Azure PowerShell is offered as a primary scripting method alongside Azure CLI. Linux-specific instructions are sometimes less prominent or appear after Windows guidance.
Recommendations
  • Ensure Linux instructions are presented with equal prominence and ordering as Windows instructions, especially in tabbed or pivoted sections.
  • Where possible, provide Linux examples before or alongside Windows/PowerShell examples, rather than after.
  • Highlight Linux-specific limitations or differences (e.g., inability to pin runtime in Consumption plan) in a dedicated section for clarity.
  • Consider adding Bash or shell script examples for Linux users where PowerShell scripts are provided for Windows.
  • Explicitly state when a method (e.g., Azure PowerShell) is not available for Linux, and suggest alternatives.
GitHub Create Pull Request