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 126-150 of 1604 flagged pages
Backup Offline seeding workflow for MARS using customer-owned disks with Azure Import/Export - Azure Backup ...n/articles/backup/backup-azure-backup-import-export.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All workflow steps, prerequisites, and tooling (MARS agent, AzureOfflineBackupDiskPrep utility, Azure PowerShell, Recovery Services Agent) are exclusively described for Windows environments. There are no Linux equivalents or examples, and requirements such as Internet Explorer/Edge, BitLocker, and Windows-specific agent installation further reinforce the Windows-centric approach. The documentation does not mention or support Linux systems for offline seeding with customer-owned disks.
Recommendations
  • Explicitly state Windows-only support at the beginning of the article if Linux is not supported, or clarify platform limitations.
  • If Linux support is possible, provide equivalent instructions, tooling, and examples for Linux environments (e.g., using az CLI, Linux-compatible disk preparation tools, and browser requirements).
  • Reference or link to any Linux-compatible workflows or alternatives for offline seeding, if available.
  • Where possible, use cross-platform tools (such as Azure CLI) and document their usage alongside PowerShell.
  • Avoid requiring Windows-only features (e.g., BitLocker, Internet Explorer) unless strictly necessary, and suggest Linux alternatives (e.g., LUKS for disk encryption).
Backup Azure Kubernetes Service (AKS) backup support matrix ...azure-kubernetes-service-cluster-backup-support-matrix.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Azure Kubernetes Service (AKS) backup support matrix exhibits mild Windows bias. It references Azure PowerShell as a primary tool for backup and restore operations, listing it alongside Azure CLI, ARM, Bicep, and Terraform in the 'Next steps' section. However, there is no mention of Linux-specific command-line tools or shell examples (e.g., Bash), nor are Linux-native patterns (such as shell scripting or Linux package management) discussed. The documentation does not provide explicit Linux command examples, and PowerShell is listed before ARM/Bicep/Terraform, which may suggest a Windows-first approach. Additionally, while the documentation states that the backup extension can only be installed on Ubuntu or Azure Linux node pools, it does not provide guidance or examples for Linux users, nor does it mention Linux-specific troubleshooting or usage patterns.
Recommendations
  • Add explicit Bash or Linux shell command examples for backup and restore operations, especially in sections referencing Azure CLI.
  • Include Linux-native troubleshooting steps and usage patterns, such as using systemd, journalctl, or Linux file permissions.
  • Reorder the 'Next steps' section to list Azure CLI and Linux-native tools before PowerShell, reflecting the AKS platform's Linux-centric nature.
  • Clarify that PowerShell is optional and primarily for Windows users, while Azure CLI and Bash are recommended for Linux environments.
  • Provide guidance on installing and using the Azure CLI on Linux, including package manager commands (apt, yum, etc.).
  • Add links or references to Linux documentation for AKS node pool management and backup extension installation.
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for the MARS Agent is heavily focused on Windows environments. All backup and recovery scenarios explicitly mention Windows files, folders, volumes, and system state. The agent's reliance on Windows-specific technologies such as VSS (Volume Shadow Copy Service) and USN change journal is highlighted, with no mention of Linux support, examples, or equivalent tooling. There are no Linux or cross-platform instructions, examples, or references, and the documentation implicitly assumes the reader is operating in a Windows context.
Recommendations
  • Explicitly state platform support (e.g., clarify if MARS Agent is Windows-only or provide Linux support status).
  • If Linux is supported, add equivalent Linux examples and instructions for installation, backup, and recovery.
  • Mention Linux backup tools or patterns where appropriate, or provide links to Azure Backup solutions for Linux.
  • If MARS Agent is not supported on Linux, suggest alternative Azure Backup solutions for Linux workloads.
  • Avoid using Windows-specific terminology (e.g., VSS, USN) without noting platform limitations or alternatives.
Backup Back up SQL Server to Azure as a DPM workload ...s/blob/main/articles/backup/backup-azure-backup-sql.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, specifically Data Protection Manager (DPM), which is a Windows-only tool. All examples, screenshots, and instructions assume the use of Windows Server, DPM, and related Windows concepts (such as NTAuthority\System, Logical Disk Manager, and protection group workflows). There are no references to Linux-based SQL Server deployments, nor are there examples or guidance for backing up SQL Server on Linux. The only automation reference is to PowerShell, further reinforcing Windows bias.
Recommendations
  • Add explicit guidance and examples for backing up SQL Server on Linux, including supported scenarios and limitations.
  • Reference and provide parity for Linux-native backup tools and workflows (e.g., Azure Backup agent for Linux, CLI commands, or REST API usage).
  • Include screenshots and walkthroughs for Linux environments where SQL Server is supported.
  • Mention differences in prerequisites, permissions, and backup/restore processes for Linux-based SQL Server deployments.
  • Provide automation examples using Bash, Azure CLI, or other cross-platform tools, not just PowerShell.
  • Clarify in the introduction and prerequisites which operating systems are supported and whether DPM is required or if alternatives exist for Linux.
Backup Monitor Azure Backup protected workloads ...les/backup/backup-azure-monitoring-built-in-monitor.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric backup tools (DPM, MABS, MARS) and linking to 'manage-windows-server' resources. There are no explicit examples or mentions of Linux backup agents or Linux-specific monitoring workflows. Windows tools and patterns are mentioned exclusively, with no Linux parity in examples or guidance.
Recommendations
  • Include examples and guidance for monitoring Azure Backup workloads protected by Linux servers and agents.
  • Reference Linux backup agents (such as Azure Backup for Linux VM or Azure Backup Agent for Linux) alongside Windows tools.
  • Add links to documentation pages specifically for managing and monitoring Linux backup items.
  • Ensure that instructions and screenshots cover both Windows and Linux scenarios where applicable.
  • Mention any differences in monitoring or notification workflows for Linux workloads.
Backup Restore Key Vault key & secret for encrypted Azure VM ...ain/articles/backup/backup-azure-restore-key-secret.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on Azure PowerShell, with all examples and instructions using PowerShell cmdlets and Windows-style file paths (e.g., C:\). There are no CLI/bash examples, and Linux scenarios are only briefly mentioned as a variant of the Windows PowerShell workflow, not as a first-class workflow. The documentation assumes the use of Windows tools and patterns throughout, making it less accessible for Linux users or those preferring Azure CLI or bash scripting.
Recommendations
  • Provide equivalent Azure CLI/bash examples for all steps, including disk restore, key/secret extraction, and Key Vault operations.
  • Use platform-neutral file paths and examples (e.g., /home/user/vmencryption_config.json for Linux).
  • Explicitly document Linux workflows, including prerequisites and environment setup, not just as a variant of Windows/PowerShell.
  • Mention and link to cross-platform tools (e.g., Azure CLI, REST API) alongside PowerShell, and clarify which steps are platform-specific.
  • Reorder examples so that Linux and cross-platform approaches are presented alongside or before Windows-specific instructions.
Backup Manage and monitor MARS Agent backups .../blob/main/articles/backup/backup-azure-manage-mars.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows environments. All instructions, screenshots, and tool references are specific to the Microsoft Azure Recovery Services (MARS) Agent, which is a Windows-only backup solution. There are no Linux equivalents, examples, or even mentions of Linux support or alternative tooling. The documentation assumes the use of Windows consoles, directories (e.g., %ProgramFiles%), and Windows-specific management patterns throughout.
Recommendations
  • Clearly state at the beginning that the MARS Agent is only supported on Windows, and provide links to equivalent Linux backup solutions (such as Azure Backup for Linux VMs or Azure CLI-based solutions).
  • Where possible, include references or links to documentation for managing and monitoring backups on Linux systems using Azure services.
  • If the product is Windows-only, make this explicit in the prerequisites and scope, and suggest alternative Azure-native backup approaches for Linux workloads.
  • Consider providing a comparison table or section outlining backup options for both Windows and Linux, guiding users to the appropriate documentation for their OS.
Backup Back up SQL Server by using Azure Backup Server ...ocs/blob/main/articles/backup/backup-azure-sql-mabs.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily oriented towards Windows environments, specifically referencing Microsoft Azure Backup Server (MABS) and Data Protection Manager (DPM), which are Windows-only tools. All examples, screenshots, and instructions assume the use of Windows Server and SQL Server on Windows. There is no mention of Linux-based SQL Server deployments, nor are there examples or guidance for backing up SQL Server running on Linux. Windows-specific concepts (NTAuthority\System, Windows Azure Blob storage, Windows failover clustering) are referenced without Linux equivalents.
Recommendations
  • Explicitly state platform limitations at the beginning, clarifying that MABS/DPM are Windows-only tools.
  • Provide alternative backup solutions or references for SQL Server running on Linux, such as using Azure Backup with Linux agents, or native SQL Server backup/restore commands.
  • Include examples and guidance for backing up SQL Server on Linux, if supported, or link to relevant documentation for Linux environments.
  • Mention Linux-specific considerations (e.g., service accounts, file permissions, storage paths) where appropriate.
  • If Azure Backup supports Linux SQL Server, add parity in screenshots, CLI commands, and workflows.
Backup Back up Exchange server with Azure Backup Server ...lob/main/articles/backup/backup-azure-exchange-mabs.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively describes backup and recovery procedures for Microsoft Exchange Server using Microsoft Azure Backup Server (MABS), which is a Windows-only product. All examples, instructions, and referenced tools (such as Eseutil.exe, MABS Administrator Console) are Windows-centric, with no mention of Linux equivalents, cross-platform alternatives, or guidance for Exchange deployments on non-Windows platforms. The documentation assumes the use of Windows GUIs and tools, and does not provide parity for Linux users.
Recommendations
  • Clarify early in the documentation that MABS is a Windows-only solution and suggest cross-platform alternatives (such as Azure Backup integration with Linux servers or third-party tools) for Linux environments.
  • Provide links or references to backup solutions for Exchange-like workloads on Linux (e.g., for mail servers such as Postfix, Dovecot, or Zimbra).
  • If possible, include a section on backing up Linux-based mail servers to Azure, with example commands and procedures.
  • Explicitly state platform limitations and guide users to appropriate documentation for non-Windows scenarios.
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias in several areas: Windows backup scenarios and tools (MARS agent, DPM, MABS) are described first and in greater detail, with Linux support often mentioned as 'not supported' or as a secondary note. Many backup features (such as direct on-premises backup with MARS agent, app-aware backup, deduplication, and compression) are available only for Windows, with Linux support either missing or limited to VM-level backups via extensions or third-party virtualization platforms. Windows-specific tools and patterns (MARS agent, DPM, MABS) are referenced throughout, while Linux equivalents are not provided or are explicitly unsupported.
Recommendations
  • Provide Linux-first or Linux-parity examples and scenarios alongside Windows ones, especially in tables and feature lists.
  • Explicitly state Linux limitations and offer alternative solutions or workarounds where possible.
  • Include Linux-specific backup tools or recommend open-source alternatives for on-premises Linux backup.
  • Clarify which features are Windows-only and which are available for Linux, and avoid presenting Windows features as the default.
  • Add more detail and guidance for configuring app-consistent backups on Linux, including sample scripts and best practices.
  • Where a feature is not supported for Linux, link to roadmap or feedback channels for future support.
Backup Enable Backup During Azure VM Creation by Using Azure Backup ...blob/main/articles/backup/backup-during-vm-creation.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows is mentioned before Linux in instructions, and the only Resource Manager template example provided is for deploying a Windows VM with backup enabled. There are no explicit Linux-focused examples or templates, and PowerShell is referenced as the automation method for configuring backup resource groups, with no mention of Linux CLI alternatives.
Recommendations
  • Present Windows and Linux instructions/examples in parallel, or alternate which is mentioned first.
  • Include Resource Manager template examples for Linux VMs with backup enabled.
  • Provide equivalent automation instructions using Azure CLI or Bash scripts, not just PowerShell.
  • Explicitly mention that all backup features and steps apply equally to Linux VMs where applicable.
  • Add screenshots and walkthroughs for Linux VM creation and backup configuration.
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily focuses on using the Azure portal for backup operations, which is cross-platform. However, when mentioning automation or scripting, PowerShell is listed before Azure CLI, and there are no explicit Linux-specific examples or references to Linux tools or workflows. The page does not provide parity in examples or guidance for Linux users, especially in scripting and automation contexts.
Recommendations
  • When referencing automation, mention Azure CLI before or alongside PowerShell, as CLI is cross-platform and preferred by many Linux users.
  • Provide explicit Linux/Unix shell examples (e.g., Bash scripts using Azure CLI) for backup and restore operations.
  • Clarify that all portal operations are OS-agnostic, but scripting examples should be balanced between PowerShell and CLI.
  • Add a section or links for Linux administrators, highlighting best practices or common patterns for managing Azure Disk backups from Linux environments.
  • Ensure that any downloadable script templates or role assignment instructions include both PowerShell and Bash/CLI versions.
Backup Back up SQL Server on Azure Stack using Azure Backup ...ob/main/articles/backup/backup-mabs-sql-azure-stack.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on Microsoft Azure Backup Server (MABS), which is a Windows-only tool. All workflow steps, screenshots, and terminology reference Windows environments (e.g., NTAuthority\System, SQL Server on Windows, Windows-style wizards and blades). There are no examples, instructions, or mentions of Linux-based SQL Server deployments or backup tools. The documentation assumes the use of Windows tools and patterns throughout, with no Linux parity.
Recommendations
  • Explicitly state platform requirements and limitations at the beginning, including that MABS is Windows-only.
  • Provide guidance or links for backing up SQL Server on Azure Stack when running on Linux, if supported, or clarify that Linux is not supported.
  • Include alternative backup workflows or tools for Linux-based SQL Server deployments, such as Azure Backup integration with Linux or third-party solutions.
  • Add examples and screenshots for Linux environments if/when support is available.
  • Mention Linux equivalents for system accounts, permissions, and backup/restore procedures where applicable.
Backup Release notes for Microsoft Azure Backup Server v3 ...b/main/articles/backup/backup-mabs-release-notes-v3.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation for Microsoft Azure Backup Server v3 is heavily focused on Windows environments. All examples, instructions, and tools referenced (such as SQL Server Management Studio, SQL Server Reporting Services, and file paths) are Windows-specific. There are no mentions of Linux equivalents, nor any guidance for Linux-based backup scenarios. The documentation assumes the use of Windows Server and related Microsoft tools, with no consideration for cross-platform or Linux users.
Recommendations
  • Include explicit statements about platform support (e.g., clarify if MABS is Windows-only or provide Linux guidance if supported).
  • If Linux is supported, add equivalent instructions for Linux environments, such as using sqlcmd or Azure CLI for database operations.
  • Reference Linux file paths and tools where applicable, or note their absence if not supported.
  • Provide parity in troubleshooting steps and examples for both Windows and Linux users.
  • Mention any limitations or requirements for non-Windows platforms early in the documentation.
Backup Offline Backup with Azure Data Box for DPM and MABS ...icles/backup/offline-backup-azure-data-box-dpm-mabs.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All instructions, examples, and supported platforms are Windows Server only (2016/2019), with no mention of Linux or cross-platform alternatives. The setup steps rely on Windows-specific tools (PSExec, registry editing, Windows command prompt, PowerShell modules), and troubleshooting is entirely Windows-centric. There are no Linux equivalents or examples, nor any guidance for non-Windows users.
Recommendations
  • Explicitly state Windows-only support in the introduction and platform requirements.
  • If possible, add support for Linux-based backup servers and document the equivalent steps for Linux environments (e.g., mounting NFS shares, certificate management, Azure CLI usage).
  • Where PowerShell is used, provide Azure CLI or REST API alternatives for cross-platform compatibility.
  • Replace or supplement Windows-specific tools (e.g., PSExec, regedit) with platform-agnostic or Linux-native alternatives.
  • Include troubleshooting steps and examples for Linux environments if/when supported.
  • If Linux is not supported, clarify this limitation early in the documentation and provide links to alternative solutions for Linux users.
Backup Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Server using a Terraform template ...p/quick-backup-postgresql-flexible-server-terraform.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by mentioning Windows-centric tools (PowerShell) and patterns before Linux equivalents. In the prerequisites, PowerShell is listed as a client for Azure Backup before CLI and other cross-platform tools. There is a specific note about PowerShell authentication, and the documentation refers to the Azure PowerShell module, which is primarily used on Windows. No Linux-specific instructions, examples, or troubleshooting are provided, and the CLI is mentioned only in passing.
Recommendations
  • List cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell) in all tool lists.
  • Provide explicit Linux usage instructions, including installation and authentication steps for Azure CLI and Terraform on Linux.
  • Include troubleshooting steps and examples for Linux environments.
  • Avoid mentioning PowerShell unless necessary, and always provide equivalent CLI/bash examples.
  • Clarify that all steps are cross-platform, and highlight any OS-specific differences where relevant.
Backup Create and use private endpoints for Azure Backup ...re-docs/blob/main/articles/backup/private-endpoints.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. Most command-line examples and scripts are provided only for PowerShell, with no Bash, CLI, or Linux shell equivalents. Windows-centric tools and patterns (PowerShell, ARMClient with Windows file paths, MARS agent, DPM server) are referenced exclusively or before any cross-platform alternatives. There are no explicit instructions or examples for Linux users, and the workflow assumes familiarity with Windows environments and tooling.
Recommendations
  • Provide Azure CLI (az) and Bash examples alongside PowerShell for all command-line operations, including role assignment, private endpoint creation, and DNS management.
  • Reference cross-platform tools (e.g., Azure CLI, REST API via curl) before or alongside Windows-specific tools like PowerShell and ARMClient.
  • Include Linux-specific instructions for tasks such as DNS configuration, file uploads, and script execution (e.g., using scp, curl, or az commands).
  • Clarify that the process is applicable to both Windows and Linux VMs, and provide troubleshooting steps for Linux environments.
  • Offer guidance for using Linux-based backup agents or alternatives to MARS/DPM where possible.
  • Ensure all file path examples use cross-platform formats or provide both Windows and Linux path formats.
Backup Quickstart - Configure vaulted backup for Azure Files using Azure CLI ...cles/backup/quick-backup-azure-files-vault-tier-cli.md
High Priority View Details →
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 page demonstrates subtle Windows bias. While the main focus is on Azure CLI (which is cross-platform), references to Azure PowerShell and the Azure portal are given as alternatives, with PowerShell mentioned before the portal in several places. The example CLI output includes a Windows-style path (C:\Users\testuser\Downloads\...), which may confuse Linux users. Installation instructions mention Windows and macOS specifically, but do not explicitly mention Linux, and Docker is suggested for Windows/macOS users, leaving Linux users without tailored guidance.
Recommendations
  • Provide explicit Linux installation instructions for Azure CLI, alongside Windows and macOS.
  • Ensure example CLI output uses neutral or Linux-style paths (e.g., ~/Downloads/...), or clarify that the CLI works identically on Linux.
  • When listing alternatives (PowerShell, portal), alternate the order or mention Linux-native tools if available.
  • Add notes or examples for common Linux shell environments (e.g., bash, zsh), and clarify that all CLI commands work on Linux.
  • Avoid Windows-centric terminology (such as 'Terminal' with capital T) unless also referencing Linux equivalents (e.g., 'terminal, shell, or command prompt').
Backup Quickstart - Resource Manager template VM Backup .../blob/main/articles/backup/quick-backup-vm-template.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. It exclusively provides Azure PowerShell examples for deploying and managing VM backups via ARM templates, with no equivalent Azure CLI or Bash examples. The template referenced is for a Windows VM, and Windows-centric tools and workflows (PowerShell, Windows VM creation) are mentioned first and used throughout. Linux-specific instructions, examples, or parity are missing.
Recommendations
  • Add Azure CLI and Bash examples for deploying ARM templates and managing backups, alongside PowerShell.
  • Include a template example for Linux VMs, or clarify how to adapt the template for Linux workloads.
  • Mention Linux-compatible tools and workflows (e.g., Azure CLI in Bash, Cloud Shell Bash) at the same prominence as PowerShell.
  • Ensure cleanup instructions include Azure CLI/Bash equivalents, not just PowerShell cmdlets.
  • Balance references to Windows and Linux VMs in both the template and explanatory text.
Backup Offline backup for Data Protection Manager (DPM) and Microsoft Azure Backup Server (MABS) - previous versions ...cles/backup/offline-backup-server-previous-versions.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented towards Windows environments, with all examples, screenshots, and tool references assuming Windows Server, Windows client, or Windows-specific utilities (e.g., .exe files, registry edits, Certlm.msc, regedit, PowerShell commands). There are no Linux equivalents, nor any mention of how to perform these steps on Linux systems. The workflow, prerequisites, and troubleshooting steps are all described from a Windows perspective, and Linux support is not addressed.
Recommendations
  • Explicitly state platform limitations (e.g., if offline backup is not supported on Linux, clarify this early in the documentation).
  • If Linux support exists, provide equivalent instructions, tools, and examples for Linux environments (e.g., shell commands, Linux file paths, certificate management via OpenSSL, etc.).
  • Include screenshots and workflow steps for Linux-based systems, if applicable.
  • Mention any cross-platform alternatives or limitations, and provide guidance for users on non-Windows platforms.
  • If only Windows is supported, add a clear note at the beginning to prevent confusion for Linux users.
Backup Quickstart - Configure vaulted backup for Azure Blobs using Azure CLI .../main/articles/backup/quick-blob-vaulted-backup-cli.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Azure PowerShell and linking to PowerShell-based instructions before or alongside CLI examples. The 'create a Backup vault' link points to a PowerShell guide, and the 'Next step' section lists Azure PowerShell before Azure CLI, suggesting a Windows-first approach. There is no explicit mention of Linux-specific considerations or examples, and no references to Linux-native tools or shell environments.
Recommendations
  • Ensure that all linked instructions (such as creating a Backup vault) have Azure CLI equivalents and link to those as the primary or at least equally prominent option.
  • List Azure CLI instructions before PowerShell in all sections to avoid Windows-first ordering.
  • Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and provide examples or notes for Linux users where relevant.
  • Review included files to confirm they do not contain Windows-specific commands or assumptions (e.g., PowerShell syntax, Windows paths).
  • Add troubleshooting or environment setup notes for Linux users if there are platform-specific considerations.
Backup Accidental Delete Protection for Azure Files ...b/main/articles/backup/soft-delete-azure-file-share.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing a 'Undelete File Share Script' that is specifically a PowerShell script, without mentioning or providing equivalent Linux or cross-platform CLI examples. The instructions and links focus on the Azure Portal and PowerShell, with no mention of Azure CLI, Bash, or Linux-native tooling for undelete or management operations. This may disadvantage Linux users or those preferring non-Windows environments.
Recommendations
  • Provide equivalent examples and scripts using Azure CLI and Bash for undelete and management operations.
  • Explicitly mention cross-platform options where PowerShell scripts are referenced, and link to Linux-compatible instructions.
  • Add a section or FAQ entry addressing how Linux users can perform these operations, including sample commands.
  • Ensure that future documentation includes parity between Windows/PowerShell and Linux/Azure CLI approaches for all major tasks.
Backup Transport Layer Security in Azure Backup .../blob/main/articles/backup/transport-layer-security.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, providing only Windows-specific instructions (such as registry edits and KB articles) for enabling TLS 1.2 in Azure Backup. There are no examples or guidance for Linux systems, nor any mention of Linux-specific tools or configuration patterns. All troubleshooting and configuration steps assume a Windows platform.
Recommendations
  • Add a dedicated section for enabling and verifying TLS 1.2 on Linux systems, including common distributions (e.g., Ubuntu, CentOS).
  • Provide examples for configuring TLS on Linux, such as updating OpenSSL or modifying system-wide crypto policies.
  • Include troubleshooting steps for Linux backup agents or services, and reference relevant Linux documentation.
  • Ensure parity in FAQs and related content by mentioning both Windows and Linux scenarios.
  • List Linux equivalents for any Windows tools or registry changes (e.g., config files, command-line utilities).
Backup Selective Disk Backup and Restore for Azure Virtual Machines .../main/articles/backup/selective-disk-backup-restore.md
High Priority View Details →
Scanned: 2026-01-12 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 both Azure CLI and PowerShell examples for configuring selective disk backup and restore, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and there are no explicit Linux shell (bash) or Linux-native scripting examples. Windows-specific terminology and tools (such as drive C, BitLocker, and PowerShell cmdlets) are mentioned directly, while Linux equivalents are referenced but not illustrated with concrete examples. Linux-specific requirements (like lsblk and lsscsi) are mentioned, but no step-by-step Linux command-line walkthrough is provided. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users in terms of example scripts or troubleshooting steps.
Recommendations
  • Add explicit bash/Linux shell examples for configuring selective disk backup and restore, including sample scripts using az CLI in bash.
  • Provide troubleshooting steps and examples for common Linux issues (e.g., verifying lsblk/lsscsi availability, handling permissions, etc.).
  • Include Linux-native terminology and patterns (e.g., referencing /dev/sdX, using sudo, etc.) alongside Windows terms.
  • Balance the use of PowerShell and CLI by prioritizing CLI examples (which are cross-platform) and relegating PowerShell to a secondary section.
  • Add a section with Linux-specific best practices for disk backup and restore, including handling logical volumes and encrypted disks.
  • Ensure that screenshots and UI references are not Windows-centric, and clarify any OS-specific differences in the Azure portal experience.
Backup Upgrade the Microsoft Azure Recovery Services (MARS) agent for Azure Backup ...e-docs/blob/main/articles/backup/upgrade-mars-agent.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation exclusively describes upgrading the MARS agent in the context of Windows environments, referencing Remote Desktop, Windows login URLs, and Windows-specific tools (DPM Console, agent upgrade wizard). There are no Linux examples, instructions, or mentions of Linux compatibility, and the 'Next steps' section further reinforces a Windows-only focus.
Recommendations
  • Clarify whether the MARS agent is supported on Linux. If not, explicitly state this early in the documentation.
  • If Linux support exists, add parallel instructions for Linux environments, including command-line steps (e.g., using SSH, Linux package managers) and screenshots.
  • Mention Linux equivalents for remote access (e.g., SSH) and agent installation/upgrade procedures.
  • Provide examples of firewall configuration for Linux servers.
  • Ensure parity in troubleshooting and next steps for both Windows and Linux platforms.