← Back to Dashboard
229
Pages Scanned
62
Pages Flagged
229
Changed Pages
27.1%
% Pages Flagged

Scan Information

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

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

Status: completed

Target Repo: Azure

Current Phase: discovery

Files Queued: 229

Files Completed: 229

Problematic Pages

62 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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The tutorial exclusively uses Azure PowerShell and Windows PowerShell cmdlets for all steps, including certificate creation and resource management. It assumes a local administrative PowerShell session, and the certificate creation relies on Windows-only tools (New-SelfSignedCertificate, Export-PfxCertificate), with no mention of Linux/macOS alternatives. There are no Bash, Azure CLI, or cross-platform instructions, making it difficult for Linux/macOS users to follow the tutorial as written.
Recommendations
  • Add equivalent Azure CLI (az) commands for all resource creation and management steps.
  • Provide instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and explain how to use them in Azure.
  • Clarify which steps are Windows-specific and offer cross-platform alternatives where possible.
  • Include notes or links to cross-platform documentation for users who do not have access to Windows or PowerShell.
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
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 images for VM creation and provides only Windows/PowerShell instructions for configuring IIS on backend VMs. There are no Linux VM options, nor any Bash/SSH or Linux-native web server setup examples. Windows tools and patterns (PowerShell, IIS) are mentioned exclusively, with no Linux parity.
Recommendations
  • Include instructions for creating Linux-based VMs (e.g., Ubuntu) as backend pool members.
  • Provide Linux-specific steps for installing a web server (e.g., Apache or Nginx) using Bash/SSH.
  • Offer both Windows and Linux examples side-by-side for backend configuration and testing.
  • Clarify that backend VMs can be either Windows or Linux, and link to relevant Linux setup guides.
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 'Manage certificates in Azure Automation' demonstrates a notable bias towards Windows/PowerShell tooling and workflows. PowerShell cmdlets are featured prominently and exclusively for certificate management tasks (creation, deletion, modification), with no equivalent CLI or Linux-native examples. The only alternatives shown are Python runbook functions, but these are limited to certificate retrieval and do not cover management operations. The portal workaround also recommends PowerShell as the solution. Windows/PowerShell tools and patterns are mentioned first and most extensively.
Recommendations
  • Add Azure CLI examples for certificate management tasks (create, update, delete) to support Linux/macOS users.
  • Include REST API or ARM template deployment instructions that can be executed from any platform.
  • Clarify which operations are platform-agnostic and which require Windows/PowerShell, and provide parity where possible.
  • If PowerShell is required for certain tasks, explicitly state this and suggest alternatives for Linux/macOS users where feasible.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page for Azure Application Gateway v2 shows a moderate Windows bias. Migration guidance and registration/unregistration for the Basic SKU preview are provided only with Azure PowerShell commands, and the main tutorial link is PowerShell-focused. There are no Linux/macOS CLI (az CLI) or ARM template examples, and PowerShell is presented as the default method for key operations.
Recommendations
  • Add equivalent Azure CLI (az) command examples for registration, unregistration, and migration tasks, ensuring Linux/macOS users have clear guidance.
  • Include links to ARM template or Bicep deployment guides where relevant.
  • When listing tutorials, offer parity by linking to both PowerShell and Azure CLI versions, or clarify which platforms are supported.
  • Explicitly state that PowerShell commands can be run cross-platform (if true), or provide platform-specific notes.
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, there is a notable bias in example commands: the only explicit command-line example for identifying a VM's associated Key Vault uses PowerShell, with no equivalent Azure CLI or Bash example provided. Additionally, PowerShell is mentioned before Azure CLI in the section about setting access policies, and screenshots and instructions are portal-centric, which is neutral but may favor Windows users slightly.
Recommendations
  • Provide equivalent Azure CLI and Bash examples alongside PowerShell commands, especially for tasks like identifying the Key Vault associated with a VM.
  • When mentioning automation options, list Azure CLI and Bash alternatives before or alongside PowerShell to avoid Windows-first ordering.
  • Add explicit Linux/macOS-friendly instructions or notes where relevant, such as command syntax differences or prerequisites.
  • Ensure that all command-line examples are available for both Windows and Linux users, and clarify any OS-specific requirements.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides only Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI (cross-platform) or Bash examples. The deployment walkthrough is written entirely around PowerShell usage, and the output screenshots reference PowerShell. Additionally, the template configures Internet Information Services (IIS), a Windows-only web server, as the default workload, which further centers the example on Windows environments.
Recommendations
  • Add Azure CLI (az) and/or Bash examples for deploying the ARM template, alongside the PowerShell script.
  • Explicitly mention that the Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
  • If possible, offer an alternative template or instructions for deploying a Linux-based workload (e.g., Apache or Nginx) for users who do not wish to use IIS.
  • Ensure screenshots and walkthroughs include both PowerShell and CLI outputs where relevant.
GitHub Create Pull Request
App Service Environment Variables and App Settings Reference ...ob/main/articles/app-service/reference-app-settings.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page provides extensive coverage of environment variables and app settings for Azure App Service, but exhibits several Windows-centric biases. Windows-specific paths (e.g., D:\home), tools (e.g., msbuild, Web Deploy/MSDeploy), and configuration references (e.g., applicationHost.config, IIS, w3wp.exe) are mentioned frequently and often before their Linux equivalents. Some examples and explanations default to Windows conventions, and certain sections (such as build automation and logging) provide more detail for Windows than Linux. Linux-specific options are present but less emphasized, and examples for Linux/macOS users are sometimes missing or less detailed.
Recommendations
  • Ensure Linux and macOS equivalents are mentioned alongside Windows tools and paths, especially in tables and examples.
  • Provide Linux/macOS-specific examples and usage patterns where Windows tools (e.g., msbuild, Web Deploy) are referenced.
  • When describing environment variables, list Linux and Windows paths side-by-side (e.g., D:\home and /home).
  • Clarify which settings are platform-specific and provide parity in explanation and detail for Linux features (e.g., Oryx build automation, container settings).
  • Add explicit notes or tabs for Linux/macOS users where workflows or troubleshooting steps differ.
  • Review sections where Windows terminology (e.g., applicationHost.config, IIS, w3wp.exe) is used and ensure Linux alternatives or limitations are described.
GitHub Create Pull Request
Application Gateway Migrate from V1 to V2 - Azure Application Gateway ...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation for migrating Azure Application Gateway from V1 to V2 is heavily focused on Azure PowerShell scripts and cmdlets, with all examples and instructions using PowerShell syntax. There is no mention of Bash, Azure CLI, or cross-platform alternatives, nor are there Linux/macOS-specific instructions or examples. The guidance assumes the use of PowerShell modules and tools, which are native to Windows and only recently supported on Linux/macOS, potentially creating friction for non-Windows users.
Recommendations
  • Provide equivalent Azure CLI (az) commands and scripts for all migration steps, including configuration cloning and IP retention.
  • Add explicit instructions for running PowerShell scripts on Linux/macOS, including prerequisites (e.g., installing PowerShell Core, Az modules).
  • Include Bash script examples or references for common migration tasks.
  • Clarify cross-platform support for the provided PowerShell scripts (e.g., test and document compatibility with PowerShell Core on Linux/macOS).
  • Mention Azure Cloud Shell as a cross-platform alternative more prominently, and provide direct links or guidance for using it.
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, and the 'Next steps' section directs users to a PowerShell-specific guide. While Azure CLI is mentioned and a CLI example is provided, the PowerShell instructions are more comprehensive and appear first. There is no mention of Linux-specific tools or workflows, and no explicit Linux/macOS parity guidance is offered.
Recommendations
  • Ensure CLI examples are as detailed as PowerShell examples, including step-by-step instructions for all major configuration tasks.
  • Add explicit guidance for Linux/macOS users, such as certificate extraction/management using OpenSSL or other cross-platform tools.
  • In the 'Next steps' section, provide links to both PowerShell and CLI guides, or a unified guide with platform-specific tabs.
  • Where possible, avoid presenting PowerShell examples before CLI unless there is a technical reason (e.g., feature parity lag in CLI).
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 Azure PowerShell scripts as the primary migration tooling, with no mention of Azure CLI or Bash alternatives. All automation and migration examples are PowerShell-centric, which may create friction for Linux/macOS users who prefer Bash or Azure CLI. There are no Linux/macOS-specific instructions or parity examples.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples for migration tasks, especially for public IP retention and configuration migration.
  • Explicitly state OS/platform requirements for the PowerShell scripts and link to cross-platform PowerShell installation guides.
  • Add guidance or references for Linux/macOS users on how to perform migration steps using their preferred tools.
  • Where possible, offer downloadable scripts in both PowerShell and Bash/Azure CLI formats.
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 (with links to registry settings and PowerShell cmdlets) are mentioned first and in greater detail. Several backup and retention examples reference Windows PowerShell cmdlets without offering equivalent Linux CLI or Azure CLI alternatives, and asset management relies on Windows-centric tooling. Linux instructions are present but less detailed and less integrated into the workflow.
Recommendations
  • Provide Azure CLI or REST API equivalents for PowerShell cmdlets used in backup/export/recovery operations, especially for Linux/macOS users.
  • Include Linux-first or cross-platform examples where possible, such as using Bash scripts or Azure CLI for exporting runbooks and DSC configurations.
  • Balance the order of presentation so that Linux and Windows guidance are given equal prominence, or group platform-specific instructions clearly.
  • Clarify which operations are platform-agnostic and which require Windows, and offer alternatives or workarounds for Linux/macOS users.
GitHub Create Pull Request
Automation Configure runbook input parameters in Azure Automation ...b/main/articles/automation/runbook-input-parameters.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page on configuring runbook input parameters in Azure Automation demonstrates a notable bias towards Windows and PowerShell environments. Most examples, screenshots, and step-by-step instructions focus on PowerShell, PowerShell Workflow, and graphical runbooks (which are PowerShell-based). There is minimal coverage of Python runbooks, and no examples or guidance for Bash, Linux shell scripts, or cross-platform command-line usage. Additionally, all CLI examples use PowerShell syntax and Windows-centric cmdlets, with no mention of Linux/macOS equivalents or considerations.
Recommendations
  • Add examples for starting runbooks and passing parameters using Azure CLI (az automation runbook ...), which is cross-platform.
  • Provide sample code or instructions for Bash or shell script usage, especially for Linux/macOS users.
  • Expand the Python runbook section with concrete parameter passing examples, including how to invoke Python runbooks from Linux/macOS.
  • Clarify which features or steps are platform-agnostic and which are Windows/PowerShell-specific.
  • Include notes or links for Linux/macOS users on prerequisites and alternative tooling.
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_first
Summary
The documentation for disaster recovery in Azure Automation is heavily focused on PowerShell scripts and workflows for migration tasks, with no mention of Bash, Python, or Linux-native alternatives. While the page states applicability to both Linux and Windows VMs, all migration examples and tooling are PowerShell-based, and instructions reference Windows tabs and patterns first. 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 using Bash, Python, or Azure CLI to support Linux/macOS users.
  • Clarify whether PowerShell Core (cross-platform) is supported and provide instructions for installation/use on Linux/macOS.
  • Add tabs or sections for Linux/macOS users in all step-by-step instructions, especially where 'windows' tabs are referenced.
  • Explicitly mention any limitations or requirements for Linux users, such as PowerShell module compatibility.
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 is heavily focused on PowerShell and Windows-centric tooling, with all examples and instructions using PowerShell modules and cmdlets. There are no references to Bash, Azure CLI, or Linux/macOS scripting environments. The credential management and runbook examples are exclusively PowerShell-based, and the use of Windows PowerShell is explicitly mentioned. This creates friction for Linux/macOS users who may prefer or require Bash or Azure CLI workflows.
Recommendations
  • Add equivalent Azure CLI and Bash examples for credential asset creation and runbook authentication.
  • Clarify which steps are platform-agnostic and which are Windows/PowerShell-specific.
  • Include guidance for Linux/macOS users on how to interact with Azure Automation and Microsoft Entra ID using non-PowerShell tools.
  • Mention cross-platform alternatives (e.g., Azure CLI, REST API) where possible.
  • Rephrase sections to avoid implying PowerShell is the only supported or recommended approach unless that is truly the case.
GitHub Create Pull Request
Automation Manage credentials in Azure Automation ...in/articles/automation/shared-resources/credentials.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page for managing credentials in Azure Automation is heavily focused on PowerShell and Windows-centric tooling. All CLI examples are in PowerShell, and Windows PowerShell is explicitly referenced as the method for creating credential assets outside the portal. There are no Bash, Linux shell, or cross-platform CLI examples. The Python section is present, but only for runbooks, not for asset management. Windows/PowerShell tools and patterns are mentioned first and exclusively for asset management tasks.
Recommendations
  • Add Azure CLI examples for credential asset management, if supported.
  • Clarify whether credential management can be performed via REST API or Azure CLI, and provide examples.
  • Explicitly state if PowerShell is the only supported method for credential asset management, to set expectations for Linux/macOS users.
  • If possible, provide guidance for Linux/macOS users on installing and using PowerShell Core cross-platform.
  • Include a note about platform support and limitations for credential management tasks.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides a general overview of Azure Change Tracking and Inventory, which supports both Windows and Linux. However, there is a notable Windows bias: registry key tracking is described in detail with a large table of Windows registry keys, while there is no equivalent section or examples for Linux configuration tracking (such as monitoring changes to /etc files or systemd units). Windows terminology and features (registry, Internet Explorer, explorer.exe) are explained, but Linux-specific tools, files, or configuration patterns are not mentioned. Most examples and screenshots are either generic or Windows-centric, and Windows features are described before Linux equivalents.
Recommendations
  • Add a section detailing what Linux configuration elements can be tracked (e.g., /etc/passwd, /etc/ssh/sshd_config, systemd service files) and provide examples.
  • Include a table or list of commonly monitored Linux files or directories, similar to the Windows registry key table.
  • Clarify in each feature section (e.g., file content tracking, inventory) how the feature applies to Linux systems, with explicit examples.
  • Ensure screenshots and walkthroughs alternate between Windows and Linux, or show both where possible.
  • Mention Linux-specific terminology and tools where relevant (e.g., daemons, config files, package managers).
GitHub Create Pull Request
Azure Netapp Files Azure NetApp Files for Azure Government ...b/main/articles/azure-netapp-files/azure-government.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides access instructions for Azure NetApp Files in Azure Government via the Portal, Azure CLI, REST API, and PowerShell. While the Azure CLI and REST API sections are platform-neutral, the PowerShell section is detailed and prominent, listing multiple PowerShell connection types and commands. There is no equivalent section for Linux/macOS shell scripting (e.g., Bash), nor are Linux-specific tools or workflows mentioned. The PowerShell section appears after CLI but is more extensive, and the 'Next steps' links include a PowerShell-specific REST API guide, suggesting a slight Windows/PowerShell bias.
Recommendations
  • Add explicit Bash or shell scripting examples for connecting to Azure Government and managing Azure NetApp Files, especially for REST API usage.
  • Clarify that Azure CLI is cross-platform and provide sample Bash scripts for common operations.
  • Balance the PowerShell section with equivalent Linux/macOS guidance, or note that PowerShell Core is available cross-platform.
  • Include links to Linux/macOS-specific documentation or troubleshooting guides.
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 ⚠️ windows_tools
Summary
The documentation provides both Linux and Windows migration paths, but Windows/PowerShell/Azure CLI examples and instructions are often presented first or in greater detail. Windows-specific tools and patterns (such as Azure CLI commands, PowerShell scripts, and portal workflows) are frequently used as the default, with Linux alternatives sometimes relegated to pivots or notes. Some advanced automation (e.g., az functionapp flex-migration) is currently Linux-only, but the overall structure and example order favor Windows users.
Recommendations
  • Ensure Linux examples and instructions are presented with equal prominence and detail as Windows examples, especially in step-by-step guides.
  • Where Windows tools/scripts are shown, provide equivalent Linux shell commands (bash/zsh) and clarify any platform-specific differences.
  • Avoid presenting Windows/PowerShell examples before Linux equivalents unless there is a technical reason (e.g., feature availability).
  • Expand Linux-specific automation and tooling coverage, and clearly indicate when features are Linux-only.
  • Review all CLI and portal instructions to ensure parity in detail, troubleshooting, and edge-case handling for Linux users.
GitHub Create Pull Request
Azure Netapp Files Create volume replication for Azure NetApp Files ...etapp-files/cross-region-replication-create-peering.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 Azure PowerShell examples first and in detail for feature registration and status checking, with only a brief mention that Azure CLI commands can also be used. The step-by-step instructions and code blocks are PowerShell-centric, which may create friction for Linux/macOS users who typically use Azure CLI. There are no explicit Linux/macOS examples or screenshots, and the workflow assumes use of the Azure portal or PowerShell.
Recommendations
  • Provide full Azure CLI command examples alongside PowerShell for feature registration and status checking.
  • Include explicit instructions and screenshots for using the Azure portal on non-Windows platforms, if relevant.
  • Ensure that all command-line steps are presented in both PowerShell and CLI formats, with equal prominence.
  • Consider a section or callout for Linux/macOS users, clarifying any platform-specific considerations.
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 page provides several PowerShell command examples (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without equivalent Azure CLI or Bash alternatives in those sections. While some Azure CLI examples are present (notably for az group create, az deployment group create, and a Bash script for az acr import), key preparatory and integration steps are shown only with PowerShell. Additionally, PowerShell commands are often mentioned first or exclusively, and there is no explicit guidance for Linux/macOS users for those steps.
Recommendations
  • For every PowerShell example (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster), provide equivalent Azure CLI and/or Bash examples, or clearly indicate if a CLI alternative does not exist.
  • When listing commands or tools, present Azure CLI (cross-platform) examples before PowerShell, or show both side-by-side.
  • Explicitly state OS-agnostic approaches where possible, and clarify any steps that are Windows-only.
  • Ensure all critical workflow steps can be completed using cross-platform tools.
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 Azure Firewall relocation using the Azure Portal and Azure PowerShell, but does not offer equivalent examples or guidance for Linux/macOS users who would typically use Azure CLI or Bash. All command-line examples are PowerShell-centric, and references to scripting or automation are exclusively in PowerShell syntax, which may create friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations, including template export, modification, and deployment.
  • Explicitly mention that Azure CLI and Bash can be used on Linux/macOS and provide links to relevant Azure CLI documentation.
  • Ensure that any references to scripts or automation include cross-platform options (e.g., Bash scripts, Azure CLI commands).
  • Where PowerShell is referenced for policy migration or deployment, provide Azure CLI alternatives or note any limitations.
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 describes the Azure VM restore process in a generally OS-agnostic manner, but there is notable bias in the 'Restore an encrypted VM' scenario. This section exclusively references Windows VM encryption and restoration, mentioning PowerShell as the required tool and linking only to Windows-specific guides. There are no Linux VM encryption restore examples or references to Linux tooling (such as Bash or CLI). Additionally, the encrypted VM restore scenario is presented before any mention of Linux equivalents, which are absent.
Recommendations
  • Add guidance and examples for restoring encrypted Linux VMs, including references to Azure Disk Encryption for Linux and relevant restore procedures.
  • Include Linux-specific tooling (such as Bash, Azure CLI, or other Linux-native commands) alongside PowerShell where applicable.
  • Clarify in the encrypted VM restore section whether the instructions are Windows-only, and provide parity for Linux users if supported.
  • Ensure that restore scenarios and examples are balanced between Windows and Linux, or clearly indicate OS-specific limitations.
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 frequently references Azure portal and PowerShell as primary methods for exporting and deploying templates, with no explicit Linux/macOS CLI examples. Infrastructure as Code (IAC) tools are mentioned, but PowerShell is listed alongside Azure CLI without clear parity or ordering. Screenshots and step-by-step instructions focus on the Azure portal, which may be less accessible for Linux users. There are no bash or Linux-specific CLI examples for key steps such as exporting templates or deploying resources.
Recommendations
  • Add explicit Azure CLI (bash) examples for exporting and deploying templates, especially for steps currently shown only via portal or PowerShell.
  • Clarify that all steps can be performed using Azure CLI on Linux/macOS, and provide sample commands.
  • Where screenshots are used, consider adding CLI output or command snippets for parity.
  • List Azure CLI examples before or alongside PowerShell to avoid Windows-first ordering.
  • Mention cross-platform tools (e.g., Terraform, Bicep) where applicable, and provide links or examples.
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 for Azure Backup architecture is notably Windows-centric in its coverage of on-premises backup scenarios. It exclusively describes backup methods for on-premises Windows machines (using the MARS agent and DPM/MABS), with explicit statements that Linux machines aren't supported for direct backup to Azure. There are no Linux examples or equivalent Linux backup tools mentioned for on-premises scenarios, and Windows tools (MARS, DPM, MABS) are referenced throughout, often without Linux alternatives or parity. While Azure VM backup is platform-agnostic, the documentation does not clarify Linux support or provide Linux-specific guidance for on-premises backup.
Recommendations
  • Clearly state the limitations for Linux on-premises backup upfront, and provide links to alternative solutions or third-party tools for Linux backup to Azure if available.
  • Add a dedicated section or callout for Linux users, explaining supported scenarios (e.g., Azure VM backup for Linux VMs) and any workarounds or best practices for Linux data protection.
  • Where possible, mention parity or differences in backup features for Linux VMs versus Windows VMs, especially in tables and feature comparisons.
  • Ensure future documentation updates include Linux-specific examples or guidance when new features or agents support Linux.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ powershell_heavy
Summary
The documentation provides general guidance for restoring Azure VMs using the portal, but there is a notable Windows bias in example links, terminology, and guidance. Windows/PowerShell examples are referenced before or instead of Linux equivalents, and links to Windows-specific documentation are more prevalent. Linux-specific restore scenarios, troubleshooting, and automation are underrepresented, and PowerShell is often suggested as the automation method without mentioning Azure CLI or Bash alternatives.
Recommendations
  • Include explicit Linux VM restore examples and links (e.g., how to attach restored disks to Linux VMs, how to reset SSH keys/passwords using Linux tools).
  • When referencing automation, provide Azure CLI and Bash examples alongside PowerShell, especially in sections like 'Restore disks', 'Restore VMs with special configurations', and 'Post-restore steps'.
  • Balance links to Windows and Linux documentation (e.g., when linking to disk attachment, availability sets, and troubleshooting guides).
  • Clarify when guidance applies equally to both Windows and Linux, and call out Linux-specific considerations (e.g., cloud-init password reset, SSH key usage, VM agent installation on Linux).
  • Add troubleshooting steps for common Linux restore issues (e.g., boot problems, agent installation, SSH access).
GitHub Create Pull Request
Backup Selective Disk Backup and Restore for Azure Virtual Machines .../main/articles/backup/selective-disk-backup-restore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring selective disk backup and restore for Azure VMs. However, PowerShell is given a dedicated section with detailed, step-by-step examples, which may be perceived as Windows-centric since PowerShell is most commonly used on Windows. The CLI examples are cross-platform, but PowerShell is presented as an equal or primary automation method, which can create friction for Linux/macOS users. Additionally, PowerShell is mentioned before REST API and after CLI, reinforcing its prominence. There are no Linux-specific CLI examples or shell scripts, and no explicit mention of Bash or Linux-native tooling for automation, aside from a few notes about required Linux utilities (lsblk, lsscsi).
Recommendations
  • Clarify that Azure CLI is fully cross-platform and suitable for Linux/macOS users, and consider presenting CLI examples before PowerShell.
  • Add explicit Bash/shell script examples for common operations to improve accessibility for Linux/macOS users.
  • Where PowerShell is referenced, note that it is available cross-platform, but CLI is typically preferred on Linux/macOS.
  • Add a short section or callout for Linux/macOS users, summarizing recommended tools and approaches.
  • Ensure parity in troubleshooting and advanced scenarios (e.g., error handling, scripting) for Linux/macOS users.
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 a comprehensive support matrix for Azure VM backups, covering both Windows and Linux. However, there is a noticeable Windows bias: Windows scenarios and tools (such as PowerShell and MARS agent) are often mentioned first or exclusively, with Linux support described separately and sometimes as 'not supported' for key features (e.g., MARS agent, DPM/MABS). Restore instructions and examples frequently reference PowerShell and Windows-centric workflows, while equivalent Linux CLI or automation examples are missing. Some advanced backup/restore features and file-level restore capabilities are more robust for Windows than Linux, with Linux users encountering more limitations and fewer step-by-step guides.
Recommendations
  • Provide Linux CLI (az CLI, Bash) examples alongside PowerShell for restore and backup operations.
  • Where features are Windows-only (e.g., MARS agent, DPM/MABS), clarify alternatives or workarounds for Linux users.
  • Ensure that restore workflows and file-level restore instructions include Linux-specific guidance and troubleshooting.
  • List Linux support and examples before or alongside Windows in tables and documentation sections where parity exists.
  • Expand documentation on custom script usage for app-consistent Linux backups, including sample scripts and best practices.
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. PowerShell is referenced as the primary automation method for creating a VM from restored disks, with no equivalent CLI or Linux-native example. The OS disk swap example links only to Windows documentation. Linux-specific restore steps are brief and lack detailed guidance or examples, while Windows-related actions and references appear first or exclusively.
Recommendations
  • Provide Azure CLI or Bash examples for creating a VM from restored disks, alongside PowerShell.
  • Include a link or section for swapping OS disks on Linux VMs, not just Windows.
  • Expand the Linux restore section with step-by-step instructions and code samples (e.g., reinstalling ADE extension, mounting disks).
  • Ensure Linux and Windows examples are presented with equal detail and prominence.
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 deployment methods using PowerShell and Visual Studio, which are primarily Windows-centric tools, and lists them before mentioning more cross-platform options like ARM templates and the Azure Portal. There are no explicit Linux/macOS CLI examples or mentions of Azure CLI or Bash scripting, which are common on non-Windows platforms. This creates a subtle bias toward Windows users, though the core service itself is not Windows-only.
Recommendations
  • Add explicit examples and links for deploying Cloud Services (extended support) using Azure CLI and Bash scripts, which are cross-platform.
  • Clarify that ARM templates can be deployed using Azure CLI or other cross-platform tools, not just PowerShell.
  • Reorder deployment method lists to start with platform-neutral options (ARM template, Azure Portal, Azure CLI) before Windows-specific tools (PowerShell, Visual Studio).
  • Provide guidance or links for Linux/macOS users on how to perform common tasks (deployment, migration) using their preferred tools.
GitHub Create Pull Request
Data Share Tutorial: Share outside your org - Azure Data Share ...-docs/blob/main/articles/data-share/share-your-data.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides examples for Azure Portal, Azure CLI, and PowerShell. While Azure CLI is cross-platform, the PowerShell examples and instructions are Windows-centric, including references to local file paths (e.g., 'D:\testFiles') and PowerShell-specific guides. There is no mention of Linux/macOS equivalents for file upload or shell usage, and PowerShell is presented as a primary automation option alongside CLI, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
  • Add explicit Bash shell examples for common tasks such as uploading files to Azure Storage, using azcopy or Azure CLI from Bash.
  • Clarify that Azure CLI commands work on Linux/macOS and provide sample commands using Unix-style file paths (e.g., '/home/user/testFiles/textfile.csv').
  • Where PowerShell is referenced, note that PowerShell Core is available cross-platform, and provide instructions or examples for installing and using it on Linux/macOS.
  • Avoid using Windows-style file paths in generic examples, or provide both Windows and Unix-style path examples.
  • Link to cross-platform guides for Azure Cloud Shell, emphasizing its availability from any OS.
GitHub Create Pull Request
Data Share Tutorial: Accept & receive data - Azure Data Share ...ob/main/articles/data-share/subscribe-to-data-share.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 step-by-step instructions for using the Azure Portal, Azure CLI, and PowerShell to accept and receive data via Azure Data Share. While Azure CLI is cross-platform and examples are provided, PowerShell examples are given equal prominence and detail, including local file paths and Windows-centric usage patterns (e.g., referencing 'D:\testFiles'). There are no explicit Linux/macOS shell examples (e.g., Bash scripts for file upload), and PowerShell-specific instructions (including local execution) may confuse Linux/macOS users. The ordering of examples sometimes places PowerShell before CLI, and file path examples are Windows-centric.
Recommendations
  • Add explicit Bash/shell examples for file upload and storage operations, especially for steps currently showing only PowerShell with Windows file paths.
  • Clarify that PowerShell commands can be run in Azure Cloud Shell (which is cross-platform), but provide alternative Bash/CLI instructions for local execution on Linux/macOS.
  • Avoid using Windows-specific file paths (e.g., 'D:\testFiles') in generic examples; use platform-neutral or Azure Cloud Shell paths.
  • Ensure CLI examples are shown first or equally, and highlight their cross-platform compatibility.
  • Add notes or links for Linux/macOS users on how to perform equivalent tasks (e.g., uploading files to Azure Storage using az CLI or azcopy).
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 examples for Linux-based DNS servers (such as BIND or dnsmasq). Windows DNS is presented as the default/primary example for on-premises integration, and there are no instructions or references for Linux equivalents.
Recommendations
  • Add a section or example for configuring conditional forwarders on popular Linux DNS servers (e.g., BIND, dnsmasq, Unbound).
  • Include screenshots or configuration file snippets for Linux DNS server setups.
  • Explicitly mention that the procedure applies to both Windows and Linux DNS servers, and link to relevant external documentation for Linux DNS configuration if full instructions are out of scope.
  • Where possible, present both Windows and Linux examples side-by-side, or clarify when steps are OS-specific.
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 for ExpressRoute virtual network gateways demonstrates a moderate Windows bias. PowerShell is the only example shown for gateway subnet creation, with no Azure CLI or ARM template equivalents provided. References to PowerShell and REST APIs are present, but Linux/macOS-friendly CLI examples and tooling are not mentioned or linked. This could create friction for users on non-Windows platforms who prefer or require cross-platform command-line tools.
Recommendations
  • Add equivalent Azure CLI examples alongside PowerShell for all resource creation/configuration steps.
  • Explicitly mention that Azure CLI can be used from Linux/macOS and provide links to CLI documentation.
  • Where PowerShell cmdlets are referenced, also reference Azure CLI commands and ARM template options.
  • Ensure screenshots and walkthroughs are not Windows-centric (e.g., avoid showing only Windows PowerShell terminals).
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias by presenting Windows/PowerShell examples and tools (psping.exe) before Linux equivalents. The primary troubleshooting commands use Windows-specific tools and syntax, with Linux alternatives mentioned only briefly and without equivalent detail. The use of Windows tools like psping.exe and references to tcpping.exe further reinforce the Windows-centric approach.
Recommendations
  • Provide Linux/macOS examples alongside Windows examples, ensuring parity in detail and explanation.
  • List Linux/macOS commands (e.g., 'telnet', 'nc', 'curl', or 'openssl') before or alongside Windows commands, not after.
  • Include download or installation instructions for Linux troubleshooting tools (e.g., how to install 'telnet', 'nc', or 'tcping' on Linux).
  • Offer troubleshooting steps using cross-platform tools (e.g., Wireshark, curl) with example commands for both Windows and Linux/macOS.
  • Avoid using Windows-only tools (like psping.exe) as the primary example; instead, use platform-neutral or widely available 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 page for configuring an outbound-only load balancer in Azure provides step-by-step instructions using the Azure portal, but when it comes to VM creation and connectivity testing, it exclusively references Windows Server (specifically Windows Server 2022 Datacenter) and Windows tools (Microsoft Edge browser). There are no examples or guidance for deploying or testing with Linux VMs, nor are Linux-specific tools or patterns mentioned.
Recommendations
  • Include instructions for creating a Linux VM (e.g., Ubuntu) alongside the Windows VM example, or clarify that the process is identical for Linux.
  • Provide guidance for connectivity testing on Linux VMs, such as using Firefox, Chrome, or command-line tools like curl or wget to verify outbound connectivity.
  • Explicitly state that the load balancer configuration applies to both Windows and Linux VMs, and note any differences if applicable.
  • Where possible, show both Windows and Linux examples in parallel, especially in sections involving VM creation and connectivity testing.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation provides step-by-step instructions for creating a public load balancer in Azure using the portal, but when configuring the backend VMs, it exclusively demonstrates installing IIS using Windows PowerShell commands. There are no equivalent instructions or examples for Linux VMs (e.g., installing Apache or Nginx), nor are Linux command-line examples provided. The use of Windows PowerShell and IIS is presented as the default, with no mention of Linux alternatives.
Recommendations
  • Add a parallel section demonstrating how to install a web server (such as Apache or Nginx) on Linux VMs, including relevant Bash commands.
  • Explicitly state that the backend VMs can be either Windows or Linux, and provide guidance for both.
  • When showing code examples, present both Windows and Linux commands side-by-side or indicate which OS each applies to.
  • Consider using a more platform-neutral test workload (e.g., a simple HTML file served by any web server) to illustrate load balancing.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides detailed instructions for moving Azure Load Balancers between regions using the Azure portal and Azure PowerShell. All CLI-based examples and automation steps use Azure PowerShell cmdlets, which are primarily Windows-centric and require PowerShell. There are no examples or guidance for using Azure CLI (az), which is cross-platform and preferred by many Linux/macOS users. Additionally, instructions for editing exported templates reference Windows tools (e.g., notepad.exe) and PowerShell-specific workflows, with no mention of Linux/macOS equivalents or editors.
Recommendations
  • Add parallel instructions and examples using Azure CLI (az) for all steps currently covered with Azure PowerShell.
  • Reference cross-platform text editors (e.g., vim, nano, VS Code) when instructing users to edit JSON files, or use generic language like 'open in a text editor'.
  • Explicitly note that both Azure PowerShell and Azure CLI can be used for resource export, deployment, and verification, and link to relevant Azure CLI documentation.
  • Consider providing a comparison table or guidance on choosing between Azure PowerShell and Azure CLI based on OS/platform.
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 documentation provides only Windows VM creation instructions and exclusively uses Windows PowerShell commands to install and configure IIS on the backend VMs. There are no examples or guidance for deploying Linux VMs, nor are Linux equivalents (such as Apache or Nginx) mentioned or demonstrated. The tutorial assumes Windows as the default platform for backend pool members and web server configuration.
Recommendations
  • Add parallel instructions for creating Linux VMs (e.g., Ubuntu) in the backend pool.
  • Provide Linux-specific examples for installing and configuring a web server (such as Apache or Nginx), including sample shell commands.
  • Include both Windows and Linux options in the VM creation steps, making it clear that either OS can be used.
  • Present PowerShell and Bash/CLI examples side-by-side where relevant.
  • Clarify that IIS is only required if using Windows VMs; suggest alternatives for Linux users.
GitHub Create Pull Request
Logic Apps Examples & common scenarios ...ticles/logic-apps/logic-apps-examples-and-scenarios.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 Logic Apps 'Examples & common scenarios' includes references to running PowerShell scripts from workflows and mentions PowerShell as a supported language for custom code. However, there is no mention of Linux shell scripting (e.g., Bash) or other Linux-native tools. Additionally, examples and tutorials do not provide parity for Linux/macOS users in terms of scripting or automation options, focusing primarily on Microsoft-centric technologies (PowerShell, .NET, C#).
Recommendations
  • Add examples and documentation for running Bash scripts or other Linux shell scripts from Logic Apps workflows.
  • Explicitly mention cross-platform scripting options and clarify any OS-specific limitations for script actions.
  • Where PowerShell is referenced, also provide equivalent Linux/macOS alternatives if supported (e.g., Bash, Python).
  • Ensure tutorials and walkthroughs include steps for Linux/macOS environments, especially for automation and deployment scenarios.
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 occasionally demonstrates Windows bias, primarily in the tools and examples referenced for Azure Function creation and management. PowerShell and Visual Studio are mentioned alongside cross-platform options, but Windows-centric tools are listed before Linux/macOS alternatives. The guide for finding tenant IDs explicitly references PowerShell, with no Linux/macOS CLI alternative provided. The use of Kudu's CMD console is also more familiar to Windows users, though it is accessible via the portal for all platforms.
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 equivalents for PowerShell commands, especially for tasks like finding tenant IDs, to ensure Linux/macOS users have clear instructions.
  • Clarify that Kudu's debug console is accessible from any OS via the browser, and optionally mention Bash as an alternative to CMD for users more familiar with Unix shells.
  • Review screenshots and instructions to ensure they do not assume a Windows environment where not necessary.
GitHub Create Pull Request
Azure Government Azure guidance for secure isolation ...es/azure-government/azure-secure-isolation-guidance.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation is generally cross-platform and covers both Windows and Linux scenarios for Azure isolation. However, there is a mild Windows bias in several areas: Windows terminology and technologies (e.g., Hyper-V, Windows Firewall, BitLocker, Windows Server) are mentioned first or exclusively in some technical explanations, and PowerShell is referenced as a primary management tool before Azure CLI. Some examples and technical details (especially in compute isolation and disk encryption) are described with a Windows-first perspective, even when Linux equivalents exist and are supported.
Recommendations
  • Ensure Linux tools and patterns (e.g., Azure CLI, SSH, DM-Crypt) are mentioned alongside or before Windows/PowerShell equivalents where both are supported.
  • When describing technical architecture (e.g., firewalls, disk encryption), provide equal detail for Linux technologies (e.g., iptables, DM-Crypt) as for Windows ones.
  • In management instructions, alternate or parallelize examples for Azure CLI and PowerShell, and clarify when both are supported.
  • Review sections that reference Windows-specific technologies (e.g., Hyper-V, Windows Firewall) to ensure Linux equivalents (e.g., KVM, iptables) are referenced where applicable, or clarify if the underlying platform is Windows-only.
  • Where examples or links are provided for VM provisioning, disk encryption, or remote access, ensure Linux scenarios are equally represented and not relegated to secondary mentions.
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 page is focused on migrating from BizTalk Server (a Windows-only product) to Azure Logic Apps. While the overall content is appropriately Windows-centric due to BizTalk's nature, there are several instances where Windows tools (such as MMC snap-ins, PowerShell, and Windows registry) are referenced as default or primary options, sometimes without mentioning Linux/macOS alternatives or parity. Examples and tool references (e.g., BizTalk Administration Console, BizTalk Health Monitor, PowerShell for deployment) are Windows-specific and appear before any mention of cross-platform or Linux-native tools. However, Azure Logic Apps and related Azure services are described as cross-platform, and the documentation does not prevent Linux/macOS users from completing migration or using Azure services.
Recommendations
  • Where possible, clarify which management and deployment tasks for Azure Logic Apps can be performed using cross-platform tools (e.g., Azure CLI, Bash scripts) in addition to PowerShell.
  • When referencing developer experiences, highlight Visual Studio Code and Azure portal as cross-platform options before mentioning Windows-only tools.
  • For monitoring and operations, mention Azure Monitor, Application Insights, and other web-based or cross-platform tools before or alongside Windows-only tools.
  • Explicitly state when a tool or feature is Windows-only and suggest alternatives for Linux/macOS users if available.
  • In deployment sections, provide examples using both PowerShell and Azure CLI/Bash where applicable.
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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides instructions for both Linux/macOS and Windows users when connecting via SSH, but Windows/PowerShell is mentioned first and the SSH example uses Windows path notation ('.\Downloads\lb-key-pair.pem'). There are no Linux-specific tools or patterns missing, but the ordering and example syntax favor Windows users slightly.
Recommendations
  • Present Linux/macOS and Windows instructions in parallel or alternate which is shown first.
  • Provide SSH command examples with both Linux/macOS and Windows path syntax, e.g., '~/Downloads/lb-key-pair.pem' for Linux/macOS.
  • Clarify that the SSH command works on all platforms and adjust the example to be platform-neutral if possible.
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 demonstrates mild Windows bias by referencing Azure PowerShell cmdlets (set-azapimanagement) alongside Azure CLI and REST API for managing regional gateways, and by listing PowerShell before Linux-friendly tools. However, the majority of operational instructions are platform-agnostic, focusing on the Azure portal, Azure CLI, and REST API, which are cross-platform. No critical steps are Windows-only, but the inclusion and ordering of PowerShell examples may cause minor friction for Linux/macOS users.
Recommendations
  • When listing command-line options, mention Azure CLI and REST API before PowerShell, as these are cross-platform.
  • Provide explicit Bash/Linux/macOS shell examples where command-line usage is shown, especially for Azure CLI.
  • Clarify that PowerShell is optional and provide links to installation guides for non-Windows platforms if referenced.
  • Where possible, avoid listing Windows-specific tools unless there is unique functionality unavailable elsewhere.
GitHub Create Pull Request
Azure Cache For Redis Azure Cache for Redis with Azure Private Link ...n/articles/azure-cache-for-redis/cache-private-link.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for managing private endpoints, but PowerShell examples are presented first and in greater detail. The CLI examples are present and sufficient for Linux/macOS users, but the ordering and emphasis may create minor friction for non-Windows users. The rest of the documentation is Azure portal-focused and platform-neutral.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid implicit prioritization of Windows tooling.
  • Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Ensure parity in example detail and explanation between PowerShell and CLI sections.
  • Consider adding a short note at the top of scripting sections clarifying platform compatibility.
GitHub Create Pull Request
Azure Functions Guide for running C# Azure Functions in an isolated worker process ...icles/azure-functions/dotnet-isolated-process-guide.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides both Windows and Linux guidance for running C# Azure Functions in an isolated worker process. However, there are several instances where Windows tools, patterns, or commands are mentioned before their Linux equivalents, and Windows-specific instructions are sometimes more detailed or presented first. For example, ReadyToRun instructions and CLI commands for checking/changing bitness are shown with Windows examples first, and PowerShell is listed as a deployment option before ARM templates and the Azure portal. While Linux equivalents are present and the guide is broadly cross-platform, the ordering and emphasis may create minor friction for Linux/macOS users.
Recommendations
  • Ensure that Linux and macOS examples are presented with equal prominence and ordering as Windows examples, especially in sections about deployment, configuration, and performance optimizations.
  • When listing tools or methods (e.g., Azure CLI, PowerShell, Visual Studio), alternate or group by platform rather than listing Windows-first.
  • Add explicit Linux/macOS command-line examples where only Windows commands are shown, and clarify any platform-specific differences.
  • Review the ordering of instructions in tables and lists to avoid implicit prioritization of Windows tools or workflows.
  • Where possible, provide parity in detail and troubleshooting steps for both platforms.
GitHub Create Pull Request
Azure Functions App settings reference for Azure Functions ...ain/articles/azure-functions/functions-app-settings.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides a comprehensive reference for Azure Functions app settings, covering both Windows and Linux scenarios. However, there are minor signs of Windows bias: some examples and explanations mention Windows first or exclusively (e.g., environment variable delimiters, sample paths), and Windows tools (Azure PowerShell) are mentioned before Linux equivalents (Azure CLI). Most settings are OS-agnostic, and Linux-specific settings (like linuxFxVersion) are documented, but Windows is sometimes presented as the default or primary platform.
Recommendations
  • Ensure that examples and explanations consistently mention both Windows and Linux/macOS scenarios, especially for environment variables, file paths, and delimiters.
  • When referencing tools for managing app settings, mention Azure CLI before or alongside Azure PowerShell, as CLI is cross-platform.
  • Where sample values use Windows-style paths (e.g., %HOME%\typescript), provide Linux/macOS equivalents (e.g., $HOME/typescript).
  • For settings that behave differently on Windows and Linux (such as delimiters), clarify the differences in a balanced way and provide explicit Linux/macOS examples.
  • Review the ordering of OS-specific settings and ensure Linux/macOS settings are not relegated to secondary status.
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_first
Summary
The documentation is generally cross-platform, but exhibits minor Windows bias in a few areas. The 'managedDependency' feature is described as PowerShell-only (which is accurate), but the explanation and links are Windows-centric. Some settings (e.g., Application Insights snapshot configuration) reference Windows environment variables (LOCALAPPDATA, APPDATA, TEMP) before mentioning Linux equivalents or alternatives. The use of timespan strings refers to .NET conventions, which are familiar to Windows users but may be less so for Linux/macOS users. Console logging settings mention Linux, but only in the context of disabling ANSI colors. Overall, Linux/macOS users can complete all tasks, but may encounter minor friction due to Windows-first terminology and examples.
Recommendations
  • Where environment variables or folder paths are mentioned (e.g., for tempFolder, shadowCopyFolder), explicitly note Linux/macOS equivalents (such as $HOME, /tmp) and clarify cross-platform behavior.
  • For managedDependency, clarify that PowerShell support is available on both Windows and Linux hosts, and link to Linux-specific guidance if available.
  • When referencing .NET conventions (e.g., timespan string format), provide a brief explanation or example for non-Windows users unfamiliar with .NET.
  • Ensure that any references to file paths, environment variables, or tooling include both Windows and Linux/macOS formats where applicable.
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, but there are some instances of Windows bias. In the 'Mount file shares' section, both Azure CLI (Linux-focused) and Azure PowerShell (Windows-focused) examples are provided, but PowerShell is shown second. Elsewhere, references to Consumption plan sometimes specify 'Windows only' before mentioning Linux, and PowerShell-specific features (like managed dependencies) are called out in Azure Files usage. However, Linux-specific guidance is present, and most examples and instructions are platform-neutral.
Recommendations
  • Ensure that Linux and macOS examples are presented with equal prominence and order as Windows/PowerShell examples.
  • When mentioning features or settings that differ by OS (e.g., Consumption plan on Windows vs. Linux), clarify parity and provide explicit Linux/macOS instructions where possible.
  • Expand on Linux-specific deployment and configuration scenarios, especially where Azure Files or storage connection settings differ.
  • Where PowerShell is referenced, also provide Bash or Azure CLI equivalents if applicable.
GitHub Create Pull Request
Azure Functions Deployment technologies in Azure Functions ...s/azure-functions/functions-deployment-technologies.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation generally presents deployment methods and tools in a cross-platform manner, but there are subtle biases: Windows-based tools (Visual Studio, Visual Studio Code) are often mentioned before Linux/CLI options, and some explanations (such as remote build) discuss Windows scenarios first. However, Linux deployment options and caveats are well-covered, and Linux-specific guidance is present throughout.
Recommendations
  • When listing deployment tools, alternate or randomize the order, or explicitly state that all tools are cross-platform where applicable.
  • Provide explicit Linux/macOS command-line examples alongside or before Windows/Visual Studio examples, especially in sections discussing deployment from development tools.
  • Clarify in tool-based deployment sections that Visual Studio Code and Azure Functions Core Tools are fully supported on Linux/macOS.
  • Where possible, include bash or shell script examples in addition to Azure CLI and PowerShell.
  • Highlight any Linux/macOS-specific caveats or best practices in the same prominence as Windows notes.
GitHub Create Pull Request
Azure Resource Manager Bicep functions - resources ...ure-resource-manager/bicep/bicep-functions-resource.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 for Bicep resource functions is generally platform-neutral, focusing on Bicep syntax and Azure REST APIs. However, in the section about discovering 'list*' operations, it mentions the Windows PowerShell cmdlet (Get-AzProviderOperation) before the Azure CLI equivalent, and provides a PowerShell example before the Azure CLI example. This ordering and inclusion of Windows-specific tooling can create minor friction for Linux/macOS users, though the Azure CLI example is present and the rest of the page is not Windows-centric.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform.
  • Explicitly note that Azure CLI works on Linux/macOS and is recommended for cross-platform use.
  • Where possible, avoid referring to Windows-specific tools or cmdlets unless there is no cross-platform alternative.
  • Consider adding a short note that Bicep and its resource functions are platform-agnostic and can be used from any OS with Azure CLI or Bicep CLI installed.
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 PowerShell and Azure CLI examples for discovering list operations, but the PowerShell example is presented first. No other Windows-specific tools, patterns, or examples are present, and all code samples are platform-neutral (ARM template JSON). The page does not omit Linux equivalents, nor does it use Windows-only tools for critical tasks.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid implicit Windows-first ordering.
  • Explicitly note that both Azure CLI and PowerShell are cross-platform and provide links to installation guides for both.
  • Where possible, add Bash or shell scripting context for CLI commands to reinforce Linux parity.
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 some minor signs of Windows bias: Windows-specific tools (VSS, DPM, MABS, MARS Agent) are referenced without Linux equivalents, and the VSS (Windows Volume Shadow Copy Service) is mentioned before Linux alternatives in the 'Application consistent backup' entry. However, Linux is acknowledged in some places (e.g., mentioning pre/post scripts for Linux in backups), and most definitions are platform-agnostic.
Recommendations
  • Where Windows-specific backup technologies (e.g., VSS) are mentioned, explicitly note Linux alternatives or clarify when Linux uses different mechanisms.
  • For entries like 'Application consistent backup', provide a brief example or link for Linux backup consistency methods (e.g., fsfreeze, custom scripts).
  • Add references to Linux backup tools or patterns where relevant (e.g., mention Azure Backup support for Linux VMs and how consistency is achieved).
  • Ensure glossary entries for backup agents/tools (MARS, DPM, MABS) clarify their platform support and mention Linux equivalents or alternatives if available.
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. Keyboard layout configuration instructions are Windows-specific, with no guidance for Linux or macOS users. No Linux/macOS-specific examples or instructions are provided for tasks like keyboard layout changes or file transfer, despite Bastion supporting SSH (commonly used on Linux/macOS).
Recommendations
  • Add instructions for configuring keyboard layouts on Linux and macOS systems alongside the Windows steps.
  • When listing supported browsers, mention Linux explicitly and provide recommendations for Linux users (e.g., Chrome, Firefox).
  • For file transfer, clarify SSH client compatibility on Linux/macOS and provide example workflows for those platforms.
  • Ensure parity in examples and instructions for common cross-platform tasks, especially where SSH is involved.
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 HTTP requests, but PowerShell examples are consistently presented first in each tabbed section. This ordering may subtly prioritize Windows users. There are no Linux-specific tools or patterns mentioned, but curl is a cross-platform tool, and all Azure CLI commands are platform-neutral. No critical functionality is missing for Linux/macOS users.
Recommendations
  • Present curl examples before PowerShell, or alternate the order to avoid implicit prioritization.
  • Explicitly note that curl commands work on Linux/macOS and Windows (with curl installed), and PowerShell is primarily for Windows users.
  • Consider adding bash examples for common tasks, if relevant.
  • Clarify that all Azure CLI commands work on Linux, macOS, and Windows.
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, ensuring cross-platform coverage. However, PowerShell examples are consistently included and sometimes shown before or alongside Bash, which may create a slight Windows-first impression. There are no Linux-specific tools or patterns missing, and all instructions are compatible with Linux/macOS environments. No critical steps are Windows-only.
Recommendations
  • Consider listing Bash examples before PowerShell in all code tabs to reinforce Linux/macOS parity.
  • Explicitly mention that all Azure CLI commands work on Linux/macOS and Windows.
  • Add a brief note in the prerequisites section confirming that the quickstart is fully cross-platform.
GitHub Create Pull Request
Container Apps Troubleshooting in Azure Container Apps ...s/blob/main/articles/container-apps/troubleshooting.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_reference ⚠️ windows_first
Summary
The documentation is largely cross-platform and CLI-focused, but there are minor instances of Windows bias. Specifically, the section verifying Docker image accessibility references running Docker in an 'elevated command prompt' and links to Docker's Windows installation guide, without mentioning Linux/macOS equivalents. Additionally, the phrase 'elevated command prompt' is Windows-centric, and Windows is referenced before other platforms. However, all core troubleshooting steps and CLI examples are platform-agnostic, and Linux/macOS users can follow the guidance without significant friction.
Recommendations
  • When instructing users to run Docker commands, mention that these can be run in any terminal (e.g., Bash, PowerShell, Terminal) on Windows, Linux, or macOS.
  • Provide links to Docker installation guides for Linux and macOS alongside the Windows link.
  • Replace 'elevated command prompt' with 'terminal with appropriate permissions' or clarify for all platforms.
  • Ensure that references to platform-specific tools or environments are balanced or presented in parallel (e.g., 'If you're running Docker on Windows, Linux, or macOS...').
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page presents deployment options for Azure Container Apps in a generally cross-platform manner, but there are subtle Windows biases. Visual Studio is mentioned before Visual Studio Code, and PowerShell is referenced alongside Bash in CLI automation, but no Linux/macOS-specific editor or workflow is highlighted. There are no explicit Linux/macOS examples or screenshots, and the resources focus on Visual Studio (Windows-first) and Visual Studio Code (cross-platform, but often perceived as Windows-centric in Azure docs). No Linux-specific tools or patterns are discussed.
Recommendations
  • Add explicit Linux/macOS examples or workflows, such as using VS Code on Linux, or CLI commands run in Bash.
  • Include references to Linux/macOS terminal environments and package managers where relevant (e.g., apt, Homebrew for CLI installation).
  • Balance editor recommendations by mentioning cross-platform alternatives (e.g., JetBrains Rider, Vim, etc.) if appropriate.
  • Provide example commands and screenshots from both Windows (PowerShell) and Linux/macOS (Bash) environments.
  • Clarify that all CLI-based workflows work equally well on Linux/macOS, and link to platform-specific installation guides.
GitHub Create Pull Request
Cyclecloud User Authentication ...main/articles/cyclecloud/how-to/user-authentication.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation page presents Active Directory (a Windows-centric technology) before LDAP, and the AD example uses Windows-style username formats (EXAMPLE\username) without showing Linux-style equivalents. However, the page does provide LDAP and Entra ID instructions, and the built-in authentication is cross-platform. No PowerShell or Windows-only tools are referenced, and Linux clusters are explicitly mentioned in the Entra ID section.
Recommendations
  • When describing Active Directory authentication, include Linux-style username formats (e.g., user@domain.com) and clarify how Linux users can authenticate.
  • Provide explicit examples for LDAP authentication that reference typical Linux environments or directory structures.
  • Ensure screenshots and examples do not exclusively show Windows conventions (e.g., backslash in usernames), or add Linux/macOS equivalents.
  • Consider mentioning any platform-specific caveats for authentication methods, especially for Linux clusters.
GitHub Create Pull Request
Event Grid Concepts (push delivery) in Event Grid basic ...s/azure-docs/blob/main/articles/event-grid/concepts.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation page provides example links for creating Event Grid subscriptions using Azure CLI, Azure PowerShell, and Azure Resource Manager templates. The PowerShell example is listed before the Resource Manager template, and both CLI and PowerShell are mentioned, but there is no explicit Linux shell (e.g., Bash) example or mention of Linux-specific tools. However, Azure CLI is cross-platform and the page does not contain Windows-specific commands, tools, or patterns. The bias is minor and limited to the order of example links.
Recommendations
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS as well as Windows.
  • Add explicit Bash or Linux shell examples if there are any platform-specific considerations.
  • Consider listing CLI examples before PowerShell to emphasize cross-platform parity.
  • Add a note that PowerShell Core is available on Linux/macOS if PowerShell examples are relevant.
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 cross-platform and does not focus on Windows-specific deployment or configuration patterns. However, there are minor instances of Windows bias: PowerShell is mentioned as the only CLI tool for updating firewall policy tags, and an FTP workaround links to IIS documentation, a Windows-only web server. These references may create friction for Linux/macOS users who may prefer Bash, Azure CLI, or Linux-based FTP servers.
Recommendations
  • When referencing CLI tools, provide Azure CLI and/or Bash examples alongside PowerShell, especially for common operations like updating firewall policy tags.
  • For FTP server configuration workarounds, include links or examples for popular Linux FTP servers (e.g., vsftpd, ProFTPD) in addition to IIS.
  • Clarify when a workaround or tool is Windows-specific, and offer Linux/macOS alternatives where possible.
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
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides platform-specific instructions for manual failover, listing 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), and no mention of Linux-specific tools or workflows. The ordering and inclusion of PowerShell may create minor friction for Linux/macOS users, though the CLI option is sufficient for most tasks.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS and provide example shell usage.
  • Consider listing Azure CLI before PowerShell to emphasize cross-platform support.
  • Add a Bash shell example for CLI usage, showing command execution and output.
  • Clarify that PowerShell is optional and primarily for Windows users.
  • Ensure parity in code samples and management instructions for Linux/macOS environments.
GitHub Create Pull Request