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 1326-1350 of 1604 flagged pages
Backup Back up SQL Server always on availability groups ...les/backup/backup-sql-server-on-availability-groups.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation focuses exclusively on SQL Server running in Azure VMs and Always On Availability Groups, with no mention of Linux-based SQL Server deployments, nor any examples or instructions for Linux environments. All references to backup extensions, registration, and node management implicitly assume Windows VMs, as Azure Backup for SQL Server does not support on-premises or Linux-based SQL Server instances. There are no PowerShell-specific examples or Windows tools named, but the lack of Linux parity is notable.
Recommendations
  • Explicitly state whether Linux-based SQL Server AGs are supported or not.
  • If Linux support exists, provide examples and instructions for Linux environments (e.g., using bash, systemd, or Linux-specific backup agents).
  • If Linux is not supported, clarify this early in the documentation to set expectations for cross-platform users.
  • Add a comparison table or section outlining feature parity (or lack thereof) between Windows and Linux SQL Server AG backups in Azure.
  • Reference any alternative backup solutions for Linux SQL Server AGs, if Azure Backup is not supported.
GitHub Create Pull Request
Backup Support matrix for Azure VM backups ...lob/main/articles/backup/backup-support-matrix-iaas.md
Medium Priority View Details →
Scanned: 2026-01-13 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 moderate Windows bias. Windows-specific backup agents (MARS, DPM, MABS) and tools are discussed in detail, with examples and restore instructions referencing PowerShell and Windows patterns. Windows scenarios and OS support are presented before Linux equivalents, and some features (such as file-level restore, backup agents, and backup server integration) are either unsupported or not described for Linux. Linux support is covered in separate sections, but with less detail and fewer actionable examples.
Recommendations
  • Provide Linux CLI (az, bash) examples for backup and restore operations, especially where PowerShell is referenced.
  • Add parity in agent and backup server support for Linux, or clearly document alternatives/workarounds for Linux users.
  • Present Windows and Linux scenarios side-by-side in tables and examples, rather than separating them or listing Windows first.
  • Expand documentation for Linux-specific backup limitations and supported workflows, including troubleshooting and best practices.
  • Clarify restore procedures for Linux VMs, especially where file-level restore or disk replacement is discussed.
  • Where features are Windows-only (e.g., MARS agent), explicitly state this at the top of relevant sections and suggest Linux alternatives.
GitHub Create Pull Request
Backup Encrypt backup data in a Backup vault by using customer-managed keys ...backup/encryption-at-rest-with-cmk-for-backup-vault.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions and examples for the Azure portal, PowerShell, and Azure CLI. However, PowerShell examples are prominent and detailed, and the CLI examples are present but less emphasized. There are no Linux- or macOS-specific shell examples (e.g., Bash scripts), and PowerShell is a Windows-centric tool, though it is now cross-platform. The documentation does not mention or provide parity for Linux-native tooling or workflows, and the ordering of examples often places PowerShell before CLI, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit Bash shell examples for all CLI commands to demonstrate usage on Linux/macOS.
  • Where PowerShell is used, clarify that Azure PowerShell is available cross-platform, or provide Bash equivalents.
  • Reorder sections so that Azure CLI (which is cross-platform and popular among Linux/macOS users) appears before PowerShell.
  • Explicitly mention Linux/macOS compatibility in relevant sections, especially where commands or tools are cross-platform.
  • Include troubleshooting notes or tips relevant to Linux/macOS environments if there are any known differences.
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-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 page for Azure Backup Server (MABS) V3 UR1 protection matrix exhibits a notable Windows bias. Windows workloads are listed first and in much greater detail, with extensive coverage of Windows-specific features (NTFS, VSS, deduplication, system state, bare metal recovery, etc.), while Linux support is relegated to a single, brief section. Linux protection is only available for guest VMs, with no mention of agent-based or file-level backup for Linux, nor examples of Linux-specific recovery scenarios. Windows tools and patterns (e.g., Volume Shadow Copy Service, NTFS, Windows Management Framework) are referenced exclusively, and recovery options for Linux VMs are limited compared to Windows. There are no Linux command-line or tool examples, and critical features (item-level recovery, deduplication, system state) are only available for Windows.
Recommendations
  • Expand the Linux section to include agent-based backup and recovery scenarios for Linux workloads, if supported.
  • Provide Linux-specific examples and instructions, such as supported file systems, backup/restore commands, and recovery options.
  • Clarify limitations and feature parity between Windows and Linux (e.g., item-level recovery, deduplication, system state backup).
  • List Linux workloads alongside Windows workloads in the main protection matrix, rather than in a separate, minimized section.
  • Reference Linux tools and patterns (e.g., LVM snapshots, ext4/xfs file systems) where relevant.
  • If Linux support is limited, explicitly state this and provide guidance or alternatives for Linux users.
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-13 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 page exhibits a notable Windows bias. Most automation and scripting examples use PowerShell, including role assignment, DNS entry creation, and private endpoint management. The use of Windows-specific tools (PowerShell scripts, .ps1 files, and references to uploading files in the PowerShell window) is pervasive, with no equivalent Bash, Azure CLI, or Linux/macOS shell examples. The instructions for uploading and running scripts are tailored to Windows users, and Windows terminology (e.g., host files, domain controller) is used. Linux/macOS users are left to infer how to adapt these steps, creating friction and potential confusion.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell scripts and automation steps.
  • Include instructions for uploading and running scripts in Bash/Cloud Shell for Linux/macOS users.
  • Add examples of managing private endpoints, DNS records, and permissions using Azure CLI and REST API via curl.
  • Clarify terminology for cross-platform users (e.g., explain host file locations on Linux/macOS).
  • Ensure that all critical steps (role assignment, DNS management, endpoint creation) have platform-neutral or platform-specific guidance for both Windows and Linux/macOS.
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-13 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 notable Windows bias. The only command-line deployment example is given in Azure PowerShell, with no Azure CLI or Bash example provided. The instructions and next steps reference PowerShell before CLI or REST, and the deployment section does not show how to deploy the ARM template from Linux/macOS environments.
Recommendations
  • Add Azure CLI and Bash examples for deploying the ARM template, especially in the 'Deploy the template' section.
  • Present both PowerShell and CLI/Bash examples side-by-side or in tabs, ensuring Linux/macOS users have clear guidance.
  • In the 'Next steps' section, list Azure CLI and REST API options before or alongside PowerShell, not after.
  • Explicitly mention that all deployment methods (PowerShell, CLI, portal, REST) are cross-platform, and provide links/examples for each.
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-13 00:00
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 in several ways. It references PowerShell objects and behaviors as the default, describes modification patterns using Windows-style file paths (e.g., .\OSSPolicy.json), and mentions PowerShell before CLI in the overview. There are no explicit Linux/macOS examples, and file path syntax is Windows-centric throughout. The guidance for modifying policy templates assumes Windows conventions and does not provide parity for Linux/macOS users.
Recommendations
  • Provide Linux/macOS-specific examples, including file path syntax (e.g., ./OSSPolicy.json) and shell usage.
  • Clarify that the Azure CLI commands work cross-platform and show examples in bash/zsh.
  • Avoid referring to PowerShell objects as the default; instead, present CLI and PowerShell approaches equally.
  • Add notes or sections for Linux/macOS users, especially regarding file handling and scripting differences.
  • Reorder tool mentions so CLI and PowerShell are presented with equal prominence, or alternate order.
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-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 demonstrates a strong Windows bias by exclusively providing PowerShell deployment instructions and referencing Azure PowerShell modules, with no mention of Azure CLI or Bash alternatives. All example scripts and next steps are PowerShell-centric, leaving Linux/macOS users without guidance for their native environments.
Recommendations
  • Add Azure CLI and Bash examples for template deployment alongside PowerShell.
  • Explicitly mention that deployment can be performed from Linux/macOS using Azure CLI.
  • Provide links to cross-platform tooling documentation (e.g., Azure CLI install and usage).
  • Reorder or parallelize instructions so that Windows and Linux/macOS approaches are presented equally.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides only PowerShell-based deployment instructions for the Bicep template, with no mention of Azure CLI or Bash alternatives. The instructions and next steps are focused on PowerShell, which is primarily used on Windows, creating friction for Linux/macOS users who typically use Azure CLI or Bash. No Linux/macOS-specific guidance or examples are provided.
Recommendations
  • Add Azure CLI and Bash examples for deploying the Bicep template, alongside PowerShell.
  • Explicitly mention cross-platform options and provide links to Azure CLI documentation.
  • Reorder or parallelize instructions so that CLI/Bash examples are shown before or alongside PowerShell.
  • Include notes clarifying that PowerShell is available on Linux/macOS, but CLI/Bash may be more familiar to non-Windows users.
GitHub Create Pull Request
Backup Quickstart - Resource Manager template VM Backup .../blob/main/articles/backup/quick-backup-vm-template.md
Medium Priority View Details →
Scanned: 2026-01-13 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 notable Windows bias by exclusively providing PowerShell deployment examples, referencing Windows VM creation in the template, and omitting direct Linux/macOS CLI or Bash instructions. While Azure CLI and portal methods are mentioned, no explicit Linux-friendly example is shown, and Windows/PowerShell patterns are presented first and in detail.
Recommendations
  • Add explicit Azure CLI and Bash examples for template deployment, showing commands suitable for Linux/macOS users.
  • Include instructions for deploying a Linux VM in the ARM template or clarify how to modify the template for Linux VM backup.
  • Present CLI/Bash examples alongside PowerShell, or alternate their order to avoid Windows-first bias.
  • Reference Linux/macOS shell usage in the Cloud Shell, not just right-click paste (which is Windows-centric).
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-13 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 how to back up a Windows virtual machine in Azure using Terraform. All examples, resource creation steps, and references are for Windows VMs only, with no mention of Linux VM equivalents or how to adapt the process for Linux. The 'Next steps' section also directs users to Windows VM articles, reinforcing the Windows-centric focus.
Recommendations
  • Add parallel instructions and Terraform code samples for creating and backing up a Linux VM (e.g., using azurerm_linux_virtual_machine).
  • Include notes or sections explaining differences between Windows and Linux VM backup processes, if any.
  • Provide links to documentation and samples for Linux VM backup with Terraform.
  • Ensure that CLI commands and resource names are generalized or include Linux examples where appropriate.
  • Update the 'Next steps' section to reference both Windows and Linux VM articles.
GitHub Create Pull Request
Backup Quickstart - Install Azure Backup extension in an AKS cluster ...main/articles/backup/quick-install-backup-extension.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides only Azure Portal-based instructions, which are platform-agnostic but visually and operationally most familiar to Windows users. There are no direct CLI or shell-based examples in the quickstart, which would benefit Linux/macOS users. The 'Next steps' section lists PowerShell before CLI, ARM, Bicep, and Terraform, subtly prioritizing Windows tooling.
Recommendations
  • Add Azure CLI instructions directly in the quickstart, alongside or instead of portal steps, to ensure parity for Linux/macOS users.
  • Reorder 'Next steps' to list CLI before PowerShell, or group them together neutrally.
  • Include screenshots or notes clarifying that the portal is accessible from any OS/browser.
  • Explicitly mention that all steps can be performed from Linux/macOS environments using CLI or browser.
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-13 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 notable Windows bias by exclusively providing PowerShell deployment instructions for the ARM template, with no mention of Azure CLI, Bash, or Linux/macOS workflows. The prerequisites and deployment sections focus on PowerShell, and Linux alternatives are not referenced or linked directly in the quickstart flow.
Recommendations
  • Add Azure CLI and Bash examples for deploying the ARM template, ensuring parity for Linux/macOS users.
  • Explicitly mention that the deployment steps can be performed on Linux/macOS using Azure CLI or Bash, and provide links or inline instructions.
  • Reorder or parallelize example sections so that Windows and Linux/macOS instructions are presented together or in equal prominence.
  • Include a note clarifying cross-platform support for Azure Resource Manager deployments.
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-13 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 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 instructions reference Windows-specific shell interactions (right-click to paste). While the Bicep template itself is cross-platform, the operational guidance is Windows-centric.
Recommendations
  • Add Azure CLI and Bash examples for deploying the Bicep template, ensuring Linux/macOS users have clear, native instructions.
  • Present CLI and PowerShell deployment options side-by-side, or at least mention both, to avoid implying PowerShell is required.
  • Replace or supplement Windows-specific shell instructions (e.g., right-click to paste) with platform-neutral guidance.
  • Explicitly state that the Bicep CLI and Azure CLI are available and supported on Linux/macOS, and link to relevant 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-13 00:00
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, referencing Windows-specific features (e.g., registry edits), and omitting Linux VM recovery examples or guidance. All item-level restore instructions are for Windows VMs, and the registry key configuration for parallel restores is a Windows-only pattern. There are no examples or notes for Linux or macOS users, nor any mention of restoring files from Linux VMs.
Recommendations
  • Add explicit guidance and examples for restoring individual files from Linux VMs, or clarify if this is unsupported.
  • If Linux file-level recovery is not supported, state this clearly and suggest alternative approaches for Linux VM users.
  • Include parity in documentation structure: mention Linux/macOS scenarios where relevant, and avoid Windows-only terminology (e.g., registry keys) without alternatives.
  • Provide troubleshooting and recovery steps for Linux VMs, or link to relevant resources.
  • When listing recovery options, specify OS limitations up front and offer cross-platform context.
GitHub Create Pull Request
Backup Restore encrypted Azure VMs ...les/backup/restore-azure-encrypted-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides restore instructions for both Windows and Linux Azure VMs, but there is a notable Windows bias. PowerShell is mentioned as the primary method for creating a VM from restored disks, with no equivalent CLI or Linux-native example. The process for Linux VMs is relegated to a separate step, focusing only on reinstallation of the ADE extension, without detailed restore or deployment instructions. Windows-specific links and patterns (e.g., OS disk swap) are referenced before Linux equivalents, and Linux users lack parity in automation and scripting guidance.
Recommendations
  • Add Azure CLI and/or Bash examples for creating a VM from restored disks, alongside PowerShell.
  • Provide step-by-step instructions for restoring and deploying Linux VMs, not just ADE extension reinstallation.
  • Include links to Linux-specific documentation (e.g., disk swap for Linux VMs) where Windows links are present.
  • Ensure automation and scripting guidance is available for both platforms.
  • Present Windows and Linux instructions in parallel, rather than Windows-first.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation consistently references Windows-centric resources and patterns, such as SQL Server databases on Azure VMs (which are typically Windows-based), Windows-style file paths (e.g., C:\SQLfiles\Default.ldf), and does not mention or provide examples for Linux-based SQL Server deployments. All example resource names, directory paths, and database instances assume a Windows environment. There are no references to Linux tools, Linux file paths, or instructions for restoring SQL Server databases on Linux VMs.
Recommendations
  • Explicitly state whether the REST API supports SQL Server on Linux VMs and clarify any differences in restore procedures.
  • Provide Linux-specific examples, including file paths (e.g., /var/opt/mssql/data), resource naming conventions, and alternate directory mappings.
  • Mention any Linux prerequisites or considerations, such as required permissions, service names, or differences in SQL Server instance management.
  • If PowerShell or Windows-only tools are referenced elsewhere, include equivalent Bash/CLI commands for Linux users.
  • Add a section or note addressing cross-platform compatibility and limitations.
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-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 exhibits a moderate Windows bias. It references Windows-specific tools (PsExec, NT AUTHORITY\SYSTEM), assumes Windows file paths (C:\...), and does not provide Linux equivalents or examples for key restore operations. All examples and instructions are tailored to Windows environments, with no mention of Linux or cross-platform alternatives for mounting shares, file permissions, or running SQL Server on Linux VMs.
Recommendations
  • Add Linux-specific instructions for mounting Azure File Shares, including sample commands using 'mount' and setting permissions with 'chmod' and 'chown'.
  • Provide examples of restoring SQL Server databases on Linux-based Azure VMs, including file paths and service management (e.g., systemctl for SQL Server Agent).
  • Replace or supplement references to Windows tools (PsExec, NT AUTHORITY\SYSTEM) with Linux equivalents (e.g., sudo, relevant user accounts).
  • Include screenshots or CLI steps from Linux environments where applicable.
  • Explicitly state support and any limitations for SQL Server on Linux Azure VMs in restore scenarios.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation primarily describes restore workflows using the Azure portal and mentions using PowerShell or CLI scripts for permissions, but does not provide explicit Linux-specific instructions or examples. The language and screenshots are focused on the Azure portal, which is cross-platform, but there is a subtle bias in referencing PowerShell and CLI scripts without clarifying Linux usage or providing bash/Linux command examples. There are no explicit Windows-only tools, but Linux parity is not fully addressed.
Recommendations
  • Add explicit bash/Linux CLI examples for permission assignment and disk mounting, alongside PowerShell examples.
  • Clarify that Azure CLI commands work on Linux/macOS and provide sample commands for common restore operations.
  • Include notes or sections on mounting restored disks in Linux environments, referencing relevant Linux tools (e.g., mount, fdisk).
  • Ensure that any script references (PowerShell or CLI) are accompanied by platform-specific instructions for both Windows and Linux.
  • Add screenshots or walkthroughs for Linux desktop environments if relevant.
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-13 00:00
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) and does not mention or show Linux/macOS equivalents (e.g., ./rqbody-disableSoftDelete.json). There is no guidance on running armclient on Linux/macOS, nor are alternative tools or shell patterns discussed.
Recommendations
  • Add Linux/macOS command examples using forward slashes (e.g., ./rqbody-disableSoftDelete.json).
  • Clarify whether armclient is cross-platform and provide installation instructions for Linux/macOS if supported.
  • Mention alternative tools or methods for Linux/macOS users if armclient is Windows-only.
  • Explicitly state OS requirements and parity in prerequisites.
GitHub Create Pull Request
Backup Accidental Delete Protection for Azure Files ...b/main/articles/backup/soft-delete-azure-file-share.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation references an 'Undelete File Share Script' that is a PowerShell script, without mentioning or providing equivalent Linux/macOS CLI or Bash examples. The only script/tool referenced is PowerShell, and there is no indication of parity for Linux users. This creates friction for non-Windows users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Provide equivalent CLI or Bash scripts for undeleting file shares, or clarify if Azure CLI can be used for the same operations.
  • Explicitly mention cross-platform alternatives (e.g., Azure CLI, REST API) alongside PowerShell scripts.
  • Ensure that all example scripts and tools are available for Linux/macOS users, or link to platform-agnostic documentation.
  • If PowerShell is required, note how to install and use PowerShell Core on Linux/macOS.
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-13 00:00
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 performing soft delete operations using the Azure Portal and Azure PowerShell, but does not mention or provide examples for Linux/macOS command-line tools (such as Azure CLI or REST API). PowerShell, a Windows-centric tool, is the only command-line method described, and it is presented before any Linux-friendly alternatives. This creates friction for users on Linux or macOS who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include REST API examples for advanced users who may automate these operations from any OS.
  • Explicitly state OS requirements or limitations for PowerShell, and provide guidance for Linux/macOS users on how to install or use PowerShell if necessary.
  • Present Azure CLI examples before or alongside PowerShell to avoid Windows-first bias.
GitHub Create Pull Request
Backup Soft delete for virtual machines ...b/main/articles/backup/soft-delete-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
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 the Azure portal and Azure PowerShell, with all CLI examples using PowerShell cmdlets. There are no Bash, Azure CLI, or Linux/macOS-specific examples. PowerShell is featured as the primary automation method, which is most commonly used on Windows. The lack of Linux-native command-line instructions may create friction for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI (az backup ...) examples for all PowerShell cmdlets shown.
  • Explicitly mention that PowerShell Core is cross-platform, or clarify if Windows PowerShell is required.
  • Include Bash script snippets or guidance for Linux/macOS users where automation is discussed.
  • Reorder sections so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides extensive PowerShell examples and references to Windows-specific tools and concepts (e.g., BitLocker, drive C), while Linux-specific instructions and examples are minimal or absent. Windows terminology and examples often appear before Linux equivalents, and there is little guidance for Linux users beyond brief mentions of required utilities (lsblk, lsscsi). No Linux shell (bash) or distro-specific examples are given, and PowerShell is presented as a primary scripting option, which is less common on Linux.
Recommendations
  • Add Linux/bash command examples for all CLI and scripting operations, especially for tasks currently shown only in PowerShell.
  • Provide parity in troubleshooting and error handling for Linux environments, including common issues with required utilities (lsblk, lsscsi).
  • Explicitly mention Linux/macOS compatibility for CLI commands and clarify any differences in output or usage.
  • Include Linux-specific screenshots or walkthroughs in portal sections if UI differs.
  • Present Linux and Windows examples side-by-side, or alternate which OS is shown first in examples.
  • Expand documentation on disk encryption for Linux (dm-crypt) to match the detail given for Windows (BitLocker).
GitHub Create Pull Request
Backup Use Archive tier .../blob/main/articles/backup/use-archive-tier-support.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides comprehensive guidance for Azure Backup Archive tier usage across three pivots: Azure Portal, PowerShell, and Azure CLI. While the CLI section is present and covers cross-platform usage, there is a notable emphasis on PowerShell, with more detailed examples, explanations, and advanced scripting guidance. PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. Additionally, in 'Next steps' and cross-references, PowerShell is often mentioned before CLI, reflecting a 'Windows-first' ordering.
Recommendations
  • Ensure CLI examples are as detailed and comprehensive as PowerShell examples, including advanced scenarios and scripting at scale.
  • In 'Next steps' and cross-references, alternate the order of PowerShell and CLI, or list CLI first to balance perceived priority.
  • Explicitly mention that Azure CLI is fully supported on Linux/macOS and provide links to platform-specific installation guides.
  • Where sample scripts are provided for PowerShell, consider providing equivalent Bash or Python scripts for CLI users.
  • Audit for any PowerShell-only features and clarify if any functionality is not available via CLI, or provide workarounds.
GitHub Create Pull Request
← Previous Page 54 of 65 Next →