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 476-500 of 520 flagged pages
Backup Encrypt backup data in a Backup vault by using customer-managed keys ...backup/encryption-at-rest-with-cmk-for-backup-vault.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides step-by-step instructions for Azure portal, PowerShell, and Azure CLI. PowerShell examples and references are prominent, and in several sections, PowerShell is presented before CLI. There is a slight ordering bias toward Windows-centric tools (PowerShell) over cross-platform CLI, but Linux/macOS users can complete all tasks using Azure CLI, which is included throughout. No Windows-only tools or patterns are required, and parity is generally maintained.
Recommendations
  • Present Azure CLI examples before PowerShell in all code tabs and sections, as CLI is cross-platform and preferred for Linux/macOS users.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, to reassure non-Windows users.
  • Add a short note at the start of each code section clarifying that both CLI and PowerShell are supported and that CLI is recommended for Linux/macOS.
  • Where screenshots are shown for Azure portal, consider adding CLI command equivalents as callouts for parity.
  • Review and ensure that all PowerShell instructions have direct CLI equivalents and vice versa.
GitHub Create Pull Request
Backup Monitoring and reporting solutions for Azure Backup ...main/articles/backup/monitoring-and-alerts-overview.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by consistently listing Azure PowerShell as the first non-portal client for monitoring and reporting tasks, and referencing PowerShell in examples and links before CLI or REST API. There are no explicit Linux/macOS examples or tool recommendations, and the documentation does not mention cross-platform command-line usage or provide parity guidance for Linux users.
Recommendations
  • Alternate the order of PowerShell and CLI references, or list CLI first in some sections to avoid implicit prioritization of Windows tools.
  • Provide explicit examples for both Azure PowerShell and Azure CLI, noting cross-platform compatibility.
  • Include notes or sections clarifying that all monitoring and reporting tasks can be performed from Linux/macOS using Azure CLI and REST API.
  • Add links to CLI documentation alongside PowerShell links, and mention Bash scripting where relevant.
  • Consider including a table or sidebar summarizing tool parity for Windows, Linux, and macOS users.
GitHub Create Pull Request
Backup Configure Multi-user authorization using Resource Guard .../blob/main/articles/backup/multi-user-authorization.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides command-line examples for both PowerShell and Azure CLI, but PowerShell examples are consistently presented before CLI examples in every section. This ordering implicitly prioritizes Windows tooling and patterns. There are no Linux-specific tools or shell examples (e.g., Bash), nor any mention of platform-specific considerations for Linux/macOS users. However, Azure CLI is cross-platform and the examples are sufficient for non-Windows users to complete all tasks.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid implicit Windows prioritization.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Add a short note or section confirming that all steps and commands are fully supported on Linux/macOS, and that no Windows-specific tooling is required.
  • Consider including Bash script examples or screenshots from Linux/macOS environments for parity.
  • Clarify that PowerShell Core is available cross-platform, if relevant, and provide guidance for Linux/macOS users where appropriate.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Files using Azure CLI ...cles/backup/quick-backup-azure-files-vault-tier-cli.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page is generally cross-platform, focusing on Azure CLI (which is available on Windows, Linux, and macOS). However, there is mild Windows bias: the CLI output example includes a Windows-style command prompt (C:\Users\testuser\Downloads\...), and references to PowerShell and Azure portal alternatives are listed before Linux/macOS equivalents. The prerequisites mention Bash in Azure Cloud Shell, but do not provide explicit Linux/macOS local shell examples or clarify parity for those platforms.
Recommendations
  • Replace or supplement the CLI output example with a Linux/macOS shell prompt (e.g., $ az backup protection enable-for-azurefileshare ...), or clarify that the command works identically on all platforms.
  • Ensure that alternative instructions (e.g., for PowerShell, portal) are listed in a neutral order or explicitly mention Linux/macOS options where relevant.
  • Add a note or section confirming that all CLI commands are fully supported on Linux/macOS, and provide troubleshooting tips for those platforms if needed.
  • Include explicit Linux/macOS installation and usage steps for Azure CLI, not just Docker container instructions.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Files using Azure Terraform ...ackup/quick-backup-azure-files-vault-tier-terraform.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation references both Azure CLI and Azure PowerShell for authentication, but clarifies that only Azure CLI is supported for Terraform authentication. However, Azure PowerShell is mentioned first in several places, and the 'Next steps' section lists PowerShell before CLI and REST API, suggesting a Windows-centric ordering. There are no explicit Linux/macOS examples, nor are Linux-specific tools or shell commands referenced. The documentation is generally cross-platform due to the use of Terraform and Azure CLI, but the ordering and emphasis show a mild Windows bias.
Recommendations
  • List Azure CLI before Azure PowerShell when describing authentication and management options, as CLI is cross-platform.
  • Explicitly mention that all commands (terraform, Azure CLI) work on Linux/macOS and Windows.
  • Add a note or section confirming Linux/macOS compatibility and provide links to installation guides for those platforms.
  • When listing management options (e.g., in 'Next steps'), alternate or randomize the order of PowerShell and CLI, or group cross-platform tools together.
GitHub Create Pull Request
Backup Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Server using a Terraform template ...p/quick-backup-postgresql-flexible-server-terraform.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions Azure PowerShell and the Azure portal as primary clients for backup management before mentioning CLI and other options. There is a specific note clarifying that authentication for Terraform is only supported via Azure CLI, not PowerShell, but PowerShell is still referenced as a tool for Terraform work. No explicit Linux/macOS examples or considerations are given, and the order of tool presentation favors Windows-centric tools.
Recommendations
  • Present Azure CLI and cross-platform tools before Windows-specific tools like PowerShell and Azure portal.
  • Add explicit guidance or examples for Linux/macOS users, such as shell commands or environment setup notes.
  • Clarify that all steps are cross-platform unless otherwise noted, and avoid unnecessary references to Windows-only tools.
  • Include troubleshooting steps or links relevant to Linux/macOS environments.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Blobs using Azure CLI .../main/articles/backup/quick-blob-vaulted-backup-cli.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page shows mild Windows bias by referencing Azure PowerShell and linking to PowerShell-based instructions before or alongside CLI/REST API options. The link to create a Backup vault points to a PowerShell-based guide, and PowerShell is mentioned as a restore option before CLI and REST API. There are no explicit Linux/macOS examples or mentions, and the documentation does not clarify cross-platform compatibility for the CLI commands.
Recommendations
  • Provide direct links to Linux/macOS instructions or clarify that Azure CLI commands work identically across platforms.
  • Ensure that all referenced guides (such as creating a Backup vault) have CLI-based instructions, not just PowerShell.
  • List CLI and REST API options before PowerShell when presenting alternatives, to avoid Windows-first ordering.
  • Explicitly mention platform compatibility in prerequisites and examples.
GitHub Create Pull Request
Backup Quickstart - Install Azure Backup extension in an AKS cluster ...main/articles/backup/quick-install-backup-extension.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides instructions exclusively for the Azure portal UI, which is platform-agnostic, but it does not show any command-line examples (Azure CLI, PowerShell, etc.) for installing the backup extension. The 'Next steps' section lists Azure PowerShell before Azure CLI, which is more commonly used on Linux/macOS. There are no explicit Linux/macOS-specific instructions or examples, and no mention of Linux tools or shell commands.
Recommendations
  • Add explicit Azure CLI instructions for installing the backup extension, as CLI is cross-platform and preferred by many Linux/macOS users.
  • If PowerShell examples are provided, ensure Azure CLI examples are shown first or side-by-side.
  • Include screenshots or notes clarifying that the Azure portal is accessible from any OS/browser.
  • Add a note or section for Linux/macOS users, confirming that all steps are platform-neutral or providing any necessary OS-specific guidance.
GitHub Create Pull Request
Backup Restore Azure Managed Disks ...ocs/blob/main/articles/backup/restore-managed-disks.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides parity between Windows and Linux for disk attachment and OS disk swap instructions, but Windows instructions and links are presented before Linux equivalents in the section on using restored disks with virtual machines. No PowerShell-heavy or Windows-only examples are present, and Linux instructions are included, but the ordering favors Windows.
Recommendations
  • Present Windows and Linux instructions in parallel or alternate the order to avoid implicit prioritization.
  • Consider grouping OS-specific instructions under clear subheadings (e.g., 'For Windows VMs', 'For Linux VMs') to make parity explicit.
  • Ensure that any screenshots or examples are balanced between Windows and Linux scenarios if applicable.
GitHub Create Pull Request
Backup Tutorial - Restore a VM with Azure CLI ...ocs/blob/main/articles/backup/tutorial-restore-disk.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page is focused on Azure CLI and restoring VMs, and provides examples and instructions that are generally cross-platform. However, there is a notable Windows bias in the introductory section, where PowerShell is mentioned as an alternative and linked before any Linux-specific alternatives. Additionally, references to VM types and restore scenarios sometimes link to Windows-specific documentation (e.g., zone-pinned VMs link to a Windows VM creation guide). There are no Linux-specific examples or explicit parity checks, and Windows terminology/tools are referenced first or exclusively in some places.
Recommendations
  • Add explicit references to Linux/macOS alternatives when mentioning PowerShell, such as Bash scripts or Linux CLI usage.
  • Ensure links to VM creation or zone-pinning guides include both Windows and Linux VM documentation.
  • Provide examples or notes for restoring Linux VMs, especially if there are differences in restore steps or requirements.
  • Avoid mentioning Windows tools (PowerShell) before cross-platform tools unless contextually necessary.
  • Include a parity checklist or table for supported platforms and any known limitations.
GitHub Create Pull Request
Backup About agentless multi-disk crash-consistent backup for Azure Virtual Machines by using Azure Backup ...ure-vms-agentless-multi-disk-crash-consistent-overview.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references Windows-specific backup tools (Volume Shadow Copy Service - VSS) before mentioning the Linux equivalent (fsfreeze), and links to Windows VM agent/extensions before Linux equivalents. Windows terminology and tools are presented first, and Linux examples or links are less prominent.
Recommendations
  • Present Linux and Windows tools in parallel (e.g., 'VSS (Windows) or fsfreeze (Linux)'), or alternate which is mentioned first.
  • Include links to both Windows and Linux VM agent documentation, not just Windows.
  • Add explicit examples or references for Linux VM backup scenarios, including relevant commands or extension links.
  • Ensure parity in documentation structure and detail for both platforms.
GitHub Create Pull Request
Backup Quickstart - Configure vaulted backup for Azure Blobs using Azure Backup ...ob/main/articles/backup/blob-backup-configure-quick.md
Low 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 references Azure PowerShell before Azure CLI and REST API in the 'Next step' section, suggesting a Windows-first approach. While Azure CLI is mentioned, there are no explicit Linux/macOS examples or guidance, and PowerShell is traditionally associated with Windows environments.
Recommendations
  • Provide explicit Linux/macOS instructions or examples, especially for Azure CLI usage.
  • Ensure CLI examples are shown before or alongside PowerShell examples to signal cross-platform parity.
  • Clarify that Azure CLI works natively on Linux/macOS and provide installation links.
  • Include notes on using PowerShell Core on Linux/macOS if PowerShell is required.
GitHub Create Pull Request
Backup Quickstart - Back up a VM with the Azure portal by using Azure Backup ...cs/blob/main/articles/backup/quick-backup-vm-portal.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page generally maintains cross-platform parity, but there is a minor Windows bias in the 'create a VM' link, which points to the Windows VM creation guide before mentioning Linux alternatives. The VM agent installation instructions are presented in parallel for Windows and Linux, with no clear preference or omission. No PowerShell-heavy, Windows-only tools, or missing Linux examples are found.
Recommendations
  • Provide both Windows and Linux VM creation links in the introductory section, or link to a platform-neutral VM creation guide.
  • Ensure that any screenshots or UI references do not assume Windows-specific VM configurations.
  • Continue to present agent installation instructions for both platforms side-by-side, as done here.
GitHub Create Pull Request
Backup Restore Azure Managed Disks ...ocs/blob/main/articles/backup/restore-managed-disks.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides parity between Windows and Linux for disk attachment and OS disk swap instructions, but consistently lists Windows instructions before Linux instructions. No PowerShell-heavy or Windows-only examples are present, and Linux guidance is included. The order may subtly signal a preference for Windows users.
Recommendations
  • Alternate the order in which Windows and Linux instructions are presented, or present them side-by-side.
  • Explicitly state that instructions apply equally to both Windows and Linux, where applicable.
  • Ensure that screenshots and examples reflect both Windows and Linux environments where possible.
GitHub Create Pull Request
Backup Quickstart - Configure backup for Azure Database for PostgreSQL - Flexible Server using a Terraform template ...p/quick-backup-postgresql-flexible-server-terraform.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions Azure PowerShell and the Azure portal as primary clients for Azure Backup, listing them before the Azure CLI. It also clarifies that Terraform authentication is only supported via Azure CLI, not PowerShell, but still references PowerShell as a tool for Terraform work. No explicit Linux/macOS examples or tools are highlighted, and the ordering of tools may suggest a Windows-first perspective.
Recommendations
  • List cross-platform tools (Azure CLI, Terraform) before Windows-specific tools (PowerShell, Azure portal) when describing supported clients.
  • Explicitly mention Linux/macOS compatibility and provide links to platform-specific setup guides for Terraform and Azure CLI.
  • Remove or clarify references to PowerShell in the context of Terraform, emphasizing that CLI is the supported method for all platforms.
  • Add a note or section confirming that all steps are platform-agnostic and can be performed on Linux/macOS as well as Windows.
GitHub Create Pull Request
Backup Azure Backup - Archive tier overview ...docs/blob/main/articles/backup/archive-tier-support.md
Low 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 lists PowerShell as a supported client before CLI, and references PowerShell-specific pivots in usage instructions. There are no explicit Linux/macOS examples or mentions of Bash, nor are Linux-specific tools or patterns referenced. The examples and screenshots are generic and do not show OS-specific commands, but the ordering and client emphasis suggest a mild Windows bias.
Recommendations
  • List CLI (az) before PowerShell in supported clients and usage instructions to reflect cross-platform parity.
  • Provide explicit Bash/Linux/macOS command examples alongside PowerShell, especially in usage guides.
  • Clarify that all operations can be performed via CLI on Linux/macOS, and link to relevant cross-platform documentation.
  • Include screenshots or walkthroughs from Linux/macOS environments where applicable.
GitHub Create Pull Request
Backup Azure Backup glossary ...ocs/blob/main/articles/backup/azure-backup-glossary.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The glossary page shows mild Windows bias, mainly through frequent references to Windows-specific backup tools (DPM, MABS, MARS Agent, VSS) and by listing Azure PowerShell before Azure CLI in the tooling section. The VSS (Windows Volume Shadow Copy Service) is described in detail, while Linux equivalents are only briefly mentioned (e.g., 'pre or post scripts for Linux'). Most backup concepts are platform-neutral, but workload-specific terms and examples lean toward Windows environments.
Recommendations
  • Add explicit references to Linux backup mechanisms (e.g., LVM snapshots, fsfreeze, etc.) where VSS is mentioned.
  • Provide links to Linux/macOS documentation or backup strategies for Azure workloads.
  • Ensure parity in tool listing order (e.g., alternate Azure CLI and PowerShell, or group them together).
  • Clarify which backup features/tools are cross-platform and which are Windows-only.
  • Expand glossary entries for Linux/macOS backup scenarios, especially where Windows tools are highlighted.
GitHub Create Pull Request
Backup Azure Kubernetes Service (AKS) backup using Azure Backup prerequisites ...kup/azure-kubernetes-service-cluster-backup-concept.md
Low 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 mild Windows bias by listing Azure PowerShell as a primary method for backup and restore operations, and by referencing the Azure portal (which is often associated with Windows environments) before mentioning Azure CLI. There are no explicit Linux/macOS command-line examples, nor any mention of Linux-specific tools or shell usage. The documentation does not provide parity in example commands for Linux/macOS users, and the ordering of instructions and links tends to favor Windows-centric tools.
Recommendations
  • Add explicit Linux/macOS command-line examples using Azure CLI and kubectl where appropriate.
  • Ensure that Azure CLI instructions are presented before or alongside Azure PowerShell and portal instructions.
  • Clarify that all operations can be performed from Linux/macOS environments using Azure CLI and kubectl.
  • Include notes or sections for Linux/macOS users, highlighting any OS-specific considerations or differences.
  • Balance the presentation of Azure PowerShell and Azure CLI in 'Next steps' and throughout the documentation.
GitHub Create Pull Request
Backup What is Azure Kubernetes Service (AKS) Backup? ...les/backup/azure-kubernetes-service-backup-overview.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page does not provide explicit command-line examples or tooling instructions within its main content, but in the 'Related content' section, the PowerShell (Windows) backup guide is listed before the Azure CLI (cross-platform) restore guide. This ordering may subtly suggest a Windows-first approach. No direct PowerShell-heavy content, Windows-only tools, or missing Linux examples are present in the main body.
Recommendations
  • List cross-platform tools (such as Azure CLI) before or alongside Windows-specific tools (PowerShell) in the 'Related content' section.
  • Ensure that any future example commands or walkthroughs include both Azure CLI and PowerShell, with clear indications of platform compatibility.
  • Explicitly state that Azure CLI is available and supported on Linux/macOS, and provide links to installation guides for those platforms.
  • If possible, add a section summarizing platform parity and clarifying that all backup/restore operations can be performed from Linux/macOS as well as Windows.
GitHub Create Pull Request
Backup Troubleshoot Azure Kubernetes Service backup ...backup/azure-kubernetes-service-backup-troubleshoot.md
Low 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 consistently presents troubleshooting and operational steps using the Azure portal UI and Azure CLI, which are cross-platform, but does not provide any Windows-specific tools or PowerShell examples. However, there is a notable bias in that all portal screenshots and step-by-step instructions use the Azure portal, which is identical across platforms but often associated with Windows workflows. There are no explicit Linux/macOS-specific instructions, nor any mention of Linux-native tools or shell scripting. CLI examples use az and kubectl, which are cross-platform, but there are no examples of Linux-specific troubleshooting patterns (e.g., using grep, tail, less, or bash scripting for log analysis). The documentation does not mention PowerShell, Windows CMD, or Windows-only tools, but the ordering and UI focus may create minor friction for Linux users.
Recommendations
  • Add explicit notes confirming that all CLI commands (az, kubectl) work identically on Linux, macOS, and Windows.
  • Include Linux/macOS-specific troubleshooting tips, such as using grep, tail, less, or bash scripting for log analysis.
  • Provide example commands for common Linux shell environments (e.g., bash, zsh) when referencing log review or file manipulation.
  • Clarify that the Azure portal UI is platform-agnostic and accessible from any OS.
  • If possible, add screenshots or instructions for using CLI-only workflows for users who prefer not to use the portal.
GitHub Create Pull Request
Backup Back up Azure Database for PostgreSQL - Flexible Server using Azure CLI ...p/back-up-azure-database-postgresql-flex-backup-cli.md
Low 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 is generally cross-platform, focusing on Azure CLI commands, which are available on Windows, Linux, and macOS. However, there is a notable Windows bias in the example for submitting the backup request, where the file path is given in Windows format ('.\OSSBkpInstance.JSON') rather than a cross-platform or Linux/macOS format ('./OSSBkpInstance.JSON'). There are no explicit Linux/macOS examples or notes about platform differences, and the documentation does not mention shell-specific considerations (e.g., PowerShell vs. Bash) except for one brief note that 'the following example uses bash'.
Recommendations
  • Use cross-platform file path syntax in examples (e.g., './OSSBkpInstance.JSON') or provide both Windows and Linux/macOS variants.
  • Explicitly state that Azure CLI commands work on Windows, Linux, and macOS.
  • Add notes or examples for Linux/macOS users where shell or path differences may occur.
  • Avoid Windows-centric syntax unless necessary, and clarify when it is used.
GitHub Create Pull Request
Backup Azure Kubernetes Service (AKS) backup support matrix ...azure-kubernetes-service-cluster-backup-support-matrix.md
Low 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 references Azure PowerShell as a supported method for backup and restore, which is primarily a Windows tool. In the 'Next steps' section, Azure PowerShell is listed alongside Azure CLI, ARM, Bicep, and Terraform, but there is no explicit mention of Linux/macOS-specific instructions or parity for PowerShell usage. The documentation does not provide examples or guidance for Linux/macOS users regarding PowerShell, nor does it clarify whether all features are available via CLI or other cross-platform tools. Additionally, while the documentation states that the Backup Extension can only be installed on Ubuntu or Azure Linux node pools (and not Windows-based node pools), this is a technical limitation rather than a documentation bias.
Recommendations
  • Clarify in the documentation whether Azure PowerShell commands can be run on Linux/macOS (via PowerShell Core), or provide explicit instructions/examples for Linux/macOS users.
  • Ensure that all CLI examples are shown before or alongside PowerShell examples, emphasizing cross-platform compatibility.
  • Add a note or section highlighting that the backup extension is Linux-only, and provide guidance for users who may be running mixed OS clusters.
  • Where possible, provide parity in examples and instructions for Linux/macOS users, especially for scripting and automation tasks.
GitHub Create Pull Request
Backup Restore Azure VMs using REST API .../backup/backup-azure-arm-userestapi-restoreazurevms.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Os Type Windows In Examples
Summary
The documentation is generally platform-neutral, focusing on REST API calls and JSON request/response bodies, which are inherently cross-platform. However, there is mild Windows bias in the example responses: in the Cross Region Restore section, the 'osType' and 'OsType' fields are set to 'Windows' in all sample recovery points and metadata. There are no explicit Linux or macOS examples, nor is there mention of Linux-specific restore scenarios or considerations. No PowerShell, Windows command-line, or Windows-only tooling is referenced, and all instructions are generic HTTP/JSON, suitable for any OS.
Recommendations
  • Include example recovery points and restore requests for Linux VMs (e.g., with 'osType': 'Linux').
  • Add a note clarifying that the REST API applies equally to Windows and Linux VMs, and highlight any differences if they exist.
  • If there are Linux-specific restore considerations (e.g., file system, bootloader, encryption), mention them.
  • Ensure that sample responses and request bodies alternate or include both Windows and Linux VM scenarios.
GitHub Create Pull Request
Backup Back Up Azure VMs in a Recovery Services Vault ...b/main/articles/backup/backup-azure-arm-vms-prepare.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation generally presents a platform-neutral workflow for backing up Azure VMs, with both Windows and Linux supported. However, in the 'Install the VM agent' section, Windows installation instructions are listed first and in greater detail, including explicit verification steps and links, while Linux instructions are more general and lack step-by-step guidance. No PowerShell or Windows-specific tools are mentioned elsewhere, and most instructions are portal-based and cross-platform.
Recommendations
  • Present Linux and Windows agent installation instructions in parallel, with equal detail and verification steps for both.
  • Include explicit Linux verification steps (e.g., checking agent version via command line).
  • If possible, alternate the order of Windows and Linux instructions or present them side-by-side.
  • Add links to Linux agent update instructions and troubleshooting, similar to Windows.
  • Ensure screenshots and examples are not Windows-centric if CLI examples are added in future.
GitHub Create Pull Request
Backup Create Backup Policies for PostgreSQL Databases by Using the Data Protection REST API ...rotection-use-rest-api-create-update-postgresql-policy.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias by referencing PowerShell objects and patterns as the default or primary way to conceptualize backup policy objects. There are no explicit Linux/macOS examples or CLI references, and the only tooling mentioned is PowerShell, which is traditionally associated with Windows. However, the main workflow uses REST API calls and JSON payloads, which are cross-platform.
Recommendations
  • Remove or rephrase references to 'default PowerShell object' and instead describe the policy object in generic, platform-neutral terms.
  • Add example commands using Azure CLI (az dataprotection ...) for creating or managing backup policies, which are natively supported on Linux/macOS.
  • Explicitly state that the REST API and JSON payloads can be used from any OS, and provide sample curl commands for Linux/macOS users.
  • If scripting is discussed, provide Bash or shell script examples alongside PowerShell, or avoid platform-specific scripting references altogether.
GitHub Create Pull Request
← Previous Page 20 of 21 Next →