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 776-800 of 1604 flagged pages
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-arm-restore-vms.md ...b/main/articles/backup/backup-azure-arm-restore-vms.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several areas: Windows-specific examples and links (such as PowerShell and Windows VM guides) are provided before or instead of Linux equivalents, especially in restore scenarios and network configuration. References to Windows tools and patterns (e.g., bcdedit, netdom, RDP, Windows Server AD recovery) are prevalent, while Linux-specific guidance is minimal or missing. Where Linux is mentioned (e.g., cloud-init), the guidance is brief and lacks parity with the detailed Windows instructions.
Recommendations
  • Provide Linux-specific examples and guidance for common restore scenarios, such as restoring Linux VMs, handling SSH keys, and troubleshooting post-restore access.
  • Include links to Linux documentation (e.g., restoring Linux VMs, configuring network interfaces, resetting passwords via cloud-init or SSH) alongside Windows links.
  • Balance PowerShell examples with Azure CLI and Bash scripts for VM creation, disk attachment, and network configuration.
  • Add troubleshooting steps for Linux VMs (e.g., repairing broken domain relationships for Linux AD-integrated VMs, restoring cloud-init functionality, resetting sudo passwords).
  • Where Windows tools (bcdedit, netdom, RDP) are referenced, provide Linux equivalents (e.g., grub, SSH, Linux domain tools) and clarify which steps are OS-specific.
  • Ensure that all restore options and features (such as managed identities, network configuration, and backup continuation) are explained for both Windows and Linux VMs.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-server-vmware.md ...n/articles/backup/backup-azure-backup-server-vmware.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 for backing up VMware VMs using Azure Backup Server (MABS) is heavily oriented toward Windows environments. All examples, configuration steps, and scripts assume the use of Windows tools (Registry Editor, Certificate Import Wizard, PowerShell, .reg files), with no mention of Linux equivalents or cross-platform alternatives. There are no Linux-specific instructions or examples, and all automation and scripting guidance is provided in PowerShell, which is native to Windows. The documentation also references Windows-specific paths and GUI dialogs, reinforcing the Windows-centric approach.
Recommendations
  • Provide Linux-specific instructions for certificate import, such as using openssl and update-ca-certificates.
  • Include examples using Bash or Python scripts for automation, in addition to PowerShell.
  • Document how to configure MABS or interact with VMware from Linux-based management hosts, if supported.
  • Clarify whether MABS can be installed or managed from Linux, and if not, explicitly state the Windows-only requirement.
  • Where registry edits are required, suggest Linux equivalents (e.g., config files) or note that these steps are not applicable on Linux.
  • Add a section comparing Windows and Linux management workflows for VMware backup, highlighting any differences or limitations.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-backup-disks.md ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-backup-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 page demonstrates Windows bias primarily through its references and links. The only explicit tool mentioned for assigning permissions is Azure PowerShell, with the link to prerequisites pointing to a PowerShell-focused page. In the 'Next steps' section, PowerShell is listed before Azure CLI, and no Linux-specific examples or shell commands are provided anywhere in the page. There is no mention of Linux tools, nor are there bash or shell script examples for REST API calls, which are common for Linux users. All examples are generic HTTP requests and JSON bodies, but the supporting tooling and guidance lean toward Windows/PowerShell.
Recommendations
  • Provide explicit examples using Azure CLI (az) for all operations, especially for assigning permissions and managing backup instances.
  • Ensure that links to prerequisites and related tasks include both PowerShell and CLI/Linux options, or link to pages that cover both.
  • Add sample curl commands for REST API calls to demonstrate usage in Linux/macOS environments.
  • List Azure CLI before PowerShell in 'Next steps' or present them together to avoid perceived prioritization.
  • Include a note or section on cross-platform usage, clarifying that all operations can be performed from Linux, macOS, or Windows, and provide guidance for each.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-sharepoint-mabs.md ...articles/backup/backup-azure-backup-sharepoint-mabs.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 biased toward Windows environments. All instructions, tools, and examples are based on Windows-specific components (e.g., CMD, Registry Editor, NT AUTHORITY\SYSTEM, %Program Files%, HKLM), and the use of Microsoft Azure Backup Server (MABS) is described exclusively in the context of Windows servers. There are no references to Linux equivalents, nor are any cross-platform or Linux-specific instructions, tools, or examples provided. The documentation assumes the reader is operating in a Windows domain and using Windows administrative patterns.
Recommendations
  • Explicitly state platform requirements and limitations at the beginning of the document, clarifying that MABS is Windows-only if that is the case.
  • If Linux support is possible (e.g., via Azure Backup or other tools), provide parallel instructions or links for Linux-based SharePoint deployments or alternatives.
  • Where possible, mention cross-platform backup solutions or Azure-native backup options that work with Linux servers.
  • Include a section comparing Windows and Linux backup scenarios, even if only to clarify that Linux is unsupported by MABS, and suggest alternatives.
  • Avoid using Windows-specific terminology (e.g., Registry Editor, %Program Files%, HKLM) without noting that these steps are not applicable to Linux.
  • If the product is Windows-only, make this explicit in prerequisites and supported scenarios, and direct Linux users to appropriate resources.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-database-postgresql-overview.md ...es/backup/backup-azure-database-postgresql-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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the pgAdmin GUI tool (commonly used on Windows) for database management and privilege assignment, without mentioning or providing examples for Linux-native or CLI-based alternatives (such as psql). There are no Linux-specific instructions, nor are command-line examples provided for common administrative tasks. The documentation also refers to Azure portal screenshots and workflows, which are typically accessed via a browser on Windows, and does not mention cross-platform or Linux-friendly approaches.
Recommendations
  • Include examples using psql, the PostgreSQL command-line client, for database management and privilege assignment. Provide equivalent SQL commands and connection instructions for Linux users.
  • Mention and provide instructions for using Azure CLI and Azure PowerShell for backup configuration and management, noting cross-platform compatibility.
  • Reference Linux-native tools (such as DBeaver or CLI utilities) alongside pgAdmin, and clarify that pgAdmin is available on multiple platforms.
  • Add explicit notes or sections for Linux users, including firewall rule configuration and connectivity steps from Linux environments.
  • Ensure screenshots and instructions are platform-neutral or provide alternatives for Linux desktop environments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-mabs-troubleshoot.md ...main/articles/backup/backup-azure-mabs-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 Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation for troubleshooting Azure Backup Server exhibits a strong Windows bias. All examples, paths, tools, and troubleshooting steps are tailored exclusively for Windows environments. Windows-specific tools (e.g., registry editor, Windows services, Control Panel, Internet Explorer, Windows Server Backup, DPM, MARS agent) are referenced throughout, with no mention of Linux equivalents or cross-platform considerations. File paths, commands, and service management instructions are Windows-centric, and there are no Linux or PowerShell Core examples. Linux backup scenarios, troubleshooting steps, or agent installation are not addressed.
Recommendations
  • Add troubleshooting steps and examples for Linux-based servers, including common issues and solutions.
  • Include Linux file paths and service management commands (e.g., systemctl, journalctl) where relevant.
  • Reference Linux-compatible backup agents and document their installation, configuration, and troubleshooting.
  • Provide parity in antivirus configuration instructions for Linux (e.g., excluding directories in ClamAV, Sophos, etc.).
  • Document how to verify network connectivity, agent status, and service health on Linux systems.
  • Include PowerShell Core and Bash examples for cross-platform command-line operations.
  • Mention any limitations or unsupported scenarios for Linux, if applicable, to clarify platform coverage.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-monitoring-built-in-monitor.md ...les/backup/backup-azure-monitoring-built-in-monitor.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 Windows bias by referencing Windows-specific backup tools (DPM, MABS, MARS) and providing links and examples focused on Windows Server management. There is no mention of Linux backup agents, Linux-specific monitoring, or parity in examples for Linux workloads. Windows tools and scenarios are described in detail, while Linux equivalents are absent.
Recommendations
  • Include examples and guidance for monitoring Linux-based backup workloads, such as Azure Backup for Linux VMs or Azure Backup agent for Linux.
  • Mention Linux-compatible backup tools and their monitoring capabilities alongside Windows tools like DPM, MABS, and MARS.
  • Provide parity in documentation structure by offering Linux-specific navigation paths, screenshots, and troubleshooting notes.
  • Add notes or sections clarifying differences and similarities in monitoring between Windows and Linux workloads.
  • Ensure that links and references to management guides include Linux scenarios, not just Windows Server.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-delete-vault.md ...blob/main/articles/backup/backup-azure-delete-vault.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 clear Windows bias. PowerShell is presented as the primary automation method, with detailed scripts and command references. Windows-specific backup management tools (MARS, MABS, DPM) are referenced throughout, with instructions and screenshots for their consoles. The ARMClient tool is installed via Chocolatey (a Windows package manager), and only Windows-centric methods are described for on-premises scenarios. Linux equivalents for backup management, automation, or CLI usage are absent or minimally addressed. The CLI section is limited in scope and does not provide parity with PowerShell or Windows tools.
Recommendations
  • Provide equivalent Linux automation examples, such as Bash scripts using Azure CLI, for vault and backup deletion.
  • Include instructions for installing and using ARMClient on Linux (e.g., via .NET Core or direct download), not just via Chocolatey.
  • Reference cross-platform package managers (e.g., apt, yum, Homebrew) for tool installation where applicable.
  • Clarify which backup management features/tools are available on Linux and provide guidance for Linux-based on-premises backup scenarios.
  • Ensure CLI examples cover all supported backup item types, or clearly state limitations and provide alternatives for Linux users.
  • Add screenshots and walkthroughs for Linux environments where possible, especially for Azure CLI and portal usage from Linux systems.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-encrypted-vm-troubleshoot.md ...icles/backup/backup-azure-encrypted-vm-troubleshoot.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 referencing PowerShell as the only command-line example for configuring permissions, without mentioning Linux equivalents such as Azure CLI or Bash. There are no Linux-specific instructions or examples, and the documentation implicitly assumes a Windows-centric workflow by listing PowerShell before any other tooling.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell for all command-line instructions.
  • Explicitly mention Linux support and provide troubleshooting steps relevant to Linux-based Azure VMs.
  • Ensure parity in tool references by listing cross-platform tools (Azure CLI, REST API) before or alongside Windows-specific tools.
  • Add notes or sections highlighting differences or considerations for Linux VMs when backing up and restoring encrypted disks.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-mars-troubleshoot.md ...main/articles/backup/backup-azure-mars-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 Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. All troubleshooting steps, examples, and tool references are specific to Windows (e.g., MMC console, Internet Explorer, Task Scheduler, Registry, Device Manager, vssadmin, PowerShell). There are no Linux equivalents or examples, and the documentation does not mention Linux support or alternative procedures for non-Windows systems. The use of Windows-specific tools and terminology is pervasive throughout the document.
Recommendations
  • Clarify in the introduction whether the MARS agent is Windows-only, or provide equivalent troubleshooting steps for Linux if supported.
  • Add Linux-specific troubleshooting sections if the agent supports Linux, including commands, log locations, and common issues.
  • Provide examples using Linux tools (e.g., systemctl, journalctl, cron, bash scripts) alongside Windows tools.
  • Replace or supplement references to Internet Explorer, Task Scheduler, Registry, and MMC console with cross-platform alternatives or note their Windows specificity.
  • Include PowerShell alternatives for Linux (such as Bash or Azure CLI) where applicable.
  • Explicitly state OS requirements and limitations at the top of the documentation.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-exchange-mabs.md ...lob/main/articles/backup/backup-azure-exchange-mabs.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 for Microsoft Exchange using Azure Backup Server (MABS), which is a Windows-only tool. All instructions, screenshots, and examples reference Windows environments, such as using the MABS Administrator Console, copying files to C:\Program Files, and running Windows-specific utilities like Eseutil.exe. There are no Linux equivalents, nor is there any mention of Linux-based Exchange deployments or backup tools. The documentation assumes the reader is operating in a Windows ecosystem from start to finish.
Recommendations
  • Explicitly state that MABS and Exchange Server are Windows-only products, and clarify platform requirements in the prerequisites.
  • If Linux-based Exchange alternatives (e.g., via IMAP/SMTP or open-source mail servers) are supported by Azure Backup, provide parallel instructions or links.
  • Offer guidance or references for backing up mail servers on Linux, such as using Azure Backup for Linux workloads or third-party solutions.
  • Include a comparison table or section outlining backup options for both Windows and Linux mail servers to help users choose the right solution for their environment.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-recovery-services-vault-overview.md ...ackup/backup-azure-recovery-services-vault-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 page demonstrates a moderate Windows bias. While it mentions support for both Linux and Windows VMs, most examples, linked resources, and tool references focus on Windows-centric technologies (e.g., System Center DPM, Windows Server, Azure Backup Server). There is a lack of explicit Linux backup scenarios, tools, or walkthroughs, and Windows-specific backup methods are referenced before or instead of Linux equivalents.
Recommendations
  • Include explicit examples and walkthroughs for backing up Linux VMs and workloads using Recovery Services vaults.
  • Reference Linux-compatible backup tools and agents (such as Azure VM extension for Linux) alongside Windows tools.
  • Ensure parity in documentation links: provide direct links to Linux backup guides and FAQs, not just Windows Server or DPM.
  • Add a section or table comparing backup procedures for Windows and Linux environments.
  • Highlight any differences or considerations for Linux users (e.g., file system support, agent installation, restore scenarios).
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dpm-introduction.md .../main/articles/backup/backup-azure-dpm-introduction.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows environments, specifically System Center Data Protection Manager (DPM), which is a Windows-only product. All examples, prerequisites, and tooling references (such as PowerShell, .NET Framework, and MARSAgentInstaller.exe) are Windows-centric. There are no Linux equivalents, examples, or mentions of cross-platform alternatives. The documentation assumes the administrator is working in a Windows environment and does not address Linux backup scenarios or tooling.
Recommendations
  • Clarify early in the documentation that DPM is a Windows-only solution, and provide links to Azure Backup documentation for Linux workloads.
  • Add a section or cross-reference for backing up Linux servers to Azure, including supported agents and procedures.
  • Where PowerShell is mentioned, offer equivalent CLI or Bash examples for Linux environments, if applicable.
  • Discuss Azure Backup agent support and installation for Linux, including prerequisites and troubleshooting.
  • Explicitly state limitations regarding non-Windows platforms and suggest alternative backup strategies for Linux workloads.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-restore-files-from-vm.md .../articles/backup/backup-azure-restore-files-from-vm.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 instructions and tools (such as registry edits, Storage Spaces, and File Explorer) are described in greater detail and often appear before Linux equivalents. Windows-specific troubleshooting steps (e.g., registry key changes) are more explicit, while Linux steps are less detailed or rely on generic commands. PowerShell is referenced in the 'Next steps' section before Azure CLI, and Windows terminology (e.g., 'Download Executable') is prioritized over Linux ('Download Script'). Some examples and screenshots are Windows-centric, and Linux instructions sometimes lack parity in depth and troubleshooting guidance.
Recommendations
  • Ensure Linux instructions are as detailed as Windows ones, especially for troubleshooting (e.g., provide more explicit steps for Linux disk mounting issues, permissions, and error handling).
  • Present Windows and Linux steps in parallel, or alternate which OS is described first in each section.
  • Include Linux-specific screenshots and examples where Windows screenshots are provided.
  • Reference Azure CLI and Linux tools before or alongside PowerShell and Windows tools in 'Next steps' and throughout the documentation.
  • Expand Linux troubleshooting guidance to match the registry-level detail given for Windows (e.g., more on iSCSI, LVM, RAID, and permissions).
  • Avoid using Windows-centric terminology (e.g., 'Download Executable') as the default; clarify both OS options equally.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-database-postgresql.md ...in/articles/backup/backup-azure-database-postgresql.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 areas. PowerShell is the only scripting example provided for granting database privileges, and the instructions for setting up environment variables are exclusively Windows-centric (Control Panel, System Properties). There are no Linux or macOS equivalents for these steps, nor are Linux shell commands or environment variable setup instructions given. The use of Windows tools and patterns (e.g., Notepad, Control Panel) is assumed throughout, and Linux alternatives are not mentioned or linked.
Recommendations
  • Provide Linux/macOS equivalents for environment variable setup (e.g., using .bashrc, export commands).
  • Include bash or shell script examples alongside PowerShell for granting database privileges.
  • Mention and demonstrate use of Linux-native editors (e.g., nano, vim) for editing connection strings.
  • Clarify that the PSQL tool is cross-platform and provide installation instructions for Linux/macOS.
  • Ensure screenshots and step-by-step instructions are available for both Windows and Linux environments.
  • Explicitly state that the instructions apply to all platforms, or provide platform-specific sections.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-manage-vms.md ...s/blob/main/articles/backup/backup-azure-manage-vms.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation predominantly focuses on Windows-based workflows, especially in the section on reinstalling the VMSnapshot backup extension, where detailed, step-by-step instructions are provided for Windows VMs using PowerShell, Windows-specific tools (Registry Editor, services.msc), and Windows file paths. In contrast, the Linux section is minimal, offering only brief, high-level commands without detailed guidance or troubleshooting. Throughout the rest of the document, examples and screenshots are Windows-centric, and Linux equivalents are either missing or less detailed.
Recommendations
  • Provide equally detailed, step-by-step instructions for Linux VMs, including commands for common distributions, relevant file paths, and troubleshooting steps.
  • Include Linux CLI examples (e.g., Bash, Azure CLI) alongside PowerShell commands throughout the documentation.
  • Ensure screenshots and UI walkthroughs include Linux VM contexts where applicable.
  • Mention Linux tools and patterns (e.g., systemd for services, Linux file permissions) in parity with Windows tools.
  • Review all sections for implicit Windows-first language and rephrase to be OS-neutral where possible.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-move-recovery-services-vault.md ...es/backup/backup-azure-move-recovery-services-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 by providing PowerShell examples for moving Recovery Services vaults, referencing Windows-specific update instructions, and omitting Linux-specific command-line examples (such as Bash scripting or Linux shell usage). While Azure CLI is mentioned, there is a lack of parity in detailed Linux-oriented guidance, and Windows update instructions are given before Linux equivalents.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux users alongside PowerShell examples.
  • Include explicit instructions for updating Linux VMs (e.g., sample commands for popular distributions like Ubuntu, CentOS) rather than generic 'refer to distributor guidance'.
  • Ensure that CLI examples are presented with both Windows (CMD/PowerShell) and Linux (Bash) syntax where differences exist.
  • Avoid presenting Windows-specific instructions before Linux equivalents; instead, group OS-specific guidance together or alternate the order.
  • Reference Linux-native tools (such as curl, wget, or az CLI in Bash) where appropriate, and clarify any OS-specific prerequisites or steps.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vm-file-recovery-troubleshoot.md ...s/backup/backup-azure-vm-file-recovery-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 Windows bias in several ways: Windows troubleshooting steps and tools (e.g., File Explorer, Disk Management, Server Manager, ISCSI initiator Properties) are described in detail with screenshots, while Linux instructions are often brief and refer to external links. Windows examples and solutions are typically presented before Linux equivalents, and some troubleshooting steps (such as disk management and deduplication) are only explained for Windows. Linux guidance is sometimes missing or less detailed, relying on users to follow external documentation.
Recommendations
  • Provide equally detailed, step-by-step instructions for Linux scenarios, including screenshots of relevant Linux tools (e.g., GNOME Disks, lsblk, mount commands).
  • Include Linux-specific troubleshooting for issues like disk attachment, volume mounting, and deduplication, with concrete command-line examples.
  • Present Windows and Linux solutions in parallel sections, ensuring neither is prioritized over the other.
  • Avoid referencing Windows tools (e.g., File Explorer, Disk Management) without offering Linux alternatives (e.g., Nautilus, GNOME Disks, CLI commands).
  • Ensure all error messages and troubleshooting steps have both Windows and Linux examples where applicable.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-private-endpoints-concept.md ...icles/backup/backup-azure-private-endpoints-concept.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 page demonstrates a Windows bias by focusing on Windows-centric backup tools (MARS agent, DPM, MABS), mentioning them exclusively and in detail, and omitting Linux-specific backup scenarios or agents. All examples and recommendations are centered around Windows workloads (SQL Server, SAP HANA in Azure VM, MARS agent, DPM), with no mention of Linux backup agents, Linux VM scenarios, or Linux-specific configuration steps. There are no PowerShell-specific commands, but the overall narrative and supported scenarios are Windows-first and Windows-only.
Recommendations
  • Add explicit examples and guidance for Linux VM backup scenarios, including how private endpoints affect Linux VM backups.
  • Mention and document Linux-compatible backup agents or extensions, if available, and describe their network requirements in parity with Windows tools.
  • Include a table or section comparing Windows and Linux backup scenarios, highlighting any differences or similarities in private endpoint usage.
  • Provide sample DNS and network configuration steps for Linux environments (e.g., using /etc/hosts, systemd-resolved, or common Linux DNS setups).
  • Clarify whether private endpoints are supported for Linux workloads and agents, and if so, provide step-by-step instructions for Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-monitor-troubleshoot.md ...n/articles/backup/backup-azure-monitor-troubleshoot.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 exclusively references Windows-specific tools and patterns (Task Manager, Control Panel, Windows file paths) for troubleshooting Azure Backup monitoring issues. No Linux equivalents or cross-platform guidance is provided, and all examples and instructions assume a Windows environment.
Recommendations
  • Add troubleshooting steps for Linux environments, including how to check and manage relevant processes and services using Linux commands (e.g., systemctl, ps, service).
  • Provide Linux file path examples for log locations, if Azure Backup agent is supported on Linux.
  • Mention cross-platform tools or clarify platform-specific instructions at the start of each troubleshooting section.
  • Ensure parity in examples and screenshots for both Windows and Linux environments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-manage-mars.md .../blob/main/articles/backup/backup-azure-manage-mars.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 the Microsoft Azure Recovery Services (MARS) Agent, which is a Windows-only tool. All examples, screenshots, and instructions reference Windows interfaces, paths, and tools (e.g., MARS console, %ProgramFiles%, .exe binaries, Windows Server, DPM/MABS). There are no Linux equivalents, examples, or mentions of Linux backup agents or workflows. Antivirus configuration and troubleshooting steps are also Windows-centric.
Recommendations
  • Clearly state at the beginning that MARS Agent is a Windows-only solution and provide links to equivalent Linux backup solutions (such as Azure Backup for Linux or Azure VM Backup).
  • Add a comparison section highlighting differences between Windows (MARS Agent) and Linux backup approaches in Azure.
  • Where possible, provide guidance or references for Linux users, including links to documentation for configuring and monitoring backups on Linux systems.
  • Ensure that related documentation (e.g., support matrix, FAQ) also clarifies platform support and directs Linux users to appropriate resources.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-sql-mabs.md ...ocs/blob/main/articles/backup/backup-azure-sql-mabs.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, focusing exclusively on Microsoft Azure Backup Server (MABS) and Data Protection Manager (DPM), both of which are Windows-only tools. All examples, screenshots, and instructions assume the use of Windows Server and SQL Server on Windows. There is no mention of Linux-based SQL Server deployments, nor are there any examples or guidance for backing up SQL Server running on Linux. Windows-specific concepts (e.g., NTAuthority\System, Windows Azure Blob storage, protection group creation in the MABS/DPM console) are used throughout, with no Linux equivalents or alternatives provided.
Recommendations
  • Add explicit guidance and examples for backing up SQL Server running on Linux, including any Azure-native or third-party backup solutions that support Linux.
  • Clarify in the prerequisites and introduction that MABS/DPM are Windows-only, and provide links or references to backup solutions for SQL Server on Linux.
  • Include parity in screenshots and step-by-step instructions for Linux environments, if supported, or offer alternative workflows for Linux users.
  • Mention and compare any cross-platform backup tools or Azure services that can be used for both Windows and Linux SQL Server deployments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-security-feature.md .../main/articles/backup/backup-azure-security-feature.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 exclusively discusses security features for Azure Backup in the context of Microsoft tools (MABS, DPM, MARS) that are Windows-only. All examples, instructions, and troubleshooting steps reference Windows environments, Windows agents, and Windows-centric tools (including PowerShell commands). There is no mention of Linux backup agents, Linux-specific procedures, or parity for Linux workloads. The documentation implicitly assumes the user is operating in a Windows ecosystem.
Recommendations
  • Explicitly state the scope of supported platforms at the beginning, clarifying if Linux workloads are not supported by these features.
  • Add equivalent instructions, examples, and troubleshooting steps for Linux backup scenarios if supported by Azure Backup.
  • Include references to Linux backup agents or third-party tools where applicable, and provide parity in documentation for enabling, configuring, and recovering backups on Linux systems.
  • If features are not available for Linux, provide guidance or links to alternative security best practices for Linux backup scenarios.
  • Balance PowerShell/Windows command examples with Bash/Linux CLI equivalents where possible.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-system-state-troubleshoot.md ...icles/backup/backup-azure-system-state-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 Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically on-premises Windows servers. All troubleshooting steps, examples, and commands use Windows-specific tools (PowerShell, Server Manager, wbadmin), and there is no mention of Linux systems, Linux equivalents, or cross-platform considerations. Windows terminology and tools are presented exclusively and in detail, with no Linux parity.
Recommendations
  • Clearly state in the introduction that System State Backup is a Windows-only feature, and provide links or references to equivalent backup solutions for Linux systems if relevant.
  • Where possible, mention Linux backup and recovery options (e.g., Azure Backup for Linux, or third-party solutions) and provide troubleshooting resources for those platforms.
  • If the documentation is intended to be cross-platform, add Linux-specific troubleshooting steps, commands, and examples alongside Windows ones.
  • Avoid using Windows terminology (e.g., PowerShell, Server Manager) exclusively; provide parity for Linux (e.g., Bash commands, Linux backup utilities) where applicable.
  • Include a comparison table or section outlining differences and similarities between Windows and Linux backup solutions in Azure.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-restore-system-state.md ...n/articles/backup/backup-azure-restore-system-state.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation is exclusively focused on Windows Server, with all examples, tools, and instructions tailored to Windows environments. It references only Windows-specific utilities (MARS agent, Windows Server Backup, wbadmin, Win RE) and does not mention or provide guidance for Linux systems or cross-platform scenarios. There are no Linux equivalents, examples, or alternative instructions, indicating a strong Windows bias.
Recommendations
  • Add a section clarifying platform support, explicitly stating whether Linux servers are supported for System State backup/restore in Azure, or if this is a Windows-only feature.
  • If Linux support exists, provide equivalent step-by-step instructions for restoring system state on Linux servers, including relevant tools (e.g., Azure Backup agent for Linux, native Linux backup/restore utilities).
  • Include Linux command-line examples and screenshots where appropriate.
  • Reference Linux documentation for backup and restore procedures, or link to relevant Azure/Linux resources.
  • If the feature is Windows-only, make this clear at the beginning of the article to set user expectations and avoid confusion.
GitHub Create Pull Request
← Previous Page 32 of 65 Next →