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 101-125 of 520 flagged pages
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 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Microsoft Azure Backup Server (MABS), which is a Windows-only tool. All instructions, screenshots, and workflows assume use of Windows Server and Windows-style management consoles, with no mention of Linux or macOS alternatives, nor any cross-platform command-line examples. There is no guidance for Linux-based SQL Server deployments or backup solutions, and Windows terminology (e.g., NTAuthority\System, blades, right-click) is used exclusively.
Recommendations
  • Explicitly state that MABS is Windows-only and provide guidance for Linux-based SQL Server deployments.
  • Add alternative instructions or links for backing up SQL Server on Linux (e.g., using Azure Backup agent, CLI, or third-party tools).
  • Include parity examples for Linux environments, such as command-line steps or references to Azure Backup for Linux.
  • Clarify prerequisites and limitations for non-Windows users at the top of the article.
  • Consider reordering or separating instructions so Linux users can quickly find relevant content.
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 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, referencing Windows Server Backup, Windows Recovery Environment (WinRE), Windows-specific folders and paths, and PowerShell cmdlets. All workflows, prerequisites, and recovery instructions are tailored for Windows Server, with no mention of Linux or macOS support, tools, or equivalent procedures. There are no examples or guidance for non-Windows systems, and the documentation assumes the user is operating within a Windows ecosystem.
Recommendations
  • Clarify in the introduction and prerequisites that Azure Backup Server's system state and BMR features are Windows-only, if that is the case.
  • If Linux/macOS support is possible, provide equivalent backup and recovery workflows for those platforms, referencing native tools (e.g., rsync, tar, dd, or third-party solutions).
  • Include examples and instructions for Linux-based systems, or link to relevant documentation for Linux/macOS backup and recovery.
  • If Azure Backup Server does not support Linux/macOS for system state/BMR, explicitly state this limitation to avoid confusion.
  • Consider providing a comparison table of supported features across Windows, Linux, and macOS, if applicable.
Backup Troubleshoot SQL Server database backup ...rticles/backup/backup-sql-server-azure-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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, with all examples, file paths, and troubleshooting steps referencing Windows-specific tools, directories, and services. The AzureBackupWindowsWorkload extension and its usage are described only for Windows VMs, and all operational instructions (such as file placement, service accounts, and permissions) use Windows conventions. PowerShell is referenced for automation, and there are no Linux-specific instructions, examples, or parity notes for users running SQL Server on Linux VMs.
Recommendations
  • Add explicit guidance for SQL Server on Linux VMs, including supported backup and restore workflows.
  • Provide Linux-specific examples for file paths, service accounts, and extension installation.
  • Include troubleshooting steps relevant to Linux environments (e.g., systemd services, SELinux, Linux antivirus exclusions).
  • Clarify whether the AzureBackupWindowsWorkload extension or similar functionality is available for Linux VMs, and if not, document alternatives.
  • Offer PowerShell alternatives (such as Bash scripts or Azure CLI) for Linux users.
  • Ensure parity in error message documentation, including Linux-specific causes and resolutions.
Backup MABS & System Center DPM support matrix ...main/articles/backup/backup-support-matrix-mabs-dpm.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows environments, with all examples, supported operating systems, and deployment scenarios centered around Windows Server and related Microsoft technologies. There is no mention of Linux or macOS support, nor are any examples or guidance provided for non-Windows platforms. All backup agents, workflows, and compatibility matrices are exclusively for Windows-based systems.
Recommendations
  • Explicitly state whether Linux/macOS platforms are supported or not, and provide rationale.
  • If Linux backup is possible (e.g., via agent or interoperability), add clear instructions and examples for Linux deployments.
  • Include a support matrix or section for non-Windows operating systems, even if only to clarify limitations.
  • If Windows-only is by design, add a prominent note at the top of the documentation to set expectations for cross-platform users.
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 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows-based SQL Server VMs. It exclusively references Windows-specific extensions (AzureBackupWindowsWorkload, SqlIaaSExtension), Windows service accounts (NT Service\AzureWLBackupPluginSvc), and does not mention or provide guidance for Linux-based SQL Server VMs. There are no Linux-specific instructions, examples, or notes regarding parity or differences.
Recommendations
  • Explicitly state whether the described backup process applies to Linux-based SQL Server VMs, and if not, provide a link or section for Linux instructions.
  • Add examples and guidance for configuring Azure Backup on SQL Server running on Linux VMs, including any required extensions, service accounts, or differences in workflow.
  • Clarify in prerequisites and throughout the documentation which steps/tools are Windows-only and provide Linux alternatives where possible.
  • Include screenshots and step-by-step instructions for Linux scenarios if supported.
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, with all examples, tools, and recovery procedures relying on Windows-specific utilities (e.g., mountvol.exe, diskshadow.exe, psexec.exe, PowerShell commands, Net Share, Windows Explorer, and references to drive letters and Windows file paths). There are no Linux/macOS equivalents or alternative instructions, and all backup and restore workflows assume the use of Windows Server and Windows-based tools.
Recommendations
  • Add explicit statements clarifying that MABS is Windows-only, or, if partial Linux support exists (e.g., for SQL Server), provide Linux/macOS instructions for backup and restore operations.
  • Where possible, offer cross-platform alternatives for database backup and restore (e.g., using sqlcmd, native SQL Server backup commands, or SMB shares from Linux).
  • Include notes or links for users running SQL Server on Linux, describing how to adapt backup/restore procedures.
  • Reorder examples so that platform-neutral or cross-platform methods (e.g., SQL Server native backup) are presented before Windows-specific workflows.
  • Clearly indicate which steps/tools are Windows-only, and suggest alternatives or workarounds for non-Windows 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 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation for the MARS agent is exclusively focused on Windows environments. All examples, supported operating systems, installation instructions, and tooling references are Windows-specific, with no mention of Linux or macOS support or equivalents. Windows tools (PowerShell, MMC, DISM.exe, registry edits) are referenced throughout, and all backup scenarios and limitations are described only for Windows platforms.
Recommendations
  • Explicitly state in the introduction that the MARS agent is Windows-only, and provide guidance or links for Linux/macOS backup solutions (e.g., Azure Backup for Linux VMs, Azure Backup Server alternatives).
  • Add a comparison table or section listing backup options for non-Windows platforms, including supported agents and features.
  • Where possible, mention cross-platform alternatives for backup, such as Azure Backup for Linux VMs, and provide links to relevant documentation.
  • Clarify in installation and requirements sections that Linux/macOS are not supported, and suggest alternative approaches for those platforms.
Backup Install the Microsoft Azure Recovery Services (MARS) agent ...e-docs/blob/main/articles/backup/install-mars-agent.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is exclusively focused on installing and using the MARS agent for Windows machines. All examples, instructions, prerequisites, and screenshots are Windows-specific. There is no mention of Linux or macOS support, nor are any equivalent tools or instructions provided for non-Windows platforms. PowerShell and Windows-specific components (e.g., .NET Framework, .exe installers) are referenced throughout, with no alternatives for other operating systems.
Recommendations
  • Clearly state in the introduction and prerequisites whether the MARS agent is Windows-only, and if so, provide guidance for Linux/macOS users (e.g., suggest alternative backup solutions supported on those platforms).
  • If Linux/macOS support is possible, add installation and usage instructions for those platforms, including relevant command-line examples and screenshots.
  • Mention and link to Azure backup solutions for Linux (such as Azure Backup for Linux VMs, or third-party tools) in the 'Next steps' or 'See also' sections.
  • Avoid using 'Windows machines' as the default term throughout; specify platform limitations and alternatives where appropriate.
Backup Manage telemetry settings in Microsoft Azure Backup Server (MABS) ...ure-docs/blob/main/articles/backup/manage-telemetry.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on the Microsoft Azure Backup Server (MABS) console, which is a Windows-only tool. All instructions and screenshots pertain to the Windows GUI, with no mention of Linux or macOS equivalents, nor any CLI or cross-platform alternatives. There are no examples or guidance for managing telemetry settings outside of the Windows environment.
Recommendations
  • Clarify in the introduction that MABS is a Windows-only product, if applicable.
  • If telemetry management is possible via command line or scripts, provide PowerShell and, if supported, Bash/Linux shell examples.
  • Explicitly state platform limitations and suggest alternatives for Linux/macOS users (e.g., Azure Backup alternatives, cross-platform tools).
  • If any telemetry settings can be managed via configuration files, document their location and format for manual editing on non-Windows systems.
Backup What Azure Backup Server V3 RTM can back up .../backup/microsoft-azure-backup-server-protection-v3.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows workloads and environments, listing only Windows operating systems, applications, and backup scenarios in detail. Linux is mentioned only briefly as a guest VM, with no specific Linux distributions, file systems, or application backup scenarios covered. Windows-specific technologies (NTFS, VSS, ReFS, Windows Management Framework, Hyper-V, etc.) are referenced throughout, while Linux equivalents are absent.
Recommendations
  • Add detailed Linux support matrix, including supported distributions, file systems (e.g., ext4, xfs), and application backup scenarios.
  • Include Linux-specific recovery options and limitations, such as item-level recovery, file system consistency, and snapshot mechanisms.
  • Provide parity in examples and explanations for Linux environments, not just Windows VMs.
  • Clarify whether Azure Backup Server can be installed on Linux hosts, or if only Windows is supported.
  • Mention Linux backup tools or patterns if relevant, and address any differences in backup/restore workflows.
Backup Offline backup by using Azure Data Box .../main/articles/backup/offline-backup-azure-data-box.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows Only Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows, with all instructions, prerequisites, and examples tailored exclusively for Windows environments. The process requires Windows-specific tools (MARS Agent, PowerShell, PsExec, Windows registry, Control Panel), and there is no mention of Linux or macOS support or alternatives. All examples and screenshots are Windows-centric, and critical steps (such as mounting, agent installation, and troubleshooting) rely on Windows-only components.
Recommendations
  • Clearly state platform limitations at the top of the article, including lack of Linux/macOS support.
  • If possible, provide parity for Linux/macOS users by documenting equivalent workflows, tools, or supported agents.
  • If the MARS Agent is Windows-only, suggest alternative Azure backup solutions for Linux/macOS and link to relevant documentation.
  • Where PowerShell is required, note whether Azure CLI or other cross-platform tools can be used for any steps.
  • Add a support matrix section that explicitly lists unsupported platforms and explains why.
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation focuses exclusively on backup tools that are Windows-centric (MARS Agent, MABS, DPM-A), with no mention of Linux-native backup agents or workflows. There are no examples, instructions, or references for performing offline backup from Linux systems, nor is there discussion of cross-platform utilities or compatibility. This creates a bias toward Windows environments and leaves Linux/macOS users without clear guidance.
Recommendations
  • Explicitly state platform requirements and limitations for offline backup options.
  • Add sections or links describing how Linux users can perform offline backups, including supported agents (if any), compatible utilities, and workflows.
  • If Linux is not supported, clarify this early in the documentation to set expectations.
  • Provide parity by including Linux command-line examples and tools where possible, or reference third-party solutions for Linux environments.
Backup Using Pre-Backup and Post-Backup Scripts ...main/articles/backup/pre-backup-post-backup-scripts.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows environments, referencing Windows-specific paths, tools, and conventions (e.g., 'Drive:', 'cscript', and Windows-style file paths). There are no examples or guidance for Linux or macOS systems, and all instructions assume a Windows file system and scripting environment.
Recommendations
  • Add explicit notes about platform support: clarify whether MABS supports Linux/macOS as protected computers and, if so, provide equivalent instructions.
  • If Linux/macOS are supported, include examples using Linux paths (e.g., /opt/scripts/myscript.sh), shell scripts, and relevant execution commands.
  • Mention Linux/macOS permission management (e.g., chmod, chown) alongside Windows ACLs.
  • If only Windows is supported, state this clearly at the top to avoid confusion for non-Windows users.
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-11 06:20
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 towards Windows environments. All instructions, examples, and tooling are specific to Windows Server, DPM, and MABS. There are no Linux or macOS equivalents, nor any mention of how to perform these tasks on non-Windows platforms. Windows-specific tools (PSExec, Azure PowerShell, registry edits) are required, and all example commands are for Windows. This makes the documentation inaccessible for Linux/macOS users.
Recommendations
  • Explicitly state platform limitations at the top of the document.
  • If possible, provide guidance or alternatives for Linux/macOS users, or clarify that the feature is not supported on those platforms.
  • Offer cross-platform Azure tooling examples (e.g., Azure CLI, REST API) where feasible.
  • If Data Box or Azure Backup supports Linux servers, add Linux-specific instructions and examples.
  • Where PowerShell is used, mention if Azure CLI or other cross-platform tools can be substituted.
  • Avoid requiring Windows-only utilities (e.g., PSExec, registry edits) unless absolutely necessary, and document alternatives if available.
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-11 06:20
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 toward Windows environments, with all examples, screenshots, and instructions referencing Windows Server, Windows clients, DPM, MABS, and Windows-specific utilities (elevated command prompt, regedit, Certlm.msc, etc.). There are no Linux/macOS examples, nor any mention of how to perform the workflow on non-Windows platforms. All tooling and workflows assume a Windows OS, and PowerShell is referenced for user ID retrieval. This creates significant friction for Linux/macOS users and may prevent them from completing the workflow.
Recommendations
  • Explicitly state OS requirements and limitations at the beginning of the article.
  • If possible, provide equivalent workflows or guidance for Linux/macOS environments, or clarify that the tools/utilities are Windows-only.
  • Offer alternative methods for certificate generation, registry modification, and disk preparation that could be performed on Linux/macOS, if supported.
  • Include Linux/macOS-specific examples, commands, and screenshots where applicable.
  • If the workflow is fundamentally Windows-only, provide links to Linux/macOS backup solutions or Azure Import/Export documentation for those platforms.
Backup Quickstart - Bicep file VM Backup ...lob/main/articles/backup/quick-backup-vm-bicep-file.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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. All deployment and cleanup instructions use Azure PowerShell scripts exclusively, with no mention of Azure CLI or Bash alternatives. The Bicep template provisions only Windows VMs, with no Linux options or parameters. The guidance assumes familiarity with Windows tools and patterns, and links to PowerShell-centric backup/monitoring instructions. Linux/macOS users are left without direct, platform-agnostic steps for deploying or managing backups.
Recommendations
  • Add Azure CLI and Bash examples for template deployment, resource cleanup, and backup operations.
  • Include Linux VM options in the Bicep template, such as an 'osType' parameter or a separate Linux-focused example.
  • Provide links to Linux/macOS-specific documentation for backup and monitoring tasks.
  • Reorder examples so that platform-neutral or cross-platform options (e.g., Azure CLI) appear before or alongside PowerShell.
  • Explicitly state platform requirements and alternatives in the prerequisites section.
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows environments, specifically the MARS agent, which is a Windows-only backup tool. All operational steps, screenshots, and automation references are centered around the Windows MARS console and PowerShell commands. There are no Linux/macOS equivalents or examples, and the documentation does not address cross-platform scenarios or alternative backup agents for non-Windows systems.
Recommendations
  • Clearly state at the beginning that MARS agent is Windows-only and provide links to equivalent backup solutions for Linux/macOS (e.g., Azure Backup for Linux VMs).
  • Add a comparison table or section outlining backup agent options for Linux/macOS and how passphrase/key management works for those platforms.
  • If possible, provide CLI-only workflows that could be run from Linux/macOS for Key Vault management, even if the backup agent itself is Windows-only.
  • Ensure that PowerShell and Windows-specific instructions are labeled as such, and offer Azure CLI examples wherever feasible.
  • Include troubleshooting notes for users who may attempt to use MARS on non-Windows platforms, clarifying support boundaries.
Backup Script Sample - Create a new or modify the current file and folder backup policy ...ticles/backup/scripts/set-file-folder-backup-policy.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is exclusively focused on Windows, providing only PowerShell script examples and instructions for managing backup policies with the MARS agent. There are no Linux or macOS equivalents, nor any mention of cross-platform alternatives or parity. All tooling and patterns are Windows-centric, and the workflow assumes a Windows environment.
Recommendations
  • Add equivalent examples for Linux/macOS using Bash, Python, or other relevant scripting languages.
  • Clarify whether the MARS agent and backup policy management are supported on Linux/macOS, and if not, suggest alternative solutions for those platforms.
  • If cross-platform support is unavailable, explicitly state the Windows-only scope at the top of the documentation.
  • Provide links or references to Linux/macOS backup automation documentation if available.
Backup Script Sample - Create a new or modify the current system state backup policy ...icles/backup/scripts/set-system-state-backup-policy.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
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, referencing Windows-specific modules and registry paths. There are no examples or guidance for Linux or macOS users, nor any mention of equivalent tools or procedures for non-Windows platforms.
Recommendations
  • Clarify in the introduction that the script and procedure are Windows-only, if that is the case.
  • If Linux/macOS support exists, provide equivalent scripts or command-line instructions for those platforms.
  • Mention whether the MARS agent and system state backup functionality are available on Linux/macOS, and link to relevant documentation if so.
  • If not supported, explicitly state the platform limitation to avoid confusion for non-Windows users.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation exclusively describes upgrading the Microsoft Azure Recovery Services (MARS) agent, which is a Windows-only tool. All instructions, screenshots, and examples are tailored for Windows environments (including Remote Desktop, DPM, and Windows UI wizards). There is no mention of Linux or macOS support, nor are alternative backup agent upgrade instructions provided for non-Windows platforms. The 'Next steps' section further reinforces the Windows focus.
Recommendations
  • Explicitly state that the MARS agent is only supported on Windows, and provide links or references to equivalent Azure Backup solutions for Linux/macOS (e.g., Azure Backup for Linux VMs, Azure CLI, or Recovery Services Vault documentation for Linux).
  • Add a section clarifying backup agent upgrade procedures for Linux servers, if applicable, or direct users to the appropriate documentation for Linux backup solutions.
  • If Azure Backup supports Linux agents, include upgrade instructions and examples for those platforms.
  • Ensure parity in documentation by mentioning Linux/macOS limitations or alternatives at the beginning of the article.
Backup Tutorial - Back Up SQL Server Databases to Azure ...-docs/blob/main/articles/backup/tutorial-sql-backup.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively describes backup of SQL Server databases on Azure VMs using Windows-centric tooling and patterns. It references the installation of the AzureBackupWindowsWorkload extension, creation of a Windows service account (NT Service\AzureWLBackupPluginSvc), and relies on the SQLIaaSExtension—all of which are Windows-specific. There are no examples, instructions, or notes for Linux-based SQL Server VMs, nor is there any mention of Linux support or alternative procedures for non-Windows environments.
Recommendations
  • Explicitly state whether Linux-based SQL Server VMs are supported or not for Azure Backup.
  • If Linux support exists, provide parallel instructions and screenshots for Linux VMs, including any differences in extension installation, service account creation, and backup configuration.
  • If Linux is not supported, add a clear note at the beginning of the tutorial to inform users.
  • Include CLI or script-based examples (e.g., Bash, Azure CLI) for Linux users where applicable.
  • Reference Linux-specific documentation or alternatives if Azure Backup for SQL Server on Linux is not available.
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-10 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 (MABS), which is a Windows-only tool. All instructions, screenshots, and file paths (e.g., C:\Program Files\...) are Windows-centric. There are no Linux equivalents, examples, or mentions of Linux-based Exchange deployments or backup tools. The documentation assumes the administrator is operating in a Windows environment from start to finish.
Recommendations
  • Explicitly state that MABS is a Windows-only solution and clarify platform requirements at the beginning.
  • Provide guidance or links for Linux-based Exchange alternatives, if supported, or mention that Linux is not supported.
  • If Linux support is planned, add parallel instructions, examples, and screenshots for Linux environments.
  • Reference cross-platform backup tools or Azure-native backup options that can be used with Linux servers, if applicable.
  • Ensure that documentation for similar backup scenarios includes both Windows and Linux workflows where possible.
Backup Monitor Azure Backup protected workloads ...les/backup/backup-azure-monitoring-built-in-monitor.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias by referencing Windows-centric backup tools (DPM, MABS, MARS) and providing links and examples that focus on Windows Server management. There are no explicit Linux backup tool mentions, nor are there examples or instructions for monitoring Linux workloads. The order and emphasis are on Windows solutions, with no Linux parity in examples or tool references.
Recommendations
  • Include explicit references to Linux-supported backup agents and workloads (e.g., Azure Backup for Linux VMs, Azure Backup agent for Linux).
  • Provide examples and instructions for monitoring Linux backup items and jobs, including any differences in portal experience or supported features.
  • Mention Linux-specific constraints or requirements (e.g., supported distributions, file system considerations) alongside Windows details.
  • Ensure parity in documentation structure by presenting Linux and Windows solutions side-by-side where applicable.
  • Add links to Linux backup management documentation and troubleshooting guides.
Backup Tutorial - Back up Azure Database for PostgreSQL server ...lob/main/articles/backup/tutorial-postgresql-backup.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by primarily referencing PowerShell scripts for privilege assignment and not providing equivalent Linux/Unix command-line examples. PowerShell is mentioned as the main method for granting database privileges, with alternatives (PG admin or PSQL tool) only briefly referenced and not documented with examples. The step-by-step instructions and screenshots are focused on the Azure portal, which is platform-agnostic, but the only explicit scripting guidance is for PowerShell, leaving Linux users without clear instructions.
Recommendations
  • Provide equivalent examples using Linux/Unix command-line tools (e.g., psql) for granting database privileges.
  • Include sample bash scripts or psql commands alongside PowerShell scripts to ensure parity.
  • Explicitly document how to perform all steps on Linux systems, especially privilege assignment and automation.
  • Clarify that PowerShell is not required and offer guidance for users on non-Windows platforms.
  • Where templates/scripts are generated, offer both PowerShell and bash/psql versions for download.
Backup Azure Backup - Archive tier overview ...docs/blob/main/articles/backup/archive-tier-support.md
High Priority View Details →
Scanned: 2026-01-10 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 by listing PowerShell as a supported client before CLI, referencing Azure Virtual Machines (which are typically Windows-centric) as the primary workload, and omitting explicit Linux or Bash examples. The screenshots and walkthroughs focus on Azure VM backup scenarios, which are often associated with Windows environments, and do not mention Linux-specific backup scenarios or tools. There is no mention of Linux-based recovery point management, nor are there examples using Bash or Linux-native tooling.
Recommendations
  • Add explicit Linux/Bash CLI examples for managing Archive tier operations, alongside PowerShell examples.
  • Clarify that Azure Virtual Machines can run both Windows and Linux, and provide examples/scenarios for both OS types.
  • Include screenshots or walkthroughs for Linux VM backup and recovery point management.
  • List CLI before PowerShell in supported clients, or present them together to avoid order bias.
  • Reference Linux-native tools or commands where applicable, and ensure parity in documentation coverage for Linux workloads.