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 601-625 of 1604 flagged pages
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/blob-backup-configure-quick.md ...ob/main/articles/backup/blob-backup-configure-quick.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 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell as a restore method before Azure CLI, and by referencing PowerShell-specific instructions and tools. There is a lack of explicit Linux-focused examples or parity in command-line tooling, and the ordering suggests a preference for Windows-centric workflows.
Recommendations
  • Provide Linux-specific examples and instructions, especially for command-line operations.
  • List Azure CLI (cross-platform) before PowerShell in restore options to avoid implicit prioritization of Windows tools.
  • Explicitly mention platform compatibility for each tool and provide guidance for both Windows and Linux users.
  • Include bash or shell script examples where appropriate, alongside PowerShell.
  • Ensure that any referenced links or included files also maintain parity between Windows and Linux instructions.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-azure-files-vault-tier-bicep.md ...es/backup/quick-backup-azure-files-vault-tier-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 page demonstrates a Windows bias by exclusively providing PowerShell deployment instructions, referencing the Azure PowerShell module as a prerequisite, and omitting equivalent Azure CLI or Bash examples. The deployment workflow and next steps prioritize PowerShell, with CLI and REST API options mentioned only later and without examples. There is no guidance for Linux/macOS users who may prefer Bash or Azure CLI.
Recommendations
  • Add Azure CLI and Bash deployment instructions alongside PowerShell, including example commands for template deployment.
  • List both PowerShell and CLI tools as prerequisites, with installation links for each.
  • Present cross-platform options equally, avoiding PowerShell-first ordering in step-by-step guides.
  • Ensure all next steps include CLI and Bash alternatives with direct links and examples.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both environments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-vm-bicep-file.md ...lob/main/articles/backup/quick-backup-vm-bicep-file.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 Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. The Bicep template exclusively provisions a Windows VM, with no mention or example for Linux VMs. All deployment and management instructions use Azure PowerShell, with no Azure CLI or Bash alternatives provided. References to VM backup and monitoring link to PowerShell-centric articles, and resource cleanup is described only with PowerShell cmdlets. There is no guidance for Linux VM backup scenarios, nor parity in tooling or example OS images.
Recommendations
  • Add a Linux VM example to the Bicep template, including parameters for Linux images and authentication (e.g., SSH keys).
  • Provide Azure CLI and Bash script equivalents for deployment, backup initiation, monitoring, and cleanup steps.
  • Update references and links to include Linux VM backup documentation and CLI-based workflows.
  • Clearly indicate in the template and instructions how to modify for Linux VMs, including supported images and required parameters.
  • Present Windows and Linux options side-by-side, or alternate which is shown first, to avoid 'windows_first' ordering.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-kubernetes-backup-bicep.md .../main/articles/backup/quick-kubernetes-backup-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 page demonstrates a Windows bias by exclusively providing Azure PowerShell deployment instructions and referencing PowerShell as the primary method for deploying the Bicep template. There are no Linux-specific or cross-platform CLI examples (such as Azure CLI or Bash), and PowerShell is mentioned before other tools both in the prerequisites and deployment steps.
Recommendations
  • Add equivalent Azure CLI (az) deployment instructions for Linux/macOS users alongside the PowerShell example.
  • Explicitly mention that Bicep and Azure CLI are cross-platform and provide links or steps for installing and using them on Linux/macOS.
  • Reorder tool mentions in the introduction and prerequisites to avoid listing Windows/PowerShell tools first, or present all options equally.
  • Include a note or section on how to deploy the Bicep template using Bash or shell scripts for non-Windows environments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-kubernetes-backup-arm.md ...ob/main/articles/backup/quick-kubernetes-backup-arm.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 demonstrates Windows bias by providing only PowerShell examples for deploying the ARM template, referencing Azure PowerShell module installation in the prerequisites, and omitting equivalent Linux/macOS-friendly instructions (such as Bash or Azure CLI). The deployment workflow and tooling are presented from a Windows-centric perspective, with no mention of cross-platform alternatives or parity.
Recommendations
  • Add Azure CLI and Bash examples for template deployment, ensuring instructions are platform-agnostic.
  • Include installation steps for Azure CLI alongside PowerShell in the prerequisites, clarifying cross-platform compatibility.
  • Explicitly state that the deployment steps work on Linux, macOS, and Windows, and provide guidance for each.
  • Reorder or parallelize instructions so that Windows and Linux/macOS tooling are presented together, not with Windows first.
  • Review all referenced articles and links to ensure Linux parity in restore and management workflows.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/scripts/set-system-state-backup-policy.md ...icles/backup/scripts/set-system-state-backup-policy.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 Missing Linux Example Windows First
Summary
The documentation exclusively provides a PowerShell script for managing system state backup policies with the MARS agent, which is a Windows-specific tool. There are no examples or mentions of Linux equivalents, nor any guidance for non-Windows environments. All instructions, tooling, and terminology are centered around Windows and PowerShell, with no cross-platform consideration.
Recommendations
  • Add equivalent scripting examples for Linux environments, using Bash or Python where applicable.
  • Clarify whether the MARS agent or system state backup policy management is supported on Linux, and if not, suggest alternative solutions for Linux users.
  • Include references to Linux backup tools (e.g., rsync, tar, cron jobs) and how similar policies can be managed.
  • Structure documentation to mention both Windows and Linux options, or explicitly state platform limitations at the beginning.
  • Provide parity in step-by-step instructions for Linux users, or link to relevant Linux documentation.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/about-azure-vm-restore.md ...cs/blob/main/articles/backup/about-azure-vm-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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing restore scenarios and examples that focus exclusively on Windows VMs, especially in the context of encrypted VM restores. Only Windows-specific links and PowerShell are mentioned for restoring encrypted VMs, with no mention of Linux equivalents or tools. There are no Linux-specific examples or references, and Windows terminology and tools (such as PowerShell and Microsoft Entra ID) are used without Linux parity.
Recommendations
  • Add equivalent restore instructions and references for Linux VMs, especially for encrypted VM restore scenarios.
  • Include examples or links for restoring encrypted Linux VMs, such as those using Azure Disk Encryption with Linux.
  • When mentioning tools like PowerShell for Windows, also mention or provide Bash/CLI alternatives for Linux.
  • Ensure that documentation for item-level restore and disk restore scenarios explicitly covers both Windows and Linux VMs, noting any differences.
  • Review all scenario tables and ensure Linux is represented equally alongside Windows, with clear guidance for both platforms.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/about-restore-microsoft-azure-recovery-services.md ...kup/about-restore-microsoft-azure-recovery-services.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 for Microsoft Azure Recovery Services (MARS) agent demonstrates a strong Windows bias. All restore options and examples are focused exclusively on Windows environments, referencing Windows Server System State, PowerShell for automation, and Windows-specific tools like robocopy. There is no mention of Linux support, equivalent Linux tools, or cross-platform usage patterns. The prerequisites and instructions assume the user is operating in a Windows context, and there are no examples or guidance for Linux users.
Recommendations
  • Clarify platform support: Explicitly state whether the MARS agent is Windows-only or if Linux is supported, and provide guidance for Linux users if applicable.
  • Add Linux examples: If Linux is supported, include equivalent restore instructions and examples using Linux tools (e.g., rsync, cp) and shell commands.
  • Mention Linux limitations: If the agent does not support Linux, add a note to inform users and suggest alternative Azure backup solutions for Linux workloads.
  • Balance tool references: When recommending tools like robocopy or PowerShell, provide Linux alternatives or note their Windows specificity.
  • Reorganize content: Avoid always listing Windows options first; if cross-platform, alternate or group by OS for parity.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/automation-backup.md ...re-docs/blob/main/articles/backup/automation-backup.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 demonstrates a Windows bias by consistently referencing PowerShell as the primary automation client, especially in example workflows and automation scenarios. PowerShell is mentioned before CLI and other cross-platform tools, and there are no explicit Linux/bash examples or references to Linux-native automation patterns. While the list of supported automation methods includes cross-platform tools, the narrative and examples focus on PowerShell and Windows-centric workflows.
Recommendations
  • Provide explicit bash/CLI examples alongside PowerShell for all automation scenarios.
  • When listing automation clients, alternate or randomize the order, or list CLI before PowerShell to avoid implicit prioritization.
  • Include Linux-native automation tools or scripts (e.g., bash scripts, cron jobs) in example workflows.
  • Highlight cross-platform compatibility in all examples, clarifying which commands/tools work on Linux, macOS, and Windows.
  • Where videos or walkthroughs are provided, ensure at least one demonstrates automation from a Linux environment.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-data-lake-storage-backup-support-matrix.md ...ackup/azure-data-lake-storage-backup-support-matrix.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and the Azure portal as primary configuration methods, with Azure CLI mentioned only as an alternative. There are no explicit Linux-specific examples, nor are Linux tools or workflows highlighted. The ordering and phrasing suggest a preference for Windows-centric tools and patterns, with Linux parity not clearly addressed.
Recommendations
  • Provide explicit Linux-oriented examples and workflows, such as step-by-step instructions using Azure CLI on Linux.
  • Include references to Bash scripting and Linux shell environments where relevant.
  • Ensure that Azure CLI examples are presented before or alongside PowerShell examples, not as an afterthought.
  • Clarify that all features and operations are equally supported on Linux, and highlight any platform-specific considerations.
  • Add troubleshooting or FAQ sections for common Linux-specific issues or scenarios.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-data-lake-storage-configure-backup.md ...les/backup/azure-data-lake-storage-configure-backup.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides detailed instructions for configuring vaulted backup for Azure Data Lake Storage using the Azure portal, PowerShell, and Azure CLI. The PowerShell section is extensive and assumes the use of Azure PowerShell, which is primarily a Windows-centric tool. The prerequisites for PowerShell explicitly mention installation steps for Azure PowerShell, reinforcing a Windows bias. Additionally, PowerShell examples and terminology appear before CLI examples in the zone pivot structure, and there is no mention of Linux-specific shell usage or cross-platform considerations in the PowerShell section. The CLI section is more platform-neutral, but the overall structure and depth of PowerShell coverage suggest a Windows-first approach.
Recommendations
  • Explicitly mention that Azure PowerShell is available on Linux and macOS, and provide installation instructions for those platforms.
  • Include Bash or shell script examples alongside PowerShell where possible, especially for tasks like fetching ARM IDs or manipulating JSON.
  • Ensure that CLI examples are as detailed and comprehensive as PowerShell examples, including step-by-step breakdowns and troubleshooting tips.
  • Add notes or links about using Azure CLI in Linux environments, including any differences in authentication or environment setup.
  • Review the order of presentation to avoid implicit prioritization of Windows/PowerShell over CLI/Linux tools.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/archive-tier-support.md ...docs/blob/main/articles/backup/archive-tier-support.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its focus on Azure Virtual Machines (which are often Windows-based), and by listing PowerShell as a supported client before CLI. There are no explicit Linux-specific examples, nor is there mention of Linux tools or workflows. The examples and screenshots are centered on Azure VM backup, with no reference to Linux VM backup scenarios or Linux-specific recovery workflows.
Recommendations
  • Add explicit examples and guidance for Linux VM backup and recovery, including any differences in archive tier support.
  • Ensure CLI examples (az CLI) are provided and prioritized equally or before PowerShell, as CLI is cross-platform and widely used on Linux.
  • Include screenshots or walkthroughs for Linux VM scenarios, not just Azure VM (Windows) backup.
  • Mention any Linux-specific considerations, such as file system support, agent requirements, or restore limitations.
  • Where possible, clarify that the guidance applies to both Windows and Linux VMs, or note any differences.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-backup-glossary.md ...ocs/blob/main/articles/backup/azure-backup-glossary.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The glossary page demonstrates a Windows bias through frequent references to Windows-specific technologies (VSS, DPM, MABS, MARS agent), and by listing Windows tools and concepts (Azure PowerShell, VSS) before or without Linux equivalents. Application-consistent backup mentions VSS in detail, with Linux only briefly referenced as 'pre or post scripts.' There are no explicit Linux tool examples or parity in explanations for backup agents or system state backup. The documentation also references Azure PowerShell and Windows-specific backup methods more prominently than cross-platform or Linux-native approaches.
Recommendations
  • Include Linux-specific backup technologies and terminology (e.g., LVM snapshots, fsfreeze, etc.) where relevant.
  • Provide parity in explanations for backup agents and system state backup for Linux workloads (e.g., describe how system state backup is handled on Linux).
  • Add explicit Linux CLI examples or references alongside Azure PowerShell and Windows tools.
  • Where Windows tools or concepts are referenced (e.g., VSS, DPM), include Linux equivalents or clarify their applicability.
  • Ensure that cross-platform tools (like Azure CLI) are given equal prominence and example coverage as Windows-centric tools.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-backup-overview.md ...les/backup/azure-kubernetes-service-backup-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through its ordering and references. The 'Related content' section lists PowerShell (Windows-centric) instructions before Azure CLI (cross-platform, but often used on Linux), and the only explicit backup example is for PowerShell. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-native tools or patterns. The documentation does not provide parity in example commands or workflows for Linux users, and the use of PowerShell as the primary example may alienate those on Linux or macOS platforms.
Recommendations
  • Add explicit Bash or Linux shell examples for backup and restore operations alongside PowerShell examples.
  • In 'Related content', list Azure CLI instructions before or alongside PowerShell to emphasize cross-platform support.
  • Include notes or sections clarifying that all operations can be performed on Linux and macOS, not just Windows.
  • Reference Linux-native tools or patterns where relevant, and avoid implying PowerShell is the default or preferred method.
  • Ensure screenshots and walkthroughs use both Windows and Linux environments where possible.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-backup-concept.md ...kup/azure-kubernetes-service-cluster-backup-concept.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias, primarily through the ordering and emphasis of tooling. In the 'Next steps' section, Azure PowerShell is mentioned alongside or before Azure CLI, and there is no mention of Bash, Linux shell, or cross-platform scripting. No explicit Linux/Unix-specific examples or guidance are provided, and the documentation does not clarify that Azure CLI is cross-platform or provide parity examples for Linux users. The focus on Azure portal and PowerShell, both of which are more familiar to Windows administrators, may leave Linux users underserved.
Recommendations
  • Ensure that Azure CLI examples are presented before or alongside PowerShell, and clarify that Azure CLI is cross-platform.
  • Include explicit Linux/Bash shell examples where relevant, especially for command-line operations.
  • Add notes or sections highlighting Linux/macOS compatibility and any OS-specific considerations.
  • Balance references to PowerShell and Azure CLI in 'Next steps' and throughout the documentation.
  • Where PowerShell scripts are provided, offer equivalent Bash or shell script examples for Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-backup-support-matrix.md ...azure-kubernetes-service-cluster-backup-support-matrix.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. While the AKS Backup Extension itself only supports Linux-based node pools (Ubuntu or Azure Linux), the 'Next steps' section lists Azure PowerShell as a primary method for backup and restore, which is traditionally a Windows-centric tool. Azure CLI and Terraform are also mentioned, but Azure PowerShell is listed before Bicep and Terraform, and there are no explicit Linux shell (bash) examples or references to Linux-native tools. There is no mention of Linux-specific command-line usage or scripting patterns, and no examples for Linux users are provided. The documentation does clarify that Windows node pools are not supported, but does not offer guidance or parity for Linux users in terms of tooling or examples.
Recommendations
  • Add explicit Linux shell (bash) examples for backup and restore operations, especially using Azure CLI.
  • Clarify that Azure PowerShell is cross-platform, but highlight Azure CLI and bash scripting as primary options for Linux users.
  • Reorder the 'Next steps' tooling list to put Azure CLI and Terraform before Azure PowerShell, reflecting the Linux-first support of the AKS Backup Extension.
  • Include a note or section for Linux users, outlining recommended tools and usage patterns.
  • Provide sample scripts or walkthroughs for Linux environments, including automation via bash or other Linux-native tools.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-backup-using-cli.md ...p/azure-kubernetes-service-cluster-backup-using-cli.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page is primarily focused on Azure CLI usage, which is cross-platform. However, there is evidence of Windows bias in several areas: PowerShell is mentioned as an alternative before Linux equivalents, and a key example for creating a private endpoint uses PowerShell-style syntax (backticks for line continuation, variable assignment with $), which is specific to Windows/PowerShell. No Bash or Linux shell equivalents are provided for these commands, and the documentation does not clarify how Linux users should adapt these steps. The mention of PowerShell as an alternative is presented before any reference to Bash or Linux shells.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell-specific examples, especially for multi-line commands and variable assignment.
  • When referencing alternative tooling, mention Bash/Linux shell usage equally and not only PowerShell.
  • Avoid using PowerShell-specific syntax (such as backticks for line continuation and $ for variable assignment) in generic documentation, or provide both PowerShell and Bash versions side by side.
  • Add explicit notes or tabs for Linux/Mac users where command syntax or environment differs.
  • Ensure that all steps can be followed on Linux without requiring translation from PowerShell syntax.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-backup.md ...cles/backup/azure-kubernetes-service-cluster-backup.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing the Azure portal and Azure PowerShell for backup and restore operations, with no mention of Azure CLI or Linux-native tools. PowerShell is referenced as the alternative automation method, and examples or guides for Linux users (such as Bash scripts or Azure CLI commands) are missing. The documentation does not provide parity for Linux users, who are likely to use Azure CLI or shell scripting for automation.
Recommendations
  • Add Azure CLI examples for all backup and restore operations alongside PowerShell instructions.
  • Explicitly mention Linux and macOS compatibility for command-line instructions.
  • Provide Bash script samples for deploying backup hooks and configuring AKS backup.
  • Ensure that references to automation tools (PowerShell, CLI) are presented together, not with Windows tools first.
  • Include screenshots or walkthroughs for Linux environments where relevant.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/back-up-azure-stack-hyperconverged-infrastructure-virtual-machines.md ...e-stack-hyperconverged-infrastructure-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools, commands, and patterns throughout. PowerShell commands are used for agent deployment and firewall configuration, with no Linux equivalents or instructions. The prerequisites and backup procedures focus on Windows features (Hyper-V, VHD, Windows authentication methods), and Linux support is mentioned only briefly, with no detailed steps or examples. All screenshots and UI references are for Windows-based MABS consoles, and there are no Linux-specific walkthroughs or troubleshooting guidance.
Recommendations
  • Provide Linux-specific backup and recovery examples, including command-line instructions for agent deployment and configuration.
  • Include equivalent Linux firewall configuration steps (e.g., using iptables or firewalld) for agent communication.
  • Clarify any differences in the backup process for Linux VMs, such as limitations or required settings.
  • Add screenshots or UI references for Linux environments if applicable, or explicitly state that the MABS console is Windows-only.
  • Expand the Linux prerequisites section with step-by-step guidance for supported distributions and agent installation.
  • List Linux authentication methods and any required configuration for workgroup or untrusted domain scenarios.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/back-up-hyper-v-virtual-machines-mabs.md ...ticles/backup/back-up-hyper-v-virtual-machines-mabs.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 is heavily focused on Windows environments, specifically Hyper-V on Windows Server, and Microsoft Azure Backup Server (MABS). Windows-specific tools, features, and patterns (such as VSS, NTLM, registry keys, Hyper-V integration services, and Windows Server roles) are mentioned throughout, often without Linux equivalents or alternatives. Linux support is referenced briefly and only in passing, with no detailed instructions or examples for Linux VMs. Item-level recovery is explicitly stated as available only for Windows Server VMs, and all step-by-step examples and screenshots are for Windows environments.
Recommendations
  • Provide detailed instructions and examples for backing up and restoring Linux VMs, including any differences in process, limitations, and supported features.
  • Include Linux-specific prerequisites and troubleshooting steps, such as required agents, supported file systems, and integration with Linux guest OS.
  • Clarify which features (e.g., item-level recovery, VSS-based backups) are available for Linux VMs and suggest Linux-native alternatives where applicable.
  • Add screenshots and walkthroughs for Linux VM backup and recovery operations.
  • Mention Linux authentication and security considerations (e.g., SSH keys, Linux user permissions) where relevant.
  • Clearly indicate Windows-only features and provide parity or workarounds for Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/back-up-file-data.md ...re-docs/blob/main/articles/backup/back-up-file-data.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 for backing up file data with MABS demonstrates a Windows bias. All instructions and terminology are centered around Windows environments and tools (e.g., MABS console, Data Deduplication, Volume Shadow Copy Service, SAN hardware snapshots, tape libraries), with no mention of Linux-specific procedures, commands, or considerations. There are no Linux examples, and prerequisites and recovery steps assume Windows-only features and patterns.
Recommendations
  • Add explicit instructions and examples for backing up Linux machines with MABS, including agent installation and supported file systems.
  • Clarify which features (e.g., deduplication, VSS, tape backup) are available or not available for Linux clients.
  • Provide Linux command-line examples (e.g., shell commands) for agent deployment, backup initiation, and recovery, alongside Windows/Powershell equivalents.
  • Include a support matrix or table that highlights differences and limitations between Windows and Linux backup/recovery with MABS.
  • Mention any Linux-specific requirements or troubleshooting steps, such as permissions, SELinux/AppArmor considerations, or supported distributions.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-architecture.md ...-docs/blob/main/articles/backup/backup-architecture.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 page exhibits a strong Windows bias. Backup methods and agents are described primarily for Windows environments, with the MARS agent and DPM/MABS tools only supporting Windows. Linux is explicitly mentioned as unsupported for direct backup via MARS, and there are no Linux-specific backup examples, agents, or workflows presented. Windows tools and patterns (VSS, MARS, DPM, MABS) are referenced throughout, with no mention of Linux equivalents or alternatives. The documentation consistently presents Windows scenarios first and in greater detail, while Linux support is either omitted or only referenced in passing (e.g., managed disks for Linux VMs).
Recommendations
  • Add explicit sections and examples for Linux backup scenarios, including supported agents, workflows, and limitations.
  • Clarify Linux support in tables and feature matrices, not just as exclusions.
  • If direct backup for Linux is unsupported, suggest alternative approaches (e.g., using Azure VM backup extension, third-party tools, or scripts for Linux).
  • Include parity in architecture diagrams and step-by-step instructions for Linux VMs and workloads.
  • Reference Linux-specific documentation and tools where applicable (e.g., Azure CLI, shell scripts, cron jobs for scheduling backups).
  • Ensure that Linux and Windows scenarios are presented with equal prominence and detail, or clearly state any limitations upfront.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-alternate-dpm-server-troubleshoot.md ...ckup/backup-azure-alternate-dpm-server-troubleshoot.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 is heavily focused on Microsoft Azure Backup Server (MABS), which is a Windows-only product. All troubleshooting steps and error messages reference Windows Server, Windows Client, and tools such as the Azure Backup agent and DPM (Data Protection Manager), which are not available for Linux. There are no examples, recommendations, or troubleshooting steps for Linux systems or cross-platform backup solutions.
Recommendations
  • Clarify in the introduction that MABS is a Windows-only solution and mention alternatives for Linux environments.
  • Provide links or references to Azure backup solutions for Linux (e.g., Azure Backup for Linux VMs, Azure Recovery Services for Linux).
  • Include troubleshooting steps or error messages relevant to Linux-based backup scenarios, if applicable.
  • Ensure parity in documentation by offering guidance for both Windows and Linux users where Azure Backup is supported.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-about-mars.md ...s/blob/main/articles/backup/backup-azure-about-mars.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 the MARS agent is heavily Windows-centric. All backup and recovery scenarios explicitly reference Windows files, folders, volumes, and system state. There is no mention of Linux support, examples, or tools. Windows-specific technologies like VSS (Volume Shadow Copy Service) and USN change journal are referenced without Linux equivalents or alternatives. The installation and operation instructions assume a Windows environment, with no guidance for Linux users.
Recommendations
  • Clearly state platform support at the beginning (e.g., if MARS agent is Windows-only, make this explicit).
  • If Linux is supported, add equivalent examples and instructions for Linux systems, including installation, configuration, and backup/recovery scenarios.
  • Mention Linux backup tools or patterns if applicable, or provide links to Azure Backup solutions for Linux.
  • Avoid using Windows-specific terminology (e.g., VSS, USN journal) without clarifying platform applicability.
  • Provide a comparison table of supported features and limitations for Windows vs. Linux.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-alternate-dpm-server.md ...n/articles/backup/backup-azure-alternate-dpm-server.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively describes recovery using Azure Backup Server and System Center Data Protection Manager (DPM), which are Windows-only tools. All steps, screenshots, and terminology are specific to the Windows ecosystem, with no mention of Linux equivalents, CLI options, or cross-platform alternatives. There are no examples or guidance for Linux-based recovery scenarios.
Recommendations
  • Add guidance for recovering data from Linux-based systems, including supported backup agents and workflows.
  • Include CLI-based recovery instructions (e.g., Azure CLI, REST API) that work across platforms.
  • Mention cross-platform backup and recovery options available in Azure, such as MARS agent support for Linux or Azure Backup for Linux VMs.
  • Provide parity in examples and screenshots for Linux environments where applicable.
  • Clarify platform limitations and direct Linux users to relevant documentation or tools.
GitHub Create Pull Request
← Previous Page 25 of 65 Next →