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 826-850 of 1604 flagged pages
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-sharepoint-azure-stack.md .../articles/backup/backup-mabs-sharepoint-azure-stack.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows security groups). All examples and instructions assume a Windows OS, with no mention of Linux equivalents, cross-platform alternatives, or compatibility. The documentation uses Windows terminology and patterns throughout, and does not provide guidance for Linux-based SharePoint deployments or backup/restore scenarios.
Recommendations
  • Clarify OS requirements and explicitly state if MABS and SharePoint backup are Windows-only, or provide guidance for Linux environments if supported.
  • If Linux is supported, add equivalent instructions and examples for Linux, including command-line tools, file paths, and permissions.
  • Mention alternative backup solutions or tools for Linux-based SharePoint or SQL Server deployments, if MABS is not available.
  • Include a section on cross-platform considerations, such as differences in agent installation, service management, and monitoring.
  • Where possible, use OS-neutral terminology or provide parallel instructions for both Windows and Linux.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-files-applications-azure-stack.md ...s/backup/backup-mabs-files-applications-azure-stack.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively describes backup and recovery procedures using Microsoft Azure Backup Server, which is a Windows-based tool. All instructions and screenshots reference the Azure Backup Server console, a Windows GUI application, with no mention of Linux-based alternatives, CLI commands, or cross-platform tools. There are no examples or guidance for Linux VMs or Linux-native backup workflows. The documentation implicitly assumes a Windows environment and does not address Linux users or provide parity for Linux administration.
Recommendations
  • Include instructions and examples for backing up files and applications on Linux-based Azure Stack VMs, using supported tools or agents.
  • Provide CLI-based examples (e.g., using Azure CLI, shell scripts, or Linux-native backup utilities) alongside GUI instructions.
  • Mention any Linux support or limitations for Azure Backup Server, and link to relevant documentation for Linux VM backup.
  • Add screenshots or walkthroughs for Linux environments where applicable.
  • Clarify whether the described process is Windows-only, and suggest alternative approaches for Linux workloads if Azure Backup Server is not supported.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-managed-disks.md ...docs/blob/main/articles/backup/backup-managed-disks.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation primarily focuses on using the Azure portal for backup operations, which is cross-platform. However, when mentioning automation or scripting, PowerShell is listed before Azure CLI, and there is no explicit mention or example of Linux-specific tools or workflows. The references to scripts use 'PowerShell/CLI', with PowerShell mentioned first, which may suggest a Windows-first bias. There are no direct Linux shell or bash examples, nor any discussion of Linux-specific considerations or parity in the backup workflow.
Recommendations
  • When referencing automation, list Azure CLI before or alongside PowerShell to avoid Windows-first bias.
  • Include explicit bash or shell script examples for Linux users, especially in sections discussing scripting or automation.
  • Add notes or sections highlighting Linux parity, such as confirming that all portal and CLI operations work identically on Linux systems.
  • Where role assignment templates or scripts are mentioned, clarify that they can be executed using Azure CLI on Linux/macOS, and provide example commands.
  • Consider adding a 'Linux considerations' section to address any platform-specific nuances or reassure users of full support.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-rbac-rs-vault.md ...docs/blob/main/articles/backup/backup-rbac-rs-vault.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It specifically references Windows-centric backup tools (Azure Backup agent client UI, System Center Data Protection Manager UI, Azure Backup Server UI) when discussing out-of-scope actions, and lists 'Register on-premises Windows Server/client/SCDPM or Azure Backup Server' as a management operation, without mentioning Linux equivalents. There are no examples or explicit instructions for Linux-based backup agents or tools, nor are Linux-specific scenarios (such as registering Linux servers or using Linux backup agents) discussed. The order and language suggest Windows environments are the primary or default context for on-premises backup management.
Recommendations
  • Add explicit references and examples for Linux-based backup scenarios, such as registering Linux servers with Recovery Services vault, and managing their backups.
  • Mention Linux backup agents/tools (e.g., MARS agent for Linux, or third-party Linux backup solutions) in parity with Windows tools.
  • Clarify whether the listed operations and role requirements apply equally to Linux servers, and provide guidance for Linux-specific backup management tasks.
  • Include links to documentation for Linux backup agent installation, configuration, and management.
  • Ensure that examples and instructions for PowerShell are accompanied by equivalent Azure CLI or Bash examples, especially for cross-platform parity.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-on-availability-groups.md ...les/backup/backup-sql-server-on-availability-groups.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page focuses exclusively on SQL Server backups in Azure environments, implicitly assuming Windows-based deployments. There are no examples or guidance for Linux-based SQL Server instances, nor is there mention of Linux-specific tools or patterns. The terminology and backup extension references are aligned with Windows VM management, and the absence of Linux parity is notable throughout the document.
Recommendations
  • Explicitly mention support (or lack thereof) for SQL Server on Linux, and clarify any differences in backup configuration or limitations.
  • Provide examples and instructions for backing up SQL Server AGs running on Linux VMs, including any required Linux-specific setup steps or tools.
  • Reference Linux-native management tools (e.g., Bash, systemd, cron) alongside Windows tools like PowerShell, where applicable.
  • Ensure that any diagrams or sample deployments include Linux VM scenarios, not just Windows.
  • Add troubleshooting and error codes relevant to Linux environments, if they differ from Windows.
  • Include links to documentation for SQL Server on Linux backup and restore processes, if available.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-matrix-mabs-dpm.md ...main/articles/backup/backup-support-matrix-mabs-dpm.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation for MABS & System Center DPM is heavily focused on Windows environments. All examples, supported operating systems, deployment scenarios, and backup workflows are exclusively described for Windows Server and related Microsoft technologies. There is no mention of Linux support, Linux-based workloads, or cross-platform backup scenarios. The documentation assumes the use of Windows domains, Windows-based VMs, and Windows-specific tools, with no parity for Linux environments.
Recommendations
  • Explicitly state whether Linux servers and workloads are supported or not, and provide guidance for Linux users.
  • If Linux backup is supported, add sections detailing supported Linux distributions, deployment scenarios, and configuration steps.
  • Include Linux-specific examples for agent installation, backup workflows, and recovery procedures.
  • Mention Linux equivalents for domain/workgroup authentication, storage configuration, and deduplication support.
  • If Linux is not supported, clarify this early in the documentation to set expectations for cross-platform users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-release-notes-archived.md .../main/articles/backup/backup-release-notes-archived.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page for Azure Backup release notes demonstrates a moderate Windows bias. Several features and tools are described with explicit references to Windows-centric technologies, such as the MARS agent, Microsoft Azure Backup Server (MABS), and Windows Server compatibility. PowerShell is frequently mentioned as a primary management interface, sometimes before or without equal mention of Linux alternatives. While there is some coverage of Linux workloads (e.g., SAP HANA on RHEL, PostgreSQL), Windows tools and patterns are more prominent and often described first or exclusively.
Recommendations
  • Ensure that Linux equivalents (e.g., Azure CLI, Bash scripts) are mentioned alongside PowerShell in all feature descriptions and examples.
  • Highlight cross-platform compatibility for agents and management tools, specifying Linux support where available.
  • Provide explicit examples and guidance for Linux environments, especially for backup agents and server software (e.g., clarify if MARS/MABS have Linux alternatives or limitations).
  • Balance the order of presentation so that Linux and Windows tools/features are introduced together, or alternate which platform is described first.
  • Add more details about backup and restore procedures for Linux-based workloads, including command-line and automation options.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-matrix-mars-agent.md ...in/articles/backup/backup-support-matrix-mars-agent.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 for the MARS agent is exclusively focused on Windows environments. All examples, supported operating systems, and instructions refer only to Windows or Windows Server. Windows-specific tools and patterns (such as PowerShell, MMC, registry edits, NTFS, VSS, DISM.exe) are mentioned throughout, with no reference to Linux or other platforms. There are no Linux equivalents, examples, or even a statement clarifying lack of support for Linux. The documentation assumes a Windows-first audience and omits any cross-platform considerations.
Recommendations
  • Explicitly state that the MARS agent is not supported on Linux or non-Windows platforms, if that is the case.
  • If Linux support is planned or available via other Azure Backup agents, provide links or references to those solutions.
  • Add a comparison section or FAQ addressing Linux backup scenarios and alternatives for parity.
  • Where possible, clarify Windows-specific instructions (e.g., registry edits, PowerShell usage) as not applicable to Linux.
  • Consider including a table or note summarizing which Azure Backup agents support Linux and how Linux users should proceed.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-azure-troubleshoot.md ...rticles/backup/backup-sql-server-azure-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All troubleshooting steps, file paths, and extension names are Windows-specific (e.g., C:\ paths, NT AUTHORITY\SYSTEM, Control Panel references). The AzureBackupWindowsWorkload extension is mentioned exclusively, with no reference to Linux equivalents. Antivirus exclusions, service accounts, and error resolutions are all described using Windows terminology and tools. PowerShell is referenced for automation, and there are no examples or instructions for Linux-based SQL Server VMs. No Linux file paths, services, or troubleshooting patterns are provided.
Recommendations
  • Add equivalent troubleshooting steps and examples for SQL Server running on Linux Azure VMs.
  • Include Linux file paths (e.g., /opt/azureworkloadbackup) and service account details.
  • Reference Linux tools (e.g., systemctl, journalctl) for service and extension management.
  • Provide instructions for installing and managing the AzureBackupWorkload extension on Linux VMs.
  • Offer guidance for antivirus exclusions and permissions using Linux commands (e.g., chown, chmod).
  • Include automation examples using Bash or Azure CLI for Linux environments.
  • Clearly indicate which steps are Windows-specific and provide Linux alternatives where applicable.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/microsoft-azure-backup-server-protection-v3-ur1.md ...kup/microsoft-azure-backup-server-protection-v3-ur1.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page for MABS V3 UR1 protection matrix demonstrates a clear Windows bias. Windows workloads and tools are listed first and in detail, with extensive coverage of Windows Server, NTFS, VSS, and related features. Linux support is relegated to a single table, with minimal detail and only virtual machine-level protection (no file-level recovery or application backup). Windows-specific tools and patterns (NTFS, VSS, ReFS, FAT, FAT32, Windows Management Framework) are mentioned exclusively, and there are no Linux-specific backup scenarios, examples, or recovery options. Powershell and Windows administrative patterns are implied throughout, while Linux equivalents are absent.
Recommendations
  • Add detailed Linux backup and recovery scenarios, including file-level and application-level protection if supported.
  • Provide Linux-specific examples and usage patterns, such as backup/restore commands for Linux workloads.
  • Mention Linux file systems (e.g., ext4, xfs) and their support status, not just NTFS/ReFS.
  • Clarify limitations and parity between Windows and Linux backup features (e.g., item-level recovery, snapshot consistency).
  • Include Linux administrative tools or commands where relevant, and avoid assuming Windows-only environments.
  • Present Linux and Windows workloads in parallel, rather than listing Windows first and Linux last.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/encryption-at-rest-with-cmk-for-backup-vault.md ...backup/encryption-at-rest-with-cmk-for-backup-vault.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides step-by-step instructions for enabling encryption with customer-managed keys in Azure Backup vaults. While it offers examples for Azure Portal, PowerShell, and Azure CLI, there is a noticeable bias towards Windows-centric tooling and patterns. PowerShell examples are detailed and appear before CLI examples, and there are no explicit Linux shell (bash) or cross-platform scripting examples. The documentation assumes familiarity with PowerShell and does not mention Linux-specific considerations or alternative command-line environments.
Recommendations
  • Add explicit bash shell examples for all CLI commands, including environment variable usage and scripting patterns common on Linux.
  • Clarify that Azure CLI commands can be run natively on Linux, macOS, and Windows, and provide any OS-specific notes if applicable.
  • Include troubleshooting steps or notes for Linux users, such as file permissions, environment setup, or differences in managed identity handling.
  • Ensure that PowerShell and CLI examples are presented with equal prominence, or alternate their order to avoid Windows-first bias.
  • Mention cross-platform compatibility of Azure CLI and provide links to installation guides for Linux and macOS.
  • If screenshots are OS-specific (e.g., Windows UI), consider adding Linux/macOS equivalents or clarifying UI differences.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/disk-backup-overview.md ...docs/blob/main/articles/backup/disk-backup-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions Windows-specific technologies (e.g., Windows Server Failover Cluster, Volume Shadow Copy Service (VSS), Windows 2008 32-bit Server) before or more prominently than Linux equivalents. There are no concrete Linux-specific examples, tools, or patterns provided, and no Linux command-line or scripting examples are present. The discussion of application-consistent backup references VSS (Windows-centric) but does not mention Linux alternatives. Linux is referenced only in passing, and practical guidance for Linux users is missing.
Recommendations
  • Provide explicit Linux-centric examples, such as how to configure backups for Linux VMs, including agentless backup scenarios and application-consistent backup alternatives for Linux (e.g., fsfreeze, pre/post scripts).
  • Mention Linux clustering technologies (e.g., Pacemaker, Corosync) alongside Windows Server Failover Cluster, and provide parity in explanation.
  • Include references to Linux-supported backup tools and patterns, and clarify differences in backup/restore processes for Linux VMs.
  • Add practical Linux command-line examples (e.g., using Azure CLI or REST API from Linux shell) for backup and restore operations.
  • Discuss limitations and best practices for Linux environments explicitly, not just as a secondary note.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/monitor-azure-backup-with-backup-explorer.md ...es/backup/monitor-azure-backup-with-backup-explorer.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 exclusively referencing Azure virtual machines (VMs) and workflows that are typically associated with Windows environments. There are no examples, mentions, or guidance for Linux VMs or Linux-specific backup scenarios. Export functionality is described only in terms of Excel, a Windows-centric tool, and there is no mention of alternative formats or tools commonly used on Linux. The navigation and action patterns (e.g., Azure portal panes, Excel export) are presented without Linux parity or alternatives.
Recommendations
  • Include explicit examples and guidance for monitoring backups of Linux VMs, including any differences in workflow or supported features.
  • Mention and provide instructions for exporting data in open formats (e.g., CSV, JSON) and using Linux-friendly tools (e.g., LibreOffice, command-line utilities).
  • Clarify whether Backup Explorer supports Linux VMs and, if so, highlight any Linux-specific considerations or limitations.
  • Add references to cross-platform automation options (e.g., Azure CLI, REST API) for users who may not use Windows or PowerShell.
  • Ensure that screenshots and navigation instructions are applicable to both Windows and Linux users, or note any differences.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/install-mars-agent.md ...e-docs/blob/main/articles/backup/install-mars-agent.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All instructions, examples, and prerequisites are specific to Windows machines, including references to Windows-only tools (MARSagentinstaller.exe, Windows Powershell, .NET Framework). There are no examples, instructions, or mentions of Linux support or alternatives. The page assumes the user is backing up Windows machines and does not address Linux scenarios.
Recommendations
  • Clarify early in the documentation that the MARS agent is only supported on Windows, and provide links or guidance for Linux backup solutions (such as Azure Backup for Linux VMs or Azure Backup extension for Linux).
  • Add a comparison table or section outlining backup options for both Windows and Linux, with clear guidance on which agent or extension to use for each OS.
  • If possible, include Linux-specific backup instructions or link to relevant documentation for Linux users.
  • Avoid using 'machines' generically when only Windows is supported; specify 'Windows machines' throughout to prevent confusion.
  • Provide parity in troubleshooting and prerequisites, mentioning Linux equivalents or alternatives where appropriate.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/pre-backup-post-backup-scripts.md ...main/articles/backup/pre-backup-post-backup-scripts.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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, referencing Windows-specific paths, tools, and conventions (e.g., 'Drive:', 'Microsoft Data Protection Manager', 'cscript', and Windows SharePoint Services). There are no examples or instructions for Linux systems, nor any mention of Linux-compatible scripting or file paths.
Recommendations
  • Add explicit instructions and examples for configuring pre- and post-backup scripts on Linux-based protected computers, including typical file paths and permissions.
  • Include Linux shell script examples (e.g., Bash) alongside Windows batch/PowerShell examples.
  • Clarify whether MABS supports Linux agents and, if so, document any differences in script configuration and execution.
  • Mention Linux equivalents for Windows-specific tools and conventions (e.g., use of /mnt/data instead of Drive:, and shell interpreters instead of cscript).
  • Ensure that references to application data sources (SQL, Exchange, SharePoint) include Linux-supported alternatives where applicable.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-azure-files-vault-tier-arm.md ...cles/backup/quick-backup-azure-files-vault-tier-arm.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 and PowerShell usage. The only explicit command-line deployment example uses Azure PowerShell, with no Azure CLI or Bash example provided. In the 'Next steps' section, PowerShell-based management tasks are listed before CLI or REST API alternatives, and tracking/restore links prioritize PowerShell. There is no mention of Linux-specific workflows or tools, and the documentation does not provide parity for Linux users who may prefer Azure CLI or Bash.
Recommendations
  • Add Azure CLI and Bash examples for ARM template deployment alongside the PowerShell example.
  • In the 'Next steps' section, list Azure CLI and REST API options before or alongside PowerShell to avoid ordering bias.
  • Explicitly mention that all deployment and management steps can be performed on Linux/macOS using Azure CLI.
  • Provide links to Azure CLI documentation for tracking backup jobs and restoring files, ensuring Linux users have clear guidance.
  • Consider including a table or section comparing PowerShell, CLI, and portal workflows for cross-platform clarity.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/manage-backup-vault.md ...-docs/blob/main/articles/backup/manage-backup-vault.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 primarily through the prioritization of Windows-centric tools and workflows. PowerShell is mentioned explicitly as a method for moving Backup vaults, while Linux-specific command-line examples (such as Bash or Azure CLI on Linux) are not provided. The instructions and screenshots focus on the Azure portal, which is platform-agnostic, but when scripting is referenced, PowerShell is listed first and CLI is mentioned only as a secondary option, with no concrete examples for either. There are no Linux shell or cross-platform script examples, nor any mention of Linux-specific considerations.
Recommendations
  • Provide explicit Azure CLI examples for all operations where PowerShell is referenced, including moving Backup vaults.
  • Include Bash shell script examples for common tasks to demonstrate Linux parity.
  • When listing command-line options, mention Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and provide platform-agnostic instructions.
  • Add a section or note highlighting cross-platform management options and best practices for Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/move-to-azure-monitor-alerts.md ...b/main/articles/backup/move-to-azure-monitor-alerts.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and patterns, such as the Microsoft Azure Recovery Services (MARS) agent, System Center Data Protection Manager (SC-DPM), and Microsoft Azure Backup Server (MABS), all of which are Windows-only solutions. The discussion of alert exceptions and job status mentions 'portal/PowerShell/the CLI clients', listing PowerShell before CLI, which is more commonly used on Linux. There are no explicit Linux-specific examples, nor are Linux backup agents or workflows mentioned. Notification configuration is stated to be available only via the Azure portal, with no mention of Linux-friendly automation or scripting alternatives.
Recommendations
  • Add examples and references for Linux backup agents and workflows, such as Azure VM Linux backup scenarios.
  • Provide CLI (az) and REST API examples for alert management and notification configuration, with clear instructions for Linux users.
  • Mention Linux-compatible backup tools or patterns where appropriate, and avoid listing Windows tools before their cross-platform equivalents.
  • Clarify whether features (such as notification configuration) are equally available to Linux users, and provide parity where possible.
  • Include screenshots or walkthroughs using the Azure CLI on Linux, not just portal or PowerShell.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/offline-backup-azure-data-box-dpm-mabs.md ...icles/backup/offline-backup-azure-data-box-dpm-mabs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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. All instructions, examples, and prerequisites are specific to Windows Server (2016/2019), DPM, and MABS, with no mention of Linux or cross-platform alternatives. The use of Windows-specific tools (PSExec, Windows Registry, Windows certificate manager), PowerShell modules, and Windows paths further reinforces this bias. No Linux equivalents or guidance are provided, and the workflow assumes a Windows-only context throughout.
Recommendations
  • Add explicit statements about Linux support or lack thereof for DPM/MABS and Azure Data Box workflows.
  • If Linux support is possible, provide equivalent instructions for Linux environments, including mounting Data Box via NFS, certificate management, and Azure CLI/PowerShell alternatives.
  • Include examples using Linux tools (e.g., mount, openssl, Azure CLI) where applicable.
  • Clarify platform limitations early in the documentation and link to Linux-specific backup solutions if DPM/MABS is Windows-only.
  • Consider restructuring sections to mention cross-platform options or alternatives before diving into Windows-specific steps.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-postgresql-flexible-server-arm.md .../backup/quick-backup-postgresql-flexible-server-arm.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 exclusively providing PowerShell deployment instructions for the ARM template, with no equivalent Azure CLI or Bash examples for Linux/macOS users. The prerequisites and next steps also emphasize PowerShell, further reinforcing the Windows-centric approach.
Recommendations
  • Add Azure CLI and Bash examples for deploying the ARM template, ensuring Linux/macOS users have clear guidance.
  • Mention Azure CLI as an alternative in the prerequisites section, alongside PowerShell.
  • Provide links to both PowerShell and CLI-based restore guides in the 'Next steps' section.
  • Ensure that all tooling instructions (installation, usage) are platform-neutral or offer parity for Linux/macOS environments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/microsoft-azure-backup-server-protection-v3.md .../backup/microsoft-azure-backup-server-protection-v3.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Windows Heavy
Summary
The documentation page exhibits strong Windows bias: nearly all examples, supported workloads, and backup scenarios are centered on Windows operating systems and applications (Windows Server, SQL Server, Exchange, SharePoint, Hyper-V). Linux support is mentioned only briefly and solely as a guest VM, with no details on file-level backup or recovery, nor any Linux-specific backup scenarios or tools. Windows-specific technologies (NTFS, VSS, ReFS, Windows Management Framework, Hyper-V, etc.) are referenced throughout, while Linux equivalents are absent.
Recommendations
  • Add explicit examples and matrix entries for Linux workloads, including supported distributions, file systems, and backup/recovery scenarios.
  • Clarify whether file-level backup and item-level recovery are supported for Linux VMs, and if not, document any roadmap or alternatives.
  • Include Linux-specific backup technologies (e.g., LVM snapshots, ext4/xfs file systems) and note any limitations or requirements.
  • Provide parity in documentation for Linux environments, such as backup of physical Linux servers, not just VMs.
  • Mention Linux tools and patterns where relevant, and avoid referencing only Windows-centric technologies (e.g., NTFS, VSS) without Linux context.
  • Add guidance for Linux admins on best practices for using Azure Backup Server with Linux workloads.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-install-backup-extension.md ...main/articles/backup/quick-install-backup-extension.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily describes installation of the Azure Backup extension in an AKS cluster using the Azure portal, which is platform-agnostic but often associated with Windows environments. In the 'Next steps' section, Azure PowerShell is mentioned before Azure CLI, ARM, Bicep, and Terraform, suggesting a Windows-first approach. There are no explicit Linux-specific instructions, nor are there examples using Linux-native tools or shell commands. No screenshots or examples show Linux terminal usage.
Recommendations
  • Provide explicit Linux command-line examples (e.g., using Azure CLI in Bash) alongside or before PowerShell examples.
  • Ensure parity by including instructions for installing and managing the extension via Linux shell environments.
  • Reorder 'Next steps' to mention Azure CLI before PowerShell, as CLI is cross-platform and more commonly used in Linux environments.
  • Add screenshots or terminal output from Linux environments to demonstrate cross-platform support.
  • Clarify that the Azure portal and CLI instructions apply equally to Windows, Linux, and macOS, and highlight any platform-specific considerations.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/manage-telemetry.md ...ure-docs/blob/main/articles/backup/manage-telemetry.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows environments, specifically referencing the Microsoft Azure Backup Server (MABS) console, which is a Windows-only tool. All instructions and screenshots pertain to the Windows GUI, with no mention of Linux equivalents, command-line alternatives, or cross-platform considerations. There are no examples or guidance for managing telemetry settings on Linux systems, nor any references to Linux tools or patterns.
Recommendations
  • Clarify platform support: Explicitly state whether MABS and its telemetry management features are available only on Windows, or if there are Linux equivalents.
  • Provide Linux alternatives: If telemetry settings can be managed on Linux, include instructions using Linux tools (e.g., configuration files, CLI commands) and examples.
  • Add parity in examples: For each Windows-based example, provide a corresponding Linux example if applicable.
  • Mention cross-platform considerations: If the feature is Windows-only, explain why and suggest alternatives for Linux users (such as Azure Backup agent for Linux or other backup solutions).
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/multi-user-authorization.md .../blob/main/articles/backup/multi-user-authorization.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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. There are no explicit Linux shell (bash) examples, nor any mention of Linux-specific tooling or considerations. The documentation assumes users are familiar with PowerShell, which is traditionally a Windows-centric tool, and does not address Linux environments or shell usage directly. No Linux-specific screenshots, instructions, or troubleshooting are provided.
Recommendations
  • Present Azure CLI examples before PowerShell examples, or alternate their order to avoid implicit prioritization.
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide example shell environments (e.g., bash, zsh).
  • Add Linux-specific notes or troubleshooting steps, especially for authentication flows and file paths.
  • Include screenshots or instructions for Linux terminal usage where relevant.
  • Clarify that PowerShell Core is cross-platform, but also provide bash equivalents for scripting tasks.
  • Ensure that all command-line instructions are tested and documented for Linux environments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-terraform.md ...blob/main/articles/backup/quick-backup-vm-terraform.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively demonstrates backup for an Azure Windows virtual machine, with no mention of Linux VM equivalents or examples. The resource creation and verification steps are tailored to Windows VMs, and the 'Next steps' section further emphasizes Windows VM articles. There are no Linux VM Terraform code samples, nor any guidance for Linux-specific backup scenarios.
Recommendations
  • Add parallel instructions and Terraform code samples for creating and backing up an Azure Linux VM.
  • Include verification steps for Linux VMs, such as retrieving Linux VM names and running backup commands.
  • Update the 'Next steps' section to link to both Windows and Linux VM articles.
  • Clarify in the introduction that the process applies to both Windows and Linux VMs, or specify that this article is Windows-specific and provide a link to a Linux version.
  • Ensure examples and terminology are inclusive of both platforms, or provide platform-specific guidance where necessary.
GitHub Create Pull Request
← Previous Page 34 of 65 Next →