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 901-925 of 1604 flagged pages
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: 2025-08-21 00:01
Reviewed by: Unknown
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-specific tools (VSS) and PowerShell are mentioned first and in detail, while Linux equivalents are referenced only briefly or generically (e.g., 'pre/post scripts' and 'freeze' tool). There are no concrete Linux command/script examples, and guidance for Linux is less prescriptive. The restore example specifically references PowerShell for managed disk restores, with no Linux CLI or automation alternatives provided.
Recommendations
  • Provide Linux CLI (az CLI) and shell script examples alongside PowerShell examples for backup and restore operations.
  • Mention Linux tools (e.g., LVM snapshots, fsfreeze) with equal detail as VSS for Windows.
  • Include step-by-step Linux backup/restore automation workflows, not just generic references to 'pre/post scripts'.
  • Present Windows and Linux instructions in parallel, rather than listing Windows first.
  • Clarify any differences in agent/extension installation and configuration for Linux VMs.
  • Add troubleshooting and best practices sections specific to Linux environments.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/blob-backup-configure-manage.md ...b/main/articles/backup/blob-backup-configure-manage.md
High Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily describes backup configuration and management using the Azure Portal, which is platform-agnostic. However, in the 'Related content' section, Azure PowerShell is listed before Azure CLI and REST API, suggesting a Windows-first approach. There are no explicit Linux-specific examples, nor are Linux command-line tools or patterns mentioned. The documentation does not provide parity in examples for Linux users, such as Bash scripts or CLI walkthroughs, and omits references to Linux desktop environments when describing portal navigation.
Recommendations
  • List Azure CLI examples before or alongside Azure PowerShell to avoid Windows-first ordering.
  • Add explicit step-by-step examples using Azure CLI for all major backup and restore operations, not just in related content.
  • Include Bash script samples for automating backup tasks on Linux.
  • Mention that the Azure Portal is accessible from any OS and clarify any platform-specific differences if they exist.
  • Where screenshots are shown, note that the UI is identical across platforms and browsers.
  • Ensure REST API examples include curl commands for Linux users.
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: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits Windows bias by referencing PowerShell as the restore method for encrypted VMs, and by only linking to Windows-specific disk encryption documentation. There are no Linux-specific restore examples, nor are Linux disk encryption scenarios mentioned. The restore scenarios table and linked articles focus on Windows tools and patterns, omitting Linux equivalents.
Recommendations
  • Include Linux-specific restore instructions and examples, especially for encrypted VMs (e.g., using CLI or Azure portal for Linux VMs).
  • Add links to Linux disk encryption documentation (such as Azure Disk Encryption for Linux).
  • Mention Linux restore scenarios explicitly in tables and descriptions, ensuring parity with Windows.
  • Provide sample commands for both PowerShell (Windows) and Bash/CLI (Linux) where applicable.
  • Clarify which restore options and features are available for Linux VMs, and note any differences.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-arm-restore-vms.md ...b/main/articles/backup/backup-azure-arm-restore-vms.md
High Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows VM examples, referencing Windows-specific tools and patterns (such as PowerShell and bcdedit), and omitting equivalent Linux-focused guidance or examples. Linux scenarios are only briefly mentioned, with minimal actionable detail, and no Linux command-line or tool examples are provided.
Recommendations
  • Provide Linux-specific examples alongside Windows ones, especially for restore operations, disk attachment, and post-restore steps.
  • Include Linux command-line (e.g., Bash, Azure CLI) and tool usage (such as cloud-init, SSH, or Linux disk mounting) in relevant sections.
  • Balance references to Windows and Linux documentation links (e.g., for attaching disks, resetting passwords, or configuring networking).
  • Where PowerShell is mentioned, also provide equivalent Azure CLI or Bash scripts for Linux users.
  • In post-restore troubleshooting, add Linux-specific recovery steps (e.g., using GRUB, resetting SSH keys, fixing fstab, or re-enabling cloud-init).
  • Explicitly call out differences in restore workflows or limitations for Linux VMs, not just Windows.
  • Ensure that screenshots and UI walkthroughs are not exclusively Windows-centric, and clarify when steps are OS-agnostic.
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: 2025-08-21 00:01
Reviewed by: Unknown
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 usage. All examples are provided exclusively in PowerShell, with Windows file paths (e.g., C:\), and there is no mention of Bash, Azure CLI, or Linux-native tooling. Even when Linux VMs are referenced, the instructions and code samples remain PowerShell-centric, assuming the user is running PowerShell (likely on Windows) and using Windows-style file handling. There are no Linux command-line examples or guidance for users who manage Azure resources from Linux environments.
Recommendations
  • Provide equivalent examples using Azure CLI (az) and Bash scripts for Linux users.
  • Include Linux file path examples (e.g., /home/user/vmencryption_config.json) alongside Windows paths.
  • Clarify which steps are OS-agnostic and which are specific to Windows or Linux.
  • Add a section or callouts for performing these operations from a Linux or cross-platform environment.
  • Reference cross-platform tools and patterns (e.g., Azure Cloud Shell, which supports both PowerShell and Bash).
  • Ensure that Linux VM scenarios are given equal prominence and not treated as an afterthought.
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: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides general guidance for backing up and restoring encrypted Azure VMs, mentioning both Windows and Linux support. However, when it comes to practical examples and command-line instructions, only PowerShell commands are provided (e.g., for identifying a VM's associated key vault), with no equivalent Linux (Bash/CLI) examples. Additionally, Windows tools and terminology (BitLocker, PowerShell) are mentioned before their Linux equivalents (dm-crypt), and there is a lack of parity in step-by-step instructions for Linux users.
Recommendations
  • Add Bash/Azure CLI examples alongside PowerShell commands for all VM and Key Vault operations.
  • When describing encryption technologies, mention Linux (dm-crypt) first or equally with Windows (BitLocker), and provide links to relevant Linux documentation.
  • Ensure all procedural steps (such as identifying a VM's key vault, setting access policies) include both Windows and Linux command-line instructions.
  • Review screenshots and UI instructions to ensure they are OS-neutral or provide notes for Linux-specific considerations.
  • Explicitly state that both Windows and Linux VMs are supported in all relevant sections, and avoid implying Windows is the default or primary platform.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/restore-azure-encrypted-virtual-machines.md ...les/backup/restore-azure-encrypted-virtual-machines.md
High Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias by referencing Windows-specific tools and patterns before Linux equivalents. For example, the OS disk swap is linked only to Windows documentation, and PowerShell is suggested for VM creation without mentioning Linux alternatives (such as Azure CLI or Bash). Linux-specific restore steps are relegated to a separate section, and there are no Linux command examples or references to Linux-native tooling. Windows terminology and links appear first or exclusively in several places.
Recommendations
  • Provide Linux-specific examples alongside Windows ones, such as using Azure CLI or Bash scripts for VM creation from restored disks.
  • Include links to both Windows and Linux OS disk swap documentation.
  • Mention Linux tools and patterns (e.g., cloud-init, SSH) where relevant, not just PowerShell.
  • Ensure that restore steps for Linux VMs are integrated throughout the guide, not isolated in a separate section.
  • Add parity in troubleshooting and next steps, referencing both Windows and Linux agent/extension issues.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sap-hana-database-instances-restore.md ...articles/backup/sap-hana-database-instances-restore.md
High Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by primarily referencing the Azure portal (a GUI tool most familiar to Windows users), mentioning PowerShell/CLI scripts for permissions without providing explicit Linux (bash) examples, and omitting any Linux-specific command-line workflows for mounting or restoring disks. There are no examples or instructions tailored for Linux administrators, despite SAP HANA commonly running on Linux.
Recommendations
  • Add explicit Linux command-line (bash) examples for mounting and restoring disks, such as using 'lsblk', 'mount', or 'fdisk' to identify and mount attached disks.
  • Provide Azure CLI examples in bash syntax, not just PowerShell, for assigning permissions and managing resources.
  • Include a section or callouts specifically for Linux administrators, detailing steps that would be performed on a Linux VM (e.g., mounting disks, updating fstab, checking disk status).
  • Ensure parity in screenshots and instructions for both Windows and Linux environments, or clarify when steps are OS-agnostic.
  • Avoid referencing PowerShell or Windows tools/scripts as the default; instead, present both PowerShell and bash/CLI alternatives side by side.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-arm-restore-vms.md ...b/main/articles/backup/backup-azure-arm-restore-vms.md
High Priority View Details →
Scanned: 2025-08-20 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a Windows bias in several ways: Windows and PowerShell are referenced more frequently and often before Linux equivalents. Many example links and guidance for advanced scenarios (e.g., restoring with custom images, availability sets, network configurations) point to Windows-specific documentation or PowerShell usage, while Linux or cross-platform alternatives are missing or only mentioned in passing. Some post-restore steps and troubleshooting commands are provided only for Windows (e.g., bcdedit, netdom), with no Linux equivalents or guidance.
Recommendations
  • Provide parallel Linux examples and links (e.g., for restoring VMs with custom images, availability sets, or special network configurations, include Linux documentation and CLI/Bash examples).
  • When referencing PowerShell, also provide Azure CLI or Bash alternatives for all major operations, especially for VM creation and disk attachment.
  • In post-restore steps, include Linux-specific troubleshooting and recovery guidance (e.g., how to reset SSH keys, repair bootloaders, or rejoin a Linux VM to a domain or directory service).
  • Avoid linking only to Windows-specific documentation (such as /windows/ URLs); always include or prioritize Linux or cross-platform links where available.
  • Explicitly mention any differences or additional steps required for Linux VMs in scenarios such as restoring SQL VMs, domain controllers, or VMs with special configurations.
  • Ensure that screenshots and UI walkthroughs are not Windows-centric, and clarify when steps are identical for Linux VMs.
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: 2025-08-20 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by providing restore examples and links that are exclusively or primarily focused on Windows VMs. In the 'Restore an encrypted VM' scenario, only Windows-specific encryption scenarios and PowerShell are mentioned, with no reference to Linux VMs or their restore/encryption processes. There are no Linux-specific examples, tools, or documentation links, and the restore process references (such as PowerShell) are Windows-centric.
Recommendations
  • Include equivalent Linux VM restore scenarios, especially for encrypted VMs, with links to relevant Linux documentation.
  • Provide examples and instructions for restoring both Windows and Linux VMs, including any differences in process or tooling.
  • Mention and link to Linux-native tools (such as Bash/CLI commands) alongside PowerShell where applicable.
  • Ensure that documentation for features like Item Level Restore (ILR) and disk encryption covers both Windows and Linux use cases.
  • Balance references to Windows and Linux in tables and scenario descriptions, so Linux users can easily find relevant guidance.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sap-hana-database-instances-restore.md ...articles/backup/sap-hana-database-instances-restore.md
High Priority View Details →
Scanned: 2025-08-20 00:01
Reviewed by: Unknown
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 PowerShell/CLI scripts for permission management, without providing explicit Linux shell or command-line examples. There is no mention of Linux-specific tools or workflows, and the instructions assume a GUI or PowerShell-centric approach, which may not align with common Linux administration practices for SAP HANA.
Recommendations
  • Include explicit Linux shell (bash) command examples for tasks such as mounting disks, managing permissions, and interacting with Azure resources (e.g., using Azure CLI in bash).
  • Provide parity in instructions for both Windows (PowerShell) and Linux (bash/CLI), ensuring that Linux administrators can follow along without needing to translate PowerShell commands.
  • Mention Linux-native tools and workflows (such as using SSH, Linux mount commands, and file system management) where relevant, especially for mounting and restoring disks.
  • Clarify that the procedures are applicable to both Windows and Linux VMs, or specify any OS-specific considerations.
  • Add screenshots or terminal output examples from Linux environments where GUI steps are not available or not preferred.
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: 2025-08-20 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation references Windows-specific tools (Volume Shadow Copy Service - VSS) before mentioning the Linux equivalent (*fsfreeze*), and links to Windows-specific agent and extension documentation without providing Linux equivalents. There are no Linux-specific examples or links, and the pattern of mentioning Windows first suggests a subtle Windows bias.
Recommendations
  • When mentioning consistency mechanisms, present Linux and Windows tools in parallel (e.g., 'Volume Shadow Copy Service (VSS) for Windows or fsfreeze for Linux').
  • Provide links to both Windows and Linux VM Agent and snapshot extension documentation.
  • Include explicit Linux examples or scenarios, such as referencing the Linux VM agent or snapshot extension documentation.
  • Ensure that any references to scripts or tools (such as pre/post scripts for Linux) are accompanied by links or further explanation, matching the detail given for Windows.
  • Review the order of presentation to avoid always listing Windows tools or documentation first.
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: 2025-08-20 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing more detailed and prioritized information for Windows VMs, especially regarding snapshot consistency and backup tooling. Windows-specific tools (VSS, PowerShell) are mentioned first or exclusively, while Linux guidance is less detailed and relies on users to provide their own scripts. There are no concrete Linux command examples, and automation/restoration guidance is PowerShell-centric.
Recommendations
  • Provide Linux command-line examples (e.g., using Azure CLI or Bash) alongside or before PowerShell examples, especially for restore operations.
  • Offer more detailed, step-by-step Linux backup and restore procedures, including sample pre/post scripts for common applications (e.g., MySQL, PostgreSQL).
  • Balance the explanation of snapshot consistency mechanisms by giving equal detail to Linux (e.g., describe the 'freeze' tool and common Linux application consistency strategies).
  • When referencing tools (e.g., VSS for Windows), also mention and explain Linux equivalents (e.g., fsfreeze, LVM snapshots) and their integration with Azure Backup.
  • Ensure that best practices and troubleshooting sections include Linux-specific advice and not just Windows/PowerShell-centric guidance.
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: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily Windows-centric. All restore options and examples are described in the context of Windows environments, referencing Windows-specific tools (robocopy, Windows Server Backup utility) and PowerShell for automation. There are no mentions of Linux support, tools, or examples, and the documentation implicitly assumes the user is operating on Windows.
Recommendations
  • Clarify early in the documentation whether the MARS agent is Windows-only or if Linux is supported. If Linux is not supported, state this explicitly.
  • If Linux support is available or planned, provide equivalent Linux examples for restore operations, including command-line instructions and references to Linux-native tools.
  • Avoid referencing Windows tools (e.g., robocopy, Windows Server Backup) exclusively; if alternatives exist for other platforms, mention them.
  • When describing automation, include both PowerShell and bash (or other Linux shell) examples if cross-platform support exists.
  • Structure documentation sections so that platform-specific instructions are clearly separated, and avoid always presenting Windows first if multiple platforms are supported.
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: 2025-08-19 00:01
Reviewed by: Unknown
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 instructions use Windows tools (PowerShell, ntdsutil.exe), and there are no references to Linux-based Active Directory alternatives or cross-platform scenarios. The documentation assumes the use of Windows Server and does not provide parity for Linux administrators or mention Samba or other open-source AD-compatible solutions.
Recommendations
  • Include a section or note clarifying that the instructions are specific to Windows Server Active Directory, and mention whether Linux-based AD-compatible solutions (e.g., Samba) are supported by Azure Backup.
  • If Azure Backup or related tools support Linux-based domain controllers (e.g., Samba AD DC), provide equivalent backup and restore instructions for those environments.
  • Where PowerShell scripts are provided, offer equivalent command-line examples for Linux (if applicable), or explicitly state if no equivalent exists.
  • Reference Linux tools or methods (such as using rsync, tar, or native Samba backup tools) where appropriate, or clarify their (lack of) support.
  • Ensure that any mention of tools like ntdsutil.exe or DSRM is accompanied by a note about their Windows-specific nature and alternatives (if any) for Linux.
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: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the tool for restoring encrypted VMs, and by providing links and examples that are exclusively for Windows VM encryption scenarios. There are no Linux-specific restore examples, nor are Linux tools or workflows mentioned. The documentation also references Windows-specific features (e.g., Microsoft Entra ID integration for Windows disk encryption) without Linux equivalents or guidance.
Recommendations
  • Add explicit examples and guidance for restoring Linux VMs, especially for encrypted Linux VMs, including relevant tools (e.g., Azure CLI, Bash scripts) and links to Linux documentation.
  • Where PowerShell is mentioned for VM creation/restoration, also provide equivalent Azure CLI or Bash commands for Linux users.
  • Include links to documentation about Linux disk encryption and restore processes, ensuring parity with the Windows-focused links.
  • In scenario tables and explanations, clarify when steps or tools are Windows-specific, and provide Linux alternatives where applicable.
  • Review all restore scenarios to ensure both Windows and Linux workflows are described with equal prominence and detail.
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: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page lists PowerShell as a supported client before CLI, and does not provide any explicit Linux-specific examples or mention Linux tools. The examples and workload focus are centered on Azure Virtual Machines, SQL Server, and SAP HANA in Azure VMs, which are often associated with Windows environments. There are no Linux command-line examples or references to Linux-native tools, and the documentation does not clarify parity or differences for Linux users.
Recommendations
  • Provide explicit Linux CLI examples alongside or before PowerShell examples, especially in sections referencing client tools.
  • Clarify whether all features and workflows are supported equally on Linux and Windows, and note any differences.
  • Include references to Linux-native tools or scripts where applicable, and ensure that CLI instructions are cross-platform.
  • Add a section or FAQ addressing common Linux user scenarios or concerns, such as using Azure CLI on Linux to manage Archive tier operations.
  • Ensure that documentation screenshots and walkthroughs are not exclusively from Windows environments.
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: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The glossary demonstrates a Windows bias by referencing Windows-specific technologies (e.g., VSS, DPM, MABS, System State backup, Bare metal backup) and tools (Azure PowerShell, Windows-specific documentation links) more frequently and in greater detail than Linux equivalents. In the few places where Linux is mentioned (e.g., application-consistent backup), it is treated as an afterthought or parenthetical. There are no explicit Linux-focused examples, tools, or documentation links, and Windows patterns and terminology are introduced first or exclusively.
Recommendations
  • Add Linux-specific backup concepts and terms (e.g., LVM snapshots, fsfreeze, pre/post backup scripts) to the glossary.
  • Where Windows-specific tools or technologies are mentioned (e.g., VSS, DPM, MABS, System State backup), provide Linux equivalents or note their absence.
  • Include references and links to Linux backup documentation and tools (e.g., Azure CLI usage on Linux, Linux agent documentation).
  • When describing cross-platform features (like application-consistent backup), give equal detail and examples for both Windows and Linux.
  • Avoid always listing Windows tools or patterns first; alternate or group by platform where appropriate.
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: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing a dedicated link and mention for Azure PowerShell usage (a Windows-centric tool) both in the introduction and in the 'Next steps' section, while not offering equivalent guidance or links for Linux-native tools such as Azure CLI. There are no command-line examples for Linux users, and the only shell command shown is 'kubectl', which is cross-platform but not Azure-specific. The documentation does not mention or link to Azure CLI instructions for backup/restore, nor does it provide Bash or Linux terminal examples, leading to a lack of parity for Linux users.
Recommendations
  • Add equivalent Azure CLI instructions and links alongside all PowerShell references, both in the introduction and 'Next steps'.
  • Provide example commands for both PowerShell and Bash/Azure CLI where relevant, especially for backup and restore operations.
  • Ensure that any references to Azure PowerShell are paired with Azure CLI alternatives, and do not present PowerShell as the default or only automation option.
  • Consider adding a section or callout for Linux/macOS users, clarifying that all operations can be performed using Azure CLI and providing direct links to those instructions.
  • Review screenshots and UI instructions to ensure they are not Windows-specific, and clarify where steps are platform-agnostic.
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: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools and concepts (such as Volume Shadow Copy Service, Data Deduplication, and the MABS console UI), and by omitting any Linux-specific instructions or examples. There are no mentions of Linux client support, Linux command-line procedures, or Linux-specific backup/recovery considerations, despite the stated intent to support both server and client machines.
Recommendations
  • Include explicit information about Linux support: clarify whether MABS supports Linux clients/servers, and if so, provide setup and usage instructions.
  • Add Linux-specific examples for installing the protection agent, configuring protection groups, and performing backup and recovery operations (e.g., using command-line tools or scripts).
  • Mention Linux equivalents for Windows features (such as VSS and Data Deduplication), or clearly state if such features are unavailable or handled differently on Linux.
  • Ensure that UI instructions are supplemented with CLI or cross-platform alternatives where possible.
  • If Linux is not supported, clearly state this limitation at the beginning of the documentation.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-sql.md ...s/blob/main/articles/backup/backup-azure-backup-sql.md
High Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented toward Windows environments, specifically focusing on Data Protection Manager (DPM), which is a Windows-only tool. All instructions, screenshots, and workflows assume the use of Windows Server, Windows-based SQL Server, and DPM. There are no examples or guidance for Linux-based SQL Server deployments, nor are alternative tools or methods for Linux environments mentioned. The only automation reference is to PowerShell, a Windows-centric scripting environment.
Recommendations
  • Add explicit mention of Linux support or limitations for SQL Server backup to Azure, clarifying whether DPM or equivalent solutions exist for Linux.
  • Provide parallel instructions or references for backing up SQL Server on Linux (e.g., using Azure Backup Server, Azure CLI, or native SQL tools).
  • Include examples and screenshots for Linux-based SQL Server environments, if supported.
  • Reference cross-platform automation options (such as Azure CLI, REST API, or Bash scripts) alongside or instead of PowerShell.
  • Clearly state in the prerequisites and introduction that the documented workflow is specific to Windows/DPM, and link to Linux-specific documentation if available.
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: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, with all command-line examples using PowerShell and Windows-specific tools (e.g., .exe installers, PowerShell cmdlets). The workflow assumes the use of Hyper-V and Windows Server features, with only minimal mention of Linux support (limited to a single line about file-consistent snapshots). There are no Linux-specific instructions, examples, or parity in tooling or recovery workflows.
Recommendations
  • Provide equivalent Linux command-line examples (e.g., using Bash or relevant Linux tools) where applicable, especially for agent installation and firewall configuration.
  • Include explicit instructions for backing up and recovering Linux VMs, including any differences in workflow or limitations.
  • Clarify the support level for Linux VMs (e.g., agent installation, recovery options, snapshot consistency) in dedicated sections.
  • Mention Linux scenarios alongside Windows/Hyper-V scenarios, not as an afterthought or in a separate, minimized section.
  • If certain features are unavailable for Linux, clearly state this and provide recommended alternatives or workarounds.
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: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Missing Linux Example Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias. It focuses heavily on Windows-specific backup agents (MARS, DPM, MABS), with direct backup support only for Windows machines. Linux is mentioned only to note lack of support in some scenarios, and there are no Linux-specific examples, tools, or workflows described. Windows tools and patterns (VSS, MARS agent, DPM/MABS) are discussed in detail, while Linux backup options are not addressed. The structure and order of information consistently present Windows solutions first and in more depth.
Recommendations
  • Add explicit Linux backup scenarios, including supported agents, workflows, and limitations.
  • Provide Linux-specific examples and references (e.g., using Azure Backup for Linux VMs, integration with native Linux backup tools, or third-party solutions).
  • Clarify parity or gaps between Windows and Linux support in tables and feature lists.
  • Include Linux-focused architecture diagrams and process flows where applicable.
  • If direct backup for Linux is not supported, offer guidance or alternatives for Linux users (e.g., using Azure VM backup extension, scripts, or partner tools).
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: 2025-08-19 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively references Microsoft Azure Backup Server and Data Protection Manager (DPM), both of which are Windows-based solutions. All troubleshooting steps and error messages assume the use of Windows Server or Windows Client, with no mention of Linux environments, tools, or equivalent recovery processes. There are no examples, recommendations, or troubleshooting guidance for Linux-based backup or recovery scenarios.
Recommendations
  • Explicitly state that Azure Backup Server and DPM are Windows-only products, if that is the case, to clarify scope.
  • If Linux backup and recovery is supported via Azure Backup, add equivalent troubleshooting sections and error messages for Linux-based agents or servers.
  • Provide links or references to Linux-specific documentation for Azure Backup, if available.
  • Include examples or notes for Linux administrators, or clarify alternative solutions for Linux environments.
  • Ensure parity in documentation structure and troubleshooting guidance for both Windows and Linux users where applicable.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-arm-restore-vms.md ...b/main/articles/backup/backup-azure-arm-restore-vms.md
High Priority View Details →
Scanned: 2025-08-19 00:01
Reviewed by: Unknown
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: Windows-specific examples and references (such as PowerShell and Windows tutorials) are provided without equivalent Linux examples; Windows tools and patterns (e.g., bcdedit, netdom, RDP, Windows-specific restore scenarios) are mentioned exclusively or before Linux alternatives; and guidance for Linux VMs is minimal, often limited to brief notes or links, with no step-by-step Linux-specific instructions or CLI examples.
Recommendations
  • Provide Linux-specific restore scenarios and examples, including step-by-step instructions for common Linux distributions (e.g., Ubuntu, CentOS, RHEL).
  • Include equivalent Linux command-line examples (e.g., Azure CLI, Bash scripts) alongside or before PowerShell/Windows commands.
  • Reference Linux documentation and tools (e.g., SSH, cloud-init, Linux agent troubleshooting) in parity with Windows tools like RDP, bcdedit, and netdom.
  • Ensure that links to further reading or tutorials are balanced between Windows and Linux (e.g., include /azure/virtual-machines/linux/ links where appropriate).
  • Add troubleshooting steps and post-restore guidance specific to Linux VMs, such as handling SSH keys, resetting passwords with the VMAccess extension, and dealing with Linux-specific boot or agent issues.
  • Review all scenario tables and ensure Linux is explicitly addressed, not just as a note or afterthought.
GitHub Create Pull Request
← Previous Page 37 of 65 Next →