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 101-125 of 1604 flagged pages
Backup Troubleshoot SQL Server database backup ...rticles/backup/backup-sql-server-azure-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-13 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 is heavily biased towards Windows environments. All examples, file paths, and troubleshooting steps reference Windows-specific tools, directories (e.g., C:\Program Files), and services. The required extension is named AzureBackupWindowsWorkload, and instructions for tasks such as antivirus exclusions, file placement, and service permissions are exclusively for Windows. The only automation example for re-registration is in PowerShell, with no mention of Linux or cross-platform alternatives. There is no guidance for SQL Server on Linux VMs, nor are Linux file paths or tools referenced.
Recommendations
  • Add explicit instructions and examples for SQL Server running on Linux VMs, including relevant file paths (e.g., /opt/...), service management, and extension installation.
  • Provide Linux equivalents for all troubleshooting steps, especially for antivirus exclusions, file placement, and service permissions.
  • Include automation examples using Bash/CLI for Linux environments alongside PowerShell.
  • Clarify which steps are Windows-only and which are applicable to Linux, or provide a table comparing both.
  • Reference Linux documentation and tools where relevant (e.g., systemctl for service management, Linux guest agent installation).
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-13 00:00
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 Linux-based SQL Server VMs or provide instructions/examples for them. There is no guidance for Linux SQL Server VMs, nor any indication that Linux is supported or unsupported, which may leave Linux users uncertain or unable to complete the task.
Recommendations
  • Explicitly state whether Linux-based SQL Server VMs are supported or unsupported for Azure Backup in this scenario.
  • If Linux support exists, add equivalent instructions and screenshots for Linux SQL Server VMs, including any differences in extensions, service accounts, or configuration steps.
  • If Linux is not supported, add a clear note at the top of the article to inform users.
  • Where possible, use neutral terminology (e.g., 'SQL Server VM' instead of 'Windows VM') and avoid Windows-specific steps unless necessary.
  • Provide links or references to Linux backup solutions if Azure Backup does not support Linux SQL Server VMs.
Backup Support matrix for the MARS agent ...in/articles/backup/backup-support-matrix-mars-agent.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation for the MARS agent is exclusively focused on Windows environments. All examples, supported operating systems, installation instructions, and requirements are Windows-specific. There is no mention of Linux or macOS support, nor are there any examples or guidance for non-Windows platforms. Windows tools and patterns (e.g., registry edits, PowerShell, MMC, NTFS, VSS) are referenced throughout, with no Linux equivalents or alternatives.
Recommendations
  • Explicitly state that the MARS agent is not supported on Linux/macOS, if that is the case, to avoid confusion.
  • If any cross-platform alternatives exist (e.g., Azure Backup for Linux), provide links and guidance for Linux/macOS users.
  • Add a comparison table or section outlining backup options for Linux and macOS environments in Azure, including supported agents or methods.
  • Where possible, mention Linux backup tools or Azure solutions for Linux workloads, and provide parity documentation.
  • Consider adding a FAQ or 'Alternatives for non-Windows systems' section.
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-13 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 notable Windows bias. It assumes SQL Server VMs are running Windows, references Windows-specific tools and extensions (e.g., AzureBackupWindowsWorkload, NT Service\AzureWLBackupPluginSvc), and links to Windows-only troubleshooting scripts. There are no explicit instructions, examples, or troubleshooting guidance for Linux-based SQL Server VMs, nor mention of Linux-specific requirements or differences. All examples, agent requirements, and extension references are Windows-centric.
Recommendations
  • Explicitly state whether Linux-based SQL Server VMs are supported for Azure Backup, and if so, provide parallel instructions for Linux environments.
  • Include Linux-specific prerequisites, such as required agents, .NET versions, and extension installation steps.
  • Offer troubleshooting scripts or guidance for Linux VMs, similar to the Windows connectivity test scripts.
  • Clarify whether extensions like AzureBackupWindowsWorkload and NT Service\AzureWLBackupPluginSvc have Linux equivalents, or describe alternative mechanisms for Linux.
  • Add examples and screenshots for Linux VM configuration and backup workflows.
  • If Linux is not supported, clearly state this limitation at the beginning of the article.
Scanned: 2026-01-13 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 is heavily oriented toward Windows environments, with all examples, tools, and procedures relying on Windows-only utilities (e.g., psexec.exe, mountvol.exe, diskshadow.exe, Vssadmin, Net Share) and PowerShell commands. There are no Linux or macOS equivalents, nor any mention of how to perform these tasks on non-Windows platforms. All backup and recovery steps assume Windows file paths, Windows shares, and Windows-specific features like VSS Previous Versions. The documentation does not provide guidance for Linux or macOS users, making it difficult or impossible for them to follow the procedures.
Recommendations
  • Explicitly state that MABS is Windows-only if that is the case, or clarify platform requirements at the start of the documentation.
  • If any backup or restore operations can be performed from Linux/macOS (e.g., via SMB shares, SQL Server tools, or Azure CLI), provide equivalent examples and procedures.
  • Where possible, mention cross-platform alternatives (e.g., using Azure CLI or REST APIs for backup/restore tasks).
  • For SQL Server backup/restore, provide Linux/macOS command-line examples (e.g., using sqlcmd, Azure CLI, or other cross-platform tools).
  • If recovery of files from backup shares is possible from Linux/macOS, include instructions for mounting SMB shares and accessing backup files.
  • If the product is fundamentally Windows-only, make this clear to avoid confusion and wasted effort by non-Windows users.
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-13 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 exclusively focused on installing and using the MARS agent for Windows machines. All instructions, examples, and screenshots reference Windows-specific tools, installers (.exe), and requirements (PowerShell, .NET Framework). There is no mention of Linux or macOS support, nor any guidance for non-Windows platforms. The use of Windows terminology and tools is pervasive and unaccompanied by Linux alternatives.
Recommendations
  • Clearly state platform support at the beginning, including whether Linux/macOS are supported or not.
  • If MARS agent is Windows-only, provide links or references to equivalent backup solutions for Linux/macOS (e.g., Azure Backup for Linux, Azure VM backup extension).
  • Add a comparison table showing platform compatibility and alternative approaches for non-Windows users.
  • If partial support exists for Linux/macOS, include installation and usage instructions for those platforms.
  • Avoid using 'Windows machines' as a default term; specify platform scope where relevant.
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-13 00:00
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 application. All instructions reference the Windows GUI and do not mention any Linux or macOS equivalents, nor do they provide command-line or cross-platform alternatives. There is no guidance for managing telemetry settings outside of the Windows environment, and no mention of Powershell, but the overall approach assumes a Windows server and tools.
Recommendations
  • Clarify that MABS is a Windows-only product, if applicable, to set expectations for Linux/macOS users.
  • If telemetry settings can be managed via command-line tools or configuration files, provide instructions for those methods, which may be more accessible to non-Windows users.
  • If there are Azure Backup solutions for Linux, link to those and provide parity in telemetry management documentation.
  • Explicitly state platform requirements at the top of the article.
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-13 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 Azure Backup Server V3 RTM is heavily Windows-centric. All examples, supported workloads, and technical details focus on Windows operating systems, Windows-based applications (SQL Server, Exchange, SharePoint), and Windows-specific technologies (NTFS, VSS, Hyper-V, ReFS). Linux is mentioned only as a guest VM, with limited support (entire VM backup only, file-consistent snapshots), and there are no examples or details for Linux workloads, filesystems, or recovery scenarios. Windows tools and patterns (e.g., VSS, NTFS, Windows Management Framework) are referenced exclusively.
Recommendations
  • Add explicit documentation for Linux workloads, including supported distributions, filesystems, and backup/recovery scenarios.
  • Provide parity for item-level recovery on Linux VMs, or clearly state limitations and possible workarounds.
  • Include Linux-first or Linux-specific examples in the protection matrix, not just as an afterthought.
  • Document any Linux-specific requirements, limitations, and best practices for Azure Backup Server.
  • Reference Linux tools and backup patterns where applicable, and clarify differences in snapshot and recovery mechanisms.
Backup Offline backup by using Azure Data Box .../main/articles/backup/offline-backup-azure-data-box.md
High Priority View Details →
Scanned: 2026-01-13 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 towards Windows environments. All instructions, examples, and prerequisites are specific to Windows OS versions and Windows Server SKUs. The use of Windows PowerShell, Windows-specific tools (Control Panel, PsExec, registry editing), and references to Windows-only applications (MARS Agent, Microsoft Azure Backup application) exclude Linux and macOS users. No Linux or macOS equivalents, alternatives, or guidance are provided.
Recommendations
  • Explicitly state Windows-only support in the introduction and support matrix.
  • If possible, provide parity for Linux/macOS by documenting any supported workflows, agents, or tools for those platforms.
  • If Data Box/MARS Agent is not supported on Linux/macOS, suggest alternative Azure backup solutions for those platforms.
  • Add a section clarifying platform limitations and linking to cross-platform backup options.
  • Where PowerShell is required, note if Azure CLI or REST API alternatives exist for Linux/macOS 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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows environments. All supported platforms are Windows Server versions, and all setup, configuration, and troubleshooting instructions assume a Windows OS. Only Windows tools (e.g., PSExec, regedit, Windows command prompt, PowerShell modules) are referenced, with no mention of Linux or macOS equivalents or support. There are no examples or instructions for non-Windows systems, and the workflow is deeply integrated with Windows-specific patterns.
Recommendations
  • Clearly state if Linux/macOS are unsupported, or provide parity instructions/examples for those platforms if support is possible.
  • If DPM/MABS are Windows-only, mention alternative Azure backup solutions for Linux/macOS users.
  • Where possible, provide cross-platform tooling or note equivalent Linux/macOS commands (e.g., for mounting NFS shares, certificate management).
  • Avoid assuming the use of Windows-only utilities (like regedit, PSExec) without alternatives or explanations.
  • Add a section explicitly addressing platform support and guidance for non-Windows users.
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation focuses exclusively on backup solutions using Microsoft Azure Backup Server (MABS), System Center Data Protection Manager (DPM), and the MARS Agent—all Windows-only tools. There is no mention of Linux or macOS backup agents, nor examples or guidance for non-Windows environments. The described utilities and workflows are tailored to Windows platforms, leaving Linux/macOS users without clear instructions or parity.
Recommendations
  • Explicitly state platform support for each backup method, clarifying if Linux/macOS are unsupported.
  • If Linux backup is possible (e.g., via Azure CLI, AzCopy, or other tools), provide equivalent Linux/macOS workflows and examples.
  • Reference any Azure backup agents or third-party solutions available for Linux/macOS.
  • Include a comparison table row for OS/platform support.
  • If Windows-only, add a note to inform users and suggest alternatives for Linux/macOS.
Backup Quickstart - Bicep file VM Backup ...lob/main/articles/backup/quick-backup-vm-bicep-file.md
High Priority View Details →
Scanned: 2026-01-13 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. All deployment and cleanup instructions use Azure PowerShell, with no mention of Azure CLI or Bash alternatives. The template example is for a Windows VM only, with no Linux VM options or parameters. References to monitoring and backup jobs link to PowerShell-based guides. There is no guidance for Linux/macOS users or parity in tooling or examples.
Recommendations
  • Add Azure CLI and Bash examples for template deployment and resource cleanup.
  • Include a Linux VM option in the Bicep template, with parameters for Linux images and authentication.
  • Provide links to Linux/macOS-specific guides for backup and monitoring tasks.
  • Clearly indicate which steps are cross-platform and which are Windows-specific.
  • Present CLI/Bash examples before or alongside PowerShell examples to avoid Windows-first bias.
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-13 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 focused on Windows environments, with all examples, screenshots, and instructions referencing Windows Server, Windows clients, and Windows-specific tools (e.g., command prompt, registry editor, .exe utilities, Certlm.msc). There are no Linux or macOS equivalents provided, nor is there any mention of how to perform these tasks on non-Windows platforms. The workflow assumes the use of Windows-only utilities and patterns throughout.
Recommendations
  • Explicitly state platform requirements and limitations at the beginning of the article.
  • If Linux/macOS support is possible, provide equivalent steps, tools, and screenshots for those platforms.
  • If the workflow is Windows-only, clarify this for cross-platform administrators and suggest alternative Azure backup solutions for Linux/macOS.
  • Reference Azure CLI or REST API alternatives where possible, as these are cross-platform.
  • Add notes or links to documentation for Linux/macOS backup workflows using Azure services.
Backup Using Pre-Backup and Post-Backup Scripts ...main/articles/backup/pre-backup-post-backup-scripts.md
High Priority View Details →
Scanned: 2026-01-13 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 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, nor any mention of how to configure or run scripts in non-Windows environments.
Recommendations
  • Add explicit guidance for configuring pre/post-backup scripts on Linux/macOS systems, including file paths and permissions.
  • Provide Linux/macOS script examples (e.g., bash, sh) alongside Windows examples.
  • Clarify whether MABS supports non-Windows agents and, if so, document any differences in script configuration and execution.
  • Mention Linux equivalents for tools (e.g., using 'bash myscript.sh' instead of 'cscript myscript.vbs').
  • Include notes about file system differences and how to specify paths on Linux/macOS.
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows Missing Linux Only Explicit Windows Exclusion
Summary
The documentation page is explicitly Linux-centric, supporting SAP ASE backups only on Azure Linux VMs. Windows is listed as unsupported in the topology matrix, and there are no Windows or PowerShell examples, tools, or patterns mentioned. All example scripts and instructions are for Linux environments (bash, shell scripts, sudo). Azure CLI/PowerShell support is also stated as unavailable. This creates a strong bias against Windows users, who cannot use this solution for SAP ASE backups.
Recommendations
  • Clearly state at the top of the documentation that Windows is not supported for SAP ASE backups with Azure Backup.
  • If future support for Windows is planned, provide a roadmap or alternatives for Windows users.
  • Offer links or references to Windows-compatible backup solutions for SAP ASE, if any exist.
  • Ensure parity in documentation when/if Windows support is added, including PowerShell/Windows CLI examples and instructions.
Scanned: 2026-01-13 00:00
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 the Windows MARS agent and its console, with all agent-side instructions and screenshots referencing Windows-only tools and UI. Automation and scripting examples use PowerShell and reference Windows-specific cmdlets (Set-OBMachineSetting), with no mention of Linux or macOS equivalents. There are no instructions or guidance for Linux or macOS users, and the MARS agent itself is a Windows-only backup solution.
Recommendations
  • Explicitly state that the MARS agent is Windows-only early in the documentation, clarifying that Linux/macOS users should use other Azure backup solutions.
  • Provide links or references to Azure backup documentation for Linux and macOS, such as Azure Backup for Azure VMs or Azure Backup Server.
  • If any cross-platform alternatives exist for storing backup passphrases in Key Vault, mention them and provide examples.
  • Ensure CLI examples are not solely tied to Windows agent operations; include generic Key Vault usage where possible.
  • Add a comparison table or section outlining backup options for different OS platforms.
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-13 00:00
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 using Windows-specific modules (e.g., MSOnlineBackup) and registry paths, with no mention of Linux or macOS equivalents. All instructions and tooling are tailored for Windows environments, and there are no alternative examples or guidance for non-Windows users.
Recommendations
  • Clearly state at the beginning that the script and instructions are Windows-only and require the MARS agent, which is not available for Linux/macOS.
  • If Linux/macOS support is possible, provide equivalent scripts or command-line instructions for those platforms.
  • If Linux/macOS are not supported, explicitly mention this limitation to set user expectations.
  • Consider linking to documentation or tools for Linux-based backup solutions if relevant.
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-13 00:00
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 backup policies with the MARS agent, which is a Windows-only tool. There are no examples, instructions, or mentions of Linux/macOS equivalents or cross-platform alternatives. The content assumes the user is on Windows and familiar with PowerShell, omitting any guidance for non-Windows environments.
Recommendations
  • Include equivalent script samples for Linux/macOS environments, such as Bash or Python scripts using relevant backup tools.
  • Clarify platform requirements early in the documentation, specifying if the solution is Windows-only.
  • If cross-platform support is not available, provide links or references to backup automation solutions for Linux/macOS (e.g., rsync, cron, Azure CLI).
  • Add a section comparing Windows and Linux backup automation approaches for parity and user guidance.
Backup Transport Layer Security in Azure Backup .../blob/main/articles/backup/transport-layer-security.md
High Priority View Details →
Scanned: 2026-01-13 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 exclusively for Windows (registry edits, KB articles, .NET Framework registry keys). There are no instructions, examples, or references for enabling or verifying TLS 1.2 on Linux or macOS systems, nor any mention of cross-platform Azure Backup agents or their TLS configuration. Windows tools and patterns (registry, KB articles) are used throughout, and the only protocol negotiation reference links to Windows documentation.
Recommendations
  • Add equivalent instructions for enabling and verifying TLS 1.2 on Linux and macOS, including relevant configuration files (e.g., OpenSSL, system-wide TLS settings).
  • Provide examples for common Linux distributions (Ubuntu, CentOS, RHEL) and macOS, showing how to check and enforce TLS 1.2 support.
  • Reference cross-platform Azure Backup agents and clarify any differences in TLS configuration between platforms.
  • Include troubleshooting steps and error messages relevant to Linux/macOS environments.
  • Link to platform-neutral or Linux/macOS-specific documentation about TLS handshake and protocol negotiation.
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-13 00:00
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 SQL Server running on Windows-based Azure VMs. It references Windows-specific extensions (AzureBackupWindowsWorkload, SqlIaaSExtension), Windows service accounts (NT Service\AzureWLBackupPluginSvc), and does not mention Linux-based SQL Server VMs or provide any Linux-specific instructions or examples. All screenshots and steps assume the Windows environment, with no guidance for Linux users.
Recommendations
  • Explicitly state whether the process supports SQL Server on Linux VMs, and if not, clarify limitations.
  • If Linux SQL Server VMs are supported, add parallel instructions and screenshots for Linux environments.
  • Document any differences in required extensions, service accounts, or permissions for Linux VMs.
  • Provide troubleshooting steps and error messages relevant to Linux-based SQL Server deployments.
  • Include CLI or script-based examples (e.g., Bash, Azure CLI) for Linux users, not just portal-based workflows.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All instructions, screenshots, and examples assume the use of Windows servers and tools (Remote Desktop, DPM, Windows agent installers). There is no mention of Linux or macOS support, nor are there any examples or guidance for non-Windows platforms. The process described is not applicable to Linux systems, and the only next step offered is for backing up Windows machines.
Recommendations
  • Clarify early in the documentation that the MARS agent is Windows-only, if that is the case.
  • If Linux/macOS support exists, add equivalent upgrade instructions and examples for those platforms.
  • Provide links or references to Linux/macOS backup solutions (such as Azure Backup for Linux VMs) if MARS agent is not supported.
  • Ensure that alternative remote access methods (e.g., SSH for Linux) are mentioned where appropriate.
  • Include a comparison table or section outlining platform support and upgrade paths.
Backup Back up Azure Kubernetes Service (AKS) using Azure CLI ...p/azure-kubernetes-service-cluster-backup-using-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 a Windows bias primarily through the use of Windows-specific syntax (PowerShell backticks) in command examples, mentions Azure PowerShell as an alternative before Linux equivalents, and includes Windows-centric tools and patterns (e.g., PowerShell variable assignment, backtick line continuation). There are no explicit Linux shell (bash) examples, and the only alternative to Azure CLI is Azure PowerShell, which is Windows-focused. The documentation does not provide parity for Linux users in terms of shell syntax or tool recommendations.
Recommendations
  • Replace PowerShell-specific command syntax (such as backticks for line continuation and $variable assignment) with bash-compatible syntax (e.g., backslash for line continuation, export for variable assignment) or provide both Windows and Linux examples side by side.
  • Explicitly mention bash or Linux shell usage in examples, especially for Azure CLI commands, as Azure CLI is cross-platform.
  • Where Azure PowerShell is referenced as an alternative, also mention bash scripting or Linux-native tools if available.
  • Add a section or note clarifying cross-platform compatibility and provide links to Linux-specific documentation or guides.
  • Ensure that all command examples are tested and presented in both Windows (PowerShell) and Linux (bash) formats to improve accessibility for Linux users.
Backup Quickstart - Configure vaulted backup for Azure Data Lake Storage using ARM or Bicep template ...ata-lake-storage-backup-configure-quickstart-arm-bicep.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides only PowerShell deployment examples for both ARM and Bicep templates, with no mention of Azure CLI, Bash, or Linux-native deployment methods. This approach assumes users are familiar with PowerShell, which is more common on Windows, and does not offer parity for Linux or cross-platform users. The deployment instructions do not reference Azure CLI, Bash, or provide alternative commands for non-Windows environments.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell for both ARM and Bicep templates.
  • Explicitly mention that Azure Cloud Shell supports both PowerShell and Bash, and provide Bash/CLI instructions.
  • Include notes or links for Linux/macOS users on how to run deployments using Azure CLI.
  • Ensure that PowerShell is not presented as the only or primary method; alternate methods should be given equal prominence.
  • Where possible, provide cross-platform guidance and clarify any differences in command syntax or prerequisites.
Backup Recover data from an Azure Backup Server by using Azure Backup ...n/articles/backup/backup-azure-alternate-dpm-server.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 is heavily focused on Azure Backup Server and System Center Data Protection Manager (DPM), which are Windows-only tools. All instructions, screenshots, and terminology are specific to the Windows ecosystem, with no mention of Linux equivalents, cross-platform tools, or CLI alternatives. There are no examples or guidance for Linux-based recovery scenarios, and Windows patterns (e.g., right-click, management console) are assumed throughout.
Recommendations
  • Add explicit notes clarifying platform support and limitations, especially that Azure Backup Server and DPM are Windows-only.
  • Provide guidance or links for Linux-based backup and recovery scenarios using Azure Backup (e.g., MARS agent, Azure CLI, or third-party tools).
  • Include parity examples for Linux environments, such as command-line recovery steps or references to supported Linux backup agents.
  • Reorganize content to mention platform support up front, and offer alternative workflows for non-Windows users.
  • Where possible, use neutral terminology and avoid assuming a GUI/Windows workflow as the default.
Backup Configure Vaulted Backup for Azure Data Lake Storage using Azure portal, PowerShell, or Azure CLI ...les/backup/azure-data-lake-storage-configure-backup.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured as a primary automation method, with detailed step-by-step instructions and example cmdlets, which are inherently Windows-centric. The prerequisites for PowerShell specifically mention installation of Azure PowerShell, a tool most commonly used on Windows. The structure of the page and the zone pivots present the Azure portal (GUI, often accessed from Windows) and PowerShell before the Azure CLI, which is more cross-platform and Linux-friendly. There is no mention of Linux-specific shell usage, nor are Bash or Linux-native scripting examples provided. The CLI section does not reference Linux environments or shell integration, and the overall documentation assumes familiarity with Windows tools and patterns.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI commands, including how to run them in typical Linux environments.
  • Include notes or sections on installing and using Azure CLI and PowerShell on Linux and macOS, not just Windows.
  • Present CLI examples before PowerShell in the documentation, or at least give them equal prominence.
  • Reference Linux-native tools or scripting patterns where appropriate, such as using environment variables, jq for JSON parsing, or shell scripting for automation.
  • Clarify that Azure CLI is cross-platform and provide links to installation instructions for Linux and macOS.
  • Avoid assuming the use of Windows-only tools; mention alternatives for Linux users when discussing prerequisites and setup.