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 151-175 of 1604 flagged pages
Backup Restore options with Microsoft Azure Recovery Services (MARS) agent ...kup/about-restore-microsoft-azure-recovery-services.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 is heavily focused on Windows environments, with all examples and instructions referencing Windows Server, PowerShell, and Windows-specific utilities like robocopy. There are no Linux equivalents or examples provided, and the restore options are described exclusively in the context of Windows systems. This creates a strong Windows bias and excludes Linux administrators from understanding how (or if) the MARS agent can be used in non-Windows environments.
Recommendations
  • Clarify whether the MARS agent supports Linux systems, and if not, explicitly state its Windows-only scope.
  • If Linux support exists or is planned, provide equivalent restore instructions and examples for Linux environments, including command-line tools and workflows.
  • Mention Linux file copy tools (e.g., rsync, cp) alongside robocopy when discussing file transfer from mounted recovery points.
  • Add a section comparing restore options and limitations between Windows and Linux (if applicable).
  • Ensure that prerequisites and automation examples include Linux-specific guidance where relevant.
GitHub Create Pull Request
Backup About the Azure Virtual Machine restore process ...cs/blob/main/articles/backup/about-azure-vm-restore.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 exhibits Windows bias in several ways: examples and links for encrypted VM restore are exclusively for Windows VMs, and the restore process for encrypted VMs specifically mentions using PowerShell (a Windows-centric tool) without mentioning Linux alternatives. There are no references to Linux VM restore scenarios, nor are Linux-specific tools or commands provided. The documentation links for disk encryption also point only to Windows VM guides.
Recommendations
  • Add equivalent Linux VM restore scenarios and examples, especially for encrypted VMs.
  • Include instructions for restoring encrypted Linux VMs, referencing Azure CLI or other cross-platform tools instead of only PowerShell.
  • Provide links to Linux disk encryption documentation (e.g., for VMs using DM-Crypt or Azure Disk Encryption for Linux).
  • Ensure that restore steps and troubleshooting guides cover both Windows and Linux VMs equally, with clear parity in examples and tool recommendations.
GitHub Create Pull Request
Backup Azure Backup - Archive tier overview ...docs/blob/main/articles/backup/archive-tier-support.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 focusing exclusively on Azure Virtual Machines (which are often Windows-based), SQL Server (a Windows-centric workload), and SAP HANA in Azure VMs. The 'Supported clients' section lists PowerShell before CLI, and there are no explicit Linux or Bash examples, nor any mention of Linux-specific workloads or tools. Screenshots and step-by-step instructions reference the Azure portal and PowerShell, with no parity for Linux command-line usage or Linux VM scenarios.
Recommendations
  • Add explicit examples for Linux VMs, including backup and archive operations for Linux workloads.
  • Provide Bash/CLI command examples alongside PowerShell, and list CLI before or alongside PowerShell in 'Supported clients'.
  • Include screenshots or instructions for Linux users, such as using Azure CLI on Linux systems.
  • Mention Linux-specific backup scenarios and clarify if archive tier support applies equally to Linux VMs.
  • Ensure documentation covers both Windows and Linux environments with equal depth and visibility.
GitHub Create Pull Request
Backup Back up and restore Active Directory using Azure Backup ...ain/articles/backup/active-directory-backup-restore.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 is heavily oriented toward Windows environments, with all examples, scripts, and tools (e.g., PowerShell, ntdsutil.exe, Active Directory Domain Services) being Windows-specific. There are no Linux equivalents or examples, and the guidance assumes the use of Windows Server for domain controllers. Windows terminology and tools are used exclusively and presented first, with no mention of Linux-based alternatives or cross-platform scenarios.
Recommendations
  • Include explicit statements clarifying that Active Directory domain controllers are Windows-only, but acknowledge Samba as a potential open-source alternative for Linux environments.
  • Provide guidance or links for backing up and restoring Samba-based domain controllers on Linux, if relevant to Azure Backup.
  • Add examples or notes for Linux-based backup tools and procedures where possible, or clarify Azure Backup's limitations regarding non-Windows domain controllers.
  • Where PowerShell is used, offer Bash or shell script equivalents for any operations that could be performed on Linux (e.g., querying backup status, interacting with Azure Backup APIs).
  • Clearly state platform limitations and recommend best practices for Linux administrators who may be seeking similar functionality.
GitHub Create Pull Request
Backup Automation in Azure Backup ...re-docs/blob/main/articles/backup/automation-backup.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 page demonstrates a Windows bias by repeatedly mentioning PowerShell as a primary automation method and example, listing PowerShell before CLI and other cross-platform tools, and providing workflow examples that center on PowerShell and Azure Automation Runbooks (which are often Windows-centric). There are no explicit Linux shell (bash) or cross-platform CLI examples, and no mention of Linux-specific patterns or considerations. The video walkthroughs also appear to focus on PowerShell-based workflows.
Recommendations
  • Add explicit bash/CLI examples alongside PowerShell for each automation scenario.
  • When listing automation methods, alternate or randomize the order, or explicitly state both Windows and Linux options.
  • Include Linux-centric automation workflows, such as using bash scripts, cron jobs, or Linux-native tools in conjunction with Azure CLI.
  • Provide sample code snippets for both PowerShell and bash/CLI in key sections.
  • Clarify which automation methods are cross-platform and highlight any differences in usage or capabilities between Windows and Linux.
  • Ensure video walkthroughs or linked resources include Linux/CLI demonstrations.
GitHub Create Pull Request
Backup Azure Backup glossary ...ocs/blob/main/articles/backup/azure-backup-glossary.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 glossary page for Azure Backup documentation demonstrates a Windows bias in several ways. Windows-specific technologies (such as VSS, DPM, MABS, MARS Agent) are referenced and explained in detail, while Linux equivalents are either omitted or mentioned only briefly. For example, application-consistent backup describes VSS in detail and only refers to 'pre or post scripts for Linux' without further explanation or links. Many backup scenarios and tools (e.g., Bare Metal Backup, System State Backup, DPM, MABS) are Windows-centric, with no Linux alternatives or parity. References to Azure PowerShell are explicit, but Linux CLI or scripting approaches are not highlighted. The glossary also links to Windows-specific documentation (e.g., VSS) and provides examples and terminology that are more relevant to Windows workloads.
Recommendations
  • Add equivalent Linux backup concepts and tooling (e.g., LVM snapshots, fsfreeze, etc.) where Windows-specific technologies like VSS are mentioned.
  • Provide links to Linux documentation and examples for backup scenarios, especially for application-consistent and file-system-consistent backups.
  • Include Linux-centric backup agents or methods (such as Azure Backup for Linux VMs, or third-party Linux backup solutions) alongside Windows tools like MARS, DPM, and MABS.
  • Ensure parity in examples and terminology, describing both Windows and Linux approaches for each relevant glossary entry.
  • Highlight Azure CLI usage and scripting for Linux environments as prominently as Azure PowerShell is for Windows.
GitHub Create Pull Request
Backup Support matrix for Azure Data Lake Storage Vaulted Backup ...ackup/azure-data-lake-storage-backup-support-matrix.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 references configuration and management via Azure portal, PowerShell, or Azure CLI, but lists PowerShell before Azure CLI and does not provide explicit Linux-oriented examples or mention Bash/Shell scripting. There are no references to Linux-specific tools, nor are Linux command-line patterns highlighted. The ordering and emphasis suggest a Windows-first approach, and the lack of Linux examples or parity in tooling may hinder Linux users.
Recommendations
  • Ensure that Azure CLI (cross-platform) is mentioned before or alongside PowerShell in all instructions and links.
  • Provide explicit Bash/Shell scripting examples for common backup and restore operations.
  • Include notes or sections highlighting Linux compatibility and any platform-specific considerations.
  • Avoid listing Windows-centric tools (PowerShell) before cross-platform tools (Azure CLI) unless contextually justified.
  • Add troubleshooting tips or FAQs for Linux environments, especially for command-line operations.
GitHub Create Pull Request
Backup What is Azure Kubernetes Service (AKS) Backup? ...les/backup/azure-kubernetes-service-backup-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 Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. While the main content is platform-neutral and focuses on AKS concepts, the 'Related content' section lists 'Back up AKS by using Azure PowerShell' before 'Restore AKS by using the Azure CLI', suggesting a Windows-first orientation. The explicit mention of PowerShell as a backup tool and the absence of Linux-specific examples or references to Bash or Linux-native tools further reinforce this bias. There are no explicit Linux examples, and PowerShell (a Windows-centric tool) is highlighted as a primary method for backup operations.
Recommendations
  • Provide backup examples using Bash scripts or Linux-native tools alongside PowerShell.
  • List Azure CLI and Bash-based instructions before or alongside PowerShell in 'Related content' and throughout the documentation.
  • Explicitly mention cross-platform compatibility for all command-line tools and clarify that both Windows and Linux users are supported.
  • Include links to Linux-specific guides or troubleshooting for AKS backup and restore operations.
  • Ensure parity in example scripts, showing both PowerShell and Bash/CLI equivalents where possible.
GitHub Create Pull Request
Backup Azure Kubernetes Service (AKS) backup using Azure Backup prerequisites ...kup/azure-kubernetes-service-cluster-backup-concept.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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Azure portal and PowerShell as primary management interfaces for AKS backup operations. Examples and next steps reference Azure PowerShell before Azure CLI, and there are no explicit Linux shell or bash examples. The documentation assumes familiarity with Windows-centric tools and patterns, such as PowerShell and the Azure portal, while Linux-native workflows (e.g., bash scripting, kubectl usage from Linux terminals) are not mentioned or illustrated.
Recommendations
  • Provide explicit bash/Linux shell examples for AKS backup operations using Azure CLI and kubectl.
  • List Azure CLI instructions before or alongside PowerShell in all relevant sections and next steps.
  • Include guidance for managing AKS backup from Linux/macOS environments, such as using terminal commands and scripting.
  • Clarify that all operations can be performed from Linux systems, and highlight any platform-specific differences or requirements.
  • Add references to Linux-native tools and workflows where applicable, ensuring parity in documentation for non-Windows users.
GitHub Create Pull Request
Backup Restore Azure Kubernetes Service (AKS) using Azure Backup ...les/backup/azure-kubernetes-service-cluster-restore.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 by explicitly referencing Azure PowerShell as an alternative restore method and linking to a PowerShell-specific guide, without mentioning or providing equivalent examples for Linux-native tools (such as Azure CLI or Bash scripting). The main restore workflow is GUI-based, which is cross-platform, but the only command-line option highlighted is PowerShell. There are no Linux or Azure CLI examples, nor is there guidance for Linux users, which may hinder parity and accessibility for non-Windows environments.
Recommendations
  • Add equivalent Azure CLI (az) examples and workflows for restoring AKS clusters using Azure Backup.
  • Explicitly mention that both Azure PowerShell and Azure CLI can be used, and provide links to Linux/Bash-friendly documentation.
  • Include sample scripts or walkthroughs for Linux users, such as Bash shell commands, to complement the PowerShell instructions.
  • Ensure that references to command-line tools do not prioritize Windows/PowerShell over cross-platform alternatives.
  • Review screenshots and UI instructions to confirm they are not Windows-specific, and clarify any OS-agnostic steps.
GitHub Create Pull Request
Backup Back up file data with MABS ...re-docs/blob/main/articles/backup/back-up-file-data.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 for backing up file data with MABS is heavily oriented toward Windows environments. It references Windows-specific features (such as Data Deduplication and VSS), uses terminology and UI patterns from Windows (e.g., 'Properties', 'Previous Versions'), and does not provide examples or guidance for Linux systems. There are no Linux-specific instructions, screenshots, or parity notes, despite mentioning that MABS can protect both server and client computers.
Recommendations
  • Add explicit instructions and examples for backing up Linux machines with MABS, including agent installation, supported file systems, and recovery procedures.
  • Include Linux-specific prerequisites, such as required packages, permissions, and supported distributions.
  • Document any differences in backup and recovery workflows between Windows and Linux clients.
  • Mention Linux equivalents for Windows features (e.g., alternatives to VSS, deduplication support) or clarify limitations.
  • Provide screenshots or CLI examples for Linux systems where applicable.
  • Ensure that references to features or UI elements are not exclusively Windows-centric, or provide Linux alternatives where possible.
GitHub Create Pull Request
Backup Back up Azure Kubernetes Service by using Azure Backup ...cles/backup/azure-kubernetes-service-cluster-backup.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 Windows bias by referencing Azure PowerShell as the only CLI alternative to the Azure Portal, both in the introduction and in the 'Next steps' section. There are no examples or instructions for using Azure CLI, Bash, or Linux-native tools for AKS backup operations. The documentation does not mention or provide parity for Linux users, who typically use Azure CLI and Bash scripts, nor does it provide cross-platform command examples.
Recommendations
  • Add Azure CLI examples alongside or before Azure PowerShell examples for all backup and restore operations.
  • Explicitly mention that both Azure CLI and PowerShell can be used, and provide links to Linux/Bash instructions where relevant.
  • Ensure screenshots and step-by-step instructions are not Windows-centric (e.g., avoid only showing PowerShell or Windows UI).
  • Include Bash script samples for deploying backup hooks and configuring AKS backup, in addition to kubectl commands.
  • Review all references to command-line tools and ensure Linux parity is maintained throughout the documentation.
GitHub Create Pull Request
Backup Back up Azure Local virtual machines with MABS ...e-stack-hyperconverged-infrastructure-virtual-machines.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 demonstrates a strong Windows bias. All command-line examples use Windows tools (PowerShell, .exe installers), and instructions for agent installation and firewall configuration are exclusively Windows-centric. Linux prerequisites are mentioned briefly, but there are no Linux-specific backup or recovery examples, nor any guidance for Linux users on how to perform equivalent operations. Windows terminology and patterns (Hyper-V, VHD, Windows authentication methods) are used throughout, with no parity for Linux environments.
Recommendations
  • Provide Linux-specific command-line examples for agent installation, configuration, and backup/recovery operations (e.g., using shell commands or Linux package managers).
  • Include instructions for managing firewall rules and agent deployment on Linux VMs, not just Windows/PowerShell.
  • Clarify which steps are applicable to Linux VMs and highlight any differences or limitations.
  • Add screenshots or walkthroughs of the process for Linux VMs where the UI or workflow differs.
  • Expand the 'Linux prerequisites' section to include troubleshooting, supported distributions, and recovery procedures.
  • Where Windows authentication methods are mentioned, note Linux equivalents (e.g., SSH keys, certificate-based auth).
GitHub Create Pull Request
Backup Back up Hyper-V virtual machines with MABS ...ticles/backup/back-up-hyper-v-virtual-machines-mabs.md
High 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 is heavily focused on Windows environments, specifically Hyper-V on Windows Server. All examples, procedures, and screenshots are for Windows Server and Windows-based tools (MABS, Hyper-V, VSS). Linux is only mentioned briefly as a supported guest OS, with no detailed instructions, examples, or screenshots for Linux VMs. Windows-specific features and registry keys are referenced, and there is no parity in guidance for Linux VM backup or recovery.
Recommendations
  • Add detailed backup and recovery procedures for Linux VMs, including step-by-step instructions and screenshots.
  • Provide examples of item-level recovery for Linux VMs, noting any limitations or differences compared to Windows VMs.
  • Include Linux-specific prerequisites and troubleshooting steps, such as supported file systems, integration services, and consistency levels.
  • Clarify which features are Windows-only and suggest Linux alternatives or workarounds where possible.
  • Ensure that Linux scenarios are presented with equal prominence and detail as Windows scenarios.
GitHub Create Pull Request
Backup Tutorial - Back up Azure Managed Disks using Azure Backup ...main/articles/backup/back-up-managed-disks-tutorial.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 primarily describes backing up Azure Managed Disks using the Azure portal, which is platform-agnostic. However, when scripting is mentioned, PowerShell is listed before Azure CLI, and the only explicit script references in the main flow are to PowerShell and CLI, with PowerShell mentioned first. There are no Linux-specific examples, nor is Bash or Linux tooling highlighted. The documentation does not provide parity in examples or guidance for Linux users, and the scripting section implicitly prioritizes Windows/PowerShell.
Recommendations
  • When mentioning scripting options, list Azure CLI before or alongside PowerShell, as CLI is cross-platform and preferred by many Linux users.
  • Provide explicit Bash/Linux shell examples for common tasks, such as automating disk backup, alongside PowerShell examples.
  • Include notes or sections clarifying that all portal-based steps are OS-agnostic, and highlight any differences for Linux users if applicable.
  • Reference Linux-friendly tools or workflows (e.g., Bash scripts, automation via cron) where appropriate.
  • Ensure that links to scripting guides (PowerShell/CLI) are presented with equal prominence and that Linux users are not implicitly directed to Windows-centric tools.
GitHub Create Pull Request
Backup Architecture Overview ...-docs/blob/main/articles/backup/backup-architecture.md
High 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 in several ways: backup scenarios and tooling (MARS agent, DPM, MABS) are described exclusively for Windows, with Linux support either omitted or explicitly stated as unsupported. Windows tools and patterns (VSS, MARS agent) are discussed in detail, while Linux equivalents or alternatives are not mentioned. Examples and instructions for backup setup focus on Windows environments, with no Linux parity or guidance.
Recommendations
  • Add explicit coverage of Linux backup scenarios, including supported methods and limitations.
  • Provide Linux-specific examples and tooling (such as Azure Backup integration with Linux agents or third-party solutions).
  • If Linux is not supported for certain backup methods, clarify alternatives or workarounds for Linux users.
  • Ensure that backup architecture diagrams and walkthroughs include both Windows and Linux environments where applicable.
  • List Linux support status in tables and matrices, not just as a footnote or omission.
  • Consider parity in terminology and process explanations (e.g., mention Linux snapshot mechanisms if discussing VSS for Windows).
GitHub Create Pull Request
Backup Troubleshoot data recovery from Microsoft Azure Backup Server by using Azure Backup ...ckup/backup-azure-alternate-dpm-server-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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Microsoft Azure Backup Server (MABS), which is a Windows-only product. All troubleshooting steps, error messages, and recommendations refer to Windows Server, Windows Client, and Windows-specific agents (such as DPM and Azure Backup agent). There are no examples, references, or troubleshooting steps for Linux systems or Linux backup agents, nor is there mention of Linux-compatible recovery workflows.
Recommendations
  • Clearly state in the introduction that MABS is a Windows-only product, and provide links to equivalent Linux backup and recovery documentation for Azure.
  • Add a section or cross-reference for troubleshooting data recovery on Linux systems using Azure Backup (e.g., for Azure Backup for Linux VMs or Azure File shares).
  • Include examples and error messages relevant to Linux backup agents and recovery scenarios, if supported.
  • If the product does not support Linux, clarify this limitation and guide Linux users to appropriate Azure solutions.
GitHub Create Pull Request
Backup Restore VMs by using the Azure portal using Azure Backup ...b/main/articles/backup/backup-azure-arm-restore-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 exhibits a moderate Windows bias. Windows-specific examples, links, and terminology are frequently presented before or instead of Linux equivalents. PowerShell is referenced as the primary automation tool for VM creation and disk restore, with no equivalent Bash or Azure CLI examples. Many guidance links and scenarios point to Windows documentation or use Windows-centric terminology (e.g., Hybrid Use Benefit, domain controller restore, NSG examples, and references to RDP and CMD commands). Linux-specific restore scenarios are only briefly mentioned, and there are no step-by-step Linux restore examples or references to Linux tools (such as SSH, cloud-init, or Azure CLI) in the main restore workflows.
Recommendations
  • Provide Linux-specific examples and workflows alongside Windows examples, especially for disk restore, VM creation, and post-restore steps.
  • Include Azure CLI and Bash script examples for all automation steps currently described with PowerShell.
  • Add links to Linux documentation (e.g., restoring Linux VMs, troubleshooting Linux VM restores, managing SSH keys) wherever Windows documentation is referenced.
  • Explicitly mention Linux restore considerations in all relevant scenarios (e.g., network configuration, managed identities, availability sets, cloud-init password resets).
  • Ensure parity in screenshots and UI walkthroughs by including examples with Linux VMs.
  • Clarify when guidance applies to both Windows and Linux, and avoid using Windows terminology as the default (e.g., RDP, CMD, domain controllers) without Linux equivalents.
GitHub Create Pull Request
Backup Create backup policies via REST API in Azure Backup ...up/backup-azure-arm-userestapi-createorupdatepolicy.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 Timezones Missing Linux Example
Summary
The documentation page exhibits subtle Windows bias primarily through the use of Windows-centric time zones (e.g., 'Pacific Standard Time') in examples and the ordering of examples, which consistently start with Azure VM (typically Windows workloads) before Linux or cross-platform workloads. There is no explicit mention of Linux-specific patterns, tools, or time zone formats, nor are there examples tailored to Linux VMs or Linux-specific backup scenarios. The documentation does not provide parity for Linux users in terms of examples, time zone handling, or guidance for Linux-centric environments.
Recommendations
  • Include explicit examples for Linux VMs, such as Ubuntu or CentOS, demonstrating backup policy creation for Linux workloads.
  • Use cross-platform or IANA time zone identifiers (e.g., 'America/Los_Angeles') in examples, or clarify how to specify time zones for Linux environments.
  • Add notes or sections highlighting any differences or considerations when backing up Linux VMs versus Windows VMs.
  • Ensure that examples and guidance are balanced between Windows and Linux, possibly by alternating the order or providing tabs for both OS types.
  • Reference Linux command-line tools (e.g., curl, jq) for REST API calls alongside any PowerShell or Windows tools, if mentioned elsewhere.
GitHub Create Pull Request
Backup Back Up Azure VMs in a Recovery Services Vault ...b/main/articles/backup/backup-azure-arm-vms-prepare.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 provides detailed, step-by-step instructions for installing the VM agent on Windows, including download links, file paths, and verification steps. In contrast, the Linux instructions are brief, generic, and lack concrete examples or commands. Windows-specific tools and patterns (MSI installer, file paths, right-click actions) are mentioned exclusively, while Linux equivalents (e.g., package manager commands, verification steps) are omitted. The Windows instructions are presented first, reinforcing a Windows-first bias.
Recommendations
  • Provide explicit Linux installation commands (e.g., apt-get, yum, zypper) for installing/updating the Azure Linux agent.
  • Include Linux-specific verification steps, such as checking agent version via command line (e.g., waagent --version) and relevant file paths.
  • Present Windows and Linux instructions with equal detail and in parallel, rather than listing Windows first.
  • Mention Linux troubleshooting steps or links alongside Windows troubleshooting.
  • Avoid Windows-centric language (e.g., 'right-click', 'MSI installer') without Linux equivalents.
GitHub Create Pull Request
Backup Back up an Exchange server via System Center DPM ...articles/backup/backup-azure-backup-exchange-server.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation exclusively describes backup procedures for Microsoft Exchange using System Center DPM, a Windows-only tool, with all examples and steps referencing Windows environments, tools, and paths. There is no mention of Linux equivalents, alternative cross-platform solutions, or parity for Linux-based Exchange deployments. PowerShell is referenced in related content, reinforcing the Windows-centric approach.
Recommendations
  • Clarify early in the documentation that System Center DPM is a Windows-only solution and suggest alternatives for Linux environments.
  • Provide guidance or links for backing up Exchange on Linux (if supported) or for Linux-based mail servers (e.g., Postfix, Dovecot) using Azure Backup or other Microsoft-supported tools.
  • Include examples or references for cross-platform backup tools where possible.
  • Balance related content by including automation or backup management examples for Linux (e.g., using Bash scripts or Azure CLI).
GitHub Create Pull Request
Backup Back up VMware VMs using Azure Backup Server ...n/articles/backup/backup-azure-backup-server-vmware.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 Tools Windows First Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All examples and instructions assume the use of Windows tools (e.g., Registry Editor, Certificate Import Wizard, PowerShell scripts), and there are no Linux equivalents or cross-platform alternatives provided. The documentation presumes Azure Backup Server is installed on Windows and omits any guidance for Linux-based administration or scripting. PowerShell is used exclusively for scripting tasks, and Windows registry modifications are required for configuration. Linux users are not addressed, and no Bash or Linux-native instructions are present.
Recommendations
  • Add instructions and examples for Linux environments, such as how to import certificates using Linux tools (e.g., openssl, update-ca-certificates).
  • Provide Bash script equivalents for PowerShell scripts, or clarify if the functionality is unavailable on Linux.
  • Clarify platform requirements early in the documentation (e.g., if MABS is Windows-only, state this explicitly).
  • Where registry edits are required, suggest alternative configuration methods for Linux (if supported), or note platform limitations.
  • Include notes or sections for Linux administrators, even if only to state that certain features/tools are not available.
  • If possible, provide cross-platform CLI examples (e.g., using Azure CLI, REST API) instead of only Windows GUI or PowerShell.
GitHub Create Pull Request
Backup Back up a SharePoint farm to Azure with DPM ...main/articles/backup/backup-azure-backup-sharepoint.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 Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows-centric tools and workflows, specifically System Center Data Protection Manager (DPM), which is a Windows-only product. All examples, instructions, and screenshots reference DPM and Windows interfaces, with no mention of Linux equivalents or cross-platform alternatives. The only automation reference is to PowerShell, a Windows-first scripting language, and there are no Linux command-line or tool examples provided.
Recommendations
  • Explicitly state DPM's platform limitations and mention if Linux support is unavailable.
  • Provide alternative solutions or workflows for Linux-based SharePoint deployments, if supported.
  • Include examples using cross-platform tools or Azure-native backup solutions that work on both Windows and Linux.
  • Offer parity in automation examples, such as Bash scripts or Azure CLI commands, alongside PowerShell.
  • Clarify prerequisites and supported environments, highlighting any OS-specific requirements.
GitHub Create Pull Request
Backup Offline seeding workflow for DPM and MABS using customer-owned disks with Azure Import/Export - Azure Backup ...les/backup/backup-azure-backup-server-import-export.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 is heavily oriented towards Windows environments, specifically System Center Data Protection Manager (DPM) and Microsoft Azure Backup Server (MABS), both of which are Windows-only products. All examples, prerequisites, and tooling references (such as AzureOfflineBackupDiskPrep.exe, Azure PowerShell, and requirements for Microsoft Edge/Internet Explorer) are Windows-specific. There is no mention of Linux equivalents, nor are there instructions or examples for performing offline seeding from Linux systems. The workflow assumes the use of Windows servers and tools throughout.
Recommendations
  • Explicitly state that DPM and MABS are Windows-only, and clarify Linux support status at the top of the article.
  • If Azure Backup supports offline seeding from Linux systems (e.g., via MARS agent or other means), provide equivalent Linux workflows, including supported tools and commands.
  • Include examples using Linux-compatible utilities (such as azcopy, Azure CLI, or shell scripts) for disk preparation and import job creation.
  • Mention browser requirements for Linux users (e.g., Chrome, Firefox) if applicable.
  • Reference documentation or workflows for Linux-based backup solutions where possible, or provide links to relevant Linux documentation.
GitHub Create Pull Request
Backup Back up a SharePoint farm to Azure with MABS ...articles/backup/backup-azure-backup-sharepoint-mabs.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 is heavily biased towards Windows environments. All instructions, tools, and examples assume the use of Windows servers, Windows command-line tools (CMD, Registry Editor), and Windows-specific paths and permissions. There are no references to Linux equivalents, nor any guidance for SharePoint deployments on non-Windows platforms. The use of tools like ConfigureSharePoint.exe, Registry Editor, and explicit references to Windows groups and permissions further reinforce the Windows-centric approach.
Recommendations
  • Clarify early in the documentation that MABS and SharePoint are Windows-only products, if that is the case. If Linux support is possible, provide explicit guidance for Linux environments.
  • If any part of the backup or restore process can be performed from Linux (e.g., Azure Backup operations, monitoring, or scripting), include Linux shell examples and instructions.
  • Mention cross-platform alternatives or limitations, and provide links to documentation for Linux-based backup solutions if SharePoint or MABS is not supported on Linux.
  • Where possible, abstract instructions to be OS-agnostic (e.g., use generic file paths, avoid registry-specific steps, provide both CMD and Bash equivalents for commands).
  • Add a section on prerequisites and limitations that clearly states OS requirements and whether Linux is supported or not.
GitHub Create Pull Request
← Previous Page 7 of 65 Next →