← Back to Dashboard
239
Pages Scanned
50
Pages Flagged
239
Changed Pages
20.9%
% Pages Flagged

Scan Information

Started At: 2026-02-10 00:00:07

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

Status: completed

Target Repo: Azure

Current Phase: discovery

Files Queued: 239

Files Completed: 239

Problematic Pages

50 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 page is heavily focused on Windows, especially in the SignTool integration section. All examples, prerequisites, and installation instructions are Windows-specific, using tools like SignTool.exe, PowerShell, MSI installers, and Windows Package Manager (winget). There are no Linux or macOS equivalents or instructions for setting up Artifact Signing with non-Windows tools. While other integrations (GitHub Actions, Azure DevOps, SDK) are mentioned, their instructions are deferred to external links and not detailed here, and the primary walkthrough is Windows-only.
Recommendations
  • Add explicit instructions or examples for Linux/macOS users, especially for GitHub Actions, Azure DevOps, and SDK integrations.
  • Clarify which integrations are cross-platform and provide parity in documentation (e.g., show how to use Artifact Signing from Linux build agents or macOS).
  • If SignTool is Windows-only, state this clearly and provide alternative signing tools or workflows for Linux/macOS users.
  • Include sample scripts or commands for Linux/macOS environments where possible (e.g., using dotnet CLI, bash, or other cross-platform tools).
  • Document any limitations or platform requirements for each integration up front.
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 resources. No Linux/macOS CLI examples or tools (such as Azure CLI or ARM templates) are mentioned, and the only 'Next steps' tutorial is PowerShell-focused, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI examples and tutorials for autoscaling and zone-redundant Application Gateway v2.
  • Mention ARM template or Bicep options for cross-platform resource deployment.
  • Ensure 'Next steps' links include both PowerShell and CLI-based guides, or clearly indicate platform requirements.
GitHub Create Pull Request
Application Gateway Tutorial: Improve web application access - Azure Application Gateway .../articles/application-gateway/tutorial-autoscale-ps.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The tutorial exclusively uses Azure PowerShell and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of Linux/macOS alternatives or Azure CLI. All code examples and instructions assume a Windows environment, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent Azure CLI examples throughout the tutorial for cross-platform compatibility.
  • Offer instructions for creating self-signed certificates using OpenSSL (commonly available on Linux/macOS) alongside the Windows PowerShell method.
  • Clarify which steps are Windows-specific and offer Linux/macOS alternatives where possible.
  • Add a note in the prerequisites section indicating that the tutorial is PowerShell-centric and suggest Azure CLI documentation for Linux/macOS users.
GitHub Create Pull Request
Azure Functions Tutorial: Trigger Azure Functions on blob containers using an event subscription ...s/azure-functions/functions-event-grid-blob-trigger.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The tutorial is heavily oriented around Visual Studio Code and its Azure extensions, which are cross-platform but often associated with Windows workflows. All instructions and examples use Visual Studio Code commands and GUI interactions, with no mention of CLI alternatives (such as Azure CLI or PowerShell vs Bash). The documentation does not provide Linux/macOS-specific examples or workflows, but it does not explicitly require Windows-only tools. The use of Azurite and Visual Studio Code is cross-platform, but the documentation assumes Visual Studio Code as the primary development environment, which may create friction for Linux/macOS users preferring CLI or other editors.
Recommendations
  • Add alternative instructions using Azure CLI for creating storage accounts, blob containers, event subscriptions, and deploying function apps.
  • Explicitly mention that Azurite and Visual Studio Code are cross-platform and provide links to installation guides for Linux/macOS.
  • Provide Bash shell examples alongside PowerShell or dotnet CLI commands where relevant.
  • Include a section on how to perform the same tasks without Visual Studio Code, for users who prefer terminal-based workflows.
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: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides both Windows and Linux guidance for TLS configuration, but consistently lists Windows registry/PowerShell tools and examples first, and provides more detailed instructions for Windows (including multiple links to Windows registry settings and PowerShell cmdlets). Linux instructions are present but less detailed and sometimes only reference external sources. Several backup and data management examples reference only PowerShell cmdlets, with no equivalent CLI or scripting guidance for Linux/macOS users.
Recommendations
  • Provide Azure CLI or Bash examples alongside PowerShell cmdlets for tasks like exporting runbooks and DSC configurations.
  • When referencing platform-specific guidance, list Linux and Windows equally (or alternate order) and provide parity in detail.
  • For asset backup and retrieval, include Linux/macOS-compatible methods or explicitly state if only PowerShell is supported.
  • Where possible, link to cross-platform documentation (e.g., Azure CLI docs) in addition to Windows-specific registry or PowerShell pages.
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
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 provides examples for Azure portal, Azure CLI, and Azure PowerShell. Azure PowerShell is a Windows-centric tool, and its example is given equal prominence to Azure CLI. However, there are no explicit Linux/macOS-specific instructions or notes, and PowerShell is presented as a primary workflow alongside CLI, which may create friction for Linux/macOS users. The CLI example is cross-platform, but the PowerShell section assumes familiarity with Windows tooling. Additionally, the prerequisites list Azure PowerShell without clarifying its cross-platform support or alternatives for Linux users.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommend it as the primary automation tool for Linux/macOS users.
  • Add a note about Azure PowerShell's cross-platform availability, or explicitly mention that it can be installed on Linux/macOS if relevant.
  • Consider reordering sections so that Azure CLI examples appear before PowerShell, emphasizing CLI as the default for non-Windows environments.
  • Add brief instructions or links for installing Azure CLI and Azure PowerShell on Linux/macOS.
  • If PowerShell is not commonly used on Linux/macOS, consider marking it as an alternative for Windows users.
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 demonstrates a moderate Windows bias. Windows-specific certificate store access is covered in detail with C# and Java examples, while Linux guidance is limited to file-based access and only C# examples are provided. Non-Windows languages (Node.js, PHP, Python, Java) are referenced but not exemplified. Windows certificate store tools and patterns are discussed first and more thoroughly, with Linux instructions appearing later and less prominently.
Recommendations
  • Add explicit Linux examples for accessing certificates in popular languages (Node.js, Python, Java, PHP) using file paths and environment variables.
  • Present Linux and Windows guidance in parallel sections, rather than Windows-first.
  • Expand Linux guidance to include common certificate management patterns and troubleshooting.
  • Clarify that file-based access is the primary method for Linux, and provide code samples for multiple languages.
  • Mention Linux environment variables for certificate paths earlier and more prominently.
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 Azure PowerShell examples for RBAC assignment, but PowerShell is given equal prominence and referenced in automation FAQs. Windows-specific certificate tools (IIS, Certreq.exe) are mentioned for certificate export, with only a brief reference to OpenSSL for Linux/macOS users. Windows tools are mentioned before Linux equivalents, and PowerShell is featured alongside CLI, which may create friction for Linux/macOS users.
Recommendations
  • Ensure all automation and scripting examples are provided for Azure CLI first, as it is cross-platform, and PowerShell second.
  • Expand instructions for certificate export using OpenSSL, including guidance for both Linux and macOS users.
  • Add explicit guidance for exporting certificates on Linux/macOS, avoiding references to Windows-only tools unless necessary.
  • Where Windows tools are mentioned (IIS, Certreq.exe), provide equivalent Linux/macOS instructions or links.
  • In FAQs and automation sections, highlight Azure CLI as the primary method for cross-platform users.
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 ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides a PowerShell-only example for enabling diagnostic logging, with no equivalent CLI or Bash example for Linux/macOS users. The PowerShell method is presented before the Azure portal method, and there is no mention of Azure CLI or ARM template approaches. Additionally, references to log conversion tools are tied to Visual Studio and C#, which are Windows-centric, with no alternatives for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for enabling diagnostic logging, as CLI is cross-platform and widely used by Linux/macOS users.
  • Include Bash or shell script snippets where appropriate, or reference ARM template methods for automation.
  • Mention or link to log conversion tools that work on Linux/macOS, such as Python scripts or open-source alternatives.
  • Present portal-based instructions first or equally, as they are platform-agnostic.
  • Explicitly state that PowerShell examples are for Windows users and provide parity for other platforms.
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 across platforms, but exhibits a moderate Windows bias. Windows-specific paths, tools, and configuration patterns are often mentioned first or exclusively (e.g., use of D:\home, references to IIS, applicationHost.config, and .bat files). Some examples and descriptions use Windows-centric syntax or refer to Windows-only tools (e.g., msbuild, Web Deploy/MSDeploy, w3wp.exe) without always providing Linux equivalents or clarifying platform differences. Linux-specific details are sometimes present but less prominent or detailed.
Recommendations
  • For every Windows-specific path or example (e.g., D:\home), provide the Linux equivalent (/home) alongside.
  • When referencing Windows tools (e.g., msbuild, Web Deploy), explicitly state their Linux alternatives or clarify if not applicable.
  • Ensure that Linux and macOS examples are provided with equal prominence, especially in sections like deployment, logging, and build automation.
  • Where platform-specific variables or behaviors exist, clearly label them as such and provide parity in documentation depth.
  • Add more Linux/macOS-focused troubleshooting notes and usage patterns where only Windows ones are currently present.
GitHub Create Pull Request
Application Gateway Quickstart: Deploy Application Gateway for Containers ALB Controller - Helm ...application-gateway-for-containers-alb-controller-helm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides parallel Azure CLI and Azure PowerShell instructions throughout, but PowerShell is featured heavily and often shown immediately after Azure CLI. Windows-specific tools (winget) are mentioned for Helm installation, while Linux instructions are less prominent and lack detail. There are no Bash-only or Linux-native examples for Azure resource management; all resource provisioning is via Azure CLI (cross-platform) or PowerShell (Windows-centric). The Helm install section for Linux is brief, and Windows installation is described first. No macOS-specific instructions are given.
Recommendations
  • Provide Bash-native examples for Azure CLI steps, highlighting cross-platform compatibility.
  • List Linux installation instructions for Helm before Windows instructions, or group them equally.
  • Include macOS installation instructions for Helm and clarify Azure CLI usage on macOS.
  • Add explicit notes that Azure CLI commands work on Linux/macOS as well as Windows.
  • Consider including a table or section summarizing tool compatibility across OSes.
  • Where PowerShell is used, clarify that Azure CLI is recommended for Linux/macOS users.
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 page demonstrates a notable Windows bias. It exclusively uses a Windows-based SQL Server VM as the backend example, references Windows Server images, and instructs users to connect using SQL Server Management Studio (SSMS), a Windows-only tool. There are no examples or guidance for deploying a Linux-based SQL Server VM, nor for connecting from Linux/macOS clients (e.g., using Azure Data Studio, sqlcmd, or other cross-platform tools). This may create friction for users who prefer or require Linux environments.
Recommendations
  • Include instructions for deploying a SQL Server VM on Linux (e.g., Ubuntu) as an alternative backend.
  • Provide connection examples using cross-platform tools such as Azure Data Studio, sqlcmd, or other CLI clients available on Linux/macOS.
  • Clarify that the backend can be any SQL Server VM (Windows or Linux), and highlight any differences in configuration steps.
  • Add screenshots or CLI commands relevant to Linux/macOS environments where appropriate.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation is heavily focused on Azure PowerShell scripts and cmdlets for migration, with all examples, instructions, and downloadable scripts provided in PowerShell syntax. There is no mention of Bash, Azure CLI, or Linux/macOS-specific workflows, nor are there alternative instructions for users who do not use PowerShell. The guidance assumes the reader is using PowerShell, which is most commonly associated with Windows environments, and does not address how to perform the migration from Linux or macOS systems.
Recommendations
  • Provide equivalent Azure CLI (az) commands and scripts for all migration steps, including configuration and traffic migration.
  • Include explicit instructions or examples for running migration tasks from Linux/macOS environments, such as using Azure Cloud Shell (Bash) or local Azure CLI.
  • Clarify whether the PowerShell scripts can be run cross-platform (e.g., via PowerShell Core on Linux/macOS) and provide installation guidance for non-Windows users.
  • Add a section comparing PowerShell and Azure CLI approaches, and recommend the most cross-platform method for users.
  • Where possible, offer downloadable Bash scripts or templates for common migration scenarios.
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 provides configuration instructions and code samples for both Azure PowerShell and Azure CLI, but PowerShell is consistently presented first, and the 'Next steps' section links only to a PowerShell-based guide. There are no explicit Linux/macOS-specific examples or guidance, and the CLI section is less detailed than the PowerShell section. This may create friction for Linux/macOS users who prefer or require CLI or ARM/Bicep approaches.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
  • Expand the Azure CLI section to match the detail and step-by-step guidance provided in the PowerShell section.
  • Include a 'Next steps' link to a CLI-based mutual authentication configuration guide, or provide parity in walkthroughs for both PowerShell and CLI.
  • Explicitly mention that all configuration steps can be performed from Linux/macOS using Azure CLI, and provide any relevant platform-specific notes if needed.
  • Consider adding ARM/Bicep template examples for users who prefer declarative infrastructure as code approaches, which are platform-agnostic.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation repeatedly references an Azure PowerShell script as the primary (and seemingly only) migration tool, without mentioning Azure CLI, Bash, or cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and the term 'PowerShell script' is used exclusively, which may cause confusion or friction for users on non-Windows platforms.
Recommendations
  • Explicitly state whether the PowerShell migration script is supported on PowerShell Core (pwsh) for Linux/macOS, and provide installation guidance if so.
  • If available, provide equivalent Azure CLI commands or scripts for migration, or clarify if only PowerShell is supported.
  • Add examples or notes for Linux/macOS users, such as how to run the PowerShell script on their platforms.
  • Mention any prerequisites or platform-specific considerations for running the migration script on non-Windows systems.
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: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page for Azure Application Gateway v2 shows moderate Windows bias. Migration instructions and tutorials are PowerShell-centric, with no Linux/bash equivalents provided. Azure CLI commands are shown, but the registration/unregistration examples use PowerShell context-setting commands. The 'Next steps' section links to a PowerShell tutorial as the primary onboarding path. There are no explicit Linux/macOS examples or references to bash or cross-platform scripting.
Recommendations
  • Provide equivalent bash/Azure CLI examples for migration and onboarding tasks, especially for Linux/macOS users.
  • Add links to tutorials using Azure CLI or ARM templates for Application Gateway v2 creation and migration.
  • Clarify which commands are cross-platform and which are Windows-specific, and offer alternatives where possible.
  • In 'Next steps', include links to Linux/macOS-friendly guides or CLI-based tutorials alongside PowerShell options.
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 provides only PowerShell-based scripts and workflows for asset migration, with no equivalent examples or guidance for Linux-native tools or Bash scripting. All migration instructions rely on PowerShell, which is traditionally a Windows-centric tool, although PowerShell Core is cross-platform. There are no Bash, CLI, or Python examples, and the documentation repeatedly references Windows patterns and tools first or exclusively.
Recommendations
  • Add Bash or Azure CLI examples for asset migration, or clarify if PowerShell Core is required and supported on Linux/macOS.
  • Explicitly mention cross-platform support for PowerShell scripts and provide installation guidance for Linux/macOS users.
  • Include alternative migration approaches using Python or REST API for users who do not wish to use PowerShell.
  • Balance the documentation by showing Linux/macOS workflows alongside Windows/PowerShell ones, especially in critical migration sections.
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 usage for Azure Automation authentication with Microsoft Entra ID. All code examples, module references, and credential management instructions are PowerShell-centric, with no mention of Bash, CLI, or Linux/macOS alternatives. Windows-specific tools and patterns (e.g., PSCredential, Get-AutomationPSCredential, New-AzAutomationCredential) are referenced exclusively, and Linux users are not provided with equivalent guidance.
Recommendations
  • Add Azure CLI examples for credential asset creation and authentication, highlighting cross-platform compatibility.
  • Clarify which steps are PowerShell-specific and provide Bash or Azure CLI alternatives where possible.
  • Mention that Azure Automation runbooks can be authored in Python and provide a Python example for credential retrieval and Azure authentication.
  • Explicitly state PowerShell requirements and link to cross-platform PowerShell installation instructions.
  • If certain features are Windows-only, clearly indicate this to set expectations for Linux/macOS users.
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 emphasizes PowerShell cmdlets and examples for managing certificates in Azure Automation, with PowerShell presented first and in greater detail than Python. There are no examples or guidance for Linux/macOS users who may prefer Bash, CLI, or other non-PowerShell tools. The PowerShell-centric approach may create friction for non-Windows users, especially since Azure Automation supports Python runbooks but does not provide parity in certificate management examples or CLI alternatives.
Recommendations
  • Add Azure CLI examples for certificate management tasks alongside PowerShell examples.
  • Include guidance or examples for uploading certificates using Bash or other Linux-native tools.
  • Clarify whether PowerShell cmdlets can be used cross-platform (e.g., PowerShell Core on Linux/macOS) and provide instructions if so.
  • Present Python and CLI examples before or alongside PowerShell to avoid Windows-first bias.
  • Explicitly mention any limitations or requirements for Linux/macOS users when managing certificates in Azure Automation.
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 heavily focuses on PowerShell and PowerShell Workflow runbooks, with detailed examples, screenshots, and step-by-step instructions. PowerShell cmdlets and Windows-centric patterns are used throughout, and PowerShell is presented first in nearly all sections. There are no examples or instructions for starting runbooks from Linux/macOS terminals or using cross-platform tools (e.g., Azure CLI, Bash). Python runbooks are briefly mentioned, but only in passing, with no concrete example. The SDK and REST API sections are platform-neutral, but the practical examples for parameter assignment are almost exclusively PowerShell-based.
Recommendations
  • Add Azure CLI examples for starting runbooks and passing parameters, including JSON and object parameters.
  • Include Bash shell examples for calling REST API endpoints to start runbooks and assign parameters.
  • Provide explicit instructions for Linux/macOS users, such as how to authenticate and use Azure Automation from non-Windows platforms.
  • Expand the Python runbook section with a concrete example of parameter usage and invocation.
  • Where PowerShell is used, clarify its cross-platform availability (PowerShell Core/7+) and note any Windows-only limitations.
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_first ⚠️ missing_linux_example
Summary
The documentation page heavily features Windows PowerShell cmdlets and examples, with all CLI instructions and code samples provided only for PowerShell. There is no mention of Bash, Linux shell, or cross-platform CLI equivalents for credential management. The Python section is present, but all CLI and asset creation instructions are Windows/PowerShell-centric, and the graphical runbook instructions also assume a Windows/PowerShell context.
Recommendations
  • Add Azure CLI examples for credential asset creation and management, if supported.
  • Clarify whether credential assets can be managed from Linux/macOS environments, and provide instructions if possible.
  • Include Bash or cross-platform shell examples where applicable.
  • Explicitly state if PowerShell is required for certain operations, and provide guidance for Linux/macOS users (e.g., using PowerShell Core on Linux).
  • Mention PowerShell Core as a cross-platform option, and provide installation links for Linux/macOS users.
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 demonstrates a bias toward Windows and PowerShell in its local SQL Server setup instructions. The Docker-based SQL Server setup is presented exclusively with PowerShell commands, and while a note mentions PowerShell is available on Linux/macOS, no equivalent Bash or shell script examples are provided. The troubleshooting section and validation steps also use PowerShell syntax. Linux/macOS users must adapt these steps themselves, creating friction. Additionally, the page often presents Windows-centric tools (e.g., SQL Server Express) before mentioning cross-platform alternatives.
Recommendations
  • Provide equivalent Bash shell script examples for Docker-based SQL Server setup and validation, alongside PowerShell.
  • Explicitly mention and demonstrate how to run Docker commands in Bash on Linux/macOS, including environment variable handling.
  • Include troubleshooting steps relevant to Linux/macOS users, such as file path differences or Docker nuances.
  • List cross-platform tools (e.g., Docker, SQLCMD) before Windows-specific ones (e.g., SQL Server Express) and clarify their applicability.
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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation covers Azure Change Tracking and Inventory for both Windows and Linux, but there is a notable Windows bias in certain sections. Windows registry key tracking is described in detail, with a large table of Windows-specific registry keys and explanations, while there is no equivalent section for Linux configuration tracking (such as monitoring changes to /etc, systemd units, or other Linux-specific settings). Additionally, the registry tracking section is presented before any Linux-specific configuration tracking, and no Linux examples or details are provided for comparable features.
Recommendations
  • Add a section describing Linux-specific configuration tracking, such as monitoring changes to key configuration files (e.g., /etc/passwd, /etc/ssh/sshd_config), systemd service changes, or other relevant Linux settings.
  • Provide examples or tables for Linux configuration tracking similar to the Windows registry key table.
  • Clarify parity between Windows and Linux features, noting any limitations or differences.
  • Ensure Linux examples and terminology are presented alongside Windows examples, not only after or omitted.
GitHub Create Pull Request
Azure Functions Deployment technologies in Azure Functions ...s/azure-functions/functions-deployment-technologies.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation generally presents deployment technologies in a cross-platform manner, but there is a subtle Windows bias in several areas. Windows-specific deployment options (e.g., source control, local Git, FTPS) are mentioned as 'Windows-only' without always providing Linux alternatives or clarifying Linux limitations. Examples and tool recommendations (Visual Studio, Azure CLI, Core Tools) are often presented with Windows-centric language or order. Some sections, such as remote build, describe Windows behavior first and in more detail, while Linux instructions are secondary. However, Linux deployment options (Docker, external package URL, Flex Consumption) are covered, and Linux-specific caveats are noted.
Recommendations
  • Where deployment methods are Windows-only, explicitly link to Linux alternatives or clarify Linux limitations and workarounds.
  • Present examples and tool instructions for both Windows and Linux in parallel, rather than Windows-first.
  • Add more Linux/macOS-specific examples (e.g., CLI commands, VS Code usage on Linux, Core Tools usage on Linux/macOS).
  • Clarify which features are unavailable or behave differently on Linux, and provide guidance for Linux users.
  • Ensure that tool recommendations (e.g., Visual Studio Code, Core Tools) are not presented as Windows-centric, and highlight their cross-platform nature.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides Azure Functions networking options for all hosting plans, but there are subtle signs of Windows bias. In the 'Hybrid Connections' section, Windows support is highlighted, and Linux is explicitly unsupported. In the 'Virtual network triggers' section, CLI, PowerShell, and portal instructions are given, but PowerShell is presented as a first-class option, and Linux-specific guidance is missing. Throughout, there are no explicit Linux/macOS examples or troubleshooting tips, and Windows-specific subnet sizing is mentioned before Linux. However, most features are cross-platform, and Linux support is generally referenced.
Recommendations
  • Add Linux/macOS-specific examples and troubleshooting steps where relevant, especially for automation and CLI usage.
  • Clarify parity for PowerShell and Azure CLI usage, noting any limitations for Linux users.
  • In subnet sizing tables and guidance, present Linux and Windows requirements equally, not Windows-first.
  • Where features are Windows-only (e.g., Hybrid Connections), clearly state alternatives or workarounds for Linux users.
  • Include explicit Linux/macOS testing and configuration scenarios, especially in sections about automation and troubleshooting.
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 page presents Azure PowerShell as the sole method for identifying function apps to migrate, without offering equivalent CLI or Bash examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell is mentioned before any cross-platform alternatives, which are absent.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell scripts for identifying function apps, as Azure CLI is fully cross-platform.
  • Explicitly mention that PowerShell scripts can be run on Linux/macOS if PowerShell Core is installed, but provide CLI/Bash alternatives for parity.
  • Where possible, present cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools.
  • Review other sections for implicit Windows-centric assumptions (e.g., Visual Studio references) and clarify cross-platform options (e.g., VS Code, dotnet CLI).
GitHub Create Pull Request
Azure Functions How to target Azure Functions runtime versions ...b/main/articles/azure-functions/set-runtime-version.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ minor_missing_linux_example
Summary
The documentation provides both Windows and Linux guidance, but Windows/PowerShell examples and explanations are often presented first or in greater detail. Azure PowerShell is featured as a primary method for Windows, while Linux users are limited to Azure CLI and portal methods. Some sections (like pinning runtime versions) offer more detailed Windows instructions and Visual Studio-specific notes, while Linux instructions are more concise and lack parity in tooling (e.g., no PowerShell or portal support for linuxFxVersion).
Recommendations
  • Ensure Linux instructions are given equal prominence and detail as Windows instructions, including example order and depth.
  • Where possible, provide Linux-specific examples for portal operations or clarify limitations explicitly.
  • Add notes about alternative Linux tooling (such as Bash scripts or relevant Linux-native tools) if Azure CLI is not sufficient.
  • Consider grouping Windows and Linux instructions side-by-side or using tabs to avoid implicit prioritization.
  • Clarify in the introduction that some features (like PowerShell or Visual Studio integration) are Windows-specific, and offer Linux alternatives where possible.
GitHub Create Pull Request
Application Gateway Troubleshoot Application Gateway for Containers ...cation-gateway/for-containers/troubleshooting-guide.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides troubleshooting guidance for Application Gateway for Containers and generally uses cross-platform Kubernetes tools (kubectl, helm). However, in the section on collecting logs, Windows-specific command-line patterns (findstr) are presented alongside Linux (grep), but the Windows example is shown after the Linux one. The documentation does not exclusively favor Windows, but it does provide explicit Windows command examples, which is positive for parity. There are no missing Linux/macOS examples, and all critical tasks can be completed on any platform.
Recommendations
  • Ensure that Linux/macOS and Windows examples are always presented together, preferably in tabbed format, to avoid any perception of bias.
  • Consider adding macOS-specific notes if there are any differences (though none are apparent here).
  • Maintain parity by continuing to provide both grep (Linux/macOS) and findstr (Windows) examples for log filtering.
  • If possible, clarify that all commands are cross-platform except where noted, to reassure 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 creating, retrieving, and removing private endpoints. However, PowerShell examples are presented first, which may subtly prioritize Windows users. The Azure portal instructions are platform-neutral, but the scripting sections show a mild Windows bias by listing PowerShell before CLI and not mentioning Bash or Linux-specific shell environments explicitly.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly state that Azure CLI commands can be run on Linux, macOS, and Windows, while PowerShell is primarily for Windows (though PowerShell Core is cross-platform, most Azure users on Linux/macOS use CLI).
  • Consider adding Bash shell script examples or clarifying that CLI commands are suitable for Bash/zsh environments.
  • Where possible, note any OS-specific requirements or limitations for PowerShell and CLI usage.
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 examples for both bash and PowerShell, but consistently presents bash (Linux/macOS) examples first, followed by PowerShell (Windows) syntax. There are no Windows-only tools or patterns, and all instructions are cross-platform. However, PowerShell examples are included throughout, which may be unnecessary for Linux/macOS users. Visual Studio Code is recommended, which is cross-platform, and no Windows-specific tools are mentioned.
Recommendations
  • Consider grouping bash and PowerShell examples in collapsible tabs or sections to reduce clutter and clarify platform relevance.
  • Explicitly state that all CLI commands are cross-platform and clarify when PowerShell syntax is needed.
  • Add a brief note at the start of CLI sections indicating that bash examples are for Linux/macOS and PowerShell for Windows, to help users quickly identify their relevant instructions.
  • If possible, provide a single, generic CLI example unless syntax differences are significant.
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 the PowerShell examples are labeled as 'Formatted for PowerShell' and appear immediately after the Bash examples. There is a slight bias in favor of Windows/PowerShell users, as PowerShell examples are given equal prominence and are not clearly separated as 'Windows' vs 'Linux/macOS'. No Linux-specific tools or patterns are missing, but the dual-formatting may create friction for Linux/macOS users.
Recommendations
  • Clearly label Bash examples as 'Linux/macOS' and PowerShell examples as 'Windows', so users can easily identify which applies to their platform.
  • Consider placing Bash (Linux/macOS) examples before PowerShell (Windows) examples, or use tabs to allow users to select their platform.
  • Ensure that Bash examples are fully functional and do not rely on Windows-specific syntax or features.
  • Add a brief note clarifying that Azure CLI works cross-platform and that Bash examples are suitable for Linux/macOS terminals.
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 alongside Bash for every step, and in some cases, PowerShell syntax is shown first. This creates a slight bias toward Windows users, as Linux/macOS users may find the PowerShell examples unnecessary or confusing. There are no missing Linux examples, but the presence of PowerShell throughout suggests a Windows-first approach.
Recommendations
  • Clearly label Bash and PowerShell examples, and ensure Bash is shown first for cross-platform parity.
  • Consider separating Bash and PowerShell examples into distinct tabs or sections, rather than showing both inline.
  • Add a note clarifying that Bash examples are suitable for Linux/macOS terminals, while PowerShell is for Windows users.
  • Review variable naming consistency (e.g., $apicObjID vs. $apimID) to avoid confusion.
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 examples for deploying Bicep files. However, Azure PowerShell is highlighted as a primary option alongside Azure CLI, and PowerShell examples are given equal prominence. There is minor bias in listing PowerShell as a main deployment method, which is more common on Windows, but Linux/macOS users are not excluded and can follow the Azure CLI instructions.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider listing Azure CLI examples before PowerShell, or clarifying that PowerShell is primarily for Windows users.
  • Add a brief note about using Bash or other shells for Linux/macOS users, if relevant.
  • Ensure prerequisites and environment setup sections clearly indicate cross-platform compatibility.
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 Azure PowerShell examples for deploying the ARM template, but PowerShell is given equal prominence and is mentioned in metadata and prerequisites. There is a slight bias in that PowerShell (a Windows-centric tool) is featured alongside CLI, and the metadata includes 'devx-track-azurepowershell', which may suggest a Windows focus. However, Linux users can use Azure CLI and Cloud Shell, and no critical steps are Windows-only.
Recommendations
  • Ensure Azure CLI examples are shown first, as CLI is cross-platform.
  • Explicitly mention that Azure CLI and Azure Cloud Shell are available on Linux/macOS.
  • Add a note clarifying that PowerShell Core is available cross-platform, but Azure CLI is recommended for Linux/macOS users.
  • Remove or balance metadata tags if they suggest a Windows/PowerShell focus unless required for tracking.
  • Consider adding a Bash script example for Linux users, if relevant.
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 covers Azure App Service plans for both Windows and Linux, with most content being OS-neutral. However, the 'Managed Instance on Azure App Service (preview)' section is Windows-only and is presented before any Linux-specific features or parity notes. The main links and examples reference Windows pricing and features first, but do not exclude Linux users from completing the tasks described.
Recommendations
  • Add explicit Linux parity notes or links where relevant, especially in sections discussing features or pricing tiers.
  • Ensure that examples and feature lists mention Linux support and limitations alongside Windows, rather than after or not at all.
  • Provide links to Linux-specific documentation or guidance where Managed Instance or other Windows-only features are discussed.
  • Clarify in the Managed Instance section that this feature is Windows-only and direct Linux users to alternative 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
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation primarily uses Azure Portal and Azure CLI examples, but in the section about disabling routing to a regional gateway, it references Azure PowerShell cmdlets alongside Azure CLI and REST API. The PowerShell example is mentioned after CLI, but no Linux/macOS-specific tools or shell examples are provided. However, Azure CLI is cross-platform and the portal instructions are OS-agnostic. There are no Windows-only tools or patterns, and no exclusive PowerShell or Windows tool usage, but PowerShell is referenced without explicit Linux parity.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS.
  • Add explicit Bash or shell script examples if relevant.
  • When referencing PowerShell, note that Azure PowerShell is available cross-platform, or provide equivalent CLI commands for all tasks.
  • Consider mentioning that all portal steps are OS-independent.
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 detailed PowerShell examples for backup and restore operations, with PowerShell shown first in each example section. Azure CLI and REST API examples are also included, ensuring Linux/macOS users are supported. However, PowerShell is emphasized and presented before cross-platform alternatives, which may create a perception of Windows preference.
Recommendations
  • Present Azure CLI examples before PowerShell, or alternate the order to avoid Windows-first bias.
  • Explicitly note that Azure CLI and REST API methods are fully supported on Linux/macOS and are recommended for cross-platform environments.
  • Add clarifying statements that PowerShell examples are for users who prefer or require PowerShell, while CLI and REST are suitable for all platforms.
  • Consider including Bash scripting examples for common automation scenarios, further demonstrating Linux parity.
GitHub Create Pull Request
API Management Import SOAP API to Azure API Management | Microsoft Docs ...s/blob/main/articles/api-management/import-soap-api.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 importing a SOAP API, but the PowerShell example is given equal prominence and detail. The PowerShell section is not marked as Windows-specific, and there is no mention of Linux/macOS compatibility or alternatives for PowerShell. The order of examples is CLI first, then PowerShell, which is not Windows-first, but the PowerShell example is detailed and assumes cross-platform availability without clarification. No Windows-only tools or patterns are mentioned, and the Azure CLI example is fully cross-platform.
Recommendations
  • Clarify that Azure PowerShell is available on Linux/macOS, or explicitly note any limitations.
  • Provide Bash or shell script examples for Linux users if relevant.
  • Add a note about cross-platform compatibility for both Azure CLI and PowerShell.
  • Consider mentioning that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
GitHub Create Pull Request
App Service Migrate from gateway-based to regional virtual network integration .../app-service/migrate-gateway-based-vnet-integration.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides command-line examples for Azure CLI and Azure PowerShell in all relevant sections. Azure PowerShell examples are consistently included and shown after Azure CLI, but there is no explicit Linux/macOS bias or omission. However, PowerShell is a Windows-centric tool (despite cross-platform support), and its inclusion may suggest a Windows-first mindset. The documentation does not reference Windows-specific tools or patterns, nor does it omit Linux/macOS equivalents. Azure CLI is cross-platform and is always presented first, minimizing friction for Linux/macOS users.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, not just on Windows.
  • Consider adding Bash shell script examples (where relevant) to further support Linux/macOS users.
  • Explicitly mention that all Azure CLI commands are fully supported on Linux and macOS.
  • If possible, provide links to installation guides for Azure CLI and Azure PowerShell on Linux/macOS.
GitHub Create Pull Request
Application Gateway Quickstart: Deploy Application Gateway for Containers ALB Controller - AKS Add-on ...pplication-gateway-for-containers-alb-controller-addon.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 CLI and Azure PowerShell examples for most steps, but PowerShell is featured as a first-class option throughout, including module installation and resource management. Azure CLI is cross-platform, but PowerShell is primarily used on Windows, and its inclusion as a main tab may create friction for Linux/macOS users. In several sections, PowerShell examples are shown before or alongside CLI, and there are no Linux/macOS-specific notes or parity checks. However, all critical tasks can be completed with Azure CLI, which is cross-platform.
Recommendations
  • Consider making Azure CLI the default or primary example, as it is cross-platform and more widely used by Linux/macOS users.
  • Add explicit notes clarifying that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
  • Ensure that all PowerShell instructions are matched with Azure CLI equivalents, and avoid presenting PowerShell as the first or preferred option.
  • If possible, add a 'bash' or 'Linux/macOS' tab for any steps where CLI usage may differ (e.g., environment variable syntax).
  • Review for any subtle assumptions (e.g., use of Windows-style variables or paths) and clarify for cross-platform compatibility.
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 (and Windows-style) examples, tools, and patterns are often presented first or in greater detail. Some sections, especially for manual migration steps, are more detailed for Windows users, and the use of PowerShell/Azure CLI is sometimes Windows-centric. Linux instructions are present but sometimes less emphasized or appear after Windows instructions.
Recommendations
  • Ensure Linux and macOS instructions are always presented with equal prominence as Windows, including in tabbed sections and code samples.
  • Where possible, provide Linux/macOS-specific command-line examples (e.g., bash scripts, common Linux tools) before or alongside Windows/PowerShell equivalents.
  • Review the order of examples and ensure Linux is not always second or less detailed.
  • Add explicit notes when a tool or feature is Windows-only, and provide Linux alternatives or workarounds.
  • Where Azure CLI is used, clarify that it is cross-platform and provide shell-agnostic examples.
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
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell examples are included throughout, which are primarily relevant to Windows users. Azure CLI is cross-platform and shown first in each example, but there is no explicit mention of Linux/macOS compatibility or guidance for those environments. The documentation does not reference Windows-specific tools or patterns, but the presence of PowerShell examples may create minor bias toward Windows users.
Recommendations
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS as well as Windows.
  • Add a note indicating that PowerShell examples are primarily for Windows users, while Azure CLI is recommended for Linux/macOS.
  • Consider including brief instructions or links for installing Azure CLI on Linux/macOS.
  • Ensure parity in troubleshooting or environment setup guidance for Linux/macOS users.
GitHub Create Pull Request
Azure App Configuration Monitor Azure App Configuration ...s/azure-app-configuration/monitor-app-configuration.md
Low 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 is presented as a primary option alongside CLI and Portal. Additionally, the CLI instructions mention Windows PowerShell as an example of a command console, which may imply Windows as the default environment. There are no Linux-specific examples or explicit mentions of Linux/macOS tools or environments, and PowerShell is presented without reference to PowerShell Core or its cross-platform capabilities.
Recommendations
  • Clarify that Azure CLI works on Linux, macOS, and Windows, and provide explicit instructions for Linux/macOS users (e.g., 'open a terminal' instead of 'Windows PowerShell').
  • Mention PowerShell Core as a cross-platform option, or note that the PowerShell instructions are applicable on any OS where PowerShell Core is installed.
  • Add Linux/macOS-specific guidance or screenshots where relevant, especially for opening terminals or using CLI.
  • Consider listing CLI instructions before PowerShell, as CLI is more universally available across platforms.
  • Avoid implying Windows as the default environment when referencing command consoles.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ minor_windows_cli_bias
Summary
The documentation provides a comprehensive guide for running C# Azure Functions in an isolated worker process and is generally cross-platform. However, there are minor instances of Windows bias: Windows tools and patterns (e.g., Visual Studio, Azure PowerShell) are sometimes mentioned before their Linux equivalents, and Windows-specific instructions or CLI commands are occasionally shown first. There are also references to checking/changing Windows app bitness and ReadyToRun publishing examples that default to Windows. Linux equivalents are present but often appear after Windows instructions or are less detailed.
Recommendations
  • Ensure Linux and macOS examples are presented alongside Windows examples, ideally in parallel or with equal prominence.
  • When listing tools or methods (e.g., Visual Studio, VS Code, Azure CLI, PowerShell), avoid always listing Windows tools first; alternate order or clarify cross-platform support.
  • Expand Linux-specific instructions where Windows instructions are detailed (e.g., ReadyToRun publishing, debugging, deployment).
  • Where CLI commands are shown for Windows, provide Linux/macOS equivalents immediately after, not in separate sections.
  • Clarify when instructions are cross-platform and when they are Windows-only, to reduce ambiguity.
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 provides a comprehensive reference for Azure Functions app settings, covering both Windows and Linux scenarios. However, there are minor instances of Windows bias: Windows-specific tools (Azure PowerShell) are mentioned before Linux equivalents (Azure CLI) in the section about programmatically updating settings, and some examples (such as environment variable delimiters and paths) show Windows conventions first or exclusively. Additionally, certain settings (e.g., WEBSITE_NODE_DEFAULT_VERSION) are marked as Windows-only, but this is clearly indicated. Overall, Linux parity is strong, with explicit Linux settings and considerations included throughout.
Recommendations
  • When mentioning tools for programmatically updating settings, list Azure CLI and Azure PowerShell together, or mention Azure CLI first to avoid Windows-first bias.
  • Where environment variable syntax or paths are shown, provide both Windows and Linux/macOS examples side-by-side.
  • Continue to clearly mark Windows-only settings and avoid unnecessary Windows-centric language in cross-platform sections.
  • Review sample values and explanations to ensure Linux/macOS conventions are equally represented.
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 mostly cross-platform, but there are several subtle signs of Windows bias. Windows terminology ('func.exe'), Windows-specific issues (Python packaging on Windows), and PowerShell-specific features are mentioned. Windows is referenced first in some places, and Windows tools (like the Storage Emulator) are mentioned before their Linux equivalents. The '--managed-dependencies' option is PowerShell-only, and the documentation sometimes assumes Windows as the default environment. However, Linux/macOS users can generally complete all tasks, and most commands are platform-agnostic.
Recommendations
  • Replace references to 'func.exe' with 'func' or clarify that the tool is cross-platform.
  • When mentioning platform-specific issues (e.g., Python packaging), provide equivalent Linux/macOS guidance and highlight best practices for those platforms.
  • Mention Linux/macOS storage emulator options alongside Windows Storage Emulator, or link to relevant resources.
  • Ensure examples and notes do not assume Windows as the default; explicitly state cross-platform compatibility where relevant.
  • Where PowerShell-specific features are discussed, clarify their scope and provide parity notes for other shells/runtimes.
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 guidance for developing Azure Functions locally across multiple languages and platforms. While it generally supports Linux, macOS, and Windows, there is a mild Windows bias: Visual Studio (a Windows-only IDE) is listed first for C# development, and Windows-specific tools like PowerShell and Visual Studio are mentioned before cross-platform or Linux-native alternatives. However, Linux/macOS options (VS Code, command line, Azurite, curl) are included and described, and the page explicitly notes cross-platform support in most cases.
Recommendations
  • For C# development, list Visual Studio Code and command line options before or alongside Visual Studio to avoid implying Windows is the default or preferred platform.
  • When mentioning HTTP test tools, list cross-platform tools (curl, Bruno, VS Code REST Client) before Windows-specific tools (PowerShell, Visual Studio).
  • Explicitly state that all major workflows are supported on Linux/macOS and provide links to Linux/macOS-specific setup guides where relevant.
  • Add brief notes or callouts in tables/sections clarifying which tools are Windows-only and which are cross-platform.
  • Ensure parity in example commands (e.g., show bash/zsh equivalents for any PowerShell commands if present).
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 provides troubleshooting guidance for Python function apps in Azure Functions, which run exclusively on Linux at runtime. However, several sections present Windows/PowerShell commands before their Linux equivalents, and some examples are Windows-centric or lack parity in detail for Linux/macOS users. For instance, PowerShell commands are shown first for checking Python bitness, and in some cases, Windows-specific tools (like 'py') are referenced before 'python3'. Additionally, some command examples (such as deleting directories) list Bash, PowerShell, and Cmd, but Bash is not always shown first. There are also references to generating requirements.txt from Windows/macOS, but mitigation steps are generic and do not provide Linux-specific guidance.
Recommendations
  • Present Linux/macOS examples before Windows/PowerShell equivalents, especially since Azure Functions Python runs on Linux.
  • Ensure all command examples have clear, detailed Linux/macOS instructions, not just Windows/PowerShell.
  • Where Windows-specific tools (e.g., 'py') are referenced, clarify the Linux/macOS equivalent ('python3') and provide parity in explanation.
  • Highlight Linux/macOS best practices for requirements.txt generation and deployment, given the runtime environment.
  • Review all troubleshooting steps to ensure Linux/macOS users are not left with ambiguous or less detailed guidance.
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 is generally cross-platform and covers both Windows and Linux scenarios for Azure Functions storage considerations. However, in the 'Mount file shares' section, PowerShell and Azure CLI examples are presented in parallel, but PowerShell is a Windows-centric tool. Additionally, in some sections, Windows hosting plans are mentioned before Linux, and certain features are described as 'Windows only' without always providing equivalent Linux guidance upfront. Overall, Linux is well-supported, but there is a slight tendency to mention Windows and PowerShell first.
Recommendations
  • When presenting command-line examples, consider showing Azure CLI (cross-platform) examples before PowerShell, or clearly indicate which platforms each applies to.
  • Where features are Windows-only, ensure the Linux equivalent (if any) is mentioned immediately after, or clarify if no equivalent exists.
  • In sections describing hosting plans or features, alternate the order of Windows and Linux mentions, or group guidance by platform for clarity.
  • Where possible, provide explicit Linux/macOS examples or callouts, especially for deployment and configuration scenarios.
GitHub Create Pull Request
Azure Government Azure guidance for secure isolation ...es/azure-government/azure-secure-isolation-guidance.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 generally covers Azure secure isolation in a cross-platform manner, referencing both Windows and Linux where appropriate. However, there are several instances where Windows technologies, tools, and terminology are mentioned first or exclusively, such as Hyper-V, Windows Firewall, BitLocker, and PowerShell. In some sections, Windows-specific examples or references precede Linux equivalents, and Windows tools (e.g., PowerShell) are listed as primary management interfaces, even when Linux alternatives (Azure CLI, SSH, DM-Crypt) are available. These patterns may create minor friction for Linux/macOS users, though the documentation does ultimately provide Linux parity in most critical areas.
Recommendations
  • When listing management tools (e.g., Azure portal, PowerShell, CLI), alternate the order or explicitly mention Linux/macOS compatibility for Azure CLI.
  • Where Windows technologies (e.g., BitLocker, Windows Firewall) are referenced, ensure Linux equivalents (e.g., DM-Crypt, iptables/firewalld) are mentioned with equal prominence.
  • Provide example commands for both Windows (PowerShell) and Linux (CLI/SSH) when discussing VM provisioning, disk encryption, or network configuration.
  • Clarify that Azure CLI is fully supported on Linux/macOS and provide links to installation guides for those platforms.
  • Where Windows terminology is used (e.g., Host OS as Windows Server), clarify the analogous Linux scenario or note platform-agnostic aspects.
GitHub Create Pull Request