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 1201-1225 of 1604 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-23 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 provides comprehensive coverage for both Windows and Linux Azure VM backup scenarios, but there are notable signs of Windows bias. Windows-specific tools (MARS agent, DPM, MABS) are referenced and supported, while their use for Linux is explicitly marked as unsupported. Restore examples and instructions frequently mention PowerShell and Windows-centric workflows, with Linux alternatives rarely described in detail. Windows scenarios and tools are often listed first, and some restore methods (e.g., file-level restore, disk replacement) reference Windows patterns or tools without Linux-specific guidance. Linux support is present, but less detailed and with more unsupported features.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside PowerShell for restore and backup operations.
  • Include more detailed Linux-specific workflows for restore scenarios, especially for file-level restore and disk replacement.
  • Clarify Linux limitations and offer workarounds or alternatives where possible.
  • Balance the order of presentation so that Linux and Windows are treated equally in tables and lists.
  • Reference Linux-native backup tools or scripts where relevant, or explain why they are not supported.
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-22 01:38
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell scripts multiple times as the primary method for granting privileges to database users, with alternatives like PG Admin or PSQL mentioned only as secondary options. The explicit callout to PowerShell in both the prerequisites and configuration steps, and the phrasing that prioritizes PowerShell, create a Windows-first impression. Linux-native tools are not given equal prominence or example coverage.
Recommendations
  • Provide explicit, step-by-step examples for granting privileges using psql (command-line) and/or PG Admin, not just mention them as alternatives.
  • Where PowerShell scripts are referenced, include equivalent bash/psql commands or scripts for Linux/macOS users.
  • In prerequisites and main steps, list Linux/macOS-friendly methods (e.g., psql, bash scripts) alongside or before PowerShell, to avoid the impression that PowerShell is the default or only supported method.
  • Clarify that all steps can be performed on Linux/macOS as well as Windows, and link to relevant cross-platform tooling documentation.
GitHub Create Pull Request
Backup Tutorial - Back up Azure Database for PostgreSQL server ...lob/main/articles/backup/tutorial-postgresql-backup.md
Medium Priority View Details →
Scanned: 2026-01-22 01:38
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias, primarily through the use of PowerShell scripts for privilege assignment and by referencing PowerShell before mentioning alternatives like PG admin or PSQL. There are no explicit Linux/macOS command-line examples, and the guidance for non-Windows users is less detailed, which may create friction for those users.
Recommendations
  • Provide explicit Linux/macOS command-line examples using psql and/or bash scripts for privilege assignment and other database operations.
  • When mentioning PowerShell scripts, always include equivalent steps using psql or PG admin, and present them side-by-side or in parallel sections.
  • Clarify which steps are OS-agnostic (e.g., Azure portal actions) and which require OS-specific tooling, ensuring parity for Linux/macOS users.
  • Add notes or links to official PostgreSQL documentation for privilege management via psql and PG admin.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page is focused on Azure CLI usage, which is cross-platform, but several examples and instructions use Windows-style file paths (e.g., .\OSSPolicy.json) and redirection (>) that are specific to Windows/PowerShell. There is no mention of Linux/macOS equivalents, and the file manipulation workflow is described in a way that assumes a Windows environment. Additionally, PowerShell is referenced as the default for object manipulation, with no Linux shell alternatives discussed.
Recommendations
  • Provide Linux/macOS shell examples alongside Windows examples, especially for file paths (use ./OSSPolicy.json for Linux/macOS) and output redirection.
  • Clarify that the Azure CLI commands work on all platforms and note any differences in file handling or shell syntax.
  • Include a note or section on how to perform file manipulations (input/output redirection, renaming) in Bash/zsh.
  • When referencing PowerShell object manipulation, mention Linux/macOS alternatives (e.g., jq for JSON editing).
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-15 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 examples for deploying the Bicep template and restoring backups, with no mention of Azure CLI or Bash equivalents. The instructions and next steps are written from a Windows/PowerShell perspective, creating friction for Linux/macOS users who typically use Azure CLI or Bash.
Recommendations
  • Add Azure CLI and Bash examples for deploying the Bicep template.
  • Clearly state that both PowerShell and Azure CLI can be used, and provide links to relevant CLI documentation.
  • Ensure next steps include Linux/macOS-friendly instructions (e.g., restoring via Azure CLI).
  • Where possible, mention cross-platform tools first or equally.
GitHub Create Pull Request
Backup Delete a Microsoft Azure Recovery Services Vault ...blob/main/articles/backup/backup-azure-delete-vault.md
Medium Priority View Details →
Scanned: 2026-01-15 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 demonstrates a moderate Windows bias. PowerShell is presented as the primary automation method, with detailed scripts and command references. Windows-specific tools (MARS, MABS, DPM consoles) are described in depth, while Linux alternatives for on-premises backup management are not mentioned. The ARMClient installation instructions use Chocolatey, a Windows package manager, with no Linux/macOS equivalents. The CLI section is limited in scope and does not provide parity with PowerShell capabilities, and there are no Bash or cross-platform scripting examples.
Recommendations
  • Provide Bash or Azure CLI script examples for deleting vaults and backup items, especially for Linux/macOS users.
  • Include instructions for installing ARMClient on Linux/macOS (e.g., via npm or direct download), not just via Chocolatey.
  • Clarify which steps or tools are Windows-only and offer Linux/macOS alternatives where possible.
  • Expand CLI support and documentation to cover more backup types, not just Azure VM backups.
  • Add notes or links for Linux/macOS users on how to perform equivalent operations, especially for on-premises scenarios.
GitHub Create Pull Request
Backup Troubleshoot encrypted Azure VM backup errors ...icles/backup/backup-azure-encrypted-vm-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-14 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 CLI example for configuring permissions, without mentioning Linux/macOS equivalents such as Azure CLI or Bash. Windows tools and patterns (PowerShell) are mentioned exclusively, and there are no Linux-specific instructions or examples. This may create friction for users on Linux/macOS platforms who need to perform the same tasks.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all command-line instructions.
  • Explicitly mention cross-platform tools and provide parity in step-by-step guides.
  • Clarify that the steps apply to all supported operating systems, and note any OS-specific differences.
  • Ensure that portal-based instructions do not assume Windows-only environments.
GitHub Create Pull Request
Backup About Azure VM backup .../main/articles/backup/backup-azure-vms-introduction.md
Medium Priority View Details →
Scanned: 2026-01-14 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 demonstrates a moderate Windows bias. Windows-specific backup mechanisms (VSS) are described in detail, with PowerShell mentioned for restore operations. Windows examples and tools are presented before Linux equivalents, and Linux instructions are less detailed, relying on users to create custom scripts. There are no explicit Linux command-line examples or automation guidance, and PowerShell is referenced for restore operations without a Linux alternative.
Recommendations
  • Provide equivalent Linux CLI (e.g., Bash, Azure CLI) examples for backup and restore operations, especially where PowerShell is referenced.
  • Offer more detailed guidance and sample scripts for Linux app-consistent backups, not just links.
  • Present Windows and Linux instructions in parallel, rather than Windows-first.
  • Include automation examples for Linux (e.g., using Azure CLI, shell scripts) where PowerShell is used for Windows.
  • Clarify Linux-specific considerations and best practices, matching the detail given for Windows.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Blobs using Azure CLI .../main/articles/backup/quick-blob-vaulted-backup-cli.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page references Azure CLI as the primary tool, which is cross-platform. However, in the prerequisites section, the link to create a Backup vault points to a PowerShell-based guide, suggesting Windows tooling first. In the 'Next step' section, Azure PowerShell is mentioned before Azure CLI, again prioritizing Windows-centric tools. There are no explicit Linux/macOS examples or references, and no mention of platform-specific considerations.
Recommendations
  • Ensure that all linked guides (such as creating a Backup vault) have Azure CLI instructions and link to those by default or alongside PowerShell.
  • In the 'Next step' section, list Azure CLI before Azure PowerShell to reinforce cross-platform parity.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide any platform-specific notes if needed.
  • Audit included markdown files to confirm they do not contain Windows-only examples or instructions.
GitHub Create Pull Request
Backup Azure Resource Manager and Bicep files ...lob/main/articles/backup/backup-rm-template-samples.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page lists Azure Resource Manager and Bicep templates for backup scenarios, but includes a template specifically for deploying a Windows Server VM with backup enabled, without mentioning or providing an equivalent example for Linux VMs. This prioritizes Windows scenarios and may lead Linux users to feel unsupported or uncertain about Linux parity.
Recommendations
  • Add a template example for deploying a Linux VM with backup enabled, similar to the Windows Server VM example.
  • Explicitly state that backup templates and policies apply to both Windows and Linux VMs where applicable.
  • Ensure that examples and descriptions do not imply Windows is the default or only supported platform.
  • Review other template descriptions for implicit Windows bias and clarify Linux support where relevant.
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-14 00:00
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 notable Windows bias. Windows backup scenarios (especially with MARS agent, DPM, and MABS) are described in detail and presented first, while Linux support is often listed as 'not supported' or relegated to secondary tables. Windows-specific tools (MARS agent, DPM, MABS) are referenced throughout, with limited or no Linux equivalents. Linux backup options are less comprehensive, and Linux examples or workflows are missing or only briefly mentioned (e.g., requiring custom scripts for app-consistent backups).
Recommendations
  • Provide Linux-first or Linux-parity examples and workflows, especially for common backup scenarios.
  • Include equivalent Linux tooling or recommend open-source alternatives where possible.
  • Add detailed guidance for Linux backup, including step-by-step instructions and supported use cases.
  • Clarify limitations for Linux users early and suggest workarounds or roadmap items.
  • Balance tables and sections so Linux and Windows support are presented equally, not with Windows-first ordering.
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-14 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 managing soft delete of Azure VM backups using the Azure Portal and Azure PowerShell, with PowerShell being a Windows-centric tool. There are no CLI (az), Bash, or Linux/macOS-specific examples or guidance. The PowerShell section is extensive and appears before REST API coverage, reinforcing a Windows-first approach and leaving Linux/macOS users without direct parity or clear alternatives.
Recommendations
  • Add equivalent examples using Azure CLI (az), which is cross-platform and widely used on Linux/macOS.
  • Include Bash script snippets for common operations (delete, undelete, resume backup) to help Linux users.
  • Explicitly mention that PowerShell Core is available cross-platform, but provide CLI alternatives for users who prefer native Linux tools.
  • Reorder sections so that cross-platform tools (CLI, REST API) are presented before or alongside PowerShell.
  • Add a note clarifying tool availability and platform compatibility for each method.
GitHub Create Pull Request
Backup About the Azure Virtual Machine restore process ...cs/blob/main/articles/backup/about-azure-vm-restore.md
Medium Priority View Details →
Scanned: 2026-01-14 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 primarily in the 'Restore an encrypted VM' scenario, where only Windows VM encryption scenarios are discussed and PowerShell is mentioned as the tool for VM creation after disk restore. There are no references to Linux VM encryption or restore processes, nor are Linux-specific tools or examples provided. The overall restore process is described in a platform-neutral way, but critical details for encrypted VM restore are Windows-centric.
Recommendations
  • Add equivalent Linux VM encryption restore scenarios, including links to documentation for restoring encrypted Linux VMs.
  • Provide examples using Azure CLI or other cross-platform tools, not just PowerShell, especially for VM creation after disk restore.
  • Explicitly mention Linux support and any differences in restore workflows for Linux VMs, particularly for encrypted VMs.
  • Ensure that restore scenarios and troubleshooting sections include Linux-specific guidance where applicable.
GitHub Create Pull Request
Backup Azure Backup - Archive tier overview ...docs/blob/main/articles/backup/archive-tier-support.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation lists PowerShell as a supported client before CLI, which may suggest a Windows-first approach. There are references to Azure Virtual Machines and SQL Server/SAP HANA in Azure VMs, which are commonly Windows workloads, but Linux VMs are not explicitly mentioned. The client support section includes PowerShell and CLI, but does not provide example commands or workflows for either, nor does it clarify parity between Windows and Linux usage. No explicit Linux examples, tools, or patterns are provided, and screenshots show the Azure Portal, which is cross-platform, but no CLI or Linux-specific guidance is present.
Recommendations
  • Explicitly mention Linux VM support and provide examples for Linux workloads where applicable.
  • Add CLI examples alongside PowerShell, and clarify that CLI is cross-platform.
  • Ensure that any PowerShell instructions are matched with Bash/CLI equivalents.
  • Include screenshots or walkthroughs for CLI usage on Linux/macOS.
  • Clarify any differences or limitations for Linux users in supported workloads or operations.
GitHub Create Pull Request
Backup Azure Backup glossary ...ocs/blob/main/articles/backup/azure-backup-glossary.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The glossary page demonstrates a moderate Windows bias. Windows-specific technologies and tools (such as VSS, DPM, MABS, and MARS agent) are referenced without equivalent Linux alternatives or explanations. Windows-centric backup concepts (e.g., 'Bare metal backup', 'System State backup', 'VSS') are described in detail, while Linux approaches are only briefly mentioned or omitted. Azure PowerShell is listed alongside Azure CLI, but Windows tools and patterns are more prevalent and often described first. Linux-specific backup mechanisms and examples are largely missing.
Recommendations
  • For each Windows-specific tool or concept (e.g., VSS, DPM, MABS, MARS agent), add a note or section describing the Linux equivalent or alternative approach, or clarify if not applicable.
  • Where backup consistency is discussed (e.g., 'Application consistent backup'), provide more detail on Linux methods (such as pre/post scripts), including links to relevant documentation.
  • Include references to Linux-native backup tools or patterns where appropriate (e.g., mention rsync, tar, or Azure Backup support for Linux VMs).
  • Ensure that examples and terminology are balanced between Windows and Linux workloads, or explicitly state when a feature is Windows-only.
  • In the 'Snapshot' and 'System State backup' sections, clarify Linux support and provide links to Linux documentation if available.
GitHub Create Pull Request
Backup Automation in Azure Backup ...re-docs/blob/main/articles/backup/automation-backup.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is repeatedly mentioned as a primary automation method and example client, often listed before cross-platform alternatives like CLI or SDKs. Automation scenarios and workflows reference PowerShell and Runbooks (which are often Windows-centric), with no explicit Linux/macOS shell or scripting examples. However, the page does acknowledge CLI, REST API, and SDKs, and links to Terraform and Ansible samples, which are cross-platform.
Recommendations
  • Provide explicit Linux/macOS shell (bash) examples alongside PowerShell, especially for common automation tasks.
  • When listing automation methods, alternate or randomize the order, or list CLI before PowerShell to avoid implicit prioritization.
  • Include sample scripts or walkthroughs using Azure CLI and SDKs in Python/Go for key scenarios.
  • Clarify that Runbooks and PowerShell are available cross-platform via Azure Automation, or provide Linux-native alternatives where appropriate.
  • Add a section or callout for Linux/macOS users with tips or links to relevant resources.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Data Lake Storage using ARM or Bicep template ...ata-lake-storage-backup-configure-quickstart-arm-bicep.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell deployment examples for both ARM and Bicep templates, with no Azure CLI or Bash equivalents. PowerShell is a Windows-centric tool, and while Azure Cloud Shell supports PowerShell, many Linux/macOS users prefer Azure CLI or Bash. The lack of cross-platform deployment instructions creates friction for non-Windows users.
Recommendations
  • Add Azure CLI and Bash deployment examples alongside PowerShell for both ARM and Bicep templates.
  • Explicitly mention that Azure Cloud Shell supports both PowerShell and Bash, and provide links to relevant Azure CLI documentation.
  • Clarify that the deployment steps are platform-agnostic when using Azure Cloud Shell, but provide local instructions for Linux/macOS users who may not use PowerShell.
  • Consider listing Azure CLI/Bash examples first or side-by-side to emphasize cross-platform support.
GitHub Create Pull Request
Backup Back up Azure Kubernetes Service by using Azure Backup ...cles/backup/azure-kubernetes-service-cluster-backup.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by repeatedly referencing Azure PowerShell as an alternative to the Azure portal, both in the introduction and in the 'Next steps' section. No mention is made of Azure CLI or Bash scripting, which are more common on Linux/macOS. All examples and instructions are either GUI-based or reference PowerShell, with no Linux-specific command-line examples or parity for Linux users. The only command-line example provided is 'kubectl apply', which is cross-platform, but the backup/restore orchestration is not shown for Linux environments.
Recommendations
  • Include Azure CLI examples alongside or before PowerShell examples for all backup and restore operations.
  • Explicitly mention Linux/macOS compatibility for command-line steps.
  • Provide Bash or shell script examples for common tasks, such as installing the Backup extension or configuring backup policies.
  • Add a section or links for Linux/macOS users, clarifying how to perform tasks without relying on PowerShell.
  • Ensure that references to command-line tools are not Windows-centric and provide parity for Linux users.
GitHub Create Pull Request
Backup Configure Vaulted Backup for Azure Data Lake Storage using Azure portal, PowerShell, or Azure CLI ...les/backup/azure-data-lake-storage-configure-backup.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides three pivots: Azure portal, PowerShell, and Azure CLI. PowerShell is given a dedicated section with detailed step-by-step examples and cmdlets, which are inherently Windows-centric. The PowerShell pivot appears before the CLI pivot, and there is explicit mention of installing Azure PowerShell, a tool most commonly used on Windows. There are no Linux-specific instructions or examples (e.g., Bash, shell scripting), nor is there any mention of Linux/macOS compatibility for PowerShell. The CLI section is present and reasonably detailed, but the overall structure and example order favor Windows users.
Recommendations
  • Add explicit notes about PowerShell Core compatibility on Linux/macOS, or provide Bash equivalents where possible.
  • Ensure CLI examples are as detailed and comprehensive as PowerShell examples.
  • Consider presenting CLI and PowerShell pivots in parallel or with CLI first, to reduce perceived Windows-first bias.
  • Include troubleshooting or installation notes for Linux/macOS users (e.g., how to install Azure CLI and PowerShell Core on Linux).
  • Add links to cross-platform tooling guides.
GitHub Create Pull Request
Backup Troubleshoot Azure Kubernetes Service backup ...backup/azure-kubernetes-service-backup-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively referencing the Azure portal UI for configuration steps and not providing equivalent command-line or YAML-based instructions for Linux/macOS users. All example commands use Azure CLI and kubectl, which are cross-platform, but UI-based steps (e.g., scaling node pools, updating extension pod resource limits) are described only via the Azure portal, with screenshots, and lack Linux-friendly alternatives. There are no references to Windows-specific tools (e.g., PowerShell), but the documentation does not provide parity for Linux users who may prefer or require CLI or YAML-based workflows.
Recommendations
  • For every Azure portal UI step, provide equivalent Azure CLI and/or kubectl YAML instructions so Linux/macOS users can perform the same operations without relying on the portal.
  • Add explicit notes clarifying that Azure CLI and kubectl are cross-platform and can be used on Linux/macOS.
  • Where screenshots are used, supplement with CLI commands and YAML manifests for resource updates.
  • Ensure troubleshooting steps (e.g., scaling node pools, updating extension pod resource limits) have CLI/YAML alternatives.
GitHub Create Pull Request
Backup Azure Kubernetes Service (AKS) backup support matrix ...azure-kubernetes-service-cluster-backup-support-matrix.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation references Azure PowerShell as a primary tool for backup and restore operations, listing it alongside Azure CLI, ARM, Bicep, and Terraform. However, there is no explicit mention of Linux/macOS-specific instructions or parity for PowerShell usage, nor is there guidance for Bash or shell scripting. The documentation does not clarify whether PowerShell examples are cross-platform or Windows-specific, and PowerShell is listed before ARM/Bicep/Terraform in the 'Next steps' section. There is also no mention of Linux-specific tools or patterns, and the absence of explicit Linux/macOS examples may create friction for non-Windows users.
Recommendations
  • Clarify whether Azure PowerShell instructions are cross-platform (Windows, Linux, macOS) and provide explicit guidance for Linux/macOS users.
  • Add Bash or shell scripting examples for common backup and restore operations, especially where PowerShell is referenced.
  • Ensure that CLI examples are shown before or alongside PowerShell, and note that Azure CLI is fully cross-platform.
  • Explicitly state that all listed tools (CLI, PowerShell, ARM, Bicep, Terraform) are supported on Linux/macOS, where applicable.
  • Consider adding a section or note on Linux/macOS compatibility and best practices for AKS backup operations.
GitHub Create Pull Request
Backup Restore Azure Kubernetes Service (AKS) using Azure Backup ...les/backup/azure-kubernetes-service-cluster-restore.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page displays Windows bias by explicitly referencing Azure PowerShell as an alternative method for restoring AKS clusters, without mentioning or providing equivalent CLI or Bash examples for Linux/macOS users. The only command-line restore option is linked as 'Azure PowerShell', and there is no mention of Azure CLI or Bash scripts. The main walkthrough is GUI-based, which is cross-platform, but the only advanced/automated method referenced is Windows-centric.
Recommendations
  • Add equivalent Azure CLI and Bash examples for restoring AKS clusters, and link to them alongside the PowerShell documentation.
  • Explicitly mention that the GUI steps are cross-platform and can be performed from any OS.
  • Where PowerShell is referenced, also reference Azure CLI and provide parity in documentation and examples.
  • Include a section on restoring AKS using Linux/macOS command-line tools.
GitHub Create Pull Request
Backup Back up Azure Local virtual machines with MABS ...e-stack-hyperconverged-infrastructure-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-14 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 notable Windows bias. All command-line examples use PowerShell and Windows-specific tools (e.g., Disable-NetFirewallRule, .exe installers), with no Linux/macOS equivalents or instructions. The prerequisites and procedures focus on Windows environments (Hyper-V, Windows Server), and Linux is only briefly mentioned as supported for file-consistent snapshots, without further guidance or examples. There are no instructions for agent installation, backup, or recovery on Linux VMs, nor any mention of Linux-specific tools or commands.
Recommendations
  • Provide Linux/macOS-specific instructions and examples for agent installation, backup, and recovery, including relevant shell commands.
  • Include guidance for managing firewall rules and agent configuration on Linux systems.
  • Clarify any limitations or differences in the backup/recovery process for Linux VMs, and offer troubleshooting steps.
  • Present Linux examples alongside Windows examples, not just as a footnote.
  • Mention Linux tools (e.g., iptables, systemctl, .sh installers) where appropriate.
GitHub Create Pull Request
Backup Architecture Overview ...-docs/blob/main/articles/backup/backup-architecture.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a notable Windows bias. Backup of on-premises machines is described as Windows-only, with the MARS agent explicitly supporting only Windows. Linux machines are stated as 'not supported' for direct backup, and no Linux alternatives or examples are provided. The backup server options (DPM/MABS) are also Microsoft-centric and primarily Windows-based. Throughout, Windows tools and patterns (MARS agent, VSS, DPM/MABS) are mentioned exclusively or before any Linux context. There is no guidance or parity for Linux on-premises backup scenarios.
Recommendations
  • Clearly state Linux backup limitations and provide links to alternative solutions for Linux on-premises machines (e.g., third-party agents, Azure Backup integration with Linux backup tools).
  • Add explicit Linux backup scenarios or a comparison table showing feature parity/gaps between Windows and Linux.
  • If Linux on-premises backup is not supported, suggest best practices for Linux users (such as using Azure Files, Blob, or VM-level backup for Linux VMs).
  • Include references to Linux documentation where relevant, especially in sections discussing Azure managed disks and VM backup.
  • Avoid presenting Windows-only tools (MARS, DPM/MABS) as the default without mentioning Linux context.
GitHub Create Pull Request
Backup Restore VMs by using the Azure portal using Azure Backup ...b/main/articles/backup/backup-azure-arm-restore-vms.md
Medium Priority View Details →
Scanned: 2026-01-14 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 demonstrates a moderate Windows bias. Windows-specific tools, terms, and examples (such as PowerShell, bcdedit, netdom, and RDP) are mentioned explicitly, often without equivalent Linux guidance. Windows-centric links and instructions appear before or instead of Linux alternatives. Linux scenarios are referenced but lack detailed, actionable steps or command examples, especially for post-restore troubleshooting and advanced network configurations.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for post-restore steps (e.g., resetting passwords, repairing boot, rejoining domains).
  • Include Linux command-line equivalents (such as bash/SSH commands) where PowerShell or Windows CMD is shown.
  • Add links to Linux documentation for VM management, troubleshooting, and network configuration.
  • Clarify when instructions are Windows-only and offer parallel Linux workflows where possible.
  • Mention Linux-specific considerations (e.g., SELinux, cloud-init, SSH key management) in relevant sections.
  • Where Windows tools (like bcdedit, netdom, RDP) are referenced, also describe the Linux approach (e.g., grub, SSH, Linux domain join/leave).
GitHub Create Pull Request
← Previous Page 49 of 65 Next →