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 451-475 of 1604 flagged pages
Backup
Azure Backup - Archive tier overview
...docs/blob/main/articles/backup/archive-tier-support.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits Windows bias by focusing exclusively on Azure Virtual Machines, SQL Server, and SAP HANA workloads in Azure VMs, which are typically Windows-centric. The 'Supported clients' section lists PowerShell before CLI, and there are no explicit Linux-specific examples, tools, or guidance. Screenshots and instructions reference the Azure portal and PowerShell, but do not mention or illustrate Linux workflows or tools, nor do they address Linux backup scenarios or file recovery. The FAQ and recommendations are tailored to Azure VM backups, which are predominantly Windows environments.
Recommendations
- Add explicit examples and instructions for Linux-based workloads and recovery scenarios.
- Include Bash/Azure CLI examples alongside or before PowerShell examples to ensure parity.
- Mention and illustrate Linux file recovery options, if supported, or clarify limitations.
- Provide screenshots and walkthroughs for Linux VM backup and archive workflows.
- Clarify whether archive tier features and recommendations apply to Linux VMs and workloads, and document any differences.
Create Pull Request
Backup
About the Azure Virtual Machine restore process
...cs/blob/main/articles/backup/about-azure-vm-restore.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits Windows bias by referencing PowerShell as the tool for restoring encrypted VMs, and by linking only to Windows-specific disk encryption documentation. There are no examples or guidance for Linux VM restore scenarios, nor are Linux-specific tools or patterns mentioned. Windows-related procedures and references are presented exclusively, with no Linux parity.
Recommendations
- Include Linux VM restore scenarios and examples alongside Windows examples.
- Provide guidance for restoring encrypted Linux VMs, including relevant tools (e.g., Azure CLI, Bash scripts).
- Add links to Linux disk encryption documentation and restore procedures.
- Ensure that references to PowerShell are balanced with Linux equivalents (e.g., Azure CLI commands).
- Clearly indicate when instructions are Windows-specific and provide Linux alternatives where applicable.
Backup
Restore options with Microsoft Azure Recovery Services (MARS) agent
...kup/about-restore-microsoft-azure-recovery-services.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page for Microsoft Azure Recovery Services (MARS) agent exhibits a strong Windows bias. All restore options and examples are centered around Windows environments, referencing Windows Server System State, PowerShell for automation, and Windows-specific tools like robocopy. There is no mention of Linux support, equivalent Linux commands, or cross-platform usage, and all instructions implicitly assume a Windows operating system.
Recommendations
- Explicitly state platform support: Clarify whether the MARS agent is Windows-only or if Linux is supported. If Linux is not supported, make this clear early in the documentation.
- Provide Linux parity information: If Linux support exists or is planned, include equivalent restore options, commands, and examples for Linux systems.
- Mention cross-platform alternatives: If the MARS agent is Windows-only, suggest alternative Azure backup solutions for Linux users and link to relevant documentation.
- Avoid Windows-centric tool recommendations: Where possible, recommend platform-agnostic tools or provide Linux equivalents (e.g., suggest rsync for Linux instead of robocopy).
- Balance example order: If both platforms are supported, alternate or parallelize examples for Windows and Linux, rather than presenting Windows first or exclusively.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by frequently referencing PowerShell as a primary automation tool, listing it first among automation methods, and providing examples and workflow descriptions that center on PowerShell and Azure Automation Runbooks. There are no explicit Linux shell (bash) or cross-platform CLI examples, nor is there mention of Linux-specific automation patterns or tools. While CLI, SDKs, Terraform, and Ansible are listed, practical examples and workflows focus on PowerShell and Windows-centric automation, leaving Linux users with less guidance.
Recommendations
- Provide explicit bash or Azure CLI examples alongside PowerShell for each scenario.
- Include Linux-focused automation workflows, such as using cron jobs, shell scripts, or Ansible playbooks for backup automation.
- Ensure that references to automation tools do not prioritize PowerShell or Windows-first approaches; list CLI and SDKs equally.
- Add sample scripts and videos demonstrating automation from Linux environments.
- Highlight cross-platform compatibility and note any differences or considerations for Linux users.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The glossary page demonstrates a Windows bias through frequent references to Windows-specific technologies (e.g., VSS, DPM, MARS agent, Azure Backup Server), and by listing Windows tools and concepts (such as Azure PowerShell and VSS) before or instead of Linux equivalents. Examples and explanations often focus on Windows scenarios, with Linux mentioned only as an aside (e.g., 'pre or post scripts for Linux'). There is a lack of Linux-specific backup concepts, tools, or examples, and the documentation does not provide parity in describing Linux backup workflows or technologies.
Recommendations
- Include Linux-specific backup concepts and glossary entries, such as native Linux snapshot tools (e.g., LVM snapshots, fsfreeze), and explain how Azure Backup interacts with them.
- Provide examples and explanations for both Windows and Linux scenarios, ensuring Linux workflows are described with equal detail.
- Add references to Linux command-line tools (e.g., Azure CLI usage on Linux, shell scripts) alongside PowerShell, and clarify cross-platform usage.
- Where Windows-specific technologies are mentioned (e.g., VSS), provide equivalent Linux mechanisms or explicitly state differences in backup consistency approaches.
- Ensure workload-specific terms (such as 'bare metal backup', 'system state backup') are explained for Linux systems as well, or clarify their Windows-only applicability.
- Review glossary entries to avoid assuming Windows as the default platform, and balance references to Windows and Linux throughout the page.
Backup
Quickstart - Configure vaulted backup for Azure Data Lake Storage using ARM or Bicep template
...ata-lake-storage-backup-configure-quickstart-arm-bicep.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation provides only PowerShell deployment examples for both ARM and Bicep templates, with no Azure CLI or Bash equivalents. This approach favors Windows users and those familiar with PowerShell, while Linux and macOS users—who typically use Azure CLI or Bash—are left without direct guidance. The deployment instructions mention Azure Cloud Shell, which does support PowerShell and Bash, but only PowerShell scripts are shown. No Linux-specific tools, patterns, or examples are provided.
Recommendations
- Add Azure CLI deployment examples alongside PowerShell for both ARM and Bicep templates.
- Include Bash script examples for template deployment, especially for users on Linux and macOS.
- Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide parity in instructions.
- Where possible, provide guidance for deploying templates using cross-platform tools (e.g., az deployment group create).
- Consider reordering instructions so that CLI/Bash examples are presented before or alongside PowerShell, not after.
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
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured as a primary automation example, with detailed step-by-step instructions and cmdlets, while Linux-native shells or scripting languages are not mentioned. The Azure CLI section is present and reasonably detailed, but PowerShell is given equal prominence and is referenced in metadata and custom tags. There is no mention of Linux-specific tooling, nor are there examples using Bash or Linux shell scripting. The prerequisites for PowerShell include installation instructions, but there are no analogous instructions for CLI environments on Linux. The documentation also references Windows-centric tools and patterns (PowerShell, cmdlets) without providing Linux alternatives or parity in introductory content.
Recommendations
- Add explicit Bash shell examples for Azure CLI commands, showing usage in Linux environments.
- Include installation instructions for Azure CLI on Linux, similar to the PowerShell installation guidance.
- Reference Linux-native scripting and automation patterns (e.g., Bash scripts, cron jobs) alongside PowerShell.
- Ensure that Azure CLI examples are as detailed and comprehensive as PowerShell examples, including parameter explanations and output samples.
- Review metadata and custom tags to ensure Linux/CLI parity (e.g., avoid 'devx-track-azurepowershell' without equivalent 'devx-track-linux-cli').
- Consider adding a section comparing PowerShell and Bash/CLI workflows for cross-platform users.
Backup
What is Azure Kubernetes Service (AKS) Backup?
...les/backup/azure-kubernetes-service-backup-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates Windows bias primarily through the ordering and emphasis of Windows-centric tools and examples. The 'Related content' section lists PowerShell-based backup before CLI-based restore, suggesting a Windows-first approach. There is a dedicated link for backing up AKS using Azure PowerShell, but no equivalent Linux-focused example (e.g., Bash or shell scripts). The documentation refers to Azure PowerShell and CLI, but does not provide in-page examples for either, nor does it mention Linux-native tools or workflows. The use of terms like 'Azure PowerShell' and the absence of explicit Linux or Bash examples further reinforce the bias.
Recommendations
- Provide explicit Linux/Bash examples for backup and restore operations alongside or before PowerShell examples.
- Reorder the 'Related content' section to list CLI or Bash-based workflows before PowerShell, or present both equally.
- Include guidance for Linux administrators, such as using kubectl, Bash scripts, or Linux-native automation tools for AKS backup and restore.
- Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux (Bash).
- Add troubleshooting or operational notes relevant to Linux environments, such as file permissions, shell differences, or integration with Linux-based CI/CD pipelines.
Backup
Restore Azure Kubernetes Service (AKS) using Azure Backup
...les/backup/azure-kubernetes-service-cluster-restore.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Azure PowerShell as an alternative restore method, without mentioning or providing equivalent examples for Linux users (e.g., Azure CLI, Bash). The only explicit alternative workflow is via PowerShell, which is typically associated with Windows environments. No Linux-specific tools, commands, or examples are provided, and the documentation does not address cross-platform parity in restore operations.
Recommendations
- Add Azure CLI-based restore instructions and examples alongside PowerShell, ensuring parity for Linux and macOS users.
- Explicitly mention that restore operations can be performed from Linux environments, and provide Bash script samples where relevant.
- Where PowerShell is referenced, also link to or include equivalent CLI documentation.
- Review screenshots and UI instructions to ensure they are not Windows-centric (e.g., avoid showing only Windows-style dialogs or file paths).
- Include a section on cross-platform compatibility, clarifying supported OSes and tools for AKS restore operations.
Backup
Azure Kubernetes Service (AKS) backup using Azure Backup prerequisites
...kup/azure-kubernetes-service-cluster-backup-concept.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Azure portal and Azure PowerShell in the 'Next steps' section, mentioning PowerShell before CLI or Linux-native tools, and omitting explicit Linux shell/bash examples for AKS backup operations. The instructions and references focus on Azure portal (GUI) and PowerShell, which are traditionally Windows-centric, with CLI mentioned less prominently and no direct Linux command-line walkthroughs. There is no mention of Linux-specific patterns, such as bash scripts or kubectl usage from Linux terminals.
Recommendations
- Add explicit Linux/bash examples for key operations, such as installing the Backup Extension and enabling Trusted Access.
- Ensure Azure CLI instructions are presented at least as prominently as PowerShell, ideally before PowerShell in lists and examples.
- Include references to Linux-native tools and workflows (e.g., kubectl, bash scripting) where relevant.
- Provide parity in walkthroughs for both Windows (PowerShell) and Linux (bash/CLI), including screenshots or terminal outputs.
- Clarify that all operations can be performed from Linux environments and provide guidance for Linux users where necessary.
Backup
Back up Azure Kubernetes Service (AKS) using Azure CLI
...p/azure-kubernetes-service-cluster-backup-using-cli.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page is focused on Azure CLI usage, which is cross-platform. However, there are signs of Windows bias: PowerShell is mentioned as an alternative at the top and in 'Next steps', and a key example for creating a private endpoint uses PowerShell-style syntax (backticks for line continuation and variable assignment with $), which is specific to Windows/PowerShell. There are no explicit Linux shell/bash examples for these commands, and Windows/PowerShell patterns are presented without Linux equivalents or notes.
Recommendations
- Provide bash/Linux shell equivalents for all PowerShell-style examples, especially for multi-line commands and variable assignment.
- Avoid using PowerShell-specific syntax (backticks for line continuation, $ for variables) in generic CLI documentation, or clarify when examples are Windows-only.
- When mentioning alternative tools (e.g., PowerShell), ensure parity by linking to Linux/bash guides or noting cross-platform support.
- Explicitly state that Azure CLI commands work on Linux/macOS and provide any OS-specific instructions or caveats.
- For variable assignment and scripting, show both PowerShell and bash syntax side-by-side where relevant.
Backup
Back up Azure Local virtual machines with MABS
...e-stack-hyperconverged-infrastructure-virtual-machines.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools, commands, and examples. PowerShell is used for critical steps (e.g., disabling firewall rules), and all agent installation/configuration commands are Windows-specific (EXE installers, .exe configuration tools). The prerequisites and backup procedures focus on Windows environments (Hyper-V, Windows Server), with only brief mention of Linux support and no Linux-specific examples or guidance. There are no Linux command-line examples, nor is there parity in troubleshooting or operational instructions for Linux VMs.
Recommendations
- Add Linux-specific backup and recovery examples, including command-line instructions for agent installation and configuration on Linux VMs.
- Provide parity in troubleshooting steps for Linux environments, such as how to handle firewall or agent issues on Linux.
- Include guidance for Linux VM prerequisites, such as required packages, services, or permissions for successful backup and recovery.
- Clarify any differences in backup/restore workflows for Linux VMs, and explicitly document limitations or alternative approaches.
- Where PowerShell or Windows tools are referenced, provide equivalent Linux shell commands or scripts.
- Ensure screenshots and UI instructions are relevant for both Windows and Linux VM management contexts, or note any differences.
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page for backing up file data with MABS demonstrates a Windows bias. It exclusively references Windows-specific tools, features, and patterns (such as Data Deduplication, Volume Shadow Copy Service, and SAN hardware snapshots), and all instructions and terminology are tailored to the Windows environment. There are no examples, guidance, or mentions of Linux systems, nor any parity for Linux-specific backup scenarios or recovery workflows.
Recommendations
- Add explicit instructions and examples for backing up and recovering file data on Linux machines protected by MABS, including agent installation and supported file systems.
- Document any differences in backup and recovery workflows for Linux clients, such as supported features, limitations, and alternative methods for deduplication and snapshots.
- Where Windows-specific features (e.g., VSS, Data Deduplication) are mentioned, clarify their applicability and provide Linux equivalents or note their absence.
- Include a section comparing Windows and Linux support in MABS, highlighting feature parity and gaps.
- Ensure terminology and screenshots (if any) reflect both Windows and Linux environments where possible.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias. Example responses for recovery points and metadata frequently use 'osType': 'Windows', and XML fragments contain <OsType>Windows</OsType>. There are no examples or mention of Linux VMs, nor any Linux-specific restore scenarios, patterns, or considerations. Windows terminology and tooling (e.g., 'Microsoft-IIS', 'ASP.NET', 'windowscloudbackup.com') appear in headers and metadata, reinforcing a Windows-centric perspective. No PowerShell commands are present, but the lack of Linux parity is evident.
Recommendations
- Include example responses and request bodies for Linux VMs (e.g., 'osType': 'Linux').
- Add a section or note describing any differences or considerations when restoring Linux VMs (such as file system, bootloader, or configuration nuances).
- Ensure metadata and sample XML fragments alternate or include Linux values (e.g., <OsType>Linux</OsType>).
- Mention Linux-specific restore scenarios, such as restoring VMs with custom kernels or handling SSH keys.
- If there are no differences, explicitly state that the process applies equally to Linux and Windows VMs.
- Review terminology and headers to avoid reinforcing Windows-centric patterns unless technically required.
Backup
Back up Hyper-V virtual machines with MABS
...ticles/backup/back-up-hyper-v-virtual-machines-mabs.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Windows Heavy
Summary
The documentation page demonstrates a strong Windows bias. All backup and recovery procedures are described exclusively for Hyper-V (a Windows-only virtualization platform) and Microsoft Azure Backup Server (MABS), which is designed for Windows environments. Examples, screenshots, and step-by-step instructions are tailored to Windows Server and Windows tools (e.g., VSS, NTLM, registry keys). Linux support is mentioned only briefly and generically, with no concrete examples, procedures, or parity in item-level recovery. The documentation does not provide Linux-specific guidance or equivalent tooling, and recovery of individual files is explicitly limited to Windows Server VMs.
Recommendations
- Provide concrete examples and step-by-step instructions for backing up and restoring Linux VMs, including guest-level agent installation and recovery procedures.
- Clarify limitations and supported features for Linux VMs, such as item-level recovery, application-consistent backups, and integration services.
- Include screenshots and walkthroughs for Linux VM scenarios, demonstrating parity with Windows workflows where possible.
- List Linux-specific prerequisites and configuration steps, such as supported file systems, required agents, and authentication methods.
- Explicitly state any feature gaps between Windows and Linux VM backup/recovery, and provide guidance or workarounds for Linux users.
- If MABS does not support Linux VMs beyond file-consistent snapshots, recommend alternative backup solutions for Linux environments.
Backup
Tutorial - Back up Azure Managed Disks using Azure Backup
...main/articles/backup/back-up-managed-disks-tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation primarily focuses on using the Azure portal for backup operations, which is platform-agnostic, but when mentioning automation or scripting, it lists PowerShell before CLI and does not provide explicit Linux or Bash examples. References to scripts are labeled as 'PowerShell/CLI', with PowerShell mentioned first, and there is no demonstration of Linux-specific tools or workflows. There are no screenshots or step-by-step instructions for Linux users, nor any mention of Bash or shell scripting alternatives.
Recommendations
- When listing automation options, mention Azure CLI before or alongside PowerShell, and clarify that CLI works cross-platform (Windows, Linux, macOS).
- Provide explicit examples or links for Bash/shell scripting on Linux, not just PowerShell.
- Include screenshots or instructions for using Azure CLI in a Linux terminal.
- Add a section or note highlighting Linux compatibility and best practices for Linux administrators.
- Ensure parity in scripting documentation by linking to or embedding Linux/Bash walkthroughs where PowerShell is referenced.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. Backup scenarios and tooling are described almost exclusively for Windows environments, with the MARS agent and DPM/MABS servers being Windows-only solutions. Linux is explicitly stated as unsupported for direct backup with MARS, and there are no Linux-specific backup agent examples or equivalent Linux tooling mentioned. Windows backup patterns and tools (MARS, VSS, DPM/MABS) are described in detail, while Linux backup scenarios are omitted or only referenced indirectly (e.g., SAP HANA, Azure managed disks for Linux VMs). The documentation consistently presents Windows solutions first and in greater detail, with Linux support either missing or relegated to external links.
Recommendations
- Add explicit Linux backup scenarios and workflows, including supported agents and methods for on-premises Linux machines.
- Provide parity in example detail for Linux environments, including step-by-step guides and architecture diagrams.
- Mention Linux-compatible backup tools (such as Azure Backup integration with Azure VM Linux agents, or third-party solutions) where appropriate.
- Clarify limitations and alternatives for Linux users when Windows-only tools (MARS, DPM/MABS) are discussed.
- Include Linux-specific references and links in 'Next steps' and throughout the documentation, not just as external resources.
- If direct backup of Linux machines is not supported, state this clearly and suggest recommended alternatives or roadmap plans.
Backup
Restore VMs by using the Azure portal using Azure Backup
...b/main/articles/backup/backup-azure-arm-restore-vms.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits Windows bias in several areas: Windows-specific examples and links are provided before or instead of Linux equivalents, especially in restore scenarios and network configuration. PowerShell is frequently mentioned as the method to create or customize VMs, with no equivalent Bash or Azure CLI examples for Linux users. References to Windows tools and features (such as Hybrid Use Benefit, domain controller restore, and NSG/availability set configuration) are prevalent, while Linux-specific guidance is minimal or absent. Linux restore scenarios, troubleshooting, and customization steps are not covered with the same depth or clarity as Windows.
Recommendations
- Provide Azure CLI and Bash examples alongside PowerShell for all VM restore and customization steps.
- Include explicit Linux VM restore scenarios, such as restoring SSH keys, cloud-init configurations, and troubleshooting common Linux-specific issues.
- Add links to Linux documentation (e.g., restoring Linux VMs, configuring network interfaces, handling Linux disk attachment) wherever Windows links are present.
- Ensure parity in guidance for special configurations (e.g., availability sets, managed identities, network settings) for both Windows and Linux VMs.
- Highlight differences and considerations for Linux VMs in post-restore steps, such as handling SELinux, systemd, or other Linux-specific services.
- Balance examples and screenshots to include both Windows and Linux VM restore workflows.
Backup
Back Up Azure VMs in a Recovery Services Vault
...b/main/articles/backup/backup-azure-arm-vms-prepare.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the 'Install the VM agent' section, where Windows instructions are presented first and in greater detail, including download links, file paths, and verification steps. In contrast, Linux instructions are brief, lack explicit command examples, and defer to distribution repositories without showing concrete installation or verification steps. No Linux command-line examples (e.g., shell commands) are provided anywhere, while Windows-specific file paths and actions are described. The overall flow and screenshots are platform-neutral, but the agent installation guidance favors Windows.
Recommendations
- Provide explicit Linux installation commands (e.g., 'sudo apt install walinuxagent' or 'sudo yum install WALinuxAgent') for popular distributions.
- Include Linux verification steps, such as checking the agent version ('waagent --version') and relevant file paths.
- Present Windows and Linux instructions in parallel, with equal detail and prominence.
- Add troubleshooting tips for both platforms, not just Windows.
- Ensure that examples and screenshots (where applicable) represent both Windows and Linux environments.
Backup
Replace your tape infrastructure by using Azure Backup
...n/articles/backup/backup-azure-backup-cloud-as-tape.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing System Center Data Protection Manager (DPM), a Windows-only backup tool, and linking to a 'backup-windows-with-mars-agent' guide in the Next Steps section. There are no mentions of Linux backup tools, Linux-specific examples, or parity in guidance for non-Windows environments. All screenshots and examples are generic or Windows-centric, and Linux users are not addressed.
Recommendations
- Include examples and guidance for configuring Azure Backup from Linux servers, such as using Azure CLI or REST API.
- Reference Linux-compatible backup tools (e.g., Azure Backup Server, third-party solutions) alongside DPM.
- Add links to documentation for backing up Linux workloads to Azure.
- Provide screenshots or walkthroughs from Linux environments where applicable.
- Ensure terminology and instructions are platform-neutral or explicitly cover both Windows and Linux scenarios.
Backup
Offline seeding workflow for MARS using customer-owned disks with Azure Import/Export - Azure Backup
...n/articles/backup/backup-azure-backup-import-export.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All workflow steps, prerequisites, and tooling are described exclusively for Windows environments. The use of the MARS agent, AzureOfflineBackupDiskPrep utility, and Azure PowerShell are all Windows-specific. There is no mention of Linux support, nor are there any Linux command-line examples, alternative tools, or guidance for non-Windows platforms. The documentation assumes the user is operating on Windows Server or Windows client, with requirements for Microsoft Edge or Internet Explorer, and BitLocker, further reinforcing the Windows-centric approach.
Recommendations
- Explicitly state platform limitations (e.g., if Linux is unsupported, clarify early in the document).
- If Linux support is possible, provide equivalent instructions, tooling, and examples for Linux environments (e.g., using Azure CLI, Bash, or Linux-compatible disk preparation utilities).
- Mention alternatives for non-Windows users, such as Data Box or other supported workflows.
- Include a comparison table of supported platforms and features for offline seeding.
- If the workflow is Windows-only, add a prominent note to guide Linux users to alternative solutions or documentation.
Backup
Back up VMware VMs using Azure Backup Server
...n/articles/backup/backup-azure-backup-server-vmware.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily oriented towards Windows environments, with all configuration examples, scripts, and registry modifications shown for Windows. Powershell is used exclusively for scripting, and all instructions for certificate management, registry edits, and tool usage assume a Windows OS. There are no Linux equivalents or alternative instructions for non-Windows platforms, and Windows-specific tools and patterns (Registry Editor, Certificate Import Wizard, Powershell scripts in Windows paths) are mentioned throughout.
Recommendations
- Provide equivalent instructions for Linux environments, such as how to import CA certificates using Linux tools (e.g., update-ca-certificates, openssl).
- Include Linux shell script examples for tasks currently shown only in Powershell.
- Document how to configure MABS or interact with VMware from Linux-based management hosts, if supported.
- Clarify OS requirements for Azure Backup Server and whether Linux-based management is possible; if not, state this explicitly.
- If Powershell scripts are required, note whether Powershell Core on Linux is supported, and provide usage examples.
- For registry modifications, explain alternatives or note that these steps are Windows-only.
- Add a section comparing Windows and Linux support, and highlight any limitations or differences.
Backup
Back up a SharePoint farm to Azure with DPM
...main/articles/backup/backup-azure-backup-sharepoint.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on Windows-centric tools and workflows, specifically System Center Data Protection Manager (DPM), which is only available for Windows. All examples, instructions, and referenced tools (e.g., ConfigureSharePoint.exe, PowerShell) are Windows-specific, with no mention of Linux equivalents or cross-platform alternatives. The documentation assumes the reader is operating in a Windows environment and does not provide guidance for Linux-based SharePoint deployments or backup solutions.
Recommendations
- Explicitly state that DPM is a Windows-only solution and clarify platform requirements up front.
- Provide information or links to cross-platform or Linux-compatible backup solutions for SharePoint, if available.
- Include examples or alternative workflows for Linux environments, or acknowledge the lack thereof.
- Offer parity in automation examples by including Bash/CLI commands where possible, not just PowerShell.
- Mention Azure-native backup options that do not require Windows infrastructure, if applicable.
Backup
Back up an Exchange server via System Center DPM
...articles/backup/backup-azure-backup-exchange-server.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation exclusively describes backup procedures for Microsoft Exchange using System Center DPM, a Windows-only tool, with all examples and instructions referencing Windows interfaces, file paths, and tools (such as Eseutil.exe and DPM Administrator Console). There are no Linux equivalents, alternative cross-platform tools, or Linux-specific instructions provided. PowerShell is referenced in related content, reinforcing a Windows-centric approach.
Recommendations
- Explicitly state that System Center DPM and Exchange Server are Windows-only, and clarify platform limitations at the start of the document.
- Provide guidance or links for Linux-based email server backup solutions (e.g., for Postfix, Dovecot, or Zimbra) and how to back them up to Azure.
- Include alternative cross-platform backup tools (such as Azure Backup Server, or third-party solutions) and compare their usage for Linux environments.
- If PowerShell automation is referenced, offer Bash or shell script equivalents for Linux where possible.
- Add a section discussing backup strategies for organizations with mixed Windows/Linux infrastructure.
Backup
Offline seeding workflow for DPM and MABS using customer-owned disks with Azure Import/Export - Azure Backup
...les/backup/backup-azure-backup-server-import-export.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented towards Windows environments, specifically System Center Data Protection Manager (DPM) and Microsoft Azure Backup Server (MABS), which are Windows-only products. All workflow steps, prerequisites, and tooling (such as AzureOfflineBackupDiskPrep and references to PowerShell, Edge/IE, BitLocker, and command prompt) are Windows-centric. There are no examples, instructions, or mentions of Linux equivalents, nor is there guidance for performing similar workflows on Linux systems.
Recommendations
- Clarify in the introduction that the workflow is specific to Windows-based backup solutions (DPM/MABS), and note the lack of Linux support.
- If possible, provide parity documentation for Linux-based backup tools (e.g., Azure Backup integration with Linux servers), including offline seeding workflows.
- Include examples or references for performing similar offline backup workflows from Linux systems, such as using azcopy, Azure CLI, or other cross-platform tools.
- Mention alternative disk preparation and encryption tools available on Linux (e.g., LUKS for disk encryption, bash scripts for automation).
- Where PowerShell is referenced, provide Azure CLI equivalents for cross-platform usage.
- Explicitly state OS requirements and limitations in the prerequisites section.