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 351-375 of 1604 flagged pages
Backup Install Azure Backup Server on Azure Stack Hub ...ain/articles/backup/backup-mabs-install-azure-stack.md
High Priority View Details →
Scanned: 2026-01-11 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 biased towards Windows environments. All instructions, prerequisites, and examples assume the use of Windows Server (specifically Windows Server 2022/2019 Datacenter), Windows file paths (C:\, D:\), Windows domain joining, and Windows-only tools (PowerShell, Windows Update, .NET Framework). There are no references to Linux-based installations, Linux VM images, or cross-platform alternatives. The only command-line example provided is a PowerShell cmdlet, with no Linux shell equivalent. The documentation does not mention whether Azure Backup Server can be installed or operated on Linux, nor does it provide guidance for non-Windows users.
Recommendations
  • Explicitly state platform limitations: If Azure Backup Server is Windows-only, clarify this early in the documentation.
  • If Linux support exists or is planned, add equivalent instructions for Linux VM images, including prerequisites, installation steps, and troubleshooting.
  • Provide Linux shell (bash) equivalents for command-line operations, such as connectivity checks.
  • Reference Linux tools and patterns where appropriate (e.g., package managers, systemd services, Linux file paths).
  • Include guidance for mixed environments, such as backing up Linux workloads or integrating with Linux-based infrastructure.
  • If only Windows is supported, add a section explaining how to protect Linux workloads using other Azure Backup solutions.
Backup MABS (Azure Backup Server) V4 protection matrix .../main/articles/backup/backup-mabs-protection-matrix.md
High Priority View Details →
Scanned: 2026-01-11 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 for Azure Backup Server (MABS) V4 protection matrix exhibits a strong Windows bias. Windows workloads, versions, and recovery scenarios are described in detail and presented first, with extensive coverage of Windows-specific features (NTFS, VSS, Visual C++ dependencies, etc.). Linux support is relegated to a single table, with minimal detail and only as a guest OS on Windows-based hypervisors. There are no Linux-specific backup/recovery examples, tools, or agent installation instructions. Windows tools and patterns (Volume Shadow Copy Service, NTLM authentication, Control Panel, etc.) are referenced exclusively, and the documentation assumes Windows as the default environment throughout.
Recommendations
  • Add detailed Linux backup and recovery examples, including agent installation and configuration steps for Linux workloads.
  • Provide parity in documentation for Linux file systems (e.g., ext4, xfs) and clarify limitations or supported features compared to NTFS.
  • Include Linux-specific troubleshooting, authentication, and recovery scenarios, not just as VMs on Windows hosts.
  • Reference Linux tools and commands (e.g., systemctl, journalctl) where relevant, and avoid exclusive reliance on Windows tools and terminology.
  • Present Linux and Windows support side-by-side in tables and sections, rather than listing Windows first and Linux last.
  • Clarify whether direct backup of physical Linux servers (not just VMs) is supported, and document any differences in agent capabilities.
Backup Azure Instant Restore Capability ...n/articles/backup/backup-instant-restore-capability.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides configuration instructions for Azure Instant Restore using PowerShell only, with no mention of Linux CLI tools (such as Azure CLI or Bash examples). The use of PowerShell as the sole automation example suggests a Windows-centric approach. There are no Linux-specific instructions or parity in example commands, and the documentation does not mention alternative methods for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI (az) examples for configuring snapshot retention and other operations, ensuring Linux and macOS users have clear guidance.
  • Explicitly mention that both PowerShell and Azure CLI can be used for management tasks, and provide links to relevant CLI documentation.
  • Where screenshots or UI instructions are given, clarify that the Azure portal is cross-platform and accessible from any OS.
  • Review FAQ and operational sections to ensure that any references to scripting or automation include both PowerShell and CLI/Bash options.
  • Consider adding a table or section comparing PowerShell and CLI commands for common tasks related to Instant Restore.
Backup Back up files in Azure Stack VMs ...s/backup/backup-mabs-files-applications-azure-stack.md
High Priority View Details →
Scanned: 2026-01-11 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 using Microsoft Azure Backup Server, which is a Windows-based tool. All instructions reference the Azure Backup Server console, a Windows GUI, and concepts like Volume Shadow Copy Service (VSS), which are specific to Windows. There are no examples or guidance for Linux VMs, Linux file systems, or Linux-native backup tools. The documentation does not mention or provide parity for Linux environments, nor does it discuss cross-platform considerations.
Recommendations
  • Add explicit instructions or examples for backing up files and applications from Linux-based Azure Stack VMs, including command-line steps and supported Linux backup agents.
  • Mention Linux compatibility and limitations of Azure Backup Server, and provide links to Linux-specific backup documentation if available.
  • Include parity in recovery procedures for Linux VMs, such as restoring files using Linux tools or Azure Backup CLI commands.
  • Discuss alternative backup solutions for Linux workloads if Azure Backup Server is not supported, and clarify support boundaries.
  • Ensure screenshots and walkthroughs are not exclusively Windows GUI-based; provide CLI or Linux-native tool examples where possible.
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-11 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 examples, screenshots, and instructions assume usage of Windows environments (e.g., NTAuthority\System, Windows-style management consoles, GUI blades, and terminology). There are no mentions of Linux equivalents, CLI alternatives, or cross-platform backup approaches for SQL Server on Azure Stack. Linux scenarios, tools, or commands are entirely absent.
Recommendations
  • Explicitly state that MABS is Windows-only and clarify platform requirements early in the documentation.
  • Provide guidance or links for Linux-based backup solutions for SQL Server on Azure Stack, such as using Azure Backup via CLI, Azure Recovery Services Vault, or third-party tools.
  • Include examples or references for backing up SQL Server databases running on Linux (if supported on Azure Stack), or clarify limitations if not supported.
  • Add parity by mentioning how backup and recovery workflows differ for Linux-based SQL Server deployments, including any supported tools or scripts.
  • Where possible, offer PowerShell and CLI (az, bash) examples side-by-side for common tasks.
Backup System state and bare-metal recovery protection for Azure Backup ...in/articles/backup/backup-mabs-system-state-and-bmr.md
High Priority View Details →
Scanned: 2026-01-11 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 focused on Windows environments, referencing Windows Server Backup, Windows Recovery Environment (WinRE), and Windows-specific file paths and tools throughout. All examples, workflows, and prerequisites are tailored to Windows, with no mention of Linux or cross-platform alternatives. PowerShell cmdlets are referenced for disk allocation, and recovery instructions rely on Windows-only utilities and UI flows.
Recommendations
  • Explicitly state whether Azure Backup Server supports Linux system state or bare-metal recovery, and if not, provide guidance or links for Linux backup solutions.
  • If Linux support exists, add equivalent Linux workflows, including examples using native Linux backup tools (e.g., rsync, dd, tar, or third-party solutions) and recovery procedures.
  • Provide parity in command-line examples, such as Bash or shell commands for Linux, alongside PowerShell for Windows.
  • Clarify prerequisites and limitations for non-Windows operating systems, including supported distributions and required packages.
  • Reference Linux file paths and configuration files where applicable, and avoid assuming Windows-only directory structures.
  • Include troubleshooting and recovery steps for Linux systems, and mention any Azure Backup Server features or limitations specific to Linux.
Backup What's new in Microsoft Azure Backup Server ...lob/main/articles/backup/backup-mabs-whats-new-mabs.md
High Priority View Details →
Scanned: 2026-01-11 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 for Microsoft Azure Backup Server (MABS) demonstrates a strong Windows bias. Features and supportability are consistently described in terms of Windows Server versions, Windows-based workloads (SQL Server, Exchange, SharePoint), and Windows-specific tools (PowerShell, registry keys). There is little to no mention of Linux support, Linux workloads, or Linux-based backup scenarios. Examples, instructions, and feature tables focus exclusively on Windows environments, with no parity for Linux users.
Recommendations
  • Explicitly state Linux support status for MABS, including any limitations or planned enhancements.
  • Add examples and instructions for protecting Linux workloads (e.g., Linux VMs, file servers), if supported.
  • Include Linux equivalents for configuration steps currently described with Windows tools (e.g., registry keys, PowerShell), such as using configuration files or Linux command-line utilities.
  • Mention Linux-compatible backup agents or integration options, if available.
  • Ensure feature tables and support matrices include Linux platforms and workloads where applicable.
  • Provide parity in troubleshooting and recovery scenarios for Linux environments.
Backup Configure and manage backup for Azure Blobs using Azure Backup ...b/main/articles/backup/blob-backup-configure-manage.md
High Priority View Details →
Scanned: 2026-01-11 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 describes backup configuration and management using the Azure Portal, with references to Azure PowerShell, Azure CLI, and REST API in the 'Related content' section. However, throughout the main content, there is a notable absence of command-line examples, and when alternatives are mentioned, PowerShell is listed before CLI, suggesting a Windows-first bias. There are no explicit Linux-specific instructions, nor are there examples demonstrating Linux shell usage or parity with Windows tools. The documentation assumes GUI usage, which is platform-neutral, but when scripting is referenced, it leans toward Windows/PowerShell.
Recommendations
  • Include step-by-step examples for both Azure CLI and PowerShell in the main documentation, not just in 'Related content'.
  • When referencing scripting or automation, present Azure CLI (cross-platform) examples before or alongside PowerShell to avoid Windows-first bias.
  • Add explicit notes or sections for Linux/macOS users, including screenshots or terminal commands where relevant.
  • Ensure REST API examples include curl or other Linux-friendly tools, not just PowerShell/Windows-centric methods.
  • Review and update all references to scripting tools to provide equal visibility and guidance for Linux and Windows users.
Backup Quickstart - Configure vaulted backup for Azure Files using Azure Resource Manager ...cles/backup/quick-backup-azure-files-vault-tier-arm.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell usage. The only explicit command-line deployment example is given in Azure PowerShell, with no equivalent Azure CLI or Bash example. References to PowerShell precede mentions of Azure CLI or REST API in both deployment and management steps. There are no Linux-specific instructions or examples, and the documentation assumes familiarity with PowerShell, which is primarily a Windows tool.
Recommendations
  • Add Azure CLI and Bash examples for ARM template deployment, alongside PowerShell.
  • Present deployment options in a platform-neutral order (e.g., Azure portal, Azure CLI, PowerShell, REST API).
  • Include explicit instructions for Linux/macOS users, such as using Azure CLI in Bash.
  • Ensure management and restore steps provide parity between PowerShell and CLI, with links and examples for both.
  • Clarify that PowerShell is available cross-platform, but highlight CLI/Bash options for Linux users.
Backup Azure Backup support matrix for SQL Server Backup in Azure VMs ...e-docs/blob/main/articles/backup/sql-support-matrix.md
High Priority View Details →
Scanned: 2026-01-11 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 biased towards Windows environments. Only Windows Server operating systems are supported and listed, with Linux explicitly stated as unsupported. All examples and tooling references (such as PowerShell) are Windows-centric, with no mention of Linux equivalents or cross-platform CLI support. Windows tools and patterns (e.g., IIS file extension filtering) are referenced exclusively.
Recommendations
  • Add support and documentation for Linux-based SQL Server deployments in Azure VMs, or clarify roadmap and alternatives for Linux users.
  • Provide equivalent examples and instructions using Azure CLI or other cross-platform tools, not just PowerShell.
  • Include Linux-specific considerations, limitations, and troubleshooting steps where appropriate.
  • Reference Linux tools and patterns alongside Windows ones (e.g., discuss file extension filtering in Apache/Nginx if relevant).
  • If Linux is not supported, offer clear guidance on alternative backup solutions for Linux SQL Server in Azure.
Backup Transport Layer Security in Azure Backup .../blob/main/articles/backup/transport-layer-security.md
High Priority View Details →
Scanned: 2026-01-11 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, with all configuration and verification steps described using Windows registry edits and references to Windows KB articles. There are no examples or instructions for enabling or verifying TLS 1.2 on Linux systems, nor is there any mention of Linux-specific tools or configuration files. The FAQ and related content also reference Windows-centric resources and patterns.
Recommendations
  • Add instructions for enabling and verifying TLS 1.2 on Linux systems, including relevant configuration files (e.g., OpenSSL, libssl, system-wide TLS settings).
  • Provide Linux command-line examples (such as using openssl or curl to verify TLS support) alongside Windows registry examples.
  • Reference Linux documentation and best practices for TLS configuration in the 'Related content' section.
  • Clarify Azure Backup support and requirements for Linux-based clients, if applicable.
  • Ensure parity in troubleshooting steps for both Windows and Linux environments.
Backup Restore SQL Server databases on an Azure VM .../main/articles/backup/restore-sql-database-azure-vm.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: it exclusively references Windows-specific tools (e.g., PsExec, NT AUTHORITY\SYSTEM), assumes Windows file paths (C:\Program Files), and provides examples and instructions tailored to Windows environments. There are no Linux-specific examples, instructions, or mentions of restoring SQL Server databases on Linux-based Azure VMs, nor guidance for Linux file permissions, paths, or equivalent tooling. The documentation also implicitly assumes SQL Server is running on Windows, omitting any mention of SQL Server on Linux, which is supported in Azure VMs.
Recommendations
  • Add explicit guidance and examples for restoring SQL Server databases on Linux-based Azure VMs, including Linux file paths and permissions.
  • Provide Linux equivalents for Windows-only tools and commands (e.g., alternatives to PsExec for privilege escalation, instructions for mounting Azure File Shares on Linux, and managing file permissions).
  • Include T-SQL restore examples that use Linux-style paths and clarify any differences in restore procedures on Linux.
  • Mention and link to documentation for SQL Server on Linux in Azure VMs, and clarify any platform-specific limitations or requirements.
  • Ensure that instructions for creating and editing configuration files (such as ExtensionSettingsOverrides.json) include Linux file system locations and syntax.
  • Where screenshots or UI references are platform-specific, note any differences for Linux users or provide alternative visuals.
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation primarily focuses on using the Azure portal for disk backup operations and mentions automation via PowerShell and CLI only in passing. When scripting is referenced, PowerShell is listed before CLI, which can suggest a Windows-first bias. There are no explicit Linux-specific examples, nor is Bash or Linux tooling discussed. The documentation does not provide parity in example scripts or walkthroughs for Linux users, and the CLI is not given equal prominence to PowerShell.
Recommendations
  • Provide explicit Azure CLI (bash) examples alongside PowerShell for all automation steps, especially for configuring backups across subscriptions.
  • When referencing scripting options, list Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
  • Include a section or callout for Linux users, clarifying that all operations can be performed from Linux environments using Azure CLI.
  • Add links to Linux-specific guides or troubleshooting for disk backup operations.
  • Ensure screenshots and walkthroughs do not assume a Windows environment (e.g., avoid showing only Windows-style UI or PowerShell terminals).
Backup Back Up a PostgreSQL Databases by Using the Azure CLI ...ocs/blob/main/articles/backup/backup-postgresql-cli.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. PowerShell is referenced repeatedly as the default or primary scripting environment, especially in policy object discussions and modification workflows. File path examples use Windows-style backslashes (e.g., .\OSSPolicy.json), and instructions for editing policy files assume Windows conventions. There is no mention of Linux shell equivalents (such as bash, sh, or Linux file paths), nor are Linux-specific examples or notes provided for file manipulation or scripting. The documentation assumes familiarity with Windows tools and patterns, and does not offer parity for Linux users.
Recommendations
  • Provide Linux/bash equivalents for all PowerShell and Windows-centric examples, including file path conventions and scripting workflows.
  • Explicitly mention cross-platform compatibility for Azure CLI commands, and clarify any differences in file handling between Windows and Linux.
  • Include sample commands using Linux file paths (e.g., ./OSSPolicy.json) and demonstrate editing JSON files with common Linux tools (e.g., jq, sed, nano, vi).
  • Add a section or callouts for Linux users, highlighting any platform-specific considerations or best practices.
  • Avoid referring to PowerShell objects as the default or only way to interact with policies; instead, present both PowerShell and bash approaches side by side.
Backup Azure Backup release notes - Archive .../main/articles/backup/backup-release-notes-archived.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation shows evidence of Windows bias, primarily through repeated references to Windows-specific backup tools (MARS agent, Microsoft Azure Backup Server), features that are exclusive or primarily available for Windows Server, and examples or instructions that mention PowerShell before CLI or Linux alternatives. Linux workloads (e.g., SAP HANA on RHEL, PostgreSQL) are mentioned, but Windows-centric solutions and tools are more frequently highlighted, and some features/tools (MARS, MABS) are Windows-only. In several cases, PowerShell is referenced as the primary automation method, with CLI mentioned as an alternative or after PowerShell. There is limited coverage of Linux-native backup agents or parity in management tooling.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows/PowerShell ones, especially for automation and agent installation.
  • Clearly indicate platform support for each feature/tool, and highlight Linux parity where available.
  • When mentioning backup agents or servers (e.g., MARS, MABS), note their platform limitations and suggest Linux alternatives or Azure-native solutions for Linux workloads.
  • Ensure CLI and REST API examples are given equal prominence to PowerShell, and consider Bash scripting examples for Linux users.
  • Expand documentation on backup/restore for Linux workloads (e.g., SAP HANA on RHEL, PostgreSQL) with detailed, platform-specific guidance.
Backup Manage Backups with Azure role-based access control ...docs/blob/main/articles/backup/backup-rbac-rs-vault.md
High Priority View Details →
Scanned: 2026-01-11 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 a Windows bias primarily through its explicit focus on Windows-centric backup scenarios and tooling. It references Windows Server, System Center Data Protection Manager (SCDPM), and Azure Backup Server in backup registration and management operations, without mentioning Linux equivalents or scenarios. The 'Important' note highlights PowerShell and UI tools that are Windows-specific, and the only on-premises backup examples are for Windows platforms. There are no examples or guidance for Linux-based backup agents, nor are Linux-specific tools or patterns discussed. Additionally, the order of presentation and examples consistently prioritize Windows environments.
Recommendations
  • Include examples and guidance for Linux-based backup agents and scenarios, such as Azure Backup for Linux VMs or on-premises Linux servers.
  • Mention Linux CLI tools (e.g., Bash, Azure CLI on Linux) alongside or before PowerShell, and clarify cross-platform support for all command-line instructions.
  • Add documentation for registering and managing backups for on-premises Linux servers, including any supported agents or integration patterns.
  • Ensure parity in describing UI and automation options for both Windows and Linux environments, including REST API and CLI usage on Linux.
  • Review and update terminology to avoid Windows-first language, and explicitly state platform support where relevant.
Backup Troubleshoot SQL Server database backup ...rticles/backup/backup-sql-server-azure-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-11 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 towards Windows environments. All examples, file paths, and troubleshooting steps reference Windows-specific locations (e.g., C:\Program Files\...), Windows services, and Windows security policies. The AzureBackupWindowsWorkload extension is mentioned exclusively, with no reference to Linux equivalents. Troubleshooting steps and error resolutions rely on Windows tools (Control Panel, Local Security Policy), and PowerShell is suggested for automation. There are no examples or guidance for SQL Server running on Linux VMs, nor any mention of Linux file paths, services, or commands.
Recommendations
  • Add explicit guidance and troubleshooting steps for SQL Server running on Linux VMs, including Linux-specific file paths and service management.
  • Include Linux equivalents for extension installation, configuration, and error resolution (e.g., systemd service management, relevant Linux permissions).
  • Provide examples using Linux shell commands (bash) alongside PowerShell, where applicable.
  • Reference Linux documentation and support articles where relevant.
  • Clarify which steps are Windows-only and which are cross-platform, and provide parity for Linux users wherever possible.
Backup Back up SQL Server always on availability groups ...les/backup/backup-sql-server-on-availability-groups.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses exclusively on SQL Server deployments in Azure VMs, which are typically Windows-based. There is no mention of Linux-based SQL Server deployments, nor are there examples or guidance for Linux environments. All backup workflows, node registration, and extension installation instructions implicitly assume Windows VMs. No Linux-specific tools, commands, or troubleshooting are referenced, and the documentation does not clarify whether the guidance applies to SQL Server on Linux VMs or provide parity for such scenarios.
Recommendations
  • Explicitly state whether the guidance applies to both Windows and Linux SQL Server deployments.
  • Add examples and instructions for Linux-based SQL Server AG nodes, including how to install and configure the workload backup extension on Linux VMs.
  • Reference Linux-specific tools and commands (e.g., systemctl, shell scripts) where relevant.
  • Clarify any limitations or differences in Azure Backup support for SQL Server AGs on Linux.
  • Provide troubleshooting steps and error codes relevant to Linux environments.
  • Ensure parity in diagrams and sample deployments by including Linux VM scenarios.
Backup Back up SQL Server from the Azure VM blade using Azure Backup ...ckup/backup-sql-server-database-from-azure-vm-blade.md
High Priority View Details →
Scanned: 2026-01-11 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 a Windows bias by exclusively describing backup procedures for SQL Server on Azure VMs using Windows-specific tools and extensions (e.g., AzureBackupWindowsWorkload, NT Service accounts, SQLIaaSExtension). There are no references to Linux-based SQL Server deployments, nor are Linux-specific instructions, examples, or tools mentioned. The documentation implicitly assumes the SQL Server VM is running Windows, with no guidance for users running SQL Server on Linux VMs.
Recommendations
  • Add explicit guidance and examples for backing up SQL Server running on Linux-based Azure VMs, including any differences in process, prerequisites, and supported features.
  • Mention and document Linux-specific backup extensions or agents, if available, or clarify limitations for Linux SQL Server VMs.
  • Include screenshots and step-by-step instructions for Linux VM scenarios, or provide links to relevant Linux documentation.
  • Clarify in the prerequisites section whether the instructions apply only to Windows VMs, and provide parity for Linux users where possible.
Backup Back up multiple SQL Server VMs from the vault ...rticles/backup/backup-sql-server-database-azure-vms.md
High Priority View Details →
Scanned: 2026-01-11 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 page exhibits a strong Windows bias. All examples, instructions, and tooling references are specific to Windows-based SQL Server VMs. The AzureBackupWindowsWorkload extension, NT Service accounts, and connectivity test scripts are all Windows-centric. There is no mention of Linux-based SQL Server VMs, nor are any Linux-specific instructions, troubleshooting steps, or tools provided. The documentation implicitly assumes the SQL Server VM is running Windows, and does not address scenarios for SQL Server on Linux VMs.
Recommendations
  • Add explicit guidance and examples for backing up SQL Server running on Linux Azure VMs, including any differences in prerequisites, agent/extension installation, and supported features.
  • Provide parity in troubleshooting tools, such as connectivity test scripts for Linux environments.
  • Clarify which steps, extensions, and service accounts are Windows-specific, and document the Linux equivalents (if available) or limitations.
  • Include Linux-specific screenshots, CLI commands, and configuration steps where applicable.
  • Mention any differences in backup/restore support matrix for SQL Server on Linux VMs.
  • If SQL Server on Linux is not supported by Azure Backup, state this clearly in the prerequisites and support matrix.
Backup Automation in Azure Backup support matrix ...blob/main/articles/backup/backup-support-automation.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page consistently lists PowerShell as the first automation method for nearly all backup and restore operations, reflecting a Windows-centric approach. PowerShell is highlighted with direct links to examples, and its support is emphasized even for workloads that are commonly deployed on Linux (e.g., PostgreSQL, SAP HANA). There is a lack of explicit mention of Linux-specific tools or shell scripting alternatives, and no Bash or Linux shell examples are provided. The documentation implicitly assumes PowerShell as the primary scripting interface, which may disadvantage Linux users.
Recommendations
  • Alternate the order of automation methods (e.g., list CLI before PowerShell in some tables) to avoid Windows-first perception.
  • Explicitly mention that Azure CLI is cross-platform and provide Bash/Linux shell script examples alongside PowerShell for key operations.
  • Where PowerShell is not supported (e.g., SAP HANA), clarify that CLI is suitable for Linux environments and provide Linux-centric guidance.
  • Add a section or callout for Linux administrators, summarizing best practices and recommended tools for automation.
  • Include references to Linux-native automation tools (e.g., Bash, cron, Ansible) where appropriate, or link to relevant Azure/Linux integration documentation.
Backup MABS & System Center DPM support matrix ...main/articles/backup/backup-support-matrix-mabs-dpm.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation for MABS & System Center DPM support matrix is heavily focused on Windows environments. All examples, supported operating systems, and deployment scenarios are centered around Windows Server and related Microsoft products. There is no mention of Linux support, Linux-based workloads, or cross-platform backup scenarios. Windows-specific tools, patterns, and requirements (such as domain membership, NTFS/ReFS, and Windows authentication) are referenced exclusively and repeatedly, with no Linux equivalents or alternatives provided.
Recommendations
  • Explicitly state whether Linux workloads are supported or not, and if so, provide guidance and examples for Linux backup scenarios.
  • If Linux is not supported, add a clear note at the beginning of the document to inform users.
  • If partial Linux support exists (e.g., for file-level backup or agent-based protection), include Linux-specific instructions, supported distributions, and limitations.
  • Provide parity in documentation by listing Linux operating systems and workloads in support matrices where applicable.
  • Include examples of backup and restore operations for Linux machines, using relevant tools or agents.
  • Mention any cross-platform alternatives or integration options (e.g., using Azure Backup directly for Linux VMs) to help users with heterogeneous environments.
Backup Support matrix for the MARS agent ...in/articles/backup/backup-support-matrix-mars-agent.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows Only 🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation for the MARS agent is heavily Windows-centric. All examples, supported operating systems, and tooling references are exclusively for Windows environments. There is no mention of Linux support, Linux equivalents, or cross-platform considerations. Windows-specific tools (PowerShell, MMC, DISM.exe, registry edits) are referenced throughout, and all instructions and support matrices are for Windows OSes only.
Recommendations
  • Explicitly state that the MARS agent is Windows-only, and clarify if Linux support is unavailable or planned.
  • Provide guidance or links for Linux backup solutions in Azure, such as Azure Backup for Linux VMs or third-party agents.
  • Where possible, mention Linux equivalents for backup, restore, and offline seeding workflows.
  • Add a comparison table or section outlining backup options for Linux machines in Azure, including supported agents and features.
  • If any cross-platform backup features exist (e.g., via REST API, CLI), include examples for Linux environments.
  • Avoid assuming Windows as the default platform; structure documentation to acknowledge other OSes and their backup needs.
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation for backing up the MABS server is heavily Windows-centric. All examples, instructions, and tooling references are specific to Windows environments (e.g., PowerShell, mountvol.exe, diskshadow.exe, psexec.exe, Net Share, Windows Explorer, Windows VSS). There are no Linux equivalents, nor any mention of how to perform these tasks on Linux or cross-platform systems. Windows tools and patterns are presented exclusively and are assumed as the default, with no guidance for administrators using Linux servers or tools.
Recommendations
  • Explicitly state that MABS is a Windows-only product if true, or clarify platform limitations at the start of the documentation.
  • If any components (such as SQL Server backup/restore) can be performed from Linux or cross-platform tools, provide equivalent Linux examples (e.g., using sqlcmd, mounting VHDs on Linux, SMB shares, etc.).
  • Where PowerShell or Windows-specific tools are used, mention alternatives for Linux (if possible) or note that these steps require a Windows environment.
  • Add a section addressing backup strategies for environments where Linux servers are present, even if only for accessing or copying backup files.
  • If Azure Backup or SQL Server supports Linux agents or clients, provide instructions for those platforms.
  • Make clear in the prerequisites and overview that all steps assume a Windows Server environment, and suggest workarounds or alternatives for mixed OS environments.
Backup Support matrix for Azure VM backups ...lob/main/articles/backup/backup-support-matrix-iaas.md
High Priority View Details →
Scanned: 2026-01-11 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 page demonstrates a Windows bias in several ways: Windows scenarios, tools, and agents (such as MARS, DPM, MABS, PowerShell) are described in detail and often presented before or instead of Linux equivalents. Windows-specific restore methods (e.g., using PowerShell) are mentioned, while Linux CLI or scripting alternatives are absent. Many backup and restore features (such as file-level restore, use of MARS agent, DPM/MABS integration) are supported only for Windows, with Linux support either missing or explicitly called out as unsupported. Examples and instructions for Linux users are minimal, and Linux-specific limitations are listed without offering parity solutions.
Recommendations
  • Provide Linux CLI (e.g., Azure CLI, Bash) examples alongside or before PowerShell examples for backup and restore operations.
  • Include Linux-specific guidance for restore scenarios, such as disk attachment and VM creation using Linux tools.
  • Expand support matrices and feature tables to clarify Linux support and offer alternative solutions or workarounds where features are Windows-only.
  • Offer parity for agent-based backup and restore features (e.g., file-level restore, DPM/MABS integration) for Linux, or document equivalent open-source or Azure-native solutions.
  • Ensure that Linux scenarios are described with the same level of detail and step-by-step instructions as Windows scenarios.
  • Add more Linux-focused 'Next steps' links and tutorials, similar to those provided for Windows.