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 801-825 of 1604 flagged pages
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-restore-key-secret.md ...ain/articles/backup/backup-azure-restore-key-secret.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page is heavily focused on PowerShell-based workflows, with all examples and instructions using PowerShell cmdlets and Windows-style file paths (e.g., 'C:\...'). There is no mention of Bash, Azure CLI, or Linux-native tools, and Linux scenarios are only referenced in passing, with no actual Linux command examples. The documentation assumes the use of Windows tools and patterns throughout, making it difficult for Linux users to follow or replicate the steps without adaptation.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all key steps, including restoring keys and secrets.
  • Use platform-neutral file paths and explain how to adapt them for Linux (e.g., '/home/user/...').
  • Explicitly document any differences or additional steps required for Linux environments, such as handling JSON files, secure strings, and storage account access.
  • Include a section or callouts for Linux users, outlining the recommended workflow and tools.
  • Reference cross-platform automation options (e.g., Azure CLI, REST API) alongside PowerShell.
  • Ensure that Linux examples are given equal prominence and detail as Windows/PowerShell examples.
GitHub Create Pull Request
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All examples, instructions, and tooling references assume SQL Server is running on Windows VMs. Steps for configuring permissions, managing service accounts, and automating tasks use Windows-specific concepts (NT SERVICE accounts, SSMS, Windows authentication, PowerShell, Task Manager, SMB shares). There is no mention of Linux-based SQL Server VMs, nor are there any Linux-specific instructions, examples, or parity notes.
Recommendations
  • Add explicit guidance for SQL Server on Linux VMs, including differences in service account management, permissions, and backup extension installation.
  • Provide Linux-specific examples for configuring permissions (e.g., using sqlcmd, chown/chmod for file permissions, systemd service management).
  • Include automation scripts for Linux environments (e.g., bash scripts, use of sqlcmd on Linux, systemctl commands).
  • Clarify which instructions are Windows-only and offer equivalent steps for Linux, or note limitations if Linux is not supported.
  • Mention Linux support status early in the document, and link to Linux-specific documentation if available.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-agentless-multi-disk-crash-consistent-overview.md ...ure-vms-agentless-multi-disk-crash-consistent-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows tools and terminology (such as Volume Shadow Copy Service (VSS)) are mentioned before Linux equivalents (fsfreeze), and links to VM Agent and snapshot extension documentation point to Windows-specific pages. There are no concrete examples or links for Linux VM agent or snapshot extension, and Linux backup patterns (such as pre/post scripts) are mentioned only in passing, without detail or parity in guidance.
Recommendations
  • Provide equal prominence to Linux tools and patterns (e.g., mention fsfreeze before or alongside VSS, and link to Linux VM agent/snapshot extension documentation).
  • Include concrete examples or references for Linux backup scenarios, such as how crash-consistent backups interact with Linux file systems and backup scripts.
  • Ensure that documentation links and extension references cover both Windows and Linux, or clarify OS-specific differences.
  • Add a section or table explicitly comparing Windows and Linux backup mechanisms, requirements, and limitations for crash-consistent backups.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and CLI versions for trusted launch support before mentioning REST API, and by not providing any Linux-specific examples or guidance. All command-line references are generic or Windows-centric (PowerShell, Azure CLI), with no mention of Linux shell usage, nor are there screenshots or instructions for Linux environments. The documentation assumes use of the Azure Portal or Windows tools, omitting Linux-specific patterns or considerations.
Recommendations
  • Include explicit Linux shell (bash) examples for CLI commands, showing usage in a Linux terminal.
  • Clarify that Azure CLI commands work cross-platform and provide sample commands for both Windows (PowerShell) and Linux (bash).
  • Add notes or sections on how to perform migration steps from Linux environments, including any OS-specific prerequisites or troubleshooting.
  • Ensure screenshots and instructions do not assume Windows-only environments (e.g., avoid PowerShell-only references, show CLI in bash where appropriate).
  • Mention Linux tools or patterns where relevant (e.g., scripting bulk migrations with bash, using Linux authentication methods).
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. Windows tools and patterns (such as VSS and PowerShell) are mentioned first and in greater detail, while Linux equivalents are referenced briefly or require user customization (e.g., custom scripts for app consistency). PowerShell is specifically called out for restore operations, with no mention of Linux CLI or automation alternatives. Examples and troubleshooting guidance are Windows-centric, and Linux instructions are less prescriptive, often shifting responsibility to the user.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside PowerShell for backup and restore automation.
  • Include step-by-step Linux app-consistent backup examples, not just references to custom scripts.
  • Mention Linux tools (e.g., fsfreeze, LVM snapshots) explicitly and describe their integration with Azure Backup.
  • Balance troubleshooting and best practice sections with Linux-specific guidance and examples.
  • When listing processes or tools, present Windows and Linux options in parallel rather than Windows-first.
  • Add links to Linux-focused documentation where appropriate, similar to the Windows references.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-encryption.md ...ob/main/articles/backup/backup-azure-vms-encryption.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. PowerShell is the only command-line example provided for identifying a VM's associated Key Vault, with no equivalent Linux (bash/Azure CLI) example. Windows tools and terminology (BitLocker, PowerShell) are mentioned before Linux equivalents (dm-crypt), and the only explicit command-line instructions use Windows-centric tooling. There are no Linux-specific command-line examples or instructions, and the documentation does not provide parity for Linux administrators.
Recommendations
  • Add equivalent Azure CLI and/or bash examples alongside PowerShell commands, especially for tasks like identifying the Key Vault associated with a VM.
  • When discussing encryption technologies, mention Linux (dm-crypt) and Windows (BitLocker) together, or alternate the order to avoid Windows-first bias.
  • Include Linux-specific troubleshooting steps, examples, and screenshots where appropriate.
  • Explicitly state that all steps and features apply equally to Linux VMs, and provide links to Linux-focused documentation where available.
  • Ensure that automation and scripting instructions are provided for both Windows (PowerShell) and Linux (Azure CLI/bash) environments.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias in its encryption coverage for Azure Backup. Windows-specific technologies (BitLocker, SQL Server, TDE) are mentioned first or exclusively, with more detail and links, while Linux equivalents (DM-Crypt) are referenced only briefly and without further explanation or links. There are no Linux-specific examples, and the documentation assumes familiarity with Windows tools and patterns.
Recommendations
  • Provide equal detail for Linux encryption technologies, such as DM-Crypt, including links to relevant documentation and usage examples.
  • Include Linux-specific backup and restore scenarios, with step-by-step instructions or references.
  • Balance the order of presentation so that Linux and Windows technologies are introduced together, or alternate which is mentioned first.
  • Add examples or notes for Linux database backup and restore processes, especially for encrypted workloads.
  • Ensure that references to command-line tools or scripts include both PowerShell (Windows) and Bash (Linux) equivalents where applicable.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-release-notes-v3.md ...b/main/articles/backup/backup-mabs-release-notes-v3.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation for Microsoft Azure Backup Server v3 is heavily oriented toward Windows environments. All examples, tools, and instructions reference Windows-only components such as SQL Server Management Studio (SSMS), SQL Server Reporting Services (SSRS), and Windows file paths. There are no examples or guidance for Linux systems, nor are Linux backup scenarios or tools mentioned. The documentation assumes the administrator is working on Windows, with no mention of cross-platform or Linux support.
Recommendations
  • Add explicit statements about platform support, clarifying whether Linux is supported or not.
  • If Linux is supported, provide equivalent instructions and examples for Linux environments, including relevant tools and commands.
  • Mention Linux backup scenarios and any differences in known issues or workarounds for Linux deployments.
  • Where file paths or tools are referenced, include Linux equivalents or note their absence.
  • Ensure parity in troubleshooting steps and error messages for both Windows and Linux platforms.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. All instructions, prerequisites, and examples are tailored exclusively for Windows environments. The installation steps, VM recommendations, and tooling (e.g., PowerShell cmdlets, Windows Server images, Windows Update, domain joining) are Windows-specific. There are no references to Linux-based deployment, Linux VM images, or cross-platform alternatives. The use of Windows-centric terminology and tools (e.g., C:\, D:\, domain join, PowerShell, Windows Update) further reinforces this bias.
Recommendations
  • Add guidance for deploying Azure Backup Server on Linux-based VMs if supported, or clarify Windows-only support explicitly.
  • Provide parity by including Linux equivalents for prerequisites, such as .NET installation steps, disk mounting, and storage configuration.
  • If PowerShell is required, mention cross-platform alternatives (e.g., Azure CLI, Bash scripts) or note PowerShell Core compatibility on Linux.
  • Reference Linux VM images in Azure Stack Hub where applicable, and provide instructions for their setup.
  • Clarify any limitations or lack of support for Linux, so administrators can make informed decisions.
  • Include troubleshooting steps and network configuration examples for Linux environments.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on Microsoft Azure Backup Server (MABS), which is a Windows-only tool. All instructions, screenshots, and workflows assume a Windows environment, with references to Windows-specific accounts (NTAuthority\System) and SQL Server features configured via Windows. There are no examples, instructions, or mentions of Linux-based SQL Server deployments, nor any cross-platform backup tools or CLI alternatives. The documentation does not address Linux parity or provide guidance for users running SQL Server on Linux or using non-Windows backup solutions.
Recommendations
  • Add explicit notes about platform support, clarifying that MABS is Windows-only and provide alternatives for Linux-based SQL Server deployments.
  • Include examples or references for backing up SQL Server on Linux, such as using Azure Backup via CLI, or third-party tools compatible with Linux.
  • Mention Linux-specific considerations (e.g., service accounts, file system paths, permissions) where relevant.
  • Provide parity in documentation structure: if step-by-step workflows are given for Windows, offer equivalent workflows for Linux environments where possible.
  • Link to documentation for cross-platform backup solutions or Azure-native backup options that support Linux.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-system-state.md ...blob/main/articles/backup/backup-azure-system-state.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation 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 Windows-specific, with no mention of Linux systems, Linux backup tools, or cross-platform alternatives. The agent and backup process described are only applicable to Windows, and Linux users are neither addressed nor provided with equivalent guidance.
Recommendations
  • Add a section or separate documentation for backing up Linux system state or files to Azure, using supported Azure Backup methods (e.g., Azure Backup for Linux VMs, Azure CLI, or third-party tools).
  • Clearly state in the introduction that the guide is Windows-specific, and provide links to Linux backup documentation for parity.
  • Include comparative tables or notes about differences in backup procedures between Windows and Linux environments.
  • If Azure Backup does not support Linux system state backup, explicitly mention this limitation and suggest alternative backup strategies for Linux systems.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a Windows bias in several ways: troubleshooting steps and examples often mention Windows tools (services.msc, Control Panel, Event Viewer) and PowerShell before or instead of Linux equivalents. Windows-specific patterns (such as .NET requirements, Visual C++ Redistributable installation, regsvr32 usage) are described in detail, while Linux troubleshooting is less detailed and sometimes lacks parity in step-by-step guidance or tool references. Windows instructions are frequently listed first, and some troubleshooting steps (e.g., antivirus exclusions, extension troubleshooting) are described only for Windows paths and tools, with Linux equivalents missing or less emphasized.
Recommendations
  • Ensure Linux troubleshooting steps are as detailed and actionable as Windows steps, including specific commands and tool references (e.g., systemctl, journalctl, log file locations).
  • Provide Linux equivalents for all Windows tools mentioned (e.g., mention systemctl/service for services.msc, apt/yum for MSI installs, syslog/journalctl for Event Viewer logs).
  • When listing troubleshooting steps, alternate or parallelize Windows and Linux instructions, rather than listing Windows first.
  • Include Linux-specific examples for antivirus exclusions, extension troubleshooting, and agent installation/updating, with explicit file paths and commands.
  • Add parity in screenshots or command-line examples for Linux environments where appropriate.
  • Review all references to PowerShell and ensure CLI/bash alternatives are provided and equally emphasized.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. In the 'Install the VM agent' section, Windows instructions are given first, with detailed steps and verification guidance, while Linux instructions are more generic and lack step-by-step detail. Windows-specific tools (MSI installer, file paths, .exe verification) are mentioned, but Linux equivalents (commands, file paths, verification steps) are missing. Throughout the page, there are no Linux-specific screenshots or examples, and the overall flow assumes familiarity with Windows conventions.
Recommendations
  • Provide Linux instructions before or alongside Windows instructions in the 'Install the VM agent' section, with equal detail (e.g., specific commands for RPM/DEB installation, verification steps, file paths).
  • Include Linux-specific screenshots or terminal output where relevant, especially for agent installation and verification.
  • Mention Linux tools and conventions explicitly (e.g., using systemctl to check agent status, log file locations).
  • Ensure that all procedures and examples are equally detailed for both Windows and Linux VMs.
  • Consider adding a table or section comparing Windows and Linux backup agent installation and troubleshooting steps.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-database-from-azure-vm-blade.md ...ckup/backup-sql-server-database-from-azure-vm-blade.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific tools and patterns (e.g., AzureBackupWindowsWorkload extension, NT Service accounts, SQLIaaSExtension), with no mention of Linux-based SQL Server VM scenarios or equivalents. All instructions and screenshots assume a Windows environment, and there are no examples or guidance for Linux VMs running SQL Server.
Recommendations
  • Add explicit guidance and examples for backing up SQL Server running on Linux-based Azure VMs, including any differences in workflow, required extensions, and service accounts.
  • Clarify whether the described process applies only to Windows VMs or both Windows and Linux, and provide links to Linux-specific documentation if available.
  • Mention Linux equivalents (if any) for the AzureBackupWindowsWorkload extension and NT Service accounts, or note limitations for Linux support.
  • Include screenshots and step-by-step instructions for Linux VM scenarios, or state that the feature is not supported for Linux if that is the case.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric, with all instructions, screenshots, and tooling (Server Manager, PowerShell cmdlets, ReFS filesystem) exclusively referencing Windows Server environments. There are no Linux equivalents, examples, or mentions of cross-platform support. Windows tools and patterns are presented as the only option, and PowerShell is the sole scripting example.
Recommendations
  • Clarify platform support early in the article, explicitly stating if Linux is unsupported or providing Linux alternatives if available.
  • If Azure Backup Server or Modern Backup Storage can be used on Linux, add equivalent instructions, tooling, and examples for Linux environments (e.g., using Linux filesystems, CLI tools, or shell scripts).
  • Where PowerShell is used, provide Bash or other Linux shell equivalents if possible.
  • Add a comparison table or section outlining differences and limitations between Windows and Linux deployments.
  • If the product is Windows-only, make this clear in the prerequisites and summary, and consider linking to Linux backup solutions for Azure if relevant.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-matrix-iaas.md ...lob/main/articles/backup/backup-support-matrix-iaas.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several areas: Windows scenarios, tools, and examples are presented first and in greater detail; PowerShell is referenced as the primary method for VM restore operations; Windows-specific backup agents (MARS, DPM, MABS) are described extensively, while Linux support is limited and often marked as 'not supported' for these tools. Linux backup scenarios are less detailed, lack parity in agent-based backup options, and do not provide CLI or script examples analogous to the PowerShell references for Windows.
Recommendations
  • Present Linux and Windows scenarios side-by-side, or alternate which is described first in tables and sections.
  • Provide Linux CLI (az CLI, Bash) examples for restore operations, especially where PowerShell is referenced for Windows.
  • Expand documentation on Linux backup and restore workflows, including supported tools and scripts.
  • Clarify agent support parity and provide guidance for Linux users where Windows-only agents are mentioned.
  • Include references to Linux-native backup tools or third-party solutions where Azure Backup does not support Linux directly.
  • Add troubleshooting and best practices sections specifically for Linux VM backups, similar to the detail given for Windows.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: troubleshooting steps and examples frequently reference Windows tools (Event Viewer, Services.msc, Registry Editor, command prompt commands like net start/stop, icacls, regedit, msdtc, vssadmin), and PowerShell is often mentioned as the automation method for restore operations. Windows-specific errors (VSS, COM+, BitLocker, Visual C++ Redistributable) are covered in detail, with step-by-step instructions, while Linux troubleshooting is less detailed and often only briefly mentioned. In many sections, Windows instructions are given first or exclusively, with Linux guidance appearing later or being less comprehensive. Some error resolutions and automation steps lack Linux equivalents or examples.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples for all major error scenarios, especially where only Windows tools (Event Viewer, Registry, VSS, COM+) are referenced.
  • Include CLI/bash commands and Linux file paths where Windows commands (net start, icacls, regedit, msdtc, vssadmin) are given, and ensure parity in detail and clarity.
  • When referencing automation (e.g., restore operations), offer equivalent Linux CLI or Azure CLI examples alongside PowerShell.
  • Present Windows and Linux instructions side-by-side or in parallel sections to avoid Windows-first ordering.
  • Expand coverage of Linux-specific backup/restore issues, such as SELinux, mount point handling, and agent installation, with step-by-step guidance and troubleshooting logs.
  • Where screenshots or UI references are Windows-specific, add Linux screenshots or terminal output where relevant.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-system-state-and-bmr.md ...in/articles/backup/backup-mabs-system-state-and-bmr.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All examples, workflows, and tool references are specific to Windows (e.g., Windows Server Backup, WinRE, PowerShell cmdlets, Windows file paths). There is no mention of Linux support, Linux equivalents, or cross-platform scenarios. The documentation assumes the reader is using Windows servers and tools, and does not provide guidance or parity for Linux-based systems.
Recommendations
  • Explicitly state platform support at the beginning of the documentation (e.g., whether Linux is supported for system state/BMR backups).
  • If Linux is supported, provide equivalent workflows, examples, and tool references for Linux systems (e.g., using native Linux backup tools, recovery environments, and file paths).
  • Include Linux-specific prerequisites, limitations, and recovery procedures.
  • If Azure Backup Server does not support Linux for system state/BMR, clarify this limitation and link to alternative solutions for Linux environments.
  • Balance PowerShell examples with CLI or shell script examples for Linux, where applicable.
  • Mention Linux backup and recovery patterns/tools (e.g., rsync, tar, dd, Timeshift, etc.) if relevant.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-matrix.md ...ocs/blob/main/articles/backup/backup-support-matrix.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a Windows bias in several ways: Windows backup scenarios are described first and in more detail, with specific tools (MARS agent, DPM, MABS) that are Windows-centric. Linux backup support is often described as 'not supported' or as requiring custom scripts, and Linux examples are missing or less detailed. Windows tools and features (e.g., deduplication, app-aware backup) are mentioned exclusively or before Linux equivalents. There are no Linux command-line or tool examples, and the documentation focuses heavily on Windows backup patterns.
Recommendations
  • Provide Linux-specific backup examples and workflows where possible, including command-line or script examples for configuring backups and restores.
  • Include Linux tools and patterns (e.g., native Linux backup utilities, integration with Azure Backup) alongside Windows tools, and mention them with equal prominence.
  • Clarify and expand on Linux support for features such as app-aware backup, deduplication, and compression, including any limitations and workarounds.
  • Ensure that Linux scenarios are described with the same level of detail as Windows scenarios, and avoid presenting Windows options first by default.
  • Add explicit guidance for Linux administrators, such as best practices for backup and restore, and troubleshooting steps.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page for Azure Backup Server (MABS) V4 protection matrix demonstrates a strong Windows bias. Windows workloads, tools, and patterns are described in detail and presented first, with Linux support relegated to a single, limited section. Examples, supported features, and recovery options are almost exclusively for Windows environments, with Linux coverage limited to VM-level backup and lacking parity in features and examples. Windows-specific tools and requirements (e.g., NTFS, VSS, Visual C++ redistributables, Windows Management Framework) are mentioned throughout, while Linux equivalents are absent.
Recommendations
  • Provide Linux-specific backup and recovery examples, including file-level and application-level scenarios where possible.
  • List Linux workloads alongside Windows workloads in the main protection matrix, not as a separate, minimal section.
  • Clarify which features (e.g., item-level recovery, deduplication, system state backup) are available or not for Linux, and explain any limitations.
  • Mention Linux file systems (e.g., ext4, xfs) and backup consistency mechanisms (e.g., fsfreeze, LVM snapshots) where relevant, not only NTFS/VSS.
  • Include guidance for Linux agent installation, configuration, and troubleshooting, similar to the detail provided for Windows.
  • Reference Linux-specific tools or commands where Windows tools (e.g., Control Panel, VSS, Visual C++) are mentioned.
  • Ensure parity in documentation structure, so Linux administrators can easily find relevant information without feeling like an afterthought.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-postgresql-cli.md ...ocs/blob/main/articles/backup/backup-postgresql-cli.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways. PowerShell is referenced as the default or primary object model for policy manipulation, and examples of modifying policies reference PowerShell objects first. File path examples use Windows-style backslashes (e.g., .\OSSPolicy.json), and there is no mention of Linux-specific tools or shell environments beyond generic Bash variable assignment. The guidance for editing policy files is written from a Windows perspective, with no explicit Linux or cross-platform file handling examples. There are no Linux-specific command-line examples, nor are Linux shell scripting patterns (such as sed, jq, or typical Linux file paths) demonstrated.
Recommendations
  • Provide Linux/Unix shell examples alongside PowerShell, especially for file manipulation and scripting (e.g., show how to edit JSON files using jq or sed).
  • Use platform-neutral file paths (e.g., ./OSSPolicy.json) or explicitly show both Windows and Linux path conventions.
  • Clarify that the Azure CLI commands work identically on Linux, macOS, and Windows, and provide sample scripts for Bash/zsh.
  • Avoid referencing PowerShell objects as the default or primary model; instead, present Azure CLI and REST API approaches as platform-neutral.
  • Add a section or callouts for Linux users, including tips for scripting, file handling, and troubleshooting in Linux environments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-automation.md ...blob/main/articles/backup/backup-support-automation.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation consistently lists PowerShell as the first automation method for nearly all operations, and provides direct links to PowerShell examples. This reflects a Windows-centric approach, as PowerShell is primarily a Windows tool (though cross-platform now, it's still most associated with Windows environments). There is a heavy emphasis on PowerShell support and examples, with CLI and REST API listed second and third. No Linux-specific shell examples (e.g., bash scripts) or references to Linux-native tooling are present. The documentation does not mention or provide parity for Linux-specific automation scenarios, nor does it acknowledge differences in usage patterns between Windows and Linux administrators.
Recommendations
  • Alternate the order of automation methods in tables, listing CLI first in some cases to avoid implicit prioritization of PowerShell.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Add Linux shell (bash) script examples for common automation scenarios alongside PowerShell examples.
  • Where PowerShell is referenced, clarify that it is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
  • Include notes or sections on Linux-specific automation best practices, such as using cron jobs, shell scripts, or integrating with configuration management tools popular in Linux environments.
  • Audit linked example pages to ensure Linux parity in step-by-step instructions and screenshots.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-database-azure-vms.md ...rticles/backup/backup-sql-server-database-azure-vms.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias in several ways: it exclusively references Windows environments and tooling (e.g., AzureBackupWindowsWorkload extension, NT Service accounts, Windows-specific connectivity test scripts), omits any mention of Linux-based SQL Server VMs or their backup requirements, and provides examples and troubleshooting steps only for Windows. The documentation assumes the use of Windows VMs throughout, with no parity for Linux SQL Server deployments.
Recommendations
  • Add explicit guidance and examples for backing up SQL Server on Linux-based Azure VMs, including prerequisites and supported scenarios.
  • Reference Linux equivalents for VM agents, backup extensions, and service accounts (e.g., systemd services, Linux backup agents).
  • Provide troubleshooting scripts and tools for Linux environments (e.g., Bash scripts for connectivity tests).
  • Clarify which steps and features are Windows-only, and offer alternative instructions for Linux where possible.
  • Include links to documentation for SQL Server on Linux in Azure, and highlight any differences in backup configuration and management.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by prioritizing Windows VM deployment in the Resource Manager template section, referencing PowerShell for resource group configuration without mentioning Linux/CLI alternatives, and lacking Linux-specific examples or parity in automation and template links. While both Windows and Linux quick-create links are provided in the VM creation steps, subsequent automation and template guidance focus solely on Windows.
Recommendations
  • Include a Resource Manager template example and link for deploying a Linux VM with backup enabled, alongside the Windows template.
  • Provide equivalent CLI (az CLI) or Bash scripting instructions for configuring Azure Backup resource groups, not just PowerShell.
  • Ensure all automation and scripting sections mention both Windows and Linux approaches, or clarify cross-platform compatibility.
  • Add explicit Linux-focused examples/screenshots where applicable, especially in sections demonstrating backup policy customization and resource group naming.
  • Review related content and troubleshooting links to ensure Linux VM scenarios are covered equally.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/guidance-best-practices.md ...s/blob/main/articles/backup/guidance-best-practices.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools, terminology, and examples. PowerShell is frequently mentioned as an automation channel, and Windows-specific backup agents (MARS, DPM/MABS) are referenced without Linux equivalents. There are no explicit Linux or cross-platform CLI examples, and the guidance assumes familiarity with Windows backup paradigms. Linux workloads and tools are not discussed, and Linux-specific backup scenarios, commands, or considerations are missing.
Recommendations
  • Include explicit Linux backup scenarios and examples, such as backing up Linux VMs, files, and databases.
  • Provide Azure CLI and Bash script examples alongside PowerShell, especially for automation and job retry procedures.
  • Mention Linux-compatible backup agents or third-party tools where relevant, and clarify support for Linux workloads.
  • Add guidance for Linux-specific security, encryption, and network considerations (e.g., SELinux, iptables, SSH keys).
  • Ensure parity in describing monitoring and alerting for Linux workloads, including integration with Linux-native tools.
  • Balance references to Windows tools (MARS, DPM/MABS) with Linux alternatives or clarify platform applicability.
GitHub Create Pull Request
← Previous Page 33 of 65 Next →