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 201-225 of 1604 flagged pages
Backup Troubleshoot Azure VM file recovery ...s/backup/backup-azure-vm-file-recovery-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows troubleshooting steps and tools (e.g., 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 summarized briefly. Some troubleshooting sections present Windows solutions first or exclusively, with Linux guidance provided as a secondary note or omitted entirely. Linux examples are less detailed, and Linux-specific errors are sometimes addressed only by referencing external guides.
Recommendations
  • Provide equally detailed, step-by-step instructions for Linux troubleshooting, including screenshots of relevant Linux tools (e.g., GNOME Disks, terminal commands for mounting/unmounting, LVM/RAID management).
  • Include Linux command-line equivalents for all Windows GUI actions (e.g., mounting disks, changing drive letters/paths, checking disk status).
  • Present Windows and Linux solutions in parallel, rather than listing Windows first or exclusively.
  • Expand Linux troubleshooting sections to cover common scenarios (e.g., handling encrypted volumes, manual mounting, dealing with raw partitions) with concrete examples.
  • Avoid referencing Linux solutions only via external links; summarize key steps directly in the documentation.
  • Add troubleshooting for Linux-specific features (e.g., SELinux, file permissions, systemd services) where relevant.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by mentioning Windows-specific tools (VSS) before Linux equivalents (fsfreeze) when discussing backup consistency mechanisms. References to VM Agent and snapshot extension link only to Windows documentation, omitting direct Linux equivalents or links. There are no Linux-specific examples, commands, or links to Linux agent documentation, and Linux patterns (such as pre/post scripts) are mentioned only in passing, without detail.
Recommendations
  • Provide equal coverage of Linux backup mechanisms, including direct links to Linux VM Agent and snapshot extension documentation.
  • Include Linux-specific examples or scenarios, such as how crash-consistent backup interacts with Linux filesystems and typical Linux workloads.
  • Mention Linux tools (e.g., fsfreeze) alongside Windows tools (VSS), and avoid listing Windows tools first.
  • Clarify Linux support and limitations for agentless backups, including any differences in implementation or recommended practices.
  • Add references to Linux documentation and best practices for backup consistency.
GitHub Create Pull Request
Backup Move VM backup - standard to enhanced policy in Azure Backup ...cles/backup/backup-azure-vm-migrate-enhanced-policy.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and CLI versions for trusted launch support before mentioning REST API, and by not providing any Linux-specific examples or guidance. All command-line references are generic or Windows-centric (PowerShell), and there is no mention of Linux shell usage, nor are there screenshots or instructions tailored for Linux users. The documentation assumes familiarity with Windows tools and patterns, and does not address Linux-specific considerations or workflows.
Recommendations
  • Include explicit Linux shell (bash) examples for CLI commands, showing usage in Linux environments.
  • Add notes or sections addressing Linux-specific considerations, such as differences in Azure CLI installation or authentication on Linux.
  • Provide parity in screenshots or instructions for Linux users, such as terminal examples or references to Linux desktop environments.
  • Mention Linux tools (e.g., shell scripting, cron integration) where relevant, alongside PowerShell.
  • Ensure REST API usage examples are platform-neutral and provide sample requests using curl or similar Linux tools.
GitHub Create Pull Request
Backup Back Up and Restore Encrypted Azure VMs ...ob/main/articles/backup/backup-azure-vms-encryption.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. PowerShell is the only command-line example provided for identifying a VM's associated key vault, with no equivalent Linux (bash/Azure CLI) example. Windows tools and terminology (such as BitLocker) are mentioned before Linux equivalents (dm-crypt), and Windows is often referenced first in lists and explanations. There are no explicit Linux command examples or instructions, and the documentation assumes familiarity with Windows-centric workflows.
Recommendations
  • Provide Azure CLI and/or bash examples alongside PowerShell commands, especially for tasks like identifying key vault associations.
  • Ensure that Linux-specific encryption tools and workflows (e.g., dm-crypt) are described with equal prominence and detail as Windows tools (BitLocker).
  • Alternate the order of Windows and Linux references in lists and explanations to avoid implicit prioritization.
  • Include screenshots or instructions that are relevant for Linux VMs, such as those created from Linux Marketplace images or with custom Linux configurations.
  • Add troubleshooting and automation guidance for Linux users, including common Linux-specific issues and solutions.
GitHub Create Pull Request
Backup About Azure VM backup .../main/articles/backup/backup-azure-vms-introduction.md
High 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 demonstrates a Windows bias in several ways: Windows tools (VSS) are mentioned before Linux equivalents, Windows backup mechanisms are described in more detail, and PowerShell is referenced for restore operations without Linux CLI parity. Linux instructions are less detailed, relying on users to create custom scripts, and Linux-specific examples or tools are not provided with the same clarity or prominence.
Recommendations
  • Provide Linux CLI (az CLI, Bash) examples for backup and restore operations alongside PowerShell examples.
  • Describe Linux backup mechanisms (such as fsfreeze) with the same level of detail as VSS for Windows, including troubleshooting and best practices.
  • Include explicit Linux restore instructions and automation options, not just PowerShell.
  • Ensure that Linux tools and patterns are mentioned with equal prominence and before or alongside Windows equivalents.
  • Add sample pre/post script templates for common Linux workloads to help users achieve application consistency.
  • Clarify any differences in backup/restore behavior or limitations between Windows and Linux VMs.
GitHub Create Pull Request
Backup Troubleshoot backup errors with Azure VMs .../main/articles/backup/backup-azure-vms-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: troubleshooting steps and examples frequently reference Windows-specific tools (Event Viewer, Services.msc, Registry Editor, command prompt commands like net start/stop, icacls, msdtc, vssadmin, regedit, MSIEXEC, etc.) and registry modifications. Windows troubleshooting is often described in more detail and appears before Linux equivalents. PowerShell is mentioned as the automation method for VM restore, with no Linux CLI or Azure CLI alternatives. Some error resolutions and examples are exclusively Windows-focused, and Linux guidance is sometimes brief or missing.
Recommendations
  • Provide equivalent Linux troubleshooting steps and examples for each Windows-specific instruction (e.g., show how to check agent status, logs, and services on Linux).
  • Include Azure CLI and Bash examples alongside PowerShell for automation and scripting tasks.
  • Ensure Linux tools (systemctl, journalctl, /var/log, etc.) are referenced where appropriate, especially for agent/service management and log review.
  • Present Windows and Linux instructions in parallel, or clearly separate them under distinct headings, to avoid Windows-first ordering.
  • Expand Linux error handling and configuration guidance to match the detail provided for Windows (e.g., registry changes should have Linux config file or environment variable equivalents if applicable).
  • Add troubleshooting steps for common Linux backup/restore issues, such as SELinux, file system consistency, and agent installation/validation.
  • Where screenshots or examples are Windows-only, add Linux equivalents (e.g., log file output, config file locations).
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias, primarily through references to PowerShell scripts and Microsoft Database Backup scripts in the Community Hub section. There is no mention of Linux-specific tools, shell scripts, or examples, nor are cross-platform CLI examples highlighted. The documentation does not provide parity for Linux administrators or mention Linux-native backup patterns, despite Azure supporting Linux VMs and workloads.
Recommendations
  • Include sample Bash shell scripts and Linux-native backup automation examples alongside PowerShell scripts.
  • Explicitly mention Azure CLI commands as cross-platform alternatives to PowerShell, and provide examples for both.
  • Reference Linux backup tools and patterns where relevant, especially for scenarios involving Linux VMs.
  • Ensure that documentation for automated deployments and scripting covers both Windows and Linux environments equally.
  • Add a note clarifying that Backup center supports both Windows and Linux workloads, and link to Linux-specific guidance where available.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric, with all instructions, screenshots, and tooling focused on Windows Server environments. There are no Linux examples, and the use of Windows-specific tools (Server Manager, PowerShell cmdlets, ReFS filesystem) is pervasive. The documentation assumes the user is operating on Windows and does not mention Linux support or alternatives.
Recommendations
  • Clarify whether Azure Backup Server or Modern Backup Storage is supported on Linux. If not, explicitly state this in the prerequisites.
  • If Linux support exists or is planned, provide equivalent instructions and examples for Linux environments, including CLI commands and supported filesystems.
  • Mention Linux backup solutions or integration points if Azure Backup Server is Windows-only, to help Linux administrators understand their options.
  • Avoid assuming Windows as the default platform; structure documentation to address cross-platform scenarios or highlight platform limitations up front.
  • If PowerShell is used, offer Bash or shell script equivalents for Linux where possible.
GitHub Create Pull Request
Backup Install Azure Backup Server on Azure Stack Hub ...ain/articles/backup/backup-mabs-install-azure-stack.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented toward Windows environments. It exclusively references Windows Server images, Windows file paths (C:\, D:\), Windows domain joining, and Windows-specific tools (PowerShell, .NET Framework, SQL Server, Windows Update). There are no instructions, examples, or notes for Linux-based environments, nor any mention of Linux compatibility or alternatives. All examples and screenshots are Windows-centric, and PowerShell is the only command-line tool referenced.
Recommendations
  • Explicitly state whether Azure Backup Server supports Linux-based VMs or not. If not, clarify this early in the documentation.
  • If Linux support exists, provide equivalent instructions for Linux environments, including prerequisites, installation steps, and command-line examples (e.g., Bash, CLI).
  • Mention Linux-compatible backup solutions or alternatives if Azure Backup Server is Windows-only.
  • Include notes or links for users running non-Windows workloads, clarifying what is and isn't supported.
  • Where possible, provide parity in tooling (e.g., Azure CLI commands for connectivity checks, Linux-based SQL installation guidance).
  • Add a comparison table or section outlining differences between Windows and Linux support for Azure Backup Server.
GitHub Create Pull Request
Backup Azure Instant Restore Capability ...n/articles/backup/backup-instant-restore-capability.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides configuration instructions for Instant Restore using the Azure portal and PowerShell, but does not mention or provide examples for Linux users or CLI tools commonly used on Linux (such as Azure CLI or Bash scripts). The only command-line example is in PowerShell, which is Windows-centric. There is no mention of Linux-specific considerations, nor are Linux-friendly tools or workflows presented alongside or before Windows options.
Recommendations
  • Add equivalent Azure CLI examples for configuring snapshot retention and other Instant Restore operations, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that PowerShell is available on Linux and macOS, or clarify if the instructions are Windows-only.
  • Provide Bash script examples or reference automation options for Linux environments.
  • Ensure that any tool or workflow mentioned (such as PowerShell) is paired with its Linux-friendly counterpart (such as Azure CLI) and present both options side-by-side.
  • Include a note or section addressing Linux-specific considerations for VM backup and restore operations, if any exist.
GitHub Create Pull Request
Backup Back up files in Azure Stack VMs ...s/backup/backup-mabs-files-applications-azure-stack.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively describes backup and recovery procedures using Microsoft Azure Backup Server, which is a Windows-based tool. All instructions and screenshots are for the Azure Backup Server console, with no mention of Linux tools, command-line alternatives, or cross-platform methods. There are no examples or guidance for Linux VMs, nor are Linux-native backup patterns or tools referenced. The documentation assumes a Windows-centric workflow and environment.
Recommendations
  • Add equivalent instructions for backing up files and applications on Linux-based Azure Stack VMs, including use of Linux-native tools and integration with Azure Backup.
  • Provide command-line examples (e.g., Bash scripts, CLI commands) for Linux environments alongside the GUI-based Windows instructions.
  • Mention and link to documentation for cross-platform backup solutions or third-party tools that support Linux workloads in Azure Stack.
  • Clarify any limitations or requirements for Linux VM backup in Azure Stack, and provide guidance for mixed Windows/Linux environments.
  • Ensure screenshots and step-by-step guides include both Windows and Linux scenarios where applicable.
GitHub Create Pull Request
Backup MABS (Azure Backup Server) V4 protection matrix .../main/articles/backup/backup-mabs-protection-matrix.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation for Azure Backup Server v4 is heavily focused on Windows workloads, with detailed support matrices and examples for Windows Server, SQL Server, Exchange, SharePoint, and Hyper-V. Windows-specific tools and technologies (NTFS, VSS, Visual C++, Windows Management Framework) are referenced throughout, while Linux support is limited to a single table row describing backup of Linux VMs as guests on Windows-based Hyper-V/VMware hosts. There are no Linux-specific backup scenarios, examples, or instructions, and Linux is only mentioned after all Windows scenarios. Recovery options for Linux are limited compared to Windows (only file-consistent snapshots, no item-level recovery).
Recommendations
  • Add explicit Linux backup scenarios, including direct backup of Linux workloads and filesystems, not only as VMs hosted on Windows.
  • Provide Linux-specific instructions and examples, including supported filesystems, recovery options, and agent installation steps.
  • Mention Linux support earlier in the documentation and in parity with Windows, rather than as an afterthought.
  • Clarify limitations and differences for Linux protection, and offer guidance for Linux administrators.
  • Reference Linux tools and patterns (e.g., ext4, XFS, LVM snapshots) where relevant, not just NTFS/VSS.
  • Include parity in recovery options, such as item-level recovery for Linux files and folders if supported, or document alternatives.
GitHub Create Pull Request
Backup Back up a SharePoint farm on Azure Stack using Microsoft Azure Backup Server .../articles/backup/backup-mabs-sharepoint-azure-stack.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page is heavily biased toward Windows environments. All instructions, tools, and examples assume the use of Windows servers, Windows command-line tools (CMD, Registry Editor), and Windows-specific services (VSS Writer, DCOM, NT AUTHORITY\SYSTEM). There is no mention of Linux-based SharePoint deployments, nor any examples or guidance for Linux systems. The documentation exclusively references Windows patterns and tools, and does not provide parity for Linux users.
Recommendations
  • Explicitly state that MABS and SharePoint farm protection are only supported on Windows, if that is the case. If Linux support is possible, add equivalent instructions and examples for Linux environments.
  • Provide a section clarifying platform requirements and limitations, including whether Linux-based SharePoint or SQL Server deployments are supported.
  • If any components (such as Azure Backup Server or SQL Server) can run on Linux, include Linux-specific setup, configuration, and recovery steps.
  • Add notes or links to documentation for Linux backup solutions if MABS is not supported on Linux.
  • Ensure that any command-line instructions, file paths, and registry settings are accompanied by Linux equivalents or a statement of non-applicability.
GitHub Create Pull Request
Backup System state and bare-metal recovery protection for Azure Backup ...in/articles/backup/backup-mabs-system-state-and-bmr.md
High 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 is heavily focused on Windows environments, referencing only Windows Server, Windows Server Backup, WinRE, and PowerShell cmdlets. All workflows, examples, and recovery steps are specific to Windows, with no mention of Linux or cross-platform support. Linux equivalents, tools, or procedures are absent throughout the page.
Recommendations
  • Add explicit statements about Linux support or limitations for Azure Backup Server, clarifying whether Linux system state/BMR is supported.
  • If Linux is supported, provide equivalent workflows, examples, and recovery steps for Linux systems, including relevant tools (e.g., rsync, tar, dd, or native Linux backup utilities).
  • Include Linux command-line examples and configuration file locations alongside Windows/Powershell examples.
  • Mention Linux-specific prerequisites, limitations, and recovery environments (e.g., using a live CD, systemd, or GRUB for recovery).
  • If Azure Backup Server is Windows-only, state this clearly at the beginning to set expectations for cross-platform users.
GitHub Create Pull Request
Backup Manage Backups with Azure role-based access control ...docs/blob/main/articles/backup/backup-rbac-rs-vault.md
High 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 demonstrates Windows bias primarily by referencing Windows-specific backup agents and tools (e.g., Azure Backup agent client UI, System Center Data Protection Manager UI, Azure Backup Server UI) when discussing on-premises backup registration and management. These Windows tools are mentioned exclusively, with no mention of equivalent Linux backup agents or procedures. Additionally, the registration and deletion operations for on-premises resources are explicitly tied to Windows Server/client/SCDPM or Azure Backup Server, with no Linux alternatives or parity. Examples and instructions for backup management focus on Windows-centric scenarios, and there are no CLI or Linux-specific examples for agent-based backup operations.
Recommendations
  • Include references to Linux-based backup agents or procedures for on-premises backup registration and management, if supported.
  • Provide parity by mentioning Linux equivalents (such as MARS agent alternatives, if available) alongside Windows tools.
  • Add examples or instructions for managing backups on Linux servers, including CLI commands and agent installation/configuration steps.
  • Clarify whether agent-based backup operations are supported for Linux, and if not, explicitly state the limitation.
  • Ensure that documentation for backup management operations is platform-neutral where possible, or provides clear guidance for both Windows and Linux environments.
GitHub Create Pull Request
Backup Troubleshoot SQL Server database backup ...rticles/backup/backup-sql-server-azure-troubleshoot.md
High 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 is heavily oriented toward Windows environments. All examples, file paths, extension names, and troubleshooting steps reference Windows-specific tools, directories (e.g., C:\Program Files), and services (e.g., NT AUTHORITY\SYSTEM, Local Security Policy). The AzureBackupWindowsWorkload extension is mentioned exclusively, and instructions for re-registering the extension refer only to PowerShell. There is no mention of Linux-based SQL Server VMs, nor are any Linux-specific troubleshooting steps, file paths, or commands provided.
Recommendations
  • Include explicit guidance for SQL Server running on Linux-based Azure VMs, if supported.
  • Provide Linux equivalents for file paths, extension installation, and configuration steps (e.g., /opt/ or /var/ directories, systemd services).
  • Add troubleshooting steps and error messages relevant to Linux environments (e.g., permissions, SELinux/AppArmor, systemd service status).
  • Offer examples using Bash or Linux-native tools alongside PowerShell, where applicable.
  • Clarify in the introduction whether the documentation applies only to Windows VMs, or update the scope to include Linux VMs if supported.
GitHub Create Pull Request
Backup What's new in Microsoft Azure Backup Server ...lob/main/articles/backup/backup-mabs-whats-new-mabs.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation for Microsoft Azure Backup Server (MABS) is heavily Windows-centric. Features and examples almost exclusively reference Windows Server, Windows-specific technologies (ReFS, Hyper-V, registry keys), and Windows tools (PowerShell cmdlets). There is no mention of Linux support, Linux workloads, or Linux-specific backup scenarios, nor are any Linux equivalents or examples provided. Windows features and tools are consistently presented first and often exclusively.
Recommendations
  • Explicitly state the level of Linux support in MABS, if any, and document limitations.
  • Add examples and instructions for backing up Linux-based VMs and workloads, if supported.
  • Include Linux equivalents for Windows-centric features (e.g., registry key changes, PowerShell cmdlets), or clarify if such features are unavailable on Linux.
  • Document backup and recovery procedures for Linux file systems and workloads.
  • If MABS is Windows-only, clarify this early in the documentation and provide links to Azure backup solutions for Linux environments.
  • Ensure parity in feature tables and examples by including Linux alongside Windows where applicable.
GitHub Create Pull Request
Backup Back Up a PostgreSQL Databases by Using the Azure CLI ...ocs/blob/main/articles/backup/backup-postgresql-cli.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways. It repeatedly references PowerShell objects and workflows as the default or primary method for policy manipulation, even in an Azure CLI-focused article. Windows/PowerShell terminology is used to explain concepts before their Linux/CLI equivalents, and file path examples use Windows-style syntax (e.g., .\file.json) without showing Linux alternatives. There are no explicit Linux shell or cross-platform examples for file manipulation, and the guidance assumes familiarity with Windows tools and patterns.
Recommendations
  • Provide Linux/macOS shell examples alongside Windows/PowerShell examples, especially for file manipulation (e.g., use ./file.json instead of .\file.json, and show both syntaxes).
  • Avoid referencing PowerShell objects as the default; clarify that Azure CLI is cross-platform and show equivalent Linux workflows.
  • Explicitly mention that all CLI commands work on Linux/macOS and Windows, and highlight any OS-specific considerations.
  • Add notes or sections for Linux users, such as using Bash scripts, file redirection, and path conventions.
  • Ensure that terminology and examples do not assume a Windows environment; use neutral or cross-platform language and patterns.
GitHub Create Pull Request
Backup Azure Backup release notes - Archive .../main/articles/backup/backup-release-notes-archived.md
High 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 for Azure Backup release notes demonstrates a moderate Windows bias. Several features and examples reference Windows-specific tools (such as MARS agent, Microsoft Azure Backup Server, and PowerShell) without equivalent Linux alternatives or examples. Windows-centric solutions (MARS, MABS) are described in detail, while Linux backup scenarios (other than SAP HANA on RHEL) are rarely mentioned. PowerShell is frequently referenced for management tasks, with less emphasis on Azure CLI or Linux-native tooling. In some cases, Windows features are listed before Linux equivalents, and Linux-specific backup scenarios are underrepresented.
Recommendations
  • Provide Linux-specific examples and tooling (e.g., CLI commands, shell scripts) alongside or before Windows/PowerShell examples.
  • Highlight Linux-compatible backup agents and solutions where available, and clarify platform support for each feature.
  • Ensure parity in documentation for both Windows and Linux environments, especially for agent-based backup solutions and management workflows.
  • Explicitly mention support for popular Linux distributions and workloads (beyond SAP HANA on RHEL), such as Ubuntu, CentOS, and containerized applications.
  • Include cross-platform guidance for backup and restore operations, avoiding exclusive reliance on Windows tools or terminology.
GitHub Create Pull Request
Backup Back up multiple SQL Server VMs from the vault ...rticles/backup/backup-sql-server-database-azure-vms.md
High 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 demonstrates a Windows bias in several ways: it consistently references Windows-specific components (e.g., AzureBackupWindowsWorkload extension, NT Service accounts), links to Windows-only troubleshooting scripts, and omits any mention of Linux-based SQL Server VMs or their backup procedures. All examples, instructions, and screenshots assume a Windows environment, with no guidance for Linux users. The documentation also references Windows tools and patterns (such as service accounts and extensions) without Linux equivalents or alternatives.
Recommendations
  • Explicitly state whether Linux-based SQL Server VMs are supported or not, and provide guidance for Linux users if supported.
  • Include examples, troubleshooting steps, and scripts for Linux environments (e.g., Bash, systemd services, Linux VM agent).
  • Reference and link to Linux-specific documentation, tools, and extensions where applicable.
  • Clarify any differences in backup configuration, agent installation, and permissions for Linux SQL Server VMs.
  • Provide parity in screenshots and step-by-step instructions for both Windows and Linux scenarios.
  • If certain features are Windows-only, clearly call this out and suggest alternatives for Linux users.
GitHub Create Pull Request
Backup Support matrix for Azure VM backups ...lob/main/articles/backup/backup-support-matrix-iaas.md
High 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 Windows bias in several areas. Windows-specific tools (MARS agent, DPM, MABS) are discussed in detail and supported for backup and restore, while their Linux equivalents are either unsupported or not mentioned. Windows scenarios and OS support are presented first and in greater detail, with Linux support relegated to separate, shorter sections. Restore instructions and examples frequently reference PowerShell and Windows-centric workflows, with no equivalent Linux CLI or automation examples. Linux backup options are limited, and unsupported scenarios are listed without alternative solutions or workarounds.
Recommendations
  • Provide Linux CLI (az CLI) and automation examples alongside PowerShell instructions for restore and backup operations.
  • Present Windows and Linux support matrices side-by-side or in parallel sections to avoid Windows-first ordering.
  • Expand Linux backup and restore documentation to include more detailed workflows, troubleshooting, and supported scenarios.
  • Mention Linux-native backup tools or third-party solutions where Azure-native options are unavailable.
  • Clarify limitations for Linux and offer guidance or alternatives for unsupported scenarios (e.g., file-level restore on LVM/RAID, Docker mount points).
  • Ensure parity in documentation detail, examples, and troubleshooting between Windows and Linux environments.
GitHub Create Pull Request
Backup MABS & System Center DPM support matrix ...main/articles/backup/backup-support-matrix-mabs-dpm.md
High 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 is heavily focused on Windows environments, with all examples, supported operating systems, and deployment scenarios centered around Windows Server versions and Microsoft technologies. There is no mention of Linux support, Linux-based workloads, or cross-platform backup scenarios. All instructions, requirements, and compatibility matrices are exclusively for Windows, and Windows terminology and tools are used throughout.
Recommendations
  • Explicitly state whether Linux operating systems and workloads are supported or not in the context of MABS/DPM.
  • If Linux support exists, add equivalent examples, compatibility matrices, and deployment instructions for Linux environments.
  • Include guidance on backing up Linux VMs or workloads, both on-premises and in Azure, using MABS/DPM or alternative Azure Backup solutions.
  • Mention any limitations or differences in backup/restore workflows for Linux compared to Windows.
  • Provide links to documentation for Linux backup scenarios if MABS/DPM does not support them, or suggest alternative Azure Backup products for Linux workloads.
GitHub Create Pull Request
Backup Support matrix for the MARS agent ...in/articles/backup/backup-support-matrix-mars-agent.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation for the MARS agent is exclusively focused on Windows environments. All examples, supported operating systems, and instructions pertain only to Windows (including Windows Server and Windows desktop editions). There is no mention of Linux support, Linux equivalents, or cross-platform considerations. Windows-specific tools and patterns (such as PowerShell, MMC, registry edits, NTFS, VSS, DISM.exe) are referenced throughout, with no alternatives or parity for Linux systems. The documentation assumes a Windows-centric audience and does not address Linux users or scenarios.
Recommendations
  • Clearly state at the beginning that the MARS agent is only supported on Windows, and suggest alternatives for Linux environments (such as Azure Backup for Linux or other agents).
  • Provide links or references to documentation for Linux backup solutions within Azure, so Linux users can find relevant guidance.
  • If partial Linux support exists or is planned, include a support matrix for Linux operating systems and examples of installation, configuration, and backup/restore operations on Linux.
  • Avoid using Windows-specific terminology (e.g., registry edits, MMC, PowerShell) without clarifying that these are not applicable to Linux, and provide Linux equivalents where possible.
  • Add a comparison table or section that highlights differences between Windows and Linux backup approaches in Azure, helping users choose the right solution for their platform.
GitHub Create Pull Request
Backup Back up SQL Server from the Azure VM blade using Azure Backup ...ckup/backup-sql-server-database-from-azure-vm-blade.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily focused on backing up SQL Server databases on Azure VMs using Windows-specific tools and patterns. It exclusively references the AzureBackupWindowsWorkload extension, NT Service accounts, and Windows-based SQL Server VM configurations. There are no examples, instructions, or mentions of Linux-based SQL Server VMs or their backup processes. The documentation assumes a Windows environment throughout and does not provide parity for Linux users.
Recommendations
  • Add explicit guidance for backing up SQL Server databases running on Linux-based Azure VMs, if supported.
  • Mention and document any Linux-specific extensions, agents, or service accounts required for backup operations.
  • Include Linux command-line examples (e.g., Bash, Azure CLI on Linux) alongside Windows/PowerShell examples.
  • Clarify any differences in backup configuration steps between Windows and Linux SQL Server VMs.
  • If Linux is not supported, state this clearly in the prerequisites or introduction to avoid confusion.
GitHub Create Pull Request
Backup Back up SQL Server always on availability groups ...les/backup/backup-sql-server-on-availability-groups.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page focuses exclusively on backing up SQL Server Always On Availability Groups in Azure VMs, implicitly assuming a Windows environment. There is no mention of Linux-based SQL Server deployments, nor are there examples or guidance for Linux VMs. All references to backup extensions, registration, and failover scenarios are described in the context of Windows VMs, with no parity for Linux tools, commands, or patterns.
Recommendations
  • Explicitly state whether Linux-based SQL Server AGs are supported or not, and provide guidance for Linux if supported.
  • Include examples and instructions for configuring backups on Linux VMs, including any differences in extension installation, registration, and failover handling.
  • Mention Linux-specific tools or commands (e.g., shell scripts, systemd services) where appropriate, alongside Windows/Powershell equivalents.
  • Clarify any limitations or differences in Azure Backup support for SQL Server AGs on Linux versus Windows.
  • Ensure that diagrams and deployment scenarios include Linux VM nodes if supported, and describe their registration and backup processes.
GitHub Create Pull Request
← Previous Page 9 of 65 Next →