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 276-300 of 1604 flagged pages
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation primarily describes backup operations using the Azure portal, which is platform-agnostic, but when mentioning automation or scripting, it lists PowerShell before CLI and does not provide explicit Linux-specific examples or guidance. The references to scripting use 'PowerShell/CLI' phrasing, with PowerShell mentioned first, and there are no bash or Linux shell script examples. There is no mention of Linux-specific tools, nor are Linux usage patterns (such as az CLI in bash) highlighted. The documentation does not address Linux user needs directly, and the scripting guidance is Windows-centric.
Recommendations
  • Provide explicit examples using Azure CLI in bash or Linux shell environments alongside PowerShell examples.
  • When listing automation options, alternate the order (e.g., CLI/PowerShell) or group them together as 'CLI/PowerShell' to avoid Windows-first bias.
  • Include notes or sections for Linux users, such as how to run az CLI commands in Linux terminals.
  • Add links to Linux-specific documentation or troubleshooting guides.
  • Ensure parity in screenshots and instructions for both Windows and Linux environments where applicable.
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-11 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 oriented toward Windows environments, specifically System Center Data Protection Manager (DPM) and Microsoft Azure Backup Server (MABS), which are Windows-only products. All examples, tools, and prerequisites assume a Windows OS: references to Microsoft Edge/Internet Explorer, BitLocker, and Azure PowerShell are made without mention of Linux alternatives. The disk preparation utility (AzureOfflineBackupDiskPrep.exe) is a Windows executable, and all command-line instructions use Windows syntax. There are no Linux equivalents, examples, or guidance for performing offline seeding from Linux servers, nor is there discussion of cross-platform compatibility.
Recommendations
  • Explicitly state that the workflow is only supported on Windows, and clarify OS limitations early in the document.
  • If possible, provide guidance or alternatives for Linux-based backup scenarios, including whether offline seeding is supported for Linux workloads and what tools or workflows are available.
  • Include examples or references for Linux users, such as using Azure CLI, Bash scripts, or Linux-compatible disk preparation methods if available.
  • Mention browser requirements for Linux (e.g., Chrome, Firefox) if the Azure portal or related workflows can be accessed from Linux.
  • Provide parity in documentation for Linux backup solutions (e.g., Azure Backup for Linux VMs), or link to relevant Linux documentation if offline seeding is not supported.
GitHub Create Pull Request
Backup Back up Exchange server with Azure Backup Server ...lob/main/articles/backup/backup-azure-exchange-mabs.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively describes backup and recovery procedures for Exchange servers using Microsoft Azure Backup Server (MABS), a Windows-only tool. All instructions, screenshots, and file paths (e.g., C:\Program Files\...) are Windows-centric, with no mention of Linux equivalents, cross-platform alternatives, or Linux-specific guidance. There are no PowerShell examples, but the entire workflow assumes a Windows environment and Windows server management patterns.
Recommendations
  • Explicitly state that MABS is a Windows-only solution and clarify platform limitations at the beginning of the article.
  • Provide guidance or links for backing up Exchange-like workloads on Linux, or suggest cross-platform alternatives where possible.
  • If Azure Backup supports Linux workloads, include a section or links describing backup procedures for Linux servers.
  • Where file paths or tools are mentioned, clarify their platform specificity and suggest Linux equivalents if applicable.
  • Add a comparison table or sidebar outlining backup options for both Windows and Linux environments.
GitHub Create Pull Request
Backup Monitor Azure Backup protected workloads ...les/backup/backup-azure-monitoring-built-in-monitor.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-centric backup tools (DPM, MABS, MARS) and linking to management guides specifically for Windows Server. There are no Linux-specific backup tool mentions, examples, or instructions, and Windows tools are discussed exclusively when describing backup item management and monitoring.
Recommendations
  • Include examples and instructions for monitoring Azure Backup workloads that originate from Linux servers or workloads.
  • Mention Linux-compatible backup agents or solutions (e.g., Azure Backup for Linux VMs, Azure CLI usage for Linux).
  • Provide parity in documentation by linking to Linux-specific management guides alongside Windows Server guides.
  • Clarify whether features and monitoring capabilities apply equally to Linux workloads, and explicitly describe any differences.
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-11 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 and instructions assume the use of Windows environments and tools (such as ConfigureSharePoint.exe and PowerShell), with no mention of Linux alternatives or cross-platform backup solutions. There are no Linux-specific instructions, examples, or references to equivalent open-source or Azure-native tools that could be used on non-Windows platforms.
Recommendations
  • Include information about cross-platform backup solutions, such as Azure Backup's support for Linux workloads or third-party tools.
  • Provide Linux-specific instructions or examples where possible, especially for Azure-native backup and restore operations.
  • Mention open-source alternatives or Azure CLI commands that can be used on Linux systems for similar backup/restore tasks.
  • Clarify early in the documentation that DPM is a Windows-only solution and suggest alternatives for Linux-based SharePoint or hybrid environments.
  • Add parity in monitoring and automation examples by including Bash/CLI scripts alongside PowerShell.
GitHub Create Pull Request
Backup Security features that protect hybrid backups .../main/articles/backup/backup-azure-security-feature.md
High Priority View Details →
Scanned: 2026-01-11 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 page focuses exclusively on Windows-centric backup tools (MABS, DPM, MARS), with no mention of Linux backup agents, Linux-specific workflows, or examples. All instructions, error messages, and feature descriptions are tailored to Windows environments and tools, including PowerShell commands. There is no parity for Linux users or administrators, and Linux backup scenarios are not addressed.
Recommendations
  • Add sections or examples for Linux-based backup scenarios, including supported agents and workflows.
  • Mention Linux-compatible backup tools (such as Azure Backup for Linux VMs or third-party agents) and clarify feature availability for Linux workloads.
  • Provide Linux command-line examples (e.g., bash, CLI) alongside PowerShell commands where relevant.
  • Clarify in the introduction which features are Windows-only and provide guidance or links for Linux users.
  • Include troubleshooting and recovery steps for Linux environments if supported.
  • Ensure parity in screenshots and UI instructions for Linux-based management tools (if available).
GitHub Create Pull Request
Backup Troubleshoot encrypted Azure VM backup errors ...icles/backup/backup-azure-encrypted-vm-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the only CLI example for configuring permissions, without mentioning Linux equivalents such as Azure CLI or Bash. There are no Linux-specific instructions or examples, and Windows tooling (PowerShell) is mentioned before any cross-platform alternatives.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell for all command-line instructions.
  • Explicitly state that steps apply to both Windows and Linux VMs, and highlight any differences.
  • Add troubleshooting steps and examples relevant to Linux environments, such as using SSH or Linux-native tools.
  • Ensure parity in documentation by listing cross-platform tools before or alongside Windows-specific tools.
GitHub Create Pull Request
Backup Troubleshoot the Azure Backup agent ...main/articles/backup/backup-azure-mars-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation for troubleshooting the Azure Backup (MARS) agent is heavily Windows-centric. All examples, tools, and troubleshooting steps reference Windows-specific components (MMC console, Task Scheduler, Registry, Internet Explorer, Device Manager, vssadmin, etc.), and PowerShell commands. There is no mention of Linux equivalents, nor any guidance for non-Windows platforms. The documentation assumes the user is operating in a Windows environment throughout.
Recommendations
  • Add a clear statement at the top specifying platform support (e.g., if MARS agent is Windows-only, clarify this).
  • If Linux or cross-platform backup agents exist, link to their troubleshooting documentation.
  • Where possible, provide Linux equivalents for troubleshooting steps (e.g., checking network connectivity, proxy settings, disk space, antivirus exclusions).
  • Include examples using Linux tools (such as systemctl, journalctl, cron, bash commands) where relevant.
  • Mention browser-agnostic steps for credential downloads, rather than focusing on Internet Explorer.
  • If PowerShell is required, note alternatives for Linux (such as Azure CLI or Bash scripts).
  • Clarify which troubleshooting steps are not applicable to Linux, and provide guidance for Linux users.
GitHub Create Pull Request
Backup Recover files and folders from Azure VM backup .../articles/backup/backup-azure-restore-files-from-vm.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows terminology, tools, and patterns are frequently mentioned first or in greater detail. Windows-specific instructions (e.g., registry edits, Storage Spaces, drive letters, File Explorer) are more prominent and detailed than Linux equivalents. PowerShell is referenced in 'Next steps' before CLI, and some troubleshooting steps (like registry changes) are only provided for Windows. Linux instructions are present but sometimes less detailed or appear after Windows sections.
Recommendations
  • Present Windows and Linux instructions in parallel, rather than Windows-first ordering.
  • Provide equally detailed troubleshooting steps for Linux (e.g., more guidance for LVM/RAID, common errors, permissions).
  • Include Linux-specific tools and patterns (e.g., mention file managers, SELinux, systemd services) where relevant.
  • Reference Azure CLI before or alongside PowerShell in 'Next steps' and throughout the guide.
  • Add more screenshots and examples for Linux workflows to match Windows parity.
  • Clarify any differences in limitations or performance for Linux, not just Windows.
  • Ensure all configuration changes (e.g., registry for Windows, config files for Linux) are explained for both platforms.
GitHub Create Pull Request
Backup Restore Key Vault key & secret for encrypted Azure VM ...ain/articles/backup/backup-azure-restore-key-secret.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All examples and instructions use PowerShell cmdlets, with file paths and tooling (e.g., Set-AzCurrentStorageAccount, Get-AzStorageBlobContent) that are native to Windows environments. Even when mentioning Linux VMs, the restore process is described using PowerShell, with no Bash, Azure CLI, or Linux-native alternatives. Windows file paths (C:\) are used throughout, and there is no guidance for performing these tasks on Linux or macOS systems.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for Linux and macOS users.
  • Include instructions for restoring keys and secrets using Linux file paths and tools (e.g., /home/user/vmencryption_config.json).
  • Add a section explicitly describing the process for Linux administrators, including prerequisites and environment setup.
  • Mention cross-platform compatibility of Azure tools and clarify which steps require Windows/PowerShell and which can be performed on Linux.
  • Ensure that references to backup and restore articles include both PowerShell and Azure CLI options.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias. PowerShell is the only command-line example provided for identifying a VM's associated key vault, with no equivalent Linux (Azure CLI or Bash) example. The reference to Azure BitLocker for Windows comes before dm-crypt for Linux in the ADE section, and Windows terminology/tools are mentioned first or exclusively in several places. There is no explicit Linux command-line example, and the documentation assumes familiarity with Windows-centric tools and patterns.
Recommendations
  • Add equivalent Azure CLI or Bash examples alongside PowerShell commands, especially for tasks like identifying the key vault associated with a VM.
  • When describing ADE, present Windows and Linux encryption mechanisms in parallel or alternate order to avoid Windows-first bias.
  • Explicitly mention Linux-specific considerations or troubleshooting steps where relevant.
  • Ensure screenshots and UI instructions are OS-neutral, or provide clarifying notes for Linux users if any steps differ.
  • Include links to Linux-focused documentation or quickstarts where appropriate.
GitHub Create Pull Request
Backup Back up SQL Server by using Azure Backup Server ...ocs/blob/main/articles/backup/backup-azure-sql-mabs.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, specifically referencing Microsoft Azure Backup Server (MABS) and Data Protection Manager (DPM), which are Windows-only tools. All examples, screenshots, and instructions assume a Windows GUI and Windows authentication patterns (e.g., NTAuthority\System). There is no mention of Linux support, Linux SQL Server instances, or command-line alternatives for non-Windows platforms.
Recommendations
  • Clarify in the prerequisites whether MABS/DPM supports Linux-based SQL Server instances and, if not, provide links to equivalent Linux backup solutions (such as Azure Backup for Linux or native SQL Server backup tools).
  • Add examples or guidance for backing up SQL Server running on Linux, if supported, including command-line steps and authentication differences.
  • If MABS/DPM is Windows-only, explicitly state this limitation at the top of the documentation and direct Linux users to appropriate Azure backup documentation.
  • Include parity tables or comparison sections showing how backup workflows differ between Windows and Linux environments.
  • Provide PowerShell and Bash/CLI examples side-by-side where possible.
GitHub Create Pull Request
Backup Troubleshoot Azure Backup failures caused by agent or extension issues ...up-azure-troubleshoot-vm-backup-fails-snapshot-timeout.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: troubleshooting steps and examples often mention Windows tools (services.msc, Control Panel, Event Viewer) and PowerShell before or instead of Linux equivalents; Windows-specific troubleshooting (e.g., COM+, MSDTC, VSS writer, .NET, Visual C++ Redistributable) is detailed, while Linux troubleshooting is less extensive and lacks parity in example commands and tool references. Windows instructions are frequently presented first, and some steps (such as antivirus exclusions and backup job cancellation) only provide Windows-centric details or PowerShell commands, with Linux alternatives missing or minimal.
Recommendations
  • Provide Linux-first or parallel Linux instructions/examples alongside Windows steps, including equivalent commands and troubleshooting tools (e.g., systemctl, journalctl, Linux file paths for logs, package managers for agent installation).
  • Include Linux-specific troubleshooting for extension failures, backup job cancellation, and agent issues, with concrete commands and references to common Linux distributions.
  • Add Linux antivirus exclusion instructions and clarify how to check for blocked extensions or processes on Linux systems.
  • Balance the coverage of Windows-specific services (COM+, MSDTC, VSS writer, .NET, Visual C++ Redistributable) with Linux equivalents or note their non-applicability.
  • Ensure that PowerShell examples are paired with Azure CLI or Bash alternatives for Linux users, especially for backup job management and VM configuration.
  • Review the order of presentation so that Linux and Windows instructions are given equal prominence, or alternate which platform is presented first.
GitHub Create Pull Request
Backup Back Up an Azure Virtual Machine with Azure Extended Zones Portal ...ain/articles/backup/backup-azure-vms-extended-zones.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. In the 'Install the VM agent' section, Windows instructions are presented first, with explicit download links and detailed steps, while Linux instructions are less detailed and refer users to distribution repositories without specific commands or examples. Windows-specific tools (MSI installer, file paths, and executable verification) are mentioned, but equivalent Linux commands (such as rpm, dpkg, or systemctl status) are not provided. Throughout the document, screenshots and examples are generic to the Azure portal and do not show OS-specific differences, but where OS-specific steps are needed, Windows is prioritized.
Recommendations
  • Provide Linux installation instructions with explicit command-line examples (e.g., 'sudo apt install walinuxagent' or 'sudo yum install WALinuxAgent').
  • Include verification steps for Linux agent installation (e.g., checking service status with 'systemctl status walinuxagent' or verifying the agent version).
  • Present Windows and Linux instructions in parallel or side-by-side, rather than listing Windows first.
  • Mention Linux file paths and agent binaries for parity with Windows details.
  • Ensure that any troubleshooting or update steps are equally detailed for both platforms.
GitHub Create Pull Request
Backup Release notes for Microsoft Azure Backup Server v3 ...b/main/articles/backup/backup-mabs-release-notes-v3.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, with all examples, instructions, and tools referencing Windows-only technologies (e.g., SQL Server Management Studio, Windows Server, SSRS, DPM, and Windows file paths). There are no mentions of Linux equivalents, nor any guidance for users running MABS in non-Windows environments. The documentation assumes the reader is using Windows and does not provide parity for Linux users.
Recommendations
  • Include information on whether MABS supports Linux workloads and, if so, document known issues and workarounds for Linux environments.
  • Provide examples and instructions for managing backups and restores using Linux-compatible tools (e.g., Azure CLI, SQL tools for Linux, or relevant open-source alternatives).
  • Mention Linux file paths and conventions where applicable, alongside Windows paths.
  • If certain features or issues are Windows-specific, clearly state this and provide guidance or alternatives for Linux users.
  • Add troubleshooting steps and examples for Linux-based backup scenarios, if supported.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-specific troubleshooting steps, tools, and registry edits are frequently mentioned first or exclusively (e.g., Services.msc, Event Viewer, regedit, VSS, BitLocker, COM+), with Linux equivalents either missing or less detailed. PowerShell and Windows command prompt examples are provided, while Linux CLI or scripting alternatives are sparse. Some error resolutions and diagnostic steps are only described for Windows, leaving Linux users with less guidance.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples alongside Windows instructions, especially for agent/service management, filesystem issues, and extension errors.
  • Include Linux CLI commands (e.g., systemctl, journalctl, dmesg) where Windows tools like Services.msc or Event Viewer are referenced.
  • Offer Bash or Azure CLI alternatives for PowerShell examples, and ensure parity in automation guidance for both platforms.
  • Mention Linux error logs (e.g., /var/log/messages, /var/log/waagent.log) and diagnostic procedures where Windows event logs are discussed.
  • Clarify when a solution is Windows-only and provide equivalent Linux steps or explicitly state if not applicable.
  • Balance the order of presentation so that Linux and Windows instructions are given equal prominence.
GitHub Create Pull Request
Backup Enable Backup During Azure VM Creation by Using Azure Backup ...blob/main/articles/backup/backup-during-vm-creation.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias in several ways: Windows is mentioned before Linux in VM creation instructions, the Resource Manager template example is exclusively for Windows VMs, and PowerShell is referenced as the automation tool for configuring backup resource groups without mentioning Linux alternatives (such as Azure CLI or Bash). There are no explicit Linux-focused examples or templates for enabling backup during VM creation.
Recommendations
  • Present Windows and Linux instructions in parallel or alternate their order to avoid implicit prioritization.
  • Provide Resource Manager template examples for both Windows and Linux VMs, or a generic template that works for either.
  • Include automation instructions using Azure CLI and Bash scripts alongside PowerShell, highlighting cross-platform options.
  • Add explicit Linux VM backup configuration examples and links to Linux-specific documentation where relevant.
  • Ensure screenshots and walkthroughs are representative of both Windows and Linux VM creation flows.
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-11 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 oriented toward Windows environments, with exclusive use of Windows tools (MABS, Registry Editor, CMD commands, Windows file paths), and no mention of Linux equivalents or support. All examples, prerequisites, and procedures assume Windows servers, Windows authentication, and Windows-specific administrative patterns. There are no Linux instructions, examples, or references, and the documentation does not address cross-platform scenarios.
Recommendations
  • Explicitly state platform requirements and limitations at the beginning, clarifying that MABS and SharePoint farm protection are Windows-only if that is the case.
  • If Linux support is possible, provide equivalent instructions for Linux-based environments, including command-line examples, file paths, and administrative steps.
  • Mention alternative backup solutions for SharePoint farms running on Linux (if supported) or hybrid environments.
  • Where possible, use platform-neutral terminology and highlight any cross-platform capabilities or limitations.
  • Add a section addressing Linux users, even if only to clarify that the procedure is not supported, and suggest alternatives.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias in several ways. Restore scenarios and encryption examples reference Windows-specific technologies (Microsoft Entra ID, Windows disk encryption) and PowerShell as the tool for VM creation after restore. There are no explicit Linux examples, nor are Linux-specific restore or encryption scenarios mentioned. Windows tools and patterns are referenced exclusively or before any mention of Linux equivalents.
Recommendations
  • Add examples and guidance for restoring Linux VMs, including disk encryption scenarios (e.g., Azure Disk Encryption for Linux, dm-crypt).
  • Include Linux command-line tools (such as Azure CLI or Bash scripts) as alternatives to PowerShell for VM creation and restore operations.
  • Reference Linux documentation and restore workflows alongside Windows examples, ensuring parity in detail and visibility.
  • Clarify which restore options and features apply to both Windows and Linux VMs, and note any differences or limitations.
  • Provide links to Linux-specific troubleshooting and FAQ resources.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Windows Server domain controllers. All examples, scripts, and tools referenced (such as PowerShell, ntdsutil.exe, and Active Directory Domain Services) are Windows-specific. There are no Linux equivalents or examples, and the documentation does not address scenarios involving Samba or other non-Windows Active Directory implementations. Windows terminology and tools are used exclusively and are introduced first, with no mention of Linux-based alternatives.
Recommendations
  • Add guidance for backing up and restoring Samba-based Active Directory domain controllers on Linux.
  • Include Linux command-line examples (e.g., using samba-tool or native backup utilities) alongside PowerShell scripts.
  • Clarify that the procedures are specific to Windows Server, and provide links or sections for Linux-based AD environments if supported.
  • Mention cross-platform considerations, such as interoperability with Linux-based domain controllers or hybrid environments.
  • If Azure Backup does not support Linux-based AD, explicitly state this limitation.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric workloads (Azure VMs, SQL Server, SAP HANA in Azure VMs), listing PowerShell as a supported client before CLI, and omitting explicit Linux examples or Linux-specific guidance. The examples and screenshots focus exclusively on Azure Virtual Machines, which are typically Windows-based, and do not mention Linux VM backup scenarios or Linux command-line usage. There is no mention of Linux tools, nor are there examples using Bash or Linux-native utilities.
Recommendations
  • Add explicit examples and guidance for Linux VM backup scenarios, including how to use the archive tier for Linux workloads.
  • Provide CLI (az) and Bash script examples alongside PowerShell, and ensure CLI instructions are given equal prominence.
  • Include screenshots or walkthroughs for Linux VM backup management in the Azure portal.
  • Clarify whether archive tier features and recommendations apply equally to Linux VMs, and note any differences.
  • List supported clients in a neutral order (e.g., Portal, CLI, PowerShell) and avoid prioritizing Windows tools.
  • Mention Linux-specific considerations, such as file system support or backup/restore nuances for Linux VMs.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through its 'Next steps' section, which lists PowerShell before Azure CLI when describing configuration options. There is no mention of Linux-specific tools or workflows, and the examples or guidance do not provide parity for Linux users. The documentation does not reference Bash, shell scripting, or Linux-native tools, and the ordering implies a preference for Windows/PowerShell environments.
Recommendations
  • Ensure that Azure CLI (cross-platform) is mentioned before or alongside PowerShell in all instructions and 'Next steps' sections.
  • Add explicit examples and guidance for Linux users, including Bash/shell scripting where relevant.
  • Include notes or links to Linux-specific documentation or troubleshooting guides.
  • Review all referenced articles to ensure Linux parity in examples and tool recommendations.
  • Avoid implying PowerShell is the default or preferred method; present Azure CLI and PowerShell equally.
GitHub Create Pull Request
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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation for Microsoft Azure Recovery Services (MARS) agent is heavily Windows-centric. All restore options and examples reference Windows-specific features (e.g., Windows Server System State, Windows Server Backup utility), PowerShell automation, and Windows tools like robocopy. There are no mentions of Linux equivalents, nor are Linux restore scenarios or commands provided. The prerequisites and instructions assume a Windows environment throughout.
Recommendations
  • Explicitly state platform support: Clarify whether MARS agent supports Linux, and if not, direct users to equivalent Azure Backup solutions for Linux.
  • Provide Linux restore scenarios: If Linux is supported, add examples and instructions for restoring files on Linux systems, including command-line tools and automation scripts.
  • Include Linux tools: Where robocopy is recommended, suggest Linux alternatives such as rsync or cp, and provide usage examples.
  • Balance PowerShell with Bash: For automation, offer Bash or shell script examples alongside PowerShell.
  • Add cross-platform notes: Where features are Windows-only (e.g., System State backup), clearly indicate this and link to Linux documentation for 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-11 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 bias toward Windows environments by consistently mentioning PowerShell as the primary automation client, listing it before CLI and other cross-platform tools, and providing workflow examples that rely on PowerShell and Azure Automation Runbooks (which are often Windows-centric). There are no explicit Linux/bash examples, nor is there mention of Linux-native automation tools or patterns (e.g., Bash scripting, cron jobs). The examples and guidance implicitly assume a Windows/PowerShell context, which may leave Linux users underserved.
Recommendations
  • Provide explicit Linux/bash examples alongside PowerShell, especially for common automation scenarios.
  • Mention and demonstrate the use of Azure CLI and SDKs in Linux environments, including sample scripts.
  • Highlight Linux-compatible automation workflows, such as using cron jobs or shell scripts with Azure CLI.
  • Clarify that Azure Automation Runbooks can be authored in Python and used cross-platform, not just with PowerShell.
  • Ensure that tool lists and examples do not always lead with Windows/PowerShell, but alternate or group by platform.
  • Include links to Linux-focused documentation or community resources for Azure Backup automation.
GitHub Create Pull Request
Backup Azure Backup glossary ...ocs/blob/main/articles/backup/azure-backup-glossary.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The glossary page exhibits a Windows bias through frequent references to Windows-specific technologies (VSS, DPM, MABS, MARS agent), and by listing Windows tools and documentation (Azure PowerShell, VSS) before or without Linux equivalents. Application consistency is described with VSS as the primary method, with Linux scripts mentioned only as an aside. There are no explicit Linux backup tools or patterns referenced, and examples or documentation links for Linux scenarios are missing.
Recommendations
  • Include Linux-specific backup technologies and terminology (e.g., LVM snapshots, fsfreeze, native Linux backup agents) where relevant.
  • When describing application consistency, provide equal detail for Linux methods (e.g., pre/post scripts, supported filesystems) and link to Linux documentation.
  • Add references to Linux command-line tools (e.g., Azure CLI usage on Linux, shell scripts) alongside or before Windows tools.
  • Ensure examples and documentation links are provided for both Windows and Linux scenarios, especially for agent installation, backup, and restore processes.
  • Clarify which features or terms are cross-platform and which are Windows-only, to help Linux users understand applicability.
GitHub Create Pull Request
← Previous Page 12 of 65 Next →