← Back to Dashboard
229
Pages Scanned
52
Pages Flagged
229
Changed Pages
22.7%
% Pages Flagged

Scan Information

Started At: 2026-01-24 00:00:09

Finished At: 2026-02-10 18:00:39

Status: completed

Target Repo: Azure

Current Phase: discovery

Files Queued: 229

Files Completed: 229

Problematic Pages

52 issues found
Application Gateway Tutorial: Improve web application access - Azure Application Gateway .../articles/application-gateway/tutorial-autoscale-ps.md
High 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 tutorial is heavily focused on Azure PowerShell and Windows-specific tools, such as New-SelfSignedCertificate and Export-PfxCertificate, with all examples and instructions using PowerShell syntax. There are no Bash, Azure CLI, or Linux/macOS alternatives provided, and the certificate creation steps rely on Windows-only cmdlets. This creates notable friction for Linux/macOS users who cannot easily follow the steps as written.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all resource creation and management steps.
  • Include instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and exporting to PFX format.
  • Add notes clarifying cross-platform options and limitations, and link to relevant cross-platform documentation.
  • Consider reordering or parallelizing examples so Linux/macOS methods are presented alongside Windows/PowerShell methods.
GitHub Create Pull Request
Load Balancer Tutorial: Protect your public load balancer with Azure DDoS Protection ...s/load-balancer/tutorial-protect-load-balancer-ddos.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The tutorial exclusively demonstrates backend VM setup using Windows Server images and Windows PowerShell commands to install IIS. There are no Linux VM options, nor are there Bash/SSH instructions or Apache/Nginx examples. The documentation assumes Windows as the default, which creates friction for users wishing to use Linux VMs or web servers.
Recommendations
  • Add parallel instructions for creating Linux VMs (e.g., Ubuntu) in the backend pool.
  • Provide Linux-specific steps for installing a web server (e.g., Apache or Nginx) using Bash/SSH commands.
  • Include both Windows and Linux examples for configuring the backend web server, showing how to display the VM name in the default page.
  • Clarify in the prerequisites or VM creation section that either Windows or Linux VMs can be used, and link to relevant documentation for both.
  • Present Windows and Linux options side-by-side or in separate sections, rather than only Windows.
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 provides comprehensive coverage of environment variables and app settings for Azure App Service, but there is a notable Windows bias in several areas. Windows-specific paths (e.g., D:\home), tools (e.g., Web Deploy/MSDeploy), and configuration files (e.g., applicationHost.config, Web.config) are frequently referenced, often before or instead of Linux equivalents. Some sections, such as build automation and Java/.NET settings, provide more detail for Windows (Kudu, MSDeploy, Jetty/Tomcat on Windows) than for Linux (Oryx, Tomcat on Linux). Linux-specific instructions and examples are present but less detailed and sometimes appear after Windows content. There are also several environment variables and features that are only described for Windows, with Linux coverage being less explicit or omitted.
Recommendations
  • For every Windows-specific path or example (e.g., D:\home), provide the Linux equivalent (/home) alongside or first.
  • When referencing Windows tools like Web Deploy or MSDeploy, explicitly mention Linux deployment alternatives and provide links or examples.
  • Ensure that Linux-specific features (e.g., Oryx build automation, Tomcat on Linux) are described with equal detail and clarity as their Windows counterparts.
  • Where variables or behaviors differ between Windows and Linux, clearly indicate the differences in tables or callouts.
  • Add more Linux/macOS command-line examples and troubleshooting steps where only Windows/PowerShell examples are given.
  • Review sections that reference configuration files (e.g., Web.config, applicationHost.config) to clarify their applicability and provide Linux/container equivalents if available.
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 provides a 'Next steps' link that exclusively references Azure PowerShell for creating an autoscaling, zone redundant application gateway, without mentioning or linking to equivalent Azure CLI or ARM template instructions. This prioritizes Windows/PowerShell tooling and may create friction for Linux/macOS users who typically use Azure CLI or other cross-platform tools.
Recommendations
  • Add links or examples for creating autoscaling, zone redundant Application Gateway v2 using Azure CLI and ARM templates.
  • Present cross-platform instructions (Azure CLI, ARM/Bicep) alongside PowerShell examples in the 'Next steps' section.
  • Explicitly state that Azure PowerShell is not required and that equivalent functionality is available via CLI and templates.
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 ⚠️ missing_linux_example
Summary
The documentation page for Azure Application Gateway v2 demonstrates a moderate Windows/PowerShell bias. Key migration and registration/unregistration steps are provided only using Azure PowerShell commands, with no equivalent Azure CLI (bash) or REST API examples. The migration script is referenced as a PowerShell Gallery resource, and the main tutorial link is for PowerShell. There is no mention of Linux/macOS-friendly alternatives or parity in examples, which may create friction for users on non-Windows platforms.
Recommendations
  • Provide Azure CLI (bash) equivalents for all PowerShell commands, especially for registration, unregistration, and migration steps.
  • Reference cross-platform scripts or tools (e.g., Azure CLI, REST API, ARM templates) alongside PowerShell resources.
  • Ensure tutorial links include both PowerShell and Azure CLI options, or clarify platform compatibility.
  • Explicitly state that all management operations can be performed from Linux/macOS using Azure CLI or portal, where applicable.
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 PowerShell and Windows-centric tooling, such as PSCredential, Get-AutomationPSCredential, and Windows PowerShell modules. All code examples and instructions use PowerShell, with no mention of Bash, Azure CLI, or Linux/macOS alternatives. The creation of credential assets and runbook examples are exclusively shown using PowerShell, which may create friction for Linux/macOS users who prefer or require non-PowerShell environments.
Recommendations
  • Add equivalent examples using Azure CLI and Bash for credential management and runbook authentication.
  • Clarify which steps are PowerShell-specific and provide guidance for Linux/macOS users where possible.
  • Mention cross-platform alternatives to PSCredential and PowerShell modules, such as using environment variables or Azure CLI for authentication.
  • Include notes on how Azure Automation can be used with Python or other cross-platform languages, if supported.
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, specifically Windows PowerShell and Az modules. All command-line examples are given in PowerShell, with no mention of Bash, CLI, or Linux-native tools. The process for creating credentials outside the portal is described only with Windows PowerShell, and PowerShell cmdlets are listed first and in detail. Python is supported and documented, but only as an alternative for runbooks, not for asset management or administrative tasks. There are no Linux/macOS shell examples or references to cross-platform CLI usage.
Recommendations
  • Add Azure CLI examples for credential management, if supported.
  • Clarify whether PowerShell Core (cross-platform) is supported and provide examples if so.
  • Explicitly state platform requirements for PowerShell cmdlets (Windows-only or cross-platform).
  • If credential management is possible via REST API or SDKs, provide links or examples.
  • Consider reordering sections so that platform-neutral or cross-platform methods are presented before Windows-specific ones.
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 for migration, with all examples, instructions, and downloadable tools provided in PowerShell format. There are no Bash, Azure CLI, or Linux/macOS shell equivalents, nor any guidance for users who do not use PowerShell. The instructions assume the use of PowerShell modules and cmdlets, which are most commonly used on Windows, and do not mention cross-platform alternatives or considerations for Linux/macOS users.
Recommendations
  • Provide equivalent Azure CLI (az) commands and scripts for all major migration steps, including configuration cloning and IP retention.
  • Include example workflows for Bash or shell environments, especially for Linux/macOS users.
  • Explicitly state whether the provided PowerShell scripts can be run in Azure Cloud Shell (which supports PowerShell and Bash) and clarify any OS-specific limitations.
  • Add notes or links to cross-platform installation instructions for Azure PowerShell modules and scripts.
  • Consider offering downloadable scripts or templates in other languages (e.g., Python, Bash) if PowerShell is not strictly required.
  • Reorder examples or add parallel examples so Linux/macOS users are not required to adapt Windows-centric instructions.
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 and examples for mutual authentication on Azure Application Gateway, with a notable emphasis on Azure PowerShell. PowerShell examples 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/macOS-specific tools or workflows. Portal support is noted as unavailable, but Linux users are expected to use Azure CLI, which is referenced but not explained in depth. There are no Linux/macOS-specific certificate management or extraction examples, nor are cross-platform considerations discussed.
Recommendations
  • Provide equally detailed Azure CLI examples alongside PowerShell, especially for critical configuration steps.
  • Include links to Linux/macOS certificate management workflows, such as using OpenSSL for certificate extraction and chain management.
  • In 'Next steps', offer parallel guides for Azure CLI and ARM/Bicep templates, not just PowerShell.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Add notes or examples for certificate file handling on Linux/macOS (e.g., file formats, permissions, OpenSSL commands).
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_tools ⚠️ missing_linux_example
Summary
The documentation page on Application Gateway V1 retirement and migration to V2 heavily references Azure PowerShell scripts for migration tasks, including configuration migration and public IP retention. There is no mention of Azure CLI, Bash, or cross-platform alternatives, nor are Linux/macOS-specific instructions or examples provided. This creates friction for users who do not use Windows or PowerShell.
Recommendations
  • Provide equivalent Azure CLI (az) commands or scripts for migration steps, especially for configuration migration and public IP retention.
  • Explicitly state whether the PowerShell scripts can be run on PowerShell Core (cross-platform) or if they are Windows-only.
  • Include Bash or shell script examples where relevant, or clarify if only PowerShell is supported.
  • Add a section addressing migration for Linux/macOS users, including any limitations or workarounds.
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 provides disaster recovery guidance for Azure Automation that applies to both Linux and Windows VMs. However, all migration scripts and runbook examples are exclusively in PowerShell or PowerShell Workflow, with no Bash, Python, or cross-platform alternatives. The documentation references only PowerShell modules and tools, and does not provide Linux-native scripting options or examples. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other scripting environments.
Recommendations
  • Provide equivalent migration scripts or runbook examples in Bash or Python, or explicitly state if PowerShell is the only supported method.
  • Clarify if PowerShell Core (pwsh) is required/supported on Linux/macOS, and provide installation guidance if so.
  • Mention or link to any available cross-platform tools or SDKs (e.g., Azure CLI, Python SDK) that can be used for asset migration.
  • Add a note about PowerShell availability on Linux/macOS and any limitations.
  • If PowerShell is required due to Azure Automation platform constraints, make this explicit for Linux users.
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 instructions and PowerShell cmdlets are mentioned first and more frequently. Several backup and retention examples rely on Windows PowerShell cmdlets, with no Linux CLI or cross-platform alternatives provided for tasks like exporting runbooks or DSC configurations. References to Windows registry settings and PowerShell modules are prominent, while Linux equivalents (such as Azure CLI or REST API) are missing.
Recommendations
  • Include Azure CLI or REST API examples for exporting runbooks and DSC configurations, alongside PowerShell cmdlets.
  • Provide Linux/macOS-specific instructions for asset backup and retrieval, not just Windows PowerShell.
  • Present platform guidance in a parallel or grouped manner, rather than listing Windows first.
  • Reference cross-platform tools (e.g., Azure CLI, Python SDK) where possible, especially for automation and backup tasks.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page demonstrates a notable Windows/PowerShell bias. Most examples, code snippets, and workflows are centered around PowerShell, PowerShell Workflow, and graphical runbooks (which are inherently PowerShell-based). The only non-Windows example is a brief mention of Python runbooks, which lacks detailed code samples and practical usage scenarios. All CLI examples for starting runbooks use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux-native workflows. The process for passing parameters, especially with JSON, is exclusively shown using PowerShell, and there are no Linux shell or cross-platform alternatives provided.
Recommendations
  • Add equivalent examples using Azure CLI (az automation runbook start) for assigning parameters, including JSON object passing.
  • Provide Bash or shell script examples for starting runbooks and passing parameters, especially for Python runbooks.
  • Expand the Python runbook section with concrete code samples and parameter passing scenarios.
  • Clarify which features are platform-agnostic and which are PowerShell-specific, to help Linux/macOS users understand applicability.
  • Include notes or links to cross-platform tooling where possible (e.g., REST API usage from curl or other Linux tools).
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_tools ⚠️ windows_first
Summary
The documentation page for managing certificates in Azure Automation is heavily PowerShell-centric, with all creation and management examples using PowerShell cmdlets and Windows-centric tooling. PowerShell examples are presented first and in greater detail than Python, and there are no Linux-native CLI or bash examples. The certificate provider requirement ('Microsoft Enhanced RSA and AES Cryptographic Provider') is Windows-specific, and workarounds for portal limitations are PowerShell-only. This creates friction for Linux/macOS users who may prefer Azure CLI, bash, or other cross-platform tools.
Recommendations
  • Add equivalent Azure CLI examples for certificate management tasks (creation, retrieval, deletion).
  • Clarify whether certificate provider requirements are Windows-only and provide guidance for Linux/macOS users on generating compatible certificates.
  • Include bash or shell script examples for uploading and managing certificates.
  • Present Python and cross-platform examples with equal prominence to PowerShell.
  • Document any limitations or differences for Linux/macOS users explicitly.
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 generally presents Azure Change Tracking and Inventory as supporting both Windows and Linux. However, there is a notable Windows bias in the 'Track registry keys' section, which exclusively discusses Windows registry monitoring without mentioning Linux equivalents (such as Linux configuration files or system settings). Windows terminology and examples (e.g., registry keys, Internet Explorer, Windows Explorer) are presented without Linux counterparts or guidance. Most examples and screenshots are generic or mention both platforms, but Windows-specific tools and concepts are described in detail, while Linux-specific monitoring is not.
Recommendations
  • Add a section describing Linux-specific configuration monitoring, such as tracking changes in key configuration files (e.g., /etc/passwd, /etc/ssh/sshd_config) or systemd service files.
  • Provide Linux examples alongside Windows ones, especially in sections that currently only discuss Windows concepts (e.g., registry keys).
  • Clarify which features are Windows-only and which are cross-platform, to help Linux users understand what is supported.
  • Include screenshots or walkthroughs for Linux systems where appropriate.
  • Explicitly mention how Linux daemons and configuration files are tracked, similar to the detailed Windows registry coverage.
GitHub Create Pull Request
Azure Functions Migrate Consumption plan apps to Flex Consumption in Azure Functions ...unctions/migration/migrate-plan-consumption-to-flex.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 both Windows and Linux migration paths, but Windows/PowerShell/Azure CLI examples and instructions are often presented first or in more detail. Some migration steps and CLI commands are more thoroughly documented for Windows users, and certain sections (such as premigration tasks and manual migration) are Windows-centric, with Linux instructions sometimes relegated to pivots or less prominent sections. The Linux migration process is described as more automated, but the overall guidance and troubleshooting are more detailed for Windows users.
Recommendations
  • Ensure Linux and Windows instructions/examples are presented with equal prominence and detail, ideally side-by-side or with clear pivots.
  • Expand Linux-specific troubleshooting and manual migration steps to match the depth provided for Windows.
  • Where CLI commands differ, provide explicit Linux and Windows variants in every relevant section.
  • Add more Linux-specific examples for infrastructure-as-code (IaC) migration, troubleshooting, and rollback.
  • Review the order of presentation so that Linux is not consistently secondary to Windows.
GitHub Create Pull Request
Azure Resource Manager Relocate an Azure Container Registry to another region ...management/relocation/relocation-container-registry.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 several examples using Azure PowerShell cmdlets (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without equivalent Bash/Azure CLI or cross-platform alternatives. In some cases, PowerShell commands are shown first or exclusively, even though Azure CLI is generally more cross-platform. There is a Bash/Azure CLI script for image import, but the initial steps and AKS integration are PowerShell-centric. No explicit Linux/macOS guidance is provided for these steps.
Recommendations
  • For every PowerShell command (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster), provide equivalent Azure CLI or Bash examples, or clearly indicate if there is no cross-platform equivalent.
  • When listing command options, present Azure CLI (Bash) examples first or side-by-side with PowerShell, since Azure CLI is cross-platform.
  • Explicitly state when a step is Windows/PowerShell-only, and provide guidance or workarounds for Linux/macOS users if possible.
  • Review all code snippets and ensure Linux/macOS users can follow the workflow without switching to Windows or PowerShell.
GitHub Create Pull Request
Azure Resource Manager Relocation guidance for Azure Firewall ...e-manager/management/relocation/relocation-firewall.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 step-by-step instructions for relocating Azure Firewall using the Azure Portal and Azure PowerShell. All CLI-based examples and automation instructions use Azure PowerShell cmdlets, with no mention of Azure CLI or Bash scripting. This creates friction for Linux/macOS users who may prefer or require cross-platform tools. There is no explicit Windows-only requirement for the relocation process; Azure PowerShell is available on Linux/macOS, but Azure CLI is more commonly used in cross-platform automation.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell steps, especially for template export, modification, and deployment.
  • Clarify that Azure PowerShell can be used on Linux/macOS, but offer Azure CLI as a first-class alternative.
  • Include Bash scripting examples for automation where appropriate.
  • Consider reordering examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
GitHub Create Pull Request
Backup About the Azure Virtual Machine restore process ...cs/blob/main/articles/backup/about-azure-vm-restore.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 on Azure VM restore process contains notable Windows bias. In the 'Restore an encrypted VM' scenario, only PowerShell is mentioned as the method to recreate the VM after restoring disks, with all linked guides focused on Windows VM disk encryption. There is no mention of Linux equivalents, nor are Linux-specific restore scenarios or tools referenced. The restore process examples and linked documentation prioritize Windows VM scenarios, leaving Linux VM users without clear guidance for encrypted VM restore.
Recommendations
  • Add explicit guidance for restoring encrypted Linux VMs, including steps and supported tools (e.g., Azure CLI, Bash scripts).
  • Include links to documentation about Linux VM disk encryption and restore processes.
  • Where PowerShell is referenced for Windows, provide Azure CLI or Bash alternatives for Linux.
  • Clarify which restore scenarios apply to both Windows and Linux, and which are Windows-only.
GitHub Create Pull Request
Backup Architecture Overview ...-docs/blob/main/articles/backup/backup-architecture.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ missing_linux_example ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation for Azure Backup architecture is notably Windows-centric in its coverage of on-premises backup scenarios. It exclusively details the use of the MARS agent (Windows-only) and System Center DPM/MABS (Windows-based tools) for on-premises backups, with no mention of Linux support or Linux backup alternatives. The documentation also presents Windows backup methods before any mention of cross-platform or Linux-compatible approaches, and does not clarify Linux limitations or provide guidance for Linux users.
Recommendations
  • Explicitly state Linux support limitations for on-premises backup scenarios at the start of relevant sections.
  • Provide guidance or references for Linux on-premises backup, such as using Azure Backup Server (if supported), Azure File Sync, or third-party solutions.
  • Include a comparison table or section summarizing backup options for both Windows and Linux machines, clearly indicating which features are Windows-only.
  • Link to documentation on Linux VM backup in Azure where relevant.
  • If Linux on-premises backup is not supported, clarify this early and direct Linux users to alternative Azure-native or partner solutions.
GitHub Create Pull Request
Backup Back Up and Restore Encrypted Azure VMs ...ob/main/articles/backup/backup-azure-vms-encryption.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation generally covers both Windows and Linux VMs for encrypted backup and restore, mentioning ADE (BitLocker for Windows, dm-crypt for Linux) and providing parity in feature descriptions. However, in the 'Provide permissions' section, the example for identifying a VM's associated Key Vault is given only in PowerShell, with no equivalent Azure CLI or Bash example. PowerShell is typically associated with Windows environments, and its exclusive use may create friction for Linux/macOS users. Additionally, PowerShell is mentioned before Azure CLI in the context of setting access policies, suggesting a slight Windows-first bias.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell for tasks such as identifying the Key Vault associated with a VM.
  • When referencing automation or scripting, ensure both PowerShell and Azure CLI/Bash options are presented equally and in parallel.
  • Explicitly state that all procedures can be performed from Linux/macOS environments using Azure CLI, and link to relevant cross-platform guides.
  • Consider reordering examples so that CLI/Bash and PowerShell are presented together or in alternating order.
GitHub Create Pull Request
Backup Support matrix for Azure VM backups ...lob/main/articles/backup/backup-support-matrix-iaas.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 comprehensive coverage of both Windows and Linux VM backup scenarios, but there are several areas of Windows bias. Windows-specific tools (MARS agent, DPM, MABS) are described in detail, with examples and restore instructions often referencing PowerShell and Windows workflows. Linux support is present but less detailed, with some features (e.g., file-level backup via MARS agent, DPM/MABS integration) unavailable for Linux, and Linux restore instructions lacking parity in example depth. Windows examples and tools are frequently mentioned first or exclusively, while Linux alternatives are not always provided or are described as unsupported.
Recommendations
  • Where PowerShell or Windows tool examples are given for restore or backup operations, provide equivalent CLI or script examples for Linux (e.g., using Azure CLI, Bash).
  • Clarify in each section whether a feature is Windows-only, and if so, suggest Linux alternatives or workarounds where possible.
  • Expand Linux backup and restore documentation to include more detailed workflows and troubleshooting steps, similar to the Windows sections.
  • Add explicit notes or links to Linux-specific backup and restore guides in the 'Next steps' and throughout the page.
  • Where features are unsupported for Linux, provide guidance or references to alternative backup strategies for Linux VMs.
GitHub Create Pull Request
Backup Restore encrypted Azure VMs ...les/backup/restore-azure-encrypted-virtual-machines.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 both Windows and Linux coverage in its scope and introductory statements. However, in the main restore workflow, it gives explicit PowerShell-based instructions for creating a VM from restored disks, without offering an equivalent CLI or portal example suitable for Linux/macOS users. The only Linux-specific guidance is relegated to a later section, and focuses on re-installing the ADE extension, not the core restore workflow. There is also a direct link to a Windows-specific disk swap operation. This creates friction for Linux users who may not use PowerShell or Windows-centric tools.
Recommendations
  • Add Azure CLI and/or Azure Portal instructions for creating a VM from restored disks, alongside or before the PowerShell example.
  • Provide explicit Linux/macOS-compatible command examples for all major steps, especially VM creation from restored disks.
  • Ensure that links to further reading (e.g., OS disk swap) include both Windows and Linux variants where available.
  • Consider reordering sections so Linux-specific steps are not separated or treated as an afterthought.
GitHub Create Pull Request
Backup Restore VMs by using the Azure portal using Azure Backup ...b/main/articles/backup/backup-azure-arm-restore-vms.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 exhibits a moderate Windows bias. While the main restore workflow is platform-agnostic (since Azure VMs can be Windows or Linux), many example links, references, and instructions prioritize or exclusively mention Windows tools, PowerShell, or Windows-specific guidance. Linux equivalents are rarely mentioned, and Linux-specific restore scenarios are not illustrated. Some post-restore steps and advanced scenarios reference Windows-centric tools and workflows, with only brief or indirect Linux guidance.
Recommendations
  • Where PowerShell is referenced for VM creation or disk attachment, add Azure CLI and/or ARM template examples, especially for Linux users.
  • When linking to guides for attaching disks, creating VMs, or configuring network settings, include both Windows and Linux documentation (e.g., /azure/virtual-machines/linux/attach-disk-portal alongside the Windows link).
  • In post-restore steps, provide explicit Linux guidance for common tasks such as resetting SSH keys, reconfiguring network settings, or handling cloud-init password issues.
  • For advanced restore scenarios (e.g., restoring domain controllers, special network configurations), clarify when guidance is Windows-specific and provide Linux alternatives where applicable.
  • Review all code snippets and command-line instructions to ensure parity between Windows (PowerShell/CMD) and Linux (Bash/CLI) environments.
GitHub Create Pull Request
Cloud Services Extended Support About Azure Cloud Services (extended support) ...n/articles/cloud-services-extended-support/overview.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 page for Azure Cloud Services (extended support) presents deployment options with a notable Windows/PowerShell bias. PowerShell and Visual Studio (Windows-centric tools) are listed before Linux-friendly alternatives, and there are no explicit CLI or Linux/macOS-specific examples or guidance. This may create friction for Linux/macOS users seeking parity in deployment and management workflows.
Recommendations
  • Add explicit Azure CLI examples for deployment and management tasks alongside PowerShell examples.
  • Include references to cross-platform editors (e.g., VS Code) in addition to Visual Studio.
  • Clarify which deployment methods are cross-platform and provide links or guidance for Linux/macOS users.
  • Where PowerShell is mentioned, note that Azure CLI is available and provide equivalent instructions.
  • Consider reordering deployment options so that platform-neutral or Linux-friendly methods (ARM templates, CLI, Portal) are listed before Windows-specific tools.
GitHub Create Pull Request
DNS Resolve Azure and on-premises domains. .../blob/main/articles/dns/private-resolver-hybrid-dns.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides detailed steps and screenshots for configuring on-premises DNS conditional forwarders using a Windows DNS server, but does not mention or provide equivalent instructions for Linux-based DNS servers (e.g., BIND, dnsmasq, Unbound). All on-premises DNS configuration examples are Windows-centric, which may create friction for Linux users.
Recommendations
  • Add a section or examples for configuring conditional forwarders on common Linux DNS servers such as BIND (named.conf options), dnsmasq, or Unbound.
  • Explicitly state that the procedure is similar for non-Windows DNS servers and provide links or references to relevant Linux DNS documentation.
  • Where screenshots or step-by-step instructions are given for Windows DNS, provide equivalent command-line or configuration file examples for Linux DNS servers.
  • Clarify in the 'Configure on-premises DNS conditional forwarders' section that both Windows and Linux DNS servers are supported, and highlight any differences.
GitHub Create Pull Request
Event Hubs Geo-disaster recovery - Azure Event Hubs| Microsoft Docs ...ocs/blob/main/articles/event-hubs/event-hubs-geo-dr.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 platform-specific instructions for manual failover using Azure portal, Azure CLI, PowerShell, and C#. While Azure CLI is cross-platform, PowerShell is Windows-centric and is listed before C#. There are no explicit Linux/macOS shell examples (e.g., Bash scripts), and the order of examples tends to favor Windows tools first. No Linux-specific guidance or parity is provided for scripting or automation beyond CLI.
Recommendations
  • Add explicit Bash/shell scripting examples for Linux/macOS users, especially for automation scenarios.
  • Clarify that Azure CLI commands work on Linux/macOS and provide example usage in those environments.
  • Reorder sections so that cross-platform tools (Azure CLI) are listed before Windows-centric tools (PowerShell).
  • Include notes or links to Linux/macOS prerequisites for CLI usage, if relevant.
  • Provide parity in sample code for other languages/platforms (e.g., Python, JavaScript) if possible.
GitHub Create Pull Request
Event Grid Troubleshoot network connectivity issues - Azure Event Grid | Microsoft Docs ...ticles/event-grid/troubleshoot-network-connectivity.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 shows a notable Windows bias: network connectivity test examples use Windows tools (psping.exe) and PowerShell syntax first, with only a minimal Linux example (telnet) provided. In the transient issues section, only Windows tools are mentioned for packet testing, and Linux alternatives (like nc, nmap, or tcpping for Linux) are not discussed. This may cause friction for Linux/macOS users who need equivalent troubleshooting steps.
Recommendations
  • Provide Linux/macOS equivalents for all network testing commands (e.g., use nc, nmap, or tcpping for Linux/macOS).
  • Present examples for both Windows and Linux/macOS side by side, or clearly label them.
  • List cross-platform tools (such as curl, nc, or nmap) where possible, and not just Windows-specific tools.
  • When referencing downloadable tools (like psping.exe), mention if there are Linux/macOS alternatives or equivalents.
GitHub Create Pull Request
Expressroute About ExpressRoute virtual network gateways ...ssroute/expressroute-about-virtual-network-gateways.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 provides configuration examples and references primarily using Azure PowerShell cmdlets, with no equivalent Azure CLI or Linux/macOS shell examples. Sections such as gateway subnet creation and REST API/PowerShell references focus on PowerShell, which is traditionally Windows-centric, and do not offer parity for Linux/macOS users who may prefer Bash or Azure CLI. This creates friction for non-Windows users attempting to follow the documentation.
Recommendations
  • Add Azure CLI examples alongside PowerShell examples for all configuration steps, especially for gateway subnet creation.
  • Explicitly mention that Azure CLI is cross-platform and provide links to CLI documentation.
  • Where REST API and PowerShell cmdlets are referenced, include Azure CLI equivalents in the resource tables.
  • Ensure screenshots and instructions do not assume use of Windows-only tools.
GitHub Create Pull Request
Load Balancer Outbound-only load balancer configuration ...e-docs/blob/main/articles/load-balancer/egress-only.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides step-by-step instructions for configuring an outbound-only load balancer in Azure, but all virtual machine creation and connectivity testing examples use Windows Server as the VM image and Microsoft Edge for browser-based connectivity checks. There are no Linux VM examples, nor instructions for Linux-based connectivity testing, which may create friction for users deploying Linux workloads.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu) in the 'Create virtual machine' section, with appropriate settings for SSH authentication.
  • Provide connectivity testing steps for Linux VMs, such as using curl or wget from the command line to verify outbound connectivity (e.g., 'curl https://whatsmyip.org').
  • Clarify that the load balancer configuration is OS-agnostic and works for both Windows and Linux VMs.
  • Where browser-based testing is mentioned, suggest alternatives for Linux users (e.g., Firefox, Chromium, or command-line tools).
GitHub Create Pull Request
Load Balancer Quickstart: Create a public load balancer - Bicep ...ncer/quickstart-load-balancer-standard-public-bicep.md
Medium 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 presented as a first-class option, and the IIS web server (a Windows-only component) is used as the default application for testing. While Linux users can deploy the Bicep file using Azure CLI, the use of IIS and lack of Linux-based test examples (e.g., Apache or Nginx) introduces a subtle Windows bias.
Recommendations
  • Add Linux-based examples for the deployed VMs, such as using Apache or Nginx as the web server, or clarify that the template can be modified to use a Linux VM.
  • Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for non-Windows users.
  • If possible, provide a Linux variant of the Bicep template or instructions on how to adapt it.
  • Note that the default template configures IIS on Windows VMs, and provide guidance for users who wish to deploy Linux VMs instead.
GitHub Create Pull Request
Load Balancer Quickstart: Create a public load balancer - Azure portal ...cer/quickstart-load-balancer-standard-public-portal.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 only Windows/PowerShell instructions for configuring the backend VMs (specifically, installing IIS via PowerShell). There are no equivalent instructions for Linux VMs (such as installing Apache or Nginx), nor is there any mention of Linux tools or shell commands. This creates a notable bias toward Windows users in the 'Install IIS' section, despite the rest of the guide being platform-agnostic.
Recommendations
  • Add parallel instructions for Linux VMs (e.g., Ubuntu), such as using SSH and apt to install Apache or Nginx, and creating a custom index.html file.
  • Explicitly state that the backend VMs can be either Windows or Linux, and provide guidance for both.
  • Where PowerShell is used, provide Bash equivalents for Linux/macOS users.
  • Consider splitting the 'Install web server' section into 'Install IIS on Windows' and 'Install Apache/Nginx on Linux' subsections.
GitHub Create Pull Request
Load Balancer Tutorial: Create a public load balancer with an IP-based backend - Azure portal ...d-balancer/tutorial-load-balancer-ip-backend-portal.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 tutorial is generally cross-platform until the 'Install IIS' section, where it exclusively provides instructions for installing IIS on Windows Server VMs using PowerShell. The VM creation steps default to Windows Server images, and there are no examples or guidance for deploying Linux VMs or using Linux-based web servers (e.g., Apache, Nginx). This creates friction for Linux users, who must adapt the instructions themselves.
Recommendations
  • Provide parallel instructions for creating Linux VMs (e.g., Ubuntu) during the VM creation steps.
  • Include Linux-based web server installation steps (e.g., installing Apache or Nginx) and example commands (using Bash/SSH) alongside the Windows/IIS steps.
  • Show both Windows and Linux examples for backend pool configuration and testing, or clarify that the steps are similar for Linux VMs.
  • Explicitly state that the tutorial can be followed with Linux VMs and web servers, and link to relevant Linux documentation.
GitHub Create Pull Request
Load Balancer Move an Azure Load Balancer to another Azure region ...ad-balancer/move-across-regions-azure-load-balancer.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides detailed instructions for moving an Azure Load Balancer to another region using the Azure Portal and Azure PowerShell. However, it does not mention or provide examples for using the Azure CLI (az), which is the primary cross-platform command-line tool for Azure and is natively supported on Linux and macOS. All command-line automation is shown exclusively with PowerShell, which is more familiar to Windows users. There are no bash, Azure CLI, or Linux/macOS-specific instructions or notes.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell steps, especially for exporting resources, deploying templates, and managing resource groups.
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide links to relevant Azure CLI documentation.
  • Where file editing is required (e.g., editing JSON templates), provide editor-agnostic instructions or mention common Linux/macOS editors (e.g., nano, vim) in addition to notepad.exe.
  • Add a short section or note clarifying that all operations can be performed from Linux/macOS using Azure CLI, and link to the Azure CLI installation guide.
GitHub Create Pull Request
Load Balancer Quickstart: Create a public load balancer - ARM template ...r/quickstart-load-balancer-standard-public-template.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 only Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI or Bash examples. The step-by-step instructions and screenshots are PowerShell-centric, and the IIS web server (Windows-specific) is used for demonstration. While Azure PowerShell is cross-platform, the documentation assumes familiarity with Windows/PowerShell workflows and does not offer Linux/macOS-friendly alternatives or mention them until after the main walkthrough.
Recommendations
  • Add equivalent Azure CLI (az) examples for template deployment, with step-by-step instructions.
  • Explicitly mention that Azure PowerShell and Azure CLI are both cross-platform, and provide links to installation guides for Linux/macOS.
  • Include a Bash script example for Linux users.
  • Clarify that the IIS web server is a Windows workload, and optionally provide an example using a Linux-based web server (e.g., Nginx or Apache) for parity.
  • Reorder or parallelize instructions so that CLI and PowerShell options are presented together, not PowerShell-first.
GitHub Create Pull Request
Logic Apps Call Azure Functions from workflows ...cles/logic-apps/call-azure-functions-from-workflows.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 examples and guidance for creating Azure Functions using a variety of tools, including Visual Studio, Visual Studio Code, Azure CLI, Azure PowerShell, and ARM templates. However, Windows-centric tools (Visual Studio, PowerShell) are mentioned before Linux/macOS-friendly options (VS Code, CLI). In the section for finding tenant IDs, PowerShell is suggested as the command-line method, with no mention of Azure CLI or other cross-platform alternatives. The use of Kudu (Advanced Tools) for editing files is also more familiar to Windows users, though it is technically available cross-platform. No Linux/macOS-specific examples or workflows are provided, and PowerShell is referenced without CLI parity.
Recommendations
  • When listing tools for creating Azure Functions, mention cross-platform options (Azure CLI, Visual Studio Code) before Windows-only tools (Visual Studio, PowerShell).
  • Provide Azure CLI commands alongside PowerShell commands for tasks such as finding tenant IDs, object IDs, and application IDs.
  • Include explicit guidance or examples for Linux/macOS users, such as using VS Code and Azure CLI for function creation and management.
  • Clarify that Kudu (Advanced Tools) is accessible from any OS via the browser, and suggest alternative file editing methods for Linux/macOS users (e.g., using FTP, Azure CLI, or VS Code remote extensions).
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: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page provides command-line examples for disabling routing to a regional gateway using Azure CLI and references Azure PowerShell cmdlets (set-azapimanagement) alongside REST API and Azure CLI. The Azure CLI is cross-platform, but the explicit mention of Azure PowerShell (which is most commonly used on Windows) and the order in which tools are listed (PowerShell before REST API and CLI) may suggest a slight Windows bias. No Linux/macOS-specific instructions or examples are provided, but all tasks can be completed using cross-platform tools.
Recommendations
  • When listing command-line tools, mention Azure CLI first as it is cross-platform, followed by REST API, then Azure PowerShell.
  • Clarify that Azure PowerShell is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
  • Add explicit Linux/macOS shell examples where relevant, or note that Azure CLI commands work on all platforms.
  • Avoid implying PowerShell is the primary or preferred method unless required by the task.
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 covers both Windows and Linux scenarios. However, there are minor instances of Windows bias: some examples and explanations mention Windows first or use Windows-style paths (e.g., %HOME%\typescript), and Windows-specific settings (like WEBSITE_NODE_DEFAULT_VERSION) are called out, sometimes before Linux equivalents. The recommendation to use Azure CLI or Azure PowerShell for programmatic management mentions PowerShell, but does not equally highlight Bash/CLI for Linux users. There are no critical sections that are Windows-only, and Linux/macOS users can complete all tasks described.
Recommendations
  • When providing example paths, include both Windows and Linux formats (e.g., %HOME%\typescript and $HOME/typescript).
  • When referencing tools for managing settings, mention Azure CLI and Bash scripts equally with PowerShell.
  • Where settings are OS-specific, clearly label them and provide Linux/macOS equivalents or note if not applicable.
  • In lists or tables, avoid always listing Windows first; alternate or group by OS.
  • Ensure that all examples and sample values are provided for both Windows and Linux where differences exist.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation generally presents deployment methods and examples in a cross-platform manner, but there is a subtle Windows bias. Windows-based deployment technologies (such as Kudu, source control, FTPS, and local Git) are mentioned as 'Windows-only' or with Windows as the default context, and Windows hosting plans are often listed first. Visual Studio (Windows-centric) is frequently referenced before Visual Studio Code or CLI tools. Some deployment instructions and tables list Windows options before Linux, and certain features (like source control and FTPS) are available only on Windows, but this is clearly indicated. Linux deployment methods are covered, but sometimes appear after Windows equivalents.
Recommendations
  • Ensure Linux deployment examples and instructions are presented with equal prominence and clarity as Windows examples.
  • When listing deployment technologies or methods, alternate the order or explicitly state Linux and Windows support side-by-side.
  • Provide explicit Linux/macOS command-line examples (e.g., bash, zsh) where appropriate, not just Azure CLI or Visual Studio/PowerShell.
  • Clarify when a deployment method is cross-platform and provide links to Linux/macOS-specific guides where available.
  • Highlight Linux-specific deployment scenarios and troubleshooting tips in parity with Windows coverage.
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
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_terms
Summary
The documentation is generally cross-platform and does not show strong Windows bias. However, there are some minor Windows-centric elements: the managedDependency feature is described as PowerShell-only (which is most commonly used on Windows), and some references to environment variables use Windows-style syntax (e.g., %TEMP%). There are also mentions of Windows-specific folders in fallback logic for snapshot debugging. No critical configuration steps or examples are Windows-only, and Linux/macOS users can follow all instructions.
Recommendations
  • Clarify when environment variable references (e.g., %TEMP%) are platform-specific, and provide Linux/macOS equivalents (e.g., $TMPDIR or /tmp).
  • Where fallback folder logic is described, mention how it works on Linux/macOS.
  • For managedDependency, explicitly state that PowerShell functions are supported on both Windows and Linux, if true, or clarify platform limitations.
  • Ensure that any references to file paths or folders are accompanied by notes about platform differences.
GitHub Create Pull Request
Azure Resource Manager Template functions - resources ...ource-manager/templates/template-functions-resource.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for discovering list operations, but the PowerShell example is presented first. No other evidence of Windows bias is present: all code samples are in ARM template JSON, which is platform-agnostic, and there are no references to Windows-specific tools or patterns. The page does not omit Linux/macOS equivalents, and the only minor bias is the ordering of PowerShell before CLI.
Recommendations
  • Present Azure CLI and PowerShell examples side-by-side or alternate which is shown first.
  • Explicitly note that both Azure CLI and PowerShell are cross-platform, and users can choose either based on their environment.
  • Consider adding a short note for Linux/macOS users clarifying that all template examples are platform-neutral and can be used on any OS.
GitHub Create Pull Request
Backup Azure Backup glossary ...ocs/blob/main/articles/backup/azure-backup-glossary.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The glossary is generally cross-platform and workload-neutral, but there are a few instances of Windows bias. The 'VSS (Windows Volume Shadow Copy Service)' entry links only to Windows documentation, and the 'Application consistent backup' definition mentions VSS first, with Linux alternatives referenced only parenthetically. The 'Snapshot' entry links to a Windows-specific disk snapshot page before mentioning file snapshots. Several backup agent and server entries (MARS, DPM, MABS) are Windows-centric, but these reflect actual product scope rather than documentation bias.
Recommendations
  • For 'Application consistent backup', provide equal detail or links for Linux backup consistency mechanisms (e.g., pre/post scripts, fsfreeze, etc.), not just mention them parenthetically.
  • For 'VSS', clarify that it is Windows-specific and, if relevant, mention Linux alternatives or link to documentation about Linux consistency methods.
  • In the 'Snapshot' entry, link to both Windows and Linux disk snapshot documentation, or use a platform-neutral page if available.
  • Where backup agents/servers are Windows-only (MARS, DPM, MABS), clarify their platform scope to avoid confusion, but do not flag as bias since these are inherently Windows products.
GitHub Create Pull Request
Bastion Azure Bastion FAQ ...s/azure-docs/blob/main/articles/bastion/bastion-faq.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation shows minor Windows bias in a few sections. For example, browser recommendations mention Windows first and provide more detail for Windows users. The keyboard layout and configuration instructions are exclusively for Windows, with no mention of how to set keyboard layouts on Linux or macOS. There are no explicit Linux/macOS examples or instructions in these areas, which may cause friction for non-Windows users.
Recommendations
  • In the browser support section, clarify that Chrome and Edge Chromium are supported on Linux as well, if applicable.
  • In the keyboard layout section, add instructions or references for setting keyboard layouts on Linux and macOS.
  • Wherever native client or file transfer is discussed, explicitly mention support for Linux/macOS clients and provide links or examples if there are platform-specific steps.
  • Review the FAQ for other areas where Windows instructions are given and add parity for Linux/macOS where relevant.
GitHub Create Pull Request
Container Apps Code to cloud options in Azure Container Apps .../main/articles/container-apps/code-to-cloud-options.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 a cross-platform approach, but there is a subtle Windows bias in the 'Code editor' section, where Visual Studio (a Windows-first IDE) is mentioned before Visual Studio Code (cross-platform). In the Infrastructure as Code section, PowerShell is mentioned alongside Bash, but PowerShell is listed first, which may imply a Windows-first orientation. However, Linux/macOS users are not blocked from completing any tasks, and Bash is acknowledged. No examples are given that are Windows-only, and Linux equivalents are referenced.
Recommendations
  • List Visual Studio Code before Visual Studio in the 'Code editor' section, as VS Code is cross-platform and more relevant to Linux/macOS users.
  • In the CLI table, mention Bash before PowerShell to reflect the cross-platform default shell for many users.
  • Where possible, clarify that all CLI instructions work on Bash (Linux/macOS) as well as PowerShell (Windows), and provide explicit examples if there are differences.
  • Consider adding a brief note in the 'Code editor' section that Visual Studio is only available on Windows, while Visual Studio Code is available on all platforms.
GitHub Create Pull Request
Container Apps Quickstart: Deploy a Dapr application to Azure Container Apps with an Azure Resource Manager or Bicep file ...iner-apps/microservices-dapr-azure-resource-manager.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 (Azure CLI) and PowerShell examples for all deployment, log viewing, and cleanup commands. However, PowerShell examples are given equal prominence to Bash, and in some sections (such as deployment and log viewing), PowerShell examples appear immediately after Bash, which may create a subtle Windows-first impression. There are no Linux-specific tools or patterns mentioned, but the documentation does not omit Linux/macOS instructions and does not rely on Windows-only tools.
Recommendations
  • Consider making Bash (Linux/macOS) examples the default or first shown, with PowerShell as an alternative tab.
  • Explicitly note that Bash commands work on Linux/macOS and Windows (with WSL or Azure CLI installed), and PowerShell is primarily for Windows users.
  • Add a short note clarifying cross-platform compatibility of Azure CLI and Git.
  • If possible, include a brief section or callout for Linux/macOS users to confirm parity and ease of use.
GitHub Create Pull Request
Container Apps Deploy the Dapr extension for Azure Functions in Azure Container Apps ...in/articles/container-apps/dapr-functions-extension.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 PowerShell and curl examples for invoking Azure Functions and viewing logs, but consistently presents PowerShell examples before curl. This ordering subtly prioritizes Windows/PowerShell users, even though curl is available on all platforms. All other setup and deployment steps use Azure CLI, which is cross-platform, and no Windows-only tools or patterns are present.
Recommendations
  • Present curl examples before PowerShell, or show curl as the default with PowerShell as an alternative.
  • Explicitly mention that curl commands work on Linux, macOS, and Windows (with WSL or Git Bash), while PowerShell is primarily for Windows users.
  • Consider using tabbed examples with clear platform labels (e.g., 'Linux/macOS (curl)', 'Windows (PowerShell)').
  • Ensure that any future troubleshooting or advanced sections include Linux/macOS-specific guidance if needed.
GitHub Create Pull Request
Container Apps Create a zone-redundant container app ...main/articles/container-apps/how-to-zone-redundancy.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric and is presented as a full example set alongside CLI. In several sections, PowerShell examples are given equal prominence to CLI, and in some cases, PowerShell is shown after CLI but before any mention of Bash or Linux-specific tooling. There are no Linux/macOS-specific shell examples (e.g., Bash scripts), nor is there explicit mention of Linux/macOS usage patterns. However, the CLI examples are sufficient for Linux/macOS users to complete the tasks.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users, especially for environment variable assignment and command chaining.
  • Clarify that Azure CLI commands work cross-platform and highlight any OS-specific nuances if applicable.
  • Consider moving PowerShell examples to a separate section or clearly label them as Windows-specific.
  • Add notes or links for Linux/macOS users on installing and using Azure CLI.
GitHub Create Pull Request
Data Share Tutorial: Share outside your org - Azure Data Share ...-docs/blob/main/articles/data-share/share-your-data.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides examples for Azure Portal, Azure CLI, and PowerShell. While Azure CLI is cross-platform, the PowerShell examples and instructions are prominent, and some file path examples (e.g., 'D:\testFiles\textfile.csv') use Windows conventions. PowerShell is shown as a first-class option, and Windows-style file paths are used in upload examples, which may create friction for Linux/macOS users. However, Azure CLI is available and fully supported, mitigating most issues.
Recommendations
  • Add explicit notes that Azure CLI commands work on Linux/macOS and Windows.
  • When showing file upload examples, include Linux/macOS path examples (e.g., '/home/user/testFiles/textfile.csv') alongside Windows paths.
  • Clarify that PowerShell can be used on macOS/Linux via PowerShell Core, or recommend Azure CLI for those platforms.
  • Avoid using only Windows-style file paths in code samples; provide both formats or use generic placeholders.
  • Consider listing Azure CLI before PowerShell in tabbed examples to emphasize cross-platform parity.
GitHub Create Pull Request
Firewall Azure Firewall known issues and limitations ...s/blob/main/articles/firewall/firewall-known-issues.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_tools
Summary
The documentation for Azure Firewall known issues and limitations is largely platform-neutral, focusing on Azure service behaviors and limitations. However, there is a minor instance of Windows bias: in the mitigation for Passive FTP issues, the documentation links to an IIS-specific (Windows-only) configuration example, without mentioning Linux FTP server equivalents. No PowerShell-heavy, Windows-first, or missing Linux example biases are present, and the page does not assume Windows usage elsewhere.
Recommendations
  • When referencing FTP server configuration for Passive FTP, provide equivalent guidance or links for popular Linux FTP servers (e.g., vsftpd, ProFTPD, Pure-FTPd) alongside the IIS example.
  • Clarify that the IIS link is for Windows users, and suggest Linux alternatives for cross-platform parity.
  • Review other mitigation steps to ensure that any tool or command references are not Windows-exclusive, or that Linux/macOS equivalents are provided where relevant.
GitHub Create Pull Request
Load Balancer Tutorial: Create a single virtual machine inbound NAT rule - Azure portal ...ancer/tutorial-load-balancer-port-forwarding-portal.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides SSH connection instructions for both Mac/Linux (Bash) and Windows (PowerShell) users, but the example SSH command uses Windows path syntax ('.\Downloads\lb-key-pair.pem') and is shown before any Linux/macOS equivalent. There is no explicit Linux/macOS example for the SSH command with typical Unix-style paths, which may cause minor confusion for non-Windows users. However, the rest of the tutorial is platform-agnostic and uses Linux VMs and tools (NGINX, apt-get), making it accessible to all users.
Recommendations
  • Provide both Windows and Linux/macOS SSH command examples, with appropriate path syntax (e.g., './Downloads/lb-key-pair.pem' for Linux/macOS).
  • Explicitly mention that the SSH command path should be adapted to the user's OS.
  • Consider listing Linux/macOS instructions first or side-by-side with Windows instructions to avoid implicit Windows prioritization.
GitHub Create Pull Request
Logic Apps Why move from BizTalk Server to Azure Logic Apps? ...ticles/logic-apps/biztalk-server-migration-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides a comprehensive comparison between BizTalk Server (a Windows-only product) and Azure Logic Apps. While the Azure Logic Apps sections are generally cross-platform, there are several areas where Windows-specific tools, patterns, and terminology are mentioned first or exclusively, such as references to PowerShell, MMC snap-ins, Visual Studio (Windows-only), and the Windows registry. Some developer and admin tooling examples (e.g., BizTalk Administration Console, BizTalk Health Monitor, Visual Studio) are Windows-centric, and PowerShell is mentioned as an automation tool without equal emphasis on Bash or CLI alternatives. However, this bias is somewhat expected given BizTalk Server's Windows-only nature.
Recommendations
  • When discussing Azure Logic Apps developer and admin experiences, ensure parity by providing examples for both Windows and Linux/macOS users (e.g., Azure CLI, Bash scripts, Visual Studio Code).
  • Where PowerShell is mentioned for automation or deployment, also reference Azure CLI or Bash equivalents.
  • In tables or lists of tools, clarify which are cross-platform (e.g., Visual Studio Code, Azure CLI) and which are Windows-only (e.g., Visual Studio, MMC snap-ins).
  • For sections about deployment, monitoring, or automation in Azure, include Linux/macOS-friendly approaches and tools.
  • Where the Windows registry is mentioned as a configuration store, note that this is not applicable in cross-platform or cloud-native environments.
GitHub Create Pull Request
Load Balancer Tutorial: Create Inbound NAT rule V2 - Azure portal ...ad-balancer/tutorial-nat-rule-multi-instance-portal.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Linux and Windows instructions for opening a terminal (Bash for Mac/Linux, PowerShell for Windows) and uses cross-platform SSH and NGINX commands. However, in the SSH command examples, the path to the private key is given in Windows (backslash) format (e.g., '.\Downloads\myKey.pem'), and PowerShell is mentioned before Bash. This is a minor 'windows_first' bias, but Linux users can easily adapt the instructions.
Recommendations
  • Show both Windows and Linux/Mac SSH command examples, with appropriate path separators (e.g., '.\Downloads\myKey.pem' for Windows, '~/Downloads/myKey.pem' for Linux/Mac).
  • List Bash (Linux/Mac) before PowerShell (Windows) in the instructions, or present them together.
  • Explicitly state that the SSH command is the same on all platforms, but the path format may differ.
  • Consider using a generic path (e.g., '<path-to-key>/myKey.pem') in the SSH command example.
GitHub Create Pull Request