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 576-600 of 1604 flagged pages
Backup Tutorial - Restore a VM with Azure CLI ...ocs/blob/main/articles/backup/tutorial-restore-disk.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 Reference Windows Links
Summary
While the tutorial is focused on Azure CLI and provides cross-platform, shell-agnostic examples, there is evidence of subtle Windows bias. The documentation references PowerShell and Windows-specific VM documentation before or alongside Linux equivalents, and links to Windows-centric pages (e.g., availability zones for Windows VMs). However, the CLI commands themselves are platform-neutral and most examples use Bash-style syntax, which is common on Linux and macOS.
Recommendations
  • When referencing PowerShell-based documentation, also provide parallel links to Linux CLI or Bash scripting guides for parity.
  • Avoid linking to Windows-specific VM documentation (such as zone-pinned VMs for Windows) without also linking to the equivalent Linux VM documentation.
  • Ensure that any mention of Windows or PowerShell is balanced with Linux/Bash alternatives, especially in introductory or overview sections.
  • Explicitly state that all CLI commands work on Linux, macOS, and Windows, and provide example shell environments if relevant.
  • If referencing scripting or automation, include both Bash and PowerShell script snippets where appropriate.
GitHub Create Pull Request
Backup Upgrade the Microsoft Azure Recovery Services (MARS) agent for Azure Backup ...e-docs/blob/main/articles/backup/upgrade-mars-agent.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 exclusively describes upgrading the MARS agent on Windows environments, referencing Windows-specific tools (Remote Desktop, DPM Console), and does not mention Linux systems, Linux equivalents, or provide any Linux-specific instructions or examples. The screenshots and steps are tailored to Windows workflows, and the 'Next steps' section explicitly refers to backing up Windows machines.
Recommendations
  • Clarify in the introduction whether the MARS agent is Windows-only, or explicitly state platform support.
  • If Linux is supported, add equivalent instructions and examples for Linux environments, including command-line steps and screenshots.
  • Mention Linux backup agent alternatives if MARS is not supported on Linux, and link to relevant documentation.
  • Avoid Windows-centric terminology where possible, or provide cross-platform alternatives.
  • Ensure parity in 'Next steps' by including links or references for Linux backup scenarios.
GitHub Create Pull Request
Backup Tutorial - Back Up SQL Server Databases to Azure ...-docs/blob/main/articles/backup/tutorial-sql-backup.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 focuses exclusively on backing up SQL Server databases on Azure VMs using Windows-based tools and extensions. It references the installation of the AzureBackupWindowsWorkload extension, the creation of a Windows service account (NT Service\AzureWLBackupPluginSvc), and the use of SQLIaaSExtension, all of which are Windows-specific. There are no examples, instructions, or mentions of Linux-based SQL Server VMs, nor any guidance for users running SQL Server on Linux. The documentation implicitly assumes a Windows environment throughout.
Recommendations
  • Add explicit guidance and examples for backing up SQL Server databases running on Linux-based Azure VMs.
  • Document any differences in required extensions, permissions, or service accounts for Linux SQL Server VMs.
  • Include Linux command-line examples (e.g., Bash, systemctl) where relevant, alongside Windows/Powershell instructions.
  • Clarify in prerequisites and throughout the tutorial whether the steps apply only to Windows VMs, and provide links or sections for Linux scenarios.
  • Mention and describe any Linux-specific backup tools or patterns, such as using cron jobs or native Linux agents, if supported.
GitHub Create Pull Request
Backup Use Archive tier .../blob/main/articles/backup/use-archive-tier-support.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 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently presenting Windows-centric tools (Azure Portal and PowerShell) before Linux-friendly alternatives (CLI), and by providing more detailed and step-by-step examples for PowerShell. The 'Get started' instructions in the PowerShell section reference downloading PowerShell from GitHub, which is a Windows-native tool, and the portal instructions are inherently Windows-focused. CLI instructions are present, but are less detailed and appear after PowerShell in the navigation and 'Next steps' links. There is no mention of Linux-specific shell scripting or integration, nor any explicit parity checks for Linux users.
Recommendations
  • Ensure CLI examples are as detailed and comprehensive as PowerShell examples, including step-by-step instructions and troubleshooting output.
  • Present CLI instructions before or alongside PowerShell instructions, especially in 'Next steps' and navigation pivots, to avoid Windows-first ordering.
  • Explicitly mention Linux compatibility and provide guidance for Linux shell environments (e.g., Bash, Zsh), including installation and usage notes.
  • Add parity checks to confirm that all operations possible in PowerShell are also available and documented for CLI.
  • Include sample scripts or automation examples for Linux environments, not just PowerShell.
  • Clarify that Azure CLI is cross-platform and highlight its use for Linux/macOS users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/active-directory-backup-restore.md ...ain/articles/backup/active-directory-backup-restore.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, specifically Windows Server domain controllers. All examples and procedures reference Windows tools (PowerShell, ntdsutil.exe), Windows-specific terminology (DSRM, System State), and Windows Server features. There are no examples or guidance for Linux-based domain controllers, nor mention of cross-platform alternatives. Windows tools and patterns are presented exclusively and before any Linux equivalents (which are absent).
Recommendations
  • Explicitly state that Azure Backup does not support Linux-based Active Directory domain controllers, if that is the case.
  • If Linux-based domain controllers (e.g., Samba AD DC) are supported, provide equivalent backup and restore procedures for Linux environments, including command-line examples and tool references.
  • Include a section comparing Windows and Linux domain controller backup/restore scenarios, clarifying platform limitations.
  • Where PowerShell is used, offer Bash or shell script equivalents if applicable.
  • Reference Linux backup tools (such as rsync, tar, or native Samba backup utilities) if Linux domain controllers are in scope.
  • Clarify in the introduction that the procedures are specific to Windows Server Active Directory, and suggest alternatives for Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-data-lake-storage-backup-configure-quickstart-arm-bicep.md ...ata-lake-storage-backup-configure-quickstart-arm-bicep.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only PowerShell deployment examples for both ARM and Bicep templates, with no mention of Azure CLI, Bash, or Linux-native workflows. This can be interpreted as a Windows bias, as PowerShell is primarily associated with Windows environments, and Azure Cloud Shell supports both PowerShell and Bash. No Linux or cross-platform instructions are provided, nor is Azure CLI usage demonstrated.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell scripts for both ARM and Bicep templates.
  • Explicitly mention that deployment can be performed from Bash in Azure Cloud Shell or from Linux/macOS terminals using Azure CLI.
  • Provide sample Bash scripts or CLI commands for template deployment, ensuring parity for Linux users.
  • Clarify that PowerShell is not required and highlight cross-platform options in the prerequisites and deployment sections.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/back-up-managed-disks-tutorial.md ...main/articles/backup/back-up-managed-disks-tutorial.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily describes backup operations using the Azure portal, which is platform-agnostic, but when mentioning automation or scripting, it lists PowerShell before Azure CLI and does not provide explicit Linux-specific examples or guidance. The only script references are to PowerShell and CLI, with PowerShell mentioned first, and there are no examples or notes about Linux shell usage, nor any mention of Bash or Linux-specific patterns. This ordering and omission suggest a subtle Windows bias.
Recommendations
  • When referencing automation, mention Azure CLI before or alongside PowerShell, and clarify that CLI is cross-platform and works natively on Linux and macOS.
  • Provide explicit Bash/Linux shell examples for common tasks, such as configuring backups or assigning roles, to ensure parity for Linux users.
  • Add notes or tips for Linux users, such as how to install and use Azure CLI on Linux, and clarify any platform-specific differences in scripting or tooling.
  • Ensure that all script references (e.g., role assignment templates) include both PowerShell and Bash/CLI versions, and link to Linux-friendly documentation where appropriate.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-server-vmware.md ...n/articles/backup/backup-azure-backup-server-vmware.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. All operational instructions, examples, and tooling references are exclusively for Windows environments. Steps such as certificate import, registry modifications, and script execution are described using Windows-specific tools (e.g., Certificate Import Wizard, Windows Registry Editor, PowerShell scripts, and Windows file paths). There are no Linux equivalents or alternative instructions for non-Windows platforms, nor is there any mention of Linux support or parity.
Recommendations
  • Provide instructions for performing certificate import and management on Linux systems (e.g., using openssl, update-ca-certificates, etc.).
  • Include Linux-compatible methods for modifying configuration (e.g., environment variables, config files) instead of or alongside Windows Registry edits.
  • Offer Linux shell script equivalents for PowerShell scripts, or clarify if the tooling is Windows-only.
  • Explicitly state platform requirements and limitations (e.g., if MABS is Windows-only, clarify this early in the documentation).
  • Add notes or sections for Linux administrators, even if only to explain why Linux support is not available or to suggest alternatives.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-arm-vms-prepare.md ...b/main/articles/backup/backup-azure-arm-vms-prepare.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides more detailed, step-by-step instructions for installing the VM agent on Windows, including download links, file paths, and verification steps. In contrast, Linux instructions are brief, lacking specific commands or examples, and do not mention verification steps. Windows tools (MSI installer, file paths) are mentioned explicitly, while Linux instructions defer to distribution repositories without concrete guidance. The Windows instructions are presented first in the installation table.
Recommendations
  • Provide explicit Linux installation commands (e.g., apt, yum, zypper) for installing/updating the Azure Linux agent.
  • Include verification steps for Linux agent installation, such as checking the agent version and service status.
  • Present Windows and Linux instructions with equal detail and clarity, possibly alternating which OS is listed first or grouping them together.
  • Mention troubleshooting steps specific to Linux agent installation and operation.
  • Ensure screenshots and examples are OS-neutral or provide both Windows and Linux variants where applicable.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-restore.md ...les/backup/azure-kubernetes-service-cluster-restore.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Azure PowerShell as an alternative method for restoring AKS clusters, without mentioning or providing equivalent CLI (az) or Bash examples. The only alternative workflow linked is PowerShell-specific, and there are no Linux-oriented instructions or examples (such as using Azure CLI or shell scripting). This prioritizes Windows/PowerShell tooling and omits guidance for Linux users, who are common in Kubernetes environments.
Recommendations
  • Add equivalent Azure CLI (az) instructions and examples for restoring AKS clusters, alongside or before PowerShell references.
  • Include Bash shell scripting examples for common restore operations.
  • Explicitly mention cross-platform support and clarify that all steps can be performed on Linux, macOS, and Windows.
  • Provide links to both PowerShell and Azure CLI documentation for restore operations.
  • When referencing alternative methods (e.g., 'You can also restore AKS cluster using...'), list CLI and Bash options before or alongside PowerShell.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-data-protection-use-rest-api-create-update-postgresql-policy.md ...rotection-use-rest-api-create-update-postgresql-policy.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through repeated references to PowerShell objects and patterns, with no mention of Linux-native tools, shell commands, or examples. The only scripting context provided is PowerShell, and there are no CLI (az), Bash, or Linux-specific instructions or examples. This may make the documentation less accessible or intuitive for Linux users, who are a significant portion of the PostgreSQL and Azure user base.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux.
  • Provide sample Bash scripts or curl commands for interacting with the REST API, demonstrating how Linux users can automate policy creation.
  • Replace or supplement references to 'PowerShell objects' with generic JSON or REST API payloads, clarifying that these are not PowerShell-specific.
  • Explicitly mention that the REST API can be used from any platform, and provide guidance for Linux and Mac users.
  • Where PowerShell is referenced, add a parallel section for Bash or CLI usage, ensuring parity in instructions and examples.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-encrypted-vm-troubleshoot.md ...icles/backup/backup-azure-encrypted-vm-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing PowerShell as the only command-line automation method for configuring permissions, without mentioning Linux-native alternatives such as Azure CLI or Bash. No Linux-specific instructions or examples are provided, and PowerShell is mentioned before any cross-platform tools.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell for all automation steps.
  • Explicitly mention that steps can be performed from Linux/macOS environments, not just Windows.
  • Add troubleshooting instructions and examples relevant to Linux VMs, such as common error codes or permission issues specific to Linux.
  • Ensure parity in tool recommendations, listing cross-platform tools before or alongside Windows-specific ones.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-backup-blobs.md ...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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. While the main content is focused on REST API usage (which is cross-platform), the only command-line tool explicitly mentioned for assigning permissions is PowerShell, and 'Azure portal, PowerShell, or REST API' is listed before Azure CLI. There are no Linux-specific examples, nor is Azure CLI shown in any example for the main backup workflow, despite being a common cross-platform tool. The related content section lists Azure PowerShell before Azure CLI, reinforcing a Windows-first pattern.
Recommendations
  • Add explicit Azure CLI examples for all major operations (assigning permissions, configuring backup, validating, deleting) alongside REST API and PowerShell.
  • Mention Azure CLI as an equal alternative to PowerShell and REST API when describing how to assign permissions.
  • Where command-line examples are given, show both PowerShell and Azure CLI syntax, and consider listing CLI first or side-by-side.
  • Add notes or links for Linux/macOS users to clarify that all REST API and Azure CLI steps are fully supported cross-platform.
  • Review ordering in related content and prerequisites to avoid consistently listing Windows tools before cross-platform alternatives.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-exchange-mabs.md ...lob/main/articles/backup/backup-azure-exchange-mabs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Microsoft Azure Backup Server (MABS), which is a Windows-only tool, and all instructions, screenshots, and examples assume a Windows environment (e.g., file paths like C:\Program Files\, use of .exe files, and GUI navigation). There are no Linux equivalents, examples, or mentions of how to perform similar tasks on Linux-based Exchange deployments or with Linux-compatible backup tools. Windows tools and patterns are mentioned exclusively and first throughout.
Recommendations
  • Clarify early in the documentation that MABS is a Windows-only solution and specify platform requirements.
  • Provide guidance or links for Linux-based Exchange alternatives, if applicable, or explicitly state that Linux is not supported.
  • If Azure Backup supports Linux workloads, add parallel documentation or examples for Linux environments.
  • Where possible, mention cross-platform backup tools or Azure-native backup options that work with Linux.
  • Add a comparison table of supported platforms and backup methods to help users quickly assess applicability.
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-09 00:34
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 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, with no mention of Linux equivalents, cross-platform tools, or alternative approaches for non-Windows systems. The use of Windows-specific terminology, tools (MARSAgentInstaller.exe), and UI flows further reinforces the Windows bias.
Recommendations
  • Add a section or cross-reference for backing up Linux system state or equivalent data to Azure, using Azure Backup or other supported methods.
  • Include examples and instructions for Linux environments, such as using Azure Backup Server, Azure CLI, or third-party backup tools compatible with Linux.
  • Clearly state the scope and limitations at the beginning, indicating that the guide is Windows-specific and provide links to Linux backup documentation.
  • Where possible, mention cross-platform backup solutions and provide parity in documentation for both Windows and Linux users.
GitHub Create Pull Request
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows and PowerShell. All examples use PowerShell cmdlets and Windows-style file paths (e.g., C:\), with no mention of Bash, Azure CLI, or Linux-native tools. Even when Linux VMs are referenced, the restoration steps still use PowerShell, which is not native to most Linux environments. There are no Linux shell or Azure CLI examples, and prerequisites and workflow are described in terms of PowerShell usage only.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all steps, especially for Linux VM scenarios.
  • Use platform-agnostic file paths in examples, or show both Windows and Linux paths (e.g., C:\vmencryption_config.json and /home/user/vmencryption_config.json).
  • Explicitly mention and link to Linux-native tools and workflows where possible.
  • Reorganize the documentation so that Linux and Windows workflows are presented in parallel, rather than Windows/PowerShell-first.
  • Clarify which steps require PowerShell and offer alternatives for Linux users (e.g., running PowerShell Core on Linux, or using Azure CLI).
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-09 00:34
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-specific technologies (e.g., SQL Server Management Studio, Visual C++ Redistributable, Windows Server versions, file paths using Windows conventions). There is no mention of Linux support, Linux-based backup scenarios, or equivalent Linux tools. The documentation assumes the reader is operating in a Windows-only context.
Recommendations
  • Explicitly state platform support and limitations (e.g., clarify if MABS is Windows-only or provide Linux support details if available).
  • If Linux is supported, add equivalent instructions and examples for Linux environments (e.g., using sqlcmd or Azure CLI on Linux for database operations).
  • Include Linux file path conventions and tool references where appropriate.
  • Provide troubleshooting steps and known issues relevant to Linux deployments, if applicable.
  • Ensure parity in guidance for both Windows and Linux users, or clearly indicate when features are Windows-exclusive.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by mentioning Windows-specific tools (VSS) before Linux equivalents (fsfreeze) and linking only to Windows VM agent and snapshot extension documentation. There are no Linux-specific examples, links, or detailed instructions, and Linux tooling is referenced only briefly and generically.
Recommendations
  • Provide equivalent links to Linux VM agent and snapshot extension documentation, not just Windows.
  • Include examples or references for Linux backup scenarios, such as how crash-consistent backups interact with Linux filesystems and tools.
  • Mention Linux-specific considerations (e.g., supported distributions, file system types, common backup patterns) alongside Windows details.
  • Ensure that Linux tools (like fsfreeze) are described with equal detail and prominence as Windows tools (like VSS).
  • Add links to Azure documentation for managing Linux VM backups and extensions.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-security-feature.md .../main/articles/backup/backup-azure-security-feature.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 (MABS, DPM, MARS), with no mention of Linux backup agents, Linux-specific procedures, or cross-platform parity. All examples, troubleshooting, and feature descriptions are tailored to Windows environments, and PowerShell commands are referenced without Bash or Linux CLI equivalents. There is no guidance for Linux users or mention of Linux support for these security features.
Recommendations
  • Explicitly state whether these security features are available for Linux workloads and agents.
  • Add examples and procedures for enabling and using security features with Linux-based backup agents, if supported.
  • Include Linux CLI or Bash command equivalents for PowerShell commands and operations.
  • Mention Linux backup tools (such as Azure Backup for Linux VMs or other supported agents) and provide parity in documentation structure and troubleshooting.
  • If features are not supported for Linux, clarify this early in the document and link to relevant Linux backup security documentation.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, with all examples, workflows, and tool references centered around Windows Server, Windows Server Backup, and PowerShell cmdlets. There is no mention of Linux support, Linux backup tools, or equivalent workflows for non-Windows systems. The prerequisites, recovery steps, and backup procedures are exclusively described for Windows, and Windows terminology and tools (such as WinRE, wbadmin, and PowerShell) are used throughout.
Recommendations
  • Clearly state OS support at the beginning, including whether Linux is supported or not.
  • If Azure Backup Server supports Linux, add equivalent Linux backup and recovery workflows, using native Linux tools (e.g., rsync, tar, dd, or Azure Linux agent).
  • Provide Linux-specific examples for backup and recovery, including command-line instructions and file paths.
  • Mention Linux limitations and prerequisites where appropriate.
  • If Linux is not supported, explicitly state this to avoid confusion for cross-platform users.
  • Balance PowerShell/Windows Server Backup references with Linux alternatives (e.g., bash scripts, cron jobs, Linux backup utilities).
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-09 00:34
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 discovering a VM's associated key vault, with no equivalent Linux (bash/Azure CLI) example. Windows encryption tooling (BitLocker) is mentioned before Linux (dm-crypt), and the documentation refers to Windows and PowerShell patterns more frequently. There is a lack of explicit Linux-focused instructions or examples, especially for command-line operations, and screenshots and UI flows do not clarify Linux-specific nuances.
Recommendations
  • Provide Azure CLI and/or bash examples alongside PowerShell for all command-line instructions, especially for tasks like discovering key vault associations.
  • Ensure Linux encryption tooling (dm-crypt) is described with equal detail and prominence as Windows BitLocker, including links to relevant Linux documentation.
  • Add explicit Linux VM agent installation instructions and troubleshooting steps, as Linux agent installation can differ from Windows.
  • Include screenshots or UI notes clarifying any Linux-specific differences in the Azure portal experience.
  • Review all steps to ensure Linux VMs are referenced with equal frequency and clarity as Windows VMs, including in examples, tips, and troubleshooting.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-sharepoint-azure-stack.md .../articles/backup/backup-mabs-sharepoint-azure-stack.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, with all examples, tools, and instructions referencing Windows-specific components (such as CMD, Registry Editor, NT AUTHORITY accounts, and Windows file paths). There is no mention of Linux equivalents, nor any guidance for Linux-based SharePoint deployments or Azure Backup Server usage on Linux. Windows tools and patterns are presented exclusively and first, with no cross-platform consideration.
Recommendations
  • Explicitly state platform requirements and limitations at the start, clarifying that MABS and SharePoint farm protection are Windows-only if that is the case.
  • If Linux support is possible (e.g., for SQL Server or other workloads), provide equivalent Linux instructions, commands, and file paths.
  • Add notes or sections addressing Linux users, including alternatives or workarounds if MABS does not support Linux.
  • Where possible, use platform-neutral terminology and avoid hardcoding Windows paths and registry keys without explanation.
  • Include a comparison table or FAQ clarifying which features/tools are available on Windows vs. Linux.
  • If only Windows is supported, make this explicit and suggest Linux-compatible backup solutions for similar scenarios.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/microsoft-azure-backup-server-protection-v3-ur1.md ...kup/microsoft-azure-backup-server-protection-v3-ur1.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation for Azure Backup Server (MABS) V3 UR1 protection matrix demonstrates a strong Windows bias. Windows workloads and tools are described in detail and presented first, with extensive coverage of Windows-specific features (NTFS, VSS, ReFS, system state, bare metal, deduped volumes, etc.). Linux support is relegated to a separate section with minimal detail, limited to VM-level backup only, and lacks parity in item-level recovery and feature explanations. Windows tools and patterns (Volume Shadow Copy Service, NTFS, ReFS, Windows Management Framework, etc.) are referenced exclusively, with no mention of Linux equivalents or tooling. Powershell and Windows-centric administrative patterns are implied throughout, while Linux backup scenarios and recovery options are not explored.
Recommendations
  • Provide Linux backup examples and scenarios, including supported file systems, distributions, and recovery options.
  • Clarify limitations and feature parity for Linux (e.g., item-level recovery, snapshot types, supported storage containers).
  • Include Linux administrative tools and patterns (e.g., use of native Linux backup agents, CLI commands, integration with Linux file systems like ext4, xfs, btrfs).
  • Present Linux and Windows workloads side-by-side in tables where possible, rather than segregating Linux to a separate section.
  • Explicitly document any differences in backup and recovery workflows between Windows and Linux, and offer guidance for Linux administrators.
  • Reference Linux documentation and best practices for backup and recovery, not just Windows-centric resources.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-matrix-mabs-dpm.md ...main/articles/backup/backup-support-matrix-mabs-dpm.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation for MABS & System Center DPM support matrix is heavily focused on Windows environments. All examples, supported operating systems, deployment scenarios, and backup workflows are exclusively centered around Windows Server and related Microsoft technologies. There is no mention of Linux support, Linux-based workloads, or examples using Linux tools. The documentation assumes Windows as the default and only platform, with no parity or guidance for Linux users.
Recommendations
  • Explicitly state whether Linux servers and workloads are supported or not, and provide guidance for Linux users if support exists.
  • If Linux backup is supported via MABS/DPM or Azure Backup, include equivalent examples, supported scenarios, and configuration steps for Linux environments.
  • Add a section comparing Windows and Linux support, highlighting any limitations or differences.
  • If Linux is not supported, recommend alternative Azure Backup solutions for Linux workloads and link to relevant documentation.
  • Ensure that future updates to the documentation consider cross-platform scenarios and do not assume Windows as the only environment.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/offline-backup-overview.md ...s/blob/main/articles/backup/offline-backup-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric backup tools (MARS Agent, Microsoft Azure Backup Server, System Center Data Protection Manager), with no mention of Linux backup agents or workflows. There are no examples or guidance for Linux environments, and Windows tools are presented as the default or only supported options.
Recommendations
  • Include information about Linux-compatible backup agents or workflows for offline backup to Azure, if available.
  • Provide explicit examples or instructions for performing offline backups from Linux systems, including supported utilities and disk preparation steps.
  • Clarify whether the described offline backup options (Data Box, Import/Export) are supported for Linux workloads, and if so, document any differences or additional steps required.
  • If Linux is not supported, state this clearly to avoid confusion and help users plan accordingly.
  • Ensure future documentation includes parity between Windows and Linux environments, presenting both sets of tools and workflows side-by-side where possible.
GitHub Create Pull Request
← Previous Page 24 of 65 Next →