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 476-500 of 1604 flagged pages
Backup Back up a SharePoint farm to Azure with MABS ...articles/backup/backup-azure-backup-sharepoint-mabs.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, with all examples, tools, and procedures referencing Windows-specific components such as CMD commands, Registry Editor, Windows file paths, and Windows services. The use of tools like ConfigureSharePoint.exe, references to NT AUTHORITY\SYSTEM, and reliance on Windows Registry and Windows groups (e.g., WSS_Admin_WPG) further reinforce this bias. There are no Linux equivalents or cross-platform instructions provided, nor is there any mention of Linux support or alternative workflows.
Recommendations
  • Clearly state platform requirements and limitations at the beginning of the document, including whether Linux is supported or not.
  • If Linux support is possible, provide equivalent instructions, examples, and tooling for Linux environments (e.g., shell commands, Linux file paths, service management).
  • Include a section that addresses cross-platform considerations and explicitly mentions any unsupported platforms.
  • Where possible, use platform-agnostic terminology and avoid assuming Windows-only environments.
  • If MABS is Windows-only, provide links or references to alternative Azure backup solutions for SharePoint on Linux (if available), or clarify that Linux is not supported.
GitHub Create Pull Request
Backup Back up SQL Server to Azure as a DPM workload ...s/blob/main/articles/backup/backup-azure-backup-sql.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. It exclusively references Data Protection Manager (DPM), a Windows-only backup solution, and all examples, screenshots, and instructions are tailored to Windows environments (e.g., NTAuthority\System, Logical Disk Manager, DPM console). There are no Linux equivalents or cross-platform instructions, nor is there mention of Linux backup agents or tools. The only automation reference is to PowerShell, further reinforcing the Windows-centric approach.
Recommendations
  • Include equivalent instructions and examples for Linux environments, such as using Azure Backup for SQL Server running on Linux VMs.
  • Mention and provide guidance for cross-platform backup tools (e.g., Azure Backup agent for Linux, or native SQL Server backup to Azure Blob from Linux).
  • Add automation examples using Bash or CLI commands, not just PowerShell.
  • Clarify in the prerequisites and introduction that the guide is specific to Windows/DPM, and link to Linux-specific backup documentation if available.
  • Provide parity in screenshots and workflow descriptions for Linux users, or explicitly state limitations.
GitHub Create Pull Request
Backup Create Backup Policies for PostgreSQL Databases by Using the Data Protection REST API ...rotection-use-rest-api-create-update-postgresql-policy.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through repeated references to PowerShell objects and patterns as the default or primary method for policy definition and explanation. There are no examples or mentions of Linux-native tools, shell commands (such as curl), or cross-platform CLI usage for interacting with the REST API. The documentation assumes familiarity with PowerShell constructs and does not provide parity for Linux users, who are likely to use Bash, curl, or other command-line utilities.
Recommendations
  • Provide equivalent Linux/Bash examples for REST API calls, such as using curl or httpie to create and manage backup policies.
  • Avoid referencing PowerShell objects as the 'default' or primary method; instead, use neutral, platform-agnostic JSON or REST API payloads.
  • Include cross-platform CLI instructions (e.g., Azure CLI) where possible, and clarify that the REST API can be used from any OS.
  • Add a section explicitly addressing Linux and macOS users, with sample commands and workflow guidance.
  • Review terminology to ensure that Windows-specific tools or patterns are not presented as the only or preferred option.
GitHub Create Pull Request
Backup Overview of Azure Database for PostgreSQL Backup ...es/backup/backup-azure-database-postgresql-overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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. The only client tool mentioned for interacting with PostgreSQL is pgAdmin, which is primarily a GUI tool popular on Windows. There are no examples or instructions for using Linux-native tools (such as psql from the command line), nor are there references to Linux workflows or shell commands. The screenshots and step-by-step instructions focus on GUI interactions, which are more common in Windows environments. No PowerShell-specific examples are present, but the absence of Linux CLI examples and the reliance on GUI tools suggest a Windows-first approach.
Recommendations
  • Add examples for connecting to Azure Database for PostgreSQL using the psql command-line tool, including installation instructions for Linux and macOS.
  • Provide sample backup and restore commands using psql or bash scripts to demonstrate Linux-native workflows.
  • Include screenshots or instructions for configuring firewall rules and permissions using Azure CLI or REST API, which are cross-platform.
  • Mention alternative PostgreSQL client tools available on Linux (e.g., DBeaver, CLI tools) and provide parity in instructions.
  • Ensure that any references to GUI tools are balanced with equivalent command-line instructions for Linux users.
GitHub Create Pull Request
Backup Prepare the DPM server to back up workloads .../main/articles/backup/backup-azure-dpm-introduction.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows environments, specifically System Center DPM, which is a Windows-only product. All instructions, prerequisites, and tooling references (such as PowerShell, .NET Framework, and MARSAgentInstaller.exe) are Windows-specific. There are no Linux equivalents or examples provided, and Windows tools and patterns are mentioned exclusively and first throughout the page.
Recommendations
  • Clarify early in the documentation that DPM is a Windows-only solution and suggest alternatives for Linux workloads (e.g., Azure Backup for Linux VMs, MARS agent for Linux, or other Azure-native backup solutions).
  • Provide links or references to Azure Backup documentation for Linux systems, including step-by-step guides for Linux VM backup and recovery.
  • Where PowerShell or Windows tools are mentioned, add notes or sections describing equivalent Linux commands or processes if available, or explicitly state that these steps are not applicable to Linux.
  • Add a comparison table or section outlining backup options for both Windows and Linux workloads in Azure, helping users choose the right solution for their environment.
GitHub Create Pull Request
Backup Back Up Azure Database for PostgreSQL by Using the Azure Portal ...in/articles/backup/backup-azure-database-postgresql.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several areas: environment variable configuration is described exclusively using Windows Control Panel screenshots and instructions, PowerShell is presented as the primary scripting method for privilege assignment, and there are no explicit Linux shell or cross-platform examples for key steps. Linux equivalents (e.g., bash, export, .bashrc, or Linux environment variable management) are not mentioned, and the order of presentation favors Windows tools and workflows.
Recommendations
  • Add explicit Linux instructions and screenshots for environment variable configuration (e.g., using export, .bashrc, or .profile).
  • Provide bash or shell script equivalents for privilege assignment, alongside PowerShell scripts.
  • Include cross-platform guidance for running the PSQL tool, such as installation and usage on Linux/macOS.
  • Ensure that CLI examples (Azure CLI) are given equal prominence and detail as PowerShell examples.
  • Clearly indicate which steps are platform-specific and offer alternatives for both Windows and Linux users.
GitHub Create Pull Request
Backup Back up Azure Disks using Azure Data Protection REST API. ...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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through its references and links. Permission assignment is linked to a PowerShell-based guide (backup-managed-disks-ps.md), with no mention of Linux or Bash equivalents. In the 'Next steps' section, the order of restore options lists Azure PowerShell before Azure CLI, which is more commonly used on Linux. There are no explicit Linux/Bash command examples or references to Linux tools for managing permissions or backup operations, and no guidance for Linux users on how to perform these tasks.
Recommendations
  • Provide explicit Azure CLI and Bash examples for all operations, especially for permission assignment and backup configuration.
  • Add links to Linux-focused documentation (e.g., backup-managed-disks-cli.md) alongside or before PowerShell references.
  • Ensure that CLI examples are presented before or alongside PowerShell examples to avoid Windows-first ordering.
  • Include notes or sections addressing Linux-specific considerations, such as environment setup or authentication differences.
  • Review all referenced guides and ensure Linux parity in instructions and examples.
GitHub Create Pull Request
Backup Delete a Microsoft Azure Recovery Services vault ...blob/main/articles/backup/backup-azure-delete-vault.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. PowerShell is heavily featured as the primary automation and scripting method, with detailed examples and instructions. Windows-specific backup tools (MARS, MABS, DPM) are referenced throughout, and management consoles described are Windows-only. The ARMClient installation instructions rely on Chocolatey, a Windows package manager, with no mention of Linux alternatives. CLI coverage is minimal and limited to Azure VM backups, with no Linux shell or cross-platform scripting examples. There are no Bash, Linux, or macOS-specific instructions or parity for on-premises scenarios.
Recommendations
  • Add Bash and Azure CLI examples for all major operations, including vault deletion and backup item removal, not just for VM backups.
  • Document Linux/macOS-compatible methods for ARMClient installation and usage, or suggest REST API calls via curl or other cross-platform tools.
  • Reference cross-platform backup agents or clarify Windows-only limitations for MARS, MABS, and DPM.
  • Provide parity in automation examples, such as Python or Bash scripts for vault and backup management.
  • Explicitly state platform limitations where applicable, and link to Linux-specific documentation if available.
  • Ensure screenshots and UI instructions are not exclusively Windows-centric, or provide Linux alternatives where possible.
GitHub Create Pull Request
Backup Back up Exchange server with Azure Backup Server ...lob/main/articles/backup/backup-azure-exchange-mabs.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively describes backup and recovery procedures for Microsoft Exchange using Azure Backup Server (MABS), which is a Windows-only tool. All instructions, screenshots, and file paths (e.g., C:\Program Files\...) are Windows-specific, with no mention of Linux equivalents, Linux Exchange deployments, or cross-platform considerations. The use of Windows-centric terminology and tools (MABS, eseutil, .exe files) further reinforces the Windows bias.
Recommendations
  • Explicitly state that MABS is a Windows-only solution, and clarify platform requirements early in the documentation.
  • Provide guidance or references for backing up Exchange servers running on Linux (if supported), or alternative backup solutions for Linux-based mail servers.
  • Include parity documentation for Linux environments, such as examples using Azure Backup with Linux servers, or mention relevant Linux backup tools and patterns.
  • If Exchange on Linux is not supported, add a note explaining this limitation and suggest alternative approaches for Linux-based email systems.
GitHub Create Pull Request
Backup Troubleshoot Azure Backup Server ...main/articles/backup/backup-azure-mabs-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation for troubleshooting Azure Backup Server is heavily Windows-centric. All examples, paths, and troubleshooting steps reference Windows tools, registry keys, Windows services, and Windows-specific folders. There are no examples or guidance for Linux systems, nor any mention of Linux equivalents for commands, services, or file paths. Windows terminology and tools (such as registry edits, Windows Server Backup, Volume Shadow Copy Service, and Internet Explorer) are used exclusively and are presented as the default or only option.
Recommendations
  • Add troubleshooting steps and examples for Linux-based Azure Backup Server deployments, if supported.
  • Include Linux equivalents for file paths, service management (e.g., systemctl), and configuration locations.
  • Provide examples using Linux command-line tools (e.g., bash, grep, systemctl) alongside Windows CMD/PowerShell.
  • Reference Linux antivirus configuration and exclusion patterns where relevant.
  • Clarify platform support at the top of the documentation, and explicitly state if the product or troubleshooting steps are Windows-only.
  • If Azure Backup Server is not supported on Linux, make this clear to avoid confusion for cross-platform administrators.
GitHub Create Pull Request
Backup Manage and monitor MARS Agent backups .../blob/main/articles/backup/backup-azure-manage-mars.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on the Microsoft Azure Recovery Services (MARS) Agent, which is a Windows-only backup solution. All instructions, screenshots, and tool references are for Windows environments, specifically referencing the MARS management console, Windows file paths, and Windows-specific binaries. There are no examples, instructions, or even mentions of Linux or cross-platform equivalents, and all operational steps assume a Windows environment.
Recommendations
  • Clearly state early in the documentation that the MARS Agent is only supported on Windows, and provide links to equivalent Linux backup solutions (such as Azure Backup for Linux VMs or Azure CLI-based backup).
  • Add a comparison table or section outlining backup options for both Windows and Linux, with links to relevant documentation for Linux users.
  • Where possible, include references to cross-platform tools (such as Azure CLI or REST API) for managing backups, and provide example commands for Linux environments if supported.
  • Ensure that any monitoring or reporting instructions (e.g., using Azure Monitor or Backup Reports) include Linux-compatible steps or clarify platform limitations.
  • If MARS Agent is not available for Linux, explicitly direct Linux users to the appropriate Azure backup solutions and documentation.
GitHub Create Pull Request
Backup Troubleshoot the Azure Backup agent ...main/articles/backup/backup-azure-mars-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric, with all troubleshooting steps, examples, and tool references tailored exclusively for Windows environments. There are no Linux equivalents or cross-platform guidance. Windows tools (MMC console, Task Scheduler, Internet Explorer, Device Manager, Registry Editor, vssadmin, PowerShell) are referenced throughout, and all examples (including PowerShell commands and file paths) assume a Windows OS. No mention is made of Linux support, troubleshooting, or alternative commands/tools.
Recommendations
  • Clearly state OS support at the beginning of the document. If MARS agent is Windows-only, make this explicit.
  • If Linux support exists, add equivalent troubleshooting steps, commands, and tool references for Linux environments.
  • Provide parity in examples: for every Windows example (e.g., PowerShell, MMC, Task Scheduler), include a Linux alternative (e.g., Bash scripts, cron jobs, systemd, relevant Linux tools).
  • Reference cross-platform browsers and network troubleshooting methods, not just Internet Explorer.
  • Avoid hardcoding Windows paths and registry keys; provide Linux equivalents or clarify OS-specific instructions.
  • Include troubleshooting steps for Linux-specific issues (permissions, SELinux, system logs, etc.) if applicable.
  • If the agent is Windows-only, consider linking to Linux backup solutions or alternatives for Azure.
GitHub Create Pull Request
Backup Manage and monitor Azure VM backups ...s/blob/main/articles/backup/backup-azure-manage-vms.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias, especially in the section on reinstalling the VMSnapshot backup extension. The Windows instructions are extensive, detailed, and include PowerShell cmdlets, registry edits, and use of Windows-specific tools (services.msc, regedit, command prompt). In contrast, the Linux instructions are minimal, lacking step-by-step guidance, troubleshooting, or parity in detail. Throughout the page, examples and screenshots are either Windows-centric or do not mention Linux alternatives, and Windows procedures are presented before Linux ones.
Recommendations
  • Provide equally detailed, step-by-step instructions for Linux VM extension management, including troubleshooting, verification steps, and relevant commands.
  • Include Linux shell commands for backup management where PowerShell is used for Windows.
  • Add screenshots or terminal output examples for Linux procedures, similar to those provided for Windows.
  • Mention Linux-specific tools and patterns (e.g., systemctl for service management, file system paths) alongside Windows tools.
  • Ensure that both Windows and Linux instructions are presented in parallel or with equal prominence, rather than Windows-first.
  • Clarify any differences in backup behavior or extension management between Windows and Linux VMs.
GitHub Create Pull Request
Backup Use Azure Backup Server to back up workloads ...articles/backup/backup-azure-microsoft-azure-backup.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. All installation, configuration, and operational steps assume Windows Server as the platform, with no mention of Linux support or examples. Only Windows tools and patterns (e.g., .exe installers, registry edits, PowerShell cmdlets) are referenced, and there is no guidance for Linux users or parity in examples. The documentation does not discuss Linux-based workloads or provide alternatives for non-Windows environments.
Recommendations
  • Explicitly state platform limitations and whether Linux is supported or not at the beginning of the documentation.
  • If Azure Backup Server does not support Linux, provide links or references to Azure backup solutions for Linux workloads (e.g., Azure Backup for Linux VMs, Azure Recovery Services for Linux).
  • Where possible, add Linux-specific guidance or alternatives for backup and recovery, especially for mixed environments.
  • Include examples or references for Linux tools and command-line patterns if any part of the workflow can be performed on Linux systems.
  • Clarify whether agents or backup targets can be Linux-based, and if so, provide installation and configuration steps for those scenarios.
GitHub Create Pull Request
Backup How to move Azure Backup Recovery Services vaults ...es/backup/backup-azure-move-recovery-services-vault.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell examples for moving Recovery Services vaults, mentioning Windows update procedures before Linux equivalents, and lacking Linux-specific command-line examples (e.g., Bash scripts). The CLI section is present but minimal, and there are no Linux shell or automation examples. Windows terminology and tools (PowerShell, Windows updates) are referenced first or exclusively in several places.
Recommendations
  • Provide equivalent Bash or shell script examples for moving Recovery Services vaults using Azure CLI, including automation scenarios.
  • Expand the CLI section to include more detailed steps and troubleshooting, similar to the PowerShell section.
  • When discussing prerequisites (e.g., certificates), give equal prominence and detail to Linux update procedures, possibly linking to common Linux distributions’ documentation.
  • Avoid listing Windows steps before Linux steps; present both together or alternate their order.
  • Mention cross-platform tools (e.g., AzCopy, Azure CLI) as primary options, and clarify that PowerShell is available on Linux and macOS as well.
  • Add explicit notes or examples for Linux administrators, such as using cron jobs or shell scripts for backup automation.
GitHub Create Pull Request
Backup Overview of Recovery Services vaults ...ackup/backup-azure-recovery-services-vault-overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Recovery Services vaults demonstrates a Windows bias. Windows-specific tools and workloads (System Center DPM, Windows Server, Azure Backup Server) are mentioned prominently and exclusively in several sections, while Linux equivalents or examples are missing. References to backup scenarios and monitoring focus on Windows-centric assets, with links and examples for Windows Server backup but no parallel Linux instructions. The order of presentation also tends to mention Windows before Linux, and Linux-specific backup scenarios are not detailed.
Recommendations
  • Include explicit examples and links for backing up Linux servers, both on-premises and in Azure VMs.
  • Mention Linux-compatible backup tools or agents where Windows tools (e.g., MARS agent, DPM) are referenced.
  • Provide parity in documentation structure: for every Windows backup scenario or tool, add the Linux equivalent or clarify if not supported.
  • Add Linux-focused monitoring and management instructions alongside Windows-centric ones.
  • Ensure that lists and feature descriptions alternate or balance Windows and Linux references, rather than defaulting to Windows-first.
GitHub Create Pull Request
Backup Private Endpoints Overview: Version 2 Experience ...icles/backup/backup-azure-private-endpoints-concept.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by focusing on Windows-specific backup tools (MARS agent, DPM, MABS) and providing recommendations and examples that are primarily relevant to Windows workloads. There is little to no mention of Linux backup agents, Linux VM scenarios, or Linux-specific configuration steps, and all agent/tool references are Windows-centric. This may leave Linux users without clear guidance for implementing private endpoints with Azure Backup.
Recommendations
  • Include explicit references to Linux VM backup scenarios and clarify how private endpoints apply to Linux workloads.
  • Document Linux-compatible backup agents or extensions, if available, and provide configuration steps/examples for Linux environments.
  • Add examples or notes for DNS configuration, agent installation, and connectivity troubleshooting on Linux systems.
  • Balance recommendations and supported scenarios to include both Windows and Linux workloads, ensuring parity in guidance and examples.
  • If certain features/tools are Windows-only, clearly state this and provide alternative guidance for Linux users.
GitHub Create Pull Request
Backup Troubleshoot System Center Data Protection Manager .../articles/backup/backup-azure-scdpm-troubleshooting.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on troubleshooting System Center Data Protection Manager (DPM), a product that is only available for Windows. All examples, commands, and troubleshooting steps reference Windows-specific tools (such as 'net stop dpmra'), concepts (NT AUTHORITY\SYSTEM, sysadmin role), and agents (MARS, Azure Backup agent) without mention of Linux equivalents or cross-platform considerations. There are no Linux or PowerShell Core examples, and all instructions assume a Windows environment.
Recommendations
  • Explicitly state that DPM is a Windows-only product at the beginning of the documentation to clarify platform scope.
  • If any Azure Backup or Recovery Services Vault features are available for Linux, provide troubleshooting steps and examples for those platforms.
  • Where possible, reference cross-platform alternatives (e.g., Azure Backup for Linux) and link to their documentation.
  • For commands and agent installation, mention if there are Linux equivalents or clarify that the instructions are Windows-specific.
  • Consider adding a section that compares DPM to Azure Backup for Linux, outlining differences and linking to relevant Linux documentation.
GitHub Create Pull Request
Backup Recover files and folders from Azure VM backup .../articles/backup/backup-azure-restore-files-from-vm.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions and tools (such as registry edits, Windows Explorer, and .NET requirements) are presented before Linux equivalents, with more detailed troubleshooting steps for Windows (e.g., registry changes for large disks). PowerShell is referenced in 'Next steps' before Azure CLI, and Windows-specific concepts (drive letters, Storage Spaces) are explained in greater detail. Linux instructions are present but sometimes less detailed, and some advanced Linux scenarios (e.g., LVM/RAID) are covered, but troubleshooting for Linux is less extensive than for Windows.
Recommendations
  • Present Windows and Linux instructions in parallel sections, giving equal prominence to both platforms.
  • Ensure troubleshooting steps for Linux (e.g., large disk issues) are as detailed as those for Windows, including common error messages and solutions.
  • Provide Linux-specific examples for browsing and recovering files (e.g., using Nautilus, Midnight Commander, or command-line tools) similar to Windows Explorer references.
  • List Azure CLI instructions before or alongside PowerShell in 'Next steps' to avoid implying PowerShell is the default.
  • Expand Linux prerequisites and troubleshooting, including more details on required packages, SELinux/AppArmor considerations, and common permission issues.
  • Include screenshots for Linux steps where possible, matching the visual guidance given for Windows.
  • Mention cross-platform tools and patterns (e.g., using Python scripts on Windows via WSL) where relevant.
GitHub Create Pull Request
Backup Restore System State to a Windows Server ...n/articles/backup/backup-azure-restore-system-state.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation exclusively covers restoring System State for Windows Server using Windows-specific tools (MARS agent, Windows Server Backup, wbadmin, Win RE) and provides only Windows-based instructions and screenshots. There are no Linux equivalents, examples, or mentions of restoring system state on Linux servers, nor any cross-platform guidance. The documentation assumes a Windows environment throughout and does not address Linux scenarios.
Recommendations
  • Add a section or separate documentation for restoring system state or equivalent on Linux servers using Azure Backup, if supported.
  • Provide parity in examples by including Linux tools (e.g., rsync, tar, Timeshift, etc.) and command-line instructions for Linux system recovery.
  • Mention limitations or differences in Azure Backup support for Linux vs. Windows, and link to Linux-specific recovery guides if available.
  • If Azure Backup does not support Linux system state restore, explicitly state this in the documentation to clarify scope and avoid confusion.
  • Ensure that cross-platform users are guided to relevant resources for Linux backup and recovery.
GitHub Create Pull Request
Backup Security features that protect hybrid backups .../main/articles/backup/backup-azure-security-feature.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation page is heavily focused on Windows-centric backup tools (MABS, DPM, MARS) and provides examples, troubleshooting, and feature descriptions exclusively for these Windows-based solutions. There is no mention of Linux backup agents, Linux-specific recovery procedures, or parity for Linux workloads. PowerShell commands and Windows UI screenshots are used, with no equivalent CLI or Linux instructions. The documentation implicitly assumes the user is operating in a Windows environment.
Recommendations
  • Add sections describing how security features apply to Linux workloads, if supported, or clarify limitations for Linux users.
  • Provide examples and instructions for Linux backup agents (such as Azure Backup for Linux VMs or Azure CLI usage for Linux).
  • Include Linux-specific troubleshooting steps and error codes where relevant.
  • Offer parity in screenshots and step-by-step guides for Linux environments, such as using the Azure CLI or REST API.
  • Clearly state at the beginning which platforms are supported and highlight any gaps in Linux support for these security features.
GitHub Create Pull Request
Backup Back up SQL Server databases to Azure ...blob/main/articles/backup/backup-azure-sql-database.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily Windows-centric, with all examples, instructions, and tooling focused on Windows environments. It exclusively references Windows-specific accounts (NT SERVICE, NT AUTHORITY), Windows authentication, Windows file paths, and Windows tools (SSMS, PowerShell, Task Manager, SMB shares). There are no examples or guidance for Linux-based SQL Server VMs, nor are Linux authentication or file system patterns mentioned. PowerShell is the only scripting language provided for automation, and all troubleshooting steps assume a Windows OS.
Recommendations
  • Add explicit instructions and examples for SQL Server running on Linux-based Azure VMs, including differences in service accounts, authentication, and file system paths.
  • Provide Linux equivalents for automation (e.g., Bash scripts, sqlcmd usage on Linux, systemctl/service commands for managing services).
  • Include guidance for configuring permissions and local backup folders using Linux file system conventions and tools (e.g., chown, chmod).
  • Mention any differences in extension installation or operation on Linux VMs.
  • Clarify which steps are Windows-only and provide parallel Linux steps where applicable.
  • Offer troubleshooting guidance for common Linux-specific issues.
GitHub Create Pull Request
Backup Back up SQL Server by using Azure Backup Server ...ocs/blob/main/articles/backup/backup-azure-sql-mabs.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on Microsoft Azure Backup Server (MABS) and Data Protection Manager (DPM), which are Windows-only tools. All examples, screenshots, and workflows assume a Windows environment, with references to Windows-specific accounts (NTAuthority\System) and SQL Server features configured via Windows. There is no mention of Linux support, nor are there any examples or guidance for backing up SQL Server on Linux or using Linux-native tools.
Recommendations
  • Clarify in the prerequisites or introduction that MABS/DPM are Windows-only solutions and note any Linux limitations.
  • Provide alternative guidance or links for backing up SQL Server on Linux, such as using Azure Backup for Linux VMs, or native SQL Server backup tools on Linux.
  • Include examples or references for Linux-based SQL Server deployments, if supported, or explicitly state that Linux is not supported.
  • Mention Linux equivalents for concepts like system accounts, file permissions, and backup scheduling.
  • If Azure Backup supports Linux SQL Server, add parity in screenshots, workflows, and step-by-step instructions.
GitHub Create Pull Request
Backup Back up Windows system state to Azure using Azure Backup ...blob/main/articles/backup/backup-azure-system-state.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is exclusively focused on backing up Windows Server system state to Azure using the Microsoft Azure Recovery Services (MARS) Agent. All instructions, screenshots, and tool references are specific to Windows environments. There are no examples, guidance, or mentions of Linux systems, Linux backup tools, or cross-platform alternatives. The documentation assumes the user is operating on Windows and does not address Linux parity.
Recommendations
  • Add a section or a separate article for backing up Linux system state or equivalent (e.g., file system, configuration) to Azure using Azure Backup.
  • Include examples and instructions for Linux environments, such as using Azure Backup Server, Azure CLI, or other supported Linux backup agents.
  • Mention Linux support (or lack thereof) explicitly in the prerequisites or introduction, clarifying platform limitations.
  • If Azure Backup does not support Linux system state backup, provide links or guidance to alternative Azure solutions for Linux backup.
  • Ensure parity in screenshots and step-by-step guides for both Windows and Linux where applicable.
GitHub Create Pull Request
Backup Troubleshoot slow backup of files and folders ...ackup-azure-troubleshoot-slow-backup-performance-issue.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. All troubleshooting steps, examples, and tool recommendations are specific to Windows environments. The only performance monitoring tool mentioned is Windows Performance Monitor (Perfmon), and all file paths, agent references, and log locations are Windows-specific. There are no Linux equivalents, examples, or guidance for users running Azure Backup on Linux systems.
Recommendations
  • Add troubleshooting steps and examples for Linux environments, including common distributions supported by Azure Backup.
  • Mention and provide guidance for Linux performance monitoring tools such as 'top', 'htop', 'iotop', 'vmstat', and 'sar', alongside Windows Perfmon.
  • Include Linux-specific agent installation, log file locations, and troubleshooting commands.
  • Ensure that recommendations for antivirus/process interference and disk optimization include Linux equivalents (e.g., 'e4defrag', 'systemd-analyze', Linux backup agents, and exclusion rules for common Linux antivirus solutions).
  • Present Windows and Linux guidance in parallel sections or tables, rather than focusing exclusively on Windows.
GitHub Create Pull Request
← Previous Page 20 of 65 Next →