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 501-525 of 1604 flagged pages
Backup Restore SQL server databases in Azure VMs using Azure Backup via CLI ...b/main/articles/backup/backup-azure-sql-restore-cli.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by exclusively referencing SQL Server (a Microsoft/Windows-centric database), using Windows-style VM/server names (e.g., testSQLVM), and omitting any mention of Linux-based SQL deployments or restoration scenarios. All examples and instructions assume the SQL instance is running on a Windows VM, with no guidance for Linux VMs or for restoring other database types (e.g., PostgreSQL, MySQL) that are commonly run on Linux. There are no examples or notes about differences or requirements for Linux-based SQL Server VMs, nor about using CLI commands in a Linux shell environment.
Recommendations
  • Add explicit guidance and examples for restoring SQL Server databases on Linux-based Azure VMs, including any differences in CLI usage, file paths, permissions, or prerequisites.
  • Mention and provide parity for Linux shell environments (bash, zsh) in CLI command examples, including notes about quoting, file paths, and environment setup.
  • Clarify whether the documented process applies to both Windows and Linux SQL Server VMs, and highlight any platform-specific considerations.
  • Include references or links to documentation for restoring other database types (e.g., PostgreSQL, MySQL) on Azure VMs, especially those commonly run on Linux.
  • Use neutral VM/server naming conventions in examples (e.g., avoid 'testSQLVM', use 'testSQLServer' or 'testDBServer') and clarify OS assumptions where relevant.
GitHub Create Pull Request
Backup Troubleshoot System State Backup ...icles/backup/backup-azure-system-state-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, with all troubleshooting steps, examples, and tools (such as PowerShell, Server Manager, and Windows-specific services) exclusively referencing Windows Server. There are no Linux equivalents, examples, or mentions, and Windows tools and patterns are presented as the only option.
Recommendations
  • If System State Backup is not supported on Linux, clearly state this limitation at the beginning of the document.
  • If similar backup or troubleshooting functionality exists for Linux, provide equivalent examples and steps for Linux systems (e.g., using native Linux backup tools, commands, and troubleshooting procedures).
  • Where PowerShell or Windows-specific tools are referenced, mention Linux alternatives or clarify that the instructions are Windows-only.
  • Consider adding a section comparing Windows and Linux backup approaches, or linking to Linux backup documentation for users managing mixed environments.
GitHub Create Pull Request
Backup Move VM backup - standard to enhanced policy in Azure Backup ...cles/backup/backup-azure-vm-migrate-enhanced-policy.md
High Priority View Details →
Scanned: 2026-01-10 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 referencing PowerShell and CLI versions for migration, but does not provide explicit Linux shell examples or mention Linux-specific usage. The only command-line example is a link to Azure CLI, but there are no bash or Linux terminal screenshots, nor are Linux patterns or tools discussed. The portal-based instructions and screenshots are platform-neutral, but command-line references implicitly prioritize Windows (PowerShell) and do not clarify Linux compatibility or provide parity.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example commands in bash syntax.
  • Include Linux shell (bash) examples alongside PowerShell, especially for migration operations.
  • Add screenshots or terminal outputs from Linux environments to demonstrate parity.
  • Clarify any differences in experience or prerequisites for Linux users (e.g., installation steps, authentication).
  • Avoid referencing PowerShell before CLI, or provide both in parallel to avoid perceived prioritization.
GitHub Create Pull Request
Backup Troubleshoot Azure VM file recovery ...s/backup/backup-azure-vm-file-recovery-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-10 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 demonstrates a Windows bias in several ways: Windows troubleshooting steps and tools (e.g., File Explorer, Server Manager, Disk Management, ISCSI initiator Properties) are described in detail with step-by-step instructions and screenshots, while Linux troubleshooting is often referenced via external links or given minimal explanation. Windows solutions are frequently presented before Linux equivalents, and some error scenarios provide only Windows-specific guidance or examples. Linux instructions are less detailed, sometimes missing direct command examples or screenshots, and rely on users to consult other documentation for full procedures.
Recommendations
  • Provide equally detailed, step-by-step instructions for Linux scenarios, including screenshots where applicable (e.g., using GNOME Disks, lsblk, mount commands, etc.).
  • Include Linux command-line examples for tasks such as mounting/unmounting disks, checking disk status, and assigning mount points.
  • Present troubleshooting steps for Windows and Linux in parallel, rather than Windows-first, to improve parity and accessibility for Linux users.
  • Avoid referencing Windows tools (e.g., File Explorer, Disk Management) exclusively; mention Linux equivalents (e.g., Nautilus, GNOME Disks, CLI tools) alongside.
  • Ensure that all error scenarios have both Windows and Linux solutions, with clear instructions for each platform.
  • Where external links are used for Linux, consider integrating the relevant steps directly into the troubleshooting guide for consistency.
GitHub Create Pull Request
Backup Back Up and Restore Encrypted Azure VMs ...ob/main/articles/backup/backup-azure-vms-encryption.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates moderate Windows bias. PowerShell is the only command-line example provided for identifying a VM's associated key vault, with no equivalent Linux (Azure CLI) example. BitLocker (Windows) is mentioned before dm-crypt (Linux) in the ADE section, and PowerShell is referenced multiple times for configuration and automation tasks. There are no explicit Linux command examples or references to Linux-specific tools or workflows.
Recommendations
  • Provide Azure CLI examples alongside PowerShell commands, especially for tasks like identifying the key vault associated with a VM.
  • Mention Linux encryption tools (dm-crypt) before or alongside Windows tools (BitLocker) to ensure parity.
  • Include explicit Linux workflow steps and screenshots where applicable.
  • Add references to Linux documentation and troubleshooting guides in the 'Related content' section.
  • Where automation is discussed, provide both PowerShell and Bash/CLI script examples.
GitHub Create Pull Request
Backup About agentless multi-disk crash-consistent backup for Azure Virtual Machines by using Azure Backup ...ure-vms-agentless-multi-disk-crash-consistent-overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by mentioning Windows-specific backup mechanisms (VSS) before Linux equivalents (fsfreeze), referencing Windows VM agent and snapshot extension links, and omitting direct Linux agent/extension documentation or examples. No Linux-specific backup commands, tools, or patterns are provided, and the discussion of agent requirements is focused on Windows.
Recommendations
  • Provide direct links to Linux VM agent and snapshot extension documentation, not just Windows equivalents.
  • Include Linux-specific examples or references, such as how crash-consistent backups interact with Linux file systems and backup tools.
  • Mention Linux backup patterns (e.g., use of pre/post scripts, fsfreeze) with equal prominence and detail as Windows VSS.
  • Ensure that any discussion of agent or extension requirements covers both Windows and Linux scenarios, including supported/unsupported OS lists.
  • Add a section or table comparing Windows and Linux backup mechanisms and requirements for clarity.
GitHub Create Pull Request
Backup Back Up Azure VMs with the Enhanced Policy ...in/articles/backup/backup-azure-vms-enhanced-policy.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides detailed PowerShell examples for configuring Enhanced backup policies, with step-by-step cmdlets and explanations. PowerShell instructions are given before Azure CLI examples, and the CLI section is less detailed. There is a strong emphasis on PowerShell, which is primarily a Windows tool, and no mention of Linux-specific tools, shell environments, or considerations. The CLI examples are generic and do not address Linux-specific usage patterns or troubleshooting.
Recommendations
  • Provide Bash shell examples alongside PowerShell, especially for scripting on Linux.
  • Include Linux-specific notes or troubleshooting tips (e.g., permissions, environment variables, common errors).
  • Ensure CLI examples use syntax and idioms familiar to Linux users (e.g., jq for JSON parsing, avoiding Windows-specific commands like tr -d '"').
  • Mention cross-platform compatibility explicitly, clarifying that Azure CLI works on Linux, macOS, and Windows.
  • Balance the depth of CLI and PowerShell sections, ensuring Linux users have equally detailed guidance.
  • Reference Linux tools (e.g., cron for scheduling, systemd for automation) where relevant.
GitHub Create Pull Request
Backup About Azure VM backup .../main/articles/backup/backup-azure-vms-introduction.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by consistently mentioning Windows tools (such as VSS) before Linux equivalents, providing detailed instructions and examples for Windows (e.g., PowerShell usage for restore operations), and omitting equivalent Linux command-line examples. Linux backup consistency relies on user-created scripts, but no concrete Linux script samples or automation guidance are provided, while Windows-specific tooling and processes are described in detail.
Recommendations
  • Provide Linux CLI examples (e.g., Bash, Azure CLI) for backup and restore operations alongside PowerShell examples.
  • Include sample pre/post script templates for Linux VM application-consistent backups, similar to the detailed VSS process for Windows.
  • Mention Linux tools (such as fsfreeze) with practical usage instructions and troubleshooting steps, not just conceptual descriptions.
  • Ensure that instructions for restoring managed disks include both PowerShell and Azure CLI/Bash workflows.
  • Present Windows and Linux guidance in parallel, rather than listing Windows first or in more detail.
  • Add troubleshooting sections for Linux snapshot issues, similar to the referenced Windows troubleshooting article.
GitHub Create Pull Request
Backup Overview of Backup center for Azure Backup and Azure Site Recovery ...cs/blob/main/articles/backup/backup-center-overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page references PowerShell scripts and Microsoft Database Backup scripts as sample automation resources, but does not mention or provide parity for Linux-specific tools or scripting examples (such as Bash, shell scripts, or Linux-native backup utilities). There is a lack of explicit Linux CLI or automation examples, and the tooling referenced is predominantly Windows-centric.
Recommendations
  • Include sample Bash or shell scripts for common backup automation tasks alongside PowerShell examples.
  • Reference Linux-native backup tools or utilities where relevant, or clarify cross-platform support for scripts.
  • Provide explicit Azure CLI examples for backup management, as Azure CLI is cross-platform and widely used on Linux.
  • Mention and document any differences or considerations for Linux VMs or workloads in backup scenarios.
  • Ensure that community resources and samples include Linux-focused content and not just Windows/PowerShell scripts.
GitHub Create Pull Request
Backup Enable Backup During Azure VM Creation by Using Azure Backup ...blob/main/articles/backup/backup-during-vm-creation.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias in several ways: Windows is mentioned before Linux in VM creation instructions, the Resource Manager template example is only for Windows VMs, and PowerShell is referenced for resource group configuration without mention of Linux/CLI alternatives. There are no explicit Linux or cross-platform CLI examples for backup configuration or resource group management.
Recommendations
  • Provide equal and parallel examples for both Windows and Linux VM creation, including links and step-by-step instructions.
  • Include Resource Manager template examples for Linux VMs, or clarify how to adapt the template for Linux.
  • When referencing automation or scripting (e.g., PowerShell), also provide Azure CLI and/or Bash examples for Linux users.
  • Ensure that screenshots and walkthroughs are not Windows-centric and represent both OS types where applicable.
  • Review related content and troubleshooting links to confirm Linux parity in guidance.
GitHub Create Pull Request
Backup Azure Instant Restore Capability ...n/articles/backup/backup-instant-restore-capability.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides configuration instructions for Azure Instant Restore using the Azure portal and PowerShell, but does not mention or provide examples for Linux users or CLI tools commonly used on Linux (such as Azure CLI). The only code example is in PowerShell, which is primarily a Windows tool, and there is no mention of Bash, shell scripting, or Linux-specific guidance. This suggests a bias toward Windows environments and administrators.
Recommendations
  • Add equivalent Azure CLI (az) examples for configuring snapshot retention and other operations, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, if PowerShell is the only supported scripting tool, and provide installation guidance.
  • Include notes or examples for Linux users, such as how to perform these operations from a Bash shell or using automation tools common in Linux environments.
  • Ensure that any screenshots or UI instructions are not Windows-specific, or clarify cross-platform parity in the portal experience.
  • Review FAQ and feature sections for assumptions about OS or tooling, and add Linux-relevant information where appropriate.
GitHub Create Pull Request
Backup Use Modern Backup Storage with Azure Backup Server ...s/blob/main/articles/backup/backup-mabs-add-storage.md
High Priority View Details →
Scanned: 2026-01-10 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 is strongly Windows-centric: all instructions, screenshots, and tooling references are for Windows Server environments. There are no examples or guidance for Linux systems, and all management is described via Windows Server tools (Server Manager, PowerShell, Administrator Console). The only scripting example is a PowerShell cmdlet, with no Linux shell or cross-platform alternatives. The requirement for ReFS and Windows Server is stated up front, and Linux is not mentioned as a supported platform.
Recommendations
  • Explicitly state platform support and limitations at the beginning, clarifying if Linux is unsupported or providing parity guidance.
  • If Linux is supported, add equivalent instructions for Linux environments, including CLI (e.g., bash) and Linux-native tools.
  • Provide alternative examples using cross-platform Azure CLI or REST API where possible.
  • Mention Linux file systems and storage management patterns if relevant.
  • If only Windows is supported, clarify this to avoid confusion for Linux users.
GitHub Create Pull Request
Backup Back up files in Azure Stack VMs ...s/backup/backup-mabs-files-applications-azure-stack.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively describing backup and recovery procedures using Microsoft Azure Backup Server, which is a Windows-based tool. All instructions reference the Azure Backup Server console, a Windows GUI application, and there are no examples or guidance for Linux-based VMs, command-line tools, or cross-platform alternatives. The documentation does not mention Linux backup agents, CLI (such as az CLI), or provide parity for Linux environments, implying that only Windows-centric workflows are supported or documented.
Recommendations
  • Add explicit instructions or examples for backing up and recovering files on Linux-based Azure Stack VMs, including any required agents or supported methods.
  • Include CLI-based examples (e.g., using az CLI, shell scripts) for backup and recovery to support automation and Linux users.
  • Clarify whether Azure Backup Server can protect Linux VMs and, if so, document any differences or prerequisites for Linux environments.
  • Mention and link to Linux-native backup solutions or integration patterns if Azure Backup Server is not suitable for Linux workloads.
  • Ensure that screenshots and UI references are supplemented with equivalent command-line or Linux workflow steps where possible.
GitHub Create Pull Request
Backup MABS (Azure Backup Server) V4 protection matrix .../main/articles/backup/backup-mabs-protection-matrix.md
High Priority View Details →
Scanned: 2026-01-10 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 for Azure Backup Server v4 is heavily Windows-centric. Windows workloads, versions, and tools are listed first and in detail, with Linux support relegated to a single, limited section. Examples, technical notes, and recovery options are almost exclusively for Windows environments, with Linux only supported as a guest VM and lacking parity in features (e.g., item-level recovery). Windows-specific tools and patterns such as NTFS, VSS, Visual C++ dependencies, and domain/workgroup authentication are referenced throughout, with no Linux equivalents or guidance. Powershell and Windows Management Framework are mentioned, but no Linux command-line or automation examples are provided.
Recommendations
  • Provide Linux-specific backup and recovery examples, including command-line instructions (e.g., using shell scripts or native Linux tools).
  • Clarify Linux support for item-level recovery and document any limitations or workarounds.
  • List Linux workloads and supported distributions in the main protection matrix, not only as guest VMs.
  • Include Linux filesystem support details (e.g., ext4, xfs) and note any restrictions.
  • Offer guidance for authentication and protection in Linux domains/workgroups, including certificate management.
  • Mention Linux equivalents for Windows tools (e.g., alternatives to VSS, NTFS) or explain why they are not supported.
  • Balance the order of presentation so Linux is not always last or in a separate section.
GitHub Create Pull Request
Backup Manage Backups with Azure role-based access control ...docs/blob/main/articles/backup/backup-rbac-rs-vault.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by referencing Windows-specific backup agents and tools (e.g., Azure Backup agent client UI, System Center Data Protection Manager UI, Azure Backup Server UI) and by listing Windows Server and client registration operations explicitly. PowerShell is mentioned as a primary automation interface, with no mention of Bash or Linux shell equivalents. There are no explicit Linux backup agent references, nor examples for Linux VM backup scenarios, even though Azure supports Linux VMs. The order of presentation and examples tends to prioritize Windows-centric tools and patterns.
Recommendations
  • Include explicit references and examples for Linux VM backup scenarios, such as registering and managing Linux VMs in Recovery Services vault.
  • Mention Linux-compatible tools and interfaces (e.g., Bash, Azure CLI in Linux environments) alongside PowerShell, and provide example commands for both platforms.
  • Add notes or sections clarifying parity between Windows and Linux backup management, including any differences in supported features or role assignments.
  • List Linux backup agent/client UI (if available) or clarify that only Windows agents are supported, to avoid ambiguity.
  • Ensure that documentation for backup operations (registration, restore, etc.) covers both Windows and Linux VMs, with clear instructions for each.
GitHub Create Pull Request
Backup Install Azure Backup Server on Azure Stack Hub ...ain/articles/backup/backup-mabs-install-azure-stack.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias. All installation instructions, prerequisites, and examples are exclusively for Windows Server environments. The only supported OS mentioned is Windows Server (2022/2019 Datacenter), with no reference to Linux or cross-platform alternatives. All tooling and commands (e.g., PowerShell cmdlets, Windows Update, domain join, drive letters like C:\ and D:\) are Windows-centric. There are no Linux installation steps, examples, or troubleshooting guidance, nor are Linux-based Azure Stack Hub VMs or tools discussed.
Recommendations
  • Explicitly state OS requirements and clarify if Linux is unsupported, or provide Linux support if possible.
  • If Azure Backup Server is Windows-only, suggest alternative backup solutions for Linux workloads in Azure Stack Hub and link to their documentation.
  • Add a section comparing Windows and Linux backup options for Azure Stack Hub, including supported features and limitations.
  • If any components (e.g., Recovery Services vault, agent) support Linux, provide Linux-specific installation and configuration steps.
  • Include troubleshooting guidance for Linux environments if relevant.
  • Avoid assuming Windows conventions (e.g., drive letters, domain join) in general Azure Stack Hub documentation, or provide Linux equivalents where possible.
GitHub Create Pull Request
Backup What's new in Microsoft Azure Backup Server ...lob/main/articles/backup/backup-mabs-whats-new-mabs.md
High Priority View Details →
Scanned: 2026-01-10 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 for Microsoft Azure Backup Server (MABS) exhibits a strong Windows bias. Features and support are consistently described in terms of Windows Server versions, Windows-specific technologies (ReFS, Hyper-V, PowerShell, registry keys), and Windows-centric workloads (SQL Server, Exchange, SharePoint). There are no examples, instructions, or references for Linux environments, Linux-based VMs, or Linux backup scenarios. Windows tools and patterns (e.g., registry keys, PowerShell cmdlets, right-click context menus) are mentioned exclusively, with no Linux equivalents or parity.
Recommendations
  • Add explicit support statements and examples for Linux-based VMs and workloads, if supported.
  • Include Linux-centric backup scenarios, such as item-level recovery for Linux VMs, and instructions for Linux file systems.
  • Provide Linux command-line examples (e.g., bash scripts, CLI commands) alongside PowerShell examples.
  • Mention Linux tools and configuration patterns (e.g., config files, systemd services) where applicable.
  • Clarify any limitations or lack of support for Linux environments, and link to relevant cross-platform backup solutions if MABS is Windows-only.
  • Ensure parity in documentation structure: for every Windows feature or example, provide the Linux equivalent or state its absence.
GitHub Create Pull Request
Backup Back up Azure Managed Disks ...docs/blob/main/articles/backup/backup-managed-disks.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation primarily describes backup operations using the Azure portal and references automation via PowerShell and CLI scripts. PowerShell is mentioned before CLI in the only place where scripting is discussed, and there are no explicit Linux-specific examples or references to Linux tools or shell scripting. The documentation does not provide parity in examples for Linux users, such as bash scripts or CLI-first workflows, nor does it mention Linux-specific considerations or patterns.
Recommendations
  • When mentioning automation, list Azure CLI before or alongside PowerShell to avoid Windows-first impression.
  • Provide explicit examples for both PowerShell and Azure CLI, including sample commands for Linux/macOS environments.
  • Include references to bash scripting or Linux shell environments where applicable.
  • Add notes or sections highlighting any Linux-specific considerations, such as permission management or environment setup.
  • Ensure that all downloadable script templates are available in both PowerShell (.ps1) and bash (.sh) formats.
GitHub Create Pull Request
Backup Back Up a PostgreSQL Databases by Using the Azure CLI ...ocs/blob/main/articles/backup/backup-postgresql-cli.md
High Priority View Details →
Scanned: 2026-01-10 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 in several ways. PowerShell is referenced as the default or primary object model for policy manipulation, and PowerShell objects are described before CLI/file-based workflows. There are multiple mentions of PowerShell and Windows-centric patterns (such as using objects and .\ notation for file paths), while Linux-specific examples (such as Bash scripting or Linux file paths) are minimal or absent. The CLI examples use Windows-style file paths (e.g., .\filename.json) and do not provide Linux equivalents (e.g., ./filename.json). There is no explicit mention of Linux tools or workflows, and the documentation does not address cross-platform differences in scripting or file handling.
Recommendations
  • Provide Linux/Bash examples alongside Windows/PowerShell examples, especially for file manipulation and scripting.
  • Use platform-neutral file path notation in CLI examples (e.g., ./filename.json instead of .\filename.json), or show both Windows and Linux variants.
  • Clarify differences in object handling between PowerShell and Bash, and offer Bash-native workflows for policy editing and manipulation.
  • Explicitly mention that the Azure CLI is cross-platform and provide guidance for Linux users where workflows differ.
  • Avoid presenting PowerShell as the default or primary workflow; instead, present CLI and Bash workflows first or in parallel.
  • Add a section on Linux prerequisites or environment setup for Azure CLI usage.
GitHub Create Pull Request
Backup Azure Backup release notes - Archive .../main/articles/backup/backup-release-notes-archived.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits a moderate Windows bias, primarily through frequent references to Windows-specific backup tools (MARS agent, Microsoft Azure Backup Server), and repeated mention of PowerShell as a management interface. Windows tools and features (MARS, MABS) are described in detail, often without equivalent Linux alternatives or parity in example coverage. In sections where both Windows and Linux workloads are supported (e.g., SAP HANA on RHEL), Linux support is mentioned but not elaborated upon, and Windows-centric tools are introduced first or exclusively. PowerShell is often listed as a primary automation interface, with Azure CLI mentioned less frequently or as an afterthought.
Recommendations
  • Provide equivalent Linux-focused examples and tooling references (e.g., Bash/CLI scripts, Linux agent details) wherever Windows tools like MARS or MABS are discussed.
  • Ensure parity in coverage for Linux workloads (such as SAP HANA on RHEL, PostgreSQL) by including explicit Linux management instructions and examples.
  • When listing automation interfaces, mention Azure CLI and REST API before or alongside PowerShell, and provide sample commands for both.
  • For features that are Windows-specific, clarify their scope and suggest Linux alternatives or note limitations for Linux users.
  • Expand documentation on Linux backup scenarios, including troubleshooting, agent installation, and integration with native Linux tools.
GitHub Create Pull Request
Backup Troubleshoot SQL Server database backup ...rticles/backup/backup-sql-server-azure-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-10 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 a strong Windows bias. All examples, file paths, and troubleshooting steps reference Windows-specific tools, directories (e.g., C:\Program Files), and concepts. The AzureBackupWindowsWorkload extension is mentioned exclusively, with no mention of Linux equivalents. Troubleshooting steps and error resolutions reference Windows features such as Control Panel, Local Security Policy, NT AUTHORITY\SYSTEM, and PowerShell, with no guidance for Linux-based SQL Server VMs. There are no Linux file path examples, nor instructions for Linux-based environments.
Recommendations
  • Add explicit guidance and troubleshooting steps for SQL Server running on Linux-based Azure VMs.
  • Include Linux file path examples (e.g., /opt/azureworkloadbackup) alongside Windows paths.
  • Document the installation and management of Azure Backup workload extensions for Linux VMs, or clarify if not supported.
  • Provide PowerShell and Bash/CLI equivalents for all command-line instructions.
  • Reference Linux-specific tools and configuration patterns (e.g., systemd services, Linux permissions) where applicable.
  • Clarify any feature limitations or differences between Windows and Linux SQL Server VM backup support.
GitHub Create Pull Request
Backup Back up SQL Server from the Azure VM blade using Azure Backup ...ckup/backup-sql-server-database-from-azure-vm-blade.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page focuses exclusively on backing up SQL Server databases on Azure VMs using Windows-specific tools and extensions. It references the AzureBackupWindowsWorkload extension, NT Service accounts, and SQLIaaSExtension, all of which are Windows-centric. There are no examples, instructions, or mentions of Linux-based SQL Server VMs, nor any Linux-specific backup tools or patterns. The documentation implicitly assumes the SQL Server VM is running Windows, and does not address Linux parity.
Recommendations
  • Add explicit guidance and examples for backing up SQL Server databases on Linux-based Azure VMs.
  • Document any differences in backup tooling, extensions, or service accounts for Linux SQL Server VMs.
  • If Azure Backup does not support Linux SQL Server VMs, state this clearly and provide alternative solutions or workarounds.
  • Include Linux command-line examples (e.g., using Azure CLI, shell scripts) where relevant.
  • Mention any Linux-specific prerequisites or configuration steps alongside Windows instructions.
GitHub Create Pull Request
Backup Back up multiple SQL Server VMs from the vault ...rticles/backup/backup-sql-server-database-azure-vms.md
High Priority View Details →
Scanned: 2026-01-10 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 demonstrates a Windows bias in several ways: it references Windows-specific tools and extensions (e.g., AzureBackupWindowsWorkload, NT Service\AzureWLBackupPluginSvc), links to Windows-only connectivity test scripts, and omits any mention of Linux-based SQL Server VMs or their backup procedures. All examples, screenshots, and instructions assume a Windows environment, with no guidance for Linux users. The documentation also refers to the Azure Virtual Machine Agent using a Windows-specific link and does not clarify Linux support or differences.
Recommendations
  • Add explicit guidance and examples for backing up SQL Server on Linux-based Azure VMs, including any differences in prerequisites, agent installation, and extension support.
  • Provide parity in troubleshooting tools, such as connectivity test scripts for Linux environments.
  • Clarify whether features like auto-protection, backup policies, and extensions are supported on Linux SQL Server VMs, and document any limitations.
  • Include Linux-specific links and instructions alongside Windows ones, especially for agent installation and configuration.
  • Ensure that references to service accounts, extensions, and permissions are applicable or alternatives are provided for Linux VMs.
GitHub Create Pull Request
Backup Back up SQL Server always on availability groups ...les/backup/backup-sql-server-on-availability-groups.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses exclusively on SQL Server deployments in Azure VMs, which are predominantly Windows-based. There is no mention of Linux-based SQL Server deployments, nor are there examples or instructions for Linux environments. All backup mechanisms, node registration, and extension installation processes are described in a way that assumes Windows VMs and Windows tooling. There is no reference to Linux-specific commands, tools, or considerations, and the documentation does not clarify whether the described processes apply to SQL Server on Linux or mixed OS AGs.
Recommendations
  • Explicitly state whether the backup process supports SQL Server AGs running on Linux VMs, and if so, provide Linux-specific instructions.
  • Include examples and guidance for registering and backing up AG nodes on Linux-based SQL Server instances, including any differences in extension installation or management.
  • Mention any limitations or differences in Azure Backup support for SQL Server AGs on Linux, such as supported versions, backup scheduling, or failover handling.
  • Provide parity in troubleshooting steps, error codes, and workflows for Linux environments.
  • Reference Linux tools (e.g., Bash, systemd, Linux file paths) where appropriate, and clarify if PowerShell or Windows-only tools are required.
GitHub Create Pull Request
Backup Automation in Azure Backup support matrix ...blob/main/articles/backup/backup-support-automation.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page consistently lists PowerShell as the first automation method for nearly every operation, and provides PowerShell examples for all supported scenarios. PowerShell is a Windows-centric tool, and its prioritization in the table order and example links signals a Windows bias. There is no explicit mention of Linux shell scripting, Bash, or Linux-specific automation patterns. The CLI is included and supported, but PowerShell is always listed first, and the documentation does not clarify cross-platform usage or provide parity guidance for Linux users.
Recommendations
  • Alternate the order of PowerShell and CLI columns, or list CLI first for operations where it is more cross-platform.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Add notes or sections highlighting Linux automation patterns (e.g., Bash scripting, cron jobs) where applicable.
  • Provide example scripts for Linux environments alongside PowerShell examples, especially for common automation scenarios.
  • Clarify in the introduction that PowerShell examples are primarily for Windows, and direct Linux users to CLI or REST API examples.
  • Where PowerShell is not supported (e.g., SAP HANA), highlight CLI as the primary method for Linux users.
GitHub Create Pull Request
← Previous Page 21 of 65 Next →