Backup

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 426-450 of 1604 flagged pages
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 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a Windows bias by exclusively referencing Windows-specific tools and patterns (such as the AzureBackupWindowsWorkload extension, NT Service accounts, and SQLIaaSExtension), and does not mention or provide guidance for Linux-based SQL Server deployments. All examples and instructions assume a Windows VM environment, with no consideration for Linux VMs or cross-platform scenarios.
Recommendations
  • Include explicit guidance and examples for backing up SQL Server databases running on Linux-based Azure VMs, if supported.
  • Clarify whether the described process and extensions are Windows-only, and provide alternative instructions or links for Linux users.
  • Mention Linux-specific requirements, limitations, or tools (such as relevant agent extensions or service accounts) where applicable.
  • Add a section comparing Windows and Linux support for SQL Server backup to Azure, including any feature gaps or differences.
  • Ensure screenshots and terminology are inclusive of both Windows and Linux environments, or clearly indicate platform specificity.
GitHub Create Pull Request
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 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation exclusively describes upgrading the MARS agent on Windows environments, referencing Windows-specific tools (Remote Desktop, DPM Console), and does not mention Linux or provide Linux-specific instructions or examples. All screenshots and steps assume Windows usage, and there is no parity for Linux systems or alternative platforms.
Recommendations
  • Clarify in the introduction whether the MARS agent is Windows-only, or explicitly state platform limitations.
  • If Linux support exists, add equivalent instructions and examples for Linux environments, including command-line steps and screenshots.
  • Mention Linux backup solutions or agents if MARS is not supported, and link to relevant documentation.
  • Avoid using Windows-specific terminology (e.g., Remote Desktop, DPM Console) without noting platform applicability.
  • Provide parity in 'Next steps' for Linux users, such as links to Linux backup agent documentation or guidance.
GitHub Create Pull Request
Backup Support matrix for Azure Data Lake Storage Vaulted Backup ...ackup/azure-data-lake-storage-backup-support-matrix.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 references configuration and management via Azure portal, PowerShell, and Azure CLI, but lists PowerShell before Azure CLI and does not mention Bash, Linux shell, or Linux-specific tools. There are no explicit Linux examples or references to Linux-native workflows, and the examples and instructions do not address Linux parity or cross-platform considerations. The documentation implicitly prioritizes Windows tools and patterns.
Recommendations
  • Explicitly mention and provide examples for Linux users, such as Bash scripts and Linux shell commands for Azure CLI.
  • List Azure CLI before PowerShell when describing cross-platform configuration steps, as Azure CLI is natively supported on both Windows and Linux.
  • Include notes or sections on Linux compatibility, such as prerequisites for running Azure CLI or PowerShell Core on Linux.
  • Add references to Linux documentation or guides for Azure Data Lake Storage backup and restore operations.
  • Ensure parity in examples and instructions for both Windows and Linux environments, including troubleshooting steps and tool installation guides.
GitHub Create Pull Request
Backup Azure Kubernetes Service (AKS) backup support matrix ...azure-kubernetes-service-cluster-backup-support-matrix.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page displays mild Windows bias by referencing Azure PowerShell and Windows-based node pools, listing PowerShell as a primary tool for backup/restore operations, and explicitly stating that the Backup Extension cannot be installed on Windows-based node pools. However, Linux is the only supported OS for the backup extension, and Ubuntu/Azure Linux are mentioned as required. There is a lack of explicit Linux CLI examples or parity in tooling recommendations, and PowerShell is listed alongside CLI and portal in 'Next steps' without clarifying platform differences.
Recommendations
  • Clarify that Azure PowerShell is primarily for Windows environments and provide equivalent Linux shell (bash) examples wherever PowerShell is mentioned.
  • In 'Next steps', list Azure CLI and Linux-native tools before PowerShell, or group them by platform to avoid Windows-first ordering.
  • Explicitly state that the backup extension is supported only on Ubuntu/Azure Linux node pools and provide guidance for users migrating from Windows node pools.
  • Add a note or section highlighting Linux command-line usage and best practices for AKS backup, including sample bash scripts or CLI workflows.
  • Ensure that all tooling recommendations (CLI, Terraform, ARM, Bicep) include Linux compatibility notes and examples.
GitHub Create Pull Request
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-10 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 Windows environments, with no mention of Linux equivalents, cross-platform tools, or command-line alternatives. There are no examples or guidance for Linux-based recovery scenarios, and Windows-centric patterns (such as right-click context menus and GUI navigation) are used throughout.
Recommendations
  • Add guidance for recovering data from Linux-based backup solutions or agents, if supported by Azure Backup.
  • Include command-line examples (e.g., using Azure CLI, REST API, or PowerShell Core on Linux) for recovery operations.
  • Mention cross-platform backup agents or tools, if available, and provide parity in documentation for Linux environments.
  • Clarify in the introduction that the documented process is specific to Windows/DPM, and link to Linux recovery documentation if available.
  • Provide screenshots or walkthroughs for non-Windows environments, or explicitly state limitations for Linux users.
GitHub Create Pull Request
Backup Back up Azure Kubernetes Service by using Azure Backup ...cles/backup/azure-kubernetes-service-cluster-backup.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 demonstrates a Windows bias by referencing Azure PowerShell as the only CLI alternative to the portal, both in the introduction and in the 'Next steps' section. There are no examples or mentions of Azure CLI, Bash, or Linux-native tools for backup configuration or management. The documentation does not provide parity for Linux users, omitting equivalent command-line instructions or references for non-Windows environments.
Recommendations
  • Add Azure CLI examples for all backup and restore operations, ensuring parity with PowerShell instructions.
  • Reference Azure CLI documentation alongside PowerShell in introductory and 'Next steps' sections.
  • Include Bash script samples for Kubernetes operations where appropriate.
  • Explicitly mention that all steps can be performed from Linux/macOS environments, not just Windows/PowerShell.
  • Ensure screenshots and UI references are not Windows-specific, or provide notes for Linux users if differences exist.
GitHub Create Pull Request
Backup About the MARS Agent ...s/blob/main/articles/backup/backup-azure-about-mars.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation for the MARS Agent is heavily Windows-centric. All backup and recovery scenarios, process descriptions, and technical details reference Windows systems, files, and tools (such as VSS and USN). There are no examples, instructions, or mentions of Linux support or equivalents, nor are Linux tools or patterns discussed. The documentation assumes the reader is working exclusively with Windows environments.
Recommendations
  • Explicitly state platform support at the beginning of the documentation (e.g., clarify if MARS Agent is Windows-only or if Linux is supported).
  • If Linux is supported, provide equivalent examples and instructions for Linux systems, including installation, configuration, and backup/recovery processes.
  • Mention Linux-specific tools or patterns (e.g., LVM snapshots, rsync, cron) where applicable.
  • If MARS Agent is not supported on Linux, suggest alternative Azure Backup solutions for Linux workloads and link to relevant documentation.
  • Ensure diagrams and tables include Linux scenarios or clearly indicate platform limitations.
GitHub Create Pull Request
Backup Troubleshoot encrypted Azure VM backup errors ...icles/backup/backup-azure-encrypted-vm-troubleshoot.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 page demonstrates a Windows bias by referencing PowerShell as the only command-line automation option for configuring permissions, without mentioning Linux equivalents such as Azure CLI or Bash. There are no examples or instructions tailored for Linux users, and Windows/PowerShell tools are mentioned first and exclusively in relevant troubleshooting steps.
Recommendations
  • Include Linux-specific instructions and examples, such as using Azure CLI or Bash scripts, alongside PowerShell steps.
  • Explicitly mention cross-platform support in troubleshooting steps, ensuring parity for both Windows and Linux VM administrators.
  • Provide links to both Windows and Linux automation documentation where relevant.
  • Review all troubleshooting steps to ensure that Linux users are not excluded from guidance and that examples are balanced between platforms.
GitHub Create Pull Request
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 a Windows bias by referencing Windows-centric backup tools (DPM, MABS, MARS) and linking to Windows Server-specific management guides. There are no examples or mentions of Linux backup agents, Linux-specific monitoring, or parity in tool coverage. Windows tools and patterns are mentioned exclusively, with no Linux equivalents or guidance provided.
Recommendations
  • Add examples and guidance for monitoring Azure Backup workloads protected by Linux machines, including references to Linux backup agents.
  • Include links to documentation for managing and monitoring Linux backup items in Recovery Services vault and Backup vault.
  • Mention Linux-specific constraints, naming conventions, and supported versions where relevant, similar to the detailed notes for Windows tools.
  • Ensure that both Windows and Linux scenarios are covered equally in all monitoring and configuration instructions.
GitHub Create Pull Request
Backup Restore Key Vault key & secret for encrypted Azure VM ...ain/articles/backup/backup-azure-restore-key-secret.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on Azure PowerShell, with all examples and instructions using PowerShell cmdlets and Windows-style file paths (e.g., C:\). There are no CLI, Bash, or Linux-native tool examples, and the workflow assumes use of Windows tools and conventions. Even the Linux VM section uses PowerShell, and there are no Linux-specific instructions or parity for non-Windows environments.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all steps, especially for Linux users.
  • Include Linux-native file paths and storage access patterns (e.g., /home/user/vmencryption_config.json).
  • Explicitly document any differences in workflow or requirements for Linux VMs, including how to perform these operations from a Linux host.
  • Provide guidance on using cross-platform tools (e.g., az CLI, REST API) for restoring keys and secrets.
  • Ensure that Linux examples are presented alongside Windows examples, not only as a note or afterthought.
GitHub Create Pull Request
Backup Troubleshoot monitoring issues for Azure Backup ...n/articles/backup/backup-azure-monitor-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows-specific tools (Task Manager, Control Panel), Windows service names, and Windows file paths. There are no examples, troubleshooting steps, or references for Linux environments or Linux agents. All instructions assume a Windows OS context.
Recommendations
  • Add equivalent troubleshooting steps for Linux environments, such as using systemctl or service commands to check and restart the agent process.
  • Include Linux file path examples for log locations.
  • Mention Linux-specific tools (e.g., top, ps, journalctl) for process and log inspection.
  • Clarify whether the Azure Backup agent is available for Linux, and if not, state this explicitly to avoid confusion.
  • Present troubleshooting steps for both Windows and Linux in parallel, or clearly separate them by OS.
GitHub Create Pull Request
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively references Microsoft Azure Backup Server (MABS), which is a Windows-only tool, and all workflows, screenshots, and terminology are centered around Windows environments (e.g., NTAuthority\System, Management Console, blades, protection groups). There are no Linux-specific instructions, examples, or mentions of Linux-compatible backup tools or patterns. The documentation implicitly assumes the user is operating in a Windows environment, with no consideration for Linux-based SQL Server deployments or backup workflows.
Recommendations
  • Explicitly state that MABS is Windows-only and clarify platform requirements at the beginning of the article.
  • Provide guidance or links for Linux-based SQL Server backup on Azure Stack, such as using Azure Backup with Linux agents or alternative backup solutions.
  • Include examples or references for Linux authentication and permissions (e.g., service accounts, file system permissions) where appropriate.
  • Add parity in backup and recovery workflows for SQL Server running on Linux, if supported, or direct users to relevant documentation.
  • Mention cross-platform alternatives or Azure-native backup options that support both Windows and Linux SQL Server workloads.
GitHub Create Pull Request
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-10 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, referencing Windows Server Backup, Windows Recovery Environment (WinRE), and Windows-specific file paths and tools throughout. All examples, workflows, and recovery steps are tailored to Windows systems, with no mention of Linux or cross-platform alternatives. PowerShell cmdlets are referenced for configuration, and Windows-centric terminology and procedures are used exclusively.
Recommendations
  • Clearly state platform support at the beginning, including whether Linux is supported for system state and BMR protection.
  • If Linux is supported, provide equivalent workflows, examples, and recovery steps for Linux systems, referencing appropriate Linux backup and recovery tools (e.g., rsync, dd, tar, or native Azure Backup Linux agent).
  • Include Linux file paths and configuration file locations where relevant.
  • Offer CLI examples using Bash or other Linux shells, not just PowerShell.
  • If Linux is not supported, explicitly mention this limitation to avoid confusion for cross-platform administrators.
GitHub Create Pull Request
Backup Troubleshoot backup errors with Azure VMs .../main/articles/backup/backup-azure-vms-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-10 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: troubleshooting steps and examples frequently reference Windows-specific tools (Event Viewer, Services.msc, Registry Editor, command prompt commands like net start/stop, vssadmin, icacls, msdtc, regedit, MSIEXEC), and PowerShell is often mentioned as the automation method for restore operations. Windows troubleshooting patterns and registry modifications are described in detail, while Linux equivalents are either briefly mentioned or omitted. Linux-specific troubleshooting steps are present but less detailed, and often appear after Windows instructions. Some error resolutions and examples are only provided for Windows, with no Linux parity.
Recommendations
  • Provide Linux equivalents for all Windows troubleshooting steps (e.g., commands for checking agent status, service management, log inspection, and permissions).
  • Include Linux-specific examples and error messages where Windows examples are given (e.g., show how to check for backup extension failures in Linux logs, how to manage services, and how to handle file system permissions).
  • Offer Bash or CLI examples alongside PowerShell for automation and restore operations.
  • Ensure that Linux troubleshooting steps are as detailed as Windows steps, including step-by-step instructions for common issues.
  • Where Windows registry modifications are described, clarify whether similar configuration changes are needed or possible on Linux, and provide guidance if so.
  • Balance the order of presentation so that Linux and Windows instructions are given equal prominence, or group OS-specific instructions clearly.
GitHub Create Pull Request
Backup Troubleshoot Azure Backup failures caused by agent or extension issues ...up-azure-troubleshoot-vm-backup-fails-snapshot-timeout.md
High Priority View Details →
Scanned: 2026-01-10 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 troubleshooting steps and tools (e.g., services.msc, Event Viewer, Control Panel, .NET, regsvr32.exe, Visual C++ Redistributable, AppLocker) are described in detail, often with screenshots, while Linux equivalents are either briefly mentioned or omitted. Windows instructions and examples are frequently presented before Linux ones, and PowerShell is referenced as a primary automation tool. Linux troubleshooting steps lack comparable detail, examples, and visual aids. Some sections (e.g., antivirus exclusions, extension troubleshooting, backup job cancellation) only provide Windows paths, tools, or commands, with no Linux alternatives.
Recommendations
  • Provide Linux-specific troubleshooting steps with equal detail, including example commands, log file locations, and configuration file edits.
  • Include screenshots or terminal output examples for Linux procedures, similar to those provided for Windows.
  • Mention Linux tools (e.g., systemctl, journalctl, log file paths) and automation options (e.g., Azure CLI, shell scripts) alongside PowerShell.
  • List Linux instructions before or alongside Windows instructions in each troubleshooting section to avoid implicit prioritization.
  • For antivirus and application control solutions, specify Linux equivalents (e.g., SELinux, AppArmor, Linux antivirus paths) and how to configure exclusions.
  • When referencing extension or agent installation, provide links and steps for both Windows and Linux, including manual installation and update procedures.
  • Ensure parity in error resolution steps, such as backup job cancellation, by including Linux-compatible commands and tools.
GitHub Create Pull Request
Backup Release notes for Microsoft Azure Backup Server v3 ...b/main/articles/backup/backup-mabs-release-notes-v3.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation for Microsoft Azure Backup Server v3 is heavily focused on Windows environments. All examples, tools, and procedures reference Windows-specific technologies (e.g., SQL Server Management Studio, SQL Server Reporting Services, Windows file paths, and Windows Server versions). There are no mentions of Linux equivalents, nor are any Linux-specific issues, workarounds, or instructions provided. The documentation assumes the user is operating in a Windows ecosystem.
Recommendations
  • Include information on whether MABS supports Linux workloads, and if so, document known issues and workarounds for Linux environments.
  • Provide examples and instructions for backup and recovery operations on Linux servers, if supported.
  • Mention Linux-compatible tools or alternatives to Windows-only utilities like SSMS and SSRS, or clarify if these steps are Windows-exclusive.
  • Explicitly state platform limitations (e.g., if MABS is Windows-only) to help users understand the scope.
  • If Linux is not supported, consider adding a note for cross-platform users and suggest alternative Azure backup solutions for Linux.
GitHub Create Pull Request
Backup Back up a SharePoint farm on Azure Stack using Microsoft Azure Backup Server .../articles/backup/backup-mabs-sharepoint-azure-stack.md
High Priority View Details →
Scanned: 2026-01-10 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 exclusive references to Windows tools (such as ConfigureSharePoint.exe, Registry Editor, CMD commands, and Windows-specific file paths), and no mention of Linux equivalents or cross-platform alternatives. All instructions, examples, and screenshots assume a Windows OS, and there are no examples or guidance for Linux-based deployments or administration. The documentation assumes familiarity with Windows administrative concepts and tools, and does not address Linux scenarios or provide parity for Linux users.
Recommendations
  • Explicitly state OS requirements and limitations at the beginning of the documentation.
  • If MABS and SharePoint farm protection are Windows-only, clarify this and provide links to Linux-compatible backup solutions for SharePoint or similar workloads.
  • Where possible, mention whether any steps (such as agent installation, backup configuration, or monitoring) can be performed from Linux or via cross-platform tools (e.g., REST APIs, Azure CLI).
  • Provide parity examples for Linux environments if supported, or explain why Linux is unsupported.
  • Include notes or alternative guidance for administrators managing hybrid or Linux-based infrastructure.
  • Reference any Azure-native backup solutions that work with Linux workloads, if applicable.
GitHub Create Pull Request
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-10 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 towards Windows and PowerShell by providing only Azure PowerShell deployment examples and referencing PowerShell for backup management tasks. There are no explicit Linux or Azure CLI deployment examples, and PowerShell is mentioned before CLI and REST API options in the 'Next steps' section. This may make it less accessible for Linux users or those who prefer cross-platform tools.
Recommendations
  • Add Azure CLI deployment instructions alongside PowerShell, with full example commands.
  • Explicitly mention cross-platform compatibility for deployment methods, including Bash and Cloud Shell.
  • Reorder 'Next steps' to present Azure CLI and REST API options before or alongside PowerShell.
  • Include notes or links for Linux/macOS users on how to perform the same tasks using CLI.
  • Ensure all referenced management tasks (track, restore, manage) have CLI and REST API documentation links and examples.
GitHub Create Pull Request
Backup Using Pre-Backup and Post-Backup Scripts ...main/articles/backup/pre-backup-post-backup-scripts.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page is heavily oriented toward Windows environments. All examples and instructions reference Windows file paths, Windows-specific application naming conventions (e.g., Drive: notation, Exchange, SQL Server, SharePoint), and Windows folder structures. There are no examples or guidance for Linux systems, nor any mention of Linux-compatible scripting or file paths. The use of cscript and VBScripts further reinforces the Windows bias.
Recommendations
  • Add explicit instructions and examples for configuring pre-backup and post-backup scripts on Linux-based protected computers, including Linux file paths and script types (e.g., Bash, Python).
  • Clarify whether MABS supports Linux agents and, if so, provide parity in documentation for Linux environments.
  • Include examples using Linux tools and scripting patterns, such as shell scripts (.sh), and demonstrate how to specify these in ScriptingConfig.xml.
  • Mention Linux-specific permissions and best practices for script security (e.g., chmod, chown).
  • If MABS is Windows-only, state this clearly at the beginning of the documentation to avoid confusion for cross-platform users.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Files using Azure Terraform ...ackup/quick-backup-azure-files-vault-tier-terraform.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias by referencing Azure PowerShell and Azure CLI together, but clarifies that only Azure CLI is supported for Terraform authentication. However, it mentions Azure PowerShell repeatedly in restore and management steps, and does not provide any Linux-specific guidance or examples (such as Bash, shell scripting, or Linux-native tools). The troubleshooting and next steps sections list PowerShell before CLI, and do not mention Linux-specific environments or considerations.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and provide example commands for both Windows (PowerShell) and Linux (Bash).
  • Add Linux/Bash-specific authentication and usage instructions, especially for logging in and running Terraform.
  • In 'Next steps', alternate the order of PowerShell and CLI, or group CLI and Bash together to emphasize cross-platform support.
  • Include troubleshooting tips for Linux environments (e.g., common issues with Bash, environment variables, file permissions).
  • Avoid referencing PowerShell as the default or primary tool unless it is truly required; clarify when CLI is preferred for cross-platform use.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for an Azure Kubernetes Service (AKS) cluster using Azure Backup via Azure Resource Manager ...ob/main/articles/backup/quick-kubernetes-backup-arm.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 page demonstrates a Windows bias by providing only PowerShell deployment instructions for the ARM template, with no equivalent Bash, Azure CLI, or Linux shell example. The prerequisites and deployment steps reference PowerShell and Windows-centric tooling first and exclusively, omitting Linux-native workflows and commands. This may hinder Linux users or those preferring cross-platform tools.
Recommendations
  • Add Azure CLI and Bash examples for deploying the ARM template, alongside the PowerShell script.
  • Explicitly mention that both PowerShell and Azure CLI are cross-platform, but provide instructions for both environments.
  • Include guidance for Linux and macOS users, such as using Bash or zsh shells.
  • Reorder or parallelize instructions so that Windows and Linux options are presented together, avoiding Windows-first presentation.
  • Reference installation steps for Azure CLI and Bicep on Linux/macOS, not just PowerShell.
GitHub Create Pull Request
Backup SAP ASE Backup support matrix .../main/articles/backup/sap-ase-backup-support-matrix.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows Missing Linux Only Explicit Windows Exclusion
Summary
The documentation page exhibits a strong Linux bias, with support and examples exclusively for SAP ASE backups on Azure Linux VMs. Windows is explicitly listed as unsupported, and there are no Windows or PowerShell examples, tools, or instructions. All scripts and operational patterns are Linux-centric (bash, shell scripts, sudo), and Azure CLI/PowerShell support is noted as unavailable.
Recommendations
  • If Windows support is planned, add equivalent instructions, examples, and supported scenarios for Windows VMs, including PowerShell and Windows-native tools.
  • If Windows support is not planned, clarify this in the introduction and throughout the documentation to set user expectations.
  • Consider providing a rationale for Linux-only support, and link to any Windows alternatives or related documentation for users seeking Windows backup solutions.
  • Monitor user feedback for requests regarding Windows support and update documentation accordingly if support changes.
GitHub Create Pull Request
Backup Quickstart: Back up a virtual machine in Azure with Terraform ...blob/main/articles/backup/quick-backup-vm-terraform.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively demonstrates backing up a Windows virtual machine in Azure using Terraform, with no mention or example of Linux VM backup. The description, checklist, and verification steps all focus on Windows VMs, and the 'Next steps' section links only to Windows VM articles. There is no parity for Linux VM scenarios, and the documentation does not provide guidance or code samples for Linux users.
Recommendations
  • Add parallel instructions and Terraform code samples for creating and backing up a Linux VM in Azure.
  • Update the checklist and verification steps to include both Windows and Linux VM scenarios.
  • Provide links to articles and resources for Azure Linux VMs in the 'Next steps' section.
  • Clarify in the introduction that the process applies to both Windows and Linux VMs, or specify if there are differences.
  • Ensure that environment variable and CLI usage examples are applicable to both Windows and Linux environments.
GitHub Create Pull Request
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-10 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 versions are listed as supported operating systems, with Linux explicitly stated as unsupported. Backup configuration is only available via the Azure portal or PowerShell, with no CLI or Linux-native tooling support. All examples, guidance, and limitations are framed around Windows and Windows-specific tools, with no parity or alternatives for Linux users.
Recommendations
  • Clearly indicate future plans or timelines for Linux support, if any.
  • Provide equivalent Linux support or alternatives, such as support for SQL Server on Linux VMs.
  • Include Azure CLI or other cross-platform tooling examples for backup configuration and management.
  • Add documentation sections that address Linux environments, even if only to clarify limitations and suggest workarounds.
  • Ensure that any Windows-specific instructions (e.g., PowerShell) are accompanied by Linux-compatible alternatives where possible.
GitHub Create Pull Request
Backup Back up and restore Active Directory using Azure Backup ...ain/articles/backup/active-directory-backup-restore.md
High Priority View Details →
Scanned: 2026-01-10 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 is heavily focused on Windows environments, specifically Windows Server domain controllers. All examples, scripts, and tools referenced (e.g., PowerShell, ntdsutil.exe, DSRM) are Windows-specific. There are no Linux equivalents or examples, nor is there mention of backing up/restoring Samba-based or Linux-hosted Active Directory-compatible services. The guidance assumes the use of Windows tools and patterns throughout.
Recommendations
  • Add examples and guidance for Linux-based Active Directory-compatible domain controllers (e.g., Samba AD DC).
  • Include backup and restore procedures using Linux tools and command-line utilities where applicable.
  • Provide parity in scripting examples (e.g., bash scripts, Linux CLI commands) alongside PowerShell.
  • Clarify which instructions are Windows-specific and offer alternative steps for Linux environments.
  • Reference cross-platform backup tools or Azure Backup support for Linux VMs hosting AD-compatible services.
GitHub Create Pull Request
← Previous Page 18 of 65 Next →