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 301-325 of 520 flagged pages
Backup Replace your tape infrastructure by using Azure Backup ...n/articles/backup/backup-azure-backup-cloud-as-tape.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses on Azure Backup in the context of tape replacement, but references System Center Data Protection Manager (DPM) and links to a 'backup-windows-with-mars-agent' guide, both of which are Windows-centric tools. There are no Linux/macOS examples, nor is there mention of Linux backup agents or procedures. The examples and screenshots are generic, but the only tool-specific guidance is for Windows environments.
Recommendations
  • Include guidance and examples for Linux-based backup scenarios, such as using Azure Backup with Linux servers or workloads.
  • Reference Linux-compatible backup agents or third-party tools that integrate with Azure Backup.
  • Add links to documentation pages for backing up Linux workloads to Azure.
  • Balance tool references by mentioning both Windows (DPM, MARS agent) and Linux equivalents where applicable.
GitHub Create Pull Request
Backup Create Backup Policies for PostgreSQL Databases by Using the Data Protection REST API ...rotection-use-rest-api-create-update-postgresql-policy.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias. It repeatedly references PowerShell objects as the default or primary way to conceptualize and configure backup policies, without mentioning Linux/macOS equivalents (such as Azure CLI, Bash, or other cross-platform tools). The narrative and examples assume familiarity with PowerShell constructs and terminology, and Windows tooling is referenced before any cross-platform alternatives. There are no explicit Linux/macOS examples or guidance, which may create friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI examples for all operations, especially for creating and managing backup policies.
  • Replace or supplement references to 'PowerShell object' with cross-platform terminology (e.g., 'policy JSON', 'API request body').
  • Include explicit instructions or examples for Linux/macOS users, such as using curl or other REST clients.
  • Clarify that the REST API can be used from any platform and provide sample commands for Bash/curl.
  • Reorder sections so that cross-platform methods (REST API, CLI) are presented before or alongside PowerShell.
GitHub Create Pull Request
Backup Overview of Azure Database for PostgreSQL Backup ...es/backup/backup-azure-database-postgresql-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the pgAdmin GUI tool for database management and privilege assignment, without mentioning or providing examples for Linux-native alternatives (such as psql CLI usage). All screenshots and workflow descriptions are tailored to the Windows/GUI experience, and there are no command-line instructions or examples for Linux/macOS users. The documentation also omits guidance for using Linux tools or patterns for firewall configuration and database user management.
Recommendations
  • Provide equivalent instructions and examples using the psql command-line tool, which is standard on Linux/macOS.
  • Include screenshots or walkthroughs for connecting to Azure Database for PostgreSQL from Linux/macOS terminals.
  • Add guidance for managing firewall rules and database users using CLI tools (e.g., Azure CLI, psql) on Linux/macOS.
  • Reorder sections or add parallel instructions so that Linux/macOS users are not required to use Windows-specific tools.
  • Explicitly mention cross-platform compatibility and provide links to Linux/macOS documentation where relevant.
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-12 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 moderate Windows bias. While the main backup workflow is platform-neutral (using the Azure Portal), the only detailed example for granting database privileges is via a dynamically generated PowerShell script, with explicit instructions for setting environment variables using Windows Control Panel. Linux/macOS alternatives (such as bash or shell scripts, or environment variable setup) are only briefly mentioned (pgAdmin/PSQL tool) and not documented with step-by-step guidance or screenshots. The PowerShell script workflow is described in detail, while Linux/macOS users must infer their own approach.
Recommendations
  • Provide explicit Linux/macOS instructions for running the privilege-granting script, including sample bash commands and environment variable setup.
  • Include screenshots or terminal examples for Linux/macOS environments (e.g., setting PATH in ~/.bashrc or ~/.zshrc).
  • Offer downloadable bash scripts alongside PowerShell scripts for privilege assignment.
  • Ensure that all tool references (pgAdmin, PSQL) include links and usage examples for Linux/macOS.
  • Present platform-agnostic instructions first, or in parallel, rather than Windows-first.
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-12 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 notable Windows bias. PowerShell is the primary automation method described, with extensive PowerShell script and cmdlet examples, and explicit instructions to install PowerShell 7. Windows-specific tools (MARS, MABS, DPM management consoles) are referenced throughout, with no mention of Linux equivalents or cross-platform alternatives for on-premises backup management. The ARMClient tool is installed via Chocolatey (Windows-only), and all screenshots and UI references are Windows-centric. The CLI section is brief, limited in scope, and does not provide parity with PowerShell capabilities, nor does it address Linux scenarios for on-premises backup servers.
Recommendations
  • Provide Bash and Azure CLI examples for all major steps, especially for deleting vaults and backup items.
  • Clarify which steps and tools are cross-platform, and explicitly document Linux/macOS workflows for on-premises backup management.
  • Include instructions for installing and running ARMClient on Linux/macOS (e.g., via .NET Core or manual download).
  • Reference Linux-compatible backup agents or clarify platform limitations for MARS, MABS, and DPM.
  • Balance example order: present CLI/Bash examples before or alongside PowerShell, and avoid assuming Windows as the default environment.
  • Add notes or links for Linux users where Windows-only tools are mentioned.
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-12 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 notable Windows bias, especially in the section on reinstalling the VMSnapshot backup extension. The Windows instructions are detailed, step-by-step, and include PowerShell commands, registry edits, and service management, while the Linux section is brief and lacks comparable detail or troubleshooting guidance. Windows tools and patterns (e.g., registry editor, services.msc, PowerShell) are mentioned exclusively and before any Linux equivalents. Most examples and screenshots throughout the page are from the Azure Portal, which is platform-neutral, but the only command-line example given is for Windows/PowerShell. Linux users are left with minimal guidance for extension management.
Recommendations
  • Provide equally detailed Linux instructions for managing the VMSnapshot extension, including troubleshooting steps, common issues, and command-line examples (e.g., using systemctl for waagent, file permissions, log locations).
  • Include Linux-specific commands for extension removal and reinstallation, such as using az CLI or shell scripts.
  • Add troubleshooting tips for Linux VMs (e.g., checking waagent logs, verifying extension status).
  • Ensure parity in screenshots and step-by-step guides for both OS types.
  • Where Windows tools (e.g., registry editor, services.msc) are referenced, mention Linux equivalents or alternatives (e.g., config files, systemctl, journalctl).
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias, primarily through the use of PowerShell examples for scripting resource moves, and by referencing Windows-specific update procedures before Linux equivalents. The CLI example is present but less detailed, and PowerShell is mentioned first and in greater depth. Windows update instructions are explicit, while Linux guidance is generic and less actionable.
Recommendations
  • Provide equally detailed Azure CLI and Bash script examples for all resource move operations, including subscription moves.
  • List CLI/Bash examples before or alongside PowerShell to avoid Windows-first ordering.
  • Offer Linux-specific troubleshooting and update instructions with actionable steps, not just generic distributor guidance.
  • Clarify that all operations can be performed on Linux/macOS using Azure CLI, and link to relevant cross-platform documentation.
  • Include screenshots or terminal output from Linux/macOS environments where applicable.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It 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. All example agents and extensions discussed are Windows-only, and there are no Linux or cross-platform command-line examples or instructions. This may create friction for Linux users seeking parity or clarity on how private endpoints affect Linux VM backup scenarios.
Recommendations
  • Explicitly mention how private endpoints work for Linux VM backup scenarios, including any differences in agent or extension requirements.
  • Include examples or references for Linux-based backup workflows, such as Azure VM backup for Linux, and clarify if/how private endpoints affect them.
  • Add cross-platform command-line examples (e.g., Azure CLI, Bash) alongside any Windows/Powershell instructions.
  • Reference any Linux-compatible backup tools or extensions, or clarify their absence.
  • Ensure recommendations and tables include Linux VM scenarios, not just SQL Server/SAP HANA (which are often Windows workloads).
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. It references Windows-centric backup tools (System Center DPM, Windows Server, Azure Backup Server) and provides a direct link to backing up Windows Server, while Linux-specific backup instructions or examples are absent. Windows workloads and tools are mentioned before Linux equivalents, and no Linux-specific backup scenarios or links are provided in the 'Next steps' section.
Recommendations
  • Add explicit examples and links for backing up Linux VMs and workloads, similar to the Windows Server example.
  • Mention Linux backup tools or common Linux backup scenarios alongside Windows tools in the feature overview.
  • Ensure parity in 'Next steps' by including guidance for Linux VM backup and restore.
  • Provide references to Linux-specific documentation or troubleshooting guides.
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-12 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 generally presents Windows-specific instructions and tools before Linux equivalents, with more detailed guidance and screenshots for Windows users. Windows registry edits and File Explorer usage are described in depth, while Linux instructions are more concise and sometimes lack step-by-step screenshots. PowerShell is referenced as a next step, while Linux CLI is less emphasized. Some troubleshooting and advanced scenarios (e.g., registry changes for large disks) are Windows-only, with Linux alternatives presented later or less thoroughly.
Recommendations
  • Present Linux and Windows instructions in parallel, with equal detail and prominence.
  • Add more Linux-specific screenshots and step-by-step guidance, especially for advanced scenarios.
  • Include Linux CLI examples and troubleshooting tips alongside PowerShell references.
  • Ensure that troubleshooting steps for large disks, permissions, and mounting are equally detailed for Linux.
  • Avoid presenting Windows instructions first by default; alternate or group by OS.
  • Highlight Linux tools and patterns (e.g., bash, Python, LVM, RAID) as prominently as Windows tools (e.g., File Explorer, registry).
GitHub Create Pull Request
Backup Restore Key Vault key & secret for encrypted Azure VM ...ain/articles/backup/backup-azure-restore-key-secret.md
Medium Priority View Details →
Scanned: 2026-01-12 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 is heavily focused on Azure PowerShell, with all examples and instructions using PowerShell cmdlets and Windows-style file paths (e.g., C:\). There are no Bash, CLI, or Linux-native examples provided, and the workflow assumes the use of PowerShell and Windows tooling even for Linux VM scenarios. Linux-specific instructions are limited to minor tag changes, but the actual restore process is not demonstrated using Linux-friendly tools or environments.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all restore operations, especially for Linux users.
  • Include examples using Bash shell and Linux file paths (e.g., /home/user/vmencryption_config.json).
  • Clarify whether PowerShell Core (pwsh) on Linux/macOS is supported and provide cross-platform instructions if so.
  • Add a section explicitly addressing Linux/macOS users, outlining any prerequisites or differences in workflow.
  • Avoid using Windows-specific file paths in generic examples; use environment-agnostic paths or show both Windows and Linux formats.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation consistently assumes the SQL Server is running on a Windows-based Azure VM, with all examples referencing SQL Server and Windows-style resource/container naming. There are no examples or guidance for restoring databases on Linux-based SQL Server VMs, nor any mention of Linux-specific considerations, tools, or file paths (except a single instance of a Unix-style path in a restore-as-files example). The documentation does not clarify whether the CLI commands and restore procedures are equally applicable to Linux SQL Server VMs, and does not provide parity for Linux users.
Recommendations
  • Explicitly state whether the documented CLI restore process applies to both Windows and Linux SQL Server VMs.
  • Add examples and guidance for restoring SQL Server databases on Linux-based Azure VMs, including any differences in resource/container naming, file paths, or prerequisites.
  • Include Linux-specific notes, such as required permissions, service management, and file system considerations.
  • Where file paths are referenced, clarify OS-specific conventions and provide both Windows and Linux examples.
  • If there are limitations or differences for Linux SQL Server VMs, document them clearly.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation primarily describes migration using the Azure portal and references Azure CLI, but does not provide explicit CLI or PowerShell command examples inline. There is a mention of PowerShell and CLI support for trusted launch VMs, but no concrete Linux/macOS-specific guidance or examples. The workflow and screenshots are entirely portal-based, which is platform-agnostic, but the lack of CLI walkthroughs or Linux/macOS shell examples creates friction for non-Windows users who prefer automation or scripting.
Recommendations
  • Add step-by-step CLI examples for the migration process, including full command syntax and expected output.
  • Include PowerShell and Bash (or generic shell) script examples for both Windows and Linux/macOS users.
  • Explicitly mention platform compatibility for CLI commands and provide troubleshooting notes for Linux/macOS environments.
  • Where portal screenshots are used, supplement with equivalent CLI instructions for parity.
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-12 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 exhibits a moderate Windows bias. Windows troubleshooting steps are often presented first and in greater detail, with screenshots and explicit GUI instructions (e.g., Server Manager, Disk Management, ISCSI initiator Properties). Linux troubleshooting is referenced but often redirects to other documentation or provides less detailed, command-line-centric guidance. Some Windows-specific tools (File Explorer, Disk Management, deduplication) are mentioned without Linux equivalents, and Linux examples are sometimes missing or less explicit.
Recommendations
  • Provide Linux troubleshooting steps with equal detail, including screenshots and explicit commands for common desktop environments (e.g., GNOME Disks, mount commands).
  • Include Linux equivalents for Windows tools (e.g., show how to mount disks using 'mount', 'lsblk', or graphical disk utilities).
  • Present Linux and Windows solutions side-by-side or in parallel, rather than Windows-first.
  • Expand Linux error resolution sections to match the depth of Windows instructions, including more examples and step-by-step guidance.
  • Mention deduplication and other advanced features in the Linux context if applicable, or clarify their absence.
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-12 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 demonstrates a moderate Windows bias. Windows troubleshooting steps and tools (services.msc, Event Viewer, Control Panel, .NET, regsvr32.exe, Visual C++ Redistributable, AppLocker) are described in detail, often with screenshots and step-by-step instructions. Windows-specific tools and patterns (PowerShell, Windows file paths) are mentioned before or instead of Linux equivalents. Linux instructions are present but less detailed, with fewer examples, no screenshots, and less emphasis on Linux-specific troubleshooting tools. Some troubleshooting steps (e.g., antivirus exclusions, extension troubleshooting) only mention Windows paths/applications, omitting Linux equivalents.
Recommendations
  • Provide Linux-first or parallel examples for all troubleshooting steps, especially where Windows tools (services.msc, Event Viewer, Control Panel) are referenced.
  • Include Linux-specific troubleshooting tools and commands (e.g., systemctl, journalctl, log file locations) with the same level of detail and screenshots as Windows.
  • Where antivirus exclusions are discussed, include Linux paths and common Linux AV solutions.
  • When referencing PowerShell, also provide equivalent Azure CLI or shell commands for Linux/macOS users.
  • Ensure troubleshooting steps for extension failures, agent installation, and backup job management are equally detailed for Linux.
  • Add explicit instructions for Linux package dependencies and update mechanisms, matching the depth of Windows MSI installation guidance.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions Windows-specific tools (Volume Shadow Copy Service - VSS) before Linux equivalents (fsfreeze) when describing backup mechanisms. It references the VM Agent and snapshot extension with Windows-focused links, and does not provide Linux-specific links or examples. There are no Linux command-line or workflow examples, and Linux considerations are mentioned only in passing (e.g., pre/post scripts for Linux VM backups) without detail or parity.
Recommendations
  • Provide equal detail for Linux backup mechanisms, including links to Linux VM Agent and snapshot extension documentation.
  • Include Linux-specific examples or workflows, such as how crash-consistent backups interact with Linux filesystems and typical Linux workloads.
  • Mention Linux tools (e.g., fsfreeze) alongside Windows tools (VSS), and provide links to relevant Linux documentation.
  • Ensure that references to VM Agent and snapshot extension include both Windows and Linux versions.
  • Add troubleshooting or best practices sections for Linux users, similar to any Windows guidance.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation generally covers both Windows and Linux Azure VMs, but there is a notable Windows bias in several areas. Windows encryption tools (BitLocker) are mentioned before Linux equivalents (dm-crypt), and PowerShell is the only command-line example given for identifying a VM's associated key vault, with no Linux or Azure CLI equivalent shown. No Linux-specific command or example is provided for tasks like identifying the key vault, which may create friction for Linux users.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell for tasks such as identifying a VM's associated key vault.
  • When mentioning encryption tools, present Windows and Linux options in parallel, rather than listing Windows first.
  • Explicitly show Linux-specific steps or screenshots where workflows differ.
  • Ensure all automation and scripting instructions include both PowerShell and CLI/Bash alternatives.
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-12 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 moderate Windows bias. Troubleshooting steps and error resolutions frequently reference Windows tools (Event Viewer, Services.msc, Registry Editor, command prompt commands like net start/stop, icacls, msdtc, regedit, vssadmin, MSIEXEC, etc.) and PowerShell cmdlets, often without Linux equivalents or with Linux instructions appearing later or in less detail. Some errors and solutions are Windows-specific (VSS, BitLocker, Visual C++ Redistributable), and examples for Linux are less frequent and less detailed. In networking and restore sections, PowerShell is referenced for static IP setup and VM restore, with Linux CLI or portal alternatives missing or less emphasized.
Recommendations
  • Provide Linux-specific troubleshooting steps and command equivalents alongside Windows instructions (e.g., systemctl/service commands for service management, journalctl/log file locations for error logs).
  • Include Linux CLI examples (such as Azure CLI or bash commands) for tasks currently shown only with PowerShell.
  • Balance the order of presentation: present Linux and Windows instructions together or alternate which comes first.
  • For registry or Windows-specific configuration, clarify if/how similar issues can be addressed on Linux, or explicitly state if the error is Windows-only.
  • Add more Linux error screenshots and log file examples.
  • Reference Linux documentation links as frequently as Windows ones.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation mentions sample PowerShell scripts before CLI commands and does not provide explicit Linux/macOS examples or tools. Windows-centric scripting (PowerShell) is highlighted as a primary automation method, with no parity for Bash or Linux-native tooling. There are no references to Linux-specific patterns or guidance, and Windows/PowerShell is implicitly prioritized.
Recommendations
  • Provide Bash or shell script examples alongside PowerShell samples for automation tasks.
  • Explicitly mention Azure CLI usage on Linux/macOS and provide equivalent examples.
  • Clarify that Backup center is accessible and fully functional from Linux/macOS environments via the Azure portal and CLI.
  • Include references to Linux-native tools or workflows where relevant.
  • Ensure that scripting and automation guidance is cross-platform by default.
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-12 00:00
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 'SQL in Azure VM', 'SAP HANA in Azure VM', 'System Center Data Protection Manager', 'Azure Backup Agent (MARS)', and 'Azure Backup Server (MABS)' are mentioned explicitly, while Linux-specific workloads are not called out. The ordering of workloads and examples consistently places Windows technologies first, and Windows-only backup tools are referenced without Linux equivalents.
Recommendations
  • Explicitly mention Linux VM backup support and any Linux-specific scenarios or limitations.
  • Include examples or references for Linux workloads (e.g., backup/restore for Linux VMs, PostgreSQL on Linux, etc.).
  • Balance the ordering of workloads so Linux and Windows are presented equally, or group by OS type.
  • Reference Linux-compatible backup tools or clarify when a tool is Windows-only.
  • Add a section or table row for Linux-specific backup agents or methods if available.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits several signs of Windows bias. Windows is mentioned before Linux in VM creation instructions, and the only Resource Manager template example provided is for deploying and backing up a Windows VM, with no Linux equivalent. PowerShell is referenced for resource group configuration, but no CLI or Bash alternatives are given. There is a lack of Linux/macOS-specific guidance or parity in automation and template examples.
Recommendations
  • Provide equal prominence to Linux VM creation and backup instructions, including examples and links.
  • Add Resource Manager template examples for deploying and backing up Linux VMs.
  • Include Azure CLI and Bash script examples for resource group configuration and backup tasks, not just PowerShell.
  • Ensure that automation and troubleshooting sections reference Linux/macOS tools and workflows where applicable.
GitHub Create Pull Request
Backup Azure Instant Restore Capability ...n/articles/backup/backup-instant-restore-capability.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides configuration instructions for Instant Restore snapshot retention using PowerShell only, with no mention of CLI, Bash, or Linux/macOS-compatible methods. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools. The documentation also refers to PowerShell as the primary automation tool, reinforcing a Windows-centric approach.
Recommendations
  • Add equivalent Azure CLI examples for configuring snapshot retention, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell examples are for Windows and provide guidance for Linux/macOS users.
  • Include Bash or shell script examples where appropriate.
  • Ensure that all configuration steps are accessible via the Azure portal and Azure CLI, and document these methods equally.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Azure Backup Server v4 exhibits a notable Windows bias. Windows workloads and tools are described in detail, with multiple examples and scenarios, while Linux support is relegated to a single, brief section. The Linux section only covers protection as a VM guest, with no mention of file-level or application-level backup for native Linux servers. Windows-specific technologies (NTFS, VSS, Visual C++, etc.) are referenced throughout, and Windows examples are always presented first or exclusively. There is no parity in example depth, nor are Linux-specific backup scenarios or limitations discussed.
Recommendations
  • Expand the Linux section to include supported backup scenarios for native Linux servers, not just as VM guests.
  • Provide detailed examples for Linux workloads, including supported file systems, backup/restore procedures, and limitations.
  • List Linux support alongside Windows in all relevant tables, rather than in a separate, minimal section.
  • Mention Linux-specific tools, file systems (e.g., ext4, xfs), and backup mechanisms where applicable.
  • Clarify whether application-level backup (e.g., for MySQL, PostgreSQL) is supported for Linux, and provide guidance if not.
  • Ensure that any Windows-only limitations are clearly marked, and Linux alternatives/workarounds are suggested.
GitHub Create Pull Request
Backup Azure Backup release notes - Archive .../main/articles/backup/backup-release-notes-archived.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page for Azure Backup release notes shows a moderate Windows bias. Several features and updates reference Windows-specific tools (such as MARS agent and Microsoft Azure Backup Server), and Windows Server compatibility is highlighted. Windows-centric backup solutions (MARS, MABS) are described in detail, while Linux-specific equivalents are less prominent or only mentioned in passing. In some cases, Windows tools and features are listed before their Linux counterparts, and PowerShell is referenced as a management option, sometimes before CLI. However, the page does mention support for Linux workloads (e.g., SAP HANA on RHEL, PostgreSQL), and many features are platform-agnostic.
Recommendations
  • Ensure Linux and macOS equivalents are mentioned alongside Windows tools (e.g., for MARS/MABS, clarify Linux backup options).
  • Provide explicit Linux/macOS examples or references for backup agents and management tools, not just Windows-centric ones.
  • When listing features or tools, avoid listing Windows options first unless they are the only supported platform.
  • Where PowerShell is mentioned, also reference Azure CLI and REST API usage for parity.
  • Highlight cross-platform support in summary sections and link to Linux/macOS-specific guides where relevant.
GitHub Create Pull Request
Backup Automation in Azure Backup support matrix ...blob/main/articles/backup/backup-support-automation.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is consistently listed as the first automation method for nearly all operations, and examples are referenced with PowerShell links before CLI or REST API. The use of PowerShell as a primary automation tool is inherently Windows-centric, as PowerShell is native to Windows and only more recently available on Linux/macOS. There is no explicit mention of Linux/macOS-specific tools or shell scripting alternatives, and no guidance for users who may prefer Bash or other Linux-native automation approaches. However, Azure CLI and REST API options are generally present, which mitigates the impact for non-Windows users.
Recommendations
  • Alternate the order of PowerShell and CLI in tables and examples, or list CLI first in some sections to avoid implicit prioritization.
  • Explicitly mention that Azure CLI and REST API are cross-platform and suitable for Linux/macOS users.
  • Provide links or examples for Bash scripting, especially for common automation tasks, to improve Linux parity.
  • Add a short section or note clarifying PowerShell Core's cross-platform availability and any limitations compared to Windows PowerShell.
  • Where possible, include troubleshooting notes for Linux/macOS users (e.g., authentication, environment setup) when using PowerShell or CLI.
GitHub Create Pull Request
← Previous Page 13 of 21 Next →