381
Total Pages
181
Linux-Friendly Pages
200
Pages with Bias
52.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

1604 issues found
Showing 251-275 of 1604 flagged pages
Backup Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Server with an Azure Resource Manager template .../backup/quick-backup-postgresql-flexible-server-arm.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell deployment instructions for the ARM template, referencing Azure PowerShell modules in prerequisites, and omitting equivalent Azure CLI or Bash examples that would be more familiar to Linux users. The 'Next steps' section also links exclusively to PowerShell-based restore instructions.
Recommendations
  • Add Azure CLI and Bash examples for deploying the ARM template, alongside PowerShell.
  • Mention installation steps for Azure CLI in the prerequisites, not just PowerShell.
  • Provide links to both PowerShell and CLI/Bash restore guides in the 'Next steps' section.
  • Ensure that all instructions and code snippets are platform-agnostic or include both Windows and Linux variants.
Backup Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Servers with a Bicep file ...ackup/quick-backup-postgresql-flexible-server-bicep.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a clear Windows bias by exclusively providing PowerShell deployment instructions and referencing Azure PowerShell for next steps. No Azure CLI or Linux shell examples are given, and the guidance assumes use of Windows tools and patterns throughout. Linux users are not provided with equivalent instructions or parity in deployment workflow.
Recommendations
  • Add Azure CLI deployment instructions alongside PowerShell, including example commands for deploying the Bicep template from Bash or other Linux shells.
  • Explicitly mention that the Bicep CLI and Azure CLI are cross-platform and provide installation and usage guidance for Linux/macOS.
  • Include links to Linux/macOS-specific documentation for installing prerequisites and running deployments.
  • Ensure that next steps reference both PowerShell and CLI-based restore workflows, or provide parity in supported tooling.
  • Avoid language that assumes a Windows shell (e.g., 'right-click the shell window and then select Paste') and use platform-neutral instructions.
Backup Quickstart - Create a backup policy for Azure Database for PostgreSQL - Flexible Server using Azure CLI .../backup/quick-backup-postgresql-flexible-server-cli.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by referencing PowerShell objects and workflows as the default or primary approach, especially in the 'Modify the policy template' section. It describes PowerShell object manipulation first, then contrasts it with Azure CLI file-based editing, implying PowerShell (and thus Windows) is the more natural or preferred environment. File path examples use Windows-style backslashes (e.g., .\OSSPolicy.json), and there is no mention of Linux shell equivalents or examples. The documentation does not provide Linux-specific guidance or examples for file handling, scripting, or path formats.
Recommendations
  • Provide Linux shell equivalents for all CLI examples, including file path formats (e.g., ./OSSPolicy.json instead of .\OSSPolicy.json).
  • Include explicit instructions or notes for Linux users on how to perform file-based edits, such as using cat, jq, or sed.
  • Avoid presenting PowerShell as the default or preferred workflow; instead, treat CLI and PowerShell approaches equally, or provide parallel examples.
  • Mention cross-platform compatibility of Azure CLI and clarify any OS-specific differences in scripting or file handling.
  • Add a section or callout for Linux/macOS users with tips for adapting the examples to their environment.
Backup Quickstart - Install Azure Backup extension in an AKS cluster ...main/articles/backup/quick-install-backup-extension.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily describes installation of the Azure Backup extension in AKS using the Azure Portal, which is platform-agnostic, but in the 'Next steps' section, Azure PowerShell is listed before Azure CLI, and there is no mention of Linux-specific tools or shell examples. There are no explicit Linux command-line instructions or screenshots, and the guidance does not address Linux users directly, potentially leading to a Windows-centric impression.
Recommendations
  • Provide explicit Linux shell (bash) examples for installing and configuring the extension, especially for command-line steps.
  • List Azure CLI instructions before or alongside PowerShell, as CLI is cross-platform and widely used on Linux.
  • Include screenshots or instructions for Linux environments where relevant, such as using the Azure CLI in a Linux terminal.
  • Mention platform compatibility for each tool (Portal, PowerShell, CLI) and clarify which are recommended for Linux users.
  • Add troubleshooting or notes for Linux-specific scenarios, such as permissions or networking configurations.
Backup Quickstart: Back up a virtual machine in Azure with Terraform ...blob/main/articles/backup/quick-backup-vm-terraform.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively demonstrates backing up a Windows virtual machine in Azure using Terraform. All examples, descriptions, and resource creation steps focus on Windows VMs, with no mention of Linux VM equivalents or how to adapt the process for Linux. The page title, summary, and next steps reinforce a Windows-centric approach, and there are no Linux-specific instructions, code samples, or troubleshooting advice.
Recommendations
  • Add parallel instructions and code samples for creating and backing up a Linux VM in Azure using Terraform.
  • Update the introduction and checklist to mention both Windows and Linux VM scenarios.
  • Include Linux-specific Azure CLI commands and considerations, such as SSH key generation and Linux VM resource names.
  • Provide troubleshooting tips relevant to Linux VMs.
  • Offer 'Next steps' links to articles about Azure Linux VMs and their backup procedures.
Backup Quickstart - Configure vaulted backup for an Azure Kubernetes Service (AKS) cluster using Azure Backup via Azure Resource Manager ...ob/main/articles/backup/quick-kubernetes-backup-arm.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by providing only Azure PowerShell deployment instructions, referencing PowerShell and its installation in the prerequisites, and omitting equivalent Azure CLI or Linux shell examples. The deployment workflow and scripting guidance are tailored to Windows/PowerShell users, with no mention of Linux or cross-platform alternatives.
Recommendations
  • Add Azure CLI deployment instructions alongside PowerShell, including example commands for template deployment.
  • Reference both PowerShell and Azure CLI in prerequisites, with installation links for Linux/macOS users.
  • Explicitly mention that the ARM template can be deployed from any OS and shell, and provide cross-platform guidance.
  • Consider providing Bash or shell script examples for Linux users.
  • Ensure that next steps and related links highlight both PowerShell and CLI options equally.
Backup Quickstart - Configure vaulted backup for an Azure Kubernetes Service (AKS) cluster using Azure Backup via Azure Bicep .../main/articles/backup/quick-kubernetes-backup-bicep.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by exclusively providing PowerShell deployment instructions for the Bicep template, with no equivalent Bash, Azure CLI, or Linux shell examples. The prerequisites and deployment steps focus on Azure PowerShell, which is most commonly used on Windows, and do not mention or prioritize cross-platform tools. The 'Next steps' section lists PowerShell before CLI, further reinforcing Windows-first ordering.
Recommendations
  • Add equivalent deployment instructions using Azure CLI and Bash shell, which are cross-platform and commonly used on Linux and macOS.
  • In the prerequisites section, mention both Azure PowerShell and Azure CLI as supported options for deploying Bicep templates.
  • In the 'Next steps' section, alternate or randomize the order of PowerShell and CLI links to avoid Windows-first ordering.
  • Explicitly state that the deployment steps can be performed on any OS, and provide guidance for Linux/macOS users.
  • Where possible, provide examples for both PowerShell and Bash/CLI side-by-side to ensure parity and inclusivity.
Backup Restore VMware virtual machines using Azure Backup Server .../articles/backup/restore-azure-backup-server-vmware.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows Server VMs for individual file recovery, omitting Linux VM examples and recovery procedures. All item-level restore instructions are limited to Windows, and registry key modifications (a Windows-specific tool) are used for advanced configuration. There are no Linux-specific recovery steps, tools, or troubleshooting guidance, and the documentation does not mention parity or limitations for Linux VMs.
Recommendations
  • Add explicit instructions and examples for restoring individual files from Linux VMs, or clarify if this feature is unavailable for Linux.
  • Include Linux-specific recovery options, such as mounting VMDK files on a Linux system and extracting files.
  • Document any limitations or differences in recovery features between Windows and Linux VMs.
  • If registry modifications are required for advanced configuration, provide equivalent steps for Linux environments (if supported), or state that such configuration is Windows-only.
  • Ensure troubleshooting and next steps sections include guidance for Linux VM recovery scenarios.
Backup Restore SQL Server databases on an Azure VM .../main/articles/backup/restore-sql-database-azure-vm.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: it exclusively references Windows tools (e.g., PsExec, NT AUTHORITY\SYSTEM, C:\Program Files), provides examples and instructions tailored to Windows environments, and omits Linux-specific guidance or parity (e.g., no mention of restoring SQL Server on Linux VMs, no Linux file system paths, no Linux commands or service management). The use of Windows-centric terminology and tools appears throughout, and there are no examples or instructions for SQL Server on Linux VMs, even though SQL Server is supported on Linux in Azure.
Recommendations
  • Add explicit instructions and examples for restoring SQL Server databases on Linux-based Azure VMs.
  • Include Linux file system paths (e.g., /var/opt/mssql/data) and relevant commands for file permissions and service management (e.g., systemctl for SQL Server service).
  • Provide Linux equivalents for Windows tools and procedures, such as using sudo and chown/chmod for file permissions instead of PsExec and NT AUTHORITY\SYSTEM.
  • Clarify which steps are Windows-specific and which are applicable to Linux, or provide parallel sections for both platforms.
  • Mention any differences or limitations in restore functionality between Windows and Linux SQL Server on Azure VMs.
  • Ensure screenshots and UI references are not exclusively Windows-oriented, or note any platform-specific differences.
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits several signs of Windows bias. Windows terminology and tools (such as PowerShell) are mentioned before Linux equivalents, and examples for restoring VMs using PowerShell are provided without corresponding Linux CLI or script examples. The process for restoring encrypted Linux VMs is described only briefly, lacking step-by-step instructions or command-line examples, while Windows-specific operations (like OS disk swap) are referenced directly. The use of Windows-centric documentation links and the absence of Linux-focused guidance further reinforce the bias.
Recommendations
  • Provide equivalent Linux CLI (az CLI, Bash) examples for restoring VMs and disks, alongside PowerShell examples.
  • Include step-by-step instructions for restoring encrypted Linux VMs, including reinstallation of the ADE extension, with sample commands.
  • Reference Linux-specific documentation and tools where appropriate, such as links to Linux OS disk swap procedures.
  • Ensure that both Windows and Linux scenarios are covered equally in all sections, including troubleshooting and next steps.
  • Avoid mentioning Windows tools or patterns before Linux equivalents; present both in parallel or in separate, clearly labeled sections.
Backup Restore SQL server databases in Azure VMs with REST API .../main/articles/backup/restore-azure-sql-vm-rest-api.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based SQL Server instances, using Windows-style directory paths (e.g., C:\SQLfiles\Default.ldf), and omitting any mention of Linux-based SQL Server or examples relevant to Linux VMs. All resource names, directory paths, and restore scenarios assume a Windows environment, with no guidance for Linux users or parity in examples.
Recommendations
  • Add explicit examples and instructions for restoring SQL Server databases on Linux-based Azure VMs, including Linux-style directory paths (e.g., /var/opt/mssql/data).
  • Clarify whether the REST API supports SQL Server on Linux VMs and document any differences or prerequisites.
  • Provide alternate request body examples using Linux file paths and container names relevant to Linux VMs.
  • Include a note or section on cross-platform support, outlining any limitations or additional steps for Linux users.
  • Ensure terminology and resource naming do not assume a Windows-only environment (e.g., avoid only using 'C:\' paths or Windows hostnames).
Backup Restore SAP HANA database instances on Azure VMs ...articles/backup/sap-hana-database-instances-restore.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing the use of PowerShell or CLI scripts for permission management, but does not provide explicit Linux shell (bash) examples or mention Linux tools. The workflow and screenshots are centered around the Azure portal, which is platform-agnostic, but the only command-line references are to PowerShell and CLI, with PowerShell mentioned first. There are no examples or instructions tailored for Linux users, such as bash scripts or Linux-specific commands for disk attachment or mounting.
Recommendations
  • Provide explicit bash shell examples for Linux users alongside PowerShell/CLI instructions.
  • Mention Linux-native tools (e.g., mount, fdisk) for disk management and mounting operations.
  • Ensure that command-line instructions are presented in a platform-neutral order, or group them by OS.
  • Clarify when Azure CLI commands are cross-platform and provide examples for both Windows (PowerShell) and Linux (bash).
  • Include screenshots or references to Linux desktop environments where relevant.
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily focused on the Windows platform, specifically the MARS agent (which is Windows-only), and provides examples using Windows-centric tools such as PowerShell and the MARS console. There are no Linux-specific instructions, nor any mention of Linux backup agents or workflows. The automation and scripting examples are all in PowerShell or Azure CLI, but the operational steps (installation, passphrase management) are exclusively described for Windows environments.
Recommendations
  • Clearly state at the beginning that the MARS agent is Windows-only, and provide links or references to equivalent Linux backup solutions (e.g., Azure Backup for Linux VMs or Azure Backup Server).
  • Where possible, add parity documentation for Linux backup agents, including how to securely store and retrieve encryption credentials using Azure Key Vault.
  • If Azure CLI is cross-platform, clarify which steps can be performed from Linux/macOS and which are Windows-only.
  • Provide alternative examples or workflows for Linux users, or direct them to relevant documentation.
  • Avoid assuming the use of Windows tools (e.g., MARS console, PowerShell) in generic Azure Key Vault instructions—offer platform-agnostic guidance where feasible.
Backup Script Sample - Create a new or modify the current file and folder backup policy ...ticles/backup/scripts/set-file-folder-backup-policy.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides a PowerShell script for managing backup policies with the MARS agent, which is a Windows-specific tool. There are no examples, instructions, or mentions of Linux equivalents, nor is there guidance for Linux administrators. The focus on PowerShell and Windows registry paths further reinforces a Windows-centric approach.
Recommendations
  • Add equivalent script samples for Linux environments, using Bash or Python.
  • Mention and provide guidance for Linux-compatible backup tools (e.g., rsync, cron, Azure CLI for Linux).
  • Clarify platform support for the MARS agent and suggest alternatives for Linux if MARS is not supported.
  • Structure documentation so that both Windows and Linux approaches are presented, ideally side-by-side.
  • Explicitly state any platform limitations at the beginning of the page.
Backup Soft delete for SQL server in Azure VM and SAP HANA in Azure VM workloads ...articles/backup/soft-delete-sql-saphana-in-azure-vm.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed instructions and code examples exclusively for Azure PowerShell, a Windows-centric tool, with no mention of Linux-native CLI tools or workflows. The examples and guidance prioritize Windows patterns and do not offer parity for Linux users, such as Bash/CLI commands or references to Linux tooling. The documentation also refers to PowerShell before any other automation or scripting options, and does not acknowledge Linux environments or alternatives.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, as Azure CLI is cross-platform and preferred by many Linux users.
  • Explicitly mention that the operations can be performed from Linux/macOS environments using Azure CLI or REST API, not just PowerShell.
  • Include screenshots or instructions for Linux users where UI or command-line differences exist.
  • Clarify any prerequisites or environment-specific requirements for both Windows and Linux users.
  • Review terminology and tool references to ensure Linux parity (e.g., avoid assuming PowerShell is the default automation tool).
Backup Azure Backup support matrix for SQL Server Backup in Azure VMs ...e-docs/blob/main/articles/backup/sql-support-matrix.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. Only Windows Server operating systems are supported and listed, with explicit mention that Linux is not supported. All examples and tooling references (such as PowerShell) are Windows-centric, and there is no mention of Linux equivalents or parity. The documentation does not provide guidance or examples for Linux users, nor does it discuss future support or alternatives for Linux-based SQL Server deployments.
Recommendations
  • Clearly state the roadmap or plans for Linux support, if any, to inform users of future parity.
  • Add a dedicated section for Linux users explaining current limitations, possible workarounds, or alternative backup strategies.
  • If possible, provide examples or references for Linux-based backup solutions (e.g., using Azure CLI, third-party tools, or manual backup procedures).
  • Ensure that tooling references (such as PowerShell) are balanced with Azure CLI or other cross-platform tools, and clarify their platform compatibility.
  • Regularly review and update the documentation to reflect any changes in Linux support or cross-platform capabilities.
Backup Script Sample - Create a new or modify the current system state backup policy ...icles/backup/scripts/set-system-state-backup-policy.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides a PowerShell script sample for managing system state backup policy with the MARS agent, which is a Windows-centric tool. All instructions, code, and next steps reference Windows tools and workflows, with no mention of Linux equivalents or cross-platform alternatives. There are no examples or guidance for Linux users, and Windows patterns are presented as the default.
Recommendations
  • Include equivalent script samples for Linux environments, such as Bash or Python, if supported.
  • Clarify whether the MARS agent and system state backup policy management are available or supported on Linux, and provide alternatives if not.
  • Mention and link to Linux backup tools (e.g., rsync, tar, cron jobs, Azure CLI for Linux) where appropriate.
  • Add a section comparing Windows and Linux backup management approaches, highlighting platform-specific considerations.
  • Ensure that documentation titles and descriptions specify platform limitations or provide cross-platform guidance where possible.
Backup Soft delete for virtual machines ...b/main/articles/backup/soft-delete-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples for managing soft delete operations, referencing Windows-centric tools and patterns, and omitting equivalent Linux CLI or automation examples. The PowerShell section is given prominence and detail, while there are no Bash/CLI or Linux-native instructions. The use of 'Az.RecoveryServices' and PowerShell cmdlets further reinforces the Windows-centric approach.
Recommendations
  • Add equivalent Azure CLI (az backup ...) examples for all operations shown in PowerShell, including delete, undelete, and resume backup.
  • Explicitly mention cross-platform support and clarify that operations can be performed from Linux/macOS environments using Azure CLI or REST API.
  • Provide Bash script snippets for automation tasks, ensuring Linux administrators have parity in guidance.
  • Reorder or parallelize example sections so that Azure CLI (cross-platform) instructions appear before or alongside PowerShell, rather than after.
  • Reference Linux tools and automation patterns where relevant, such as cron jobs or shell scripting for backup management.
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive use of PowerShell scripts for troubleshooting and recovery operations (e.g., finding Recovery Services vaults, undeleting file shares). No Linux or cross-platform CLI (such as Azure CLI, Bash, or shell script) alternatives are provided. Additionally, references to tools and portals (such as 'Files portal') are Windows-centric, and there is a lack of parity for Linux administrators who may need to perform similar tasks.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples for all PowerShell scripts referenced, ensuring Linux users can perform the same troubleshooting and recovery operations.
  • Explicitly mention cross-platform tools and workflows (e.g., Azure CLI, REST API) alongside Windows-specific instructions.
  • Add notes or sections clarifying how Linux/macOS administrators can access or perform operations (such as undeleting file shares, finding Recovery Services vaults) without relying on PowerShell.
  • Ensure screenshots and UI references are not exclusively Windows-oriented, and clarify if the portal experience is identical across platforms.
  • Regularly review documentation for platform-specific language and update to reflect Azure's cross-platform capabilities.
Backup Tutorial - Back up Azure Database for PostgreSQL server ...lob/main/articles/backup/tutorial-postgresql-backup.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing PowerShell scripts as the primary method for granting database privileges, mentioning PowerShell before alternatives like PG admin or PSQL, and lacking explicit Linux or cross-platform command-line examples. There are no bash, Linux shell, or platform-neutral instructions for privilege assignment, and the only script-based example is PowerShell, which is native to Windows environments.
Recommendations
  • Provide equivalent examples using Linux-native tools such as bash scripts, psql CLI commands, or instructions for using PG admin on Linux.
  • Present privilege assignment methods in a platform-neutral order, listing psql and PG admin before or alongside PowerShell.
  • Explicitly state cross-platform compatibility for all steps and scripts, and clarify how Linux users can perform each operation.
  • Include screenshots or walkthroughs for Linux environments where appropriate.
  • Add a dedicated section or callout for Linux users, summarizing the steps and tools available on Linux.
Backup Tutorial - Back Up SQL Server Databases to Azure ...-docs/blob/main/articles/backup/tutorial-sql-backup.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific components and patterns. All instructions and background processes assume the SQL Server VM is running Windows, with references to Windows-only extensions (AzureBackupWindowsWorkload), service accounts (NT Service\AzureWLBackupPluginSvc), and permissions models. There are no examples, instructions, or notes for Linux-based SQL Server VMs, nor are Linux tools or patterns mentioned. The documentation does not acknowledge or support SQL Server on Linux, and all technical details are Windows-centric.
Recommendations
  • Add explicit guidance and examples for backing up SQL Server databases running on Linux-based Azure VMs, if supported.
  • Clarify whether the Azure Backup solution supports SQL Server on Linux VMs, and if not, provide alternative backup strategies or links to relevant documentation.
  • Mention Linux-specific requirements, such as service accounts, permissions, and extension installation steps, if applicable.
  • Include screenshots and walkthroughs for the Linux experience in the Azure portal or via CLI.
  • If only Windows is supported, state this clearly at the beginning of the tutorial to avoid confusion for Linux users.
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. The Azure portal (GUI) instructions are Windows-centric, as the Azure portal is most commonly used on Windows environments, and the workloads discussed are all Azure VMs or databases running on Windows-based platforms (SQL Server, SAP HANA in Azure VMs). The PowerShell section is extensive and presented before the CLI section, with detailed step-by-step instructions and sample scripts, reinforcing a Windows-first approach. PowerShell, a Windows-native tool, is given prominence over the cross-platform Azure CLI. There are no explicit Linux shell (bash) examples, nor any mention of Linux-native tools or patterns, and the CLI section is less detailed than PowerShell. The documentation does not address Linux-specific backup scenarios or provide parity in example depth for Linux users.
Recommendations
  • Add explicit Linux shell (bash) examples for all CLI commands, including sample scripts for automation.
  • Include instructions for using Azure CLI on Linux, such as installation via apt/yum and running commands in bash.
  • Mention Linux-native tools and patterns for scripting and automation, such as cron jobs or shell scripts.
  • Ensure CLI examples are as detailed and comprehensive as PowerShell examples, including error handling and output parsing.
  • Add a section or notes addressing backup scenarios for Linux VMs and workloads, if supported.
  • Avoid assuming the Azure portal is only used on Windows; clarify cross-platform access and usage.
  • Balance the order of presentation so CLI and PowerShell are given equal prominence, or alternate their order.
Backup Move VM backup - standard to enhanced policy in Azure Backup ...cles/backup/backup-azure-vm-migrate-enhanced-policy.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing PowerShell and CLI versions for migration, but does not provide explicit Linux shell (bash) examples or mention Linux-specific usage patterns. The only command-line example is a link to Azure CLI documentation, but no actual command is shown, and there is no mention of Linux shell syntax or considerations. The portal-based instructions and screenshots are platform-neutral, but the command-line guidance implicitly prioritizes Windows tools and omits Linux parity.
Recommendations
  • Add explicit bash/Azure CLI command examples for Linux users, including syntax and sample commands.
  • Clarify that Azure CLI is cross-platform and provide instructions for both Windows (PowerShell) and Linux (bash) environments.
  • Include notes or sections addressing Linux-specific considerations, such as authentication, environment setup, or shell differences.
  • Ensure that any references to PowerShell are balanced with equivalent bash examples, especially for automation scenarios.
Backup Restore Azure Kubernetes Service (AKS) using Azure Backup ...les/backup/azure-kubernetes-service-cluster-restore.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation exhibits Windows bias by explicitly referencing Azure PowerShell as an alternative method for restoring AKS clusters, without mentioning or providing equivalent examples for Azure CLI (which is cross-platform and widely used on Linux/macOS). The only command-line restore method linked is PowerShell, and there are no Linux-specific instructions, CLI examples, or references to Linux-native tools. This may lead Linux users to feel unsupported or unclear about how to perform these operations outside of Windows environments.
Recommendations
  • Add Azure CLI examples for restoring AKS clusters, alongside or before PowerShell references.
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide links to relevant CLI documentation.
  • Ensure that any command-line instructions are presented in a cross-platform manner, avoiding exclusive reliance on PowerShell.
  • If there are differences in restore procedures between Windows and Linux environments, document them clearly.
  • Include screenshots or walkthroughs from Linux terminals where appropriate.
Backup Quickstart - Configure vaulted backup for Azure Data Lake Storage using ARM or Bicep template ...ata-lake-storage-backup-configure-quickstart-arm-bicep.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only PowerShell deployment instructions for both ARM and Bicep templates, with no mention of Azure CLI or Bash equivalents. This approach assumes users are familiar with PowerShell, which is more common on Windows, and does not offer Linux-friendly or cross-platform alternatives. The deployment steps are Windows-centric, potentially excluding Linux and macOS users who prefer Bash or Azure CLI.
Recommendations
  • Add Azure CLI deployment examples for both ARM and Bicep templates, showing equivalent commands for Linux/macOS users.
  • Include Bash script examples for template deployment, especially for users working in native Linux environments.
  • Explicitly state that Azure Cloud Shell supports both PowerShell and Bash, and provide instructions for both.
  • Reorder or parallelize instructions so that Windows and Linux/macOS options are presented together, avoiding implicit prioritization of Windows/PowerShell.
  • Mention cross-platform compatibility and recommend tools that work equally well on all operating systems.