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 176-200 of 1604 flagged pages
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by repeatedly referencing PowerShell objects as the default or primary method for describing backup policy configuration, without providing equivalent Linux or cross-platform CLI examples. The term 'PowerShell object' is used to describe the policy structure, and no examples are given for Linux shell (bash), Azure CLI, or other non-Windows tooling. This may lead Linux users to feel unsupported or unclear about how to perform the same operations on their platform.
Recommendations
  • Replace or supplement references to 'PowerShell object' with neutral terms like 'policy object' or 'JSON policy definition'.
  • Provide equivalent examples using Azure CLI commands, which are cross-platform and commonly used on Linux and macOS.
  • Explicitly mention that the REST API can be invoked from any platform, and provide sample curl or httpie commands for Linux users.
  • Add a section or note highlighting Linux and macOS compatibility, and link to platform-agnostic tooling.
  • Avoid implying that PowerShell is the default or only supported method for interacting with the API.
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-12 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 towards Windows by exclusively referencing the pgAdmin GUI tool for database management tasks, without mentioning or providing examples for Linux-native or CLI alternatives (such as psql or Azure CLI). Screenshots and instructions are tailored to the Windows/GUI experience, and there is no guidance for users who may prefer or require Linux command-line workflows. The order of presentation and tool selection implicitly prioritizes Windows-centric patterns.
Recommendations
  • Include examples using psql, the standard PostgreSQL CLI tool available on Linux and Windows, for database connection, user creation, and privilege assignment.
  • Provide Azure CLI or Azure PowerShell command examples for resource and permission management, with explicit mention of cross-platform compatibility.
  • Add instructions and screenshots for connecting to Azure Database for PostgreSQL from Linux environments, including firewall rule configuration and credential management.
  • Reference Linux package managers (apt, yum) for installing PostgreSQL tools, alongside the pgAdmin download link.
  • Clearly state that all procedures can be performed on both Windows and Linux, and highlight any platform-specific differences where relevant.
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-12 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 Windows bias in several areas: environment variable setup is described exclusively using Windows Control Panel and System Properties, with screenshots and instructions tailored to Windows users. The PowerShell script is presented as the primary method for granting database privileges, with alternatives (pgAdmin, PSQL) mentioned only briefly and without example commands. There are no explicit Linux or macOS instructions or screenshots for environment variable configuration or script execution, and Windows tools/patterns (e.g., Notepad, Control Panel) are referenced without Linux equivalents.
Recommendations
  • Add step-by-step instructions and screenshots for configuring environment variables on Linux and macOS (e.g., using ~/.bashrc or ~/.profile).
  • Provide example commands for running the PowerShell script on Linux/macOS (using PowerShell Core), or offer equivalent Bash/PSQL scripts.
  • Include Linux/macOS alternatives for editing connection strings (e.g., using nano, vim, or gedit instead of Notepad).
  • Mention and demonstrate how to use pgAdmin and PSQL for privilege assignment with concrete example commands.
  • Ensure that CLI and REST API documentation links are given equal prominence to PowerShell, and consider including direct examples inline.
  • Review screenshots and UI references to ensure cross-platform applicability, or clarify when instructions are OS-specific.
GitHub Create Pull Request
Backup Back up blobs in a storage account using Azure Data Protection REST API. ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-backup-blobs.md
High Priority View Details →
Scanned: 2026-01-12 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 by mentioning Windows-centric tools (Azure PowerShell) before Linux-friendly alternatives (Azure CLI), and by referencing PowerShell in related content without providing equivalent Linux shell or CLI examples. The main workflow is described using REST API calls, which are cross-platform, but there is a lack of explicit Linux command-line examples (e.g., curl, az CLI) and no mention of Linux-specific patterns or tools. The only tool-specific references are to PowerShell and the Azure portal, with CLI mentioned last in related content. There are no examples showing how to perform these REST API operations from a Linux shell environment.
Recommendations
  • Add explicit examples using Azure CLI for all major operations (assigning permissions, configuring backup, validating requests, deleting backup instances).
  • Provide sample curl commands for REST API calls to demonstrate usage from a Linux shell.
  • When listing tools or methods (e.g., 'Azure portal, PowerShell, or REST API'), mention Azure CLI alongside PowerShell, and alternate the order to avoid Windows-first bias.
  • Include a section or note clarifying that all REST API operations can be performed from any OS, and provide guidance for Linux/macOS users.
  • In related content, ensure parity by linking to both PowerShell and CLI guides, and consider providing Bash script examples for common tasks.
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-12 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 Windows bias by prioritizing PowerShell and Windows-specific tools (such as MARS, MABS, DPM, and ARMClient via Chocolatey), providing detailed instructions and examples for Windows environments, and omitting equivalent Linux instructions or alternatives. PowerShell is presented as the primary automation method, and ARMClient installation is described only for Windows (via Chocolatey). There is no mention of Bash, Linux-native CLI usage, or cross-platform alternatives for on-premises scenarios.
Recommendations
  • Provide Bash and Linux CLI examples alongside PowerShell, especially for automation and scripting tasks.
  • Document ARMClient installation and usage for Linux (e.g., via npm or direct download), not just via Chocolatey.
  • Clarify which steps and tools are cross-platform, and explicitly note any Windows-only limitations.
  • Include guidance for managing on-premises backup items from Linux servers, or note if such scenarios are unsupported.
  • Where possible, reference Azure CLI as a cross-platform alternative to PowerShell for supported operations.
  • Add parity in screenshots and instructions for Linux environments (e.g., terminal commands, file paths).
GitHub Create Pull Request
Backup Troubleshoot encrypted Azure VM backup errors ...icles/backup/backup-azure-encrypted-vm-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the only command-line automation example for configuring permissions, without mentioning Linux equivalents such as Azure CLI or Bash. No Linux-specific troubleshooting steps, tools, or examples are provided, and Windows-centric terminology (PowerShell) appears before any cross-platform alternatives.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell for all automation steps, especially for permission configuration.
  • Explicitly mention that troubleshooting steps apply to both Windows and Linux VMs, or provide separate guidance if there are platform-specific differences.
  • Add references to Linux tools and workflows where relevant (e.g., using SSH, Linux disk management commands).
  • Ensure that links and instructions for restoring or backing up VMs include both Windows and Linux scenarios.
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-12 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 backup solution. All examples, prerequisites, and instructions reference Windows tools (PowerShell, .NET Framework, MARSAgentInstaller.exe), and there is no mention of Linux equivalents or cross-platform considerations. The documentation assumes the administrator is working on Windows, and does not provide guidance for Linux-based workloads or backup agents.
Recommendations
  • Clarify early in the documentation that DPM is a Windows-only solution, and provide links or references to Azure Backup solutions for Linux workloads.
  • Where possible, mention Azure Backup agents or procedures for Linux servers, even if only to direct users to relevant documentation.
  • If PowerShell or Windows-specific tools are required, note their lack of cross-platform support and suggest alternatives for Linux (e.g., Azure CLI, REST API).
  • Add a section comparing backup strategies for Windows and Linux workloads in Azure, and how to achieve parity in protection and management.
  • Ensure troubleshooting and prerequisites sections mention Linux considerations, or explicitly state their scope is limited to Windows/DPM.
GitHub Create Pull Request
Backup Troubleshoot Azure Backup Server ...main/articles/backup/backup-azure-mabs-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-12 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 Azure Backup Server troubleshooting is heavily Windows-centric. All examples, folder paths, registry keys, and troubleshooting steps reference Windows tools, services, and conventions (e.g., Service console, registry edits, Windows Server Backup, csc.exe, DPM, MARS agent, Internet Explorer, psexec). There are no Linux-specific instructions, examples, or parity for troubleshooting on Linux systems. The documentation assumes the administrator is working in a Windows environment and does not mention or support Linux-based deployments.
Recommendations
  • Add troubleshooting steps and examples for Linux-based backup servers, if supported.
  • Include Linux equivalents for antivirus exclusions, service management, and folder paths.
  • Provide command-line examples using bash or shell scripts for Linux, alongside Windows CMD/PowerShell.
  • Mention Linux tools and patterns (e.g., systemctl, journalctl, /etc directories) where relevant.
  • Clarify platform support at the beginning of the documentation and explicitly state if Linux is not supported.
  • If Azure Backup Server is Windows-only, add a note explaining this and direct Linux users to appropriate Azure backup solutions.
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-12 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 focused on Windows environments, with all troubleshooting steps, examples, and tool references tailored to Windows systems. There are no Linux-specific instructions, examples, or references to Linux tools. Windows tools (MMC console, Task Scheduler, Internet Explorer, Device Manager, Registry Editor, vssadmin, PowerShell) are mentioned exclusively and repeatedly, and all paths, error codes, and procedures assume a Windows OS. There is no mention of Linux equivalents or guidance for users running Azure Backup agent on Linux systems.
Recommendations
  • Add troubleshooting steps and examples for Linux environments where Azure Backup agent is supported.
  • Include Linux-specific commands and tools (e.g., systemctl, journalctl, cron, bash scripts) alongside Windows instructions.
  • Provide parity in error messages and their resolution for Linux systems.
  • Reference Linux file paths and configuration locations in addition to Windows paths.
  • Clarify in the introduction which OSes are supported and, if only Windows is supported, state this explicitly to avoid confusion.
  • If Azure Backup agent is Windows-only, provide links or guidance for Linux backup solutions in Azure.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing PowerShell examples for moving Recovery Services vaults, referencing Windows-specific update instructions before Linux equivalents, and omitting Linux-specific CLI or shell script examples. While Azure CLI is mentioned, the scripting guidance and troubleshooting steps prioritize Windows tools and patterns, and do not offer parity for Linux administrators.
Recommendations
  • Provide Bash or shell script examples for moving Recovery Services vaults, especially for Linux users.
  • Include Linux-specific instructions and troubleshooting steps alongside Windows guidance (e.g., how to update certificates on Linux with concrete commands).
  • Ensure that CLI examples are given equal prominence to PowerShell, and consider presenting CLI/Bash examples before or alongside PowerShell.
  • Reference cross-platform tools (like Azure CLI) as the primary method, with PowerShell as an alternative, to avoid Windows-first perception.
  • Add explicit notes or sections for Linux administrators, clarifying any differences in process or requirements.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. The detailed instructions for reinstalling the VMSnapshot backup extension are provided first and extensively for Windows, including PowerShell cmdlets, registry edits, and use of Windows-specific tools (services.msc, regedit, command prompt). In contrast, the Linux section is much shorter, lacks step-by-step guidance, and omits example commands for common operations (e.g., deleting directories, restarting agents). Throughout the page, examples and screenshots are Windows-centric, with little parity for Linux users.
Recommendations
  • Provide Linux instructions with equal detail and step-by-step guidance, including example shell commands for deleting extension directories, restarting the waagent, and verifying extension status.
  • Include screenshots or terminal output examples for Linux operations where appropriate.
  • Present Windows and Linux instructions side-by-side or in parallel sections to avoid implicit prioritization of Windows.
  • Where PowerShell or Windows tools are mentioned, also mention equivalent Linux commands and tools (e.g., Azure CLI, shell commands).
  • Clarify any differences in backup management workflows between Windows and Linux VMs, and ensure both are covered in all relevant sections.
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-12 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 exhibits a strong Windows bias. All installation, configuration, and operational instructions are exclusively for Windows Server environments, with no mention of Linux support or examples. Windows-specific tools (e.g., PowerShell cmdlets, registry edits, Windows Server Deduplication) are referenced throughout, and the only supported platforms listed are Windows Server editions. There are no Linux equivalents, nor any guidance for deploying or managing Azure Backup Server on Linux systems.
Recommendations
  • Explicitly state platform limitations early in the document (e.g., 'Azure Backup Server is only supported on Windows Server').
  • If Linux support is planned or available, add parallel instructions/examples for Linux environments.
  • Where possible, mention alternatives for Linux users (e.g., Azure Backup agent for Linux, or other backup solutions).
  • Include a comparison table of supported platforms and features for Windows and Linux.
  • Avoid assuming Windows-only environments in introductory and summary sections.
  • If PowerShell is referenced, note whether cross-platform PowerShell Core is supported or provide Bash/CLI alternatives for Linux.
  • Clarify whether any components (e.g., SQL Server, DPM) can be run on Linux, or provide links to Linux-specific backup documentation.
GitHub Create Pull Request
Backup Troubleshoot monitoring issues for Azure Backup ...n/articles/backup/backup-azure-monitor-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-12 00:00
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 Windows tools (Task Manager, Control Panel), Windows-specific processes and file paths, and omitting any mention of Linux equivalents or troubleshooting steps for Linux-based Azure Backup agents.
Recommendations
  • Add troubleshooting steps for Linux environments, such as using 'ps', 'systemctl', or 'journalctl' to check and manage the agent process.
  • Include Linux file path examples for agent logs (e.g., /var/lib/azurebackup/...).
  • Mention Linux service management commands and tools alongside Windows instructions.
  • Clarify whether the guidance applies only to Windows or provide parity for Linux users.
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-12 00:00
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 mentioning Windows-centric backup tools (System Center DPM, Windows Server, Azure Backup Server) before or instead of Linux equivalents. Examples and links for backing up Windows Server are provided, but there are no equivalent Linux server backup examples or references to Linux-native backup tools. The documentation lists Windows workloads and tools first and does not provide parity for Linux server backup scenarios.
Recommendations
  • Include explicit examples and links for backing up Linux servers, not just Linux VMs.
  • Mention Linux-native backup tools or workflows supported by Recovery Services vaults, if available.
  • Ensure that references to backup scenarios and tools are balanced between Windows and Linux, listing both platforms equally.
  • Add a section or FAQ entry addressing Linux server backup support and best practices.
  • Provide step-by-step guides or links for Linux server backup using Recovery Services vaults, similar to the Windows Server example.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows examples, tools, and troubleshooting steps are often presented before their Linux equivalents, and Windows-specific registry edits and GUI tools (e.g., File Explorer) are described in detail. PowerShell is referenced in the 'Next steps' section before Azure CLI. Linux instructions are present and reasonably detailed, but Windows is generally prioritized in ordering and depth.
Recommendations
  • Alternate the order of Windows and Linux instructions throughout the documentation, or present them in parallel sections to avoid implicit prioritization.
  • Provide equally detailed troubleshooting steps for Linux as are given for Windows (e.g., registry edits for Windows are described in detail; ensure Linux config changes are similarly explained).
  • Include Linux-specific tools and file browsing methods (e.g., mention using Nautilus, Dolphin, or command-line tools for browsing recovered files, not just File Explorer for Windows).
  • In the 'Next steps' section, list Azure CLI and Linux automation options before or alongside PowerShell to avoid reinforcing Windows-first patterns.
  • Where screenshots or images are used, ensure parity by including Linux equivalents, not just Windows GUI images.
  • Explicitly mention Linux desktop environments and file managers where relevant, to help Linux users navigate recovered files.
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-12 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 is exclusively focused on Windows Server system state restore, using only Windows-specific tools (MARS agent, Windows Server Backup, wbadmin, Win RE) and providing no mention or examples for Linux systems. All instructions, screenshots, and command-line examples are Windows-centric, with no Linux parity or alternatives discussed.
Recommendations
  • Clarify in the introduction that the procedure is Windows-specific, and provide links to equivalent Linux backup/restore documentation if available.
  • If Azure Backup supports Linux system state or similar functionality, add parallel sections for Linux, including examples using Linux tools (e.g., rsync, tar, Azure CLI, etc.).
  • Where possible, mention cross-platform backup/restore strategies and tools, or provide guidance for Linux administrators on how to achieve similar outcomes.
  • Ensure future documentation on backup and restore covers both Windows and Linux scenarios, or clearly scopes the content as Windows-only to avoid confusion.
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-12 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 Windows bias by repeatedly referencing Windows-specific backup tools (MARS agent, DPM, MABS) and scenarios, with no mention of Linux equivalents or examples. All workload and agent references are for Windows environments, and there are no instructions, recommendations, or clarifications for Linux-based backup agents or VM workloads. The documentation assumes the use of Microsoft-centric backup solutions and does not address how private endpoints interact with Linux backup scenarios.
Recommendations
  • Include examples and scenarios for Linux-based Azure VM backups, such as using Azure Backup for Linux VMs and any Linux-specific agents or extensions.
  • Clarify whether private endpoints support Linux workloads and describe any differences or considerations for Linux environments.
  • Mention Linux-compatible backup tools or third-party solutions where applicable, and provide guidance for configuring DNS and network connectivity for Linux VMs.
  • Add explicit instructions or notes for Linux users, including any required ports, FQDNs, or configuration steps that differ from Windows.
  • Ensure parity in documentation by listing both Windows and Linux scenarios in tables and recommendations.
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-12 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 is heavily focused on Windows-centric backup tools (MARS, DPM, MABS) and provides examples, instructions, and troubleshooting steps 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, and Linux equivalents or cross-platform alternatives are absent.
Recommendations
  • Include information about Azure Backup support for Linux workloads, if available, and document any Linux agents or integration methods.
  • Provide Linux-specific examples for enabling security features, recovering deleted backup data, and troubleshooting errors.
  • Add CLI-based instructions (e.g., Azure CLI, Bash) alongside PowerShell and Windows UI steps.
  • Mention Linux backup tools or third-party solutions that integrate with Azure Backup, if applicable.
  • Ensure that parity in security features and immutability support for Linux workloads is clearly documented.
  • Add screenshots or walkthroughs for Linux environments where relevant.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references Windows-centric tools and patterns, such as Data Protection Manager (DPM), Azure Backup agent, MARS agent, and command-line instructions using 'net stop/start dpmra'. There are no examples, troubleshooting steps, or references for Linux environments or equivalent Linux backup solutions. The guidance assumes the reader is operating in a Windows ecosystem, with no mention of Linux commands, services, or compatibility.
Recommendations
  • Include troubleshooting steps and examples for Linux-based backup solutions, if supported.
  • Provide equivalent Linux commands or service management instructions (e.g., systemctl) alongside Windows command prompt examples.
  • Clarify platform support and limitations at the beginning of the documentation.
  • Mention or link to Linux-compatible backup tools or agents, if available.
  • Ensure parity in error resolution steps for both Windows and Linux environments.
GitHub Create Pull Request
Backup Troubleshoot System State Backup ...icles/backup/backup-azure-system-state-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-12 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 focused on Windows environments, specifically on-premises Windows servers. All troubleshooting steps, prerequisites, and examples use Windows-specific tools (PowerShell, Server Manager, Windows Server Backup, wbadmin, VSS, MARS agent) with no mention of Linux equivalents or cross-platform scenarios. The documentation assumes the user is operating in a Windows-only context and does not provide guidance for Linux systems or alternative backup tools.
Recommendations
  • Clearly state in the introduction that System State Backup is a Windows-only feature and provide links to Linux backup documentation for parity.
  • If Azure Backup supports Linux in other contexts, add a section or cross-reference for troubleshooting Linux backup issues.
  • Where possible, mention Linux backup tools (e.g., rsync, tar, Azure Backup for Linux) and provide guidance or links for similar troubleshooting steps.
  • Ensure that examples and troubleshooting steps are balanced or, if not applicable, explicitly state platform limitations to avoid confusion.
  • Consider adding a comparison table of backup features and troubleshooting steps for Windows vs. Linux environments.
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-12 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 page demonstrates a strong Windows bias. All examples, instructions, and tooling references are exclusively for Windows environments (e.g., NT SERVICE accounts, SSMS, PowerShell, Windows file paths, Task Manager, SMB shares). There is no mention of Linux-based SQL Server VMs, nor are Linux equivalents for permissions, file paths, or automation provided. The documentation assumes the use of Windows-specific features and tools throughout.
Recommendations
  • Add explicit guidance for SQL Server running on Linux VMs, including how to install and configure the Azure Backup extension in Linux environments.
  • Provide Linux-specific instructions for setting up permissions, such as using systemd service accounts or local users, and configuring SQL Server authentication on Linux.
  • Include automation examples using Bash scripts or sqlcmd on Linux, rather than only PowerShell.
  • Show Linux file path conventions (e.g., /var/opt/mssql/backups) alongside Windows paths.
  • Describe how to manage local backup folders and permissions using Linux tools (chmod, chown) and explain how to mount network shares (e.g., using CIFS).
  • Clarify any differences or limitations in Azure Backup support for SQL Server on Linux VMs, and link to relevant support matrix sections.
GitHub Create Pull Request
Backup Restore SQL server databases in Azure VMs using Azure Backup via CLI ...b/main/articles/backup/backup-azure-sql-restore-cli.md
High Priority View Details →
Scanned: 2026-01-12 00:00
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 exclusively referencing SQL Server (a Microsoft/Windows-centric database), using Windows-style resource and naming conventions (e.g., MSSQLSERVER, testSQLVM), and omitting any mention or example of restoring non-Windows SQL workloads (such as Linux-based SQL Server or other database engines). All examples and terminology assume a Windows VM and SQL Server instance, with no guidance for Linux VMs or alternative database platforms.
Recommendations
  • Add explicit guidance and examples for restoring SQL Server databases running on Linux Azure VMs, including any differences in CLI usage, file paths, or prerequisites.
  • Clarify whether the documented process applies to both Windows and Linux SQL Server deployments, and note any limitations or required steps for Linux.
  • Include examples using Linux-style file paths and VM naming conventions to demonstrate parity.
  • Mention support (or lack thereof) for other database engines (e.g., PostgreSQL, MySQL) if applicable, or link to relevant documentation.
  • Where possible, use neutral terminology (e.g., 'SQL VM' instead of 'testSQLVM', '/home/sql/restoreasfiles' instead of Windows paths) and clarify platform-specific requirements.
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-12 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, a Windows-only tool. All instructions, screenshots, and examples are tailored for Windows environments, with no mention of Linux equivalents, Linux system state backup, or cross-platform alternatives. The documentation assumes the user is operating on Windows and does not provide parity for Linux users.
Recommendations
  • Add a section or a separate article for backing up Linux system state or equivalent data to Azure, using supported tools (e.g., Azure Backup for Linux, Azure CLI, or third-party solutions).
  • Include cross-platform backup strategies and mention Linux support (if available) early in the documentation, not just Windows.
  • If system state backup is not supported for Linux, explicitly state this limitation and provide guidance on alternative backup approaches for Linux systems.
  • Provide links to Linux backup documentation and tools where relevant.
  • Ensure that future documentation covers both Windows and Linux scenarios, or clearly scopes the content as Windows-only in the title and introduction.
GitHub Create Pull Request
Backup Troubleshoot Azure Backup failures caused by agent or extension issues ...up-azure-troubleshoot-vm-backup-fails-snapshot-timeout.md
High Priority View Details →
Scanned: 2026-01-12 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 Windows bias in several ways: Windows troubleshooting steps and tools (e.g., services.msc, Event Viewer, Control Panel, .NET, Visual C++ Redistributable) are described in detail, often with screenshots, while Linux equivalents are less detailed or omitted. Windows is frequently mentioned first in lists and instructions, and PowerShell is referenced for operations without equivalent Bash/CLI commands for Linux. Some troubleshooting steps (e.g., antivirus exclusions, COM+/MSDTC, VSS writer) are Windows-specific, with no Linux alternatives or explanations. Linux instructions are present but less comprehensive, and examples for Linux (e.g., log locations, service management) are brief and lack visual aids.
Recommendations
  • Provide Linux troubleshooting steps with equal detail, including screenshots or terminal output where appropriate.
  • Include Linux equivalents for all Windows tools mentioned (e.g., show how to check agent status with systemctl, view logs with journalctl or tail, manage packages, etc.).
  • When listing steps or causes, alternate or group by OS rather than always listing Windows first.
  • Add Bash/CLI commands for operations currently only described with PowerShell (e.g., cancelling backup jobs, configuring static IPs).
  • For Windows-specific features (e.g., VSS, COM+/MSDTC, Event Viewer), clarify their Linux equivalents or note if not applicable.
  • Expand Linux agent troubleshooting to cover common issues (e.g., permissions, SELinux/AppArmor, dependency installation) and provide links to relevant Linux documentation.
  • Ensure antivirus and application control troubleshooting covers common Linux solutions (e.g., ClamAV, SELinux policies) 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-12 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. Only Windows tools (such as Performance Monitor) are mentioned, and all file paths, agent references, and troubleshooting guidance assume the use of Windows. 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 performance bottlenecks and how to diagnose them.
  • Mention and provide guidance for Linux monitoring tools (e.g., top, iostat, vmstat, sar) alongside Windows Performance Monitor.
  • Include Linux-specific file paths and log locations for the Azure Backup agent.
  • Clarify which recommendations apply to both Windows and Linux, and explicitly call out any platform-specific differences.
  • Provide parity in antivirus and backup process troubleshooting for Linux systems, including common interfering processes and exclusion rules.
GitHub Create Pull Request
← Previous Page 8 of 65 Next →