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 651-675 of 1604 flagged pages
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-sql-database.md ...blob/main/articles/backup/backup-azure-sql-database.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All examples, instructions, and tooling references are for Windows-based SQL Server VMs, including exclusive use of Windows service accounts (NT SERVICE, NT AUTHORITY), Windows file paths, Windows-only tools (SSMS, Task Manager, PowerShell), and SMB share configuration via PowerShell. There are no Linux equivalents or instructions for SQL Server on Linux VMs, nor any mention of Linux authentication, file permissions, or backup extension installation on Linux.
Recommendations
  • Add explicit instructions and examples for SQL Server running on Linux VMs, including service account setup, permissions, and backup extension installation.
  • Provide Linux shell (bash) equivalents for PowerShell commands, especially for automating permissions and configuring SMB/NFS shares.
  • Include Linux file path examples and clarify differences in folder structure and permissions management.
  • Document how the AzureBackup extension works on Linux, including any differences in plugin/service names, configuration files, and required privileges.
  • Mention Linux authentication methods (e.g., local users, sudo) and how to grant SQL sysadmin permissions on Linux.
  • Ensure parity in troubleshooting steps and error messages for Linux environments.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is exclusively focused on Windows Server system state restore, using Windows-specific tools (MARS agent, Windows Server Backup, wbadmin, Win RE) and workflows. No Linux equivalents, examples, or alternative approaches are mentioned. All instructions, screenshots, and command-line examples are for Windows environments only.
Recommendations
  • Add a section or cross-reference for restoring system state or equivalent on Linux servers using Azure Backup, if supported.
  • Provide parity by including Linux-specific tools (e.g., rsync, tar, Timeshift, etc.) and workflows for system recovery, or clarify if such functionality is not available.
  • If Azure Backup supports Linux server recovery, include step-by-step instructions and screenshots for Linux environments.
  • Explicitly state the Windows-only scope in the introduction if Linux is not supported, to set expectations for cross-platform users.
  • Where possible, mention alternative backup/restore strategies for Linux servers in Azure, or link to relevant documentation.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation exclusively describes backup and recovery of SQL Server databases using Microsoft Azure Backup Server (MABS) and Data Protection Manager (DPM), both of which are Windows-only tools. All examples, screenshots, and instructions assume a Windows environment, referencing Windows-specific features (such as NTAuthority\System, Windows Azure Blob storage, and Windows Failover Clusters). There are no mentions of Linux-based SQL Server deployments, nor are there instructions or examples for Linux environments.
Recommendations
  • Explicitly state in the prerequisites that MABS and DPM are Windows-only, and clarify support for Linux-based SQL Server deployments.
  • Provide guidance or links for backing up SQL Server running on Linux, such as using Azure Backup for Linux VMs or native SQL Server backup tools.
  • Include examples or alternative workflows for Linux environments, if supported, or direct users to appropriate Azure Backup documentation for Linux.
  • Mention Linux equivalents (such as system accounts, file permissions, and backup/restore commands) where relevant.
  • Ensure parity in documentation by offering platform-agnostic advice or clearly delineating Windows-specific instructions.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-sql-restore-cli.md ...b/main/articles/backup/backup-azure-sql-restore-cli.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 SQL Server (a Windows-centric database), using Windows-style VM and SQL instance naming conventions, and omitting any examples or guidance for Linux-based SQL deployments. All examples assume the use of SQL Server on Azure VMs, which are typically Windows-based, and there is no mention of Linux SQL Server or other database engines. Additionally, the documentation does not address differences in file paths, permissions, or restore procedures that may apply to Linux VMs.
Recommendations
  • Explicitly state whether the instructions apply to both Windows and Linux Azure VMs running SQL Server.
  • Add examples and guidance for restoring SQL Server databases on Linux-based Azure VMs, including differences in file paths, permissions, and service management.
  • Clarify any prerequisites or limitations for Linux SQL Server support in Azure Backup.
  • If only Windows is supported, make this clear at the beginning of the documentation.
  • Include troubleshooting tips or links for Linux-specific restore scenarios.
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-09 00:34
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 such as PowerShell, Server Manager, and Windows Server Backup. There are no references to Linux systems, Linux backup tools, or cross-platform alternatives. The prerequisites, error messages, and resolutions are all tailored to Windows, with no mention of Linux equivalents or guidance for non-Windows users.
Recommendations
  • Clearly state at the beginning that System State Backup is only supported on Windows, and provide links to equivalent Linux backup documentation for parity.
  • Where possible, mention Linux backup solutions (e.g., rsync, tar, Timeshift, etc.) and how similar troubleshooting steps would apply.
  • If Azure Backup supports Linux in other scenarios, provide cross-references and troubleshooting links for those platforms.
  • Include a section comparing Windows and Linux backup approaches, highlighting differences and similarities.
  • Avoid using only PowerShell examples; if relevant, provide Bash or shell command equivalents, or clarify that PowerShell is Windows-only.
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-09 00:34
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., Server Manager, Disk Management, ISCSI initiator Properties) are described in detail with screenshots and step-by-step instructions, while Linux troubleshooting is often referenced via links to other documentation or given minimal detail. Windows solutions are frequently presented before Linux equivalents, and some error scenarios (such as deduplication) are only discussed for Windows. There are also more examples and screenshots for Windows, while Linux instructions are less comprehensive.
Recommendations
  • Provide equally detailed, step-by-step instructions for Linux scenarios, including screenshots of relevant tools (e.g., GNOME Disks, lsblk output, mount commands).
  • Include Linux-specific troubleshooting for issues like deduplication, disk mounting, and iSCSI session management.
  • Present Windows and Linux solutions in parallel, rather than Windows-first, to ensure parity.
  • Expand Linux examples beyond referencing external links; include direct commands and expected outputs.
  • Mention Linux tools (e.g., parted, fdisk, mdadm, iscsiadm) where appropriate, alongside Windows tools.
  • Ensure error messages and troubleshooting steps are covered for both platforms, not just Windows.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-troubleshoot-slow-backup-performance-issue.md ...ackup-azure-troubleshoot-slow-backup-performance-issue.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 examples, troubleshooting steps, and tools referenced (such as Performance Monitor, MARS agent, and log file paths) are specific to Windows. There are no Linux equivalents, examples, or troubleshooting guidance provided, and the language assumes the user is operating in a Windows environment.
Recommendations
  • Add explicit guidance for Linux environments, including supported backup agents and their troubleshooting steps.
  • Include Linux-specific performance monitoring tools (e.g., top, iostat, vmstat, sar) and provide example commands for diagnosing bottlenecks.
  • Document log file locations and formats for Linux agents, if supported.
  • Clarify in the prerequisites and throughout the article whether the guidance applies only to Windows, or provide parallel instructions for Linux where possible.
  • If Azure Backup for files/folders is not supported on Linux, state this clearly at the beginning of the article.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-troubleshoot-vm-backup-fails-snapshot-timeout.md ...up-azure-troubleshoot-vm-backup-fails-snapshot-timeout.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: troubleshooting steps and examples often mention Windows tools (services.msc, Event Viewer, Control Panel, .NET, Visual C++ Redistributable) before or instead of Linux equivalents. PowerShell is referenced for operations like setting static IPs and cancelling backup jobs, while Linux CLI alternatives are not provided. Windows-specific troubleshooting is more detailed, with screenshots and step-by-step instructions, whereas Linux guidance is more generic and lacks equivalent visual aids. Some error resolutions and best practices are described only for Windows environments, with Linux steps either summarized or omitted.
Recommendations
  • Provide Linux-specific examples and commands alongside Windows instructions for all troubleshooting steps (e.g., systemctl, journalctl, Linux file paths for logs, package managers for agent installation).
  • Include Linux CLI alternatives for PowerShell commands, such as using Azure CLI or shell scripts for backup job management and network configuration.
  • Add screenshots or terminal output examples for Linux troubleshooting steps, similar to those provided for Windows.
  • Mention Linux tools (e.g., systemd, syslog, package managers) explicitly and ensure parity in diagnostic and resolution guidance.
  • Ensure that error codes and solutions are equally detailed for both Windows and Linux, avoiding generic references for Linux while providing specifics for Windows.
  • Where Windows-specific software (like .NET or Visual C++ Redistributable) is referenced, clarify Linux equivalents or note when such steps are not applicable.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vm-migrate-enhanced-policy.md ...cles/backup/backup-azure-vm-migrate-enhanced-policy.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 PowerShell and CLI versions for migration support, mentioning PowerShell before CLI, and omitting explicit Linux shell examples. The only command-line reference is to Azure CLI and PowerShell, with no bash or Linux-specific instructions. The portal instructions and screenshots are platform-neutral, but command-line guidance is Windows-centric.
Recommendations
  • Provide explicit bash/Linux shell examples for CLI commands, including syntax for common Linux environments.
  • Mention Linux support and any platform-specific considerations for CLI usage (e.g., az CLI on Linux/macOS).
  • List CLI instructions before or alongside PowerShell instructions to avoid Windows-first ordering.
  • Clarify that all steps and tools are cross-platform where applicable, and note any differences in behavior or prerequisites on Linux.
  • Add troubleshooting notes or links for Linux users if there are known issues or differences.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-introduction.md .../main/articles/backup/backup-azure-vms-introduction.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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-first bias in several areas. Windows tools and patterns (such as VSS and PowerShell) are mentioned before their Linux equivalents, and detailed instructions or examples are provided for Windows (e.g., VSS integration, PowerShell restore), while Linux guidance is more generic (e.g., 'write your own scripts'). There are no concrete Linux command examples or detailed walkthroughs, and PowerShell is referenced as the automation tool for restores without mention of Linux CLI alternatives.
Recommendations
  • Provide Linux CLI (az CLI, Bash) examples alongside PowerShell for backup and restore operations.
  • Offer detailed, step-by-step Linux examples for configuring app-consistent backups, including sample pre/post scripts.
  • Mention Linux tools (such as fsfreeze) with the same level of detail as Windows tools (like VSS), and provide usage examples.
  • Ensure that Linux-specific considerations and best practices are as detailed as those for Windows.
  • When referencing automation or scripting, include both PowerShell and Bash/CLI options, and avoid assuming PowerShell as the default.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-extended-zones.md ...ain/articles/backup/backup-azure-vms-extended-zones.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 primarily in the 'Install the VM agent' section, where Windows instructions are presented first, with explicit download links and detailed verification steps. The Linux instructions are less detailed, lack specific commands or examples, and refer users to external repositories without step-by-step guidance. Additionally, Windows file paths and tools (MSI installer, WaAppAgent.exe) are mentioned explicitly, while Linux equivalents are not. No PowerShell or CLI examples are present, but the overall pattern favors Windows in ordering and detail.
Recommendations
  • Provide Linux installation instructions with explicit commands (e.g., apt, yum, zypper) for installing/updating the Azure Linux agent.
  • Include verification steps for Linux agent installation, such as checking the agent version via command line (e.g., waagent --version).
  • Present Windows and Linux instructions in parallel, or alternate which OS is presented first in each section.
  • Add screenshots or terminal output examples for Linux where appropriate, similar to Windows.
  • Reference both Windows and Linux agent documentation equally, and provide direct links to endorsed Linux distributions and their package repositories.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-troubleshoot.md .../main/articles/backup/backup-azure-vms-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 troubleshooting steps, tools, and registry edits are described in detail and often appear before or instead of Linux equivalents. Many error resolutions reference Windows-specific tools (Event Viewer, Services.msc, regedit.exe, command prompt commands like net start/stop, icacls, msdtc, vssadmin, MSIEXEC, etc.), and PowerShell is frequently mentioned for automation and VM creation. Linux troubleshooting is present but less detailed, and some errors only provide Windows solutions or examples. Linux-specific instructions are sometimes included but are less comprehensive and often appear after Windows steps.
Recommendations
  • Ensure every troubleshooting step that references a Windows tool (e.g., Event Viewer, Services.msc, regedit.exe, command prompt) has a Linux equivalent (e.g., syslog/journalctl, systemctl/service, editing config files, bash commands) with equal detail.
  • Provide Linux shell script examples and CLI commands alongside PowerShell examples for automation and VM creation.
  • Where registry edits are suggested for Windows, offer guidance for equivalent configuration changes on Linux (if applicable), or explicitly state when an issue is Windows-only.
  • Balance the order of presentation so Linux and Windows instructions are given equal prominence and detail, ideally in parallel sections.
  • Expand Linux troubleshooting for common errors (e.g., VSS equivalents, disk mounting, agent installation/validation, antivirus exclusions) to match the depth of Windows coverage.
  • Add more Linux screenshots, log file locations, and error message examples to match the Windows visuals and context.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-center-overview.md ...cs/blob/main/articles/backup/backup-center-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page references PowerShell scripts and Microsoft Database Backup scripts as sample resources for automated deployments, but does not mention or provide equivalent Linux shell (bash) scripts or Linux-native backup tools. The examples and tooling referenced are Windows-centric, and there is no explicit mention of Linux command-line usage or parity in automation examples.
Recommendations
  • Include sample bash scripts and Linux CLI commands alongside PowerShell scripts in the Community Hub resources.
  • Explicitly mention Linux-compatible backup automation options and provide examples using Azure CLI on Linux.
  • Reference Linux-native backup tools or patterns where relevant, ensuring parity with Windows tooling.
  • Add documentation sections or examples that demonstrate backup management from Linux environments, not just Windows/PowerShell.
  • Ensure that all automation and scripting guidance is cross-platform, with clear indications of compatibility.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-instant-restore-capability.md ...n/articles/backup/backup-instant-restore-capability.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides configuration instructions for Azure Instant Restore using the Azure portal and PowerShell, but does not mention or provide examples for Linux-based CLI tools such as Azure CLI or Bash scripting. PowerShell is featured as the only command-line example, which may disadvantage Linux users or those who prefer cross-platform tools. There is no mention of Linux-specific patterns, nor are Linux equivalents presented alongside or before Windows-centric tools.
Recommendations
  • Add Azure CLI examples for configuring snapshot retention and other Instant Restore operations, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash script snippets or instructions where relevant, especially for automation scenarios.
  • Explicitly mention that PowerShell examples are applicable on Linux (via PowerShell Core), or clarify platform compatibility.
  • Ensure that documentation sections presenting command-line instructions offer both PowerShell and Azure CLI options, ideally presenting Azure CLI first or side-by-side.
  • Review other areas for Windows-centric terminology or assumptions, and add clarifications or alternatives for Linux environments.
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-09 00:34
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 operations using Microsoft Azure Backup Server, which is a Windows-based tool. All instructions reference GUI steps in the Azure Backup Server console, with no mention of Linux-based backup tools, CLI commands, or PowerShell alternatives. There are no examples or guidance for Linux VMs, nor any mention of Linux-native backup patterns or integration. The documentation assumes a Windows-centric environment and does not address Linux parity.
Recommendations
  • Include examples for backing up and recovering files from Linux VMs in Azure Stack, using Linux-native tools and methods.
  • Provide CLI-based instructions (e.g., Bash, Azure CLI) for backup and recovery operations, in addition to GUI steps.
  • Mention or link to Linux-compatible backup solutions that can be used with Azure Stack, if Azure Backup Server is not available for Linux.
  • Clearly state platform limitations and provide guidance for mixed Windows/Linux environments.
  • Add troubleshooting or integration notes for Linux workloads, such as handling file permissions, recovery, and scheduling backups.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-during-vm-creation.md ...blob/main/articles/backup/backup-during-vm-creation.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias in several ways: Windows is mentioned before Linux when referencing setup instructions, the Resource Manager template example is only provided for Windows VMs, and PowerShell is referenced as the automation tool for configuring Azure Backup resource groups without mention of Linux CLI alternatives. There are no explicit Linux-focused examples or templates, and Linux automation options are not discussed.
Recommendations
  • Provide equal prominence to Linux by listing Linux instructions before or alongside Windows instructions.
  • Include Resource Manager template examples for deploying and protecting Linux VMs, not just Windows VMs.
  • Add automation instructions using Azure CLI or Bash scripts for Linux users, in addition to PowerShell.
  • Ensure screenshots and examples reflect both Windows and Linux VM scenarios.
  • Explicitly mention Linux support and link to Linux-specific documentation where relevant.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-encryption.md ...re-docs/blob/main/articles/backup/backup-encryption.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page on Azure Backup encryption demonstrates a Windows bias in several ways. Windows-specific technologies (BitLocker, TDE for SQL Server) are mentioned before their Linux equivalents (DM-Crypt), and examples or instructions are focused on Windows tools and patterns. There is no explicit Linux example or parity in instructions, and the documentation assumes familiarity with Windows-centric encryption methods.
Recommendations
  • Provide explicit Linux examples and instructions, such as how to configure DM-Crypt for Azure VM backups.
  • Mention Linux tools and patterns alongside Windows ones, giving equal prominence (e.g., DM-Crypt before or alongside BitLocker).
  • Include references to Linux-specific documentation for disk encryption and backup scenarios.
  • Ensure that any code samples or walkthroughs are available for both Windows (PowerShell) and Linux (Bash/CLI).
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-add-storage.md ...s/blob/main/articles/backup/backup-mabs-add-storage.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows-centric, with all instructions, screenshots, and tooling focused exclusively on Windows Server environments. There are no Linux equivalents or examples, and Windows-specific tools (Server Manager, PowerShell cmdlets, ReFS filesystem) are used throughout. The prerequisites and workflows assume Windows, with no mention of Linux support or alternatives.
Recommendations
  • Clarify in the introduction whether Azure Backup Server supports Linux hosts, and if not, explicitly state the limitation.
  • If Linux support exists or is planned, provide parallel instructions and examples for Linux environments, including relevant commands and tools (e.g., using LVM, ext4/xfs, Linux CLI commands).
  • Mention Linux-compatible filesystems and storage management options if applicable.
  • If PowerShell is required, suggest Linux alternatives (such as Bash scripts or Azure CLI commands) where possible.
  • Add a comparison table or section outlining feature parity and differences between Windows and Linux deployments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-install-azure-stack.md ...ain/articles/backup/backup-mabs-install-azure-stack.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 toward Windows environments. All instructions, prerequisites, and examples assume the use of Windows Server (specifically Windows Server 2022/2019 Datacenter) and Windows-based tooling. There are no references to Linux-based Azure Stack Hub VMs, nor any guidance for installing or running Azure Backup Server on Linux. The only command-line example provided is a PowerShell cmdlet, and all file paths, installer instructions, and screenshots are Windows-centric. No Linux equivalents, alternatives, or parity guidance are offered.
Recommendations
  • Explicitly state whether Azure Backup Server supports Linux-based Azure Stack Hub VMs. If not, clarify this limitation early in the documentation.
  • If Linux support exists or is planned, provide equivalent installation instructions for Linux environments, including prerequisites, download, extraction, and configuration steps.
  • Include Linux command-line examples (e.g., Bash, CLI) alongside PowerShell, or provide cross-platform Azure CLI instructions where possible.
  • Reference Linux tools and patterns (e.g., systemd, package managers, Linux file paths) where relevant.
  • Add troubleshooting steps and network connectivity validation methods for Linux environments.
  • Ensure parity in screenshots and UI guidance for Linux-based Azure Stack Hub management portals, if available.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-sql-azure-stack.md ...ob/main/articles/backup/backup-mabs-sql-azure-stack.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, specifically referencing Microsoft Azure Backup Server (MABS), which is a Windows-only tool. All instructions, screenshots, and terminology are based on Windows UI paradigms (e.g., blades, workspaces, right-click context menus) and SQL Server running on Windows. There are no examples, instructions, or mentions of Linux-based SQL Server deployments, nor any Linux-native backup tools or command-line workflows.
Recommendations
  • Add explicit statements about Linux support or limitations, clarifying whether MABS can protect SQL Server running on Linux (currently, it cannot).
  • Provide alternative guidance for backing up SQL Server on Linux, such as using Azure Backup with Recovery Services Vault, or native SQL Server backup/restore commands with Azure Blob Storage.
  • Include Linux-specific examples or workflows, such as command-line instructions for scheduling backups, restoring databases, or integrating with Azure services.
  • Mention cross-platform backup tools or approaches where applicable, and provide parity in documentation structure and detail.
  • If MABS is Windows-only, link to Linux backup documentation in the prerequisites or supported scenarios section.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-whats-new-mabs.md ...lob/main/articles/backup/backup-mabs-whats-new-mabs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation for Microsoft Azure Backup Server (MABS) is heavily Windows-centric. All examples, supported platforms, and operational instructions focus on Windows Server, SQL Server (Windows), and Windows-specific technologies (e.g., registry keys, PowerShell cmdlets, ReFS, Hyper-V). There is no mention of Linux support, Linux-based workloads, or equivalent Linux tools. Windows terminology and tools (registry, PowerShell, Windows authentication) are used exclusively and appear first in all feature tables and descriptions.
Recommendations
  • Explicitly state whether Linux workloads are supported or not. If supported, add Linux-specific instructions and examples.
  • Include parity examples for Linux environments, such as backup/restore of Linux VMs, files, and workloads.
  • Mention Linux-compatible backup agents or integration options, if available.
  • Provide equivalent Linux command-line instructions (e.g., shell commands) alongside PowerShell examples.
  • Reference Linux file systems and backup scenarios (e.g., ext4, xfs) where applicable.
  • Clarify limitations or roadmap for Linux support in MABS, if Linux is not currently supported.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-protection-matrix.md .../main/articles/backup/backup-mabs-protection-matrix.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation for MABS v4 protection matrix demonstrates a strong Windows bias. Windows workloads, tools, and recovery scenarios are described in detail and presented first, with Linux support relegated to a single, limited section. Examples and instructions are almost exclusively Windows-centric, referencing Windows-specific technologies (NTFS, VSS, Visual C++, Windows Management Framework, Control Panel, etc.) and omitting Linux equivalents or guidance. Linux protection is only supported as a guest VM running on Windows Server Hyper-V/VMware, with no mention of direct Linux server backup or recovery details. There are no Linux command-line or tool references, and recovery options for Linux are minimal compared to Windows.
Recommendations
  • Add explicit Linux backup and recovery examples, including supported file systems, distributions, and recovery scenarios.
  • Include Linux command-line instructions (e.g., shell commands) and references to Linux-native tools where appropriate.
  • Clarify whether direct backup of Linux physical servers is supported, and if not, state limitations and alternatives.
  • Present Linux support details alongside Windows in all relevant tables, rather than in a separate, minimized section.
  • Discuss Linux-specific requirements, such as agent installation, supported authentication methods, and file system compatibility.
  • Provide parity in documentation for Linux recovery options, including item-level recovery and snapshot consistency details.
  • Avoid Windows-centric terminology (e.g., Control Panel, NTFS, VSS) without Linux equivalents or explanations.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily focuses on using the Azure portal for backup operations and mentions scripting options only in passing. When automation is discussed, PowerShell is listed before CLI, and there are no explicit Linux-specific examples or references to Linux tools or shell scripting. The CLI is mentioned, but not demonstrated, and PowerShell is given prominence in links and script references. There are no screenshots or step-by-step instructions for Linux users, nor is there guidance for Linux-specific scenarios or environments.
Recommendations
  • Provide explicit Azure CLI examples alongside PowerShell, with equal prominence and detail.
  • Include screenshots or terminal output for CLI commands, demonstrating usage on Linux systems.
  • Mention Linux shell scripting as an automation option, and provide sample Bash scripts where appropriate.
  • Ensure that references to scripting (PowerShell/CLI) always list CLI first or equally, and clarify cross-platform compatibility.
  • Add a section or note addressing Linux users, including any platform-specific considerations or tips.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by explicitly mentioning Windows-specific backup tools (Azure Backup agent client UI, System Center Data Protection Manager UI, Azure Backup Server UI) and by listing Windows Server registration operations in the main backup management table. There is no mention of Linux backup agents or Linux-specific backup scenarios, nor are Linux equivalents for on-premises backup registration discussed. The 'Next steps' section lists PowerShell before Azure CLI, which may suggest a Windows-first approach. There are no Linux shell or Linux agent examples, and the documentation does not address Linux on-premises backup registration or management.
Recommendations
  • Add information and examples for Linux on-premises backup scenarios, including how to register and manage Linux servers with Recovery Services vault.
  • Mention Linux backup agents or supported Linux tools alongside Windows tools in all relevant sections.
  • Include Linux shell (bash) examples for role assignment and backup management operations, not just PowerShell.
  • In the 'Next steps' section, alternate the order of PowerShell and Azure CLI, or present them together to avoid Windows-first perception.
  • Clarify whether Linux on-premises backup is supported and provide guidance or links if so.
  • Review all tables and ensure Linux equivalents for Windows-specific operations are included or explicitly state platform limitations.
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-09 00:34
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 displays a moderate Windows bias. Several features and examples reference Windows-specific tools (such as MARS agent and Microsoft Azure Backup Server), and PowerShell is often mentioned as a primary management interface. Windows workloads (SQL Server, MARS agent, MABS) are described in more detail and appear earlier or more frequently than Linux equivalents. Linux support (e.g., SAP HANA on RHEL) is mentioned but less prominently and with fewer details/examples.
Recommendations
  • Ensure parity in examples and instructions for both Windows and Linux environments, especially for agent-based backup solutions and server support.
  • Include CLI and Bash examples alongside PowerShell for all relevant operations.
  • Highlight Linux support (such as SAP HANA on RHEL, PostgreSQL) with equal detail and visibility as Windows workloads.
  • Explicitly mention supported Linux distributions and provide links to Linux-specific documentation where applicable.
  • When referencing tools like MARS or MABS, clarify their platform support and provide alternatives or equivalents for Linux users.
  • Avoid listing Windows tools/features before Linux equivalents unless there is a technical reason; strive for balanced presentation.
GitHub Create Pull Request
← Previous Page 27 of 65 Next →