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 326-350 of 1604 flagged pages
Backup Back up Azure Disks using Azure Data Protection REST API. ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-backup-disks.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 a mild Windows bias. In the 'Next steps' section, the order of restore options lists 'Azure portal' and 'Azure PowerShell' before 'Azure CLI', which is more commonly used on Linux and cross-platform environments. The only explicit reference to a platform-specific tool is PowerShell, with no mention of Bash or Linux-specific scripting. Additionally, the link for assigning permissions refers to a PowerShell-based documentation page ('backup-managed-disks-ps.md'), with no parallel Linux/Bash example or CLI-based instructions in the main flow. There are no explicit Linux examples or references to Linux tools or shell environments throughout the page.
Recommendations
  • Provide Azure CLI examples alongside or before PowerShell examples, especially for permission assignment and other management tasks.
  • Include references to Bash scripting or Linux shell environments where applicable, to demonstrate parity for Linux users.
  • Reorder the 'Next steps' section to list cross-platform tools (Azure CLI, REST API) before platform-specific tools (PowerShell), or group them together to avoid perceived prioritization.
  • Ensure all links to platform-specific instructions (e.g., PowerShell) are accompanied by equivalent CLI/Bash/Linux documentation links.
GitHub Create Pull Request
Backup Delete a Microsoft Azure Recovery Services vault ...blob/main/articles/backup/backup-azure-delete-vault.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a clear Windows bias. PowerShell is heavily featured, with detailed script examples and instructions, while Linux alternatives (such as Bash or cross-platform CLI) are limited or missing. Windows-specific tools (MARS, MABS, DPM, ARMClient via Chocolatey) are referenced without Linux equivalents or installation instructions. The order of presentation prioritizes Windows/PowerShell methods before CLI or ARM/REST approaches, and there is no mention of Linux-native management consoles or guidance for Linux users. The CLI section is brief, limited in scope, and does not provide parity with PowerShell functionality.
Recommendations
  • Provide Bash and cross-platform CLI examples for all operations, not just for Azure VM backups.
  • Include instructions for installing and using ARMClient on Linux (e.g., via npm or direct download), not just via Chocolatey.
  • Mention and document Linux-compatible backup agents or clarify if MARS/MABS/DPM are Windows-only, and suggest alternatives for Linux workloads.
  • Reorder sections so that cross-platform methods (CLI, REST API) are presented before or alongside Windows/PowerShell methods.
  • Add explicit notes or guidance for Linux users, including troubleshooting steps and supported tools.
  • Ensure all screenshots and management console instructions are platform-neutral or provide Linux equivalents where possible.
GitHub Create Pull Request
Backup Integrate Microsoft Defender's ransomware alerts to protect Azure Backup recovery points ...up-azure-integrate-microsoft-defender-using-logic-apps.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by focusing exclusively on Azure Virtual Machines (implicitly Windows-centric), referencing Microsoft Defender and Office 365 (Windows ecosystem tools), and omitting any mention of Linux VMs, Linux-compatible security solutions, or Linux-specific deployment/automation examples. All workflow steps, permissions, and screenshots assume Windows-based environments and tools, with no guidance for Linux users or cross-platform scenarios.
Recommendations
  • Explicitly state whether the solution supports Linux VMs and, if so, provide Linux-specific instructions or caveats.
  • Include examples and screenshots for Linux VM scenarios, such as integrating Defender for Cloud with Linux-based workloads.
  • Mention and provide alternatives for email alerting that do not rely solely on Office 365 (e.g., SMTP, SendGrid, or Linux-native mail solutions).
  • Clarify RBAC and role assignment steps for Linux administrators, including CLI (az, bash) examples alongside portal instructions.
  • Reference Defender for Cloud's Linux agent capabilities and provide links to documentation for onboarding Linux VMs.
  • Add troubleshooting notes for common Linux deployment issues (e.g., managed identity assignment, automation triggers).
GitHub Create Pull Request
Backup Prepare the DPM server to back up workloads .../main/articles/backup/backup-azure-dpm-introduction.md
High Priority View Details →
Scanned: 2026-01-11 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 is heavily focused on Windows environments, specifically System Center Data Protection Manager (DPM), which is a Windows-only product. All examples, prerequisites, and tooling references are for Windows (e.g., Windows PowerShell, .NET Framework, MARSAgentInstaller.exe). There are no Linux equivalents or examples, and Windows tools and patterns are mentioned exclusively and first throughout the page.
Recommendations
  • Clarify early in the documentation that DPM is a Windows-only solution and suggest alternatives for Linux workloads (e.g., Azure Backup for Linux, MARS agent for Linux, or other Azure-native backup solutions).
  • Where possible, provide links or references to documentation for backing up Linux workloads to Azure, including supported agents and procedures.
  • If any cross-platform backup scenarios exist (e.g., backing up Linux VMs via Azure Backup), include a section or callout with Linux-specific instructions and examples.
  • Avoid assuming Windows-only environments in general Azure Backup documentation; consider including a comparison table of backup options for Windows and Linux workloads.
  • Explicitly state the limitations regarding case-sensitive file systems and Linux file system features, and provide guidance for Linux administrators.
GitHub Create Pull Request
Backup Manage and monitor MARS Agent backups .../blob/main/articles/backup/backup-azure-manage-mars.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on the Microsoft Azure Recovery Services (MARS) Agent, which is a Windows-only backup solution. All instructions, screenshots, and tool references are specific to Windows environments (e.g., MARS management console, Windows file paths, and binaries). There are no examples, instructions, or even mentions of Linux or cross-platform equivalents. The documentation assumes the user is operating in a Windows environment throughout.
Recommendations
  • Explicitly state early in the documentation that MARS Agent is only supported on Windows, and provide links to equivalent Azure Backup solutions for Linux (such as Azure VM Backup or Azure Backup for Linux).
  • Where possible, add a comparison or table outlining backup options for both Windows and Linux, with links to relevant Linux documentation.
  • If any cross-platform or Linux support is planned or available via other Azure Backup agents, reference those agents and provide guidance for Linux users.
  • Avoid using only Windows-specific terminology (e.g., 'Actions pane', '%ProgramFiles%') without clarifying platform scope.
  • For parity, consider including a 'Linux support' or 'Alternatives for Linux' section to guide non-Windows users.
GitHub Create Pull Request
Backup Troubleshoot Azure Backup Server ...main/articles/backup/backup-azure-mabs-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-11 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 for troubleshooting Azure Backup Server is heavily oriented towards Windows environments. All examples, paths, registry keys, and troubleshooting steps reference Windows-specific tools, services, and file locations. There are no examples or guidance for Linux systems, nor any mention of Linux-compatible backup agents or troubleshooting steps. Windows tools and patterns (such as registry editing, Windows services, Control Panel, and Windows Server Backup) are referenced exclusively and often as the only method for resolving issues.
Recommendations
  • Add troubleshooting steps and examples for Linux-based servers, including supported backup agents and relevant commands.
  • Include Linux file paths and configuration locations where applicable, alongside Windows equivalents.
  • Provide parity in antivirus configuration guidance for popular Linux antivirus solutions (e.g., ClamAV, Sophos) and their exclusion patterns.
  • Reference Linux service management commands (systemctl, service) and equivalents for registry/configuration changes (e.g., config files, environment variables).
  • Clarify which features or troubleshooting steps are Windows-only, and offer alternatives or limitations for Linux users.
  • Add examples for Linux shell commands (bash, systemctl, etc.) where cmd or PowerShell commands are given for Windows.
GitHub Create Pull Request
Backup Manage and monitor Azure VM backups ...s/blob/main/articles/backup/backup-azure-manage-vms.md
High Priority View Details →
Scanned: 2026-01-11 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 page demonstrates a Windows bias in several ways. The section on reinstalling the VMSnapshot backup extension provides extensive, step-by-step instructions for Windows VMs, including PowerShell commands, registry edits, and use of Windows-specific tools (services.msc, regedit, command prompt). In contrast, the Linux instructions are minimal, only mentioning directory navigation and deletion, with no detailed guidance or troubleshooting. Throughout the page, examples and screenshots are Windows-centric, and Windows procedures are presented first and in greater detail, while Linux coverage is brief and lacks parity.
Recommendations
  • Provide equally detailed, step-by-step instructions for Linux VM extension management, including troubleshooting tips, relevant commands, and screenshots.
  • Include Linux-specific examples and commands (e.g., using Azure CLI, shell scripts) alongside or before Windows/PowerShell examples.
  • Balance the order of presentation so that Linux and Windows procedures are given equal prominence, or alternate which is presented first.
  • Mention Linux tools and patterns (such as systemctl, journalctl, or relevant log locations) where appropriate.
  • Add troubleshooting sections for Linux VMs similar to those provided for Windows, covering common issues and solutions.
  • Ensure screenshots and UI references include Linux VM scenarios where applicable.
GitHub Create Pull Request
Backup Use Azure Backup Server to back up workloads ...articles/backup/backup-azure-microsoft-azure-backup.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows-centric, with all installation and operational instructions assuming Windows Server as the platform. There are no Linux examples, nor is Linux mentioned as a supported platform. All tooling references (e.g., registry edits, PowerShell cmdlets, Windows Server Deduplication) are Windows-specific. The documentation does not provide parity for Linux administrators or environments.
Recommendations
  • Explicitly state platform support: If Linux is not supported, clarify this early in the documentation. If partial support exists, document limitations and alternatives.
  • Provide Linux parity: If possible, add instructions for deploying backup solutions on Linux servers, including supported workloads and configuration steps.
  • Include Linux tooling: Where PowerShell or Windows registry edits are referenced, provide equivalent Linux commands (e.g., shell scripts, configuration files) if supported.
  • Mention alternatives: If Azure Backup Server is Windows-only, suggest Azure-native backup solutions or third-party tools for Linux workloads.
  • Balance examples: When showing examples (e.g., VM creation, agent installation), include both Windows and Linux scenarios if supported.
  • Clarify prerequisites: Clearly list supported operating systems and platforms in a dedicated section, and provide guidance for mixed environments.
GitHub Create Pull Request
Backup Troubleshoot monitoring issues for Azure Backup ...n/articles/backup/backup-azure-monitor-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-11 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 references Windows-specific tools and patterns, such as Task Manager, Control Panel, Windows service names, and Windows file paths. There are no examples or troubleshooting steps provided for Linux environments or non-Windows Azure Backup agents, indicating a strong Windows bias.
Recommendations
  • Add equivalent troubleshooting steps for Linux environments, such as using systemctl or service commands to check and restart the relevant agent process.
  • Include Linux file path examples (e.g., /var/log/azure-backup/) for log inspection.
  • Mention cross-platform agent names and clarify if the instructions apply only to Windows or to both Windows and Linux.
  • Provide parity in examples and troubleshooting steps for both Windows and Linux users.
GitHub Create Pull Request
Backup How to move Azure Backup Recovery Services vaults ...es/backup/backup-azure-move-recovery-services-vault.md
High Priority View Details →
Scanned: 2026-01-11 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 page demonstrates a Windows bias in several ways. PowerShell is presented as the primary scripting method for moving Recovery Services vaults, with detailed cmdlet examples and no equivalent Bash or Linux shell scripting guidance. Windows-specific instructions (e.g., updating certificates via Windows Update) are given before Linux equivalents, and Windows tools (PowerShell cmdlets) are referenced more frequently and in greater detail than cross-platform or Linux-native alternatives. There is a lack of Linux-specific examples for scripting or automation, and no mention of Linux command-line tools (e.g., Bash scripts, shell commands) for resource management.
Recommendations
  • Provide equivalent Bash or shell script examples for moving Recovery Services vaults, using Azure CLI or REST API calls.
  • Include Linux-specific instructions and examples for certificate management, automation, and scripting, presented with equal prominence as Windows instructions.
  • Reference cross-platform tools (e.g., Azure CLI, REST API) before or alongside Windows-specific tools like PowerShell.
  • Add explicit guidance for Linux administrators, such as using cron jobs or shell scripts for automation, and clarify any differences in workflow or prerequisites for Linux environments.
  • Ensure all examples and instructions are tested and applicable on both Windows and Linux platforms, and indicate platform-specific steps where necessary.
GitHub Create Pull Request
Backup Overview of Recovery Services vaults ...ackup/backup-azure-recovery-services-vault-overview.md
High Priority View Details →
Scanned: 2026-01-11 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 mentioning Windows-centric backup solutions (System Center DPM, Windows Server, Azure Backup Server) prominently and providing specific next steps for backing up Windows Server, while lacking equivalent Linux examples or references to Linux backup tools. Linux is mentioned only in passing in the context of IaaS VMs, with no dedicated instructions or parity in examples.
Recommendations
  • Add explicit examples and guidance for backing up Linux servers, including links to relevant documentation and tools.
  • Ensure that Linux backup scenarios are mentioned alongside Windows scenarios, not only as a secondary note.
  • Include references to Linux-native backup agents or integration patterns, if available.
  • Provide parity in 'Next steps' by including instructions for backing up Linux servers (e.g., using Azure Backup for Linux VMs or other supported Linux workloads).
  • Review all mentions of backup tools to ensure Linux equivalents are listed where appropriate (e.g., not just System Center DPM and Windows Server).
GitHub Create Pull Request
Backup Private Endpoints Overview: Version 2 Experience ...icles/backup/backup-azure-private-endpoints-concept.md
High Priority View Details →
Scanned: 2026-01-11 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 repeatedly referencing Windows-specific backup tools (MARS agent, DPM, MABS) and scenarios, with no mention of Linux backup agents or Linux-specific configuration steps. All workload examples focus on SQL Server and SAP HANA in Azure VMs, which can run on Linux, but the backup tooling described is Windows-centric. There are no Linux command-line examples, nor is there guidance for Linux-based backup agents or integration patterns.
Recommendations
  • Include examples and guidance for Linux-based backup scenarios, such as using Azure Backup for Linux VMs and workloads.
  • Mention and document Linux-compatible backup agents or integration methods, if available.
  • Provide parity in instructions for configuring private endpoints from Linux environments (e.g., using CLI, shell scripts, or Linux-native tools).
  • Clarify whether MARS agent, DPM, and MABS are Windows-only, and suggest alternatives for Linux users.
  • Add explicit Linux VM backup and restore walkthroughs, including DNS and network configuration steps relevant to Linux.
  • Ensure diagrams and workflow descriptions do not imply Windows-only environments.
GitHub Create Pull Request
Backup Troubleshoot System Center Data Protection Manager .../articles/backup/backup-azure-scdpm-troubleshooting.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on System Center Data Protection Manager (DPM), a Windows-only product. All troubleshooting steps assume a Windows environment, referencing Windows services (e.g., net stop/start dpmra), NT AUTHORITY\SYSTEM, and command prompt usage. There are no Linux-specific examples, tools, or troubleshooting steps, and no mention of Linux equivalents or cross-platform considerations.
Recommendations
  • Clearly state that DPM is a Windows-only product at the beginning of the documentation.
  • If Azure Backup Server or related services have Linux support, provide troubleshooting steps and examples for Linux environments.
  • Include Linux command equivalents or alternative procedures where possible (e.g., service management, agent installation).
  • Mention Linux backup solutions or integration points if relevant, and provide links to their documentation.
  • Avoid assuming Windows-only terminology (e.g., NT AUTHORITY\SYSTEM, command prompt) without clarifying platform limitations.
GitHub Create Pull Request
Backup Back up Windows system state to Azure using Azure Backup ...blob/main/articles/backup/backup-azure-system-state.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is exclusively focused on backing up Windows Server system state using Azure Backup. All examples, instructions, screenshots, and tool references are Windows-specific (e.g., MARS Agent, SFC command, Windows Server versions). There is no mention of Linux systems, Linux backup tools, or cross-platform alternatives. The documentation assumes the user is running Windows and does not provide parity for Linux environments.
Recommendations
  • Add a section or a separate article for backing up Linux system state or equivalent data to Azure using Azure Backup.
  • Provide Linux-specific instructions, examples, and screenshots, including relevant tools (e.g., Azure Backup agent for Linux, CLI commands).
  • Mention Linux support (or lack thereof) explicitly, so users are aware of platform limitations.
  • If Azure Backup does not support Linux system state backup, suggest alternative Azure solutions for Linux backup and link to relevant documentation.
  • Ensure future documentation covers both Windows and Linux scenarios, presenting them with equal prominence.
GitHub Create Pull Request
Backup Restore System State to a Windows Server ...n/articles/backup/backup-azure-restore-system-state.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is exclusively focused on restoring System State for Windows Server, using Windows-specific tools such as the Microsoft Azure Recovery Services (MARS) agent, Windows Server Backup snap-in, and wbadmin command-line utility. All instructions, screenshots, and examples are tailored to Windows environments, with no mention of Linux equivalents, cross-platform tools, or parity for Linux-based servers. The documentation assumes the reader is operating within a Windows ecosystem and does not provide guidance for Linux system state recovery or backup restoration.
Recommendations
  • Add a section or a separate article for restoring system state or equivalent on Linux servers, including supported backup agents and recovery workflows.
  • Include Linux-specific examples, such as using Azure Backup for Linux VMs, and reference Linux tools (e.g., rsync, tar, Timeshift, or Azure CLI commands for Linux VM restore).
  • Clarify early in the documentation that the instructions are Windows-specific, and provide links to Linux documentation for similar scenarios.
  • Where possible, mention cross-platform Azure backup and restore capabilities, and provide parity in troubleshooting steps for Linux environments.
  • Ensure that future documentation for backup and restore covers both Windows and Linux platforms, or clearly distinguishes platform-specific instructions.
GitHub Create Pull Request
Backup Back up SQL Server databases to Azure ...blob/main/articles/backup/backup-azure-sql-database.md
High Priority View Details →
Scanned: 2026-01-11 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 page exhibits a strong Windows bias. All instructions, examples, and tooling references are exclusively for Windows environments. The backup extension is named AzureBackupWindowsWorkload, permissions are managed using Windows service accounts (NT SERVICE\AzureWLBackupPluginSvc, NT AUTHORITY\SYSTEM), and all walkthroughs use SQL Server Management Studio (SSMS) and PowerShell scripts. There is no mention of Linux-based SQL Server VMs, nor any guidance for Linux authentication, file paths, or command-line tools. Even file path examples and configuration steps use Windows conventions (e.g., C:\Program Files, E:\LocalBackup), and SMB share configuration is shown only with PowerShell.
Recommendations
  • Add explicit instructions and examples for SQL Server running on Linux-based Azure VMs, including authentication, permissions, and service account management.
  • Provide Linux equivalents for file paths, configuration files, and backup storage locations (e.g., /var/opt/mssql/backups).
  • Include command-line examples using Bash, sqlcmd, and Linux utilities for permission management and backup configuration.
  • Clarify whether the AzureBackupWindowsWorkload extension is available or supported on Linux, or provide details about the Linux equivalent.
  • Offer parity in automation scripts, e.g., Bash or Python scripts for Linux environments.
  • Mention any differences or limitations for Linux-based SQL Server VMs in the support matrix and feature considerations.
GitHub Create Pull Request
Backup Restore SQL server databases in Azure VMs using Azure Backup via CLI ...b/main/articles/backup/backup-azure-sql-restore-cli.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page consistently assumes the use of SQL Server on Azure VMs, which are typically Windows-based, and does not provide any examples or guidance for restoring databases on Linux-based SQL Server VMs. All references to SQL Server instances, server names, and database names use Windows conventions (e.g., MSSQLSERVER, master), and there is no mention of Linux-specific considerations, such as file paths, SQL Server on Linux, or differences in restore procedures. The CLI examples and explanations do not address Linux scenarios, nor do they clarify whether the steps are applicable to SQL Server on Linux VMs.
Recommendations
  • Add explicit guidance and examples for restoring SQL Server databases on Linux-based Azure VMs, including any differences in file paths, permissions, or restore procedures.
  • Clarify whether the documented CLI commands and parameters are applicable to both Windows and Linux SQL Server VMs, and note any platform-specific limitations.
  • Include Linux-specific SQL Server instance names and database paths in examples (e.g., /var/opt/mssql/data for file restores).
  • Mention prerequisites or configuration steps unique to SQL Server on Linux, such as ensuring the SQL Server service account has access to restored files.
  • Add a section or note highlighting cross-platform support and any differences users should be aware of when restoring to Linux VMs.
GitHub Create Pull Request
Backup Troubleshoot System State Backup ...icles/backup/backup-azure-system-state-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-11 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 is heavily focused on Windows environments, with all examples, troubleshooting steps, and tool references specific to Windows Server, PowerShell, and Windows system utilities. There are no Linux equivalents or cross-platform considerations, and Windows terminology and tools are used exclusively and presented first throughout the page.
Recommendations
  • If System State Backup is only supported on Windows, clearly state this limitation at the top and consider linking to equivalent Linux backup documentation for parity.
  • Where possible, provide troubleshooting steps or backup strategies for Linux servers, or reference Azure Backup documentation for Linux.
  • Include examples for Linux environments (e.g., using Azure CLI, shell commands, or Linux backup tools) if/when support is available.
  • Avoid using Windows-specific terminology (e.g., PowerShell, Server Manager) without noting alternatives or limitations for non-Windows users.
  • Add a section explicitly addressing cross-platform backup and recovery options, including links to Linux documentation.
GitHub Create Pull Request
Backup Troubleshoot slow backup of files and folders ...ackup-azure-troubleshoot-slow-backup-performance-issue.md
High Priority View Details →
Scanned: 2026-01-11 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 tools (such as Performance Monitor), providing troubleshooting steps and log file paths specific to Windows, and discussing issues in the context of Windows systems and the MARS agent. There are no examples, tools, or troubleshooting guidance for Linux systems or agents, nor any mention of Linux equivalents or parity.
Recommendations
  • Add troubleshooting steps and examples for Linux systems, including relevant log file locations and commands.
  • Reference Linux performance monitoring tools (such as top, iostat, vmstat, sar) alongside Windows Performance Monitor.
  • Clarify whether the guidance applies only to Windows or also to Linux, and provide parity where possible.
  • Include information about the Azure Backup agent or MARS agent availability and behavior on Linux systems.
  • Provide Linux-specific recommendations for antivirus/process interference and disk optimization.
GitHub Create Pull Request
Backup About agentless multi-disk crash-consistent backup for Azure Virtual Machines by using Azure Backup ...ure-vms-agentless-multi-disk-crash-consistent-overview.md
High Priority View Details →
Scanned: 2026-01-11 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-first bias by mentioning Windows backup mechanisms (VSS) before Linux equivalents (fsfreeze), and by linking only to Windows-specific VM Agent and snapshot extension documentation. There are no Linux-specific examples, links, or tool references provided, and Linux patterns (such as pre/post scripts) are only mentioned in passing as a reason not to use crash-consistent backups.
Recommendations
  • Provide equal coverage for Linux by including links to Linux VM Agent and snapshot extension documentation.
  • Add Linux-specific examples or scenarios, such as how crash-consistent backup interacts with common Linux workloads.
  • Mention Linux tools and patterns (e.g., fsfreeze, pre/post scripts) in parallel with Windows tools, not only as exceptions.
  • Ensure that references to backup mechanisms (VSS for Windows, fsfreeze for Linux) are presented with equal detail and prominence.
  • Include guidance or references for Linux users who want agentless backups, similar to what is provided for Windows.
GitHub Create Pull Request
Backup Troubleshoot Azure VM file recovery ...s/backup/backup-azure-vm-file-recovery-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows troubleshooting steps and tools (such as File Explorer, Server Manager, Disk Management, ISCSI initiator Properties) are described in detail with screenshots and step-by-step instructions, while Linux troubleshooting is often referenced via links to other documentation or given minimal explanation. Windows examples and solutions are frequently presented before Linux equivalents, and some error scenarios provide only Windows-centric guidance. There is a lack of parity in the depth and clarity of Linux instructions, with Linux steps often summarized or omitted.
Recommendations
  • Provide equally detailed, step-by-step instructions for Linux scenarios, including screenshots of relevant Linux tools (e.g., GNOME Disks, lsblk output, mount commands).
  • Include Linux command-line equivalents for all Windows GUI actions (e.g., how to manually mount/unmount disks, change volume labels, check disk status).
  • Present troubleshooting steps for both Windows and Linux in parallel, rather than listing Windows first or in greater detail.
  • Add examples for common Linux distributions (e.g., Ubuntu, CentOS) where appropriate, not just SUSE.
  • Ensure error messages and their resolutions are covered for both platforms, with clear guidance for Linux users.
  • Reference Linux-specific tools (e.g., mdadm, lvm, parted, gnome-disks) where Windows tools are mentioned.
GitHub Create Pull Request
Backup About Azure VM backup .../main/articles/backup/backup-azure-vms-introduction.md
High Priority View Details →
Scanned: 2026-01-11 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 page demonstrates a Windows bias in several ways: Windows-specific tools (VSS) and patterns are mentioned first and in more detail, PowerShell is referenced for restore operations without equivalent Linux CLI examples, and Windows backup mechanisms are described with more guidance than Linux (which is relegated to 'write your own scripts'). Linux instructions are less detailed and lack concrete examples, while Windows instructions reference built-in tooling and provide more actionable information.
Recommendations
  • Provide Linux CLI (az CLI, Bash) examples for backup and restore operations alongside PowerShell examples.
  • Offer more detailed guidance and sample scripts for Linux app-consistent backups, including common scenarios (e.g., MySQL, PostgreSQL).
  • Mention Linux tools (e.g., fsfreeze) with the same prominence and detail as Windows tools (VSS), and clarify their usage with step-by-step instructions.
  • Ensure that both Windows and Linux procedures are described with equal depth and clarity, including troubleshooting and best practices.
  • Avoid listing Windows-specific tools or procedures before Linux equivalents; present both platforms in parallel or in separate, equally detailed sections.
GitHub Create Pull Request
Backup Overview of Backup center for Azure Backup and Azure Site Recovery ...cs/blob/main/articles/backup/backup-center-overview.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 Tools Missing Linux Example
Summary
The documentation page mentions sample PowerShell scripts and Microsoft Database Backup scripts as resources for automated deployments, but does not mention or provide parity for Linux-native tools or scripting examples (e.g., Bash, shell scripts). There are no explicit Linux or cross-platform CLI examples, and Windows-centric tools are referenced without equivalent Linux alternatives.
Recommendations
  • Include sample Bash or shell scripts alongside PowerShell examples for backup automation.
  • Explicitly mention Azure CLI commands as cross-platform alternatives to PowerShell scripts.
  • Reference Linux-native backup tools or patterns where applicable, or clarify that the provided scripts are cross-platform.
  • Add examples or links for Linux administrators to perform common backup tasks using their preferred tools.
  • Ensure that documentation for automated deployments and scripting covers both Windows and Linux environments equally.
GitHub Create Pull Request
Backup Encryption in Azure Backup ...re-docs/blob/main/articles/backup/backup-encryption.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. In the section describing Azure Disk Encryption (ADE), BitLocker (Windows tool) is mentioned before DM-Crypt (Linux tool), and the overall explanation gives more detail about Windows-specific technologies (BitLocker, TDE for SQL Server) than their Linux equivalents. The SQL Server example is Windows-centric, with no mention of Linux-based database backup scenarios or tools. There are no Linux command-line examples or references to Linux backup patterns.
Recommendations
  • Present Linux and Windows encryption tools (BitLocker, DM-Crypt) in parallel, with equal detail and prominence.
  • Include examples or references for Linux-based database backup and restore workflows, such as PostgreSQL or MySQL.
  • Add sample commands or scripts for both Windows (PowerShell) and Linux (bash/CLI) environments where relevant.
  • Explicitly mention support and considerations for Linux workloads in backup and encryption scenarios.
  • Ensure documentation links and next steps include Linux-specific resources where applicable.
GitHub Create Pull Request
Backup Use Modern Backup Storage with Azure Backup Server ...s/blob/main/articles/backup/backup-mabs-add-storage.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows-centric, with all instructions, screenshots, and tooling (Server Manager, PowerShell cmdlets, ReFS filesystem) focused exclusively on Windows Server environments. There are no Linux equivalents, examples, or mentions, and Windows tools and patterns are presented as the only supported or recommended approach.
Recommendations
  • Clarify in the introduction whether Modern Backup Storage and Azure Backup Server are supported or unsupported on Linux, and if not, provide guidance for Linux users.
  • If Linux support exists or is planned, add equivalent instructions and examples for Linux environments, including CLI commands, filesystems, and storage management tools.
  • Where PowerShell is used, offer alternative commands for Linux (e.g., Bash scripts, Azure CLI) if applicable.
  • Explicitly state OS requirements and limitations early in the documentation to set expectations for non-Windows users.
  • If only Windows is supported, consider linking to alternative backup solutions for Linux environments.
GitHub Create Pull Request
← Previous Page 14 of 65 Next →