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 226-250 of 520 flagged pages
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-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is mentioned as the primary method for creating a VM from restored disks, with no equivalent CLI or Linux-native example provided. The OS disk swap note links only to Windows-specific documentation. Linux-specific guidance is relegated to a separate step, and lacks detailed, step-by-step instructions or examples. Windows tools and patterns (such as PowerShell and OS disk swap) are referenced before or instead of Linux equivalents.
Recommendations
  • Provide Azure CLI and/or Bash examples for restoring and recreating VMs from restored disks, alongside PowerShell.
  • Include links to Linux-specific documentation for OS disk swap and VM restore operations.
  • Offer detailed, step-by-step instructions for restoring encrypted Linux VMs, including ADE extension reinstallation and configuration.
  • Ensure that Linux and Windows procedures are presented with equal prominence and detail throughout the documentation.
  • When referencing tools or commands, mention both Windows and Linux options together, or in parallel sections.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sap-ase-backup-support-matrix.md .../main/articles/backup/sap-ase-backup-support-matrix.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows Explicit Exclusion Linux Only Examples Missing Windows Example
Summary
The documentation page is strongly Linux-centric, explicitly stating that only SAP ASE databases running on Azure Linux VMs are supported for backup, with Windows configurations listed as unsupported. All example scripts and operational instructions use Linux tools (bash, sudo, shell scripts), with no PowerShell, Windows command-line, or Windows tool examples provided. Azure CLI/PowerShell support is explicitly marked as unavailable, and there are no references to Windows-specific patterns or tools.
Recommendations
  • Clarify the roadmap for Windows support, if any, or provide a rationale for Linux-only support to help Windows users understand the limitation.
  • If Windows support is planned, add equivalent examples and instructions for Windows environments (e.g., PowerShell scripts, Windows command-line usage).
  • Explicitly mention alternative backup strategies for SAP ASE on Windows VMs, if available, or link to relevant documentation.
  • Consider adding a section that addresses common questions from Windows users, including migration guidance or interoperability notes.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sap-ase-database-about.md ...cs/blob/main/articles/backup/sap-ase-database-about.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits subtle Windows bias by referencing Windows-specific VM creation links, omitting explicit Linux examples, and not clarifying cross-platform parity for backup and restore operations. There are no PowerShell-heavy sections, but the only explicit VM creation link points to a Windows VM guide, and there are no Linux-specific instructions or examples. The documentation does not mention Linux tools or provide Linux-first guidance, despite SAP ASE being commonly deployed on Linux.
Recommendations
  • Add explicit examples and links for both Windows and Linux VM creation and management, ensuring Linux parity.
  • Clarify that the backup and restore procedures apply equally to Linux-based Azure VMs, or provide any Linux-specific prerequisites or differences.
  • Include Linux-specific instructions or screenshots where relevant, such as running the preregistration script on Linux (e.g., using Bash in Azure Cloud Shell).
  • Where VM restore options are discussed, provide links to both Windows and Linux VM creation guides.
  • Explicitly state supported operating systems for the Azure Backup plugin for ASE, and highlight any OS-specific considerations.
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-12-29 18:00
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 consistently referencing Azure portal workflows and PowerShell/CLI scripts for permission management, without providing explicit Linux shell examples or guidance. The use of terms like 'PowerShell or CLI script' and the absence of Linux-specific commands or tools (such as bash scripts or Linux-native utilities) suggests a preference for Windows-centric administration patterns. Additionally, the documentation does not clarify how to perform key steps (like disk mounting or permission assignment) on Linux VMs, which are common for SAP HANA deployments.
Recommendations
  • Add explicit Linux shell (bash) examples for disk mounting and permission assignment, alongside PowerShell/CLI instructions.
  • Clarify how to perform restore operations using Linux-native tools and commands, especially for SAP HANA running on Linux VMs.
  • Ensure that references to scripting (e.g., 'PowerShell or CLI script') are accompanied by both Windows and Linux command examples.
  • Include screenshots or step-by-step instructions for Linux environments in addition to Azure portal workflows.
  • Review terminology to avoid Windows-first language and ensure equal visibility for Linux administration patterns.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/selective-disk-backup-restore.md .../main/articles/backup/selective-disk-backup-restore.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides extensive examples for Azure CLI and PowerShell, with PowerShell (a Windows-centric tool) featured as a primary automation method. There are no explicit Linux shell (bash) or cross-platform scripting examples, and PowerShell is presented as the only scripting alternative to the CLI. Windows-specific tools and terminology (e.g., drive letters, BitLocker) are mentioned before Linux equivalents, and Linux-specific instructions are limited to brief notes about required utilities (lsblk, lsscsi) rather than full examples. There are no bash or Linux-native command examples for configuring or managing selective disk backup, and the documentation assumes familiarity with Windows tools and patterns.
Recommendations
  • Add bash/Linux shell script examples for common operations (e.g., using Azure CLI in bash scripts, handling output with jq, etc.).
  • Provide Linux-native automation examples alongside PowerShell, such as bash scripts for configuring selective disk backup.
  • When discussing OS-specific requirements (e.g., BitLocker for Windows, dm-crypt for Linux), present Linux and Windows information in parallel rather than Windows-first.
  • Include troubleshooting steps and examples for common Linux distributions, not just notes about required utilities.
  • Clarify that PowerShell Core is cross-platform, but also provide bash alternatives for users who prefer native Linux tooling.
  • Ensure that all CLI examples are shown in a way that is copy-paste friendly for both Windows (cmd/PowerShell) and Linux (bash) environments.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/scripts/set-system-state-backup-policy.md ...icles/backup/scripts/set-system-state-backup-policy.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides a PowerShell script for managing system state backup policies with the MARS agent, which is a Windows-centric tool. All instructions, examples, and referenced modules are specific to Windows environments, with no mention of Linux equivalents, alternative scripting languages, or cross-platform approaches. The page assumes the user is on Windows and does not address Linux users or provide parity for non-Windows platforms.
Recommendations
  • Include equivalent instructions or scripts for Linux environments, if supported, using Bash or other common Linux tools.
  • Explicitly state platform requirements and limitations at the beginning of the documentation.
  • If the MARS agent is Windows-only, suggest Linux alternatives for backup management (e.g., Azure Backup for Linux, or other supported agents).
  • Provide links or references to Linux documentation for similar backup policy management tasks.
  • Consider adding a comparison table of backup solutions for Windows and Linux, highlighting feature parity and differences.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/scripts/disable-soft-delete-for-file-shares.md .../backup/scripts/disable-soft-delete-for-file-shares.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides command-line examples using armclient with Windows-style paths (e.g., '.\rqbody-disableSoftDelete.json'), which are specific to Windows and PowerShell. There are no Linux or macOS shell examples, nor is there guidance for using armclient on non-Windows platforms. The mention of PowerShell and Azure CLI is only in a link, not in the main content. This creates a bias toward Windows users and may confuse or exclude Linux/macOS users.
Recommendations
  • Provide equivalent Linux/macOS shell examples, using forward slashes (e.g., './rqbody-disableSoftDelete.json') and bash syntax.
  • Explicitly state that armclient is cross-platform (if it is), or provide alternative tools/commands for Linux/macOS.
  • Add a section or callout for Linux/macOS users, showing how to install and use armclient on those platforms.
  • When referencing file paths or commands, show both Windows and Linux/macOS variants side-by-side.
  • Consider including Azure CLI or REST API examples directly in the documentation, not just as a link.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/scripts/set-file-folder-backup-policy.md ...ticles/backup/scripts/set-file-folder-backup-policy.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides a PowerShell script sample and instructions for managing backup policies using the MARS agent, which is a Windows-specific tool. There are no examples, instructions, or references for Linux environments, nor are Linux-compatible tools or scripting languages mentioned. The documentation assumes a Windows context throughout.
Recommendations
  • Add equivalent script samples for Linux environments, using Bash or Python.
  • Mention and provide guidance for Linux-compatible backup tools (e.g., rsync, cron, Azure CLI, etc.) if supported.
  • Clarify platform prerequisites and limitations at the top of the page.
  • If the MARS agent is Windows-only, explicitly state this and link to Linux backup solutions.
  • Provide parity in documentation structure and detail for Linux users, including example commands and automation patterns.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/sql-support-matrix.md ...e-docs/blob/main/articles/backup/sql-support-matrix.md
High Priority View Details →
Scanned: 2025-12-29 18:00
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. Only Windows Server operating systems are listed as supported, with Linux explicitly stated as unsupported. All examples and tooling references (e.g., PowerShell) are Windows-centric, with no mention of Linux equivalents or parity. The backup configuration is only supported via the Azure portal or PowerShell, and CLI is not supported, further reinforcing Windows bias.
Recommendations
  • Clearly indicate plans or timelines for Linux support, if any, or provide rationale for its absence.
  • Add Linux support where feasible, including examples and instructions for common Linux distributions running SQL Server in Azure VMs.
  • Support Azure CLI for backup configuration to enable cross-platform management, and provide CLI examples alongside PowerShell.
  • Where features are Windows-only, explicitly state alternatives or workarounds for Linux users.
  • Review all tooling and example sections to ensure parity and visibility for Linux administrators.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides detailed instructions for the Azure Portal and Azure PowerShell, both of which are Windows-centric tools. There are no examples or instructions for Linux-native tools (e.g., Azure CLI, Bash scripting), nor is there mention of Linux command-line equivalents. PowerShell is presented as the only scripting/automation method, and no Linux-first or cross-platform guidance is provided.
Recommendations
  • Add Azure CLI examples for all operations (delete, undelete, restore, resume backup) alongside PowerShell examples.
  • Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide Bash shell command examples.
  • If certain operations are not supported in Azure CLI, state this clearly and provide alternative guidance for Linux users.
  • Reorder sections or provide parallel tabs for Azure CLI and PowerShell to ensure Linux users are not an afterthought.
  • Include screenshots or walkthroughs using the Azure CLI in a Linux terminal where possible.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing a PowerShell script for undeleting file shares and not providing equivalent examples or scripts for Linux environments (e.g., Bash, Azure CLI). The term 'script' is used without clarifying its platform, but the linked script is PowerShell-based. There are no Linux or cross-platform command-line examples, and the documentation does not mention or prioritize Linux tools or workflows.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for undeleting file shares and other operations, and link to them alongside the PowerShell script.
  • Explicitly state when a script is PowerShell-specific, and offer guidance for Linux/macOS users.
  • Include examples using Azure CLI, which is cross-platform, for all major operations (undelete, disable soft delete, etc.).
  • Review all documentation links and ensure that Linux and macOS users are supported with clear, platform-agnostic instructions.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/threat-detection-configure-monitor-tutorial.md .../backup/threat-detection-configure-monitor-tutorial.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by only referencing Microsoft-centric tools and workflows (Azure Portal, Microsoft Defender for Cloud, Microsoft Sentinel) without mentioning or providing parity for Linux-specific tools, command-line interfaces, or automation methods. There are no examples or guidance for Linux users (e.g., using Azure CLI, Bash, or Linux-based automation), and all instructions are oriented around GUI workflows typical for Windows administrators.
Recommendations
  • Add examples using Azure CLI and/or Azure PowerShell for enabling and monitoring threat detection, ensuring both Windows and Linux users can follow along.
  • Explicitly mention that the Azure Portal and Defender for Cloud are cross-platform, and clarify any platform-specific requirements or limitations.
  • Provide sample scripts or automation steps that can be run from Linux environments (e.g., Bash scripts, az CLI commands) for all major operations described.
  • Include a section or callout addressing Linux VM backup scenarios, and note any differences or considerations for Linux VMs.
  • Where screenshots are provided, consider including CLI output or code snippets as alternatives for users who do not use the Azure Portal.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/transport-layer-security.md .../blob/main/articles/backup/transport-layer-security.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively discusses enabling TLS 1.2 for Azure Backup on Windows systems, with detailed registry and .NET Framework configuration steps. There are no instructions, examples, or references for Linux systems or cross-platform scenarios. All troubleshooting and configuration guidance is Windows-centric, and Windows tools (registry, KB articles) are mentioned exclusively.
Recommendations
  • Add a dedicated section for enabling and verifying TLS 1.2 on Linux systems, including relevant configuration files (e.g., OpenSSL, system-wide TLS settings).
  • Provide command-line examples for Linux (e.g., using openssl, curl, or systemctl) to verify TLS support.
  • Include troubleshooting steps and common issues for Linux environments.
  • Reference Azure Backup client requirements and TLS configuration for Linux agents, if available.
  • Ensure parity in examples and guidance for both Windows and Linux users, presenting both platforms side-by-side where possible.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows by providing PowerShell scripts as the primary or only example for granting privileges to database users. There is no equivalent example for Linux users (e.g., bash shell, psql commands), and PowerShell is mentioned before alternatives like PG admin or PSQL. This can make it harder for Linux users to follow the tutorial, especially in environments where PowerShell is not available.
Recommendations
  • Add explicit Linux/Unix examples for granting privileges, such as using psql commands or bash scripts.
  • When referencing PowerShell, always provide equivalent steps for Linux (e.g., using psql or shell scripts) and mention them together.
  • Avoid presenting Windows/PowerShell methods first; instead, list both Windows and Linux approaches side by side or in parallel sections.
  • Clarify that PG admin and PSQL are cross-platform tools and provide example commands for both.
  • Review all steps to ensure that Linux users can complete the tutorial without needing access to PowerShell.
Backup https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/tutorial-sql-backup.md ...-docs/blob/main/articles/backup/tutorial-sql-backup.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on SQL Server running on Azure VMs with Windows OS. It exclusively references Windows-specific components (such as AzureBackupWindowsWorkload extension, NT Service accounts, and SQLIaaSExtension), and does not mention or provide guidance for SQL Server on Linux VMs. There are no Linux-specific instructions, examples, or troubleshooting steps, and all tooling and extension references are Windows-centric.
Recommendations
  • Add explicit guidance for SQL Server running on Linux VMs, including prerequisites, supported backup scenarios, and any differences in process.
  • Provide Linux-specific examples and screenshots where applicable, such as using the Azure portal or CLI to discover and back up SQL Server databases on Linux VMs.
  • Document the equivalent Linux extensions or agents (if available), or clarify if the described backup solution is not supported for Linux.
  • Include troubleshooting steps and permission requirements relevant to Linux environments (e.g., service accounts, file permissions, SQL authentication).
  • Clearly state OS limitations or support matrix at the beginning of the tutorial to set expectations for users running SQL Server on Linux.
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-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation exclusively describes upgrading the MARS agent on Windows environments, referencing Windows-specific tools (Remote Desktop, DPM Console), graphical wizards, and agent installers. There are no Linux examples, nor any mention of Linux-compatible procedures or tools. All instructions assume a Windows server context and Windows administrative patterns.
Recommendations
  • Clarify in the introduction that the MARS agent is only supported on Windows, if that is the case. If Linux support exists or is planned, add equivalent instructions for Linux environments.
  • If Linux support is not available, explicitly state this to avoid confusion for cross-platform administrators.
  • Where possible, provide parity for Linux by referencing Azure Backup solutions or agents available for Linux, and link to their documentation.
  • Avoid using Windows-specific terminology (e.g., Remote Desktop, DPM Console) without noting platform limitations.
  • Add a section comparing Windows and Linux backup agent options in Azure, to help users choose the right solution for their OS.
Backup Support matrix for Azure VM backups ...lob/main/articles/backup/backup-support-matrix-iaas.md
Medium Priority View Details →
Scanned: 2026-01-25 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides comprehensive coverage of both Windows and Linux Azure VM backup scenarios, but there are notable signs of Windows bias. Windows-specific tools (MARS agent, DPM, MABS) are described in detail, with examples and restore methods often referencing PowerShell and Windows-centric workflows. Linux support is covered, but Linux-specific limitations and exclusions are listed more than actionable guidance. Windows examples and tools are mentioned first and more frequently, and Linux alternatives (where available) are not always given equal detail or prominence.
Recommendations
  • Provide Linux CLI or script examples alongside PowerShell references, especially in restore workflows.
  • Add more actionable Linux backup and restore scenarios, including step-by-step guides for common tasks.
  • Where Windows tools (MARS agent, DPM, MABS) are mentioned, clarify Linux alternatives or explicitly state their absence and suggest best practices for Linux users.
  • Balance the order of presentation so Linux support is not consistently listed after Windows support.
  • Expand documentation on Linux-specific backup limitations with troubleshooting and mitigation steps.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page describes the Azure VM restore process in a mostly OS-neutral way, but the 'Restore an encrypted VM' scenario exclusively references Windows VM encryption and PowerShell-based restoration, with no mention of Linux VM disk encryption or Linux restoration workflows. Additionally, the encrypted VM restore scenario links only to Windows-specific documentation, and PowerShell is presented as the sole automation tool for restoring encrypted VMs, with no Bash, CLI, or Linux-native alternatives. This creates friction for Linux VM users seeking parity in encrypted VM restore guidance.
Recommendations
  • Add equivalent guidance for restoring encrypted Linux VMs, including links to Linux disk encryption documentation and restore workflows.
  • Provide examples using Azure CLI or Bash scripts for restoring encrypted VMs, not just PowerShell.
  • Clarify in the encrypted VM restore scenario whether Linux VMs are supported, and if not, explicitly state the limitation.
  • Ensure restore scenarios and linked documentation cover both Windows and Linux VM types where applicable.
Backup Back Up and Restore Encrypted Azure VMs ...ob/main/articles/backup/backup-azure-vms-encryption.md
Medium Priority View Details →
Scanned: 2026-01-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation generally covers both Windows and Linux Azure VMs, including references to ADE (BitLocker for Windows, dm-crypt for Linux). However, there is a notable Windows bias in the 'Provide permissions' section, where the PowerShell example to identify a VM's associated key vault is given first and exclusively, without an equivalent Azure CLI or Bash example. This may create friction for Linux/macOS users who prefer CLI or Bash commands. Additionally, PowerShell is mentioned before Azure CLI in the context of setting access policies.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell commands, especially for tasks like identifying the associated Key Vault.
  • When referencing automation options (e.g., setting access policies), mention Azure CLI and Bash alternatives before or alongside PowerShell.
  • Ensure screenshots and instructions are OS-agnostic or clarify when steps differ for Linux/macOS users.
Scanned: 2026-01-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation for Azure Backup architecture is notably Windows-centric in its coverage of on-premises backup scenarios. It exclusively describes the use of the MARS agent (Windows-only) and DPM/MABS (Windows-based tools) for on-premises backups, with explicit statements that Linux machines aren't supported for direct backup. There are no Linux backup agent options or Linux-specific examples provided for on-premises scenarios, and Windows tools are referenced first and exclusively. However, for Azure VM backups, the documentation is OS-agnostic, and Linux is referenced in the context of managed disks.
Recommendations
  • Clarify in the 'Back up on-premises machines' section that direct backup of Linux machines is not supported, and provide guidance or references for Linux backup strategies (e.g., using third-party tools, Azure File Sync, or custom scripts).
  • If Azure Backup now supports any Linux on-premises backup scenarios, add documentation and examples for those workflows.
  • In tables and feature lists, explicitly indicate Linux support status for each backup method, rather than omitting Linux entirely.
  • Consider adding a short section or FAQ entry addressing common Linux backup needs and Azure-compatible solutions, even if Azure Backup does not natively support them.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a generally cross-platform overview of restoring Azure VMs using the portal, but there are several areas where Windows bias is evident. PowerShell is frequently referenced as the automation/CLI method, often without mentioning Azure CLI or Bash alternatives. Many links and examples for advanced scenarios (e.g., restoring with special network configurations, availability sets, or post-restore steps) point to Windows-specific guides or use PowerShell. Some sections (like resetting static IPs or restoring special VMs) reference Windows-centric tools or documentation first, and Linux-specific guidance is minimal or absent. There are also post-restore steps and troubleshooting commands that are Windows-specific, with no Linux equivalents provided.
Recommendations
  • Where PowerShell is referenced as a method to create or restore VMs, add equivalent Azure CLI and/or Bash examples and links, especially for Linux users.
  • When linking to guides for creating VMs from restored disks, include both Windows and Linux documentation (e.g., /azure/virtual-machines/linux/attach-managed-disk-portal alongside the Windows link).
  • In post-restore steps, provide Linux-specific guidance for common tasks (e.g., resetting static IPs, rejoining domains, troubleshooting boot issues) and reference relevant Linux documentation.
  • For sections on restoring special VMs (e.g., SQL VMs, domain controllers), clarify when steps are Windows-only and provide Linux alternatives or explicitly state if not applicable.
  • Review all automation and scripting references to ensure both PowerShell and Azure CLI are covered, or clarify when only one is supported.
Medium Priority View Details →
Scanned: 2026-01-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation covers restoring both Windows and Linux encrypted Azure VMs, but there is a notable bias towards Windows/PowerShell workflows. In the 'Recreate the virtual machine instance' section, only PowerShell is mentioned for creating a VM from restored disks, with no Linux/CLI or Azure CLI example provided. Additionally, the step for swapping the OS disk links to a Windows-specific article. The Linux-specific restore instructions are brief and lack detailed, step-by-step guidance or command examples, while Windows/PowerShell options are more explicitly referenced.
Recommendations
  • Add Azure CLI and/or Bash examples for creating a VM from restored disks, alongside or before PowerShell examples.
  • Provide a Linux-specific step-by-step guide (with command examples) for restoring and reconfiguring ADE on Linux VMs, including how to reinstall the ADE extension.
  • Where possible, link to Linux documentation for tasks like swapping the OS disk, not just Windows guides.
  • Ensure that Linux and Windows instructions are presented with equal detail and prominence.
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-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page on Azure VM restore process contains notable Windows bias. In the 'Restore an encrypted VM' scenario, only PowerShell is mentioned as the method to recreate the VM after restoring disks, with all linked guides focused on Windows VM disk encryption. There is no mention of Linux equivalents, nor are Linux-specific restore scenarios or tools referenced. The restore process examples and linked documentation prioritize Windows VM scenarios, leaving Linux VM users without clear guidance for encrypted VM restore.
Recommendations
  • Add explicit guidance for restoring encrypted Linux VMs, including steps and supported tools (e.g., Azure CLI, Bash scripts).
  • Include links to documentation about Linux VM disk encryption and restore processes.
  • Where PowerShell is referenced for Windows, provide Azure CLI or Bash alternatives for Linux.
  • Clarify which restore scenarios apply to both Windows and Linux, and which are Windows-only.
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation for Azure Backup architecture is notably Windows-centric in its coverage of on-premises backup scenarios. It exclusively details the use of the MARS agent (Windows-only) and System Center DPM/MABS (Windows-based tools) for on-premises backups, with no mention of Linux support or Linux backup alternatives. The documentation also presents Windows backup methods before any mention of cross-platform or Linux-compatible approaches, and does not clarify Linux limitations or provide guidance for Linux users.
Recommendations
  • Explicitly state Linux support limitations for on-premises backup scenarios at the start of relevant sections.
  • Provide guidance or references for Linux on-premises backup, such as using Azure Backup Server (if supported), Azure File Sync, or third-party solutions.
  • Include a comparison table or section summarizing backup options for both Windows and Linux machines, clearly indicating which features are Windows-only.
  • Link to documentation on Linux VM backup in Azure where relevant.
  • If Linux on-premises backup is not supported, clarify this early and direct Linux users to alternative Azure-native or partner solutions.
Backup Back Up and Restore Encrypted Azure VMs ...ob/main/articles/backup/backup-azure-vms-encryption.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation generally covers both Windows and Linux VMs for encrypted backup and restore, mentioning ADE (BitLocker for Windows, dm-crypt for Linux) and providing parity in feature descriptions. However, in the 'Provide permissions' section, the example for identifying a VM's associated Key Vault is given only in PowerShell, with no equivalent Azure CLI or Bash example. PowerShell is typically associated with Windows environments, and its exclusive use may create friction for Linux/macOS users. Additionally, PowerShell is mentioned before Azure CLI in the context of setting access policies, suggesting a slight Windows-first bias.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell for tasks such as identifying the Key Vault associated with a VM.
  • When referencing automation or scripting, ensure both PowerShell and Azure CLI/Bash options are presented equally and in parallel.
  • Explicitly state that all procedures can be performed from Linux/macOS environments using Azure CLI, and link to relevant cross-platform guides.
  • Consider reordering examples so that CLI/Bash and PowerShell are presented together or in alternating order.