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 526-550 of 1604 flagged pages
Backup MABS & System Center DPM support matrix ...main/articles/backup/backup-support-matrix-mabs-dpm.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits strong Windows bias: all examples, supported operating systems, and deployment scenarios are exclusively Windows-based. There is no mention of Linux support, Linux agents, or backup of Linux workloads. All management, storage, and domain requirements are centered around Windows Server and related Microsoft technologies, with no parity for Linux environments.
Recommendations
  • Explicitly state whether Linux workloads are supported or not, and if not, provide guidance or alternatives for Linux backup in Azure.
  • If Linux support exists, add examples and scenarios for backing up Linux servers and workloads, including agent installation, supported distributions, and restore procedures.
  • Include Linux-specific requirements, limitations, and best practices alongside Windows information.
  • Mention Linux equivalents for domain/workgroup authentication, storage configuration, and deduplication features if applicable.
  • Provide links to documentation for Linux backup solutions in Azure, such as Azure Backup for Linux VMs, or third-party integrations.
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-10 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 scenarios, tools, and agent support are described first and in greater detail; PowerShell is frequently referenced for restore operations; Windows-specific backup agents (MARS, DPM, MABS) are highlighted, while Linux support is limited and often described as 'not supported' for these tools. Linux examples and parity features are missing or less detailed, and Linux-specific restore scenarios are less prominent.
Recommendations
  • Present Linux and Windows scenarios in parallel tables or sections to ensure equal visibility.
  • Add Linux CLI (az, bash) examples for backup and restore operations, especially where PowerShell is referenced.
  • Expand documentation on Linux backup and restore workflows, including supported distributions, limitations, and troubleshooting.
  • Clarify agent and tool parity: explicitly state alternatives for Linux where Windows-only tools (MARS, DPM, MABS) are mentioned.
  • Include more Linux-specific use cases, such as database backup, file-level restore, and integration with common Linux storage/file systems.
  • Ensure that limitations for Linux are explained with context and, where possible, provide workarounds or roadmap information.
GitHub Create Pull Request
Backup Back up the MABS server ...cs/blob/main/articles/backup/backup-the-mabs-server.md
High Priority View Details →
Scanned: 2026-01-10 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 backing up the Microsoft Azure Backup Server (MABS) is heavily Windows-centric. All examples, tools, and procedures assume a Windows environment, referencing Windows-specific utilities (PowerShell, mountvol.exe, diskshadow.exe, psexec.exe, Net Share), Windows file paths, and features like Previous Versions in Explorer. There are no Linux equivalents or cross-platform guidance, and the documentation does not mention or accommodate Linux-based workflows or tools.
Recommendations
  • Add explicit statements about platform requirements and limitations, clarifying that MABS is Windows-only if that is the case.
  • If any components (such as SQL Server backup/restore) can be performed from Linux, provide Linux command-line examples (e.g., using sqlcmd, smbclient, or native Linux backup tools).
  • Where possible, mention cross-platform alternatives for file sharing, mounting, and backup (e.g., using Samba shares, mounting VHDs on Linux, or using Azure CLI from Linux).
  • Provide guidance for accessing backups from non-Windows systems, such as how to retrieve backup files from Azure or network shares using Linux tools.
  • If Linux is not supported, explicitly state this in the documentation to set expectations for administrators.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows Only 🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is exclusively focused on Windows environments, with all examples, supported operating systems, and tooling (PowerShell, MMC, .NET, VC++ Redistributable, DISM.exe) being Windows-specific. There is no mention of Linux support, Linux equivalents, or cross-platform considerations. The installation, configuration, and operational details are all tailored to Windows, and the support matrix lists only Windows OSes.
Recommendations
  • Explicitly state in the introduction that the MARS agent is Windows-only, and provide links to Azure Backup solutions for Linux (e.g., Azure Backup for Linux VMs, Azure Backup Server alternatives).
  • Add a comparison table or section outlining backup options for Linux machines, including supported agents, features, and limitations.
  • Where Windows tools (PowerShell, MMC, registry edits) are mentioned, clarify that these steps are not applicable to Linux, and provide guidance or references for Linux backup management.
  • Include cross-platform backup architecture diagrams and workflows to help administrators choose the right solution for both Windows and Linux environments.
  • If possible, add references to Azure Backup documentation for Linux, and clarify the scope and limitations of MARS agent usage.
GitHub Create Pull Request
Backup Azure Backup support matrix ...ocs/blob/main/articles/backup/backup-support-matrix.md
High Priority View Details →
Scanned: 2026-01-10 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 page demonstrates a Windows bias in several ways: Windows backup scenarios and tools (MARS agent, DPM, MABS) are described first and in greater detail, with Linux support often noted as 'not supported' or limited to specific VM scenarios. Windows-specific backup agents and features (MARS, DPM, MABS) are referenced throughout, while Linux equivalents are either missing or relegated to secondary mentions. Examples and feature tables frequently prioritize Windows, and Linux support is often described in terms of what is not available.
Recommendations
  • Provide Linux-first or Linux-parity examples and tables, especially for backup scenarios and agent support.
  • Include explicit Linux command-line or tool references where appropriate, rather than only mentioning Windows tools.
  • Clarify and expand on Linux backup options, including third-party or open-source alternatives if Microsoft tools do not support Linux directly.
  • Add more detailed documentation for Linux app-consistent backup, including step-by-step guides and sample scripts.
  • Ensure that feature tables and summaries present Linux and Windows options side-by-side for easy comparison.
  • Avoid phrasing that frames Linux support in terms of limitations only; highlight supported scenarios and best practices for Linux environments.
GitHub Create Pull Request
Backup Configure and manage backup for Azure Blobs using Azure Backup ...b/main/articles/backup/blob-backup-configure-manage.md
High Priority View Details →
Scanned: 2026-01-10 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 backup management for Azure Blobs using the Azure portal, with only passing references to REST API, Azure PowerShell, and Azure CLI. In the 'Related content' section, Azure PowerShell is listed before Azure CLI and REST API, suggesting a Windows-first approach. There are no explicit Linux-specific examples, nor is there mention of Linux-native tools or shell commands. The step-by-step instructions and screenshots are focused on the Azure portal, which is platform-agnostic, but the lack of parity in command-line examples and the ordering of PowerShell before CLI indicate a subtle Windows bias.
Recommendations
  • Provide explicit Linux shell (bash) examples for common backup and restore operations, especially where PowerShell is referenced.
  • In 'Related content', list Azure CLI before PowerShell, or present both equally, to avoid Windows-first ordering.
  • Where command-line instructions are given, ensure both PowerShell and CLI examples are present and equally detailed.
  • Reference Linux-native tools or workflows where applicable, and clarify that all operations can be performed from Linux environments using Azure CLI.
  • Add a section or callout for Linux users, highlighting any platform-specific considerations or tips.
GitHub Create Pull Request
Backup Restore Azure Blobs ...s/azure-docs/blob/main/articles/backup/blob-restore.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references Azure PowerShell as the first programmatic method for restoring blobs, with a dedicated link to a PowerShell guide. While Azure CLI and REST API are also mentioned, there are no explicit Linux-oriented examples, nor is there mention of Bash or Linux shell usage. The ordering and emphasis suggest a Windows-first approach, and the lack of Linux-specific instructions or screenshots further reinforces this bias.
Recommendations
  • Provide explicit Linux/Bash examples for restoring blobs using Azure CLI, including sample commands and expected output.
  • Re-order the list of programmatic options to present Azure CLI before PowerShell, or present them together with equal prominence.
  • Include screenshots or terminal output from Linux environments to demonstrate parity.
  • Add notes or sections clarifying cross-platform compatibility, especially for CLI and REST API usage.
  • Ensure that any referenced scripts or automation examples are available for both Windows (PowerShell) and Linux (Bash/sh).
GitHub Create Pull Request
Backup Overview of Azure Disk Backup ...docs/blob/main/articles/backup/disk-backup-overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates subtle Windows bias by mentioning Windows Server Failover Cluster before Linux clusters, referencing Windows-specific technologies (such as Volume Shadow Copy Service, VSS), and providing examples of unsupported scenarios focused on Windows (e.g., Windows 2008 32-bit Server). There are no explicit Linux command-line or tooling examples, and Linux-specific backup challenges are discussed only in passing, without concrete guidance or parity in example depth.
Recommendations
  • Alternate the order of Windows and Linux references to avoid 'Windows first' bias (e.g., mention Linux clusters before or alongside Windows clusters).
  • Provide Linux-specific examples and scenarios, such as common Linux backup challenges, supported distributions, and how to handle application-consistent backups on Linux.
  • Include references to Linux-native tools or patterns (e.g., LVM snapshots, fsfreeze, or application hooks) where relevant.
  • Expand unsupported scenario examples to include Linux cases (e.g., unsupported Linux OS versions or filesystems).
  • Ensure parity in troubleshooting and best practices for both Windows and Linux environments.
GitHub Create Pull Request
Backup Encrypt backup data in a Backup vault by using customer-managed keys ...backup/encryption-at-rest-with-cmk-for-backup-vault.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions and code examples for Azure portal, PowerShell, and Azure CLI. PowerShell is featured prominently and is presented before CLI in all code sections, which may suggest a Windows-first approach. There are no explicit Linux shell (bash) examples or references to Linux-specific tools, nor is there mention of Linux environments or considerations. The CLI examples are generic and do not clarify usage in Linux shells, and there are no screenshots or instructions tailored for Linux users.
Recommendations
  • Add explicit bash shell examples for each CLI command, including syntax and environment notes for Linux users.
  • Include screenshots or terminal output from Linux environments where relevant.
  • Clarify that Azure CLI commands are cross-platform and provide any necessary Linux-specific instructions (e.g., authentication, environment setup).
  • Consider presenting CLI examples before PowerShell to avoid implicit Windows prioritization.
  • Mention Linux support and parity in introductory sections to reassure non-Windows users.
  • If PowerShell is required on Linux, provide installation and usage guidance for PowerShell Core on Linux.
GitHub Create Pull Request
Backup Guidance and best practices ...s/blob/main/articles/backup/guidance-best-practices.md
High Priority View Details →
Scanned: 2026-01-10 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. Examples and automation references frequently mention PowerShell before CLI, and Windows-centric tools like MARS agent, DPM/MABS are highlighted without equivalent Linux alternatives. There is a lack of explicit Linux backup scenarios or examples, and the guidance assumes Windows-based environments (e.g., SQL Server on Azure VM, SAP HANA on Azure VM) without mentioning Linux VMs or workloads. Automation and troubleshooting sections focus on PowerShell, and there are no Linux shell (bash) or cross-platform CLI examples. The documentation does not address Linux-specific backup needs or tools, nor does it provide parity in examples or guidance for Linux administrators.
Recommendations
  • Add explicit examples for Linux VM backup scenarios, including automation via Azure CLI and bash scripts.
  • Mention Linux workloads (e.g., PostgreSQL, MySQL, file servers) and provide guidance for their backup and restore processes.
  • When listing automation options, present Azure CLI and REST API before or alongside PowerShell, and provide sample commands for both.
  • Include references to Linux-native backup agents or third-party tools where applicable, or clarify parity of features for Linux and Windows environments.
  • Ensure troubleshooting and monitoring guidance includes Linux-specific considerations (e.g., log file locations, permissions).
  • Provide links to documentation or tutorials specifically targeting Linux backup strategies in Azure.
GitHub Create Pull Request
Backup Encrypt backup data by using customer-managed keys ...ob/main/articles/backup/encryption-at-rest-with-cmk.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured prominently and often listed before Azure CLI, which is more cross-platform. There are multiple warnings and recommendations specifically about PowerShell usage, and the overall structure and examples tend to prioritize Windows-centric tools and workflows. There is no explicit mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments. While Azure CLI is included, the documentation assumes familiarity with PowerShell and Windows conventions.
Recommendations
  • Provide explicit Bash shell examples alongside PowerShell and Azure CLI, especially for steps that involve scripting or automation.
  • Ensure that Azure CLI examples are presented before or alongside PowerShell examples to emphasize cross-platform support.
  • Add notes clarifying that all CLI commands work equally on Linux, macOS, and Windows, and highlight any platform-specific caveats.
  • Avoid warnings or recommendations that are PowerShell-specific unless there is a true platform limitation; otherwise, provide equivalent guidance for CLI/Bash users.
  • Include screenshots or terminal outputs from Linux environments where relevant, not just Windows/PowerShell.
  • Mention Linux-native tools or patterns if applicable, and clarify when steps are platform-agnostic.
GitHub Create Pull Request
Backup Install the Microsoft Azure Recovery Services (MARS) agent ...e-docs/blob/main/articles/backup/install-mars-agent.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is exclusively focused on installing and using the MARS agent for Windows machines. All instructions, examples, and prerequisites are Windows-centric, including references to Windows-specific tools (PowerShell, .NET Framework), installer files (.exe), and UI elements. There is no mention of Linux support, alternatives, or parity, and no Linux examples or equivalent tools are provided.
Recommendations
  • Clearly state in the introduction whether MARS agent is Windows-only, and if so, provide guidance or links for Linux backup solutions (e.g., Azure Backup for Linux VMs).
  • Add a comparison table or section outlining backup options for Linux machines, including supported agents and workflows.
  • If any cross-platform alternatives exist, provide installation and usage instructions for Linux alongside Windows.
  • Avoid using 'machines' generically when only Windows is supported; specify 'Windows machines' to prevent confusion.
  • Include links to documentation for Linux backup solutions to help users find relevant information.
GitHub Create Pull Request
Backup Manage Backup vaults ...-docs/blob/main/articles/backup/manage-backup-vault.md
High Priority View Details →
Scanned: 2026-01-10 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 moderate Windows bias. When mentioning command-line options for moving Backup vaults, PowerShell is listed first and referenced explicitly, while the Azure CLI is mentioned second and only in passing. No Linux-specific examples, screenshots, or shell commands are provided, and there is no mention of Linux tools or workflows. The page relies heavily on Azure portal GUI instructions and PowerShell, which are more familiar to Windows users, and does not provide parity for Linux users who may prefer Bash or CLI workflows.
Recommendations
  • Provide explicit Azure CLI examples alongside PowerShell for all command-line operations, including moving Backup vaults.
  • Include sample Bash scripts or Linux shell commands where relevant, especially for automation tasks.
  • Ensure that references to command-line tools do not prioritize Windows tools (e.g., PowerShell) over cross-platform options (e.g., Azure CLI).
  • Add screenshots or instructions showing CLI usage on Linux/macOS terminals.
  • Mention platform compatibility for all tools and clarify when instructions apply equally to Linux, macOS, and Windows.
GitHub Create Pull Request
Backup Manage telemetry settings in Microsoft Azure Backup Server (MABS) ...ure-docs/blob/main/articles/backup/manage-telemetry.md
High Priority View Details →
Scanned: 2026-01-10 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 biased towards Windows environments. All instructions reference the Microsoft Azure Backup Server console, which is a Windows application. There are no examples or guidance for managing telemetry settings via Linux tools, command-line interfaces, or cross-platform methods. The documentation implicitly assumes the user is operating in a Windows environment and does not mention Linux compatibility or alternatives.
Recommendations
  • Clarify whether MABS is supported on Linux, and if so, provide equivalent instructions for Linux environments.
  • If telemetry settings can be managed via command-line or scripts, include examples for PowerShell (Windows) and Bash (Linux) side-by-side.
  • Mention any Linux-compatible tools or interfaces for managing telemetry, or explicitly state if such options are unavailable.
  • Add a section addressing telemetry management for users who do not use the Windows console, including remote management scenarios.
  • Ensure parity in screenshots and step-by-step instructions for both Windows and Linux platforms, if applicable.
GitHub Create Pull Request
Backup What Azure Backup Server V3 RTM can back up .../backup/microsoft-azure-backup-server-protection-v3.md
High Priority View Details →
Scanned: 2026-01-10 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 a strong Windows bias. All workload examples, protection scenarios, and supported features are centered on Windows operating systems, Windows-based applications (SQL Server, Exchange, SharePoint), and Windows file systems (NTFS, ReFS). Linux is only mentioned briefly as a guest VM, with limited support (entire VM backup only, no item-level recovery), and no Linux-native workloads or file systems are referenced. Windows tools and technologies (Volume Shadow Copy Service, NTFS, Windows Management Framework, Hyper-V, etc.) are discussed exclusively, with no Linux equivalents or parity.
Recommendations
  • Add explicit support matrix entries for Linux workloads, including common distributions and versions, and clarify which features (e.g., item-level recovery, file system support) are available for Linux VMs.
  • Provide examples and documentation for Linux file systems (e.g., ext4, xfs, btrfs) and clarify backup/recovery limitations or capabilities for these.
  • Include Linux-native applications (e.g., MySQL, PostgreSQL, Apache, Nginx) in the protection matrix if supported, or explicitly state if not supported.
  • Mention Linux backup tools or patterns (e.g., LVM snapshots, rsync, tar) where relevant, or clarify integration points.
  • Ensure that Linux scenarios are described with equal detail and prominence as Windows scenarios, including item-level recovery, cluster support, and backup/restore workflows.
  • If Linux support is intentionally limited, clearly state the limitations and provide guidance or alternatives for Linux users.
GitHub Create Pull Request
Backup Backup Classic Alerts using Azure Backup ...b/main/articles/backup/move-to-azure-monitor-alerts.md
High Priority View Details →
Scanned: 2026-01-10 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 a Windows bias by referencing PowerShell and the Azure portal as primary management interfaces, with no mention of Linux-specific tools or CLI workflows. The only client interfaces mentioned for immediate feedback are 'portal/PowerShell/the CLI clients', listing PowerShell before CLI and omitting any Linux-specific examples or guidance. There are no Linux command-line examples, nor is there mention of Linux-native backup agents or integration patterns.
Recommendations
  • Add explicit examples and instructions for managing alerts using Azure CLI on Linux, including relevant commands.
  • Reference Linux-native backup agents or clarify cross-platform compatibility for alerting and notification features.
  • Ensure that client interfaces are listed in a neutral order (e.g., 'portal, CLI, PowerShell') and provide parity in documentation for both Windows and Linux users.
  • Include screenshots or walkthroughs from Linux environments where applicable.
  • Clarify whether features such as notifications and alert deactivation are accessible and functionally equivalent on Linux systems.
GitHub Create Pull Request
Backup Configure Multi-user authorization using Resource Guard .../blob/main/articles/backup/multi-user-authorization.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides command-line examples for both Azure PowerShell and Azure CLI, but PowerShell examples are consistently presented before CLI examples, reflecting a 'Windows-first' ordering. There are no Linux-specific instructions, nor are there any references to Linux shell environments, scripting, or platform-specific considerations. The documentation assumes that users are familiar with PowerShell, which is traditionally associated with Windows, and does not address Linux shell usage or provide parity for Linux users beyond the CLI commands.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid implicit Windows prioritization.
  • Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide guidance for running them in Linux environments (e.g., bash, zsh).
  • Include notes or sections for Linux users, such as how to install and use Azure CLI on Linux, and how to authenticate or manage credentials in Linux shell environments.
  • Where scripting is discussed, provide bash script equivalents alongside PowerShell scripts.
  • Clarify that PowerShell Core is available on Linux and macOS, and provide installation instructions or links for non-Windows platforms if PowerShell usage is required.
GitHub Create Pull Request
Backup MABS (Azure Backup Server) V3 UR1 protection matrix ...kup/microsoft-azure-backup-server-protection-v3-ur1.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation for MABS (Azure Backup Server) V3 UR1 protection matrix demonstrates a strong Windows bias. Windows workloads, tools, and patterns are described in detail and appear first in all relevant sections. Linux support is limited to guest VMs, with minimal detail and no examples or parity for advanced features. Windows-specific technologies (NTFS, VSS, ReFS, deduplication, system state, bare metal recovery) are referenced throughout, while Linux equivalents are not mentioned or supported. Recovery options for Linux are limited compared to Windows, and there are no Linux-specific usage examples or guidance.
Recommendations
  • Provide Linux-specific backup and recovery examples, including command-line instructions and supported scenarios.
  • Expand the Linux section to detail supported distributions, file systems, and any limitations or workarounds.
  • List Linux support alongside Windows in all relevant tables, rather than relegating Linux to a separate, minimal section.
  • Clarify if and how advanced features (e.g., item-level recovery, application-aware backup, deduplication) are or are not supported for Linux, and provide guidance or alternatives.
  • Where Windows-specific tools or patterns (e.g., VSS, NTFS, ReFS) are mentioned, add notes about Linux equivalents or explicitly state the lack of support.
  • Include parity in troubleshooting, cluster support, and unsupported data types sections for Linux workloads.
GitHub Create Pull Request
Backup Monitor your backups with Backup Explorer ...es/backup/monitor-azure-backup-with-backup-explorer.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Backup Explorer demonstrates a Windows bias by focusing exclusively on Azure virtual machines (VMs) data, which typically refers to Windows VMs. The examples and references throughout the page mention Azure VMs and their backup/restore operations, but do not clarify or provide examples for Linux VMs. Additionally, export functionality is described in terms of Excel, a Windows-centric tool, with no mention of alternatives for Linux users. There are no PowerShell examples, but the overall framing and terminology prioritize Windows environments and tools.
Recommendations
  • Explicitly mention support for Linux VMs if available, and provide examples or screenshots for Linux VM backup monitoring.
  • Include references to alternative export formats (e.g., CSV, JSON) and tools (e.g., LibreOffice, command-line utilities) for Linux users.
  • Clarify whether Backup Explorer supports both Windows and Linux VMs, and if not, provide guidance or links for Linux VM backup monitoring.
  • Avoid using Windows-centric terminology (e.g., Excel) exclusively; mention cross-platform options.
  • Add documentation sections or examples that demonstrate usage and troubleshooting for Linux VM backup scenarios.
GitHub Create Pull Request
Backup Monitoring and reporting solutions for Azure Backup ...main/articles/backup/monitoring-and-alerts-overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is consistently mentioned as a primary non-portal client for monitoring and reporting, often listed before Azure CLI and REST API. Windows-centric backup solutions and tools (such as Azure Backup Agent, DPM, Azure Backup Server) are referenced in alert tables and scenarios, with little to no mention of Linux-specific backup agents or workflows. There are no explicit Linux command examples, and the documentation does not highlight Linux parity or provide guidance for Linux administrators.
Recommendations
  • Include Linux-specific examples and workflows, such as using Azure CLI on Linux, Bash scripts, or automation via Linux-native tools.
  • Ensure that CLI examples are given equal prominence to PowerShell, and consider listing CLI before PowerShell in example lists.
  • Explicitly mention Linux compatibility and supported Linux workloads in alert tables and scenario descriptions.
  • Add documentation or links for monitoring and reporting Azure Backup from Linux environments, including troubleshooting steps and best practices.
  • Clarify whether features and tools (such as Azure Backup Agent, DPM, Azure Backup Server) are Windows-only, and provide Linux alternatives or note their absence.
GitHub Create Pull Request
Backup Offline Backup with Azure Data Box for DPM and MABS ...icles/backup/offline-backup-azure-data-box-dpm-mabs.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows Only Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows environments, specifically Windows Server and Windows-based tools. All instructions, examples, and troubleshooting steps are tailored for Windows Server (2016/2019) and rely on Windows-specific utilities (e.g., PSExec, regedit, Windows registry paths, Windows certificate manager). PowerShell modules are referenced exclusively, and there is no mention of Linux support, equivalent Linux tools, or cross-platform alternatives. The supported platforms section lists only Windows Server versions, and all procedural steps assume a Windows context.
Recommendations
  • Explicitly state platform limitations at the beginning of the article, clarifying that Linux is not supported if that is the case.
  • If Linux support is possible, provide equivalent instructions for Linux environments, including mounting NFS shares, certificate management, and Azure CLI usage.
  • Reference Linux-compatible Azure backup solutions or alternatives for non-Windows users.
  • Where PowerShell is used, offer Azure CLI or REST API alternatives for cross-platform compatibility.
  • Avoid exclusive reliance on Windows tools (e.g., PSExec, regedit) and mention open-source or platform-neutral alternatives if available.
  • Include a comparison table or section outlining differences and limitations between Windows and Linux support for Azure Data Box offline backup.
GitHub Create Pull Request
Backup Offline backup for Data Protection Manager (DPM) and Microsoft Azure Backup Server (MABS) - previous versions ...cles/backup/offline-backup-server-previous-versions.md
High Priority View Details →
Scanned: 2026-01-10 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, with all examples, tools, and workflows described exclusively for Windows Server, Windows clients, and Windows-specific utilities (such as .exe files and registry edits). There is no mention of Linux support, nor are Linux equivalents or examples provided. The use of Windows command prompts, registry editing, and PowerShell commands further reinforces the Windows bias.
Recommendations
  • Explicitly state whether Linux platforms are supported or not for DPM/MABS offline backup workflows.
  • If Linux support exists, provide parallel instructions, examples, and screenshots for Linux environments (e.g., using Bash, Linux file paths, and Linux-compatible utilities).
  • Mention Linux-compatible tools or alternatives to Windows-only utilities like AzureOfflineBackupDiskPrep.exe and AzureOfflineBackupCertGen.exe, or clarify their platform limitations.
  • Include guidance for performing offline backup from Linux servers, if possible, or link to relevant documentation.
  • Avoid assuming the use of Windows registry or command prompt; provide cross-platform instructions where feasible.
GitHub Create Pull Request
Backup Offline backup by using Azure Data Box .../main/articles/backup/offline-backup-azure-data-box.md
High Priority View Details →
Scanned: 2026-01-10 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 is heavily biased towards Windows environments. All supported platforms listed are Windows SKUs, with no mention of Linux or macOS support. All examples and instructions use Windows-specific tools (PowerShell, MARS Agent, Control Panel, PsExec, registry editor), and there are no Linux equivalents or alternatives provided. The prerequisite and troubleshooting steps rely exclusively on Windows and PowerShell commands, further excluding Linux users.
Recommendations
  • Clearly state platform limitations at the beginning, including whether Linux is unsupported or provide guidance for Linux users.
  • If Linux support is possible, add equivalent instructions for Linux environments, including how to interact with Azure Data Box and perform offline backup seeding.
  • Provide Linux command-line examples (e.g., Bash, Azure CLI) alongside PowerShell instructions where feasible.
  • Mention Linux tools for mounting NFS shares and handling certificates, such as mount, openssl, and relevant Azure CLI commands.
  • If the MARS Agent is Windows-only, suggest alternative backup solutions for Linux and link to relevant documentation.
  • Ensure troubleshooting steps include Linux scenarios or explicitly state their applicability.
GitHub Create Pull Request
Backup Create and use private endpoints for Azure Backup ...re-docs/blob/main/articles/backup/private-endpoints.md
High Priority View Details →
Scanned: 2026-01-10 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 page exhibits a notable Windows bias. Most command-line examples and scripts are provided exclusively in PowerShell, with references to Windows-centric tools (e.g., MARS agent, DPM server, domain controller, DNS Manager). There are no Bash, Azure CLI, or Linux shell equivalents for key operations such as role assignment, private endpoint creation, or DNS configuration. Instructions for uploading and running scripts are tailored to the PowerShell environment, and Windows terminology (e.g., host files, domain controller) is used throughout. Linux alternatives are not mentioned, and the documentation assumes a Windows administrative context.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for all PowerShell commands and scripts.
  • Include instructions for Linux administrators, such as managing DNS with BIND or dnsmasq, and configuring host files on Linux systems.
  • Add guidance for running scripts in Linux-based Azure Cloud Shell, not just PowerShell.
  • Mention Linux-compatible backup agents or clarify cross-platform support for MARS/DPM.
  • Use neutral terminology (e.g., 'command line' instead of 'PowerShell window') and avoid assuming a Windows-only environment.
  • Where screenshots or instructions reference Windows tools (e.g., DNS Manager), provide Linux alternatives or note platform differences.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Files using Azure Bicep ...es/backup/quick-backup-azure-files-vault-tier-bicep.md
High Priority View Details →
Scanned: 2026-01-10 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 towards Windows and PowerShell environments. The deployment instructions exclusively use Azure PowerShell, with no Azure CLI or Bash examples provided. The prerequisites mention Azure PowerShell before any Linux-friendly alternatives. The 'Next steps' section lists PowerShell-based management and restore options before CLI or REST API, reinforcing a Windows-centric workflow. There is no guidance for Linux users or those preferring Bash/CLI.
Recommendations
  • Add Azure CLI and Bash examples for template deployment, alongside PowerShell.
  • In prerequisites, mention both Azure PowerShell and Azure CLI, with installation links for each.
  • In the deployment section, provide step-by-step instructions for both PowerShell and CLI/Bash users.
  • In 'Next steps', list CLI and REST API options alongside PowerShell, or in parallel, to avoid ordering bias.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and show how to select the preferred shell.
GitHub Create Pull Request
← Previous Page 22 of 65 Next →