Backup

755
Total Pages
562
Linux-Friendly Pages
193
Pages with Bias
25.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

520 issues found
Showing 376-400 of 520 flagged pages
Backup Overview of Azure Database for PostgreSQL Backup ...es/backup/backup-azure-database-postgresql-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias by exclusively recommending and illustrating the use of the pgAdmin GUI tool for database privilege management and user creation, without mentioning or providing examples for Linux-native alternatives (such as psql CLI or other Linux tools). All screenshots and workflow descriptions are based on GUI interactions, which are more common in Windows environments. There are no explicit Linux/macOS command-line examples or references to Linux-specific workflows, even though PostgreSQL is widely used on Linux. The order of presentation and tool selection implicitly prioritizes Windows patterns.
Recommendations
  • Add equivalent instructions and examples for Linux/macOS users, such as using the psql command-line tool to manage privileges and users.
  • Provide CLI commands for privilege grants and user creation, alongside GUI instructions.
  • Mention and link to Linux-native tools (e.g., psql, DBeaver) and clarify that the process is platform-agnostic.
  • Include screenshots or terminal output from Linux environments where relevant.
  • Explicitly state that the backup and restore process can be performed from any OS with PostgreSQL tools installed.
GitHub Create Pull Request
Backup Back Up Azure Database for PostgreSQL by Using the Azure Portal ...in/articles/backup/backup-azure-database-postgresql.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: environment variable configuration is described only using Windows Control Panel screenshots and instructions; PowerShell scripts are emphasized for privilege assignment, with no Linux/macOS shell equivalents; references to tools and workflows (e.g., setting PATH, running scripts) are Windows-centric; Linux/macOS alternatives (e.g., bash, environment variable setting, shell script usage) are not shown or are mentioned only in passing.
Recommendations
  • Add explicit Linux/macOS instructions for setting environment variables (e.g., using export in bash/zsh).
  • Provide shell script equivalents for the PowerShell script, or clarify how Linux/macOS users should grant privileges.
  • Include screenshots or terminal examples for Linux/macOS environments alongside Windows images.
  • Clarify that the PSQL tool is cross-platform and show how to install and use it on Linux/macOS.
  • Avoid assuming Windows as the default platform; present platform-agnostic steps first, or in parallel.
GitHub Create Pull Request
Backup Troubleshoot encrypted Azure VM backup errors ...icles/backup/backup-azure-encrypted-vm-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Troubleshooting steps reference PowerShell as the only CLI example for configuring permissions, without mentioning Linux/macOS equivalents (such as Azure CLI or Bash). No Linux-specific tools or commands are provided, and PowerShell is mentioned before any cross-platform alternatives. This may cause friction for Linux/macOS users attempting to follow automation or scripting steps.
Recommendations
  • Add Azure CLI and Bash examples for all automation steps, especially for permission configuration.
  • Explicitly mention that PowerShell commands are Windows-specific and provide cross-platform alternatives.
  • Ensure that references to tools and scripts are platform-neutral or include both Windows and Linux/macOS options.
  • Review linked pages to ensure Linux parity in step-by-step instructions.
GitHub Create Pull Request
Backup Delete a Microsoft Azure Recovery Services vault ...blob/main/articles/backup/backup-azure-delete-vault.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is the primary automation example, with detailed scripts and commands provided, while Linux/macOS alternatives (such as Bash or cross-platform scripting) are absent. Windows-specific tools like MARS, MABS, DPM, and ARMClient (installed via Chocolatey) are referenced exclusively, with no mention of Linux equivalents or installation methods. The CLI section is limited in scope and does not provide parity with PowerShell. In most cases, Windows-centric instructions and tools are presented first or exclusively, leaving Linux/macOS users with limited guidance.
Recommendations
  • Provide Bash or cross-platform shell script examples for vault deletion and dependency removal, especially for automation.
  • Reference installation and usage of ARMClient and other tools on Linux/macOS (e.g., via Homebrew, direct download, or .NET Core).
  • Clarify which tools (MARS, MABS, DPM) are Windows-only and suggest alternatives or note limitations for Linux/macOS users.
  • Expand the Azure CLI section to cover more scenarios, or note its limitations and suggest REST API or SDK usage for Linux/macOS users.
  • Ensure that examples and instructions are presented in a platform-neutral order, or explicitly call out platform differences.
GitHub Create Pull Request
Backup Manage and monitor Azure VM backups ...s/blob/main/articles/backup/backup-azure-manage-vms.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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, particularly in the section on reinstalling the VMSnapshot backup extension. The Windows instructions are extensive, detailed, and use Windows-specific tools (PowerShell, Registry Editor, Services, Command Prompt), while the Linux instructions are brief and less detailed. Windows examples and screenshots dominate, and Windows procedures are described first and in greater depth.
Recommendations
  • Expand the Linux section to provide step-by-step instructions comparable to the Windows section, including troubleshooting tips, screenshots, and explanations of relevant Linux tools and commands.
  • Include parity in example depth: for Linux, describe how to check extension status, restart the Linux Azure Guest Agent, and verify successful reinstallation.
  • Where PowerShell is used for Windows, provide Azure CLI or Bash alternatives for Linux/macOS users.
  • Balance the order of presentation: alternate or parallelize Windows and Linux instructions, or clearly label each section for platform-specific guidance.
  • Add notes or links for cross-platform differences, and clarify which steps are OS-specific.
GitHub Create Pull Request
Backup How to move Azure Backup Recovery Services vaults ...es/backup/backup-azure-move-recovery-services-vault.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented as the primary scripting example for moving Recovery Services vaults, with detailed cmdlet usage and confirmation steps. Windows-specific instructions (such as updating Windows certificates) are given before Linux equivalents, and Windows tools (PowerShell) are referenced more prominently than cross-platform alternatives. While Azure CLI is mentioned, it receives less detail and is presented after PowerShell. There are no Linux/macOS-specific examples or guidance for shell scripting, nor are there references to Linux-native tools.
Recommendations
  • Provide Linux/macOS-specific examples, such as Bash scripts using Azure CLI.
  • Present Azure CLI examples before or alongside PowerShell to emphasize cross-platform support.
  • Include explicit instructions for Linux/macOS users, such as how to install and use Azure CLI.
  • Clarify that all CLI commands work on Linux/macOS and Windows equally.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., authentication, environment setup).
GitHub Create Pull Request
Backup Private Endpoints Overview: Version 2 Experience ...icles/backup/backup-azure-private-endpoints-concept.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page repeatedly references Windows-centric backup tools (MARS agent, DPM, MABS) and scenarios, with no mention of Linux-specific backup agents or guidance for Linux VMs. Examples and recommendations focus on Windows workloads and tools, and the order of presentation prioritizes Windows solutions. There are no explicit Linux/macOS command-line examples or instructions, and the documentation does not address how Linux users should configure or interact with private endpoints for Azure Backup.
Recommendations
  • Include explicit guidance for Linux VM backup scenarios, such as using Azure Backup for Linux workloads.
  • Add examples and instructions for configuring private endpoints from Linux environments (e.g., using Azure CLI, shell commands).
  • Mention Linux-compatible backup agents or extensions, if available, and clarify support for Linux workloads.
  • Present both Windows and Linux scenarios in parallel, or alternate the order to avoid Windows-first bias.
  • Provide troubleshooting steps or considerations specific to Linux/macOS environments.
GitHub Create Pull Request
Backup Overview of Recovery Services vaults ...ackup/backup-azure-recovery-services-vault-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-centric backup tools (System Center DPM, Windows Server, Azure Backup Server) and provides a 'Back up a Windows Server' link in the Next Steps section, while omitting equivalent Linux backup examples or tools. Windows workloads and management patterns are mentioned first or exclusively, with little explicit guidance for Linux users.
Recommendations
  • Add explicit examples and links for backing up Linux servers and workloads, such as 'Back up a Linux Server' or guidance for Linux VMs.
  • Mention Linux-compatible backup tools and processes alongside Windows tools (e.g., clarify support for Linux workloads in System Center DPM or alternatives).
  • Ensure parity in Next Steps by including Linux-specific articles and instructions.
  • Where Windows-specific features or agents are referenced, clarify Linux support or alternatives.
GitHub Create Pull Request
Backup Recover files and folders from Azure VM backup .../articles/backup/backup-azure-restore-files-from-vm.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions and tools (e.g., registry edits, File Explorer, drive letters) are described in greater detail and are presented before Linux equivalents. Windows-specific troubleshooting (registry changes) is covered extensively, while Linux troubleshooting is less detailed. The 'Next steps' section highlights PowerShell before Azure CLI, and Windows terminology (e.g., 'Download Executable') is used more prominently than Linux ('Download Script'). Linux examples are present but sometimes less thorough, and some advanced Linux scenarios (LVM/RAID) require manual intervention without step-by-step parity to Windows.
Recommendations
  • Present Windows and Linux instructions in parallel sections, with equal detail and prominence.
  • Provide Linux troubleshooting steps with the same depth as Windows (e.g., registry edits vs. Linux config changes).
  • Include Linux-specific screenshots and walkthroughs for each major step, matching the Windows visuals.
  • List Azure CLI instructions before or alongside PowerShell in 'Next steps', and clarify parity.
  • Avoid Windows-centric terminology (e.g., 'Download Executable') as the default; use neutral phrasing.
  • Expand Linux advanced scenarios (LVM/RAID) with step-by-step guides and troubleshooting tips.
GitHub Create Pull Request
Backup Troubleshoot Azure Backup failures caused by agent or extension issues ...up-azure-troubleshoot-vm-backup-fails-snapshot-timeout.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools (services.msc, Event Viewer, Control Panel, regsvr32.exe, Visual C++ Redistributable, AppLocker) are mentioned and illustrated in detail, often with screenshots, while Linux troubleshooting steps are less detailed and lack equivalent visual aids. Windows instructions and examples frequently appear before Linux ones, and PowerShell is referenced as the primary CLI tool for backup job management. Some troubleshooting steps (e.g., antivirus exclusions, COM+/MSDTC, VSS writer) are Windows-only, with no Linux equivalents or clarifications. Linux instructions are present but less comprehensive, and some sections lack parity in example depth or tool references.
Recommendations
  • Provide Linux-specific troubleshooting screenshots and step-by-step instructions, matching the detail given for Windows (e.g., using systemctl, journalctl, log file locations, package managers).
  • Include Linux equivalents for Windows tools (e.g., show how to check agent status with systemctl, review logs with tail/cat/journalctl, manage extensions via CLI).
  • List Linux steps/examples before or alongside Windows ones to avoid 'Windows-first' ordering.
  • Reference Linux command-line tools (bash, Azure CLI) equally with PowerShell, and provide CLI examples for both platforms.
  • Clarify which troubleshooting steps are Windows-only and provide Linux alternatives or explicitly state when a step is not applicable to Linux.
  • Add guidance for common Linux-specific issues (e.g., SELinux/AppArmor blocking extensions, package dependency troubleshooting, systemd service management).
GitHub Create Pull Request
Backup Back Up Azure VMs with the Enhanced Policy ...in/articles/backup/backup-azure-vms-enhanced-policy.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for configuring Enhanced backup policies, with step-by-step cmdlets and explanations. The Azure CLI section is present and reasonably complete, but the PowerShell instructions are much more extensive and appear before CLI examples. There are no explicit Linux/macOS shell examples (e.g., Bash), nor are there notes about platform-specific differences or requirements for Linux users. The documentation implicitly assumes familiarity with PowerShell, which is primarily a Windows tool, and does not address Linux-specific considerations.
Recommendations
  • Add Bash shell examples for Azure CLI commands, including variable usage and JSON file creation for policy definitions.
  • Explicitly mention that Azure CLI works cross-platform and provide guidance for Linux/macOS users, such as prerequisites and environment setup.
  • Balance the depth of PowerShell and CLI sections, ensuring CLI instructions are as detailed and explanatory as PowerShell ones.
  • Add notes about PowerShell Core availability on Linux/macOS if relevant, or clarify if any PowerShell cmdlets are Windows-only.
  • Consider listing CLI instructions before PowerShell to reduce Windows-first impression.
GitHub Create Pull Request
Backup Troubleshoot Azure VM file recovery ...s/backup/backup-azure-vm-file-recovery-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 moderate Windows bias. Troubleshooting steps and UI walkthroughs for Windows (e.g., Server Manager, Disk Management, ISCSI initiator Properties) are detailed with screenshots and step-by-step instructions, while Linux guidance is often limited to external links or brief command-line references. Windows solutions are frequently presented first and in greater detail, whereas Linux instructions are less comprehensive and sometimes refer users to other documentation. Some troubleshooting scenarios are described only for Windows, with Linux equivalents missing or less explicit.
Recommendations
  • Provide step-by-step Linux troubleshooting instructions equivalent to Windows sections, including screenshots of Linux tools (e.g., GNOME Disks, lsblk output, iSCSI management via open-iscsi).
  • Include Linux-specific error messages and their resolutions directly in the document, not just via external links.
  • Balance the order of presentation so that Linux and Windows guidance are given equal prominence, or alternate which OS is presented first.
  • Add examples for common Linux desktop environments (e.g., Ubuntu, CentOS) and clarify differences for various distributions.
  • Where Windows GUI tools are referenced, provide Linux CLI and GUI alternatives (e.g., for mounting/unmounting disks, managing iSCSI sessions).
GitHub Create Pull Request
Backup Move VM backup - standard to enhanced policy in Azure Backup ...cles/backup/backup-azure-vm-migrate-enhanced-policy.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation primarily describes how to migrate Azure VM backups from standard to enhanced policy using the Azure Portal, with only a brief mention of Azure CLI and PowerShell in a note. There are no explicit CLI or PowerShell command examples, nor are Linux/macOS-specific instructions or screenshots provided. The portal-based workflow is platform-neutral but the lack of CLI examples disadvantages Linux users who may prefer or require command-line automation.
Recommendations
  • Provide explicit CLI examples for the migration process, including full command syntax and sample output.
  • Include PowerShell and Azure CLI instructions in dedicated sections, with clear notes on platform compatibility (Windows, Linux, macOS).
  • Add screenshots or terminal output for CLI steps on both Windows and Linux/macOS.
  • Ensure that references to PowerShell and CLI are given equal prominence as portal instructions, not relegated to notes.
GitHub Create Pull Request
Backup Back Up and Restore Encrypted Azure VMs ...ob/main/articles/backup/backup-azure-vms-encryption.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation generally addresses both Windows and Linux Azure VMs, but there is a subtle Windows bias. Windows technologies (BitLocker, PowerShell) are mentioned first or exclusively in some sections. For example, the PowerShell command to identify a VM's associated key vault is given, but no Linux equivalent (such as Azure CLI or Bash) is provided. Encryption tooling is described with Windows (BitLocker) before Linux (dm-crypt), and PowerShell is referenced for automation and access policy configuration, with Azure CLI only mentioned later. No explicit Linux command-line examples are provided.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell commands, especially for tasks like identifying the key vault associated with a VM.
  • When describing encryption tooling, alternate the order or give equal prominence to Linux (dm-crypt) and Windows (BitLocker).
  • Ensure that automation and scripting instructions are available for both Windows (PowerShell) and Linux/macOS (Azure CLI, Bash).
  • Add explicit Linux/macOS instructions or screenshots where relevant, not just generic references.
GitHub Create Pull Request
Backup Troubleshoot backup errors with Azure VMs .../main/articles/backup/backup-azure-vms-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 notable Windows bias. Many troubleshooting steps and examples reference Windows-specific tools (Event Viewer, Services.msc, Registry Editor, VSS, BitLocker, Visual C++ Redistributable, MSIEXEC), and provide command-line instructions primarily for Windows (cmd, regedit, net start/stop, icacls). PowerShell is mentioned for restore operations, with no equivalent Bash or CLI examples for Linux. Windows solutions and terminology often appear before or instead of Linux alternatives. Linux troubleshooting is present but less detailed, and some error resolutions lack Linux-specific guidance.
Recommendations
  • Provide equivalent Linux commands and troubleshooting steps wherever Windows tools (Event Viewer, Services.msc, Registry Editor, VSS, BitLocker, MSIEXEC, icacls) are referenced.
  • Include Bash/Azure CLI examples alongside PowerShell for restore and backup operations.
  • Ensure Linux-specific error codes and solutions are as detailed as Windows ones, especially for extension failures and agent installation/validation.
  • Present Windows and Linux instructions in parallel sections, or clearly label them to avoid confusion.
  • Reference Linux tools (journalctl, systemctl, dmesg, etc.) for log and service management.
  • Add troubleshooting steps for common Linux backup/restore issues, such as SELinux, file system permissions, and agent failures.
GitHub Create Pull Request
Backup Azure Instant Restore Capability ...n/articles/backup/backup-instant-restore-capability.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides configuration instructions for Instant Restore snapshot retention using the Azure portal and PowerShell, but does not mention or provide examples for Linux/macOS users (e.g., Azure CLI or REST API). PowerShell is Windows-centric and is presented as the only scripting option, creating friction for non-Windows users. The examples and tooling references are Windows-first, with no Linux parity.
Recommendations
  • Add equivalent Azure CLI examples for configuring snapshot retention, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention REST API options for advanced users who may not use PowerShell or the portal.
  • Explicitly state that PowerShell examples are applicable on Linux/macOS if using PowerShell Core, or clarify platform requirements.
  • Present cross-platform tools (Azure CLI, REST API) before or alongside PowerShell to avoid Windows-first bias.
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
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions sample PowerShell scripts as a primary automation resource and lists them before CLI commands and other script types. There are no explicit Linux/macOS examples, nor are Bash or shell scripts referenced. The focus on PowerShell and lack of Linux-specific guidance may create friction for non-Windows users.
Recommendations
  • Include Bash and shell script samples alongside PowerShell scripts in the Community Hub resources.
  • Explicitly mention Azure CLI usage for automation and provide examples for Linux/macOS environments.
  • Ensure that automation and scripting guidance is platform-neutral or provides parity for Linux/macOS users.
  • Add notes clarifying cross-platform support for all tools and scripts referenced.
GitHub Create Pull Request
Backup Support matrix for Backup center for Azure Backup ...b/main/articles/backup/backup-center-support-matrix.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page lists supported workloads and scenarios for Azure Backup Center, with a notable emphasis on Windows-centric technologies. Windows-based workloads (such as Azure Virtual Machine, SQL in Azure VM, SAP HANA in Azure VM) are consistently listed first in tables and examples. Additionally, Windows-specific backup tools like System Center Data Protection Manager, Azure Backup Agent (MARS), and Azure Backup Server (MABS) are mentioned in the 'Insights' section, while Linux/macOS equivalents or considerations are absent. There are no explicit Linux examples or references to Linux-specific backup agents or workloads, and the documentation does not address cross-platform usage or parity.
Recommendations
  • Include Linux workloads (e.g., Linux VMs, Linux databases) in supported scenarios and examples.
  • Add references to Linux-compatible backup agents and tools, if available.
  • Ensure that examples and workload lists alternate or balance Windows and Linux technologies, rather than listing Windows first.
  • Provide guidance or links for Linux/macOS users on how to use Backup Center with their environments.
  • Clarify any limitations or differences for Linux/macOS users in the support matrix.
GitHub Create Pull Request
Backup Enable Backup During Azure VM Creation by Using Azure Backup ...blob/main/articles/backup/backup-during-vm-creation.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits several Windows biases: Windows instructions and links are listed before Linux equivalents, PowerShell is referenced as the automation tool with no mention of Linux alternatives (such as Azure CLI or Bash), and the Resource Manager template example is Windows-only. There are no Linux-specific examples for automation or template deployment, and screenshots do not clarify OS parity.
Recommendations
  • Present Windows and Linux instructions/examples side-by-side or in parallel, rather than listing Windows first.
  • Include Linux automation options, such as Azure CLI or Bash scripts, alongside PowerShell instructions.
  • Provide a Resource Manager template example for deploying and protecting Linux VMs.
  • Clarify in screenshots and notes that steps apply equally to both Windows and Linux VMs, or highlight any differences.
  • Explicitly mention Linux support in automation and backup policy customization sections.
GitHub Create Pull Request
Backup Encryption in Azure Backup ...re-docs/blob/main/articles/backup/backup-encryption.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation mentions BitLocker for Windows VMs before DM-Crypt for Linux VMs when describing in-guest encryption, and references SQL Server and TDE (a Microsoft/Windows-centric technology) without mentioning Linux database equivalents. There are no Linux/macOS-specific examples or tools discussed, and the documentation implicitly assumes familiarity with Windows technologies.
Recommendations
  • Present DM-Crypt (Linux) and BitLocker (Windows) with equal prominence, ideally listing both together or alternating order.
  • Include examples or references for Linux database backup and encryption scenarios (e.g., MySQL/MariaDB/PostgreSQL with LUKS or native encryption).
  • Add explicit guidance for Linux users on configuring and verifying encryption, including command-line examples.
  • Clarify that Azure Backup supports both Windows and Linux workloads, and link to Linux-specific documentation where available.
GitHub Create Pull Request
Backup MABS (Azure Backup Server) V4 protection matrix .../main/articles/backup/backup-mabs-protection-matrix.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation for Azure Backup Server v4 is heavily Windows-centric, with detailed support matrices and examples for Windows workloads and tools. Linux support is relegated to a single table, with limited details and only VM-level protection described. Windows tools and patterns (e.g., VSS, NTFS, system state, bare metal recovery) are mentioned exclusively, and Windows examples always precede Linux. There are no Linux-specific backup/recovery scenarios, nor guidance for Linux file-level recovery or agent installation.
Recommendations
  • Provide Linux-specific backup and recovery examples, including file-level and application-level scenarios.
  • Clarify agent installation and supported Linux filesystems (e.g., ext4, xfs) and limitations.
  • List Linux distributions and versions directly in the matrix, not just as a link.
  • Describe Linux recovery options, including limitations and parity with Windows features.
  • Include Linux-first or side-by-side examples in tables and documentation sections.
  • Mention Linux tools or patterns (e.g., LVM snapshots, native backup utilities) where relevant.
GitHub Create Pull Request
Backup Manage Backups with Azure role-based access control ...docs/blob/main/articles/backup/backup-rbac-rs-vault.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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, primarily by referencing Windows-specific backup agents and tools (e.g., Azure Backup agent client UI, System Center Data Protection Manager, Azure Backup Server) when discussing on-premises backup registration and management. These tools are Windows-only, and there is no mention of Linux equivalents or parity for on-premises Linux backup scenarios. Additionally, the registration and management operations for on-premises resources are described only for Windows environments, and the documentation does not clarify Linux support or provide Linux-specific examples. The page also lists PowerShell as a primary management tool before Azure CLI, which is cross-platform, but does not provide explicit examples or guidance for Linux/macOS users.
Recommendations
  • Explicitly state whether on-premises Linux servers can be registered and managed with Azure Backup, and provide guidance or links for Linux backup scenarios if supported.
  • Include Linux/macOS-specific examples for command-line management, such as using Azure CLI or REST API, and clarify any differences in workflow or prerequisites.
  • When listing management tools, present cross-platform options (Azure CLI, REST API) before or alongside Windows-specific tools (PowerShell, agent UI), and clarify platform compatibility.
  • If certain features are Windows-only, clearly indicate this and suggest alternatives or workarounds for Linux users.
GitHub Create Pull Request
Backup Back Up a PostgreSQL Databases by Using the Azure CLI ...ocs/blob/main/articles/backup/backup-postgresql-cli.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation is primarily focused on Azure CLI usage, which is cross-platform, and most examples use Bash syntax. However, there is a notable Windows bias in the 'Create a backup policy' section, where the PowerShell object model is described first and in detail, and modifications are discussed in terms of PowerShell objects before mentioning file-based edits for Azure CLI (Linux/macOS). The documentation also uses Windows-style file paths (e.g., .\OSSPolicy.json) in CLI examples, which may confuse Linux/macOS users. No Linux-specific tools or patterns are mentioned, and PowerShell is referenced as the default for object manipulation.
Recommendations
  • Present PowerShell and Azure CLI approaches in parallel, or lead with CLI/file-based examples for broader platform parity.
  • Replace Windows-style file paths (e.g., .\OSSPolicy.json) with cross-platform alternatives (e.g., ./OSSPolicy.json) in CLI examples.
  • Clarify that all Azure CLI commands work on Linux/macOS and provide explicit Bash examples where file manipulation is involved.
  • Add a short section or note for Linux/macOS users highlighting any differences or considerations (e.g., file path syntax, shell environment).
  • Avoid describing PowerShell object manipulation as the 'default' or 'primary' approach unless truly required.
GitHub Create Pull Request
Backup Azure Resource Manager and Bicep files ...lob/main/articles/backup/backup-rm-template-samples.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page lists Azure Resource Manager and Bicep templates for backup scenarios, with one example ('Deploy Windows Server VM with backup enabled') specifically mentioning Windows Server. No Linux-specific VM backup example is provided, and the only OS-specific template is for Windows, which appears before any mention of Linux or cross-platform scenarios.
Recommendations
  • Add equivalent templates/examples for deploying and backing up Linux VMs, such as 'Deploy Ubuntu VM with backup enabled'.
  • Include notes clarifying that most templates are OS-agnostic unless otherwise stated.
  • Ensure parity by providing examples for both Windows and Linux where OS-specific features are involved.
  • Consider reordering or grouping OS-specific templates to avoid implicit prioritization of Windows.
GitHub Create Pull Request
Backup Back up multiple SQL Server VMs from the vault ...rticles/backup/backup-sql-server-database-azure-vms.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 notable Windows bias. It consistently references Windows-specific tools and extensions (e.g., AzureBackupWindowsWorkload extension, NT Service accounts), links to Windows-only troubleshooting scripts, and omits explicit Linux instructions or examples. The VM agent link points to the Windows version, and there is no mention of Linux equivalents or guidance for SQL Server on Linux VMs. The documentation assumes SQL Server is running on Windows, with no consideration for Linux-based deployments.
Recommendations
  • Add explicit guidance and examples for backing up SQL Server on Linux VMs, including any differences in agent installation, extension support, and service accounts.
  • Provide troubleshooting scripts and connectivity test tools for Linux environments.
  • Reference both Windows and Linux VM agent documentation.
  • Clarify which features or steps are Windows-only, and offer Linux alternatives where possible.
  • Include CLI and REST API examples for Linux users, and ensure parity in portal instructions.
GitHub Create Pull Request
← Previous Page 16 of 21 Next →