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 251-275 of 520 flagged pages
Backup
Support matrix for Azure VM backups
...lob/main/articles/backup/backup-support-matrix-iaas.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides comprehensive coverage of both Windows and Linux VM backup scenarios, but there are several areas of Windows bias. Windows-specific tools (MARS agent, DPM, MABS) are described in detail, with examples and restore instructions often referencing PowerShell and Windows workflows. Linux support is present but less detailed, with some features (e.g., file-level backup via MARS agent, DPM/MABS integration) unavailable for Linux, and Linux restore instructions lacking parity in example depth. Windows examples and tools are frequently mentioned first or exclusively, while Linux alternatives are not always provided or are described as unsupported.
Recommendations
- Where PowerShell or Windows tool examples are given for restore or backup operations, provide equivalent CLI or script examples for Linux (e.g., using Azure CLI, Bash).
- Clarify in each section whether a feature is Windows-only, and if so, suggest Linux alternatives or workarounds where possible.
- Expand Linux backup and restore documentation to include more detailed workflows and troubleshooting steps, similar to the Windows sections.
- Add explicit notes or links to Linux-specific backup and restore guides in the 'Next steps' and throughout the page.
- Where features are unsupported for Linux, provide guidance or references to alternative backup strategies for Linux VMs.
Create Pull Request
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Windows and Linux coverage in its scope and introductory statements. However, in the main restore workflow, it gives explicit PowerShell-based instructions for creating a VM from restored disks, without offering an equivalent CLI or portal example suitable for Linux/macOS users. The only Linux-specific guidance is relegated to a later section, and focuses on re-installing the ADE extension, not the core restore workflow. There is also a direct link to a Windows-specific disk swap operation. This creates friction for Linux users who may not use PowerShell or Windows-centric tools.
Recommendations
- Add Azure CLI and/or Azure Portal instructions for creating a VM from restored disks, alongside or before the PowerShell example.
- Provide explicit Linux/macOS-compatible command examples for all major steps, especially VM creation from restored disks.
- Ensure that links to further reading (e.g., OS disk swap) include both Windows and Linux variants where available.
- Consider reordering sections so Linux-specific steps are not separated or treated as an afterthought.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. While the main restore workflow is platform-agnostic (since Azure VMs can be Windows or Linux), many example links, references, and instructions prioritize or exclusively mention Windows tools, PowerShell, or Windows-specific guidance. Linux equivalents are rarely mentioned, and Linux-specific restore scenarios are not illustrated. Some post-restore steps and advanced scenarios reference Windows-centric tools and workflows, with only brief or indirect Linux guidance.
Recommendations
- Where PowerShell is referenced for VM creation or disk attachment, add Azure CLI and/or ARM template examples, especially for Linux users.
- When linking to guides for attaching disks, creating VMs, or configuring network settings, include both Windows and Linux documentation (e.g., /azure/virtual-machines/linux/attach-disk-portal alongside the Windows link).
- In post-restore steps, provide explicit Linux guidance for common tasks such as resetting SSH keys, reconfiguring network settings, or handling cloud-init password issues.
- For advanced restore scenarios (e.g., restoring domain controllers, special network configurations), clarify when guidance is Windows-specific and provide Linux alternatives where applicable.
- Review all code snippets and command-line instructions to ensure parity between Windows (PowerShell/CMD) and Linux (Bash/CLI) environments.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page for Azure Backup architecture shows a notable Windows bias in its coverage of on-premises backup scenarios and agent tooling. Windows backup methods (MARS agent, DPM/MABS) are described in detail, with explicit statements that Linux machines aren't supported for direct backup via MARS. There are no Linux-specific examples, agents, or equivalent tooling mentioned for on-premises backup, and Windows tools are introduced first and exclusively for these scenarios. Azure VM backup is described in a platform-neutral way, but on-premises backup coverage is Windows-centric.
Recommendations
- Clearly state Linux backup limitations and provide links or references to alternative solutions for Linux on-premises backup, if available (e.g., third-party tools, Azure File Sync, or native Linux backup to Azure Blob Storage).
- Add a comparison table or section outlining backup options for Linux on-premises machines, even if only to clarify that direct backup is not supported and suggest alternatives.
- Where possible, include parity in examples and workflows for Linux VMs in Azure (e.g., mention that the Azure VM backup extension works for both Windows and Linux VMs).
- Consider reordering sections so that platform-neutral Azure VM backup is described before Windows-only on-premises backup methods.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides general guidance for restoring Azure VMs using the portal and templates, but several example links and instructions reference Windows-specific pages and PowerShell, especially for creating VMs from restored disks and configuring network settings. Linux-specific instructions, examples, or links are notably absent, and Windows documentation is referenced first or exclusively in several places.
Recommendations
- Add explicit Linux VM restore examples, including links to Linux-specific documentation for attaching disks, creating VMs from restored disks, and configuring network settings.
- Where PowerShell is referenced for VM creation or configuration, also provide equivalent Azure CLI or portal instructions applicable to Linux VMs.
- Ensure links to tutorials and guides for availability sets, network configuration, and VM creation include both Windows and Linux variants, or clarify when instructions are OS-agnostic.
- In sections referencing post-restore steps (e.g., resetting passwords, VM agent installation), provide Linux-specific guidance and links, such as using cloud-init, SSH, and troubleshooting Linux VM agent issues.
Backup
Back Up and Restore Encrypted Azure VMs
...ob/main/articles/backup/backup-azure-vms-encryption.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation generally covers both Windows and Linux Azure VMs with encrypted disks, referencing both ADE (BitLocker for Windows, dm-crypt for Linux) and platform/customer-managed keys. However, in the 'Provide permissions' section, the example for identifying a VM's associated Key Vault is given only in PowerShell, with no equivalent Azure CLI or Bash example. Additionally, the PowerShell example appears before mentioning that Azure CLI can also be used, which may create friction for Linux/macOS users who are less likely to use PowerShell.
Recommendations
- Add Azure CLI and Bash examples alongside PowerShell for tasks such as identifying a VM's associated Key Vault.
- Where automation or scripting is referenced, provide both PowerShell and Azure CLI/Bash commands, or link to equivalent instructions.
- When listing tools or commands, avoid presenting Windows/PowerShell options first unless there is a technical reason.
- Explicitly state that all steps can be performed on both Windows and Linux, and clarify any OS-specific differences.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation covers restoring both Windows and Linux encrypted Azure VMs, but there is a notable Windows bias. In the 'Recreate the virtual machine instance' section, only a PowerShell-based method is explicitly mentioned for creating a VM from restored disks, with no Linux/CLI/Bash equivalent. Additionally, the disk swap example links to a Windows-specific article. The Linux-specific restore steps are separated into a later section, and there is no example or command-line guidance for Linux users to automate VM recreation.
Recommendations
- Add Azure CLI and/or Bash examples for recreating a VM from restored disks, especially for Linux users.
- Provide parity in automation guidance for Linux, not just PowerShell.
- When referencing disk swap operations, include links or instructions for both Windows and Linux VMs.
- Reorganize sections so that Linux and Windows guidance is presented with equal prominence, or clarify when steps are OS-agnostic.
Backup
Support matrix for Azure VM backups
...lob/main/articles/backup/backup-support-matrix-iaas.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a comprehensive support matrix for Azure VM backups, covering both Windows and Linux. However, there is a notable Windows-first bias: Windows scenarios, tools (such as MARS agent, DPM, MABS), and PowerShell are mentioned first and in more detail. Linux support is described separately and is more limited, with several backup/restore methods (e.g., MARS agent, DPM/MABS) not supported for Linux. Some restore instructions reference PowerShell without mentioning Linux CLI equivalents. Linux examples and parity are less prominent, and some advanced backup features are Windows-only.
Recommendations
- Where PowerShell is mentioned for restore or backup operations, add equivalent Azure CLI or Bash examples for Linux users.
- When listing supported scenarios or tools, present Windows and Linux options together, or clarify up front which are Windows-only and which are cross-platform.
- Expand Linux sections to include more detailed guidance, especially for restore scenarios and file-level restore limitations.
- Clearly indicate in each scenario/table which features are Windows-only, Linux-only, or cross-platform, to reduce ambiguity.
- Where possible, provide workarounds or alternatives for Linux users when a feature is not supported.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is primarily focused on Azure CLI usage, which is cross-platform. However, there are several instances of Windows bias: PowerShell objects and file paths are referenced first or exclusively (e.g., '.\OSSPolicy.json'), and the 'default PowerShell object' is described before CLI equivalents. The documentation assumes a Windows/PowerShell environment for file manipulation and command syntax, which may cause confusion or friction for Linux/macOS users.
Recommendations
- When referencing file paths, use platform-neutral syntax (e.g., './OSSPolicy.json') or provide both Windows ('.\file.json') and Linux/macOS ('./file.json') examples.
- Avoid describing PowerShell objects as the default or primary method unless the documentation is specifically for PowerShell. Instead, focus on CLI and JSON file manipulation, which are cross-platform.
- If mentioning PowerShell objects, immediately follow with equivalent Linux/macOS or Bash-based approaches.
- Explicitly state that all Azure CLI commands work on Windows, Linux, and macOS, and clarify any OS-specific differences in file handling or command usage.
- Add notes or examples for common Linux/macOS shell usage, such as using 'mv' instead of 'rename', or using '/' as the path separator.
Backup
Quick start - Back up Azure Database for PostgreSQL server
...cles/backup/quick-backup-postgresql-database-portal.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation references PowerShell scripts as the primary method for granting privileges to database users, both in the prerequisites and during the backup configuration process. While it briefly mentions alternatives like PG admin or PSQL, these are only listed as secondary options after PowerShell. There are no concrete examples or scripts provided for Linux/macOS users, and PowerShell is presented first and most prominently.
Recommendations
- Provide explicit examples for granting privileges using psql (the standard PostgreSQL CLI tool available on Linux/macOS) alongside PowerShell.
- List cross-platform or Linux-native tools (e.g., psql, bash scripts) before or alongside PowerShell in both the prerequisites and step-by-step instructions.
- Include sample commands for both PowerShell and psql/PG admin where privilege assignment is required.
- Clarify that PowerShell is not required and that all steps can be performed using platform-agnostic tools.
Backup
Tutorial - Back up Azure Database for PostgreSQL server
...lob/main/articles/backup/tutorial-postgresql-backup.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page for backing up Azure Database for PostgreSQL server demonstrates a moderate Windows bias. It references PowerShell scripts as the primary method for granting database privileges, with alternatives (PG admin or PSQL tool) mentioned only secondarily and without example commands. No explicit Linux/macOS CLI examples or screenshots are provided, and the workflow assumes use of the Azure portal, which is cross-platform but does not address OS-specific command-line tooling. The PowerShell approach is presented first and in detail, while Linux-native tools are only briefly referenced.
Recommendations
- Provide explicit example commands for granting database privileges using psql (Linux/macOS) and pgAdmin, alongside the PowerShell script.
- Clarify that the PowerShell script can be run on Linux/macOS using PowerShell Core, or provide equivalent bash/psql scripts.
- Add screenshots or step-by-step instructions for using Linux/macOS tools where applicable.
- Ensure that any ARM template or automation instructions are OS-agnostic or include Linux/macOS usage notes.
Backup
Delete a Microsoft Azure Recovery Services Vault
...blob/main/articles/backup/backup-azure-delete-vault.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation exhibits a notable Windows bias. PowerShell is the primary automation example, with extensive PowerShell cmdlets and scripts provided, and explicit instructions for installing PowerShell 7. Windows-specific backup management tools (MARS, MABS, DPM) are referenced throughout, with GUI instructions for their consoles. The ARMClient tool is suggested for advanced deletion, but its installation is described only via Chocolatey (a Windows package manager), and usage examples are Windows-centric. The Azure CLI section is brief, limited in scope, and notes that CLI support is incomplete. There are no Bash, Linux-native, or macOS-specific examples or guidance for users who do not use Windows or PowerShell.
Recommendations
- Provide equivalent Bash/Azure CLI scripts for all major operations, especially for deleting backup items and vaults.
- Clarify how to perform all steps on Linux/macOS, including how to install and use ARMClient on those platforms (e.g., via .NET Core or as a cross-platform tool).
- Mention and prioritize cross-platform tools (like Azure CLI) before Windows-specific tools, or at least present them in parallel.
- Add guidance for managing Recovery Services vaults using the Azure Portal and Azure CLI for all supported backup types, not just Azure VMs.
- Where PowerShell is used, clarify that PowerShell Core (v7+) is cross-platform, and provide installation instructions for Linux/macOS.
- If certain features are Windows-only (e.g., MARS, MABS, DPM), clearly state this and suggest alternatives for Linux/macOS users.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. Windows-specific backup mechanisms (VSS) are described in detail before Linux equivalents, and PowerShell is mentioned as the tool for restoring managed disks, with no Linux CLI or Bash alternatives provided. Linux backup consistency relies on custom scripting, but no example scripts or guidance are given, whereas Windows VSS is explained thoroughly. The documentation generally presents Windows approaches first and in more depth.
Recommendations
- Provide equivalent CLI/Bash examples for Linux users, especially for restore operations currently described only with PowerShell.
- Include sample pre/post scripts for Linux VM application-consistent backups, or link to such resources.
- Present Windows and Linux instructions side-by-side or in parallel sections to avoid Windows-first ordering.
- Mention cross-platform tools (e.g., Azure CLI) for backup and restore tasks, with examples for both OSes.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell deployment instructions and referencing PowerShell modules in the prerequisites. There are no Linux/macOS CLI examples, and the deployment workflow is tailored to Windows users (e.g., right-click to paste in shell window). This creates friction for Linux/macOS users who typically use Azure CLI or Bash.
Recommendations
- Add Azure CLI deployment instructions alongside PowerShell, with equivalent parameter prompts and resource creation steps.
- Update prerequisites to mention both Azure PowerShell and Azure CLI, with links to installation guides for each.
- Replace or supplement Windows-specific instructions (e.g., right-click to paste) with cross-platform guidance (e.g., use Ctrl+Shift+V in Linux terminals).
- Clearly indicate that both PowerShell and CLI are supported, and provide parity in example scripts.
Backup
Restore Azure Kubernetes Service (AKS) using Azure Backup
...les/backup/azure-kubernetes-service-cluster-restore.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page references Azure PowerShell as an alternative method for restoring AKS clusters and links to a PowerShell-specific guide, but does not mention or provide examples for Linux/macOS command-line tools (such as Azure CLI or Bash scripts). The main restore workflow is described via the Azure Portal UI, which is cross-platform, but the only programmatic example referenced is Windows-centric. There is no mention of Linux/macOS equivalents or parity in automation approaches.
Recommendations
- Add references and examples for restoring AKS clusters using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Ensure that any linked guides (such as the PowerShell guide) have equivalent Azure CLI or Bash script documentation.
- Explicitly mention that the Azure Portal workflow is OS-agnostic, and clarify any steps that may differ for Linux/macOS users.
- Where automation is discussed, provide both PowerShell and CLI examples side-by-side.
Backup
Azure Resource Manager and Bicep files
...lob/main/articles/backup/backup-rm-template-samples.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page lists Azure Resource Manager and Bicep templates for Azure Backup features. While most templates are platform-agnostic, one template specifically highlights deploying a Windows Server VM with backup enabled, without mentioning Linux VM equivalents or providing parity. Additionally, the Windows example appears before any mention of Linux, which is absent.
Recommendations
- Add equivalent templates and examples for deploying and backing up Linux VMs, such as Ubuntu or CentOS, alongside the Windows Server VM example.
- Explicitly state that the templates are platform-agnostic where applicable, and clarify any platform-specific limitations.
- Ensure that examples for Linux are provided and are given equal prominence as Windows examples.
- Where a template is Windows-specific, explain why and provide guidance for Linux users.
Backup
Azure Backup - Archive tier overview
...docs/blob/main/articles/backup/archive-tier-support.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation lists PowerShell as a supported client before CLI, and references PowerShell-specific pivots in links. There are no explicit Linux/macOS examples or mentions of Linux-specific tools or patterns. The use of PowerShell as a primary automation example may create friction for Linux/macOS users, though Azure CLI is also listed as supported.
Recommendations
- Ensure that CLI examples are provided alongside PowerShell examples, especially for automation tasks.
- List CLI and PowerShell clients together, or alternate their order to avoid Windows-first perception.
- Explicitly mention Linux/macOS support and provide guidance or examples for those platforms.
- Where screenshots or walkthroughs are given, include CLI-based steps and outputs.
- Clarify that all features are equally available via CLI on Linux/macOS, and note any exceptions.
Backup
Back up Azure Kubernetes Service (AKS) using Azure CLI
...p/azure-kubernetes-service-cluster-backup-using-cli.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation is largely cross-platform, focusing on Azure CLI commands which work on Windows, Linux, and macOS. However, there is evidence of Windows bias in the private endpoint creation section, where PowerShell-style syntax (backticks for line continuation and variable assignment with $) is used, which is specific to Windows PowerShell. Additionally, the example for fetching the subnet ID and creating a private endpoint uses PowerShell conventions, potentially confusing Linux/macOS users. The mention of Azure PowerShell as an alternative is given early, but no Linux shell equivalents are provided for the PowerShell-specific examples.
Recommendations
- Provide bash/zsh equivalents for all PowerShell-specific examples, especially for private endpoint creation and variable assignment.
- Use cross-platform syntax for line continuation (e.g., \ for bash) and variable assignment (e.g., var=value for bash).
- Clearly indicate which examples are platform-specific and offer alternatives for Linux/macOS users.
- Consider showing bash examples first or side-by-side with PowerShell to avoid Windows-first impression.
Backup
Private Endpoints Overview: Version 2 Experience
...icles/backup/backup-azure-private-endpoints-concept.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It repeatedly references Windows-specific backup tools (MARS agent, DPM, MABS) and scenarios, with little to no mention of Linux backup agents or workflows. Examples and recommendations are centered around Windows workloads (SQL Server, SAP HANA in Azure VMs, MARS agent, DPM), and there is no guidance for Linux VM backup or restore operations, nor are Linux-specific tools or commands referenced. The documentation assumes the use of Windows-centric backup solutions and does not provide parity for Linux users.
Recommendations
- Include explicit examples and guidance for Linux VM backup and restore operations using private endpoints.
- Mention Linux backup agents (such as Azure Backup for Linux VMs) and clarify their compatibility or limitations with private endpoints.
- Provide Linux command-line examples (e.g., using Azure CLI, shell scripts) alongside or before Windows/Powershell examples.
- Reference Linux-specific considerations for DNS configuration, agent installation, and network connectivity.
- Clarify whether private endpoints support Linux workloads and agents, and if not, document workarounds or alternatives.
Backup
Troubleshoot Azure Backup failures caused by agent or extension issues
...up-azure-troubleshoot-vm-backup-fails-snapshot-timeout.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows troubleshooting steps, tools, and examples (services.msc, Control Panel, Event Viewer, regsvr32.exe, .NET, Visual C++ Redistributable, AppLocker) are described in detail, often with screenshots and step-by-step instructions. Linux guidance is present but less detailed, with fewer explicit commands, no screenshots, and less coverage of common Linux troubleshooting tools. PowerShell is referenced for job cancellation, but Linux CLI alternatives are not shown. Windows-specific tools and patterns (services.msc, Event Viewer, AppLocker) are mentioned without Linux equivalents, and Windows examples often precede Linux ones.
Recommendations
- Provide Linux-specific troubleshooting steps with equivalent detail, including explicit commands for checking agent status, logs, and extension health.
- Include Linux screenshots or terminal output examples where Windows screenshots are used.
- Mention Linux alternatives for Windows tools (e.g., systemctl for services.msc, journalctl/syslog for Event Viewer, Linux security frameworks for AppLocker).
- Offer CLI examples for job management (e.g., Azure CLI commands for cancelling backup jobs) alongside PowerShell.
- Ensure Linux instructions are presented with equal prominence and detail as Windows instructions, and alternate the order in which OS-specific steps are presented.
Backup
Azure Backup release notes - Archive
.../main/articles/backup/backup-release-notes-archived.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page for Azure Backup release notes shows some evidence of Windows bias. Several features and updates specifically mention Windows-centric tools such as MARS (Microsoft Azure Recovery Services agent), Microsoft Azure Backup Server (MABS), and Windows Server compatibility. These Windows tools are referenced by name and described in detail, while Linux/macOS equivalents are not mentioned or are less prominent. In feature lists, Windows-specific solutions (MARS, MABS) are often listed before Linux-related features, and PowerShell is referenced for automation, with less emphasis on Bash/CLI or cross-platform scripting. However, the page also covers cross-platform workloads (AKS, PostgreSQL, SAP HANA on RHEL), and many features are platform-agnostic.
Recommendations
- Ensure parity by explicitly mentioning Linux/macOS support or alternatives where Windows tools (MARS, MABS) are referenced.
- Provide examples or links for Linux/macOS backup agents or procedures alongside Windows-specific instructions.
- When listing features, alternate the order or group by platform-neutral features first, then platform-specific ones.
- Reference Azure CLI and Bash scripting equally with PowerShell, especially for automation and policy management.
- Add notes or links to documentation for Linux backup scenarios (e.g., Azure Backup for Linux VMs, SAP HANA on Linux) wherever Windows backup tools are discussed.
Backup
Automation in Azure Backup support matrix
...blob/main/articles/backup/backup-support-automation.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation consistently lists PowerShell as a primary automation method for Azure Backup tasks, with 'Supported' and example links for PowerShell in nearly every operation and resource type. PowerShell is a Windows-centric tool, and its presence as the first column in all tables, as well as the frequent use of PowerShell-specific documentation links, signals a Windows-first approach. There is little to no mention of Linux/macOS-specific scripting environments (e.g., Bash, shell scripts), nor any explicit guidance for Linux users on using PowerShell Core cross-platform. The CLI is present and supported, but PowerShell is always listed first and often receives more detailed example links. No Linux-specific tools or patterns are mentioned.
Recommendations
- Reorder columns to list Azure CLI before PowerShell, or alternate the order to avoid implicit prioritization.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Add notes or links about using PowerShell Core on Linux/macOS, if relevant, or clarify any limitations.
- Provide example scripts in Bash/shell where possible, especially for common automation scenarios.
- Include a section or callout for Linux/macOS users describing best practices and tool choices for automation.
- Audit example links to ensure CLI examples are as comprehensive and prominent as PowerShell ones.
Backup
Support matrix for Azure VM backups
...lob/main/articles/backup/backup-support-matrix-iaas.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows tools and backup agents (such as MARS, DPM, and MABS) are described in detail and are supported only for Windows, with Linux support explicitly marked as 'Not supported' in several sections. Windows-specific restore and backup scenarios are often described first or in more detail, and PowerShell is referenced as the default automation tool for restore operations. Linux backup support is present but more limited, with several advanced features (such as file-level backup with agents, DPM/MABS integration, and Docker/ZFS support) unavailable. Linux examples and tools are less emphasized, and Linux users are often directed to generic or OS-agnostic solutions rather than dedicated Linux tooling.
Recommendations
- Provide parity in backup and restore features for Linux VMs, such as agent-based file-level backup and restore.
- Include Linux CLI (az CLI, Bash) examples alongside or before PowerShell examples for restore operations.
- Expand documentation of Linux-specific limitations and workarounds, and offer guidance for common Linux backup scenarios.
- Highlight Linux support and scenarios earlier in the documentation, not just in dedicated Linux sections.
- Where features are Windows-only, clearly state the roadmap or alternatives for Linux users.
Backup
Quickstart - Install Azure Backup extension in an AKS cluster
...main/articles/backup/quick-install-backup-extension.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes installation of the Azure Backup extension in AKS using the Azure portal UI, with screenshots and step-by-step instructions. There are no examples or instructions for command-line installation via Azure CLI, which is the typical approach for Linux/macOS users. The 'Next steps' section mentions CLI, PowerShell, ARM, Bicep, and Terraform, but the main quickstart only covers the portal workflow, which is most commonly used on Windows. This creates friction for Linux/macOS users who may prefer or require CLI-based automation.
Recommendations
- Add parallel instructions for installing the Backup extension using Azure CLI, including example commands.
- Explicitly mention that the portal workflow is cross-platform, but highlight CLI alternatives for Linux/macOS users.
- Include links or inline examples for PowerShell and CLI in the main quickstart, not just in 'Next steps'.
- Clarify any platform-specific requirements or limitations for each installation method.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation for Azure Backup shows a notable Windows bias. Windows backup scenarios (MARS agent, DPM, MABS) are described first and in greater detail, with Linux support often mentioned as 'not supported' or as a secondary note. Windows-specific tools (MARS agent, DPM, MABS) are referenced throughout, while Linux backup options are limited and less prominently featured. There are no Linux-specific examples or guidance for on-premises backup, and agent-based backup is only available for Windows. App-consistent backup for Linux requires custom scripting, which is referenced but not explained in detail here.
Recommendations
- Add Linux-first or Linux-parity examples for backup scenarios, especially for on-premises machines.
- Provide explicit guidance and examples for configuring app-consistent backups on Linux, including links to relevant scripts and best practices.
- Clearly indicate alternatives for Linux users where Windows-only tools (MARS agent, DPM, MABS) are mentioned.
- Reorganize tables and sections to present Windows and Linux support side-by-side, rather than Windows-first.
- Include Linux-specific limitations and workarounds more prominently, not just as footnotes.
- Reference cross-platform backup tools or third-party solutions where Microsoft tooling is Windows-only.