← Back to Dashboard
211
Pages Scanned
53
Pages Flagged
211
Changed Pages
25.1%
% Pages Flagged

Scan Information

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

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

Status: completed

Target Repo: Azure

Current Phase: discovery

Files Queued: 211

Files Completed: 211

Problematic Pages

53 issues found
Load Balancer Tutorial: Protect your public load balancer with Azure DDoS Protection ...s/load-balancer/tutorial-protect-load-balancer-ddos.md
High 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 uses Windows Server VM images and Windows PowerShell commands to install and configure IIS for load balancer testing. There are no Linux VM options, nor are there Bash or Linux-native instructions for installing a web server. Windows tools and patterns (PowerShell, IIS) are presented without Linux equivalents, and Windows is the only platform shown for backend pool configuration and testing.
Recommendations
  • Add parallel instructions for deploying Linux VMs (e.g., Ubuntu) in the backend pool.
  • Provide Bash commands for installing and configuring a web server (such as Apache or Nginx) on Linux VMs.
  • Show both Windows and Linux examples for backend pool setup and load balancer testing.
  • Explicitly state that either Windows or Linux VMs can be used, and link to relevant Linux documentation.
  • Include screenshots or CLI examples for Linux VM configuration where appropriate.
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 link to a tutorial for creating an autoscaling, zone-redundant Application Gateway using Azure PowerShell, without mentioning or linking to equivalent instructions for Linux/macOS users (such as Azure CLI or ARM templates). This prioritizes Windows/PowerShell tooling and may create friction for users on other platforms.
Recommendations
  • Add links or sections for creating autoscaling, zone-redundant Application Gateway using Azure CLI and ARM templates.
  • Ensure that examples and tutorials are provided for both Windows (PowerShell) and cross-platform tools (CLI, REST API).
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, or clarify cross-platform options.
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 and recommends an Azure PowerShell script for migration from Application Gateway V1 to V2, without mentioning Azure CLI or Bash alternatives. There are no Linux/macOS-specific instructions or examples, and the only automation tool referenced is PowerShell, which is more familiar to Windows users. This may create friction for Linux/macOS users who may prefer or require cross-platform tools.
Recommendations
  • Provide equivalent Azure CLI (az) commands or scripts for migration tasks, or clarify if such tools are not available.
  • Explicitly state whether the PowerShell script can be run cross-platform (e.g., using PowerShell Core on Linux/macOS) and provide installation guidance if so.
  • Add Bash or shell script examples where appropriate, or link to cross-platform migration tooling if available.
  • Mention any limitations or requirements for non-Windows users when using the provided PowerShell scripts.
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 is heavily focused on Azure PowerShell and Windows-specific tools, such as the use of PowerShell cmdlets and the New-SelfSignedCertificate/Export-PfxCertificate commands, which are only available on Windows. There are no examples or guidance for Linux/macOS users, such as using Azure CLI or OpenSSL for certificate creation. This creates friction for non-Windows users attempting to follow the tutorial.
Recommendations
  • Provide equivalent Azure CLI commands for all steps, especially for resource creation and management.
  • For certificate creation, include OpenSSL-based instructions for Linux/macOS users alongside the PowerShell examples.
  • Clarify in the prerequisites that the tutorial is PowerShell-focused, and link to any available Azure CLI or cross-platform tutorials.
  • Where possible, use cross-platform tools and commands, or clearly indicate which steps are Windows-only and provide alternatives.
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 for disaster recovery in Azure Automation is heavily focused on PowerShell scripts and workflows for migration, with no equivalent examples or guidance for Linux users (e.g., Bash, CLI, Python SDK). All migration automation is described using PowerShell, which is more familiar to Windows users. While the documentation mentions both Windows and Linux Hybrid Runbook Workers, all automation and scripting examples are PowerShell-centric, and there are no Linux-native or cross-platform alternatives provided.
Recommendations
  • Provide equivalent migration scripts or automation examples using Azure CLI, Bash, or Python SDK to support Linux/macOS users.
  • Explicitly mention if PowerShell Core (pwsh) is supported on Linux/macOS and provide instructions for those platforms.
  • Add guidance or links for running PowerShell scripts on Linux/macOS, if PowerShell is the only supported method.
  • Include at least one end-to-end example for Linux users, such as using Bash or Azure CLI to replicate Automation account assets.
  • Clarify any platform limitations in the prerequisites or introduction.
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 for migrating Azure Application Gateway from V1 to V2 is heavily focused on PowerShell-based workflows, with all examples, scripts, and tooling provided exclusively for Azure PowerShell. There is no mention of Bash, Azure CLI, or cross-platform alternatives, nor are Linux/macOS-specific instructions or examples provided. The use of PowerShell is assumed throughout, and installation/usage instructions are tailored to Windows/PowerShell environments. This creates friction for users on Linux or macOS, who may prefer or require Azure CLI or Bash scripting.
Recommendations
  • Provide equivalent Azure CLI scripts and examples for all migration steps, including configuration cloning and IP retention.
  • Explicitly note cross-platform compatibility for PowerShell scripts (e.g., Azure Cloud Shell, PowerShell Core on Linux/macOS) and provide instructions for running scripts in those environments.
  • Add Bash/CLI examples for common operations (e.g., retrieving resource IDs, uploading certificates) alongside PowerShell examples.
  • Clarify any limitations or requirements for running provided scripts on non-Windows platforms.
  • Consider linking to or referencing Azure CLI documentation for Application Gateway management.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page for Azure Application Gateway v2 shows a moderate Windows/PowerShell bias. Migration and registration/unregistration examples use Azure PowerShell (Set-AzContext, Register-AzProviderFeature, etc.) rather than cross-platform Azure CLI or Bash equivalents. The 'Next steps' section links to a PowerShell tutorial first. There are no explicit Linux/macOS CLI or Bash examples, and PowerShell is implicitly assumed as the primary automation tool.
Recommendations
  • Provide Azure CLI and/or Bash equivalents for all PowerShell command examples, especially for registration, unregistration, and migration steps.
  • When listing tutorials or quickstarts, offer both PowerShell and Azure CLI (or Bash) options, or clearly indicate cross-platform options.
  • Clarify in the text that Azure PowerShell commands can be run on any platform, or link to cross-platform installation guides.
  • Consider reordering or balancing the prominence of PowerShell and CLI/Bash examples to avoid the impression of Windows-first bias.
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_tools ⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page provides both Windows and Linux guidance for TLS upgrades, but several critical examples and references are Windows/PowerShell-centric. Key backup and retention operations reference Windows PowerShell cmdlets without Linux or cross-platform CLI alternatives. Windows registry settings and PowerShell cmdlets are mentioned before Linux equivalents, and Linux instructions are less detailed or rely on manual scripting.
Recommendations
  • Include Azure CLI or REST API examples for backup and retention operations, especially for exporting runbooks and DSC configurations, to provide parity for Linux/macOS users.
  • Add explicit Linux/macOS instructions or scripts for tasks currently covered only by Windows PowerShell cmdlets (e.g., unregistering DSC nodes, exporting runbooks/configurations).
  • Where possible, present platform-neutral or cross-platform solutions first, or provide parallel examples for both Windows and Linux/macOS.
  • Clarify when a feature or cmdlet is Windows-only, and suggest alternatives for other platforms if available.
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_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation is heavily focused on PowerShell and Windows-centric tooling, with most examples, screenshots, and instructions using PowerShell cmdlets and patterns. There is minimal coverage of Python runbooks, and no examples or guidance for Linux/macOS users on how to interact with Azure Automation runbooks outside of PowerShell. REST API and SDK examples are platform-neutral, but all CLI examples use PowerShell, and Windows tools are referenced exclusively.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux/macOS.
  • Provide Python runbook parameter examples with more detail, including how to pass arguments from non-Windows environments.
  • Include instructions or examples for starting runbooks from Linux/macOS terminals, such as using Bash scripts or Azure CLI.
  • Clarify that PowerShell examples can be run using PowerShell Core (pwsh) on Linux/macOS, and note any differences.
  • Where screenshots show Windows-only tools, add notes or alternative visuals for Linux/macOS users.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation is heavily focused on PowerShell-based workflows and examples, with all code samples and module instructions referencing PowerShell. There is no mention of Bash, CLI, or cross-platform scripting alternatives. The term 'Windows PowerShell' is used, and no Linux/macOS-specific guidance or parity examples are provided, which may create friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI (az) examples for credential creation, authentication, and runbook management, where possible.
  • Clarify that Azure Automation runbooks can use PowerShell Core (cross-platform) and/or Python, and provide examples for these where supported.
  • Replace 'Windows PowerShell' with 'PowerShell' where the instructions are not Windows-specific, and clarify when Windows-only modules are required.
  • Explicitly state the platform requirements for each module or script, and provide guidance for Linux/macOS users on how to achieve similar outcomes.
  • Link to documentation on using Azure Automation with Python runbooks and/or Bash scripts, 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 and Windows-centric tooling. All CLI examples are provided in PowerShell, with explicit references to Windows PowerShell and PSCredential objects. There is no mention of Linux shell (bash, sh) equivalents, nor are there examples for managing credentials via Azure CLI or REST API. The Python section is present, but only for runbook usage, not for asset management. The ordering also places Windows/PowerShell methods before Python, and there is no guidance for Linux/macOS users who may wish to manage credentials outside the portal or Python runbooks.
Recommendations
  • Add examples for managing credentials using Azure CLI and/or REST API, which are cross-platform.
  • Clarify that PowerShell examples can be run using PowerShell Core on Linux/macOS, if applicable.
  • Provide guidance or links for Linux/macOS users who wish to automate credential management outside of PowerShell.
  • Reorder sections so that portal and cross-platform methods are presented before Windows/PowerShell-specific methods.
  • Explicitly state platform requirements for PowerShell cmdlets (e.g., Windows PowerShell vs PowerShell Core).
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation is heavily PowerShell-centric, with all command-line examples using PowerShell cmdlets and .NET types. There are no examples using Bash, Azure CLI, or Linux-native tools for certificate management. The only non-PowerShell examples are for Python runbooks, but these are limited to in-runbook usage, not certificate management or upload. The guidance for uploading certificates outside the portal recommends PowerShell as the workaround, with no Linux/macOS alternative. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Azure CLI.
Recommendations
  • Add Azure CLI examples for certificate management tasks (upload, retrieve, delete) where possible.
  • Explicitly mention if certain operations (e.g., uploading certificates) are only supported via PowerShell, and provide guidance for Linux/macOS users (e.g., using Azure CLI, REST API, or PowerShell Core on Linux).
  • If PowerShell is required, clarify that PowerShell Core is cross-platform and provide installation links for Linux/macOS.
  • Include Bash/Azure CLI equivalents alongside PowerShell examples, especially for common tasks like uploading or retrieving certificates.
  • Document any REST API options for certificate management for users who cannot use PowerShell.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation generally aims for cross-platform coverage, but there are subtle Windows biases. Windows-based deployment methods (such as source control, local Git, FTPS) are called out in the technology availability table before Linux equivalents, and some deployment instructions (e.g., remote build, zip deploy) mention Windows scenarios first or in more detail. There is a tendency to reference Visual Studio (Windows-only) and PowerShell/CLI tools before Linux-native workflows. Some Linux-specific deployment limitations are mentioned, but Linux examples and workflows are less detailed or presented after Windows ones.
Recommendations
  • Ensure Linux deployment examples are given equal prominence and detail as Windows examples, especially for zip deploy and remote build.
  • When listing deployment technologies, alternate or group by OS rather than listing Windows-first.
  • Provide explicit Linux/macOS command-line examples where possible, not just generic Azure CLI or Visual Studio references.
  • Clarify when a deployment method is cross-platform and provide links to Linux/macOS setup guides.
  • Highlight Linux-specific tools and workflows (e.g., Oryx, Docker, bash scripts) alongside Windows tools.
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 and command snippets using Azure PowerShell cmdlets (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without equivalent Bash/Azure CLI or Linux/macOS-native alternatives. In some cases, Azure CLI is used, but PowerShell commands are often shown first or exclusively for key steps (such as listing repositories or configuring AKS integration). There is no mention of Linux/macOS-specific considerations or examples for these tasks.
Recommendations
  • For every PowerShell example (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster), provide an equivalent Azure CLI or Bash command, and show both side-by-side or with clear tabs for each platform.
  • Ensure that Azure CLI (cross-platform) examples are shown first, or at least equally, before PowerShell-specific commands.
  • Clarify in each section which commands are cross-platform and which are Windows/PowerShell-specific.
  • Add notes or links for Linux/macOS users where PowerShell commands are shown, explaining how to install/use Azure CLI or PowerShell Core if needed.
  • Review the use of terms like 'script' and ensure that Bash scripting examples are provided alongside PowerShell scripts.
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 command-line examples use Azure PowerShell, with no mention of Azure CLI or Bash scripts, which are cross-platform and preferred by many Linux/macOS users. There are no Linux-specific instructions or parity for command-line operations, and the only automation tooling referenced is PowerShell, which is most commonly used on Windows.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell command-line steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that both Azure PowerShell and Azure CLI can be used, and link to Azure CLI documentation where relevant.
  • Where scripts or automation are referenced, provide Bash script examples or note how Linux/macOS users can perform the same actions.
  • Consider reordering examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell, or use tabs for both.
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
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for Azure Backup architecture shows a notable Windows bias in its coverage of on-premises backup scenarios and agent tooling. Windows backup methods (MARS agent, DPM/MABS) are described in detail, with explicit statements that Linux machines aren't supported for direct backup via MARS. There are no Linux-specific examples, agents, or equivalent tooling mentioned for on-premises backup, and Windows tools are introduced first and exclusively for these scenarios. Azure VM backup is described in a platform-neutral way, but on-premises backup coverage is Windows-centric.
Recommendations
  • Clearly state Linux backup limitations and provide links or references to alternative solutions for Linux on-premises backup, if available (e.g., third-party tools, Azure File Sync, or native Linux backup to Azure Blob Storage).
  • Add a comparison table or section outlining backup options for Linux on-premises machines, even if only to clarify that direct backup is not supported and suggest alternatives.
  • Where possible, include parity in examples and workflows for Linux VMs in Azure (e.g., mention that the Azure VM backup extension works for both Windows and Linux VMs).
  • Consider reordering sections so that platform-neutral Azure VM backup is described before Windows-only on-premises backup methods.
GitHub Create Pull Request
Azure Resource Manager Relocate Azure Virtual Machine Scale Sets to another region ...nt/relocation/relocation-virtual-machine-scale-sets.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 references PowerShell and Azure portal workflows, but does not provide Linux/macOS-specific CLI examples or mention cross-platform tools first. The use of PowerShell is implied as a primary method, and the Azure portal screenshots and instructions are Windows-centric. There is no explicit guidance for Linux users, such as Bash or Azure CLI commands, nor are Linux/macOS workflows shown alongside Windows ones.
Recommendations
  • Add Azure CLI (az) command examples for all steps where PowerShell or portal is referenced, especially for exporting templates, setting instance counts, and deploying resources.
  • Include screenshots or instructions for Linux/macOS environments where relevant, such as using Azure CLI in Bash.
  • Explicitly state that all steps can be performed on Linux/macOS using Azure CLI, and provide links to cross-platform tool documentation.
  • Present CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides general guidance for restoring Azure VMs using the portal and templates, but several example links and instructions reference Windows-specific pages and PowerShell, especially for creating VMs from restored disks and configuring network settings. Linux-specific instructions, examples, or links are notably absent, and Windows documentation is referenced first or exclusively in several places.
Recommendations
  • Add explicit Linux VM restore examples, including links to Linux-specific documentation for attaching disks, creating VMs from restored disks, and configuring network settings.
  • Where PowerShell is referenced for VM creation or configuration, also provide equivalent Azure CLI or portal instructions applicable to Linux VMs.
  • Ensure links to tutorials and guides for availability sets, network configuration, and VM creation include both Windows and Linux variants, or clarify when instructions are OS-agnostic.
  • In sections referencing post-restore steps (e.g., resetting passwords, VM agent installation), provide Linux-specific guidance and links, such as using cloud-init, SSH, and troubleshooting Linux VM agent issues.
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 Azure VMs with encrypted disks, referencing both ADE (BitLocker for Windows, dm-crypt for Linux) and platform/customer-managed keys. 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. Additionally, the PowerShell example appears before mentioning that Azure CLI can also be used, which may create friction for Linux/macOS users who are less likely to use PowerShell.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for tasks such as identifying a VM's associated Key Vault.
  • Where automation or scripting is referenced, provide both PowerShell and Azure CLI/Bash commands, or link to equivalent instructions.
  • When listing tools or commands, avoid presenting Windows/PowerShell options first unless there is a technical reason.
  • Explicitly state that all steps can be performed on both Windows and Linux, and clarify any OS-specific differences.
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 covers restoring both Windows and Linux encrypted Azure VMs, but there is a notable Windows bias. In the 'Recreate the virtual machine instance' section, only a PowerShell-based method is explicitly mentioned for creating a VM from restored disks, with no Linux/CLI/Bash equivalent. Additionally, the disk swap example links to a Windows-specific article. The Linux-specific restore steps are separated into a later section, and there is no example or command-line guidance for Linux users to automate VM recreation.
Recommendations
  • Add Azure CLI and/or Bash examples for recreating a VM from restored disks, especially for Linux users.
  • Provide parity in automation guidance for Linux, not just PowerShell.
  • When referencing disk swap operations, include links or instructions for both Windows and Linux VMs.
  • Reorganize sections so that Linux and Windows guidance is presented with equal prominence, or clarify when steps are OS-agnostic.
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 ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides a comprehensive support matrix for Azure VM backups, covering both Windows and Linux. However, there is a notable Windows-first bias: Windows scenarios, tools (such as MARS agent, DPM, MABS), and PowerShell are mentioned first and in more detail. Linux support is described separately and is more limited, with several backup/restore methods (e.g., MARS agent, DPM/MABS) not supported for Linux. Some restore instructions reference PowerShell without mentioning Linux CLI equivalents. Linux examples and parity are less prominent, and some advanced backup features are Windows-only.
Recommendations
  • Where PowerShell is mentioned for restore or backup operations, add equivalent Azure CLI or Bash examples for Linux users.
  • When listing supported scenarios or tools, present Windows and Linux options together, or clarify up front which are Windows-only and which are cross-platform.
  • Expand Linux sections to include more detailed guidance, especially for restore scenarios and file-level restore limitations.
  • Clearly indicate in each scenario/table which features are Windows-only, Linux-only, or cross-platform, to reduce ambiguity.
  • Where possible, provide workarounds or alternatives for Linux users when a feature is not supported.
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
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation references PowerShell and Visual Studio as primary deployment methods, both of which are Windows-centric tools. PowerShell is mentioned before alternatives, and Visual Studio is listed as a deployment option without mention of cross-platform equivalents. There are no explicit Linux/macOS CLI or automation examples, and the documentation does not highlight Azure CLI or other platform-neutral tools for deployment, which may create friction for non-Windows users.
Recommendations
  • Add explicit examples and links for deploying Cloud Services (extended support) using Azure CLI, which is cross-platform.
  • Clarify that PowerShell and Visual Studio are Windows-centric, and provide alternative instructions for Linux/macOS users.
  • Ensure deployment steps and automation scripts are available for Bash/shell environments.
  • List platform-neutral tools (e.g., Azure CLI, VS Code) before or alongside Windows-specific tools.
  • Include a note on supported platforms for each deployment method.
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, without mentioning or providing examples for Linux-based DNS servers (e.g., BIND). All on-premises DNS configuration guidance is Windows-centric, which may hinder Linux users. Azure-side steps are cross-platform, but on-premises guidance lacks Linux parity.
Recommendations
  • Add a section or example for configuring conditional forwarders on a Linux-based DNS server (such as BIND/named), including relevant configuration file snippets.
  • Explicitly mention that the procedure applies to both Windows and Linux DNS servers, and link to official documentation for Linux DNS configuration.
  • Where screenshots are used for Windows DNS Manager, consider adding equivalent CLI or config file examples for Linux environments.
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: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page provides PowerShell examples for gateway subnet creation and references PowerShell cmdlets for configuration, but does not include equivalent Azure CLI (cross-platform) or Bash examples. This creates friction for Linux/macOS users who may prefer or require CLI-based workflows.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all resource creation and configuration steps, especially for gateway subnet creation.
  • Reference Azure CLI documentation and commands in the REST APIs and PowerShell cmdlets section, ensuring parity with PowerShell resources.
  • Where screenshots or instructions reference PowerShell, clarify that equivalent steps can be performed with Azure CLI and provide links or examples.
  • Consider listing CLI examples before or alongside PowerShell to signal equal support for cross-platform users.
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 page provides step-by-step instructions for configuring an outbound-only load balancer in Azure. When creating the virtual machine, the guide exclusively uses a Windows Server 2022 image and references Windows tools (e.g., Microsoft Edge browser) for connectivity testing. There are no Linux VM creation examples, nor are Linux tools or workflows mentioned for testing outbound connectivity. This creates friction for users wishing to deploy Linux-based workloads.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu or CentOS) in the VM creation section.
  • When testing connectivity, provide Linux-based alternatives (e.g., using curl or wget from the terminal) alongside the Windows browser example.
  • Clarify that the load balancer configuration applies to both Windows and Linux VMs, and link to relevant Linux documentation if available.
  • When referencing tools for connectivity testing, mention both Windows and Linux options.
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 troubleshooting commands are presented first and primarily using Windows tools (psping.exe, PowerShell syntax), with Linux alternatives either missing or only briefly mentioned. Some sections provide only Windows examples, and Linux users are left to infer equivalent commands or tools.
Recommendations
  • Provide Linux/macOS equivalents for all troubleshooting commands (e.g., use 'nc', 'telnet', or 'nmap' for port checks, and 'hping3' or 'tcping' for TCP tests).
  • List Linux/macOS commands alongside Windows commands, not after or as an afterthought.
  • When referencing downloadable tools (like psping.exe), suggest cross-platform alternatives or note their platform limitations.
  • Include example outputs for both Windows and Linux commands to help users interpret results.
  • Avoid using Windows-specific paths or syntax (e.g., '.\psping.exe') without also providing the Linux equivalent.
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, listing Azure portal, Azure CLI, PowerShell, and C# methods. PowerShell is highlighted as a distinct option, and C#/.NET samples are referenced. While Azure CLI is cross-platform, there are no explicit Linux/macOS shell examples (e.g., Bash), nor are there references to Linux-specific tooling or workflows. Windows/PowerShell options are presented before Linux-native alternatives, and the sample code is .NET-focused.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users, especially for CLI usage.
  • Clarify that Azure CLI commands work on Linux/macOS and provide sample terminal commands.
  • Include references or samples for other languages/platforms (e.g., Python, JavaScript) if available.
  • Ensure that instructions do not assume use of PowerShell or Windows-only tooling.
  • Consider listing cross-platform options (CLI) before Windows-specific ones (PowerShell).
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell deployment instructions, but PowerShell is presented as an equal alternative rather than secondary. However, there are no explicit Linux/macOS-specific instructions or examples (e.g., bash shell, Cloud Shell), and the web server deployed is IIS (Windows-only), with no mention of Linux VM or web server alternatives. This may create friction for Linux/macOS users who wish to deploy a Linux-based solution.
Recommendations
  • Add explicit instructions or examples for deploying and testing with Linux VMs (e.g., using NGINX or Apache instead of IIS).
  • Clarify that the current template deploys Windows VMs with IIS, and provide a link or instructions for a Linux-based load balancer quickstart.
  • Consider showing Azure CLI (cross-platform) examples first, and PowerShell second.
  • Mention that Azure CLI works on all platforms, and reference Azure Cloud Shell as a browser-based, cross-platform option.
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 Azure CLI (bash) or Linux/macOS-specific instructions. The deployment walkthrough is PowerShell-centric, and the IIS web server example further reinforces a Windows-first approach. While the page mentions that other methods (Azure CLI, REST API, portal) are available, it does not provide concrete examples or guidance for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI (bash) examples for template deployment, including parameter prompts and resource group creation.
  • Include instructions for running the deployment from Linux/macOS environments using Azure CLI.
  • Clarify that the Cloud Shell supports both Bash and PowerShell, and provide links or examples for both.
  • If IIS is used only for demonstration, mention how Linux users could test with a simple NGINX or Apache setup, or clarify that the template is Windows VM-specific.
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 documentation provides only Windows Server VM creation instructions and exclusively uses PowerShell commands to install IIS, with no mention of Linux VM options or equivalent Linux web server setup. This creates friction for Linux users who wish to follow the tutorial.
Recommendations
  • Provide parallel instructions for creating Linux-based VMs (e.g., Ubuntu) in the 'Create virtual machines' section.
  • Add a section or alternative steps for installing a web server (such as Apache or Nginx) on Linux VMs, including the necessary shell commands.
  • When showing PowerShell commands for Windows, also show bash commands for Linux where applicable.
  • Explicitly mention that the tutorial can be followed with Linux VMs and link to relevant Linux documentation for web server installation.
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 across regions using the Azure Portal and Azure PowerShell. However, it does not include any examples or guidance for users of Azure CLI (which is cross-platform and preferred by many Linux/macOS users) or Bash scripting. All command-line instructions are exclusively in PowerShell, and there is no mention of Azure CLI equivalents.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell command-line steps, including resource export, deployment, and verification.
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide links or code blocks for common tasks.
  • Where file editing is required (e.g., editing JSON templates), suggest cross-platform editors (such as 'code', 'nano', or 'vim') instead of only 'notepad.exe'.
  • Add a short section or note clarifying that all operations can be performed from Linux/macOS using Azure CLI, and link to relevant Azure CLI documentation.
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 using PowerShell). There are no equivalent instructions or examples for Linux VMs or for using Linux-native tools (e.g., Apache, Nginx). This creates friction for users who wish to use Linux VMs as load balancer backends.
Recommendations
  • Add a parallel section showing how to create Linux VMs as backend pool members.
  • Provide Linux-specific instructions for installing a web server (e.g., Apache or Nginx) on Ubuntu/CentOS VMs, including the necessary shell commands.
  • Explicitly state that the backend VMs can be either Windows or Linux, and link to relevant quickstarts for both.
  • When showing PowerShell commands, also show equivalent Bash/SSH commands for Linux.
  • Clarify in the prerequisites or introduction that the example uses Windows VMs, but Linux is also supported.
GitHub Create Pull Request
Migrate Create an Azure SQL assessment ...articles/migrate/how-to-create-azure-sql-assessment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation is generally cross-platform, focusing on Azure SQL assessment via the Azure Migrate tool, which supports SQL Server on any OS. However, there are several instances where Windows-specific tools, features, or documentation are referenced first or exclusively (e.g., Windows Server Failover Clusters, Cloud Witness, and links to Windows-specific best practices). Linux equivalents or considerations are not mentioned, and the documentation assumes familiarity with Windows-based SQL Server deployments.
Recommendations
  • Wherever Windows-specific features (e.g., Cloud Witness, Windows Server Failover Clusters) are mentioned, add notes or links about Linux equivalents (e.g., Linux clustering, Pacemaker, or other HA/DR options for SQL Server on Linux).
  • When linking to best practices for SQL Server on Azure VMs, include both Windows and Linux documentation links.
  • Clarify in the 'Assessment settings' and 'High availability and disaster recovery properties' sections which options are Windows-only and provide guidance for Linux users.
  • Explicitly state that the assessment process applies to SQL Server on Linux as well, and note any limitations or differences.
  • Add examples or screenshots that include Linux-based SQL Server instances, if supported.
GitHub Create Pull Request
Migrate Tutorial to assess SQL instances in VMware VMs for migration to SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database ...ob/main/articles/migrate/tutorial-assess-sql-vmware.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation is generally platform-neutral, focusing on assessing SQL Server instances in VMware VMs for migration to Azure SQL solutions. However, there are subtle signs of Windows bias: references to Windows Server Failover Clusters and Cloud Witness are made without mentioning Linux equivalents, and links to performance guidelines and high availability features are Windows-centric. The order and examples tend to prioritize Windows scenarios, with no explicit Linux/SQL Server on Linux references or examples.
Recommendations
  • Include explicit guidance or notes for SQL Server instances running on Linux VMs, clarifying any differences in assessment or migration steps.
  • Where high availability and disaster recovery options are discussed, mention Linux clustering solutions (e.g., Pacemaker) and provide relevant Azure documentation links.
  • Add references or links to performance guidelines for SQL Server on Linux VMs in Azure.
  • Clarify if the Azure Migrate assessment tool supports SQL Server on Linux and, if so, provide examples or screenshots for Linux-based scenarios.
  • Ensure terminology and screenshots do not implicitly assume Windows-only environments unless the feature is truly Windows-specific.
GitHub Create Pull Request
Migrate Tutorial to assess SQL instances for migration to SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database ...docs/blob/main/articles/migrate/tutorial-assess-sql.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. While the tutorial is about assessing SQL Server instances for migration to Azure SQL, which is relevant to both Windows and Linux environments, several examples and references (such as cluster quorum configuration and Cloud Witness) are Windows-centric. The documentation refers to Windows Server Failover Clusters and provides links to Windows-specific best practices and tools, without mentioning Linux equivalents (e.g., Pacemaker clusters, Linux witness options). There are no explicit Linux/PowerShell/Bash command examples, nor guidance for Linux-based SQL Server deployments.
Recommendations
  • Add explicit guidance or notes for users assessing SQL Server on Linux, including any differences in assessment, migration, or high availability/disaster recovery options.
  • Include references or links to Linux-based SQL Server clustering and witness configuration documentation (e.g., Pacemaker, Linux witness options).
  • Where Windows-specific features (like Cloud Witness) are mentioned, clarify their applicability and provide Linux alternatives or state if not applicable.
  • Provide examples or screenshots that reflect Linux environments, where relevant (e.g., SQL Server on Linux VMs).
GitHub Create Pull Request
Nat Gateway Manage a Standard V2 NAT Gateway ...lob/main/articles/nat-gateway/manage-nat-gateway-v2.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 step-by-step instructions for managing a Standard V2 NAT Gateway using the Azure portal and Azure PowerShell. However, it does not include any examples or instructions for using the Azure CLI, which is cross-platform and widely used on Linux and macOS. All command-line examples are PowerShell-specific, and there is no mention of Bash, Azure CLI, or Cloud Shell Bash usage. This creates friction for Linux/macOS users who may not use PowerShell.
Recommendations
  • Add Azure CLI (az) command examples for all operations currently shown with PowerShell, such as creating, associating, and deleting NAT gateways, and managing public IPs/prefixes.
  • Include a tab or section for Azure CLI alongside the existing Azure portal and Azure PowerShell tabs.
  • In the prerequisites, mention that Azure CLI can be used and provide installation or usage links for Linux/macOS users.
  • Where possible, clarify that Azure PowerShell can be run in Azure Cloud Shell (which supports Bash and PowerShell), but recommend Azure CLI for Linux/macOS parity.
GitHub Create Pull Request
Nat Gateway Quickstart: Create a Standard V2 Azure NAT Gateway - Deployment templates ...-gateway/quickstart-create-nat-gateway-v2-templates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides deployment instructions for both ARM and Bicep templates, but the primary ARM template deployment example is PowerShell-focused and uses Azure Cloud Shell with PowerShell commands. Azure CLI (cross-platform) is only shown for Bicep, and PowerShell is consistently presented first. There are no Linux-specific deployment examples for the ARM template path, and PowerShell is emphasized throughout.
Recommendations
  • Add Azure CLI examples for ARM template deployment alongside the PowerShell examples, since Azure CLI is cross-platform and widely used on Linux/macOS.
  • Present Azure CLI and PowerShell examples in parallel tabs for both ARM and Bicep sections, or default to CLI first for parity.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
  • Ensure that any references to copying/pasting scripts or using the shell mention both Bash and PowerShell users.
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 provides examples for managing API Management multi-region deployments using Azure CLI and Azure PowerShell, but does not mention or provide examples for Linux/macOS-specific tools or workflows. Azure PowerShell is referenced alongside Azure CLI, and the PowerShell cmdlet is mentioned before other tools in the section about disabling routing to a regional gateway. No Linux/macOS-specific shell examples (e.g., Bash) or platform notes are included, and the documentation assumes familiarity with Azure portal and CLI, which are cross-platform, but PowerShell is traditionally Windows-centric.
Recommendations
  • Add explicit notes clarifying that Azure CLI commands work on Linux/macOS as well as Windows.
  • Provide Bash shell examples for equivalent operations, especially for tasks currently shown only with Azure PowerShell.
  • Reorder tool mentions so that cross-platform tools (Azure CLI) are listed before Windows-centric tools (PowerShell).
  • Include a brief section or note on platform compatibility for all tools referenced.
  • Where possible, link to documentation on installing and using Azure CLI and PowerShell on Linux/macOS.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation is generally cross-platform and covers both Windows and Linux scenarios for Azure Functions app settings. However, there are some instances of Windows bias: Windows-specific syntax (e.g., %HOME% in AzureWebJobs_TypeScriptPath) is shown without Linux equivalents; PowerShell-specific settings are documented in detail, while other language runtimes (e.g., bash, sh) are not mentioned; and Windows-only settings (e.g., WEBSITE_NODE_DEFAULT_VERSION) are called out, but Linux equivalents are not always shown first or equally. Some examples and patterns (such as hierarchical delimiters) explain Windows behavior before Linux. The use of Azure CLI and Azure PowerShell is recommended for managing settings, but Linux-native tools (e.g., bash, curl) are not suggested.
Recommendations
  • For settings where Windows syntax is shown (e.g., %HOME%), add equivalent Linux/macOS examples (e.g., $HOME).
  • When documenting PowerShell-specific settings, provide parity by mentioning if similar settings exist for bash/sh or other Linux-native runtimes.
  • When recommending tools for managing app settings, include Linux-native options (e.g., Azure CLI usage from bash, REST API with curl) alongside Azure PowerShell.
  • In sections discussing reserved delimiters (double-underscore vs colon), present Linux behavior first or equally, and clarify differences up front.
  • For settings that are OS-specific (e.g., WEBSITE_NODE_DEFAULT_VERSION), always indicate Linux alternatives or explicitly state if none exist.
GitHub Create Pull Request
Azure Functions Guide for running C# Azure Functions in an isolated worker process ...icles/azure-functions/dotnet-isolated-process-guide.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation is largely cross-platform and provides both Windows and Linux guidance for running C# Azure Functions in the isolated worker process. However, there are a few areas where Windows tools or patterns are mentioned before Linux equivalents, and some CLI examples default to Windows-first (e.g., checking 32/64-bit status, ReadyToRun instructions). Azure PowerShell is listed as a deployment option alongside Azure CLI, but not all Linux users will have PowerShell installed. Overall, Linux parity is strong, but minor ordering and tool preference biases exist.
Recommendations
  • When listing deployment or resource creation methods, mention Azure CLI before Azure PowerShell, as CLI is more universally available across platforms.
  • In tables or lists that show both Windows and Linux instructions, alternate the order or clarify that both are equally supported.
  • Where CLI commands are shown for Windows, ensure Linux equivalents are shown immediately after or in parallel.
  • If referencing Visual Studio, always mention Visual Studio Code as an alternative for Linux/macOS users in the same context.
  • Explicitly state in the introduction that all features (unless noted) are supported on both Windows and Linux, to reassure non-Windows users.
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 hosting scenarios for Azure Functions. However, there are minor signs of Windows bias: in the 'Mount file shares' section, PowerShell examples are presented alongside Azure CLI, and references to Windows hosting plans (e.g., Consumption plan on Windows) appear before Linux equivalents in some places. The majority of examples and guidance are platform-neutral, and Linux-specific features (like mounting Azure Files shares) are clearly documented. There are no critical omissions for Linux users.
Recommendations
  • Ensure that Linux examples (CLI, code snippets) are presented before or alongside Windows/PowerShell examples, especially in sections relevant to both platforms.
  • Where PowerShell is shown, consider also providing Bash or Linux shell equivalents if applicable.
  • Explicitly clarify platform applicability in each example or section to help users quickly identify relevant instructions.
  • Continue to expand Linux-specific guidance, especially for advanced deployment and storage scenarios.
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 is generally cross-platform and focused on ARM template functions, which are platform-agnostic. However, in the section describing how to determine which resource types have a list operation, the PowerShell example is presented before the Azure CLI example. This ordering may subtly favor Windows/PowerShell users, but both Windows and Linux/macOS users are provided with equivalent instructions.
Recommendations
  • Present Azure CLI and PowerShell examples side-by-side or alternate the order to avoid implicit prioritization.
  • Explicitly state that both Azure CLI and PowerShell are available on all major platforms, and provide links to installation guides for each.
  • Where possible, include Bash or shell scripting examples for Linux/macOS users, especially in sections where command-line usage is demonstrated.
GitHub Create Pull Request
Backup Back Up Azure VMs in a Recovery Services Vault ...b/main/articles/backup/backup-azure-arm-vms-prepare.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation generally presents a platform-neutral workflow for backing up Azure VMs, with both Windows and Linux VMs supported. However, in the 'Install the VM agent' section, instructions for Windows appear before Linux, which is a minor instance of Windows-first ordering. Both platforms are covered with appropriate detail, and no critical steps are Windows-only.
Recommendations
  • Consider alternating the order of Windows and Linux instructions in sections where both are equally relevant, or present them in parallel tabs to avoid perceived preference.
  • Where possible, clarify that all main backup workflows apply equally to both Windows and Linux VMs.
  • Continue ensuring that Linux-specific details (such as package names or commands) are as explicit as Windows instructions.
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 neutral, but there are minor signs of Windows bias: Windows-specific technologies (like VSS and MARS agent) are referenced directly, and Windows examples (e.g., VSS for application-consistent backup) are mentioned before Linux equivalents. Linux alternatives are referenced only briefly ("pre or post scripts for Linux") and not linked or explained in detail. Some backup features/tools (DPM, MABS) are Windows-centric, but these are marked as workload-specific and do not constitute bias under the provided guidelines.
Recommendations
  • Where Windows technologies like VSS are referenced, provide equivalent Linux mechanisms (e.g., LVM snapshots, fsfreeze, application scripts) with links to relevant documentation.
  • In sections mentioning backup agents or extensions (e.g., MARS agent), clarify Linux support or alternatives if applicable.
  • When describing application-consistent backup, offer equal detail for Linux approaches (not just a parenthetical mention).
  • Ensure that examples and references are balanced between Windows and Linux, or explicitly state when a feature is Windows-only.
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 Azure Bastion FAQ documentation demonstrates minor Windows bias in several areas. Browser recommendations mention Windows first and provide more detail for Windows users. Instructions for setting keyboard layouts are Windows-specific, with no guidance for Linux or macOS users. There are no Linux/macOS-specific examples or instructions for tasks such as keyboard configuration or file transfer, despite Azure Bastion supporting SSH (commonly used on Linux/macOS).
Recommendations
  • Add instructions for setting keyboard layouts on Linux and macOS systems alongside the Windows guidance.
  • When listing supported browsers, avoid listing Windows first and provide parity in recommendations for Linux/macOS browsers.
  • Include examples or notes for file transfer using SSH clients on Linux/macOS, as well as RDP clients available for those platforms.
  • Where native client usage is mentioned, clarify supported clients for Linux/macOS and provide links to relevant documentation.
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 and PowerShell examples for all CLI commands, but PowerShell examples are consistently present and sometimes shown before or alongside Bash. This can be interpreted as a mild Windows bias, as PowerShell is primarily a Windows shell (though it is available cross-platform). No Linux-specific tools or workflows are omitted, and Bash examples are always present, ensuring Linux/macOS users can follow along. However, the inclusion of PowerShell in every example and the presence of 'devx-track-azurepowershell' metadata may signal a slight preference for Windows environments.
Recommendations
  • Ensure Bash examples are always shown first, as Bash is the default shell for most Linux/macOS users.
  • Clarify in the introduction that both Bash and PowerShell are supported, and that Bash is recommended for Linux/macOS.
  • Consider adding a note that PowerShell Core is available cross-platform, but Bash is more common on Linux/macOS.
  • Review metadata and ensure parity in tracking for Bash and PowerShell usage.
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 parallel examples for Azure Portal, Azure CLI, and PowerShell, but PowerShell is given equal prominence to Azure CLI and is described as usable both locally and in Azure Cloud Shell. Some PowerShell examples reference Windows file paths (e.g., D:\testFiles\textfile.csv), which may confuse Linux/macOS users. There is no explicit mention of Linux/macOS alternatives for file upload or local file path conventions. The CLI examples are cross-platform, but PowerShell's presence and Windows-centric file paths create minor friction for non-Windows users.
Recommendations
  • Clarify that PowerShell commands can be run in Azure Cloud Shell (which is cross-platform) and/or locally on any OS with PowerShell Core.
  • For file upload examples, provide Linux/macOS path examples (e.g., /home/user/testFiles/textfile.csv) alongside Windows paths.
  • Explicitly state that Azure CLI is fully cross-platform and recommend it for Linux/macOS users.
  • Add notes or links for installing PowerShell Core on Linux/macOS if users prefer PowerShell.
  • Where local file operations are shown, mention OS-specific conventions or provide alternative commands for Linux/macOS.
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: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both PowerShell and curl examples for invoking Azure Functions and viewing logs, but PowerShell examples are consistently presented before curl. All other instructions use the Azure CLI, which is cross-platform. No exclusive Windows tools or patterns are used, and Linux/macOS users can follow all steps without issue.
Recommendations
  • Present curl examples before PowerShell, or present both side-by-side to avoid the perception of Windows-first bias.
  • Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS.
  • Consider adding bash or zsh shell examples if relevant, though curl is sufficient for HTTP requests.
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: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation is generally platform-neutral, but there are a few instances where Windows-centric tools (PowerShell) are referenced as the primary or only method for certain operations, such as updating Azure Firewall Policy tags. There are no Linux/macOS-specific examples or CLI parity recommendations in these cases.
Recommendations
  • Where PowerShell is referenced as the only workaround (e.g., updating tags), add equivalent Azure CLI commands and examples, which are cross-platform.
  • Explicitly mention REST API or ARM template alternatives when PowerShell is not available or supported.
  • Ensure that mitigation steps and workarounds do not assume the user is on Windows; provide CLI and portal instructions where possible.
  • Review all tool references and ensure parity between PowerShell and Azure CLI in documentation examples.
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 prompt) and Windows (PowerShell prompt), but the example SSH commands use Windows-style paths (e.g., .\Downloads\lb-key-pair.pem) and show the Windows example first. No PowerShell-specific commands or Windows-only tools are used, and Linux users are not blocked from completing the tutorial. The NGINX installation steps are Linux-specific, indicating the VMs are likely Linux-based.
Recommendations
  • Present both Linux/Mac and Windows SSH command examples, with Linux/Mac shown first or side-by-side.
  • Use platform-neutral path examples (e.g., ~/Downloads/lb-key-pair.pem for Linux/Mac, .\Downloads\lb-key-pair.pem for Windows) and clarify which is for which OS.
  • Explicitly state that the tutorial is for Linux VMs (if true), or provide Windows VM instructions if applicable.
GitHub Create Pull Request
Logic Apps Call Azure Functions from workflows ...cles/logic-apps/call-azure-functions-from-workflows.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation provides a list of tools for creating Azure Functions, including Visual Studio, Visual Studio Code, Azure CLI, Azure PowerShell, and ARM templates. While most tools are cross-platform, PowerShell and Visual Studio are Windows-centric. Additionally, when instructing users to find the tenant ID, a PowerShell command (Get-AzContext) is mentioned before the Azure Portal method, which may create a subtle Windows-first impression. However, the majority of the guide is platform-neutral, focusing on Azure Portal and web-based workflows, and examples for function code are in JavaScript (cross-platform).
Recommendations
  • When listing tools for creating Azure Functions, clarify which are cross-platform (e.g., Visual Studio Code, Azure CLI, ARM templates) and which are Windows-only (Visual Studio, Azure PowerShell).
  • Provide equivalent Linux/macOS commands (e.g., Azure CLI) alongside PowerShell commands for tasks like retrieving the tenant ID.
  • When mentioning PowerShell, avoid presenting it before cross-platform alternatives unless it is the only option.
  • Explicitly state that most steps can be performed from any OS via the Azure Portal or cross-platform tools.
GitHub Create Pull Request
Logic Apps Create workflows with multiple Azure services ...ic-apps/tutorial-process-email-attachments-workflow.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 demonstrates a mild Windows bias. While it does mention both Azure PowerShell and Azure CLI for resource creation and management, PowerShell is consistently listed before CLI, and the examples reference PowerShell tabs and links first. The use of Microsoft Azure Storage Explorer, a GUI tool available for Windows, macOS, and Linux, is required, but no alternative CLI or cross-platform instructions are provided for users who may prefer command-line tools. Additionally, in the function app creation section, Windows is selected as the example OS, and in-portal editing is noted as only available on Windows, but Linux options are not highlighted or explained for parity.
Recommendations
  • Alternate the order of PowerShell and Azure CLI instructions or present both equally, with clear cross-platform guidance.
  • Explicitly mention that Azure CLI and PowerShell are available on all major platforms, and provide example commands for both.
  • For steps involving Storage Explorer, offer equivalent Azure CLI or azcopy commands for users who prefer or require command-line tools.
  • When showing function app creation, provide parallel instructions or notes for Linux/macOS users, especially regarding local development and OS selection.
  • Clarify any Windows-only limitations (such as in-portal editing) and direct Linux/macOS users to alternative workflows.
GitHub Create Pull Request
Nat Gateway What is Azure NAT Gateway? ...re-docs/blob/main/articles/nat-gateway/nat-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation is generally platform-neutral, focusing on Azure NAT Gateway concepts and configuration. However, there are minor instances of Windows bias: (1) Windows-specific services (Windows Activation and Windows Updates) are mentioned as requiring outbound connectivity, while Linux equivalents are not referenced; (2) upgrade guidance for basic public IPs and Load Balancers links to PowerShell-based instructions, which are typically Windows-centric, and does not mention CLI or Linux alternatives first.
Recommendations
  • When discussing outbound connectivity requirements, mention Linux equivalents (e.g., package updates via apt/yum) alongside Windows Activation/Updates.
  • Where upgrade instructions are linked (e.g., upgrading Load Balancer or public IP), ensure that Azure CLI and/or portal-based instructions are referenced equally or before PowerShell, and clarify cross-platform options.
  • Add explicit examples or notes for Linux/macOS users where relevant, especially in sections referencing tooling or OS-specific outbound needs.
GitHub Create Pull Request