Backup

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 401-425 of 520 flagged pages
Backup Support matrix for Azure VM backups ...lob/main/articles/backup/backup-support-matrix-iaas.md
Medium 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 demonstrates a moderate Windows bias. Windows scenarios, tools, and agents (such as MARS, DPM, MABS, and PowerShell) are described in greater detail and often appear first. Windows-specific backup and restore options are more comprehensive, with Linux support frequently noted as 'not supported' for agents and backup servers. Restore instructions and examples reference PowerShell and Windows tooling, with Linux equivalents missing or less detailed. Some features (e.g., file-level restore, backup agents) are unavailable for Linux, and workarounds or alternatives are not always provided.
Recommendations
  • Provide Linux CLI and script examples alongside PowerShell instructions for backup and restore operations.
  • Expand documentation for Linux scenarios, including supported distributions, limitations, and troubleshooting steps.
  • Clarify parity between Windows and Linux for each backup/restore method, and explicitly note when a feature is Windows-only.
  • Where features are not supported for Linux, suggest alternative approaches or link to roadmap/feature requests.
  • Reorder sections to present Windows and Linux support side-by-side, rather than Windows-first.
  • Include more details on agentless backup and restore for Linux, and highlight any supported third-party tools.
GitHub Create Pull Request
Backup Tutorial - Configure vaulted backup for Azure Blobs using Azure Backup ...main/articles/backup/blob-backup-configure-tutorial.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page references Azure PowerShell as a primary method for restoring Azure Blobs, listing it before Azure CLI and REST API. This ordering and emphasis may suggest a Windows-centric approach, as PowerShell is traditionally associated with Windows environments. There are no explicit Linux/macOS examples or guidance, and no mention of platform-specific considerations for CLI or REST API usage.
Recommendations
  • Provide explicit examples for both Azure CLI and PowerShell, ensuring parity in detail and visibility.
  • List cross-platform tools (Azure CLI, REST API) before Windows-centric tools (PowerShell) to avoid implying preference.
  • Add notes or sections clarifying that Azure CLI and REST API are fully supported on Linux/macOS, and provide any necessary setup instructions.
  • If PowerShell is used, mention that PowerShell Core is available cross-platform, and provide installation guidance for Linux/macOS users.
GitHub Create Pull Request
Backup Azure Backup support matrix ...ocs/blob/main/articles/backup/backup-support-matrix.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation page for Azure Backup support matrix demonstrates a moderate Windows bias. Windows-centric backup tools (MARS agent, DPM, MABS) are described in detail, with Windows scenarios and features listed first and more extensively. Linux support is frequently described in terms of limitations or as 'not supported', and Linux backup options are less detailed and often require workarounds (e.g., custom scripts for app-consistent backups). There are no Linux-specific examples or guidance for on-premises direct backup, and Windows tools are referenced exclusively for several critical backup scenarios.
Recommendations
  • Add Linux-specific examples and guidance for backup scenarios, especially for on-premises machines.
  • Provide parity in feature tables, listing Linux options alongside Windows, not only as limitations.
  • Include alternative Linux backup tools or workflows where direct support is unavailable, or link to recommended third-party solutions.
  • Reorder tables and sections to present Windows and Linux options equally, rather than listing Windows first.
  • Clarify any workarounds or best practices for Linux users, such as using custom scripts for app-consistent backups.
GitHub Create Pull Request
Backup Guidance and best practices ...s/blob/main/articles/backup/guidance-best-practices.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While it covers Azure Backup concepts broadly and mentions automation channels like PowerShell, CLI, ARM templates, and REST APIs, there is a notable tendency to reference PowerShell procedures and Windows-centric tools first (or exclusively) in automation and troubleshooting sections. Examples and guidance for Linux/macOS users (such as Bash, Azure CLI, or cross-platform scripting) are missing or not prioritized. The use of PowerShell is highlighted for auto-retry scenarios, and there are no explicit Linux or macOS command examples or references to their tooling. This could create friction for non-Windows users, especially in automation and scripting contexts.
Recommendations
  • Add explicit Azure CLI and Bash examples alongside PowerShell for automation tasks, especially in sections discussing auto-retry and scripting.
  • Ensure that references to automation channels (PowerShell, CLI, ARM, REST) provide parity in example coverage and ordering (e.g., CLI before or alongside PowerShell).
  • Include notes or links for Linux/macOS users on how to perform equivalent tasks using their preferred tools.
  • When referencing videos or external guides, clarify if the procedures are cross-platform or provide alternative instructions for Linux/macOS.
  • Review all sections mentioning scripting or automation to ensure Linux/macOS users are not left without guidance.
GitHub Create Pull Request
Backup Manage Backup vaults ...-docs/blob/main/articles/backup/manage-backup-vault.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation references PowerShell as a method for moving Backup vaults, but does not provide equivalent Linux/macOS shell (e.g., Bash/Azure CLI) examples or instructions. The mention of PowerShell precedes CLI, and no explicit Bash or cross-platform CLI commands are shown. This creates friction for Linux/macOS users who may not use PowerShell.
Recommendations
  • Provide explicit Azure CLI (az) command examples for all operations currently shown with PowerShell.
  • Ensure that CLI instructions are shown before or alongside PowerShell, with clear notes on cross-platform compatibility.
  • Add notes or links to Bash scripting examples for common tasks, especially for move operations.
  • Clarify that Azure CLI is fully supported on Linux/macOS and provide installation links if relevant.
GitHub Create Pull Request
Backup MABS (Azure Backup Server) V3 UR1 protection matrix ...kup/microsoft-azure-backup-server-protection-v3-ur1.md
Medium 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 for Azure Backup Server (MABS) V3 UR1 protection matrix exhibits a notable Windows bias. Windows workloads and tools are described in detail, with extensive coverage of Windows Server, NTFS, VSS, and related features. Windows examples and scenarios are presented first and in greater depth, while Linux support is limited to a single section with minimal detail. Linux backup is only supported as a guest VM, with no mention of agent-based or file-level Linux backup, and recovery options for Linux are restricted to entire VM restores. Windows-specific tools and patterns (NTFS, VSS, Windows Management Framework) are referenced throughout, with no Linux equivalents or alternatives provided.
Recommendations
  • Provide more detailed Linux backup and recovery scenarios, including agent-based or file-level backup for Linux workloads.
  • Include Linux-specific examples and instructions alongside Windows examples, not only as VM guests.
  • Mention Linux file systems and snapshot technologies (e.g., ext4, XFS, LVM snapshots) where relevant.
  • Clarify limitations and alternatives for Linux users, and link to Linux backup best practices.
  • Ensure parity in documentation structure and depth between Windows and Linux sections.
GitHub Create Pull Request
Backup Create and use private endpoints for Azure Backup ...re-docs/blob/main/articles/backup/private-endpoints.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias, primarily through the exclusive use of PowerShell and Windows-centric tools (e.g., armclient, .ps1 scripts, Azure PowerShell) for automation and scripting. All code samples and automation instructions are provided in PowerShell, with no Bash, Azure CLI, or Linux/macOS alternatives. Instructions for uploading scripts reference the PowerShell window in Cloud Shell, and file paths use Windows conventions. There are no explicit Linux or macOS examples, and Windows tools/patterns are mentioned first and exclusively throughout critical sections.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell scripts and automation steps.
  • Include instructions for running scripts on Linux/macOS, such as using Azure CLI, Bash, or Python.
  • Use platform-neutral file path examples or clarify how to adapt them for Linux/macOS.
  • Reference the Bash shell in Azure Cloud Shell alongside PowerShell.
  • Explicitly state cross-platform compatibility for scripts and tools, or provide alternatives where necessary.
GitHub Create Pull Request
Backup Quickstart: Configure an Azure Kubernetes Services cluster backup ...ure-docs/blob/main/articles/backup/quick-backup-aks.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses Azure Portal GUI instructions and screenshots, which are platform-agnostic but typically more familiar to Windows users. There are no command-line examples (e.g., Azure CLI, kubectl) for configuring backup, which would benefit Linux/macOS users. The CLI is only mentioned as a next step for restore, not for configuration.
Recommendations
  • Add Azure CLI and/or kubectl command examples for configuring AKS backup, alongside portal instructions.
  • Explicitly state that the portal is accessible from any OS/browser to clarify platform neutrality.
  • Provide links to Linux/macOS-specific guidance or troubleshooting if relevant.
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
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing only Azure PowerShell examples for deploying the ARM template and tracking/restoring backups. There are no Azure CLI or Bash examples for Linux/macOS users, and PowerShell is mentioned before other cross-platform tools in the 'Next steps' section. This creates friction for non-Windows users who may prefer or require CLI/Bash-based workflows.
Recommendations
  • Add Azure CLI and Bash examples for deploying ARM templates, tracking backup jobs, and restoring files.
  • Ensure that cross-platform tools (Azure CLI, REST API) are mentioned alongside or before PowerShell in relevant sections.
  • Explicitly state that all deployment and management tasks can be performed from Linux/macOS using Azure CLI or REST API.
  • Provide links to Azure CLI documentation and examples in the 'Next steps' section.
  • Consider a table or side-by-side code blocks for PowerShell and CLI/Bash to improve parity.
GitHub Create Pull Request
Backup Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Server with an Azure Resource Manager template .../backup/quick-backup-postgresql-flexible-server-arm.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell deployment instructions and referencing Azure PowerShell for restore operations. There are no examples or guidance for deploying the ARM template using Azure CLI, Bash, or other cross-platform tools, which may hinder Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI deployment instructions alongside the PowerShell example.
  • Include Bash script examples for template deployment.
  • Reference restore documentation for Azure CLI and other cross-platform tools, not just PowerShell.
  • Explicitly state that the ARM template can be deployed from any OS and provide links to cross-platform tooling.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Files using Azure Bicep ...es/backup/quick-backup-azure-files-vault-tier-bicep.md
Medium 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 demonstrates a notable Windows bias: PowerShell is the only deployment example provided, and the prerequisites specifically call out Azure PowerShell installation. There are no Azure CLI or Bash examples for deploying the Bicep template, and instructions for using the Azure Cloud Shell assume PowerShell usage. Linux/macOS users are left without direct guidance, despite Azure CLI and Bash being fully supported in Cloud Shell and on their platforms.
Recommendations
  • Add Azure CLI and Bash deployment examples alongside PowerShell, especially for the Bicep template deployment.
  • Update the prerequisites to mention Azure CLI as an alternative to Azure PowerShell.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
  • Ensure that links to management and restore operations include parity for Azure CLI and REST API, not just PowerShell.
GitHub Create Pull Request
Backup Quick start - Back up Azure Database for PostgreSQL server ...cles/backup/quick-backup-postgresql-database-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. PowerShell is referenced multiple times as the primary method for granting privileges to database users, with Linux alternatives (PG admin or PSQL tool) mentioned only as an afterthought. No explicit Linux/macOS command-line examples are provided, and the workflow assumes familiarity with Windows-centric tools and patterns.
Recommendations
  • Provide explicit Linux/macOS command-line examples using psql and/or bash scripts for privilege assignment and other tasks.
  • Mention Linux tools (e.g., psql, bash) before or alongside PowerShell, rather than only as alternatives.
  • Include screenshots or walkthroughs for Linux/macOS environments where applicable.
  • Clarify that all steps can be performed on Linux/macOS and provide parity in instructions.
GitHub Create Pull Request
Backup Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Servers with a Bicep file ...ackup/quick-backup-postgresql-flexible-server-bicep.md
Medium 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 demonstrates a strong Windows bias by exclusively providing PowerShell deployment instructions, referencing PowerShell modules, and omitting Azure CLI or Bash examples. The guidance assumes use of a Windows shell and does not mention Linux/macOS workflows or tools, creating friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI deployment instructions for the Bicep template, suitable for Bash or other shells on Linux/macOS.
  • Include notes or sections on how to run Bicep deployments from Linux/macOS terminals.
  • Reference both PowerShell and CLI tools in prerequisites, with links to installation guides for each platform.
  • Present examples for both PowerShell and CLI side-by-side or in separate tabs, ensuring parity.
  • Avoid language that assumes right-click/paste workflows specific to Windows shells.
GitHub Create Pull Request
Backup Quickstart - Create a backup policy for Azure Database for PostgreSQL - Flexible Server using Azure CLI .../backup/quick-backup-postgresql-flexible-server-cli.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily by referencing PowerShell objects as the default for backup policy manipulation and using Windows-style file paths (e.g., .\OSSPolicy.json) in CLI examples. The explanation of modifying policy templates emphasizes PowerShell's object-based workflow before describing the CLI's file-based approach, implicitly prioritizing Windows tooling and patterns. No explicit Linux/macOS examples or file path conventions are provided, and the CLI examples use Windows path separators throughout.
Recommendations
  • Add Linux/macOS-specific examples, including file path conventions (e.g., ./OSSPolicy.json instead of .\OSSPolicy.json).
  • Clarify that CLI commands work cross-platform and provide notes or examples for Linux/macOS users.
  • Avoid referencing PowerShell as the 'default' unless parity is established; instead, present CLI and PowerShell approaches equally.
  • Include a table or section comparing PowerShell and CLI workflows for both Windows and Linux/macOS environments.
  • Explicitly state that all CLI commands are supported on Linux/macOS and provide troubleshooting tips for non-Windows users.
GitHub Create Pull Request
Backup Quickstart: Back up a virtual machine in Azure with Terraform ...blob/main/articles/backup/quick-backup-vm-terraform.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively demonstrates how to back up a Windows virtual machine in Azure using Terraform. All examples, resource creation steps, and verification commands reference Windows VMs only, with no mention of Linux VM equivalents or how to adapt the process for Linux. The article title, description, and next steps reinforce a Windows-centric approach, potentially excluding Linux/macOS users who wish to back up non-Windows VMs.
Recommendations
  • Add parallel instructions and Terraform code samples for creating and backing up a Linux VM (e.g., using azurerm_linux_virtual_machine).
  • Clarify in the introduction that the process applies to both Windows and Linux VMs, or provide links to Linux VM backup guides.
  • Include verification and backup commands for Linux VMs, noting any differences in Azure CLI usage or resource naming.
  • Update the 'Next steps' section to reference articles about Azure Linux VMs as well.
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
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing Azure PowerShell deployment instructions, with no equivalent Azure CLI, Bash, or Linux/macOS shell examples. The prerequisites and deployment steps focus on PowerShell, which is most commonly used on Windows, and do not mention or show how to perform the same actions on Linux or macOS platforms. This creates friction for non-Windows users, who must seek out or adapt instructions themselves.
Recommendations
  • Add Azure CLI and Bash examples for template deployment, shown alongside or before PowerShell.
  • Explicitly mention that deployment can be performed from Linux/macOS and provide steps for those platforms.
  • In the prerequisites, include installation instructions for Azure CLI and note cross-platform compatibility.
  • Ensure all critical steps (deployment, restore, management) have CLI and Bash equivalents, not just PowerShell.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for an Azure Kubernetes Service (AKS) cluster using Azure Backup via Azure Bicep .../main/articles/backup/quick-kubernetes-backup-bicep.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing only Azure PowerShell deployment instructions, with no equivalent Azure CLI or Bash example for Linux/macOS users. The PowerShell script is presented as the sole method for deploying the Bicep template, and Windows-specific interaction patterns (e.g., right-click to paste in the shell window) are mentioned. Linux tools and workflows are absent from the deployment section.
Recommendations
  • Add Azure CLI and Bash examples for deploying the Bicep template, ensuring Linux/macOS users have clear, platform-appropriate instructions.
  • Present deployment options for both Windows (PowerShell) and Linux/macOS (CLI/Bash) side-by-side or in parallel sections.
  • Avoid Windows-specific interaction instructions (such as right-click to paste) or provide equivalent instructions for Linux/macOS terminals.
  • Explicitly state that both PowerShell and CLI can be used, and link to relevant cross-platform installation guides.
GitHub Create Pull Request
Backup Restore VMware virtual machines using Azure Backup Server .../articles/backup/restore-azure-backup-server-vmware.md
Medium 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 demonstrates a Windows bias by focusing exclusively on Windows Server VMs for individual file recovery (ILR), referencing Windows-specific features (e.g., registry key modification), and omitting Linux/macOS examples or guidance. All screenshots and instructions are based on the MABS Administrator Console, which is a Windows application, and there is no mention of Linux VM file recovery or alternative tools for non-Windows environments.
Recommendations
  • Explicitly state whether individual file recovery (ILR) is supported for Linux VMs, and if not, provide alternative guidance or workarounds for Linux users.
  • Include examples or notes for restoring files from Linux VMs, such as mounting VMDK files on a Linux system or using third-party tools.
  • Clarify if the MABS Administrator Console is available or accessible from non-Windows platforms, and suggest remote management options for Linux/macOS users.
  • Where registry modifications are required, offer equivalent configuration steps for Linux environments if applicable, or note the limitation.
  • Add troubleshooting and recovery scenarios for Linux VMs to improve parity.
GitHub Create Pull Request
Backup Restore encrypted Azure VMs ...les/backup/restore-azure-encrypted-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell-based example for creating a VM from restored disks but does not offer an equivalent CLI or Linux-specific example. The OS disk swap link is Windows-specific, and Windows terminology or links appear before Linux equivalents. Linux instructions are minimal and relegated to a separate step, lacking detailed guidance or command-line examples.
Recommendations
  • Add Azure CLI and/or Bash examples for creating a VM from restored disks, alongside the PowerShell example.
  • Provide explicit instructions and links for swapping OS disks on Linux VMs, not just Windows.
  • Ensure Linux and Windows procedures are presented with equal detail and prominence.
  • Include references to Linux-specific documentation and troubleshooting guides where relevant.
GitHub Create Pull Request
Backup Restore SQL server databases in Azure VMs with REST API .../main/articles/backup/restore-azure-sql-vm-rest-api.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is focused exclusively on restoring SQL Server databases in Azure VMs using the REST API, but all examples and references assume Windows-based SQL Server instances. Paths in request bodies use Windows-style (e.g., C:\SQLfiles\Default.ldf), and there is no mention of Linux-based SQL Server VMs or their directory conventions. No Linux/macOS-specific guidance or examples are provided, and Windows patterns (such as drive letters and backslashes) are used throughout.
Recommendations
  • Add explicit guidance for restoring SQL Server databases on Linux-based Azure VMs, including differences in file paths, directory structures, and any REST API nuances.
  • Provide example request bodies using Linux-style paths (e.g., /var/opt/mssql/data/Default.ldf) alongside Windows examples.
  • Clarify whether the REST API supports both Windows and Linux SQL Server VMs, and document any limitations or required settings for Linux.
  • Include a note or section on how to adapt the process for Linux/macOS users, especially for file system operations and alternate directory mappings.
  • Ensure parity in troubleshooting and next steps for both Windows and Linux environments.
GitHub Create Pull Request
Backup Restore SQL Server databases on an Azure VM .../main/articles/backup/restore-sql-database-azure-vm.md
Medium 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 page exhibits a notable Windows bias. It references Windows-specific tools (e.g., PsExec, NT AUTHORITY\SYSTEM), assumes Windows-style file paths (e.g., C:\Program Files), and provides instructions and examples that are only applicable to Windows environments. There are no Linux or macOS-specific instructions, nor are alternative commands or patterns for those platforms mentioned. The use of Windows terminology and tools occurs without any mention of Linux equivalents or cross-platform considerations.
Recommendations
  • Add Linux-specific instructions for mounting Azure File Shares, including required permissions and example commands (e.g., using mount.cifs and setting file permissions).
  • Provide examples for restoring SQL Server databases on Linux-based Azure VMs, including file paths and service management commands (e.g., systemctl for SQL Server Agent).
  • Mention Linux equivalents for Windows tools (e.g., alternatives to PsExec for privilege escalation, such as sudo).
  • Include notes or sections clarifying differences in file system paths, user accounts, and service management between Windows and Linux.
  • Ensure that all example commands and screenshots are available for both Windows and Linux environments, or explicitly state platform limitations.
GitHub Create Pull Request
Backup Restore SAP HANA database instances on Azure VMs ...articles/backup/sap-hana-database-instances-restore.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses on restoring SAP HANA database instances on Azure VMs but demonstrates a Windows bias by referencing the Azure portal UI and mentioning PowerShell/CLI scripts only in passing, without providing explicit Linux or bash examples. The workflow and screenshots are tailored to the Azure portal, which is most commonly used on Windows, and there is no mention of Linux-specific commands, tools, or procedures for mounting disks or restoring databases. The only reference to scripting is generic ('PowerShell or CLI script'), with no concrete Linux CLI or bash instructions.
Recommendations
  • Provide explicit Linux/bash command examples for disk attachment, mounting, and permission assignment.
  • Include screenshots or instructions for using Azure CLI on Linux/macOS, not just the Azure portal UI.
  • Clarify any OS-specific steps, especially for mounting disks and running preregistration scripts.
  • Add a section or callouts for Linux users, detailing any differences or additional steps required.
  • Ensure parity in scripting examples: if PowerShell is mentioned, also show equivalent bash/Azure CLI commands.
GitHub Create Pull Request
Backup Script Sample - Disable Soft delete for File Share using ARM API .../backup/scripts/disable-soft-delete-for-file-shares.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides command-line examples using armclient with Windows-style path separators (e.g., .\rqbody-disableSoftDelete.json), but does not mention or show Linux/macOS equivalents. There is no guidance on running armclient on Linux/macOS, nor are examples provided using Linux shell syntax. This may cause confusion or friction for non-Windows users.
Recommendations
  • Add explicit instructions or notes about armclient compatibility with Linux/macOS, including installation steps if different.
  • Provide example commands using Linux/macOS path separators (e.g., ./rqbody-disableSoftDelete.json) alongside Windows examples.
  • Clarify whether armclient works cross-platform, and if not, suggest alternative tools or approaches for Linux/macOS users.
  • Consider including Azure CLI or REST API curl examples, which are natively cross-platform.
GitHub Create Pull Request
Backup Selective Disk Backup and Restore for Azure Virtual Machines .../main/articles/backup/selective-disk-backup-restore.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring selective disk backup and restore, but PowerShell (a Windows-centric tool) is given equal prominence and detail as the CLI. There are no explicit Linux shell (bash) or macOS-specific examples, and the only mention of Linux tools is in the context of prerequisites (lsblk, lsscsi). Windows-specific terminology and tools (PowerShell, drive C) are referenced before or more prominently than Linux equivalents. No Linux/macOS command-line walkthroughs are provided, and troubleshooting or advanced configuration is shown only for PowerShell and CLI, not for native Linux tools.
Recommendations
  • Add explicit bash/Linux shell examples for common operations, especially for users who prefer not to use Azure CLI or PowerShell.
  • Where PowerShell is referenced, clarify cross-platform support and provide equivalent bash or shell scripts for Linux/macOS users.
  • When discussing prerequisites, provide installation instructions for Linux tools (lsblk, lsscsi) for multiple distributions, and mention macOS considerations if relevant.
  • In sections comparing Windows and Linux, present Linux information first or side-by-side with Windows to avoid 'windows_first' bias.
  • Include troubleshooting steps and advanced configuration examples for Linux/macOS environments, not just PowerShell/CLI.
GitHub Create Pull Request
Backup Soft delete for SQL server in Azure VM and SAP HANA in Azure VM workloads ...articles/backup/soft-delete-sql-saphana-in-azure-vm.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for soft delete operations using the Azure Portal and Azure PowerShell, with all CLI examples given in PowerShell. There are no examples or guidance for Linux/macOS users, such as Bash, Azure CLI, or REST API usage. The PowerShell section is prominent and assumes users have access to PowerShell, which is primarily a Windows tool, though it is available cross-platform. No Linux-specific tools or workflows are mentioned.
Recommendations
  • Add equivalent examples using Azure CLI (az backup ...) for Linux/macOS users.
  • Include REST API instructions for soft delete operations to ensure platform neutrality.
  • Explicitly mention cross-platform compatibility for PowerShell, or provide installation guidance for non-Windows users.
  • Present CLI examples for both PowerShell and Azure CLI side-by-side, or alternate which is shown first.
  • Clarify any platform-specific limitations or prerequisites for each method.
GitHub Create Pull Request
← Previous Page 17 of 21 Next →