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 976-1000 of 1604 flagged pages
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-07-13 21:37
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 linking only to Windows-specific disk encryption documentation. There are no Linux-specific examples or references for restoring encrypted VMs or for file-level restore scenarios. The documentation mentions Windows tools and patterns exclusively or before Linux equivalents, and omits Linux parity in restore instructions.
Recommendations
  • Include Linux-specific restore instructions and examples, especially for encrypted VMs (e.g., using Azure CLI or relevant Linux tools).
  • Provide links to Linux disk encryption documentation (such as for VMs encrypted with Azure Disk Encryption for Linux).
  • When referencing PowerShell, also mention Azure CLI or Bash alternatives for cross-platform parity.
  • Ensure that file-level restore instructions and examples cover both Windows and Linux VMs, including any OS-specific considerations.
  • Avoid listing only Windows scenarios or tools; always present Linux equivalents alongside or before Windows examples.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-mabs-add-storage.md ...s/blob/main/articles/backup/backup-mabs-add-storage.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. All instructions, screenshots, and tooling references are specific to Windows Server (e.g., Server Manager, ReFS, PowerShell cmdlets). There are no Linux equivalents or cross-platform guidance, and the prerequisites explicitly require Windows Server. PowerShell is the only scripting interface mentioned.
Recommendations
  • Clearly state in the introduction that Azure Backup Server is only supported on Windows, if that is the case. If Linux support is planned or available, provide equivalent instructions for Linux environments.
  • If any features are available on Linux (or via Azure-native tools), add parallel sections with Linux commands, tools, and screenshots.
  • Where PowerShell is used, provide Bash or CLI equivalents if possible, or explain why only PowerShell is supported.
  • Reference cross-platform Azure tools (such as Azure CLI or REST APIs) where applicable, and provide examples for both Windows and Linux.
  • If the product is fundamentally Windows-only, add a prominent note to clarify this, and consider linking to alternative backup solutions for Linux workloads.
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: 2025-07-13 21:37
Reviewed by: Unknown
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 Data Protection Manager (DPM), both of which are Windows-based tools. There are no references to Linux-based recovery workflows, nor are there examples or instructions for Linux systems. The screenshots and terminology are all specific to Windows environments, and no parity is provided for Linux users.
Recommendations
  • Include a section or separate instructions for recovering data from Linux-based systems protected by Azure Backup.
  • Mention and provide examples for Linux-compatible tools or command-line workflows, such as using Azure CLI or REST API for recovery operations.
  • Clarify in the introduction that the documented process is specific to Windows environments, and link to Linux-specific recovery documentation if available.
  • Add parity in screenshots and step-by-step guides for Linux users, or explicitly state if Linux is not supported by Azure Backup Server.
  • If Linux is unsupported in this scenario, provide alternative recovery options for Linux workloads protected by Azure Backup.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/pre-backup-post-backup-scripts.md ...main/articles/backup/pre-backup-post-backup-scripts.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation assumes a Windows environment throughout: all file paths use Windows conventions, only Windows-specific examples (such as Drive: notation and cscript for VBScript) are provided, and there is no mention of Linux or cross-platform considerations. There are no Linux shell script examples, no Linux file path formats, and no guidance for non-Windows environments.
Recommendations
  • Add explicit guidance for Linux environments, including examples using Linux file paths (e.g., /opt/Microsoft/DataProtectionManager/DPM/Scripting).
  • Provide sample scripts and command-line usage for Linux shells (e.g., bash, sh) alongside Windows examples.
  • Clarify whether MABS supports Linux agents and, if so, document any differences in script execution, permissions, and configuration.
  • Mention Linux equivalents for Windows tools (e.g., using bash or sh instead of cscript for script execution).
  • Ensure all instructions and XML examples are platform-agnostic or provide both Windows and Linux variants.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/upgrade-mars-agent.md ...e-docs/blob/main/articles/backup/upgrade-mars-agent.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively describes the upgrade process for the Microsoft Azure Recovery Services (MARS) agent on Windows-based systems. All instructions, screenshots, and tool references (such as Remote Desktop, DPM Console, and the MARS agent itself) are Windows-specific. There are no mentions of Linux systems, Linux tools, or cross-platform considerations, indicating a strong Windows bias.
Recommendations
  • Explicitly state in the introduction whether the MARS agent is supported only on Windows, or clarify if Linux support is unavailable.
  • If Linux support exists or is planned, provide equivalent instructions and examples for Linux systems, including command-line steps, package management, and remote connection methods (e.g., SSH).
  • Include a section addressing cross-platform environments, even if only to clarify platform limitations.
  • Where possible, use neutral language and avoid assuming Remote Desktop or Windows GUI tools are the only management options.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-restore-files-from-vm.md .../articles/backup/backup-azure-restore-files-from-vm.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several ways: Windows terminology and tools (e.g., 'Download Executable', registry edits, Windows Explorer/File Explorer) are often mentioned before or in more detail than their Linux equivalents. Powershell and Windows-specific troubleshooting steps are prominent, while Linux steps are sometimes less detailed or appear after Windows instructions. Some advanced Windows scenarios (like registry edits for iSCSI timeouts) are described in depth, while Linux equivalents are less emphasized or missing. The 'Next steps' section also lists PowerShell before Azure CLI, reinforcing the Windows-first pattern.
Recommendations
  • Ensure Linux instructions and troubleshooting steps are as detailed and prominent as Windows ones, especially for advanced scenarios (e.g., provide more in-depth guidance for Linux iSCSI/RAID/LVM troubleshooting).
  • Present Linux and Windows instructions in parallel or in clearly separated, equally detailed sections, rather than always listing Windows first.
  • Include Linux CLI examples and tools (e.g., show how to browse and copy files using common Linux file managers or CLI commands, not just Windows Explorer).
  • In 'Next steps', alternate the order of PowerShell and CLI links, or group them by platform to avoid reinforcing a Windows-first impression.
  • Where Windows registry edits are described, provide equivalent Linux configuration file changes (e.g., for iSCSI timeouts) with equal prominence and explanation.
  • Use neutral language and headings (e.g., 'For Windows and Linux' or 'Platform-specific steps') to avoid implying Windows is the default or primary platform.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by listing Azure PowerShell as a primary method for backup/restore operations in the 'Next steps' section, sometimes before or alongside Azure CLI, and never mentioning Bash, Linux shell, or kubectl-native workflows. There are no explicit Linux or cross-platform command-line examples, and the documentation does not clarify parity or differences between Windows and Linux environments for AKS backup operations.
Recommendations
  • Ensure that all example commands and references include both Azure CLI (cross-platform) and Azure PowerShell, with CLI listed first to reflect its cross-platform nature.
  • Explicitly mention that all operations can be performed from Linux, macOS, and Windows environments, and clarify any OS-specific requirements or differences.
  • Where possible, provide kubectl-native or Bash shell examples for common tasks, especially for AKS users who may be operating from Linux-based environments.
  • In the 'Next steps' section, list Azure CLI before PowerShell, and add links or notes for Linux/macOS users.
  • Add a brief section or note confirming that all prerequisites and operations are supported equally on Linux, macOS, and Windows, or detail any exceptions.
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-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically using 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 Windows authentication patterns (e.g., NTAuthority\System). There are no examples or guidance for Linux-based SQL Server deployments, nor are any Linux tools or commands mentioned.
Recommendations
  • Add a section or parallel guide for backing up SQL Server on Linux to Azure, using supported tools (e.g., Azure Backup integration with Linux, or native SQL Server backup to Azure Blob Storage).
  • Explicitly state that DPM is a Windows-only solution and provide links or references to Linux-compatible backup solutions for SQL Server.
  • Include examples, prerequisites, and screenshots for Linux environments where possible, or clarify the scope of the article as Windows-only at the outset.
  • Mention alternative backup and recovery workflows for SQL Server on Linux, such as using sqlcmd, bash scripts, or Azure CLI.
  • If Azure Backup supports Linux SQL Server workloads, provide step-by-step instructions for those scenarios.
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-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric tools, UI elements, and features (such as Volume Shadow Copy Service, Data Deduplication, and the MABS console), and by omitting any Linux-specific instructions or examples. There is no mention of Linux client support, installation, or recovery procedures, nor are any Linux command-line or UI examples provided.
Recommendations
  • Include explicit instructions and examples for backing up and recovering file data from Linux machines, if supported by MABS.
  • Document the process for installing the MABS protection agent on Linux systems, including any required dependencies or configuration steps.
  • Provide parity in examples: for every Windows UI workflow, offer equivalent Linux command-line or UI steps.
  • Clarify any limitations or unsupported features for Linux clients (e.g., if VSS or Data Deduplication is not available on Linux, state this clearly).
  • Reference Linux-native backup and recovery tools or methods where appropriate, and explain how they integrate with MABS.
  • If Linux is not supported, explicitly state this in the prerequisites or supported platforms section.
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: 2025-07-13 21:37
Reviewed by: Unknown
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, specifically Hyper-V on Windows Server, and Microsoft Azure Backup Server (MABS), which is itself a Windows-based solution. Linux is only briefly mentioned as a supported guest OS for file-consistent backups, with no detailed instructions or examples. All procedures, prerequisites, and recovery steps are described exclusively in the context of Windows tools, roles, and patterns (e.g., VSS, SCSI controllers, registry keys, Windows authentication methods, and Windows Server roles). There are no Linux command-line examples, nor any mention of Linux-specific backup or recovery nuances beyond a single line in the prerequisites table.
Recommendations
  • Add explicit Linux guest backup and recovery examples, including step-by-step instructions for both backup and restore operations involving Linux VMs.
  • Clarify any limitations or differences in backup and recovery workflows for Linux VMs, such as the lack of application-consistent backups or item-level recovery.
  • Provide Linux-specific troubleshooting tips and best practices, including how to verify backup consistency and restore files within Linux VMs.
  • Include examples of how to interact with MABS from Linux environments, if supported (e.g., via SMB/NFS shares, agent installation, or command-line tools).
  • Balance the documentation by introducing Linux scenarios earlier and more prominently, rather than as a brief note in a prerequisites table.
  • If MABS does not support certain Linux features, clearly state these limitations and suggest alternative solutions or workarounds.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/quick-backup-postgresql-database-portal.md ...cles/backup/quick-backup-postgresql-database-portal.md
High Priority View Details →
Scanned: 2025-07-13 21:37
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 referencing PowerShell scripts as the primary or default method for granting privileges to database users, both in the prerequisites and during the backup configuration flow. While it briefly mentions alternatives like PG admin or PSQL tool, these are listed after PowerShell and without any concrete examples or guidance. No Linux-specific or cross-platform command-line examples are provided, and the documentation assumes familiarity with Windows-centric tools and workflows.
Recommendations
  • Provide equivalent Linux/bash/psql command examples alongside PowerShell scripts for all privilege-granting and configuration steps.
  • List cross-platform or Linux-native tools (such as psql or bash scripts) before or alongside PowerShell, not only as an afterthought.
  • Include explicit instructions or code snippets for using psql or PG admin to grant privileges, ensuring Linux users have clear, actionable guidance.
  • Clarify that all steps can be performed from Linux or macOS environments, and highlight any differences or requirements for non-Windows users.
  • Where ARM templates or Azure CLI are referenced, ensure examples are platform-agnostic and not reliant on Windows-specific tooling.
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-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Missing Linux Example Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a clear Windows bias. It focuses heavily on Windows-centric backup tools (MARS agent, DPM, MABS), provides detailed architectural explanations only for Windows/on-premises Windows Server scenarios, and lacks equivalent Linux backup workflows or examples. Linux is mentioned only to state that certain features are unsupported. The documentation also introduces Windows tools and patterns first, with little to no mention of Linux-native backup agents or processes.
Recommendations
  • Add explicit Linux backup scenarios and workflows, including supported agents or third-party options for on-premises Linux machines.
  • Provide architectural diagrams and step-by-step processes for Linux backup, similar to the detailed Windows/MARS agent sections.
  • Include Linux command-line examples and tools where relevant, not just Windows or PowerShell-based instructions.
  • Clarify Linux support limitations up front, and link to alternative solutions or roadmap items for Linux parity.
  • Ensure that tables and feature matrices indicate Linux support status, and avoid presenting Windows-only tools as the default or only option.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-backup-sharepoint.md ...main/articles/backup/backup-azure-backup-sharepoint.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references System Center Data Protection Manager (DPM), a Windows-only backup solution, and provides instructions and screenshots for a Windows GUI workflow. There are no Linux equivalents, examples, or alternative tools mentioned. All prerequisite steps and tooling (e.g., ConfigureSharePoint.exe) are Windows-specific, and the documentation assumes a Windows environment throughout.
Recommendations
  • Acknowledge that DPM is a Windows-only tool and clarify this limitation early in the documentation.
  • Provide information or links to alternative solutions for backing up SharePoint data from Linux environments, if any exist.
  • If Azure Backup supports Linux-based backup agents or third-party tools for SharePoint or similar workloads, include examples or references.
  • Where possible, offer parity by mentioning command-line or scriptable options (e.g., PowerShell, CLI) and note if these are Windows-only.
  • Add a section explicitly addressing Linux/Unix users, outlining their options or the lack thereof.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-encryption.md ...re-docs/blob/main/articles/backup/backup-encryption.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. In the discussion of Azure Disk Encryption (ADE), BitLocker (a Windows-specific tool) is mentioned before DM-Crypt (the Linux equivalent), and the explanation of TDE-encrypted database restores links to SQL Server (a Microsoft/Windows-centric product) without mentioning cross-platform or Linux SQL options. There are no Linux-specific command examples or references to Linux tooling, and the documentation implicitly assumes familiarity with Windows technologies.
Recommendations
  • When mentioning Azure Disk Encryption, present DM-Crypt (Linux) and BitLocker (Windows) with equal prominence, or alternate the order in which they are listed.
  • Include explicit examples or references for both Windows and Linux scenarios, such as command-line instructions or links to relevant Linux documentation.
  • Where SQL Server is referenced, clarify support for cross-platform (Linux) SQL Server deployments and provide links or notes for Linux-specific procedures.
  • Review all sections to ensure Linux tools and workflows are described with the same detail and priority as Windows equivalents.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dpm-introduction.md .../main/articles/backup/backup-azure-dpm-introduction.md
High Priority View Details →
Scanned: 2025-07-13 21:37
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, focusing exclusively on System Center Data Protection Manager (DPM), a Windows-only product. All instructions, requirements, and tooling (such as the use of Windows PowerShell, .NET Framework, and .exe installers) are specific to Windows environments. There are no Linux equivalents, examples, or mentions of cross-platform support. The documentation assumes the reader is operating in a Windows ecosystem and does not address Linux-based backup scenarios or tools.
Recommendations
  • Clearly state at the beginning that DPM is a Windows-only product, and provide links to equivalent Azure Backup documentation for Linux environments.
  • Where possible, mention or link to Azure Backup solutions and agents for Linux, such as the MARS agent for Linux or Azure VM backup for Linux VMs.
  • If relevant, provide parallel instructions or references for Linux-based backup scenarios, or clarify that the described steps are not applicable to Linux.
  • Avoid assuming the presence of Windows-only components (e.g., PowerShell, .NET Framework) without noting their platform specificity.
  • Include a comparison table or section outlining backup options for both Windows and Linux workloads in Azure.
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: 2025-07-13 21:37
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 referencing PowerShell as a primary automation method for configuring permissions and restoring encrypted VMs, without mentioning or providing equivalent examples for Linux environments (such as Azure CLI or Bash scripts). There are no Linux-specific instructions or parity in tooling references, and the only command-line example given is PowerShell.
Recommendations
  • Include Azure CLI and/or Bash script examples alongside PowerShell for all automation steps, especially for configuring permissions and restoring VMs.
  • Explicitly mention that steps can be performed from both Windows and Linux environments, and provide links or references to Linux-compatible tools.
  • Add a section or callouts for Linux users, ensuring that all procedures are accessible regardless of the administrator's operating system.
  • Review all references to ensure that Windows tools are not presented as the default or only option.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively describes backup and recovery procedures for Microsoft Exchange using Microsoft Azure Backup Server (MABS), a Windows-only tool. All instructions, screenshots, and file paths are Windows-centric (e.g., referencing C:\Program Files), and there are no mentions of Linux equivalents, support, or examples. The documentation assumes the use of Windows-based Exchange servers and does not address scenarios for Linux environments.
Recommendations
  • Explicitly state that MABS and Exchange Server are Windows-only, if that is the case, to clarify platform limitations.
  • If Azure Backup supports Linux-based workloads or other cross-platform backup scenarios, provide parallel documentation or links for those cases.
  • Include a section on backing up Linux servers or applications with Azure Backup, if supported, to ensure Linux parity.
  • Where possible, mention alternative tools or approaches for Linux environments, such as Azure Backup integration with Linux VMs or third-party solutions.
  • Avoid hardcoding Windows paths and terminology unless the product is strictly Windows-only; otherwise, provide Linux equivalents.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-scdpm-troubleshooting.md .../articles/backup/backup-azure-scdpm-troubleshooting.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows environments, referencing Windows-specific tools (such as 'net stop dpmra'), Windows service management patterns, and concepts like NT AUTHORITY\SYSTEM. There are no examples or troubleshooting steps for Linux systems, nor any mention of Linux equivalents or cross-platform considerations. The documentation assumes the use of Windows throughout.
Recommendations
  • Include troubleshooting steps and examples for Linux-based backup agents or workloads, if supported.
  • When referencing service management (e.g., restarting services), provide both Windows (e.g., 'net stop dpmra') and Linux (e.g., 'systemctl restart <service>') equivalents.
  • Clarify whether Data Protection Manager is Windows-only, or explicitly state platform limitations at the start of the documentation.
  • If Linux workloads or agents are supported, add sections or notes for Linux-specific errors, logs, and commands.
  • Avoid assuming Windows-specific user accounts (e.g., NT AUTHORITY\SYSTEM) without mentioning Linux alternatives or stating that this is Windows-only.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/soft-delete-virtual-machines.md ...b/main/articles/backup/soft-delete-virtual-machines.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions and examples for managing soft delete of VM backups using the Azure portal and Azure PowerShell, but does not mention or provide examples for Linux CLI tools (such as Azure CLI), Bash scripting, or Linux-specific workflows. PowerShell is featured exclusively in the automation section, and there are no Linux command-line equivalents or parity in the examples.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell operations (delete, undelete, resume backup) to support Linux and cross-platform users.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI, and provide links or code snippets.
  • Where automation is discussed, provide both PowerShell and Bash (with Azure CLI) script examples.
  • Review screenshots and UI instructions to ensure they are not Windows-centric (e.g., avoid referencing right-click if not applicable cross-platform).
  • Include a section or note on cross-platform compatibility and tool choice for users on non-Windows systems.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-move-recovery-services-vault.md ...es/backup/backup-azure-move-recovery-services-vault.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is the only scripting example given in detail for moving Recovery Services vaults, with no equivalent Bash or Linux shell script provided. The CLI section is present but less detailed and lacks context or troubleshooting guidance. Throughout the document, Windows-specific instructions (such as installing Windows updates) are mentioned before Linux equivalents, and Linux guidance is less explicit or refers users to external distributor documentation. There are no Linux-specific command-line or automation examples.
Recommendations
  • Provide Bash or Linux shell script examples for moving Recovery Services vaults, especially for common automation scenarios.
  • Expand the Azure CLI section to include more detailed steps, troubleshooting, and context, matching the depth of the PowerShell section.
  • When mentioning OS-specific prerequisites (e.g., updating certificates), give equal detail for Linux, including example commands for popular distributions (e.g., apt, yum, zypper).
  • Ensure that Linux tools and workflows are mentioned alongside Windows tools, not just as a reference to distributor documentation.
  • Consider including a table or section that summarizes equivalent commands and steps for Windows (PowerShell), Linux (Bash/CLI), and possibly MacOS where relevant.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vm-file-recovery-troubleshoot.md ...s/backup/backup-azure-vm-file-recovery-troubleshoot.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows troubleshooting steps are often presented first and in greater detail, with explicit GUI walkthroughs (e.g., Server Manager, Disk Management, ISCSI initiator Properties). Windows-specific tools and error codes (e.g., deduplication, 0x80070780) are mentioned without Linux equivalents. Linux troubleshooting is generally referenced via links to other articles, with fewer in-place step-by-step instructions or screenshots. Some Linux scenarios lack direct examples or detailed guidance, especially for common tasks like mounting volumes or handling deduplication.
Recommendations
  • Provide Linux troubleshooting steps alongside Windows, not just as links but with in-place, step-by-step instructions and screenshots.
  • Include Linux equivalents for all Windows tools and error codes (e.g., show how to check and mount disks using lsblk, mount, or parted; address deduplication or file access errors on Linux).
  • Balance the order of presentation: alternate or parallelize Windows and Linux sections, or clearly separate them under OS-specific headings.
  • Add Linux-specific error messages and their resolutions where only Windows errors are currently described.
  • Where GUI steps are given for Windows, provide equivalent CLI or GUI steps for common Linux desktop environments (e.g., using GNOME Disks, KDE Partition Manager, or command-line tools).
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-database-from-azure-vm-blade.md ...ckup/backup-sql-server-database-from-azure-vm-blade.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific tools and extensions (e.g., AzureBackupWindowsWorkload extension, NT Service accounts), and does not mention or provide guidance for SQL Server on Linux VMs. There are no examples or notes for Linux-based SQL Server VMs, and the process described assumes a Windows environment throughout.
Recommendations
  • Explicitly state whether the described process applies only to Windows-based SQL Server VMs or also to Linux-based ones.
  • If Linux-based SQL Server VMs are supported, provide equivalent instructions, examples, and screenshots for configuring Azure Backup on Linux VMs.
  • Mention and document any Linux-specific requirements, extensions, or limitations (e.g., use of different agents, service accounts, or backup plugins).
  • If Linux is not supported for this feature, add a clear note at the beginning of the article to inform users.
  • Ensure parity in terminology and step-by-step guidance for both Windows and Linux environments where applicable.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is exclusively focused on backing up Windows Server system state using Azure Backup. All instructions, screenshots, and tools (such as the Microsoft Azure Recovery Services (MARS) Agent) are Windows-specific. There are no references to Linux systems, Linux backup tools, or cross-platform alternatives. The workflow, terminology, and examples are tailored entirely to Windows environments, with no mention of how to achieve similar outcomes on Linux or other operating systems.
Recommendations
  • Add a section or a separate article explaining how to back up Linux system state or equivalent using Azure Backup, if supported.
  • Include Linux-specific tools, commands, and examples (e.g., using Azure CLI, shell scripts, or Linux backup agents).
  • If Azure Backup does not support Linux system state backup, clearly state this limitation at the beginning of the article and provide links to alternative solutions for Linux.
  • Ensure parity in documentation structure and detail for both Windows and Linux backup scenarios, including screenshots, step-by-step guides, and troubleshooting tips.
  • Avoid using Windows terminology (e.g., 'System State', 'MARSAgentInstaller.exe') exclusively; provide Linux equivalents or clarify OS-specific concepts.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-troubleshoot-slow-backup-performance-issue.md ...ackup-azure-troubleshoot-slow-backup-performance-issue.md
High Priority View Details →
Scanned: 2025-07-13 21:37
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 strong Windows bias. All troubleshooting steps, examples, and tool recommendations are specific to Windows environments. Windows tools like Performance Monitor are mentioned exclusively, and all file paths and agent references are Windows-specific. There are no Linux equivalents or examples provided, and the language assumes the user is operating in a Windows environment.
Recommendations
  • Add troubleshooting steps and examples for Linux environments, including relevant commands and log file locations.
  • Mention and explain Linux equivalents for Windows tools (e.g., using 'iostat', 'vmstat', 'top', or 'htop' for performance monitoring instead of Performance Monitor).
  • Provide Linux file paths and agent installation instructions where applicable.
  • Clarify whether the Azure Backup agent or MARS agent is supported on Linux, and if not, direct Linux users to the appropriate Azure Backup solutions (such as Azure Backup for Linux VMs or Azure Backup Server).
  • Ensure that all recommendations and troubleshooting steps are presented for both Windows and Linux, or clearly state platform limitations.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-vms-enhanced-policy.md ...in/articles/backup/backup-azure-vms-enhanced-policy.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell examples before CLI examples, using Windows-centric tooling (PowerShell cmdlets), and offering more step-by-step guidance for PowerShell users. The CLI section is less detailed and lacks parity in explanation and context. There are no explicit Linux-specific examples or references to Linux shell environments, and the documentation assumes familiarity with Windows tools and patterns.
Recommendations
  • Provide Linux shell (bash) equivalents for all PowerShell examples, especially for tasks like date/time manipulation and JSON policy creation.
  • Ensure CLI examples are as detailed as PowerShell ones, including step-by-step breakdowns and explanations of parameters.
  • Explicitly mention compatibility and usage on Linux/macOS platforms, including any prerequisites or differences in behavior.
  • Add notes or examples for common Linux tools (e.g., jq for JSON manipulation, date for time handling) where relevant.
  • Reorder sections or present CLI and PowerShell examples side-by-side to avoid the perception of Windows-first bias.
GitHub Create Pull Request
← Previous Page 40 of 65 Next →