Backup

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 551-575 of 1604 flagged pages
Backup Quickstart - Configure vaulted backup for Azure Files using Azure CLI ...cles/backup/quick-backup-azure-files-vault-tier-cli.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page shows mild Windows bias. While the main instructions use Azure CLI (which is cross-platform), references to Azure PowerShell and the Azure portal are given as alternatives before REST API, and the example CLI output includes a Windows-style path (C:\Users\testuser\Downloads\CLIForAFS\azure-cli>). The prerequisites mention running CLI locally on Windows or macOS with Docker, but do not mention Linux explicitly. There is no explicit Linux example or mention of Linux-specific patterns, and the CLI example output is shown from a Windows environment.
Recommendations
  • Include explicit instructions and examples for running Azure CLI on Linux, such as installation steps and sample commands from a Linux shell.
  • Show CLI example outputs from both Windows and Linux terminals, or use a neutral prompt (e.g., $) to avoid platform bias.
  • Mention Linux as a supported platform for local CLI installation alongside Windows and macOS.
  • Ensure parity in alternative tool references by listing REST API and CLI before PowerShell and portal, or grouping them without platform order bias.
  • Add a note clarifying that all CLI commands work equally on Linux, macOS, and Windows.
GitHub Create Pull Request
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-10 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, 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 both Azure PowerShell and Azure CLI tools in prerequisites, with installation links for Linux and macOS.
  • Ensure 'Next steps' includes links to restore instructions using Azure CLI and Bash.
  • Clearly indicate that the process is cross-platform and provide guidance for users on Linux and macOS.
GitHub Create Pull Request
Backup Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Server using a Terraform template ...p/quick-backup-postgresql-flexible-server-terraform.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by mentioning PowerShell as a client for Azure Backup before CLI and other options, and by referencing the Azure PowerShell module in the authentication note. No Linux-specific tools or shell examples are provided, and there is no explicit mention of Linux environments or parity. The authentication note clarifies that only Azure CLI is supported for Terraform authentication, but still refers to PowerShell usage, which may confuse Linux users. All code samples are platform-neutral (Terraform), but supporting steps and troubleshooting lack Linux-specific guidance.
Recommendations
  • List Azure CLI before PowerShell when enumerating supported clients, or mention both together to avoid implying a preference.
  • Add explicit instructions or notes for Linux/macOS users, such as shell commands for directory creation and file editing.
  • Clarify that Azure CLI is cross-platform and provide links or instructions for installation on Linux/macOS.
  • Remove or rephrase references to PowerShell in authentication notes to avoid confusion for non-Windows users.
  • Include troubleshooting steps or links relevant to Linux environments.
  • Consider adding a brief section or callout confirming that all steps work equally on Linux, macOS, and Windows.
GitHub Create Pull Request
Backup Quick start - Back up Azure Database for PostgreSQL server ...cles/backup/quick-backup-postgresql-database-portal.md
High Priority View Details →
Scanned: 2026-01-10 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 referencing PowerShell scripts as the primary method for granting privileges to database users, both in the prerequisites and in the main configuration flow. While alternatives like PG admin or PSQL are briefly mentioned, they are listed after PowerShell and lack concrete examples or guidance. No Linux-specific command-line examples (e.g., Bash, psql CLI) are provided, and Windows-centric tooling (PowerShell) is presented as the default, with no parity for Linux users.
Recommendations
  • Provide step-by-step examples for granting privileges using psql (PostgreSQL CLI) and PG admin, including sample commands and screenshots where appropriate.
  • Explicitly mention and demonstrate how Linux users can perform all required operations, such as privilege assignment and secret management, using native Linux tools.
  • Reorder instructions to present platform-neutral or Linux-native methods before or alongside PowerShell, ensuring equal visibility.
  • Clarify that PowerShell is optional and not required for users on Linux or macOS, and provide links to relevant Linux documentation.
  • Add a dedicated section or callout for cross-platform support, listing equivalent commands and tools for Windows, Linux, and macOS.
GitHub Create Pull Request
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-10 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 strong Windows bias by exclusively providing PowerShell deployment instructions and referencing Azure PowerShell for subsequent operations. There are no examples or guidance for deploying the Bicep template using cross-platform tools like Azure CLI, nor are Linux or macOS workflows mentioned. The instructions and next steps focus on PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Add Azure CLI deployment instructions alongside PowerShell, showing how to deploy the Bicep template from bash or other shells.
  • Include explicit notes that both PowerShell and CLI are supported on Windows, Linux, and macOS, and provide parity in example scripts.
  • Mention or link to cross-platform installation guides for Bicep and Azure CLI, not just PowerShell.
  • In the 'Next steps' section, provide links and examples for restoring using Azure CLI as well as PowerShell.
  • Consider reordering examples so that cross-platform tools (CLI) are presented before or alongside PowerShell, rather than PowerShell-first.
GitHub Create Pull Request
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-10 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 primarily by referencing PowerShell objects and behaviors before Linux alternatives, describing modification patterns in terms of PowerShell objects, and using Windows-style file paths (e.g., .\OSSPolicy.json) in CLI examples. The explanation of policy modification emphasizes PowerShell object manipulation and only briefly mentions the CLI's file-based approach, which is more relevant for Linux/macOS users. There are no explicit Linux/macOS examples or notes about cross-platform differences in file paths or scripting patterns.
Recommendations
  • Provide explicit Linux/macOS examples, including file path formats (e.g., ./OSSPolicy.json instead of .\OSSPolicy.json).
  • Clarify CLI usage patterns for Linux/macOS, such as file redirection and naming conventions.
  • Avoid describing PowerShell object manipulation as the default or primary method; instead, present CLI and file-based workflows first or equally.
  • Add notes about cross-platform compatibility and differences in scripting environments.
  • Ensure that all examples and instructions are tested and presented for both Windows and Linux/macOS platforms.
GitHub Create Pull Request
Backup Quickstart - Bicep file VM Backup ...lob/main/articles/backup/quick-backup-vm-bicep-file.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. The Bicep template provisions only Windows VMs, with no mention of Linux images or parameters. All deployment and management examples use Azure PowerShell, with no Azure CLI or Bash equivalents provided. The instructions and cleanup steps reference only PowerShell cmdlets, and there is no guidance for Linux users or cross-platform tooling. The template and workflow are tailored exclusively for Windows environments.
Recommendations
  • Provide equivalent Bicep template parameters and examples for deploying Linux VMs (e.g., Ubuntu, CentOS) alongside the Windows options.
  • Include Azure CLI (az) and Bash examples for deploying the Bicep template, starting backup jobs, monitoring, and cleanup, in addition to PowerShell.
  • Mention and demonstrate cross-platform tools and workflows (e.g., Azure Cloud Shell with Bash, VS Code on Linux/Mac).
  • Clarify in the prerequisites and throughout the guide that the process is applicable to both Windows and Linux VMs, or clearly scope the guide as Windows-only if that is the intent.
  • Link to Linux-specific backup and restore documentation where relevant, or provide a parallel quickstart for Linux VM backup using Bicep.
GitHub Create Pull Request
Backup Quickstart - Back up a VM with the Azure portal by using Azure Backup ...cs/blob/main/articles/backup/quick-backup-vm-portal.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias primarily by referencing Windows VM creation first, providing more detailed steps and links for Windows agent installation, and mentioning Windows tools (MSI installer, file paths) before Linux equivalents. The Linux section is less detailed, lacks explicit command/package examples, and refers users to external sources for installation. There are no CLI or shell examples for Linux, and the agent installation instructions for Linux are less actionable than for Windows.
Recommendations
  • Provide equal prominence to Linux VM creation and management, including direct links to Linux VM quickstart guides.
  • Include explicit Linux agent installation commands (e.g., apt, yum, zypper) and package names, not just general instructions.
  • Add Linux-specific troubleshooting steps and verification commands (e.g., checking agent version via shell).
  • Ensure screenshots and examples reflect both Windows and Linux environments where applicable.
  • Avoid referencing Windows tools (MSI, file paths) before Linux equivalents; present both side-by-side or in parallel sections.
  • Clarify that both Windows and Linux VMs are fully supported, and highlight any differences in backup/restore behavior.
GitHub Create Pull Request
Backup Quickstart - Resource Manager template VM Backup .../blob/main/articles/backup/quick-backup-vm-template.md
High Priority View Details →
Scanned: 2026-01-10 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 clear Windows bias by focusing exclusively on Azure PowerShell for deployment and cleanup instructions, with no equivalent Azure CLI or Bash examples. The template itself is described as deploying a Windows VM, and all code samples and operational steps use PowerShell syntax. Linux tools and workflows are only mentioned in passing, and not demonstrated or prioritized.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all deployment and cleanup steps.
  • Explicitly mention and demonstrate how to deploy and back up Linux VMs using ARM templates.
  • Ensure that references to tools (e.g., Azure CLI, Bash) are given equal prominence and ordering as PowerShell.
  • Provide links to Linux-specific quickstarts and tutorials where relevant.
  • Clarify in the template review section whether the template supports both Windows and Linux VMs, and if not, provide or link to a Linux VM equivalent.
GitHub Create Pull Request
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by primarily guiding users through the Azure portal UI, which is most commonly used on Windows. In the 'Next steps' section, Azure PowerShell is listed before Azure CLI, ARM, Bicep, and Terraform, suggesting a preference for Windows-centric tooling. There are no Linux-specific examples, nor is there mention of Linux-native tools or shell commands. The documentation does not provide parity for Linux users, such as Bash or shell script examples, and omits guidance for command-line installation outside of the portal.
Recommendations
  • Provide explicit Linux/Bash command-line examples for installing and configuring the Azure Backup extension in AKS clusters.
  • List Azure CLI before Azure PowerShell in 'Next steps', as CLI is cross-platform and more commonly used on Linux.
  • Include screenshots or instructions for using the Azure portal from Linux environments (e.g., browser-based, Cloud Shell).
  • Add a section comparing Azure PowerShell and Azure CLI, highlighting cross-platform usage.
  • Ensure all steps can be performed using CLI tools available on Linux, and link directly to those instructions.
GitHub Create Pull Request
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-10 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 towards Windows by exclusively providing PowerShell deployment instructions and referencing the Azure PowerShell module for backup configuration. There are no examples using Azure CLI, Bash, or Linux-native tools, and PowerShell is presented as the primary method for deploying the Bicep template. This may disadvantage users on Linux or macOS platforms who typically use Azure CLI or Bash scripts.
Recommendations
  • Add Azure CLI and Bash examples for deploying the Bicep template, ensuring Linux and macOS users have clear guidance.
  • Mention both Azure PowerShell and Azure CLI as supported options in the prerequisites and deployment sections, rather than referencing PowerShell exclusively.
  • Reorder instructions or provide parallel examples so that CLI/Bash and PowerShell methods are presented with equal prominence.
  • Explicitly state cross-platform compatibility for the Bicep CLI and deployment steps.
  • Include notes or links to platform-specific installation guides for both PowerShell and Azure CLI.
GitHub Create Pull Request
Backup Restore VMware virtual machines using Azure Backup Server .../articles/backup/restore-azure-backup-server-vmware.md
High Priority View Details →
Scanned: 2026-01-10 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 focusing exclusively on Windows-based recovery scenarios and tools. All examples and procedures are centered around the Microsoft Azure Backup Server (MABS) Administrator Console, which is a Windows application. Individual file recovery is only supported for Windows Server VMs, with no mention of Linux VM file-level restore. Registry key configuration for parallel restore jobs is described using Windows Registry paths, with no Linux equivalent or alternative provided. There are no examples, instructions, or references for Linux VMs or Linux-based recovery processes.
Recommendations
  • Add guidance and examples for restoring individual files from Linux VMs, or clarify if this is not supported.
  • If Linux VM file-level restore is not supported, explicitly state this limitation and suggest alternative approaches for Linux VM recovery.
  • Provide parity in documentation by including Linux-specific tools, commands, or configuration steps where applicable.
  • When mentioning configuration changes (such as registry edits), offer Linux equivalents (e.g., config files, CLI commands) if supported.
  • Ensure that troubleshooting and next steps sections include Linux-specific guidance if Linux VMs are supported by MABS.
GitHub Create Pull Request
Backup Restore encrypted Azure VMs ...les/backup/restore-azure-encrypted-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias by prioritizing Windows-specific instructions and tools. PowerShell is mentioned as the primary method for creating a VM from restored disks, with no equivalent CLI or Linux example provided. The OS disk swap operation links only to Windows documentation. Linux-specific guidance is relegated to a separate step, with less detail and no command-line examples. Windows tools and patterns are referenced before their Linux counterparts, and Linux parity is lacking in automation and scripting examples.
Recommendations
  • Provide Azure CLI and/or Bash examples for restoring and deploying VMs from restored disks, alongside PowerShell.
  • Include links and instructions for OS disk swap operations for Linux VMs, not just Windows.
  • Ensure Linux-specific restore steps are as detailed as Windows steps, including automation and scripting options.
  • Mention Linux tools and patterns (e.g., cloud-init, SSH, Linux VM extensions) where relevant.
  • Structure instructions so that Windows and Linux guidance are presented in parallel, rather than Windows-first.
GitHub Create Pull Request
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific SQL Server database paths (e.g., C:\SQLfiles\Default.ldf), using Windows-style path separators, and not providing any Linux-based examples or guidance. All resource and example names (e.g., SQLServer2012, sqlserver-0) imply Windows environments, and there is no mention of Linux SQL Server VMs or their restore patterns. There are no PowerShell-specific examples, but the documentation assumes Windows conventions throughout.
Recommendations
  • Add examples for restoring SQL Server databases on Linux-based Azure VMs, including Linux-style file paths (e.g., /var/opt/mssql/data).
  • Explicitly mention support for SQL Server on Linux and clarify any differences in restore procedures or API usage.
  • Provide alternate request body examples using Linux directory structures for alternateDirectoryPaths.
  • Include a note or section discussing any OS-specific considerations, such as file permissions or service management differences between Windows and Linux.
  • Ensure terminology and examples are inclusive of both Windows and Linux environments, or clarify when something is Windows-specific.
GitHub Create Pull Request
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-10 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 exhibits a Windows bias in several ways: all operational examples and instructions assume a Windows environment, specifically referencing Windows paths (e.g., C:\Program Files), NT AUTHORITY\SYSTEM, and Windows-only tools like PsExec and SSMS. There are no instructions or examples for restoring SQL Server databases on Linux-based Azure VMs, nor any mention of Linux equivalents for the tools or procedures described. The documentation implicitly assumes SQL Server is running on Windows, and restoration steps are tailored to Windows patterns and tooling.
Recommendations
  • Add explicit instructions and examples for restoring SQL Server databases on Linux-based Azure VMs, including file paths and service management commands relevant to Linux.
  • Provide Linux equivalents for Windows-only tools and procedures, such as alternatives to PsExec for privilege escalation and file access.
  • Include examples using cross-platform tools (e.g., Azure CLI, REST API) for restore operations, and clarify any differences in process or prerequisites for Linux VMs.
  • Mention and document how to use SQL Server tools available on Linux (e.g., sqlcmd, Azure Data Studio) for restore operations, alongside SSMS.
  • Ensure that references to file system paths, permissions, and service management cover both Windows and Linux conventions.
  • Clearly state at the beginning of the article whether the instructions apply to both Windows and Linux SQL Server deployments, and provide links to Linux-specific documentation if available.
GitHub Create Pull Request
Backup Save and manage MARS agent passphrase securely in Azure Key Vault ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/save-backup-passphrase-securely-in-azure-key-vault.md
High Priority View Details →
Scanned: 2026-01-10 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 oriented toward Windows environments. All operational steps for saving and managing the MARS agent passphrase are based on the MARS agent, which is a Windows-only tool. Examples and automation references use PowerShell and the MARS console, with no mention of Linux equivalents or support for Linux backup agents. The installation and passphrase management workflows are described exclusively for Windows, and there are no examples or guidance for Linux systems or cross-platform scenarios.
Recommendations
  • Clearly state at the beginning that the MARS agent is Windows-only, and provide links to equivalent Linux backup solutions (e.g., Azure Backup for Linux VM).
  • Add a comparison table or section outlining backup passphrase management for Linux agents, if available, and how to use Azure Key Vault with those agents.
  • Include CLI-only workflows where possible, as these are more cross-platform, and clarify which steps are Windows-specific.
  • If Linux support is not available, explicitly mention this limitation and suggest alternative approaches for Linux users.
  • Review automation scripts and examples to ensure parity or provide Linux alternatives where feasible.
GitHub Create Pull Request
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-10 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 references for Linux environments or equivalent Linux tools. The focus is entirely on Windows technologies, with no mention of how to achieve similar automation or backup management on Linux systems.
Recommendations
  • Include equivalent script samples for Linux environments, such as Bash or Python examples using Linux-native backup tools (e.g., rsync, cron, or third-party backup agents).
  • Explicitly state platform requirements and limitations at the top of the documentation, clarifying if the solution is Windows-only.
  • Provide guidance or links to Linux backup policy automation documentation for parity.
  • If the MARS agent is not available for Linux, suggest alternative Azure backup solutions that support Linux and provide automation examples for those.
  • Ensure future documentation covers both Windows and Linux scenarios, or clearly distinguishes platform-specific content.
GitHub Create Pull Request
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-10 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 system state backup policies with the MARS agent, which is a Windows-only tool. All instructions, examples, and referenced modules (e.g., MSOnlineBackup) are specific to Windows environments. There are no Linux shell or cross-platform examples, nor is there mention of equivalent Linux tooling or procedures.
Recommendations
  • Add equivalent Linux shell (bash) script examples for backup policy management, if supported.
  • Explicitly state platform limitations (e.g., if MARS agent and system state backup are Windows-only) at the top of the documentation.
  • Provide references or links to Linux backup solutions (such as Azure Backup for Linux or other supported agents) and their automation methods.
  • If cross-platform support is not available, clarify this and suggest alternative approaches for Linux users.
GitHub Create Pull Request
Backup Accidental Delete Protection for Azure Files ...b/main/articles/backup/soft-delete-azure-file-share.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing a 'Undelete File Share Script' that is a PowerShell script, without mentioning or providing equivalent Linux or cross-platform CLI examples. All script/tool references are Windows-centric, and there are no instructions or examples for Linux users (e.g., Bash, Azure CLI). This may hinder Linux administrators from following the guidance effectively.
Recommendations
  • Provide equivalent examples using Azure CLI or Bash scripts for undeleting file shares and other operations.
  • Explicitly mention cross-platform options and tools where PowerShell scripts are referenced.
  • Add instructions or links for Linux/macOS users to perform the same tasks, ensuring parity in guidance.
  • Where possible, present CLI examples before or alongside PowerShell scripts to avoid Windows-first bias.
GitHub Create Pull Request
Backup Soft delete for virtual machines ...b/main/articles/backup/soft-delete-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-10 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 and instructions, referencing Windows-centric tools (PowerShell cmdlets), and omitting equivalent examples for Linux users (such as Bash/CLI commands). The PowerShell section is given prominence after the Azure portal, with no mention of Linux shell usage or cross-platform CLI alternatives. This may disadvantage Linux administrators or those using non-Windows environments.
Recommendations
  • Add Azure CLI (az backup) examples for all operations (delete, undelete, resume backup) alongside PowerShell.
  • Explicitly mention that Azure CLI is cross-platform and provide Bash-friendly command snippets.
  • Clarify that PowerShell Core is available on Linux, but also offer native Bash/CLI instructions for parity.
  • Ensure REST API examples include sample curl commands for Linux users.
  • Review screenshots and UI instructions to ensure they are not Windows-specific, and note any OS-neutral aspects.
  • Consider a dedicated 'Linux/CLI' tab in the client selection section, parallel to PowerShell.
GitHub Create Pull Request
Backup Transport Layer Security in Azure Backup .../blob/main/articles/backup/transport-layer-security.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, with all configuration and verification steps described using Windows registry edits and references to Windows KB articles. There are no examples or guidance for enabling or verifying TLS 1.2 on Linux systems, nor are Linux tools or configuration patterns mentioned. The FAQ and related content also reference Windows-specific documentation and tools.
Recommendations
  • Add equivalent instructions for enabling and verifying TLS 1.2 on Linux systems, such as updating OpenSSL or configuring stunnel.
  • Include examples of how to check TLS protocol support on Linux (e.g., using openssl s_client or examining configuration files).
  • Reference Linux-specific documentation and best practices for TLS configuration.
  • Clarify whether Azure Backup supports Linux clients and, if so, provide parity in guidance for those platforms.
GitHub Create Pull Request
Backup Selective Disk Backup and Restore for Azure Virtual Machines .../main/articles/backup/selective-disk-backup-restore.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring selective disk backup and restore for Azure VMs. However, PowerShell (a Windows-centric tool) is given equal prominence to the CLI, and there are no explicit Linux shell (bash) script examples. Windows-specific tools and terminology (e.g., BitLocker, drive C) are mentioned before their Linux equivalents (e.g., dm-crypt, root filesystem). The documentation assumes familiarity with Windows patterns and does not provide Linux-specific command-line walkthroughs or troubleshooting steps beyond mentioning required utilities (lsblk, lsscsi).
Recommendations
  • Add explicit bash/shell script examples for Linux users, demonstrating equivalent operations to PowerShell (e.g., using az CLI in bash, scripting disk selection, etc.).
  • Where Windows-specific tools or terminology are mentioned (e.g., BitLocker, drive C), ensure Linux equivalents (e.g., dm-crypt, root filesystem) are described with equal detail and prominence.
  • Include troubleshooting steps and examples for common Linux distributions, such as how to install and verify lsblk and lsscsi, and how to interpret disk LUNs in Linux environments.
  • Clarify that PowerShell is cross-platform, but provide guidance for Linux users who may prefer bash or other shells.
  • Add screenshots or walkthroughs of the Azure portal experience from the perspective of a Linux VM, highlighting any differences or considerations.
GitHub Create Pull Request
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for soft delete operations using the Azure Portal and Azure PowerShell, with all command-line examples exclusively in PowerShell. There are no CLI or Linux-native examples, and PowerShell is presented as the only scripting interface, which may disadvantage Linux users or those preferring Bash/CLI workflows.
Recommendations
  • Add equivalent Azure CLI (az backup ...) examples for all PowerShell commands to support Linux and cross-platform users.
  • Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide links to relevant CLI documentation.
  • Where possible, include Bash script snippets or guidance for automating these operations on Linux systems.
  • Ensure that instructions do not assume a Windows environment (e.g., PowerShell), and clarify cross-platform compatibility for all tools.
  • Consider adding a 'Choose your platform' section that lists both PowerShell and CLI options side-by-side.
GitHub Create Pull Request
Backup Troubleshoot Azure Files backup .../blob/main/articles/backup/troubleshoot-azure-files.md
High Priority View Details →
Scanned: 2026-01-10 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 by referencing PowerShell scripts for key troubleshooting tasks (e.g., finding Recovery Services vaults, undeleting file shares), and by mentioning the 'Files portal' (which is typically accessed via Windows environments) as the primary GUI. There are no equivalent Bash, Azure CLI, or Linux-native instructions or scripts provided, nor is there mention of Linux tools or workflows for these operations.
Recommendations
  • Provide Azure CLI and Bash script equivalents for all referenced PowerShell scripts, and link to them alongside the PowerShell versions.
  • Explicitly mention that troubleshooting steps can be performed from Linux/macOS environments using Azure CLI, and provide example commands.
  • Where 'Files portal' is referenced, clarify that it is accessible from any OS via browser, and offer CLI alternatives for file share management.
  • Ensure that screenshots and instructions do not assume a Windows environment (e.g., avoid showing only Windows-style dialogs or PowerShell terminals).
  • Add a section or callouts for Linux administrators, highlighting any OS-specific considerations or tools.
GitHub Create Pull Request
Backup Tutorial - Back up Azure Database for PostgreSQL server ...lob/main/articles/backup/tutorial-postgresql-backup.md
High Priority View Details →
Scanned: 2026-01-10 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 primarily through the use of PowerShell scripts for privilege assignment, with no equivalent Linux shell (bash) or cross-platform CLI examples provided. PowerShell is mentioned as the main method for granting database privileges, and alternative Linux tools (such as bash scripts or psql commands) are referenced only as an afterthought. The documentation does not provide explicit Linux or macOS command-line examples, nor does it clarify how to perform these steps on non-Windows platforms.
Recommendations
  • Provide explicit bash/psql command examples for privilege assignment, alongside PowerShell scripts.
  • Include instructions for using Azure CLI and/or REST API for all steps, ensuring cross-platform compatibility.
  • Clearly state which steps are platform-agnostic and which require OS-specific tools, offering alternatives for each.
  • Add screenshots or walkthroughs for Linux/macOS environments where relevant.
  • Ensure that references to PowerShell are balanced with equivalent Linux/macOS tooling, and avoid implying PowerShell is the default or only option.
GitHub Create Pull Request
← Previous Page 23 of 65 Next →