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 301-325 of 1604 flagged pages
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 →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides detailed instructions for configuring vaulted backup for Azure Data Lake Storage using the Azure portal, PowerShell, and Azure CLI. There is a noticeable Windows bias: PowerShell is featured as a primary automation method (which is native to Windows), and prerequisites for PowerShell include installation instructions for Azure PowerShell, a Windows-centric tool. The portal and PowerShell pivots are presented before CLI, and there is no mention of Linux-specific shell environments or cross-platform scripting alternatives. The CLI section does not reference Bash, Linux, or macOS environments, and examples are generic, lacking explicit Linux context.
Recommendations
  • Add explicit Bash/Linux/macOS examples and notes in the Azure CLI section, including shell environment setup and command usage.
  • Clarify that Azure CLI is cross-platform and provide guidance for Linux/macOS users (e.g., installation, environment variables, file paths).
  • Include links or references to Linux-specific documentation or troubleshooting guides.
  • Balance the order of pivots so that CLI (cross-platform) is presented before PowerShell (Windows-centric) or clarify parity.
  • Mention alternatives to PowerShell for Linux/macOS users, such as Bash scripts or Python SDK usage.
GitHub Create Pull Request
Backup What is Azure Kubernetes Service (AKS) Backup? ...les/backup/azure-kubernetes-service-backup-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Azure PowerShell in the related content before mentioning Azure CLI, which is more commonly used on Linux/macOS. The related content includes a dedicated page for 'Back up AKS by using Azure PowerShell', but only provides a restore example for Azure CLI, omitting backup instructions for CLI users. There are no explicit Linux shell or bash examples, and no mention of Linux-native tools or workflows. The documentation does not provide parity in examples or guidance for Linux users, and the ordering of tools suggests a preference for Windows-centric approaches.
Recommendations
  • Provide backup instructions and examples using Azure CLI, not just PowerShell.
  • Ensure that CLI and shell/bash examples are included alongside PowerShell for all major operations.
  • Reorder related content to present Azure CLI and cross-platform tools before or alongside PowerShell, not after.
  • Explicitly mention Linux/macOS compatibility and workflows where relevant.
  • Include notes or sections highlighting how Linux users can perform the same tasks, with equivalent commands and screenshots if applicable.
GitHub Create Pull Request
Backup Azure Kubernetes Service (AKS) backup using Azure Backup prerequisites ...kup/azure-kubernetes-service-cluster-backup-concept.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias by listing Azure PowerShell as a primary method for backup and restore operations, mentioning it before Azure CLI in some cases, and lacking explicit Linux shell/bash examples. The references to Azure portal and PowerShell are prominent, while Linux-native tooling or command-line patterns (e.g., bash scripts, kubectl usage) are not provided or referenced. There is no mention of Linux-specific instructions, nor are there examples tailored for Linux environments.
Recommendations
  • Add explicit Linux/bash examples for backup and restore operations, including step-by-step instructions using Azure CLI and kubectl.
  • Ensure Azure CLI examples are presented before or alongside PowerShell examples, highlighting cross-platform compatibility.
  • Include notes or sections clarifying that all operations can be performed from Linux, macOS, and Windows environments.
  • Reference Linux-native tools and patterns where relevant (e.g., bash scripting, environment variables).
  • Provide parity in troubleshooting and operational guidance for both Windows and Linux users.
GitHub Create Pull Request
Backup Azure Kubernetes Service (AKS) backup support matrix ...azure-kubernetes-service-cluster-backup-support-matrix.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Azure Kubernetes Service (AKS) backup support matrix exhibits mild Windows bias. While the core backup extension is only supported on Linux-based node pools (Ubuntu or Azure Linux), the documentation references Windows-specific tools such as Azure PowerShell and lists them alongside cross-platform tools (CLI, ARM, Bicep, Terraform) in the 'Next steps' section. There is no explicit mention of Linux-native tools or shell usage (e.g., Bash), and PowerShell is referenced before Linux equivalents in some places. Additionally, there are no examples or guidance tailored for Linux users, such as Bash scripts or Linux command-line patterns.
Recommendations
  • Clarify that Azure PowerShell is primarily for Windows, and provide equivalent Bash/CLI examples for Linux users.
  • In the 'Next steps' section, list cross-platform tools (CLI, Terraform, ARM, Bicep) before Windows-specific tools like PowerShell.
  • Add explicit guidance or examples for Linux environments, such as Bash scripts or Linux shell commands for backup and restore operations.
  • Where PowerShell is referenced, include a note about its platform compatibility and suggest alternatives for Linux users.
  • Ensure that any tool or workflow mentioned is accompanied by Linux-compatible instructions or links.
GitHub Create Pull Request
Backup Restore Azure Kubernetes Service (AKS) using Azure CLI ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/azure-kubernetes-service-cluster-restore-using-cli.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by mentioning Azure PowerShell as an alternative method for restoring AKS clusters before any Linux or bash equivalents, and by not providing any Linux-specific or bash examples for command-line usage. All examples are given using Azure CLI, which is cross-platform, but there is no explicit guidance or examples for Linux users, nor any mention of shell scripting patterns or Linux-specific considerations. The documentation also references PowerShell in the context of alternative tooling, but does not mention bash or Linux-native tools.
Recommendations
  • Explicitly mention that Azure CLI commands work on both Windows and Linux, and provide sample bash scripts or Linux shell usage patterns for common tasks (e.g., variable assignment, piping, error handling).
  • If referencing PowerShell as an alternative, also mention bash or Linux shell as an alternative for scripting and automation.
  • Add a section or note for Linux users, highlighting any OS-specific considerations (such as environment variable syntax differences, file redirection, or authentication methods).
  • Ensure parity in alternative tooling references: if PowerShell is mentioned, also mention bash or other Linux-native tools where applicable.
  • Include troubleshooting tips or links for Linux environments, such as permissions, package installation, or CLI authentication issues.
GitHub Create Pull Request
Backup Back up Azure Kubernetes Service by using Azure Backup ...cles/backup/azure-kubernetes-service-cluster-backup.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily by referencing Azure PowerShell as the only CLI alternative to the Azure portal, both in the introduction and in the 'Next steps' section. There are no examples or mentions of Azure CLI (which is cross-platform and commonly used on Linux/macOS) for backup or restore operations. Additionally, there are no Linux-specific instructions, nor are Linux tools or shell commands (other than kubectl, which is cross-platform) provided for AKS backup management. The documentation implicitly prioritizes Windows tooling and patterns by omission.
Recommendations
  • Add Azure CLI examples for all backup and restore operations alongside or before PowerShell examples.
  • Explicitly mention that Azure CLI is supported and provide links to relevant CLI documentation.
  • Ensure that all command-line instructions are presented in a cross-platform manner, using bash/zsh syntax where appropriate.
  • Include Linux/macOS screenshots or clarify that the portal and CLI instructions apply equally to non-Windows environments.
  • Review all references to PowerShell and ensure parity with Azure CLI, especially in 'how-to' and 'next steps' sections.
GitHub Create Pull Request
Backup Back up Azure Local virtual machines with MABS ...e-stack-hyperconverged-infrastructure-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented towards Windows environments, with instructions and examples primarily referencing Windows Server, PowerShell commands, and Windows-specific tools (e.g., Hyper-V, NTLM, SetDpmServer.exe). Linux support is mentioned only briefly and generically, with no detailed steps, examples, or parity in tooling or process. All command-line instructions and screenshots are Windows-centric, and there are no Linux-specific backup or recovery workflows provided.
Recommendations
  • Provide step-by-step backup and recovery instructions for Linux VMs, including relevant commands and tooling.
  • Include Linux-specific examples for agent installation, configuration, and recovery, using native Linux tools (e.g., shell commands, systemd services).
  • Clarify any differences in backup/restore capabilities and limitations for Linux VMs, and offer guidance for common Linux scenarios.
  • Add screenshots or terminal output examples from Linux environments to match the Windows visuals.
  • Explicitly mention supported Linux distributions and versions, and any prerequisites or caveats for Linux VM backup.
  • Where PowerShell or Windows tools are referenced, offer equivalent Linux commands or workflows (e.g., using SSH, bash scripts, or Linux firewall management).
GitHub Create Pull Request
Backup Back up Hyper-V virtual machines with MABS ...ticles/backup/back-up-hyper-v-virtual-machines-mabs.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page is heavily focused on Windows environments, specifically Hyper-V on Windows Server, with procedures, prerequisites, and recovery steps almost exclusively referencing Windows tools, features, and patterns. Linux support is mentioned only briefly, with no detailed examples or parity in recovery features (e.g., item-level recovery is only available for Windows Server VMs). There are no Linux-specific walkthroughs, commands, or screenshots. Windows terminology and features (VSS, NTLM, SCSI controller, registry keys) are used throughout, and Windows Server versions are referenced as prerequisites and in examples.
Recommendations
  • Provide detailed Linux backup and recovery examples, including step-by-step instructions for Linux VMs.
  • Clarify which features are available for Linux VMs and document any limitations or differences compared to Windows VMs.
  • Include Linux-specific prerequisites, such as supported distributions, required agents, and configuration steps.
  • Offer parity in recovery features where possible, or clearly document feature gaps (e.g., item-level recovery for Linux VMs).
  • Add Linux-focused screenshots and console output to balance the visual representation.
  • Reference Linux authentication methods and file systems where relevant, not just Windows-centric ones.
  • If PowerShell or Windows registry modifications are required, provide Linux equivalents or note their absence.
GitHub Create Pull Request
Backup About the MARS Agent ...s/blob/main/articles/backup/backup-azure-about-mars.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation for the MARS Agent is heavily Windows-centric. All backup and recovery scenarios, process descriptions, and technical details explicitly refer to Windows systems, files, folders, volumes, and system state. There is no mention of Linux support, Linux file systems, or Linux-specific backup/recovery patterns. Windows tools and technologies (e.g., VSS, USN journal) are referenced exclusively, and no Linux equivalents or alternatives are discussed.
Recommendations
  • Clarify whether the MARS Agent supports Linux systems. If not, explicitly state that it is Windows-only.
  • If Linux support exists or is planned, add equivalent Linux examples and scenarios, including Linux file system backup, recovery, and system state concepts.
  • Mention Linux backup tools or mechanisms (e.g., LVM snapshots, rsync, tar) where appropriate, and provide guidance for Linux administrators.
  • Ensure parity in diagrams and tables by including Linux scenarios and terminology.
  • Provide links to Linux-specific documentation or recommend alternative Azure backup solutions for Linux systems.
GitHub Create Pull Request
Backup Back up file data with MABS ...re-docs/blob/main/articles/backup/back-up-file-data.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation for backing up file data with MABS is heavily oriented toward Windows environments. It references Windows-specific features (such as Data Deduplication, Volume Shadow Copy Service, and SAN hardware snapshots), and all instructions and terminology assume the use of the MABS console, which is a Windows application. There are no examples or guidance for Linux systems, nor are Linux-specific backup scenarios, agents, or recovery workflows mentioned. The documentation does not clarify whether or how Linux clients are supported, and Windows tools and patterns are referenced exclusively and first.
Recommendations
  • Add explicit guidance for backing up and recovering file data from Linux machines, including agent installation, supported file systems, and any limitations.
  • Provide Linux-specific examples and screenshots where applicable, such as command-line workflows or agent configuration.
  • Clarify which features (e.g., deduplication, VSS, SAN snapshots) are Windows-only and suggest Linux alternatives or note their absence.
  • Include a section on cross-platform support, listing supported operating systems and any differences in backup/recovery procedures.
  • Ensure parity in documentation structure by presenting Linux instructions alongside Windows ones, not only after or as an afterthought.
GitHub Create Pull Request
Backup Architecture Overview ...-docs/blob/main/articles/backup/backup-architecture.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias in several ways: backup scenarios and agent descriptions prioritize Windows machines and tools (MARS agent, DPM, MABS), with explicit statements that Linux is not supported for direct backup via MARS. There are no Linux-specific examples or equivalent Linux backup workflows described, and Windows-centric tools and terminology (VSS, MARS agent) are used exclusively or before any mention of Linux. Linux support is only referenced in passing or as unsupported, and Linux backup scenarios are not detailed.
Recommendations
  • Add explicit sections or tables describing backup options and workflows for Linux machines, including supported agents, limitations, and alternatives.
  • Provide Linux-specific examples and guidance, such as using Azure Backup for Linux VMs, supported file systems, and application-consistent backup strategies.
  • Clarify the parity (or lack thereof) between Windows and Linux backup features, and link to Linux documentation where available.
  • If certain backup scenarios are not supported for Linux, clearly state alternatives or workarounds, and indicate roadmap or plans for Linux support if applicable.
  • Avoid presenting Windows tools and workflows first or exclusively; instead, present both Windows and Linux options side-by-side where possible.
GitHub Create Pull Request
Backup Restore VMs by using the Azure portal using Azure Backup ...b/main/articles/backup/backup-azure-arm-restore-vms.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific tools and patterns (such as PowerShell and Windows VM references) are mentioned before or instead of Linux equivalents. Many example links and guidance are Windows-centric, with PowerShell being the only automation method explicitly referenced for VM creation and disk attachment. There is a lack of Linux-specific examples, and Linux restore scenarios are not described in detail. Windows terminology and features (e.g., Hybrid Use Benefit, domain controller restore, Active Directory, RDP, bcdedit, netdom) are prominent, while Linux equivalents (e.g., SSH, cloud-init, Linux disk mounting, Linux VM restore automation) are either missing or only briefly mentioned.
Recommendations
  • Provide Linux-specific examples and guidance alongside Windows instructions, such as using Azure CLI, Bash, or ARM templates for VM creation and disk attachment.
  • Include links to Linux documentation for restoring VMs, attaching disks, and configuring network settings.
  • Add Linux restore scenarios (e.g., restoring Linux VMs with cloud-init, SSH key management, troubleshooting boot issues) in parity with Windows domain controller and Active Directory scenarios.
  • Mention Linux VM agent installation and troubleshooting steps, not just Windows agent.
  • Reference Linux tools and commands for post-restore steps (e.g., mounting disks, resetting SSH keys/passwords) and avoid assuming RDP or Windows-only access patterns.
  • Ensure that automation examples (e.g., scripts for VM creation from restored disks) are provided for both PowerShell and Azure CLI/Bash.
GitHub Create Pull Request
Backup Recover data from an Azure Backup Server by using Azure Backup ...n/articles/backup/backup-azure-alternate-dpm-server.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Azure Backup Server and System Center Data Protection Manager (DPM), which are Windows-only tools. All instructions, screenshots, and terminology refer to Windows environments and the DPM management console, with no mention of Linux equivalents, CLI options, or cross-platform recovery workflows. There are no examples or guidance for Linux-based backup or recovery, nor any references to Linux tools or patterns.
Recommendations
  • Add explicit guidance for Linux environments, including supported backup/recovery workflows for Linux servers.
  • Include CLI or script-based examples (e.g., Azure CLI, Bash) for recovery operations, not just GUI-based Windows console steps.
  • Mention and link to Azure Backup solutions for Linux, such as Azure VM backup for Linux or MARS agent alternatives.
  • Clarify platform limitations and provide parity tables or comparison charts for Windows vs. Linux backup/recovery features.
  • Ensure screenshots and terminology are inclusive of both Windows and Linux scenarios where applicable.
GitHub Create Pull Request
Backup Replace your tape infrastructure by using Azure Backup ...n/articles/backup/backup-azure-backup-cloud-as-tape.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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 tool, and linking to a 'backup-windows-with-mars-agent' guide in the Next Steps section. There are no mentions of Linux backup agents, Linux-compatible tools, or examples relevant to Linux environments. All screenshots and workflow descriptions appear to be based on Windows-centric interfaces.
Recommendations
  • Include equivalent Linux backup agent documentation and examples, such as using Azure Backup with Linux VMs or workloads.
  • Mention Linux-compatible backup tools and workflows alongside Windows tools like DPM.
  • Add screenshots and step-by-step guides for configuring backup and retention policies on Linux systems.
  • Ensure Next Steps links include Linux-specific guides (e.g., 'backup-linux-with-azure-agent').
  • Clarify in introductory sections that Azure Backup supports both Windows and Linux workloads, and provide parity in instructions.
GitHub Create Pull Request
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 →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All examples, tools, and prerequisites are Windows-centric: the workflow requires the Azure Backup Agent (MARS), which is only available for Windows; instructions reference Windows-specific utilities (AzureOfflineBackupDiskPrep.exe), require Azure PowerShell, and mandate browsers only available on Windows (Edge, IE11). There are no Linux equivalents, examples, or guidance for performing offline seeding from Linux systems, nor is there mention of cross-platform compatibility.
Recommendations
  • Explicitly state platform limitations at the beginning of the document (e.g., 'This workflow is supported only on Windows systems').
  • Provide guidance or links for Linux-based offline seeding workflows if available, or clarify that such workflows are not supported.
  • If possible, develop and document cross-platform tools/utilities for offline seeding, or provide alternatives for Linux users.
  • Include Linux-specific prerequisites, examples, and troubleshooting steps if/when Linux support is added.
  • Mention Azure CLI and browser options available on Linux (e.g., Chrome, Firefox) if the workflow is ever extended to Linux.
GitHub Create Pull Request
Backup Back up a SharePoint farm to Azure with MABS ...articles/backup/backup-azure-backup-sharepoint-mabs.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All instructions, tools, and examples assume the use of Windows servers, Windows command-line tools (CMD), Windows registry, and Windows-specific services (VSS Writer, DCOM, etc). There are no references to Linux equivalents, nor any guidance for SharePoint deployments on Linux (which, while rare, are possible in containerized scenarios or with SQL Server on Linux). The documentation also exclusively uses Windows paths, environment variables, and administrative patterns, and does not mention PowerShell alternatives, but relies on Windows CMD and GUI steps.
Recommendations
  • Explicitly state that MABS and SharePoint backup are only supported on Windows, if that is the case, and clarify platform limitations.
  • If Linux support is possible (e.g., for SQL Server or file shares), provide equivalent instructions, tools, and examples for Linux environments.
  • Where possible, mention cross-platform alternatives or note the lack of Linux support for specific features.
  • Add a table or section comparing Windows and Linux support for MABS and SharePoint backup scenarios.
  • If PowerShell is used, provide CLI examples for both Windows (PowerShell/CMD) and Linux (Bash), or clarify that only Windows is supported.
  • Review and update documentation to avoid assuming Windows as the default platform unless it is a strict requirement.
GitHub Create Pull Request
Backup Restore Azure VMs using REST API .../backup/backup-azure-arm-userestapi-restoreazurevms.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: example responses and request bodies frequently reference Windows VMs (e.g., osType: "Windows"), and metadata fields such as <OsType>Windows</OsType> appear repeatedly. There are no examples or notes for Linux VMs, nor any mention of Linux-specific restore considerations, patterns, or troubleshooting. All sample VM sizes and configurations are generic or Windows-centric, and no Linux tools or CLI examples are provided.
Recommendations
  • Include example responses and request bodies for Linux VMs (osType: "Linux").
  • Add notes or sections describing any differences or considerations when restoring Linux VMs (e.g., handling SSH keys, boot diagnostics, disk mount points).
  • Provide sample VM configurations and metadata for Linux, such as <OsType>Linux</OsType> in tokenExtendedInformation.
  • Mention Linux-specific troubleshooting steps or common issues (e.g., kernel mismatches, cloud-init).
  • Ensure parity in documentation by alternating examples between Windows and Linux, or providing both side-by-side.
  • If there are CLI or scripting examples, include Bash/cURL or Azure CLI commands alongside any PowerShell or Windows-centric tools.
GitHub Create Pull Request
Backup Back Up Azure VMs in a Recovery Services Vault ...b/main/articles/backup/backup-azure-arm-vms-prepare.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. In the 'Install the VM agent' section, Windows instructions are presented first, with explicit steps, download links, and verification details, while Linux instructions are less detailed and lack concrete example commands. The Windows agent installation references a specific MSI installer and file path, whereas the Linux instructions only mention using RPM/DEB packages without examples. No PowerShell or CLI examples are present, but the overall pattern prioritizes Windows tools and details.
Recommendations
  • Provide Linux installation instructions with explicit example commands (e.g., apt, yum, zypper) for installing/updating the Azure Linux agent.
  • Include verification steps for Linux agent installation, such as checking the agent version via command line.
  • Present Windows and Linux instructions in parallel or side-by-side, rather than listing Windows first.
  • Add troubleshooting tips specific to Linux environments, similar to those given for Windows.
  • Ensure that screenshots, examples, and terminology are balanced between Windows and Linux contexts.
GitHub Create Pull Request
Backup Back up an Exchange server via System Center DPM ...articles/backup/backup-azure-backup-exchange-server.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows environments, specifically System Center DPM and Microsoft Exchange, which are Windows-only products. All instructions, examples, and tooling references (such as DPM Administrator Console, Eseutil.exe, and PowerShell automation) are exclusive to Windows. There are no Linux equivalents, alternative cross-platform tools, or mention of Linux-based Exchange alternatives. The documentation assumes a Windows infrastructure throughout.
Recommendations
  • Explicitly state that DPM and Exchange are Windows-only and clarify platform limitations at the start of the documentation.
  • If Azure Backup supports Linux workloads, provide links or sections for Linux backup scenarios and tools (such as MABS, Azure Backup for Linux VMs, or third-party solutions).
  • Offer guidance or references for backing up Linux-based mail servers (e.g., Postfix, Dovecot) to Azure Backup, if applicable.
  • Include a comparison table of supported platforms and backup solutions to help users identify appropriate documentation for their environment.
  • Ensure related content and next steps include Linux backup documentation where relevant.
GitHub Create Pull Request
Backup Back up VMware VMs using Azure Backup Server ...n/articles/backup/backup-azure-backup-server-vmware.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All operational steps, configuration instructions, and scripts assume the Azure Backup Server is running on Windows. Registry edits, certificate installation, and scripting are exclusively described using Windows tools (Registry Editor, Certificate Import Wizard, PowerShell). There are no examples or guidance for performing these tasks on Linux systems, nor is there mention of Linux-based Azure Backup Server support or alternatives.
Recommendations
  • Clarify platform support: Explicitly state whether Azure Backup Server supports Linux hosts. If not, mention this early in the documentation.
  • Provide Linux alternatives: For each Windows-specific step (e.g., registry edits, certificate installation, PowerShell scripts), offer equivalent instructions for Linux environments if supported (e.g., editing configuration files, using OpenSSL, Bash scripts).
  • Balance examples: Include both Windows and Linux command-line examples for scripting and automation tasks.
  • Mention cross-platform tools: Where possible, suggest platform-agnostic tools or approaches (e.g., using REST APIs, cross-platform scripting languages).
  • Reorder instructions: Avoid always presenting Windows steps first; if Linux is supported, alternate or group by platform.
GitHub Create Pull Request
Backup Back up SQL Server to Azure as a DPM workload ...s/blob/main/articles/backup/backup-azure-backup-sql.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation is heavily oriented toward Windows environments, specifically focusing on Data Protection Manager (DPM), a Windows-only backup tool. All examples, screenshots, and instructions assume the use of Windows Server, SQL Server on Windows, and DPM. There is no mention of Linux-based SQL Server deployments, nor are there any examples or guidance for backing up SQL Server on Linux. The only automation reference is to PowerShell, which is Windows-centric.
Recommendations
  • Add sections or examples for backing up SQL Server running on Linux, using Azure Backup or other supported tools.
  • Mention Linux-compatible backup solutions (such as MABS, Azure Backup for Linux, or third-party tools) where appropriate.
  • Provide parity in automation examples, such as Bash scripts or Azure CLI commands, alongside PowerShell.
  • Clarify in prerequisites and supported scenarios whether Linux-based SQL Server deployments are supported or not, and link to relevant documentation if they are.
  • Include screenshots or walkthroughs for Linux environments if supported.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by referencing PowerShell objects as the default way to conceptualize backup policies for PostgreSQL. There are no examples or mentions of Linux-native tools, shell scripts, or CLI usage, and the only scripting context provided is PowerShell. This may make the documentation less approachable for Linux users, who are common in PostgreSQL and cloud automation scenarios.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash shell scripts, which are platform-agnostic and widely used on Linux.
  • Replace or supplement references to PowerShell objects with JSON or YAML representations, clarifying that these can be used with any REST client.
  • Explicitly mention that the REST API can be invoked from any OS and provide sample curl commands for Linux users.
  • Add a section or callout for Linux users, describing how to automate policy creation using tools available on Linux (e.g., curl, jq, Azure CLI).
  • Avoid language that implies PowerShell is the default or only way to interact with the API; use neutral phrasing.
GitHub Create Pull Request
Backup Back up blobs in a storage account using Azure Data Protection REST API. ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-dataprotection-use-rest-api-backup-blobs.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by mentioning Azure PowerShell as a method for assigning permissions before Azure CLI, and by not providing any explicit Linux or cross-platform command-line examples for REST API usage. All example commands are shown as HTTP requests or JSON payloads, but when discussing role assignment, only Azure portal and PowerShell are named, with CLI mentioned last. There are no Linux-specific instructions, shell scripts, or CLI examples for common Linux environments.
Recommendations
  • Provide explicit Azure CLI examples for all operations, especially for permission assignment and resource management, alongside PowerShell.
  • Mention Azure CLI before or alongside PowerShell when listing supported tools, to signal parity.
  • Add Linux shell (bash) examples for REST API calls using curl, demonstrating how Linux users can interact with the API.
  • Clarify that all REST API examples are platform-agnostic, and provide guidance for both Windows and Linux users.
  • Include a 'Platform considerations' section noting any differences or requirements for Windows vs. Linux environments.
GitHub Create Pull Request
Backup Overview of Azure Database for PostgreSQL Backup ...es/backup/backup-azure-database-postgresql-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates Windows bias by exclusively referencing the pgAdmin GUI tool (commonly used on Windows), providing only GUI-based instructions and screenshots, and omitting command-line examples (such as psql or Azure CLI) that are more typical for Linux users. There are no Linux-specific instructions, nor are cross-platform alternatives (e.g., psql, Azure CLI, Bash scripts) mentioned or demonstrated. The documentation assumes use of the Azure Portal and GUI tools, which are more familiar to Windows users, and does not address Linux workflows or tooling.
Recommendations
  • Include command-line examples using psql for backup privilege grants and database management.
  • Demonstrate how to perform backup and restore operations using Azure CLI and Bash scripts.
  • Add instructions for connecting to Azure Database for PostgreSQL using psql, including sample connection strings and firewall rule configuration.
  • Provide parity in screenshots and instructions for Linux environments, such as using terminal commands and native Linux tools.
  • Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux users throughout the documentation.
GitHub Create Pull Request
Backup Back Up Azure Database for PostgreSQL by Using the Azure Portal ...in/articles/backup/backup-azure-database-postgresql.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: PowerShell is the only scripting example provided for granting database privileges, and instructions for setting up the PSQL tool and environment variables are exclusively Windows-centric (Control Panel, System Properties). There are no Linux-specific instructions or examples for running scripts or configuring environment variables, and Windows tools/patterns are mentioned before any cross-platform alternatives. Linux users are left to infer how to perform equivalent steps on their systems.
Recommendations
  • Provide explicit Linux instructions for setting environment variables (e.g., using ~/.bashrc or export commands) and running the PowerShell script (e.g., using PowerShell Core on Linux or providing a Bash/psql equivalent).
  • Include screenshots or terminal commands relevant to Linux environments alongside Windows examples.
  • Mention Linux tools and workflows (such as using nano/vim for editing, or the export command for environment variables) in parallel with Windows tools.
  • Offer Bash or shell script alternatives for privilege granting, or clarify how to run the provided PowerShell script on Linux (with PowerShell Core).
  • Ensure that all steps and prerequisites are described for both Windows and Linux users, including network configuration and tool installation.
GitHub Create Pull Request
← Previous Page 13 of 65 Next →