755
Total Pages
562
Linux-Friendly Pages
193
Pages with Bias
25.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

520 issues found
Showing 351-375 of 520 flagged pages
Backup Soft delete for SQL server in Azure VM and SAP HANA in Azure VM workloads ...articles/backup/soft-delete-sql-saphana-in-azure-vm.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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 using the Azure portal and Azure PowerShell to manage soft delete for SQL Server and SAP HANA backups. All command-line examples use PowerShell, with no mention of Bash, Azure CLI, or Linux-native tools. The PowerShell section appears after the portal instructions, but there is no Linux/macOS parity in command-line guidance, nor any indication of how non-Windows users should proceed.
Recommendations
  • Add equivalent examples using Azure CLI (az backup ...) for all PowerShell operations.
  • Explicitly mention cross-platform options for command-line management, such as Azure CLI, and provide links to relevant documentation.
  • Clarify that PowerShell Core is available on Linux/macOS, or recommend Azure CLI for those platforms.
  • Ensure screenshots and UI instructions are platform-neutral or note any differences for Linux/macOS users.
Backup Soft delete for virtual machines ...b/main/articles/backup/soft-delete-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions and examples for performing soft delete operations using the Azure Portal and Azure PowerShell, but omits equivalent examples or guidance for Linux/macOS users (e.g., Azure CLI or Bash). PowerShell is presented as the only command-line option, and is shown before REST API, which is less user-friendly for many users. There are no Linux-native or cross-platform command-line instructions, and Windows-centric tools (PowerShell) are emphasized.
Recommendations
  • Add Azure CLI examples for all operations (delete, undelete, resume backup) alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell must be used, and provide installation instructions.
  • Reorder or parallelize command-line sections so that Azure CLI is presented before or alongside PowerShell, to avoid Windows-first bias.
  • Include Bash script snippets or guidance for REST API usage with curl, to help Linux/macOS users.
  • Clarify tool/platform requirements for each method, so users know which options are available on their OS.
Backup Tutorial - Back up Azure Database for PostgreSQL server ...lob/main/articles/backup/tutorial-postgresql-backup.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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 environments, primarily by referencing PowerShell scripts for privilege assignment and not providing equivalent Linux/macOS command examples. The mention of PowerShell occurs before alternatives like PG admin or PSQL, and no explicit Linux/macOS shell commands are shown for critical steps. This may create friction for users on non-Windows platforms.
Recommendations
  • Provide explicit Linux/macOS command-line examples (e.g., using psql or bash scripts) for database privilege assignment and other relevant steps.
  • Mention cross-platform tools (PG admin, psql) before or alongside PowerShell, and clarify that all steps can be completed on Linux/macOS.
  • Add screenshots or instructions for Linux/macOS environments where UI or CLI steps differ.
  • Ensure ARM template instructions are platform-neutral and clarify how to run them from Linux/macOS.
  • Review all references to PowerShell and supplement with equivalent bash/psql commands.
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools
Summary
The documentation provides comprehensive coverage for Azure portal (GUI), PowerShell, and Azure CLI methods. However, there is a noticeable Windows bias: PowerShell (a Windows-centric tool) is given a dedicated section with extensive examples and scripting, and is referenced before CLI in several places. The CLI section is present and detailed, but PowerShell is often positioned as the primary automation method. There are no Linux/macOS-specific shell examples (e.g., Bash), and PowerShell is suggested for scripting and automation, which may disadvantage Linux users who prefer Bash or native shell scripting. The initial 'Get started' instructions for PowerShell include downloading PowerShell from GitHub, which is not native on Linux/macOS. The portal instructions are OS-neutral, but the scripting/automation focus leans Windows.
Recommendations
  • Add Bash shell scripting examples for Linux/macOS users, especially for automation tasks.
  • Explicitly mention that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Reorder sections so that CLI and portal instructions appear before PowerShell, or present all scripting options together.
  • Clarify PowerShell installation steps for Linux/macOS, or link to cross-platform PowerShell docs.
  • Include notes or links for Linux/macOS users on how to adapt PowerShell scripts or use CLI alternatives.
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page exhibits moderate Windows bias by repeatedly mentioning PowerShell as a primary automation method and in example workflows, often listing it before cross-platform tools like CLI, REST API, or SDKs. Automation scenarios and sample workflows reference PowerShell and Runbooks, which are more familiar to Windows users, with no explicit Linux/macOS shell or scripting examples. However, the page does acknowledge CLI, SDKs, Terraform, and Ansible, and links to their samples.
Recommendations
  • Provide explicit Linux/macOS shell (bash) examples alongside PowerShell, especially in automation scenarios.
  • Ensure CLI examples are shown before or alongside PowerShell to emphasize cross-platform support.
  • Include references or links to Linux/macOS automation workflows (e.g., using cron, bash scripts, Ansible playbooks) in relevant sections.
  • Clarify that Azure Automation Runbooks can be authored in Python or other languages, not just PowerShell.
  • Add sample code snippets for Linux/macOS environments in key sections.
Backup Quickstart - Configure vaulted backup for Azure Data Lake Storage using ARM or Bicep template ...ata-lake-storage-backup-configure-quickstart-arm-bicep.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides only PowerShell deployment examples for both ARM and Bicep templates, with no mention of Bash, Azure CLI, or cross-platform alternatives. This creates friction for Linux/macOS users who may not use PowerShell or prefer Bash/Azure CLI. The deployment instructions assume PowerShell is available, which is more common on Windows systems.
Recommendations
  • Add Azure CLI and Bash examples for deploying ARM and Bicep templates.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
  • Clarify that the deployment steps are cross-platform when using Azure Cloud Shell, but provide local deployment instructions for Linux/macOS users.
  • Consider listing Azure CLI/Bash examples before or alongside PowerShell to avoid Windows-first perception.
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing more detailed, tool-specific instructions for Windows VMs (e.g., VSS integration, PowerShell restore instructions) while Linux guidance is less explicit and relies on users creating their own scripts. Windows tools and patterns (VSS, PowerShell) are mentioned first and in more detail, whereas Linux equivalents are referenced in passing or require user implementation.
Recommendations
  • Provide explicit Linux command-line examples (e.g., Bash, CLI) for backup and restore operations, especially where PowerShell is referenced for Windows.
  • Include step-by-step Linux backup/restore scenarios, not just references to custom scripts.
  • Mention Linux tools (e.g., fsfreeze) with usage examples and troubleshooting tips, similar to the VSS coverage for Windows.
  • Ensure parity in troubleshooting and best practices sections for both Windows and Linux VMs.
  • When referencing automation, include Azure CLI or Bash scripts alongside PowerShell examples.
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily describes backing up Azure Managed Disks using the Azure portal, which is cross-platform. However, when mentioning automation and scripting, PowerShell is listed first and more prominently than Azure CLI. There are references to PowerShell scripts for automating backup across subscriptions, but no explicit Linux/macOS shell examples or guidance. The CLI is mentioned, but not as the primary or first example. No Linux-specific tools or workflows are described, and there is no parity in example scripts for Linux users.
Recommendations
  • Present Azure CLI examples alongside PowerShell, or even before PowerShell, to ensure Linux/macOS users have clear guidance.
  • Explicitly state that all portal instructions are OS-agnostic, and provide links to CLI and REST API guides for users who prefer command-line automation.
  • Add sample bash scripts or CLI commands for common tasks, such as cross-subscription backup configuration.
  • Avoid listing PowerShell before CLI unless there is a technical reason; alternate order or present both equally.
  • Include a note clarifying that PowerShell is available on Linux/macOS, but CLI may be more familiar to non-Windows users.
Backup Back up SQL Server always on availability groups ...les/backup/backup-sql-server-on-availability-groups.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation focuses exclusively on SQL Server AG backups within Azure VMs, with no mention of Linux-based SQL Server deployments or examples. All instructions implicitly assume Windows environments, as SQL Server AG is traditionally Windows-centric, but recent versions support Linux. There are no references to Linux tools, commands, or considerations, nor is there guidance for Linux users attempting similar tasks.
Recommendations
  • Explicitly state OS requirements and limitations (e.g., if AG backup is Windows-only, clarify this early).
  • If Linux-based SQL Server AGs are supported, add dedicated sections or examples for Linux environments, including any differences in backup configuration, node registration, and failover handling.
  • Mention any Azure Backup limitations for Linux SQL Server AGs, or provide alternative backup strategies for Linux users.
  • Include references to Linux tools (such as systemd, shell commands) where relevant, and clarify any differences in workload backup extension installation or operation on Linux.
  • Add troubleshooting notes for Linux users, if applicable.
Backup Update the existing VM backup policy using CLI ...docs/blob/main/articles/backup/modify-vm-policy-cli.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a file path example using Windows-style paths (C:\temp2\Policy.json) and does not mention or show Linux/macOS equivalents. There are no PowerShell-specific commands, but the file path usage implicitly favors Windows users and may confuse Linux/macOS users. No explicit Linux/macOS instructions or examples are given.
Recommendations
  • Include Linux/macOS file path examples (e.g., /home/user/Policy.json) alongside Windows examples.
  • Add a note clarifying that file paths should be adapted to the user's operating system.
  • Consider showing both Windows and Linux/macOS command examples where file paths are referenced.
  • Explicitly state that Azure CLI works cross-platform and provide guidance for Linux/macOS users.
Backup Automation in Azure Backup support matrix ...blob/main/articles/backup/backup-support-automation.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First πŸ”§ Windows Tools
Summary
The documentation consistently lists PowerShell as the first automation method for every operation, and provides extensive PowerShell support and example links. PowerShell is a Windows-centric tool, and its prominence may suggest a Windows-first approach. There is no explicit mention of Linux/macOS shell scripting, nor are Bash or platform-neutral scripting examples provided. The documentation assumes users are familiar with PowerShell, which may create friction for Linux/macOS users who prefer Bash or other native tools.
Recommendations
  • Alternate the order of PowerShell and CLI in tables, or list CLI first for parity.
  • Explicitly mention that Azure CLI is fully cross-platform and provide Bash/zsh example snippets where relevant.
  • Add notes or links for Linux/macOS users on how to install and use Azure CLI and REST API from their platforms.
  • Where PowerShell is referenced, clarify if PowerShell Core (cross-platform) is supported, and provide guidance for non-Windows users.
  • Consider adding a 'Platform considerations' section to clarify tool support and best practices for Linux/macOS users.
Backup Quickstart - Resource Manager template VM Backup .../blob/main/articles/backup/quick-backup-vm-template.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias: deployment instructions and code samples are exclusively provided using Azure PowerShell, with no equivalent Azure CLI or Bash examples. The template itself is described as creating a Windows VM, and PowerShell is referenced as the primary automation tool. While Azure CLI and REST API are mentioned as alternatives, no concrete examples or guidance are given for Linux/macOS users. The cleanup steps also use PowerShell cmdlets only.
Recommendations
  • Add Azure CLI and Bash examples for template deployment and resource cleanup alongside PowerShell scripts.
  • Clarify whether the ARM template supports Linux VM creation, or provide a Linux VM variant/template.
  • Present CLI and PowerShell instructions in parallel, or default to CLI for cross-platform parity.
  • Explicitly mention platform compatibility for each step and tool.
  • Link directly to Linux/macOS-friendly guides where available.
Backup Quickstart - Install Azure Backup extension in an AKS cluster ...main/articles/backup/quick-install-backup-extension.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes installation of the Azure Backup extension in AKS using the Azure Portal UI, which is most commonly accessed on Windows. There are no command-line examples (e.g., Azure CLI, kubectl) shown in the main quickstart, and no Linux/macOS-specific guidance is provided. The 'Next steps' section mentions CLI, PowerShell, ARM, Bicep, and Terraform, but these are not demonstrated in the quickstart itself.
Recommendations
  • Add step-by-step instructions for installing the backup extension using Azure CLI and kubectl, which are cross-platform and widely used on Linux/macOS.
  • Include screenshots or terminal output for CLI-based installation to complement the portal-based instructions.
  • Explicitly mention that the Azure Portal is accessible from any OS, but provide parity by showing how to perform the same actions from the command line.
  • Ensure that references to PowerShell are balanced with equivalent Bash/CLI examples.
Backup About the Azure Virtual Machine restore process ...cs/blob/main/articles/backup/about-azure-vm-restore.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page shows evidence of Windows bias, particularly in the 'Restore an encrypted VM' scenario, where only PowerShell is mentioned as the tool for creating the VM after disk restore. All example links for encrypted VM restoration point to Windows-specific documentation, with no mention of Linux equivalents or CLI alternatives. There are no Linux-specific restore instructions or examples, and Windows tools are referenced exclusively for critical restore steps.
Recommendations
  • Add explicit instructions and examples for restoring encrypted Linux VMs, including references to relevant Linux documentation.
  • Provide Azure CLI or Bash-based workflows for VM restoration, especially for steps currently described with PowerShell.
  • Ensure parity in documentation by listing both Windows and Linux restore methods, tools, and scenarios side-by-side.
  • Link to Linux disk encryption and restore guides where appropriate.
Backup Configure Vaulted Backup for Azure Data Lake Storage using Azure portal, PowerShell, or Azure CLI ...les/backup/azure-data-lake-storage-configure-backup.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides full parity between Azure Portal, PowerShell, and Azure CLI, but the PowerShell section is notably more detailed, with multi-step example scripts and explicit cmdlets. PowerShell is a Windows-centric tool, and its prominence may create a perception of Windows bias. The CLI section is present and functional, but PowerShell examples are more elaborate and appear before CLI examples in the document structure.
Recommendations
  • Expand Azure CLI examples to match the depth and clarity of PowerShell examples, including step-by-step instructions and sample scripts.
  • Explicitly mention cross-platform compatibility for Azure CLI and PowerShell Core (which runs on Linux/macOS), to reassure non-Windows users.
  • Consider providing Bash shell examples for common tasks, or clarify that Azure CLI commands are intended for Linux/macOS as well as Windows.
  • Ensure that all portal-based instructions are platform-neutral and avoid references to Windows-specific UI elements.
  • Add a note about PowerShell Core support for Linux/macOS if applicable, or link to installation guides for non-Windows platforms.
Backup Back up Azure Kubernetes Service by using Azure Backup ...cles/backup/azure-kubernetes-service-cluster-backup.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It repeatedly references Azure PowerShell as an alternative to the Azure portal for backup and restore operations, but does not mention or provide examples for Azure CLI, Bash, or Linux-native tools. The 'Next steps' section lists PowerShell before any Linux-friendly alternatives, and there are no command-line examples for Linux/macOS users. The documentation assumes users will use the Azure portal or PowerShell, which may create friction for those on Linux or macOS who prefer CLI workflows.
Recommendations
  • Add Azure CLI examples for all backup and restore operations alongside PowerShell instructions.
  • Explicitly mention Azure CLI as a supported method in introductory sections and 'Next steps'.
  • Provide Bash script samples where appropriate, especially for automation scenarios.
  • Ensure screenshots and instructions are platform-neutral or include both Windows and Linux variants.
  • Clarify that all operations can be performed from Linux/macOS environments using CLI tools.
Backup Restore Azure Kubernetes Service (AKS) using Azure Backup ...les/backup/azure-kubernetes-service-cluster-restore.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias by explicitly referencing Azure PowerShell as an alternative method for restoring AKS clusters, without mentioning or providing parity for Linux/macOS-friendly tools like Azure CLI or Bash scripts. The only command-line option referenced is PowerShell, and no examples or guidance are given for Linux-native workflows. This may create friction for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI instructions and examples for restoring AKS clusters, ensuring Linux/macOS users have clear guidance.
  • Explicitly mention cross-platform options (e.g., Bash, Azure CLI) alongside PowerShell in introductory and instructional sections.
  • Include screenshots or walkthroughs for Linux/macOS environments where relevant.
  • Review linked articles (such as the PowerShell restore guide) for similar bias and provide CLI alternatives.
Backup Back up Azure Kubernetes Service (AKS) using Azure CLI ...p/azure-kubernetes-service-cluster-backup-using-cli.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Powershell Heavy Windows First
Summary
The documentation is primarily focused on Azure CLI commands, which are cross-platform, but there are several signs of Windows bias. The introduction mentions Azure PowerShell as an alternative, and the only non-Azure CLI example is a private endpoint creation script that uses PowerShell-style syntax (backticks for line continuation and variable assignment with $). This script is not Linux/macOS friendly, as Bash users would need to adapt it. Additionally, the PowerShell alternative is mentioned before any Linux-specific guidance, and there are no explicit Bash or Linux/macOS examples for tasks that may differ in shell syntax.
Recommendations
  • Provide Bash/Linux/macOS equivalents for any PowerShell-style scripts, especially for multi-line commands and variable assignment.
  • When mentioning alternatives, list Azure CLI (cross-platform) first, and clarify that PowerShell is primarily for Windows users.
  • Add notes or code tabs for Linux/macOS users where command syntax differs (e.g., line continuation, variable assignment).
  • Ensure all example scripts are compatible with Bash or provide separate examples for Bash and PowerShell.
  • Explicitly state that Azure CLI commands work on all platforms and highlight any platform-specific caveats.
Backup Back up Azure Local virtual machines with MABS ...e-stack-hyperconverged-infrastructure-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
πŸ”§ Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. The backup solution (MABS) is inherently Windows-centric, and nearly all examples, commands, and screenshots reference Windows tools (e.g., PowerShell, .exe installers, Windows Firewall rules, Hyper-V). Linux support is mentioned only briefly and generically, with no concrete Linux-specific instructions, examples, or screenshots. All command-line examples use Windows syntax, and prerequisites and recovery steps are described in terms of Windows environments and tools.
Recommendations
  • Provide explicit Linux backup and recovery examples, including command-line steps for agent installation, configuration, and recovery on Linux VMs.
  • Include Linux-specific troubleshooting steps and prerequisites (e.g., required packages, agent compatibility, SELinux/AppArmor considerations).
  • Add screenshots or CLI output from Linux environments where applicable.
  • Clarify limitations and differences for Linux VMs (e.g., file-consistent vs. application-consistent backups) in relevant sections.
  • Where PowerShell or Windows-specific commands are given, offer Linux alternatives (e.g., bash commands, systemctl usage, firewall-cmd for firewalls).
  • Reorder sections to present Linux and Windows instructions in parallel, or clearly separate them for clarity.
Backup Tutorial - Back up Azure Managed Disks using Azure Backup ...main/articles/backup/back-up-managed-disks-tutorial.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The tutorial focuses exclusively on using the Azure portal for backup operations, which is cross-platform. However, when mentioning automation or scripting, PowerShell is listed before CLI, and links to PowerShell scripts are provided alongside CLI, but no Linux/macOS-specific examples or considerations are given. There is no mention of Linux tools, shell scripts, or platform-specific guidance for non-Windows users. The documentation assumes users are familiar with PowerShell and does not provide parity for Linux/macOS users in terms of example scripts or troubleshooting steps.
Recommendations
  • Provide explicit Bash/CLI examples for Linux/macOS users alongside PowerShell examples.
  • When referencing automation, mention Azure CLI first or equally with PowerShell.
  • Include notes or sections on running Azure CLI commands from Linux/macOS terminals.
  • Add troubleshooting steps or tips relevant to Linux/macOS environments.
  • Ensure links to CLI documentation are as prominent as PowerShell links.
Backup Back up Hyper-V virtual machines with MABS ...ticles/backup/back-up-hyper-v-virtual-machines-mabs.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Hyper-V on Windows Server, and Microsoft Azure Backup Server (MABS). Windows-specific tools, features, and patterns (e.g., VSS, Hyper-V Integration Services, registry keys, NTLM authentication, BitLocker, SMB shares, SCSI controller requirements) are described in detail, while Linux support is only briefly mentioned and lacks concrete examples or guidance. Item-level recovery is explicitly stated as available only for Windows Server VMs, with no equivalent for Linux VMs.
Recommendations
  • Provide detailed, step-by-step backup and recovery instructions for Linux VMs, including any limitations or differences in process.
  • Include Linux-specific examples and screenshots where applicable, especially for backup and recovery operations.
  • Clarify what features (e.g., item-level recovery, consistency checks) are available or unavailable for Linux VMs, and suggest workarounds if possible.
  • Mention Linux authentication and storage patterns (e.g., ext4, XFS, NFS) where relevant, not just Windows-centric technologies.
  • Add a comparison table summarizing feature parity between Windows and Linux VM backup/recovery in MABS.
Backup Restore VMs by using the Azure portal using Azure Backup ...b/main/articles/backup/backup-azure-arm-restore-vms.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Many example links and references point to Windows-specific guides (e.g., restoring VMs using PowerShell, attaching disks to Windows VMs, and managing IP addresses via PowerShell). Windows terminology and tools (PowerShell, bcdedit, netdom) are used in examples and troubleshooting steps, while Linux equivalents are missing or only briefly mentioned. Windows scenarios (Hybrid Use Benefit, SQL VMs, domain controllers) are described in detail, whereas Linux-specific restore scenarios are not covered. In post-restore steps, Windows commands are shown for fixing domain join issues, but Linux troubleshooting is limited to a brief mention of cloud-init and password reset.
Recommendations
  • Provide Linux-specific examples and links for disk attachment, VM creation, and troubleshooting (e.g., using Azure CLI, Bash, or cloud-init).
  • Include parity for Linux restore scenarios, such as restoring VMs with SSH keys, handling SELinux/AppArmor, and restoring Linux-based SQL or application servers.
  • Add troubleshooting steps and commands for common Linux issues after restore (e.g., fixing broken fstab, network configuration, or agent installation).
  • Present examples using Azure CLI and Bash alongside PowerShell, and avoid showing Windows tools first or exclusively.
  • Clarify when instructions are OS-specific and offer alternatives for Linux/macOS users.
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example πŸ”§ Windows Tools Windows First
Summary
The documentation page demonstrates a notable Windows bias. Backup methods and agents for on-premises machines focus exclusively on Windows (MARS agent, DPM, MABS), with explicit statements that Linux machines aren't supported for direct backup. Windows tools and patterns (VSS, MARS agent) are described in detail, while Linux backup scenarios are omitted. Examples and workflows are Windows-centric, and Windows is mentioned first and exclusively in critical sections.
Recommendations
  • Clearly state Linux backup limitations and provide alternative solutions or references for Linux backup (e.g., Azure Backup for Linux VMs, third-party solutions, or native Azure VM backup for Linux).
  • Add parity examples and workflows for Linux environments where possible, such as backing up Linux Azure VMs, or clarify that on-premises Linux backup is unsupported and suggest alternatives.
  • Include a comparison table or section summarizing support for both Windows and Linux, making it easier for users to understand platform differences.
  • If Linux support is planned, note this in the documentation and link to roadmap or feedback channels.
Backup Replace your tape infrastructure by using Azure Backup ...n/articles/backup/backup-azure-backup-cloud-as-tape.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation page focuses on Azure Backup in the context of tape replacement, but references System Center Data Protection Manager (DPM)β€”a Windows-only toolβ€”and links to a 'backup-windows-with-mars-agent' guide in the Next Steps section. There are no Linux/macOS-specific examples, tools, or instructions, and the only backup agent mentioned is the Windows MARS agent. No mention is made of Linux backup agents or how Linux servers can participate in Azure Backup for tape replacement scenarios.
Recommendations
  • Include explicit instructions and examples for configuring Azure Backup on Linux servers, including supported agents and setup steps.
  • Reference Linux-compatible backup solutions (such as Azure Backup Server or third-party tools) where appropriate.
  • Provide parity in screenshots and walkthroughs for Linux environments.
  • Add links to documentation for Linux backup scenarios in the Next Steps section.
  • Clarify whether the described features and policies apply equally to Linux workloads, and note any differences.
Backup Create backup policies via REST API in Azure Backup ...up/backup-azure-arm-userestapi-createorupdatepolicy.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation consistently uses 'Pacific Standard Time' as the default time zone in examples, which is a Windows-specific time zone identifier. It does not mention Linux/macOS time zone formats (such as IANA/Olson identifiers like 'America/Los_Angeles'), nor does it clarify cross-platform compatibility for time zone values. However, there are no explicit Windows-only tools, PowerShell commands, or CLI examples; all API usage is platform-neutral.
Recommendations
  • Clarify which time zone formats are accepted by the API (Windows, IANA, both).
  • Provide examples using both Windows and IANA time zone identifiers, or explicitly state that only Windows time zones are supported.
  • Add a note for Linux/macOS users on how to find and use the correct time zone value.
  • If only Windows time zones are supported, link to a mapping resource for Linux/macOS users.