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 876-900 of 1604 flagged pages
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/soft-delete-azure-file-share.md ...b/main/articles/backup/soft-delete-azure-file-share.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by referencing a 'Undelete File Share Script' that is a PowerShell script, without mentioning or providing equivalent Linux or cross-platform CLI examples. The instructions and links consistently refer to the Azure Portal and PowerShell, which are more commonly used on Windows, and do not mention Azure CLI, Bash, or other Linux-native tools. There are no examples or guidance for Linux users, and Windows-centric tools are referenced first and exclusively.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for undeleting file shares and managing soft delete settings.
  • Explicitly mention cross-platform tools and workflows, such as Azure CLI, alongside PowerShell and portal instructions.
  • Add a section or links for Linux/macOS users, detailing how to perform the same operations from those environments.
  • Ensure that references to scripts and automation include both PowerShell and Bash/CLI options, or note their platform compatibility.
  • Review all instructions to avoid assuming the user is on Windows, and clarify when steps are platform-specific.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/troubleshoot-azure-files.md .../blob/main/articles/backup/troubleshoot-azure-files.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing troubleshooting scripts only in PowerShell, referencing Windows-centric tools (such as Azure File Sync), and omitting equivalent Linux or cross-platform CLI examples. There are no Bash, Azure CLI, or Linux-specific instructions or scripts, and the only automation examples are PowerShell-based. This may disadvantage users managing Azure Files from Linux or macOS environments.
Recommendations
  • Provide equivalent troubleshooting scripts using Azure CLI and Bash, especially for tasks like finding Recovery Services vaults and undeleting file shares.
  • Explicitly mention cross-platform alternatives to PowerShell scripts, and clarify which steps can be performed from Linux/macOS.
  • Include examples and screenshots for Linux environments where relevant (e.g., using Azure CLI in terminal).
  • Reference Azure CLI documentation alongside PowerShell scripts for parity.
  • Avoid assuming users have access to Windows tools such as Azure File Sync; clarify platform requirements or alternatives.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/soft-delete-sql-saphana-in-azure-vm.md ...articles/backup/soft-delete-sql-saphana-in-azure-vm.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for performing soft delete operations using the Azure Portal and Azure PowerShell, but does not mention or provide examples for Linux-native tools, Azure CLI, or bash scripting. PowerShell is emphasized as the only command-line automation method, which is more familiar to Windows users. There are no Linux-specific instructions or parity for users who may prefer or require non-Windows tooling.
Recommendations
  • Add equivalent Azure CLI (az backup ...) examples for all PowerShell operations, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that all operations can be performed from Linux environments using Azure CLI or REST API, and provide links or examples.
  • If any steps require PowerShell specifically, clarify why and provide workarounds or alternatives for Linux users.
  • Consider including bash script snippets or references for automation scenarios on Linux.
  • Review the documentation structure to ensure that Windows-specific 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/use-archive-tier-support.md .../blob/main/articles/backup/use-archive-tier-support.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: Windows-centric tools (PowerShell, Azure portal) are presented first in navigation and examples, with extensive PowerShell scripting coverage. The CLI section is present, but less detailed and often refers back to portal/PowerShell workflows. There are no explicit Linux-specific examples, nor references to Linux-native tools or patterns, and the documentation assumes familiarity with Windows-based management paradigms.
Recommendations
  • Add explicit Linux usage examples, such as shell scripting (bash) for Azure CLI commands, and clarify cross-platform compatibility.
  • Include instructions for installing and using Azure CLI on Linux, with troubleshooting tips for common Linux environments.
  • Balance the depth of CLI examples to match PowerShell coverage, including advanced scenarios and automation.
  • Reference Linux-native tools or patterns where relevant (e.g., cron jobs for automation, environment variable usage).
  • Clarify that PowerShell Core is cross-platform, but also provide bash/zsh alternatives for scripting tasks.
  • Review navigation and ordering so that Windows and Linux approaches are presented with equal prominence.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/tutorial-restore-disk.md ...ocs/blob/main/articles/backup/tutorial-restore-disk.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. It references PowerShell-based instructions and links to Windows-centric articles before introducing CLI-based (cross-platform) instructions. The only cross-link for alternative tooling is to a PowerShell tutorial, and the cross-zonal restore section links to a Windows VM creation guide. There is no explicit Linux example for restoring a VM, and the documentation does not mention Linux-specific considerations or parity with Windows tooling. All CLI examples are generic and do not clarify Linux/Windows differences.
Recommendations
  • Add explicit Linux and Windows example sections for restoring VMs, highlighting any differences in process or parameters.
  • Provide links to both Linux and Windows VM creation guides in cross-zonal restore sections.
  • Include a parity table or note clarifying which steps or commands differ for Linux vs. Windows VMs.
  • Reference Linux-specific documentation (e.g., restoring Linux VMs with CLI) alongside PowerShell/Windows links.
  • Ensure that introductory and cross-reference links do not prioritize Windows/PowerShell over CLI or Linux options.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/tutorial-postgresql-backup.md ...lob/main/articles/backup/tutorial-postgresql-backup.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows by primarily referencing PowerShell scripts for privilege assignment and not providing equivalent Linux/Unix command-line examples. The only explicit script-based example is PowerShell, and while alternatives like 'PG admin or PSQL tool' are mentioned, they are not documented or illustrated. This can make the tutorial less accessible for users managing PostgreSQL on Linux VMs, which is a common scenario.
Recommendations
  • Provide explicit Linux/Unix command-line examples (e.g., using psql) for granting database privileges, alongside PowerShell scripts.
  • Include step-by-step instructions or sample commands for using PG admin and psql to perform the same tasks as the PowerShell script.
  • Ensure that any ARM template or automation instructions are platform-neutral, or provide guidance for running them on Linux/macOS.
  • Where PowerShell is referenced, add equivalent Bash or shell script examples.
  • Clarify that the tutorial applies equally to both Windows and Linux VMs, and highlight any platform-specific considerations.
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-29 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by providing restore scenarios and encrypted VM restore instructions that reference only Windows-specific tools and documentation. In the 'Restore an encrypted VM' scenario, only Windows VM encryption links and PowerShell are mentioned, with no mention of Linux VM encryption or restore processes. There are no Linux-specific examples or references, and Windows tools and patterns are presented exclusively.
Recommendations
  • Add equivalent restore instructions and documentation links for Linux VMs, especially for encrypted Linux VM restore scenarios.
  • Include examples or references for restoring Linux VMs, such as using Azure CLI or relevant Linux tools, alongside PowerShell.
  • Ensure that both Windows and Linux scenarios are covered equally in tables and explanations, or clearly indicate when a scenario is Windows-only.
  • Provide parity in documentation links, such as linking to both Windows and Linux disk encryption documentation where appropriate.
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-29 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 focused on Windows environments, specifically Windows Server-based Active Directory. All examples, tools, and procedures are Windows-centric, with explicit use of Windows tools (e.g., PowerShell, ntdsutil.exe) and no mention of Linux-based domain controllers or cross-platform scenarios. Linux is not referenced at all, and all backup/restore instructions assume a Windows operating system.
Recommendations
  • Acknowledge that Active Directory Domain Services (AD DS) is a Windows technology, but clarify whether Azure Backup supports Samba/LDAP-based domain controllers on Linux (if applicable).
  • If Linux-based domain controllers (e.g., Samba AD) are supported, provide equivalent backup and restore guidance, including Linux command-line examples and tools.
  • Where PowerShell scripts are provided, offer bash or shell script equivalents if Linux is supported.
  • Explicitly state in the prerequisites or introduction that the procedures apply only to Windows Server-based AD DS if Linux is not supported, to avoid confusion.
  • Include a comparison table or section outlining backup/restore options for both Windows and Linux environments, even if only to clarify limitations.
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-25 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 only linking to Windows-specific encryption documentation. There are no Linux-specific examples, tools, or references provided for VM restore scenarios, especially for encrypted VMs. The documentation also lists Windows scenarios and tools before (or instead of) Linux equivalents, and omits Linux-specific guidance in key restore workflows.
Recommendations
  • Add explicit Linux restore examples, especially for encrypted VMs, including references to Linux disk encryption and restore workflows.
  • Include links to Linux VM encryption documentation (e.g., Azure Disk Encryption for Linux) alongside Windows links.
  • Provide CLI or Bash-based restore instructions in addition to PowerShell, ensuring parity for Linux administrators.
  • Where PowerShell is referenced, clarify if/when Azure CLI or other cross-platform tools can be used, and provide those examples.
  • Review restore scenarios to ensure Linux-specific considerations (such as file system types, mount instructions, or agent requirements) are addressed.
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-25 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 exhibits a Windows bias in several ways: Windows and PowerShell are mentioned or linked first and more frequently than Linux equivalents, especially in examples and guidance for restoring VMs with special configurations. There are multiple references to Windows-specific tools (e.g., PowerShell, bcdedit, netdom), and links to Windows documentation, while Linux-specific instructions are sparse or absent. Where Linux is mentioned, it is often as a note or afterthought, and there are no concrete Linux command examples or links to Linux VM restore scenarios.
Recommendations
  • Provide Linux-specific examples and guidance alongside Windows instructions, especially for restoring VMs, handling network configurations, and post-restore steps.
  • Include links to Linux VM documentation (e.g., restoring Ubuntu/CentOS VMs, using cloud-init, troubleshooting Linux VM restore issues).
  • Offer equivalent CLI or shell (bash/az CLI) commands for all PowerShell and Windows command-line examples.
  • Avoid mentioning Windows tools or patterns (e.g., PowerShell, bcdedit, netdom) exclusively; when referenced, provide Linux alternatives (e.g., grub, systemctl, SSH troubleshooting).
  • Ensure that references to documentation for special VM types (e.g., SQL VMs, domain controllers) include Linux-based options where applicable (e.g., restoring Linux SQL VMs).
  • Balance the order of presentation so that Linux and Windows are treated equally (e.g., do not always mention Windows first or exclusively in lists or tables).
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-25 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 referencing PowerShell/CLI scripts for permissions without specifying or providing Linux shell examples, and by focusing on Azure Portal workflows (which are often more familiar to Windows users). There is no explicit mention of Linux-specific commands, tools, or workflows, despite SAP HANA's common deployment on Linux. The documentation does not provide parity for Linux administrators, omitting bash or Linux CLI examples and not clarifying cross-platform steps.
Recommendations
  • Include explicit Linux shell (bash) command examples for all steps where PowerShell or CLI scripts are referenced.
  • Clarify that the instructions apply to both Windows and Linux VMs, or specify any OS-specific differences.
  • Provide Linux-native workflow screenshots and terminal commands, especially for mounting disks and managing permissions.
  • When referencing 'PowerShell or CLI script', specify and provide both PowerShell (for Windows) and Bash/Azure CLI (for Linux) equivalents.
  • Add a section or callout for Linux administrators, highlighting any nuances or best practices for SAP HANA on 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-24 00:00
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 exclusively to Windows-specific encryption documentation. There are no Linux-specific examples, tools, or references for restoring Linux VMs, particularly in scenarios involving encryption or item-level restore. The documentation assumes Windows as the default context for advanced restore scenarios, omitting Linux parity.
Recommendations
  • Include equivalent Linux restore instructions and examples, especially for scenarios involving encrypted VMs. Reference Azure CLI, Bash, or other Linux-native tools where appropriate.
  • Add links to Linux VM encryption documentation (e.g., Azure Disk Encryption for Linux) and describe the restore process for encrypted Linux VMs.
  • Ensure that item-level restore scenarios mention both Windows and Linux file systems, and clarify any differences in supported features or workflows.
  • When referencing tools (e.g., PowerShell), also mention and provide examples for cross-platform tools such as Azure CLI or REST API.
  • Review all scenario tables and ensure that Linux-specific considerations or limitations are explicitly documented alongside Windows information.
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-24 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by mentioning Windows-specific tools (Volume Shadow Copy Service, VM Agent, snapshot extension) before their Linux equivalents, and by linking only to Windows-specific agent/extension documentation. There are no Linux command or tool examples, and Linux mechanisms (fsfreeze) are mentioned only in passing, without links or further explanation.
Recommendations
  • Provide equal prominence to Linux tools and mechanisms (e.g., link to documentation about fsfreeze and Linux VM agents/extensions).
  • Include examples or references for both Windows and Linux environments when discussing backup mechanisms and requirements.
  • Avoid listing Windows tools or documentation links before Linux equivalents; present both together or in parallel.
  • Clarify any differences in agent/extension requirements for Linux VMs and provide relevant links.
  • Add a section or note specifically addressing Linux backup considerations, including references to Linux documentation.
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-24 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows-first bias in several areas. In the snapshot creation section, Windows (VSS) is described in detail before Linux, and the Linux process is described only in terms of requiring custom scripts, with no concrete example or guidance. Windows-specific tools (VSS) are mentioned by name, while the Linux equivalent ('freeze') is only briefly referenced in a note. There are no Linux command examples or detailed walkthroughs, whereas PowerShell is mentioned for restore operations. Overall, Linux users receive less actionable guidance and fewer concrete examples.
Recommendations
  • Provide concrete Linux examples for backup and restore operations, including sample pre/post scripts for common applications (e.g., MySQL, PostgreSQL).
  • Mention Linux tools (such as 'fsfreeze', 'LVM snapshots', etc.) explicitly and describe their role in achieving consistency, similar to the VSS explanation for Windows.
  • Balance the order of presentation: describe Linux and Windows processes in parallel, rather than always listing Windows first.
  • Include Linux CLI (az CLI, bash) examples for backup and restore tasks, not just PowerShell.
  • Offer troubleshooting guidance for Linux snapshot issues, similar to the linked Windows troubleshooting article.
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-24 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation shows a Windows bias by providing explicit PowerShell instructions for restoring VMs from disks, referencing Windows-specific tools (such as OS disk swap documentation pointing to Windows), and only mentioning Linux-specific steps as a brief afterthought. There are no Linux CLI or automation examples, and Windows/PowerShell approaches are prioritized or exclusively detailed.
Recommendations
  • Provide equivalent CLI and automation examples for Linux, such as using Azure CLI or Bash scripts to create a VM from restored disks.
  • Include links to Linux-specific documentation for operations like OS disk swap, not just Windows.
  • Ensure Linux restore steps are as detailed as Windows/PowerShell steps, including example commands and troubleshooting.
  • Present Windows and Linux instructions in parallel or with equal prominence, rather than relegating Linux to a separate, less-detailed section.
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-24 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a Windows bias by prioritizing or exclusively mentioning Windows-specific tools, examples, and workflows. Windows and PowerShell are referenced more frequently and earlier than Linux equivalents. There are missing Linux-specific examples, and guidance for Linux users is minimal or absent, especially in advanced or troubleshooting scenarios.
Recommendations
  • Provide Linux-specific examples alongside Windows ones, especially for tasks like restoring VMs, attaching disks, and post-restore steps.
  • Include references to Azure CLI and Bash scripts, not just PowerShell, for automation and VM creation from restored disks.
  • When mentioning Windows tools (e.g., bcdedit, netdom), also provide equivalent Linux troubleshooting steps (e.g., using GRUB, chroot, SSH recovery).
  • Balance references to Windows and Linux documentation, such as linking to both Windows and Linux VM management guides.
  • Explicitly state when a process or feature is OS-agnostic, and clarify any OS-specific limitations or requirements.
  • Add Linux-focused troubleshooting and post-restore guidance, such as handling cloud-init, resetting SSH keys, or repairing bootloaders.
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-24 00:00
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 referencing PowerShell and CLI scripts for permission management without providing explicit Linux (bash) examples or guidance. The workflow and terminology are oriented around the Azure portal and PowerShell, with no mention of Linux-native tools or command-line patterns. There are no screenshots or instructions that show Linux environments, and the documentation assumes familiarity with Windows-centric tools.
Recommendations
  • Provide explicit bash/Linux shell script examples for permission management and disk mounting, alongside or before PowerShell examples.
  • Include screenshots or step-by-step instructions for restoring SAP HANA on Azure VMs running Linux, reflecting the typical SAP HANA deployment environment.
  • Reference Linux-native tools (such as az CLI commands run from bash) and clarify any OS-specific steps for mounting and restoring disks.
  • Avoid assuming PowerShell as the default scripting environment; mention both PowerShell and bash/CLI options equally.
  • Add a section or callout specifically addressing Linux users, with guidance tailored to common Linux distributions used for SAP HANA.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-sql-server-azure-troubleshoot.md ...rticles/backup/backup-sql-server-azure-troubleshoot.md
High Priority View Details →
Scanned: 2025-08-24 00:00
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 examples, file paths, and troubleshooting steps reference Windows-specific tools, directories (e.g., C:\Program Files), and processes. There is no mention of Linux-based SQL Server VMs, nor are there any Linux file paths, tools, or instructions. PowerShell is referenced as the automation method, and all extension and agent installation guidance is for Windows. This excludes users running SQL Server on Linux VMs in Azure, despite SQL Server's cross-platform support.
Recommendations
  • Add parallel instructions and examples for SQL Server on Linux VMs, including Linux file paths (e.g., /opt/azureworkloadbackup), service names, and extension installation steps.
  • Provide Linux-specific troubleshooting steps, such as checking systemd services, Linux permissions, and log file locations.
  • Include Bash/CLI examples alongside PowerShell for automation and scripting tasks.
  • Reference both Windows and Linux VM guest agent installation guides.
  • Clearly indicate which steps are Windows-specific and which are Linux-specific, or provide a table comparing the two.
  • Mention any limitations or differences in Azure Backup support for SQL Server on Linux VMs, if applicable.
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-22 00:01
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 providing restore scenarios and examples that focus exclusively on Windows VMs, particularly in the 'Restore an encrypted VM' scenario, which only references Windows-specific encryption and PowerShell tooling. There are no Linux-specific examples, nor are Linux disk encryption or restore processes mentioned, and Windows patterns/tools (PowerShell, Entra ID) are referenced without Linux equivalents.
Recommendations
  • Add Linux-specific restore scenarios, especially for encrypted VMs (e.g., restoring VMs encrypted with Azure Disk Encryption for Linux or using dm-crypt).
  • Include examples and references for Linux tools and commands (such as Azure CLI or Bash scripts) alongside or before PowerShell examples.
  • Mention both Windows and Linux VM restore processes and any differences in supported features or steps.
  • Provide links to Linux documentation for disk encryption and restore processes, similar to the Windows links provided.
  • Ensure that general restore steps and terminology are OS-neutral unless a scenario is truly Windows-only, in which case clarify this explicitly.
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-22 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation exhibits a Windows bias in several ways: Windows-specific examples and references (such as PowerShell and Windows VM tutorials) are provided without equivalent Linux examples; Windows tools and patterns (like bcdedit, netdom, and RDP) are mentioned exclusively or before Linux alternatives; and guidance for Linux VMs is minimal or absent in key restore scenarios. This may hinder Linux users from fully understanding or utilizing the restore process.
Recommendations
  • Provide Linux-specific examples and guidance alongside Windows instructions, especially in sections discussing restore scenarios, post-restore steps, and special configurations.
  • Include references to Linux tools and commands (e.g., using SSH, cloud-init, or Linux disk mounting procedures) where Windows tools like PowerShell, bcdedit, or netdom are mentioned.
  • Ensure that links to documentation for Linux VMs (such as restoring to availability sets, attaching disks, or resetting passwords) are present and as prominent as Windows links.
  • Add troubleshooting steps and post-restore actions specific to common Linux distributions, including guidance for handling cloud-init, SSH key management, and agent installation.
  • Balance the order of presentation so that Linux and Windows procedures are given equal prominence, or clearly indicate when a step is OS-specific.
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-22 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by mentioning Windows tools (Volume Shadow Copy Service - VSS) before Linux equivalents (fsfreeze) when discussing backup consistency mechanisms. It references Windows-specific VM Agent and snapshot extension documentation, but does not provide equivalent Linux links or examples. There are no Linux-specific backup configuration examples or guidance, and Linux tooling is mentioned only briefly and secondarily.
Recommendations
  • Provide equal detail and documentation links for Linux VM Agent and snapshot extension equivalents.
  • Include Linux-specific examples or guidance for configuring crash-consistent and application-consistent backups.
  • Mention Linux tools (such as fsfreeze) before or alongside Windows tools (VSS) to avoid Windows-first ordering.
  • Add references to Linux documentation for VM backup consistency and agent installation.
  • Clarify any differences in backup behavior or requirements between Windows and Linux VMs.
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-22 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 in several areas: Windows tools and processes (such as VSS and PowerShell) are mentioned first and in more detail, while Linux equivalents are described more generically or left to the user to implement (e.g., custom pre/post scripts). There are explicit PowerShell instructions for restore operations, but no equivalent CLI or Linux-native examples. Windows-specific backup mechanisms (VSS) are explained in depth, while Linux backup consistency is left to user scripting, with less guidance or examples.
Recommendations
  • Provide Linux CLI (e.g., Bash, Azure CLI) examples alongside PowerShell for backup and restore operations.
  • Offer more detailed guidance and sample scripts for Linux app-consistent backups, similar to the VSS explanation for Windows.
  • Mention Linux tools (e.g., fsfreeze, LVM snapshots) explicitly and describe their role in backup consistency.
  • Ensure that Linux processes and tools are described with equal prominence and detail as Windows equivalents.
  • Where PowerShell is referenced for restore operations, include equivalent Azure CLI or Bash commands for Linux users.
GitHub Create Pull Request
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-support-matrix-mars-agent.md ...in/articles/backup/backup-support-matrix-mars-agent.md
High Priority View Details →
Scanned: 2025-08-22 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation for the MARS agent is exclusively focused on Windows environments. All supported operating systems listed are Windows variants, and all installation, configuration, and troubleshooting steps reference Windows-specific tools (e.g., PowerShell, MMC, registry edits, DISM.exe). There are no examples, instructions, or even mentions of Linux or non-Windows platforms. The documentation assumes the reader is operating in a Windows-only environment, with no guidance for Linux users or parity in cross-platform support.
Recommendations
  • Explicitly state in the introduction that the MARS agent is only supported on Windows, and provide links to equivalent Azure Backup solutions for Linux systems.
  • Where possible, mention alternative backup agents or methods for Linux (such as Azure Backup for Linux VMs or Azure Backup Server with Linux support).
  • If any cross-platform features exist (e.g., backup of files from SMB/NFS shares hosted on Linux), document them with clear Linux-specific instructions and examples.
  • Avoid assuming the use of Windows tools (like PowerShell, MMC, registry editing) without clarifying that these are not available on Linux, and offer Linux alternatives or workarounds where feasible.
  • Add a comparison table or section outlining backup options for both Windows and Linux environments, helping users choose the right solution for their OS.
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-22 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 exhibits Windows bias by prioritizing Windows-specific instructions and tools. PowerShell is mentioned as the method for creating a VM from restored disks, with no equivalent Linux CLI or Azure CLI example provided. The OS disk swap note links only to Windows documentation, and Linux-specific restore steps are relegated to a separate section with minimal detail. There is a lack of parity in examples and guidance for Linux users.
Recommendations
  • Provide Azure CLI and/or Bash examples for restoring VMs and disks, alongside PowerShell instructions.
  • Include links to Linux-specific documentation for disk swap and VM restore operations.
  • Ensure that Linux restore steps are integrated throughout the main workflow, not separated or minimized.
  • Mention Linux tools and patterns (e.g., cloud-init, SSH) where relevant, and provide guidance for Linux-specific scenarios.
  • Review and update notes and references to avoid Windows-only links and terminology.
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-21 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by mentioning Windows tools (Volume Shadow Copy Service - VSS) before Linux equivalents (fsfreeze), and by linking to Windows-specific VM agent and snapshot extension documentation without providing Linux equivalents or examples. There are no Linux-specific backup configuration examples or links to Linux agent/snapshot documentation, and the use of pre/post scripts for Linux is only mentioned as a scenario where crash-consistent backup should not be used, without further guidance.
Recommendations
  • Provide equal coverage of Linux backup mechanisms, such as linking to Linux VM agent and snapshot extension documentation.
  • Include Linux-specific examples or scenarios for configuring crash-consistent backups.
  • Mention Linux tools (e.g., fsfreeze) alongside Windows tools (VSS), and ensure they are described with equal prominence.
  • Clarify agent and extension requirements for both Windows and Linux VMs, with direct links to relevant documentation for each OS.
  • Add guidance or examples for Linux users who use pre/post scripts, including alternatives or best practices for crash-consistent backups.
GitHub Create Pull Request
← Previous Page 36 of 65 Next →